Bitmap Resetter JCL requirements
To run a Bitmap Resetter job, code the EXEC statement and DD statements that satisfy the Bitmap Resetter JCL requirements.
The keywords for the JCL stream that are needed to run the Bitmap Resetter utility is shown in the following table.
DDNAME | Use | Format | Need |
---|---|---|---|
STEPLIB | Input | Required See Note 1 | |
IMS | Input | Required | |
HPSIN | Input | LRECL=80 | Required |
RECONx | Input | Optional for Non-HALDB Required for HALDB |
|
database | Input/Output | Optional See Note 2 | |
IMSDALIB | Input | Same as that used in the IMS control region startup JCL stream | Optional |
HPSOUT | Output | LRECL=133 | Required |
HPSOUT2 | Output | LRECL=133 | Required |
SYSUDUMP | Output | LRECL=133 | Optional |
Notes:
|
- EXEC
- Must
be in the following form:
//name EXEC PGM=HPSBRSET,PARM='dbdname,DBRC=Y'
- dbdname
- The name of the DBD.
- DBRC=
-
- Y
- Requires DBD authorization. Specify DBRC=Y when you process HALDBs.
- N
- If DBRC=FORCE is set in SCD, returns HPSB0601E error. To use for a HALDB, you must set DBRC=Y.
- STEPLIB DD
-
//STEPLIB DD DISP=SHR,DSNAME=pgmlib // DD DISP=SHR,DSNAME=IMSESA.RESLIB
- pgmlib
- The name of the library that contains the load module of Bitmap Resetter.
- IMSESA.RESLIB
- The name of the library that contains the IMS load modules.
- IMSDALIB DD
- Specifies
a partitioned data set or data sets that contain the dynamic allocation
members for the database and the RECON data sets.
Allocation of the database and the RECON data sets is attempted in the following order:
- The DD statements that are coded in the JCL stream
- Dynamic allocation members in the IMSDALIB concatenation
- Dynamic allocation members in JOBLIB or STEPLIB concatenation
- IMS DD
- Describes the library that contains the DBD referred to in the PARM field of the EXEC statement. This data set must reside on a direct-access device.
- HPSIN DD
- Defines a data set that contains control statements that specify the functions of Bitmap Resetter. This DD statement is required. If the DD is omitted, the run terminates. For details about control statements, see Bitmap Resetter control statements.
- RECON1 DD
- Defines the first Database Recovery Control (DBRC) RECON data set.
- RECON2 DD
- Defines the second DBRC RECON data set.
- RECON3 DD
- Defines the optional DBRC RECON data set that is used when an
error is encountered in RECON1 or RECON2. This RECON data set must
be the same RECON data set as the one the control region is using. Note: If you use dynamic allocation, these RECON data set ddnames must not be used.
- database DD
- Defines
the database data set to be reset. You need one statement for each
data set that appears in the DBD that describes this database. The
ddname must match the ddname in the DBD. No DD statements are required
for whatever primary index and secondary indexes that might be associated
with this database. This data set must reside on a direct-access
device. Note: If you use dynamic allocation, do not use the DD statement for the database data sets.
For HALDBs, no DD statements are necessary for any database data sets because the data sets are always dynamically allocated.
- HPSOUT DD
- Reports, such as the HPSIN control statements report, Parameters and DBD/Data Sets report, error and warning messages, and Bitmap Reset Process Summary report, are printed. If the DD is omitted, the run terminates.
- HPSOUT2 DD
- Old and new contents of bitmap is printed. If the DD is omitted, no report is printed.
- SYSUDUMP DD
- Defines a dump data set. Most errors encountered end the Bitmap Resetter utility job by issuing an ABEND macro with the DUMP operand. Only a SYSUDUMP DD is needed. The SYSABEND DD statement is not required.