WebSphere MQ Explorer messages
AMQ4000New object not created because the default object for the object type could not be found.Severity:10 : Warning
Explanation:The creation of an object requires a default template for each object type. The required default template for this object type could not be found.
Response:Determine why the default object is not available, or create a new one. Then try the request again.
AMQ4001The queue manager specified is already shown in the console.Severity:0 : Information
Response:Message for information only.
AMQ4002Are you sure you want to delete the <insert_0> named <insert_1>?Severity:10 : Warning
Explanation:A confirmation is required before the specified object is deleted. The type of object and name are provided in the message.
Response:Continue only if you want to permanently delete the object.
AMQ4003WebSphere MQ system objects are used internally by WebSphere MQ. You are advised not to delete them. Do you want to keep the WebSphere MQ system object?Severity:0 : Information
Explanation:A confirmation is required before an internal WebSphere MQ system object (for example SYSTEM.DEFAULT.LOCAL.QUEUE) is deleted.
Response:Continue only if you want to permanently delete the system object.
AMQ4004Clear all messages from the queue?Severity:10 : Warning
Explanation:The removal of the messages from the queue is an irreversible action. If the command is allowed to proceed the action cannot be undone.
Response:Continue only if you want to permanently delete the messages.
AMQ4005The object has been replaced or deleted. The properties could not be applied.Severity:10 : Warning
Explanation:During the process of updating the properties of the object, it was determined that the object has either been deleted or replaced by another instance. The properties have not been applied.
AMQ4006WebSphere MQ successfully sent data to the remote queue manager and received the data returned.Severity:0 : Information
Explanation:An open channel has been successfully verified by WebSphere MQ as the result of a user request.
Response:Message for information only.
AMQ4007The message sequence number for the channel was reset.Severity:0 : Information
Explanation:A channel has had its sequence number successfully reset by WebSphere MQ as the result of a user request.
Response:Message for information only.
AMQ4008The request to start the channel was accepted.Severity:0 : Information
Explanation:A channel has been started successfully by WebSphere MQ as the result of a user request.
Response:Message for information only.
AMQ4009The request to stop the channel was accepted.Severity:0 : Information
Explanation:A channel has been stopped successfully by WebSphere MQ as the result of a user request.
Response:Message for information only.
AMQ4010The 'in-doubt' state was resolved.Severity:0 : Information
Explanation:A channel has had its 'in-doubt' state resolved successfully by WebSphere MQ as the result of a user request.
Response:Message for information only
AMQ4011The queue has been cleared of messages.Severity:0 : Information
Explanation:The CLEAR command completed successfully and has removed all messages from the target queue. If the CLEAR was performed using the MQGET API command, uncommitted messages might still be on the queue.
AMQ4012The object was created successfully but it is not visible with the current settings for visible objects.Severity:0 : Information
Response:Message for information only.
AMQ4014The character <insert_0> is not valid.Severity:10 : Warning
AMQ4015Supply a non-blank name.Severity:0 : Information
Response:Enter a valid name.
AMQ4016The test message was put successfully.Severity:0 : Information
Explanation:The request to place a message on the target queue has completed successfully. The queue now contains the message.
Response:Message for information only.
AMQ4019An object called <insert_0> already exists. Do you want to replace the definition of the existing object?Severity:0 : Information
Response:Confirm that you want to replace the definition.
AMQ4020The changes you are making to the attributes of page "<insert_0>" will affect the operation of the queue manager or another program currently using the object. Do you want to force the change to the object's attributes?Severity:10 : Warning
Explanation:You are trying to change a object that cannot be changed because the object is in use, or the change will affect other programs or queue managers. Some changes can be forced anyway.
Response:Select Yes to try forcing the changes, or No to abandon the change.
AMQ4021Failed to access one or more WebSphere MQ objects.Severity:10 : Warning
Explanation:The objects' icons have been marked to indicate the objects in error.
AMQ4022The name specified for the initiation queue is the same as the name of the queue itself.Severity:0 : Information
Response:Specify a different name to that of the object being created or altered.
AMQ4023The queue manager <insert_0> does not exist on this computer.Severity:0 : Information
Response:Message for information only.
AMQ4024The object cannot be replaced.Severity:0 : Information
Explanation:The request to replace the object was unsuccessful.
Response:To define this object, delete the existing object and try the operation again.
AMQ4025The changes made to the cluster attributes of the queue will take effect once they have propagated across the network.Severity:0 : Information
Response:Refresh any views containing the cluster queues in the affected clusters to show the changes.
AMQ4026You have created a queue which is shared in one or more clusters. The queue will be available as a cluster queue once its definition has propagated across the network.Severity:0 : Information
Response:Refresh any views containing the cluster queues in the affected clusters to show the cluster queue.
AMQ4027An error occurred connecting to the queue manager. Are you sure you want to show this queue manager in the folder anyway?Severity:10 : Warning
Explanation:A connection could not be made to the specified remote queue manager.
Response:Ensure that the named queue manager is running on the host and port specified, and has a channel corresponding to the specified name. Ensure that you have the authority to connect to the remote queue manager, and ensure that the network is running. Select Yes if you believe that the problem can be resolved later. Select No if you want to correct the problem now and try again.
AMQ4028Platform not supported. This queue manager cannot be administered by the WebSphere MQ Explorer because it is running on an unsupported platform. The value <insert_0> for the Platform attribute of the queue manager is not supported by the WebSphere MQ Explorer.Severity:20 : Error
AMQ4029Command level too low. This queue manager cannot be administered by the WebSphere MQ Explorer because the command level of the queue manager is less than <insert_0>.Severity:20 : Error
Response:If you want to administer this queue manager, upgrade it to a newer version of WebSphere MQ.
AMQ4030Queue manager cannot be administered because codepage conversion table not found.Severity:20 : Error
Explanation:This queue manager cannot be administered by the WebSphere MQ Explorer because a codepage conversion table was not found.
Response:Install a codepage conversion table from CCSID <insert_0> to CCSID <insert_1> on the computer on which the WebSphere MQ Explorer is running.
AMQ4031Queue manager cannot be administered because CCSID not found.Severity:20 : Error
Explanation:This queue manager cannot be administered by the WebSphere MQ Explorer because CCSID <insert_0> cannot be found in the CCSID table. The WebSphere MQ Explorer cannot convert character data to or from the unrecognized CCSID.
AMQ4032Command server not responding within timeout period.Severity:10 : Warning
Response:Ensure that the command server is running and that the queue called 'SYSTEM.ADMIN.COMMAND.QUEUE' is configured to enable programs to get messages from it.
AMQ4033Cannot get messages from the queue.Severity:0 : Information
Explanation:A reason code returned when the object was opened for input indicated that the queue is disabled for MQGET request.
Response:To get messages from this queue, enable it for GET requests.
AMQ4034Message too long. You tried to put a message on a queue that was bigger than the maximum allowed for the queue or queue manager.Severity:10 : Warning
Explanation:The request to put a message on a queue returned a reason code indicating that the data length of the message exceeds the maximum allowed in the definition of the queue.
Response:Either change the MAXMSGL attribute of the queue so that it is equal to or greater than the length of the message, or reduce the length of the message being put on the queue.
AMQ4035No message available. The response message did not arrive within a reasonable amount of time.Severity:0 : Information
Explanation:The request to get a message from a queue returned a reason code indicating that there are currently no messages on the queue that meet the selection criteria specified on the GET request.
AMQ4036Access not permitted. You are not authorized to perform this operation.Severity:10 : Warning
Explanation:The queue manager's security mechanism has indicated that the userid associated with this request is not authorized to access the object.
AMQ4037Object definition changed since it was opened.Severity:0 : Information
Explanation:Object definitions that affect this object have been changed since the Hobj handle used on this call was returned by the MQOPEN call.
Response:Issue an MQCLOSE call to return the handle to the system. It is then usually sufficient to reopen the object and try the operation again.
AMQ4038Object damaged.Severity:10 : Warning
Explanation:The object is damaged and cannot be accessed.
Response:The object should be deleted. Alternatively, it might be possible to recover it from a media image or backup.
AMQ4039Object in use. The object is already opened by another application.Severity:10 : Warning
Explanation:An MQOPEN call was issued, but the object in question has already been opened by this or another application with options that conflict with those specified in the Options parameter. This arises if the request is for shared input, but the object is already open for exclusive input. It also arises if the request is for exclusive input, but the object is already open for input (of any sort).
Response:To change the attributes of an object, specify the Force option as 'Yes' to apply the changes. If you do this, any applications using the object must close and reopen the object to proceed.
AMQ4040Cannot put messages on this queue.Severity:0 : Information
Explanation:MQPUT and MQPUT1 calls are currently inhibited for the queue, or for the queue to which this queue resolves.
AMQ4042Queue full. The queue contains the maximum number of messages.Severity:10 : Warning
Explanation:On an MQPUT or MQPUT1 call, the call failed because the queue is full; that is, it already contains the maximum number of messages possible.
AMQ4043Queue manager not available for connection.Severity:10 : Warning
Response:Ensure that the queue manager is running. If the queue manager is running on another computer, ensure it is configured to accept remote connections.
AMQ4044Queue manager stopping.Severity:0 : Information
Explanation:An MQI call was issued, but the call failed because the queue manager is shutting down. If the call was an MQGET call with the MQGMO_WAIT option, the wait has been canceled.
Response:We cannot issue any more MQI calls.
AMQ4045Queue not empty. The queue contains one or more messages or uncommitted PUT or GET requests.Severity:0 : Information
Explanation:An operation that requires the queue to be empty has failed because the queue either contains messages or has uncommitted PUT or GET requests outstanding.
AMQ4046Insufficient system resources available.Severity:20 : Error
AMQ4047Insufficient storage available.Severity:20 : Error
AMQ4048The request received an unexpected reason code from an underlying API or command request. The reason code was <insert_0>Severity:20 : Error
Explanation:While executing the requested operation, an unexpected return code was received. This has resulted in the operation not completing as expected.
Response:Use the appropriate documentation to determine why the reason code was returned.
AMQ4049Unknown object name.Severity:10 : Warning
Explanation:A command or API request was issued, but the object cannot be found.
AMQ4050Allocation failed. An attempt to allocate a conversation to a remote system failed.Severity:10 : Warning
Explanation:The error might be due to an incorrect entry in the channel definition or it might be that the listening program on the remote system was not running.
AMQ4051Bind failed. The bind to a remote system during session negotiation failed.Severity:10 : Warning
AMQ4052Coded character-set ID error. Cannot convert a command message to the CCSID of the target queue manager.Severity:10 : Warning
AMQ4053Channel in doubt. Operation not completed.Severity:10 : Warning
Explanation:The operation could not complete because the channel was in doubt.
AMQ4054Channel in use.Severity:10 : Warning
Explanation:An attempt was made to perform an operation on a channel, but the channel is currently active.
AMQ4055Channel status not found.Severity:10 : Warning
Explanation:No channel status is available for this channel. This might indicate that the channel has not been used.
AMQ4056Command failed.Severity:10 : Warning
AMQ4057Configuration error in the channel definition or communication subsystem.Severity:10 : Warning
Explanation:Allocation of a conversation is not possible.
AMQ4058Connection closed.Severity:10 : Warning
Explanation:The connection to a remote system has unexpectedly broken while receiving data.
AMQ4059Could not establish a connection to the queue manager.Severity:10 : Warning
Explanation: