See Reading a message for an explanation of how to interpret these messages.
0 : Information
WebSphere MQ queue manager <insert_5> created.
None.
0 : Information
WebSphere MQ queue manager <insert_5> deleted.
None.
0 : Information
WebSphere MQ queue manager <insert_5> started.
None.
0 : Information
WebSphere MQ queue manager <insert_5> ended.
None.
0 : Information
WebSphere MQ queue manager <insert_5> changed.
None.
0 : Information
WebSphere MQ queue <insert_5> created.
None.
0 : Information
WebSphere MQ queue <insert_5> deleted.
None.
0 : Information
WebSphere MQ queue <insert_5> changed.
None.
0 : Information
Queue <insert_5> created in library <insert_3> by copying.
None.
0 : Information
WebSphere MQ process <insert_5> created.
None.
0 : Information
WebSphere MQ process <insert_5> deleted.
None.
0 : Information
WebSphere MQ process <insert_5> changed.
None.
0 : Information
Process <insert_5> created in library <insert_3> by copying.
None.
0 : Information
WebSphere MQ channel <insert_5> created.
None.
0 : Information
WebSphere MQ channel <insert_5> deleted.
None.
0 : Information
WebSphere MQ channel <insert_5> changed.
None.
0 : Information
Channel <insert_5> created by copying.
None.
0 : Information
The channel <insert_5> is being started. The start channel function has been initiated. This involves a series of operations across the network before the channel is actually started. The channel status displays "BINDING" for a short period while communication protocols are negotiated with the channel with whom communication is being initiated.
None.
0 : Information
The channel <insert_5> has been requested to stop.
None.
0 : Information
Ping channel <insert_5> complete.
None.
0 : Information
The Request to start the Listener has been accepted and is being processed.
Should the request to start the listener be unsuccessful then information related to the error will be available in the queue manager error log. Once started the status of the listener may be monitored using the MQSC command 'DISPLAY LSSTATUS'. On iSeries the status of the listener may also be monitored using the 'WRKMQMLSR OPTION(*STATUS)' command.
0 : Information
All messages on queue <insert_5> have been deleted.
None.
0 : Information
Channel <insert_5> has been reset.
None.
0 : Information
The channel initiator for queue <insert_5> has been started.
None.
0 : Information
In doubt messages for WebSphere MQ channel <insert_5> have been resolved.
None.
0 : Information
A controlled stop request has been initiated for queue manager <insert_5>.
None.
0 : Information
The command server has been started.
None.
0 : Information
The command server has been stopped.
None.
0 : Information
Authority for object <insert_5> granted.
None.
0 : Information
Authority for object <insert_5> revoked.
None.
0 : Information
The message queue manager has been connected.
None.
0 : Information
The message queue manager has been disconnected.
None.
0 : Information
MQ object <insert_5> has been recreated from image.
None.
0 : Information
Image of MQ object <insert_5> has been recorded.
None.
0 : Information
None.
None.
0 : Information
None.
None.
0 : Information
None.
None.
0 : Information
None.
None.
0 : Information
None.
None.
0 : Information
None.
None.
40 : Stop Error
Processes, that were connected to the queue manager the last time it was running, are still active. The queue manager cannot be restarted.
Stop the processes and try to start the queue manager.
40 : Stop Error
Jobs that were connected to the queue manager the last time it was running, are still active. The queue manager cannot be restarted or deleted.
Use option 22 from WRKMQM to identify which jobs are connected to the queue manager. End the connected jobs and then retry the command.
0 : Information
0 : Information
A non runtime application attempted to connect to a queue manager on a node where support for non runtime applications has not been installed. The connect attempt will be rejected with a reason of MQRC_ENVIRONMENT_ERROR.
If the node is intended to support only runtime applications, investigate why a non runtime application has attempted to connect to the queue manager. If the node is intended to support non runtime only applications, investigate if the base option has been installed. The base option must be installed if non runtime applications are to run on this node.
0 : Information
The attempt to remove the queue manager from the Windows Active Directory failed. This may be because the appropriate entry could not be opened or modified, or the Service Control Point has already been removed.
Check that your account has the authority to delete objects from the Active Directory, and that the entry has not already been deleted.
0 : Information
The attempt to remove the queue manager from the Windows registry failed. This may be because the appropriate entry could not be opened or modified.
Check that the registry has sufficient space on your disk to grow and that your account has the authority to modify it.
0 : Information
None.
0 : Information
Information on the number of channel objects migrated from previous versions of WebSphere MQ channel definitions as well as any failures that occurred.
None.
0 : Information
Information on the number of objects created or replaced successfully as well as any failures that occurred while creating the default objects.
None.
20 : Error
While creating or replacing the default object <insert_4> for WebSphere MQ queue manager <insert_5> an error occurred. The error was due to improper authorization. The reason code is <insert_1>.
Check this log for more details of what the problem may be. Make sure there are sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager <insert_5> using dltmqm and create it again using crtmqm.
0 : Information
None.
0 : Information
None.
0 : Information
None.
20 : Error
While creating or replacing the default object <insert_4> for WebSphere MQ queue manager <insert_5> an error occurred. The error was due to a broken connection. The reason code is <insert_1>.
Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager <insert_5> using dltmqm and create it again using crtmqm.
20 : Error
While creating or replacing the default object <insert_4> for WebSphere MQ queue manager <insert_5> an error occurred. The error was due to unavailable storage. The reason code is <insert_1>.
Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager <insert_5> using dltmqm and create it again using crtmqm.
20 : Error
While creating or replacing the default object <insert_4> for WebSphere MQ queue manager <insert_5> an error occurred. The error was due to a damaged object. The reason code is <insert_1>.
Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager <insert_5> using dltmqm and create it again using crtmqm.
20 : Error
While creating or replacing the default object <insert_4> for WebSphere MQ queue manager <insert_5> an error occurred. The error was due to a channel definition error. The error code is <insert_1> (X<insert_2>).
Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager <insert_5> using dltmqm and create it again using crtmqm.
20 : Error
While creating or replacing the default object <insert_4> for WebSphere MQ queue manager <insert_5> an error occurred. The error was due to invalid records in the channel definition file. The error code is <insert_1> (X<insert_2>).
Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager <insert_5> using dltmqm and create it again using crtmqm.
20 : Error
While creating or replacing the default object <insert_4> for WebSphere MQ queue manager <insert_5> an error occurred. The error was due to not finding the channel definition file. The error code is <insert_1> (X<insert_2>).
Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager <insert_5> using dltmqm and create it again using crtmqm.
20 : Error
While creating or replacing the default object <insert_4> for WebSphere MQ queue manager <insert_5> an error occurred. The error was due to an unexpected error, error code <insert_1> (X<insert_2>).
Check this log for more details of what the problem may be. Make sure there is sufficient resources such as disk space and storage. For damaged or corrupted objects, replace these from backup objects. If all else fails, delete the queue manager <insert_5> using dltmqm and create it again using crtmqm.
10 : Warning
The command <insert_4> at line <insert_1> in the WebSphere MQ service command file <insert_3> for queue manager <insert_5> is not valid for use in the service command file. The line is ignored.
Check the contents of the file and retry the operation.
10 : Warning
An unexpected return code, <insert_1>, was returned by command <insert_3>. This command was issued by the WebSphere MQ service for queue manager <insert_4>.
Verify that the command and parameters are correct.
20 : Error
The current user <insert_5> is not authorized to issue the command <insert_3>. The command is ignored.
Add the user to the local 'mqm' security group and retry the operation.
20 : Error
The user <insert_5> is not authorized to start the trusted application <insert_3>. The application has not started.
Add the user to the local 'mqm' security group and restart the application.
20 : Error
The local group <insert_3> is unavailable. It is not possible to verify that the user is authorized. The function cannot continue.
Create the required local group and retry the operation.
20 : Error
The local mqm group is unavailable. It is not possible to verify that the user is authorized. The function cannot continue.
Create the local mqm group and retry the operation.
0 : Information
Channel <insert_5> auto-defined.
None.
0 : Information
None.
40 : Stop Error
WebSphere MQ queue manager <insert_5> not created. The ApplicationGroup specified for the crtmqm command must contain the mqm userid when the RestrictedMode option (-g) is specified.
None.
40 : Stop Error
WebSphere MQ queue manager <insert_5> not created. RestrictedMode option (-g) specified, but the ApplicationGroup does not exist.
None.
40 : Stop Error
WebSphere MQ queue manager <insert_5> not created. The RestrictedMode option was specified but is not supported on this platform.
None.
10 : Warning
The command server for queue manager <insert_3> received an administration command for channels. The user <insert_5> is not authorized to administer WebSphere MQ channels. The command server has not processed the command.
Add the user to the local 'mqm' security group, and ensure that the security policy is set as required.
10 : Warning
The Object Authority Manager was unable to resolve the specified SID into entity and domain information.
Ensure that the application provides a SID that is recognized on this system, that all necessary domain controllers are available, and that the security policy is set as you required.
10 : Warning
The Object Authority Manager received inconsistent data - the supplied SID does not match that of the supplied entity information.
Ensure that the application is supplying valid entity and SID information.
10 : Warning
The Object Authority Manager was unable to obtain a SID for the specified entity.
Ensure that the entity is valid, and that all necessary domain controllers are available.
10 : Warning
The Object Authority Manager was not supplied with SID information for the specified entity, and the security policy is set to 'NTSIDsRequired'.
Ensure that the application is supplying a valid SID, and that the security policy is set as you require.
10 : Warning
The specified entity is not authorized to access the required object. The following requested permissions are unauthorized: <insert_5>
Ensure that the correct level of authority has been set for this entity against the required object, or ensure that the entity is a member of a privileged group.
0 : Information
None.
0 : Information
The message queue manager trigger monitor job has been started for queue manager <insert_5> to process messages on the selected initiation queue. See previously issued messages for job details.'
None.
10 : Warning
WebSphere MQ, running with the authority of user <insert_4>, was unable to retrieve group membership information for the specified user.
Ensure Active Directory access permissions allow user <insert_4> to read group memberships for user <insert_3>. To retrieve group membership information for a domain user, MQ must run with the authority of a domain user.
40 : Stop Error
Message queue manager trigger job failed to start for manager <insert_5>. Failure reason code is <insert_2>. See previously issued messages for more information.'
None.
10 : Warning
The command server for queue manager <insert_3> received an administration command for a queue manager. The user <insert_5> is not authorized to administer WebSphere MQ queue managers. The command server has not processed the command.
Add the user to the local 'mqm' security group, and ensure that the security policy is set as required.
10 : Warning
The command server for queue manager <insert_3> received an administration command for clusters. The user <insert_5> is not authorized to administer WebSphere MQ clusters. The command server has not processed the command.
Add the user to the local 'mqm' security group, and ensure that the security policy is set as required.
0 : Information
WebSphere MQ queue manager <insert_3> starting.
None.
40 : Stop Error
The connection specified does not exist.
Correct the connection name and then try the command again.
0 : Information
WebSphere MQ queue manager <insert_3> is being started for replay. The strmqm command has been issued with the '-r' option. see the WebSphere MQ System Administration documentation for details.
None.
0 : Information
WebSphere MQ queue manager <insert_3> is being activated. The strmqm command has been issued with the '-a' option. see the WebSphere MQ System Administration documentation for details.
None.
0 : Information
WebSphere MQ queue manager <insert_3> is being activated. The STRMQM command has been issued with the ACTIVATE(*YES) option. see the WebSphere MQ System Administration documentation for further details.
None.
20 : Error
Whilst processing legacy services, listener <insert_3> could not be migrated to an MQ object named <insert_4>, the object creation failed with <insert_1>.
Save the generated output files and contact your IBM support center.
20 : Error
Whilst processing legacy services, trigger monitor <insert_3> could not be migrated to an MQ object named <insert_4>, the object creation failed with <insert_1>.
Save the generated output files and contact your IBM support center.
20 : Error
Whilst processing legacy services, channel service <insert_3> could not be migrated to an MQ object named <insert_4>, the object creation failed with <insert_1>.
Save the generated output files and contact your IBM support center.
20 : Error
Whilst processing legacy services, channel initiator <insert_3> could not be migrated to an MQ object named <insert_4>, the object creation failed with <insert_1>.
Save the generated output files and contact your IBM support center.
20 : Error
Whilst processing legacy services, custom service <insert_3> could not be migrated to an MQ object named <insert_4>, the object creation failed with <insert_1>.
Save the generated output files and contact your IBM support center.
0 : Information
Information on the number of service objects migrated from previous versions of WebSphere MQ for Windows services as well as any failures that occurred.
None.
40 : Stop Error
An unexpected reason code with hexadecimal value <insert_1> was received from the WebSphere MQ queue manager during command processing. (Note that hexadecimal values in the range X'07D1'-X'0BB7' correspond to MQI reason codes 2001-2999.) More information might be available in the log. If the reason code value indicates that the error was associated with a particular parameter, the parameter concerned is <insert_4>.
Correct the error and then try the command again.
30 : Severe error
The object name <insert_5> specified in <insert_4> is not valid. The length of the name must not exceed 48 characters, or 20 characters if it is a channel name. The name should contain the following characters only: lowercase a-z, uppercase A-Z, numeric 0-9, period (.), forward slash (/), underscore (_) and percent sign (%).
Change the length of the parameter value or change the parameter value to contain a valid combination of characters, then try the command again.
40 : Stop Error
There was insufficient storage available to perform the requested operation.
Free some storage and then try the command again.
40 : Stop Error
Directory <insert_3> was not found. This directory is created when WebSphere MQ is installed successfully. Refer to the log for more information.
Verify that installation of WebSphere MQ was successful. Correct the error and then try the command again.
40 : Stop Error
An object error occurred. Refer to the log for more information.
Correct the error and then try the command again.
0 : Information
The queue manager is being created.
Wait for the creation process to complete and then try the command again.
10 : Warning
The queue manager is running.
None.
10 : Warning
The queue manager <insert_3> is ending.
Wait for the queue manager to end and then try the command again.
40 : Stop Error
The queue manager is being deleted.
Wait for the deletion process to complete.
40 : Stop Error
The queue manager <insert_5> already exists.
None.
30 : Severe error
A message queue manager exists with a name different from the value <insert_5> specified in <insert_2>.
Change the parameter value to the name of the existing message queue manager and then try the command again.
40 : Stop Error
The PRCNAME parameter may not be specified for a queue of type *ALS or *RMT.
Remove the PRCNAME parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
40 : Stop Error
The TRGENBL parameter may not be specified for a queue of type *ALS or *RMT.
Remove the TRGENBL parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
40 : Stop Error
The GETENBL parameter may not be specified for a queue of type *RMT.
Remove the GETENBL parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
40 : Stop Error
The SHARE parameter may not be specified for a queue of type *ALS or *RMT.
Remove the SHARE parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
40 : Stop Error
The MSGDLYSEQ parameter may not be specified for a queue of type *ALS or *RMT.
Remove the MSGDLYSEQ parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
40 : Stop Error
Deletion of queue manager <insert_5> was only partially successful. An object was not found, or could not be deleted. Refer to the log for more information.
Delete any remaining queue manager objects.
40 : Stop Error
The queue manager <insert_5> does not exist.
Either create the queue manager (crtmqm command) or correct the queue manager name used in the command and then try the command again.
40 : Stop Error
The TRGTYPE parameter may not be specified for a queue of type *ALS or *RMT.
Remove the TRGTYPE parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
40 : Stop Error
The TRGDEPTH parameter may not be specified for a queue of type *ALS or *RMT.
Remove the TRGDEPTH parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
40 : Stop Error
The TRGMSGPTY parameter may not be specified for a queue of type *ALS or *RMT.
Remove the TRGMSGPTY parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
40 : Stop Error
The TRGDATA parameter may not be specified for a queue of type *ALS or *RMT.
Remove the TRGDATA parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
40 : Stop Error
The RTNITV parameter may not be specified for a queue of type *ALS or *RMT.
Remove the RTNITV parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
40 : Stop Error
The MAXMSGLEN parameter may not be specified for a queue of type *ALS or *RMT.
Remove the MAXMSGLEN parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
40 : Stop Error
The BKTTHLD parameter may not be specified for a queue of type *ALS or *RMT.
Remove the BKTTHLD parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
40 : Stop Error
The BKTQNAME parameter may not be specified for a queue of type *ALS or *RMT.
Remove the BKTQNAME parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
40 : Stop Error
The INITQNAME parameter may not be specified for a queue of type *ALS or *RMT.
Remove the INITQNAME parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
40 : Stop Error
The USAGE parameter may not be specified for a queue of type *ALS or *RMT.
Remove the USAGE parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
40 : Stop Error
The DFNTYPE parameter may only be specified for a queue of type *MDL.
Remove the DFNTYPE parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
40 : Stop Error
The TGTQNAME parameter may only be specified for a queue of type *ALS.
Remove the TGTQNAME parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
40 : Stop Error
The RMTQNAME parameter may only be specified for a queue of type *RMT.
Remove the RMTQNAME parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
40 : Stop Error
The RMTMQMNAME parameter may only be specified for a queue of type *RMT.
Remove the RMTMQMNAME parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
40 : Stop Error
The TMQNAME parameter may only be specified for a queue of type *RMT.
Remove the TMQNAME parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
40 : Stop Error
The HDNBKTCNT parameter may not be specified for a queue of type *ALS or *RMT.
Remove the HDNBKTCNT parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
40 : Stop Error
You are not authorized to perform the requested operation for the WebSphere MQ object <insert_5> specified in <insert_3>. Either you are not authorized to perform the requested operation, or you are not authorized to the specified MQ object. For a copy command, you may not be authorized to the specified source MQ object, or, for a create command, you may not be authorized to the system default MQ object of the specified type.
Obtain the necessary authority from your security officer or WebSphere MQ administrator. Then try the command again.
30 : Severe error
A prompt control program detected errors.
See the previously listed messages in the job log. Correct the errors and then prompt for the command again.
40 : Stop Error
The strmqm command was unsuccessful because the queue manager <insert_5> is already starting.
Wait for the strmqm command to complete.
40 : Stop Error
The operation is not valid with queue <insert_5> because it is not a local queue.
Change the QNAME parameter to specify a queue of the correct type.
10 : Warning
A connection to the WebSphere MQ queue manager already exists.
None.
40 : Stop Error
A timeout occurred in the communication between internal WebSphere MQ queue manager components. This is most likely to occur when the system is heavily loaded.
Wait until the system is less heavily loaded, then try the command again.
40 : Stop Error
The queue manager <insert_5> is starting.
Wait for the queue manager startup process to complete and then try the command again.
40 : Stop Error
The queue manager <insert_5> is stopped.
Use the strmqm command to start the queue manager, and then try the command again.
40 : Stop Error
The queue <insert_5> specified in <insert_2> is not empty or contains uncommitted updates.
Commit or roll back any uncommitted updates. If the command is DELETE QLOCAL, use the CLEAR QLOCAL command to clear the messages from the queue. Then try the command again.
40 : Stop Error
The WebSphere MQ logging resource is not available.
Use the dltmqm command to delete the queue manager and then the crtmqm command to create the queue manager. Then try the command again.
40 : Stop Error
The connection to the WebSphere MQ queue manager failed during command processing. This may be caused by an endmqm command being issued by another user, or by a queue manager error.
Use the strmqm command to start the message queue manager, wait until the message queue manager has started, and try the command again.
40 : Stop Error
The queue manager is not available because it has been stopped or has not been created.
Use the crtmqm command to create the message queue manager, or the strmqm command to start the message queue manager as necessary. Then try the command again.
40 : Stop Error
The queue manager is not available because it has been stopped or has not been created.
Use the CRTMQM command to create the message queue manager or the STRMQM command to start the message queue manager as necessary, then retry the command. If a queue manager was not specified, ensure that a default queue manager has been created and is started using the WRKMQM command.
40 : Stop Error
If the command entered was Change or Display, the object <insert_3> specified does not exist. If the command entered was Copy, the source object does not exist. If the command entered was Create, the system default MQ object of the specified type does not exist.
Correct the object name and then try the command again or, if you are creating a new queue or process object, either specify all parameters explicitly or ensure that the system default object of the required type exists. The system default queue names are SYSTEM.DEFAULT.LOCAL.QUEUE, SYSTEM.DEFAULT.ALIAS.QUEUE and SYSTEM.DEFAULT.REMOTE.QUEUE. The system default process name is SYSTEM.DEFAULT.PROCESS.
40 : Stop Error
If the command entered was Change or Display, the MQ object <insert_5> specified does not exist. If the command entered was Copy, the source MQ object does not exist. If the command entered was Create, the system default MQ object of the specified type does not exist.
Correct the MQ object name and then try the command again or, if you are creating a new MQ queue or process object, either specify all parameters explicitly or ensure that the system default object of the required type exists. The system default queue names are SYSTEM.DEFAULT.LOCAL.QUEUE, SYSTEM.DEFAULT.ALIAS.QUEUE and SYSTEM.DEFAULT.REMOTE.QUEUE. The system default process name is SYSTEM.DEFAULT.PROCESS.
40 : Stop Error
The object <insert_5> specified in <insert_3> is in use by an MQ application program.
Wait until the object is no longer in use and then try the command again. If the command is ALTER or CHANGE, specify FORCE to force the processing of the object regardless of any application program affected by the change. If the object is the dead-letter queue and the open input count is nonzero, it may be in use by an MQ channel. If the object is another queue object with a nonzero open output count, it may be in use by a MQ channel (of type RCVR or RQSTR). In either case, use the STOP CHANNEL and START CHANNEL commands to stop and restart the channel in order to solve the problem. To alter the queue USAGE the FORCE option must be used if the queue is not empty.
40 : Stop Error
The object <insert_5> specified in <insert_4> is damaged.
The object contents are not valid. Issue the DISPLAY CHANNEL, DISPLAY QUEUE, or DISPLAY PROCESS command, as required, to determine the name of the damaged object. Issue the DEFINE command, for the appropriate object type, to replace the damaged object, then try the command again.
40 : Stop Error
The object <insert_5> specified for <insert_3> could not be created because it already exists.
Check that the name is correct and try the command again specifying REPLACE, or delete the object. Then try the command again.
40 : Stop Error
The type specified for object <insert_5> is different from the type of the object being altered or defined.
Use the correct MQ command for the object type, and then try the command again.
40 : Stop Error
The type of the source object is different from that specified.
Correct the name of the command, or source object name, and then try the command again, or try the command using the REPLACE option.
40 : Stop Error
The command failed because there was insufficient disk space available for the specified queue.
Release some disk space and then try the command again.
40 : Stop Error
The WebSphere MQ queue manager was unable to load the API crossing exit.
Ensure that the API crossing exit program is valid, and that its name and directory are correctly specified. Correct any error and then try the command again.
40 : Stop Error
The queue manager connection limit has been exceeded.
The maximum limit on the number of WebSphere MQ application programs that may be connected to the queue manager has been exceeded. Try the command later.
40 : Stop Error
The queue manager is quiescing.
The queue manager was stopping with -c specified for endmqm. Wait until the queue manager has been restarted and then try the command again.
40 : Stop Error
An error was reported by the security manager program.
Inform your systems administrator, wait until the problem has been corrected, and then try the command again.
40 : Stop Error
The API crossing exit program was not found.
Ensure that the API crossing exit program for the MQI exists, and that its name and library are correctly specified. Correct any errors and then try the command again.
40 : Stop Error
The MAXDEPTH parameter may not be specified for a queue of type *ALS or *RMT.
Remove the MAXDEPTH parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
40 : Stop Error
The DFTSHARE parameter may not be specified for a queue of type *ALS or *RMT.
Remove the DFTSHARE parameter from the command or, if the command is CRTMQMQ, specify a different value for QTYPE. Then try the command again.
40 : Stop Error
AUT(*MQMPASSID) may only be specified with OBJTYPE(*ADM).
Change the AUT parameter to specify another value and then try the command again.
40 : Stop Error
AUT(*MQMPASSALL) may only be specified with OBJTYPE(*ADM).
Change the AUT parameter to specify another value and then try the command again.
40 : Stop Error
AUT(*MQMSETID) may only be specified with OBJTYPE(*ADM).
Change the AUT parameter to specify another value and then try the command again.
40 : Stop Error
AUT(*MQMSETALL) may only be specified with OBJTYPE(*ADM).
Change the AUT parameter to specify another value and then try the command again.
40 : Stop Error
AUT(*MQMALTUSR) may only be specified with OBJTYPE(*ADM).
Change the AUT parameter to specify another value and then try the command again.
40 : Stop Error
The object specified by the REFOBJ and REFOBJTYPE parameters does not exist.
Correct the reference object name and type, and then try the command again.
30 : Severe error
The referenced object name specified in REFOBJ is not valid. The length of the name must not exceed 48 characters and the name should contain the following characters only: lowercase a-z, uppercase A-Z, numeric 0-9, period (.), forward slash (/), underscore (_) and percent sign (%).
Change the length of the parameter value or change the parameter value to contain a valid combination of characters. Then try the command again.
30 : Severe error
The user profile name specified for parameter USER could not be found on the system, and is not the special value *PUBLIC.
Correct the user profile name, or use the Create User Profile (CRTUSRPRF) command to create the user profile then try the request again.
30 : Severe error
The authorization list specified for parameter AUTL does not exist. It may have been destroyed.
Either specify an authorization list that exists, or create the authorization list using the Create Authorization List (CRTAUTL) command. Try the request again.
30 : Severe error
REFOBJTYPE(*OBJTYPE) can be specified only with a specific object type.
Change the REFOBJTYPE or OBJTYPE input value to a specific object type. Then try the Grant Authority (GRTMQMAUT) command again.
30 : Severe error
AUT(*AUTL) was specified on either the Grant Authority (GRTMQMAUT) command or the Revoke Authority (RVKMQMAUT) command with the USER parameter not set to *PUBLIC. Only the authority for *PUBLIC can be deferred to the authorization list.
Change the AUT parameter to the authorities that are correct for the users or change the USER parameter to *PUBLIC. Then try the command again.
10 : Warning
The MQI reason code of 2018 was returned from the WebSphere MQ queue manager in response to an MQDISC request issued during command processing.
None.
0 : Information
There are no matching processes defined on this system.
Using the DEFINE PROCESS command to create a process.
0 : Information
There are no matching queues defined on this system.
Use the appropriate command to define a queue of the type that you require, that is, DEFINE QALIAS, DEFINE QLOCAL, DEFINE QMODEL, or DEFINE QREMOTE.
0 : Information
The trace has started successfully.
None.
0 : Information
The trace has been written successfully.
None.
0 : Information
The trace has stopped.
None.
40 : Stop Error
The trace did not start successfully.
None.
40 : Stop Error
The trace was not output successfully.
None.
40 : Stop Error
Your request to end the trace was not successful.
None.
10 : Warning
There are no matching jobs running on this system.
Specify another job name from the STRMQMSRV command.
10 : Warning
An attempt was made to set trace off, but the trace is not active.
None.
10 : Warning
An attempt was made to start trace, but trace is already running.
Either leave trace running as it is, or, if you want to change the trace settings, turn trace off and then turn it on again with appropriate settings.
10 : Warning
The job specified cannot be found in the table that controls WebSphere MQ for iSeries trace. As a result no trace action can be performed.
Specify an appropriate job name.
40 : Stop Error
The WebSphere MQ object cannot be created because an object that is not known to MQ already exists in the MQ directory with the name that should be used for the new object. Refer to the log for previous messages.
Remove the non-MQ object from the MQ library, and try the command again.
40 : Stop Error
The object <insert_5> type <insert_3> cannot be recreated because the image is not fully available in the logs that are currently online. Refer to earlier messages in the error log for information about the logs that need to be brought online for this object to be recreated.
Bring the relevant logs online, and try the command again.
40 : Stop Error
The object <insert_5>, type <insert_3>, is currently in use, so the <insert_1> command cannot be issued against it. If a generic list was presented to the command, the command is still issued against the other objects in the list.
Wait until the object is no longer in use, and try the command again.
40 : Stop Error
You are not authorized to issue the <insert_1> command against the object <insert_5> type <insert_3>. If a generic list was presented to the command, the command is still issued against the other objects in the list.
Obtain sufficient authorization for the object, and retry the command.
40 : Stop Error
The object <insert_5> type <insert_4> is damaged and the <insert_3> command cannot be issued against it. If a generic list was presented to the command then the command is still issued against the other objects in the list.
Issue the appropriate DEFINE command for the object, specifying REPLACE, and then try the command again.
40 : Stop Error
An operation performed on a generic list of objects was not completely successful.
Examine the log for details of the errors encountered, and take appropriate action.
40 : Stop Error
The command server is starting.
Wait for the strmqcsv command to complete and then try the operation again.
40 : Stop Error
The command server is starting.
Wait for the STRMQMCSVR command to complete and then try the operation again.
40 : Stop Error
The request to start the command server was unsuccessful because the command server is already starting.
Wait for the strmqcsv command to complete.
40 : Stop Error
The request to start the command server was unsuccessful because the command server is already starting.
Wait for the STRMQMCSVR command to complete.
40 : Stop Error
The command server is ending.
Wait for the endmqcsv command to complete and then try the command again.
40 : Stop Error
The command server is ending.
Wait for the ENDMQMCSVR command to complete and then try the command again.
40 : Stop Error
The end command server request was unsuccessful because the command server is already ending.
Wait for the endmqcsv command to complete.
40 : Stop Error
The end command server request was unsuccessful because the command server is already ending.
Wait for the ENDMQMCSVR command to complete.
40 : Stop Error
The strmqcsv command was unsuccessful because the command server is already running.
None.
40 : Stop Error
The STRMQMCSVR command was unsuccessful because the command server is already running.
None.
40 : Stop Error
The request to end the command server was unsuccessful because the command server is already stopped.
None.
20 : Error
The deleted MQ queue <insert_5> was damaged, and any messages it contained have been lost.
None.
20 : Error
The number of parameters passed in the call to program <insert_3> is not correct.
Correct the calling program and then retry the operation.
20 : Error
The call identifier, the first parameter passed to program QMQM, is not in the required packed decimal format, or its value is not supported. Permitted values of the call identifier are contained in the RPG copy file CMQR.
Correct the calling program, and retry the call.
40 : Stop Error
The MODENAME parameter may only be specified with TRPTYPE(*LU62).
Remove the MODENAME parameter from the command or change the TRPTYPE parameter value to specify *LU62 and then try the command again.
40 : Stop Error
The TPGMNAME parameter may only be specified with TRPTYPE(*LU62).
Remove the TPGMNAME parameter from the command or change the TRPTYPE parameter value to specify *LU62. Then try the command again.
40 : Stop Error
The TMQNAME parameter may only be specified with channel type *SDR or *SVR.
Remove the TMQNAME parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR or *SVR. Then try the command again.
40 : Stop Error
The CONNAME parameter may only be specified with channel type *SDR, *SVR, *RQSTR, *CLUSSDR, *CLTCN or *CLUSRCVR.
Remove the CONNAME parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR, *SVR, *RQSTR, *CLUSSDR, *CLTCN or *CLUSRCVR. Then try the command again.
40 : Stop Error
The MCANAME parameter may only be specified with channel type *SDR, *SVR, or *RQSTR.
Remove the MCANAME parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR, *SVR, or *RQSTR. Then try the command again.
40 : Stop Error
The DSCITV parameter may only be specified with channel type *CLUSSDR, *CLUSRCVR, *SVRCN, *SDR or *SVR.
Remove the DSCITV parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *CLUSSDR, *CLUSRCVR, *SVRCN, *SDR or *SVR. Then try the command again.
40 : Stop Error
The SHORTRTY parameter may only be specified with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR.
Remove the SHORTRTY parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *CLUSSDR, *CLUSRCVR, *SDR or *SVR. Then try the command again.
40 : Stop Error
The SHORTTMR parameter may only be specified with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR.
Remove the SHORTTMR parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *CLUSSDR, CLUSRCVR, *SDR or *SVR. Then try the command again.
40 : Stop Error
The LONGRTY parameter may only be specified with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR.
Remove the LONGRTY parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *CLUSSDR, CLUSRCVR, *SDR or *SVR. Then try the command again.
40 : Stop Error
The LONGTMR parameter may only be specified with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR.
Remove the LONGTMR parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *CLUSSDR, *CLUSRCVR, *SDR or *SVR. Then try the command again.
40 : Stop Error
The PUTAUT parameter may only be specified with channel type *RCVR or RQSTR.
Remove the PUTAUT parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *RCVR or RQSTR. Then try the command again.
40 : Stop Error
The BATCHINT parameter may only be specified with channel type *SDR or *SVR.
Remove the BATCHINT parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR or *SVR. Then try the command again.
40 : Stop Error
A required parameter was not specified.
Enter a value for parameter TPGMNAME.
40 : Stop Error
The TMQNAME parameter must be specified with channel type *SDR or *SVR.
Enter a value for parameter TMQNAME.
40 : Stop Error
The CONNAME parameter must be specified with channel types SDR, RQSTR, CLNTCONN, and CLUSSDR. It is also required with channel type CLUSRCVR if the TRPTYPE is not TCP.
Enter a value for parameter CONNAME.
40 : Stop Error
The CONNAME parameter must be specified with channel types *SDR, *RQSTR, and *CLUSSDR. It is also required with channel type *CLUSRCVR if the TRPTYPE is not *TCP.
Enter a value for parameter CONNAME.
40 : Stop Error
The CVTMSG parameter may only be specified with channel type *SDR, *SVR, *CLUSSDR or *CLUSRCVR.
Remove the CVTMSG parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR, *SVR, *CLUSSDR or CLUSRCVR. Then try the command again.
40 : Stop Error
The MODENAME parameter may only be specified with TRPTYPE(*LU62).
Remove the MODENAME parameter from the command or change the TRPTYPE parameter value to specify *LU62. Then try the command again.
40 : Stop Error
The CONNAME parameter may only be specified with channel type *SDR, *SVR, *RQSTR, CLUSSDR or CLUSRCVR.
Remove the CONNAME parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR, *SVR, *RQSTR, CLUSSDR or CLUSRCVR. Then try the command again.
30 : Severe error
30 : Severe error
Wait and try again later.
0 : Information
The PNGMQMCHL command sent <insert_1> bytes of data to <insert_3> and received the data back in <insert_4>.<insert_5> seconds. The number of bytes will be less than the amount requested on the command, when the length requested is greater than the allowed maximum, in one communications transmission, for the operating system and communications protocol.
None.
10 : Warning
The length of the ping data sent was reduced because of constraints in the current configuration.
None.
40 : Stop Error
Ping data compare failed at offset <insert_1>, data sent <insert_3>, data received <insert_4>.
This is probably due to a communications failure. Other messages may have been issued.
0 : Information
There are no channels defined on this system.
Create a channel using the CRTMQMCHL command.
30 : Severe error
The source WebSphere MQ channel does not exist.
Correct the MQ channel name and then try the command again.
30 : Severe error
The same name has been specified for the from channel name and the to channel name.
Choose two different names, of which the from channel must exist.
40 : Stop Error
The channel <insert_3> cannot be created because it already exists.
Check that the name is correct and try the command again specifying REPLACE, or delete the channel and then try the command again.
30 : Severe error
The channel could not be found.
Correct the Channel Name if wrong and then try the command again. For DEFINE CHANNEL check that the Channel Name in error exists.
30 : Severe error
The unexpected return code <insert_1> was returned to a channel command.
This message is associated with an internal error. Use WRKPRB to record the problem identifier, and to save the QPSRVDMP, QPJOBLOG, and QPDSPJOB files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
0 : Information
There are no message queue managers to administer.
Add a queue manager using PF6 or the ADMQMNAM command.
0 : Information
Either the queue manager has no objects to display (this is unlikely), or the selection criteria resulted in zero objects to display.
Change or remove the selection criteria.
0 : Information
There are no commands or command responses to display.
None.
0 : Information
The queue is empty, or the queue does not exist.
None.
0 : Information
The message contains no data.
None.
0 : Information
There is no response data to display for this command. This is probably because the command has not yet completed.
None.
0 : Information
Some commands have no required parameters.
None.
30 : Severe error
CHGMQMCHL was issued for a non-existent channel.
Correct the WebSphere MQ channel name and then try the command again.
40 : Stop Error
The NPMSPEED parameter may only be specified with channel type *SDR, *SVR, *RCVR *RQSTR, CLUSSDR or CLUSRCVR.
Remove the NPMSPEED parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR, *SVR, *RCVR *RQSTR, CLUSSDR or CLUSRCVR. Then try the command again.
30 : Severe error
An MQCONN call was issued, but the thread or process is already connected to a different queue manager. The thread or process can connect to only one queue manager at a time.
Use the MQDISC call to disconnect from the queue manager which is already connected, and then issue the MQCONN call to connect to the new queue manager. Disconnecting from the existing queue manager will close any queues which are currently open, it is recommended that any uncommitted units of work should be committed or backed out before the MQDISC call is used.
40 : Stop Error
The LOCLADDR parameter may only be specified with channel type *SDR, *SVR, *RQSTR, *CLUSSDR, *CLUSRCVR or *CLTCN.
Remove the CONNAME parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR, *SVR, *RQSTR, *CLUSSDR, *CLUSRCVR or *CLTCN. Then try the command again.
40 : Stop Error
The unexpected return code <insert_1> was returned during <insert_3> processing.
This message is associated with an internal error. Use WRKPRB to record the problem identifier, and to save the QPSRVDMP, QPJOBLOG, and QPDSPJOB files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
40 : Stop Error
The unexpected message format <insert_3> was received in message on the internal reply queue.
This message is probably a message sent erroneously to this queue. The message in error is written to the SYSTEM.ADMIN.EXCEPTION.QUEUE, where it may be viewed using the WRKMQMMSG command.
40 : Stop Error
The definition of the SSLCIPH parameter was wrong.
Correct the SSLCIPH definition and try the command again.
40 : Stop Error
The definition of the SSLPEER parameter was wrong. Possible causes may be that the syntax was invalid or that it contained an invalid attribute type.
Correct the SSLPEER definition and try the command again.
0 : Information
There are no objects with the specified name and type.
None.
0 : Information
The DISPLAY CONN command completed successfully. Details follow this message.
40 : Stop Error
The definition of WebSphere MQ object <insert_5> changed after it had been opened, thereby invalidating the open operation.
Try the command again.
40 : Stop Error
An attempt was made to exceed the maximum handle limit specified for the message queue manager.
Increase the maximum handle limit specified for the message queue manager using the CHGMQM command. Then try the command again.
40 : Stop Error
The options specified when opening WebSphere MQ object <insert_5> were not valid for the object type.
Correct the definition of the failing object. Then try the command again.
30 : Severe error
The queue being displayed does not exist on this queue manager.
Check the name of the queue and retry the operation. If you are attempting to display a queue of type *ALS, check the queue definition references an existing queue definition.
30 : Severe error
Either the necessary queue manager name has been entered incorrectly on the add queue manager panel, or the queue manager has not been defined on the connected queue manager.
Correct the name, or define <insert_3> on the connected queue manager by creating a local queue with name <insert_3> and usage *TMQ (transmission queue), and then creating sender and receiver channels on both the connected queue manager and queue manager <insert_3>.
40 : Stop Error
The program AMQMCPRA (data store program) was not started because of reason code <insert_1>.
Check the joblog for AMQMCPRA by issuing a WRKSPLF QMQM. Correct the problem and try to start the Administration application by invoking the STRMQMADM command. If the problem persists contact your systems programmer.
40 : Stop Error
Queue <insert_3> (queue manager <insert_4>) has not been authorized for your use.
Have queue <insert_3> authorized for your use. If queue manager <insert_4> is not the local queue manager, you might not be authorized to the transmission queue for this queue manager.
0 : Information
There are no channels having status information to display. This indicates either, that the channel has not been started previously, or, that the channel has been started but has not yet completed a transmission sequence.
None.
40 : Stop Error
You are not authorized to perform the requested operation for WebSphere MQ command <insert_1>.
Obtain the necessary authority from your WebSphere MQ administrator. Then try the command again.
40 : Stop Error
You are not authorized to the WebSphere MQ command because your user profile is not a member of the QMQMADM group.
Ask your MQ administrator to give your user profile *ALLOBJ authority, or add your user profile to the QMQMADM group (either as a primary or supplemental group)
10 : Warning
An attempt was made to start remote trace, but it is already running.
Either leave remote trace running as it is, or, if you want to change the settings, turn remote trace off and then turn it on again with appropriate settings.
10 : Warning
An attempt was made to end remote trace, but it is already off.
Leave remote trace off.
40 : Stop Error
The specified object is not secured by the authorization list to be revoked from it.
Use the display authority (DSPMQMAUT) command to determine what authorization list is securing the object, if any. Issue the RVKMQMAUT command again with the authorization list that is securing the the object to revoke the authorization list's authority.
0 : Information
The <insert_3> command has completed successfully. The <insert_1> MQ commands from <insert_5> have been processed without error and a report written to the printer spool file.
None.
0 : Information
The <insert_3> command completed successfully. The <insert_1> MQ commands from <insert_5> have been verified and a report written to the printer spool file.
None.
40 : Stop Error
The <insert_3> command attempted to process a sequence of MQ commands and encountered some errors, however, the operation may have partially completed.
If the STRMQMMQSC command was executed a report has been written to a printer spool file. Examine the spooled printer file for details of the errors encountered and correct the MQSC source <insert_5> and retry the operation.
40 : Stop Error
The <insert_1> command failed to open <insert_5> for MQ command processing.
Check that the intended file exists, and has been specified correctly. Correct the specification or create the object, and try the operation again.
30 : Severe error
An attempt was made to create or change a channel which had more than the allowed maximum of a total of six exit programs and/or user data fields defined.
Re-define the channel so that a total of six exit programs and/or user data fields are defined.
50 : System Error
An attempt to start the storage monitor process (job QMQM in subsystem QSYSWRK) was unsuccessful.
Check the job log for the reason for the failure, and try the command again.
50 : System Error
An error occurred while attempting to initialize WebSphere MQ services.
A call to xcsInitialize ended with the FAIL, STOP, or STOP_ALL return code. Refer to the log for messages diagnosing this problem.
50 : System Error
40 : Stop Error
A maximum of 9 traces may be running concurrently. This number is already running.
Stop one or more of the other traces and try the command again.
40 : Stop Error
A maximum of 9 traces can be running concurrently, and this number of traces is already running.
Stop one or more of the other traces and try the command again.
40 : Stop Error
The BATCHSIZE parameter may only be specified with channel type *SDR, *SVR, *RCVR, *RQSTR, CLUSSDR or CLUSRCVR.
Remove the BATCHSIZE parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR, *SVR, *RCVR *RQSTR, CLUSSDR or CLUSRCVR. Then try the command again.
40 : Stop Error
The SEQNUMWRAP parameter may only be specified with channel type *SDR, *SVR, *RCVR, *RQSTR, CLUSSDR or CLUSRCVR.
Remove the SEQNUMWRAP parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR, *SVR, *RCVR *RQSTR, CLUSSDR or CLUSRCVR. Then try the command again.
40 : Stop Error
The MSGRTYEXIT parameter may only be specified with channel type *CLUSRCVR, *RCVR or *RQSTR.
Remove the MSGRTYEXIT parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *CLUSRCVR, *RCVR or *RQSTR. Then try the command again.
40 : Stop Error
The MSGRTYDATA parameter may only be specified with channel type *CLUSRCVR, *RCVR or *RQSTR.
Remove the MSGRTYDATA parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *CLUSRCVR, *RCVR or *RQSTR. Then try the command again.
40 : Stop Error
The MSGRTYNBR parameter may only be specified with channel type *CLUSRCVR, *RCVR or *RQSTR.
Remove the MSGRTYNBR parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *CLUSRCVR, *RCVR or *RQSTR. Then try the command again.
40 : Stop Error
The MSGRTYITV parameter may only be specified with channel type *CLUSRCVR, *RCVR or *RQSTR.
Remove the MSGRTYITV parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *CLUSRCVR, *RCVR or *RQSTR. Then try the command again.
40 : Stop Error
The CLUSTER parameter may only be specified with queue type *ALS, *LCL and *RMT.
Remove the CLUSTER parameter from the command or, if the command is CRTMQMQ, change the QTYPE parameter value to specify *ALS, *LCL or *RMT. Then try the command again.
40 : Stop Error
The CLUSNL parameter may only be specified with queue type *ALS, *LCL and *RMT.
Remove the CLUSNL parameter from the command or, if the command is CRTMQMQ, change the QTYPE parameter value to specify *ALS, *LCL or *RMT. Then try the command again.
40 : Stop Error
The DEFBIND parameter may only be specified with queue type *ALS, *LCL and *RMT.
Remove the DEFBIND parameter from the command or, if the command is CRTMQMQ, change the QTYPE parameter value to specify *ALS, *LCL or *RMT. Then try the command again.
0 : Information
There are no matching namelists defined on this system.
Use the Create Namelist (CRTMQMNL) command to create a namelist.
0 : Information
There are no matching cluster queue managers defined on this system.
None.
40 : Stop Error
The CLUSTER parameter may only be specified with channel type *CLUSSDR and *CLUSRCVR.
Remove the CLUSTER parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *CLUSSDR or *CLUSRCVR. Then try the command again.
40 : Stop Error
The CLUSNL parameter may only be specified with channel type *CLUSSDR and *CLUSRCVR.
Remove the CLUSNL parameter from the command or, if the command is CRTMQMCHL, change the CHLQTYPE parameter value to specify *CLUSSDR or *CLUSRCVR. Then try the command again.
40 : Stop Error
The MSGEXIT parameter may only be specified with channel type *SDR, *SVR, *RCVR, *RQSTR, *CLUSSDR, or *CLUSRCVR.
Remove the MSGEXIT parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR or *SVR or *RCVR or *RQSTR or *CLUSSDR or *CLUSRCVR. Then try the command again.
40 : Stop Error
The MSGUSRDATA parameter may only be specified with channel type *SDR, *SVR, *RCVR *RQSTR, *CLUSSDR or *CLUSRCVR.
Remove the MSGUSRDATA parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR or *SVR or *RCVR or *RQSTR or *CLUSSDR or *CLUSRCVR. Then try the command again.
0 : Information
40 : Stop Error
The TIMEOUT parameter may only be specified when connected jobs are being ended with the ENDCCTJOB option set to *YES.
Remove the TIMEOUT parameter from the command or, if you want to fully quiesce the queue manager, change the ENDCCTJOB parameter to *YES. Then try the command again.
40 : Stop Error
When performing a pre-emptive shutdown of the queue manager the ENDCCTJOB(*YES) parameter is not allowed.
Change the ENDCCTJOB(*YES) parameter to ENDCCTJOB(*NO) or, if you want to fully quiesce the queue manager without doing a pre-emptive shutdown, change the OPTION(*PREEMPT) parameter to another value. Then try the command again.
40 : Stop Error
The OPTION(*WAIT) parameter is not allowed when performing a shutdown of all queue managers.
Remove the OPTION(*WAIT) parameter from the command or, specify individual queue manager names to shut down the queue managers one-by-one with the OPTION(*WAIT) parameter. Then try the command again.
40 : Stop Error
The MQMNAME(*ALL) parameter is only allowed when performing a full shutdown of the queue managers.
Specify individual queue manager names to shut the queue managers down one-by-one or change the ENDCCTJOB parameter to *YES. Then try the command again.
0 : Information
0 : Information
0 : Information
0 : Information
0 : Information
0 : Information
0 : Information
0 : Information
0 : Information
0 : Information
0 : Information
0 : Information
0 : Information
There are no authority records defined on this system, satisfying the input parameters.
Use the appropriate input to list all the authorities defined on the system, or enter the command again with different input..
0 : Information
You are not allowed to completely delete the authorities assigned to user QMQMADM, for a valid WebSphere MQ object, with the authority *REMOVE or *NONE.
Remove QMQMADM from the list of users to this command.
0 : Information
The delete option, which will delete this authority profile by removing all the users from this authority profile, is not valid for an object name or the special value &class.
To delete users from an object, work from the WRKMQMAUTD command.
40 : Stop Error
The BATCHHB parameter may only be specified with channel type *SDR, *SVR, *CLUSSDR, or *CLUSRCVR.
Remove the BATCHHB parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR, *SVR, *CLUSSDR or *CLUSRCVR. Then try the command again.
40 : Stop Error
The Queue Manager Name for Removal (QMNAME) parameter is not *QMID and there is a value for the Queue Manager Identifier for Removal (QMID) parameter.
A value for QMID is not allowed unless QMNAME is *QMID. Change the value specified on the QMNAME parameter or the value of the QMID parameter and then try the request again.
40 : Stop Error
The USERID parameter may only be specified with channel type *SDR, *SVR, *RQSTR, *CLUSSDR, or *CLTCN.
Remove the USERID parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR, *SVR, *RQSTR, *CLUSSDR, or *CLTCN. Then try the command again.
40 : Stop Error
The PASSWORD parameter may only be specified with channel type *SDR, *SVR, *RQSTR, *CLUSSDR, or *CLTCN.
Remove the PASSWORD parameter from the command or, if the command is CRTMQMCHL, change the CHLTYPE parameter value to specify *SDR, *SVR, *RQSTR, *CLUSSDR, or *CLTCN. Then try the command again.
40 : Stop Error
Authority changes to an object were requested but could not be made.
Check the authorities that you are granting are relevant to the object type of <insert_5>.
0 : Information
This shows the correct usage.
None.
0 : Information
0 : Information
This shows the correct usage.
None.
40 : Stop Error
The option <insert_3> was specified on the command line to the application however this is not one of the valid set of command line options.
Check the usage information for the application and then retry.
40 : Stop Error
The application expects several mandatory command line options. One of these, <insert_3>, was not specified.
Check the usage information for the application and ensure that all required parameters are specified then retry.
40 : Stop Error
The value specified for command line option <insert_3> (<insert_4>) is invalid.
Check the usage information for the application and ensure that all options specify values in the valid range then retry.
40 : Stop Error
The WebSphere MQ queue manager <insert_3> does not exist.
Either create the queue manager (crtmqm command) or correct the queue manager name used in the command and then try the command again.
40 : Stop Error
The WebSphere MQ queue manager <insert_3> is not available because it has been stopped or is otherwise not contactable.
Use the strmqm command to start the message queue manager as necessary or correct any intermittent problems (eg. network connectivity) then try the command again.
40 : Stop Error
The queue <insert_3> could not be found, it may not have been created.
Ensure that the name of the queue specified is correct, queue names are case sensitive. If the queue is not created, use the runmqsc command to create it. Then try the command again.
40 : Stop Error
The error <insert_1> was returned unexpectedly to the application.
Save the generated output files and contact your IBM support center.
40 : Stop Error
The application received an exception from the underlying .NET framework, information about the exception follows:
<insert_4>
Examine the information contained within the exception to determine if it is possible to resolve locally.
If it is not possible to resolve the problem locally, save the generated output files and contact your IBM support center.
40 : Stop Error
The WebSphere MQ .NET Monitor attempted to load assembly <insert_3> but received an exception from the underlying .NET framework indicating that it could not be found. <insert_4>
Check that the assembly does exist and is accessible to the user running the application then retry.
If the assembly should be available, contact your IBM support center.
40 : Stop Error
The WebSphere MQ .NET monitor was unable to identify any classes in referenced assembly <insert_3> which implement the IMQObjectTrigger interface.
It is a requirement of the WebSphere MQ .NET monitor that either a single class implementing the IMQObjectTrigger interface exists in the referenced assembly or that a class is identified in that assembly to execute. Either modify the assembly to include a single class implementing IMQObjectTrigger or specify a class name on the command line and retry.
40 : Stop Error
The WebSphere MQ .NET monitor found <insert_1> classes in referenced assembly <insert_3> all of which implement the IMQObjectTrigger interface.
It is a requirement of the WebSphere MQ .NET monitor that either a single class implementing the IMQObjectTrigger interface exists in the referenced assembly or that a class is identified in that assembly to execute. Either modify the assembly to include a single class implementing IMQObjectTrigger or specify a class name on the command line and retry.
10 : Warning
Whilst processing queue <insert_3> a message whose backout count exceeded the specified backout threshold (<insert_1>) was successfully moved to <insert_4>
The message moved to the backout queue has a backout count greater than the backout threshold specified (or picked up from the input queue BOTHRESH attribute). You should investigate the reason why this message was rolled back onto the input queue and resolve that issue. If backout processing is not required, modify the command line options and or queue definitions to achieve the required behaviour from the .NET monitor.
40 : Stop Error
While processing queue <insert_3> a message whose backout count exceeded the specified backout threshold (<insert_1>) was encountered however, it was not possible to move it to either a backout queue or the dead-letter queue.
Because it was not possible to move the backed out message to another queue, it has been left on the input queue. As a result, the .NET monitor has ended.
It is possible that the backout queue or dead-letter queue are full or disabled for put - in this case, resolve this problem first.
If backout processing should have resulted in the message being placed on another queue, check the command line options, input queue definition and queue manager dead-letter queue attribute to ensure that they are correct, then retry.
0 : Information
This shows the correct usage.
None.
40 : Stop Error
The option <insert_3> was specified on the command line to the application however this is not one of the valid set of command line options.
Check the usage information for the application and then retry.
40 : Stop Error
The application expects mandatory command line options. One of these, <insert_3>, was not specified.
Check the usage information for the application and ensure that all required parameters are specified then retry.
40 : Stop Error
The value specified for command line option <insert_3> (<insert_4>) is invalid.
Check the usage information for the application and ensure that all options specify values in the valid range then retry.
40 : Stop Error
The WebSphere MQ queue manager <insert_3> does not exist.
Either create the queue manager (crtmqm command) or correct the queue manager name used in the command and then try the command again.
40 : Stop Error
The WebSphere MQ queue manager <insert_3> is not available because it has been stopped or is otherwise not contactable.
Use the strmqm command to start the message queue manager as necessary or correct any intermittent problems (eg. network connectivity) then try the command again.
40 : Stop Error
The queue <insert_3> could not be found, it may not have been created.
Ensure that the name of the queue specified is correct, queue names are case sensitive. If the queue is not created, use the runmqsc command to create it. Then try the command again.
40 : Stop Error
The error <insert_1> was returned unexpectedly to the application.
Save the generated output files and contact your IBM support center.
40 : Stop Error
The application received an exception from the underlying .NET framework, information about the exception follows:
<insert_4>
Examine the information contained within the exception to determine if it is possible to resolve locally.
If it is not possible to resolve the problem locally, save the generated output files and contact your IBM support center.
0 : Information
The MQSC script contains <insert_1> commands.
None.
0 : Information
The MQSC script contains <insert_1> commands having a syntax error.
None.
0 : Information
The MQSC script contains <insert_1> commands that failed to process.
None.
0 : Information
An MQSC command has been recognized, but cannot be processed.
None.
0 : Information
The MQSC script contains <insert_1> commands having a syntax error.
None.
0 : Information
An MQSC command contains a continuation character, but the 'end of input' has been reached without completing the command.
None.
0 : Information
The MQSC DISPLAY PROCESS command completed successfully, and details follow this message.
None.
0 : Information
The MQSC DISPLAY QMGR command completed successfully, and details follow this message.
None.
0 : Information
The MQSC DISPLAY QUEUE command completed successfully, and details follow this message.
None.
0 : Information
The MQSC Parser has an internal error.
None.
0 : Information
A command in the MQSC script contains duplicate keywords.
None.
0 : Information
The value assigned to an MQSC command keyword is out of the permitted range.
None.
0 : Information
A string assigned to an MQSC keyword is either NULL, or longer than the maximum permitted for that keyword.
None.
0 : Information
The MQSC DISPLAY CHL command completed successfully, and details follow this message.
None.
0 : Information
The MQSC PING QMGR command completed successfully.
None.
0 : Information
MQSC did not receive a response message from the remote command server in the time specified.
None.
0 : Information
The MQSC DISPLAY CHANNEL STATUS command completed successfully, and details follow this message.
None.
0 : Information
Running in queued mode, <insert_1> command responses were received from the remote command server.
None.
0 : Information
The Queue is already in the cell, that is, its SCOPE attribute is already CELL.
None.
0 : Information
No status was found for the specified channel(s).
None.
0 : Information
A keyword required in this command was not specified.
None.
0 : Information
MQSC found additional command responses on the reply q. They will fill follow this message.
None.
0 : Information
The DCE cell directory is not available, so the requested operation has failed.
None.
0 : Information
A keyword in an MQSC command contained a name string which was not valid. This may be because it contained characters which are not accepted in MQ names. Typical keywords which can produce this error are QLOCAL (and the other q types), CHANNEL, XMITQ, INITQ, MCANAME etc.
None.
0 : Information
A keyword in an MQSC command contained a value that was not valid.
None.
0 : Information
The text shows valid MQSC commands.
None.
0 : Information
The text shown is the valid syntax for the MQSC command.
None.
0 : Information
The TYPE has already been specified after the DISPLAY verb, for example DISPLAY QUEUE(*) type(QLOCAL) type(QALIAS).
Delete the second TYPE keyword and run the command again.
0 : Information
A syntax error occurred an the exit parameter. This may be because it contained characters which are not accepted as exit names. Check the parameters in the MSGEXIT, RCVEXIT, SCYEXIT and SENDEXIT definitions.
None.
0 : Information
The Remote queue manager name is not known to this queue manager. Check that a transmission queue of the same name as the remote queue manager name exists.
Create a transmission queue of the same name as the remote queue manager if one does not exist.
0 : Information
The transmission queue does not exist on this queue manager.
None.
0 : Information
An attempt to set both the REPOS and REPOSNL fields has been made. Only one of these fields can have a value other than blank. Both of the fields may be blank.
None.
0 : Information
An attempt to set both the CLUSTER and CLUSNL fields has been made. Only one of these fields can have a value other than blank. Both of the fields may be blank.
None.
0 : Information
The repository is unavailable and the data cannot be accessed. Stop and restart the queue manager.
None.
0 : Information
The MQSC script contains no commands that failed to process.
None.
0 : Information
The MQSC script contains one command that failed to process.
None.
0 : Information
The MQSC script contains no commands.
None.
0 : Information
The MQSC script contains one command.
None.
0 : Information
The MQSC script contains no commands having a syntax error.
None.
0 : Information
The MQSC script contains one command which has a syntax error.
None.
0 : Information
The MQSC DISPLAY CLUSQMG command completed successfully, and details follow this message.
None.
0 : Information
An attempt has been made to set USAGE to XMITQ when the CLUSTER or CLUSNL field has a value. Change the value of USAGE, or set the CLUSTER and CLUSNL fields to blank, and try the command again.
None.
0 : Information
An attempt has been made to set USAGE to *TMQ when the CLUSTER or CLUSNL field has a value. Change the value of USAGE, or set the CLUSTER and CLUSNL fields to blank, and try the command again.
None.
0 : Information
An attempt has been made to set both CLUSTER and CLUSNL fields. One and only one of the fields may have a value, the other field must be blank. Change the value of one of the fields to blank and try the command again.
None.
0 : Information
Both the CLUSTER and CLUSNL fields are blank. One and only one of the fields may be blank, the other field must be a value. Change one of the fields from blank to a value and try the command again.
None.
30 : Severe error
An attempt to open a queue manager object has failed.
See the previously listed messages in the job log.
30 : Severe error
The requested operation failed because the channel is currently active.
See the previously listed messages in the job log.
30 : Severe error
The operation requested cannot be performed because channel <insert_5> is not of a suitable type. For example, only sender, server and cluster-sender channels can be resolved.
Check that the correct operation was requested. If it was, check that the correct channel name was specified.
30 : Severe error
A request to end channel <insert_5> has failed because the channel is not running.
Check that the correct operation was requested. If it was, check that the correct channel name was specified.
30 : Severe error
An MQGET failed because the queue <insert_5> had been previously inhibited for MQGET.
None.
0 : Information
The MQSC DISPLAY QSTATUS command completed successfully. Details follow this message.
0 : Information
The STATUS(*STOPPED) parameter is not allowed when specifying CONNAME on the ENDMQMCHL command.
Remove the CONNAME parameter from the command or, specify STATUS(*INACTIVE) to end the channel instance for the specified connection name.
0 : Information
The STATUS(*STOPPED) parameter is not allowed when specifying RQMNAME on the ENDMQMCHL command.
Remove the RQMNAME parameter from the command or, specify STATUS(*INACTIVE) to end the channel instance for the specified remote queue manager.
20 : Error
You typed a path which was not syntactically correct for the operating system you are running WebSphere MQ on.
Determine the correct syntax of a path name for the operating system you are running WebSphere MQ on and use this information to type in a valid path.
20 : Error
The data you entered for <insert_3> does not conform to the syntax rules laid down by WebSphere MQ for this parameter.
Carefully check the data entered for this parameter in conjunction with the WebSphere MQ Command Reference to determine the cause of error.
20 : Error
The password string length is rounded up by WebSphere MQ to the nearest eight bytes. This rounding causes the total length of the SSLCRYP string to exceed its maximum.
Decrease the size of the password, or of earlier fields in the SSLCRYP string.
20 : Error
The command contains parameters that cannot be used together.
Refer to the WebSphere MQ Script (MQSC) Command Reference to determine an allowable combination of parameters for this command.
0 : Information
The STOP CONN command successfully stopped the connection that was specified.
None.
0 : Information
The STOP CONN command could not stop the connection that was specified.
None.
0 : Information
You specified an identifier that was not found. Please try the command again and supply a valid identifier.
None.
0 : Information
You specified an invalid connection identifier. A valid connection identifier contains 16 hex characters, where all of the characters in the connection identifier should lie within the range 0-9, a-z or A-Z.
Correct the connection identifier so that it conforms to the above specification.
0 : Information
You specified a connection identifier which is not associated with this queue manager.
Correct the connection identifier so that it describes a connection identifier which is associated with this queue manager. Use the command DISPLAY CONN to identify potential connection identifiers to use with this command.
0 : Information
The MQSC script contains <insert_1> commands.
None.
0 : Information
None.
None.
0 : Information
20 : Error
A request by the command server to initialize common services failed with return code <insert_1>.
None.
20 : Error
A request by the command server to connect shared memory failed with return code <insert_1>.
None.
20 : Error
A request by the command server to post an event semaphore failed with return code <insert_1>.
None.
20 : Error
An MQINQ request by the command server, for the WebSphere MQ queue <insert_3>, failed with reason code <insert_1>.
None.
20 : Error
A request by the command server to reallocate memory failed with return code <insert_1>.
None.
20 : Error
An MQGET request by the command server, for the WebSphere MQ queue <insert_3>, failed with reason code <insert_1>.
None.
20 : Error
An attempt by the command server to put a message to the dead-letter queue, using MQPUT1, failed with reason code <insert_1>. The MQDLH reason code was <insert_2>.
None.
20 : Error
A request by the command server to delete a queue manager object list failed with return code <insert_1>.
None.
20 : Error
An MQCLOSE request by the command server for the reply-to queue failed with reason code <insert_1>.
None.
30 : Severe error
0 : Information
0 : Information
0 : Information
20 : Error
The command server has not reported the status of running, to the start request, before the timeout of <insert_1> seconds was reached.
None.
0 : Information
The total length of a channel exit string is 999 characters. The string list assigned to an MQSC keyword is longer than the maximum value of 999 characters permitted for that keyword.
None.
0 : Information
The MQSC DISPLAY NAMELIST command completed successfully, and details follow this message.
None.
0 : Information
WebSphere MQ namelist <insert_5> changed.
None.
0 : Information
WebSphere MQ namelist <insert_5> created.
None.
0 : Information
WebSphere MQ namelist <insert_5> deleted.
None.
0 : Information
The number of strings within the stringlist is greater than the maximum number allowed for the keyword. Reduce the number of strings within the list and try the command again.
None.
0 : Information
A string in a string list assigned to a keyword is longer than the maximum permitted for that keyword.
None.
0 : Information
The RESUME QUEUE MANAGER command has been accepted for processing. The command will be sent to the repository which will process the command and notify all other repositories that this queue manager is now back in the cluster.
None.
0 : Information
The SUSPEND QUEUE MANAGER command has been accepted for processing. The command will be sent to the repository which will process the command and notify all other repositories that this queue manager is leaving the cluster.
None.
0 : Information
The REFRESH CLUSTER command has been accepted for processing. The command will be sent to the Repository which will process the command and notify all other repositories that the Cluster needs refreshing.
None.
0 : Information
The RESET CLUSTER command has been accepted for processing. The command will be sent to the Repository which will process the command and notify all other repositories that the Cluster needs resetting.
None.
0 : Information
The Object Authority Manager security cache has been refreshed.
None.
10 : Warning
WebSphere MQ was unable to contact the domain controller to obtain information for user <insert_3>.
Ensure that a domain controller for the domain on which user <insert_3> is defined is available. Alternatively, if you are using a computer which is not currently connected to the network and have logged on using a domain user ID, you may wish to log on using a local user ID instead.
0 : Information
WebSphere MQ authentication information object <insert_5> created.
None.
0 : Information
WebSphere MQ authentication information object <insert_5> deleted.
None.
0 : Information
Queue Status for the specified queue could not be found.
None.
0 : Information
The MQSC DISPLAY AUTHINFO command completed successfully. Details follow this message.
None.
0 : Information
WebSphere MQ authentication information <insert_5> changed.
None.
0 : Information
There are no matching authinfo objects defined on this system.
Using the DEFINE AUTHINFO command to create an authinfo object.
0 : Information
You specified an invalid filter. Check the WHERE statement and make sure that the operator is valid for the type of parameter, that the parameter can be filtered on, and that the value that you specified for the filter is valid for the type of attribute you are filtering on.
None.
0 : Information
The keyword <insert_3> contained a value that was not valid for this configuration. Please check the MQSC Command Reference to determine valid values for <insert_3>.
None.
0 : Information
The WebSphere MQ trigger monitor has been started.
None.
0 : Information
The trigger monitor has been started with initiation queue <insert_3>.
None.
0 : Information
The WebSphere MQ trigger monitor has ended.
None.
0 : Information
None.
None.
0 : Information
The trigger monitor cannot be run due to lack of authority to the requested queue manager or initiation queue.
Obtain the necessary authority from your security officer or WebSphere MQ administrator. Then try the command again.
0 : Information
The queue manager specified for the trigger monitor does not exist, or is not active.
Check that you named the correct queue manager. Ask your systems administrator to start it, if it is not active. Then try the command again.
0 : Information
There was insufficient storage available for the WebSphere MQ trigger monitor to run.
Free some storage and then try the command again.
0 : Information
The trigger monitor's connection to the requested queue manager failed because of MQI reason code <insert_1> from MQCONN.
Consult your systems administrator about the state of the queue manager.
0 : Information
The connection to the queue manager failed while the trigger monitor was running. This may be caused by an endmqm command being issued by another user, or by a queue manager error.
Consult your systems administrator about the state of the queue manager.
0 : Information
The named initiation queue could not be found; or the queue type is not correct for an initiation queue.
Check that the named queue exists, and is a local queue, or that the named queue is an alias for a local queue which exists.
0 : Information
The WebSphere MQ trigger monitor could not open the initiation queue because the queue is open for exclusive use by another application.
Wait until the queue is no longer in use, and try the command again.
0 : Information
The WebSphere MQ trigger monitor could not open the initiation queue; reason code <insert_1> was returned from MQOPEN.
Consult your systems administrator.
0 : Information
The WebSphere MQ trigger monitor is waiting for a message to arrive on the initiation queue.
None.
0 : Information
The WebSphere MQ trigger monitor is unable to continue because the initiation queue has been deleted or changed since it was opened.
Retry the command.
0 : Information
The WebSphere MQ trigger monitor cannot read from the initiation queue because input is not enabled.
Ask your systems administrator to enable the queue for input.
0 : Information
The WebSphere MQ trigger monitor failed because of MQI reason code <insert_1> from MQGET.
Consult your systems administrator.
0 : Information
The action to trigger an application has been completed.
None.
0 : Information
The WebSphere MQ trigger monitor received a message that is not recognized as a valid trigger message. It has been written to the undelivered message queue.
Consult your systems administrator.
0 : Information
An error was detected when trying to start the application identified in a trigger message.
Check that the application the trigger monitor was trying to start is available.
0 : Information
A trigger message was received which specifies application type <insert_1>; the trigger monitor does not support this type.
Use an alternative trigger monitor for this initiation queue.
0 : Information
The trigger monitor received a message with a warning. For example, it may have been truncated or it could not be converted to the trigger monitor's data representation. The reason code for the warning is <insert_1>.
None.
0 : Information
None.
None.
0 : Information
None.
None.
0 : Information
WebSphere MQ listener <insert_5> changed.
None.
0 : Information
WebSphere MQ service <insert_5> changed.
None.
0 : Information
WebSphere MQ service <insert_5> created.
None.
0 : Information
WebSphere MQ listener <insert_5> created.
None.
0 : Information
WebSphere MQ service object <insert_5> deleted.
None.
0 : Information
WebSphere MQ listener object <insert_5> deleted.
None.
0 : Information
The MQSC DISPLAY SERVICE command completed successfully. Details follow this message.
None.
0 : Information
The MQSC DISPLAY LISTENER command completed successfully. Details follow this message.
None.
0 : Information
The MQSC DISPLAY LSSTATUS command completed successfully. Details follow this message.
0 : Information
The MQSC DISPLAY SVSTATUS command completed successfully. Details follow this message.
0 : Information
The MQSC RESET QMGR command completed successfully. Details follow this message.
None.
0 : Information
The DSPMQRTE command was expecting activity information but it was unavailable. This does not always constitute an error. Reasons why the activity information is unavailable include the following:
1) One of the queue managers on the route did not support trace-route messaging.
2) One of the queue managers on the route did not allow route information to be returned to the reply queue. See the documentation on the ActivityRecording and TraceRouteRecording queue manager attributes for more details.
3) The report could not a find route back to the reply queue.
Try and determine whether the activity information should have been available. Running the command with the 'outline' verbosity option (used with the -v flag) may be useful in determining where the message was when the activity information was generated.
0 : Information
The DSPMQMRTE command was expecting activity information but it was unavailable. This does not always constitute an error. Reasons why the activity information is unavailable include the following:
1) One of the queue managers on the route did not support trace-route messaging.
2) One of the queue managers on the route did not allow route information to be returned to the reply queue. See the documentation on the ActivityRecording and TraceRouteRecording queue manager attributes for more details.
3) The report could not a find route back to the reply queue.
Try and determine whether the activity information should have been available. Running the command with DSPINF(*ALL) may be useful in determining where the message was when the activity information was generated.
0 : Information
The DSPMQRTE command has finished processing your request but an execution error was detected. Previous messages issued by the command can be used to identify the error.
Refer to previous messages issued by the command.
0 : Information
The DSPMQMRTE command has finished processing your request but an execution error was detected. Previous messages issued by the command can be used to identify the error.
Refer to previous messages issued by the command.
0 : Information
The DSPMQRTE command has finished processing your request and no execution errors were detected.
None.
0 : Information
The DSPMQMRTE command has finished processing your request and no execution errors were detected.
None.
0 : Information
You have started the DSPMQRTE command with command line options <insert_3> and the command is now processing your request.
Wait for the command to finish processing your request. Any further messages that are issued can be used to determine the outcome of the request.
0 : Information
You have started the DSPMQMRTE command and the command is now processing your request.
Wait for the command to finish processing your request. Any further messages that are issued can be used to determine the outcome of the request.
0 : Information
The DSPMQRTE command has received confirmation of the successful arrival of the trace-route message at its destination queue on queue manager <insert_3>.
None.
0 : Information
The DSPMQMRTE command has received confirmation of the successful arrival of the trace-route message at its destination queue on queue manager <insert_3>.
None.
0 : Information
The DSPMQRTE command has received confirmation that the trace-route message has expired.
The expiry interval of trace-route messages generated by the DSPMQRTE command can be altered using the -xs option if this is required.
0 : Information
The DSPMQMRTE command has received confirmation that the trace-route message has expired.
The expiry interval of trace-route messages generated by the DSPMQMRTE command can be altered using the EXPIRY parameter if this is required.
0 : Information
The DSPMQRTE command trace-route message caused an exception on queue manager <insert_4>. The Feedback field in the report was <insert_1> or <insert_3>.
Use the feedback given to determine why the trace-route message caused the exception.
0 : Information
The DSPMQMRTE command trace-route message caused an exception on queue manager <insert_4>. The Feedback field in the report was <insert_1> or <insert_3>.
Use the feedback given to determine why the trace-route message caused the exception.
0 : Information
You started the DSPMQRTE command specifying that it should generate a trace-route message. This took place and the trace-route message had <insert_3> X<insert_4>.
The <insert_3> can be used to retrieve responses to this trace-route request. Run the DSPMQRTE command again specifying this identifier with the -i flag and with the target queue specified as the queue where the responses are expected to return or where the trace-route message is expected to have arrived. This may be on another queue manager.
0 : Information
You started the DSPMQMRTE command specifying that it should generate a trace-route message. This took place and the trace-route message had <insert_3> X<insert_4>.
The <insert_3> can be used to retrieve responses to this trace-route request. Run the DSPMQMRTE command again specifying this identifier for CRLLID and with the target queue specified as the queue where the responses are expected to return or where the trace-route message is expected to have arrived. This may be on another queue manager.
0 : Information
The request for the DSPMQRTE command to put a trace-route message on the target queue was unsuccessful. Previous messages issued by the command can be used to identify why the message could not be put on the target queue.
Refer to previous messages issued by the command.
0 : Information
The request for the DSPMQMRTE command to put a trace-route message on the target queue was unsuccessful. Previous messages issued by the command can be used to identify why the message could not be put on the target queue.
Refer to previous messages issued by the command.
0 : Information
The request for the DSPMQRTE command to put a message on the target queue was successful. The target queue resolved to <insert_3> on queue manager <insert_4>.
None.
0 : Information
The request for the DSPMQMRTE command to put a message on the target queue was successful. The target queue resolved to <insert_3> on queue manager <insert_4>.
None.
0 : Information
The DSPMQRTE command received the following activities, but they could not be printed in the correct order. This is commonly because an activity report has been received that does not contain a TraceRoute PCF group or is missing the RecordedActivities parameter which would allow it to be ordered correctly.
Find and correct the application that is generating activity reports without the necessary information for them to be ordered correctly.
0 : Information
The DSPMQMRTE command received the following activities, but they could not be printed in the correct order. This is commonly because an activity report has been received that does not contain a TraceRoute PCF group or is missing the RecordedActivities parameter which would allow it to be ordered correctly.
Find and correct the application that is generating activity reports without the necessary information for them to be ordered correctly.
20 : Error
You started the DSPMQRTE command specifying that the trace-route message should not be delivered to a local queue (-d yes was not specified). However, it has been determined that the target queue does not resolve to a transmission queue. Therefore the DSPMQRTE command has chosen not to put the trace-route message to the target queue <insert_3> on queue manager <insert_4>.
Determine whether it was expected that the target queue would resolve to a local queue.
20 : Error
You started the DSPMQMRTE command specifying that the trace-route message should not be delivered to a local queue (DLVRMSG(*NO) was specified). However, it has been determined that the target queue does not resolve to a transmission queue. Therefore the DSPMQMRTE command has chosen not to put the trace-route message to the target queue <insert_3> on queue manager <insert_4>.
Determine whether it was expected that the target queue would resolve to a local queue.
0 : Information
The DSPMQRTE command has received confirmation of the successful delivery of the trace-route message on queue manager <insert_3> to a requesting application.
None.
0 : Information
The DSPMQMRTE command has received confirmation of the successful delivery of the trace-route message on queue manager <insert_3> to a requesting application.
None.
20 : Error
An attempt was made to connect to a queue manager using a client connection. However, client connections are not supported in your environment.
Connect to the queue manager using a server connection.
20 : Error
You started the DSPMQRTE command specifying that it should connect to queue manager <insert_3>. The command could not connect to that queue manager. Previous messages issued by the command can be used to identify the error.
Refer to previous messages issued by the command.
20 : Error
You started the DSPMQMRTE command specifying that it should connect to queue manager <insert_3>. The command could not connect to that queue manager. Previous messages issued by the command can be used to identify the error.
Refer to previous messages issued by the command.
20 : Error
You started the DSPMQRTE command specifying option -i with a CorrelId <insert_3> that was invalid. The CorrelId was either too long or not in the correct format.
Refer to the command syntax, and then try the command again.
20 : Error
You started the DSPMQMRTE command specifying CRLLID with a CorrelId <insert_3> that was invalid.
Refer to the command syntax, and then try the command again.
0 : Information
The DSPMQRTE command trace-route message has been confirmed as having taken a route involving queue <insert_3> on queue manager <insert_4> in an attempt to reach the destination queue.
Wait for subsequent messages which may indicate another queue which the message has been routed through.
0 : Information
The DSPMQMRTE command trace-route message has been confirmed as having taken a route involving queue <insert_3> on queue manager <insert_4> in an attempt to reach the destination queue.
Wait for subsequent messages which may indicate another queue which the message has been routed through.
20 : Error
You started the DSPMQRTE command specifying reply queue <insert_3>. However the DSPMQRTE command could not successfully open a queue of that name on queue manager <insert_4>. Previous messages issued by the command can be used to identify the error. If the -rq option was not specified then the reply queue will be a temporary dynamic queue modelled on SYSTEM.DEFAULT.MODEL.QUEUE.
Refer to previous messages issued by the command. Specify a reply queue that can be opened and then retry the command.
20 : Error
You started the DSPMQMRTE command specifying reply queue <insert_3>. However the DSPMQMRTE command could not successfully open a queue of that name on queue manager <insert_4>. Previous messages issued by the command can be used to identify the error. If the RPLYQ parameter was not specified then the reply queue will be a temporary dynamic queue modelled on SYSTEM.DEFAULT.MODEL.QUEUE.
Refer to previous messages issued by the command. Specify a reply queue that can be opened and then retry the command.
20 : Error
You started the DSPMQRTE command specifying queue <insert_3>, using the -q option. However the DSPMQRTE command could not successfully open a queue of that name on queue manager <insert_4>. Previous messages issued by the command can be used to identify the error.
Refer to previous messages issued by the command. Specify a queue, using the -q option, that can be opened and then retry the command.
20 : Error
You started the DSPMQMRTE command specifying queue <insert_3> for the QNAME parameter. However the DSPMQMRTE command could not successfully open a queue of that name on queue manager <insert_4>. Previous messages issued by the command can be used to identify the error.
Refer to previous messages issued by the command. Specify a queue, using the QNAME parameter, that can be opened and then retry the command.
20 : Error
The DSPMQRTE command attempted to resolve queue manager <insert_3> (supplied by the -qm option) on queue manager <insert_4> but the attempt failed. The queue specified by the -q option could not be opened.
Ensure that queue manager <insert_3> can be resolved on queue manager <insert_4> or specify a different queue manager with the -qm option. Retry the command.
20 : Error
The DSPMQMRTE command attempted to resolve queue manager <insert_3> (supplied by the TGTMQM parameter) on queue manager <insert_4> but the attempt failed. The queue specified by the QNAME parameter could not be opened.
Ensure that queue manager <insert_3> can be resolved on queue manager <insert_4> or specify a different queue manager with the TGTMQM parameter. Retry the command.
20 : Error
An attempt to dynamically load the server module <insert_3> failed. Typically this is because only the client modules are installed.
Check which modules are installed and retry the command with the -c option specified if applicable.
20 : Error
The DSPMQRTE command was expecting a reply queue specified by the -rq option but no reply queue was specified. Specifying a reply queue is mandatory if both the -n (no display) option and a response generating option (-ar or -ro [activity|coa|cod|exception|expiration]) is specified.
Specify a reply queue and retry the command.
20 : Error
The DSPMQRTE command attempted to get a message from queue <insert_3>, queue manager <insert_4>, but the attempt failed. Previous messages issued by the command can be used to identify the error.
Refer to previous messages issued by the command.
20 : Error
The DSPMQMRTE command attempted to get a message from queue <insert_3>, queue manager <insert_4>, but the attempt failed. Previous messages issued by the command can be used to identify the error.
Refer to previous messages issued by the command.
20 : Error
You started the DSPMQRTE command specifying option <insert_3> with an object name <insert_4> that is invalid. In general, the names of WebSphere MQ objects can have up to 48 characters. An object name can contain the following characters:
1) Uppercase alphabetic characters (A through Z).
2) Lowercase alphabetic characters (a through z).
3) Numeric digits (0 through 9).
4) Period (.), forward slash (/), underscore (_), percent (%).
See the WebSphere MQ System Administration documentation for further details and restrictions.
Specify a valid object name and then try the command again.
20 : Error
You started the DSPMQMRTE command specifying an object name <insert_4> that is invalid. In general, the names of WebSphere MQ objects can have up to 48 characters. An object name can contain the following characters:
1) Uppercase alphabetic characters (A through Z).
2) Lowercase alphabetic characters (a through z).
3) Numeric digits (0 through 9).
4) Period (.), forward slash (/), underscore (_), percent (%).
See the WebSphere MQ System Administration documentation for further details and restrictions.
Specify a valid object name and then try the command again.
0 : Information
The DSPMQRTE command has successfully generated and put the trace-route message and is now waiting for responses to be returned to the reply queue to indicate the route that the trace-route message took to its destination.
Wait for responses to be returned to the reply queue and for the information about the route to be displayed.
0 : Information
The DSPMQMRTE command has successfully generated and put the trace-route message and is now waiting for responses to be returned to the reply queue to indicate the route that the trace-route message took to its destination.
Wait for responses to be returned to the reply queue and for the information about the route to be displayed.
20 : Error
You started the DSPMQRTE command specifying an option of <insert_3> that was not recognized. The command will end.
Refer to the command syntax and retry the command.
20 : Error
You started the DSPMQRTE command specifying a combination of the options that is not valid. The -i option cannot be specified with one or more of the following options: -ac, -ar, -d, -f, -l, -n, -o, -p, -qm, -ro, -rq, -rqm, -s, -t, -xs, -xp. The -n option cannot be specified with one or more of the following options: -b, -i, -v, -w. The -ar option can only be specified if the -ac option has also been specified. The -rqm option can only be specified if the -rq option has also been specified.
Refer to the command documentation and then try the command again.
20 : Error
You started the DSPMQRTE command specifying values for option <insert_3> that conflict. At least two values were specified for the same option but they conflict with each other. The DSPMQRTE command will end.
Refer to the command syntax and then try the command again.
20 : Error
You started the DSPMQMRTE command specifying values that conflict. At least two values were specified for the same parameter but they conflict with each other. The DSPMQMRTE command will end.
Refer to the command syntax and then try the command again.
20 : Error
You started the DSPMQRTE command specifying an invalid option value. The <insert_4> value for option <insert_3> is either not recognized or of an incorrect format.
Refer to the command syntax, and then try the command again.
20 : Error
You started the DSPMQMRTE command specifying an invalid parameter value. Value <insert_4> is either not recognized or of an incorrect format.
Refer to the command syntax, and then try the command again.
20 : Error
It was specified that the DSPMQRTE command should put a persistent trace-route message on the target queue (see the documentation for the -l option). However, persistent messages are not allowed on the reply queue because it is a temporary dynamic queue and persistent responses were expected to return to it. The trace-route message was not put on the target queue.
Ensure that the reply queue is not a temporary dynamic queue. Use the -rq option to specify the reply queue.
20 : Error
It was specified that the DSPMQMRTE command should put a persistent trace-route message on the target queue (see the documentation for the MSGPST parameter). However, persistent messages are not allowed on the reply queue because it is a temporary dynamic queue and persistent responses were expected to return to it. The trace-route message was not put on the target queue.
Ensure that the reply queue is not a temporary dynamic queue. Use the RPLYQ parameter to specify the reply queue.
20 : Error
The DSPMQRTE command tried to open queue manager <insert_3> for inquire but the open failed. Previous messages issued by the command can be used to identify the error.
Refer to previous messages issued by the command.
20 : Error
The DSPMQMRTE command tried to open queue manager <insert_3> for inquire but the open failed. Previous messages issued by the command can be used to identify the error.
Refer to previous messages issued by the command.
20 : Error
The DSPMQRTE command has detected an error from an MQI call during the execution of your request. The reason for failure is <insert_1> or <insert_3>.
See the WebSphere MQ Messages documentation for an explanation of the reason for failure. Follow any correction action and retry the command.
20 : Error
The DSPMQMRTE command has detected an error from an MQI call during the execution of your request. The reason for failure is <insert_1> or <insert_3>.
See the WebSphere MQ Messages documentation for an explanation of the reason for failure. Follow any correction action and retry the command.
0 : Information
The DSPMQRTE command successfully put a trace-route message on the target queue and it was then delivered by queue manager <insert_4> to application <insert_3> which processed the message.
Determine if it was expected that this application would process the trace-route message.
0 : Information
The DSPMQMRTE command successfully put a trace-route message on the target queue and it was then delivered by queue manager <insert_4> to application <insert_3> which processed the message.
Determine if it was expected that this application would process the trace-route message.
0 : Information
The DSPMQRTE command trace-route message was rejected after the number of activities of which it was a participant reached the maximum activities limit. The limit was set to <insert_1>. The maximum activities limit is set using the -s option.
Using the output from the command determine whether it is expected that the trace-route message should have reached the maximum activities limit.
0 : Information
The DSPMQMRTE command trace-route message was rejected after the number of activities of which it was a participant reached the maximum activities limit. The limit was set to <insert_1>. The maximum activities limit is set using the MAXACTS parameter.
Using the output from the command determine whether it is expected that the trace-route message should have reached the maximum activities limit.
0 : Information
The DSPMQRTE command trace-route message was rejected because it was about to be sent to a queue manager which does not support trace-route messaging. This behaviour was requested because the forwarding options specified on the command only allowed the trace-route message to be forwarded to queue managers which support trace-route messaging. Sending a trace-route message to a queue manager which cannot process it in accordance with its specified options could cause undesirable results, including having the trace-route message be put to a local queue on the remote queue manager. If this is acceptable then the '-f all' option can be specified.
Retry the command with different forwarding options, if appropriate.
0 : Information
The DSPMQMRTE command trace-route message was rejected because it was about to be sent to a queue manager which does not support trace-route messaging. This behaviour was requested because the forwarding options specified on the command only allowed the trace-route message to be forwarded to queue managers which support trace-route messaging. Sending a trace-route message to a queue manager which cannot process it in accordance with its specified options could cause undesirable results, including having the trace-route message be put to a local queue on the remote queue manager. If this is acceptable then FWDMSG(*ALL) can be specified.
Retry the command with different forwarding options, if appropriate.
20 : Error
The DSPMQRTE command trace-route message was rejected because one or more of the forwarding options was not recognized and it was in the MQROUTE_FORWARD_REJ_UNSUP_MASK bitmask. The forwarding options, when they were last observed, in hexadecimal were X<insert_1>.
Change the application that inserted the forwarding options that were not recognized to insert valid and supported forwarding options.
20 : Error
The DSPMQMRTE command trace-route message was rejected because one or more of the forwarding options was not recognized and it was in the MQROUTE_FORWARD_REJ_UNSUP_MASK bitmask. The forwarding options, when they were last observed, in hexadecimal were X<insert_1>.
Change the application that inserted the forwarding options that were not recognized to insert valid and supported forwarding options.
20 : Error
The DSPMQRTE command trace-route message was rejected because one or more of the delivery options was not recognized and it was in the MQROUTE_DELIVER_REJ_UNSUP_MASK bitmask. The delivery options, when they were last observed, in hexadecimal were X<insert_1>.
Change the application that inserted the delivery options that were not recognized to insert valid and supported delivery options.
20 : Error
The DSPMQMRTE command trace-route message was rejected because one or more of the delivery options was not recognized and it was in the MQROUTE_DELIVER_REJ_UNSUP_MASK bitmask. The delivery options, when they were last observed, in hexadecimal were X<insert_1>.
Change the application that inserted the delivery options that were not recognized to insert valid and supported delivery options.
0 : Information
The program operation was interrupted by a SIGINT signal on UNIX systems or a CTRL+c/CTRL+BREAK signal on Windows systems. The program is now ending.
Wait for the program to end.
20 : Error
The DSPMQRTE command has detected an unexpected error during execution of your request. The reason for failure is <insert_1> or <insert_3>. The WebSphere MQ error recording routine has been called.
Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
20 : Error
The DSPMQMRTE command has detected an unexpected error during execution of your request. The reason for failure is <insert_1> or <insert_3>. The WebSphere MQ error recording routine has been called.
Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
20 : Error
An attempt to dynamically load the client module <insert_3> failed. Typically this is because the client modules are not installed.
Check which modules are installed and retry the command without the -c option specified, if applicable.
0 : Information
None.
None.
0 : Information
None.
None.
0 : Information
None.
None.
0 : Information
The MQSC DISPLAY QMSTATUS command completed successfully. Details follow this message.
None.
0 : Information
The channel listener program has been requested to stop. This command executes asynchronously so may complete after this message has been displayed.
Further information on the progress of the request is available in the queue manager error log.
0 : Information
0 : Information
The dead-letter queue handler (runmqdlq) has been started and has parsed the input file without detecting any errors and is about to start processing the queue identified in the message.
None.
0 : Information
The dead-letter queue handler (STRMQMDLQ) has been started and has parsed the input file without detecting any errors and is about to start processing the queue identified in the message.
None.
0 : Information
The dead-letter queue handler (runmqdlq) is ending because the WAIT interval has expired and there are no messages on the dead-letter queue, or because the queue manager is shutting down, or because the dead-letter queue handler has detected an error. If the dead-letter queue handler has detected an error, an earlier message will have identified the error.
None.
0 : Information
The dead-letter queue handler (STRMQMDLQ) is ending because the WAIT interval has expired and there are no messages on the dead-letter queue, or because the queue manager is shutting down, or because the dead-letter queue handler has detected an error. If the dead-letter queue handler has detected an error, an earlier message will have identified the error.
None.
0 : Information
Syntax for the usage of runmqdlq.
None.
10 : Warning
Execution of the command <insert_3> caused job <insert_5> to be started, but the job terminated unexpectedly.
Consult the log for job <insert_5> to determine why it was terminated.
10 : Warning
The dead-letter queue handler (runmqdlq) retrieved a message from the nominated dead-letter queue, but the message was not prefixed by a recognizable MQDLH. This typically occurs because an application is writing directly to the dead-letter queue but is not prefixing messages with a valid MQDLH. The message is left on the dead-letter queue and the dead-letter queue handler continues to process the dead-letter queue. Each time the dead-letter queue handler repositions itself to a position before this message to process messages that could not be processed on a previous scan it will reprocess the failing message and will consequently re-issue this message.
Remove the invalid message from the dead-letter queue. Do not write messages to the dead-letter queue unless they have been prefixed by a valid MQDLH. If you require a dead-letter queue handler that can process messages not prefixed by a valid MQDLH, you must change the sample program called amqsdlq to cater for your needs.
10 : Warning
The dead-letter queue handler (STRMQMDLQ) retrieved a message from the nominated dead-letter queue, but the message was not prefixed by a recognizable MQDLH. This typically occurs because an application is writing directly to the dead-letter queue but is not prefixing messages with a valid MQDLH. The message is left on the dead-letter queue and the dead-letter queue handler continues to process the dead-letter queue. Each time the dead-letter queue handler repositions itself to a position before this message to process messages that could not be processed on a previous scan it will reprocess the failing message and will consequently re-issue this message.
Remove the invalid message from the dead-letter queue. Do not write messages to the dead-letter queue unless they have been prefixed by a valid MQDLH. If you require a dead-letter queue handler that can process messages not prefixed by a valid MQDLH, you must change the sample program called amqsdlq to cater for your needs.
10 : Warning
This message is produced by the dead-letter queue handler when it is requested to redirect a message to another queue but is unable to do so. If the reason that the redirect fails is the same as the reason the message was put to the dead-letter queue then it is assumed that no new error has occurred and no message is produced. The retry count for the message will be incremented and the dead-letter queue handler will continue.
Investigate why the dead-letter queue handler was unable to put the message to the dead-letter queue. The line number of the rule used to determine the action for the message should be used to help identify to which queue the dead-letter queue handler attempted to PUT the message.
10 : Warning
A request was made to stop a listener, however the listener could not be stopped at this time. Reasons why a listener could not be stopped are:
The listener has active channels and the communications protocol being used is LU 6.2, SPX or NETBIOS.
The listener has active channels and the communications protocol being used is TCP/IP and channel threads are restricted to run within the listener process.
End the channels using the STOP CHANNEL command and reissue the request.
10 : Warning
A request was made to start a listener, however the listener is already running and cannot be started.
If the listener should not be running then use the STOP LISTENER command to stop the listener before reissuing the command.
10 : Warning
A request was made to stop a listener, however the listener is not running.
If the listener should be running then use the START LISTENER command to start the listener.
0 : Information
The Request to stop the Service has been accepted and is being processed.
None.
0 : Information
The Request to start the Service has been accepted and is being processed.
None.
20 : Error
The command requested was unsuccessful because the program which was defined to be run to complete the action could not be started.
Reasons why the program could not be started are
The program does not exist at the specified location.
The WebSphere MQ user does not have sufficient access to execute the program.
If STDOUT or STDERR are defined for the program, the WebSphere MQ user does not have sufficient access to the locations specified.
Check the Queue Manager error logs for further details on the cause of the failure and correct before reissuing the command.
20 : Error
The command requested was unsuccessful because access was denied attempting to execuete the program defined to run.
Examine the definition of the object and ensure that the path to program file is correct. If the defined path is correct ensure that the program exists at the location specified and that the WebSphere MQ user has access to execute the program.
20 : Error
The command requested was unsuccessful because the attempt to execute the program defined to run was unsuccessful.
Examine the definition of the object and ensure that the path to program file is correct. If the defined path is correct ensure that the program exists at the location specified and that the WebSphere MQ user has access to execute the program. Further information on the failure may be available in the WebSphere MQ error logs.
10 : Warning
A request was made to start a service, however the service is already running and cannot be started.
If the service should not be running then use the STOP SERVICE command to stop the service before reissuing the command. If the intention is to allow more than one instance of s service to run, then the service definition may be altered to be of SERVTYPE(COMMAND) which allows more than one instance of the service to be executed concurrently, however status of services of type COMMAND is not available from the SVSTAUS command.
10 : Warning
A request was made to stop a service, however the service is not running.
If the service should be running then use the START SERVICE command to start the service.
20 : Error
A request was made to STOP a service, however the service has no Stop Command defined so no action could be taken.
Examine the definition of the service and if necessary update the definition of the service to include the command to run when STOP is issued. For services of type 'SERVER' the command to run when STOP is executed is stored when the service is started so any alteration to the service definition will have no effect until the service is restarted following the update.
20 : Error
A request was made to START a service, however the service has no Start Command defined so no action could be taken.
Examine the definition of the service and if necessary update the definition of the service to include the command to run when START is issued.
20 : Error
The dead-letter queue handler (runmqdlq) could not connect to queue manager <insert_3>. This message is typically issued when the requested queue manager has not been started or is quiescing, or if the process does not have sufficient authority. The completion code (<insert_1>) and the reason (<insert_2>) can be used to identify the error. The dead-letter queue handler ends.
Take appropriate action based upon the completion code and reason.
20 : Error
The dead-letter queue handler (STRMQMDLQ) could not connect to queue manager <insert_3>. This message is typically issued when the requested queue manager has not been started or is quiescing, or if the process does not have sufficient authority. The completion code (<insert_1>) and the reason (<insert_2>) can be used to identify the error. The dead-letter queue handler ends.
Take appropriate action based upon the completion code and reason.
20 : Error
The dead-letter queue handler (runmqdlq) could not open the queue manager object. This message is typically issued because of a resource shortage or because the process does not have sufficient authority. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Take appropriate action based upon the completion code and reason.
20 : Error
The dead-letter queue handler (STRMQMDLQ) could not open the queue manager object. This message is typically issued because of a resource shortage or because the process does not have sufficient authority. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Take appropriate action based upon the completion code and reason.
20 : Error
The dead-letter queue handler (runmqdlq) could not inquire on the queue manager. This message is typically issued because of a resource shortage or because the queue manager is ending. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Take appropriate action based upon the completion code and reason.
20 : Error
The dead-letter queue handler (STRMQMDLQ) could not inquire on the queue manager. This message is typically issued because of a resource shortage or because the queue manager is ending. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Take appropriate action based upon the completion code and reason.
20 : Error
The dead-letter queue handler (runmqdlq) could not close the queue manager. This message is typically issued because of a resource shortage or because the queue manager is ending. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Take appropriate action based upon the completion code and reason.
20 : Error
The dead-letter queue handler (STRMQMDLQ) could not close the queue manager. This message is typically issued because of a resource shortage or because the queue manager is ending. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Take appropriate action based upon the completion code and reason.
20 : Error
The dead-letter queue handler (runmqdlq) could not open the dead-letter queue <insert_3> for browsing. This message is typically issued because another process has opened the dead-letter queue for exclusive access, or because an invalid dead-letter queue name was specified. Other possible reasons include resource shortages or insufficient authority. The completion code(<insert_1>) and the reason(<insert_2>) can be used to identify the error. The dead-letter queue handler ends.
Take appropriate action based upon the completion code and reason.
20 : Error
The dead-letter queue handler (STRMQMDLQ) could not open the dead-letter queue <insert_3> for browsing. This message is typically issued because another process has opened the dead-letter queue for exclusive access, or because an invalid dead-letter queue name was specified. Other possible reasons include resource shortages or insufficient authority. The completion code(<insert_1>) and the reason(<insert_2>) can be used to identify the error. The dead-letter queue handler ends.
Take appropriate action based upon the completion code and reason.
20 : Error
The dead-letter queue handler (runmqdlq) could not close the dead-letter queue. This message is typically issued because of a resource shortage or because the queue manager is ending. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Take appropriate action based upon the completion code and reason.
20 : Error
The dead-letter queue handler (STRMQMDLQ) could not close the dead-letter queue. This message is typically issued because of a resource shortage or because the queue manager is ending. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Take appropriate action based upon the completion code and reason.
20 : Error
The integer parameter (<insert_2>) supplied to the dead-letter handler was outside of the valid range for <insert_3> on line <insert_1>.
Correct the input data and restart the dead-letter queue handler.
20 : Error
The dead-letter queue handler (runmqdlq) could not get the next message from the dead-letter queue. This message is typically issued because of the queue manager ending, a resource problem, or another process having deleted the dead-letter queue. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Take appropriate action based upon the completion code and reason.
20 : Error
The dead-letter queue handler (STRMQMDLQ) could not get the next message from the dead-letter queue. This message is typically issued because of the queue manager ending, a resource problem, or another process having deleted the dead-letter queue. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Take appropriate action based upon the completion code and reason.
20 : Error
The dead-letter queue handler (runmqdlq) was unable to commit or backout an update to the dead-letter queue. This message is typically issued because of the queue manager ending, or because of a resource shortage. If the queue manager has ended, the update to the dead-letter queue (and any associated updates) will be backed out when the queue manager restarts. If the problem was due to a resource problem then the updates will be backed out when the dead-letter queue handler terminates. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Take appropriate action based upon the completion code and reason.
20 : Error
The dead-letter queue handler (STRMQMDLQ) was unable to commit or backout an update to the dead-letter queue. This message is typically issued because of the queue manager ending, or because of a resource shortage. If the queue manager has ended, the update to the dead-letter queue (and any associated updates) will be backed out when the queue manager restarts. If the problem was due to a resource problem then the updates will be backed out when the dead-letter queue handler terminates. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Take appropriate action based upon the completion code and reason.
20 : Error
Either no input was provided to runmqdlq, or the input to runmqdlq contained no valid message templates. If input was provided to runmqdlq but was found to be invalid, earlier messages will have been produced explaining the cause of the error. The dead-letter queue handler will ends.
Correct the input data and restart the dead-letter queue handler.
20 : Error
Either no input was provided to STRMQMDLQ, or the input to STRMQMDLQ contained no valid message templates. If input was provided to STRMQMDLQ but was found to be invalid, earlier messages will have been produced explaining the cause of the error. The dead-letter queue handler will ends.
Correct the input data and restart the dead-letter queue handler.
20 : Error
The dead-letter queue handler (runmqdlq) was unable to obtain private storage. This problem would typically arise as a result of some more global problem. For example if there is a persistent problem that is causing messages to be written to the DLQ and the same problem (for example queue full) is preventing the dead-letter queue handler from taking the requested action with the message, it is necessary for the dead-letter queue handler to maintain a large amount of state data to remember the retry counts associated with each message, or if the dead-letter queue contains a large number of messages and the rules table has directed the dead-letter queue handler to ignore the messages.
Investigate if some more global problem exists, and if the dead-letter queue contains a large number of messages. If the problem persists contact your support center.
20 : Error
The dead-letter queue handler (STRMQMDLQ) was unable to obtain private storage. This problem would typically arise as a result of some more global problem. For example if there is a persistent problem that is causing messages to be written to the DLQ and the same problem (for example queue full) is preventing the dead-letter queue handler from taking the requested action with the message, it is necessary for the dead-letter queue handler to maintain a large amount of state data to remember the retry counts associated with each message, or if the dead-letter queue contains a large number of messages and the rules table has directed the dead-letter queue handler to ignore the messages.
Investigate if some more global problem exists, and if the dead-letter queue contains a large number of messages. If the problem persists contact your support center.
20 : Error
A parameter supplied as input to the dead-letter handler exceeded the maximum length for parameters of that type.
Correct the input data and restart the dead-letter queue handler.
20 : Error
Two or more parameters of the same type were supplied on a single input line to the dead-letter queue handler.
Correct the input and restart the dead-letter queue handler.
20 : Error
The dead-letter queue handler (runmqdlq) was informed of an error while attempting to release an area of private storage. The dead-letter queue handler ends.
This message should be preceded by a message or FFST information from the internal routine that detected the error. Take the action associated with the earlier error information.
20 : Error
The dead-letter queue handler (STRMQMDLQ) was informed of an error while attempting to release an area of private storage. The dead-letter queue handler ends.
This message should be preceded by a message or FFST information from the internal routine that detected the error. Take the action associated with the earlier error information.
20 : Error
An integer supplied as input to the dead-letter handler was outside of the valid range of integers supported by the dead-letter queue handler.
Correct the input data and restart the dead-letter queue handler.
20 : Error
One or more errors have been detected in the input to the dead-letter queue handler(runmqdlq). Error messages will have been generated for each of these errors. The dead-letter queue handler ends.
Correct the input data and restart the dead-letter queue handler.
20 : Error
One or more errors have been detected in the input to the dead-letter queue handler(STRMQMDLQ). Error messages will have been generated for each of these errors. The dead-letter queue handler ends.
Correct the input data and restart the dead-letter queue handler.
20 : Error
An invalid combination of input parameters has been supplied to the dead-letter queue handler. Possible causes are: no ACTION specified, ACTION(FWD) but no FWDQ specified, HEADER(YES|NO) specified without ACTION(FWD).
Correct the input data and restart the dead-letter queue handler.
30 : Severe error
The dead-letter queue handler (runmqdlq) could not perform basic initialization required to use MQ services because of an unforeseen error. The dead-letter queue handler ends.
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved.
30 : Severe error
The dead-letter queue handler (STRMQMDLQ) could not perform basic initialization required to use MQ services because of an unforeseen error. The dead-letter queue handler ends.
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved.
30 : Severe error
The dead-letter queue handler (runmqdlq) could not connect to the requested queue manager because of an unforeseen error. The dead-letter queue handler ends.
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved.
30 : Severe error
The dead-letter queue handler (STRMQMDLQ) could not connect to the requested queue manager because of an unforeseen error. The dead-letter queue handler ends.
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved.
30 : Severe error
The dead-letter queue handler (runmqdlq) could not open the queue manager because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved.
30 : Severe error
The dead-letter queue handler (STRMQMDLQ) could not open the queue manager because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved.
30 : Severe error
The dead letter queue handler (runmqdlq) could not inquire on the queue manager because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead letter queue handler ends.
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved.
30 : Severe error
The dead letter queue handler (STRMQMDLQ) could not inquire on the queue manager because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead letter queue handler ends.
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved.
30 : Severe error
The dead-letter queue handler (runmqdlq) could not close the queue manager because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved.
30 : Severe error
The dead-letter queue handler (STRMQMDLQ) could not close the queue manager because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved.
30 : Severe error
The dead-letter queue handler (runmqdlq) could not open the dead-letter queue for browsing because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved.
30 : Severe error
The dead-letter queue handler (STRMQMDLQ) could not open the dead-letter queue for browsing because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved.
30 : Severe error
The dead-letter queue handler (runmqdlq) could not close the dead-letter queue because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved.
30 : Severe error
The dead-letter queue handler (STRMQMDLQ) could not close the dead-letter queue because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved.
30 : Severe error
The dead-letter queue handler (runmqdlq) could not get the next message from the dead-letter queue because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved.
30 : Severe error
The dead-letter queue handler (STRMQMDLQ) could not get the next message from the dead-letter queue because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved.
30 : Severe error
The dead-letter queue handler (runmqdlq) was unable to either commit or backout an update to the dead-letter queue because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved.
30 : Severe error
The dead-letter queue handler (STRMQMDLQ) was unable to either commit or backout an update to the dead-letter queue because of an unforeseen error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved.
30 : Severe error
The dead-letter queue handler (runmqdlq) was unable to disconnect from the queue manager because of an unexpected error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved.
30 : Severe error
The dead-letter queue handler (STRMQMDLQ) was unable to disconnect from the queue manager because of an unexpected error. The completion code and the reason can be used to identify the error. The dead-letter queue handler ends.
Use the standard facilities supplied with your system to record the problem identifier and to save the generated output files. Contact your support center. Do not discard these files until the problem has been resolved.
40 : Stop Error
The <insert_3> command failed to open <insert_5> for WebSphere MQ processing.
Check that the intended file or member exists, and was specified correctly. Correct the specification or create the object and try the operation again.
0 : Information
None.
30 : Severe error
10 : Warning
10 : Warning
10 : Warning
10 : Warning
40 : Stop Error
The OPTION(*MVS) parameter may not be specified without specifying a value for the WAIT parameter.
Remove the OPTION(*MVS) parameter from the command or, specify a value for the WAIT parameter. Then try the command again.
30 : Severe error
The filter value <insert_5> is not valid with the keyword <insert_4>.
Specify a valid filter value for the keyword <insert_4>.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
adm |