Message manager messages (CSQM...)

csect-name MSTR user ID cannot invoke USS callable services

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.

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

Refer to Planning 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.

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

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.

Processing continues. The IGQ agent starts asynchronously.

csect-name Intra-group queuing agent stopping

The IGQ agent stops.

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

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

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.

Processing continues.

csect-name Shared channel recovery terminated, Db2® not available

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

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.

csect-name Shared channel recovery terminated, error accessing Db2

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

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.

csect-name Shared channel recovery terminated, error putting command, MQRC=mqrc (mqrc-text)

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

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.

csect-name mqapi-call failed for queue q-name, MQRC=mqrc (mqrc-text)

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

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.

For more information, see API completion and 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.

csect-name MQPUT of trigger message failed for queue q-name, MQRC=mqrc (mqrc-text)

The queue manager could not deliver a trigger message to the indicated initiation queue for the specified IBM MQ reason code (MQRC_).

The queue manager attempts to put the trigger message on to the dead-letter queue if one has been defined.

For more information about IBM MQ reason codes, and what action to take to correct the problem with the initiation queue, see API completion and reason codes.

csect-name Unable to start channel channel-name

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.

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.

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.

csect-name Queue q-name has incorrect attributes

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

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

Redefine the queue with the correct attributes.

csect-name Cluster cache is full

No more space is available in the cluster cache area.

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.

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

Consider changing the cluster cache type system parameter CLCACHE to dynamic, so that more space for the cache will be obtained automatically as required. (If you are using a cluster workload exit, ensure that it supports a dynamic cluster cache.) For information about the system parameters for the CSQ6SYSP macro, see Using CSQ6SYSP.

csect-name Cluster workload exit exit-name does not support dynamic cache

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.

The cluster workload exit is suppressed.

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.

csect-name INDXTYPE(index-type) not allowed for shared transmission queue shared-xmitq

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.

Processing continues.

Modify the INDXTYPE attribute for the shared transmission queue to NONE or MSGID.

csect-name Specified dead-letter queue name is unacceptable

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.

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.

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.

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

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.

Processing continues.

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.

csect-name mqapi-call failed, MQRC=mqrc (mqrc-text)

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

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.

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

csect-name Intra-group queuing agent ended abnormally. Restarting

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

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

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

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

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.

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

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.

csect-name Queue q-name unavailable, n events not generated

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.

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.

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.

csect-name Queue q-name, n events recovered

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.

Processing continues.

csect-name Loading of durable subscribers started

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.

Processing continues.

csect-name Loading of durable subscribers finished

The queue manager has finished reloading all of the durable subscribers.

Processing continues.

csect-name Consolidation of durable subscribers started

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.

Processing continues.

csect-name Consolidation of durable subscribers finished

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.

Processing continues

csect-name PUBLISH/SUBSCRIBE ENGINE HAS SHUTDOWN

The publish/subscribe engine has been shutdown.

The publish/subscribe engine has shutdown.

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.

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

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.

IBM MQ API request fails with return code MQRC_STORAGE_NOT_AVAILABLE 2071

Queue manager processing continues

csect-name Policy access attempt rejected due to incompatible AMS version, jobname jobname

An incompatible version of Advanced Message Security (AMS), identified by jobname, attempted to open the policy queue, SYSTEM.PROTECTION.POLICY.QUEUE.

The request to open the policy queue is rejected.

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 IBM WebSphere MQ Advanced Message Security for z/OS.

csect-name COMMAND INHIBITED DURING RESTART/TERMINATION

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.

Message CSQM085I is also issued and the command is ignored.

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.

csect-name ABNORMAL COMPLETION

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

The command is not actioned.

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

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

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

The queue manager fails to restart.

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 your IBM support center.

csect-name FAILURE REASON CODE reason-code

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.

The command is ignored.

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 your IBM support center.

csect-name FAILURE MQRC=mqrc (mqrc-text)

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.

The command is ignored.

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.

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

The command is ignored.

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

csect-name keyword(value) NAME CONTAINS INVALID CHARACTERS

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.

The command is ignored.

Reissue the command with the correct name. For more information about the command, see MQSC commands.

csect-name keyword(value) WAS NOT FOUND

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.

The command is ignored.

csect-name keyword(value) existing-disposition ALREADY EXISTS

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. (You cannot have a locally-defined object and a local copy of a group object with the same name; for local queues, you cannot have a shared queue with the same name as a queue with any other disposition.) Where applicable, existing-disposition identifies the QSG disposition of the existing object.

