Getting Started Under CMS

In the CMS environment, the Interface operates as another application program making calls to ADABAS. All files, FILEDEFs, and disk workspace that FOCUS normally requires under CMS must be present.

Interactive Access From CMS

Below is a general outline of steps to follow when invoking the Interface. The details vary from site to site:

1. After logging on to VM, link to and access the FOCUS production disk, which should have a copy of the Interface load libraries and ADAUSER TEXT.

2. Issue the GLOBAL TXTLIB command to identify the ADABAS text library. The ADABAS text files required by the Interface must be available at runtime, because FOCUS loads the Interface dynamically from a TXTLIB. This TXTLIB must be accessible through a GLOBAL command either before entering FOCUS or from FOCUS. The syntax is

   GLOBAL TXTLIB ADABAS textlib FUSELIB

where:

textlib

Is the user-supplied value for the ADABAS text library.

3. Invoke FOCUS.

Note: In the EXEC used to call FOCUS, there should be a step to execute NUCXTNTS EXEC. This step establishes a link between a VM FOCUS user's machine and the ADABAS nucleus. It must be executed before invoking FOCUS.

File Descriptions

The Interface requires a Master and Access File for each ADABAS file referenced by FOCUS. In CMS, file descriptions and FOCEXECs exist as separate files. The naming conventions are:

File Type	Contents
MASTER	Master Files.
FOCADBS or ACCESS	Access Files.
FOCEXEC	FOCUS procedures.

For more information about Master and Access Files, see Describing ADABAS Files to FOCUS.