IBM Support

PI53926: Providing the ability for a queue manager to be unable to start an outgoing shared TCP channel

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Changes to allow a queue manager to be specified as being unable
    to have a shared TCP channel started on it, when it has an
    active channel initiator and is a memeber of a queue shared
    group.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
    *                 Release 1 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: This APAR enables the ability to        *
    *                      restrict shared outgoing TCP channels   *
    *                      from being started on specified queue   *
    *                      managers through a service parm.        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    All queue managers within a queue sharing group, with an active
    channel initiator may be eligible to have a outgoing shared
    channel started on it. The starting of a outgoing shared channel
    can either be fixed to only a single queue manager, or any
    eligible queue manager in the QSG. Any queue manager with
    connection to the QSG, DB2 and the appropriate communication
    subsystem, and spare capacity (not at max channels or max
    channels for the communication method) can be selected. However
    it may not be appropriate for some qmgrs in the QSG to be able
    to start outgoing channels while still having an active channel
    initiator. This APAR implements the ability to restrict the
    starting of outgoing shared channels using TCP to be started on
    specific qmgrs.
    

Problem conclusion

  • A new service parm has been introduced to allow a queue manager
    to be restricted from starting outgoing shared TCP channels.
    Please contact IBM support for further details on how to enable
    this.
    
    --------Knowledge Center Changes--------
    A new page will be added knowledge center at location
    >WebSphere MQ
     >z/OS Messages and Codes
      >Distributed queuing messages (CSQX...)
    
    Title -
    CSQX117I: csect-name Outgoing shared channels
    are restricted from starting for TCP communication
    
    Contents-
     Explanation -
    A CHISERVP() service parm flag has been set which
    restricts the ability for this queue manager from
    being able to start an outgoing shared TCP channel.
    For more details on this flag contact IBM support.
    
     Severity -
    0
    
     System action -
    Processing continues. This queue manager will be unable
    to start outgoing shared TCP channels, and will not be
    selected during MQ workload balanced start of a shared
    channel. This restriction will persist until the flag
    is disabled and channel initiator is restarted.
    
    ----------------------------------------
    
    A link to the new page will also be added to page at
    location
    >WebSphere MQ
     >z/OS Messages and Codes
      >Distributed queuing messages (CSQX...)
    
    With the title -
    CSQX117I: csect-name Outgoing shared channels
    are restricted from starting for TCP communication
    ----------------------------------------
    100Y
    101Y
    102Y
    103Y
    104Y
    105Y
    CSQFXTXC
    CSQFXTXE
    CSQFXTXF
    CSQFXTXK
    CSQFXTXU
    CSQXQMPU
    CSQXSPRI
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI53926

  • Reported component name

    WMQ Z/OS V7

  • Reported component ID

    5655R3600

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / New Function / Xsystem

  • Submitted date

    2015-12-11

  • Closed date

    2016-02-17

  • Last modified date

    2016-05-04

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

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

    PI54073 UI35426 UI35427 UI35428 UI35429 UI35430 UI35431

Modules/Macros

  • CSQFXTXC CSQFXTXE CSQFXTXF CSQFXTXK CSQFXTXU CSQXQMPU CSQXSPRI
    

Fix information

  • Fixed component name

    WMQ Z/OS V7

  • Fixed component ID

    5655R3600

Applicable component levels

  • R100 PSY UI35426

       UP16/04/12 P F604  

  • R101 PSY UI35427

       UP16/04/12 P F604  

  • R102 PSY UI35428

       UP16/04/12 P F604  

  • R103 PSY UI35429

       UP16/04/12 P F604  

  • R104 PSY UI35430

       UP16/04/12 P F604  

  • R105 PSY UI35431

       UP16/04/12 P F604  

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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 May 2016