The command is ignored.

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

csect-name keyword(value) NAME HAS INVALID LENGTH

A name was specified that is of an incorrect length.

The command is ignored.

Reissue the command with a name of the correct length. For more information about the command, see MQSC commands.

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

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

The command is ignored.

Reissue the command with a non-blank name. For more information about the command, see MQSC commands.

csect-name keyword(value) FIELD TOO LONG

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.

The command is ignored.

Reissue the command with the correct field length. For more information about the command, see MQSC commands.

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

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. (You cannot have a locally-defined object and a local copy of a group object with the same name; for local queues, you cannot have a shared queue with the same name as a queue with any other disposition.)

The command is ignored.

Reissue the command with the correct name and subtype. For more information about the command, see MQSC commands.

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

The command is ignored.

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

csect-name keyword(value) IS CURRENTLY IN USE

The command is ignored.

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.

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

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

The command is ignored.

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, you must issue the request specifying PURGE explicitly for the local copy; specifying PURGE on the request to delete the group object has no effect.

csect-name keyword(value) FLAGGED FOR DEFERRED DELETION

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.

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

csect-name 'keyword' VALUE IS SAME AS QALIAS NAME

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.

The command is ignored.

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

csect-name DEFXMITQ( q-name) IS NOT ALLOWED

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

The command is ignored.

Reissue the command with a different DEFXMITQ name.

csect-name STGCLASS ACTIVE OR QUEUE IN USE

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.

The command is ignored.

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

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

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

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:

The command is ignored.

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

csect-name DYNAMIC QUEUE value NOT DELETED, MQRC=mqrc (mqrc-text)

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.

The named dynamic queue is not deleted.

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

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

The command is ignored.

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

csect-name COULD NOT PUT TO THE DEAD QUEUE, MQRC=mqrc (mqrc-text)

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

Processing continues.

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.

csect-name ERROR ACCESSING keyword(value)

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.

The command is ignored.

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, an explanation of the mqrc in that message, and what action to take, is given in API completion and reason codes.

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

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

The command is not actioned.

csect-name keyword(value) EXCEEDED LOCAL QUEUE LIMIT

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.

The command is not actioned.

Delete any existing queues that are no longer required.

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

The command is ignored.

For more information about the command, see MQSC commands.

csect-name ERROR ACCESSING keyword(value) QSGDISP(disposition)

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.

The command is ignored.

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.

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

Processing of the command is terminated.

For information about migration and compatibility between releases, see Migrating.

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

Processing of the command is terminated.

For information about migration and compatibility between releases, see Migrating.

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

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.

Processing of the command is terminated.

Reissue the command correctly.

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

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

Processing of the command is terminated.

Reissue the command correctly.

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

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

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.

csect-name 'keyword' VALUE CANNOT BE CHANGED

The value for the specified attribute cannot be changed.

Processing of the command is terminated.

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

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

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

Processing of the command is terminated.

Reissue the command correctly.

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

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.

The command is ignored.

csect-name 'keyword' ONLY APPLICABLE TO LU62 PROTOCOL

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

Processing of the command is terminated.

Reissue the command without the named keyword.

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

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

Processing of the command is terminated.

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

csect-name MQPUT FAILED FOR QUEUE q-name, MQRC=mqrc (mqrc-text)

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

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.

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.

csect-name keyword(value) HAS WRONG CHANNEL TYPE

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.

The command is not actioned.

Check that the correct channel name and disposition was specified on the command. For more information about the command, see MQSC commands.

csect-name CLUSTER REQUEST QUEUED

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.

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

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

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

The command is not actioned.

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

csect-name CHANNEL INITIATOR ALREADY ACTIVE

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

The command is not actioned.

csect-name UNABLE TO START CHANNEL INITIATOR

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

The command is not actioned.

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

csect-name command keyword(value) COMMAND ACCEPTED

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.

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

csect-name NO CHANNEL INITIATOR AVAILABLE

The command is not actioned.

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.

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

The command is not actioned.

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

csect-name command keyword COMMAND ACCEPTED

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.

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

csect-name CHANNEL INITIATOR STARTING

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

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

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

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.

Processing of the command is terminated.

Reissue the command with correct values.

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

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

The command is not actioned.

Reissue the command with the correct keywords.

csect-name 'LUNAME' REQUIRED WITH TRPTYPE(LU62)

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

The command is not actioned.

Reissue the command with the correct keywords.

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

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.

