Starting the IRLM

Start the IRLM from the system console of each participating system with the START irlmproc,parms z/OS® command.

irlmproc is the unique name of the IRLM procedure, and parms represents one or more IRLM control parameters that override the command defaults.

Start the IRLM subsystems before starting the batch or online IMS.

If IRLM has not completed its initialization when the IMS system tries to connect to it, IMS issues a DFS039A message that says the IRLM is not active, and asks the operator to reply to the message: retry, cancel, or dump.

  • If you have not started the IRLM, issue the z/OS START command, wait until the IRLM is active, and reply RETRY. IMS then tries to connect to the IRLM.
  • If you have a problem coordinating startup, not merely starting the IRLM, reply CANCEL to cause the IMS system to terminate with abend U0039 .

    Example:  Assume the following environment:

    • On processor J, an IMS system (IMSJ) uses an IRLM (JRLM).
    • On processor K, an IMS system (IMSK) uses an IRLM (KRLM).

    Next, assume the following scenario:

    1. A hardware error occurs on processor K.
    2. You try to restart IMSK on processor J to perform database backouts (but you do not change the IRLM name parameter, IRLMNM=KRLM).
    3. Message DFS039A indicates that KRLM is not active.
    Reply CANCEL in this case to immediately terminate the IMSK startup. Then, after changing IRLMNM= to JRLM, restart IMSK on processor J.
  • If you reply DUMP, IMS terminates with abend U0039 and a storage dump.

The z/OS console operator must watch for messages originating from the IRLM. These messages have the three-letter prefix DXR.