JCL requirements for the Online Structure Change utility

DD statements for the Online Structure Change utility determine the input and output data sets and specify how to run the utility.

Subsections:

List of DD statements

The following table summarizes the DD statements for the OSC driver job of the Online Structure Change utility.
Table 1. DD statements for the Online Structure Change utility
DDNAME Use Format Can be dynamically allocated? Required or optional
JOBLIB or STEPLIB Input PDS No Required
IMSACB Input PDS No Required when IMSCATHLQ=*NO
NEWACB Input PDS No Required when IMSCATHLQ=*NO
HFPSYSIN Input LRECL=80 No Required
HFPPRINT Output SYSOUT Yes Optional
HFPRPTS Output LRECL=133 Yes Optional
HFP3XMSG Output LRECL=133 Yes Optional
HFP3XTRA Output LRECL=133 Yes Optional
Note: Do not specify RECONx, IMSDALIB, HFPDDCHK, HFP1JCLD, and HFP1ENQ DD statements.

Input DD statements

The following input DD statements are used for the Online Structure Change utility.

JOBLIB DD
STEPLIB DD
This DD statement is a required DD statement that defines the following input data sets:
  • OSC load module library (required)
  • Library that contains the site default member (HFPOCTL0) (optional)
  • Library that contains the base configuration module HFP#imsid or HFPSETOP (optional)
  • Library that contains the IMS Tools Common Pauser base configuration module FOIUSOPT (optional)
  • IMS load module library (required)
  • IMS Tools Base library SFOILOAD (required)
  • IMS Tools Base library SGLXLOAD (required when IMSCATHLQ is specified)
  • IMS Tools Base library SHKTLOAD (required when ITKBSRVR is specified)

The Online Structure Change utility must be run as an APF-authorized program. All the data sets in the JOBLIB or the STEPLIB concatenation must also be APF-authorized.

IMSACB DD
This DD statement is a required DD statement. It defines the library that contains the active ACB member for the database.

If you specify the IMSCATHLQ keyword, IMSACB DD statements are not used. The IMS directory is used instead of the ACB library.

NEWACB DD
This DD statement is a required DD statement. It defines the library that contains the staging ACB member for the database.

If you are using a DFSMDA member with TYPE=IMSACB to specify the ACBLIB staging library, the NEWACB DD statement of the OSC driver job must specify the same ACBLIB library.

If you specify the IMSCATHLQ keyword, NEWACB DD statement is not used. The IMS directory is used instead of the ACB library.

HFPSYSIN DD
This DD statement is a required DD statement that defines the input control statement for the Online Structure Change utility.

The HFPSYSIN DD statement can be coded as a standard SYSIN file, a sequential data set, or a PDS member. LRECL=80 is required for the DCB of this data set.

The Online Structure Change utility analyzes the command syntax in columns 1 - 72. Columns 73 - 80 are regarded as comment.

For details about coding the HFPSYSIN DD statement, see Utility control statements for the Online Structure Change utility.

Output DD statements

The following output DD statements are used for the Online Structure Change utility.

HFPPRINT DD
This DD statement is an optional DD statement that defines the processing log output data set to which the Online Structure Change utility writes processing messages.
The following DCB attributes of the file are set by the OSC main task:
  • RECFM=FBA
  • LRECL=133
  • BLKSIZE=1330
Do not code the DCB information in your JCL statement. The output data set must be a standard SYSOUT or a sequential data set. You cannot specify DUMMY.
The HFPPRINT data set contains 133-byte, fixed-length records. It is recommended that you code the DD statement as follows:
//HFPPRINT DD SYSOUT=A
Note on dynamic allocation:
When this statement is not specified in the JCL statements, the Online Structure Change utility dynamically allocates the data set by using SYSOUT=*.
HFPRPTS DD
This DD statement is an optional DD statement that defines the report output data set.
The following Online Structure Change utility reports, which you can use to verify the processes that are run by the Online Structure Change utility, are written to this data set:
  • Audit report
  • Processing report
  • DBD Definition reports for both active DMB obtained from IMSACB and staging DMB obtained from NEWACB
  • Base Configuration report
  • OSC Internal Jobs Scenario report
The following DCB attributes of the file are set by the OSC main task:
  • RECFM=FBA
  • LRECL=133
  • BLKSIZE=1330
Do not code the DCB information in your JCL statement. The output data set must be a standard SYSOUT or a sequential data set.
The HFPRPTS data set contains 133-byte, fixed-length records. It is recommended that you code the DD statement as follows:
//HFPRPTS DD SYSOUT=A
Note on dynamic allocation:
When this statement is not specified in the JCL statements, the Online Structure Change utility dynamically allocates the data set by using SYSOUT=*.
HFP3XMSG DD
This DD statement is an optional DD statement that defines the processing log output data set to which the XCF CONNECT task writes processing messages.

The output data set must be a standard SYSOUT or a sequential data set.

The HFP3XMSG data set contains 133-byte, fixed-length records.

Note on dynamic allocation:
When this statement is not specified in the JCL statements, the Online Structure Change utility dynamically allocates the data set by using SYSOUT=*.
HFP3XTRA DD
This DD statement is an optional DD statement that defines output data set that the Online Structure Change utility uses to write diagnostic trace records. This data set might be required for problem diagnosis.

The HFP3XTRA data set contains 133-byte, fixed-length records.

Note on dynamic allocation:
When this statement is not specified in the JCL statements, the Online Structure Change utility dynamically allocates the data set by using SYSOUT=*.
Output destination of other reports
  • Apply report is generated in the data set that the HFPRPTS DD statement of the internal apply job (xxxxxxA0) specifies.
  • Other reports, such as unload and reload reports, are generated in the report data set that is specified in each OSC internal job.