Getting Started Under z/OS

In this section:

This section contains information about accessing each adapter under z/OS. Before you can invoke an adapter, it must be installed and operational.

In the z/OS operating environment, TSO controls the adapter and the FOCUS session. The adapter can access RDBMS tables interactively from TSO, with TSO batch processing, or as a z/OS batch job.

You can allocate the FOCUS and adapter load libraries (both from the same version and release of FOCUS) directly in your CLIST, or your site may choose to allocate them to DDNAME STEPLIB in your TSO logon procedure. (The FOCUS installation guide discusses the FOCUS CLIST in greater detail.)

To display the current FOCUS version and release, issue the ? RELEASE query command at the FOCUS prompt.

To run FOCUS interactively, you invoke a CLIST from TSO using standard allocations for DDNAMEs FOCEXEC, ERRORS, and MASTER. Allocate FOCSQL to the library containing Access Files. Allocate FOCLIB to the FOCUS product load library. You must create a new member in the ERRORS concatenation called EDASERVE which will contain the access parameters for the relational adapter you will be accessing.

The allocations in batch are similar to those in the CLIST, with a few changes. The STEPLIB allocation replaces the FOCLIB allocation from the CLIST. You must allocate the file containing executable FOCUS commands to DDNAME SYSIN. Output is written to the file or SYSOUT class allocated to DDNAME SYSPRINT.

The following topics provide CLIST and JCL examples for accessing each adapter. The FOCUS commands are coded in-stream in the samples. However they could have been stored in a data set. The FIN command is required to terminate FOCUS.

For proper JOB card specifications and data set names for your site, consult with your system support staff. For additional information on FOCUS and batch processing, refer to your FOCUS documentation.

Note: The discussions in this section assume that all of your FOCUS and adapter libraries are catalogued under the same z/OS high-level qualifier. The examples throughout this section use the identifier hlq to refer to this high-level qualifier.
Top of page
x
Accessing DB2 Under z/OS

Reference:

You must know whether the adapter was installed with the Call Attachment Facility (CAF) or Call Level Interface (CLI). The CLIST requirements are different in each case.

You must also know the four-character subsystem identifier (SSID) of the DB2 subsystem you will access and the plan name assigned to the Adapter for DB2 when it was installed. The defaults for the SSID and plan values are DSN and DSQL respectively, unless your site changed these defaults at installation time.

If the adapter was installed with the Call Attachment Facility (CAF), you can use the SET SSID and SET PLAN environmental commands to specify the SSID and plan name from FOCUS (see Adapter Commands). For CLI installations, you will connect to DB2 using a CONNECT statement.

After you prepare your CLIST or JCL, ask your database administrator whether you require SELECT, INSERT, and/or UPDATE privileges for the tables or views you wish to access.
x
Reference: Accessing the Adapter for DB2 Interactively Under CAF Using an EDASERVE Configuration File

You can use this sample CLIST as a template. Edit it to conform to the standards of your site.

ALLOC F(FOCLIB)    DA('hlq.FOCLIB.LOAD') SHR REUSE 
ALLOC F(ERRORS)    DA('user.DB2CAF.CFG' -
                      'hlq.ERRORS.DATA') SHR REUSE 
ALLOC F(MASTER)    DA('user.MASTER.DATA' -       
                      'hlq.MASTER.DATA') SHR REUSE
ALLOC F(FOCSQL)    DA('user.FOCSQL.DATA' -       
                      'hlq.FOCSQL.DATA') SHR REUSE
ALLOC F(FOCEXEC)   DA('user.FOCEXEC.DATA' -       
                      'hlq.FOCEXEC.DATA') SHR REUSE
CALL 'hlq.FOCLIB.LOAD(FOCUS)'

where:

hlq

Is the high-level qualifier for your FOCUS production data sets.

user

Is the high-level qualifier for the private version of a data set.

Note:

Execute the CLIST to invoke FOCUS and issue the following commands at the FOCUS prompt, pressing Enter after each line.

SQL DB2 ?                                               
SQL DB2                                                 
SELECT * FROM SYSIBM.SYSDUMMY1;              
END

