IBM Support

PH14856: SUPPORT BASIC SPRINGBOOT LINK-2-LIBERTY MECHANISM

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • Support basic SpringBoot Link-2-Liberty mechanism
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Provide support for EXEC CICS LINK to a *
    *                      Spring Boot application running in a    *
    *                      Liberty JVM server.                     *
    ****************************************************************
    This APAR provides support for invoking a Spring Boot
    application deployed in a Liberty JVM server. An application
    developer can add the @CICSProgram annotation to a method
    on a Spring bean.  When the application is started in Liberty,
    a CICS program definition is dynamically created.
    You can then call the Spring Boot application using an
    EXEC CICS LINK from any CICS program.
    
    CICS Explorer 5.5.0.5 also includes updates to the CICS
    annotation processor required for linking to Spring Boot
    applications. The annotation processor will also be updated on
    Maven Central.
    
    This APAR also resolves several existing problems with Link to
    Liberty:
    1. Link to Liberty does not work for non-void methods:
    It is not possible to invoke a Java method with a non-void
    return type. It fails at runtime with an AJ05 abend and a
    java.lang.NoSuchMethodError.
    To avoid this, the CICS annotation processor now issues an error
    message if an @CICSProgram annotation is added to a non-void
    method.
    
    2. Link to Liberty listener is enabled after applications are
    enabled:
    The Link to Liberty implementation involved an MDB, which was
    deployed as a Liberty application. This could start after other
    user applications, causing failures if these applications were
    invoked before the Link to Liberty MDB was available. Symptoms
    include the DFHSJ1006 message and EXEC CICS LINK RESP=INVREQ,
    RESP2=53.
    This is resolved by removing the requirement for the MDB, so
    that Link to Liberty functionality is available prior to any
    user applications starting.
    
    3. Warning message on every Link to Liberty when CICS security
    is disabled:
    The following warning appears in messages.log if SEC=NO is
    set:
    CWWKE0700W: [com.ibm.cics.wlp.link.impl]
    [CICSSecurityContextServiceRef] @Warning:
    createCICSSecurityContext() - CICSSecurityContextService
    unavailable. CICSSecurityContext will not be created
    
    This message is downgraded to debug level, and will only be
    visible in dfhjvmtrc when tracing is active.
    
    After applying this APAR, if a Liberty application invoked
    by EXEC CICS LINK throws an Exception, Liberty
    will create an FFDC.  For example:
    FFDC1015I: An FFDC Incident has been created:
    "java.lang.reflect.InvocationTargetException
    com.ibm.ws.context.service.serializable.
    ContextualInvocationHandler"
    This can safely be ignored. This has been resolved by the
    Open Liberty project via
    https://github.com/OpenLiberty/open-liberty/issues/9499
    and the fix will appear in a forthcoming Liberty fix pack.
    

Problem conclusion

Temporary fix

Comments

  • This APAR provides support for invoking a Spring Boot
    application deployed in a Liberty JVM server.
    
    Information on new and updated open source components associated
    with this APAR can be found here:
    https://www.ibm.com/support/pages/node/1107033
    

APAR Information

  • APAR number

    PH14856

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    200

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-07-24

  • Closed date

    2019-11-20

  • Last modified date

    2019-11-30

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

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

    UI66515

Modules/Macros

  • DFJ@H444 DFJ@H445 DFJ@H467 DFJ@H471 DFJ@H490
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R200 PSY UI66515

       UP19/11/21 P F911

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.5","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.5","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
30 November 2019