MSGADRnnnt

Use this procedure for any of the following conditions:

A DFSMSdss message indicates that an internal program error has occurred (for example, message ADR799E, "AN UNEXPECTED ERROR HAS OCCURRED").
A message is not issued when it should have been.
A message is issued when it should not have been.

Example: 5695DF175 RA10 MSGADR nnnt ADR mmmmm OC yy

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

Replace the nnnt in MSGADRnnnt with the message number and severity code. For example, if the message is ADR503A, the MSGADRnnnt type-of-failure keyword is MSGADR503A.
_______________________________________________________________
Replace the mmmmm in ADRmmmmm with the module identifier from the message (mmmmm in the following example).
```
ADR013I (ttt)-mmmmm(yy), date_and_time TASK ABENDED . . .
```
The number in the parentheses (ttt) immediately following the message identifier is the relative task identifier. The resulting module keyword is ADRmmmmm.
Note: For the DFSMSdss stand-alone restore program, the module keyword is always ADRDMPRS. If you select this keyword, see Maintenance-level keyword.

_______________________________________________________________
Replace the yy in OCyy with the two-character occurrence code, which is in parentheses following the module identifier in the message. For example, you could have OC01.
_______________________________________________________________

You have finished when you have identified the MSGADRnnnt type-of-failure keyword, the module keyword, and the occurrence code for the MSGADRnnnt type-of-failure. To identify the maintenance level of the module, refer to Maintenance-level keyword.