Message manager messages (CSQM...)

 

CSQM050I
csect-name Intra-group queuing agent starting, TCB=tcb-name
Explanation:

The intra-group queuing (IGQ) agent was started during the initialization of a queue manager that is in a queue-sharing group. The agent uses TCB tcb-name.

The IGQ agent handles SYSTEM.QSG.TRANSMIT.QUEUE.

Severity:

0

System Action:

Processing continues. The IGQ agent starts asynchronously.

CSQM051I
csect-name Intra-group queuing agent stopping
Explanation:

The intra-group queuing (IGQ) agent is stopping because:

  • the queue manager is stopping

  • it has retried a failing request repeatedly without success

  • it was unable to recover from an abnormal ending

Severity:

0

System Action:

The IGQ agent stops.

System Programmer Response:

If the queue manager is not stopping, investigate the cause of the error as reported in the preceding messages. To restart the IGQ agent, issue an ALTER QMGR command specifying IGQ(ENABLED).

CSQM052I
csect-name Shared channel recovery completed for qmgr-name, n channels found, p FIXSHARED, r recovered
Explanation:

The queue manager successfully recovered some shared channels that were owned by queue manager qmgr-name in the queue-sharing group when it or its channel initiator terminated abnormally. This recovery process may occur when:

n channels were found that needed recovery, of which p were originally started as FIXSHARED. The number recovered, r, may be less than n (or even 0) because other active queue managers are also recovering the channels and because FIXSHARED channels cannot be recovered by another queue manager.

See the WebSphere MQ Intercommunication manual for more information about shared channel recovery.

Severity:

0

System Action:

Processing continues.

CSQM053E
csect-name Shared channel recovery terminated, DB2 not available
Explanation:

Because DB2 is not available or no longer available, the queue manager was unable to recover some shared channels that were owned by a queue manager in the queue-sharing group when it or its channel initiator terminated abnormally. This recovery process may occur when:

Severity:

8

System Action:

The recovery process is terminated; some channels may have been recovered, while others have not.

System Programmer Response:

Use the preceding messages on the z/OS console to investigate why DB2 is not available, and resume the connection or restart DB2 if necessary. Any channels that were not recovered will be recovered when the recovery process next runs; alternatively, they can be restarted manually.

CSQM054E
csect-name Shared channel recovery terminated, error accessing DB2
Explanation:

Because there was an error in accessing DB2, the queue manager was unable to recover some shared channels that were owned by a queue manager in the queue-sharing group when it or its channel initiator terminated abnormally. This recovery process may occur when:

Severity:

8

System Action:

The recovery process is terminated; some channels may have been recovered, while others have not.

System Programmer Response:

Resolve the error reported in the preceding messages. Any channels that were not recovered will be recovered when the recovery process next runs; alternatively, they can be restarted manually.

CSQM055E
csect-name Shared channel recovery terminated, error putting command, reason=mqrc
Explanation:

Because there was an error putting a message on the system-command input queue, the queue manager was unable to recover some shared channels that were owned by a queue manager in the queue-sharing group when it or its channel initiator terminated abnormally. This recovery process may occur when:

Severity:

8

System Action:

The recovery process is terminated; some channels may have been recovered, while others have not.

System Programmer Response:

Refer to Appendix A. API completion and reason codes for information about mqrc, and resolve the error. Any channels that were not recovered will be recovered when the recovery process next runs; alternatively, they can be restarted manually.

CSQM056E
csect-name mqapi-call failed for queue q-name, reason=reason
Explanation:

The indicated MQ API call for the named queue, failed for the specified reason, which may be an MQ reason code (MQRC_) or a signal completion code (MQEC_).

Severity:

8

System Action:

If the queue is SYSTEM.ADMIN.CONFIG.EVENT or SYSTEM.ADMIN.COMMAND.EVENT, processing continues but events are not generated; message CSQM071E follows to show how many event messages have not been generated since the problem first occurred. These messages are generated on the first occurrence of the problem, and at intervals thereafter while the problem persists.

For other queues, it is the intra-group queuing (IGQ) agent that issued the call. Depending on the queue involved and the type of error, it may continue processing, retry the request at regular intervals until the error is corrected, or terminate.

System Programmer Response:

Refer to Appendix A. API completion and reason codes for information about MQ reason codes or the WebSphere MQ Application Programming Reference manual for information about signal completion codes. Correct the problem with the queue, or use the ALTER QMGR command to disable the events or the IGQ agent if the function is not required.

CSQM059E
csect-name Queue q-name has incorrect attributes
Explanation:

The named queue, used by the intra-group queuing (IGQ) agent, has incorrect attributes. For example, SYSTEM.QSG.TRANSMIT.QUEUE must have attributes USAGE(XMITQ), INDXTYPE(CORRELID), QSGDISP(SHARED).

Severity:

8

System Action:

The IGQ agent retries at regular intervals until the error is corrected.

System Programmer Response:

Redefine the queue with the correct attributes.

CSQM060E
csect-name Cluster cache is full
Explanation:

No more space is available in the cluster cache area.

Severity:

8

System Action:

The application call that resulted in the need for more space will fail with MQRC_CLUSTER_RESOURCE_ERROR. Processing continues, and existing users of clustering will be unaffected unless their actions are such as to need more cluster cache space.

System Programmer Response:

The problem may be temporary. If it persists, the queue manager must be restarted; this will cause more space to be allocated for the cluster cache area.

Consider changing the cluster cache type system parameter CLCACHE to dynamic, so that more space for the cache will be obtained automatically as required. (If you are using a cluster workload exit, ensure that it supports a dynamic cluster cache.) See the CSQ6SYSP macro in the WebSphere MQ for z/OS System Setup Guide for information about the system parameters.

CSQM061E
csect-name Cluster workload exit exit-name does not support dynamic cache
Explanation:

In response to the initialization call (using ExitReason MQXR_INIT), the cluster workload exit returned the value MQCLCT_STATIC in the ExitResponse2 field, indicating that it does not support a dynamic cluster cache.

Severity:

8

System Action:

The cluster workload exit is suppressed.

System Programmer Response:

Either change the cluster cache type system parameter CLCACHE to static, or rewrite the exit to be compatible with a dynamic cache. See the CSQ6SYSP macro in the WebSphere MQ for z/OS System Setup Guide for information about the system parameters.

CSQM064I
csect-name Intra-group queuing agent put messages to dead-letter queue
Explanation:

The intra-group queuing (IGQ) agent was unable to deliver some messages to the required destination queue, so has put them on the dead-letter queue.

Severity:

4

System Action:

Processing continues.

System Programmer Response:

Examine the contents of the dead-letter queue. Each message is contained in a structure that describes why the message was put to the queue, and to where it was originally addressed.

CSQM065E
csect-name mqapi-call failed for queue q-name, reason=reason
Explanation:

The indicated MQ API call failed for the specified reason, which is an MQ reason code (MQRC_).

Severity:

8

System Action:

It is the intra-group queuing (IGQ) agent that issued the call; it was unable to commit or backout a batch of messages for the specified reason. Depending on the type of error, it may retry the request at regular intervals until the error is corrected, or terminate.

System Programmer Response:

Refer to Appendix A. API completion and reason codes for information about MQ reason codes. Correct the problem if required.

CSQM067E
csect-name Intra-group queuing agent ended abnormally. Restarting
Explanation:

The intra-group queuing (IGQ) agent has ended abnormally because a severe error occurred, as reported in the preceding messages.

Severity:

8

System Action:

The IGQ agent attempts to restart a number of times. If it fails persistently, it terminates.

System Programmer Response:

Investigate the reason for the abnormal termination, as reported in the preceding messages.

CSQM070E
csect-name Queue q-name available again, n events not generated
Explanation:

An earlier problem with putting messages on the configuration or command event queue has been corrected. n is the number of event messages that have not been generated since the problem first occurred.

Severity:

4

System Action:

Processing continues and event messages for that queue will be generated again.

System Programmer Response:

If the queue is SYSTEM.ADMIN.CONFIG.EVENT, and complete configuration information is required, use the REFRESH QMGR TYPE(CONFIGEV) command to generate events to replace those that were not generated; specify the INCLINT parameter to cover the period when the problem was occurring.

If the queue is SYSTEM.ADMIN.COMMAND.EVENT, a limited number of the missed event messages may be recovered automatically, as reported by message CSQM072I.

CSQM071E
csect-name Queue q-name unavailable, n events not generated
Explanation:

There was an error putting a message on the configuration or command event queue, as reported in the preceding CSQM056E message; n is the number of event messages that have not been generated since the problem first occurred.

Severity:

8

System Action:

Processing continues but event messages for that queue are not generated. This message is issued on the first occurrence of the problem, and at intervals thereafter while the problem persists.

System Programmer Response:

Correct the problem with the event queue, or use the ALTER QMGR command to set the CONFIGEV or CMDEV attribute to DISABLED if events are not required.

CSQM072I
csect-name Queue q-name, n events recovered
Explanation:

An earlier problem with putting messages on the command event queue has been corrected. n event messages that were not generated have been automatically recovered and generated.

Only a limited number of the missed event messages can be recovered in this way. If n is less than the value reported in message CSQM070E, the remaining event messages are lost, and there is no way to recover them.

Severity:

0

System Action:

Processing continues.

CSQM084I
csect-name COMMAND INHIBITED DURING RESTART/TERMINATION
Explanation:

A command that will affect a recoverable object was requested either too early in queue manager startup, or too late in termination.

The usual reason for receiving this message is that some prohibited command was issued in the initialization input data set CSQINP1.

Severity:

8

System Action:

Message CSQM085I is also issued and the command is ignored.

System Programmer Response:

Wait until the queue manager is in a state where it is possible to reissue the prohibited commands. If appropriate, remove the command from CSQINP1, and place it in CSQINP2, to ensure that this problem does not reoccur.

CSQM085I
csect-name ABNORMAL COMPLETION
Explanation:

This message is issued with message CSQM084I, and indicates that the command requested has not been actioned.

Severity:

8

System Action:

The command is not actioned.

System Programmer Response:

Wait until the queue manager is in a state where it is possible to use the prohibited commands.

CSQM086E
QUEUE MANAGER CREATE ERROR, CODE=reason-code, RESTART UNSUCCESSFUL
Explanation:

During restart, the creation of the queue manager object has failed. The reason code is of the form '00D44xxx'.

Severity:

8

System Action:

The queue manager fails to restart.

System Programmer Response:

Refer to Message manager codes (X'D4') for an explanation of the reason code, and what action to take. Reissue the START QMGR command to restart the queue manager. If the error persists note this reason code, and contact your IBM support center.

CSQM090E
csect-name FAILURE REASON CODE reason-code
Explanation:

A command has failed. The reason code is of the form '00D44xxx'. This message is accompanied by one or more other more specific messages, which indicate the reason for the failure.

Severity:

8

System Action:

The command is ignored.

System Programmer Response:

See the explanations of the accompanying messages for more information. Refer to Message manager codes (X'D4') for an explanation of the reason code, and what action to take. If the reason code is not one of those listed, make a note of it and contact your IBM support center.

CSQM091E
csect-name FAILURE MQRC=mqrc
Explanation:

A command has failed. The reason code is an MQ reason code. This message is accompanied by one or more other more specific messages, which indicate the reason for the failure.

Severity:

8

System Action:

The command is ignored.

System Programmer Response:

See the explanations of the accompanying messages for more information. Refer to Appendix A. API completion and reason codes for an explanation of mqrc, and what action to take.

CSQM092I
csect-name keyword(value) VALUE INVALID OR OUT OF RANGE
Explanation:

Either:

  • A keyword was entered that takes a bounded numeric value but the value specified is outside the bounds.

  • A keyword was entered that takes a pair of numeric values defining a range, but only one value is specified or the values are not in ascending order.

Severity:

8

System Action:

The command is ignored.

System Programmer Response:

Reissue the command with the parameter specified correctly. For more information about the command, see the WebSphere MQ Script (MQSC) Command Reference manual.

CSQM093I
csect-name keyword(value) NAME CONTAINS INVALID CHARACTERS
Explanation:

A name was specified that contains one or more invalid characters. See the WebSphere MQ Script (MQSC) Command Reference manual for information about validation required for the name in question to correct this.

Severity:

8

System Action:

The command is ignored.

System Programmer Response:

Reissue the command with the correct name. For more information about the command, see the WebSphere MQ Script (MQSC) Command Reference manual.

CSQM094I
csect-name keyword(value) WAS NOT FOUND
Explanation:

A command was issued that refers to an object that does not exist. That is, no object could be found with the specified name and type (and subtype, for queues and channels) and with any disposition in the queue-sharing group.

Severity:

8

System Action:

The command is ignored.

System Programmer Response:

Check that you specified the correct name for the object, and the correct subtype (for queues and channels). If a queue-sharing group is in use, check that DB2 is available and not suspended. Define the object if necessary.

Notes:

  1. If you are dealing with a queue or channel object, an object of the same name, but of a different subtype, might already exist.

  2. Remember that the object might have recently been deleted by someone else, or from another queue manager in the queue-sharing group.

CSQM095I
csect-name keyword(value) ALREADY EXISTS
Explanation:

A DEFINE command was issued, but an object of that type with the specified name already exists, although it might not necessarily have the same subtype, or the same disposition in the queue-sharing group. (We cannot have a locally-defined object and a local copy of a group object with the same name; for local queues, we cannot have a shared queue with the same name as a queue with any other disposition.)

Severity:

8

System Action:

The command is ignored.

System Programmer Response:

Reissue the command with another name or with the REPLACE option, or use the existing object, as appropriate.

CSQM096I
csect-name keyword(value) NAME HAS INVALID LENGTH
Explanation:

A name was specified that is of an incorrect length.

Severity:

8

System Action:

The command is ignored.

System Programmer Response:

Reissue the command with a name of the correct length. For more information about the command, see the WebSphere MQ Script (MQSC) Command Reference manual.

CSQM097I
csect-name keyword(value) NAME CANNOT BE COMPLETELY BLANK
Explanation:

A name was specified that is blank. This is not allowed.

Severity:

8

System Action:

The command is ignored.

System Programmer Response:

Reissue the command with a non-blank name. For more information about the command, see the WebSphere MQ Script (MQSC) Command Reference manual.

CSQM098I
csect-name keyword(value) FIELD TOO LONG
Explanation:

Either a numeric or character parameter was specified but it is too long, or (if value is blank) a list of character parameters was specified whose total length is too long.

Severity:

8

System Action:

The command is ignored.

System Programmer Response:

Reissue the command with the correct field length. For more information about the command, see the WebSphere MQ Script (MQSC) Command Reference manual.

CSQM099I
csect-name keyword(value) NAME IN USE AS A DIFFERENT TYPE
Explanation:

An object was specified as one particular subtype, but it already exists as another subtype, although it might not necessarily have the same disposition in the queue-sharing group. (We cannot have a locally-defined object and a local copy of a group object with the same name; for local queues, we cannot have a shared queue with the same name as a queue with any other disposition.)

Severity:

8

System Action:

The command is ignored.

System Programmer Response:

Reissue the command with the correct name and subtype. For more information about the command, see the WebSphere MQ Script (MQSC) Command Reference manual.

CSQM100I
csect-name keyword(value) VALUE INVALID OR OUT OF RANGE
Explanation:

Either:

  • A keyword was entered that takes a series of character values, but the value specified is not one of them.

  • A keyword was entered that takes a series of character values, but the value specified is not valid for the particular subtype of object.

  • A keyword was entered that takes a bounded numeric value, but the value specified is outside the bounds.

  • A keyword was entered that takes a character or hexadecimal value, but the value specified is invalid for that keyword.

Severity:

8

System Action:

The command is ignored.

System Programmer Response:

Reissue the command with the parameter specified correctly. For more information about the command, see the WebSphere MQ Script (MQSC) Command Reference manual.

CSQM101I
csect-name keyword(value) IS CURRENTLY IN USE
Explanation:

The object specified is in use. This could be because:

  • It is open through the API.

  • A trigger message is presently being written to it.

  • It is in the process of being deleted.

  • When it is a storage class, there is a queue defined as using the storage class, and there are messages currently on the queue.

  • When it is a CF structure, there is a queue defined as using the CF structure, and there are messages currently on the queue or the queue is open.

  • When altering the index type of a queue, the necessary conditions regarding messages and uncommitted activity are not satisfied.

  • When altering the default transmission queue, the old queue is currently being used as a transmission queue by default.

  • Although the FORCE option was specified to overcome the object being open through the API, the object was created with a previous version of MQ.

Severity:

8

System Action:

The command is ignored.

System Programmer Response:

Either:

  • Wait until the object has been closed or deleted.
    Note:
    MCAs for receiver channels, or the intra-group queuing (IGQ) agent, can keep the destination queues open for a while even when messages are not being transmitted, and so such queues might appear to be in use.

  • Wait until all the queues that use a storage class are empty

  • Wait until the queue is empty

  • Wait until use of the queue as a default transmission queue has ended

It is not possible to use the FORCE option of the ALTER command to overcome the situations that cause this message.

For more information about the command, see the WebSphere MQ Script (MQSC) Command Reference manual.

CSQM103I
csect-name keyword(value) QSGDISP(disposition) HAS MESSAGES ASSOCIATED WITH IT
Explanation:

A local queue specified for deletion has messages associated with it, and the DELETE request did not include the PURGE option.

Severity:

8

System Action:

The command is ignored.

System Programmer Response:

Either delete the local queue when it is empty, or reissue the request specifying the PURGE option. If the queue is a local copy of a group object, issue the request specifying PURGE explicitly for the local copy; specifying PURGE on the request to delete the group object has no effect.

CSQM104I
csect-name keyword(value) FLAGGED FOR DEFERRED DELETION
Explanation:

A local dynamic queue specified on a DEFINE, ALTER, or DELETE request has been flagged for deferred deletion because it was found to be in use at the time of deletion.

Severity:

8

System Action:

The queue is no longer available to new users, and will be deleted when all existing users of it have relinquished access.

CSQM105I
csect-name 'keyword' VALUE IS SAME AS QALIAS NAME
Explanation:

An attempt was made to DEFINE or ALTER an alias queue so that the queue itself was named on the TARGQ keyword. Unless the queue is a cluster queue, this is not allowed because an alias queue can only resolve to a local or remote queue.

Severity:

8

System Action:

The command is ignored.

System Programmer Response:

Reissue the command with a different name for the TARGQ keyword.

CSQM106I
csect-name DEFXMITQ(q-name) IS NOT ALLOWED
Explanation:

The specified queue is not allowed to be used as the default transmission queue because it is reserved for use exclusively by clustering.

Severity:

8

System Action:

The command is ignored.

System Programmer Response:

Reissue the command with a different DEFXMITQ name.

CSQM107I
csect-name STGCLASS ACTIVE OR QUEUE IN USE
Explanation:

A request to ALTER or DEFINE REPLACE a local queue involving a change to the STGCLASS field is not allowed because there are messages on the queue, or other threads have the queue open.

Severity:

8

System Action:

The command is ignored.

System Programmer Response:

If there are messages on the queue, remove them before changing the storage class.

Note:
If you remove all the messages from the queue, there might be a short delay before the command can be processed successfully.

If other threads have the queue open, wait until they have closed the queue before reissuing the command.

CSQM108I
csect-name keyword(value) NOT ALLOWED, INCOMPATIBLE NAME AND TYPE
Explanation:

An attempt was made to issue a DEFINE command on a reserved object name, using an incorrect object type or subtype. The object is only allowed to be of the predetermined type listed below:

