IBM Support

OA50090: ABEND0C4 WHEN CREATING AN RMF CPU DURATION REPORT 16/11/24 PTF PECHANGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • ABEND0C4 in ERBDUCPU UA80441 +616 when creating an RMF CPU
    duration report for a VM host system.
    .
    If ERBRMFPP is run using the DINTV option to create a CPU
    duration report from SMF70 records that are cut from a VMGUEST
    system at z/OS 2.2 and NOVMGUEST option is used for the MON I
    options then the ABEND0C4 will occur trying to access the
    Logical Core Data Section of the duration SMF70 record. The
    joblog for the ERBRMFPP job will contain message:
    ERB253I PPS: CPU RECORDS NO LONGER COLLECTED DUE TO S0C4 ABEND
    IN DURATION INTERVAL.
    
    PE Information:
    User's Affected:
    Users with APAR OA44101 applied (PTF UA76026 for HRM7790) using
    the RMF Postprocessor (PP) to create an RMF PP CPU activity
    duration report.
    
    User Impact:
    APAR OA44101 provided the RMF support for Simultaneous
    MultiThreading (SMT) on the IBM z13 server, but it introduced
    a new problem.
    Users of the RMF Postprocessor (PP) may receive an ABEND0C4 in
    module ERBDUCPU, if an RMF PP CPU activity duration report is
    created.
    The problem occurs when creating the PP CPU activity duration
    report from SMF 70-1 records, that are written by a
    VM guest system running with NOVMGUEST Monitor I data gathering
    option.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: RMF User's                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: RMF Postprocessor CPU Activity          *
    *                      duration report:                        *
    *                      ABEND0C4 in ERBDUCPU (UA80441) +616     *
    ****************************************************************
    * RECOMMENDATION: None please install this apar.               *
    ****************************************************************
    RMF Postprocessor (PP) CPU Activity duration report:
    ABEND0C4 in CSECT ERBDUCPU +x'616' (level UA80441) when
    creating an RMF PP CPU duration report for a z/OS system
    running as VM guest.
    .
    The problem occurs when creating a CPU activity duration report
    from SMF 70-1 records that are cut by a VM guest system
    running with NOVMGUEST Monitor I data gathering option.
    Module ERBDUCPU calculates a wrong length of the SMF 70-1
    duration record. As result of that it fails with ABEND0C4
    occurs when trying to access the Logical Core Data Section in
    the SMF 70-1 duration record.
    Affected RMF releases: z/OS-2.1 and z/OS-2.2
    

Problem conclusion

  • With this APAR, module ERBDUCPU is changed to correctly
    calculate the length of the SMF 70-1 duration record.
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA50090

  • Reported component name

    RMF

  • Reported component ID

    566527404

  • Reported release

    7A0

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-03-14

  • Closed date

    2016-06-28

  • Last modified date

    2017-03-23

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

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

    UA82058 UA82059

Modules/Macros

  • ERBDUCPU
    

Fix information

  • Fixed component name

    RMF

  • Fixed component ID

    566527404

Applicable component levels

  • R7A0 PSY UA82058

       UP16/07/01 P F606

  • R790 PSY UA82059

       UP16/07/01 P F606

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:
23 March 2017