Processing of the command is terminated.

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

csect-name CLUSTER TOPICS INHIBITED DUE TO PSCLUS(DISABLED)

An attempt was made to define a cluster topic when the PSCLUS queue manager attribute is set to DISABLED.

Processing of the command is terminated.

If you wish to enable publish/subscribe clustering, alter the PSCLUS attribute on all queue managers in the cluster to ENABLED.

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

Processing of the command is terminated.

Reissue the command with the correct values.

csect-name 'keyword' VALUE REQUIRED FOR SHARED QUEUE

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.

Processing of the command is terminated.

Reissue the command with a value for the keyword added.

csect-name keyword(value) VALUE IS REPEATED

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

The command is ignored.

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

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

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.

Processing of the command is terminated.

Reissue the command with correct values.

csect-name 'keyword' NOT ALLOWED WITH TYPE 'value'

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

Processing of the command is terminated.

Reissue the command without the named keyword.

csect-name 'keyword' REQUIRED WITH TYPE 'value'

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

Processing of the command is terminated.

Reissue the command with the named keyword added.

csect-name 'keyword1' AND 'keyword2' VALUES ARE INCOMPATIBLE

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

Processing of the command is terminated.

Reissue the command with correct values. For information about the restrictions on the values for the keywords, see MQSC commands.

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

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.

Processing of the command is terminated.

Reissue the command with correct values.

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

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.

Processing of the command is terminated.

Reissue the command with correct values.

csect-name Db2 NOT AVAILABLE

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

Processing of the command is terminated.

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.

csect-name ERROR ACCESSING Db2

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

Processing of the command is terminated.

Resolve the error reported in the preceding messages.

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

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.

Processing of the command is terminated.

Reissue the command with correct values.

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

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.

Processing of the command is terminated.

Reissue the command with correct values.

csect-name NO SPACE FOR keyword(value)

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

The command is not actioned.

Reduce the number of application structures you are using.

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

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.

Processing of the command is terminated.

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

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

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.

Processing of the command is terminated.

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.

csect-name keyword(value) IS NOT UNIQUE

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.

The command is not executed.

Delete one of the objects.

csect-name QUEUE ATTRIBUTES ARE INCOMPATIBLE

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.

The command is not executed.

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

csect-name keyword(value) MAXDEPTH IS TOO SMALL

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.

The command is not executed.

Change the MAXDEPTH value for the queue.

csect-name ERROR USING keyword(value), MQRC=mqrc (mqrc-text)

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.

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.

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.

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

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

The command is not executed.

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.

csect-name n MESSAGES MOVED

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.

Processing continues.

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

csect-name keyword(value) NOT AUTHORIZED

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

The command is not executed for that object.

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.

csect-name PERFORMANCE EVENTS DISABLED

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

The command is not executed.

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

csect-name CONFIGURATION EVENTS DISABLED

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

The command is not executed.

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

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

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.

Processing continues.

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.

csect-name REFRESHING CONFIGURATION EVENTS SINCE date time

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.

csect-name CONFIGURATION EVENTS REFRESH NEEDED

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.

Processing continues.

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

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

Processing of the command is terminated.

Reissue the command without the named keyword.

csect-name EXPIRED MESSAGE SCAN REQUESTED FOR m QUEUES

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

Processing continues.

csect-name 'keyword' is not allowed with CFLEVEL(cflevel) - this keyword requires CFLEVEL(5)

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.

Processing for the command is terminated.

Issue the command again with correct values. You cannot alter the level of a CF structure; you must delete the structure, and then define it again.

csect-name 'keyword' cannot be altered because a data set is currently active for this structure

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.

Processing for the command is terminated.

Verify the command entry and reissue the command correctly.

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

Processing for the command is terminated.

Verify the command entry, and reissue the command correctly.

csect-name 'keyword' NOT ALLOWED WITH ACTION 'value'

The named keyword cannot be specified for channel authentication settings of the action shown.

Processing for the command is terminated.

Reissue the command without the named keyword.

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

Processing of the command is terminated.

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

csect-name CHANNEL WILL RUN USING MCAUSER(userid)

csect-name INSUFFICIENT STORAGE TO COMPLETE COMMAND

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

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

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

csect-name DURABLE SUBSCRIPTIONS NOT ALLOWED

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

The command is not executed.

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.

csect-name SUBSCRIPTION INHIBITED

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

The command is not executed.

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.

csect-name 'keyword1' AND 'keyword2' VALUES CANNOT BOTH BE BLANK

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.

