Message manager messages (CSQM...)

CSQM001E

csect-name MSTR user ID cannot invoke USS callable services

Severity

Explanation

The IBM MQ queue manager MSTR address space is running under a user ID that has not been configured with authority to execute callable Unix System Services (USS).

In RACF, the user ID requires an OMVS segment with a UID assigned.

System action

This message is issued and the process of Unix System Services calls, for reverse DNS host name lookup, are disabled in the MSTR address space.

System programmer response

Refer to Plan your z/OS UNIX or UNIX System Services environment, where queue manager MSTR and CHIN address spaces require user IDs with OMVS segments defined with a valid UID.

Correct the configuration of the queue manager MSTR address space user ID and restart the queue manager.

CSQM050I

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

Severity

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.

System action

Processing continues. The IGQ agent starts asynchronously.

CSQM051I

csect-name Intra-group queuing agent stopping

Severity

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

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

Severity

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 might occur when:

another queue manager or its channel initiator terminates abnormally
the channel initiator is started, for channels that were owned by other queue managers
the channel initiator is started, for channels that were owned by itself

n channels were found that needed recovery, of which p were originally started as FIXSHARED. The number recovered, r, might 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.

For more information about shared channel recovery, see Shared channels.

System action

Processing continues.

CSQM053E

csect-name Shared channel recovery terminated, DB2 not available

Severity

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 might occur when:

another queue manager or its channel initiator terminates abnormally
the channel initiator is started, for channels that were owned by other queue managers
the channel initiator is started, for channels that were owned by itself

System action

The recovery process is terminated; some channels might 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

Severity

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 might occur when:

another queue manager or its channel initiator terminates abnormally
the channel initiator is started, for channels that were owned by other queue managers
the channel initiator is started, for channels that were owned by itself

System action

The recovery process is terminated; some channels might 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, MQRC=mqrc (mqrc-text)

Severity

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 might occur when:

another queue manager or its channel initiator terminates abnormally
the channel initiator is started, for channels that were owned by other queue managers
the channel initiator is started, for channels that were owned by itself

System action

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

System programmer response

Refer to API completion and reason codes for information about mqrc (mqrc-text provides the MQRC in textual form), 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, MQRC=mqrc (mqrc-text)

Severity

Explanation

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

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.

Depending on the queue involved and the type of error, it might continue processing, try the request again at regular intervals until the error is corrected, or terminate.

System programmer response

See the API completion and reason codes for information about IBM MQ reason codes. For information about signal completion codes, see Signaling. Correct the problem with the queue, or use the ALTER QMGR command to disable the events.

CSQM057E: csect-name MQPUT of trigger message failed for queue q-name, MQRC=mqrc (mqrc-text)
Severity: 8
Explanation: The queue manager could not deliver a trigger message to the indicated initiation queue for the specified IBM MQ reason code (MQRC_).
System action: The queue manager attempts to put the trigger message on to the dead-letter queue if one has been defined.
System programmer response: Refer to API completion and reason codes for information about IBM MQ reason codes, and what action to take to correct the problem with the initiation queue.

CSQM058E

csect-name Unable to start channel channel-name

Severity

Explanation

An attempt was made to start cluster channel channel-name because a message was placed on the SYSTEM.CLUSTER.TRANSMIT.QUEUE. If the channel could not be started because of an internal queuing error this message is preceded by CSQM056E. This message is also issued if the queue manager encounters a storage shortage.

System action

The message remains queued on the SYSTEM.CLUSTER.TRANSMIT.QUEUE queue and the original MQPUT completes successfully. If the cluster channel is not already running it is not automatically started.

System programmer response

If required, manually start the channel using the START CHANNEL command. Stopping and restarting the channel initiator or the queue manager, or placing another message on the transmission queue for this cluster destination triggers another START request.

If message CSQM056E is issued because of an internal queuing error, action might be needed to ensure that future start channel requests can be processed correctly.

If there is a lack of storage and 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.

CSQM059E: csect-name Queue q-name has incorrect attributes
Severity: 8
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).
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

Severity

Explanation

No more space is available in the cluster cache area.

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 we are using a cluster workload exit, ensure that it supports a dynamic cluster cache.) For information about the system parameters for the CSQ6SYSP macro, see Using CSQ6SYSP.

CSQM061E: csect-name Cluster workload exit exit-name does not support dynamic cache
Severity: 8
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.
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. For information about the system parameters for the CSQ6SYSP macro, see Using CSQ6SYSP.

CSQM062I: csect-name INDXTYPE(index-type) not allowed for shared transmission queue shared-xmitq
Severity: 4
Explanation: A shared transmission queue is a queue that is defined with both USAGE(XMITQ) and QSGDISP(SHARED). To support recovery of messages that are in-doubt after a channel failure, the index type (INDXTYPE) for shared transmission queues must be either NONE or MSGID.
System action: Processing continues.
System programmer response: Modify the INDXTYPE attribute for the shared transmission queue to NONE or MSGID.

CSQM063E: csect-name Specified dead-letter queue name is unacceptable
Severity: 4
Explanation: The intra-group queuing (IGQ) agent has attempted to put a persistent message on the dead-letter queue that is defined to the queue manager. The dead-letter queue specified is either SYSTEM.QSG.TRANSMIT.QUEUE or there is no dead-letter queue name specified.
System action: The put of the message to the dead-letter queue does not take place, the get of the message from the SYSTEM.QSG.TRANSMIT.QUEUE is backed out and the intra-group queuing (IGQ) agent goes into retry.
System programmer response: Ensure the queue manager has a dead-letter queue defined which is neither blank nor SYSTEM.QSG.TRANSMIT.QUEUE. Examine the message to determine the reason for its placement on the dead-letter queue.

CSQM064I: csect-name Intra-group queuing agent put messages to dead-letter queue
Severity: 4
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.
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, MQRC=mqrc (mqrc-text)

Severity

Explanation

The indicated MQ API call failed for the specified reason, which is an IBM MQ reason code mqrc (mqrc-text provides the MQRC in textual form).

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 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
Severity: 8
Explanation: The intra-group queuing (IGQ) agent has ended abnormally because a severe error occurred, as reported in the preceding messages.
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

Severity

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.

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
Severity: 8
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.
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

Severity

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.

System action

Processing continues.

CSQM073I: csect-name Loading of durable subscribers started
Severity: 0
Explanation: Information about the durable subscribers on a queue manager is stored on the SYSTEM.DURABLE.SUBSCRIBER.QUEUE queue. During the restart of the queue manager the durable subscriptions are remade on the queue manager.
System action: Processing continues.

CSQM074I: csect-name Loading of durable subscribers finished
Severity: 0
Explanation: The queue manager has finished reloading all of the durable subscribers.
System action: Processing continues.

CSQM075I: csect-name Consolidation of durable subscribers started
Severity: 0
Explanation: Information about the durable subscribers on a queue manager is stored on the SYSTEM.DURABLE.SUBSCRIBER.QUEUE queue. To aid in restart processing and to speed up the time it takes to reload all of the durable subscribers, these messages are consolidated into fewer messages.
System action: Processing continues.

CSQM076I: csect-name Consolidation of durable subscribers finished
Severity: 0
Explanation: The queue manager has finished consolidating the messages on the SYSTEM.DURABLE.SUBSCRIBER.QUEUE queue. The processing might be restarted at a later stage if there is a change in the number of durable subscribers.
System action: Processing continues

CSQM077I: csect-name PUBLISH/SUBSCRIBE ENGINE HAS SHUTDOWN
Severity: 0
Explanation: The publish/subscribe engine has been shutdown.
System action: The publish/subscribe engine has shutdown.
System programmer response: No action is required if the queue manager is stopping. If the publish/subscribe engine has shutdown because you have disabled it, updating the PSMODE queue manager attribute from the value DISABLED will restart it.

CSQM078E

csect-name Unable to create thread structures for connection-type connection from jobname, insufficient ACE storage

Severity

Explanation

jobname attempted to create a new connection to IBM MQ as the result of issuing the first IBM MQ API call on a new thread. The connection-type is likely to be RRSBATCH.

There was insufficient common storage available to build the control blocks to represent the connection and the connect attempt failed.

There might be a system wide ECSA shortage, or the storage available for creating new queue manager connections might be limited by the ACELIM system parameter.

This message can be seen for CICS and the channel initiator, as well as for RRS applications; for example, Db2 stored procedures and WebSphere Application Server.

System action

IBM MQ API request fails with return code MQRC_STORAGE_NOT_AVAILABLE 2071

Queue manager processing continues

