AMQ4000-4999: User interface messages (WebSphere MQ for Windows and Linux® systems)

AMQ4000: New 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 unavailable, or create a new one. Then try the request again.

AMQ4001: The queue manager specified has already been added to WebSphere MQ Explorer.
Severity: 0: Information
Response: Message for information only. If the queue manager is not displayed in the Navigator view ensure that the queue manager is not hidden.

AMQ4002: Are you sure that you want to delete the object named <insert_0>?
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.

AMQ4003: WebSphere 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.

AMQ4004: Clear 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.

AMQ4005: The 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.

AMQ4006: WebSphere 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.

AMQ4007: The 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.

AMQ4008: The 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.

AMQ4009: The 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.

AMQ4010: The '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

AMQ4011: The queue has been cleared of messages.
Severity: 0: Information
Explanation: The CLEAR command has 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.

AMQ4012: The object was created successfully but it is not visible with the current settings for visible objects.
Severity: 0: Information
Response: Message for information only.

AMQ4014: The character <insert_0> is not valid.
Severity: 10: Warning

AMQ4015: Supply a non-blank name.
Severity: 0: Information
Response: Enter a valid name.

AMQ4016: The 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.

AMQ4019: An object called <insert_0> exists. Do you want to replace the definition of the existing object?
Severity: 0: Information
Response: Confirm that you want to replace the definition.

AMQ4020: The 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 an object that cannot be changed because it is in use, or the change affects 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.

AMQ4021: Failed to access one or more WebSphere MQ objects.
Severity: 10: Warning
Explanation: The icons of the objects have been marked to indicate the objects in error.

AMQ4022: The 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.

AMQ4023: The queue manager <insert_0> does not exist on this computer.
Severity: 0: Information
Response: Message for information only.

AMQ4024: The 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.

AMQ4025: The changes made to the cluster attributes of the queue 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.

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

AMQ4027: An error occurred connecting to queue manager <insert_0>. Are you sure that 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.

AMQ4028: Platform 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

AMQ4029: Command level too low. This queue manager cannot be administered by the WebSphere MQ Explorer.
Severity: 20: Error
Response: If you want to administer this queue manager, you must upgrade it to a newer version of WebSphere MQ.

AMQ4030: Queue manager cannot be administered because code page conversion table not found.
Severity: 20: Error
Explanation: This queue manager cannot be administered by the WebSphere MQ Explorer because a code page conversion table was not found.
Response: Install a code page conversion table from CCSID <insert_0> to CCSID <insert_1> on the computer on which the WebSphere MQ Explorer is running.

AMQ4031: Queue 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.

AMQ4032: Command 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.

AMQ4033: Cannot 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.

AMQ4034: Message 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.

AMQ4035: No 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.

AMQ4036: Access not permitted. You are not authorized to perform this operation.
Severity: 10: Warning
Explanation: The security mechanism of the queue manager has indicated that the user ID associated with this request is not authorized to access the object.

AMQ4037: Object 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 normally sufficient to reopen the object and try the operation again.

AMQ4038: Object damaged.
Severity: 10: Warning
Explanation: The object is damaged and cannot be accessed.
Response: The object must be deleted. Alternatively, it might be possible to recover it from a media image or backup.

AMQ4039: Object 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 application or another application with options that conflict with those options specified in the Options parameter. This situation 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 specify the Force option as 'Yes', any applications using the object must close and reopen the object to proceed.

AMQ4040: Cannot 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.

AMQ4042: Queue 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.

AMQ4043: Queue manager not available for connection.
Severity: 20: Error
Response: Ensure that the queue manager is running. If the queue manager is running on another computer, ensure that it is configured to accept remote connections.

AMQ4044: Queue manager <insert_0> is 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: You cannot issue any more MQI calls.

AMQ4045: Queue 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.

AMQ4046: Insufficient system resources available.
Severity: 20: Error

AMQ4047: Insufficient storage available.
Severity: 20: Error

AMQ4048: The request received an unexpected reason code from an underlying API or command request. The reason code was <insert_0>.
Severity: 20: Error
Explanation: While running the requested operation, an unexpected return code was received, resulting in the operation not completing as expected.
Response: Use the reason code to determine the underlying reason for the failure.

AMQ4049: Unknown object name.
Severity: 10: Warning
Explanation: A command or API request was issued, but the object cannot be found.

AMQ4050: Allocation 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.

AMQ4051: Bind failed. The bind to a remote system during session negotiation failed.
Severity: 10: Warning

AMQ4052: Coded character-set ID error. Cannot convert a command message to the CCSID of the target queue manager.
Severity: 10: Warning

AMQ4053: Channel in doubt. Operation not completed.
Severity: 10: Warning
Explanation: The operation could not be completed because the channel was in doubt.

AMQ4054: Channel in use.
Severity: 10: Warning
Explanation: An attempt was made to perform an operation on a channel, but the channel is currently active.

AMQ4055: Channel status not found.
Severity: 10: Warning
Explanation: No channel status is available for this channel, possibly indicating that the channel has not been used.

AMQ4056: Command failed.
Severity: 10: Warning

AMQ4057: Configuration error in the channel definition or communication subsystem.
Severity: 10: Warning
Explanation: Allocation of a conversation is not possible.

AMQ4058: Connection closed.
Severity: 10: Warning
Explanation: The connection to a remote system has unexpectedly broken while receiving data.

AMQ4059: Could not establish a connection to the queue manager.
Severity: 10: Warning
Explanation: The attempt to connect to the queue manager failed. This failure might be because the queue manager is incorrectly configured to allow a connection from this system, or the connection has been broken.
Response: Try the operation again. If the error persists, examine the problem determination information to see if any information has been recorded.

AMQ4060: Dynamic queue scope error.
Severity: 10: Warning
Explanation: The Scope attribute of the queue was set to MQSCO_CELL but this value is not allowed for a dynamic queue.

AMQ4061: Remote system unavailable and unable to allocate a conversation to a remote system.
Severity: 10: Warning
Response: The error might be transitory; try again later.

AMQ4062: An MQINQ call failed when the queue manager inquired about a WebSphere MQ object.
Severity: 10: Warning
Response: Check the error log of the queue manager for more information about the error.

AMQ4063: An MQOPEN call failed when the queue manager tried to open a WebSphere MQ object.
Severity: 20: Error
Response: If the error occurred while starting a channel check that the transmission queue used by the channel exists and try the operation again. If the error persists check the error log of the queue manager for more information about the error.

AMQ4064: An MQSET call failed when the queue manager tried to set the values of the attributes of a WebSphere MQ object.
Severity: 10: Warning
Response: Check the error log of the queue manager for more information about the error.

AMQ4065: Message sequence number error.
Severity: 10: Warning
Explanation: The message sequence number parameter was not valid.

AMQ4066: Message truncated because it is larger than the command server's maximum valid message size.
Severity: 10: Warning

AMQ4067: Communications manager not available.
Severity: 20: Error
Explanation: The communications subsystem is unavailable.

AMQ4068: The queue specified in the channel definition is not a transmission queue, or is in use.
Severity: 10: Warning

AMQ4069: Object already exists.
Severity: 10: Warning
Explanation: Unable to create object because the object already existed.

AMQ4070: Object is open.
Severity: 10: Warning
Explanation: An attempt was made to delete, change, or clear an object that is in use.
Response: Wait until the object is not in use, then try again.

AMQ4071: Object has wrong type. Could not replace a queue object of a different type.
Severity: 10: Warning

AMQ4072: Queue already exists in cell.
Severity: 10: Warning
Explanation: cannot define a queue with cell scope or change the scope of an existing queue from queue-manager scope to cell scope, because a queue with that name already exists in the cell.

AMQ4073: Ping error. You can only ping a sender or server channel. If the local channel is a receiver channel, ping from the remote queue manager.
Severity: 10: Warning

AMQ4074: Receive failed, possibly due to a communications failure.
Severity: 10: Warning

AMQ4075: Error while receiving data from a remote system, possibly due to a communications failure.
Severity: 10: Warning

AMQ4076: Remote queue manager terminating.
Severity: 10: Warning
Explanation: The channel stopped because the remote queue manager was terminating.

AMQ4077: Remote queue manager not available.
Severity: 10: Warning
Explanation: The channel could not be started because the remote queue manager was not available.
Response: Ensure that the remote queue manager is started, and that it is configured to accept incoming communication requests.

AMQ4078: Send failed. An error occurred while sending data to a remote system, possibly due to a communications failure.
Severity: 10: Warning

AMQ4079: Channel closed by security exit.
Severity: 10: Warning

AMQ4080: Remote channel not known.
Severity: 10: Warning
Explanation: There is no definition of this channel on the remote system.

AMQ4081: User exit not available.
Severity: 10: Warning
Explanation: The channel was closed because the user exit specified does not exist.

AMQ4082: Unexpected WebSphere MQ error (<insert_0>).
Severity: 20: Error

AMQ4083: Queue manager name not known.
Severity: 10: Warning
Explanation: If the queue manager is remote, this might indicate that another queue manager is incorrectly using the same connection name. Queue managers using TCP/IP on the same computer must listen on different port numbers. This means that they will also have different connection names.

AMQ4084: Cell directory is not available.
Severity: 10: Warning
Explanation: The Scope attribute of the queue was set to MQSCO_CELL but no name service supporting a cell directory has been configured.
Response: Configure a name service to support the cell directory.

AMQ4085: No name supplied for transmission queue.
Severity: 10: Warning
Response: Supply a non-blank transmission queue name for this channel type.

AMQ4086: No connection name supplied.
Severity: 10: Warning
Response: Supply a non-blank connection name for this channel type.

AMQ4087: An error occurred while trying to use a cluster resource.
Severity: 10: Warning
Response: Check that the queues with names that start with 'SYSTEM.CLUSTER.' are not full and that messages are allowed to be put on them.

AMQ4088: Cannot share transmission queue in cluster.
Severity: 10: Warning
Explanation: The queue is a transmission queue and cannot be shared in a cluster.

AMQ4089: PUT commands inhibited for system command queue called <insert_0>.
Severity: 10: Warning

AMQ4090: Are you sure that you want to inhibit PUT and GET commands for the queue called 'SYSTEM.ADMIN.COMMAND.QUEUE'? If you do, you will no longer be able to administer the queue manager using the WebSphere MQ Explorer.
Severity: 10: Warning
Explanation: WebSphere MQ Explorer uses the queue called 'SYSTEM.ADMIN.COMMAND.QUEUE' to administer the queue manager.
Response: Continue only if you really want to inhibit PUT or GET commands for this queue and stop using the WebSphere MQ Explorer to administer the queue manager.

AMQ4091: Cannot connect to remote queue manager.
Severity: 10: Warning
Explanation: The remote queue manager is using an unsupported protocol for connections. The WebSphere MQ Explorer only supports connections to remote queue managers using the TCP/IP protocol.

AMQ4092: The queue manager could not be removed from the cluster because its membership of the cluster is defined using namelist <insert_0>.
Severity: 10: Warning
Response: To remove the queue manager from the cluster, remove it from the namelist. Ensure that you do not inadvertently affect the definitions of other objects using the namelist.

AMQ4093: The cluster specified is already shown in the console.
Severity: 0: Information

AMQ4094: An error occurred adding this cluster to the console. Are you sure that you want to show this cluster in the console anyway?
Severity: 10: Warning
Response: 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.

AMQ4095: Queue manager <insert_0> is not a repository queue manager for cluster <insert_1>.
Severity: 0: Information
Explanation: To administer a cluster, the WebSphere MQ Explorer needs a connection to the repository queue manager.

AMQ4096: Are you sure that you want to clear the password?
Severity: 0: Information
Response: Check with the user before clearing the password. Continue only if you really want to clear the password.

AMQ4097: Unmatched quotation mark.
Severity: 10: Warning
Explanation: An unmatched quotation mark has been found in a list of attributes. Each value in the list can be enclosed in a pair of single or double quotation marks. (Only required for values which contain spaces, commas, or quotation marks.)
Response: Check that all opening and closing quotation marks are in pairs. (To include a quotation mark within an attribute, use two together with no space between.)

AMQ4098: Incorrect list format.
Severity: 10: Warning
Explanation: The attribute can contain a list of values which must be separated by a space or a comma. Each value in the list can be enclosed in a pair of single or double quotation marks. (Only required for values which contain spaces, commas, or quotation marks.)
Response: Check that values are separated by a space or a comma, and that all opening and closing quotation marks are in pairs. (To include a quotation mark within an attribute, use two together with no space between.)

AMQ4099: Cannot communicate with one or more repository queue managers. Cluster <insert_0> is configured to use one or more repository queue managers which communicate using a protocol other than TCP/IP.
Severity: 10: Warning
Explanation: The WebSphere MQ Explorer can only establish connections to remote queue managers using TCP/IP.
Response: To complete removal of the queue manager from the cluster, issue the RESET CLUSTER ACTION(FORCEREMOVE) command from the repository queue manager.

AMQ4103: An error occurred connecting to the queue manager. Are you sure that you want to show this queue manager in the folder?
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 machine specified in the selected channel definition table. Ensure that you have the authority to connect to the remote queue manager, and ensure that the network is operational. 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.

AMQ4104: The specified file <insert_0> does not contain a client definition table in the correct format.
Severity: 10: Warning
Explanation: The channel definition table is not in the correct format.
Response: Specify a file in the correct format.

AMQ4105: The remote queue manager has not been removed because it is still required by other plug-ins.
Severity: 10: Warning
Explanation: Other plug-ins have responded to the attempted removal of this queue manager by indicating that they are still using it.
Response: Ensure that the other plug-ins have finished using the queue manager before trying to delete it again.

AMQ4117: This action cannot be undone. Are you sure that you want to delete the WebSphere MQ queue manager <insert_0> from your system?
Severity: 10: Warning
Explanation: A confirmation is required before the queue manager is deleted.
Response: Continue only if you want to permanently delete the queue manager.

AMQ4121: The MQGET request received an unexpected reason code of <insert_0>.
Severity: 10: Warning
Explanation: An unexpected reason code was returned from an MQGET API request. Use the reason code to determine the underlying reason why the request failed.
Response: The MQGET request was not successful. Some messages might not have been retrieved.