Type Object
Any Queue SYSTEM.ADMIN.ACTIVITY.QUEUE SYSTEM.ADMIN.CHANNEL.EVENT SYSTEM.ADMIN.COMMAND.EVENT SYSTEM.ADMIN.CONFIG.EVENT SYSTEM.ADMIN.PERFM.EVENT SYSTEM.ADMIN.QMGR.EVENT SYSTEM.ADMIN.TRACE.ROUTE.QUEUE
Alias queue SYSTEM.DEFAULT.ALIAS.QUEUE
Alias or local queue SYSTEM.ADMIN.COMMAND.QUEUE SYSTEM.COMMAND.INPUT
Local queue SYSTEM.CHANNEL.INITQ SYSTEM.CHANNEL.SYNCQ SYSTEM.CLUSTER.COMMAND.QUEUE SYSTEM.CLUSTER.REPOSITORY.QUEUE SYSTEM.CLUSTER.TRANSMIT.QUEUE SYSTEM.DEFAULT.LOCAL.QUEUE SYSTEM.QSG.CHANNEL.SYNCQ SYSTEM.QSG.TRANSMIT.QUEUE
Model queue SYSTEM.COMMAND.REPLY.MODEL SYSTEM.DEFAULT.MODEL.QUEUE SYSTEM.MQEXPLORER.REPLY.MODEL
Remote queue SYSTEM.DEFAULT.REMOTE.QUEUE
Cluster-sender channel SYSTEM.DEF.CLUSSDR
Cluster-receiver channel SYSTEM.DEF.CLUSRCVR
Sender channel SYSTEM.DEF.SENDER
Server channel SYSTEM.DEF.SERVER
Receiver channel SYSTEM.DEF.RECEIVER
Requester channel SYSTEM.DEF.REQUESTER
Client-connection channel SYSTEM.DEF.CLNTCONN
Server-connection channel SYSTEM.ADMIN.SVRCONN SYSTEM.DEF.SVRCONN
Authentication information SYSTEM.DEFAULT.AUTHINFO.CRLLDAP
Namelist SYSTEM.DEFAULT.NAMELIST
Process SYSTEM.DEFAULT.PROCESS
Storage class SYSTEMST
Severity:

8

System Action:

The command is ignored.

System Programmer Response:

Ensure that reserved objects are defined with the correct object type or subtype.

CSQM109E
csect-name DYNAMIC QUEUE value NOT DELETED, REASON=mqrc
Explanation:

A dynamic queue could not be deleted during normal close processing, thread termination, or the end of queue manager restart, because an error occurred whilst attempting to delete it. mqrc gives the reason code for the error.

Severity:

8

System Action:

The named dynamic queue is not deleted.

System Programmer Response:

Refer to Appendix A. API completion and reason codes for information about the reason code to determine why the queue could not be deleted, and take the appropriate action as necessary. The most likely reason codes are:

  • MQRC_OBJECT_IN_USE

  • MQRC_PAGESET_ERROR

  • MQRC_Q_NOT_EMPTY

CSQM110I
csect-name keyword(value) QSGDISP(disposition) HAS INCOMPLETE UNITS OF RECOVERY
Explanation:

A command was issued that refers to a local queue that has incomplete units of recovery outstanding for it.

Severity:

8

System Action:

The command is ignored.

System Programmer Response:

Wait until all units of recovery for this queue are complete before attempting to issue the command again.

CSQM111E
csect-name COULD NOT PUT TO THE DEAD QUEUE, REASON=mqrc
Explanation:

An attempt to put a message to the dead letter queue was unsuccessful. mqrc gives the reason code for the error.

Severity:

4

System Action:

Processing continues.

System Programmer Response:

Refer to Appendix A. API completion and reason codes for information about mqrc to determine the cause of the problem.

CSQM112E
csect-name ERROR ACCESSING keyword(value)
Explanation:

While processing a command for an object, object information could not be accessed. This may be because of an error on page set zero, or in the coupling facility information, or because a coupling facility structure has failed, or because DB2 is not available or is suspended. This message is issued with message CSQM090E or CSQM091E, which include a reason code that gives more information about the error.

Severity:

4

System Action:

The command is ignored.

System Programmer Response:

Check for error messages on the console log that might relate to the problem. Verify that page set zero is set up correctly; refer to the WebSphere MQ for z/OS System Administration Guide for information about this. If a queue-sharing group is in use, check whether the coupling facility structure has failed and check that DB2 is available and not suspended. If the accompanying message is CSQM091E, refer to Appendix A. API completion and reason codes for an explanation of the mqrc in that message, and what action to take.

CSQM113E
csect-name NO SPACE FOR keyword(value) QSGDISP(disposition)
Explanation:

A command failed because page set zero is full, or because the application structure is full, or because no more application structures are available in the coupling facility (the limit is 63).

Severity:

8

System Action:

The command is not actioned.

System Programmer Response:

Do one of the following, depending on the cause of the error:

  • Increase the size of page set zero or the application structure. Refer to the WebSphere MQ for z/OS System Administration Guide for information about how to do this.

  • Reduce the number of application structures you are using.

CSQM114E
csect-name keyword(value) EXCEEDED LOCAL QUEUE LIMIT
Explanation:

A command failed because no more local queues could be defined. There is an implementation limit of 524 287 for the total number of local queues that can exist. For shared queues, there is a limit of 512 queues in a single coupling facility structure.

Severity:

8

System Action:

The command is not actioned.

System Programmer Response:

Delete any existing queues that are no longer required.

CSQM115I
csect-name keyword(value) IS CURRENTLY IN USE, ALTER WITH FORCE NEEDED
Explanation:

The object specified is in use. This could be because:

  • It is open through the API.

  • When altering the USAGE attribute of a local queue, there are messages currently on the queue.

  • When altering the default transmission queue, the old queue is currently being used as a transmission queue by default.

Severity:

8

System Action:

The command is ignored.

System Programmer Response:

Either:

  • Wait until the object has been closed or deleted.
    Note:
    MCAs for receiver channels, or the intra-group queuing (IGQ) agent, can keep the destination queues open for a while even when messages are not being transmitted, and so such queues might appear to be in use.

  • Wait until the queue is emptied.

  • Wait until use of the queue as a default transmission queue has ended.

  • Use the ALTER command with the FORCE option.
    Note:
    Any subsequent API calls referencing the object will fail with a reason code of MQRC_OBJECT_CHANGED.

For more information about the command, see the WebSphere MQ Script (MQSC) Command Reference manual.

CSQM117E
csect-name ERROR ACCESSING keyword(value) QSGDISP(disposition)
Explanation:

While processing a command for an object, object information could not be accessed. This may be because of an error on page set zero, or in the coupling facility information, or because a coupling facility structure has failed, or because DB2 is not available or is suspended. This message is issued with message CSQM090E or CSQM091E, which include a reason code that gives more information about the error.

Severity:

4

System Action:

The command is ignored.

System Programmer Response:

Check for error messages on the console log that might relate to the problem. If disposition is QMGR, COPY, or PRIVATE, verify that page set zero is set up correctly; refer to the WebSphere MQ for z/OS System Administration Guide for information about this. If disposition is GROUP or SHARED, check whether the coupling facility structure has failed and check that DB2 is available and is not suspended. If the accompanying message is CSQM091E, refer to Appendix A. API completion and reason codes for an explanation of the mqrc in that message, and what action to take.

