IDMS Installation Process (MVS)

Customizing the IEBCOPY JCL in IDMS

There are two data sets on the distribution tape which were created using the IEBCOPY utility. Create an IEBCOPY procedure like the one listed below and submit it for execution.

//COPYPDS  EXEC  PGM=IEBCOPY
//SYSPRINT DD SYSOUT=*
//INDD1    DD  DSN=IDMS.LOAD,DISP=OLD,
//         UNIT=unit,VOL=SER=volser,LABEL=(9,SL),
//INDD2    DD  DSN=IDMS.DATA,DISP=OLD,
//         UNIT=unit,VOL=SER=volser,LABEL=(10,SL)
//OUTDD1   DD DSN=prefix.IDMS.LOAD,DISP=(,CATLG,DELETE),
//         UNIT=SYSDA,SPACE=(TRK,(10,5,45),RLSE)
//OUTDD2   DD DSN=prefix.IDMS.DATA,DISP=(,CATLG,DELETE),
//         UNIT=SYSDA,SPACE=(TRK,(15,5,45),RLSE)
//SYSIN DD *
  COPY INDD=INDD1,OUTDD=OUTDD1
  COPY INDD=INDD2,OUTDD=OUTDD2
/*

where:

unit

Is the tape/cartridge.

volser

Is the tape/cartridge serial number.

prefix.IDMS.LOAD

Is the Data Adapter load library.

prefix.IDMS.DATA

Is the Data Adapter source library.

Upon successful completion there are two new PDS data sets cataloged on your system. The data set names will depend on what you specified on your IEBCOPY OUTDD1 and OUTDD2 ddcards.

Preparing the Run-time Libraries (MVS) in IDMS

1. Using your site criteria, allocate a partitioned data set (PDS) for your Access Files as ddname FOCIDMS. This library (or libraries) can be a mirror image of ddname MASTER and should have the same DCB parameters. Refer to your FOCUS MVS/TSO installation guide for assistance in selecting DCB parameters. Two suggested names for this data set are:
• prefix.ACCESS.DATA or
• prefix.FOCIDMS.DATA

Note: prefix.ACCESS.DATA and prefix.FOCIDMS.DATA are used interchangeably throughout this document.

2. The FOCUS description of an IDMS database is called a Master File. It is stored as a member of a PDS which is allocated to ddname MASTER in the FOCUS CLIST/JCL. Refer to your FOCUS MVS/TSO installation guide for assistance allocating this PDS.
3. A stored FOCUS procedure is called a FOCEXEC. A FOCEXEC is stored as a member of a PDS which is allocated to ddname FOCEXEC in the FOCUS CLIST/JCL. Refer to your FOCUS MVS/TSO installation guide for assistance allocating this PDS.

Customizing the FOCUS CLIST in IDMS

The FOCUS CLIST used to execute the IDMS Data Adapter must be modified to include the Access File PDS and the PDS containing the IDMS Data Adapter load modules. The 'prefix.IDMS.LOAD' data set, defined in Customizing the IEBCOPY JCL, includes the IDMS load modules that must be concatenated to the USERLIB, FOCLIB or STEPLIB ddnames. It is important to note that if multiple copies of the IDMS Data Adapter exist, the load module will be searched for in USERLIB first, followed by FOCLIB then STEPLIB. For batch jobs, however, allocate all load libraries to the ddname STEPLIB.

The 'prefix.IDMS.DATA' dataset, defined in Customizing the IEBCOPY JCL, contains a member named FOCIDMS which contains the IDMS Data Adapter error messages. This data set must be concatenated to the ERRORS ddname in the FOCUS CLIST. Failure to concatenate this data set to the ERRORS ddname results in the following message when using the Data Adapter:

(FOC000) ERROR MESSAGE TEXT MISSING

The CLIST or JCL must contain these allocations:

1. The PDS containing Access Files.
2. The PDS containing Master Files.
3. The PDS containing FOCUS procedures (FOCEXECs).
4. The PDS containing FOCUS error messages.
5. The PDS containing the Data Adapter load modules and FOCUS load modules.
6. The IDMS run-time load modules (refer to Accessing IDMS in Central Version and Local Mode for addition information).

The following chart identifies the allocations needed to execute a FOCUS procedure (FOCEXEC) against an IDMS database:

* For batch jobs, allocate all load modules to the ddname STEPLIB.

Linking the IDMS Data Adapter to Run Below the Line (IDMS Release 10.2 Only)

If you are running IDMS release 10.2, you must re-link the IDMSR module to run below the line. Following is a sample of the JCL needed to re-link:

//LKED  EXEC PGM=IEWL,PARM='LET,LIST,NCAL,XREF'
//OLDMOD    DD DSN=prefix.IDMS.LOAD,DISP=SHR
//SYSLMOD   DD DSN=prefix.IDMS.LOAD,DISP=SHR
//SYSPRINT  DD SYSOUT=*
//SYSUT1    DD UNIT=SYSDA,SPACE=(CYL,(1,1))
//SYSLIN    DD *
  MODE AMODE(24),RMODE(24)
  ENTRY   IDMSR
  INCLUDE OLDMOD(IDMSR)
  NAME    IDMSR(R)
/*

where:

prefix.IDMS.LOAD

Is the IDMS Data Adapter load library supplied by Information Builders.

Installing the AUTOIDMS Facility (MVS)

The 'prefix.IDMS.DATA' data set contains four members that must be renamed and copied into the appropriate libraries according to the chart below:

* Member IDMSI10M is the Master File that describes the IDMS/DB 10.2 dictionary. When it is renamed to IDMSIDD, AUTOIDMS correctly describes your release 10.2 subschemas.

The following JCL is located in member GENFAUTO in the 'prefix.IDMS.DATA' data set. This JCL unloads and renames the members needed for the AUTOIDMS facility.

Note: If you are upgrading the AUTOIDMS facility, manually delete old IDMS IDD Master and Access Files to ensure all new dictionary files are installed.

//COPYPDS   EXEC PGM=IEBCOPY
//SYSPRINT  DD SYSOUT=*
//INDD1     DD DSN=prefix.IDMS.DATA,DISP=SHR
//OUTDD1    DD DSN=prefix.MASTER.DATA,DISP=SHR
//OUTDD2    DD DSN=prefix.ACCESS.DATA,DISP=SHR
//OUTDD3    DD DSN=prefix.FOCEXEC.DATA,DISP=SHR
//SYSIN     DD *
  COPY INDD=INDD1,OUTDD=OUTDD1
  SELECT MEMBER=((IDMSIDDM,IDMSIDD))
  COPY INDD=(INDD1,R),OUTDD=OUTDD1
  SELECT MEMBER=((AUTOIDMM,AUTOIDMS))
  COPY INDD=INDD1,OUTDD=OUTDD2
  SELECT MEMBER=((IDMSIDDA,IDMSIDD))
  COPY INDD=INDD1,OUTDD=OUTDD3
  SELECT MEMBER=((AUTOIDMS,,R))

where:

prefix.IDMS.DATA

Is the unloaded PDS from the install tape.

prefix.MASTER.DATA

Is the PDS containing FOCUS Master Files.

prefix.ACCESS.DATA

Is the PDS containing Access Files.

prefix.FOCEXEC.DATA

Is the PDS containing FOCUS procedures.

AUTOIDMS and Secondary Dictionaries (MVS)

AUTOIDMS is a utility that generates FOCUS Master Files for IDMS subschemas. By default, AUTOIDMS searches for subschema descriptions in the primary dictionary. However, subschemas frequently reside in dictionaries other than the primary dictionary. These are called secondary dictionaries. When a subschema being described by AUTOIDMS is located in a secondary dictionary, DBNAME= and DICTNAME= parameters are needed in the AUTOIDMS Access File, the IDMSIDD member of ddname FOCIDMS. See Determining Which IDD Dictionaries Will Be Accessed for more information on how to set up a secondary dictionary environment.

Determining Which IDD Dictionaries Will Be Accessed (MVS) in IDMS

If there is only one primary dictionary used to generate descriptions, skip to Changing the Default Data Set Names. This topic sets up AUTOIDMS to access several IDD secondary dictionaries (these are the dictionaries where subschemas reside).

1. Determine which IDD dictionaries are accessed by AUTOIDMS. For each dictionary, select a one character identifier. This value is used to uniquely identify the dictionary for reporting purposes and is displayed on the Main Menu of AUTOIDMS. The identifier may be the letter A through Z, the number 0 through 9, or blank. For example, if you have a primary IDD dictionary and secondary dictionaries for production and test, you might select blank (primary dictionary), P (secondary production dictionary), and T (secondary test dictionary) as the identifiers.
2. Copy and rename the following files, once for each suffix selected in the previous step
   (where n represents the identifier):

From:	To:
prefix.MASTER.DATA(IDMSIDD)	prefix.MASTER.DATA(IDMSIDDn)
prefix.ACCESS.DATA(IDMSIDD)	prefix.ACCESS.DATA(IDMSIDDn)

3. Edit prefix.ACCESS.DATA(IDMSIDDn) to include the appropriate DBNAME and DICTNAME on the first line. For example

SSCHEMA=IDMSNWKA,RELEASE=14,DBNAME=SYSDIRL,DICTNAME=SYSDIRL,$

4. Edit prefix.FOCEXEC.DATA(AUTOIDMS). Locate the line that reads:

-DEFAULT &DICT_FILES=' ' 

Change the value to include each of the identifiers selected in Step 1 of this topic, and only those values. The first character is used as the default dictionary on the AUTOIDMS Main Menu. For example, if you chose P, T, and blank as your identifiers and you wish to have the production dictionary as the default, the line would read:

-DEFAULT &DICT_FILES='PT '

This indicates the following dictionaries:

P	Is the IDMSIDDP dictionary.
T	Is the IDMSIDDT dictionary.
blank	Is the IDMSIDD dictionary.

Note: Characters must be entered in upper case.

5. Repeat Steps 2 and 3 above for each of the identifiers that were selected in Step 1.

Changing the Default Data Set Names (MVS) in IDMS

AUTOIDMS displays default output data set names for the Master File, Access File, and FOCDEF file. These defaults follow standard Information Builders naming conventions. The defaults are changed on a per-user basis by replacing the values on the screen and then logging them to disk for subsequent use. Alternatively, the AUTOIDMS FOCEXEC can be modified to include site-specific naming conventions for all users.

To customize the initial data set defaults for all users, edit the following lines in the AUTOIDMS member of 'userid.FOCEXEC.DATA'. Change the expression on the right-hand side of the equal sign as appropriate. The resulting expression must retain a length of 44 characters (&USERID accounts for eight characters). You only need to customize the following lines:

-SET &DSNP0=&USERID ||'.FOCIDMS.DATA          ';
-SET &DSNM0=&USERID ||'.MASTER.DATA           ';
-SET &DSNF0=&USERID ||'.FOCIDMS.DATA          ';

where:

&DSNP0

Is the menu parameter log data set.

&DSNM0

Is the Master File output data set.

&DSNF0

Is the Access File output data set.

Verifying IDMS and AUTOIDMS Installation (MVS)

To verify the installation process, begin a FOCUS session and enter:

TABLE FILE IDMSIDDn
PRINT SS_NAM_026
IF RECORDLIMIT EQ 10
END

where:

n

Represents the secondary dictionary identifier.

These commands, due to the record limit, will create a report that includes up to 10 subschemas from the selected dictionary. Repeat this report for each dictionary.

If the record limit was not included, the report would contain all subschemas for that dictionary defined in the DICTNAME. We recommend including the record limit. If you are looking for a particular subschema, execute

TABLE FILE IDMSIDDn
PRINT SS_NAM_026
WHERE SS_NAM_026 EQ 'subschema_name'
END

where:

subschema_name

Is the value you are interested in.