IBM Support

PH54360: THE FAILURE IN CONTAINERITERATOR IS INCORRECTLY THROWING THE EXCEPTION WHEN IT SHOULDN'T BE AND CAUSING THE LOGS TO FILL

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

  • Customer had a couple of logging and monitoring outages due to
    full disk space since upgrading to CICS 6.1. The culprit seems
    to be JVM log files :
    
    E.g.
     dfhjvmlog
     dfhjvmout
     dfhjvmtrc
     dfhjvmerr
    
    most of these logs seem related to JCICS Channel
    containerIterator() throwing repeated errors.
    
    [err] 2023/04/29 21:52:36.366000 GMT+08:00
    
    [DFHSJTHP.TASK80070.CJSA] [com.ibm.cics.server] [Channel]
    @Error: getContainerNames exception () - CICS CHANNELERR
    Condition, CHANNEL_ERROR, 2,
    com.ibm.cics.delegate.DelegateError: CICS CHANNELERR Condition
    CHANNEL_ERROR(10) resp=122 resp2=2 abcode=null
    com.ibm.cics.delegate.DelegateError: CICS CHANNELERR Condition
    CHANNEL_ERROR(10) resp=122 resp2=2 abcode=null
        at com.ibm.cics.delegate.impl.DelegateChannelImpl.NativeGet
                                       ContainerNames(NativeMethod)
        at com.ibm.cics.delegate.impl.DelegateChannelImpl.getContain
                               erNames(DelegateChannelImpl.java:125)
        at
    com.ibm.cics.server.Channel.getContainerNames(Channel.java:969)
        at com.ibm.cics.server.ContainerIterator.getContainerNames(
                                        ContainerIterator.java:160)
        at com.ibm.cics.server.ContainerIterator.<init>(Container
                                                  Iterator.java:138)
        at
    com.ibm.cics.server.Channel.containerIterator(Channel.java:821)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS Users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Empty Channel causes exception log      *
    *                      message when creating a                 *
    *                      ContainerIterator.                      *
    ****************************************************************
    An application creates an empty Channel using the JCICS
    Task.createChannel(). It then calls containerIterator() to
    create a ContainerIterator for the Channel. The call is
    successful but an error is incorrectly logged to stderr /
    jvmlog.
    

Problem conclusion

  • The JCICS code has been updated to not log the error in this
    scenario.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH54360

  • 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

    2023-05-07

  • Closed date

    2023-05-26

  • Last modified date

    2023-06-01

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

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

    UI91984

Modules/Macros

  • DFJ@H356
    

Fix information

  • Fixed component name

    CICS TS Z/OS V6

  • Fixed component ID

    5655YA100

Applicable component levels

  • R400 PSY UI91984

       UP23/05/27 P F305

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

Document Information

Modified date:
01 June 2023