CSQM118I
csect-name keyword(value) QSGDISP(disposition) LEVEL IS INCOMPATIBLE
Explanation:

The definition level of the specified object is incompatible with that of the queue manager or other members of the queue-sharing group.

System Action:

Processing of the command is terminated.

System Programmer Response:

See the WebSphere MQ for z/OS Concepts and Planning Guide and the WebSphere MQ for z/OS System Setup Guide for information about migration and compatibility between releases.

CSQM119I
csect-name keyword(value) LEVEL IS INCOMPATIBLE
Explanation:

The definition level of the specified object is incompatible with that of the queue manager or other members of the queue-sharing group.

System Action:

Processing of the command is terminated.

System Programmer Response:

See the WebSphere MQ for z/OS Concepts and Planning Guide and the WebSphere MQ for z/OS System Setup Guide for information about migration and compatibility between releases.

CSQM120I
csect-name keyword(value) NOT ALLOWED FOR SHARED QUEUE
Explanation:

The specified value for the object name or attribute is not allowed for a local queue whose disposition is shared or a model queue used to create a dynamic queue that is shared.

Severity:

8

System Action:

Processing of the command is terminated.

System Programmer Response:

Reissue the command correctly.

CSQM121I
csect-name keyword(value) NOT ALLOWED, NOT IN QUEUE-SHARING GROUP
Explanation:

The specified value for the attribute requires a queue-sharing group, but the queue manager is not in a group.

Severity:

8

System Action:

Processing of the command is terminated.

System Programmer Response:

Reissue the command correctly.

CSQM122I
csect-name 'verb-name object' COMPLETED FOR QSGDISP(disposition)
Explanation:

Processing for the specified command that refers to an object with the indicated disposition has completed successfully.

Severity:

0

System Action:

A command is generated specifying CMDSCOPE(*) to perform further processing on all queue managers in the queue-sharing group. For example, if disposition is GROUP, the corresponding processing must be performed for local copies of the group object.

CSQM123I
csect-name 'keyword' VALUE CANNOT BE CHANGED
Explanation:

The value for the specified attribute cannot be changed.

Severity:

8

System Action:

Processing of the command is terminated.

System Programmer Response:

To change the attribute, the object must be deleted and then redefined with the new value.

CSQM124I
csect-name keyword(value) ALLOWED ONLY WITH QSGDISP(disposition)
Explanation:

The specified value for the attribute is allowed only for an object that has the indicated disposition.

Severity:

8

System Action:

Processing of the command is terminated.

System Programmer Response:

Reissue the command correctly.

CSQM125I
csect-name keyword(value) QSGDISP(disposition) WAS NOT FOUND
Explanation:

A command was issued that refers to an object that does not exist. That is, no object could be found with the specified name and type (and subtype, for queues and channels) and disposition in the queue-sharing group.

Severity:

8

System Action:

The command is ignored.

System Programmer Response:

Check that you specified the correct name for the object, and the correct subtype (for queues and channels) or channel definition table (for deleting channels). If disposition is GROUP or SHARED, check that DB2 is available and is not suspended. Define the object if necessary.

Notes:

  1. An object of the same name and type, but of a different disposition, might already exist.

  2. If you are dealing with a queue or channel object, an object of the same name, but of a different subtype, might already exist.

  3. Remember that the object might have recently been deleted by someone else, or from another queue manager in the queue-sharing group.

CSQM126I
csect-name 'keyword' ONLY APPLICABLE TO LU62 PROTOCOL
Explanation:

The named keyword can only be specified when TRPTYPE(LU62) is specified.

Severity:

8

System Action:

Processing of the command is terminated.

System Programmer Response:

Reissue the command without the named keyword.

CSQM127I
csect-name keyword(value) IS EMPTY OR WRONG TYPE
Explanation:

A namelist used to specify a list of clusters has no names in it or does not have type CLUSTER or NONE.

Severity:

8

System Action:

Processing of the command is terminated.

System Programmer Response:

Reissue the command specifying a namelist that is not empty and has type CLUSTER or NONE.

CSQM128E
csect-name MQPUT FAILED FOR QUEUE q-name, REASON=mqrc
Explanation:

During the processing of a command, an attempt to put a message to the named queue failed for the specified reason.

Severity:

8

System Action:

In general, the command is not actioned. If the command was REFRESH QMGR for configuration events, it may be partially completed as indicated by the preceding CSQM169I messages.

System Programmer Response:

Refer to Appendix A. API completion and reason codes for information about mqrc. If mqrc is 2003, the message could not be committed.

CSQM129I
csect-name keyword(value) HAS WRONG CHANNEL TYPE
Explanation:

The command (or the command with the particular disposition) cannot be used with the named channel because it cannot be used for channels of that type.

Severity:

8

System Action:

The command is not actioned.

System Programmer Response:

Check that the correct channel name and disposition was specified on the command. For more information about the command, see the WebSphere MQ Script (MQSC) Command Reference manual.

CSQM130I
csect-name CLUSTER REQUEST QUEUED
Explanation:

Initial processing for a command completed successfully. The command requires further action by the cluster repository manager, for which a request was queued.

This message is followed by message CSQ9022I to indicate that the command has completed successfully, in that a request has been sent. It does not indicate that the cluster request has completed successfully. Such requests are processed asynchronously by the cluster repository manager; any errors are reported to the z/OS console, not to the command issuer.

Severity:

0

System Action:

A request was queued for the cluster repository manager, which will process it asynchronously.

CSQM131I
csect-name CHANNEL INITIATOR NOT ACTIVE, CLUSTER AND CHANNEL COMMANDS INHIBITED
Explanation:

A command was issued that required the channel initiator to be started.

Severity:

8

System Action:

The command is not actioned.

System Programmer Response:

Issue the START CHINIT command to start the channel initiator, and reissue the command.

CSQM132I
csect-name CHANNEL INITIATOR ALREADY ACTIVE
Explanation:

The START CHINIT command was issued but the channel initiator is already active.

Severity:

8

System Action:

The command is not actioned.

CSQM133I
csect-name UNABLE TO START CHANNEL INITIATOR
Explanation:

A START CHINIT command was issued but the channel initiator could not be started.

This could be for one of the following reasons:

  • The system did not allow the channel initiator address space to be created at this time due to a heavy system workload

  • There was not enough storage to start the channel initiator address space

  • The system tried to obtain more address spaces than the maximum number supported

  • The queue manager was quiescing or shutting down.

Severity:

8

System Action:

The command is not actioned.

System Programmer Response:

Reissue the command when the system workload is reduced and when the queue manager is not shutting down.

CSQM134I
csect-name command keyword(value) COMMAND ACCEPTED
Explanation:

Initial processing for a command has completed successfully. The command requires further action by the channel initiator, for which a request has been queued. Messages reporting the success or otherwise of the action will be sent to the command issuer subsequently.

