IBM Support

PI71077: CSQX053E XFFSCCXSETASYNCMODE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • CSQX053E CSQXFFST Error information recorded in CSQSNAP data set
    Problem occurs when there is a send() (e.g. as indicated by
    message CSQX206E) during the starting of a new client
    conversation. rriAsyncConvControl ccxCA_START_CONV processing
    allocates a new cciCONV block and then invoked MQCONNX, which
    will add the cciCONV to a list of known connections for this
    dispatcher TCB. However, if there is then a network failure
    trying to send a response to the client, the cciCONV is released
    although the cciCONV is not removed from the list of known
    connections for the dispatcher TCB. If the cciCONV storage is
    reused for another cciCONV running on the same dispatcher TCB as
    previously, then the MQCONNX will fail with MQRC MQRC 2002,
    MQRC_ALREADY_CONNECTED, and the FFST will be issued by
    ccxSetAsyncMode.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users of IBM MQ for z/OS Version 9 Release 0             *
    * Modification 0.                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * A SHARECNV>0 SVRCONN channel failed to start and             *
    * ccxSetAsyncMode generates error message CSQX053E and FFST    *
    * datasets. The FFSTs report a reason code x'07D2' 2002        *
    * MQRC_ALREADY_CONNECTED.                                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * N/A                                                          *
    ****************************************************************
    The problem happens when a SVRCONN channel fails to start after
    it has connected to the queue manager and terminates leaking an
    active HCONN (queue manager connection handle).
    
    A subsequent start SVRCONN channel fails generating the FFST by
    ccxSetAsyncMode reporting MQRC 2002 (MQRC_ALREADY_CONNECTED)
    when the above HCONN is assigned to this channel connection.
    

Problem conclusion

  • MQDISC is now issued freeing any HCONN that have been assigned
    during the process of starting a SHAREDCNV>0 SVRCONN channel
    that has failed.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI71077

  • Reported component name

    MQ Z/OS V9

  • Reported component ID

    5655MQ900

  • Reported release

    000

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-10-21

  • Closed date

    2016-10-27

  • Last modified date

    2017-02-01

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

    PI66009

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

    UI42116

Modules/Macros

  • CSQXCCAX CSQXRMAS
    

Fix information

  • Fixed component name

    MQ Z/OS V9

  • Fixed component ID

    5655MQ900

Applicable component levels

  • R000 PSY UI42116

       UP17/01/10 P F701

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":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
01 February 2017