CSQM079I: csect-name Policy access attempt rejected due to incompatible AMS version, jobname jobname
Severity: 4
Explanation: An incompatible version of Advanced Message Security (AMS), identified by jobname, attempted to open the policy queue, SYSTEM.PROTECTION.POLICY.QUEUE.
System action: The request to open the policy queue is rejected.
System programmer response: Update the incompatible version of AMS so it does not attempt to connect to the queue manager. From Version 8.0, AMS is provided as an integrated feature of IBM MQ for z/OS. For information about how to configure AMS as an integrated feature, see Installing IBM MQ Advanced for z/OS or Installing IBM MQ Advanced for z/OS Value Unit Edition.

CSQM084I

csect-name COMMAND INHIBITED DURING RESTART/TERMINATION

Severity

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.

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 recur.

CSQM085I: csect-name ABNORMAL COMPLETION
Severity: 8
Explanation: This message is issued with message CSQM084I, and indicates that the command requested has not been actioned.
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
Severity: 8
Explanation: During restart, the creation of the queue manager object has failed. The reason code is of the form '00D44xxx'.
System action: The queue manager fails to restart.
System programmer response: See 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 the IBM support center.

CSQM090E: csect-name FAILURE REASON CODE reason-code
Severity: 8
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.
System action: The command is ignored.
System programmer response: See the explanations of the accompanying messages for more information. See 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 the IBM support center.

CSQM091E: csect-name FAILURE MQRC=mqrc (mqrc-text)
Severity: 8
Explanation: A command has failed. The reason code is an IBM MQ reason code. This message is accompanied by one or more other more specific messages, which indicate the reason for the failure.
System action: The command is ignored.
System programmer response: See the explanations of the accompanying messages for more information. Refer to API completion and reason codes for an explanation of mqrc, (mqrc-text provides the MQRC in textual form), and what action to take.

CSQM092I

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

Severity

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.

System action

The command is ignored.

System programmer response

Reissue the command with the parameter specified correctly. For more information about the command, see MQSC commands.

CSQM093I: csect-name keyword(value) NAME CONTAINS INVALID CHARACTERS
Severity: 8
Explanation: A name was specified that contains one or more invalid characters. See MQSC commands for information about validation required for the name in question to correct this.
System action: The command is ignored.
System programmer response: Reissue the command with the correct name. For more information about the command, see MQSC commands.

CSQM094I

csect-name keyword(value) WAS NOT FOUND

Severity

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.

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. Note:

If we are dealing with a queue or channel object, an object of the same name, but of a different subtype, might already exist.
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) existing-disposition ALREADY EXISTS
Severity: 8
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.) Where applicable, existing-disposition identifies the queue sharing group disposition of the existing object.
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
Severity: 8
Explanation: A name was specified that is of an incorrect length.
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 MQSC commands.

CSQM097I: csect-name keyword(value) NAME CANNOT BE COMPLETELY BLANK
Severity: 8
Explanation: A name was specified that is blank. This is not allowed.
System action: The command is ignored.
System programmer response: Reissue the command with a non-blank name. For more information about the command, see MQSC commands.

CSQM098I: csect-name keyword(value) FIELD TOO LONG
Severity: 8
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 with a total length that is too long.
System action: The command is ignored.
System programmer response: Reissue the command with the correct field length. For more information about the command, see MQSC commands.

CSQM099I: csect-name keyword(value) NAME IN USE AS A DIFFERENT TYPE
Severity: 8
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.)
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 MQSC commands.

CSQM100I

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

Severity

Explanation

A value is invalid or out of range. This could be because:

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.

System action

The command is ignored.

System programmer response

Reissue the command with the parameter specified correctly. For more information about the command, see MQSC commands.

CSQM101I

csect-name keyword(value) IS CURRENTLY IN USE

Severity

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 IBM MQ.
There is no connection from the queue manager to the structure.

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 MQSC commands.

CSQM102E

csect-name SSLCIPH sslciph IS A WEAK OR BROKEN CIPHERSPEC

Severity

Explanation

A channel could not be defined or altered, because the specified SSLCIPH parameter contains a CipherSpec that is potentially insecure.

System action

The named channel is not defined or altered

System programmer response

Examine the CipherSpec specified in the SSLCIPH parameter and consider using a more secure CipherSpec.

To re-enable the use of weak CipherSpecs, we can do so by adding a dummy Data Definition (DD) statement named CSQXWEAK to the channel initiator JCL. For example:

//CSQXWEAK DD DUMMY

To re-enable the disabled SSLv3 support in IBM MQ, we can do so by adding a dummy Data Definition (DD) statement named CSQXSSL3 to the channel initiator JCL. For example:

//CSQXSSL3 DD DUMMY

To re-enable the disabled TLS 1.0 support in IBM MQ, we can do so by adding a dummy Data Definition (DD) statement named CSQXTLS1 to the channel initiator JCL. For example:

//CSQXTLS1 DD DUMMY

We need to specify the CSQXWEAK dummy DD statement, and the:

CSQXSSL dummy DD statement, if we want to enable a weak SSL 3.0-based CipherSpec
CSQXTLS dummy DD statement, if we want to enable a weak TLS 1.0-based CipherSpec
CSQXSSL and CSQXTLS dummy statements, if we want to enable both a weak SSL 3.0-based and TLS 1.0-based CipherSpec

There are alternative mechanisms that can be used to forcibly re-enable weak CipherSpecs, and SSLv3 support, if the Data Definition change is unsuitable. Contact IBM Service for further information.

Attention: Re-enabling CipherSpecs in this manner leaves systems exposed to possible security problems. We should use CipherSpecs that use only the TLS protocol, rather than SSLv3.

CSQM103I: csect-name keyword(value) QSGDISP(disposition) HAS MESSAGES ASSOCIATED WITH IT
Severity: 8
Explanation: A local queue specified for deletion has messages associated with it, and the DELETE request did not include the PURGE option.
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, we must 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
Severity: 8
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.
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
Severity: 8
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.
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
Severity: 8
Explanation: The specified queue is not allowed to be used as the default transmission queue because it is reserved for use exclusively by clustering.
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

Severity

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.

System action

The command is ignored.

System programmer response

If there are messages on the queue, we must 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

Severity

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 in this topic:

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.PUBSUB.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.CHLAUTH.DATA.QUEUE 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.JMS.TEMPQ.MODEL 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

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, MQRC=mqrc (mqrc-text)

Severity

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.

System action

The named dynamic queue is not deleted.

System programmer response

Refer to 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
Severity: 8
Explanation: A command was issued that refers to a local queue that has incomplete units of recovery outstanding for it.
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, MQRC=mqrc (mqrc-text)
Severity: 4
Explanation: An attempt to put a message to the dead letter queue was unsuccessful. mqrc gives the reason code for the error.
System action: Processing continues.
System programmer response: Refer to API completion and reason codes for information about mqrc (mqrc-text provides the MQRC in textual form) to determine the cause of the problem.

CSQM112E: csect-name ERROR ACCESSING keyword(value)
Severity: 4
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.
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; for information about this, see Page sets. 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 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)

Severity

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).

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 Manage page sets for information about how to do this.
Reduce the number of application structures we are using.

CSQM114E: csect-name keyword(value) EXCEEDED LOCAL QUEUE LIMIT
Severity: 8
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.
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

Severity

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.

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 MQSC commands.

CSQM117E: csect-name ERROR ACCESSING keyword(value) QSGDISP(disposition)
Severity: 4
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.
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; for information about this, see Page sets. 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, see 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: For information about migration and compatibility between releases, see Maintain and migrate.

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: For information about migration and compatibility between releases, see Maintain and migrate.

CSQM120I: csect-name keyword(value) NOT ALLOWED FOR SHARED QUEUE
Severity: 8
Explanation: The specified value for the object name or attribute is not allowed for a local queue with a disposition that is shared or a model queue used to create a dynamic queue that is shared.
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
Severity: 8
Explanation: The specified value for the attribute requires a queue sharing group, but the queue manager is not in a group.
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)
Severity: 0
Explanation: Processing for the specified command that refers to an object with the indicated disposition has completed successfully.
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
Severity: 8
Explanation: The value for the specified attribute cannot be changed.
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)
Severity: 8
Explanation: The specified value for the attribute is allowed only for an object that has the indicated disposition.
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

Severity

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.

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. Note:

An object of the same name and type, but of a different disposition, might already exist.
If we are dealing with a queue or channel object, an object of the same name, but of a different subtype, might already exist.
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
Severity: 8
Explanation: The named keyword can only be specified when TRPTYPE(LU62) is specified.
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
Severity: 8
Explanation: A namelist used to specify a list of clusters has no names in it or does not have type CLUSTER or NONE.
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, MQRC=mqrc (mqrc-text)
Severity: 8
Explanation: During the processing of a command, an attempt to put a message to the named queue failed for the specified reason.
System action: In general, the command is not actioned. If the command was REFRESH QMGR for configuration events, it might be partially completed as indicated by the preceding CSQM169I messages.
System programmer response: Refer to API completion and reason codes for information about mqrc (mqrc-text provides the MQRC in textual form). If mqrc is 2003, the message could not be committed.

CSQM129I: csect-name keyword(value) HAS WRONG CHANNEL TYPE
Severity: 8
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.
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 MQSC commands.

CSQM130I

csect-name CLUSTER REQUEST QUEUED

Severity

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.

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
Severity: 8
Explanation: A command was issued that required the channel initiator to be started.
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
Severity: 8
Explanation: The START CHINIT command was issued but the channel initiator is already active.
System action: The command is not actioned.

CSQM133I

csect-name UNABLE TO START CHANNEL INITIATOR

Severity

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.

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
Severity: 0
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.
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

Severity

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

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.

CSQM136I: 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
Severity: 0
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.
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
Severity: 0
Explanation: A START CHINIT command was issued and the channel initiator address space has been started successfully.
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
Severity: 8
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.
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)
Severity: 8
Explanation: The named keyword cannot be used on a START LISTENER command for the transport type shown.
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)
Severity: 8
Explanation: A START LISTENER command was issued specifying TRPTYPE(LU62) but without the LUNAME keyword. The LUNAME keyword is required with TRPTYPE(LU62).
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
Severity: 8
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.
System action: Processing of the command is terminated.
System programmer response: Reissue the command with the correct values or on the correct queue manager.

CSQM143I: csect-name CLUSTER TOPICS INHIBITED DUE TO PSCLUS(DISABLED)
Severity: 8
Explanation: An attempt was made to define a cluster topic when the PSCLUS queue manager attribute is set to DISABLED.
System action: Processing of the command is terminated.
System programmer response: To enable publish/subscribe clustering, alter the PSCLUS attribute on all queue managers in the cluster to ENABLED.

CSQM144I

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

Severity

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:

SYSTEM.CHANNEL.INITQ
SYSTEM.CHANNEL.SYNCQ
SYSTEM.CLUSTER.COMMAND.QUEUE
SYSTEM.CLUSTER.REPOSITORY.QUEUE
SYSTEM.COMMAND.INPUT
SYSTEM.QSG.CHANNEL.SYNCQ
SYSTEM.QSG.TRANSMIT.QUEUE

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
Severity: 8
Explanation: A non-blank value must be specified for the named keyword for a local queue with a disposition that is shared or a model queue used to create a dynamic queue that is shared.
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
Severity: 8
Explanation: A keyword was entered that takes a list of values, and the named value appears more than once in the list.
System action: The command is ignored.
System programmer response: Reissue the command with the parameter specified correctly. For more information about the command, see MQSC commands.

CSQM147I: csect-name 'keyword1' AND 'keyword2' VALUES MUST BOTH BE BLANK OR NON-BLANK
Severity: 8
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.
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'
Severity: 8
Explanation: The named keyword cannot be specified for queues or channels of the type shown.
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'
Severity: 8
Explanation: The named keyword was not specified but is required for queues or channels of the type shown.
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
Severity: 8
Explanation: An attempt was made to define or alter an object so that it had incompatible values for the specified keywords.
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 MQSC commands.

CSQM151I: csect-name 'keyword1' AND 'keyword2' VALUES CANNOT BOTH BE NON-BLANK
Severity: 8
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.
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
Severity: 8
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.
System action: Processing of the command is terminated.
System programmer response: Reissue the command with correct values.

CSQM153E: csect-name Db2 NOT AVAILABLE
Severity: 8
Explanation: Because Db2 is not available or no longer available, the queue manager cannot handle the command for a CF structure or shared channel.
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
Severity: 8
Explanation: Because there was an error in accessing Db2, the queue manager cannot handle the command for a CF structure or shared channel.
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
Severity: 8
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.
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)
Severity: 8
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.
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)
Severity: 8
Explanation: An IBM MQ DEFINE CFSTRUCT command failed because no more application structures are available in the coupling facility (the limit is 63).
System action: The command is not actioned.
System programmer response: Reduce the number of application structures we are using.

CSQM158I: csect-name RECOVER(YES) NOT ALLOWED WITH CFLEVEL(value)
Severity: 8
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.
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; we must delete the structure and then redefine it.

CSQM159I: csect-name verb-name object(obj-name) NOT ALLOWED, INCOMPATIBLE QUEUE MANAGER CMDLEVELS
Severity: 8
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 certain command level. Some of the queue managers have a lower level.
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 MQSC commands.

CSQM160I: csect-name keyword(value) IS NOT UNIQUE
Severity: 8
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.
System action: The command is not executed.
System programmer response: Delete one of the objects.

CSQM161I: csect-name QUEUE ATTRIBUTES ARE INCOMPATIBLE
Severity: 8
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.
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
Severity: 8
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.
System action: The command is not executed.
System programmer response: Change the MAXDEPTH value for the queue.

CSQM163I: csect-name ERROR USING keyword(value), MQRC=mqrc (mqrc-text)
Severity: 8
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.
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 API completion and reason codes for information about mqrc (mqrc-text provides the MQRC in textual form), and take the appropriate action to resolve the problem.

CSQM164I: csect-name keyword(value) HAS MESSAGES ASSOCIATED WITH IT
Severity: 8
Explanation: A MOVE QLOCAL command was issued specifying TYPE(MOVE), the target queue already has messages associated with it.
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

Severity

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.

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
Severity: 8
Explanation: You do not have proper authorization to use the command for the specified object.
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
Severity: 8
Explanation: A command was issued that required performance events to be enabled.
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
Severity: 8
Explanation: A command was issued that required configuration events to be enabled.
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
Severity: 0
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 might be less than the number of objects found because certain objects might be excluded, such as temporary dynamic queues or objects in the process of being deleted. It might also be less than the number of objects found if there was a problem with the event queue.
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
Severity: 0
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.

CSQM171I

csect-name CONFIGURATION EVENTS REFRESH NEEDED

Severity

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.

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 we 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)
Severity: 8
Explanation: The named keyword cannot be specified with the TYPE value shown.
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
Severity: 0
Explanation: A REFRESH QMGR command was issued for expired message scanning. m queues were found that matched the specified selection criteria.
System action: Processing continues.

CSQM174E: csect-name 'keyword' is not allowed with CFLEVEL(cflevel) - this keyword requires CFLEVEL(5)
Severity: 8
Explanation: An attempt was made to define or alter the value of a structure attribute related to SMDS, but the level of the structure was less than CFLEVEL(5). This is not allowed.
System action: Processing for the command is terminated.
System programmer response: Issue the command again with correct values. We cannot alter the level of a CF structure; you must delete the structure, and then define it again.

CSQM175E: csect-name 'keyword' cannot be altered because a data set is currently active for this structure
Severity: 8
Explanation: The keywords DSGROUP and DSBLOCK can only be altered before the first data set has been allocated for the structure. Once an SMDS data set has become active for this structure then these attribute values cannot be changed.
System action: Processing for the command is terminated.
System programmer response: Verify the command entry and reissue the command correctly.

CSQM176E

csect-name SMDS cannot currently be reset to keyword(value)

Severity

Explanation

A RESET SMDS command requested a change of status which is not compatible with the existing status.

The option STATUS(FAILED) is only allowed when the current status is ACTIVE or RECOVERED (or already FAILED, in which case the command has no effect).
The option STATUS(RECOVERED) is only allowed when the current status is FAILED (or already RECOVERED).

System action

Processing for the command is terminated.

System programmer response

Verify the command entry, and reissue the command correctly.

CSQM177I: csect-name 'keyword' NOT ALLOWED WITH ACTION 'value'
Severity: 8
Explanation: The named keyword cannot be specified for channel authentication settings of the action shown.
System action: Processing for the command is terminated.
System programmer response: Reissue the command without the named keyword.

CSQM178I

csect-name ACTION NOT ALLOWED FOR CHANNEL channel-type(channel-name)

Severity

Explanation

The MATCH(RUNCHECK) action that you requested cannot be performed on the channel with the specified parameters. This may be because either: -

The channel is a SVRCONN and the QMNAME parameter was supplied.
The channel is not a SVRCONN and the CLNTUSER parameter was supplied

System action

Processing of the command is terminated.

System programmer response