Processing of the command is terminated.

Reissue the command with correct values.

csect-name SUBSCRIPTION HAS FIXED SUBUSER

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.

The command is not executed.

The subscription can be altered only by the owning userid that is displayed in the SUBUSER attribute.

csect-name DESTCLAS VALUE CANNOT BE ALTERED

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.

The command is not executed.

Ensure that the DESTCLAS attribute matches the existing subscription and rerun the request.

csect-name GROUPING VALUE CANNOT BE ALTERED

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.

The command is not executed.

Ensure that the GROUPING attribute matches the existing subscription and rerun the request.

csect-name SUBSCOPE VALUE CANNOT BE ALTERED

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.

The command is not executed.

Ensure that the SUBSCOPE attribute matches the existing subscription and rerun the request.

csect-name SELECTOR VALUE CANNOT BE ALTERED

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.

The command is not executed.

Ensure that the SELECTOR attribute matches the existing subscription and rerun the request.

csect-name TOPIC STRING IS INVALID

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

The command is not executed.

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.

csect-name TOPIC STRING CANNOT BE ALTERED

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.

The command is not executed.

Reissue the command with correct values. You cannot alter the topic string in a topic object; you must delete the object and then redefine it.

csect-name Address 'address' is invalid.

The IP address or hostname address contains invalid characters.

Processing of the command is terminated.

Reissue the command with the parameter specified correctly. Note that the BLOCKADDR list may contain only IP addresses: host name addresses are not permitted.

csect-name IP address 'ipaddress' contains an invalid range.

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.

Processing of the command is terminated.

Reissue the command with the parameter specified correctly.

csect-name IP address 'ipaddress1' overlaps existing IP address 'ipaddress2'.

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.

Processing of the command is terminated.

Reissue the command with the parameter specified correctly.

csect-name MATCH RUNCHECK FOUND A GENERIC VALUE IN field-name

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.

Processing of the command is terminated.

Reissue the command with a value in field-name which is not generic.

csect-name REQUIRED KEYWORD MISSING FOR keyword(value)

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

Processing of the command is terminated.

Reissue the command specifying one of the required keywords

csect-name 'keyword' NOT ALLOWED WITH MATCH 'value'

The named keyword cannot be specified for DISPLAY CHLAUTH in conjunction with the identified value for the MATCH keyword.

Processing of the command is terminated.

Reissue the command without the named keyword.

csect-name CHANNEL AUTHENTICATION PROFILE NAME IS INVALID

The channel profile name used in the command was not valid.

Processing of the command is terminated.

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

csect-name CFCONLOS (TOLERATE) NOT ALLOWED, INCOMPATIBLE QUEUE MANAGER CMDLEVELS

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.

Processing of the command is terminated.

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.

csect-name verb-name obj-type DETAILS

  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.

  obj-type TERMINATED WITH MAX LINES 

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

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.

csect-name PUBLISH/SUBSCRIBE ENGINE IS DISABLED

The publish/subscribe engine is unavailable because it has been disabled.

The command is actioned, but no results are returned because the publish/subscribe engine has been disabled.

This message occurs because you 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.

csect-name m obj-type FOUND MATCHING REQUEST CRITERIA

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

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

csect-name CANNOT GET INFORMATION FROM Db2

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.

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

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

csect-name UNEXPECTED ERROR DURING DISPLAY

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

The command is terminated.

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

csect-name NO item FOUND MATCHING REQUEST CRITERIA

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

csect-name TOTAL MESSAGE LENGTH ALLOWED ON CONSOLE EXCEEDED

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

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

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

csect-name INSUFFICIENT STORAGE TO COMPLETE DISPLAY

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

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.

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 your system.

object details

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:

csect-name GROUPUR agent starting TCB=tcb-name

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.

Processing continues. The GROUPUR agent is started.

csect-name GROUPUR agent stopping

The GROUPUR agent stops.

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

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

csect-name processed BACKOUT request from qmgr-name for in-doubt UOW, URID=urid, CONNECTION-NAME=name

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.

Processing continues.

csect-name processed COMMIT request from qmgr-name for in-doubt UOW, URID=urid, CONNECTION-NAME=name

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.

Startup continues.

csect-name GROUPUR support enabled

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.

The queue manager permits applications to establish transactions with a GROUP unit of recovery disposition.

csect-name GROUPUR support disabled

This message is generated during queue manager startup or in response to an ALTER QMGR command if the GROUPUR queue manager attribute is disabled.

