User Exits › MIMINIXT Exit Routine › Coding Rules for the MIMINIXT Exit Routine

Coding Rules for the MIMINIXT Exit Routine

Follow these rules when coding the MIMINIXT routine:

• Preserve all registers except registers 0, 1, and 15.
• All CA MIM exit routines execute under GCS. Therefore, use GCS macros when coding the routines. Also, assemble the routines using the GCS macro libraries.
• Acquire storage in a key that is usable to the exit routines you plan to invoke later.

  Note: CA MIM does not provide serialization for the updating of a global data area. The serialization inherent in the execution environment of the routine is the only serialization that occurs.

• Use the INITEXIT parameter on the MIMINIT statement to identify the appropriate load module for the MIMINIXT routine. If you do not provide the module name on the INITEXIT parameter, CA MIM tries to load and activate module MIMINIXT.

  Note: Specifying MIMINIT INITEXIT=NONE causes CA MIM to bypass all MIMINIXT processing.

• To assemble an exit, use High-Level Assembler.

If you write your own MIMINIXT exit routine, assemble and link edit the completed routine with the module name you specify on the INITEXIT parameter of the MIMINIT statement. Link edit the module into a load library and add the load library to the GLOBAL LOADLIB command in the PROFILE GCS file for the MIMGR user ID.

The sample file MIMINIXT ASSEMBLE on your distribution tape contains a sample MIMINIXT exit routine. A LINKEXIT EXEC is provided on the tape to link the sample MIMINIXT routine into a load library named MIMEXITS LOADLIB.