This document provides standard sample JCL for IDMS batch utilities.
Release : All supported releases.
The following is a standard starting point for any IDMS batch utility JCL. Items in lower case text must be replaced by site specific names.
//PGM EXEC PGM=pgmname,REGION=0M
//STEPLIB DD DISP=SHR,DSN=idms.dba.loadlib
// DD DISP=SHR,DSN=idms.custom.loadlib
// DD DISP=SHR,DSN=idms.cagjload
//SYSCTL DD DISP=SHR,DSN=idms.cv.sysctl
//SYSIPT DD *
input statements to the utility
//SYSIDMS DD *
ECHO=ON
DMCL=dmclname
LOCAL=on/off
//SYSPCH DD SYSOUT=*
//SYSLST DD SYSOUT=*
CV-mode vs local-mode
If the JCL contains a SYSCTL ddname, then the decision of whether the step will run in CV-mode or local-mode depends on the LOCAL parameter in SYSIDMS. OFF (the default) means CV-mode, ON means local-mode. The dataset that SYSCTL points to is the SYSCTL file of the CV against which the step should run.
If there is no SYSCTL ddname, the LOCAL parameter is ignored and the step will run in local-mode.
If the step is to run in local-mode, then any database files whose dataset name is not specified in the DMCL that the utility will need to access must be defined in the JCL. If the CV has a SYSTRK ddname, then this can be achieved by defining that file to the local mode step:
//SYSTRK DD DISP=SHR,DSN=idms.cv01.systrk
If the CV does not have a SYSTRK ddname, then any such database files must be explicitly defined to the batch step. Example:
//DICTDB DD DISP=SHR,DSN=idms.cv01.dictdb
//DLODDB DD DISP=SHR,DSN=idms.cv01.dloddb
Notes:
Information in this document assumes that a site-specific IDMSOPTI is not in use.