AMQ4122: The MQPUT request received an unexpected reason code of <insert_0>.
Severity: 10: Warning
Explanation: An unexpected reason code was returned from an MQPUT API request. Use the reason code to determine the underlying reason why the request failed.
Response: MQPUT processing was unsuccessful. No message was placed on the queue.

AMQ4123: The object <insert_0> was deleted successfully.
Severity: 0: Information
Explanation: The object of the specified name has been successfully deleted.
Response: none.

AMQ4124: The MQOPEN request received an unexpected reason code of <insert_0>.
Severity: 10: Warning
Explanation: An unexpected reason code was returned from an MQOPEN API request. The queue has not been opened.
Response: Use the reason code to determine the underlying reason for the failure.

AMQ4125: Putting a test message on the queue received an unexpected reason code <insert_0>.
Severity: 10: Warning
Explanation: One of the underlying API requests was unsuccessful. The test message was not placed on the queue.

AMQ4126: The value of one of the properties specified is not valid. The request was not processed.
Severity: 20: Error
Response: Specify a different value.

AMQ4127: WebSphere MQ failed to read queue manager information from disk because the file format is not valid. The request was not processed.
Severity: 20: Error
Explanation: The format of the WebSphere MQ_Handles file is incorrect. This file has been backed up and removed, meaning that any remote queue manager definitions are lost. All local queue managers should be detected automatically and displayed in the WebSphere MQ Explorer.
Response: Ensure that the Eclipse workspace has not been corrupted.

AMQ4128: Could not start the iKeyMan program.
Severity: 30: Severe error
Explanation: An error was encountered when trying to execute the iKeyMan program.
Response: Try again. If symptoms persist contact your System Administrator.

AMQ4129: Could not query the user ID from Java.
Severity: 10: Warning
Explanation: The Java API System.getProperty("user.id") threw a SecurityException.
Response: Configure your Java security environment using the 'policytool' to allow WebSphere MQ Explorer to query the 'user.id'.

AMQ4130: A Browser Control could not be opened. Make sure Mozilla has been installed.
Severity: 10: Warning
Explanation: The SWT Browser control depends on Mozilla being installed.
Response: Ensure that the Mozilla browser is correctly installed.

AMQ4131: A Browser Control could not be opened.
Severity: 10: Warning
Explanation: The SWT Browser control depends on the system browser being installed.
Response: Ensure that the system browser is correctly installed.

AMQ4132: Are you sure that you want to stop the object named <insert_0>?
Severity: 10: Warning
Explanation: A confirmation is required before the specified object is stopped. The type of object and name are provided in the message.
Response: Continue only if you want to stop the object.

AMQ4133

When a queue manager is removed, WebSphere MQ Explorer destroys the connection information for that queue manager.

To see the queue manager at a later date use the Add Queue Manager wizard.

Remove the queue manager <insert_0> ?

Severity

10: Warning

Response

Continue only if you want to remove the queue manager.

AMQ4134: The default channel used by remote queue managers to administer this queue manager does not exist.
Do you want to create the default remote administration channel SYSTEM.ADMIN.SVRCONN to allow this queue manager to be administered by other queue managers?
Severity: 0: Information
Response: Select Yes to create the channel.

AMQ4135: The default channel used by remote queue managers to administer this queue manager is SYSTEM.ADMIN.SVRCONN.
Do you want to delete this channel to prevent the queue manager being administered by other queue managers?
Severity: 0: Information
Response: Select Yes to delete the channel.

AMQ4136: This operation deletes all files in the errors and trace directories (including, for example, read only files). This operation cannot be undone. Are you sure that you want to proceed?
Severity: 10: Warning
Explanation: Deleting all FFSTs and Trace from this machine means that any historical error logs and trace will be lost.
Response: Select Yes to clear the contents of the errors and trace directories.

AMQ4137: The default remote administration channel SYSTEM.ADMIN.SVRCONN has been deleted successfully.
Severity: 0: Information
Response: Message for information only.

AMQ4138: Are you sure that you want to import new settings that will overwrite the current settings? This operation cannot be undone.
Severity: 10: Warning
Explanation: Importing settings into the WebSphere MQ Explorer will overwrite the current settings.
Response: Continue only if you want to overwrite the current settings.

AMQ4139: The default remote administration channel SYSTEM.ADMIN.SVRCONN was created successfully.
Severity: 0: Information
Response: Message for information only.

AMQ4140: The custom CipherSpec is not valid.
Severity: 10: Warning

AMQ4141: The Distinguished Names specification is not valid.
Severity: 10: Warning

AMQ4142: The default remote administration channel SYSTEM.ADMIN.SVRCONN could not be created.
Severity: 10: Warning
Explanation: A problem has occurred when issuing a command to the command server to create the channel.
Response: Try again. If symptoms persist contact your System Administrator.

AMQ4143: The default remote administration channel SYSTEM.ADMIN.SVRCONN could not be created.
Severity: 10: Warning
Explanation: A problem occurred when copying the default administration channel to use as a template for the channel creation.
Response: Try again. If symptoms persist contact your System Administrator.

AMQ4144: The default remote administration channel SYSTEM.ADMIN.SVRCONN could not be deleted.
Severity: 10: Warning
Explanation: A problem has occurred issuing a command to the command server to delete the channel.
Response: Ensure that the channel is not in use and try again. If symptoms persist contact your System Administrator.

AMQ4145: An error occurred connecting to the remote queue manager using the intermediate queue manager. Are you sure that 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 intermediate queue manager is available and that the named remote queue manager is running, and is accessible from the intermediate queue manager. Ensure that you have the authority to connect to the remote queue manager, and ensure that the network is operational. 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.

AMQ4146: Eclipse cannot create or read the workspace for WebSphere MQ Explorer.
Severity: 40: Stop Error
Explanation: To load the WebSphere MQ Explorer, a valid workspace is required.
Response: Ensure that you can write to the Eclipse workspace.

AMQ4147: Eclipse cannot write to the workspace for WebSphere MQ Explorer in <insert_0>.
Severity: 40: Stop Error
Explanation: To load the WebSphere MQ Explorer, write access to the workspace is required.
Response: Ensure that you can write to the Eclipse workspace.

AMQ4148: The object was created successfully.
Severity: 0: Information
Response: Message for information only.

AMQ4149: The request to start the listener was accepted.
Severity: 0: Information
Explanation: A user request to start the listener was accepted by WebSphere MQ.
Response: Message for information only.

AMQ4150: The request to stop the listener was accepted.
Severity: 0: Information
Explanation: A user request to stop the listener was accepted by WebSphere MQ.
Response: Message for information only.

AMQ4151: The request to start the service was accepted.
Severity: 0: Information
Explanation: A user request to start the service was accepted by WebSphere MQ.
Response: Message for information only.

AMQ4152: The request to stop the service was accepted.
Severity: 0: Information
Explanation: A user request to stop the service was accepted by WebSphere MQ.
Response: Message for information only.

AMQ4153: WebSphere MQ cannot stop the listener because it is not running.
Severity: 10: Warning

AMQ4154: WebSphere MQ cannot start the service because no start command has been specified.
Severity: 10: Warning
Response: Ensure that the service has a start command specified.

AMQ4155: WebSphere MQ cannot stop the service because no stop command has been specified.
Severity: 10: Warning
Response: Ensure that the service has a stop command specified.

AMQ4156: WebSphere MQ cannot stop the service because the service is not running.
Severity: 10: Warning

AMQ4157: WebSphere MQ cannot start the service because the services is already running.
Severity: 10: Warning

AMQ4158: WebSphere MQ cannot start the listener because it is already running.
Severity: 10: Warning

AMQ4159: WebSphere MQ cannot start the client connection channel because one or more of the properties are incorrectly specified.
Severity: 10: Warning
Response: Ensure that the client connection has the correct queue manager name and connection name before trying to start.

AMQ4160

WebSphere MQ cannot process the request because the executable specified cannot be started.

Severity

10: Warning

Explanation

The requested was unsuccessful because the program which was defined to be run to complete the action could not be started.

Reasons why the program could not be started are :-

The program does not exist at the specified location.

The WebSphere MQ user does not have sufficient access to execute the program.

If StdOut or StdErr are defined for the program, the WebSphere MQ user does not have sufficient access to the locations specified.

Response

Check the Queue Manager error logs for further details on the cause of the failure, correct the problem and try again.

AMQ4161: The parameter specified is not valid.
Severity: 20: Error
Explanation: The parameter specified when trying to create or alter an object is not valid.
Response: Ensure that valid parameters are specified, then try again.

AMQ4162: The password cannot be cleared.
Severity: 0: Information
Response: Try to clear the password again later.

AMQ4163: The password cannot be changed.
Severity: 10: Warning
Explanation: The attempt to change the password failed because of an error.
Response: Try a different password

AMQ4164: The password was successfully changed.
Severity: 0: Information
Response: Message for information only.

AMQ4165: No password entered in the new password field. No change applied.
Severity: 10: Warning
Explanation: You must enter a new password in both the new and confirm password fields.
Response: Enter a new password in the new password field.

AMQ4166: No password entered in the confirm new password field. No change applied.
Severity: 10: Warning
Explanation: You must enter a new password in both the new and confirm password fields.
Response: Re-enter the new password in the confirm new password field.

AMQ4167: Passwords do not match. No change applied.
Severity: 10: Warning
Explanation: You must enter the same new password in both the new and confirm password fields.
Response: Ensure that the passwords in the new and confirm fields match.

AMQ4168: WebSphere MQ failed to start listening for objects.
Severity: 20: Error
Explanation: No objects will be displayed in the currently selected view.
Response: Check the problem determination information, and ensure that WebSphere MQ and the queue manager in question are both running correctly.

AMQ4169: WebSphere MQ failed to set the object filter.
Severity: 20: Error
Explanation: The WebSphere MQ Explorer cannot listen for objects, so no objects will be displayed in the currently selected view.
Response: Check the problem determination information, and ensure that WebSphere MQ and the queue manager in question are both running correctly.

AMQ4170: The object name specified is not valid.
Severity: 20: Error
Explanation: The object name specified when trying to create or alter an object is not valid.
Response: Ensure that a valid object name is specified, then try again.

AMQ4171: There was an error when communicating with the queue manager.
Severity: 20: Error
Explanation: A request for information from the queue manager failed.
Response: Try the operation again. If the error persists, examine the problem determination information to see if any details have been recorded.

AMQ4172: There was an error when trying to set or retrieve information.
Severity: 20: Error
Explanation: There was an error when trying to set or retrieve information from the queue manager. This might have happened because you specified incorrect or inconsistent attributes when trying create or update an object.
Response: If this error occurred during object creation or modification, ensure that the attributes specified are correct for this type of object. If the error persists, examine the problem determination information to see if any details have been recorded.

AMQ4173

WebSphere MQ cannot clear one or more Trace and FFST files.

Severity

10: Warning

Explanation

WebSphere MQ cannot clear some files, because of one of the following:

The files are currently in use.

WebSphere MQ Explorer does not have the appropriate access permission.

The trace or errors directories contain user-created subdirectories which WebSphere MQ Explorer cannot delete.

Response

Check that tracing is disabled, and that the WebSphere MQ Explorer has appropriate access permission to delete the Trace and FFST files or remove user created subdirectories.

AMQ4174: FFSTs and Trace were cleared successfully.
Severity: 0: Information
Response: Message for information only.

AMQ4175: WebSphere MQ cannot process your request because the value specified is not valid.
Severity: 20: Error
Explanation: Only certain combinations and values are valid for the object your are trying to alter or create.
Response: Specify a valid value and try again.

AMQ4176: WebSphere MQ cannot process your request because the object name specified is not valid.
Severity: 20: Error
Explanation: Only certain combinations and values are valid for the object your are trying to alter or create. You might also see this message if you have specified a QSG disposition that is not valid or an invalid topic object for a subscription.
Response: Check all values are valid for this type of object and try again. If you have altered the disposition of this object, check that the value is correct. If you are creating a new subscription, check the topic object exists.

AMQ4177: The WebSphere MQ Explorer cannot process your request because the connection to WebSphere MQ is quiescing.
Severity: 20: Error
Explanation: The connection to WebSphere MQ is quiescing, so no new information can be queried.
Response: Wait for the connection to end, then try reconnecting.

AMQ4178

WebSphere MQ cannot process your request because there was a disposition conflict detected.

Severity

20: Error

Explanation

A disposition conflict was detected. Ensure that all disposition related fields are correct for this type of object.

Response

Ensure that all disposition related fields are correct for this type of object and try again.

If the error occurred when creating a shared queue check that the Coupling facility structure name on the Storage page has been entered correctly.

If the error occurred while starting a channel that uses a transmission queue with a queue sharing group disposition (QSGDISP) value of SHARED, check that the default channel disposition (DEFCDISP) is set to SHARED or FIXSHARED (and not PRIVATE).

AMQ4179: WebSphere MQ cannot process your request because the string provided was of an incorrect length.
Severity: 20: Error
Explanation: A string value has been modified or supplied that is too long or too short when creating or modifying an object.
Response: Check the values being supplied and try again.
Note: If adding exit names on IBM® i enter exactly 20 characters, the program name occupies the first 10 characters and the library name occupies the second 10 characters, use blanks to pad to the right if necessary.

AMQ4180: WebSphere MQ cannot process your request because there was a parameter conflict.
Severity: 20: Error
Explanation: When creating or modifying an object, the combination of parameters specified is not valid.
Response: Check that the combination specified is valid for the object and try again.

AMQ4181: WebSphere MQ is not responding. Do you want to continue waiting?
Severity: 10: Warning
Explanation: WebSphere MQ does not appear to be responding. This could be because of a heavily loaded remote system, or a slow network connection. However there could have been a system failure. Choosing not to continue could leave the WebSphere MQ Explorer in an unknown state, so you should restart it.
Response: If you choose not to continue waiting, restart the WebSphere MQ Explorer, if the problem persists check for problem determination information.

