Advanced Topics › Product Activation Considerations › Defining CA MIM in the Subsystem Name Table

Defining CA MIM in the Subsystem Name Table

This section explains how the CA MIM subsystem name value should be defined in the IEFSSNxx member of SYS1.PARMLIB and on the MIMINIT SUBNAME parameter of the MIMINIT member of the CA MIM parmlib.

This information is of value in environments where the order in which subsystem interface events are processed is important, specifically with tape allocations. For example, in an environment in which CA MIA coexists with the robotic tape drive software of other vendors, you would want CA MIA to process tape allocation requests after the products of other vendors do.

If you are concerned about the order in which subsystem interface events are processed, then you should define a subsystem name for CA MIM in the IEFSSNxx member of the SYS1.PARMLIB data set. Using the keyword format, place the CA MIM subsystem name definition in the appropriate order relative to other subsystem definitions. Proper placement of the CA MIM definition ensures that subsystem interface events are processed in the proper order by each subsystem.

The CA MIM subsystem naming convention for the IEFSSNxx member of SYS1.PARMLIB requires the first three characters to be “MIM” and the fourth character be alphanumeric or special. The fourth character cannot be *, D, or ?.

The following is an example of a valid IEFSSNxx definition for CA MIM:

SUBSYS SUBNAME(MIMA)     /* CA-Multi-image Allocation  */

After you update the IEFSSNxx member of SYS1.PARMLIB, you must then update the MIMINIT SUBNAME= parameter in the MIMINIT member of the CA MIM parmlib like this:

MIMINIT SUBNAME=MIMA

When the CA MIM address space is started, it processes this statement, then searchs for and locates the matching subsystem definition, MIMA, that was established when the IEFSSNxx definitions were processed.

Note: If you do not define the subsystem name properly in both parmlibs, matching definitions will not be found, and subsystem events will not be processed based on your IEFSSNxx definitions.

If you do not have concerns about the order in which subsystem interface events are processed, you do not need to provide definitions for CA MIM in the IEFSSNxx member of SYS1.PARMLIB. Regardless of whether you place a CA MIM definition in IEFSSNxx, CA MIM will still dynamically create a subsystem definition for itself during product initialization. When CA MIM is started after an IPL, the MIMINIT SUBNAME parameter are processed and an attempt is made to locate a like-named subsystem. If you do not have a CA MIM definition in IEFSSNxx, then no matching name will be found, and CA MIM will dynamically define a subsystem using the name provided on the MIMINIT SUBNAME parameter.

When a CA MIM subsystem value has not been predefined in IEFSSNxx, the first three characters of the MIMINIT SUBNAME value must be “MIM” and the fourth character can be alphanumeric or special character, except for *, ?, or D.

The following is an example of this naming convention:

MIMINIT SUBNAME=MIM&

Note: You can use most EBCDIC characters when calling the IBM subsystem services to define a subsystem. However, you can use only alphanumeric and national characters when defining subsystems in the IEFSSNxx member of SYS1.PARMLIB.

If you do not provide a subsystem name value on the MIMINIT SUBNAME parameter, CA MIM uses a default name when dynamically creating a subsystem definition during product startup.

Note: For more information, see the Statement and Command Reference Guide and the IBM guides Initialization and Tuning Reference and Using the Subsystem Interface.