IBM Support

II07428: REFERENCE APAR CONTAINING STANDARDIZED KEYWORD SYMPTOMS AND GUIDELINES USED WHEN OPENING OR FREE FORM SEARCHING APARS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as canceled.

Error description

  • -----------------------------------------------------------
    INTENT OF THIS APAR
    -----------------------------------------------------------
    The intent of this informational APAR is to document the
    accepted standards for common symptom keywords and some
    related guidelines.  When opening APARs or using free form
    searching for known problems these standards and guidelines
    should be followed.
    -----------------------------------------------------------
              CONSIDERATIONS REGARDING THIS APAR
    -----------------------------------------------------------
    1) Please note that the existence of this informational APAR
    does not guarantee that every APAR follows the standards
    documented below.  If you discover an APAR that does not
    follow the standards, please contact the support center to
    have the APAR corrected (or correct the APAR yourself when
    possible).
    2) This informational APAR may be added to or changed in the
    future.  If you have a suggestion for an addition or an
    improvement, please contact the support center to relay the
    suggestion to the informational APAR owner (or notify the
    owner directly when possible; L1/L2: the owner's node/userid can
    be found on the scratch pad).
    3) The initial scope of this APAR is limited to the
    following component areas (although some of the more general
    standards should be in wide spread use across the platform):
    BCP, LE, JES2, JES3, RACF, SMPE, TSO, and USS
    ------------------------------------------------------------
                 STANDARDIZED KEYWORD LIST   ( STANDARD )
    ------------------------------------------------------------
    ABENDxxx     Any system abend except JES3; where xxx is the
                 hexadecimal value of the abend code, always 3
                 digits including leading zeroes
    ABENDDMxxx   JES3 abend; where xxx is the hexadecimal value
                 of the abend code, always 3 digits including
                 leading zeroes
    ABENDUxxxx   User abend; where xxxx is the user abend code
    AMODE31      Program running in AMODE 31 (31-bit mode)
    AMODE64      Program running in AMODE 64 (64-bit mode)
    ARnn         Access register; where nn is the decimal
                 register number w/out leading zeroes
    CRnn         Control register; where nn is the decimal
                 register number w/out leading zeroes
    D/Txxxx      Device type; where xxxx is the device number
    DATASET      Data set
    DEQ          Dequeue
    DESCCODEnn   WTO descriptor code; where nn is the decimal
                 value of the code, 1-12, without leading zeroes
    ENQ          Enqueue
    ERRNO2n...n  Where n...n is the 4 byte hexadecimal value of
                 the errno2
    ERRNOJRn...n Where n...n is the 4 byte hexadecimal value of
                 the errnojr
    ERRNOnnn     Where nnn is the errno in decimal
    HANG         Always include this form of the word
    I/O          Input Output
    KEYn         PSW Key or Storage Key (in hex)
    KEYnn        PSW Key or Storage Key (in dec)
    LATCH#nn     Where nnn is decimal latch number w/out leading
                 zeros (i.e. LATCH#2)
    LOOP         Always include this form of the word
    LPAR         Logical Partition (PR/SM)
    LU62         Logical Unit 6.2 protocol
    MIH          Missing interrupt handler
    MSGxxxx      Any message except JES2 messages; where xxxx is
                 the complete message id of any length
    MSGHASPxxxx  JES2 messages; note that the '$' prefix has
                 been removed and xxxx is the message id of any
                 length
    OVERLAY      Storage overlay; always include this form of
                 the word
    PAGEFIX      Page-Fix
    PICxx        Program Interrupt Code associated with
                 ABEND0Cx; where xx is the interrupt code,
                 always 2 digits with leading zeroes
    Rxxx         Release level; where xxx is the product release
                 level
    RCnn         Return code; where nn is decimal or hexadecimal
                 and at least two digits
    REGnn        General purpose register; where nn is the
                 decimal register number w/out leading zeroes
    ROUTCODEnnn  WTO route code; where nnn is the decimal value
                 of the code, 1-128, without leading zeroes
    RSNxxx       Reason code; where xxx is the hexadecimal
                 reason code of any length
    SADMP        Stand-alone dump
    SIGxxxx      Where xxx is the name of the signal
                 (i.e. SIGTERM)
    SIO          Start Input Output
    SMFTYPEnnn   SMF type records; where nnn is the decimal
                 value of the record, 0-255, w/out leading
                 zeroes
    SUBTYPEnnn   SMF subtype records; where nnn is the decimal
                 value of subtype, 0-255, w/out leading zeroes.
                 Also make sure the SMFTYPEnnn is included
    SPnnn        Subpool number; where nnn is the decimal value
                 of subpool, 0-255, with no leading zeroes
    SVCnnn       Supervisor Call; where nnn is the decimal value
                 of the SVC, 0-255, with no leading zeroes
    VOLSER       Volume serial
    WAIT         Always use this form of the word
    WAITxxx      System wait condition; where xxx is the hex
                 value of the wait code, always 3 digits
                 including leading zeroes
    Z/ARCHITECTURE   64-bit mode
    -----------------------------------------------------------
                OTHER SUGGESTED GUIDELINES
    -----------------------------------------------------------
    o Always concatenate a number to a word when it modifies
      that word (eg. SVC13, ABEND0C4)
    o Include related component id's in Informational APAR's
    o Use the word "missing" whenever messages do not appear as
      expected
    o Never abbreviate system commands
    o Refer to a product by its FMID, not release (eg. HBB4420)
    o '=' may be included in a search argument as long as there
      are no blanks on either side of the '=' (eg. DISP=MOD is
      a proper search argument)
    o Do not use hyphens in search arguments (eg. a publication
      number should be  specified as SC231234)
    

Local fix

  • Search on  " II99999 " to locate this APAR
    

Problem summary

Problem conclusion

Temporary fix

Comments

  •      Closing Information APAR.
         Additional symptoms:  RETAIN STANDARD SEARCH STRING TEXT
                               CRITERIA  DB2INFO
    

APAR Information

  • APAR number

    II07428

  • Reported component name

    V2 LIB INFO ITE

  • Reported component ID

    INFOV2LIB

  • Reported release

    001

  • Status

    CLOSED CAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    1993-12-14

  • Closed date

    1996-10-23

  • Last modified date

    2023-02-10

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"z\/OS Communications Server"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"001"}]

Document Information

Modified date:
10 February 2023