IBM Support

PM84015: CSQJ105E IS ISSUED REPEATEDLY AND LOG SWITCH DOES NOT OCCUR

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • CSQJW107 fails to update the end RBA of the active log dataset
    (LDSDWND6) if there is a failure writing to the first CI of
    the dataset. This means that CSQJW107 does not invoke
    CSQJW307 to perform log-switch, so CSQJ105E is repeatedly
    issued for the same active log dataset.
    

Local fix

  • Cancel the queue manager if it is still running.
    Use CSQJU003 to remove the faulty active log dataset(s).
    Start the queue manager. It should resume normal processing.
    
    Use the normal procedures to add more active log datasets to
    replace the ones that were deleted.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
    *                 Release 1 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: The QMGR issues CSQJ105E repeatedly for *
    *                      the same active log data set.           *
    *                      The QMGR loses the ability to write     *
    *                      anything to the logs, causing it to     *
    *                      not be able to carry out any more       *
    *                      recoverable work.                       *
    *                      Any applications trying to do           *
    *                      recoverable work will start hanging.    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If a failure occurs during the write to the first Control
    Interval (CI) in the current active log dataset by the queue
    manager, CSQJW701 should update the end RBA of the current log
    and switch to the next active log.
    However this does not happen, thus the queue manager keeps
    retrying the write to the same active log.
    

Problem conclusion

  • The code was changed to correctly update the end RBA of the
    active log dataset and switch to the next active log.
    100Y
    CSQJW107
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PM84015

  • 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-03-04

  • Closed date

    2013-03-21

  • 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:

    UK92771

Modules/Macros

  • CSQJW107
    

Fix information

  • Fixed component name

    WMQ Z/OS V7

  • Fixed component ID

    5655R3600

Applicable component levels

  • R100 PSY UK92771

       UP13/05/03 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