Step F6: Control-M fallback

In general, it is not necessary to restore Control-M databases because of Control-M Minus-One Support (for details, see Chapter 1 in the Control-M for z/OS User Guide). However, certain exceptions and cautions must be observed as detailed below:

• Before performing fallback, do the following:

  —check that all components of the new environment are down

  —perform a full backup of all the Control-M files, including the journal file

• If the following message is issued by the monitor, reply with the I option:

  *CTML11W AJF/CONDITION JOURNALING DISABLED

  *xx CTML12W REPLY 'C' CONTINUE WITHOUT JOURNALING, 'I' INITIALIZE, OR 'E' END

• If you have modified global control parameters in IOAPARM or CTMPARM members (in the IOA.PARM library), changes would be required when falling back from the current release to a previous version. For example, enlarging the AJF in the current release file and reverting back to a previous version, would result in a mismatch of the AJF size between the CTMPARM AJF size value of the earlier version and the actual physical file size of the AJF.

  Similarly, installing the current release with a different QNAME, and then falling back to a previous version would create a mismatch in the QNAME IOAPARM of the earlier version and the QNAME imbedded in various product components.

1. Restore the CMEM environment
   1. Restore the copy of the CMEM rules table.
   2. Reformat the previous set of CMEM communications files.
2. Adjust Date Control records

   Copy all date records (meaning, all members that start with the DATEREC prefix) from the Control‑M PARM library in the current release to the Control‑M PARM library in the previous version.