IBM Support

PH36641: DFHSJ1009 "A TASK RUNNING IN A JVMSERVER HAS TRIGGERED A RUNAWAY CONDITION" ALWAYS HAS CJSL TRANID VS THE ACTUAL RUNAWAY TRANID.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • This message is thrown and the tranid shows CSJL, which is not
    the task that was detected as runaway;
    
    DFHSJ1009 W date time
    applid tranid trannum JVMSERVER jvmserver is being disabled and
    restarted by CICS because a task running in a JVMSERVER has
    triggered a runaway condition, leaving the JVMSERVER in an
    inconsistent state.
    
    When DFHSJ1009 occurs CICS attempts a PHASEOUT. Then after a
    delay CICS does a PURGE which typically would cause programs
    looping to get a ThreadDeath, which would turn AKC3 abend which
    would identify the runaway transaction in the log. However, in
    the case where the transaction is behaving normally, such as a
    long running task, it may not abend and there is nothing in the
    log indicating which transaction triggered the runaway.
    
    This APAR is to update DFHSJ1009 to include the transaction
    that triggered the runaway.
    
    Additional
    symptoms:
    KIXREVSVR
    DFHSJ0917I
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS Users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: A task running in a JVMSERVER triggers  *
    *                      a runaway condition and issues message  *
    *                      DFHSJ1009. The message does not         *
    *                      identify the runaway task.              *
    ****************************************************************
    A task running in a JVMSERVER triggers a CICS runaway condition
    and issues message DFHSJ1009, however it is of limited use when
    it comes to diagnosing which task it was that caused the
    runaway.  A dump and trace need to be examined to identify the
    offending task.
    
    Keywords: msgDFHSJ1009 SJ1009
    

Problem conclusion

  • A new message DFHSJ1010 will now be issued when a task running
    in a JVMSERVER triggers a runaway condition. Message DFHSJ1010
    will include both the transaction number and taskid causing
    the runaway.
    
    A new message will be added to CICS Transaction Server for z/OS
    5.5 and 5.6 Documentation:
    
    DFHSJ1010 W  date time applid tranid trannum JVMSERVER jvmserver
    is being disabled and restarted by CICS because taskname task
    tasknum running in the JVMSERVER has triggered a runaway
    condition, leaving the JVMSERVER in an inconsistent state.
    
    Explanation
    
    JVMSERVER jvmserver is being restarted by CICS because it is in
    an inconsistent state. A task runaway condition has occured,
    leaving the JVM in an inconsistent state.
    
    System action
    
    CICS disables the JVMSERVER resource with the PHASEOUT option to
    allow existing work in the JVM to complete where possible and
    prevent new work from using the JVM. After the JVMSERVER is
    successfully disabled, message DFHSJ1008 is issued. CICS
    attempts to re-enable the resource to create a new JVM.
    
    User response
    
    Determine why the task triggered runaway processing.
    
    Module
    
    DFHSJJS
    
    XMEOUT parameters/Message inserts
    
    1. date
    2. time
    3. applid
    4. tranid
    5. trannum
    6. jvmserver
    
    Destination
    
    CSMT and Console
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH36641

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    200

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-04-23

  • Closed date

    2021-08-02

  • Last modified date

    2021-09-01

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

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

    UI76554 UI76555

Modules/Macros

  • DFHAPJVM DFHAXIS2 DFHCDJNI DFHKETIX DFHMESJC DFHMESJE DFHMESJK
    DFHSJJS  DFJ@H356 DFJ@H360 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

  • R200 PSY UI76555

       UP21/08/13 P F108

  • R300 PSY UI76554

       UP21/08/13 P F108

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.

[{"Line of Business":{"code":"LOB35","label":"Mainframe SW"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.5"}]

Document Information

Modified date:
02 September 2021