DFS039A imsid ACTIVE, REPLY RETRY, CANCEL, OR DUMP.
or
Explanation
Message DFS039I is followed by this message.
Message DFS039I is first issued when an IDENTIFY request to the IRLM fails. Return code xx and reason code yy indicate an error condition. Return code 00 or 04 are returned if IRLM is holding subsystem information for a DL/I batch job. Use the F IRLMPROC,STATUS command to display information. Run batch backout for the DL/I batch job that encountered RC=00 or RC=04.
To determine the cause of the failure for message DFS039I, see the IDENTIFY request explanation in the IRLM request return and reason code information. This message is followed by a second DFS039I or a DFS039A message.
The second version of DFS039I might be issued if IMS and IRLM are enabled for the z/OS® automatic restart manager. The message indicates IMS restart is WAITING for IRLM to send READY to the automatic restart manager.
The DFS039A message is a WTOR. The first form of the message is issued if the xx-yy fields indicate the file IRLM named in the xxxx field is not active. The second form of the message is issued if the IMS ID that is identified to IRLM is already active.
System action
If IMS is not registered with the automatic restart manager and the xx-yy fields indicate that IRLM is not active or that this IMS subsystem is already identified to IRLM, the WTOR form of the message is issued. Other error return and reason codes causes IMS to abend with 0039.
If IMS is in the process of being restarted by the automatic restart manager and the xx-yy fields indicate that IRLM is not active or that this IMS subsystem is already identified to IRLM, IMS determines if IRLM was registered to the automatic restart manager in the previous IMS run. In the case when IRLM was previously registered with the automatic restart manager, IMS issues the second form of the DFS039I and WAIT until the automatic restart manager is aware that IRLM is ready for work. Other error return and reason codes cause IMS to end abnormally with abend 0039.
Operator response
Operator action is required for the WTOR form of the message.
If the IRLM named in the xxxx field is not active, ensure the xxxx name is correct. If xxxx is not the correct name, the operator can reply ABEND to the WTOR and then start IMS again specifying the correct IRLMNM. If xxxx is correct, the operator can wait until the IRLM is active and then reply RETRY to the WTOR.
If the IMS subsystem is already identified to the IRLM, the operator should investigate the status of the subsystem currently identified to IRLM. There are at least two situations where a delay in identifying to IRLM might be needed. First, the submission of two or more IMS Batch jobs with accidentally the same job name could happen. Waiting for the first batch job to finish and then replying RETRY would allow the second job to then proceed. If the same job is accidentally submitted twice, the job will probably only run once and the installation might want the operator to terminate the second job by replying CANCEL.
Second, some failures for which a CICS® XRF alternate takes over can result in the identify return code indicating the subsystem is already active. IRLM corrective action to force IRLM into an in-doubt state and then a failure state can be called before replying RETRY in this case.
- RETRY
- This causes IMS to retry the IRLM IDENTIFY. If the situation has not been corrected, the DFS039I and DFS039A messages occur again.
- CANCEL
- This causes IMS subsystem initialization to terminate with abend 0039 without a memory dump. If the IRLM was not active when the OS operator modified IMS with the RECONNECT command, responding CANCEL only terminates the IRLM reconnect processing; as a result, the OS operator receives message DFS625I with a 08 code.
- DUMP
- This problem causes the IMS subsystem to abend 0039 with a memory dump.