Messages issued by other subcomponents

  1. Record on the Keyword worksheet the message that interrupted the ISMF operation screen. For an example, see Figure 1.
  2. Press the ENTER key to get the ISMF short error message. For an example, see Figure 2.
  3. Enter HELP to get the ISMF long error message. For an example, see Figure 1.
  4. Enter HELP again to get the help panel that defines the problem further. For an example, see Figure 2.

    Read the help panel to determine if you can do something to resolve the problem. If the explanation provided does not indicatehow to correct the error, continue with this procedure.

  5. Examine the ISPF log for the message identifier. (See ISMF's use of the ISPF log for an example of the ISPF log.) The message identifier appears with the original error message. A list of possible three-letter prefixes for messages issued by some other product appears in Table 1.
  6. If the message starts with any of these prefixes, use the information indicated in Table 1 to determine the recommended action. For messages that start with other prefixes, see z/OS MVS System Messages, Vol 1 (ABA-AOM), through z/OS MVS System Messages, Vol 10 (IXC-IZP), to determine the recommended action.
    Table 1. ISMF—Message Prefixes for Other Products
    Prefix Subcomponent Name Information
    ADR DFSMSdss z/OS MVS System Messages, Vol 1 (ABA-AOM)
    ARC DFSMShsm z/OS MVS System Messages, Vol 2 (ARC-ASA)
    DFQ or DGT ISMF (User response options are given on message panel.)
    ICK ICKDSF Device Support Facilities (ICKDSF) User's Guide and Reference
    IKJ TSO/E z/OS MVS System Messages, Vol 9 (IGF-IWM)
    ISP or ISR ISPF z/OS V2R2 ISPF Messages and Codes
  7. If the message has no message identifier, issue the TSO PROFILE command specifying the keyword 'MSGID' and retry the failing function.
  8. See ISMF—module keyword.
Parent topic: ISMF—message keyword