If the adapter settings and the request output displayed, the installation and connection were successful. Issue the following command to exit FOCUS.

FIN
x
Reference: Accessing the Adapter for DB2 Interactively Under CAF Using the RRSET Module

You can use this sample CLIST as a template. Edit it to conform to the standards of your site.

ALLOC F(FOCLIB)    DA('hlq.USE.FOCSQL.LOAD' -      
                      'hlq.FOCLIB.LOAD') SHR REUSE 
ALLOC F(ERRORS)    DA('hlq.ERRORS.DATA') SHR REUSE 
ALLOC F(MASTER)    DA('user.MASTER.DATA' -         
                      'hlq.MASTER.DATA') SHR REUSE 
ALLOC F(FOCSQL)    DA('user.FOCSQL.DATA' -        
                      'hlq.FOCSQL.DATA') SHR REUSE 
ALLOC F(FOCEXEC)   DA('user.FOCEXEC.DATA'    
                      'hlq.FOCEXEC.DATA') SHR REUSE 
CALL 'hlq.FOCLIB.LOAD(FOCUS)'

where:

hlq

Is the high-level qualifier for your FOCUS production data sets.

user

Is the high-level qualifier for the private version of a data set.

Note:

Execute the CLIST to invoke FOCUS and issue the following commands at the FOCUS prompt, pressing Enter after each line.

SQL DB2 ?                                               
SQL DB2                                                 
SELECT * FROM SYSIBM.SYSDUMMY1;              
END

If the adapter settings and the request output displayed, the installation and connection were successful. Issue the following command to exit FOCUS.

FIN
x
Reference: Accessing the Adapter for DB2 in Batch Under CAF Using an EDASERVE Configuration File

You can use this sample JCL as a template. Edit it to conform to the standards of your site 

