AMQ8000-AMQ8999 WebSphere MQ administration messages - Middleware News
------------------------------------------------------------------------
AMQ8202 TMQNAME only allowed with channel type *SDR or *SVR.
Explanation: The TMQNAME parameter may only be specified with channel type *SDR or *SVR.
User Response: 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.
AMQ8204 MCANAME only allowed with channel type *SDR, *SVR, or *RQSTR.
Explanation: The MCANAME parameter may only be specified with channel type *SDR, *SVR, or *RQSTR.
User Response: 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.
AMQ8205 DSCITV only allowed with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR.
Explanation: The DSCITV parameter may only be specified with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR.
User Response: Remove the DSCITV 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.
AMQ8206 SHORTRTY only allowed with channel type *CLUSSDR, CLUSRCVR, *SDR or *SVR.
Explanation: The SHORTRTY parameter may only be specified with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR.
User Response: 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.
AMQ8207 SHORTTMR only allowed with channel type *CLUSSDR, CLUSRCVR, *SDR or *SVR.
Explanation: The SHORTTMR parameter may only be specified with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR.
User Response: 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.
AMQ8208 LONGRTY only allowed with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR.
Explanation: The LONGRTY parameter may only be specified with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR.
User Response: 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.
AMQ8209 LONGTMR only allowed with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR.
Explanation: The LONGTMR parameter may only be specified with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR.
User Response: 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.
AMQ8210 PUTAUT only allowed with channel type *RCVR or RQSTR.
Explanation: The PUTAUT parameter may only be specified with channel type *RCVR or RQSTR.
User Response: 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.
AMQ8211 BATCHINT only allowed with channel type *SDR or *SVR.
Explanation: The BATCHINT parameter may only be specified with channel type *SDR or *SVR.
User Response: 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.
AMQ8214 CONNAME parameter missing.
Explanation: 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.
User Response: Enter a value for parameter CONNAME.
AMQ8219 Command server queue is open, retry later.
Explanation:
User Response: Wait and try again later.
AMQ8226 WebSphere MQ channel already exists.
Explanation: The channel &3 cannot be created because it already exists.
User Response: Check that the name is correct and try the command again specifying REPLACE, or delete the channel and then try the command again.
AMQ8227 Channel &3 not found.
Explanation: The channel could not be found.
User Response: Correct the Channel Name if wrong and then try the command again. For DEFINE CHANNEL check that the Channel Name in error exists.
AMQ8287 No channels with status to display.
Explanation: 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.
User Response: None.
AMQ8296 &1 MQSC commands completed successfully.
Explanation: The &3 command has completed successfully. The &1 MQ commands from &5 have been processed without error and a report written to the printer spool file.
User Response: None.
AMQ8297 &1 MQSC commands verified successfully.
Explanation: The &3 command completed successfully. The &1 MQ commands from &5 have been verified and a report written to the printer spool file.
User Response: None.
AMQ8298 Error report generated for MQSC command process.
Explanation: The &3 command attempted to process the sequence of MQ commands from &5 and encountered some errors, however, the operation may have partially completed. A report has been written to the printer spool file.
User Response: Examine the spooled printer file for details of the errors encountered, correct the MQSC source file, and retry the operation.
AMQ8299 Cannot open &5 for MQSC process.
Explanation: The &1 command failed to open &5 for MQ command processing.
User Response: Check that the intended file exists, and has been specified correctly. Correct the specification or create the object, and try the operation again.
AMQ8302 Internal failure initializing WebSphere MQ services.
Explanation: An error occurred while attempting to initialize WebSphere MQ services.
User Response: A call to xcsInitialize ended with the FAIL, STOP, or STOP_ALL return code. Refer to the log for messages diagnosing this problem.
AMQ8304 Tracing cannot be started. Too many traces are already running.
Explanation: A maximum of 9 traces may be running concurrently. This number is already running.
User Response: Stop one or more of the other traces and try the command again.
AMQ8305 Tracing cannot be started. Too many traces are already running.
Explanation: A maximum of 9 traces can be running concurrently, and this number of traces is already running.
User Response: Stop one or more of the other traces and try the command again.
AMQ8315 No namelists to display.
Explanation: There are no matching namelists defined on this system.
User Response: Use the Create Namelist (CRTMQMNL) command to create a namelist.
AMQ8316 No cluster queue managers to display.
Explanation: There are no matching cluster queue managers defined on this system.
User Response: None.
AMQ8319 MSGEXIT only allowed with channel type *SDR, *SVR, *RCVR *RQSTR, *CLUSSDR or *CLUSRCVR.
Explanation: The MSGEXIT parameter may only be specified with channel type *SDR, *SVR, *RCVR, *RQSTR, *CLUSSDR, or *CLUSRCVR.
User Response: 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.
AMQ8342 No authorities to display.
Explanation: There are no authority records defined on this system, satisfying the input parameters.
User Response: Use the appropriate input to list all the authorities defined on the system, or enter the command again with different input..
AMQ8343 The authority *REMOVE is not valid with user QMQMADM.
Explanation: You are not allowed to completely delete the authorities assigned to user QMQMADM, for a valid WebSphere MQ object, with the authority *REMOVE.
User Response: Remove QMQMADM from the list of users to this command.
AMQ8344 The delete option is not valid for an object name.
Explanation: The delete option, which will delete this authority profile by removing all the users from this authority profile, is only valid for a generic profile name.
User Response: To delete users from an object, work from the WRKMQMAUTD command.
AMQ8401 &1 MQSC commands read.
Explanation: The MQSC script contains &1 commands.
User Response: None.
AMQ8402 &1 commands have a syntax error.
Explanation: The MQSC script contains &1 commands having a syntax error.
User Response: None.
AMQ8403 &1 valid MQSC commands could not be processed.
Explanation: The MQSC script contains &1 commands that failed to process.
User Response: None.
AMQ8404 Command failed.
Explanation: An MQSC command has been recognized, but cannot be processed.
User Response: None.
AMQ8405 Syntax error detected at or near end of command segment below:-
Explanation: The MQSC script contains &1 commands having a syntax error.
User Response: None.
AMQ8406 Unexpected 'end of input' in MQSC.
Explanation: An MQSC command contains a continuation character, but the 'end of input' has been reached without completing the command.
User Response: None.
AMQ8407 Display Process details.
Explanation: The MQSC DISPLAY PROCESS command completed successfully, and details follow this message.
User Response: None.
AMQ8408 Display Queue Manager details.
Explanation: The MQSC DISPLAY QMGR command completed successfully, and details follow this message.
User Response: None.
AMQ8409 Display Queue details.
Explanation: The MQSC DISPLAY QUEUE command completed successfully, and details follow this message.
User Response: None.
AMQ8410 Parser Error.
Explanation: The MQSC Parser has an internal error.
User Response: None.
AMQ8411 Duplicate Keyword Error.
Explanation: A command in the MQSC script contains duplicate keywords.
User Response: None.
AMQ8412 Numeric Range Error.
Explanation: The value assigned to an MQSC command keyword is out of the permitted range.
User Response: None.
AMQ8413 String Length Error.
Explanation: A string assigned to an MQSC keyword is either NULL, or longer than the maximum permitted for that keyword.
User Response: None.
AMQ8414 Display Channel details.
Explanation: The MQSC DISPLAY CHL command completed successfully, and details follow this message.
User Response: None.
AMQ8415 Ping WebSphere MQ Queue Manager command complete.
Explanation: The MQSC PING QMGR command completed successfully.
User Response: None.
AMQ8416 MQSC timed out waiting for a response from the command server.
Explanation: MQSC did not receive a response message from the remote command server in the time specified.
User Response: None.
AMQ8417 Display Channel Status details.
Explanation: The MQSC DISPLAY CHANNEL STATUS command completed successfully, and details follow this message.
User Response: None.
AMQ8418 &1 command responses received.
Explanation: Running in queued mode, &1 command responses were received from the remote command server.
User Response: None.
AMQ8419 The Queue is already in the DCE cell.
Explanation: The Queue is already in the cell, that is, its SCOPE attribute is already CELL.
User Response: None.
AMQ8420 Channel Status not found.
Explanation: No status was found for the specified channel(s).
User Response: None.
AMQ8421 A required keyword was not specified.
Explanation: A keyword required in this command was not specified.
User Response: None.
AMQ8422 MQSC found the following response to a previous command on the reply q :-
Explanation: MQSC found additional command responses on the reply q. They will fill follow this message.
User Response: None.
AMQ8423 Cell Directory not available.
Explanation: The DCE cell directory is not available, so the requested operation has failed.
User Response: None.
AMQ8424 Error detected in a name keyword.
Explanation: 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.
User Response: None.
AMQ8425 Attribute value error .
Explanation: A keyword in an MQSC command contained a value that was not valid.
User Response: None.
AMQ8426 Valid MQSC commands are:
Explanation: The text shows valid MQSC commands.
User Response: None.
AMQ8427 Valid syntax for the MQSC command:
Explanation: The text shown is the valid syntax for the MQSC command.
User Response: None.
AMQ8428 TYPE Keyword has already been specified.
Explanation: The TYPE has already been specified after the DISPLAY verb, for example DISPLAY QUEUE(*) type(QLOCAL) type(QALIAS).
User Response: Delete the second TYPE keyword and run the command again.
AMQ8430 Remote queue manager name is unknown.
Explanation: 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.
User Response: Create a transmission queue of the same name as the remote queue manager if one does not exist.
AMQ8431 Transmission queue does not exist
Explanation: The transmission queue does not exist on this queue manager.
User Response: None.
AMQ8433 You are not allowed to set both the CLUSTER and CLUSNL fields.
Explanation: 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.
User Response: None.
AMQ8434 The repository is unavailable.
Explanation: The repository is unavailable and the data cannot be accessed. Stop and restart the queue manager.
User Response: None.
AMQ8435 All valid MQSC commands were processed.
Explanation: The MQSC script contains no commands that failed to process.
User Response: None.
AMQ8436 One valid MQSC command could not be processed.
Explanation: The MQSC script contains one command that failed to process.
User Response: None.
AMQ8437 No MQSC commands read.
Explanation: The MQSC script contains no commands.
User Response: None.
AMQ8438 One MQSC command read.
Explanation: The MQSC script contains one command.
User Response: None.
AMQ8439 No commands have a syntax error.
Explanation: The MQSC script contains no commands having a syntax error.
User Response: None.
AMQ8440 One command has a syntax error.
Explanation: The MQSC script contains one command which has a syntax error.
User Response: None.
AMQ8443 Only the CLUSTER or CLUSNL field may have a value.
Explanation: 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.
User Response: None.
AMQ8444 The CLUSTER or CLUSNL fields must have a value.
Explanation: 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.
User Response: None.
AMQ8445 Program cannot open queue manager object.
Explanation: An attempt to open a queue manager object has failed.
User Response: See the previously listed messages in the job log.
AMQ8446 Channel is currently active.
Explanation: The requested operation failed because the channel is currently active.
User Response: See the previously listed messages in the job log.
AMQ8447 Requested operation on channel '&5' not valid for this channel type.
Explanation: The operation requested cannot be performed because channel '&5' is not of a suitable type. For example, only sender, server and cluster-sender channels can be resolved.
User Response: Check that the correct operation was requested. If it was, check that the correct channel name was specified.
AMQ8448 Channel '&5' is not running.
Explanation: A request to end channel '&5' has failed because the channel is not running.
User Response: Check that the correct operation was requested. If it was, check that the correct channel name was specified.
AMQ8449 Queue '&5' inhibited for MQGET.
Explanation: An MQGET failed because the queue '&5' had been previously inhibited for MQGET.
User Response: None.
AMQ8450 Display queue status details.
Explanation: The MQSC DISPLAY QSTATUS command completed successfully/. Details follow this message.
User Response:
AMQ8498 Starting WebSphere MQ script Commands.
Explanation: The MQSC script contains &1 commands.
User Response: None.
AMQ8499 Usage: runmqsc [-e] [-v] [-w WaitTime [-x]] QMgrName
Explanation: None.
User Response: None.
AMQ8500 WebSphere MQ Display MQ Files
Explanation:
User Response:
AMQ8501 Common services initialization failed with return code &1.
Explanation: A request by the command server to initialize common services failed with return code &1.
User Response: None.
AMQ8502 Connect shared memory failed with return code &1.
Explanation: A request by the command server to connect shared memory failed with return code &1.
User Response: None.
AMQ8503 Post event semaphore failed with return code &1.
Explanation: A request by the command server to post an event semaphore failed with return code &1.
User Response: None.
AMQ8504 Command server MQINQ failed with reason code &1.
Explanation: An MQINQ request by the command server, for the WebSphere MQ queue &3, failed with reason code &1.
User Response: None.
AMQ8505 Reallocate memory failed with return code &1.
Explanation: A request by the command server to reallocate memory failed with return code &1.
User Response: None.
AMQ8506 Command server MQGET failed with reason code &1.
Explanation: An MQGET request by the command server, for the WebSphere MQ queue &3, failed with reason code &1.
User Response: None.
AMQ8507 Command server MQPUT1 request for an undelivered message failed with reason code &1.
Explanation: An attempt by the command server to put a message to the dead-letter queue, using MQPUT1, failed with reason code &1. The MQDLH reason code was &2.
User Response: None.
AMQ8508 Queue Manager Delete Object List failed with return code &1.
Explanation: A request by the command server to delete a queue manager object list failed with return code &1.
User Response: None.
AMQ8509 Command server MQCLOSE reply-to queue failed with reason code &1.
Explanation: An MQCLOSE request by the command server for the reply-to queue failed with reason code &1.
User Response: None.
AMQ8510 Command server queue is open, try again later.
Explanation:
User Response:
AMQ8511 Usage: strmqcsv [QMgrName]
Explanation:
User Response:
AMQ8512 Usage: endmqcsv [-c | -i] QMgrName
Explanation:
User Response:
AMQ8513 Usage: dspmqcsv [QMgrName]
Explanation:
User Response:
AMQ8514 No response received after &1 seconds.
Explanation: The command server has not reported the status of running, to the start request, before the timeout of &1 seconds was reached.
User Response: None.
AMQ8549 Total string length exceeds the maximum value of 999 characters.
Explanation: 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.
User Response: None.
AMQ8550 Display namelist details.
Explanation: The MQSC DISPLAY NAMELIST command completed successfully, and details follow this message.
User Response: None.
AMQ8551 WebSphere MQ namelist changed.
Explanation: WebSphere MQ namelist &5 changed.
User Response: None.
AMQ8552 WebSphere MQ namelist created.
Explanation: WebSphere MQ namelist &5 created.
User Response: None.
AMQ8553 WebSphere MQ namelist deleted.
Explanation: WebSphere MQ namelist &5 deleted.
User Response: None.
AMQ8554 String List String Count Error.
Explanation: 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.
User Response: None.
AMQ8555 String List String Length Error.
Explanation: A string in a string list assigned to a keyword is longer than the maximum permitted for that keyword.
User Response: None.
AMQ8556 RESUME QUEUE MANAGER accepted.
Explanation: 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.
User Response: None.
AMQ8557 SUSPEND QUEUE MANAGER accepted.
Explanation: 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.
User Response: None.
AMQ8558 REFRESH CLUSTER accepted.
Explanation: 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.
User Response: None.
AMQ8559 RESET CLUSTER accepted.
Explanation: 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.
User Response: None.
AMQ8560 WebSphere MQ security cache refreshed.
Explanation: The Object Authority Manager security cache has been refreshed.
User Response: None.
AMQ8561 Domain controller unavailable.
Explanation: WebSphere MQ was unable to contact the domain controller to obtain information for user '&3'.
User Response: Ensure that a domain controller for the domain on which user '&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.
AMQ8563 WebSphere MQ authentication information object created.
Explanation: WebSphere MQ authentication information object &5 created.
User Response: None.
AMQ8564 WebSphere MQ authentication information object deleted.
Explanation: WebSphere MQ authentication information object &5 deleted.
User Response: None.
AMQ8566 Display authentication information details.
Explanation: The MQSC DISPLAY AUTHINFO command completed successfully. Details follow this message.
User Response: None.
AMQ8567 WebSphere MQ authentication information changed.
Explanation: WebSphere MQ authentication information &5 changed.
User Response: None.
AMQ8601 WebSphere MQ trigger monitor started.
Explanation: The WebSphere MQ trigger monitor has been started.
User Response: None.
AMQ8602 WebSphere MQ trigger monitor ended.
Explanation: The WebSphere MQ trigger monitor has ended.
User Response: None.
AMQ8603 Usage: runmqtrm [-m QMgrName] [-q InitQ]
Explanation: None.
User Response: None.
AMQ8604 Use of WebSphere MQ trigger monitor not authorized.
Explanation: The trigger monitor cannot be run due to lack of authority to the requested queue manager or initiation queue.
User Response: Obtain the necessary authority from your security officer or WebSphere MQ administrator. Then try the command again.
AMQ8605 Queue manager not available to the WebSphere MQ trigger monitor
Explanation: The queue manager specified for the trigger monitor does not exist, or is not active.
User Response: 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.
AMQ8606 Insufficient storage available for the WebSphere MQ trigger monitor.
Explanation: There was insufficient storage available for the WebSphere MQ trigger monitor to run.
User Response: Free some storage and then try the command again.
AMQ8607 WebSphere MQ trigger monitor connection failed.
Explanation: The trigger monitor's connection to the requested queue manager failed because of MQI reason code &1 from MQCONN.
User Response: Consult your systems administrator about the state of the queue manager.
AMQ8608 WebSphere MQ trigger monitor connection broken.
Explanation: 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.
User Response: Consult your systems administrator about the state of the queue manager.
AMQ8609 Initiation queue missing or wrong type
Explanation: The named initiation queue could not be found; or the queue type is not correct for an initiation queue.
User Response: 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.
AMQ8610 Initiation queue in use
Explanation: The WebSphere MQ trigger monitor could not open the initiation queue because the queue is open for exclusive use by another application.
User Response: Wait until the queue is no longer in use, and try the command again.
AMQ8611 Initiation queue could not be opened.
Explanation: The WebSphere MQ trigger monitor could not open the initiation queue; reason code &1 was returned from MQOPEN.
User Response: Consult your systems administrator.
AMQ8612 Waiting for a trigger message
Explanation: The WebSphere MQ trigger monitor is waiting for a message to arrive on the initiation queue.
User Response: None.
AMQ8613 Initiation queue changed or deleted
Explanation: The WebSphere MQ trigger monitor is unable to continue because the initiation queue has been deleted or changed since it was opened.
User Response: Retry the command.
AMQ8614 Initiation queue not enabled for input.
Explanation: The WebSphere MQ trigger monitor cannot read from the initiation queue because input is not enabled.
User Response: Ask your systems administrator to enable the queue for input.
AMQ8615 WebSphere MQ trigger monitor failed to get message.
Explanation: The WebSphere MQ trigger monitor failed because of MQI reason code &1 from MQGET.
User Response: Consult your systems administrator.
AMQ8616 End of application trigger.
Explanation: The action to trigger an application has been completed.
User Response: None.
AMQ8617 Not a valid trigger message.
Explanation: 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.
User Response: Consult your systems administrator.
AMQ8618 Error starting triggered application.
Explanation: An error was detected when trying to start the application identified in a trigger message.
User Response: Check that the application the trigger monitor was trying to start is available.
AMQ8619 Application type &1 not supported.
Explanation: A trigger message was received which specifies application type &1; the trigger monitor does not support this type.
User Response: Use an alternative trigger monitor for this initiation queue.
AMQ8620 Trigger message with warning &1
Explanation: 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 &1.
User Response: None.
AMQ8621 Usage: runmqtmc [-m QMgrName] [-q InitQ]
Explanation: None.
User Response: None.
AMQ8622 Usage: CICS-Transaction-Name [MQTMC2 structure]
Explanation: None.
User Response: None.
AMQ8623 Usage: &3 [-m QMgrName] [-q InitQ]
Explanation: None.
User Response: None.
AMQ8701 Usage: rcdmqimg [-z] [-l] [-m QMgrName] -t ObjType [GenericObjName]
Explanation: None.
User Response: None.
AMQ8702 Usage: rcrmqobj [-z] [-m QMgrName] -t ObjType [GenericObjName]
Explanation: None.
User Response: None.
AMQ8703 Usage: dspmqfls [-m QMgrName] [-t ObjType] GenericObjName
Explanation: None.
User Response: None.
AMQ8708 Dead-letter queue handler started to process INPUTQ(&3).
Explanation: 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.
User Response: None.
AMQ8709 Dead-letter queue handler ending.
Explanation: 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.
User Response: None.
AMQ8710 Usage: runmqdlq [QName[QMgrName]].
Explanation: Syntax for the usage of runmqdlq.
User Response: None.
AMQ8721 Dead-letter queue message not prefixed by a valid MQDLH.
Explanation: 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.
User Response: Remove the message that is not valid 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.
AMQ8722 Dead-letter queue handler unable to put message: Rule &1 Reason &2.
Explanation: 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.
User Response: 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.
AMQ8741 Unable to connect to queue manager.
Explanation: The dead-letter queue handler (runmqdlq) could not connect to queue manager &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 (&1) and the reason (&2) can be used to identify the error. The dead-letter queue handler ends.
User Response: Take appropriate action based upon the completion code and reason.
AMQ8742 Unable to open queue manager: CompCode = &1 Reason = &2.
Explanation: 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.
User Response: Take appropriate action based upon the completion code and reason.
AMQ8743 Unable to inquire on queue manager: CompCode = &1 Reason = &2.
Explanation: 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.
User Response: Take appropriate action based upon the completion code and reason.
AMQ8744 Unable to close queue manager: CompCode = &1 Reason = &2.
Explanation: 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.
User Response: Take appropriate action based upon the completion code and reason.
AMQ8745 Unable to open dead-letter queue for browse.
Explanation: The dead-letter queue handler (runmqdlq) could not open the dead-letter queue &3 for browsing. This message is typically issued because another process has opened the dead-letter queue for exclusive access, or because a dead-letter queue name that is not valid was specified. Other possible reasons include resource shortages or insufficient authority. The completion code(&1) and the reason(&2) can be used to identify the error. The dead-letter queue handler ends.
User Response: Take appropriate action based upon the completion code and reason.
AMQ8746 Unable to close dead-letter queue: CompCode = &1 Reason = &2.
Explanation: 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.
User Response: Take appropriate action based upon the completion code and reason.
AMQ8747 Integer parameter outside permissible range.
Explanation: The integer parameter (&2) supplied to the dead-letter handler was outside the valid range for &3 on line &1.
User Response: Correct the input data and restart the dead-letter queue handler.
AMQ8748 Unable to get message from dead-letter queue: CompCode = &1 Reason = &2.
Explanation: 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.
User Response: Take appropriate action based upon the completion code and reason.
AMQ8749 Unable to commit/backout action on dead-letter queue: CompCode = &1 Reason = &2.
Explanation: 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.
User Response: Take appropriate action based upon the completion code and reason.
AMQ8750 No valid input provided to runmqdlq.
Explanation: 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 not valid, earlier messages will have been produced explaining the cause of the error. The dead-letter queue handler will ends.
User Response: Correct the input data and restart the dead-letter queue handler.
AMQ8751 Unable to obtain private storage.
Explanation: 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.
User Response: 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.
AMQ8752 Parameter(&3) exceeds maximum length on line &1.
Explanation: A parameter supplied as input to the dead-letter handler exceeded the maximum length for parameters of that type.
User Response: Correct the input data and restart the dead-letter queue handler.
AMQ8753 Duplicate parameter(&3) found on line &1.
Explanation: Two or more parameters of the same type were supplied on a single input line to the dead-letter queue handler.
User Response: Correct the input and restart the dead-letter queue handler.
AMQ8756 Error detected releasing private storage.
Explanation: 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.
User Response: 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.
AMQ8757 Integer parameter(&3) outside permissible range on line &1.
Explanation: An integer supplied as input to the dead-letter handler was outside the valid range of integers supported by the dead-letter queue handler.
User Response: Correct the input data and restart the dead-letter queue handler.
AMQ8758 &1 errors detected in input to runmqdlq.
Explanation: 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.
User Response: Correct the input data and restart the dead-letter queue handler.
AMQ8759 Invalid combination of parameters to dead-letter queue handler on line &1.
Explanation: A combination of input parameters that is not valid 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).
User Response: Correct the input data and restart the dead-letter queue handler.
AMQ8760 Unexpected failure while initializing process: Reason = &1.
Explanation: 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.
User Response: 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.
AMQ8761 Unexpected failure while connecting to queue manager: CompCode = &1 Reason = &2.
Explanation: 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.
User Response: 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.
AMQ8762 Unexpected error while attempting to open queue manager: CompCode = &1 Reason = &2.
Explanation: 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.
User Response: 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.
AMQ8763 Unexpected error while inquiring on queue manager: CompCode = &1 Reason = &2.
Explanation: 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.
User Response: 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.
AMQ8764 Unexpected error while attempting to close queue manager: CompCode = &1 Reason = &2.
Explanation: 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.
User Response: 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.
AMQ8765 Unexpected failure while opening dead-letter queue for browse: CompCode = &1 Reason = &2.
Explanation: 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.
User Response: 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.
AMQ8766 Unexpected error while closing dead-letter queue: CompCode = &1 Reason = &2.
Explanation: 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.
User Response: 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.
AMQ8767 Unexpected error while getting message from dead-letter queue: CompCode = &1 Reason = &2.
Explanation: 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.
User Response: 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.
AMQ8768 Unexpected error committing/backing out action on dead-letter queue: CompCode = &1 Reason = &2.
Explanation: 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.
User Response: 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.
AMQ8769 Unable to disconnect from queue manager: CompCode = &1 Reason = &2.
Explanation: 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.
User Response: 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.
AMQ8919 There are no matching WebSphere MQ queue manager names.
Explanation:
User Response:
------------------------------------------------------------------------
AMQ8202 TMQNAME only allowed with channel type *SDR or *SVR.
Explanation: The TMQNAME parameter may only be specified with channel type *SDR or *SVR.
User Response: 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.
AMQ8204 MCANAME only allowed with channel type *SDR, *SVR, or *RQSTR.
Explanation: The MCANAME parameter may only be specified with channel type *SDR, *SVR, or *RQSTR.
User Response: 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.
AMQ8205 DSCITV only allowed with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR.
Explanation: The DSCITV parameter may only be specified with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR.
User Response: Remove the DSCITV 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.
AMQ8206 SHORTRTY only allowed with channel type *CLUSSDR, CLUSRCVR, *SDR or *SVR.
Explanation: The SHORTRTY parameter may only be specified with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR.
User Response: 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.
AMQ8207 SHORTTMR only allowed with channel type *CLUSSDR, CLUSRCVR, *SDR or *SVR.
Explanation: The SHORTTMR parameter may only be specified with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR.
User Response: 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.
AMQ8208 LONGRTY only allowed with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR.
Explanation: The LONGRTY parameter may only be specified with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR.
User Response: 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.
AMQ8209 LONGTMR only allowed with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR.
Explanation: The LONGTMR parameter may only be specified with channel type *CLUSSDR, *CLUSRCVR, *SDR or *SVR.
User Response: 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.
AMQ8210 PUTAUT only allowed with channel type *RCVR or RQSTR.
Explanation: The PUTAUT parameter may only be specified with channel type *RCVR or RQSTR.
User Response: 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.
AMQ8211 BATCHINT only allowed with channel type *SDR or *SVR.
Explanation: The BATCHINT parameter may only be specified with channel type *SDR or *SVR.
User Response: 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.
AMQ8214 CONNAME parameter missing.
Explanation: 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.
User Response: Enter a value for parameter CONNAME.
AMQ8219 Command server queue is open, retry later.
Explanation:
User Response: Wait and try again later.
AMQ8226 WebSphere MQ channel already exists.
Explanation: The channel &3 cannot be created because it already exists.
User Response: Check that the name is correct and try the command again specifying REPLACE, or delete the channel and then try the command again.
AMQ8227 Channel &3 not found.
Explanation: The channel could not be found.
User Response: Correct the Channel Name if wrong and then try the command again. For DEFINE CHANNEL check that the Channel Name in error exists.
AMQ8287 No channels with status to display.
Explanation: 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.
User Response: None.
AMQ8296 &1 MQSC commands completed successfully.
Explanation: The &3 command has completed successfully. The &1 MQ commands from &5 have been processed without error and a report written to the printer spool file.
User Response: None.
AMQ8297 &1 MQSC commands verified successfully.
Explanation: The &3 command completed successfully. The &1 MQ commands from &5 have been verified and a report written to the printer spool file.
User Response: None.
AMQ8298 Error report generated for MQSC command process.
Explanation: The &3 command attempted to process the sequence of MQ commands from &5 and encountered some errors, however, the operation may have partially completed. A report has been written to the printer spool file.
User Response: Examine the spooled printer file for details of the errors encountered, correct the MQSC source file, and retry the operation.
AMQ8299 Cannot open &5 for MQSC process.
Explanation: The &1 command failed to open &5 for MQ command processing.
User Response: Check that the intended file exists, and has been specified correctly. Correct the specification or create the object, and try the operation again.
AMQ8302 Internal failure initializing WebSphere MQ services.
Explanation: An error occurred while attempting to initialize WebSphere MQ services.
User Response: A call to xcsInitialize ended with the FAIL, STOP, or STOP_ALL return code. Refer to the log for messages diagnosing this problem.
AMQ8304 Tracing cannot be started. Too many traces are already running.
Explanation: A maximum of 9 traces may be running concurrently. This number is already running.
User Response: Stop one or more of the other traces and try the command again.
AMQ8305 Tracing cannot be started. Too many traces are already running.
Explanation: A maximum of 9 traces can be running concurrently, and this number of traces is already running.
User Response: Stop one or more of the other traces and try the command again.
AMQ8315 No namelists to display.
Explanation: There are no matching namelists defined on this system.
User Response: Use the Create Namelist (CRTMQMNL) command to create a namelist.
AMQ8316 No cluster queue managers to display.
Explanation: There are no matching cluster queue managers defined on this system.
User Response: None.
AMQ8319 MSGEXIT only allowed with channel type *SDR, *SVR, *RCVR *RQSTR, *CLUSSDR or *CLUSRCVR.
Explanation: The MSGEXIT parameter may only be specified with channel type *SDR, *SVR, *RCVR, *RQSTR, *CLUSSDR, or *CLUSRCVR.
User Response: 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.
AMQ8342 No authorities to display.
Explanation: There are no authority records defined on this system, satisfying the input parameters.
User Response: Use the appropriate input to list all the authorities defined on the system, or enter the command again with different input..
AMQ8343 The authority *REMOVE is not valid with user QMQMADM.
Explanation: You are not allowed to completely delete the authorities assigned to user QMQMADM, for a valid WebSphere MQ object, with the authority *REMOVE.
User Response: Remove QMQMADM from the list of users to this command.
AMQ8344 The delete option is not valid for an object name.
Explanation: The delete option, which will delete this authority profile by removing all the users from this authority profile, is only valid for a generic profile name.
User Response: To delete users from an object, work from the WRKMQMAUTD command.
AMQ8401 &1 MQSC commands read.
Explanation: The MQSC script contains &1 commands.
User Response: None.
AMQ8402 &1 commands have a syntax error.
Explanation: The MQSC script contains &1 commands having a syntax error.
User Response: None.
AMQ8403 &1 valid MQSC commands could not be processed.
Explanation: The MQSC script contains &1 commands that failed to process.
User Response: None.
AMQ8404 Command failed.
Explanation: An MQSC command has been recognized, but cannot be processed.
User Response: None.
AMQ8405 Syntax error detected at or near end of command segment below:-
Explanation: The MQSC script contains &1 commands having a syntax error.
User Response: None.
AMQ8406 Unexpected 'end of input' in MQSC.
Explanation: An MQSC command contains a continuation character, but the 'end of input' has been reached without completing the command.
User Response: None.
AMQ8407 Display Process details.
Explanation: The MQSC DISPLAY PROCESS command completed successfully, and details follow this message.
User Response: None.
AMQ8408 Display Queue Manager details.
Explanation: The MQSC DISPLAY QMGR command completed successfully, and details follow this message.
User Response: None.
AMQ8409 Display Queue details.
Explanation: The MQSC DISPLAY QUEUE command completed successfully, and details follow this message.
User Response: None.
AMQ8410 Parser Error.
Explanation: The MQSC Parser has an internal error.
User Response: None.
AMQ8411 Duplicate Keyword Error.
Explanation: A command in the MQSC script contains duplicate keywords.
User Response: None.
AMQ8412 Numeric Range Error.
Explanation: The value assigned to an MQSC command keyword is out of the permitted range.
User Response: None.
AMQ8413 String Length Error.
Explanation: A string assigned to an MQSC keyword is either NULL, or longer than the maximum permitted for that keyword.
User Response: None.
AMQ8414 Display Channel details.
Explanation: The MQSC DISPLAY CHL command completed successfully, and details follow this message.
User Response: None.
AMQ8415 Ping WebSphere MQ Queue Manager command complete.
Explanation: The MQSC PING QMGR command completed successfully.
User Response: None.
AMQ8416 MQSC timed out waiting for a response from the command server.
Explanation: MQSC did not receive a response message from the remote command server in the time specified.
User Response: None.
AMQ8417 Display Channel Status details.
Explanation: The MQSC DISPLAY CHANNEL STATUS command completed successfully, and details follow this message.
User Response: None.
AMQ8418 &1 command responses received.
Explanation: Running in queued mode, &1 command responses were received from the remote command server.
User Response: None.
AMQ8419 The Queue is already in the DCE cell.
Explanation: The Queue is already in the cell, that is, its SCOPE attribute is already CELL.
User Response: None.
AMQ8420 Channel Status not found.
Explanation: No status was found for the specified channel(s).
User Response: None.
AMQ8421 A required keyword was not specified.
Explanation: A keyword required in this command was not specified.
User Response: None.
AMQ8422 MQSC found the following response to a previous command on the reply q :-
Explanation: MQSC found additional command responses on the reply q. They will fill follow this message.
User Response: None.
AMQ8423 Cell Directory not available.
Explanation: The DCE cell directory is not available, so the requested operation has failed.
User Response: None.
AMQ8424 Error detected in a name keyword.
Explanation: 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.
User Response: None.
AMQ8425 Attribute value error .
Explanation: A keyword in an MQSC command contained a value that was not valid.
User Response: None.
AMQ8426 Valid MQSC commands are:
Explanation: The text shows valid MQSC commands.
User Response: None.
AMQ8427 Valid syntax for the MQSC command:
Explanation: The text shown is the valid syntax for the MQSC command.
User Response: None.
AMQ8428 TYPE Keyword has already been specified.
Explanation: The TYPE has already been specified after the DISPLAY verb, for example DISPLAY QUEUE(*) type(QLOCAL) type(QALIAS).
User Response: Delete the second TYPE keyword and run the command again.
AMQ8430 Remote queue manager name is unknown.
Explanation: 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.
User Response: Create a transmission queue of the same name as the remote queue manager if one does not exist.
AMQ8431 Transmission queue does not exist
Explanation: The transmission queue does not exist on this queue manager.
User Response: None.
AMQ8433 You are not allowed to set both the CLUSTER and CLUSNL fields.
Explanation: 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.
User Response: None.
AMQ8434 The repository is unavailable.
Explanation: The repository is unavailable and the data cannot be accessed. Stop and restart the queue manager.
User Response: None.
AMQ8435 All valid MQSC commands were processed.
Explanation: The MQSC script contains no commands that failed to process.
User Response: None.
AMQ8436 One valid MQSC command could not be processed.
Explanation: The MQSC script contains one command that failed to process.
User Response: None.
AMQ8437 No MQSC commands read.
Explanation: The MQSC script contains no commands.
User Response: None.
AMQ8438 One MQSC command read.
Explanation: The MQSC script contains one command.
User Response: None.
AMQ8439 No commands have a syntax error.
Explanation: The MQSC script contains no commands having a syntax error.
User Response: None.
AMQ8440 One command has a syntax error.
Explanation: The MQSC script contains one command which has a syntax error.
User Response: None.
AMQ8443 Only the CLUSTER or CLUSNL field may have a value.
Explanation: 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.
User Response: None.
AMQ8444 The CLUSTER or CLUSNL fields must have a value.
Explanation: 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.
User Response: None.
AMQ8445 Program cannot open queue manager object.
Explanation: An attempt to open a queue manager object has failed.
User Response: See the previously listed messages in the job log.
AMQ8446 Channel is currently active.
Explanation: The requested operation failed because the channel is currently active.
User Response: See the previously listed messages in the job log.
AMQ8447 Requested operation on channel '&5' not valid for this channel type.
Explanation: The operation requested cannot be performed because channel '&5' is not of a suitable type. For example, only sender, server and cluster-sender channels can be resolved.
User Response: Check that the correct operation was requested. If it was, check that the correct channel name was specified.
AMQ8448 Channel '&5' is not running.
Explanation: A request to end channel '&5' has failed because the channel is not running.
User Response: Check that the correct operation was requested. If it was, check that the correct channel name was specified.
AMQ8449 Queue '&5' inhibited for MQGET.
Explanation: An MQGET failed because the queue '&5' had been previously inhibited for MQGET.
User Response: None.
AMQ8450 Display queue status details.
Explanation: The MQSC DISPLAY QSTATUS command completed successfully/. Details follow this message.
User Response:
AMQ8498 Starting WebSphere MQ script Commands.
Explanation: The MQSC script contains &1 commands.
User Response: None.
AMQ8499 Usage: runmqsc [-e] [-v] [-w WaitTime [-x]] QMgrName
Explanation: None.
User Response: None.
AMQ8500 WebSphere MQ Display MQ Files
Explanation:
User Response:
AMQ8501 Common services initialization failed with return code &1.
Explanation: A request by the command server to initialize common services failed with return code &1.
User Response: None.
AMQ8502 Connect shared memory failed with return code &1.
Explanation: A request by the command server to connect shared memory failed with return code &1.
User Response: None.
AMQ8503 Post event semaphore failed with return code &1.
Explanation: A request by the command server to post an event semaphore failed with return code &1.
User Response: None.
AMQ8504 Command server MQINQ failed with reason code &1.
Explanation: An MQINQ request by the command server, for the WebSphere MQ queue &3, failed with reason code &1.
User Response: None.
AMQ8505 Reallocate memory failed with return code &1.
Explanation: A request by the command server to reallocate memory failed with return code &1.
User Response: None.
AMQ8506 Command server MQGET failed with reason code &1.
Explanation: An MQGET request by the command server, for the WebSphere MQ queue &3, failed with reason code &1.
User Response: None.
AMQ8507 Command server MQPUT1 request for an undelivered message failed with reason code &1.
Explanation: An attempt by the command server to put a message to the dead-letter queue, using MQPUT1, failed with reason code &1. The MQDLH reason code was &2.
User Response: None.
AMQ8508 Queue Manager Delete Object List failed with return code &1.
Explanation: A request by the command server to delete a queue manager object list failed with return code &1.
User Response: None.
AMQ8509 Command server MQCLOSE reply-to queue failed with reason code &1.
Explanation: An MQCLOSE request by the command server for the reply-to queue failed with reason code &1.
User Response: None.
AMQ8510 Command server queue is open, try again later.
Explanation:
User Response:
AMQ8511 Usage: strmqcsv [QMgrName]
Explanation:
User Response:
AMQ8512 Usage: endmqcsv [-c | -i] QMgrName
Explanation:
User Response:
AMQ8513 Usage: dspmqcsv [QMgrName]
Explanation:
User Response:
AMQ8514 No response received after &1 seconds.
Explanation: The command server has not reported the status of running, to the start request, before the timeout of &1 seconds was reached.
User Response: None.
AMQ8549 Total string length exceeds the maximum value of 999 characters.
Explanation: 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.
User Response: None.
AMQ8550 Display namelist details.
Explanation: The MQSC DISPLAY NAMELIST command completed successfully, and details follow this message.
User Response: None.
AMQ8551 WebSphere MQ namelist changed.
Explanation: WebSphere MQ namelist &5 changed.
User Response: None.
AMQ8552 WebSphere MQ namelist created.
Explanation: WebSphere MQ namelist &5 created.
User Response: None.
AMQ8553 WebSphere MQ namelist deleted.
Explanation: WebSphere MQ namelist &5 deleted.
User Response: None.
AMQ8554 String List String Count Error.
Explanation: 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.
User Response: None.
AMQ8555 String List String Length Error.
Explanation: A string in a string list assigned to a keyword is longer than the maximum permitted for that keyword.
User Response: None.
AMQ8556 RESUME QUEUE MANAGER accepted.
Explanation: 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.
User Response: None.
AMQ8557 SUSPEND QUEUE MANAGER accepted.
Explanation: 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.
User Response: None.
AMQ8558 REFRESH CLUSTER accepted.
Explanation: 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.
User Response: None.
AMQ8559 RESET CLUSTER accepted.
Explanation: 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.
User Response: None.
AMQ8560 WebSphere MQ security cache refreshed.
Explanation: The Object Authority Manager security cache has been refreshed.
User Response: None.
AMQ8561 Domain controller unavailable.
Explanation: WebSphere MQ was unable to contact the domain controller to obtain information for user '&3'.
User Response: Ensure that a domain controller for the domain on which user '&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.
AMQ8563 WebSphere MQ authentication information object created.
Explanation: WebSphere MQ authentication information object &5 created.
User Response: None.
AMQ8564 WebSphere MQ authentication information object deleted.
Explanation: WebSphere MQ authentication information object &5 deleted.
User Response: None.
AMQ8566 Display authentication information details.
Explanation: The MQSC DISPLAY AUTHINFO command completed successfully. Details follow this message.
User Response: None.
AMQ8567 WebSphere MQ authentication information changed.
Explanation: WebSphere MQ authentication information &5 changed.
User Response: None.
AMQ8601 WebSphere MQ trigger monitor started.
Explanation: The WebSphere MQ trigger monitor has been started.
User Response: None.
AMQ8602 WebSphere MQ trigger monitor ended.
Explanation: The WebSphere MQ trigger monitor has ended.
User Response: None.
AMQ8603 Usage: runmqtrm [-m QMgrName] [-q InitQ]
Explanation: None.
User Response: None.
AMQ8604 Use of WebSphere MQ trigger monitor not authorized.
Explanation: The trigger monitor cannot be run due to lack of authority to the requested queue manager or initiation queue.
User Response: Obtain the necessary authority from your security officer or WebSphere MQ administrator. Then try the command again.
AMQ8605 Queue manager not available to the WebSphere MQ trigger monitor
Explanation: The queue manager specified for the trigger monitor does not exist, or is not active.
User Response: 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.
AMQ8606 Insufficient storage available for the WebSphere MQ trigger monitor.
Explanation: There was insufficient storage available for the WebSphere MQ trigger monitor to run.
User Response: Free some storage and then try the command again.
AMQ8607 WebSphere MQ trigger monitor connection failed.
Explanation: The trigger monitor's connection to the requested queue manager failed because of MQI reason code &1 from MQCONN.
User Response: Consult your systems administrator about the state of the queue manager.
AMQ8608 WebSphere MQ trigger monitor connection broken.
Explanation: 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.
User Response: Consult your systems administrator about the state of the queue manager.
AMQ8609 Initiation queue missing or wrong type
Explanation: The named initiation queue could not be found; or the queue type is not correct for an initiation queue.
User Response: 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.
AMQ8610 Initiation queue in use
Explanation: The WebSphere MQ trigger monitor could not open the initiation queue because the queue is open for exclusive use by another application.
User Response: Wait until the queue is no longer in use, and try the command again.
AMQ8611 Initiation queue could not be opened.
Explanation: The WebSphere MQ trigger monitor could not open the initiation queue; reason code &1 was returned from MQOPEN.
User Response: Consult your systems administrator.
AMQ8612 Waiting for a trigger message
Explanation: The WebSphere MQ trigger monitor is waiting for a message to arrive on the initiation queue.
User Response: None.
AMQ8613 Initiation queue changed or deleted
Explanation: The WebSphere MQ trigger monitor is unable to continue because the initiation queue has been deleted or changed since it was opened.
User Response: Retry the command.
AMQ8614 Initiation queue not enabled for input.
Explanation: The WebSphere MQ trigger monitor cannot read from the initiation queue because input is not enabled.
User Response: Ask your systems administrator to enable the queue for input.
AMQ8615 WebSphere MQ trigger monitor failed to get message.
Explanation: The WebSphere MQ trigger monitor failed because of MQI reason code &1 from MQGET.
User Response: Consult your systems administrator.
AMQ8616 End of application trigger.
Explanation: The action to trigger an application has been completed.
User Response: None.
AMQ8617 Not a valid trigger message.
Explanation: 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.
User Response: Consult your systems administrator.
AMQ8618 Error starting triggered application.
Explanation: An error was detected when trying to start the application identified in a trigger message.
User Response: Check that the application the trigger monitor was trying to start is available.
AMQ8619 Application type &1 not supported.
Explanation: A trigger message was received which specifies application type &1; the trigger monitor does not support this type.
User Response: Use an alternative trigger monitor for this initiation queue.
AMQ8620 Trigger message with warning &1
Explanation: 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 &1.
User Response: None.
AMQ8621 Usage: runmqtmc [-m QMgrName] [-q InitQ]
Explanation: None.
User Response: None.
AMQ8622 Usage: CICS-Transaction-Name [MQTMC2 structure]
Explanation: None.
User Response: None.
AMQ8623 Usage: &3 [-m QMgrName] [-q InitQ]
Explanation: None.
User Response: None.
AMQ8701 Usage: rcdmqimg [-z] [-l] [-m QMgrName] -t ObjType [GenericObjName]
Explanation: None.
User Response: None.
AMQ8702 Usage: rcrmqobj [-z] [-m QMgrName] -t ObjType [GenericObjName]
Explanation: None.
User Response: None.
AMQ8703 Usage: dspmqfls [-m QMgrName] [-t ObjType] GenericObjName
Explanation: None.
User Response: None.
AMQ8708 Dead-letter queue handler started to process INPUTQ(&3).
Explanation: 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.
User Response: None.
AMQ8709 Dead-letter queue handler ending.
Explanation: 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.
User Response: None.
AMQ8710 Usage: runmqdlq [QName[QMgrName]].
Explanation: Syntax for the usage of runmqdlq.
User Response: None.
AMQ8721 Dead-letter queue message not prefixed by a valid MQDLH.
Explanation: 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.
User Response: Remove the message that is not valid 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.
AMQ8722 Dead-letter queue handler unable to put message: Rule &1 Reason &2.
Explanation: 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.
User Response: 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.
AMQ8741 Unable to connect to queue manager.
Explanation: The dead-letter queue handler (runmqdlq) could not connect to queue manager &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 (&1) and the reason (&2) can be used to identify the error. The dead-letter queue handler ends.
User Response: Take appropriate action based upon the completion code and reason.
AMQ8742 Unable to open queue manager: CompCode = &1 Reason = &2.
Explanation: 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.
User Response: Take appropriate action based upon the completion code and reason.
AMQ8743 Unable to inquire on queue manager: CompCode = &1 Reason = &2.
Explanation: 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.
User Response: Take appropriate action based upon the completion code and reason.
AMQ8744 Unable to close queue manager: CompCode = &1 Reason = &2.
Explanation: 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.
User Response: Take appropriate action based upon the completion code and reason.
AMQ8745 Unable to open dead-letter queue for browse.
Explanation: The dead-letter queue handler (runmqdlq) could not open the dead-letter queue &3 for browsing. This message is typically issued because another process has opened the dead-letter queue for exclusive access, or because a dead-letter queue name that is not valid was specified. Other possible reasons include resource shortages or insufficient authority. The completion code(&1) and the reason(&2) can be used to identify the error. The dead-letter queue handler ends.
User Response: Take appropriate action based upon the completion code and reason.
AMQ8746 Unable to close dead-letter queue: CompCode = &1 Reason = &2.
Explanation: 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.
User Response: Take appropriate action based upon the completion code and reason.
AMQ8747 Integer parameter outside permissible range.
Explanation: The integer parameter (&2) supplied to the dead-letter handler was outside the valid range for &3 on line &1.
User Response: Correct the input data and restart the dead-letter queue handler.
AMQ8748 Unable to get message from dead-letter queue: CompCode = &1 Reason = &2.
Explanation: 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.
User Response: Take appropriate action based upon the completion code and reason.
AMQ8749 Unable to commit/backout action on dead-letter queue: CompCode = &1 Reason = &2.
Explanation: 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.
User Response: Take appropriate action based upon the completion code and reason.
AMQ8750 No valid input provided to runmqdlq.
Explanation: 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 not valid, earlier messages will have been produced explaining the cause of the error. The dead-letter queue handler will ends.
User Response: Correct the input data and restart the dead-letter queue handler.
AMQ8751 Unable to obtain private storage.
Explanation: 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.
User Response: 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.
AMQ8752 Parameter(&3) exceeds maximum length on line &1.
Explanation: A parameter supplied as input to the dead-letter handler exceeded the maximum length for parameters of that type.
User Response: Correct the input data and restart the dead-letter queue handler.
AMQ8753 Duplicate parameter(&3) found on line &1.
Explanation: Two or more parameters of the same type were supplied on a single input line to the dead-letter queue handler.
User Response: Correct the input and restart the dead-letter queue handler.
AMQ8756 Error detected releasing private storage.
Explanation: 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.
User Response: 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.
AMQ8757 Integer parameter(&3) outside permissible range on line &1.
Explanation: An integer supplied as input to the dead-letter handler was outside the valid range of integers supported by the dead-letter queue handler.
User Response: Correct the input data and restart the dead-letter queue handler.
AMQ8758 &1 errors detected in input to runmqdlq.
Explanation: 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.
User Response: Correct the input data and restart the dead-letter queue handler.
AMQ8759 Invalid combination of parameters to dead-letter queue handler on line &1.
Explanation: A combination of input parameters that is not valid 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).
User Response: Correct the input data and restart the dead-letter queue handler.
AMQ8760 Unexpected failure while initializing process: Reason = &1.
Explanation: 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.
User Response: 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.
AMQ8761 Unexpected failure while connecting to queue manager: CompCode = &1 Reason = &2.
Explanation: 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.
User Response: 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.
AMQ8762 Unexpected error while attempting to open queue manager: CompCode = &1 Reason = &2.
Explanation: 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.
User Response: 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.
AMQ8763 Unexpected error while inquiring on queue manager: CompCode = &1 Reason = &2.
Explanation: 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.
User Response: 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.
AMQ8764 Unexpected error while attempting to close queue manager: CompCode = &1 Reason = &2.
Explanation: 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.
User Response: 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.
AMQ8765 Unexpected failure while opening dead-letter queue for browse: CompCode = &1 Reason = &2.
Explanation: 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.
User Response: 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.
AMQ8766 Unexpected error while closing dead-letter queue: CompCode = &1 Reason = &2.
Explanation: 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.
User Response: 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.
AMQ8767 Unexpected error while getting message from dead-letter queue: CompCode = &1 Reason = &2.
Explanation: 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.
User Response: 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.
AMQ8768 Unexpected error committing/backing out action on dead-letter queue: CompCode = &1 Reason = &2.
Explanation: 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.
User Response: 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.
AMQ8769 Unable to disconnect from queue manager: CompCode = &1 Reason = &2.
Explanation: 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.
User Response: 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.
AMQ8919 There are no matching WebSphere MQ queue manager names.
Explanation:
User Response:
Comments
Post a Comment