IBM Support

PH24650: MQ ARCHIVE LOGS LEFT AS NOT-REUSABLE WHEN MULTIPLE LOGS ARE BEING ARCHIVED AND ARCHIVE LOG CANCEL OFFLOAD IS ISSUED.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Timing issue when multiple logs are being archived and ARCHIVE
    LOG CANCEL OFFLOAD is issued.
    In these circumstances, the existing archiving task is
    terminated and a new task is started to retry the archiving.
    It is possible for the new task to begin processing the
    archiving work before the old task has fully cleaned up its
    state, which can result in logs being archived out of order.
    
     It isn't expected for logs to be archived out of order, so
    once a log with a high RBA is archived, any logs with lower RBA
    values will be ignored by the archiving task.
    This leaves some active logs as "NOT-REUSABLE" because they
    contain log data which hasn't been archived.
    

Local fix

  • na
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of IBM MQ for z/OS Version 9       *
    *                 Release 0 Modification 0 and Release 1       *
    *                 Modification 0.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: When issuing an ARCHIVE LOG CANCEL      *
    *                      OFFLOAD, there exists a timing window   *
    *                      where if the offloading is delayed,     *
    *                      some of the logs may not be archived.   *
    ****************************************************************
    If log offloading is stalling and an ARCHIVE LOG CANCEL OFFLOAD
    is issued, it is possible for a log with a higher RBA value to
    get offloaded ahead of other offloads. The log processing won't
    attempt to offload any logs with lower RBA values so this leaves
    an orphaned active log and a hole in the archived logs.
    

Problem conclusion

  • Log offload serialisation has been improved to stop logs being
    archived out of order.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH24650

  • Reported component name

    IBM MQ Z/OS V9

  • Reported component ID

    5655MQ900

  • Reported release

    000

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-04-21

  • Closed date

    2020-05-27

  • Last modified date

    2020-11-02

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

    PH23018

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

    UI69689 UI69690

Modules/Macros

  • CSQJOFF1 CSQJOFF2 CSQJOFF6 CSQJOFF7 CSQJOFF9
    

Fix information

  • Fixed component name

    IBM MQ Z/OS V9

  • Fixed component ID

    5655MQ900

Applicable component levels

  • R000 PSY UI71358

       UP20/10/14 P F010 ¢

  • R100 PSY UI71359

       UP20/10/14 P F010 ¢

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.

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0"}]

Document Information

Modified date:
03 November 2020