Last update: 12/Nov/2024
NOTES:
The CMODE (Compatibility MODE) is used to prevent the use of a new feature when working with a lower level component of the solution.
Using new features may allow the use of new values of parameters, new length of areas that might not be supported by lower level component. This is why you must NOT fallback a CMODE to lower level as some entities, like for exemple schedule definitions, might contains new values or fields that will cause failure in lower maintenance level. A CMODE can be upgraded but should never be downgraded!
The UPGRADE IN PLACE process does NOT upgrade the CMODE to allow the fallback in case of problem.
It is the administrator decision/role to upgrade the CMODE when the upgrade has been validated.
Main lines:
- Notify the CONTROL-M/Enterprise Manager administrator that the CONTROL-M for z/OS compatibility level will be upgraded and plan the upgrade date/time together.
- On the D day, confirm the date time to the EM administrator that must be available for the operation.
- Shutdown all the monitors for this INCONTROL environment, included all the IOAGATE.
- Check with the EM administrator that he could upgrade the Gateway level for this CONTROL-M at the selected level.
- Change the CMODE value on the z/OS side using IOAICE
- Restart all the monitors
- Check the IOA ONLINF INFO screenshot the Running Mode should be the expected one.
- Check that the communication with the EM is normal.
Detailed process:
1) The current Compatibility Mode and the current maintenance level are visible in the IOA ONLINE environment.
Enter the command INFO in any "COMMAND ===>" field.
- The first line display the current maintenance level, sample:
IOA Version 9.0.21.300 Information and Status
- The column Running Mode display the Compatibility Mode per component.
The running mode does NOT include the maintenance level.
Sample :
Running Mode
IOA 9.0.21
CDAM 9.0.21
CONTROL-M 9.0.21
CONTROL-M/Restart 9.0.21
CONTROL-M/JCL Verify 9.0.21
CONTROL-M/Analyzer 9.0.21
CONTROL-M/Tape 9.0.21
CONTROL-D 9.0.21
CONTROL-V 9.0.21
CONTROL-O 9.0.21
2) The Compatibility Mode is defined in IOA PARM(IOAPARM) section CMODE.
It must be updated using IOAICE to store the new values in ICE Table.
The parameters are MODExxx:
MODEIOA, MODECDAM, MODECTM, MODECTB, MODECTR, MODECTJ, MODECTT,
MODECTD, MODECTV, MODECTO, MODEASM, MODEASD, MODEASO
3) The technically supported CMODE are described in the manual:
INCONTROL for z/OS Installation Guide: Installing > Part 1: Installation and Customization Engine (ICE)
Part 3: Customized Installation
Installing IOA
IOA Installation Step Checklist
Step 4 – Specify IOA Parameters
Step 4.3 – IOA Compatibility Mode
IOA ONLINE documentation link:
https://documents.bmc.com/supportu/INC/9.0.21/en-US/INCONTROL/Installing/Part_3_Customized_installation.htm#Step4
search string 4.3
Extract:
Step 4.3 – IOA compatibility mode
This step defines the compatibility mode for each product.
Valid values are:
- 630 – IOA version 6.3.xx mode.
- 700 – IOA version 7.0.xx mode.
- 800 – IOA version 8.0.xx mode.
- 900 – IOA version 9.0.xx mode.
- 918 – IOA version 9.0.18.xxx mode.
- 919 – IOA version 9.0.19.xxx mode.
- 920 – IOA version 9.0.20.xxx mode.
- 921 – IOA version 9.0.21.xxx mode. Default.
NOTE: we only fully support this mechanism for currently supported version.
In the case of a problem with a MODECTx with a value corresponding to an unsupported version, if there is no known solution for it, we are not going to debug the problem, we will ask you to upgrade the unsupported component to a supported one as a solution.
4) The compatibility MODE should be modified using the IOAICE tool.
EX &BASEPREF.INSTALL(IOAICE)
All the monitors should be down before the validation of the new MODExxx values, including IOAGATEs.
CMODE update Process:
- IOAICE > Customization > select environment > Product: IOA / Product Customization > 1) IOAPARM Post-Installation > 2) Set compatibility mode
- Change the compatibility MODE as desired.
The new MODExxx MUST be higher to the current one without exceeding the current IOA version.
- > 4) Parameter Verification
- > 5) Save Parameters into Installation Libs.
This last step will regenerate the PARM(IOAPARM) member from the skeleton and values stored in IOAICE.
NOTE: if Control-M/Enterprise Manager is used:
- The CMODE value on INCONTROL z/OS side
and
- the Gateway level on the CONTROL-M/Enterprise Manager
must be the same to allow the communication.
It is important that the INCONTROL administrator and the CONTROL-M/Enterprise Manager administrator synchronize their action when upgrading a Gateway level (CMODE).
5) To configure Control-M/Enterprise Manager for the upgraded Control-M for z/OS
1. From the z/OS machine, shut down the IOAGATEs.
2. From the Control-M Configuration Manager, shut down the Gateway for this Control-M.
3. From the z/OS machine, set the CMODE to the new upgrade level in the MODEASM and MODECTM
parameters.
4. From the Control-M Configuration Manager, promote the Control-M Server to the new upgrade level using the Promote Control-M option.
Note : The CMODE upgrade method may change depending on CONTROL-M/EM version
NOTES:
From the Control-M Configuration Manager:
1. If the correct level is already set, the Elevate Control-M option is grayed-out & the change will be made automatically.
2. If you are using version 9.0.20 or above of the Control-M Configuration Manager then the promote option is no longer relevant & the following applies:
2.1. If the Control-M is "managed" and the mainframe is running both CTMAS and CTMCAS, then the change of versions on the mainframe side will be picked up automatically when the gateway is started from the Configuration Manager. No Elevate is required.
2.2. If the Control-M is "managed" and the mainframe is NOT running CTMCAS, then do the following:
- No Elevate is required. The option to set a new version will not be available.
- Set the Control-M to "un-managed"
- From the properties option of the Control-M Server Definition manually update the Version Field to match the new version of Control-M for z/OS (CMODE changed above).
2.3. If the Control-M is "un-managed" then do the following:
- No Elevate is required. The option to set a new version will not be available.
- From the properties option of the Control-M Server Definition manually update the Version Field to match the new version of Control-M for z/OS (CMODE changed above).
3. From the z/OS machine, start IOAGATE.
4. From the Control-M Configuration Manager, start the Gateway for this Control-M.
***