IBM Support

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

A fix is available

Subscribe

You can track all active APARs for this component.

 

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

    PH71338

  • 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

    2026-05-14

  • Closed date

    2026-09-04

  • Last modified date

    2026-09-05

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

    PH68177

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

    UO09286 UO09287 UO09288

Modules/Macros

  • DFHAPJVM DFHAXIS2 DFHCDJNI DFHSJJS  DFHSJJST DFHSJXT  DFHSJXTT
    DFJ@H360 DFJ@H387 DFJ@H427 DFJ@H467 DFJ@H561 DFJ@H609 DFJ@H638
    DFJ@H639 DFJ@H642 DFJDTCOE DFJOUTRE DFJWLPBP DFJWLPPL
    

Fix information

  • Fixed component name

    CICS TS Z/OS V6

  • Fixed component ID

    5655YA100

Applicable component levels

  • R400 PSY UO09286

       UP26/09/05 I 1000

  • R500 PSY UO09287

       UP26/09/05 I 1000

  • R600 PSY UO09288

       UP26/09/05 I 1000

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:
05 September 2026