Advanced Topics › How You Define CA MIA in the Subsystem Name Table

How You Define CA MIA in the Subsystem Name Table

The order in which tape subsystems process subsystem interface (SSI) events is important, especially in tape allocation environments where multiple tape subsystems, such as CA MIA and Sun STK's SMC and HSC, need to process the same tape device oriented events.

In an environment in which CA MIA is to coexist with the robotic tape drive software of other vendors, CA MIA should process tape-related SSI events last. Processing each event last allows CA MIA to detect and react appropriately to actions taken by other tape subsystems that have also processed the event.

Proper placement of the CA MIA definition in the IEFSSNxx member of SYS1.PARMLIB ensures that SSI tape device-oriented events are processed in the proper order by each subsystem.

To establish the order in which tape device-oriented events are processed

1. In the MIMINIT member of the MIMPARMS data set, specify MIMINIT SUBNAME=MIMA for your CA MIA started task.
2. In SYS1.PARMLIB(IEFSSNxx), using subsystem name format, CA and Sun STK recommend that you define your tape management subsystems in the following order:
   1. TMS (CA 1)
   2. SMC0 (Sun STK-SMC)
   3. SLS0 (Sun STK-HSC)
   4. MIMA (CA MIA)
3. Within SMC, make sure that MIACOMPAT(ON) is specified. Issue the following command on each system to verify that the correct value is in place:

   F SMC,ALLOCDEF LIST
   

4. Restart CA MIA, Sun STK-SMC, and Sun STK-HSC.
5. Issue the following z/OS command on every MIAplex system to verify that your tape management subsystems are defined in the proper order:

   DISPLAY SSI
   

Note: For more information, see the chapter “Advance Topics” in the CA MIM Programming Guide.