//job card goes here      
//*                                                            
//FOCDB2  EXEC PGM=FOCUS                                       
//STEPLIB  DD  DSN=hlq.FOCSQL.LOAD,DISP=SHR     
//         DD  DSN=hlq.FOCLIB.LOAD,DISP=SHR     
//         DD  DSN=DSNn10.SDSNLOAD,DISP=SHR     
//ERRORS   DD  DSN=hlq.ERRORS.DATA,DISP=SHR    
//         DD  DSN=user.DB2CAF.CFG,DISP=SHR    
//MASTER   DD  DSN=user.MASTER.DATA,DISP=SHR
//         DD  DSN=hlq.MASTER.DATA,DISP=SHR    
//FOCEXEC  DD  DSN=user.FOCEXEC.DATA,DISP=SHR
//         DD  DSN=hlq.FOCEXEC.DATA,DISP=SHR 
//FOCSQL   DD  DSN=user.FOCSQL.DATA,DISP=SHR
//         DD  DSN=hlq.FOCSQL.DATA,DISP=SHR  
//SYSPRINT DD  SYSOUT=*                                 
//SYSIN    DD  *                                        
SQL DB2 ?                                               
SQL DB2                                                 
SELECT * FROM SYSIBM.SYSDUMMY1;              
END                                                     
FIN                                                 
/*

where:

hlq

Is the high-level qualifier for your FOCUS production data sets.

n

Is the version of DB2 you will use with FOCUS.

user

Is the high-level qualifier for the private version of a data set.

Note:

If the adapter settings and the request output displayed, the installation and connection were successful.
x
Reference: Accessing the Adapter for DB2 in Batch Under CAF Using the RRSET Module

You can use this sample JCL as a template. Edit it to conform to the standards of your site 

//job card goes here      
//*                                                            
//FOCDB2  EXEC PGM=FOCUS                                       
//STEPLIB  DD  DSN=hlq.USE.FOCSQL.LOAD,DISP=SHR   
//         DD  DSN=hlq.FOCSQL.LOAD,DISP=SHR         
//         DD  DSN=hlq.FOCLIB.LOAD,DISP=SHR         
//         DD  DSN=DSNn10.SDSNLOAD,DISP=SH          
//ERRORS   DD  DSN=hlq.ERRORS.DATA,DISP=SHR    
//MASTER   DD  DSN=user.MASTER.DATA,DISP=SHR
//         DD  DSN=hlq.MASTER.DATA,DISP=SHR       
//FOCEXEC  DD  DSN=user.FOCEXEC.DATA,DISP=SHR
//         DD  DSN=hlq.FOCEXEC.DATA,DISP=SHR  
//FOCSQL   DD  DSN=user.FOCSQL.DATA,DISP=SHR
//         DD  DSN=hlq.FOCSQL.DATA,DISP=SHR   
//SYSPRINT DD  SYSOUT=*                                 
//SYSIN    DD  *                                        
SQL DB2 ?                                               
SQL DB2                                                 
SELECT * FROM SYSIBM.SYSDUMMY1;              
END                                                     
FIN                                                 
/*

where:

hlq

Is the high-level qualifier for your FOCUS production data sets.

n

Is the version of DB2 you will use with FOCUS.

user

Is the high-level qualifier for the private version of a data set.

Note:

If the adapter settings and the request output displayed, the installation and connection were successful.
x
Reference: Accessing the Adapter for DB2 Interactively Using CLI

Edit the following CLIST to conform to the standards at your site. This CLIST assumes that the adapter was installed with the Call Level Interface (CLI) 

ALLOC F(FOCLIB)    DA('hlq.FOCLIB.LOAD') SHR REUSE 
ALLOC F(ERRORS)    DA('user.DB2CLI.CFG' -
                      'hlq.ERRORS.DATA') SHR REUSE 
ALLOC F(MASTER)    DA('user.MASTER.DATA' -       
                      'hlq.MASTER.DATA') SHR REUSE
ALLOC F(FOCSQL)    DA('user.FOCSQL.DATA' -       
                      'hlq.FOCSQL.DATA') SHR REUSE
ALLOC F(FOCEXEC)   DA('user.FOCEXEC.DATA' -       
                      'hlq.FOCEXEC.DATA') SHR REUSE
CALL 'hlq.FOCLIB.LOAD(FOCUS)'

where:

hlq

Is the high-level qualifier under which you installed FOCUS. In this example, user.DB2CLI.CFG contain the members EDASERVE and FOCPROF.

user

Is the high-level qualifier for a library allocated under the user ID of a specific user.

Note: user.DB2CLI.CFG contains the members EDASERVE and FOCPROF.

Execute the CLIST to invoke FOCUS and issue the following commands at the FOCUS prompt, pressing Enter after each line.

SQL DB2 ?                                               
SQL DB2                                                 
SELECT * FROM SYSIBM.SYSDUMMY1;              
END

If the adapter settings and the request output displayed, the installation and connection were successful. Issue the following command to exit FOCUS.

Your DB2 database administrator can supply the parameters and the attachment facility chosen at the time the adapter was installed.
x
Reference: Accessing the Adapter for DB2 in Batch Using CLI

If the FOCUS load libraries are not allocated in your TSO logon procedure, use the following JCL after editing it to conform to the standards at your site. This CLIST assumes that the adapter was installed with the Call Level Interface (CLI) 

//FOCUSDB2  EXEC PGM=FOCUS,REGION=64M                                  
//STEPLIB  DD DSN=DSNn10.SDSNEXIT,DISP=SHR 
//         DD DSN=DSNn10.SDSNLOAD,DISP=SHR 
//         DD DSN=DSNn10.SDSNLOD2,DISP=SHR         
//         DD DSN=hlq.FOCLIB.LOAD,DISP=SHR           
//DB2LOAD  DD DSN=DSNn10.SDSNLOAD,DISP=SHR         
//ERRORS   DD DSN=user1.DB2CLI.CFG,DISP=SHR                    
//         DD DSN=hlq.ERRORS.DATA,DISP=SHR              
//FOCLIB   DD DSN=hlq.FOCLIB.LOAD,DISP=SHR          
//SYSPRINT DD SYSOUT=*                                               
//SYSTSPRT DD SYSOUT=*                                               
//FOCEXEC  DD DSN=hlq.FOCEXEC.DATA,DISP=SHR                    
//MASTER   DD DSN=hlq.MASTER.DATA,DISP=SHR                 
//FOCSQL   DD DSN=user1.FOCSQL.DATA,DISP=SHR    
//SYSIN DD *                                                     
  SQL DB2 ?  
  FIN                                              
/*

where:

n

Is your version of DB2, for example, 10 (A).

hlq

Is the high-level qualifier under which you installed FOCUS. In this example, hlq.FOCUS.DB2CLI.CFG contain the members EDASERVE and FOCPROF.

user1

Is the high-level qualifier for a library allocated under the user ID of a specific user.

Note: user1.DB2CLI.CFG contains the members EDASERVE and FOCPROF.

Your DB2 database administrator can supply the parameters and the attachment facility chosen at the time the Ladapter was installed.
Top of page
x
Accessing Teradata Under z/OS

Reference:

The communications link between your address space and the Teradata Director Program (TDP) is implemented with either MVS/XMS (Cross Memory Services) or Supervisor Call (SVC). (Your systems programming group determines the type of link during Teradata installation.)

After you prepare your CLIST or JCL, you must:

For DBC/SQL GRANT information and the SET CONNECTION_ATTRIBUTES command, see Connection, Authentication, and Security.

For information about the adapter SET AUTOCLOSE command, which enables you to control logon interaction with Teradata, see Controlling Connection Scope.
x
Reference: Interactive Access to Teradata Under z/OS

Create a CLIST by editing the following sample CLIST to conform to the standards at your site. 

ALLOC F(ERRORS)  DA('hlq.DBCCLI.CFG' +
                    'hlq.ERRORS.DATA') SHR REUSE
ALLOC F(FOCLIB)  DA('hlq.FOCLIB.LOAD') SHR REUSE
ALLOC F(FOCEXEC) DA('hlq.FOCEXEC.DATA') SHR REUSE
ALLOC F(MASTER)  DA('hlq.MASTER.DATA') SHR REUSE
ALLOC F(ACCESS)  DA('user.ACCESS.DATA') SHR REUSE
CALL 'hlq.FOCLIB.LOAD(FOCUS)'

where:

hlq

Is the high-level qualifier for your FOCUS production data sets.

user

Is the high-level qualifier for the private version of a data set.

Note: In this example, hlq.DBCCLI.CFG contains the members EDASERVE and FOCPROF. The EDASERVE member contains the following attributes:

dbc_cli = y      
dbc_access = y
x
Reference: Batch Access to Teradata Under z/OS

Create a job by adding a JOB card and editing the following sample JCL to conform to the standards at your site. 

job card goes here
//SQLMX    EXEC PGM=FOCUS,REGION=0M                                  
//STEPLIB  DD DSN=hlq.FOCLIB.LOAD,DISP=SHR           
//ERRORS   DD DSN=hlq.DBCCLI.CFG,DISP=SHR                    
//         DD DSN=hlq.ERRORS.DATA,DISP=SHR              
//FOCLIB   DD DSN=hlq.FOCLIB.LOAD,DISP=SHR          
//SYSPRINT DD SYSOUT=*                                               
//FOCEXEC  DD DSN=hlq.FOCEXEC.DATA,DISP=SHR                    
//MASTER   DD DSN=hlq.MASTER.DATA,DISP=SHR                 
//ACCESS   DD DSN=user.ACCESS.DATA,DISP=SHR    
//SYSIN DD *                                                     
   ENGINE SQLDBC ?
  FIN                                              
/*

where:

hlq

Is the high-level qualifier for your FOCUS production data sets.

user

Is the high-level qualifier for the private version of a data set.

Note: In this example, hlq.DBCCLI.CFG contains the members EDASERVE and FOCPROF. The EDASERVE member contains the following attributes:

dbc_cli = y      
dbc_access = y
Top of page
x
Accessing IDMS SQL Under z/OS

In this section:

Steps for invoking the adapter vary from site to site. You may be required to complete a series of menus or to execute a CLIST. Since the adapter can operate under IDMS Central Version or in Local Mode, you need to include allocations for the appropriate mode in your CLIST or JCL.

After you prepare your CLIST or JCL, ask your database administrator whether you require SELECT, INSERT, and/or UPDATE privileges for the tables or views you need to access.

If your database administrator (DBA) has turned on IDMS SQL security, the proper privileges must be granted to every adapter user. The DBA should grant you:

For more information on security and table privileges, consult Connection, Authentication, and Security. Additional prerequisites and file types are discussed in this chapter.
Example: Sample JCL for Central Version Access to IDMS

You can use the following sample JCL as a template for CV access. Add a valid job card and edit it to conform to the standards and naming conventions at your site: 

//job card goes here
//IDMSCV   EXEC PGM=FOCUS
//STEPLIB  DD  DSN=highlvl.DBA.LOADLIB,DISP=SHR
//         DD  DSN=highlvl.LOADLIB,DISP=SHR
//         DD  DSN=prefix.IDMS.LOAD,DISP=SHR
//         DD  DSN=prefix.FOCLIB.LOAD,DISP=SHR
//ERRORS   DD  DSN=prefix.ERRNLS.DATA,DISP=SHR
//         DD  DSN=prefix.ERRORS.DATA,DISP=SHR
//MASTER   DD  DSN=prefix.MASTER.DATA,DISP=SHR
//         DD  DSN=userid.MASTER.DATA,DISP=SHR
//FOCIDMS  DD  DSN=prefix.ACCESS.DATA,DISP=SHR
//FOCEXEC  DD  DSN=prefix.FOCEXEC.DATA,DISP=SHR 
//         DD  DSN=userid.FOCEXEC.DATA,DISP=SHR 
//SYSCTL   DD  DSN=highlvl.SYSCTL,DISP=SHR
//SYSIDMS  DD  DSN=highlvl.SYSIDMS,DISP=SHR
//SYSIN    DD   *
? REL
TABLE FILE EMPFILE
PRINT EMP_NAME_0415
END
FIN

where:

highlvl

Is the high-level qualifier for Computer Associates supplied data sets.

prefix

Is the high-level qualifier for FOCUS production data sets.

userid

Is the high-level qualifier for a private data set belonging to the user.
Example: Sample CLIST for Central Version Access to IDMS

You can use the following sample CLIST as a template for CV access. Edit it to conform to the standards and naming conventions at your site: 

ALLOC DD(STEPLIB) DA('highlvl.DBA.LOADLIB'-
                     'highlvl.LOADLIB') SHR REUSE
ALLOC F(FOCEXEC) DA('prefix.FOCEXEC.DATA' -
                    'userid.FOCEXEC.DATA') SHR REUSE
ALLOC F(MASTER)  DA('prefix.MASTER.DATA' -
                    'userid.MASTER.DATA') SHR REUSE
ALLOC F(FOCIDMS) DA('prefix.ACCESS.DATA') SHR REUSE
ALLOC F(USERLIB) DA('prefix.IDMS.LOAD') SHR REUSE
ALLOC F(FOCLIB)  DA('prefix.FOCLIB.LOAD') SHR REUSE
ALLOC F(ERRORS)  DA('prefix.ERRNLS.DATA' -
                    'prefix.ERRORS.DATA') SHR REUSE
ALLOC F(SYSCTL)  DA('highlvl.SYSCTL') SHR REUSE
ALLOC F(SYSIDMS) DA('highlvl.SYSIDMS') SHR REUSE
CALL 'prefix.FOCLIB.LOAD(FOCUS)'

where:

highlvl

Is the high-level qualifier for Computer Associates supplied data sets.

prefix

Is the high-level qualifier for FOCUS production data sets.

userid

Is the high-level qualifier for a private data set belonging to the user.
x
Local Mode Access

The user must allocate all IDMS database files. These files must be allocated to the ddnames that are assigned in the IDMS/DB Schema.

All journal file allocations must be made available along with the default local mode journal, SYSJRNL, assigned to DD DUMMY.

In some cases, the libraries containing the subschema, DMCL, and IDMSINTB load modules may not be authorized. If STEPLIB cannot be used for unauthorized IDMS libraries, in a local mode job you can allocate these unauthorized modules to ddname CDMSLIB. With CDMSLIB allocated, IDMS will search the CDMSLIB before STEPLIB to obtain all IDMS/DB specific load modules.
x
Both Central Version and Local Mode

The IDMS load modules IDMS and IDMSINTB must be made available at run-time, allocated to the ddname STEPLIB.

When running a CLIST, the STEPLIB ddname is not valid. These members must be allocated to either the link list or in the TSO logon procedure. Contact your Systems Programmer to add these members.

The member names of the FOCUS Master Files and Access Files to read the subschema must be identically named and made available at run time.

SYSIDMS can be allocated to identify the DMCL for both CV and LOCAL modes.
Top of page
x
Accessing Oracle Under z/OS

How to:

Reference:

You must indicate which Oracle subsystem is to be accessed.

Note: All Oracle tools and programs that use the Oracle Pro or High Level Interfaces (such as the Adapter for Oracle) require the services of the SQL Storage Anchor Module (SQLANKOR). This module resides in a library member for which the Oracle-recommended name is:

'ORACLE.V10203.CMDLOAD(CMDLOAD)' (for Oracle Version 10).

This module is generally placed in a STEPLIB, JOBLIB or system linklist library. It must be present at run time.

Any application that accesses the Oracle RDBMS must provide a means of connecting to the Oracle subsystem (or kernel).

x
Procedure: How to Connect to the Oracle Subsystem

You can set the Oracle SID by using the Oracle SET SSID command. You can issue this command in the FOCPROF profile. Alternatively, if the SID is at most four characters, you can specify it in your CLIST or JCL.

To set the SID using the SET SSID command, issue the following:

ENGINE SQLORA SET SID sid

where:

sid

Is the Oracle Subsystem ID.

This should be set before setting the USER or CONNECTION parameters and can be placed in the FOCPROF member.

If the sid is at most four characters, you can specify it in either your CLIST or JCL, instead of in FOCPROF, using the following DD allocation:

//ORA@sid DD DUMMY

where:

sid

Is the Oracle Subsystem ID.

In your CLIST, you also need to add the following allocation:

ALLOC F(ORA$LIB)  DA('ORACLE.V10203.MESG') SHR REUSE

Where ORACLE.V10203.MESG is your installation Oracle MESG library.

The TSO session also needs to have the following data sets available to it in the STEPLIB allocation, either explicitly or implicitly, using the naming conventions at your site:

ORACLE.V10203.CMDLOAD
ORACLE.V10203.MESG

If you are running in batch, the STEPLIB allocation in the JCL should have the following as part of the concatenation:

//         DD DSN=ORACLE.V10203.CMDLOAD,DISP=SHR       
//         DD DSN=ORACLE.V10203.MESG,DISP=SHR

The job also needs the ORA$LIB allocation:

//ORA$LIB  DD DSN=ORACLE.V10203.MESG,DISP=SHR
x
Reference: Creating a Batch Job to Invoke FOCUS

Create a job by adding a JOB card and editing the following sample JCL to conform to the standards at your site. 

job card goes here
//SQLMX    EXEC PGM=FOCUS,REGION=0M                                  
//STEPLIB  DD DSN=hlq.FOCLIB.LOAD,DISP=SHR 
//ERRORS   DD DSN=hlq.ORACLI.CFG,DISP=SHR   
//         DD DSN=hlq.ERRORS.DATA,DISP=SHR     
//ORA$LIB  DD DSN=ORACLE.V10203.MESG,DISP=SHR
//FOCLIB   DD DSN=hlq.FOCLIB.LOAD,DISP=SHR 
//SYSPRINT DD SYSOUT=*                                               
//FOCEXEC  DD DSN=hlq.FOCEXEC.DATA,DISP=SHR 
//MASTER   DD DSN=hlq.MASTER.DATA,DISP=SHR
//ACCESS   DD DSN=user.ACCESS.DATA,DISP=SHR    
//SYSIN    DD *  
  SQL SQLORA
   SELECT TABLE_NAME, OWNER, TABLESPACE_NAME FROM ALL_TABLES
   WHERE ROWNUM <= 10
  END
 FIN                                              
/*

where:

hlq

Is the high-level qualifier for your FOCUS production data sets.

user

Is the high-level qualifier for the private version of a data set.

ORACLE.V10203.MESG

Is your installation Oracle MESG library.

Note: If the Oracle sid is at most four characters, you can specify it in your JCL, instead of in FOCPROF. For information, see How to Connect to the Oracle Subsystem.

In this example, hlq.ORACLI.CFG has the member EDASERVE. EDASERVE contains the following attributes:

ora_oci = y      
ora_rel = 10     
ora_access = y

If the job produces a list of tables, owners, and tablespaces, the adapter installation is verified.

Note: The JESLOG may produce a message similar to the following, which can be ignored:

14.11.28 JOB23212  $HASP708 JOBNAME SYSIN    OPEN FAILED
   959             RC=03 DATA SET ALREADY OPENED 
   959             DSNAME=USERID.JOBNAME.JOBjobid.D0000101.?

where:

USERID

Is the USERID of the running JOB.

JOBNAME

Is the name of the JOB from the JOB card.

jobid

Is the system-assigned job number of the job.

D0000101

Is the system-generated identifier to keep the DSNAME unique.
x
Reference: Creating a CLIST to Invoke FOCUS Interactively

Create a CLIST by editing the following sample CLIST to conform to the standards at your site. 

ALLOC F(ERRORS)  DA('hlq.ORACLI.CFG' +
                    'hlq.ERRORS.DATA') SHR REUSE
ALLOC F(ORA$LIB) DA('ORACLE.V10203.MESG') SHR REUSE
ALLOC F(FOCLIB)  DA('hlq.FOCLIB.LOAD') SHR REUSE
ALLOC F(FOCEXEC) DA('hlq.FOCEXEC.DATA') SHR REUSE
ALLOC F(MASTER)  DA('hlq.MASTER.DATA') SHR REUSE
ALLOC F(ACCESS)  DA('user.ACCESS.DATA') SHR REUSE
CALL 'hlq.FOCLIB.LOAD(FOCUS)'

where:

hlq

Is the high-level qualifier for your FOCUS production data sets.

user

Is the high-level qualifier for the private version of a data set.

ORACLE.V10203.MESG

Is your installation Oracle MESG library.

Note: If the Oracle sid is at most four characters, you can specify it in your CLIST, instead of in FOCPROF. For information, see How to Connect to the Oracle Subsystem.

In this example, hlq.ORACLI.CFG has the member EDASERVE. EDASERVE contains the following attributes: 

ora_oci = y       
ora_rel = 10      
ora_access = y

Use your CLIST to invoke FOCUS, and issue the following command at the FOCUS prompt.

SQL SQLORA
SELECT TABLE_NAME, OWNER, TABLESPACE_NAME FROM ALL_TABLES
WHERE ROWNUM <= 10
END

If the command produces a list of tables, owners, and tablespaces, the adapter installation is verified.

Issue the following command to exit FOCUS.

FIN
Top of page
x
Additional Prerequisites: File Descriptions

The adapter requires a Master and Access File for each RDBMS table referenced by FOCUS. In z/OS, file descriptions and FOCEXECs are stored as members of partitioned data sets (PDSs). The partitioned data sets are allocated to the following DDNAMEs:

DDNAME

Contents (PDS Members)

MASTER

Master Files.

FOCSQL or ACCESS

Access Files.

FOCEXEC

Stored procedures.

Execute the AUTODB2 FOCEXEC supplied with the Adapter for DB2 or the AUTODBC CLIST supplied with the Adapter for Teradata, to automatically create Master and Access Files for existing RDBMS tables. You can customize the resulting descriptions with a text editor. Automated Procedures, describes step-by-step instructions for the AUTO facilities.

You can create new table definitions in the RDBMS from the FOCUS environment by issuing either the FOCUS CREATE FILE command (after creating a Master File and an Access File) or the SQL CREATE TABLE command. See Automated Procedures, for the FOCUS CREATE FILE command.

Information Builders