Getting Started Under VM/CMS

This section describes how to access each data adapter interactively under VM/CMS.

In this section: Accessing DB2 for VM Accessing Teradata Under VM/CMS Accessing Oracle Under VM/ CMS Additional Prerequisites: File Descriptions

Note: The IDMS/SQL Data Adapter is not available under VM.

In the VM operating environment, the CMS teleprocessing monitor controls the data adapter and FOCUS session. The data adapter can access RDBMS tables interactively. Techniques for running FOCUS in batch CMS may also be available at your site; those techniques are not discussed here. In addition to RDBMS tables, you can access VSAM data sources, FOCUS data sources, and other data sources with the appropriate data adapters installed.

Accessing DB2 for VM

Note: As of V6.1, SQL/DS has been renamed to DB2 for VM.

The following is a general outline of steps for invoking the DB2 for VM Data Adapter. The details vary from site to site:

1. After logging on to VM, link to and access the FOCUS production disk.

2. Execute an initialization EXEC.

The EXEC should link to the DB2 for VM production disk and execute SQLINIT, an IBM EXEC. The SQLINIT procedure creates bootstrap modules for the appropriate DB2 for VM data source and places them on the disk accessed as filemode A.

Note: You do not have to rerun SQLINIT unless you want access to a different DB2 for VM data source. You may wish to have your EXEC check for the existence of the bootstrap modules and conditionally execute SQLINIT if they do not exist.)

The following is a sample procedure

CP LINK SQLDBA 195 485 RR password
ACCESS 485 Q
EX SQLINIT DB(dbname)

where:

password

Is the read password for the DB2 for VM production disk.

dbname

Is the name of the DB2 for VM data source.

You can issue these commands interactively before entering the FOCUS environment, but it is probably more convenient to include them in an EXEC that issues them automatically.

3. Invoke FOCUS. If your userid is authorized to CONNECT to DB2 for VM, no further action is required. In some cases, you may need to issue the DB2 for VM CONNECT command. For information on CONNECT syntax and usage, see Connection, Authentication, and Security.

Accessing Teradata Under VM/CMS

The following is a general outline of steps for invoking the Teradata Data Adapter. The details vary from site to site:

1. After logging on to VM, link to and access the FOCUS production disk.

2. Link to and access the Teradata production disk, which is usually labeled TDAPP.

3. Issue the GLOBAL TXTLIB command to identify the CLI text library.

4. Invoke FOCUS.

5. Issue the data adapter SET CONNECTION_ATTRIBUTES command. Connection, Authentication, and Security discusses the CONNECTION_ATTRIBUTES command.

6. Obtain SELECT and/or UPDATE privileges from your DBC administrator (see Connection, Authentication, and Security for information).

Steps 1-4 can be issued interactively, but it is probably more convenient to include the commands in an EXEC so that they are issued automatically. The following is a sample initialization EXEC:

CP LINK F7009709 191 491 RR 
CP LINK TDAPP 195 495 RR
ACCESS 491 F
ACCESS 495 P
GLOBAL TXTLIB FUSELIB CLI
EXEC FOCUS

Accessing Oracle Under VM/CMS

Before invoking FOCUS and the Oracle Data Adapter, you must link to the Oracle-supplied production disk, which contains the run-time Oracle software required by the data adapter. Typically this disk is the ORACLE 191 disk (sometimes referred to as the Oracle user disk).

You must also link to the FOCUS production disk, which is required of all FOCUS users.

The formats of the LINK and ACCESS commands are as follows:

CP LINK ORACLE 191 391 RR
ACCESS 391 O
EXEC ORAIBMC ** required for ORACLE Version 7.0 and up.

These commands may be issued interactively before invoking FOCUS, but it is probably more convenient to include them in your PROFILE EXEC or PROFILE FOCEXEC so that they are issued automatically.

Once the Oracle production disk has been accessed, FOCUS may be invoked. It may be necessary for you to issue the data adapter SET CONNECTION_ATTRIBUTES command from within FOCUS. For more information on the SET CONNECTION_ATTRIBUTES command, see Connection, Authentication, and Security.

For Oracle 7.0 and above the following command must be issued:

EXEC ORAIBMC

This command must be executed before invoking FOCUS. It is convenient to include it in the user's PROFILE EXEC or PROFILE FOCEXEC.

Additional Prerequisites: File Descriptions

The data adapter requires a Master and Access File for each table referenced by FOCUS. In VM/CMS, file descriptions and FOCEXECs exist as separate files. The naming conventions are:

File Type	Contents
MASTER	Master Files.
FOCSQL	Access Files.
FOCEXEC	FOCUS procedures.

Execute the AUTOSQL EXEC supplied with the DB2 for VM Data Adapter or the AUTODBC EXEC supplied with the Teradata Data Adapter to automatically create Master and Access Files for existing DB2 for VM or Teradata 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 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.