IMS Setup menu

The menu that appears for option I (IMS) on the IMS Test Setup Menu is shown in following figure. The screens for these options are used to specify the data sets to be allocated to the IMS ddnames. The nine screens can be selected individually or all together as a complete sequence.

The following screens are required:

• IMS processing types and parameters (option 1)
• IMS authorized load libraries (option 2)
• PSB and DBD libraries (option 3)
• ACB libraries (option 4)

All these parameters are required to debug an IMS program.

The rest of the selections on the menu are optional.

The values specific to each of the screens should have been completed at installation time. You may want to merely verify them, or in some cases, add to or override the installation defaults. For example, you may want to change program parameters specific to your application.

All the IMS setup screens are described in the following subsections.

IMS Setup Menu Screen

IMS Parameter Lists Screen

The IMS Parameter Lists screen shown in following figure lets you specify the valid program types and their corresponding parameter lists.

IMS Parameter Lists Screen

The fields on the IMS Parameter Lists screen are:

TYPE

Enter the IMS program types supported at your site (DLI, DBB, BMP, etc.). Create a separate line for each type and its corresponding PARM list.

PARM LIST

Enter the PARM list for the specified type. Each list contains the program type followed by the keywords ,MODULE,PSB, and the rest of the parameters used at your site. At execution time, the ,MODULE,PSB, string is replaced with the program name and program specification block that the user enters on the test screen.

The supplied default parameter strings probably will not function correctly at your site. If you are uncertain what parameter list to specify, consult one of the following information sources:

• One of your site’s typical DLI/BMP batch PROCs
• Your system programmer
• IBM’s IMS/VS System Programming Reference Manual
• General information available through the HELP screens.

Using APARM Data from JCL

On the Code Debug TSO environments IMS Test screen (2.3), if the file specified in the File List/JCL Member field consists of JCL and its IMS parameter contains APARM data, Code Debug will use that data for the test. Replacement APARM data can be entered in the APARM position of the applicable parameter list on the IMS Parameter List screen. To prevent any APARM data, including that in the JCL, from being sent to the program being tested, enter XPNULLXP in the APARM position of the applicable parameter list.

IMS Load (DFSRESLB) Libraries Screen

The IMS DFSRESLB Libraries screen shown in following figure is used to allocate the dsnames of the IMS authorized load libraries to the DFSRESLB ddname. The DFSRESLB data set contains all the system load modules that make up the IMS software, including both DL/I and the data communications component.

IMS DFSRESLB Libraries Screen

The field on this screen is:

IMS Authorized Load Library DSNAMEs

Enter from one to six dsnames. Consult a batch IMS PROC at your site if you are not sure which dsnames to enter.

PSB and DBD Libraries Screen

The PSB/DBD Libraries screen (following figure) is used to list your IMS PSB and DBD library data set names. The PSBLIB contains your program specification blocks (PSBs). The DBDLIB contains your data base definitions (DBDs). Both of these data sets are required with DB or DB/DC systems. They can also be used if a DL/I batch region is being executed.

PSB/DBD Libraries Screen

The field on the PSB/DBD screen is:

PSB/DBD Library DSNAMEs

Enter from zero to twelve dsnames. Consult a batch IMS PROC at your site if you are unsure of the dsnames. If the application being debugged uses ACB libraries, the DSNAME field can be left blank because the ACBLIB data set stores the combined DBDs and PSBs.

ACB Libraries Screen

The ACB Libraries screen (following figure) is used to enter your ACB library data set names. When an IMS application program is executed, IMS must combine the information in the DBD and PSB before the program can be executed. Your shop can merge the DBD and PSB information in the ACBLIB, so that IMS will not have to do this each time a program runs. The use of the ACBLIB data set is optional for batch IMS programs, but is required for MPP and BMP programs.

ACB Libraries Screen

The field on this screen is:

ACB Library DSNAMEs

Enter from zero to eight dsnames. Consult a batch PROC at your site if you are unsure of the dsnames. The DSNAME field can be left blank if the application being debugged uses PSB and DBD libraries.

IMS Preload List Screen

The IMS Preload List screen lets you enter the PROCLIB data set name. Both IMS and BTS use the PROCLIB ddname to point to the data set where preload specifications are stored. The IMSVS.PROCLIB data set stores all IMS-generated cataloged procedures and jobs. DFSMPLxx is the IMSVS.PROCLIB member that contains the preload list, which is a group of modules to be loaded before IMS loads the user’s program.

A 2-character suffix from a parameter list is used to select the preload list to be executed. For example, suppose you specify that the following DLI parameter list is to be used with your program. (The DLI parameter list shown here would be displayed on your IMS Parameter Lists screen.)

Notice that the sixth parameter is a pair of zeros. This suffix is concatenated with DFSMPLxx to define DFSMPL00 as the name of your preload list. Omit the suffix if no preload list is needed.

IMS Preload List Screen

The field on this screen is:

Preload List Data Set