The queue manager inhibits applications from establishing transactions with a GROUP unit of recovery disposition.

csect-name GROUPUR qmgr attribute has been disabled CODE=code

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.

The GROUPUR queue manager attribute is disabled.

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.

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

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.

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

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. You 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). You can use this code to identify the failing check using the following list:

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

csect-name GROUPUR agent ended abnormally. Restarting

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

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

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.

csect-name PSCLUS CANNOT BE ALTERED, CLUSTER TOPICS EXIST

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.

Processing of the command is terminated.

If you wish to disable publish/subscribe clustering delete all cluster topic objects before altering the PSCLUS attribute on all queue managers in the cluster to DISABLED.

csect-name CLCHNAME MUST BE BLANK FOR DYNAMIC QUEUE

An attempt was made to define or alter a dynamic queue with a non blank value for the CLCHNAME attribute, which is not allowed.

Processing of the command is terminated.

Reissue the command with compatible attribute values.

csect-name NOSHARE NOT ALLOWED WITH NON-BLANK CLCHNAME

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.

Processing of the command is terminated.

Reissue the command, specifying either SHARE or a blank value for the CLCHNAME attribute.

csect-name CLUSTER OR CLROUTE CANNOT CURRENTLY BE ALTERED

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.

Processing of the command is terminated.

csect-name CLROUTE CONFLICT DETECTED FOR CLUSTER TOPIC

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.

Processing of the command is terminated.

Review the cluster routing requirements for the topic tree, then correct and reissue the command.

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

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.

Processing of the operation is terminated.

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.

csect-name CERTIFICATE LABEL NOT ALLOWED FOR SSL 3.0 CHANNEL

An attempt was made to specify a certificate label for an inbound channel that uses a SSL 3.0 CipherSpec, which is not allowed. Certificate labels for inbound channels are only supported for TLS channels.

Processing of the command is terminated.

If you need to configure a certificate label, alter the channel to use a TLS CipherSpec.

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

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.

Processing continues.

None.

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

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.

Processing continues.

None.

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

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.

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.

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

csect-name Moving messages for channel channel-name from transmission queue old-xmitq to new-xmitq

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.

Processing continues.

None.

csect-name Moved num-msgs messages for channel channel-name from transmission queue old-xmitq to new-xmitq - remaining-msgs messages remaining

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.

Processing continues.

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.

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

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.

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.

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

csect-name Unable to open transmission queue xmitq-name for channel channel-name, MQRC=mqrc (mqrc-text)

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

The switching operation fails because the moving of messages from the old transmission queue to the new transmission queue cannot be completed.

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

csect-name Unable to open new transmission queue xmitq-name for channel channel-name, MQRC=mqrc (mqrc-text)

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

The switching operation fails because the moving of messages from the old transmission queue to the new transmission queue cannot be completed.

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

csect-name Unable to persist transmission queue state for channel channel-name, MQRC=mqrc (mqrc-text)

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

The operation requiring the persisted transmission queue state to be updated fails.

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

csect-name Loading of cluster transmission queue state started

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.

Processing continues.

None.

csect-name Loading of cluster transmission queue state completed - num-records records processed

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.

Processing continues.

None.

csect-name Loading of cluster transmission queue state failed

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.

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.

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 you are unable to resolve the error contact your IBM support center.

csect-name Duplicate cluster transmission queue record found for channel channel-name

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.

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.

This condition should not occur. Contact your IBM support center.

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

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.TRANSMIT<channel name>.

Processing continues.

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

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

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.

Processing continues.

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

csect-name Delivery delay processor initialization failed, reason reason-code

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.

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

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

csect-name Delivery delay processor started

The delivery delay processor has started and is available to process messages from the delivery delay staging queue.

Processing continues.

None.

csect-name Delivery delay processor stopped

Processing continues.

None.

csect-name Delivery delay processor ended abnormally, MQRC=mqrc

The delivery delay processor has detected an error, indicated by mqrc, and has shut down.

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.

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

csect-name Delivery delay processor failed to get a message with correlation ID correlid, MQRC=mqrc (mqrc-text)

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.

Processing continues.

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.

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)

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.

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

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

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.

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.

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.

csect-name Cluster object name object_name located at QMID qmid_name is resolved using old cached information.

The cluster object referenced has been resolved using old cached information.

Processing continues.

None.

csect-name UNRECOGNIZED RETURN CODE ret-code FOR 'keyword'

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

The command is ignored.

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