[z/OS]

Console message monitoring

There are a number of information messages issued by the queue manager or channel initiator that should be considered particularly significant. These messages do not in themselves indicate a problem, but may be useful in tracking because they do indicate a potential issue which might need addressing.

The presence of these console messages might also indicate that a user application is putting a large number of messages to the page set, which might be a symptom of a larger problem:
  • A problem with the user application which PUTs messages, such as an uncontrolled loop.
  • A user application which GETs the messages from the queue is no longer functioning.
Distributed

Cluster error recovery for servers on distributed platforms

From IBM® WebSphere® MQ 7.1 onwards, the queue manager reruns operations that caused problems, until the problems are resolved. See Changes to cluster error recovery on servers other than z/OS® for more information.

[z/OS]

Console messages to monitor

The following list outlines messages which can potentially indicate larger problems. Determine if it is necessary to track these messages with system automation and provide appropriate documentation so any potential problems can be followed up effectively.

CSQI004I: csect-name CONSIDER INDEXING queue-name BY index-type FOR connection-type CONNECTION connection-name, num-msgs MESSAGES SKIPPED
  • The queue manager has detected an application receiving messages by message ID or correlation ID from a queue that does not have an index defined.
  • Consider establishing an index for the identified queue by altering the local queue object, queue-name, INDXTYPE attribute to have value index-type.
CSQI031I: csect-name THE NEW EXTENT OF PAGE SET psid HAS FORMATTED SUCCESSFULLY
  • Check the curdepth of the queues allocated to this page set.
  • Investigate the cause of the failure to process the messages.
.
CSQI041I: csect-name JOB jobname USER userid HAD ERROR ACCESSING PAGE SET psid
  • Determine if the page set is allocated to the queue manager.
  • Issue a DISPLAY USAGE command to determine the state of the page set.
  • Check the queue manager joblog for additional error messages.
.
CSQI045I: csect-name Log RBA has reached rba. Plan a log reset
  • Plan to stop the queue manager at a convenient time and reset the logs.
  • If your queue manager is using 6-byte log RBAs, consider converting the queue manager to use 8-byte log RBAs.
CSQI046E: csect-name Log RBA has reached rba. Perform a log reset
  • Plan to stop the queue manager at a convenient time and reset the logs.
  • If your queue manager is using 6-byte log RBAs, consider converting the queue manager to use 8-byte log RBAs.
CSQI047E: csect-name Log RBA has reached rba. Stop queue manager and reset logs
  • Stop the queue manager immediately and reset the logs.
  • If your queue manager is using 6-byte log RBAs, consider converting the queue manager to use 8-byte log RBAs.
CSQJ004I: ACTIVE LOG COPY n INACTIVE, LOG IN SINGLE MODE, ENDRBA= ttt
  • The queue manager has activated 'single' logging mode. This is often indicative of a log offload problem.
  • Issue a DISPLAY LOG command to determine your settings for duplexing of active and archive logs. This display also shows how many active logs need offload processing.
  • Check the queue manager joblog for additional error messages
CSQJ031D: csect-name, THE LOG RBA RANGE MUST BE RESET. REPLY 'Y' TO CONTINUE STARTUP OR 'N' TO SHUTDOWN
  • Stop the queue manager and reset the logs as soon as possible and reset the logs.
  • If your queue manager is using 6-byte log RBAs, consider converting the queue manager to use 8-byte log RBAs.
CSQJ032E: csect-name alert-lvl - APPROACHING END OF THE LOG RBA RANGE OF max-rba. CURRENT LOG RBA IS current-rba.
  • Plan to stop the queue manager and reset the logs as soon as possible.
  • If your queue manager is using 6-byte log RBAs, consider converting the queue manager to use 8-byte log RBAs.
CSQJ110E: LAST COPYn ACTIVE LOG DATA SET IS nnn PERCENT FULL
  • Take steps to complete other waiting offload tasks by performing a display request to determine the outstanding requests related to the log offload process. Take the necessary action to satisfy any requests, and permit offload to continue.
  • Consider whether there are sufficient active log data sets. If necessary, you can add additional log data sets dynamically by using the DEFINE LOG command.
CSQJ111A: OUT OF SPACE IN ACTIVE LOG DATA SETS
  • Perform a display request to ensure that there are no outstanding requests that are related to the log offload process. Take the necessary action to satisfy any requests, and permit offload to continue.
  • Consider whether there are sufficient active log data sets. If necessary, you can add additional log data sets dynamically by using the DEFINE LOG command.
  • If the delay was caused by the lack of a resource required for offload, the necessary resource must be made available to allow offload to complete and thus permit logging to proceed. For information about recovery from this condition, see Archive log problems.
CSQJ114I: ERROR ON ARCHIVE DATA SET, OFFLOAD CONTINUING WITH ONLY ONE ARCHIVE DATA SET BEING GENERATED
  • Check the queue manager joblog for additional error messages.
  • Make a second copy of the archive log and update your BSDS manually.