AMQ4182: No objects were found.
Severity: 10: Warning
Explanation: The query did not find any objects.
Response: If you were expecting objects to be found, check the problem determination information, and ensure that WebSphere MQ and the queue manager in question are both running correctly.

AMQ4183: Query failed because the queue manager is not in a queue-sharing group.
Severity: 10: Warning
Explanation: WebSphere MQ issued a query that required the queue manager to be a member of a queue-sharing group.
Response: Try the operation again, if the problem persists check the problem determination information for more details.

AMQ4184: The channel is not currently active.
Severity: 10: Warning
Explanation: The channel was not stopped because it was not currently active.
Response: If attempting to stop a specific instance of a channel, change the connection name or remote queue manager name and try the operation again.

AMQ4185: WebSphere MQ failed to import your settings.
Severity: 20: Error
Explanation: One or more of the selected preferences has failed to import your settings.
Response: Try again. If the error persists, examine the problem determination information to see if any details have been recorded.

AMQ4186: WebSphere MQ failed to export your settings.
Severity: 20: Error
Response: Try again. If the error persists, examine the problem determination information to see if any details have been recorded.

AMQ4187: WebSphere MQ has successfully imported your settings. (You must restart WebSphere MQ Explorer to apply the imported settings.)
Severity: 0: Information
Response: Restart WebSphere MQ explorer to apply the imported settings

AMQ4188: Are you sure that you want to remove queue manager <insert_0> from cluster <insert_1>?
Severity: 10: Warning
Explanation: A confirmation is required before the queue manager is removed from the cluster.
Response: Continue only if you want to permanently remove the queue manager from the cluster.

AMQ4189: The queue manager could not be suspended from the cluster. The operation failed with error <insert_0>.
Severity: 20: Error
Explanation: The queue manager has not been removed from the cluster.
Response: Try the operation again. If the error persists, examine the problem determination information to see if any information has been recorded.

AMQ4190: An error occurred when clearing the queue manager's REPOS field. The operation failed with error <insert_0>.
Severity: 20: Error
Explanation: The queue manager has only partially been removed from the cluster. The queue manager has been suspended from the cluster. The REPOS field of the queue manager and the CLUSTER fields of the associated cluster channels have not been cleared.
Response: Try the operation again. If the error persists, examine the problem determination information to see if any information has been recorded.

AMQ4191: An error occurred when clearing the CLUSTER field of channel <insert_0>. The operation failed with error <insert_1>.
Severity: 20: Error
Explanation: The queue manager has only partially been removed from the cluster. The queue manager has been suspended from the cluster and the queue manager's REPOS field has been cleared. Some of the CLUSTER fields of other associated cluster channels might also have been cleared.
Response: To completely remove the queue manager, ensure that all the CLUSTER fields of associated cluster channels are cleared.

AMQ4192: The queue manager could not be removed from a cluster because channel <insert_0> is using cluster namelist <insert_1>.
Severity: 10: Warning
Response: Remove the cluster channel from the cluster namelist. Ensure that you do not inadvertently affect the definitions of other objects using the namelist. Then try removing the queue manager again.

AMQ4193: The information supplied could not be correctly converted to the required code page.
Severity: 20: Error
Explanation: All or part of the information entered required conversion to a different code page. One or more characters could not be converted to an equivalent character in the new code page.
Response: Change the characters used, then try the operation again.

AMQ4194: Request failed because the queue manager attempted to use a default transmission queue which is not valid.
Severity: 20: Error
Explanation: An MQOPEN or MQPUT1 call specified a remote queue as the destination. The queue manager used the default transmission queue, as there is no queue defined with the same name as the destination queue manager, but the attempt failed because the default transmission queue is not a valid local queue.
Response: Check that the queue manager's default transmission queue property (DefXmitQName) specifies a valid local queue.

AMQ4195: WebSphere MQ Explorer is now in an unknown state and should be restarted. Do you want to restart WebSphere MQ Explorer?
Severity: 10: Warning
Explanation: You have chosen not to wait for WebSphere MQ to respond to a request. WebSphere MQ Explorer is therefore in an unknown state and should be restarted.
Response: Restart the WebSphere MQ Explorer and try the operation again. If the problem persists check for problem determination information.

AMQ4196: The command or operation is not valid against the type of object or queue specified
Severity: 20: Error
Explanation: You have attempted a command or operation against an object or queue with a type that is not valid for the operation specified. For example, browsing a remote queue; issuing the clear command against a queue with a type that is not QLOCAL; clearing by API calls, a queue who type cannot be opened for input.
Response: Retry the command or operation against an object or queue with a type that is valid for the operation requested.

AMQ4197: An MQOPEN or MQPUT1 call was issued specifying an alias queue as the target, but the BaseObjectName in the alias queue attributes is not recognized as a queue name.
Severity: 20: Error
Explanation: An MQOPEN or MQPUT1 call was issued specifying an alias queue as the target, but the BaseObjectName in the alias queue attributes is not recognized as a queue name. This reason code can also occur when BaseObjectName is the name of a cluster queue that cannot be resolved successfully.
Response: Correct the queue definitions.

AMQ4198

Queue manager <insert_0> has not been removed from one or more clusters.

If you do not remove the queue manager from the clusters, you might get unexpected errors

Do you want to delete the queue manager without removing it from these clusters?

Severity

10: Warning

Explanation

The user has chosen to delete a queue manager that is currently a member of one or more clusters. The queue manager should first be removed cleanly from these clusters before deleting the queue manager. Other queue managers in the cluster might expect the queue manager to be available.

Response

Remove the queue manager from the clusters it is a member of.

AMQ4199: Queue manager <insert_0> is not available for client connection due to an SSL configuration error.
Severity: 30: Severe error
Explanation: The user is trying to connect to a remote queue manager using a secure connection.
Response: Check the SSL configuration of the target queue manager and the local SSL trust store.

AMQ4200: There is a problem with the default configuration. Unable to display the Default Configuration window.
Severity: 20: Error
Explanation: There is a problem with WebSphere MQ.
Response: Use the 'Details>>' button to show further details about the problem and contact your systems administrator.

AMQ4201: Unable to check if the computer exists.
Severity: 20: Error
Explanation: WebSphere MQ was unable to check if the computer name you entered exists on your computer's domain.
Response: Retry the operation, if the problem persists contact your systems administrator.

AMQ4202: Unable to contact the computer <insert_0>.
Severity: 10: Warning
Explanation: WebSphere MQ was unable to locate a computer with this name on your computer's TCP/IP domain.
Response: Enter a different computer name.

AMQ4203: Unable to set up the default configuration.
Severity: 20: Error
Explanation: WebSphere MQ was unable to set up the default configuration. This error may occur if WebSphere MQ is busy with another operation.
Response: Retry the operation. If the problem persists, use the 'Details>>' and 'Print' buttons to record further details about the problem and contact your systems administrator.

AMQ4204: Unable to join the default cluster.
Severity: 20: Error
Explanation: WebSphere MQ was unable to join your computer to the default cluster. This error may occur if WebSphere MQ is busy with another operation.
Response: Retry the operation. If the problem persists, use the 'Details>>' and 'Print' buttons to record further details about the problem and contact your systems administrator.

AMQ4205: Unable to allow remote administration of the queue manager.
Severity: 20: Error
Explanation: WebSphere MQ was unable change the configuration of your queue manager to allow it to be remotely administered. This error may occur if WebSphere MQ is busy with another operation.
Response: Retry the operation. If the problem persists, use the 'Details>>' and 'Print' buttons to record further details about the problem and contact your systems administrator.

AMQ4206: Unable to prevent remote administration of the queue manager.
Severity: 20: Error
Explanation: WebSphere MQ was unable change the configuration of your queue manager to prevent it from being remotely administered. This error may occur if WebSphere MQ is busy with another operation.
Response: Retry the operation. If the problem persists, use the 'Details>>' and 'Print' buttons to record further details about the problem and contact your systems administrator.

AMQ4207: The path specified is not valid.
Severity: 20: Error
Response: Check the path specified and try again.

AMQ4208: Show this panel again the next time the queue manager is started?
Severity: 0: Information
Explanation: You can choose whether you want the same panel to be shown the next time this queue manager is started, and the default configuration is not complete.
Response: Select whether you want the panel to be shown next time.

AMQ4209: The TCP/IP name of the remote computer must not be your own computer name.
Severity: 0: Information
Explanation: You have selected that the repository queue manager is on another computer, but you have entered the name of your own computer.
Response: Enter the correct name of the repository queue manager.

AMQ4210: The command server must be active to complete this operation. Use the WebSphere MQ Services to start it, then retry the operation.
Severity: 10: Warning
Explanation: The operation you requested needs the command server to be running.
Response: Use WebSphere MQ Services to start the command server, then retry the operation.

AMQ4211: The computer name entered must be on your local domain (<insert_0>).
Severity: 10: Warning
Response: Enter the computer name which is on your local domain

AMQ4212: Unable to complete this task because you do not have authority to administer WebSphere MQ.
You must be in the mqm group to administer WebSphere MQ.
Severity: 10: Warning
Explanation: Your userid is not authorized to carry out the operation you requested.
Response: Retry the operation on a userid with the required authority, or contact your systems administrator.

AMQ4213: Unable to delete the queue manager <insert_0> because it is being used by another program.
Close any program using the queue manager, then click 'Retry'.
Severity: 10: Warning
Explanation: WebSphere MQ was unable to delete the old default configuration queue manager because another program is using the queue manager.
Response: Close the programs that are using the queue manager, and click Retry.

AMQ4214: The computer <insert_0> is not known on the network.
Severity: 10: Warning
Explanation: WebSphere MQ is unable to locate a computer with this name on your network.
Response: Enter a different computer name.

AMQ4215: Upgrade of the default configuration was canceled.
Severity: 10: Warning
Explanation: You pressed 'Cancel' while running the default configuration wizard to upgrade the default configuration.
Response: None

AMQ4216: The WebSphere MQ services component does not have the authority it requires.
Severity: 10: Warning

AMQ4217: The MQSeriesServices component does not have the authority to create the default configuration.
Severity: 10: Warning

AMQ4250: No nickname supplied - supply one.
Severity: 10: Warning
Explanation: Requires to enter the user nick name in the text box
Response: Enter the nickname in the text box

AMQ4251: Cannot Initialise WinSock - TCP/IP may not be installed. Install TCP/IP and try again
Severity: 20: Error
Explanation: Postcard was not able to initialize the interface to TCP/IP.
Response: Check that TCP/IP has been installed successfully. If the problem persists, refer to your systems administrator.

AMQ4252: Cannot Find WinSock - TCP/IP may not be installed. Install TCP/IP and try again.
Severity: 20: Error
Explanation: Postcard was not able to find the interface to TCP/IP.
Response: Check that TCP/IP has been installed successfully. If the problem persists, refer to your systems administrator.

AMQ4253: Cannot get fully qualified TCP/IP domain name - Ensure that the TCP/IP protocol is configured.
Severity: 20: Error
Explanation: Postcard was not able to determine the TCP/IP domain name for your computer.
Response: Check that TCP/IP has been installed successfully. If the problem persists, refer to your systems administrator.

AMQ4254: Failed to Allocate System Memory - Contact your system administrator.
Severity: 20: Error
Explanation: Postcard was not able to allocate enough memory to run correctly.
Response: Close other programs to release system memory. If the problem persists, refer to your systems administrator.

AMQ4255: Supply a user name with which you wish to communicate.
Severity: 10: Warning
Explanation: Requires to enter a user nick name in the To text box.
Response: Enter the user nickname in the To text box

AMQ4256: Supply <insert_0>s computer name (this must be a TCP/IP name).
Severity: 10: Warning
Explanation: Requires to enter the mail box computer name on the On field
Response: Enter the mail box computer name or queue manager name on the On text box

AMQ4257: The call MQCONN failed while preparing for a Put operation,
with Completion Code [<insert_0> (<insert_1>)], Reason Code [<insert_2> (<insert_3>)].
Severity: 20: Error
Explanation: An error occurred when Postcard tried to connect to the queue manager in order to send the postcard. This error may occur if WebSphere MQ is busy with another operation.
Response: Try to send the postcard again. If the problem persists contact your systems administrator.

AMQ4258: The call MQOPEN failed while preparing for a Put operation,
with Completion Code [<insert_0> (<insert_1>)], Reason Code [<insert_2> (<insert_3>)].
Severity: 20: Error
Explanation: An error occurred when Postcard tried to open a queue in order to send the postcard. This error may occur if WebSphere MQ is busy with another operation.
Response: Try to send the postcard again. If the problem persists contact your systems administrator.

AMQ4259: The call MQCLOSE failed while preparing for a Put operation,
with Completion Code [<insert_0> (<insert_1>)], Reason Code [<insert_2> (<insert_3>)].
Severity: 20: Error
Explanation: An error occurred when Postcard tried to close the queue after sending the postcard. This error may occur if WebSphere MQ is busy with another operation.
Response: If the problem persists contact your systems administrator.

AMQ4260: The call MQDISC failed while preparing for a Put operation,
with Completion Code [<insert_0> (<insert_1>)], Reason Code [<insert_2> (<insert_3>)].
Severity: 20: Error
Explanation: An error occurred when Postcard tried to disconnect from the queue manager after sending the postcard. This error may occur if WebSphere MQ is busy with another operation.
Response: If the problem persists contact your systems administrator.

AMQ4261: The call MQPUT failed with Completion Code [<insert_0> (<insert_1>)], Reason Code [<insert_2> (<insert_3>)].
Severity: 20: Error
Explanation: An error occurred when Postcard tried to send the postcard by putting its data to the queue. This error may occur if WebSphere MQ is busy with another operation.
Response: Try to send the postcard again. If the problem persists contact your systems administrator.

AMQ4262: The call MQCONN failed while preparing for a Get operation,
with Completion Code [<insert_0> (<insert_1>)], Reason Code [<insert_2> (<insert_3>)].
Severity: 20: Error
Explanation: An error occurred when Postcard tried to connect to the queue manager in order to receive postcards. This error may occur if WebSphere MQ is busy with another operation.
Response: Restart Postcard. If the problem persists contact your systems administrator.

