Messages issued by DADSM/CVAF

IEC614I—DADSM issues this message.

  1. Append the message identifier and function return code to their appropriate prefixes. Append the 4-byte diagnostic information field to the prefix RSN and record on the Keyword worksheet all failure-related function modifier keywords.
    Example: Suppose the message is the following one: 
    IEC614I RENAME FAILED - RC4, DIAGNOSTIC INFORMATION IS
(040D002D),STEP01,VOL0002,DATASET1
    Specify the keyword string as follows: 
    MSGIEC614I RENAME RC4 RSN040D002D
  2. See DADSM/CVAF—module keyword.

IEC603I—DADSM issues this message.

  1. Append the message identifier to the keyword prefix MSG and record it on the Keyword worksheet as the type-of-failure keyword. Append the cde code to the keyword prefix RC and record it on the Keyword worksheet as a modifier keyword.
    Example: If the cde field contains 04, specify the keyword string as follows: 
    MSGIEC603I RC04
  2. If a dump entitled “DADSM (OBTAIN, SCRATCH, ALLOCATE, OR EXTEND) ERROR” is taken, then DADSM caused the dump because of an unexpected Common VTOC Access Facility (CVAF) error. Continue below, using DADSM dumps for CVAF dump analysis assistance.
  3. Record either the DADSM function name from the dump title (for example, OBTAIN) or the 2-character code for the CVAF function last issued (and the 2-character subfunction code, if applicable), as indicated by the 1-byte CVFCTN field (offset X'06' in the CVPL), as a modifier keyword. The CVPL is in the DADSM work area. See Table 1 for a list of valid CVFCTN field values.
    Example: If the CVFCTN field contains X'07', record the modifier keywords as: 
    IX DEL
  4. See DADSM/CVAF—module keyword.

IEC606I—CVAF issues this message. It is related to CVAF ABEND18B.

  1. Append the message identifier to the keyword prefix MSG and record it on the Keyword worksheet as the type-of-failure keyword. Append the cde code to the keyword prefix RC and record it on the Keyword worksheet as a modifier keyword.
    Example: If the cde field contains 153, specify the keyword string as follows: 
    MSGIEC606I RC153

    Continue below, using DADSM dumps for CVAF dump analysis assistance.

  2. If the message type-of-failure keyword search (without the abend keyword) is inconclusive, perform software database searches by specifying keywords as follows:
    • Both ABEND18B and MSGIEC606I together as type-of-failure keywords
    • ABEND18B alone as the type-of-failure keyword
  3. Record the CVAF module name identified in the system dump title on the Keyword worksheet.
  4. See DADSM/CVAF—module keyword.

IEC608I or IEC609I—If DADSM issued either message and disabled the VTOC index, CVAF issues message IEC606I, error code 153, and causes a system dump.

  1. IEC608I—Use the explanation of the message's cde field and the message-to-module cross-reference table in z/OS MVS System Messages, Vol 7 (IEB-IEE), to determine the related module and function. If available, append these symptoms to their respective prefixes and record them on the Keyword worksheet. Continue below, using DADSM dumps for CVAF dump analysis assistance.
  2. IEC609I—Append the single-digit function code from the message text to the prefix IGGVRF0 to determine the related module name. Append the message identifier and the message's cde field to their respective identifiers and record these keywords and the function keyword (identified by the value in the message's fctn field) on the Keyword worksheet. Continue below, using DADSM dumps for CVAF dump analysis assistance.
    Example: Append the symptoms to their respective keyword prefixes as shown: 
    MSGIEC608I SCRATCH RC12
    MSGIEC609I IGGVRF01 ALLOCATE RC04
  3. See DADSM/CVAF—module keyword.
Parent topic: DADSM/CVAF—message keyword