Either correct the specified parameters or alter the channel to the appropriate channel type and then reissue the command.

CSQM179I

csect-name CHANNEL WILL RUN USING MCAUSER(userid)

Severity

Explanation

No matching channel authentication (CHLAUTH) records were found that match the given fields. Note:

The returned MCAUSER value does not take into account possible actions by a channel security exit.
Channel authentication rules that match the host name apply only if the queue manager REVDNS attribute is enabled and the DNS server returns a valid host name for the IP address.

CSQM181I: csect-name INSUFFICIENT STORAGE TO COMPLETE COMMAND
Severity: 8
Explanation: There was insufficient storage available to complete processing for the command.
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 the system.

CSQM182E

csect-name DURABLE SUBSCRIPTIONS NOT ALLOWED

Severity

Explanation

A DEFINE SUB command was issued, but it was not possible to make a durable subscription.

This could be for one of the following reasons:

The topic subscribed to is defined as DURSUB(NO)
The queue named SYSTEM.DURABLE.SUBSCRIBER.QUEUE is not available

The CSQINP2 data sets are in the wrong order, the order is:

 //CSQINP2  DD DSN=hlq.SCSQPROC(CSQ4INYS),DISP=SHR //         DD DSN=hlq.SCSQPROC(CSQ4INSX),DISP=SHR 
 //         DD DSN=hlq.SCSQPROC(CSQ4INSG),DISP=SHR

System action

The command is not executed.

System programmer response

Durable subscriptions are stored on the SYSTEM.DURABLE.SUBSCRIBER.QUEUE. Ensure that this queue is available for use. Possible reasons for failure include the queue being full, the queue being put inhibited, or the queue not existing.

If the topic subscribed to is defined as DURSUB(NO) then it is not possible to administratively define a subscription. The topic can be altered to DURSUB(YES) to enable the subscription to be defined.

CSQM183E: csect-name SUBSCRIPTION INHIBITED
Severity: 8
Explanation: A DEFINE SUB command was issued, but it was not possible to make a subscription because the topic subscribed to is defined as SUB(DISABLED).
System action: The command is not executed.
System programmer response: If the topic subscribed to is defined as SUB(DISABLED) then it is not possible to administratively define a subscription. The topic can be altered to SUB(ENABLED) to enable the subscription to be defined.

CSQM184I: csect-name 'keyword1' AND 'keyword2' VALUES CANNOT BOTH BE BLANK
Severity: 8
Explanation: An attempt was made to define or alter an object so that it had blank values for both of the specified keywords. One of those values must be provided.
System action: Processing of the command is terminated.
System programmer response: Reissue the command with correct values.

CSQM185E: csect-name SUBSCRIPTION HAS FIXED SUBUSER
Severity: 8
Explanation: An ALTER SUB command was issued, but it was not possible to ALTER the target subscription because the userid performing the ALTER did not match the SUBUSER attribute of the subscription and the subscription has had the VARUSER(FIXED) attribute set.
System action: The command is not executed.
System programmer response: The subscription can be altered only by the owning userid that is displayed in the SUBUSER attribute.

CSQM186E: csect-name DESTCLAS VALUE CANNOT BE ALTERED
Severity: 8
Explanation: An ALTER SUB command was issued, but it was not possible to ALTER the target subscription because the DESTCLAS attribute specified on the request did not match the one in the existing subscription. DESTCLAS cannot be altered.
System action: The command is not executed.
System programmer response: Ensure that the DESTCLAS attribute matches the existing subscription and rerun the request.

CSQM187E: csect-name GROUPING VALUE CANNOT BE ALTERED
Severity: 8
Explanation: An ALTER SUB command was issued, but it was not possible to ALTER the target subscription because the GROUPING attribute specified on the request did not match the one in the existing subscription. GROUPING attributes cannot be altered.
System action: The command is not executed.
System programmer response: Ensure that the GROUPING attribute matches the existing subscription and rerun the request.

CSQM188E: csect-name SUBSCOPE VALUE CANNOT BE ALTERED
Severity: 8
Explanation: An ALTER SUB command was issued, but it was not possible to ALTER the target subscription because the SUBSCOPE attribute specified on the request did not match the one in the existing subscription. SUBSCOPE cannot be altered.
System action: The command is not executed.
System programmer response: Ensure that the SUBSCOPE attribute matches the existing subscription and rerun the request.

CSQM189E: csect-name SELECTOR VALUE CANNOT BE ALTERED
Severity: 8
Explanation: An ALTER SUB command was issued, but it was not possible to ALTER the target subscription because the SELECTOR attribute specified on the request did not match the one in the existing subscription. SELECTOR cannot be altered.
System action: The command is not executed.
System programmer response: Ensure that the SELECTOR attribute matches the existing subscription and rerun the request.

CSQM190E

csect-name TOPIC STRING IS INVALID

Severity

Explanation

A DEFINE SUB command was issued, but it was not possible to make a subscription because the topic string was invalid.

This could be because the WSCHEMA attribute was set to CHAR and either:

The TOPICSTR attribute contains an invalid escape character, or
The TOPICOBJ attribute refers to a TOPIC object with a TOPICSTR attribute that contains an invalid escape character.

System action

The command is not executed.

System programmer response

Correct the TOPICSTR attribute on the DEFINE SUB command to correctly use escape characters. If the problem is with the TOPICSTR in a TOPIC object, correct that TOPIC object or refer to a different TOPIC object. If the TOPICSTR needs to use the characters in that way, set the WSCHEMA attribute to TOPIC to avoid errors with escape characters.

CSQM191E: csect-name TOPIC STRING CANNOT BE ALTERED
Severity: 8
Explanation: A DEFINE TOPIC command using the REPLACE keyword was issued, providing a value for TOPICSTR that was different from the value in the existing object. This is not allowed.
System action: The command is not executed.
System programmer response: Reissue the command with correct values. We cannot alter the topic string in a topic object; you must delete the object and then redefine it.

CSQM192I: csect-name Address 'address' is invalid.
Severity: 8
Explanation: The IP address or host name address contains invalid characters.
System action: Processing of the command is terminated.
System programmer response: Reissue the command with the parameter specified correctly. Note that the BLOCKADDR list may contain only IP addresses: host name addresses are not permitted.

CSQM193I: csect-name IP address 'ipaddress' contains an invalid range.
Severity: 8
Explanation: The IP address ipaddress contains an invalid range. For example, the lower number is greater than or equal to the upper number for the range.
System action: Processing of the command is terminated.
System programmer response: Reissue the command with the parameter specified correctly.

CSQM194I: csect-name IP address 'ipaddress1' overlaps existing IP address 'ipaddress2'.
Severity: 8
Explanation: The IP address ipaddress1 overlaps with an existing IP address ipaddress2. For example, addresses 1.2.3.4-7 and 1.2.3.6-8 overlap.
System action: Processing of the command is terminated.
System programmer response: Reissue the command with the parameter specified correctly.

CSQM195I: csect-name MATCH RUNCHECK FOUND A GENERIC VALUE IN field-name
Severity: 8
Explanation: A DISPLAY CHLAUTH command was issued using the MATCH(RUNCHECK) parameter and the field-name parameter was found to contain a generic value, which is not allowed.
System action: Processing of the command is terminated.
System programmer response: Reissue the command with a value in field-name which is not generic.

CSQM196I

csect-name REQUIRED KEYWORD MISSING FOR keyword(value)

Severity

Explanation

A required additional keyword was not specified in conjunction with keyword (value).

This message can be returned in the following scenarios:

A DISPLAY CHLAUTH command, specifying MATCH(RUNCHECK) did not specify the ADDRESS keyword or one of the keywords CLNTUSR or QMNAME.
A SET CHLAUTH command, the MCAUSER is missing when USERSRC(MAP) is specified or USERSRC is missing as USERSRC(MAP) is the default.

System action

Processing of the command is terminated.

System programmer response

Reissue the command specifying one of the required keywords

CSQM197I: csect-name 'keyword' NOT ALLOWED WITH MATCH 'value'
Severity: 8
Explanation: The named keyword cannot be specified for DISPLAY CHLAUTH in conjunction with the identified value for the MATCH keyword.
System action: Processing of the command is terminated.
System programmer response: Reissue the command without the named keyword.

CSQM198I: csect-name CHANNEL AUTHENTICATION PROFILE NAME IS INVALID
Severity: 8
Explanation: The channel profile name used in the command was not valid.
System action: Processing of the command is terminated.
System programmer response: Check that the characters entered for the profile are valid and reissue the command. If TYPE(BLOCKADDR) is specified, check that CHLAUTH('*') is also specified