Severity:

0

System Action:

A request was queued for the channel initiator. Further messages will be produced when the command has been completed.

CSQM135I
csect-name NO CHANNEL INITIATOR AVAILABLE
Explanation:

A command was issued for a shared channel, but there was no suitable channel initiator available for any active queue manager in the queue-sharing group. This could be because:

  • no channel initiators are running

  • the channel initiators that are running are too busy to allow any channel, or a channel of the particular type, to be started

Severity:

8

System Action:

The command is not actioned.

System Programmer Response:

Start a new channel initiator (on an active queue manager where there is no channel initiator running), or try again when there are fewer channels running.

CSQM136E
COMMAND NOT ALLOWED, COMMAND SERVER UNAVAILABLE
Explanation:

A command for the channel initiator was entered, but the command server is not running and not enabled so the command cannot be processed.

System Action:

The command is not actioned.

System Programmer Response:

Use the START CMDSERV command to start the command server, and reissue the command.

CSQM137I
csect-name command keyword COMMAND ACCEPTED
Explanation:

Initial processing for a command has completed successfully. The command requires further action by the channel initiator, for which a request has been queued. Messages reporting the success or otherwise of the action will be sent to the command issuer subsequently.

Severity:

0

System Action:

A request was queued for the channel initiator. Further messages will be produced when the command has been completed.

CSQM138I
csect-name CHANNEL INITIATOR STARTING
Explanation:

A START CHINIT command was issued and the channel initiator address space has been started successfully.

Severity:

0

System Action:

Further messages will be produced when the channel initiator itself has started.

CSQM139I
csect-name INDXTYPE(MSGTOKEN) NOT ALLOWED FOR TEMPORARY DYNAMIC QUEUE
Explanation:

An attempt was made to define or alter a temporary-dynamic queue from which messages could be retrieved using message tokens. This combination is not allowed.

Severity:

8

System Action:

Processing of the command is terminated.

System Programmer Response:

Reissue the command with correct values.

CSQM140I
csect-name 'keyword' NOT ALLOWED WITH TRPTYPE(value)
Explanation:

The named keyword cannot be used on a START LISTENER command for the transport type shown.

Severity:

8

System Action:

The command is not actioned.

System Programmer Response:

Reissue the command with the correct keywords.

CSQM141I
csect-name 'LUNAME' REQUIRED WITH TRPTYPE(LU62)
Explanation:

A START LISTENER command was issued specifying TRPTYPE(LU62) but without the LUNAME keyword. The LUNAME keyword is required with TRPTYPE(LU62).

Severity:

8

System Action:

The command is not actioned.

System Programmer Response:

Reissue the command with the correct keywords.

CSQM142I
csect-name CLUSTER(cluster-name) REPOSITORY IS NOT ON THIS QUEUE MANAGER
Explanation:

A RESET CLUSTER command was issued, but the queue manager does not provide a full repository management service for the specified cluster. That is, the REPOS attribute of the queue manager is not cluster-name, or the namelist specified by the REPOSNL attribute of the queue manager does not contain cluster-name or is not of type CLUSTER or NONE.

Severity:

8

System Action:

Processing of the command is terminated.

System Programmer Response:

Reissue the command with the correct values or on the correct queue manager.

CSQM144I
csect-name keyword(value) CANNOT BE A CLUSTER QUEUE
Explanation:

An attempt was made to define or alter a queue to make it part of a cluster. This is not allowed if the queue is dynamic or is one of the following reserved queues:

Severity:

8

System Action:

Processing of the command is terminated.

System Programmer Response:

Reissue the command with the correct values.

CSQM145I
csect-name 'keyword' VALUE REQUIRED FOR SHARED QUEUE
Explanation:

A non-blank value must be specified for the named keyword for a local queue whose disposition is shared or a model queue used to create a dynamic queue that is shared.

Severity:

8

System Action:

Processing of the command is terminated.

System Programmer Response:

Reissue the command with a value for the keyword added.

CSQM146I
csect-name keyword(value) VALUE IS REPEATED
Explanation:

A keyword was entered that takes a list of values, and the named value appears more than once in the list.

Severity:

8

System Action:

The command is ignored.

System Programmer Response:

Reissue the command with the parameter specified correctly. For more information about the command, see the WebSphere MQ Script (MQSC) Command Reference manual.

CSQM147I
csect-name 'keyword1' AND 'keyword2' VALUES MUST BOTH BE BLANK OR NON-BLANK
Explanation:

An attempt was made to define or alter an object so that it had a blank value for one of the specified keywords and a non-blank value for the other. Both of those values must either be blank or non-blank.

Severity:

8

System Action:

Processing of the command is terminated.

System Programmer Response:

Reissue the command with correct values.

CSQM148I
csect-name 'keyword' NOT ALLOWED WITH TYPE 'value'
Explanation:

The named keyword cannot be specified for queues or channels of the type shown.

Severity:

8

System Action:

Processing of the command is terminated.

System Programmer Response:

Reissue the command without the named keyword.

CSQM149I
csect-name 'keyword' REQUIRED WITH TYPE 'value'
Explanation:

The named keyword was not specified but is required for queues or channels of the type shown.

Severity:

8

System Action:

Processing of the command is terminated.

System Programmer Response:

Reissue the command with the named keyword added.

CSQM150I
csect-name 'keyword1' AND 'keyword2' VALUES ARE INCOMPATIBLE
Explanation:

An attempt was made to define or alter an object so that it had incompatible values for the specified keywords.

Severity:

8

System Action:

Processing of the command is terminated.

System Programmer Response:

Reissue the command with correct values. For information about the restrictions on the values for the keywords, see the WebSphere MQ Script (MQSC) Command Reference manual.

CSQM151I
csect-name 'keyword1' AND 'keyword2' VALUES CANNOT BOTH BE NON-BLANK
Explanation:

An attempt was made to define or alter an object so that it had non-blank values for both of the specified keywords. At most one of those values can be non-blank.

Severity:

8

System Action:

Processing of the command is terminated.

System Programmer Response:

Reissue the command with correct values.

CSQM152I
csect-name USAGE(XMITQ) NOT ALLOWED FOR CLUSTER QUEUE
Explanation:

An attempt was made to define or alter a queue so that it was both a transmission queue and in a cluster. This is not allowed.

Severity:

8

System Action:

Processing of the command is terminated.

System Programmer Response:

Reissue the command with correct values.

CSQM153E
csect-name DB2 NOT AVAILABLE
Explanation:

Because DB2 is not available or no longer available, the queue manager cannot handle the command for a CF structure or shared channel.

Severity:

8

System Action:

Processing of the command is terminated.

System Programmer Response:

Use the preceding messages on the z/OS console to investigate why DB2 is not available, and resume the connection or restart DB2 if necessary.

