Previous Topic: PARM OperandNext Topic: File Descriptions


Reversion Options

The OPTIONS DD contains statements to control how the reversion utility handles schedule IDs, user ID, and JCL IDs that are greater than 255. CA WA CA 7 Edition Version 12.0 permits these ID values as large as 999, but previous releases of CA 7 only permit values up to 255.

Statements with an asterisk in column 1 are comments and are ignored.

Each option must start in column 1 and must be in uppercase.

JCLID=xxxx

Objects with a JCL library ID greater than 255 are changed to a JCL library name of &xxxxnnn where xxxx is a 1 through 12 character value from the JCLID option and nnn is the original JCL library ID. If JCLID is not specified, the default is REVERT. For example, a JCL library ID of 440 is changed to a JCL library name of &REVERT440.

SCHID=nnn

Objects in the active workload with a schedule ID greater than 255 are changed to have the schedule ID specified on the SCHID option. Specify a value from 1 to 255. If a SCHID is not entered, the default is 255. See also the QUEUE option. Definitions with schedule IDs greater than 255 are deleted.

UID=nnn

Objects with a user ID number greater than 255 are changed to have the user ID specified on the UID option. Specify a value from 1 to 255. If UID is not entered, the default is 000.

QUEUE=KEEP|DELETE

The QUEUE option determines what action the reversion utility takes when an object in the active workload has a schedule ID greater than 255. By default (QUEUE=KEEP), the schedule ID of the object is changed to the SCHID option value (see SCHID). Assume that the object (job or network) is updated during reversion and later completes in the prior release of CA 7. In this case, it acts like it was brought into the queue with the updated schedule ID. Specifically, the job triggers successor jobs based on the new schedule ID. Alternately you can specify QUEUE=DELETE to remove objects from the active workload when their schedule IDs are greater than 255. These objects are not tracked, but neither do they trigger anything upon completion. Definitions with schedule IDs greater than 255 are always deleted.