IBM Support

OA56640: WAIT064 RC9 IEA304W SYSTEM WAIT STATE CODE 80009064 DURING IEAVNP09 INITIALIZATION 18/12/13 PTF PECHANGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Customer experienced WAIT064 RC09 during IPL.  MSGIEA304W noted
    RIM module IEAVNP09:
    
    IEA304W SYSTEM WAIT STATE CODE 80009064 DURING IEAVNP09
    INITIALIZATION.
    
    Diagnosis showed that an ABEND0C1 had been suffered in
    IEAVNP09+59A (UA97369) due to a BASR 14,15 issued with an
    invalid target address of 0 in register 15.
    
    When IEAVNP09 suffered the ABEND0C1, it was in the process of
    issuing MSGIEA400I as a result of detecting an invalid
    specification for parameter NSYSLX in parmlib member IEASYSxx:
    
    IEA400I NSYSLX VALUE, x, NOT VALID. DEFAULT OF (165,165) USED.
    
    The WAIT064 can be avoided by correcting the NSYSLX to have a
    valid specification per the documentation in the z/OS
    Initialization and Tuning Reference.
    
    
    VERIFICATION STEPS:
    
    1) You see message:
    
       IEA304W SYSTEM WAIT STATE CODE 80009064 DURING IEAVNP09
       INITIALIZATION.
    
    2) You determine an invalid specification for NSYSLX in an
       IEASYSxx parmlib member.  Per the z/OS Initialization and
       Tuning Reference:
    
         NSYSLX={nn | (nn,mm)}  where Value Range: 10-512 for nn,
                                                   40-8192 for mm
    PE information:
    
    Users Affected:  Customers running with the following
    environment:
    - HBB7790 PTF for OA55240 (UA96468)
    - HBB77A0 PTF for OA54807 (UA96477)
    - HBB77B0 PTF for OA55233 (UA96475)
    - AND specifying an invalid NSYSLX value in IEASYSxx
    
    User Impact:  Wait State WS064 WAIT064 RC09 during IPL
    in RIM IEAVNP09.
    
    This ONLY occurs when the NSYSLX value in IEASYSxx
    is invalid.  There is no problem if the NSYSLX value
    is valid or if one does not specify NSYSLX in IEASYSxx.
    
    User resolution:  Apply OA56640's PTFs as they are already
    available.
    

Local fix

  • Correct specification for NSYSLX in parmlib member IEASYSxx.
    
    Per the z/OS Initialization and Tuning Reference:
    
    NSYSLX={nn | (nn,mm)}  where Value Range: 10-512 for nn,
                                              40-8192 for mm
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    *  Users running z/OS HBB7790 and above,                       *
    *                                                              *
    *                 AND with the following PTFs installed:       *
    *                 - UA96468 (OA55240) for HBB7790              *
    *                 - UA96477 (OA54807) for HBB77A0              *
    *                 - UA96475 (OA55233) for HBB77B0              *
    *                                                              *
    *                 AND specifying an invalid NSYSLX value       *
    *                 in IEASYSxx.                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    *  WAIT064 RC09 during IPL in RIM                              *
    *                      IEAVNP09.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    For an invalid NSYSLX value in IEASYSxx, IEAVNP09 was unable
    to issue syntax error message MSGIEA400I due to a message
    control block that was not initialized.
    

Problem conclusion

  • Corrected IEAVNP09 to initialize the message control block
    so that it can issue IEA400I for an invalid NSYSLX value
    in IEASYSxx.
    

Temporary fix

Comments

  • **** 790, 7A0 and 7B0 PTFs in ERROR.  See OA56775 for PE
         description.
    

APAR Information

  • APAR number

    OA56640

  • Reported component name

    SUPERVISOR CONT

  • Reported component ID

    5752SC1C5

  • Reported release

    7A0

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-12-11

  • Closed date

    2018-12-12

  • Last modified date

    2019-03-13

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

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

    UA98124 UA98125 UA98130

Modules/Macros

  • IEAVNP09
    

Fix information

  • Fixed component name

    SUPERVISOR CONT

  • Fixed component ID

    5752SC1C5

Applicable component levels

  • R790 PSY UA98130

       UP18/12/13 P F812 {

  • R7A0 PSY UA98125

       UP18/12/13 P F812 {

  • R7B0 PSY UA98124

       UP18/12/13 P F812 {

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7A0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7A0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
13 March 2019