Advanced Topics › How You Use the Dynamic Compatibility Feature with Checkpoint Files

How You Use the Dynamic Compatibility Feature with Checkpoint Files

When using the dynamic compatibility level feature with checkpoint files, format the local checkpoint file to start CA MIM if either of the following conditions is true:

• The system on which you start CA MIM was never included in the activate process.

  For example, you are running CA MIM r11.9 on three systems (SYSA, SYSB, and SYSC). The current COMPATLEVEL specification is 11.9. On SYSC, CA MIM is not active and is therefore currently freed.

  Shut down CA MIM r11.9 one system at a time and bring up CA MIM r12.0 with COMPATLEVEL=11.9 (SYSA and SYSB). You do not start CA MIM on SYSC (which is in a freed state). You then issue the command:

  ACTIVATE COMPATLEVEL=(12.0,FORCE) 
  

  The FORCE option tells CA MIM to ignore the freed systems (SYSC in this case). Now you have SYSA and SYSB running at the CA MIM r12.0 level. After issuing the ACTIVATE command update the MIMPARMS data set with MIMINIT COMPATLEVEL=12.0. If you decide to bring CA MIM r12.0 up on SYSC, format the local checkpoint file using FORMAT=CHKPT on the startup command.

• You have issued a successful ACTIVATE COMPATLEVEL command and decide to revert to the previous release using a control file format.

  For example, you are running CA MIM r12.0 on three systems using COMPATLEVEL 12.0. You decide to revert to release 11.9 by a global shutdown and a control file format.

  In this case, the proper procedure is to update the MIMPARMS data set with COMPATLEVEL=11.9. Shut down the systems globally, and start with a FORMAT=BOTH on the first system, and FORMAT=CHKPT on all subsequent systems.