Storing and Acessing Parameters Under z/OS
To store parameters as a member of a PDS, use a utility program such as IEBGENER. The JCL statements follow:
idmscu
To store parameters as a member of a PDS, use a utility program such as IEBGENER. The JCL statements follow:
IEBGENER (z/OS)
// EXEC PGM=IEBGENER //SYSPRINT DD SYSOUT=A //SYSUT1 DD DSN=sequential.data.set,DISP=(OLD,KEEP) //SYSUT2 DD DSN=culprit.srclib,DISP=(OLD,KEEP) //SYSIN DD * GENERATE MAXNAME=1 MEMBER NAME=member-name /* //
culprit.srclib
| PDS into which CA Culprit parameters are to be copied and stored |
member-name
| name under which parameters are to be copied in the PDS |
sequential.data.set
| name of the sequential data set containing CA Culprit parameters to be copied |
At run time, submit the name of the PDS in the //CULLIB DD job control parameter, as shown in
Execution JCL.
CA Culprit will search the named library for the member specified on the USE parameter, =COPY parameter, or =MACRO parameter.IDD
To store parameters as modules in the CA IDMS/DB Integrated Data Dictionary (IDD), see the
CA IDMS IDD DDDL Reference section
. At run time, submit the name of the data dictionary and its associated journal file(s) in the appropriate DD job control statements, as shown in Execution JCL. CA Culprit retrieves the module specified on the USE parameter, =COPY parameter, or =MACRO parameter from the named data dictionary.