JCL requirements for PCPRRELD

(required) Code the EXEC statement as follows:

If you do not want to change the order of the segments within the database record, you can run PCPRRELD in load mode. To do so, the PSB specified bypsbname must use a PROCOPT of L or LS. If you want to change the order of the segments within the record, you must run PCPRRELD in update mode with a PROCOPT of A. The PSB must also have the parameter LANG=ASSEM or LANG=COBOL coded on the PSBGEN statement.

Specify 0M for the REGION size.

You can use the DLIBATCH procedure to run PCPRRELD. If you do, code the EXEC statement as follows:

or

(required) Insert the BMC Software load library ahead of the IMS RESLIB library.

Required if the STEPLIB concatenation includes any libraries that are not APF-authorized. This statement describes the library (typically the IMS RESLIB) containing the IMS execution modules.

(required) This statement describes the libraries that contain the DBD and PSB needed to access the database.

(required) If you use a PSB with PROCOPT of A and DBRC is specified as Yes or Force, this statement describes the primary system log data set. If you are not using an update PSB and/or DBRC is specified as NO, you can code this statement as DUMMY.

(optional) If you use a PSB with PROCOPT of A and DBRC is specified as Yes or Force, this statement describes the secondary system log data set. You can code this statement as DUMMY.

(required) This statement defines the data set that contains information used by the DL/I buffer handler.

Required as an input file if the database you are restructuring has logical relationships and/or secondary indexes defined for it. This statement defines the informational data set produced by the IMS Prereorganization utility.

Required as an output file if the database you are restructuring has logical relationships and/or secondary indexes defined for it. This statement defines the data set to which PCPRRELD will write logical relationship and/or secondary index work records. This data set will be used as input to the job steps that resolve and update logical relationship information and/or rebuild secondary indexes.

(optional) These data sets define the DBRC control data sets. BMC Software recommends that you do not include RECON DD statements in your JCL. Instead, add an MDALIB that contains the RECON data sets to your STEPLIB concatenation.

(required) PCPRRELD writes informational reports to this data set. The default DCB parameters are LRECL=121 and BLKSIZE=7260.

(optional) This statement defines the output data set to contain snaps of various PCPRRELD control blocks, including the DB-PCB at the time that an insert fails. If an abend occurs, BMC Software can use these snaps for debugging problems. Normally you would define it as a SYSOUT-type data set.

(optional) This statement defines the output data set that contains snaps of any blocks in error and miscellaneous data set statistics. Normally you would define it as a SYSOUT-type data set.

(optional) This statement defines a dump data set. If PCPRRELD encounters any problems, it prints an error message in the SYSPRINT data set and then abends. This data set contains the dump for use in resolving the problem.

(optional) This statement defines the load library that contains the user exit routine you want PCPRRELD to call for processing the records before loading them into the database. Using-a-COBOL-II-user-exit provides further information for coding and using a user exit with PCPRRELD.

(required) This statement defines the sequential data set that contains the unloaded database. Provide one datain statement for each database PCPRRELD will load in this job step. The ddname on this statement corresponds to the ddname coded on the control statement in column 21.

(required) This statement defines the IMS database data set to load. Provide one statement for each database data set PCPRRELD will load in this job step. The ddname on this statement must match the ddname specified in the DBD.

Required if you want to use the LOADPLUS LPI. This statement defines the LPI control statement data set. The LPI control statement you should use consists of the command USERLOAD and the keyword PCB. The value of the PCB keyword defines one PCB within the PSB that the LPI will service. You can specify the PCB either by number or name, using a maximum of 100 characters. Other keywords and statements are valid for the LPI.

(required) This statement defines the control statement data set. If you code the BLKSIZE parameter, its value must be a multiple of 80. Three types of control statements are valid in the SYSIN data set for program PCPRRELD:

• DB

  Describes the database that PCPRRELD will load

• SEG

  Defines a segment PCPRRELD must change before loading it into the database

• CHG

  Defines the change that PCPRRELD will make to the segment described by the preceding SEG statement

PCPRRELD can load multiple databases per job step, change multiple segments in each database, and make multiple changes to each segment. Therefore, the order of the statements in the SYSIN data set is important:

• The DB statement is required and must be first in the data set.
• One or more SEG statements can follow the DB statement, and they apply to the database described with the preceding DB statement.
• One or more CHG statements can follow each SEG statement, and they apply to the segment described with the preceding SEG statement.

The parameters on the control statements are positional; their meanings are based on the columns in which they start. The following sections describe the control statements in detail.