IBM Support

PH44600: NEWLY ADDED LOGS BY DEFINE LOG ARE NOT USED AFTER CSQJ111A ISSUED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After CSQJ111A is issued due to the active log filling, any
    tasks attempting to write to the logs are suspended until log
    space becomes available again.
    The correct behavior is that logging should resume when either:
    1) A successful log archive offload makes an existing active
    log eligible to be reused
    or
    2) DEFINE LOG is used to add a new active log dataset
    .
    However due to the error, if offloads are enabled only a
    successful offload will cause logging to be resumed, and
    logging will not be resumed when additional logs are added by
    DEFINE LOG. Further, if DEFINE LOG is used prior to a
    successful offload logging will remain suspended even after the
    log offload completes.
    

Local fix

  • In order to recover from CSQJ111A without a fix the customer
    would need to ensure that log offloading can succeed, and that
    DEFINE LOG is not issued.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of IBM MQ for z/OS Version 9       *
    *                 Release 1 Modification 0,                    *
    *                 Release 2 Modification 0 and                 *
    *                 Release 3 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: After CSQJ111A is issued and DEFINE LOG *
    *                      is used to add additional logs          *
    *                      dynamically, logging remains suspended  *
    *                      if archive log offloading is enabled.   *
    ****************************************************************
    When the last available log fills CSQJ111A is issued and logging
    is suspended until additional log space is available. If log
    offloading is enabled, a request to offload logs is scheduled,
    however this can be delayed - for example by a configuration
    error or unavailable tape system.
    DEFINE LOG can be used to dynamically add another log data set,
    however this does not resume logging, and prevents it being
    resumed when offloading continues.
    

Problem conclusion

  • DEFINE LOG processing is changed to resume the logger task when
    an additional log is dynamically added while in a log full
    situation.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH44600

  • Reported component name

    IBM MQ Z/OS V9

  • Reported component ID

    5655MQ900

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-03-03

  • Closed date

    2022-07-20

  • Last modified date

    2022-12-15

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

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

    UI81561 UI81562 UI81563

Modules/Macros

  • CSQJC00E CSQJW307
    

Fix information

  • Fixed component name

    IBM MQ Z/OS V9

  • Fixed component ID

    5655MQ900

Applicable component levels

  • R100 PSY UI81563

       UP22/08/03 P F208 ¢

  • R200 PSY UI81562

       UP22/08/03 P F208 ¢

  • R300 PSY UI81561

       UP22/08/03 P F208 ¢

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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"100","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
15 December 2022