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.
0
Processing continues. The IGQ agent starts asynchronously.
The intra-group queuing (IGQ) agent is stopping because:
0
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).
The queue manager successfully recovered some shared channels that were owned by queue manager qmgr-name in the queue-sharing group when it or its channel initiator terminated abnormally. This recovery process may occur when:
n channels were found that needed recovery, of which p were originally started as FIXSHARED. The number recovered, r, may be less than n (or even 0) because other active queue managers are also recovering the channels and because FIXSHARED channels cannot be recovered by another queue manager.
See the WebSphere MQ Intercommunication manual for more information about shared channel recovery.
0
Processing continues.
Because DB2 is not available or no longer available, the queue manager was unable to recover some shared channels that were owned by a queue manager in the queue-sharing group when it or its channel initiator terminated abnormally. This recovery process may occur when:
8
The recovery process is terminated; some channels may 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.
Because there was an error in accessing DB2, the queue manager was unable to recover some shared channels that were owned by a queue manager in the queue-sharing group when it or its channel initiator terminated abnormally. This recovery process may occur when:
8
The recovery process is terminated; some channels may 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.
Because there was an error putting a message on the system-command input queue, the queue manager was unable to recover some shared channels that were owned by a queue manager in the queue-sharing group when it or its channel initiator terminated abnormally. This recovery process may occur when:
8
The recovery process is terminated; some channels may have been recovered, while others have not.
Refer to Appendix A. API completion and reason codes for information about mqrc, and resolve the error. Any channels that were not recovered will be recovered when the recovery process next runs; alternatively, they can be restarted manually.
The indicated MQ API call for the named queue, failed for the specified reason, which may be an MQ reason code (MQRC_) or a signal completion code (MQEC_).
8
If the queue is SYSTEM.ADMIN.CONFIG.EVENT or SYSTEM.ADMIN.COMMAND.EVENT, processing continues but events are not generated; message CSQM071E follows to show how many event messages have not been generated since the problem first occurred. These messages are generated on the first occurrence of the problem, and at intervals thereafter while the problem persists.
For other queues, it is the intra-group queuing (IGQ) agent that issued the call. Depending on the queue involved and the type of error, it may continue processing, retry the request at regular intervals until the error is corrected, or terminate.
Refer to Appendix A. API completion and reason codes for information about MQ reason codes or the WebSphere MQ Application Programming Reference manual for information about signal completion codes. Correct the problem with the queue, or use the ALTER QMGR command to disable the events or the IGQ agent if the function is not required.
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).
8
The IGQ agent retries at regular intervals until the error is corrected.
Redefine the queue with the correct attributes.
No more space is available in the cluster cache area.
8
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.) See the CSQ6SYSP macro in the WebSphere MQ for z/OS System Setup Guide for information about the system parameters.
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.
8
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. See the CSQ6SYSP macro in the WebSphere MQ for z/OS System Setup Guide for information about the system parameters.
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.
4
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.
The indicated MQ API call failed for the specified reason, which is an MQ reason code (MQRC_).
8
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 Appendix A. API completion and reason codes for information about MQ reason codes. Correct the problem if required.
The intra-group queuing (IGQ) agent has ended abnormally because a severe error occurred, as reported in the preceding messages.
8
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.
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.
4
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.
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.
8
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.
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.
0
Processing continues.
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.
8
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 reoccur.
This message is issued with message CSQM084I, and indicates that the command requested has not been actioned.
8
The command is not actioned.
Wait until the queue manager is in a state where it is possible to use the prohibited commands.
During restart, the creation of the queue manager object has failed. The reason code is of the form '00D44xxx'.
8
The queue manager fails to restart.
Refer to Message manager codes (X'D4') for an explanation of the reason code, and what action to take. Reissue the START QMGR command to restart the queue manager. If the error persists note this reason code, and contact your IBM support center.
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.
8
The command is ignored.
See the explanations of the accompanying messages for more information. Refer to Message manager codes (X'D4') for an explanation of the reason code, and what action to take. If the reason code is not one of those listed, make a note of it and contact your IBM support center.
A command has failed. The reason code is an MQ reason code. This message is accompanied by one or more other more specific messages, which indicate the reason for the failure.
8
The command is ignored.
See the explanations of the accompanying messages for more information. Refer to Appendix A. API completion and reason codes for an explanation of mqrc, and what action to take.
Either:
8
The command is ignored.
Reissue the command with the parameter specified correctly. For more information about the command, see the WebSphere MQ Script (MQSC) Command Reference manual.
A name was specified that contains one or more invalid characters. See the WebSphere MQ Script (MQSC) Command Reference manual for information about validation required for the name in question to correct this.
8
The command is ignored.
Reissue the command with the correct name. For more information about the command, see the WebSphere MQ Script (MQSC) Command Reference manual.
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.
8
The command is ignored.
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.
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.)
8
The command is ignored.
Reissue the command with another name or with the REPLACE option, or use the existing object, as appropriate.
A name was specified that is of an incorrect length.
8
The command is ignored.
Reissue the command with a name of the correct length. For more information about the command, see the WebSphere MQ Script (MQSC) Command Reference manual.
A name was specified that is blank. This is not allowed.
8
The command is ignored.
Reissue the command with a non-blank name. For more information about the command, see the WebSphere MQ Script (MQSC) Command Reference manual.
Either a numeric or character parameter was specified but it is too long, or (if value is blank) a list of character parameters was specified whose total length is too long.
8
The command is ignored.
Reissue the command with the correct field length. For more information about the command, see the WebSphere MQ Script (MQSC) Command Reference manual.
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.)
8
The command is ignored.
Reissue the command with the correct name and subtype. For more information about the command, see the WebSphere MQ Script (MQSC) Command Reference manual.
Either:
8
The command is ignored.
Reissue the command with the parameter specified correctly. For more information about the command, see the WebSphere MQ Script (MQSC) Command Reference manual.
The object specified is in use. This could be because:
8
The command is ignored.
Either:
It is not possible to use the FORCE option of the ALTER command to overcome the situations that cause this message.
For more information about the command, see the WebSphere MQ Script (MQSC) Command Reference manual.
A local queue specified for deletion has messages associated with it, and the DELETE request did not include the PURGE option.
8
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.
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.
8
The queue is no longer available to new users, and will be deleted when all existing users of it have relinquished access.
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.
8
The command is ignored.
Reissue the command with a different name for the TARGQ keyword.
The specified queue is not allowed to be used as the default transmission queue because it is reserved for use exclusively by clustering.
8
The command is ignored.
Reissue the command with a different DEFXMITQ name.
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.
8
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.
An attempt was made to issue a DEFINE command on a reserved object name, using an incorrect object type or subtype. The object is only allowed to be of the predetermined type listed below:
Type | Object |
---|---|
Any Queue | SYSTEM.ADMIN.ACTIVITY.QUEUE SYSTEM.ADMIN.CHANNEL.EVENT SYSTEM.ADMIN.COMMAND.EVENT SYSTEM.ADMIN.CONFIG.EVENT SYSTEM.ADMIN.PERFM.EVENT SYSTEM.ADMIN.QMGR.EVENT SYSTEM.ADMIN.TRACE.ROUTE.QUEUE |
Alias queue | SYSTEM.DEFAULT.ALIAS.QUEUE |
Alias or local queue | SYSTEM.ADMIN.COMMAND.QUEUE SYSTEM.COMMAND.INPUT |
Local queue | SYSTEM.CHANNEL.INITQ SYSTEM.CHANNEL.SYNCQ SYSTEM.CLUSTER.COMMAND.QUEUE SYSTEM.CLUSTER.REPOSITORY.QUEUE SYSTEM.CLUSTER.TRANSMIT.QUEUE SYSTEM.DEFAULT.LOCAL.QUEUE SYSTEM.QSG.CHANNEL.SYNCQ SYSTEM.QSG.TRANSMIT.QUEUE |
Model queue | SYSTEM.COMMAND.REPLY.MODEL SYSTEM.DEFAULT.MODEL.QUEUE SYSTEM.MQEXPLORER.REPLY.MODEL |
Remote queue | SYSTEM.DEFAULT.REMOTE.QUEUE |
Cluster-sender channel | SYSTEM.DEF.CLUSSDR |
Cluster-receiver channel | SYSTEM.DEF.CLUSRCVR |
Sender channel | SYSTEM.DEF.SENDER |
Server channel | SYSTEM.DEF.SERVER |
Receiver channel | SYSTEM.DEF.RECEIVER |
Requester channel | SYSTEM.DEF.REQUESTER |
Client-connection channel | SYSTEM.DEF.CLNTCONN |
Server-connection channel | SYSTEM.ADMIN.SVRCONN SYSTEM.DEF.SVRCONN |
Authentication information | SYSTEM.DEFAULT.AUTHINFO.CRLLDAP |
Namelist | SYSTEM.DEFAULT.NAMELIST |
Process | SYSTEM.DEFAULT.PROCESS |
Storage class | SYSTEMST |
8
The command is ignored.
Ensure that reserved objects are defined with the correct object type or subtype.
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.
8
The named dynamic queue is not deleted.
Refer to Appendix A. API completion and reason codes for information about the reason code to determine why the queue could not be deleted, and take the appropriate action as necessary. The most likely reason codes are:
A command was issued that refers to a local queue that has incomplete units of recovery outstanding for it.
8
The command is ignored.
Wait until all units of recovery for this queue are complete before attempting to issue the command again.
An attempt to put a message to the dead letter queue was unsuccessful. mqrc gives the reason code for the error.
4
Processing continues.
Refer to Appendix A. API completion and reason codes for information about mqrc to determine the cause of the problem.
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.
4
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; refer to the WebSphere MQ for z/OS System Administration Guide for information about this. If a queue-sharing group is in use, check whether the coupling facility structure has failed and check that DB2 is available and not suspended. If the accompanying message is CSQM091E, refer to Appendix A. API completion and reason codes for an explanation of the mqrc in that message, and what action to take.
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).
8
The command is not actioned.
Do one of the following, depending on the cause of the error:
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.
8
The command is not actioned.
Delete any existing queues that are no longer required.
The object specified is in use. This could be because:
8
The command is ignored.
Either:
For more information about the command, see the WebSphere MQ Script (MQSC) Command Reference manual.
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.
4
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; refer to the WebSphere MQ for z/OS System Administration Guide for information about this. If disposition is GROUP or SHARED, check whether the coupling facility structure has failed and check that DB2 is available and is not suspended. If the accompanying message is CSQM091E, refer to Appendix A. API completion and reason codes for an explanation of the mqrc in that message, and what action to take.
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.
See the WebSphere MQ for z/OS Concepts and Planning Guide and the WebSphere MQ for z/OS System Setup Guide for information about migration and compatibility between releases.
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.
See the WebSphere MQ for z/OS Concepts and Planning Guide and the WebSphere MQ for z/OS System Setup Guide for information about migration and compatibility between releases.
The specified value for the object name or attribute is not allowed for a local queue whose disposition is shared or a model queue used to create a dynamic queue that is shared.
8
Processing of the command is terminated.
Reissue the command correctly.
The specified value for the attribute requires a queue-sharing group, but the queue manager is not in a group.
8
Processing of the command is terminated.
Reissue the command correctly.
Processing for the specified command that refers to an object with the indicated disposition has completed successfully.
0
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.
The value for the specified attribute cannot be changed.
8
Processing of the command is terminated.
To change the attribute, the object must be deleted and then redefined with the new value.
The specified value for the attribute is allowed only for an object that has the indicated disposition.
8
Processing of the command is terminated.
Reissue the command correctly.
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.
8
The command is ignored.
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.
The named keyword can only be specified when TRPTYPE(LU62) is specified.
8
Processing of the command is terminated.
Reissue the command without the named keyword.
A namelist used to specify a list of clusters has no names in it or does not have type CLUSTER or NONE.
8
Processing of the command is terminated.
Reissue the command specifying a namelist that is not empty and has type CLUSTER or NONE.
During the processing of a command, an attempt to put a message to the named queue failed for the specified reason.
8
In general, the command is not actioned. If the command was REFRESH QMGR for configuration events, it may be partially completed as indicated by the preceding CSQM169I messages.
Refer to Appendix A. API completion and reason codes for information about mqrc. If mqrc is 2003, the message could not be committed.
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.
8
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 the WebSphere MQ Script (MQSC) Command Reference manual.
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.
0
A request was queued for the cluster repository manager, which will process it asynchronously.
A command was issued that required the channel initiator to be started.
8
The command is not actioned.
Issue the START CHINIT command to start the channel initiator, and reissue the command.
The START CHINIT command was issued but the channel initiator is already active.
8
The command is not actioned.
A START CHINIT command was issued but the channel initiator could not be started.
This could be for one of the following reasons:
8
The command is not actioned.
Reissue the command when the system workload is reduced and when the queue manager is not shutting down.
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.
0
A request was queued for the channel initiator. Further messages will be produced when the command has been completed.
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:
8
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.
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.
0
A request was queued for the channel initiator. Further messages will be produced when the command has been completed.
A START CHINIT command was issued and the channel initiator address space has been started successfully.
0
Further messages will be produced when the channel initiator itself has started.
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.
8
Processing of the command is terminated.
Reissue the command with correct values.
The named keyword cannot be used on a START LISTENER command for the transport type shown.
8
The command is not actioned.
Reissue the command with the correct keywords.
A START LISTENER command was issued specifying TRPTYPE(LU62) but without the LUNAME keyword. The LUNAME keyword is required with TRPTYPE(LU62).
8
The command is not actioned.
Reissue the command with the correct keywords.
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.
8
Processing of the command is terminated.
Reissue the command with the correct values or on the correct queue manager.
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:
8
Processing of the command is terminated.
Reissue the command with the correct values.
A non-blank value must be specified for the named keyword for a local queue whose disposition is shared or a model queue used to create a dynamic queue that is shared.
8
Processing of the command is terminated.
Reissue the command with a value for the keyword added.
A keyword was entered that takes a list of values, and the named value appears more than once in the list.
8
The command is ignored.
Reissue the command with the parameter specified correctly. For more information about the command, see the WebSphere MQ Script (MQSC) Command Reference manual.
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.
8
Processing of the command is terminated.
Reissue the command with correct values.
The named keyword cannot be specified for queues or channels of the type shown.
8
Processing of the command is terminated.
Reissue the command without the named keyword.
The named keyword was not specified but is required for queues or channels of the type shown.
8
Processing of the command is terminated.
Reissue the command with the named keyword added.
An attempt was made to define or alter an object so that it had incompatible values for the specified keywords.
8
Processing of the command is terminated.
Reissue the command with correct values. For information about the restrictions on the values for the keywords, see the WebSphere MQ Script (MQSC) Command Reference manual.
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.
8
Processing of the command is terminated.
Reissue the command with correct values.
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.
8
Processing of the command is terminated.
Reissue the command with correct values.
Because DB2 is not available or no longer available, the queue manager cannot handle the command for a CF structure or shared channel.
8
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.
Because there was an error in accessing DB2, the queue manager cannot handle the command for a CF structure or shared channel.
8
Processing of the command is terminated.
Resolve the error reported in the preceding messages.
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.
8
Processing of the command is terminated.
Reissue the command with correct values.
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.
8
Processing of the command is terminated.
Reissue the command with correct values.
An MQ DEFINE CFSTRUCT command failed because no more application structures are available in the coupling facility (the limit is 63).
8
The command is not actioned.
Reduce the number of application structures you are using.
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.
8
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.
An attempt was made to alter the CF level of a CF structure, or to delete the structure. This action requires that all queue managers in the queue-sharing group must have a command level of at least 530. Some of the queue managers have a lower level.
8
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 the WebSphere MQ Script (MQSC) Command Reference manual.
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.
8
The command is not executed.
Delete one of the objects.
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.
8
The command is not executed.
Check that the queue names have been entered correctly. Change the queue attributes as necessary.
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.
8
The command is not executed.
Change the MAXDEPTH value for the queue.
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.
8
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 Appendix A. API completion and reason codes for information about mqrc, and take the appropriate action to resolve the problem.
A MOVE QLOCAL command was issued specifying TYPE(MOVE), the target queue already has messages associated with it.
8
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.
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.
0
Processing continues.
If the command did not complete successfully, as shown by the following CSQ9023E message, investigate the problem reported in the preceding messages.
You do not have proper authorization to use the command for the specified object.
8
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.
A command was issued that required performance events to be enabled.
8
The command is not executed.
Use the ALTER QMGR command to set the PERFMEV attribute to ENABLED if performance events are required.
A command was issued that required configuration events to be enabled.
8
The command is not executed.
Use the ALTER QMGR command to set the CONFIGEV attribute to ENABLED if configuration events are required.
A REFRESH QMGR command was issued for configuration events. m objects of the indicated type were found that matched the specified selection criteria (such as name or time of alteration), and n event messages were generated. The number of event messages may be less than the number of objects found because certain objects may be excluded, such as temporary dynamic queues or objects in the process of being deleted. It may also be less than the number of objects found if there was a problem with the event queue.
0
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.
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.
0
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.
0
Processing continues.
If complete configuration information is required, do one of the following, as appropriate:
The named keyword cannot be specified with the TYPE value shown.
8
Processing of the command is terminated.
Reissue the command without the named keyword.
A REFRESH QMGR command was issued for expired message scanning. m queues were found that matched the specified selection criteria.
0
Processing continues.
There was insufficient storage available to complete processing for the command.
8
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.
This message is the response to a command that displays attributes or other information about objects, when that command was entered from either the console, or the command server initialization server. It shows the attributes requested for obj-type, as follows:
obj-type(name) attribute-value attribute-value
·
·
·
END obj-type DETAILS
csect-name might include the command prefix (CPF), depending on how the command was entered.
Exceptionally, the last line might be:
obj-type TERMINATED WITH MAX LINES
if the number of lines allowed in a multiple line WTO to be issued on the console (255) was exceeded. This figure includes the first and last lines of the display. The only object that might cause this message is namelist because displaying a complete namelist would require 263 lines in total. (This only occurs when the command was issued from the console.)
0
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.
0
While processing a command that displays attributes or other information about objects with a disposition of GROUP or SHARED, information could not be obtained from DB2. This may be because DB2 is not available or no longer available, or because it is suspended, or because there was an error in accessing DB2, or because a DB2 table was temporarily locked.
8
Information about objects with a disposition of GROUP or SHARED is not displayed, so the information displayed may therefore be incomplete.
Refer to the console log for messages giving more information about the error.
A severe error occurred while processing a command that displays attributes or other information about objects.
8
The command is terminated.
Refer to the console log for messages giving more information about the error.
A command that displays attributes or other information about objects found that there are no objects that match the specified name and satisfy any other criteria requested (such as subtype or disposition in a queue-sharing group).
0
The total message length for the command allowed on the console (32 K) was exceeded.
8
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).
There was insufficient storage available to complete processing of a command that displays attributes or other information about objects.
8
The command is actioned, but the display of the information is terminated.
If this error occurs when a generic name is used in the command (for example, DIS Q(*) ALL), try to be more selective about the information requested (for example, DIS Q(PAY*) ALL). If the problem persists, you might need to increase the region size used by your queue manager or channel initiator, or you might need to reduce the number of jobs running in your system.
This message consists of the entire object or object status details formatted for use by applications. It is issued in response to commands entered from the command server. Message CSQ9022I follows this message.
The message number depends on the object or object status type, as follows:
Number | Object or status type |
---|---|
CSQM400I | Storage class object |
CSQM401I | Local queue object |
CSQM402I | Model queue object |
CSQM403I | Alias queue object |
CSQM406I | Remote queue object |
CSQM407I | Namelist object |
CSQM408I | Process object |
CSQM409I | Queue manager object |
CSQM410I | Sender channel object |
CSQM411I | Server channel object |
CSQM412I | Receiver channel object |
CSQM413I | Requester channel object |
CSQM415I | Server-connection channel object |
CSQM416I | Client-connection channel object |
CSQM417I | Cluster-receiver channel object |
CSQM418I | Cluster-sender channel object |
CSQM420I | Sender channel status |
CSQM421I | Server channel status |
CSQM422I | Receiver channel status |
CSQM423I | Requester channel status |
CSQM425I | Server-connection channel status |
CSQM427I | Cluster-receiver channel status |
CSQM428I | Cluster-sender channel status |
CSQM430I | CF structure object |
CSQM431I | Cluster queue object |
CSQM437I | Authentication information object |
CSQM439I | Cluster queue manager object |
CSQM440I | CF structure status |
CSQM441I | Local queue status |
CSQM442I | Connection information |
CSQM451I | Local queue statistics |
0
An unexpected return code was issued from a command, relating to the named keyword.
8
The command is ignored.
Note the return code ret-code (which is shown in hexadecimal) and contact your IBM support center.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csqsao0411 |