IBM Support

PI42987: WMQ: CSQJ103E CSQJDS06 LOG ALLOCATION ERROR, ERROR STATUS=02200000, SMS REASON CODE=00000000

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • As backout was occurring for a long-running unit of work,  the
    following errors occured:
    
    CSQJ103E CSQJDS06 LOG ALLOCATION ERROR, ERROR STATUS=02200000,
      SMS REASON CODE=00000000
    CSQJ151I CSQJR003 ERROR READING RBA rba,
      CONNECTION-ID=id CORRELATION-ID=
      REASON CODE=00D1032B
    CSQV086E QUEUE MANAGER ABNORMAL TERMINATION REASON=00D94001
    IEA794I SVC DUMP HAS CAPTURED:
      DUMPID=061 REQUESTED BY JOB (ssidMSTR)
      DUMP TITLE=ssid,ABN=5C6-00D1032B,U=SYSOPR
    ,M=CSQJRE01,LOC=CSQJL002.CSQJR003
    IEF450I ssidMSTR ssidMSTR - ABEND=S6C6 U0000 REASON=00D94001
    
    Reason 0220 for DYNALLOC:
     Meaning: Requested volume not available.(dsname allocation)
    
    This reason code may mean that the data set is in use by
    someone else and that it has an ENQ. The archive log in
    question had been created several minutes earlier so should
    have been available.
    
    If the timing of the dump does not show the ENQ, VERBX GRSTRACE
    'DETAIL QNAME(SYSDSN)' may show the history of it.
    
    The ENQ was held longer than expected by MQ due to non-zero
    values for the DEALLCT and MAXRTU parameters in CSQ6SYSP.  This
    is the same problem described in DB2 APAR PK85641.
    
    
    Additional Symptom(s) Search Keyword(s):
    CSQJLGR CSQJR002 CSQJR003 02200000
    ABEND5C6 ABENDS5C6 S5C6 S05C6 5C6 00D1032B
    ABEND6C6 ABENDS6C6 S6C6 S06C6 6C6 00D94001
    

Local fix

  • Set the CSQ6LOGP DEALLCT parameter to zero in zparm.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 8 *
    *                 Release 0 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: An ENQ on SYSZVOLS for an archive log   *
    *                      data set tape volume can be left        *
    *                      allocated to the MQ MSTR address        *
    *                      space after the archive log data set    *
    *                      has been closed and deallocated.        *
    *                                                              *
    *                      This can result in errors reading the   *
    *                      logs during shunting or backout         *
    *                      processing, reported by messages:       *
    *                      "                                       *
    *                      CSQJ103E CSQJSD06 LOG ALLOCATION ERROR  *
    *                      DSNAME=xxxx.xxxx.xxxx.xxxx, ERROR       *
    *                      STATUS=02200000, CODE=00000000          *
    *                      "                                       *
    *                      and                                     *
    *                      "                                       *
    *                      CSQJ151I CSQJR003 ERROR READING RBA     *
    *                      xxxxxxxxxxxx, CONNECTION-ID=xxxx        *
    *                      CORRELATION-ID=yyyyyyyy                 *
    *                      CODE=00D1032B                           *
    *                      "                                       *
    *                      These errors are followed by abend      *
    *                      5C6-00D1032B in CSQJL002.CSQJR003       *
    *                      and abnormal queue manager termination  *
    *                      6C6 with REASON=00D94001                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If MQ reaches the maximum tape unit count allocated for
    archive read processing (CSQ6LOGP MAXRTU parm in CSQZPARM),
    CSQJR206 will look for allocated tape volumes that are in
    the delayed deallocation process (CSQ6LOGP DEALLCT parm in
    CSQZPARM).  If any tape volumes are in delayed deallocation,
    MQ will 'steal' the tape unit by modifying the JFCB with the
    new archive log data set information and issuing an OPEN-J
    for this archive log.  The original archive volume will be
    closed and unloaded, allowing the new archive log volume
    to be opened on the allocated tape unit.  Even though the
    tape volume has been unloaded, the ENQ on SYSZVOLS for the
    archive log tape volume is not released.
    

Problem conclusion

  • MQ will now mark an archive log data set in delayed
    deallocation as 'expired', so it will be deallocated
    when MQ has reached the maximum archive tape unit count.
    This will allow the new archive log tape read request to be
    honored after the 'expired' archive log tape unit has been
    deallocated.
    000Y
    CSQJR206
    CSQJR208
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PI42987

  • Reported component name

    WMQ Z/OS 8

  • Reported component ID

    5655W9700

  • Reported release

    000

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-06-15

  • Closed date

    2015-06-25

  • Last modified date

    2015-09-02

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

    PI40603

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

    UI28840

Modules/Macros

  • CSQJR206 CSQJR208
    

Fix information

  • Fixed component name

    WMQ Z/OS 8

  • Fixed component ID

    5655W9700

Applicable component levels

  • R000 PSY UI28840

       UP15/08/11 P F508 ¢

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":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
02 September 2015