Skeleton JCL for generating MSDB Dump Recovery utility JCL
IMS DEDB Fast Recovery generates DD statements for the MSDB Dump Recovery utility from the skeleton input. The output can be used as a part of JCL for the MSDB Dump Recovery utility.
Skeleton JCL for creating MSDB Dump Recovery utility JCL
The following figure is an example of a skeleton JCL for the MSDB Dump Recovery utility.
Specify $$IEFRDER
where you want to insert the IEFRDER DD statement, and
$$MSDBCP
where you want to insert the MSDBCPn DD statements.
The JCL is written in the input data set specified by the MSDBIN DD statement. The completed JCL statements are written in the output data set specified by MSDBOUT1 and MSDBOUT2 DD statements. These two data sets produce the same output data.
$$ statements for MSDB Dump Recovery utility JCL
The $$ statement is specified in the skeleton JCL, and will be replaced by necessary DD
statements in the generated JCL. If the first and second columns of the skeleton JCL contain
$$
, the line is interpreted as a $$ statement. The $$ statements can be specified
multiple times. If there is an error in the $$ statement, the error statement is ignored and the
process is continued.
There are two types of $$ statements:
- $$IEFRDER or $$stepname.IEFRDER
- If you want to specify a job step name, specify stepname. An IEFRDER DD
statement, with DSN= and DISP=SHR subparameters, will be inserted at this place.
This DD statement describes the log data sets that contain the IMS system log, which is used for the MSDB recovery operations. In a dual logging environment, if an error is detected in the primary log data set, the secondary log data set name will be set.
- $$MSDBCP or $$stepname.MSDBCP
- If you want to specify a job step name, specify stepname. An
MSDBCPn DD statement, with DSN= and DISP=SHR subparameters, will be inserted at
this place. n is from 1 to 4 when the IMS
system to recover is an XRF complex, from 1 to 2 in other cases.
This DD statement describes the MSDB checkpoint data sets. The specification differs according to how you specify MSDB=. For details of specifying the MSDB= parameter, read JCL requirements.