DYNDB

PCP can dynamically allocate input data sets if you do not provide the DD statement in the JCL.

Use the DYNDB option to tell PCP whether to allocate the database data set itself or the most recent image copy. You can also use the DYNDB option to provide the prefix to use if PCP cannot obtain the data set name from the dynamic allocation library or the RECON data set.

PCP can use one of several methods to dynamically allocate the database data set if you do not provide it in the JCL. It tries the methods in the following order:

It retrieves the dynamic allocation member of the data set from the IMS RESLIB library or dynamic allocation library identified with the DFSRESLB DD statement (if present) or from the STEPLIB concatenation (if the DFSRESLB DD statement is not in the JCL or does not contain the DFSMDA member). In either case, the DFSRESLB or STEPLIB must point to the library that contains the dynamic allocation member created by the DFSMDA macro. Using the data set name defined in the dynamic allocation member, PCP dynamically allocates the data set.
If it cannot find a dynamic allocation member, PCP uses the prefix value of the DYNDB option to dynamically allocate the database data set with the following data set name:
prefix.dbdname.ddname
where prefix is the prefix you provided, dbdname is the name of the DBD, and ddname is the ddname of the data set group.

PCP can use one of several methods to dynamically allocate the image copy data set if you do not provide it in the JCL. It tries the methods in the following order:

It invokes DBRC to obtain the name of the latest database image copy from the RECON data sets, and using the information obtained from DBRC, it dynamically allocates the data set. For IMS Version 2.1 and higher, it honors the CATDS/NOCATDS indicator stored in DBRC; if the indicator is set to CATDS, PCP uses the system catalog to retrieve the unit name, volume serial number, and file sequence number. If the image copy is a GDG, PCP obtains the absolute GDG name.
If it cannot dynamically allocate the image copy because the data set is not registered to DBRC or the RECON data set indicates that the image copy is not usable, PCP uses the prefix value of the DYNDB option to dynamically allocate the image copy with the following data set name:
prefix.dbdname.ddname(+0)
where prefix is the prefix you provided, dbdname is the name of the DBD, and ddname is the ddname of the data set group.

Note

This option is not available when you execute PCP concurrently with another utility (the other utility controls the input process).

Uses	You can set the DYNDB option at the following levels: Global options module Generated JCL GLBL control statement
ISPF panel field	Input Is Image Copy DB Prefix
PCPSYSIN keyword	DYNDB(type,prefix)
Values	Specify one or both of the following positional values. If you omit the type value, use a comma to indicate the omission. type Specify the type of data set to allocate: IC Retrieve the data set name of the latest image copy from the RECON data set. DB Retrieve the data set name of the database from the dynamic allocation member in the dynamic allocation library. prefix Specify the high-level qualifier of the data set name to allocate if PCP cannot obtain it from the dynamic allocation library or the RECON data set. This qualifier can be 1-17 characters, including periods. When you use this option on a control statement, the prefix is necessary only if you are not using the global options module or if you need to override the value in the global options module.
Default	type: IC prefix: none
Example	In the following example, PCP allocates a database data set named IMSVS.V22.HDAM01.HDAMDD1 if the DD statement is not coded in the JCL and there is no dynamic allocation member for HDAM01: GLBL DYNDB(DB,IMSVS.V22) CHECK DBD(HDAM01)

DYNDB

On this page