IBM Support

PI63005: SUPPORT FOR INVOKING A JAVA EE APPLICATION RUNNING IN LIBERTY FROM A CICS PROGRAM

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as new function.

Error description

  • Cannot invoke Java EE application in running in CICS Liberty.
    .
    Additional Symptom(s) Search Keyword(s):
    A task trying to EXEC CICS LINK to a Liberty application gets
    errors:
    .
    DFHTR0112 Bad data passed for tracing to module DFHTRPT.
    DFHDS0001 An abend (code 0C4/AKEA) has occurred at
      offset X'08D4' in module DFHDSAC.
    DFHDS0001 An abend (code ---/AKEA) has occurred at
      offset X'1444' in module DFHDSKE.
    DFHSJ0002 A severe error (code X'0B07') has occurred in
      module DFHSJJS.
    .
    Kernel stacks for the failing task show that DFHDSAC takes the
    0C4 trying to validate the association token. Trace entries
    show error INVALID_ASSOC_TOKEN
    .
    DSAC_ASSOCIATION_TOKEN VALIDATE_ASSOCIATION_TOKEN DSACS_PTR
    DS_TCB_ASSOC_TOKEN 0B07
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All CICS users.                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Support for invoking a Java EE application running in        *
    * Liberty from a CICS program                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * .                                                            *
    ****************************************************************
    This APAR provides support for a CICS program to invoke a Java
    EE application running in a Liberty JVM server. You can invoke a
    Java EE application either as the initial program of a CICS
    transaction or by using the LINK, START or START CHANNEL
    commands from any CICS program. To be invoked by a CICS program,
    the Java EE application is required to be a plain Java object
    (POJO) packaged in a Web ARchive (WAR) or Enterprise ARchive
    (EAR).
    
    There are three main reasons why you would want to invoke a Java
    EE application from a CICS program:
    -If you have some Java code as part of an existing web
    application and you want to invoke it from a CICS application.
    You only need to maintain a single piece of logic and your code
    can access CICS resources using JCICS APIs.
    -If you want to write a new piece of function in Java as part of
    your CICS application. For example, if you want to use third
    party libraries or APIs that already exist in Java.
    -If you have existing COBOL applications, and you want to
    re-implement those applications in Java. For example, if you
    want to reduce the cost of maintenance, make the most of your
    Java skills, or, if you want your applications to be eligible to
    run on specialty engines rather than general processors.
    

Problem conclusion

  • CICS is changed to provide support for a CICS program to invoke
    a Java EE application running in a Liberty JVM server.  The CICS
    Explorer and CICS build toolkit have also been updated; version
    5.3.0.8 is required to develop Java EE applications that will be
    invoked by a CICS program.
    
    IBM is required to provide you with certain notices and other
    information regarding third party components, included by this
    APAR.
    
    This information is available at:
    
    http://www.ibm.com/support/docview.wss?uid=swg21993159
    
    In addition, the following other fixes are included in this
    APAR:
    
    The following Exception when a JPA application is initialized
    has been resolved:
    org.apache.openjpa.persistence.ArgumentException: The type
    "class <class name>" has not been enhanced.
    
    Changes have been made to reduce the likelihood that CJSU
    transactions are attached for internal Liberty threads.
    
    JVM profile parsing has been updated to support spaces around
    equals signs.
    
    CICS Liberty features have been updated to tolerate being
    restarted, which can occur when adding or removing features from
    server.xml, This avoids the following error:
    java.lang.UnsatisfiedLinkError:
    com/ibm/cics/wlp/threading/CICSThread.createCICSThread(Ljava/lan
    g/String;Ljava/lang/String;IJZLjava/lang/String;IILjava/lang/Str
    ing;IIZLjava/lang/String;)I
    
    Autoconfigure of the cicsts:jdbc-1.0 Liberty feature would in
    rare circumstances, where the customised use of DataSources was
    in operation, over-zealously remove the Liberty jdbc-1.0
    feature. Enhanced checking has been added to ensure there is no
    use of any cicsts dataSources before the jdbc-1.0 feature is
    removed by autoconfigure.
    
    Improvements have been made to shutdown processing in the
    Liberty JVM server, to terminate threads if they do not
    terminate normally. This prevents hangs during shutdown and
    allows a normal DISABLE action to be more effective.
    
    JVM server log cleanup has been fixed to ensure it cleans up
    logs in the configured log directory rather than the default
    location.
    
    DFHAXRO has been marked as non-LPA eligible. This avoids the
    following message:
    DFHLD0109I DFHLDLD1 is unable to locate module DFHAXRO in the
    LPA. DFHRPL or dynamic LIBRARY version of module will be used.
    
    
    The sample JVM profiles have been updated with a link to the IBM
    Knowledge Center page describing the complete set of options
    available.
    

Temporary fix

Comments

  • ×**** PE17/01/12 FIX IN ERROR. SEE APAR PI74853  FOR DESCRIPTION
    ×**** PE17/09/05 FIX IN ERROR. SEE APAR PI85692  FOR DESCRIPTION
    

APAR Information

  • APAR number

    PI63005

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    000

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-05-24

  • Closed date

    2016-10-28

  • Last modified date

    2017-09-05

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

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

    UI42118 UI42119 UI42120 UI42121 UI42122 UI42123 UI42124

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R000 PSY UI42118

       UP16/11/02 P F611

  • R00M PSY UI42120

       UP16/11/02 P F611

  • R001 PSY UI42122

       UP16/11/02 P F611

  • R002 PSY UI42123

       UP16/11/02 P F611

  • R003 PSY UI42124

       UP16/11/02 P F611

  • R00D PSY UI42119

       UP16/11/02 P F611

  • R00L PSY UI42121

       UP16/11/03 P F611

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.



Document information

More support for: CICS Transaction Server

Software version: 5.3

Reference #: PI63005

Modified date: 05 September 2017