CSQM199I: csect-name CFCONLOS (TOLERATE) NOT ALLOWED, INCOMPATIBLE QUEUE MANAGER CMDLEVELS
Severity: 8
Explanation: An attempt was made to change the CFCONLOS queue manager attribute to a value of TOLERATE, which enables toleration of loss of connectivity to Coupling Facility structures. This action requires that all queue managers in the queue sharing group must have a command level of at least 710. Some of the queue managers have a lower level.
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 MQSC commands.

CSQM201I

csect-name verb-name obj-type DETAILS

Severity

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

See the specific command for details of the attributes and values.

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.) For details of the fields reported, see the command description.

CSQM224I

csect-name verb-name obj-type DETAILS - CURRENTLY DISABLED

Severity

Explanation

This message is issued instead of CSQM201I for channel authentication (CHLAUTH) records if the CHLAUTH queue manager attribute has been set to DISABLED.

See the explanation of message CSQM201I for more information.

CSQM292I: csect-name PUBLISH/SUBSCRIBE ENGINE IS DISABLED
Severity: 0
Explanation: The publish/subscribe engine is unavailable because it has been disabled.
System action: The command is actioned, but no results are returned because the publish/subscribe engine has been disabled.
System programmer response: This message occurs because we are attempting to query the publish/subscribe engine but you have disabled it. To use the publish/subscribe engine, set the PSMODE queue manager attribute to a value other than DISABLED.

CSQM293I: csect-name m obj-type FOUND MATCHING REQUEST CRITERIA
Severity: 0
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.

CSQM294I: csect-name CANNOT GET INFORMATION FROM DB2
Severity: 8
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 might 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.
System action: Information about objects with a disposition of GROUP or SHARED is not displayed, so the information displayed might 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
Severity: 8
Explanation: A severe error occurred while processing a command that displays attributes or other information about objects.
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 item FOUND MATCHING REQUEST CRITERIA
Severity: 0
Explanation: A command that displays attributes or other information about objects or runtime status found that there are no items that match the specified name and satisfy any other criteria requested (such as subtype or disposition in a queue sharing group).

