Advanced Topics › Product Activation Considerations › How You Override Initialization Values at Startup Time › The SYSID Override Parameter

The SYSID Override Parameter

Each z/OS or z/VM image in your CA MIM complex has a name, an index, and an alias, all of which are used in CA MIM displays and for other CA MIM purposes. The MIMINIT statement defines the name, index, and alias. The statement must name all systems in the complex, because the order of the names in the statement determines the index value.

The MIMINIT statement typically uses the SMF ID (in z/OS systems) or the SYSID (in z/VM systems) to determine which system name, index, and alias it should assign. For example, the statement:

MIMINIT DEFSYS (FIRST,FF,SY22) (SECOND,SS,SY23)

assigns name=FIRST, alias=FF and index=1 to the system having SMF ID SY22, and SECOND, SS and index=2 to the system having SMF ID SY23.

The CA MIM system name is usually made equal to the SMF ID. The following statement makes the CA MIM ID and the SMF ID the same for SY22 and SY23:

MIMINIT DEFSYS (SY22,FF,SY22) (SY23,SS,SY23)

This is a convenient and recommended convention.

It is possible to override the SMF ID, for DEFSYS and IFSYS purposes, by using the MIMINIT SYSID statement. If used, the MIMINIT SYSID statement must be positioned before the MIMINIT DEFSYS statement in the INIT member. We recommend you use SYSID only for testing purposes. If you choose to use SYSID, then make sure you do not accidentally define the same system twice, either by sharing the INIT member, or copying the INIT member to other systems.

Having two or more systems in your CA MIM complex specify the same SYSID causes control file errors, and CA MIM will abend. Consider temporarily using a SYSID statement in the following circumstances:

• You need to override the system name for a single execution of CA MIM
• You did not specify a DEFSYS statement, and you want to define a system name that is different from the SMF ID of the system
• The SMF ID of the system is incorrect due to an error during the IPL procedure

Note: For more information about using the SYSID parameter on the MIMINIT statement, see the discussion of the MIMINIT Statement in the Statement and Command Reference Guide

Suppose you are running CA MIM on two systems and instead of using the SMF ID of the system, you want to use the system name SYSA for the local system. To do this, specify SYSID=SYSA on the PARM parameter of the startup procedure for the local system. Or, issue the following z/OS START command from the local system (if the name of the started task is MIMGR):

S MIMGR,SYSID=SYSA

Note: When you override the name of a system, you should check all CA MIM parmlib members for statements or commands that reference system names. Here are some examples:

IFSYS
CTCPATH
GLOBALVALUE
LINK
COLLECT

If the CTCPATH and GLOBALVALUE statements are incorrect, then they can prevent CA MIM from initializing at startup. If the system names are not correct, then you can issue the LINK and COLLECT commands to create new dynamic linkages and collection sets.