IBM Support

PH51034: Under CEEPIPI with COBDESTROYJVM=1, the COBOL runtime fails to destroy the second and subsequent JVMs

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In a reusable environment like the one created by CEEPIPI, the
    COBOL runtime's explicit JVM destroy feature COBDESTROYJVM=1
    fails for the second and subsequent JVMs created in the
    environment.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of Enterprise COBOL 5 and later        *
    *                 releases running COBOL programs that use     *
    *                 environment variable COBDESTROYJVM set       *
    *                 to 1 in a preinitialized environment         *
    *                 created by CEEPIPI or similar services.      *
    ****************************************************************
    * PROBLEM DESCRIPTION: An application terminates with an       *
    *                      unexpected 0C1 abend in an unknown      *
    *                      module. The abend occurs because of     *
    *                      branching to an address zero at         *
    *                      IGZXTRN1+'X55E.                         *
    ****************************************************************
    * RECOMMENDATION: Apply the PTF                                *
    ****************************************************************
    When an environment variable 'COBDESTROYJVM' is set to 1,
    COBOL Runtime destroys a JVM when COBOL programs terminate.
    
    However, in a preinitialized environment created by CEEPIPI or
    similar services where COBOL programs interacting with Java
    were called multiple times and 'COBDESTROYJVM' was set to 1,
    COBOL Runtime failed to destroy a JVM at the second time when
    the COBOL program terminated.
    
    COBOL Runtime inadvertently used a JVM destroy function
    that had been dynamically loaded and freed when the first
    call to COBOL program terminated.
    
    Refer to PH26029 for details on COBDESTROYJVM.
    
    COB0501T/K COB0502T/K COB0601T/K COB0602T/K COB0603T/K
    COB0604T/K
    

Problem conclusion

  • COBOL Runtime has been corrected to check and reload the JVM
    destroy function accordingly.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH51034

  • Reported component name

    LE ENT COBOL LI

  • Reported component ID

    568819812

  • Reported release

    7D0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-11-21

  • Closed date

    2022-12-13

  • Last modified date

    2023-01-03

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

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

Modules/Macros

  • IGZCER4  IGZCEV4  IGZCJNI2 IGZLLIBV IGZXAPI  IGZXCA31 IGZXCDA
    IGZXD24  IGZXDMR  IGZXJNI2 IGZXLPIO IGZXLPKA IGZXLPKB IGZXLPKC
    IGZXLPKD IGZXLPKE IGZXLPKF IGZXLPKG IGZXPK2
    

Fix information

  • Fixed component name

    LE ENT COBOL LI

  • Fixed component ID

    568819812

Applicable component levels

  • R7C0 PSY UI83716

       UP22/12/16 P F212

  • R7D0 PSY UI83717

       UP22/12/16 P F212

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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SS6SG3","label":"Enterprise COBOL for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7D0","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
05 January 2023