IBM Support

PI58645: WMQ CICS TRIGGER MONITOR STOPS GETTING MESSAGES FROM INIT QUEUE 16/03/07 PTF PECHANGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After applying a new RSU level, instances of the CICS trigger
    monitor stop picking up messages from the initiation queue.
    Change Team finds that this symptom occurs after application of
    the fix for PI46510(ie. UI33362) where MTHR.csTtoken may
    contain a residual value.
    .
    Additional keywords:
    CKTI GETWAIT MQGET
    CURDEPTH is non-zero for the application and initiation queues
    initq filling fills full 2053 MQRC_Q_FULL
    hang hung hanging stall stalled
    

Local fix

  • Restart CKTI or the CICS adapter (CKQC), but be aware of the
    problem in CICS APAR PI56884.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
    *                 Release 1 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: CICS transactions issuing MQGET with    *
    *                      MQGMO_WAIT or MQGMO_SET_SIGNAL are not  *
    *                      always posted when messages arrive or   *
    *                      the get wait interval expires following *
    *                      application of UI33362.                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    PI46510 changed CSQM1P1W to check if any ACEs are queued for
    deferred termination processing in the address space of the
    handle being posted, and if so to check the TCB associated with
    the handle is still valid before posting it.
    This check is performed using the tcbtoken for the TCB stored
    in the task's mthr.
    However in the CICS environment it is possible that the MTHR
    contains an out of date tcbtoken, causing CSQM1P1W to
    incorrectly determine that the TCB is no longer valid and
    skip posting the handle.
    

Problem conclusion

  • CSQMALL is changed to prevent out of date tcbtoken's remaining
    in the mthr when it is reused in a CICS environment.
    100Y
    CSQMALL
    CSQM1P1W
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PI58645

  • Reported component name

    WMQ Z/OS V7

  • Reported component ID

    5655R3600

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-03-07

  • Closed date

    2016-03-17

  • Last modified date

    2016-05-04

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

    PI58225

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

    UI36299

Modules/Macros

  • CSQMALL  CSQM1P1W
    

Fix information

  • Fixed component name

    WMQ Z/OS V7

  • Fixed component ID

    5655R3600

Applicable component levels

  • R100 PSY UI36299

       UP16/04/15 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