IBM Support

PH68177: DFHSJ0001 WHEN JAVA PROGRAM CALLS INVOKEALL() OR INVOKEANY()

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • A Liberty managed executor service is being used to submit
    Callables that can run in parallel.  However use of the untimed
    invokeAll() or invokeAny() methods can cause a CICS task to be
    built on the submitter's thread which if already running a CICS
    task can lead to a DFHSJ0001 and the Liberty server hangs.  Use
    of these methods is not supported.
    
    This APAR will add additional code to guard against a CICS task
    being built on a thread/T8 TCB that is already running a CICS
    task.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: DFHSJ0001 when a Java program calls     *
    *                      invokeAll() or invokeAny().             *
    ****************************************************************
    A Liberty JVM server is enabled and a Java program running under
    a CICS task calls one of the following untimed methods to submit
    Callable objects to the executor:
    - java.util.concurrent.ExecutorService.invokeAll(Collection<?
      extends Callable<Object>> tasks)
    - java.util.concurrent.ExecutorService.invokeAny(Collection<?
      extends Callable<Object>> tasks)
    
    These methods can result in one of the submitted Callables
    running on the submitter's thread.  If the submitted Callable
    causes a CICS task to be built (either because the Callable
    extends CICSTransactionCallable or a JCICS call is made) then
    this results in two CICS tasks running on the same thread / T8
    TCB.  This is not supported and may result in DFHSJ0001,
    DFHXM0001, DFHAP0001 and KERNDUMP errors.
    

Problem conclusion

  • CICS has been updated so that if an attempt is made to build a
    CICS task on a thread / T8 TCB already running a CICS task this
    will be rejected.  The JVM server's stderr will show a
    com.ibm.cics.domains.DomainException with a reason of
    TCB_ALREADY_RUNNING_A_TRAN.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH68177

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    300

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2025-09-17

  • Closed date

    2026-09-04

  • Last modified date

    2026-09-07

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

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

    PH71338 UO09284

Modules/Macros

  • DFHAPJVM DFHAXIS2 DFHCDJNI DFHSJJS  DFHSJJST DFJ@H356 DFJ@H360
    DFJ@H387 DFJ@H427 DFJ@H467 DFJ@H468 DFJDTCOE DFJOUTRE DFJWLPBP
    DFJWLPPL
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R300 PSY UP

       C

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.6","Line of Business":{"code":"LOB70","label":"Z TPS"}}]

Document Information

Modified date:
07 September 2026