CSQJ115E: OFFLOAD FAILED, COULD NOT ALLOCATE AN ARCHIVE DATA SET
Review the error status information of message CSQJ103E or CSQJ073E. Correct the condition that caused the data set allocation error so that, on retry, the offload can take place.
CSQJ136I: UNABLE TO ALLOCATE TAPE UNIT FOR CONNECTION-ID= xxxx CORRELATION-ID= yyyyyy, m ALLOCATED n ALLOWED
  • Check the queue manager joblog for additional error messages.
.
CSQJ151I: csect-name ERROR READING RBA rrr, CONNECTION-ID= xxxx CORRELATION-ID= yyyyyy REASON CODE= ccc
  • Check the queue manager joblog for additional messages.
  • Issue a DISPLAY CONN command to determine which connection is not committing its activity.
  • Ensure the application can commit its updates.
CSQJ160I: LONG-RUNNING UOW FOUND, URID= urid CONNECTION NAME= name
  • Check the queue manager joblog for additional messages.
  • Issue a DISPLAY CONN command to determine which connection is not committing its activity.
  • Ensure the application can commit its updates.
CSQJ161I: UOW UNRESOLVED AFTER n OFFLOADS, URID= urid CONNECTION NAME= name
  • Determine if the page set is allocated to the queue manager.
  • Issue a DISPLAY USAGE command to determine the state of the page set.
  • Check the queue manager joblog for additional messages.
CSQP011E: CONNECT ERROR STATUS ret-code FOR PAGE SET psid
  • Check the curdepth of the queues allocated to this page set.
  • Investigate the cause of the failure to process messages.
CSQP013I: csect-name NEW EXTENT CREATED FOR PAGE SET psid. NEW EXTENT WILL NOW BE FORMATTED
  • Check the curdepth of the queues allocated to this page set.
  • Investigate the cause of failure to process messages.
  • Determine if queues need to be relocated to another page set.
  • If the volume is full, determine if you need to make the page set a multi volume dataset. If the page set is already multi-volume, consider adding more volumes to the storage group being used. Once more space is available retry the expansion by setting the page set EXPAND method to SYSTEM. If a retry is required, toggle EXPAND to SYSTEM and then back to your normal setting.
CSQP014E: csect-name EXPANSION FAILED FOR PAGE SET psid. FUTURE REQUESTS TO EXTEND IT WILL BE REJECTED
  • Check the curdepth of the queues allocated to this page set.
  • Investigate the cause of failure to process messages.
  • Determine if queues need to be relocated to another page set.
CSQP016E: csect-name PAGE SET psid HAS REACHED THE MAXIMUM NUMBER OF EXTENTS. IT CANNOT BE EXTENDED AGAIN
  • Check the curdepth of the queues allocated to this page set.
  • Investigate the cause of failure to process messages.
CSQP017I: csect-name EXPANSION STARTED FOR PAGE SET psid
Issue DISPLAY THREAD commands to determine the state of the Units of Work in IBM MQ.
CSQP047E: Unavailable page sets can cause problems - take action to correct this situation
  • Follow the System Programmer Response.
CSQQ008I: nn units of recovery are still in doubt in queue manager qqqq
  • Investigate the state of your dead letter queue. Ensure the dead letter queue is not PUT disabled.
  • Ensure the dead letter queue is not at the MAXMSG limit.
CSQQ113I: psb-name region-id This message cannot be processed
  • Check the CSQOUTX dataset to determine the cause of the CSQINPX failure.
  • Some commands may not be processed.
CSQX035I: csect-name Connection to queue manager qmgr-name stopping or broken, MQCC= mqcc MQRC= mqrc (mqrc-text
CSQX032I: csect-name Initialization command handler terminated
CSQX048I: csect-name Unable to convert message for name, MQCC= mqcc MQRC= mqrc (mqrc-text)
  • Check the joblog to determine the cause of the TCP/IP failure.
  • Check the TCP/IP address space for errors.
CSQX234I: csect-name Listener stopped, TRPTYPE= trptype INDISP= disposition
  • If the listener does not stop, following a STOP command, check the TCP/IP address space for errors.
  • Follow the Systems Programmer Response.
CSQX407I: csect-name Cluster queue q-name definitions inconsistent
  • Multiple cluster queues within the cluster have inconsistent values. Investigate and resolve the differences.
CSQX411I: csect-name Repository manager stopped
  • If the repository manager has stopped because of an error, check the joblog for messages.
CSQX417I: csect-name Cluster-senders remain for removed queue manager qmgr-name
  • Follow the System Programmer Response.
CSQX418I: csect-name Only one repository for cluster cluster-name
  • For increased high availability, clusters should be configured with two full repositories.
CSQX419I: csect-name No cluster-receivers for cluster cluster-name
  • Follow the System Programmer Response.
CSQX420I: csect-name No repositories for cluster cluster-name
  • Follow the System Programmer Response.
CSQX448E: csect-name Repository manager stopping because of errors. Restart in n seconds
  • Follow the System Programmer Response.
This message is put out every 600 seconds (10 minutes) until the SYSTEM.CLUSTER.COMMAND.QUEUE is enabled, by using the command:
ALTER QLOCAL(SYSTEM.CLUSTER.COMMAND.QUEUE) GET(ENABLED)

Before enabling the queue, manual intervention might be required to resolve the problem that caused the repository manager to end, prior to the first CSQX448E message being issued.