Reversion › Prepare for Reversion › Stop Database Tasks

Stop Database Tasks

Quiesce processing and let as many jobs as possible complete successfully so that the queues are as empty as possible.

Stop all tasks accessing the logical database of the CA 7 instance you are reverting:

• Shut down CA7ONL and all the CA 7 ICOM (CA7ICOM) tasks.
• If using CA 7 Jobflow Monitor (JFM), stop that task too.
• Cancel or let complete any batch jobs, including Database Transportability jobs, that are referencing the logical database of the CA 7 instance you are reverting.

Note: Leave the CA Datacom/AD MUF up and active because it must be active to extract the data that is needed for reversion.

Identify Elements with Expanded IDs

CAL2JCL Member: AL2DCR10

Description: Queries the CA WA CA 7 Edition Version 12.0 database for elements that contain expanded IDs.

CA WA CA 7 Edition Version 12.0 lets the SCHID, UID, and JCLID fields contain values greater than 255. Because CA 7 r11.3 does not permit values greater than 255, elements with higher values require special handling during a reversion.

During a reversion, elements containing expanded IDs are assigned an alternate value or not included in the reverted file. Identifying these elements before reversion lets you have more control over what action a reversion takes.

For more information, see the Expanded ID Usage Report.

Note: The Agent VSAM file contains UID information but does not undergo conversion or reversion. If you used expanded UIDs in Version 12.0, the AGFILE command uses a UID of zero for security checks after reversion.