AMQ4263: The call MQOPEN failed while preparing for a Get operation,
with Completion Code [<insert_0> (<insert_1>)], Reason Code [<insert_2> (<insert_3>)].
Severity: 20: Error
Explanation: An error occurred when Postcard tried to open a queue in order to send the postcard. This error may occur if WebSphere MQ is busy with another operation.
Response: Restart Postcard. If the problem persists contact your systems administrator.

AMQ4264: The call MQCLOSE failed while preparing for a Get operation,
with Completion Code [<insert_0> (<insert_1>)], Reason Code [<insert_2> (<insert_3>)].
Severity: 20: Error
Explanation: An error occurred when Postcard tried to close the queue after receiving postcards. This error may occur if WebSphere MQ is busy with another operation.
Response: If the problem persists contact your systems administrator.

AMQ4265: The call MQDISC failed while preparing for a Get operation,
with Completion Code [<insert_0> (<insert_1>)], Reason Code [<insert_2> (<insert_3>)].
Severity: 20: Error
Explanation: An error occurred when Postcard tried to disconnect from the queue manager after receiving postcards. This error may occur if WebSphere MQ is busy with another operation.
Response: If the problem persists contact your systems administrator.

AMQ4266: Enter the message that you want to send to <insert_0>.
Severity: 10: Warning
Response: Enter the message in the Message text field.

AMQ4267: The call MQGET failed with Completion Code [<insert_0> (<insert_1>)], Reason Code [<insert_2> (<insert_3>)].
Severity: 20: Error
Explanation: An error occurred when Postcard tried to receive postcards by getting its data from the queue. This error may occur if WebSphere MQ is busy with another operation.
Response: Restart Postcard. If the problem persists contact your systems administrator.

AMQ4268: Postcard is unable to contact the queue manager on the remote computer.
Verify that the default configuration is running on the remote computer.
Severity: 20: Error
Explanation: The mail box queue manager in the On text box not reachable.
Response: Verify that the default configuration is running on the remote computer.

AMQ4269: Unable to run Postcard because you do not have authority to use WebSphere MQ.
You must be in the mqm group to use WebSphere MQ.
Severity: 20: Error
Explanation: The mail box queue manager in the On text box not reachable.
Response: Use Postcard on a user Id with the required authority, or contact your systems administrator.

AMQ4270: Postcard is unable to send messages to the remote computer. Postcard can only exchange messages with computers that are on the same TCP/IP domain as this computer.
Severity: 20: Error
Explanation: Unable to send messages to the remote computer
Response: Use default configuration application to add the remote computer to the same cluster.

AMQ4271: Unable to open a local queue called <insert_0> on the mailbox queue manager <insert_1>.
Use WebSphere MQ Explorer to create the queue, then restart Postcard.
Severity: 20: Error
Explanation: Postcard was unable to automatically create the queue it uses on the queue manager.
Response: Use WebSphere MQ Explorer to create the queue, and restart Postcard.

AMQ4272: The mailbox queue manager <insert_0> does not exist on this computer.
Severity: 20: Error
Explanation: The mailbox queue manager name specified after the '-m' parameter to Postcard does not exist on this computer.
Response: Restart Postcard specifying the name of a queue manager that does exist on this computer.

AMQ4273: Unable to contact the target mailbox <insert_0>.
Severity: 10: Warning
Explanation: Postcard was unable send the message as it could not contact the target mailbox.
Response: Click 'Retry' to attempt to send the message again, otherwise click 'Cancel'.

AMQ4274: Postcard has detected that <insert_0> is the name of a computer and a queue manager.
Severity: 10: Warning
Explanation: Postcard has detected that the destination mailbox name is the name of a computer and of a queue manager.
Response: Select whether you want to send the message to the computer or the queue manager with this name, then click OK.

AMQ4300: Supply some text in order for the MQPUT(1) operation to succeed.
Explanation: No text has been supplied for the user so that the MQPUT or MQPUT1 operation can proceed.
Response: Supply some text in the editable area so that the MQPUT or MQPUT1 operation can proceed.

AMQ4301: Supply some text in order for the MQPUT operation to succeed.
Explanation: No text has been supplied for the user so that the MQPUT operation may proceed.
Response: Supply some text in the editable area so that the MQPUT may proceed.

AMQ4302: Supply some text in order for the MQPUT1 operation to succeed.
Explanation: No text has been supplied for the user so that the MQPUT1 operation may proceed.
Response: Supply some text in the editable area so that the MQPUT1 may proceed.

AMQ4303: The command server for the queue manager [%s] is not started. Start the command server and try again.
Explanation: In order for the API Exerciser to function, a command server must be running.
Response: Either start the command server from the MQServices application or run strmqcsv <Queue Manager> from the command line.

AMQ4304: API Exerciser cannot enumerate objects for queue manager [%s].
Explanation: The API Exerciser encountered a problem trying to enumerate queues.
Response: Ensure that the command server is running (from the Service application) and that there are queues configured for the queue manager.

AMQ4305: There are no queue managers present in the system. Create one and try again.
Explanation: The API Exerciser could not find any queue managers on the system.
Response: Use the Services application to create one or run crtmqm <Queue Manager>.

AMQ4306: Memory allocation failure. Stop some other applications and try again.
Explanation: There are not sufficient system resources available in the system to satisfy the running of API Exerciser.
Response: Shut some other applications down and try running the API Exerciser again.

AMQ4307: API Exerciser encountered a COM failure and cannot continue. Ensure that WebSphere MQ has been correctly installed and configured and that your user id. is a member of the mqm group.
Explanation: When the API Exerciser started, it was unable to make a COM connection to WebSphere MQ Services.
Response: Ensure that WebSphere MQ has been correctly installed and configured, and that your user ID is a member of the mqm group. If the problem persists, refer to your systems administrator.

AMQ4308: API Exerciser cannot continue. Ensure that the userid you are using is a member of the mqm group.
Explanation: None.
Response: None.

AMQ4309: API Exerciser cannot continue. Ensure that the userid you are using is a member of the Administrator group.
Explanation: None.
Response: None.

AMQ4350: Setup cannot continue; a later version of this product is installed.
Explanation: Installation detected that a version of this product later than version 5.3 is already installed on the computer.
Response: Do not attempt to install version 5.3 when a later version is already installed.

AMQ4351: Uninstallation cannot continue; uninstallation is already running.
Explanation: An attempt was made to run two copies of uninstallation at once.
Response: Run only one copy of uninstallation at a time.

AMQ4352: Setup cannot continue; a supported version of Windows is required.
Explanation: None.
Response: None.

AMQ4353: Setup cannot continue; '%s' is not an Administrator.
Explanation: The user running installation does not have administrator authority.
Response: Log off and log back on using a user ID with administrator authority.

AMQ4354: No repository computer name entered.
Explanation: None.
Response: None.

AMQ4355: Repository computer name is not valid.
Explanation: None.
Response: None.

AMQ4356: Enter a remote computer name.
Explanation: None.
Response: None.

AMQ4357: Registration failed for file '%s' (code 0x%8.8lx).
Explanation: None.
Response: None.

AMQ4358: Unregistration failed for file '%s' (code 0x%8.8lx).
Explanation: None.
Response: None.

AMQ4359: Unable to register file '%s'.
Explanation: None.
Response: None.

AMQ4360: Unable to unregister file '%s'.
Explanation: None.
Response: None.

AMQ4361: Uninstall cannot continue; Administrator logon required.
Explanation: None.
Response: None.

AMQ4362: Failed to create the default configuration.
Explanation: None.
Response: None.

AMQ4363: Setup could not detect the Windows NT Service Pack level (Service Pack 3 or later is required). Is Service Pack 3 or later installed?
Explanation: None.
Response: None.

AMQ4364: Setup could not detect the Windows NT Service Pack level (Service Pack 6a or later is required). Is Service Pack 6a or later installed?
Explanation: None.
Response: None.

AMQ4365: Setup cannot continue because Service Pack 3 is not installed.
Explanation: None.
Response: None.

AMQ4366: Setup cannot continue because Service Pack 6a or later is not installed.
Explanation: None.
Response: None.

AMQ4367: Setup cannot continue because Internet Explorer Version 4.01 SP1 is not installed.
Explanation: None.
Response: None.

AMQ4368: Select at least one component to proceed.
Explanation: None.
Response: None.

AMQ4369: The 'Web Administration Server' component requires the 'Server' component.
Explanation
Response

AMQ4370: Uninstallation of the 'Server' component requires uninstallation of the 'Web Administration Server' component.
Explanation: None.
Response: None.

AMQ4371: The 'Documentation in Other Languages' component requires the 'Documentation in English' component.
Explanation: None.
Response: None.

AMQ4372: Uninstallation of the 'Documentation in English' component requires uninstallation of the 'Documentation in Other Languages' component.
Explanation: None.
Response: None.

AMQ4373: There is not enough space on drive %s (program files) to install these components. Free up some disk space or modify your selections
Explanation: None.
Response: None.

AMQ4374: There is not enough space on drive %s (data files) to install these components. Free up some disk space or modify your selections
Explanation: None.
Response: None.

AMQ4375: The program files top-level folder is not valid.
Explanation: The program files top-level folder is not a valid path.
Response: Enter a valid path.

AMQ4376: The data files top-level folder is not valid.
Explanation: The data files top-level folder is not a valid path.
Response: Enter a valid path.

AMQ4377: The log files folder is not valid.
Explanation: The log files folder name is not a valid path.
Response: Enter a valid path.

AMQ4378: A root folder is not allowed for the program files top-level folder.
Explanation: WebSphere MQ cannot be installed in a root folder, for example 'C:\'.
Response: Enter a non-root folder.

AMQ4379: A root folder is not allowed for the data files top-level folder.
Explanation: WebSphere MQ cannot be installed in a root folder, for example 'C:\'.
Response: Enter a non-root folder.

AMQ4380: A root folder is not allowed for the log files folder.
Explanation: WebSphere MQ cannot be installed in a root folder, for example 'C:\'.
Response: Enter a non-root folder.

AMQ4381: here is not enough space on drive %s (log files) to install these components. Free up some disk space or modify your selections
Explanation: None.
Response: None.

AMQ4382: Unable to create or replace folder '%s'
Explanation: None.
Response: None.

AMQ4385: Unknown language specified ('%s')
Explanation: None.
Response: None.

AMQ4386: Codepage (%d) for specified language not available.
Explanation: None.
Response: None.

AMQ4387: Before Setup can display help, this computer's help system needs upgrading to HTML Help 1.3. Would you like to upgrade now? (You might need to restart the computer.)
Explanation: None.
Response: None.

AMQ4388: WebSphere MQ Setup or uninstallation is already running.
Explanation: None.
Response: None.

AMQ4389: Setup could not create a local 'mqm' group (code %d).
Explanation: An error occurred creating a local user group called 'mqm'.
Response: Review the installation log file for details of any problems. If the error persists, contact your systems administrator.

AMQ4390: Setup could not create a global 'Domain mqm' group (code %d).
Explanation: An error occurred creating a local user group called 'mqm'.
Response: Review the installation log file for details of any problems. If the error persists, contact your systems administrator.

AMQ4391: Setup could not find the global 'Domain mqm' group.
Explanation: The global 'mqm ' group was created, but could not then be found.
Response: Review the installation log file for details of any problems. If the error persists, contact your systems administrator.

AMQ4392: Setup could not add the global 'Domain mqm' group to the local 'mqm' group (code %d).
Explanation: An error occurred adding the global 'mqm' group to the local 'mqm' group.
Response: Review the installation log file for details of any problems. If the error persists, contact your systems administrator.

AMQ4393: No ports were specified; no listeners will be created.
Explanation: None.
Response: None

AMQ4394: No queue managers are selected for remote administration.
Explanation: None.
Response: None.

AMQ4395: One or more 'Server' component prerequisites were not selected; the component cannot be installed.
Explanation: None.
Response: None.

AMQ4396: One or more prerequisite upgrades were not selected; WebSphere MQ will not operate correctly.
Explanation: None.
Response: None.

AMQ4397: Cannot install on a network drive (drive %s).
Explanation: None.
Response: None.

AMQ4400: Explorer cannot administer the queue manager because the queue <insert_0> is not defined.
Severity: 10: Warning
Explanation: Explorer uses the queue <insert_0> to administer queue managers.
Response: Define the queue <insert_0> and retry.

AMQ4401: Explorer cannot administer the queue manager because the user is not authorised to open the queue <insert_0>.
Severity: 10: Warning
Explanation: Explorer uses the queue <insert_0> to administer this queue manager.
Response: Allow Explorer to open the queue <insert_0> and retry.

AMQ4402: The queue <insert_0> could not be opened for reason <insert_1>.
Severity: 10: Warning
Explanation: Explorer uses the queue <insert_0> to administer this queue manager.
Response: Allow Explorer to open the queue <insert_0> and retry.

AMQ4403: The queue manager you are connecting to is at a higher command level than the intermediate queue manager you are using, which will cause some operations not to work. Are you sure that you want to show the destination queue manager in the folder anyway?
Severity: 10: Warning
Explanation: You are making a connection to a remote queue manager which is at a command level higher than the intermediate queue manager you are trying to use. This means that errors will occur when selecting new items such as Application Connections or queue status.
Response: Select Yes if you want to continue to use the remote queue manager with this intermediate queue manager, even though the command levels are inconsistent. Select No to chose a different intermediate queue manager.

AMQ4404: The queue manager <insert_0> is the only full repository in cluster <insert_1> and there are still partial repository queue managers defined. Removing this queue manager from the cluster prevents further repository actions from being run. Are you sure that you want to remove this queue manager?
Severity: 10: Warning
Explanation: To be able to display cluster information, the clustering component of the WebSphere MQ Explorer requires at least one full repository to be selected as the source. Removing the last full repository will prevent the display of cluster members, and hence will prevent cluster actions being run on these full repositories.
Response: Select Yes if you want to remove the full repository even though it will prevent access to remaining partial repository information.

