IBM Support

PI97320: CICS GOES INTO A LOOP AFTER STARTING A 2ND JVMSERVER 19/01/21 PTF PECHANGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A CICS region goes into a loop as soon as a second JVM server
    is started. The problem started to appear after installing
    RSU1803.
    .
    The systrace shows that the loop happens in modules IGC0003C
    and IGVVSTOR.
    
    The following message appears once the 2nd JVM is started:
    
    CWWKB0101I: The angel process is not available. No authorized
                services  will be loaded. The reason code is 260.
    
    A reason code 260 means a Liberty server by that name is
    already connected to the angel process.
    
    It appears that the option WLP_ZOS_PLATFORM=FALSE is ignored
    and that it still tried to connect to the angel process.
    

Local fix

  • not available
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS Users with PI92263                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: Liberty JVM server with                 *
    *                      WLP_ZOS_PLATFORM=false incorrectly      *
    *                      connects to the Liberty angel process.  *
    ****************************************************************
    If a JVMProfile has WLP_ZOS_PLATFORM=false set then when the
    Liberty JVM server starts up it incorrectly connects to the
    angel process. This can lead to unpredictable errors during the
    lifetime of the Liberty server.
    

Problem conclusion

  • UI53798 UI57489 UI57501 UI59403 UI53800 UI57491 UI57502 UI59406
    UI60335
    
    Corrected the launching of the Liberty server within CICS so
    that it does not connect to the angel process.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI97320

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    000

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-04-30

  • Closed date

    2019-01-22

  • Last modified date

    2019-02-02

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

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

    UI60852 UI60853 UI60854

Modules/Macros

  • DFHWLPAX
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R00L PSY UI60852

       UP19/02/02 P F901 {

  • R10L PSY UI60853

       UP19/02/02 P F901 {

  • R20L PSY UI60854

       UP19/02/02 P F901 {

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":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.3","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"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":"5.3","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 February 2019