CSQM298I: csect-name TOTAL MESSAGE LENGTH ALLOWED ON CONSOLE EXCEEDED
Severity: 8
Explanation: The total message length for the command allowed on the console (32 K) was exceeded.
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
Severity: 8
Explanation: There was insufficient storage available to complete processing of a command that displays attributes or other information about objects.
System action: The command is actioned, but the display of the information is terminated before completion. The data returned is a subset of the requested information. Refer to message CSQM293I, which indicates how many objects have information returned. The message does not indicate how many matching objects were found.
System programmer response: If this error occurs when a generic name is used in the command (for example, DIS QUEUE(*) ALL), try to be more selective about the information requested (for example, DIS QUEUE(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 the system.

CSQM4nnI

object details

Severity

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
CSQM438I	Topic object
CSQM439I	Cluster queue manager object
CSQM440I	CF structure status
CSQM441I	Local queue status
CSQM442I	Connection information
CSQM443I	Topic status
CSQM444I	Subscription
CSQM445I	Subscription status
CSQM446I	Publish/Subscribe status
CSQM451I	Local queue statistics
CSQM452I	Shared message data set
CSQM453I	Shared message data set connection
CSQM454I	Channel authentication record

CSQM500I

csect-name GROUPUR agent starting TCB=tcb-name

Severity

Explanation

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

The GROUPUR agent monitors the SYSTEM.QSG.UR.RESOLUTION.QUEUE to process requests from other queue managers within the QSG.

System action

Processing continues. The GROUPUR agent is started.

CSQM501I

csect-name GROUPUR agent stopping

Severity

Explanation

The group unit of recovery (GROUPUR) agent is stopping because of one the following reasons:

the queue manager is stopping
it was unable to recover from an IBM MQ API error or an abnormal ending

System action

The GROUPUR agent stops.

If the agent has stopped due to an error it will be automatically restarted.

System programmer response

If the queue manager is not stopping, investigate the cause of the error as reported in the preceding messages.

CSQM502I: csect-name processed BACKOUT request from qmgr-name for in-doubt UOW, URID=urid, CONNECTION-NAME=name
Severity: 0
Explanation: This message is generated during queue manager startup when the GROUPUR agent has processed a message on the SYSTEM.QSG.UR.RESOLUTION.QUEUE from another queue manager in the queue sharing group requesting that the specified UOW be backed out.
System action: Processing continues.

CSQM503I: csect-name processed COMMIT request from qmgr-name for in-doubt UOW, URID=urid, CONNECTION-NAME=name
Severity: 0
Explanation: This message is generated during queue manager startup when the GROUPUR agent has processed a message on the SYSTEM.QSG.UR.RESOLUTION.QUEUE from another queue manager in the queue sharing group requesting that the specified UOW be committed.
System action: Startup continues.

CSQM504I: csect-name GROUPUR support enabled
Severity: 0
Explanation: This message is generated during queue manager startup, or in response to an ALTER QMGR command, if the GROUPUR queue manager attribute is enabled and all of the configuration checks performed by the GROUPUR agent are satisfied.
System action: The queue manager permits applications to establish transactions with a GROUP unit of recovery disposition.

CSQM505I: csect-name GROUPUR support disabled
Severity: 0
Explanation: This message is generated during queue manager startup or in response to an ALTER QMGR command if the GROUPUR queue manager attribute is disabled.
System action: The queue manager inhibits applications from establishing transactions with a GROUP unit of recovery disposition.

CSQM506I: csect-name GROUPUR qmgr attribute has been disabled CODE=code
Severity: 4
Explanation: This message is generated at queue manager startup if the GROUPUR queue manager attribute is enabled but one of the configuration checks performed by the GROUPUR agent failed. CODE=code contains an identifier indicating which configuration check failed.
System action: The GROUPUR queue manager attribute is disabled.
System programmer response: The system programmer should use the code specified to identify what configuration check failed. If support for group units of recovery is required, they should take corrective action and then re-enable the GROUPUR queue manager attribute.

CSQM507E

csect-name GROUPUR qmgr attribute was not enabled CODE=code

Severity

Explanation

This message is generated in response to an ALTER QMGR command if an attempt to enable the GROUPUR queue manager attribute fails because one of the configuration checks performed by the GROUPUR agent are not satisfied. CODE=code contains an identifier indicating which configuration check failed.

System action

The GROUPUR queue manager attribute remains disabled and the ALTER QMGR command fails.

System programmer response

The system programmer should use the code specified to identify what configuration check failed. They should then take corrective action and then re-issue the ALTER QMGR command.

When you enable group units of recovery (GROUPUR support) a number of configuration checks are performed to ensure the configuration steps have been completed. We cannot enable this support if any of these checks fail.

These checks are also performed at queue manager startup if GROUPUR queue manager attribute is enabled. If one of these checks fails during startup then group units of recovery will be disabled until you correct the error and re-enable the GROUPUR queue manager attribute.

If a check fails it will be identified with a return code (number). We can use this code to identify the failing check using the following list:

This queue manager is not a member of a queue sharing group.
The SYSTEM.QSG.UR.RESOLUTION.QUEUE does not exist.
The SYSTEM.QSG.UR.RESOLUTION.QUEUE does not support persistent messages.
The SYSTEM.QSG.UR.RESOLUTION.QUEUE is not indexed by correlation ID.
The SYSTEM.QSG.UR.RESOLUTION.QUEUE does not reside on the system application coupling facility structure, CSQSYSAPPL.
The queue manager name is the same as the name of the queue sharing group.

CSQM508E

csect-name GROUPUR agent ended abnormally. Restarting

Severity

Explanation

The group unit of recovery (GROUPUR) agent has ended abnormally because a severe error occurred, as reported in the preceding messages.

System action

The group unit of recovery (GROUPUR) agent attempts to restart a number of times. If it fails persistently, it terminates.

System programmer response

Ensure the CFSTRUCT called CSQSYSAPPL is configured for GROUPUR operation. See Enabling GROUP units of recovery.

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

CSQM520I: csect-name PSCLUS CANNOT BE ALTERED, CLUSTER TOPICS EXIST
Severity: 8
Explanation: An attempt was made to set the PSCLUS queue manager attribute to DISABLED, indicating that Publish/Subscribe activity is not expected in this cluster between queue managers, but a cluster topic exists so the setting cannot be modified.
System action: Processing of the command is terminated.
System programmer response: To disable publish/subscribe clustering delete all cluster topic objects before altering the PSCLUS attribute on all queue managers in the cluster to DISABLED.

CSQM521I: csect-name CLCHNAME MUST BE BLANK FOR DYNAMIC QUEUE
Severity: 8
Explanation: An attempt was made to define or alter a dynamic queue with a non blank value for the CLCHNAME attribute, which is not allowed.
System action: Processing of the command is terminated.
System programmer response: Reissue the command with compatible attribute values.

CSQM522I: csect-name NOSHARE NOT ALLOWED WITH NON-BLANK CLCHNAME
Severity: 8
Explanation: An attempt was made to define or alter a queue with a non-blank value for the CLCHNAME attribute, but NOSHARE was specified or implied.
System action: Processing of the command is terminated.
System programmer response: Reissue the command, specifying either SHARE or a blank value for the CLCHNAME attribute.

CSQM523I

csect-name CLUSTER OR CLROUTE CANNOT CURRENTLY BE ALTERED

Severity

Explanation

An attempt was made to alter an administered topic that is currently in a named cluster. While a topic is in a cluster it is not permitted to modify the CLROUTE attribute, or to modify the CLUSTER attribute to an alternative cluster name if CLROUTE is set to TOPICHOST.

System action

Processing of the command is terminated.

System programmer response

To alter the CLROUTE or CLUSTER attribute, perform the following actions:

Quiesce publish/subscribe messaging for the topic.
Remove the topic from the cluster by setting the value of the CLUSTER attribute to blank.
Set the CLROUTE and CLUSTER attributes to their required value once the topic has been removed from the cluster.
Resume publish/subscribe messaging once the change is visible in the cluster and the queue manager has received proxy subscriptions for any remote subscriptions.

CSQM524I: csect-name CLROUTE CONFLICT DETECTED FOR CLUSTER TOPIC
Severity: 8
Explanation: An attempt was made to define a cluster topic but the value of the CLROUTE attribute conflicts with an existing topic, either above or below it, in the topic tree.
System action: Processing of the command is terminated.
System programmer response: Review the cluster routing requirements for the topic tree, then correct and reissue the command.

CSQM525I

csect-name obj-type(obj-name) DOES NOT EXIST OR IS DEFINED INCORRECTLY

Severity

Explanation

The queue manager could not complete a requested operation because an object named obj-name of type obj-type does not exist or is defined incorrectly.

System action

Processing of the operation is terminated.

System programmer response

Check the object has been defined correctly, then try the operation again.

For information on how to define system objects, see Sample definitions supplied with IBM MQ.

If this message has been issued for the model queue SYSTEM.CLUSTER.TRANSMIT.MODEL.QUEUE, and the queue has been defined, ensure it has the following attributes:

The USAGE attribute must be set to XMITQ
The QSGDISP attribute must not be SHARED
The DEFTYPE attribute must be set to PERMDYN
The INDXTYPE attribute must be set to CORRELID
The SHARE attribute must be set

CSQM526I: csect-name CERTIFICATE LABEL NOT ALLOWED FOR SSLv3 CHANNEL
Severity: 8
Explanation: An attempt was made to specify a certificate label for an inbound channel that uses a SSL v3 CipherSpec, which is not allowed. Certificate labels for inbound channels are only supported for TLS channels.
System action: Processing of the command is terminated.
System programmer response: For to configure a certificate label, alter the channel to use a TLS CipherSpec.

CSQM527E

csect-name attribute(value) NOT ALLOWED WITH CHANNEL TYPE channel-type

Severity

Explanation

An attempt was made to specify a channel attribute value combination which is not applicable for the specified channel type.

Either SPLPROT(ASPOLICY) was specified on a channel with CHLTYPE SDR or SVR, or SPLPROT(REMOVE) was specified on a channel with CHLTYPE RCVR or RQSTR. These combinations are not valid.

System action

Processing of the command is terminated.

System programmer response

Ensure a valid attribute and value combination is specified for the respective channel type. For more information, see SPLPROT under the DEFINE CHANNEL command.

CSQM528E: SSLCIPH(cipher specification name) is not supported
Severity: 8
Explanation: The specified cipher specification name is not supported by the queue manager.
System action: An attempt to define or alter a channel definition fails.
System programmer response: Refer to CipherSpecs order from IBM MQ Version 9.2.0 for a list of supported cipher specifications, and specify one of these.

CSQM529E: SSLCIPH(cipher specification name) is not in the AllowedCipherSpecs list
Severity: 8
Explanation: The specified cipher specification name is not in the list of AllowedCipherSpecs defined in the QMINI data set specified in the queue manager start up procedure.
System action: An attempt to define or alter a channel definition fails.
System programmer response: Define a cipher specification that is in the list of AllowedCipherSpecs, or add the cipher specification to AllowedCipherSpecs and restart the queue manager.

CSQM530E

Unsupported cipher specification in AllowedCipherSpecs list.

Severity

Explanation

The AllowedCipherSpecs list in the QMINI data set names a cipher specification that is not supported by the queue manager. It is possible that the named cipher specification is a TLS V1.3 cipher specification and the version of z/OS that the queue manager is running on does not support TLS V1.3 function.

To be able to use TLS V1.3 function, the z/OS operating system must be at V2.4 or higher.

System action

An attempt to define or alter a channel definition fails.

System programmer response

Stop the queue manager. Remove or comment out TLS V1.3 cipher specifications from the AllowedCipherSpecs list in the QMINI data set, or upgrade to a version of the z/OS operating system that supports TLS V1.3. Restart the queue manager and redefine the channel with a supported cipher specification.

CSQM550I: csect-name Switch of transmission queue for channel channel-name from old-xmitq to new-xmitq started
Severity: 0
Explanation: A switch of transmission queue for the channel identified by channel-name is required due to a change to the default cluster transmission queue configuration of the queue manager, or to the cluster channel name attribute of a cluster transmission queue. This message is issued by the queue manager when the process of switching the transmission queue from old-xmitq to new-xmitq is started.
System action: Processing continues.
System programmer response: None.

CSQM551I

csect-name Switch of transmission queue for channel channel-name completed - num-msgs messages moved from old-xmitq to new-xmitq

Severity

Explanation

A switch of transmission queue for the channel identified by channel-name was required due to a change to the default cluster transmission queue configuration of the queue manager, or to the cluster channel name attribute of a cluster transmission queue. This message is issued by the queue manager when the process of switching the transmission queue from old-xmitq to new-xmitq has completed.

During the switching process the queue manager moved num-msgs messages from old-xmitq to new-xmitq.

System action

Processing continues.

System programmer response

None.

CSQM552E

csect-name Switch of transmission queue for channel channel-name from old-xmitq to new-xmitq failed

Severity

Explanation

A switch of transmission queue for the channel identified by channel-name is required due to a change to the default cluster transmission queue configuration of the queue manager, or to the cluster channel name attribute of a cluster transmission queue. This message is issued if an error occurs when attempting to start the process of switching the transmission queue from old-xmitq to new-xmitq.

System action

The process of switching the transmission queue is not started and the channel continues to use the transmission queue old-xmitq.

The queue manager will retry to start the switching process the next time the channel starts.

System programmer response

Investigate why the process of switching the transmission queue could not be started, as reported in the preceding messages.

CSQM553I: csect-name Moving messages for channel channel-name from transmission queue old-xmitq to new-xmitq
Severity: 0
Explanation: A switch of transmission queue for the channel identified by channel-name is required due to a change to the default cluster transmission queue configuration of the queue manager, or to the cluster channel name attribute of a cluster transmission queue. This message is issued when the process of moving messages from the old transmission queue, old-xmitq, to the new transmission queue, new-xmitq, is started.
System action: Processing continues.
System programmer response: None.

CSQM554I: csect-name Moved num-msgs messages for channel channel-name from transmission queue old-xmitq to new-xmitq - remaining-msgs messages remaining
Severity: 0
Explanation: A switch of transmission queue for the channel identified by channel-name is required due to a change to the default cluster transmission queue configuration of the queue manager, or to the cluster channel name attribute of a cluster transmission queue. The switch of transmission queue requires that messages be moved from the old transmission queue, old-xmitq, to the new transmission queue, new-xmitq. This message is periodically issued to report the progress of this operation.
System action: Processing continues.
System programmer response: If this message is repeatedly issued it might indicate the old transmission queue cannot be drained of messages for the channel, which means the switching process can not complete. Applications continue to put messages to the old transmission queue during the switching process to preserve ordering. If the switching process cannot complete this might indicate that messages are being put to the old transmission queue faster than they can be moved by the switching process, or uncommitted messages remain on the old transmission queue for the channel.

CSQM555E: csect-name Moving of messages for channel channel-name from transmission queue old-xmitq to new-xmitq failed
Severity: 8
Explanation: A switch of transmission queue for the channel identified by channel-name is required due to a change to the default cluster transmission queue configuration of the queue manager, or to the cluster channel name attribute of a cluster transmission queue. The switch of transmission queue requires that messages for the channel be moved from the old transmission queue, old-xmitq, to the new transmission queue, new-xmitq. This message is issued if an error occurs while moving these messages.
System action: Moving of messages from the old transmission queue to the new transmission queue is stopped. Any existing messages on the old transmission queue and any new messages put by applications remain on the old transmission queue and are not available to be sent by the cluster-sender channel until action is taken to restart the switching process.
System programmer response: We can use preceding messages to identify and resolve the cause of the error, then restart the switching process by either stopping and starting the channel, or by using the CSQUTIL utility to restart the switching operation.

CSQM556E: csect-name Unable to open transmission queue xmitq-name for channel channel-name, MQRC=mqrc (mqrc-text)
Severity: 8
Explanation: The switch of transmission queue requires that messages for the channel be moved from the old transmission queue to the new transmission queue. This message is issued if the old transmission queue, xmitq-name, cannot be opened due to reason mqrc when attempting to perform this operation (mqrc-text provides the MQRC in textual form).
System action: The switching operation fails because the moving of messages from the old transmission queue to the new transmission queue cannot be completed.
System programmer response: We can use the reason code to identify and resolve the cause of the error, then restart the switching process by either stopping and starting the channel, or by using the CSQUTIL utility to restart the switching operation. If the error cannot be resolved, or the old transmission queue has been deleted, the CSQUTIL utility can be used to perform the switching operation without moving messages from the old transmission queue to the new transmission queue. If this option is used it is the responsibility of the IBM MQ administrator to deal with any messages for this channel on the old transmission queue.

CSQM557E: csect-name Unable to open new transmission queue xmitq-name for channel channel-name, MQRC=mqrc (mqrc-text)
Severity: 8
Explanation: The switch of transmission queue requires that messages for the channel be moved from the old transmission queue to the new transmission queue. This message is issued if the new transmission queue, xmitq-name, cannot be opened due to reason mqrc when attempting to perform this operation (mqrc-text provides the MQRC in textual form).
System action: The switching operation fails because the moving of messages from the old transmission queue to the new transmission queue cannot be completed.
System programmer response: We can use the reason code to identify and resolve the cause of the error, then restart the switching process by either stopping and starting the channel, or by using the CSQUTIL utility to restart the switching operation.

CSQM558E: csect-name Unable to persist transmission queue state for channel channel-name, MQRC=mqrc (mqrc-text)
Severity: 8
Explanation: The queue manager uses persistent messages on the queue SYSTEM.CHANNEL.SYNCQ to track which transmission queue is used by each cluster-sender channel. This message is issued if state information cannot be updated on this queue due to reason mqrc (mqrc-text provides the MQRC in textual form).
System action: The operation requiring the persisted transmission queue state to be updated fails.
System programmer response: We can use the reason code to identify and resolve the cause of the error, then review subsequent messages to identify any additional actions that are required.

CSQM559I: csect-name Loading of cluster transmission queue state started
Severity: 0
Explanation: The queue manager uses persistent messages on the queue SYSTEM.CHANNEL.SYNCQ to track which transmission queue is used by each cluster-sender channel. This message is issued during queue manager startup to indicate that loading of this information has started.
System action: Processing continues.
System programmer response: None.

CSQM560I: csect-name Loading of cluster transmission queue state completed - num-records records processed
Severity: 0
Explanation: The queue manager uses persistent messages on the queue SYSTEM.CHANNEL.SYNCQ to track which transmission queue is used by each cluster-sender channel. This message is issued during queue manager startup to indicate loading of this information has completed. The number of cluster-sender channel records that were processed is identified by num-records.
System action: Processing continues.
System programmer response: None.

CSQM561E: csect-name Loading of cluster transmission queue state failed
Severity: 8
Explanation: The queue manager uses persistent messages on the queue SYSTEM.CHANNEL.SYNCQ to track which transmission queue is used by each cluster-sender channel. This message is issued during queue manager startup to indicate that an error has occurred when loading this information.
System action: Processing continues with restricted clustering function. The queue manager is unable to determine which transmission queue should be used by each cluster-sender channel, so these channels are unable to start. Any requests to put a message to a remote cluster queue will fail with MQRC_CLUSTER_RESOURCE_ERROR.
System programmer response: Investigate why the transmission queue state information could not be loaded, as reported in preceding messages. Resolve the error, then restart the queue manager to restore clustering function. If we are unable to resolve the error contact the IBM support center.

CSQM562E: csect-name Duplicate cluster transmission queue record found for channel channel-name
Severity: 8
Explanation: The queue manager uses persistent messages on the queue SYSTEM.CHANNEL.SYNCQ to track which transmission queue is used by each cluster-sender channel. This message is issued during queue manager startup if a duplicate record is found for a channel.
System action: The duplicate record is ignored and processing continues, but the channel may use an incorrect transmission queue if the duplicated record should not have been used.
System programmer response: This condition should not occur. Contact the IBM support center.

CSQM563E

csect-name Failed to create dynamic cluster transmission queue xmitq-name, MQRC=mqrc (mqrc-text)

Severity

Explanation

A channel is required to switch to a permanent-dynamic transmission queue due to a change to the default cluster transmission queue configuration of the queue manager, or to the cluster channel name attribute of a cluster transmission queue. The queue manager could not create the permanent-dynamic transmission queue, xmitq-name, due to reason mqrc.

The cluster-sender channel that is affected can be identified from the name of the transmission queue because the queue name is in the format SYSTEM.CLUSTER.TRANSMITchannel_name.

System action

Processing continues.

System programmer response

We can use the reason code to identify and resolve the error that has prevented the permanent-dynamic cluster transmission queue from being created. Additional messages might be issued to provide further information. If the reason code is MQRC_UNKNOWN_OBJECT_NAME this means the model queue SYSTEM.CLUSTER.TRANSMIT.MODEL.QUEUE has not been defined. The definition for this model queue can be found in the supplied sample CSQ4INSX.

Refer to API completion and reason codes for information about mqrc (mqrc-text provides the MQRC in textual form).

CSQM564E

csect-name Cluster transmission model queue model-xmitq has incorrect attributes

Severity

Explanation

The queue manager failed to create a permanent-dynamic transmission queue for a cluster-sender channel because the model queue model-xmitq has been defined incorrectly.

The model queue must have the following attributes:

The USAGE attribute must be set to XMITQ
The QSGDISP attribute must not be SHARED
The DEFTYPE attribute must be set to PERMDYN
The INDXTYPE attribute must be set to CORRELID
The SHARE attribute must be set

System action

Processing continues.

System programmer response

Review and correct the definition of the model transmission queue. The definition for the model queue can be found in the supplied sample CSQ4INSX.

CSQM565E: csect-name Delivery delay processor initialization failed, reason reason-code
Severity: 8
Explanation: Initialization of the delivery delay processor task failed with the specified reason-code. As a result, any messages sent with delivery delay, using JMS 2.0, will not be processed and will be left on the delivery delay staging queue.
System action: The delivery delay processor task will end and will not restart. Messages can still be sent to the delivery delay staging queue by JMS 2.0 applications, however, the messages will not be processed until the delivery delay task is restarted. See system programmer response for instructions on how to restart the delivery delay processor.
System programmer response: The most likely reason for this message is a shortage of storage below the bar, in which case reason-code will be 4. Review the amount of storage used below the bar, and if possible try and reduce it. We can attempt to restart the delivery delay processor by altering the delivery delay staging queue state from 'get enabled' to 'get inhibited', and back to the 'get enabled' state again.

CSQM566I: csect-name Delivery delay processor started
Severity: 0
Explanation: The delivery delay processor has started and is available to process messages from the delivery delay staging queue.
System action: Processing continues.
System programmer response: None.

CSQM567I

csect-name Delivery delay processor stopped

Severity

Explanation

The delivery delay processor has stopped and is no longer available to process messages from the delivery delay staging queue. This message is output in the following situations:

The queue manager is shutting down.
The delivery delay staging queue has been deleted, or does not exist.

System action

Processing continues.

System programmer response

None.

CSQM568E: csect-name Delivery delay processor ended abnormally, MQRC=mqrc
Severity: 4
Explanation: The delivery delay processor has detected an error, indicated by mqrc, and has shut down.
System action: The delivery delay processor task ends and will not restart. Messages can still be sent to the delivery delay staging queue by JMS 2 applications, however, they will not be processed until the delivery delay task is restarted. See system programmer response for instructions on how to restart the delivery delay processor.
System programmer response: This message is output for many reasons, some of which will be expected and some will not. For example, if the delivery delay staging queue state is altered to 'get inhibited' this message will be output, and mqrc will be MQRC_GET_INHIBITED. If the message is expected then no action is required. If the message is unexpected use the value of mqrc, and any other messages to attempt to rectify the situation. We can attempt to restart the delivery delay processor by altering the delivery delay staging queue state from 'get enabled' to' get inhibited', and back to the 'get enabled' state again.

CSQM569I: csect-name Delivery delay processor failed to get a message with correlation ID correlid, MQRC=mqrc (mqrc-text)
Severity: 4
Explanation: The delivery delay processor attempted to perform a destructive MQGET for the message with the specified correlation ID from the delivery delay staging queue, SYSTEM.DDELAY.LOCAL.QUEUE. The message was no longer on the queue.
System action: Processing continues.
System programmer response: Investigate whether the message was taken off the delivery delay staging queue for a valid reason, for example, it was put there by mistake. Validate the security settings for the delivery delay staging queue to ensure that only authorized users have access to it.

CSQM570E

csect-name Delivery delay processor failed to process a message with correlation ID correlid, for queue q-name, according to its report options report-options, MQRC=mqrc (mqrc-text)

Severity

Explanation

The delivery delay processor could not put the specified message to the specified queue and, so, was attempting to either send the message to the dead-letter-queue or discard the message according to the disposition options specified in the report field of the message.

The message might have also requested an exception report. Some part of the processing of the disposition options, or the report, failed with the specified return code.

System action

The message is rolled back to the delivery delay staging queue, SYSTEM.DDELAY.LOCAL.QUEUE, and reprocessed at a time decided by the system.

System programmer response

Use the information from the message to establish the cause of the problem. Some possible explanations are:

The specified queue might no longer exist, be full, or be put disabled.
If the message should have been put to the dead-letter-queue, check that the dead-letter-queue is defined, is not full, and is put enabled.
If an exception report message was to be generated, check that the queue the report was to be put to is defined, is not full, is put enabled, and that the user ID in the message has access to the queue.

Otherwise, check that the dead-letter-queue is defined, is not full, and is put enabled.

CSQM571I

csect-name Delivery delay processor received an unexpected message with message ID msgid

Severity

Explanation

The delivery delay processor received a message from the delivery delay staging queue, SYSTEM.DDELAY.LOCAL.QUEUE, that was not in the correct format.

The delivery delay processor either sends the message to the dead-letter-queue, or discards it according to the disposition options specified in the report field of the message.

System action

The delivery delay processor either sends the message to the dead-letter-queue, or discards it according to the disposition options specified in the report field of the message. If the message specified an exception report, this will be generated.

System programmer response

Investigate why unexpected messages are being sent to the delivery delay staging queue. Validate the security settings for the delivery delay staging queue to ensure that only authorized users have access to it.

CSQM572E: Insufficient storage to parse data set data set
Severity: 8
Explanation: The queue manager could not obtain sufficient storage to parse the specified data set.
System action: The queue manager terminates during start up.
System programmer response: Investigate and resolve the reason for storage shortage and restart the queue manager

CSQM573E: Unable to parse line line in data set data set
Severity: 8
Explanation: The queue manager could not parse the specified line in the specified data set.
System action: The queue manager is unable to parse the specified data set but continues with initialization. It will not be possible to start TLS/SSL enabled channels.
System programmer response: Stop the queue manager and resolve any issues with the contents of the specified data set. Restart the queue manager and ensure that the queue manager is able to successfully parse the data set.

CSQM574E

Incorrect value value for key key in stanza stanza, data set data set, around line line

Severity

Explanation

The specified key (keyword) in the specified stanza and data set is not valid.

System action

The queue manager is unable to parse the specified data set but continues with initialization. It will not be possible to start TLS/SSL enabled channels.

System programmer response

Stop the queue manager and resolve any issues with the contents of the specified data set. Restart the queue manager and ensure that the queue manager is able to successfully parse the data set.

CSQM575E: Incorrect or duplicate key key in stanza stanza, data set data set, around line line
Severity: 8
Explanation: The specified key (keyword) in the specified stanza and data set is either not valid or has been entered more than once.
System action: The queue manager is unable to parse the specified data set but continues with initialization. It will not be possible to start TLS/SSL enabled channels.
System programmer response: Stop the queue manager and resolve any issues with the contents of the specified data set. Restart the queue manager and ensure that the queue manager is able to successfully parse the data set.

CSQM576E: Incorrect cipher specification name name in key key, stanza stanza data set data set, around line line
Severity: 8
Explanation: The specified cipher specification in the specified key, stanza and data set is not valid.
System action: The queue manager is unable to parse the specified data set but continues with initialization. It will not be possible to start TLS/SSL enabled channels.
System programmer response: Stop the queue manager and resolve any issues with the contents of the specified data set. Restart the queue manager and ensure that the queue manager is able to successfully parse the data set.

CSQM577E

Cipher specification name name in key key, in stanza stanza, data set data set, around line line is not supported

Severity

Explanation

The specified cipher specification in the specified key, stanza and data set is not supported.

System action

The queue manager is unable to parse the specified data set but continues with initialization. It will not be possible to start TLS/SSL enabled channels.

System programmer response

Stop the queue manager and define only supported cipher specification names in the specified data set. Restart the queue manager and ensure that the queue manager is able to successfully parse the data set.

CSQM578I: Data set data set read and parsed successfully
Severity: 0
Explanation: The queue manager has successfully read and parsed the specified data set.
System action: The queue manager continues with initialization.
System programmer response: None.

CSQM579E: Version of z/OS does not support TLS V1.3, in key key, stanza stanza, data set data set, around line line
Severity: 8
Explanation: TLS V1.3 properties have been defined in the specified key, stanza and data set however, the version of z/OS that the queue manager is being run on does not support TLS V1.3 function. To be able to use TLS V1.3 function, the z/OS operating system must be at V2.4 or higher.
System action: The queue manager is unable to parse the specified data set but continues with initialization. It will not be possible to start TLS/SSL enabled channels.
System programmer response: Stop the queue manager and remove or comment out TLS V1.3 properties from the specified data set, or upgrade to a version of the z/OS operating system that supports TLS V1.3. Restart the queue manager and ensure that the queue manager is able to successfully parse the data set.

CSQM580I: csect-name Cluster object name object_name located at QMID qmid_name is resolved using old cached information.
Severity: 0
Explanation: The cluster object referenced has been resolved using old cached information.
System action: Processing continues.
System programmer response: None.

CSQM581E: Error getting data from data set data set
Severity: 8
Explanation: The queue manager has not been able to read data from the specified data set.
System action: The queue manager is unable to parse the specified data set but continues with initialization. It will not be possible to start TLS/SSL enabled channels.
System programmer response: Stop the queue manager and resolve any issues with the contents of the data set. Restart the queue manager and ensure that the queue manager is able to successfully parse the data set.

CSQM582E

Unexpected error when accessing data set data set, reason reason

Severity

Explanation

The queue manager has encountered an unexpected error while accessing the specified data set.

System action

The queue manager is unable to parse the specified data set but continues with initialization. It will not be possible to start TLS/SSL enabled channels.

System programmer response

Investigate and resolve the reason for the failure. Restart the queue manager and ensure that the queue manager is able to successfully parse the data set.

If necessary, collect and gather diagnostic data, and contact the IBM support center.

CSQM583E: Error during open or close of data set data set
Severity: 8
Explanation: The queue manager encountered an error while attempting to open or close the specified data set.
System action: The queue manager is unable to parse the specified data set but continues with initialization. It will not be possible to start TLS/SSL enabled channels.
System programmer response: Stop the queue manager and ensure that the data set is defined and valid. Restart the queue manager and ensure that the queue manager is able to successfully parse the data set.

CSQM584E: Unsupported stanza skipped, stanza stanza, in data set data set
Severity: 8
Explanation: The queue manager encountered an unsupported stanza in the specified data set. The stanza has been ignored.
System action: The queue manager ignores the stanza and continues to parse the remainder of the specified data set.
System programmer response: At some point, you might want to stop the queue manager, remove or comment out the unsupported stanza, restart the queue manager and ensure that the queue manager is able to successfully parse the data set.

CSQM999E: csect-name UNRECOGNIZED RETURN CODE ret-code FOR 'keyword'
Severity: 8
Explanation: An unexpected return code was issued from a command, relating to the named keyword.
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.

Parent topic: Messages for IBM MQ for z/OS