AMQ4405

An unexpected error occurred connecting to the JNDI service provider.

The following message contains text from the JNDI service provider which might not be translated.

Error <insert_0> performing JNDI operation <insert_1> on object name <insert_2>.

Severity

30: Severe error

Explanation

An unexpected JNDI error prevented the operation from completing.

Response

Check for FFSTs to determine the reason for the error. If symptoms persist, contact your Systems Administrator.

AMQ4406: The connection could not be made to the JNDI service provider because the specified security credentials (distinguished name and password) are not valid for this service provider.
Severity: 20: Error
Explanation: Either the distinguished name or password is not valid for the service provider
Response: Correct the security credentials and try again.

AMQ4407: The Provider URL was not supplied.
Severity: 20: Error
Explanation: The Provider URL must be supplied when opening an Initial Context.
Response: Supply the Provider URL.

AMQ4408: The NAME was missing from the JMS Administration data file.
Severity: 20: Error
Response: Check for FFSTs to determine the reason for the error.

AMQ4409: A context with the nickname <insert_0> already exists.
Severity: 20: Error
Explanation: Nicknames for each context in the tree must be unique.
Response: Choose a different nickname for this context.

AMQ4410: Object type <insert_0> is not recognised when retrieving details for attribute <insert_1>.
Severity: 20: Error
Explanation: The object ID is not valid.
Response: Ensure that only supported object types are used.

AMQ4411: Object type <insert_0> is not recognised when loading objects from context <insert_1>.
Severity: 20: Error
Explanation: The object class is not valid.
Response: Ensure that only supported object types are used.

AMQ4412: Unexpected Exception: <insert_0> message <insert_1>.
Severity: 20: Error
Explanation: An unexpected error occurred.
Response: Check for FFSTs to determine the reason for the error.

AMQ4413: The context <insert_0> could not be removed, because it was not empty.
Severity: 20: Error
Explanation: A context can only be removed if it is empty.
Response: Remove the contents of the context and try again.

AMQ4414

An unexpected error occurred when connecting to the JNDI service provider.

The following message contains text from the JNDI service provider which might not be translated.

Error <insert_0> because of <insert_3> performing JNDI operation <insert_1> on object name <insert_2>.

Severity

30: Severe error

Explanation

An unexpected JNDI error prevented the operation from completing.

Response

Check for FFSTs to determine the reason for the error. If symptoms persist contact your Systems Administrator.

AMQ4415: The object could not be created because an object with the name <insert_0> already exists.
Severity: 20: Error
Explanation: An object with the same name already exists in JNDI. Note that the existing object might be of a different type to the one being created as Connection Factories, Destinations and other JNDI objects all share the same namespace within a particular JNDI context. To locate the existing object, select the JMS context tree node to display all objects within that JNDI location.
Response: Choose a different name for the new object, or delete the existing object.

AMQ4416

The object <insert_0> could not be created because you do not have authority to create objects, or there is no connection to the context.

Severity

20: Error

Explanation

If the JNDI service provider is LDAP then the connection might not have a sufficient level of security to create objects.

If the JNDI service provider is a file system then the bindings file might be read-only,

or there is no connection to the context.

Response

Connect to the JNDI service provider with the correct level of security, or ensure the permissions on the bindings file are correct and try again.

AMQ4417: The Local address could not be set to the value <insert_0>.
Severity: 20: Error
Explanation: The Local address must be a valid address in the form ip_address(port-number), where the port number can be a specific port, a range of ports (low-port,high-port), or can be omitted. A host name can be specified instead of an IP address.
Response: Correct the Local address and try again.

AMQ4418: The SSL Peer name could not be set to the value <insert_0>.
Severity: 20: Error
Explanation: SSL Peer name must be a valid Distinguished Name.
Response: Enter a valid SSL Peer name.

AMQ4419: The JNDI context was opened out of order.
Severity: 20: Error
Explanation: A context which is already open cannot be opened again.
Response: Check for FFSTs to determine the reason for the error.

AMQ4420: The JNDI context was closed out of order.
Severity: 20: Error
Explanation: A context which is already closed cannot be closed again.
Response: Check for FFSTs to determine the reason for the error.

AMQ4421: The connection could not be made to the JNDI service provider. This could be either because the physical connection has been broken, or the distinguished name in the provider URL or the distinguished name provided for the security credentials is not valid.
Severity: 20: Error
Explanation: The name provided must be a properly formed distinguished name, valid on the specified JNDI service provider.
Response: Correct the distinguished name and try again.

AMQ4422: There is a communication error connecting to the JNDI service provider with the provider URL <insert_0>.
Severity: 20: Error
Explanation: The connection to the JNDI service provider has timed out.
Response: Check the connection information and ensure that the service provider is running at the remote end and try again.

AMQ4423: The object <insert_0> could not be deleted because you do not have authority to delete objects.
Severity: 20: Error
Explanation: If the JNDI service provider is LDAP then the connection might not have a sufficient level of security to delete objects.
If the JNDI Service provider is a file system then the bindings file might be read-only.
Response: Connected to the JNDI service provider with the correct level of security or ensure the permissions on the bindings file are correct and try again.

AMQ4424: The requested level of security is not supported by the JNDI service provider.
Severity: 20: Error
Explanation: The level of security requested (none, simple or CRAM_MD5) is not supported by the JNDI service provider being used.
Response: Either change the level of security requested or the JNDI service provider and try again.

AMQ4425

It is not clear to which queue manager the value of the <insert_0> field on the <insert_1> page refers.

* Ensure that the queue manager is in WebSphere MQ Explorer.

* Ensure that the queue manager is running.

* Ensure that WebSphere MQ Explorer is connected to the queue manager.

* Ensure you have authority to list queues on the queue manager

* If there are two queue managers with the same name in WebSphere MQ Explorer, use the <insert_0> Select button to specify the queue manager again.

Severity

20: Error

Explanation

WebSphere MQ Explorer needs to know exactly which queue manager to query to populate the object selection dialog.

Response

If the queue manager name is ambiguous, use the selection button to choose a running queue manager, before selecting the object.

AMQ4426: The location <insert_0> cannot be resolved.
Severity: 20: Error
Explanation: The specified location could not be found because it is not bound.
Response: Ensure that the details for the JNDI context are correct and the context itself is accessible. Try again.

AMQ4427: The JNDI service provider cannot be found
Severity: 20: Error
Explanation: A JNDI service provider has been entered that is not valid, or it cannot be found in the CLASSPATH.
Response: Correctly specify the JNDI service provider and try again.

AMQ4428: There is an error connecting to the JNDI service provider with the provider URL <insert_0>.
The host name or IP address is not correct.
Severity: 20: Error
Explanation: The connection to the JNDI service provider has timed out due to an incorrect host name or IP address.
Response: Correct the host name or IP address and try again.

AMQ4429: There is an error connecting to the JNDI service provider with the provider URL <insert_0>.
The host name or port number is not correct or the remote server is not running.
Severity: 20: Error
Explanation: The connection to the JNDI service provider has timed out due an incorrect host name or port number, or the remote server is not running.
Response: Check the host name and port number and ensure that the remote service provider is running.

AMQ4430: There is an error connecting to the JNDI service provider with the provider URL <insert_0>.
The Local area network (LAN) is not available.
Severity: 20: Error
Explanation: The connection to the JNDI service provider has timed out due to the LAN not being available.
Response: Ensure the LAN is available and try again.

AMQ4431: The object <insert_0> could not be updated as you do not have authority to update objects.
Severity: 20: Error
Explanation: If the JNDI service provider is LDAP, then the connection might not have a sufficient level of security to update objects.
If the JNDI Service provider is a file system, then the bindings file might be read-only.
Response: Connected to the JNDI service provider with the correct level of security, or ensure the permissions on the bindings file are correct and try again.

AMQ4432: There is a communication error with the JNDI service provider.
Severity: 20: Error
Explanation: The connection to the JNDI service provider has timed out.
Response: Ensure that the LAN is available and that the remote service provider is running, then try again.

AMQ4433: The object <insert_0> could not be renamed because you do not have authority to rename objects.
Severity: 20: Error
Explanation: If the JNDI service provider is LDAP, then the connection might not have a sufficient level of security to rename objects.
If the JNDI Service provider is a file system then the bindings file might be read-only.
Response: Connect to the JNDI service provider with the correct level of security, or ensure the permissions on the bindings file are correct and try again.

AMQ4434: The object <insert_0> could not be renamed to <insert_1> because the name already exists.
Severity: 20: Error
Explanation: Names within the JNDI namespace must be unique.
Response: Choose another name and try again.

AMQ4435: The field <insert_0> must start with the prefix <insert_1>
Severity: 20: Error
Explanation: The name entered must start with the particular prefix.
Response: Correct the name and try again.

AMQ4436: The <insert_0> on the <insert_1> page cannot be <insert_2> when the <insert_3> on the <insert_4> page is <insert_5>.
Severity: 20: Error
Explanation: The attributes are inconsistent.
Response: Change one or both of the attributes to make them consistent.

AMQ4437: Unknown event; type <insert_0>.
Severity: 20: Error
Explanation: The JMS Administration plug-in encountered an unexpected event.
Response: Check for FFSTs to determine the reason for the error.

AMQ4438: The value <insert_3> from the parameter <insert_0> <insert_1> of class <insert_2> cannot be converted into a URL.
Severity: 20: Error
Explanation: The JMS Administration plug-in encountered an unexpected URL string.
Response: Check for FFSTs to determine the reason for the error.

AMQ4439: The last non-blank character of <insert_0> must be an asterisk.
Severity: 20: Error
Explanation: The name entered must end with an asterisk.
Response: Correct the name and try again.

AMQ4440: The following error was encountered when setting the field <insert_0>.
<insert_1>
Severity: 20: Error
Explanation: A JMS exception was generated when setting the SSL CRL
Response: Check that all the URLs in the SSL CRL field are in the format "ldap://host".

AMQ4441: The type of the object underlying the JMS Parameter <insert_0> <insert_1> is unexpected: <insert_2>.
Severity: 20: Error
Explanation: The JMS Administration plug-in encountered an unexpected object type.
Response: Check for FFSTs to determine the reason for the error.

AMQ4442: Unexpected JMS Exception: pcfid: <insert_0> <insert_1>, object type: <insert_2>, JMS error <insert_3> <insert_4>.
Severity: 20: Error
Explanation: The JMS Administration plug-in encountered an unexpected JMS error.
Response: Check for FFSTs to determine the reason for the error.

AMQ4443: One or more JNDI errors prevented objects being retrieved from the namespace. The last of these errors was <insert_0> for the object <insert_1>.
Severity: 30: Severe error
Explanation: An unexpected JNDI error prevented the operation from completing. The objects might have been damaged and cannot be retrieved from the namespace. Damaged objects are shown in WebSphere MQ Explorer
Response: Either delete the object (using the Explorer), or repair it using some other tool.

AMQ4444

One or more JNDI errors prevented objects being looked up from the namespace. The last of these errors was <insert_0> for the object <insert_1>.

The JNDI service provider returned the following message text:

<insert_2>.

Severity

30: Severe error

Explanation

An unexpected JNDI error prevented the operation from completing. The objects might have been damaged and cannot be retrieved from the namespace. Damaged objects are shown in WebSphere MQ Explorer

Response

Either delete the object (using the Explorer), or repair it using some other tool.

AMQ4445: The following error, reported by JNDI, prevented the transport being changed for the object: <insert_1>.
<insert_0>.
Severity: 30: Severe error
Explanation: The objects might have properties which prevent the transport being changed.
Response: Before trying to change the transport, change any conflicting properties.

AMQ4446: You are about to remove the Initial context <insert_0> (<insert_1>) from WebSphere MQ Explorer. Are you sure that you want to continue?
Severity: 0: Information
Explanation: If you remove this Initial context, it will no longer be displayed in WebSphere MQ Explorer. The context itself and its contents, will not be deleted.
Response: Continue only if you want to remove the context from WebSphere MQ Explorer.

AMQ4447: Are you sure that you want to delete the JMS object <insert_0> (<insert_1>)?
Severity: 0: Information
Explanation: The JMS object will be permanently removed from the JMS Context.
Response: Continue only if you want to permanently delete the object.

AMQ4448: The <insert_0> on the <insert_1> page cannot be specified when the <insert_2> on the <insert_3> page has not been specified.
Severity: 20: Error
Explanation: The attributes are inconsistent.
Response: Change one or both of the attributes to make them consistent.

AMQ4449: The factory class location <insert_0> is not valid.
Severity: 20: Error
Explanation: The factory class location must be in a URL format.
Response: Remove the Initial context from WebSphere MQ Explorer and add it again.

AMQ4450

This operation is not supported. The following message contains text from the JNDI service provider which might not be translated:

<insert_0>

Use this message to help you diagnose the problem.

Severity

20: Error

Explanation

The JNDI provider does not support the operation performed. One common problem is trying to connect without a password.

Response

Determine and solve the problem from the JNDI error message and try again.

AMQ4451: The <insert_0> property on the JMS object <insert_1> is set to <insert_2> but WebSphere MQ Explorer is not connected to a queue manager with that name.
Severity: 20: Error
Explanation: To create the appropriate object on the queue manager, WebSphere MQ Explorer must be connected to it.
Response: Add the required queue manager to WebSphere MQ Explorer and ensure that it is connected before attempting this operation again.

AMQ4452: The coupling-facility structure name specified in the queue definition for this queue is not defined in the CFRM data set, or is not the name of a list structure.
Severity: 20: Error
Explanation: An MQOPEN or MQPUT1 call was issued to access a shared queue, but the call failed because the coupling-facility structure name specified in the queue definition is not defined in the CFRM data set, or is not the name of a list structure.
Response: Modify the queue definition to specify the name of a coupling-facility list structure that is defined in the CFRM data set.

AMQ4453: The storage class defined for this queue does not exist.
Severity: 20: Error
Explanation: The MQPUT or MQPUT1 call was issued, but the storage-class object defined for the queue does not exist.
Response: Create the storage class object required by the queue, or modify the queue definition to use an existing storage class. The name of the storage class object used by the queue is specified by the StorageClass queue attribute.

