IBM Support

PI62746: ABEND0C4 WHEN STARTING WLM ADDRESS SPACE FOR 64BIT JSP FROM ENTRY POINT OF INVOKEJAVA FUNCTION

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Abend0C4 when starting WLM address space for 64bit JVM from
    entry point of invokejava function
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: DB2 11 for z/OS users of Java stored         *
    *                 procedures with 64-bit multi-threaded        *
    *                 Java stored procedure environment.           *
    ****************************************************************
    * PROBLEM DESCRIPTION: The following abend occurs when the     *
    *                      WLM SPAS for 64-bit multi-threaded      *
    *                      JVM starts:                             *
    *                                                              *
    *                      CEE3204S The system detected a          *
    *                               protection exception           *
    *                               (System Completion Code=0C4).  *
    *                                                              *
    *                      Location:                               *
    *                        Program Unit:  Entry: invokejava      *
    *                        Statement:     Offset: +000002F8      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The modules that start JVM environment need to be linkedit'd
    in the certain order. The current JCL for the linkedit job
    doesn't ensure the sequence and may result in the 0C4 abend
    in some circumstances.
    
    Additional keywords:
    ABEND0C4
    

Problem conclusion

  • The linkedit job has been changed to add a control
    statement to ensure the correct sequence for the
    modules that start the JVM.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI62746

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-05-20

  • Closed date

    2016-08-19

  • Last modified date

    2016-10-03

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

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

    UI40229

Modules/Macros

  • DSNX9JV6 HDBBB10J
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RB10 PSY UI40229

       UP16/09/05 P F609

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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"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":"11.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 October 2016