Enter the name of the data set containing preload lists, not the name of the data set where Code Debug TSO or IMS PROCs are stored, unless the two are identical. Consult an IMS batch PROC at your site if you are not sure which dsname to enter. If this ddname is not required, leave the DSNAME field blank.

Logging and Recovery (IEFRDER) Data set Screen

The IEFRDER Data set screen (following figure) is used to allocate a data set to the IEFRDER ddname. Supplying an IEFRDER data set causes the IMS logging facility to be invoked.

IEFRDER Data set Screen

The fields on this screen are:

DSNAME

Enter a qualified dsname (enclosed in quotes), DUMMY, TEMP, TERM, or SYSOUT (JES data set), or leave this field blank. If the dsname is entered without quotes, the user ID (or other dsname high-level qualifier) is prefixed and quotes are added. If the DSNAME field is left blank, the data set is not allocated.

Consult a batch IMS PROC at your site if you are not sure which dsname to enter. If the IEFRDER ddname is not required, you can leave the DSNAME field blank. Actually, most sites allocate this ddname to DUMMY for debugging rather than leaving it blank. This conforms to common batch and debugging message region usage.

DISP

Valid values for the DISP field are:

If you are allocating an existing data set, you can specify a disposition of SHR, OLD, or MOD. If you do not enter a value in the DISP field, a SHR disposition is assumed. Data sets with a disposition of SHR can be concatenated.

If the DSNAME field contains a value of DUMMY, TEMP, TERM, or SYSOUT, leave the DISP field blank.

Enter a disposition of NEW for a new or temporary data set. If you are allocating a new (DSNAME='qualified-dsname') or temporary file (DSNAME=TEMP), you must enter values for all the fields below except Volume and Unit, which are optional for a NEW or TEMP file.

If you specify a new data set, it is allocated before your debugging session begins and is deallocated immediately after your debugging session ends. The fields for the Process Options for New Data sets let you specify how the new data set is to be allocated and deallocated.

For more information about NEW, OLD, MOD, or SHR data set dispositions, see the Types of Files That Can Be Allocated.

Storage Class

Enter the storage class name defined by your site that contains the data set attributes related to the storage occupied by the data set. A storage class is displayed only when SMS (Storage Management Subsystem) is being used.

Unit

If your site requires it, you must supply a value for the Unit field. Otherwise, leave blank for the default value.

Volume

If your site requires it, you must supply a value for the Volume field. Also enter the volume if you are specifying an uncataloged data set. Otherwise, leave blank for the default value.

Data Class

Enter the data class name defined by your site that contains the data set attributes related to the allocation of the data set. A data class is displayed only when SMS (Storage Management Subsystem) is being used.

Space Units

Valid values are TRK, CYL, or a block size (1-32760).

Primary

Valid values are 0-32760.

Secondary

Valid values are 0-32760.

RECFM

Valid values are FBM, FBA, FB, F, VBM, VBA, VBS, VS, VB, V, and U.

LRECL

Valid values are 0-32760. Omit this field if RECFM is U for undefined length records.

BLKSIZE

Valid values are 0-32760.

If you are allocating a DUMMY or SYSOUT file (DSNAME=DUMMY or DSNAME=SYSOUT), you must enter the block size.

Before Allocation

Valid process options are:

Upon Deallocation

Valid process options are:

IMS Monitor (IMSMON) Data set Screen

The IMSMON Data set screen is used to allocate the DB and DC monitor data sets to the IMSMON ddname. IMS run-time activities, especially database calls, are recorded in the IMS monitor file. This data set can be used as an input for report programs that list, summarize, or analyze IMS activities.

IMSMON Data set Screen

The valid values for the fields on this screen are the same as for the IEFRDER screen. See the Logging and Recovery (IEFRDER) Data set Screen for descriptions of these fields.

VSAM Buffer Pool Screen

The VSAM Buffer Pool screen, shown in following figure, is used to enter the name of the data set that contains the buffer length and the number of buffers to be used for a program.

VSAM Buffer Pool Screen

The field on this screen is:

VSAM Buffer Pool Specification Data Set

The DFSVSAMP data set contains the buffer length and the number of buffers to be used for a program. If not stated, IMS uses a default buffer size. If the DFSVSAMP data set is a PDS, enter its member name.

If VSAM databases are used, this data set must be allocated. Since BTS can attach IMS more than once, define the DFSVSAMP file as a DASD data set so it can be reread. The DFSVSAMP file can also be used for ISAM/OSAM databases.

Consult a batch PROC at your site if you are unsure of the dsname. If this ddname is not required, leave the DSNAME field blank.

IMS Error (IMSERR) Data set Screen

The IMSERR Data set screen (following figure) is used to allocate data sets to the IMSERR ddname. An IMSERR data set contains the formatted dump of the IMS/VS GSAM control blocks when an error occurs, or when a DUMP or SNAP call is issued to a GSAM PCB.

IMSERR Data set Screen

The valid values for the fields on this screen are the same as for the IEFRDER screen. See the Logging and Recovery (IEFRDER) Data set Screen for descriptions of these fields.