AMQ4454: There is an error associated with this channel.
Severity: 20: Error
Explanation: A possible error cause is that the channel references a host name that cannot be resolved.
Response: Ensure that all of the properties for the channel have been defined correctly. Ensure that the channel references a host name that can be resolved.

AMQ4455: The Distinguished Name specified is not valid.
Severity: 20: Error
Response: Ensure that a valid Distinguished Name is specified.

AMQ4456: The Db2 subsystem is currently not available.
Severity: 20: Error
Explanation: An MQOPEN, MQPUT1, or MQSET call was issued to access a shared queue, but the call failed because the queue manager is not connected to a Db2 subsystem. As a result, the queue manager is unable to access the object definition relating to the shared queue. A possible cause for this error is that the Db2 subsystem is being restarted.
Response: Configure the Db2 subsystem so that the queue manager can connect to it. Ensure that the Db2 subsystem is available and running.

AMQ4457: The value <insert_0> from attribute <insert_1> on JMS object <insert_2> is not a valid name for an MQ object.
Severity: 20: Error
Explanation: The value of the specified attribute either contains invalid characters or is an invalid length for an MQ object name.
Response: Modify the attribute value by removing any invalid characters or reducing the length.

AMQ4458: The property <insert_0> on JMS object <insert_1> could not be retrieved or updated.
Severity: 20: Error
Explanation: An error occurred while requesting or updating the value of a property on a JMS object.
Response: Check for FFST information to determine the reason for the error. If symptoms persist, contact your Systems Administrator.

AMQ4459: The <insert_0> property on the JMS object <insert_1> is set to <insert_2> but no known queue managers of that name support the creation of administrative topic objects.
Severity: 20: Error
Explanation: To create the appropriate object on the queue manager, it must support the creation of administrative topic objects.
Response: Either add a queue manager of the appropriate name and that supports the creation of administrative topics to WebSphere MQ Explorer, or modify the JMS object property. Try the operation again.

AMQ4460: The default remote administration listener LISTENER.TCP was created successfully.
Severity: 0: Information
Response: Message for information only.

AMQ4461: The default remote administration listener LISTENER.TCP could not be created.
Severity: 10: Warning
Explanation: A problem occurred when issuing a command to the command server to create the listener.
Response: Check that the command server is running on the queue manager and try again. If symptoms persist contact your System Administrator.

AMQ4462: Successfully added queue manager <insert_0>.
Severity: 0: Information
Explanation: The requested queue manager was successfully added to the list of known queue managers in the WebSphere MQ Explorer.
Response: Message for information only.

AMQ4463: The <insert_0> attribute on JMS object <insert_1> is set to <insert_2> but this is not a valid name for an MQ Queue Manager.
Severity: 20: Error
Explanation: The attribute must only contain valid characters and be of the appropriate length for an MQ Queue Manager name.
Response: Modify the attribute to the name of a real MQ Queue Manager.

AMQ4464: An error occurred while trying to connect to the queue manager. WebSphere MQ Explorer could not determine the name of the queue manager so it cannot be added.
Severity: 20: Error
Explanation: Queue manager names must be determined before adding them to the WebSphere MQ Explorer. Where an asterisk (*) is used to connect, the Queue Manager must be available so that the queue manager name can be determined.
Response: Ensure the required queue manager is available before attempting this operation again, or make the queue manager name explicit rather than using an asterisk (*).

AMQ4465: New attributes have been added to WebSphere MQ Explorer objects. Your existing user-defined schemes have not been updated. If you want your user-defined schemes to contain these new attributes, you must manually add the new attributes.
Severity: 0: Information
Response: Message for information only.

AMQ4466: Successfully connected to the queue manager <insert_0>. As the required queue manager name <insert_1> starts with an asterisk (*), there might be multiple queue managers that could result from the same connection. Are you sure that you want to add this queue manager?
Severity: 0: Information
Explanation: The queue manager name used to connect starts with an asterisk (*). This means that the same connection details could be used to connect to multiple queue managers.
Response: Add the queue manager specified if it is the one you required.

AMQ4467: The filter has not been removed because it is still required by other plug-ins.
Severity: 10: Warning
Explanation: Other plug-ins have responded to the attempted removal of this filter by indicating that they are still using it.
Response: Ensure that the other plug-ins have finished using the filter before trying to delete it again.

AMQ4468: The filter named <insert_0> is used by the following automatic sets:<insert_1> Are you sure that you want to delete this filter?
Severity: 10: Warning
Explanation: A confirmation is required before the specified filter is deleted. The name is provided in the message.
Response: Continue only if you want to permanently delete the filter.

AMQ4469: The automatic set <insert_0> no longer has any filters to decide its membership.
Severity: 10: Warning
Explanation: The only filter that this set was using has been deleted. An automatic set needs at least one filter to determine which objects should be members of the set.
Response: Press OK to edit this set and in the Edit Set dialog, select one or more filters to use with this set.

AMQ4470: The Provider Version is not in the correct form.
Severity: 20: Error
Explanation: The Provider Version consists of up to 4 groups of digits separated with periods (.)but not ending with one, 63, 1.2 or 1.2.34.56 for example. Alternatively you can enter the word 'unspecified'.
Response: Correct the provider version and try again.

AMQ4471: Are you sure that you want to delete the set named <insert_0>?
Note that deleting a set does not delete its members.
Severity: 10: Warning
Explanation: A confirmation is required before the specified set is deleted.
Response: Continue only if you want to permanently delete the set.

AMQ4472

The WMQ_Schemes.xml file used to save schemes is incomplete.

A backup copy of this file has been made:

<insert_0>.

Where possible, user-defined schemes from this file have been extracted and retained,

but it is possible that some have been lost.

Severity

10: Warning

Explanation

When reading in schemes from the WMQ_Schemes.xml file, some required information was missing.

Response

Re-create user-defined schemes where necessary. Refer to the backup copy of the schemes file that was created to identify what has been changed.

AMQ4473

The WMQ_Schemes.xml file used to save schemes was found to be in an invalid format.

A backup copy of this file was made:

<insert_0>.

All user-defined schemes must be re-created.

Severity

10: Warning

Explanation

WebSphere MQ Explorer was unable to process the WMQ_Schemes.xml file as it had an invalid format. It was possibly truncated.

Response

Re-create all user-defined schemes. If possible, refer to the backup copy of the schemes file to obtain information.

AMQ4474: The WMQ_Filters.xml file used to save filters is incomplete. A backup copy of this file has been made: <insert_0>. Where possible, user-defined filters from this file have been extracted and retained, but it is possible that some have been lost.
Severity: 10: Warning
Explanation: When reading in filters from the WMQ_Filters.xml file, some required information was missing.
Response: Re-create user-defined filters where necessary. Refer to the backup copy of the filters file that was created to identify what has been changed.

AMQ4475: The WMQ_Filters.xml file used to save filters was found to be in an invalid format. A backup copy of this file was made: <insert_0>. All user-defined filters must be re-created.
Severity: 10: Warning
Explanation: WebSphere MQ Explorer was unable to process the WMQ_Filters.xml file as it had an invalid format. It was possibly truncated.
Response: Re-create all user-defined filters. If possible, refer to the backup copy of the filters file to obtain information.

AMQ4476: The WMQ_Sets.xml file used to save sets was found to be in an invalid format. A backup copy of this file was made: <insert_0>. All sets must be re-created.
Severity: 10: Warning
Explanation: WebSphere MQ Explorer was unable to process the WMQ_Sets.xml file as it had an invalid format. It was possibly truncated.
Response: Re-create all sets as necessary. If possible, refer to the backup copy of the sets file that was created to obtain information.

AMQ4477: The topic string supplied is invalid.
Severity: 10: Warning
Explanation: A topic string was missing or contained invalid characters.
Response: Ensure a topic string has been defined or that there are no invalid characters in the topic string.

AMQ4478: The publication could not be retained.
Severity: 10: Warning
Explanation: An attempt was made to publish a message on a topic, using the MQPMO_RETAIN option, but the publication could not be retained. The publication was not published to any matching subscribers. Retained publications are stored on the SYSTEM.RETAINED.PUB.QUEUE. Possible reasons for failure include the queue being full, the queue being 'put' inhibited, or the queue not existing.
Response: Ensure that the SYSTEM.RETAINED.PUB.QUEUE queue is available for use by the application.

AMQ4479: An MQOPEN or MQPUT1 call was issued, specifying an alias queue as the target, but the BaseObjectName in the alias queue attributes was not recognized as a queue or topic name.
Severity: 20: Error
Explanation: This error can also occur when BaseObjectName is the name of a cluster queue that cannot be resolved successfully.
Response: Correct the queue definitions.

AMQ4480: An MQOPEN or MQPUT1 call was issued, specifying an alias queue as the target, but the BaseObjectName in the alias queue definition resolves to a queue that is not a local queue, or local definition of a remote queue.
Severity: 20: Error
Response: Correct the queue definitions.

AMQ4481: An error occurred when unsubscribing from the topic. The operation failed with reason code <insert_0>.
Severity: 20: Error
Response: Use the reason code to determine the underlying reason for the failure.

AMQ4482: An error occurred when obtaining a publication. The operation failed with reason code <insert_0>.
Severity: 20: Error
Explanation: An error occurred when performing a get operation for the subscribed topic. The topic was automatically unsubscribed.
Response: Use the reason code to determine the underlying reason for the failure.

AMQ4483: An error occurred when publishing a message on the topic. The operation failed with reason code <insert_0>.
Severity: 20: Error
Response: Use the reason code to determine the underlying reason for the failure.

AMQ4484: An error occurred when obtaining the topic string for a publication. The operation failed with reason code <insert_0>.
Severity: 20: Error
Explanation: The topic was automatically unsubscribed.
Response: Use the reason code to determine the underlying reason for the failure.

AMQ4485: This action removes the retained publication from the topic string <insert_0> on the selected queue manager only.
Are you sure you want to clear the retained publication?
Severity: 10: Warning
Explanation: A confirmation is required before the retained publication is cleared.
Response: Continue only if you want to permanently clear the retained publication on this topic string.

AMQ4486: The retained publication on the topic string <insert_0> has been successfully cleared.
Severity: 0: Information
Response: Message for information only.

AMQ4487: Error initialising <insert_0>.
Severity: 30: Severe error
Explanation: An error occurred while starting this application.
Response: Check that the WebSphere MQ runtime libraries are available and the PATH system environment variable includes the directory for these runtime libraries.)

AMQ4488: Unable to locate a Web browser, product documentation, or IBM Eclipse Help System to display the help.
Severity: 10: Warning
Explanation: To launch the help system, the Web browser or product documentation or IBM Eclipse Help System must be included in the PATH system environment variable.
Response: Install the product documentation or IBM Eclipse Help System or set the available Web browser on the system path. Re-launch the application and try again.

AMQ4489: Error launching the IBM Eclipse Help System.
Severity: 10: Warning
Explanation: The application failed to create an instance of the IBM Eclipse Help System.
Response: Check that the IBM Eclipse Help System has been installed.

AMQ4490: Error starting the IBM Eclipse Help System.
Severity: 10: Warning
Explanation: The application failed to start the IBM Eclipse Help System.
Response: Check that the IBM Eclipse Help System has been installed.

AMQ4491: Error launching the help system with a Web browser.
Severity: 10: Warning
Explanation: The application failed to launch the help system through a Web browser.
Response: Check that the Web browser specified in the system path is working.

AMQ4492: Error launching the help system with IBM Eclipse Help System.
Severity: 10: Warning
Explanation: The application failed to launch the help system through IBM Eclipse Help System.
Response: Check that the IBM Eclipse Help System has been installed.

AMQ4493: The help documentation is not available on the system.
Severity: 10: Warning
Explanation: The application failed to locate the help documentation on the system.
Response: Check that the available help documentation for WebSphere MQ is installed.

AMQ4494: Unable to locate a Web browser in the system path.
Severity: 10: Warning
Explanation: The application failed to locate a Web browsers in the system path.
Response: Check that a suitable Web browser is specified in the system path.

AMQ4495

This action resynchronizes all the proxy subscriptions with all other directly connected queue managers in all clusters and hierarchies in which this queue manager is participating.

Are you sure you want to continue with this action?

Severity

10: Warning

Explanation

This should only be used if the queue manager is receiving proxy subscriptions that it should not be, or is not receiving proxy subscriptions that it should be.

Missing proxy subscriptions can be observed if the closest matching Topic definition has been specified with Publication scope or Subscription scope set to Queue Manager, or if it has an empty or incorrect Cluster name.

Extraneous proxy subscriptions can be observed if the closest matching Topic definition has been specified with Proxy subscription behavior set to Force.

Response

Check the Topic definitions before resynchronizing the proxy subscriptions.

AMQ4496: The request to refresh the proxy subscriptions was accepted by WebSphere MQ.
Severity: 0: Information
Response: Message for information only.

AMQ4497: The topic string has already been specified for another topic. Enter a different topic string.
Severity: 10: Warning
Response: Enter a different topic string.

AMQ4498: This action removes the retained publication from the topic string <insert_0> on all queue managers connected in the Publish/Subscribe cluster.
Are you sure you want to clear the retained publication?
Severity: 10: Warning
Explanation: A confirmation is required before the retained publication is cleared.
Response: Continue only if you want to permanently clear the retained publication on this topic string.

AMQ4499: The queue attribute for the JMS queue <insert_0> is empty. A queue name needs to be entered before mapping the JMS queue to an MQ queue.
Severity: 10: Warning
Explanation: The user has not entered a queue name for the JMS Queue and therefore an MQ Queue cannot be created.
Response: Enter a value for the queue attribute on the JMS Queue and then try to create the MQ Queue again.

AMQ4500: Are you sure that you want to forcibly remove queue manager <insert_0> from cluster <insert_1>?
Severity: 10: Warning
Explanation: You should only forcibly remove a queue manager from a cluster when it has already been deleted and cannot be removed from the cluster in the normal way. A confirmation is required before the queue manager is forcibly removed.
Response: Continue only if you want to forcibly remove the queue manager.

