IBM Support

PN71570: EXEC - OS/VS COBOL PROGRAMS WITH "READY TRACE" RUNNING UNDER LE/370 CAN FAIL DURING ABNORMAL TERMINATIO 95/06/16 PTF PECHANGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • OS/VS COBOL program has "READY TRACE", which causes the debug
    options to be set for the program.  With normal runs (using
    LE/370) there is no problem; but if an abnormal termination
    occurs, the original ABEND can be followed by ABENDU4083 (with
    reason code 1 - RC01) due to an ABEND0C1 from routine ILBODBG.
     -
    The ABEND0C1 occurs in module ILBODBG during the handling of a
    previous severe condition by the LE/370 Condition Management
    routines.  The application contains OS/VS COBOL programs that
    use READY TRACE and do not use other debug options.
     -
    The dump shows two Condition Information Blocks (CIBs) for
    LE/370: The first is for the original problem, and the second
    is for the ABEND0C1 (message CEE3201S).  The ABEND0C1 is due
    to a branch to low memory (R15 = 00000000, shown in the machine
    state block associated with the ABEND0C1).
     -
    The save area shows a loop, and this is due to ILBODBG being
    re-entered for the second condition.  This causes LE/370 to
    issue ABENDU4083 RC01 to terminate the processing.
     -
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of the OS/VS COBOL Debug functions.    *
    *                                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1. Use of READY TRACE without any other *
    *                      debug options results in ABENDU4083     *
    *                      RC=1 during processing of a previous    *
    *                      error. See Error description for        *
    *                      additional details.                     *
    *                      2. An ABENDU4087 RC=3 or ABENDU4083     *
    *                      RC=2 may occur during processing of     *
    *                      a previous error when other debug       *
    *                      options are used (with or without       *
    *                      READY TRACE).                           *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The library routines used to process OS/VS COBOL debug options
    during the handling of an LE/370 condition have the following
    problems.
    1. When READY TRACE is the only option used, an internal type 1
    program check occurs followed by detection of a loop in the
    save area backchain. This results in ABENDU4083 RC=1.
    2. When other options are in effect (with or without READY
    TRACE) an internal program check may occur which results
    in either ABENDU4087 RC=3 or ABENDU4083 RC=2.
    

Problem conclusion

  • The LE/370 condition handling library routines will be changed
    to eliminate these problems.
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PN71570

  • Reported component name

    LE COBOL LIB

  • Reported component ID

    568819802

  • Reported release

    320

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    1995-05-18

  • Closed date

    1995-06-16

  • Last modified date

    1995-10-28

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

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

    UN78399 UN78400 UN78401 UN78402 UN78403 UN78404

Modules/Macros

  •    IGZCHCM  ILBODBG
    

Fix information

  • Fixed component name

    LE COBOL LIB

  • Fixed component ID

    568819802

Applicable component levels

  • R22N PSY UN78402

       UP95/06/26 I 1000 «

  • R220 PSY UN78399

       UP95/06/27 P F506 «

  • R32N PSY UN78403

       UP95/06/26 P 9506 «

  • R320 PSY UN78400

       UP95/06/27 P F506 «

  • R42N PSY UN78404

       UP95/06/26 P 9506 «

  • R420 PSY UN78401

       UP95/06/27 P F506 «

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.

[{"Line of Business":{"code":"LOB16","label":"Mainframe HW"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG27M","label":"APARs - z\/VM environment"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"320"}]

Document Information

Modified date:
22 January 2021