CSQM154E
csect-name ERROR ACCESSING DB2
Explanation:

Because there was an error in accessing DB2, the queue manager cannot handle the command for a CF structure or shared channel.

Severity:

8

System Action:

Processing of the command is terminated.

System Programmer Response:

Resolve the error reported in the preceding messages.

CSQM155I
csect-name STATUS(STOPPED) NOT ALLOWED WITH QMNAME OR CONNAME
Explanation:

An attempt was made to stop a channel using STATUS(STOPPED), but a queue manager name or connection name was also specified. This is not allowed.

Severity:

8

System Action:

Processing of the command is terminated.

System Programmer Response:

Reissue the command with correct values.

CSQM156I
csect-name INDXTYPE(GROUPID) NOT ALLOWED FOR keyword(value)
Explanation:

An attempt was made to define or alter a queue with a reserved name so that it had an index type of GROUPID. This is not allowed.

Severity:

8

System Action:

Processing of the command is terminated.

System Programmer Response:

Reissue the command with correct values.

CSQM157E
csect-name NO SPACE FOR keyword(value)
Explanation:

An MQ DEFINE CFSTRUCT command failed because no more application structures are available in the coupling facility (the limit is 63).

Severity:

8

System Action:

The command is not actioned.

System Programmer Response:

Reduce the number of application structures you are using.

CSQM158I
csect-name RECOVER(YES) NOT ALLOWED WITH CFLEVEL(value)
Explanation:

An attempt was made to define or alter a CF structure to support recovery, but the level of the CF structure was less than 3. This is not allowed.

Severity:

8

System Action:

Processing of the command is terminated.

System Programmer Response:

Reissue the command with correct values. We cannot alter the level of a CF structure; delete the structure and then redefine it.

CSQM159I
csect-name verb-name object(obj-name) NOT ALLOWED, INCOMPATIBLE QUEUE MANAGER CMDLEVELS
Explanation:

An attempt was made to alter the CF level of a CF structure, or to delete the structure. This action requires that all queue managers in the queue-sharing group must have a command level of at least 530. Some of the queue managers have a lower level.

Severity:

8

System Action:

Processing of the command is terminated.

System Programmer Response:

Ensure all the queue managers in the queue-sharing group have the appropriate command level. For information about restrictions on the command, see the WebSphere MQ Script (MQSC) Command Reference manual.

CSQM160I
csect-name keyword(value) IS NOT UNIQUE
Explanation:

A command was issued that refers to an object that exists with more that one disposition in the queue-sharing group, so the object to be used cannot be determined.

Severity:

8

System Action:

The command is not executed.

System Programmer Response:

Delete one of the objects.

CSQM161I
csect-name QUEUE ATTRIBUTES ARE INCOMPATIBLE
Explanation:

A MOVE QLOCAL command was issued, but the queues involved have different values for one or more of these attributes: DEFTYPE, HARDENBO, INDXTYPE, USAGE. Messages cannot be moved safely if these attributes differ.

Severity:

8

System Action:

The command is not executed.

System Programmer Response:

Check that the queue names have been entered correctly. Change the queue attributes as necessary.

CSQM162I
csect-name keyword(value) MAXDEPTH IS TOO SMALL
Explanation:

A MOVE QLOCAL command was issued, but the MAXDEPTH attribute value for the target queue is too small to allow all the messages to be moved.

Severity:

8

System Action:

The command is not executed.

System Programmer Response:

Change the MAXDEPTH value for the queue.

CSQM163I
csect-name ERROR USING keyword(value), REASON=mqrc
Explanation:

During the processing of a MOVE QLOCAL command, an attempt to open the named queue or to get or put a message for it failed for the specified reason. For example, a put to the target queue will fail if a message is too long.

Severity:

8

System Action:

The command stops processing. If some messages have already been moved and committed, they will remain on the target queue; the rest of the messages will not be moved.

System Programmer Response:

Refer to Appendix A. API completion and reason codes for information about mqrc, and take the appropriate action to resolve the problem.

CSQM164I
csect-name keyword(value) HAS MESSAGES ASSOCIATED WITH IT
Explanation:

A MOVE QLOCAL command was issued specifying TYPE(MOVE), the target queue already has messages associated with it.

Severity:

8

System Action:

The command is not executed.

System Programmer Response:

Check that the queue name was entered correctly. Determine if it is safe to add messages to the queue, then reissue the command using the TYPE(ADD) option.

CSQM165I
csect-name n MESSAGES MOVED
Explanation:

A MOVE QLOCAL command was issued, and moved the indicated number of messages.

If the command completed successfully and moved all the messages on the queue, this confirms the number moved. If an error occurred while moving the messages, this shows how many messages were successfully moved to the target queue and committed.

Severity:

0

System Action:

Processing continues.

System Programmer Response:

If the command did not complete successfully, as shown by the following CSQ9023E message, investigate the problem reported in the preceding messages.

CSQM166I
csect-name keyword(value) NOT AUTHORIZED
Explanation:

You do not have proper authorization to use the command for the specified object.

Severity:

8

System Action:

The command is not executed for that object.

System Programmer Response:

Check that the object name was entered correctly. If required, arrange for someone who is authorized to use the object to issue the command for you, or get the necessary authority granted to you.

CSQM167I
csect-name PERFORMANCE EVENTS DISABLED
Explanation:

A command was issued that required performance events to be enabled.

Severity:

8

System Action:

The command is not executed.

System Programmer Response:

Use the ALTER QMGR command to set the PERFMEV attribute to ENABLED if performance events are required.

CSQM168I
csect-name CONFIGURATION EVENTS DISABLED
Explanation:

A command was issued that required configuration events to be enabled.

Severity:

8

System Action:

The command is not executed.

System Programmer Response:

Use the ALTER QMGR command to set the CONFIGEV attribute to ENABLED if configuration events are required.

CSQM169I
csect-name object-type OBJECTS: m FOUND, n EVENTS GENERATED
Explanation:

A REFRESH QMGR command was issued for configuration events. m objects of the indicated type were found that matched the specified selection criteria (such as name or time of alteration), and n event messages were generated. The number of event messages may be less than the number of objects found because certain objects may be excluded, such as temporary dynamic queues or objects in the process of being deleted. It may also be less than the number of objects found if there was a problem with the event queue.

Severity:

0

System Action:

Processing continues.

System Programmer Response:

If n is less than m, but message CSQ9022I follows these messages to indicate that the command completed successfully, no action is needed. Otherwise, investigate the problem with the event queue as reported in the preceding messages.

CSQM170I
csect-name REFRESHING CONFIGURATION EVENTS SINCE date time
Explanation:

A REFRESH QMGR command was issued for configuration events specifying a refresh interval with the INCLINT keyword. Event messages will be generated for all objects with an alteration date and time later than date time (provided they match any other specified selection criteria, such as name or type). However, event messages will not be generated for objects deleted after that time.