AMQ4501: The queue manager was successfully removed from the cluster. This might take some time to be reflected in the WebSphere MQ Explorer.
Severity: 0: Information
Explanation: The queue manager will still appear as a member of the cluster until the configuration changes have been sent across the network and the cluster channels to the queue manager have become inactive. This might take a long time.

AMQ4502: You have shared the queue in cluster <insert_0>. The queue manager is not a member of this cluster.
Severity: 10: Warning
Response: To make the queue available to the members of this cluster, you must join the queue manager to the cluster.

AMQ4503: The list of values is too long.
Severity: 10: Warning
Explanation: The list of values that you have entered is too long. The maximum number of characters allowed for this value is <insert_0>.

AMQ4504: The value is too long.
Severity: 10: Warning
Explanation: You have entered a value containing too many characters. The maximum number of characters allowed for each value of this attribute is <insert_0>.

AMQ4505: There are too many entries in the list.
Severity: 10: Warning
Explanation: You have entered too many values in the list. The maximum number of values is <insert_0>.

AMQ4506: Cannot connect to queue manager <insert_0>. It cannot be removed from the cluster in the normal way.
Severity: 10: Warning
Response: Try the operation again when the queue manager is available. If the queue manager no longer exists, you can choose to forcibly remove the queue manager from the cluster.

AMQ4507: The remote queue manager is not using TCP/IP.
Severity: 10: Warning
Explanation: The connection information available for the remote queue manager uses a communication protocol other than TCP/IP. The WebSphere MQ Explorer cannot connect to the queue manager to remove it from the cluster in the normal way.
Response: If the queue manager no longer exists, you can choose to forcibly remove the queue manager from the cluster.

AMQ4508: The queue manager successfully left the cluster.
Severity: 0: Information
Explanation: The queue manager will still appear as a member of the cluster until the configuration changes have been sent across the network and the cluster channels to the queue manager have become inactive. This might take a long time.

AMQ4509: The request to suspend membership of the cluster has been accepted.
Severity: 0: Information
Response: Message for information only.

AMQ4510: The request to resume membership of the cluster has been accepted.
Severity: 0: Information
Response: Message for information only.

AMQ4511: The queue manager is not a member of the cluster.
Severity: 0: Information
Response: Message for information only.

AMQ4512: An error occurred while performing a cluster operation. The operation failed with error <insert_0>.
Severity: 0: Information
Response: Message for information only.

AMQ4513: The request to refresh the information about the cluster has been accepted.
Severity: 0: Information
Response: Message for information only.

AMQ4514: The queue manager is not a member of cluster <insert_0>.
Severity: 10: Warning
Explanation: The object that you have shared in the cluster will not be available to other members of the cluster until you make this queue manager a member of the cluster.

AMQ4515: The repository queue manager for cluster <insert_0> is not available for connection.
Severity: 10: Warning
Explanation: Views showing cluster queues in this cluster might not be complete.

AMQ4516: Cluster workload exit error.
Severity: 10: Warning
Explanation: The queue manager's cluster workload exit failed unexpectedly or did not respond in time.

AMQ4517: Cluster resolution error.
Severity: 10: Warning
Explanation: The definition of the cluster queue could not be resolved correctly because a response from a repository queue manager was not available.

AMQ4518: AMQ4518=A call was stopped by the cluster exit.
Severity: 10: Warning
Explanation: The queue manager's cluster workload exit rejected a call to open or put a message onto a cluster queue.

AMQ4519: No destinations are available.
Severity: 10: Warning
Explanation: At the time that the message was put, there were no longer any instances of the queue in the cluster.

AMQ4520: The WebSphere MQ Explorer could not initialize TCP/IP. Administration of remote queue managers and clusters is not possible.
Severity: 10: Warning

AMQ4521: The text you entered contained a comma (,) which is used as a list separator character.
Severity: 10: Warning
Explanation: This value does not accept lists.
Response: If you want to use a comma as part of a value, enclose the value in double quotation marks.

AMQ4522: The wizard was unable to add the queue manager to the cluster.
All changes will be rolled back.
Severity: 10: Warning
Explanation: A problem occurred while defining objects or modifying the queue manager's properties.
Response: Ensure that the default objects exist for the queue manager.

AMQ4523: The wizard was unable to add one of the queue managers to the cluster.
All changes will be rolled back.
Severity: 10: Warning
Explanation: A problem occurred while defining objects or modifying one of the queue managers' properties.
Response: Ensure that the default objects exist for the queue manager.

AMQ4524: The queue manager <insert_0> is the source repository in cluster <insert_1>. Removing this queue manager from the cluster prevents further repository actions from being run. To enable repository actions again, re-select another queue manager as the source of information. Are you sure that you want to remove this queue manager?
Severity: 10: Warning
Explanation: To be able to display cluster information, the clustering component of the WebSphere MQ Explorer requires at least one full repository to be selected as the source. Removing the last full repository prevents the display of cluster members, and hence will prevent cluster actions being run on these full repositories.
Response: Select Yes if you want to remove the source repository, even though it will prevent access to remaining cluster information.

AMQ4525: Cluster workload exit load error.
Severity: 10: Warning
Explanation: The queue manager's cluster workload exit failed to load.
Response: Check that the cluster workload exit exists and the name has been specified correctly.

AMQ4526: During the import further plug-ins were enabled. Do you want to import their settings?
Severity: 0: Information
Explanation: The import file contains settings for the plug-ins enabled during the import.
Response: Select Yes to import the settings.

AMQ4527: Default Configuration is already running.
Severity: 10: Warning
Explanation: There is an instance of default configuration already running on the system.
Response: Use the previously launched default configuration application. If you fail to get the previous default configuration dialog, stop the JVM running the application and try re-launching the application.

AMQ4528: The file selected does not contain any import settings.
Severity: 20: Error
Response: Select another file and try again.

AMQ4529: Put message failed. The page set ID specified for the storage class defined for this queue is not valid.
Severity: 20: Error
Explanation: The MQPUT or MQPUT1 call was issued, but the page set id specified in the storage class object defined for the queue is not valid.
Response: Correct the page set ID value in the storage class definition used by this queue and try again. If the error persists contact your System Administrator.

AMQ4530: The request to create and start a new z/OS listener was accepted.
Severity: 0: Information
Explanation: A user request to create the listener was accepted by WebSphere MQ.
Response: Message for information only.

AMQ4531: The subscription is in use.
Severity: 20: Error
Explanation: An attempt was made to delete or change a subscription in use.
Response: Ensure that the subscription is not in use and try again.

AMQ4547
Severity: 20: Error
Explanation: Unable to load system libraries as the java.library.path and the native library path reference different installations.
Response: Ensure that the native library path (LD_LIBRARY_PATH, LIBPATH, or SHLIB_PATH) is set correctly.

AMQ4548
Severity: 20: Error
Explanation: MQ Explorer encountered a problem with the system browser when trying to display the web page.
Response: Ensure that a browser is available to display the web page. If symptoms persist, contact your System Administrator.

AMQ4549: An unexpected error occurred copying settings from workspace <insert_0>.
Severity: 10: Warning
Explanation: Some files or preferences could not be copied from the previous workspace.
Response: Ensure that the Eclipse workspace exists at the specified location and can be read.

AMQ4570: The requested application is either not installed or could not be launched.
Severity: 20: Error
Response: Check that the corresponding product feature has been installed successfully. If symptoms persist contact your System Administrator.

AMQ4571: Are you sure that you want to change the location of the Key Repository for queue manager <insert_0>?
Severity: 10: Warning
Explanation: You might prevent the queue manager from starting if you change the Key Repository field to a location which is not valid.
Response: Ensure that the location specified is correct before continuing.

AMQ4572: The request to refresh the information about all clusters has been accepted.
Severity: 0: Information
Response: Message for information only.

AMQ4573: A queue manager has not been entered in the <insert_0> field on the <insert_1> page. A value must be entered in this field before the Select button can be used to set the <insert_2> field. Note that this value can also be entered manually.
Severity: 20: Error
Explanation: WebSphere MQ Explorer needs to know exactly which queue manager to query to populate the object selection dialog.
Response: Enter a valid value into the appropriate field

AMQ4574: IBM WebSphere Explorer is already running.
Severity: 30: Severe error

AMQ4575: An error occurred initializing the data model.
Severity: 30: Severe error

AMQ4576: The working directory <insert_0> is not valid.
Severity: 30: Severe error

AMQ4577: An error occurred initializing the process.
Severity: 30: Severe error

AMQ4578: An error occurred loading the messages file <insert_0>.
Severity: 30: Severe error

AMQ4579: An error occurred loading the system libraries.
Severity: 30: Severe error

AMQ4580: An internal method detected an unexpected system return code. The method <insert_0> returned <insert_1>.
Severity: 30: Severe error
Response: Examine the problem determination information on this computer to establish the cause of the error.

AMQ4581: Parameter check failed on the internal function <insert_0>. The error was <insert_1>.
Severity: 30: Severe error
Response: Examine the problem determination information on this computer to establish the cause of the error.

AMQ4582: Queue manager <insert_0> is not available for client connection.
Severity: 30: Severe error
Response: Ensure the queue manager is running and is configured to accept remote connections.

AMQ4583: Queue manager <insert_0> is not available for connection.
Severity: 30: Severe error
Response: Ensure the queue manager is running.

AMQ4584: Queue manager <insert_0> is not available for cluster connection.
Severity: 30: Severe error
Response: Ensure that the queue manager is running. If the queue manager has been deleted it might continue to be displayed as a member of a cluster for up to 30 days.

AMQ4585: An internal method <insert_0> encountered an unexpected error.
Severity: 30: Severe error
Response: Examine the problem determination information on this computer to establish the cause of the error.

AMQ4586: The attempt to create the URL for file <insert_0> failed.
Severity: 30: Severe error
Explanation: The file name specified was not recognized.
Response: Ensure that the file exists at the specified location and can be read.

AMQ4587: The attempt to read from URL <insert_0> failed.
Severity: 30: Severe error
Explanation: There was an error when the system tried to read the Client channel definition table.
Response: Ensure that the file exists at the specified location and can be read.

AMQ4588: The attempt to read from URL <insert_0> failed.
Severity: 30: Severe error
Explanation: There was an error when the system tried to read the file.
Response: Ensure that the file exists at the specified location and can be read.

AMQ4589: No connection was found to application <insert_0>.
Severity: 10: Warning
Explanation: The connection was not found. Possibly the connection was closed before the command was issued.
Response: Check that the application connection has not been closed in the background.

AMQ4590: The queue manager connection to application <insert_0> could not be closed.
Severity: 20: Error
Explanation: The connection could not be closed due to a PCF error.
Response: Check for FFSTs.

AMQ4591: The command server for <insert_0> is not running.
Severity: 30: Severe error
Explanation: The command server has stopped for some reason, so the request cannot be processed.
Response: Start the command server. If the error persists, examine the problem determination information to see if any details have been recorded.

AMQ4592: The connection was closed successfully.
Severity: 0: Information
Explanation: The request to close the connection to an application was successful.
Response: Message for information only.

AMQ4593: Do you really want to stop the connection to application <insert_0>
Severity: 0: Information
Explanation: WebSphere MQ explorer is about to stop a connection, stopping the connection will prevent further communication between MQ and the application in question.
Response: Select yes if you want to stop the connection.

AMQ4594: The queue manager connection to application <insert_0> has not been closed.
Severity: 0: Information
Explanation: Certain WebSphere MQ queue manager processes cannot be stopped.
Response: Message for information only.

AMQ4595: No response was received to the request to close the connection to application <insert_0>.
Severity: 30: Severe error
Explanation: The command server might no longer be running.
Response: If the error persists, examine the problem determination information to see if any details have been recorded.

AMQ4596: Key store file <insert_0> cannot be found.
Severity: 10: Warning
Explanation: The SSL key store or trust store does not exist.
Response: Create a new store file or change the connection property. Then try the request again.

AMQ4597: No certificates were loaded from key store file <insert_0>.
Severity: 10: Warning
Explanation: The SSL key store or trust store does not contain any certificates.
Response: Add the appropriate certificates to the key store file. Then try the request again.

AMQ4598: Key store file <insert_0> could not be opened with the given password.
Severity: 10: Warning
Explanation: The SSL key store or trust store could not be opened.
Response: Change the password. Then try the request again.

AMQ4599: Changing the FIPS required setting will affect all client connections using SSL and requires the WebSphere MQ Explorer to be restarted. Are you sure that you want to restart the WebSphere MQ Explorer now ?
Severity: 10: Warning
Explanation: The FIPS required value is an application-wide setting and can only be changed from the Preferences page. All client connections using SSL will be affected by this setting.
Response: Restart the WebSphere MQ Explorer to apply this change.

AMQ4600: The password store <insert_0> could not be opened using the given key.
Severity: 10: Warning
Explanation: The specified password store file cannot be opened.
Response: Make sure the password store file exists. Enter a different key and try again.

AMQ4601: Do you want to copy entries from the old password store to the new one?
Severity: 10: Warning
Explanation: The user has changed the name of the password store file.
Response: Click Yes to copy entries to the new file.

AMQ4602: Unable to validate the given key for password store <insert_0>.
Severity: 10: Warning
Explanation: The password store cannot be opened with the specified key.
Response: Enter a different key and try the operation again.

AMQ4603: Invalid password store <insert_0>.
Severity: 10: Warning
Explanation: The file name is the name of a directory.
Response: Enter a valid file name.

AMQ4604: Password store <insert_0> is read-only.
Severity: 10: Warning
Explanation: WebSphere MQ Explorer only has read access to the file name.
Response: Specify the name of a file that has both read and write access.

AMQ4605: Format of password store <insert_0> is unknown.
Severity: 10: Warning
Explanation: The contents of the password store file is unknown. This may be an existing XML file which has not been created as a password store or a non-XML file.
Response: Specify an existing password store file name or specify a new XML file.

AMQ4606: Password store <insert_0> was not opened.
Severity: 10: Warning
Explanation: The user chose not to open the password store.
Response: Restart the WebSphere MQ Explorer to open the password store or use the Password preference page.

