IBM Support

PI16027: Issue new message CSQI004I to indicate that MQGET performance can be improved adding a queue index.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Queue manager does not give external indication that MQGET
    performance can be improved adding an index to the queue.
    .
    This fix is included in PI19991 for IBM MQ V8 for z/OS.
    .
    Additional Keywords:
    INDXTYPE INDEXTYPE
    

Local fix

  • Use SMF116 queue accounting records to determine if the queue is
    accessed using selective gets and if there large number of
    messages skipped.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ Version 7          *
    *                 Release 1 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: New message CSQI004I is issued when a   *
    *                      local queue is accessed getting         *
    *                      messages by message id or correlation   *
    *                      id and the queue does not have an index *
    *                      configured.                             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The problem is that the queue manager does not give any external
    indication that performance of MQGET calls can be improved
    adding an index to the queue.
    
    When queues are accessed getting messages selecting by message
    id or correlation id and the queue does not have an index
    configured, poor performance can be experienced when the queue
    depth is high. The queue is scanned sequentially searching for
    the requested message.
    

Problem conclusion

  • New message CSQI004I has been added and it will be issued when a
    local queue is accessed by message id or correlation id without
    index configured and large number of messages are skipped.
    
    ============== DOC Changes for V710 Infocenter ================
    The infocenter for V710 will be updated for this new message:
    
    WebSphere MQ
      > Reference
        > Messages
          > WebSphere MQ for z/OS messages, completion,
              and reason codes
            > Messages for WebSphere MQ for z/OS
              > Message manager messages (CSQI...)
    
    CSQI004I csect-name Consider indexing queue-name by
    index-type for connection-type connection connection-name,
    num-msgs messages skipped.
    
    Explanation -
    The queue manager has detected an application getting messages
    by message ID or correlation ID from a queue that does not
    have an index defined.
    
    The type of index that should be established for the queue is
    indicated by index-type, and is either MSGID or CORRELID. The
    type of application that is affected is identified by
    connection-type, and is either BATCH, CHIN, CICS or IMS.
    .-For batch applications connection-name contains the
      job name.
    .-For the channel initiator it contains the channel name.
    .-For CICS application it contains the region and
      transaction names.
    .-For IMS applications it contains the IMS sysid, PSTID
      and PSB name.
    
    The number of messages skipped while searching for the
    requested message, shown as num-msgs, is an indication of
    the impact of not having an index defined.
    
    Severity-
     0
    
    System action-
    Processing continues.
    
    System programmer response-
    Investigate the application to determine whether an index
    is required for the queue. Applications that get messages
    by message ID or correlation ID might encounter a
    performance degradation if an index is not defined
    and the depth of the queue is large.
    100Y
    101Y
    102Y
    103Y
    104Y
    105Y
    CSQFIDIC
    CSQFIDIE
    CSQFIDIF
    CSQFIDIK
    CSQFIDIU
    CSQFMTXC
    CSQFMTXE
    CSQFMTXF
    CSQFMTXK
    CSQFMTXU
    CSQIDPUT
    CSQIMGE3
    CSQIRECP
    CSQISTRT
    CSQIVALM
    CSQ7CBI
    CSQ7CBM
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI16027

  • Reported component name

    WMQ Z/OS V7

  • Reported component ID

    5655R3600

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-04-15

  • Closed date

    2014-07-08

  • Last modified date

    2014-09-04

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

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

    UI19408 UI19409 UI19410 UI19411 UI19412 UI19413

Modules/Macros

  • CSQFIDIC CSQFIDIE CSQFIDIF CSQFIDIK CSQFIDIU CSQFMTXC CSQFMTXE
    CSQFMTXF CSQFMTXK CSQFMTXU CSQIDPUT CSQIMGE3 CSQIRECP CSQISTRT
    CSQIVALM CSQ7CBI  CSQ7CBM
    

Fix information

  • Fixed component name

    WMQ Z/OS V7

  • Fixed component ID

    5655R3600

Applicable component levels

  • R100 PSY UI19408

       UP14/07/22 P F407

  • R101 PSY UI19409

       UP14/07/22 P F407

  • R102 PSY UI19410

       UP14/07/22 P F407

  • R103 PSY UI19411

       UP14/07/22 P F407

  • R104 PSY UI19412

       UP14/07/22 P F407

  • R105 PSY UI19413

       UP14/07/22 P F407

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 September 2014