IBM Support

PM82109: ABENDS602 CSQV086E QUEUE MANAGER ABNORMAL TERMINATION REASON 00E80100 DURING QMGR RESTART

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Level 3 analysis determined the problem occurs when using
    GROUPUR with CICS. If there are multiple CICS systems on the
    same LPAR connecting via the queue-sharing group name,and
    these CICS systems are shutdown after the queue-manager has
    been shutdown, then the S602 abend seen here may occur when
    restarting the queue-manager. The problem is in CSQ3AMI2 where
    it posts the ECBs for waiting CICS systems (which are waiting
    to be notified that the queue-manager is now active).
    CSQ3AMI2 has recovery processing to anticipate a S602 abend
    and retry from it, but this recovery processing only takes
    effect the first time a S602 occurs, i.e. if there are more
    than one ECB with an 'invalid' ASCB address (invalid because
    the address space has ended and the ASCB storage cleaned-up),
    then the S602 will occur when posting the second ECB.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ Version 7          *
    *                 Release 1 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Abend 602-00000000 is generated in      *
    *                      CSQGFRCV and the queue manager          *
    *                      terminates with reason 00E80100.        *
    *                                                              *
    *                      This abend happens when two or more     *
    *                      CICS regions that were connected to the *
    *                      queue manager are terminated before the *
    *                      queue manager is restarted.             *
    *                                                              *
    *                      The CICS regions connect using the      *
    *                      queue sharing group name and the group  *
    *                      resync (GROUPUR) feature.               *
    *                                                              *
    *                      A similar problem happens when the      *
    *                      queue manager is started with           *
    *                      GROUPUR(DISABLED) and the command ALTER *
    *                      QMGR GROUPUR(ENABLED) is entered after  *
    *                      the queue manager has restarted.        *
    *                                                              *
    *                      In this case, abend 602-00000000 is     *
    *                      generated in CSQ9SCN9 but the queue     *
    *                      manager does not terminate and GROUPUR  *
    *                      is enabled.                             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Abend S602 happens when CSQ3AMI2 posts an ECB in a CICS region
    that has been terminated.
    
    The first S602 abend is retried and no dump is generated. The
    second and subsequent S602 abends are not retried and dump is
    generated.
    
    Queue manager stops because abend S602 is not handled by the
    recovery routine CSQGFRCV allowing the exception to percolate
    terminating the queue manager.
    
    A similar problem exists in CSQMCAMM when processing command
    ALTER QMGR GROUPUR(ENABLED) but abend S602 does not terminate
    the queue manager.
    

Problem conclusion

  • CSQ3AMI2 and CSQMCAMM have been changed to reenable retry
    following the successful retry of a S602 abend to avoid
    dumps and the termination of the queue manager.
    100Y
    CSQMCAMM
    CSQ3AMI2
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PM82109

  • Reported component name

    WMQ Z/OS V7

  • Reported component ID

    5655R3600

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-02-05

  • Closed date

    2013-03-22

  • Last modified date

    2013-06-04

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

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

    UK92814

Modules/Macros

  • CSQMCAMM CSQ3AMI2
    

Fix information

  • Fixed component name

    WMQ Z/OS V7

  • Fixed component ID

    5655R3600

Applicable component levels

  • R100 PSY UK92814

       UP13/05/08 P F305 Ž

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 June 2013