IBM Support

OA67009: WAIT064 WITH REASON CODE 009 AND MESSAGE IEA304W POINTING TO IEAVNP02 24/10/02 PTF PECHANGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • MSGIEA304W against load module IEAVNP02 was followed by
    WAIT064-009 during IPL.
    The collected stand-alone dump showed that the WAIT state was
    the result of the S0C6 ABEND, triggered by not retaining
    important values before and after the FREEMAIN processing in
    load module IOSVNPTH.
    
    ANALYSIS:
    In the stand-alone dump, the very last entries in the system
    trace may look as follows (only significant data):
    
    0001 03164780  SRB        00000000_000242E8  00000000 ...
    00   IOSVNPTH
    
    0001 03164780  SSRV    78          8103FD66  0300F502 ...
    Getmain    IRDVDSE
    
    0001 03164780  SSRV    78          8103FF1C  0000F503 ...
    Freemain     -"-
    
    0001 03164780  SSRV    78          8103FD66  0300F502 ...
    Getmain      -"-
    
    0001 03164780  SSRV    78          8103FF1C  0000F503 ...
    Freemain     -"-
    
    0001 03164780  SSRV    78          80022810  0000F503 ...
    Freemain   IOSVNPTH
    
    0001 03164780  SSRV   129          80024436  031D7F0C ...  Post
       IOSVNPTH
    0001 03164780  SSRV    78          80024928  0000F503 ...
    Freemain   IOSVNPTH
    
    0001 03164780 *PGM    006 00000000_0000F507  00040006 ...
    00000000   Abend 0C6
    
    Obviously, the value of X'0000F507' as the assumed address of
    the ABEND was the result of using the preceding value of
    X'0000F503' (Freemain with BRANCH=GLOBAL in Subpool 245 or
    X'F5') in the FREEMAIN entries as the address for the failed
    branch instruction.
    .
    ANALYSIS part II:
    The device number that was non-responsive to z/OS can be
    determined from the stand-alone dump.
    Obtain a stand-alone dump of the system.
    analyze the SYSTEM TRACE.
    search for a "Time-gap" message.
    shortly after the time gap message,
    Search for a XSCH record
    followed by a CSCH record.
    the device number undergoing the Cancel / Clear is the not
    responsive device.
    In this example device 0123 is the not responsive device.
    .
    ******** Time-gap over 0000000E secs. Previous timestamp=
    02:13:42.33832691, Current timestamp= 02:13:56.92544333.
    0001 00FD66F8 SVC 10 00000000_0001E252 00000018 00000028
    0001FD6C Purge 02:13:56.925443330
    07040000 80000000
    0001 00FD66F8 .
    0001 00FD66F8 .
    0001 00FD66F8 .
    0001 00FD66F8 XSCH 00123 <------ Device # 00123
    0001 00000000 CSCH 00123 <------ Device # 00123
    .
    VERIFICATION STEPS:
    
    See the Analysis section of the APAR.
    

Local fix

  • BYPASS/CIRCUMVENTION:
    None.
    In the case of a temporary device issue,
    a re-IPL might be successful,
    however a re-IPL is not likely to be productive.
    Obtain a stand-alone dump of the system for analysis.
    This APAR is HIPER.
    The appropriate PTF should be applied immediately
    
    
    RECOVERY ACTION:
    Apply the appropriate PTF
    Re-IPL the system
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users at HBB77C0 and above who have OA64741                  *
    * installed.                                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Customers with OA64714 installed may                         *
    * encounter message IEA304W indicating                         *
    * a WAITSTATE 064 with REASON CODE 009.                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Customers with OA64714 installed may encounter a WAITSTATE 064
    with REASON CODE 009. The WAITSTATE is the result of not
    saving the contents of a register prior to issuing a FREEMAIN
    and restoring the contents of the register after the FREEMAIN
    is issued.
    

Problem conclusion

  • The register in question is saved prior to issuing the FREEMAIN
    and then restored after the FREEMAIN has completed.
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    OA67009

  • Reported component name

    IOS

  • Reported component ID

    5752SC1C3

  • Reported release

    7E0

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-09-23

  • Closed date

    2024-10-04

  • Last modified date

    2025-06-11

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

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

    UJ96054 UJ96056 UJ96057

Modules/Macros

  • IOSVNPTH
    

Fix information

  • Fixed component name

    IOS

  • Fixed component ID

    5752SC1C3

Applicable component levels

  • R7D0 PSY UJ96057

       UP24/10/16 P F410 ­

  • R7E0 PSY UJ96054

       UP24/10/16 P F410 ­

  • R7C0 PSY UJ96056

       UP24/10/16 P F410 ­

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":"BU011","label":"Systems - zSystems software"},"Product":{"code":"SG19O","label":"IOS"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"7E0"}]

Document Information

Modified date:
11 June 2025