PM83192: ABEND 0CC WHEN MAX RANGE FLOAT NUMBER IS USED WHEN ATTEMPTING TO CHART IN A TABLE.

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The customer received a GDDM Abend 0CC when running a QMF
    Testcase involving a max range float number when attempting to
    Chart it in a Table.
    The change team looked at the dump and found that the abend is
    caused by axis values that are the same and very small ( -7.2E75
    ). The code tries to adjust these equal values and fails with
    the exponent overflow.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: ALL USERS OF GDDM-PGF CHART FUNCTION         *
    ****************************************************************
    * PROBLEM DESCRIPTION: Abend 0CC occurs during the production  *
    *                      of a chart when using GDDM-PGF          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    During chart creation GDDM-PGF checks the values used in any
    ranges. In cases where the values supplied are the same the
    system attempts to create a range. This mechanism involves
    multiplying the supplied values. When the supplied value is
    already at the maximum allowed in a short floating point number
    an exponent overflow abend occurs.
    

Problem conclusion

  • GDDM-PGF has been amended to check range values before applying
    any adjustment. When the range values being considered are at
    the maximum allowed, for a short floating point, no adjustment
    is applied. These values will be checked later to determine if
    they exceed the maximum value permitted by GDDM-PGF in which
    case message ADM0546 will be issued.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM83192

  • Reported component name

    GDDM/MVS V3

  • Reported component ID

    566881201

  • Reported release

    201

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-02-19

  • Closed date

    2013-03-06

  • Last modified date

    2013-04-02

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

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

    UK92263

Modules/Macros

  • ADMBCRNG
    

Fix information

  • Fixed component name

    GDDM/MVS V3

  • Fixed component ID

    566881201

Applicable component levels

  • R201 PSY UK92263

       UP13/03/12 P F303

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.



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

z/OS family

Software version:

3.2

Operating system(s):

z/OS

Reference #:

PM83192

Modified date:

2013-04-02

Translate my page

Machine Translation

Content navigation