Archive log problems

Use this topic to investigate, and resolve problems with the archive logs.

This topic covers the following archive log problems:


Allocation problems

    Symptoms
    IBM MQ issues message: CSQJ103E 
    CSQJ103E +CSQ1 LOG ALLOCATION ERROR DSNAME=dsname,
           ERROR STATUS=eeeeiiii, SMS REASON CODE=sss
    z/OS dynamic allocation provides the ERROR STATUS. If the allocation was for offload processing, the following message is also displayed: CSQJ115E: 
    CSQJ115E +CSQ1 OFFLOAD FAILED, COULD NOT ALLOCATE AN ARCHIVE
           DATA SET

    System action
    The following actions take place:

    • If the input is needed for recovery, and recovery is not successful, and the queue manager ends abnormally.
    • If the active log had become full and an offload task was scheduled but not completed, the offload task tries again the next time it is triggered. The active log does not reuse a data set that has not yet been archived.

    System programmer action
    None.

    Operator action
    Check the allocation error code for the cause of the problem, and correct it. Ensure that drives are available, and either restart or wait for the offload task to be retried. Be careful if a DFP/DFSMS ACS user-exit filter has been written for an archive log data set, because this can cause a device allocation error when the queue manager tries to read the archive log data set.


Offload task terminated abnormally

    Symptoms
    No specific IBM MQ message is issued for write I/O errors.

    Only a z/OS error recovery program message appears. If you get IBM MQ message CSQJ128E, the offload task has ended abnormally.

    System action
    The following actions take place:

    • The offload task abandons the output data set; no entry is made in the BSDS.
    • The offload task dynamically allocates a new archive and restarts offloading from the point at which it was previously triggered.
    • If an error occurs on the new data set:

      • In dual archive mode, message CSQJ114I is generated and the offload processing changes to single mode: 
        CSQJ114I +CSQ1 ERROR ON ARCHIVE DATA SET, OFFLOAD
           CONTINUING WITH ONLY ONE ARCHIVE DATA SET BEING
           GENERATED
      • In single archive mode, the output data set is abandoned. Another attempt to process this RBA range is made the next time offload processing is triggered.
      • The active log does not wrap around; if there are no more active logs, data is not lost.

    System programmer action
    None.

    Operator action
    Ensure that offload task is allocated on a reliable drive and control unit.


Insufficient DASD space to complete offload processing

    Symptoms
    While offloading the active log data sets to DASD, the process terminates unexpectedly. IBM MQ issues message CSQJ128E: 
    CSQJ128E +CSQ1 LOG OFF-LOAD TASK FAILED FOR ACTIVE LOG nnnnn

    The error is preceded by z/OS messages IEC030I, IEC031I, or IEC032I.

    System action
    IBM MQ de-allocates the data set on which the error occurred. If IBM MQ is running in dual archive mode, IBM MQ changes to single archive mode and continues the offload task. If the offload task cannot be completed in single archive mode, the active log data sets cannot be offloaded, and the state of the active log data sets remains NOT REUSABLE. Another attempt to process the RBA range of the abandoned active log data sets is made the next time the offload task is triggered.

    System programmer action
    The most likely causes of these symptoms are:

    • The size of the archive log data set is too small to contain the data from the active log data sets during offload processing. All the secondary space allocations have been used. This condition is normally accompanied by z/OS message IEC030I. The return code in this message might provide further explanations for the cause of these symptoms. To solve the problem
      1. Issue the command CANCEL queue_manager name to cancel the queue manager job
      2. Increase the primary or secondary allocations (or both) for the archive log data set (in the CSQ6ARVP system parameters), or reduce the size of the active log data set.

        If the data to be offloaded is large, we can mount another online storage volume or make one available to IBM MQ.

      3. Restart the queue manager.

    • All available space on the DASD volumes to which the archive data set is being written has been exhausted. This condition is normally accompanied by z/OS message IEC032I.

      To solve the problem, make more space available on the DASD volumes, or make another online storage volume available for IBM MQ.

    • The primary space allocation for the archive log data set (as specified in the CSQ6ARVP system parameters) is too large to allocate to any available online DASD device. This condition is normally accompanied by z/OS message IEC032I.

      To solve the problem, make more space available on the DASD volumes, or make another online storage volume available for IBM MQ. If this is not possible, we must adjust the value of PRIQTY in the CSQ6ARVP system parameters to reduce the primary allocation. (For details, see Use CSQ6ARVP.)

      Note: If you reduce the primary allocation, you might have to increase the size of the secondary space allocation to avoid future abends.

    Operator action
    None.


Read I/O errors on the archive data set while IBM MQ is restarting

    Symptoms
    No specific IBM MQ message is issued; only the z/OS error recovery program message appears.

    System action
    This depends on whether a second copy exists:

    • If a second copy exists, it is allocated and used.
    • If a second copy does not exist, restart is not successful.

    System programmer action
    None.

    Operator action
    Try to restart, using a different drive.

Parent topic: Example recovery procedures on z/OS