Use this procedure when DFSMSdss ends abnormally. However, if the abend is user abend "0001," skip this topic, and go directly to MSGADRnnnt.

Example: 5695DF175 RA10ABENDxxx function

Procedure: To determine the keywords for type-of-failure and function, follow these instructions:

1. Replace the xxx in the ABENDxxx keyword with the abend code from either the ending message or the abend dump.

   _______________________________________________________________

2. Find the function keyword:
   Note: When a DFSMSdss task abends, the DFSMSdss scheduler module writes message ADR013I (TASK ABENDED) to the SYSPRINT (or its equivalent) data set. If you do not receive the ADR013I message, use function keyword CNTRL and refer to Module keyword.
   1. Record the relative task identifier. The number in parentheses (ttt) that immediately follows the message identifier is the relative task identifier. For example:

      ADR013I (ttt)-mmmmm(yy), date_and_time TASK ABENDED . . .

   2. Check prior messages for an ADR101I message with a task identifier that matches the one that you found in step 2.a. For example:

      ADR101I (ttt)-mmmmm(yy), TASKID xxx HAS BEEN ASSIGNED TO COMMAND 'command'

      The command that is identified in this message is the function that is executing at the time of the abend. This command name is the function keyword.

   _______________________________________________________________

You have finished when you have identified the function keyword for the ABENDxxx type-of-failure keyword. Refer to Module keyword to identify the maintenance level of the module that failed.