IBM Support

PI11537: QUEUE MANAGER ABNORMAL TERMINATION REASON=00F30420

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • QUEUE MANAGER ABNORMAL TERMINATION REASON=00F30420
    .
    In the MSTR Job-Log:
    .
    QUEUE MANAGER ABNORMAL TERMINATION REASON=00F30420
    SYSTEM COMPLETION CODE=0D6  REASON CODE=00000027
     TIME=10.22.59  SEQ=01875  CPU=0080  ASID=011D
     PSW AT TIME OF ERROR  077C1000   A5D05900  ILC 4  INTC 27
       ACTIVE LOAD MODULE    ADDRESS=25CF93B0  OFFSET=0000C550
       NAME=CSQVGEPL
       DATA AT PSW  25D058FA - 804890EC  D00C4400  E000982C
       AR/GR 0: A5D05904/0000000C   1: 00000000/7EE22E8C
             2: 00000000/265654B0   3: 00000000/25A4B6B0
             4: 00000000/000003DC   5: 00000000/25A4B744
             6: 00000000/25C50118   7: 00000000/00000001
             8: 00000000/25C4B980   9: 00000000/0000000B
             A: 00000000/A5D04342   B: 00000000/25D05341
             C: 00000000/7EE22C38   D: 00000000/7EE22C38
             E: AA5F8C52/25C4B9C8   F: 25C50118/0018C01F
     END OF SYMPTOM DUMP
    .
    In the svcdump that was generated:
    .
    Symptom             Description
    -------             -----------
    PIDS/5655R3600      Program id: 5655R3600
    RIDS/CSQ3AMGP#L     Load module name: CSQ3AMGP
    RIDS/CSQ3TM00       Csect name: CSQ3TM00
    AB/S05C6            System abend code: 05C6
    PRCS/00F30457       Abend reason code: 00F30457
    REGS/0C173          Register/PSW difference for R0C: 173
    RIDS/CSQ3AAES#R     Recovery routine csect name: CSQ3AAES
    .
    The analysis from the dump shown the 5C6-00F30457
    abend issued by CSQ3TM00.
    The problem occurs when an RRS batch application
    (in this case the broker) publishes a message to a topic
    which has PersistentMsgDelivery set to MQDLV_ALL.
    A nested unit of work is started and the puts of the
    publication messages are performed in-syncpoint.
    This results in ACEANPC being set by CSQIRRSI.
    When all of the publications have been put successfully,
    the next unit of work is committed.
    However, ACEANPC is not reset. When RRS is restarted it
    will try and clean-up all of the RRS batch ACEs.
    As  part of this processing CSQ3TM00 is invoked, and
    invokes CSQ3CT80 for thread termination, indicating that
    normal termination should take place as there is no
    inflight unit of work.
    However, CSQ3CT80 detects that ACEANPC is set, although
    it has been invoked for normal termination and therefore
    fails the request with reason code 00F30093.
    CSQ3TM00 detects the failure and the 5C6-00F30457 abend
    is issued, resulting in the queue-manager abending with
    reason code 00F30420.
    ..
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
    *                 Release 0 Modification 1 and Release 1       *
    *                 Modification 0.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Abend 5C6-00F30457 in CSQ3TM00 occurs   *
    *                      following RRS restart. The abend is     *
    *                      followed by queue manager termination   *
    *                      6C6 with reason 00F30420.               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When an RRS application publishes a message to a topic out of
    syncpoint, an internal nested uow is created if the message
    delivery option (NPMSGDLV/PMSGDLV) requires messages to be
    successfully delivered to all (or all durable) subscribers, or
    if the publication uses MQPMO_RETAIN option.
    When the publication is delivered to the subscriber queues, the
    context ACE is flagged as no longer being at a point of
    consistency (ACEANPC = on).
    After the publication completes, the internal uow is committed
    however ACEANPC is not cleared.
    
    When RRS is restarted CSQ3RRSR resyncs with RRS and drives
    the context ACE through EOT processing.
    The ACE is incorrectly flagged as not being at a point of
    consistency, leading to the reported abend and queue manager
    termination.
    

Problem conclusion

  • CSQINTOP is changed to reset ACEANPC when an internal uow is
    committed and returns the ACE to a point of consistency.
    010Y
    100Y
    CSQINTOP
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PI11537

  • Reported component name

    WMQ Z/OS V7

  • Reported component ID

    5655R3600

  • Reported release

    010

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-02-12

  • Closed date

    2014-03-06

  • Last modified date

    2014-05-02

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

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

    UI15768 UI15769

Modules/Macros

  • CSQINTOP
    

Fix information

  • Fixed component name

    WMQ Z/OS V7

  • Fixed component ID

    5655R3600

Applicable component levels

  • R010 PSY UI15768

       UP14/04/08 P F404 Ž

  • R100 PSY UI15769

       UP14/04/08 P F404 Ž

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.0.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 May 2014