Starting with z/OS version 1.4.2 (JBB7727), which became generally available in March 2004, IBM began shipping a series of enhancements to console services under the umbrella title of "Console Restructure" enhancements. These changes have been and will continue to be rolled out over a series of IBM releases. The overall philosophy behind the first phase of the changes is that the health of the z/OS system is more important than the need to display every message on a console.
The first phase of the Console Restructure was delivered as an optional feature in z/OS 1.4 and as a base component in z/OS 1.5. The key design point was the elimination of system outages caused by WTO buffer shortages.
The future change that will most impact Unicenter CA-MIM is the planned elimination of the use of one-byte console IDs in all z/OS system services. This change is currently targeted to be introduced in a release following z/OS 1.7. Console names or the 4-byte console ID (introduced in MVS/ESA 4.1.0) must be used instead of 1-byte console IDs. Console names are consistent and defined, but console IDs (including 4-byte console IDs) may vary from IPL to IPL. Therefore, from the Unicenter CA-MIM perspective, the solution is to always use console names in your product statements and commands.
Specific Unicenter CA-MIM recommendations for avoiding the use of one-byte console IDs are listed in the following sections.
- Always use console names instead of console IDs in your Unicenter CA-MIM statements, commands, and user exits.
- Avoid the use of Migration Consoles (Extended MCS consoles with Migration IDs).
Unicenter CA-MIM Statements and Commands
The statements and commands in the following table that are currently using 1-byte console ID's should be changed to the corresponding console name format.
|1-Byte Console ID Format||Console Name Format|
|COLLECT CONSOLE= ucmid||COLLECT CONSOLE= console_name|
|DISPLAY GCMF COLLECT CONSOLE= ucmid||DISPLAY GCMF COLLECT CONSOLE= console_name|
|DISPLAY GCMF LINK CONSOLE= ucmid||DISPLAY GCMF LINK CONSOLE= console_name|
|FREECONS CONSOLE= ucmid||FREECONS CONSOLE= console_name|
|GCMINIT SSCONID= ucmid||GCMINIT SSCONID= console_name |
|LINK CONSOLE= ucmid||LINK CONSOLE= console_name|
The GCMINIT EXTCON=(MIGID=USE) statement should be removed to allow the product to default to Extended MCS consoles for the target console pool. If you are currently specifying a PREFIX on the GCMINIT EXTCON statement, then remove the MIGID=USE portion from the GCMINIT statement.
The LINK UCMID=ucmid command is a special case for Exclusive Linkages. Currently, with Unicenter CA-MIM 4.6 and prior releases, there is no way to specify a console name for an exclusive linkage. For now, continue to use this parameter and contact Unicenter CA-MIM customer support so we can review your usage of Exclusive Linkages.
Unicenter CA-MIC Message Sharing (Unicenter CA-MIC) allows for a command to be routed cross system. As part of this process, Unicenter CA-MIC allows for the appending of MIGID=USE to indicate that an Extended MCS console is to be allocated with a migration ID as the target console on the target system. Moving forward, these cross-system commands should not be issued with this operand. Instead, they should be allowed to take the default of Extended MCS consoles without migration IDs.
Unicenter CA-MIM User Exits
If your installation is using any of the Unicenter CA-MIM exits listed in the following table, each exit must be evaluated for proper console ID use. The exits to be reviewed are:
|GCMCMDXT||This exit routine prevents certain local commands from being directed to external systems. The GCMCMDXT exit routine allows you to change the list of systems to which a command is distributed, or suppress the command entirely. You can also use this exit routine to code a list of users authorized to issue commands from MIMTSO.|
|GCMDSTXT||This exit routine lets you prevent destinations on the local system from receiving collected messages, or responses to cross-system commands based on routing data associated with the message. You also can use the GCMDSTXT exit routine to change the text of an imported message and routing data associated with that message.|
|GCMRCVXT||Unicenter CA-MIC uses the GCMRCVXT exit routine whenever a cross-system command is received on the local system. This exit routine lets you prevent certain commands from executing on the local system as a result of a cross system command issued from an external system. You cannot use the GCMRCVXT exit routine to change the text of commands or the information associated with a command. You must use the Unicenter CA-MIM MIMCMDXT exit routine to change the text of commands.|
|GCMSRCXT||This exit routine lets you prevent certain local messages from being directed to external systems, based on routing data associated with the messages. You also can use the GCMSRCXT exit routine to change the text of a message and routing data associated with a message.|
|MIMATHXT||You can use the optional MIMATHXT exit routine to augment the command authorization processing provided by Unicenter CA-MIM and the operating system security subsystem. The MIMATHXT exit is only called when the MIMINIT SAFCMDAUTH statement has activated Unicenter CA-MIM command authorization.|
|MIMCMDXT||You can use the optional MIMCMDXT exit routine to prevent certain Unicenter CA-MIM commands from being issued on the local system or across systems. You can also increase the command authority level associated with a console or TSO user ID so that operators or TSO users can issue Unicenter CA-MIM commands that they could not issue otherwise.|
To determine if you are running with Unicenter CA-MIM user exits enabled, issue the following command:
F MIM,D EXIT
The following is the output display from the command when user exits have been loaded:
MIM0264 MIM EXIT DISPLAY
EXIT MODULE ADDRESS STATUS PROT DUMP DISA
GCMCMDXT USR 00006910 ACTIVE YES YES NO
GCMCMDXT USREX 00006920 INACT YES YES NO
GCMSRCXT USREXIT 00006930 INACT NO YES NO
TPCRECXT USREXIT 00006940 ACTIVE NO NO YES
The following is the output display from the command when user exits have not been loaded:
MIM0262 NO EXITS LOADED
If you need assistance evaluating your user exits, contact customer support and open a support issue. In some future release of Unicenter CA-MIM, all of the console ID and migration console (Extended MCS consoles with Migration IDs) interfaces will be removed.