IBM Support

PH60843: LIBERTY JVM SERVER FAILURE OCCURS DUE TO CICS APPLID CONTAINING SPECIAL CHARACTER

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Running a Liberty JVM server in CICS with the Link to Liberty
    function, the following errors occurred:
    
    E CNTR0075E: The user-provided class
    "com.ibm.cics.server.invocation.proxy.LinkBean_xxx" needed by
    the EnterpriseBean could not be found or loaded.
    I FFDC1015I: An FFDC Incident has been created: "com.ibm.wsspi.
    injectionengine.InjectionException:com.ibm.ejs.container.EJBCon
    figurationException:Bean class com.ibm.cics.server.invocation.pr
    could not be loaded
    com.ibm.ws.webcontainer.osgi.DynamicVirtualHost startWebApp" at
    ffdc_xxx_yyy.log
    E CWWKE0701E: [com.ibm.cics.wlp.link.impl.connector]
    [CICSMessageWorker] @Error: handleLinkableInvocationException()
    - Exception com.ibm.cics.wlp.link.LinkableNotFoundException: No
    linkable services was found for program CICSPGM
    
    
    The summary of the situation:
    - deleting the workarea directory allows
    com.ibm.cics.wlp.program.link.connector to start
    - however upon restart of the Liberty JVM server the
    ClassNotFoundException for
    com.ibm.cics.wlp.link.impl.connector.CICSResourceAdapter occurs
    - when the com.ibm.cics.wlp.program.link.connector starts
    successfully, we then get NoClassDefFoundError for
    com.ibm.cics.server.invocation.InvocationProxy
    
    The CICS APPLIDs all contained a pound (#) sign as the fourth
    character which meant there was
    /directory/structure/CIC/org.eclipse.osgi directory created that
    all the JVM servers were sharing.  This was leading to the
    strange class loading problems.  The problem wouldn't have
    occurred until multiple JVM servers were set up.
    

Local fix

  • Edit the WLP_USER_DIR parameter in the JVM profile, removing the
    &APPLID from the setting.  This allows the server to start up,
    load the resource adapter file and install the bundle
    application successfully.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: The OSGi framework storage directory is *
    *                      created in the incorrect location for   *
    *                      JVMSERVER names and regions with        *
    *                      APPLIDs containing #, $, or %.          *
    ****************************************************************
    When a JVMSERVER or APPLID contains the characters #, $, or %,
    the OSGi framework storage directory will be incorrectly located
    in a directory with all the characters before the first #, $,
    or %.
    
    For example, JVMSERVER MY#JVMA would result in the following
    directory structure:
    
    directory/structure/MYAPPLID/MY/org.eclipse.osgi
    
    If another JVMSERVER was then started with name MY#JVMB there
    would be a conflict for the directory.
    
    This results in the Liberty servers not being able to use the
    CICS Link to Liberty function.
    

Problem conclusion

  • CICS has been changed so that a JVMSERVER name or APPLID
    containing the characters #, $, or % are substituted with _h,
    _d, and _p respectively when used for the OSGi framework storage
    directory.
    
    For example, JVMSERVER MY#JVMA would result in the following
    directory structure:
    
    directory/structure/MYAPPLID/MY_hJVMA/org.eclipse.osgi
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH60843

  • Reported component name

    CICS TS Z/OS V6

  • Reported component ID

    5655YA100

  • Reported release

    400

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-04-11

  • Closed date

    2024-10-14

  • Last modified date

    2024-11-03

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

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

    UI98735 UI98736

Modules/Macros

  • DFHAPJVM DFHAXIS2 DFHCDJNI DFHSJCLS DFHSJDGS DFHSJPP  DFHSJSC
    DFHSJT8  DFJ@H350 DFJ@H360 DFJ@H427 DFJ@H467 DFJ@H609 DFJDTCOE
    DFJOUTRE DFJWLPBP DFJWLPPL
    

Fix information

  • Fixed component name

    CICS TS Z/OS V6

  • Fixed component ID

    5655YA100

Applicable component levels

  • R400 PSY UI98736

       UP24/10/16 P F410

  • R500 PSY UI98735

       UP24/10/16 P F410

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":"BU048","label":"IBM Software"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB70","label":"Z TPS"}}]

Document Information

Modified date:
03 November 2024