Severity:

0

CSQM171I
csect-name CONFIGURATION EVENTS REFRESH NEEDED
Explanation:

An ALTER QMGR command was issued that enables configuration events. Event messages need to be generated to ensure that the configuration information is complete and up-to-date.

Severity:

0

System Action:

Processing continues.

System Programmer Response:

If complete configuration information is required, do one of the following, as appropriate:

  • If this is the first time that configuration events have been enabled, use the REFRESH QMGR TYPE(CONFIGEV) command to generate configuration events for all objects. If you have many objects, it may be preferable to use several such commands each with a different selection of objects, but such that all are included.

  • Otherwise, use the REFRESH QMGR TYPE(CONFIGEV) command to generate events to replace those that were not generated while configuration events were disabled; specify the INCLINT parameter to cover this period.

CSQM172I
csect-name 'keyword' NOT ALLOWED WITH TYPE(value)
Explanation:

The named keyword cannot be specified with the TYPE value shown.

Severity:

8

System Action:

Processing of the command is terminated.

System Programmer Response:

Reissue the command without the named keyword.

CSQM173I
csect-name EXPIRED MESSAGE SCAN REQUESTED FOR m QUEUES
Explanation:

A REFRESH QMGR command was issued for expired message scanning. m queues were found that matched the specified selection criteria.

Severity:

0

System Action:

Processing continues.

CSQM181I
csect-name INSUFFICIENT STORAGE TO COMPLETE COMMAND
Explanation:

There was insufficient storage available to complete processing for the command.

Severity:

8

System Action:

The command terminates. Any processing already completed may be retained or backed out.

System Programmer Response:

Refer to the accompanying messages to determine what processing has been done. Retry the command, if appropriate, when your queue manager is less busy. If the problem persists, you might need to increase the region size used by your queue manager, or you might need to reduce the number of jobs running in your system.

CSQM201I
csect-name verb-name obj-type DETAILS
Explanation:

This message is the response to a command that displays attributes or other information about objects, when that command was entered from either the console, or the command server initialization server. It shows the attributes requested for obj-type, as follows: 

 obj-type(name)
 attribute-value
 attribute-value

  ·
  ·
  ·

  END obj-type DETAILS

csect-name might include the command prefix (CPF), depending on how the command was entered.

Exceptionally, the last line might be: 

 obj-type TERMINATED WITH MAX LINES

if the number of lines allowed in a multiple line WTO to be issued on the console (255) was exceeded. This figure includes the first and last lines of the display. The only object that might cause this message is namelist because displaying a complete namelist would require 263 lines in total. (This only occurs when the command was issued from the console.)

Severity:

0

CSQM293I
csect-name m obj-type FOUND MATCHING REQUEST CRITERIA
Explanation:

A command that displays attributes or other information about objects has been issued. m objects were found that matched the specified selection criteria.

System Action:

For each object found, a message follows giving its details.

Severity:

0

CSQM294I
csect-name CANNOT GET INFORMATION FROM DB2
Explanation:

While processing a command that displays attributes or other information about objects with a disposition of GROUP or SHARED, information could not be obtained from DB2. This may be because DB2 is not available or no longer available, or because it is suspended, or because there was an error in accessing DB2, or because a DB2 table was temporarily locked.

Severity:

8

System Action:

Information about objects with a disposition of GROUP or SHARED is not displayed, so the information displayed may therefore be incomplete.

System Programmer Response:

Refer to the console log for messages giving more information about the error.

CSQM295I
csect-name UNEXPECTED ERROR DURING DISPLAY
Explanation:

A severe error occurred while processing a command that displays attributes or other information about objects.

Severity:

8

System Action:

The command is terminated.

System Programmer Response:

Refer to the console log for messages giving more information about the error.

CSQM297I
csect-name NO obj-type FOUND MATCHING REQUEST CRITERIA
Explanation:

A command that displays attributes or other information about objects found that there are no objects that match the specified name and satisfy any other criteria requested (such as subtype or disposition in a queue-sharing group).

Severity:

0

CSQM298I
csect-name TOTAL MESSAGE LENGTH ALLOWED ON CONSOLE EXCEEDED
Explanation:

The total message length for the command allowed on the console (32 K) was exceeded.

Severity:

8

System Action:

The command is actioned, but the display of the command is terminated.

System Programmer Response:

This error occurs if a command that displays attributes or other information about objects is entered using a generic name (for example, DIS Q(*) ALL), and the total amount of data to be displayed exceeds 32 K. To avoid this problem, try to be more selective about the information requested (for example, DIS Q(PAY*) ALL).

CSQM299I
csect-name INSUFFICIENT STORAGE TO COMPLETE DISPLAY
Explanation:

There was insufficient storage available to complete processing of a command that displays attributes or other information about objects.

Severity:

8

System Action:

The command is actioned, but the display of the information is terminated.

System Programmer Response:

If this error occurs when a generic name is used in the command (for example, DIS Q(*) ALL), try to be more selective about the information requested (for example, DIS Q(PAY*) ALL). If the problem persists, you might need to increase the region size used by your queue manager or channel initiator, or you might need to reduce the number of jobs running in your system.

CSQM4nnI
object details
Explanation:

This message consists of the entire object or object status details formatted for use by applications. It is issued in response to commands entered from the command server. Message CSQ9022I follows this message.

The message number depends on the object or object status type, as follows:

Number Object or status type
CSQM400I Storage class object
CSQM401I Local queue object
CSQM402I Model queue object
CSQM403I Alias queue object
CSQM406I Remote queue object
CSQM407I Namelist object
CSQM408I Process object
CSQM409I Queue manager object
CSQM410I Sender channel object
CSQM411I Server channel object
CSQM412I Receiver channel object
CSQM413I Requester channel object
CSQM415I Server-connection channel object
CSQM416I Client-connection channel object
CSQM417I Cluster-receiver channel object
CSQM418I Cluster-sender channel object
CSQM420I Sender channel status
CSQM421I Server channel status
CSQM422I Receiver channel status
CSQM423I Requester channel status
CSQM425I Server-connection channel status
CSQM427I Cluster-receiver channel status
CSQM428I Cluster-sender channel status
CSQM430I CF structure object
CSQM431I Cluster queue object
CSQM437I Authentication information object
CSQM439I Cluster queue manager object
CSQM440I CF structure status
CSQM441I Local queue status
CSQM442I Connection information
CSQM451I Local queue statistics
Severity:

0

CSQM999E
csect-name UNRECOGNIZED RETURN CODE ret-code FOR 'keyword'
Explanation:

An unexpected return code was issued from a command, relating to the named keyword.

Severity:

8

System Action:

The command is ignored.

System Programmer Response:

Note the return code ret-code (which is shown in hexadecimal) and contact your IBM support center.