IBM Support

PM86921: WMQ 710 - CHANNEL EVENTS ARE NOT GENERATED WHEN WARN=YES IS SPECIFIED IN CHLAUTH RECORDS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • No channel blocked event message with reason
    MQRC_CHANNEL_BLOCKED_WARNING is generated when WARN=YES
    is specified in CHLAUTH records.
    .
    To reproduce the problem, define only one CHLAUTH rule like this
    
    .
    SET CHLAUTH(SYSTEM.ADMIN.SVRCONN) TYPE(ADDRESSMAP) ADDRESS(*)
    USERSRC(NOACCESS) WARN(YES)
    .
    With that rule no channel blocked event message with reason code
    MQRC_CHANNEL_BLOCKED_WARNING is generated.
    
    Changing it from WARN(YES) to WARN(NO) results in a channel
    blocked event message being generated with reason
    MQRC_CHANNEL_BLOCKED.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
    *                 Release 1 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: No channel blocked event message is     *
    *                      generated when WARN=YES is specified in *
    *                      CHLAUTH records.                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The following CHLAUTH rule is defined:
    SET CHLAUTH(SYSTEM.ADMIN.SVRCONN) TYPE(ADDRESSMAP) ADDRESS(*)
    USERSRC(NOACCESS) WARN(YES)
    which should generate an event message with return code 2578
    (MQRC_CHANNEL_BLOCKED_WARNING) in the SYSTEM.ADMIN.CHANNEL When
    a connection is made that is covered by this rule, it is allowed
    and no EVENT message is written to SYSTEM.ADMIN.CHANNEL.EVENT.
    The same definition with WARN(NO) will fail and a message will
    be written to SYSTEM.ADMIN.CHANNEL.EVENT with RC 2577
    (MQRC_CHANNEL_BLOCKED).
    

Problem conclusion

  • Function rsxMapChannelToUserId in CSQXRSCM has been updated to
    honour WARN(YES) on an ADDRESSMAP rule.
    100Y
    CSQXRSCM
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM86921

  • Reported component name

    WMQ Z/OS V7

  • Reported component ID

    5655R3600

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-04-12

  • Closed date

    2013-12-03

  • Last modified date

    2014-01-02

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

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

    UI13137

Modules/Macros

  • CSQXRSCM
    

Fix information

  • Fixed component name

    WMQ Z/OS V7

  • Fixed component ID

    5655R3600

Applicable component levels

  • R100 PSY UI13137

       UP13/12/24 P F312

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:
02 January 2014