AMQ4607: Queue manager has been disabled for Publish/Subscribe operations.
Severity: 10: Warning
Explanation: An error occurred trying to perform a publish or subscribe operation.
Response: Change the PSMODE attribute on the queue manager to enable Publish/Subscribe operations.

AMQ4608: The specified destination does not exist.
Severity: 30: Severe error
Explanation: An error occurred trying to create a new subscription.
Response: Change the destination name and try again.

AMQ4609: The listener was started.
Severity: 0: Information
Explanation: The request to start a listener was successful.
Response: Message for information only.

AMQ4610: Invalid connection name.
Severity: 10: Warning
Explanation: The connection name in the channel definition could not be resolved into a network address. Either the name server does not contain the entry, or the name server was not available.
Response: Ensure that the connection name is correctly specified and that the name server is available.

AMQ4611: Applying these changes will disconnect the queue manager and reconnect with the new details. Do you want to continue?
Severity: 0: Information
Explanation: Connection details have been changed to a connected queue manager. Without reconnecting, the current connection details cannot be seen.
Response: Select yes to continue or no to cancel the changes.

AMQ4616: A newer command level has been found when connecting to <insert_0>. The old level is <insert_1> and the new level is <insert_2>. The connection to the queue manager will be replaced.
Severity: 0: Information
Explanation: A previous connection to this queue manager has been successful; the queue manager is the same but the command level is now higher. The version of WebSphere MQ has been changed.
Response: Message for information only.

AMQ4620: Channel Authentication Record already exists.
Severity: 20: Error
Explanation: An attempt was made to add a Channel Authentication Record, but it already exists.
Response: Use the properties panel to change an existing record.

AMQ4621: Channel Authentication Record not found.
Severity: 20: Error
Explanation: The specified channel authentication record does not exist.
Response: Specify a channel authentication record that exists.

AMQ4622: A Channel Authentication Record contained an IP address with a range that conflicted with an existing range.
Severity: 20: Error
Explanation: A range must be a complete superset or subset of any existing ranges for the same channel profile name.
Response: Specify a range that is a superset or a subset of existing ranges.

AMQ4623: The maximum number of Channel Authentication Records has been exceeded.
Severity: 20: Error
Explanation: A Channel Authentication Record was set taking the total number of entries for that type on a single channel profile, over the maximum number allowed.
Response: Remove some Channel Authentication Records to make room.

AMQ4624: A Channel Authentication Record contained an invalid IP address.
Severity: 20: Error
Explanation: A Channel Authentication Record contained an invalid IP address, or invalid wildcard pattern to match against IP addresses.
Response: Specify a valid IP address.

AMQ4625: A Channel Authentication Record contained an invalid IP address range.
Severity: 20: Error
Explanation: A Channel Authentication Record contained an IP address with a range that was invalid, for example, the lower number is higher or equal to the upper number of the range.
Response: Specify a valid range in the IP address.

AMQ4626: The Channel Authentication Record client user value is not valid.
Severity: 20: Error
Explanation: The client user value contains a wildcard character which is not allowed.
Response: Specify a valid value for the client user field.

AMQ4627: Channel authentication profile name is invalid.
Severity: 20: Error
Explanation: The channel profile name used in the command was not valid. This might be because it contained characters which are not accepted names, or characters which are not valid for the specified profile type.
Response: Specify a valid value for the channel authentication profile name.

AMQ4700: PCF command identifier (<insert_0>) not valid for queue manager <insert_1>.
Severity: 10: Warning
Explanation: The specified PCF command is not supported by this queue manager.

AMQ4701: The command level of the queue manager does not support the requested version of the command.
Severity: 10: Warning
Explanation: There is a mismatch between the command requested and the command level supported by the queue manager. This might be because an intermediate queue manager is being used which is of a lower command level than the remote queue manager.
Response: Ensure that the intermediate queue manager is at the same or higher command level than the queue manager it is being used to connect to. If necessary, reconnect to the queue manager using a different intermediate queue manager.

AMQ4702: The current filter not supported for queue manager <insert_0>.
Severity: 10: Warning
Explanation: The filter being applied to this view is not supported by this queue manager.
Response: Ensure that the filter settings are supported by the queue manager.

AMQ4766: Setup needs to install or upgrade this computer to version 2.0 of Microsoft Windows Installer. (MSI).
Explanation: After the upgrade you might need to reboot.
Response: Select Yes or No to Proceed.

AMQ4800: Error initializing <insert_0>.
Severity: 30: Severe error
Explanation: An error occurred while starting this application.
Response: Check that the WebSphere MQ runtime libraries are available.
Check that the PATH system environment variable includes the directory for these runtime libraries.)

AMQ4807: The message size specified (<insert_0>) is outside the permitted range.
Severity: 10: Warning
Response: Specify a value of 1000 to 100 000 000.

AMQ4808: Unknown <insert_0> <insert_1>.
Severity: 10: Warning
Explanation: The named entity for the particular type is not defined on the system.
Response: Make sure the entity is defined and it matches the type of entity.

AMQ4809: You are about to delete the authority for <insert_0> to <insert_1>. Are you sure that you want to continue?
Severity: 10: Warning
Explanation: You must confirm that you want to delete the specified authority. The entity name and object name are provided in the message.
Response: Continue only if you want to permanently delete the authority.

AMQ4810: The authority for <insert_0> to <insert_1> was deleted successfully.
Severity: 0: Information
Response: Message for information only.

AMQ4811: The authority was created successfully.
Severity: 0: Information
Response: Message for information only.

AMQ4812: You are about to delete all create authorities for <insert_0>. Are you sure that you want to continue?
Severity: 10: Warning
Explanation: You must confirm that you want to delete the specified authority. The entity name is provided in the message.
Response: Continue only if you want to permanently delete the authority.

AMQ4813: You are about to refresh SSL security for <insert_0>. This might affect the running status of active channels. Are you sure that you want to continue?
Severity: 10: Warning
Explanation: A confirmation is required before the refresh command is issued. Certain active channel types might be stopped as a result of this command. The queue manager name is provided in the message.
Response: Continue only if you want to refresh SSL security.

AMQ4814: The command server is not allowing security requests.
Severity: 10: Warning
Explanation: The command server has been started with the "-a" option which blocks security related PCFs.
Response: Restart the command server without using the "-a" option.

AMQ4815: You are about to add authority for a non-generic profile name <insert_0>. Are you sure that you want to continue?
Severity: 10: Warning
Explanation: You chose to add authorities for a generic profile name, but entered the name for a specific profile.
Response: Continue if you want to add authority for a specific profile name.

AMQ4816: The list of authorizations held internally by the authorization services component will be refreshed. Are you sure that you want to continue?
Severity: 10: Warning
Explanation: A confirmation is required before the refresh command is issued.
Response: Continue only if you want to refresh authorization service component security.

AMQ4817: The in-storage profiles for the requested resources will be refreshed. Are you sure that you want to continue?
Severity: 10: Warning
Explanation: A confirmation is required before the refresh command is issued to the WebSphere MQ in-storage ESM (External Security Manager).
Response: Continue only if you want to refresh the ESM.

AMQ4818: No authority records were found.
Severity: 10: Warning
Explanation: There are no authority records matching the specific request.
Response: Change the entity or profile name and try again.

AMQ4819: Unable to write to file <insert_0>.
Severity: 10: Warning
Explanation: You do not have write access to the file name.
Response: Check that your userid has write access to the file name.

AMQ4820: A file called <insert_0> already exists. Do you want to replace this file?
Severity: 0: Information
Response: Confirm that you want to replace the file.

AMQ4821: This action replaces an existing authority record. Are you sure that you want to continue?
Severity: 0: Information
Explanation: An explicit authority record already exists for this entity. Creating a new authority record replaces the existing authority record.
Response: Continue only if you want replace the existing authority record.

AMQ4822: You must enter a specific profile name when using an entity name.
Severity: 0: Information
Response: Enter a specific profile name.

AMQ4823: Profile <insert_0> does not exist.
Severity: 0: Information
Explanation: The profile name entered by the user does not exist for the type of object.
Response: Change the name of the profile or use the select button and try again.

AMQ4824: Invalid profile name <insert_0>.
Severity: 0: Information
Explanation: The generic profile name entered by the user is not allowed.
Response: Change the name of the profile to match the supported wildcard characters and try again.

AMQ4825: The security exit class <insert_0> is invalid or cannot be found.
Severity: 10: Warning
Response: Ensure that the security exit class is available and that it implements the com.ibm.mq.MQSecurityExit interface.

AMQ4826: There is a security profile case conflict.
Severity: 10: Warning
Explanation: The security profile case attribute of the queue manager is different from that issued on the refresh command.
Response: Change the security profile case attribute of the queue manager or of the class specified on the refresh command.

AMQ4830: You are about to add authority for a generic profile name "<insert_0>". Are you sure that you want to continue?
Severity: 10: Warning
Explanation: You chose to add authorities for a specific profile name, but entered the name for a generic profile.
Response: Continue if you want to add authority for a generic profile name.

AMQ4850: Further tests cannot be run because the WebSphere MQ Explorer Test Plug-in is currently in use.
Severity: 10: Warning
Explanation: You must either cancel these tests or wait for them to complete before initiating further tests.
Response: Either stop the current tests using the progress view, or wait until the current tests are completed.

AMQ4851: There are no tests available to run.
Severity: 0: Information
Explanation: The configuration used to launch these tests has no tests selected, this could be because no tests are selected, or there are no appropriate tests available.
Response: Try a difference configuration which has tests enabled, or try testing from a different point to ensure that there are appropriate tests available.

AMQ4852: WebSphere MQ Explorer Test Plug-in initialization error.
Severity: 20: Error
Explanation: An error has occurred during initialization of the a Tests Plug-in. This might cause problems with running tests.
Response: Examine the problem determination information to see if any details have been recorded.

AMQ4853: The test cannot be disabled because no configurations currently have this test enabled.
Severity: 0: Information
Response: No further action is required; the test is already disabled.

AMQ4854: Finished running <insert_0> tests.
Severity: 0: Information
Explanation: The requested test run is complete, and the number of tests specified have been run. This message can be disabled from the Tests plug-in preferences.
Response: No further action is required; the test run has finished

AMQ4855: The test run was canceled.
Severity: 0: Information
Explanation: The requested test run was canceled as the result of a user request. This message can be disabled from the Tests plug-in preferences.
Response: Message for information only.

AMQ4856: Are you sure that you want to clear the subscription named <insert_0>?
For a managed destination, messages already queued to the destination will be deleted.
Severity: 10: Warning
Explanation: A confirmation is required before the subscription is cleared.
Response: Continue only if you want to clear the subscription.

AMQ4857: The Subscription was cleared.
Severity: 0: Information
Explanation: The subscription was cleared to a well defined state. For a managed destination any messages already queued to the destination were deleted.
Response: Message for information only.

AMQ4858: A parameter change has been detected.
Severity: 0: Information
Explanation: A parameter has been changed without using the WebSphere MQ Explorer.
Response: Refresh the WebSphere MQ Explorer view and try the operation again.

AMQ4859: The requested function is not available.
Severity: 0: Information
Explanation: WebSphere MQ Explorer was not able to carry out the function requested.
Response: Try again. If symptoms persist contact your System Administrator.

AMQ4860: The queue manager is running in standby mode.
Severity: 0: Information
Explanation: The queue manager has been started in standby mode.

AMQ4861: WebSphere MQ cannot stop the listener because the listener is already stopped.
Severity: 10: Warning

AMQ4862: The default remote administration listener LISTENER.TCP could not be deleted.
Severity: 10: Warning
Explanation: A problem has occurred trying to delete the listener.
Response: Check that the listener has been stopped or that it has not already been deleted.

AMQ4863: The property <insert_0> has not been prefixed correctly.
Severity: 20: Error
Explanation: Service definition destination names must be prefixed with 'msg/queue/' for queues, or 'msg/topic/' for topics.
Response: Prefix the destination name with the relevant prefix.

AMQ4864: The property <insert_0> is not the correct length.
Severity: 20: Error
Explanation: Queue names cannot exceed 48 characters.
Response: Check that the name of the queue is correct.

AMQ4865: The property <insert_0> does not contain a destination name.
Severity: 20: Error
Explanation: The value entered does not include the name of a destination.
Response: Enter the name of a valid destination. Service definition destination names must be prefixed with 'msg/queue/' for queues, or 'msg/topic/' for topics.

AMQ4866: The property <insert_0> is not a valid URI format.
Severity: 20: Error
Explanation: Only valid URIs can be specified for this property.
Response: Check that the value entered is in a valid URI syntax.

AMQ4867: The property <insert_0> on page <insert_1> is not a valid URI format.
Severity: 20: Error
Explanation: Only valid URIs can be specified for this property.
Response: Check that the value entered is in a valid URI syntax.

AMQ4868: An unexpected error has occurred.
Severity: 20: Error
Explanation: An unexpected error has occurred.
Response: Contact your system administrator.

AMQ4869: The export location <insert_0> already exists. Do you want to overwrite the existing files?
Severity: 10: Warning
Explanation: The export location already exists. If you continue, existing files may be overwritten.
Response: Confirm that you want you overwrite files at the chosen export location.

AMQ4870: Could not establish a connection to the queue manager. Channel not available.
Severity: 10: Warning
Explanation: The attempt to connect to the queue manager failed. See reason code MQRC_CHANNEL_NOT_AVAILABLE for more information.
Response: Examine the queue manager and client error logs for messages explaining the cause of the problem.

AMQ4871: Could not establish a connection to the queue manager. Channel name not recognized.
Severity: 10: Warning
Explanation: The attempt to connect to the queue manager failed. The queue manager did not recognize the channel name.
Response: Use a different channel name and try again.

AMQ4999: An unexpected error (<insert_0>) has occurred.
Severity: 10: Warning
Explanation: An unlisted error has occurred in the system while retrieving PCF data.
Response: Try the operation again. If the error persists, examine the problem determination information to see if any details have been recorded.