Advanced Topics › How You Activate Features of New Releases Dynamically › How You Use the Dynamic Compatibility Feature with Checkpoint Files

How You Use the Dynamic Compatibility Feature with Checkpoint Files

If you use the dynamic compatibility level feature and have checkpoint files, note that you need to 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.7 on three systems (SYSA, SYSB, and SYSC). The current COMPATLEVEL specification is 11.7. On SYSC, CA MIM is usually not active and is therefore currently freed.

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

  ACTIVATE COMPATLEVEL=(11.8,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 r11.8 level. After issuing the activate command you will need to update the MIMPARMS data set with MIMINIT COMPATLEVEL=11.8. If you decide to bring CA MIM r11.8 up on SYSC, then you need to format the local checkpoint file using FORMAT=CHKPT on the startup command.

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

  For example, you are running CA MIM r11.8 on three systems at COMPATLEVEL 11.8. You decide to switch back to release 11.7 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.7, shutdown globally, and start with a FORMAT=BOTH on the first system, and FORMAT=CHKPT on all subsequent systems.