IBM Support

OA56747: ERB3RPRJ ABEND0C4 OR LOOPING/HUNG TSO USER TRYING TO ACCESS THE RMF MON III DELAYJ REPORT

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When using RMF Monitor III DELAYJ report an abend0c4 may occur
    when viewing a job that has processor delays.  The abend is due
    to an incorrect ASIG3PTR pointer  OA54915 changed the length
    of the ASIG3 entry, but ERB3RPRJ was not included in the PTF.
    ERB3RPRJ is calculating the ASIG3PTR incorrectly based on the
    previous length of x'470' instead of the new length of x'4A0'.
    
    PE Information:
    Users Affected:
    HRM77A0 with PTF UA97694
    HRM77B0 with PTF UA97695
    
    User Impact:  APAR OA54915 is a new function APAR that
    changed the size of a control block, but not all modules picked
    up the change.  Viewing RMF Monitor III reports that include
    jobs with processor delays may incur abend0c4 or hang.
    
    ADDITIONAL SYMPTOMS: The incorrect ASIG3 pointers may show as
    high CPU or hung TSO user trying to access an RMF MON III DELAYJ
    report. SYSTRACE entries of a dump will point to ERB3RPRJ at a
    point where the ASIG3 control blocks are being accessed.
    

Local fix

  • Do not apply OA54915, or do not view Monitor III reports with
    address space processor delay information.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: RMF Users                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: RMF Monitor III fails with ABEND0C4 in  *
    *                      ERB3RPRJ or TSO session is              *
    *                      LOOPING/HUNG after invocation of        *
    *                      Monitor III DELAYJ report               *
    ****************************************************************
    * RECOMMENDATION: None please install this apar.               *
    ****************************************************************
    RMF Monitor III:
    When using RMF Monitor III DELAYJ report an abend0c4 may occur
    when viewing a job that has processor delays. Another symptom
    is a loop/hang condition of the TSO Monitor III reporter
    session after invocation of RMF Monitor III DELAYJ report.
    The problem occurs since module ERB3RPRJ uses an old version of
    the ERBASIG3 macro.
    Affected RMF releases: z/OS-2.2 and z/OS-2.3
    

Problem conclusion

  • With this APAR, module ERB3RPRJ is re-compiled with correct
    version of ERBASIG3 macro
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA56747

  • Reported component name

    RMF

  • Reported component ID

    566527404

  • Reported release

    7B0

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-01-08

  • Closed date

    2019-01-28

  • Last modified date

    2019-02-02

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

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

    UA98433 UA98434

Modules/Macros

  • ERB3RPRJ
    

Fix information

  • Fixed component name

    RMF

  • Fixed component ID

    566527404

Applicable component levels

  • R7A0 PSY UA98433

       UP19/01/30 P F901 {

  • R7B0 PSY UA98434

       UP19/01/30 P F901 {

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":"7B0","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":"7B0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 February 2019