AMQ4xxx: User interface messages (Windows and Linux systems)
AMQ4000W
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 not available, or create a new one. Then try the request again.
AMQ4001
The queue manager specified has already been added to MQ Explorer.
Severity
0 : Informational
Response
Message for information only. If the queue manager is not displayed in the Navigator view, ensure that the queue manager is not hidden.
AMQ4002W
Are you sure that we want to delete the object named <insert_0>?
Severity
10 : Warning
Explanation
A confirmation is required before the specified object is deleted.
The name of the object is provided in the message.
Response
Continue only if we want to permanently delete the object.
AMQ4003W
System objects are used internally by IBM MQ.
Are you sure that we want to delete the system object named <insert_0>?
Severity
10 : Warning
Explanation
A confirmation is required before an internal IBM MQ system object
(for example SYSTEM.DEFAULT.LOCAL.QUEUE) is deleted.
Response
Continue only if we want to permanently delete the system object.
AMQ4004W
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 we want to permanently delete the messages.
AMQ4005W
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
IBM MQ successfully sent data to the remote queue manager and received the data returned.
Severity
0 : Informational
Explanation
An open channel has been successfully verified as the result of a user request.
AMQ4007
The message sequence number for the channel was reset.
Severity
0 : Informational
Explanation
A channel has had its sequence number successfully reset as the result of a user request.
AMQ4008I
The request to start the channel was accepted.
Severity
0 : Informational
Explanation
A channel has been started successfully as the result of a user request.
AMQ4009I
The request to stop the channel was accepted.
Severity
0 : Informational
Explanation
A channel has been stopped successfully as the result of a user request.
AMQ4010
The 'in-doubt' state was resolved.
Severity
0 : Informational
Explanation
A channel has had its 'in-doubt' state resolved successfully as the result of a user request.
AMQ4011I
The queue has been cleared of messages.
Severity
0 : Informational
Explanation
The CLEAR command completed successfully and has removed all messages from the target queue. If the CLEAR was performed using the MQGET API command, uncommitted messages might still be on the queue.
AMQ4012I
The object was created successfully but it is not visible with the current settings for visible objects.
Severity
0 : Informational
AMQ4014W
The character <insert_0> is not valid.
Severity
10 : Warning
AMQ4015I
Supply a non-blank name.
Severity
0 : Informational
Response
Enter a valid name.
AMQ4016I
The test message was put successfully.
Severity
0 : Informational
Explanation
The request to place a message on the target queue has completed successfully. The queue now contains the message.
AMQ4019I
An object called <insert_0> already exists. Do we want to replace the definition of the existing object?
Severity
0 : Informational
Response
Confirm that we want to replace the definition.
AMQ4020W
The changes we 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 we 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 will affect other programs or queue managers. Some changes can be forced anyway.
Response
Select Yes to try forcing the changes, or No to abandon the change.
AMQ4021W
Failed to access one or more objects.
Severity
10 : Warning
Explanation
The objects' icons have been marked to indicate the objects in error.
AMQ4022I
The name specified for the initiation queue is the same as the name of the queue itself.
Severity
0 : Informational
Response
Specify a different name to that of the object being created or altered.
AMQ4023I
The queue manager <insert_0> does not exist on this computer.
Severity
0 : Informational
AMQ4024I
The object cannot be replaced.
Severity
0 : Informational
Explanation
The request to replace the object was unsuccessful.
Response
To define this object, delete the existing object and try the operation again.
AMQ4025I
The changes made to the cluster attributes of the queue will take effect once they have propagated across the network.
Severity
0 : Informational
Response
Refresh any views containing the cluster queues in the affected clusters to show the changes.
AMQ4026I
We 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 : Informational
Response
Refresh any views containing the cluster queues in the affected clusters to show the cluster queue.
AMQ4027W
An error occurred connecting to queue manager <insert_0>. Are you sure that we want to show this queue manager in the folder anyway?
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 we 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 we want to correct the problem now and try again.
AMQ4028E
Platform not supported. This queue manager cannot be administered by 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 MQ Explorer.
Severity
20 : Error
AMQ4029E
Command level too low. This queue manager cannot be administered by MQ Explorer.
Severity
20 : Error
Response
To administer this queue manager, we must upgrade it to a newer version of IBM MQ.
AMQ4030E
Queue manager cannot be administered because codepage conversion table not found.
Severity
20 : Error
Explanation
This queue manager cannot be administered by MQ Explorer because a codepage conversion table was not found.
Response
Install a codepage conversion table from CCSID <insert_0> to CCSID <insert_1> on the computer on which MQ Explorer is running.
AMQ4031E
Queue manager cannot be administered because CCSID not found.
Severity
20 : Error
Explanation
This queue manager cannot be administered by MQ Explorer because CCSID <insert_0> cannot be found in the CCSID table. MQ Explorer cannot convert character data to or from the unrecognized CCSID.
AMQ4032W
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.
AMQ4033I
Cannot get messages from the queue.
Severity
0 : Informational
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.
AMQ4034W
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.
AMQ4035I
No message available. The response message did not arrive within a reasonable amount of time.
Severity
0 : Informational
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.
AMQ4036W
Access not permitted. You are not authorized to perform this operation.
Severity
10 : Warning
Explanation
The queue manager security mechanism has indicated that the userid associated with this request is not authorized to access the object.
AMQ4037I
Object definition changed since it was opened.
Severity
0 : Informational
Explanation
Object definitions that affect this object have been changed since the Hobj handle used on this call was returned by the MQOPEN call.
Response
Issue an MQCLOSE call to return the handle to the system. It is then usually sufficient to reopen the object and try the operation again.
AMQ4038W
Object damaged.
Severity
10 : Warning
Explanation
The object is damaged and cannot be accessed.
Response
The object should be deleted. Alternatively, it might be possible to recover it from a media image or backup.
AMQ4039W
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 or another application with options that conflict with those specified in the Options parameter. This arises if the request is for shared input, but the object is already open for exclusive input. It also arises if the request is for exclusive input, but the object is already open for input (of any sort).
Response
To change the attributes of an object, specify the Force option as 'Yes' to apply the changes. If you do this, any applications using the object must close and reopen the object to proceed.
AMQ4040I
Cannot put messages on this queue.
Severity
0 : Informational
Explanation
MQPUT and MQPUT1 calls are currently inhibited for the queue, or for the queue to which this queue resolves.
AMQ4042W
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.
AMQ4043E
Queue manager not available for connection - reason <insert_0>.
Severity
20 : Error
Explanation
The attempt to connect to the queue manager failed. This could be because the queue manager is incorrectly configured to allow a connection from this system, or the connection has been broken.
Response
Ensure that the queue manager is running. If the queue manager is running on another computer, ensure it is configured to accept remote connections.
AMQ4044I
Queue manager <insert_0> is stopping.
Severity
0 : Informational
Explanation
An MQI call was issued, but the call failed because the queue manager is shutting down. If the call was an MQGET call with the MQGMO_WAIT option, the wait has been canceled.
Response
We cannot issue any more MQI calls.
AMQ4045W
Queue not empty. The queue contains one or more messages or uncommitted PUT or GET requests.
Severity
10 : Warning
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.
AMQ4046E
Insufficient system resources available.
Severity
20 : Error
AMQ4047E
Insufficient storage available.
Severity
20 : Error
AMQ4048E
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 executing the requested operation, an unexpected return code was received. This has resulted in the operation not completing as expected.
Response
Use the reason code to determine the underlying reason for the failure.
AMQ4049W
Unknown object name.
Severity
10 : Warning
Explanation
A command or API request was issued, but the object cannot be found.
AMQ4050W
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.
AMQ4051W
Bind failed. The bind to a remote system during session negotiation failed.
Severity
10 : Warning
AMQ4052W
Coded character-set ID error. Cannot convert a command message to the CCSID of the target queue manager.
Severity
10 : Warning
AMQ4053W
Channel in doubt. Operation not completed.
Severity
10 : Warning
Explanation
The operation could not complete because the channel was in doubt.
AMQ4054W
Channel in use.
Severity
10 : Warning
Explanation
An attempt was made to perform an operation on a channel, but the channel is currently active.
AMQ4055W
Channel status not found.
Severity
10 : Warning
Explanation
No channel status is available for this channel. This might indicate that the channel has not been used.
AMQ4056W
Command failed.
Severity
10 : Warning
AMQ4057W
Configuration error in the channel definition or communication subsystem.
Severity
10 : Warning
Explanation
Allocation of a conversation is not possible.
AMQ4058W
Connection closed.
Severity
10 : Warning
Explanation
The connection to a remote system has unexpectedly broken while receiving data.
AMQ4059W
Could not establish a connection to the queue manager - reason <insert_0>.
Severity
10 : Warning
Explanation
The attempt to connect to the queue manager failed. This could 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.
AMQ4060W
Dynamic queue scope error.
Severity
10 : Warning
Explanation
The Scope attribute of the queue was set to MQSCO_CELL but this is not allowed for a dynamic queue.
AMQ4061W
Remote system not available. Could not allocate a conversation to a remote system.
Severity
10 : Warning
Response
The error might be transitory; try again later.
AMQ4062W
An MQINQ call failed when the queue manager inquired about an IBM MQ object.
Severity
10 : Warning
Response
Check the queue manager error log for more information about the error.
AMQ4063E
An MQOPEN call failed when the queue manager tried to open an IBM 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 queue manager error log for more information about the error.
AMQ4064W
An MQSET call failed when the queue manager tried to set the values of the attributes of an IBM MQ object.
Severity
10 : Warning
Response
Check the queue manager error log for more information about the error.
AMQ4065W
Message sequence number error.
Severity
10 : Warning
Explanation
The message sequence number parameter was not valid.
AMQ4066W
Message truncated because it is larger than the command server maximum valid message size.
Could not create object because the object already existed.
AMQ4070W
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.
AMQ4071W
Object has wrong type. Could not replace a queue object of a different type.
Severity
10 : Warning
AMQ4072W
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.
There is no definition of this channel on the remote system.
AMQ4081W
User exit not available.
Severity
10 : Warning
Explanation
The channel was closed because the user exit specified does not exist.
AMQ4082E
Unexpected IBM MQ error (<insert_0>).
Severity
20 : Error
AMQ4083W
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.
AMQ4084W
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.
PUT commands inhibited for system command queue called <insert_0>.
Severity
10 : Warning
AMQ4090W
Are you sure that we want to inhibit PUT and GET commands for the queue called 'SYSTEM.ADMIN.COMMAND.QUEUE'? If you do, we will no longer be able to administer the queue manager using MQ Explorer.
Severity
10 : Warning
Explanation
MQ Explorer uses the queue called 'SYSTEM.ADMIN.COMMAND.QUEUE' to administer the queue manager.
Response
Continue only if we want to inhibit PUT or GET commands for this queue and stop using MQ Explorer to administer the queue manager.
The remote queue manager is using an unsupported protocol for connections. MQ Explorer only supports connections to remote queue managers using the TCP/IP protocol.
AMQ4092W
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 we do not inadvertently affect the definitions of other objects using the namelist.
AMQ4093I
The cluster specified is already shown in the console.
Severity
0 : Informational
AMQ4094W
An error occurred adding this cluster to the console. Are you sure that we 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 we want to correct the problem now and try again.
AMQ4095I
Queue manager <insert_0> is not a repository queue manager for cluster <insert_1>.
Severity
0 : Informational
Explanation
To administer a cluster, MQ Explorer needs a connection to the repository queue manager.
AMQ4096I
Are you sure that we want to clear the password?
Severity
0 : Informational
Response
Check with the user before clearing the password. Continue only if you really want to clear the password.
AMQ4097W
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.)
AMQ4098W
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.)
AMQ4099W
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.
Ensure that the named queue manager is running on the machine specified in the selected channel definition table. Ensure that we have the authority to connect to the remote queue manager, and ensure that the network is up and running. Select Yes if you believe that the problem can be resolved later. Select No if we want to correct the problem now and try again.
AMQ4104W
The specified file <insert_0> does not contain a client definition table in the correct format.
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.
AMQ4117W
This action cannot be undone. Are you sure that we want to delete the queue manager <insert_0> from the system?
Severity
10 : Warning
Explanation
A confirmation is required before the queue manager is deleted.
Response
Continue only if we want to permanently delete the queue manager.
AMQ4121W
The MQGET request received an unexpected reason code of <insert_0>.
Severity
10 : Warning
Explanation
An unexpected reason code was returned from a 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.
AMQ4122W
The MQPUT request received an unexpected reason code of <insert_0>.
Severity
10 : Warning
Explanation
An unexpected reason code was returned from a 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.
AMQ4123I
The object <insert_0> was deleted successfully.
Severity
0 : Informational
Explanation
The object of the specified name has been successfully deleted.
Response
none.
AMQ4124W
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.
AMQ4125W
Put 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.
AMQ4126E
The value of one of the properties specified is not valid. The request was not processed.
Severity
20 : Error
Response
Specify a different value.
AMQ4127E
IBM 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 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 MQ Explorer.
Response
Ensure that the Eclipse workspace has not been corrupted.
AMQ4128E
Could not start the iKeyMan program.
Severity
30 : Error
Explanation
An error was encountered when trying to execute the iKeyMan program.
Response
Try again. If symptoms persist contact your System Administrator.
AMQ4129W
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 MQ Explorer to query the 'user.id'.
AMQ4130W
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.
AMQ4131W
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.
AMQ4132W
Are you sure that we 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 we want to stop the object.
AMQ4133W
When a queue manager is removed, 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 we want to remove the queue manager.
AMQ4134I
The default channel used by remote queue managers to administer this queue manager does not exist.
Do we 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 : Informational
Response
Select Yes to create the channel.
AMQ4135I
The default channel used by remote queue managers to administer this queue manager is SYSTEM.ADMIN.SVRCONN.
Do we want to delete this channel to prevent the queue manager being administered by other queue managers?
Severity
0 : Informational
Response
Select Yes to delete the channel.
AMQ4136W
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 we want to proceed?
Severity
10 : Warning
Explanation
Delete 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.
AMQ4137I
The default remote administration channel SYSTEM.ADMIN.SVRCONN has been deleted successfully.
Severity
0 : Informational
AMQ4138W
Are you sure that we want to import new settings that will overwrite the current settings? This operation cannot be undone.
Severity
10 : Warning
Explanation
Importing settings into MQ Explorer will overwrite the current settings.
Response
Continue only if we want to overwrite the current settings.
AMQ4139I
The default remote administration channel SYSTEM.ADMIN.SVRCONN was created successfully.
Severity
0 : Informational
AMQ4140W
The custom CipherSpec is not valid.
Severity
10 : Warning
AMQ4141W
The Distinguished Names specification is not valid.
Severity
10 : Warning
AMQ4142W
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.
AMQ4143W
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.
AMQ4144W
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.
AMQ4145W
An error occurred connecting to the remote queue manager using the intermediate queue manager. Are you sure that we want to show this queue manager in the folder anyway?
Ensure that the intermediate queue manager is available, and that the named remote queue manager is running and accessible from the intermediate queue manager. Ensure that we have the authority to connect to the remote queue manager, and ensure that the network is up and running. Select Yes if you believe that the problem can be resolved later. Select No if we want to correct the problem now and try again.
AMQ4146S
Eclipse cannot create or read the workspace for MQ Explorer.
Severity
40 : Severe
Explanation
A valid workspace is required to load MQ Explorer.
Response
Ensure that we can write to the Eclipse workspace.
AMQ4147S
Eclipse cannot write to the workspace for MQ Explorer in <insert_0>.
Severity
40 : Severe
Explanation
Write access to the workspace is required to load MQ Explorer.
Response
Ensure that we can write to the Eclipse workspace.
AMQ4148I
The object was created successfully.
Severity
0 : Informational
AMQ4149I
The request to start the listener was accepted.
Severity
0 : Informational
Explanation
A user request to start the listener was accepted by IBM MQ.
AMQ4150I
The request to stop the listener was accepted.
Severity
0 : Informational
Explanation
A user request to stop the listener was accepted by IBM MQ.
AMQ4151I
The request to start the service was accepted.
Severity
0 : Informational
Explanation
A user request to start the service was accepted by IBM MQ.
AMQ4152I
The request to stop the service was accepted.
Severity
0 : Informational
Explanation
A user request to stop the service was accepted by IBM MQ.
AMQ4153W
IBM MQ cannot stop the listener because the listener is not running.
Severity
10 : Warning
AMQ4154W
IBM 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.
AMQ4155W
IBM 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.
AMQ4156W
IBM MQ cannot stop the service because the service is not running.
Severity
10 : Warning
AMQ4157W
IBM MQ cannot start the service because the services is already running.
Severity
10 : Warning
AMQ4158W
IBM MQ cannot start the listener because the listener is already running.
Severity
10 : Warning
AMQ4159W
IBM 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.
AMQ4160W
IBM MQ cannot process the request because the executable specified cannot be started.
Severity
10 : Warning
Explanation
The request 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 IBM MQ user does not have sufficient access to execute the program.
If StdOut or StdErr are defined for the program, the IBM 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.
AMQ4161E
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.
AMQ4162I
The password cannot be cleared.
Severity
0 : Informational
Response
Try to clear the password again later.
AMQ4163W
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
AMQ4164I
The password was successfully changed.
Severity
0 : Informational
AMQ4165W
No password entered in the new password field. No change applied.
Severity
10 : Warning
Explanation
We must enter a new password in both the new and confirm password fields.
Response
Enter a new password in the new password field.
AMQ4166W
No password entered in the confirm new password field. No change applied.
Severity
10 : Warning
Explanation
We 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.
AMQ4167W
Passwords do not match. No change applied.
Severity
10 : Warning
Explanation
We 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.
AMQ4168E
IBM 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 IBM MQ and the queue manager in question are both running correctly.
AMQ4169E
IBM MQ failed to set the object filter.
Severity
20 : Error
Explanation
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 IBM MQ and the queue manager in question are both running correctly.
AMQ4170E
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.
AMQ4171E
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.
AMQ4172E
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.
AMQ4173W
IBM MQ cannot clear one or more Trace and FFST files.
Severity
10 : Warning
Explanation
IBM MQ cannot clear some files, because of one of the following:
The files are currently in use.
MQ Explorer does not have the appropriate access permission.
The trace or errors directories contain user-created subdirectories which MQ Explorer cannot delete.
Response
Check that tracing is disabled, and that 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 : Informational
AMQ4175E
IBM 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.
AMQ4176E
IBM 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. We might also see this message if you have specified a QSG disposition that is not valid or if you have specified an invalid topic object for a subscription.
Response
Check all values are valid for this type of object and try again. If we have altered the disposition of this object, check that the value is correct. If we are creating a new subscription, check that the topic object exists.
AMQ4177E
MQ Explorer cannot process your request because the connection to IBM MQ is quiescing.
Severity
20 : Error
Explanation
The connection to IBM MQ is quiescing, so no new information can be queried.
Response
Wait for the connection to end, then try reconnecting.
AMQ4178E
IBM MQ cannot process your request because there was a disposition conflict detected.
Severity
20 : Error
Explanation
A disposition conflict was detected. Please 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.
AMQ4179E
IBM 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 blank characters to pad to the right if necessary to ensure that exactly 20 characters are used.
AMQ4180E
IBM 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.
AMQ4181W
IBM MQ is not responding. Do we want to continue waiting?
Severity
10 : Warning
Explanation
IBM 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 MQ Explorer in an unknown state, so we should restart it.
Response
If you choose not to continue waiting, restart MQ Explorer, if the problem persists check for problem determination information.
AMQ4182W
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 IBM MQ and the queue manager in question are both running correctly.
AMQ4183W
Query failed because the queue manager is not in a queue-sharing group.
Severity
10 : Warning
Explanation
IBM 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.
AMQ4184W
The channel is not currently active.
Severity
10 : Warning
Explanation
The channel was not stopped because it is 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.
AMQ4185E
MQ Explorer 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.
AMQ4186E
MQ Explorer failed to export your settings.
Severity
20 : Error
Explanation
MQ Explorer encountered an error while writing to the specified export file.
Response
Check that we have write permissions for the specified export file and try again. If the error persists, examine the problem determination information to see if any details have been recorded.
AMQ4187
MQ Explorer has successfully imported your settings.
One or more of the imported settings require a restart for the changes to take effect. Press OK to restart MQ Explorer.
Severity
0 : Informational
Response
Restart MQ Explorer to apply the imported settings
AMQ4188W
Are you sure that we 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 we want to permanently remove the queue manager from the cluster.
AMQ4189E
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.
AMQ4190E
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.
AMQ4191E
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 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.
AMQ4192W
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 we do not inadvertently affect the definitions of other objects using the namelist. Then try removing the queue manager again.
AMQ4193E
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.
AMQ4194E
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 default transmission queue property (DefXmitQName) specifies a valid local queue.
AMQ4195W
MQ Explorer is now in an unknown state and should be restarted. Do we want to restart MQ Explorer?
Severity
10 : Warning
Explanation
We have chosen not to wait for IBM MQ to respond to a request. MQ Explorer is therefore in an unknown state and should be restarted.
Response
Restart MQ Explorer and try the operation again. If the problem persists check for problem determination information.
AMQ4196E
The command or operation is not valid against the type of object or queue specified
Severity
20 : Error
Explanation
We have attempted a command or operation against an object or queue whose type is not valid for the operation specified. For instance: browsing a remote queue; issuing the clear command against a queue whose type 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 whose type is valid for the operation requested.
AMQ4197E
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.
AMQ4198W
Queue manager <insert_0> has not been removed from one or more clusters.
If we do not remove the queue manager from the clusters, you might get unexpected errors
Do we 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 these clusters might expect the queue manager to be available.
Response
Remove the queue manager from the clusters it is a member of.
AMQ4199E
Queue manager <insert_0> is not available for client connection due to an SSL configuration error.
Severity
30 : 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.
AMQ4200E
There is a problem with the default configuration. Unable to display the Default Configuration window.
Severity
20 : Error
Explanation
There is a problem with IBM MQ.
Response
Use the 'Details>>' button to show further details about the problem and contact the systems administrator.
AMQ4201E
Unable to check if the computer exists.
Severity
20 : Error
Explanation
IBM MQ was unable to check if the computer name you entered exists on your computer domain.
Response
Retry the operation, if the problem persists contact the systems administrator.
AMQ4202W
Unable to contact the computer <insert_0>.
Severity
10 : Warning
Explanation
IBM MQ was unable to locate a computer with this name on your computer TCP/IP domain.
Response
Enter a different computer name.
AMQ4203E
Unable to set up the default configuration.
Severity
20 : Error
Explanation
IBM MQ was unable to set up the default configuration. This error may occur if IBM 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 the systems administrator.
AMQ4204E
Unable to join the default cluster.
Severity
20 : Error
Explanation
IBM MQ was unable to join your computer to the default cluster. This error may occur if IBM 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 the systems administrator.
AMQ4205E
Unable to allow remote administration of the queue manager.
Severity
20 : Error
Explanation
IBM MQ was unable change the configuration of our queue manager to allow it to be remotely administered. This error may occur if IBM 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 the systems administrator.
AMQ4206E
Unable to prevent remote administration of the queue manager.
Severity
20 : Error
Explanation
IBM MQ was unable change the configuration of our queue manager to prevent it from being remotely administered. This error may occur if IBM 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 the systems administrator.
AMQ4207E
The path specified is not valid.
Severity
20 : Error
Response
Check the path specified and try again.
AMQ4208I
Show this panel again the next time the queue manager is started?
Severity
0 : Informational
Explanation
We can choose whether we 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 we want the panel to be shown next time.
AMQ4209I
The TCP/IP name of the remote computer must not be your own computer name.
Severity
0 : Informational
Explanation
We have selected that the repository queue manager is on another computer, but you have entered the name of our own computer.
Response
Enter the correct name of the repository queue manager.
AMQ4210W
The command server must be active to complete this operation. Use IBM 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 IBM MQ Services to start the command server, then retry the operation.
AMQ4211W
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
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 the systems administrator.
AMQ4213W
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
IBM 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'.
AMQ4214W
The computer <insert_0> is not known on the network.
Severity
10 : Warning
Explanation
IBM MQ is unable to locate a computer with this name on your network.
Response
Enter a different computer name.
AMQ4215W
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
AMQ4216W
The IBM MQ services component does not have the authority it requires.
Severity
10 : Warning
AMQ4217W
The MQSeriesServices component does not have the authority to create the default configuration.
Severity
10 : Warning
AMQ4250W
No nickname supplied - Please 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
AMQ4251E
Cannot Initialise WinSock - TCP/IP may not be installed. Please install TCP/IP and try again
Severity
20 : Error
Explanation
Postcard was not able to initialise the interface to TCP/IP.
Response
Check that TCP/IP has been installed successfully. If the problem persists, refer to the systems administrator.
AMQ4252E
Cannot Find WinSock - TCP/IP may not be installed. Please 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 the systems administrator.
AMQ4253E
Cannot get fully qualified TCP/IP domain name - Please ensure that the TCP/IP protocol is configured.
Severity
20 : Error
Explanation
Postcard was not able to determine the TCP/IP domain name for the computer.
Response
Check that TCP/IP has been installed successfully. If the problem persists, refer to the systems administrator.
AMQ4254E
Failed to Allocate System Memory - Please contact the 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 the systems administrator.
AMQ4255W
Please 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
AMQ4256W
Please 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
AMQ4257E
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 might occur if IBM MQ is busy with another operation.
Response
Try to send the postcard again. If the problem persists contact the systems administrator.
AMQ4258E
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 might occur if IBM MQ is busy with another operation.
Response
Try to send the postcard again. If the problem persists contact the systems administrator.
AMQ4259E
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 might occur if IBM MQ is busy with another operation.
Response
If the problem persists contact the systems administrator.
AMQ4260E
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 might occur if IBM MQ is busy with another operation.
Response
If the problem persists contact the systems administrator.
AMQ4261E
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 might occur if IBM MQ is busy with another operation.
Response
Try to send the postcard again. If the problem persists contact the systems administrator.
AMQ4262E
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 might occur if IBM MQ is busy with another operation.
Response
Restart Postcard. If the problem persists contact the systems administrator.
AMQ4263E
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 might occur if IBM MQ is busy with another operation.
Response
Restart Postcard. If the problem persists contact the systems administrator.
AMQ4264E
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 might occur if IBM MQ is busy with another operation.
Response
If the problem persists contact the systems administrator.
AMQ4265E
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 might occur if IBM MQ is busy with another operation.
Response
If the problem persists contact the systems administrator.
AMQ4266W
Enter the message that we want to send to <insert_0>.
Severity
10 : Warning
Response
Enter the message in the Message text field.
AMQ4267E
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 a postcards by getting its data from the queue. This error might occur if IBM MQ is busy with another operation.
Response
Restart Postcard. If the problem persists contact the systems administrator.
AMQ4268E
Postcard is unable to contact the queue manager on the remote computer.
Verify that the default configuration is up and 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 up and running on the remote computer.
AMQ4269E
Unable to run Postcard because we do not have authority to use IBM MQ.
We must be in the mqm group to use IBM 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 the systems administrator.
AMQ4270E
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.
AMQ4271E
Unable to open a local queue called <insert_0> on the mailbox queue manager <insert_1>.
Use 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 MQ Explorer to create the queue, and restart Postcard.
AMQ4272E
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.
AMQ4273W
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'.
AMQ4274W
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 we want to send the message to the computer or the queue manager with this name, then click 'OK'.
AMQ4400W
MQ Explorer cannot administer the queue manager because the queue <insert_0> is not defined.
Severity
10 : Warning
Explanation
MQ Explorer uses the queue to administer queue managers.
Response
Define the queue and retry.
AMQ4401W
MQ Explorer cannot administer the queue manager because the user is not authorized to open the queue <insert_0>.
Severity
10 : Warning
Explanation
MQ Explorer uses the queue to administer this queue manager.
Response
Allow MQ Explorer to open the queue and retry.
AMQ4402W
The queue <insert_0> could not be opened for reason <insert_1>.
Severity
10 : Warning
Explanation
MQ Explorer uses the queue to administer this queue manager.
Response
Allow MQ Explorer to open the queue and retry.
AMQ4403W
The queue manager we are connecting to is at a higher command level than the intermediate queue manager we are using, which will cause some operations not to work. Are you sure that we 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 we 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 we 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.
AMQ4404W
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 we want to remove this queue manager?
Severity
10 : Warning
Explanation
To be able to display cluster information, the clustering component of 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 we want to remove the full repository even though it will prevent access to remaining partial repository information.
AMQ4405E
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 : 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.
If the error NullPointerException occurs when creating an object on a file system ensure that the user has the correct permissions to access the drive being used.
AMQ4406E
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.
AMQ4407E
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.
AMQ4408E
The NAME was missing from the JMS Administration data file.
Severity
20 : Error
Response
Check for FFSTs to determine the reason for the error.
AMQ4409E
A context with the nickname <insert_0> already exists.
Severity
20 : Error
Explanation
Nicknames for each context in the tree must be unique.
Response
Please choose a different nickname for this context.
AMQ4410E
Object type <insert_0> is not recognised when retrieving details for attribute <insert_1>.
Check for FFSTs to determine the reason for the error.
AMQ4413E
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.
AMQ4414E
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 : 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.
AMQ4415E
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 given 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.
AMQ4416E
The object <insert_0> could not be created because we 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.
AMQ4417E
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 obmitted. A host name can be specified instead of an IP address.
Response
Correct the Local address and try again.
AMQ4418E
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.
AMQ4419E
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.
AMQ4420E
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.
AMQ4421E
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.
AMQ4422E
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.
AMQ4423E
The object <insert_0> could not be deleted because we 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.
AMQ4424E
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.
AMQ4425E
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 MQ Explorer.
* Ensure that the queue manager is running.
* Ensure that 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 MQ Explorer, use the <insert_0> Select button to specify the queue manager again.
Severity
20 : Error
Explanation
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.
AMQ4426E
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.
AMQ4427E
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.
AMQ4428E
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.
AMQ4429E
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.
AMQ4430E
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.
AMQ4431E
The object <insert_0> could not be updated as we 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.
AMQ4432E
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.
AMQ4433E
The object <insert_0> could not be renamed because we 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.
AMQ4434E
The object <insert_0> could not be renamed to <insert_1> because the name already exists.
The JMS Administration plug-in encountered an unexpected JMS error.
Response
Check for FFSTs to determine the reason for the error.
AMQ4443E
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 : 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 MQ Explorer
Response
Either delete the object (using MQ Explorer), or repair it using some other tool.
AMQ4444E
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 : 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 MQ Explorer
Response
Either delete the object (using MQ Explorer), or repair it using some other tool.
AMQ4445E
The following error, reported by JNDI, prevented the transport being changed for the object: <insert_1>.
<insert_0>.
Severity
30 : Error
Explanation
The objects might have properties which prevent the transport being changed.
Response
Before trying to change the transport, change any conflicting properties.
AMQ4446W
You are about to remove the Initial context <insert_0> (<insert_1>) from MQ Explorer. Are you sure that we want to continue?
Severity
10 : Warning
Explanation
If you remove this Initial context, it will no longer be displayed in MQ Explorer. The context itself and its contents, will not be deleted.
Response
Continue only if we want to remove the context from MQ Explorer.
AMQ4447W
Are you sure that we want to delete the JMS object <insert_0> (<insert_1>)?
Severity
10 : Warning
Explanation
The JMS object will be permanently removed from the JMS Context.
Response
Continue only if we want to permanently delete the object.
AMQ4448E
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 given attributes are inconsistent.
Response
Change one or both of the attributes to make them consistent.
AMQ4449E
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 MQ Explorer and add it again.
AMQ4450E
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.
AMQ4451E
The <insert_0> property on the JMS object <insert_1> is set to <insert_2> but 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, MQ Explorer must be connected to it.
Response
Add the required queue manager to MQ Explorer and ensure that it is connected before attempting this operation again.
AMQ4452E
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.
AMQ4453E
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 given by the StorageClass queue attribute.
AMQ4454E
There is an error associated with this channel.
Severity
20 : Error
Explanation
A possible error cause is that the channel references a hostname that cannot be resolved.
Response
Ensure that all of the properties for the channel have been defined correctly. Ensure that the channel references a hostname that can be resolved.
AMQ4455E
The Distinguished Name specified is not valid.
Severity
20 : Error
Explanation
The Distinguished Name specified is not in the correct format.
An example of the format of a Distinguished Name is CN=John, O=IBM, OU=Test, C=GB
For more information look at Distinguished Names in the Security section of the IBM MQ Information center.
Response
Ensure that a valid Distinguished Name is specified.
AMQ4456E
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.
AMQ4457E
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.
AMQ4458E
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.
AMQ4459E
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 MQ Explorer, or modify the JMS object property. Try the operation again.
AMQ4460I
The default remote administration listener LISTENER.TCP was created successfully.
Severity
0 : Informational
AMQ4461W
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.
AMQ4462I
Successfully added queue manager <insert_0>.
Severity
0 : Informational
Explanation
The requested queue manager was successfully added to the list of known queue managers in MQ Explorer.
AMQ4463E
The <insert_0> attribute on JMS object <insert_1> is set to <insert_2> but this is not a valid name for a queue manager.
Severity
20 : Error
Explanation
The attribute must only contain valid characters and be of the appropriate length for a queue manager name.
Response
Modify the attribute to the name of a real MQ Queue Manager.
AMQ4464E
An error occurred while trying to connect to the queue manager. 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 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 MQ Explorer objects. If we want your schemes to contain these new attributes, we must manually add them to each scheme.
Severity
0 : Informational
AMQ4466I
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 we want to add this queue manager?
Severity
0 : Informational
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.
AMQ4467W
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.
AMQ4468W
The filter named <insert_0> is used by the following automatic sets: <insert_1> Are you sure that we 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 we want to permanently delete the filter.
AMQ4469W
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.
AMQ4470E
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 we can enter the word 'unspecified'.
Response
Correct the provider version and try again.
AMQ4471W
Are you sure that we 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 we want to permanently delete the set.
AMQ4472W
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.
AMQ4473W
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
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.
AMQ4474W
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.
AMQ4475W
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
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.
AMQ4476W
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
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.
AMQ4477W
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 and that there are no invalid characters in the topic string.
AMQ4478W
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.
AMQ4479E
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.
AMQ4480E
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.
AMQ4481E
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.
AMQ4482E
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.
AMQ4483E
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.
AMQ4484E
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.
AMQ4485W
This action removes the retained publication from the topic string <insert_0> on the selected queue manager only.
Are you sure we want to clear the retained publication?
Severity
10 : Warning
Explanation
A confirmation is required before the retained publication is cleared.
Response
Continue only if we want to permanently clear the retained publication on this topic string.
AMQ4486I
The retained publication on the topic string <insert_0> has been successfully cleared.
Severity
0 : Informational
AMQ4487E
Error initialising <insert_0>.
Severity
30 : Error
Explanation
An error occurred while starting this application.
Response
Check that the IBM MQ runtime libraries are available and the PATH system environment variable includes the directory for these runtime libraries.)
AMQ4488W
Unable to locate a Web browser, information center, or IBM Eclipse Help System to display the help.
Severity
10 : Warning
Explanation
To launch the help system, the Web browser or information center or IBM Eclipse Help System must be included in the PATH system environment variable.
Response
Install the information center or IBM Eclipse Help System or set the available Web browser on the system path. Re-launch the application and try again.
AMQ4489W
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.
AMQ4490W
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.
AMQ4491W
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.
AMQ4492W
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.
AMQ4493W
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 IBM MQ is installed.
AMQ4494W
Unable to locate a web browser in the system path.
Severity
10 : Warning
Explanation
The application failed to locate a web browser in the system path.
Response
Check that a suitable web browser is specified in the system path.
AMQ4495W
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 we 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 behaviour set to Force.
Response
Check the Topic definitions before resynchronizing the proxy subscriptions.
AMQ4496
The request to refresh the proxy subscriptions was accepted by IBM MQ.
Severity
0 : Informational
AMQ4497W
The topic string has already been specified for another topic. Enter a different topic string.
Severity
10 : Warning
Response
Enter a different topic string.
AMQ4498W
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 we want to clear the retained publication?
Severity
10 : Warning
Explanation
A confirmation is required before the retained publication is cleared.
Response
Continue only if we want to permanently clear the retained publication on this topic string.
AMQ4499W
The queue attribute for the JMS queue <insert_0> is empty. A queue name must 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.
AMQ4500W
Are you sure that we want to forcibly remove queue manager <insert_0> from cluster <insert_1>?
Severity
10 : Warning
Explanation
We 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 we want to forcibly remove the queue manager.
AMQ4501
The request to remove the queue manager from the cluster has been submitted. This will be displayed in the MQ Explorer when the connected MQ repository has completed its cluster removal processing. There may be a further delay before all queue manager repositories have been updated.
Severity
0 : Informational
Explanation
The queue manager will still appear as a member of the cluster until the configuration changes have been sent across the MQ network and the cluster channels to the queue manager have become inactive, which can take a long time depending on the size of the MQ network. Note that when the MQ Explorer display has updated to indicate that the connected MQ repository has completed its cluster removal processing, other queue manager repositories may still be processing the request. No attempt should be made to add the queue manager back into the cluster until all of this processing has completed across the entire MQ network.
AMQ4502W
We 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, we must join the queue manager to the cluster.
AMQ4503W
The list of values is too long.
Severity
10 : Warning
Explanation
The list of values that we have entered is too long. The maximum number of characters allowed for this value is <insert_0>.
AMQ4504W
The value is too long.
Severity
10 : Warning
Explanation
We have entered a value containing too many characters. The maximum number of characters allowed for each value of this attribute is <insert_0>.
AMQ4505W
There are too many entries in the list.
Severity
10 : Warning
Explanation
We have entered too many values in the list. The maximum number of values is <insert_0>.
AMQ4506W
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, we can choose to forcibly remove the queue manager from the cluster.
The connection information available for the remote queue manager uses a communication protocol other than TCP/IP. 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, we can choose to forcibly remove the queue manager from the cluster.
AMQ4508I
The queue manager successfully left the cluster.
Severity
0 : Informational
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 : Informational
AMQ4510
The request to resume membership of the cluster has been accepted.
Severity
0 : Informational
AMQ4511I
The queue manager is not a member of the cluster.
Severity
0 : Informational
AMQ4512I
An error occurred while performing a cluster operation. The operation failed with error <insert_0>.
Severity
0 : Informational
AMQ4513
The request to refresh the information about the cluster has been accepted.
Severity
0 : Informational
AMQ4514W
The queue manager is not a member of cluster <insert_0>.
Severity
10 : Warning
Explanation
The object that we 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.
AMQ4515W
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.
AMQ4516W
Cluster workload exit error.
Severity
10 : Warning
Explanation
The queue manager cluster workload exit failed unexpectedly or did not respond in time.
AMQ4517W
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.
AMQ4518W
AMQ4518=A call was stopped by the cluster exit.
Severity
10 : Warning
Explanation
The queue manager cluster workload exit rejected a call to open or put a message onto a cluster queue.
AMQ4519W
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.
AMQ4520W
MQ Explorer could not initialize TCP/IP. Administration of remote queue managers and clusters is not possible.
Severity
10 : Warning
AMQ4521W
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
To use a comma as part of a value, enclose the value in double quotes.
AMQ4522W
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 properties.
Response
Ensure that the default objects exist for the queue manager.
AMQ4523W
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 manager properties.
Response
Ensure that the default objects exist for the queue manager.
AMQ4524W
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 we want to remove this queue manager?
Severity
10 : Warning
Explanation
To be able to display cluster information, the clustering component of 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 we want to remove the source repository, even though it will prevent access to remaining cluster information.
AMQ4525W
Cluster workload exit load error.
Severity
10 : Warning
Explanation
The queue manager cluster workload exit failed to load.
Response
Check that the cluster workload exit exists and the name has been specified correctly.
AMQ4526I
Further plug-ins were enabled during the import; do we want to import their settings?
Severity
0 : Informational
Explanation
The import file contains settings for the plug-ins enabled during the import.
Response
Select Yes to import the settings.
AMQ4527W
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.
AMQ4528E
The file selected does not contain any import settings.
Severity
20 : Error
Response
Select another file and try again.
AMQ4529E
Put message failed. The page set identifier 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 identifier specified in the storage class object defined for the queue, is not valid.
Response
Correct the page set identifier value in the storage class definition used by this queue and try again. If the error persists, contact your System Administrator.
AMQ4530I
The request to create and start a new z/OS listener was accepted.
Severity
0 : Informational
Explanation
A user request to create the listener was accepted by IBM MQ.
AMQ4531E
The subscription is in use.
Severity
20 : Error
Explanation
An attempt was made to delete or change a subscription that is in use.
Response
Ensure that the subscription is not in use and try again.
AMQ4532E
Group units of recovery can not be enabled due to a configuration error.
Severity
30 : Error
Explanation
When group units of recovery are enabled, a number of configuration checks are performed to ensure the configuration steps have been completed. One of these checks has failed so group units of recovery cannot be enabled.
The checks could fail for the following reasons
1. This queue manager is not a member of a queue-sharing group.
2. The SYSTEM.QSG.UR.RESOLUTION.QUEUE does not exist.
3. The SYSTEM.QSG.UR.RESOLUTION.QUEUE does not support persistent messages.
4. The SYSTEM.QSG.UR.RESOLUTION.QUEUE is not indexed by correlation id.
5. The SYSTEM.QSG.UR.RESOLUTION.QUEUE does not reside on the system application coupling facility structure, CSQSYSAPPL.
6. The queue manager name is the same as the name of the queue-sharing group.
Response
Ensure that the configuration steps are complete and try again.
AMQ4533E
The value specified for one of the attributes is not allowed because the installation and customization options chosen do not allow all functions to be used.
Severity
30 : Error
Explanation
When the queue manager is operating in compatibility mode (OPMODE=COMPAT), some functions will not be available. Precise details are dependent on the release of code being run by the queue manager, and the release of code which the queue manager has been migrated from.
Response
Further details of migration restrictions in compatibility mode may be found in the migration guide.
AMQ4534I
The subscription identity was removed successfully.
Severity
0 : Informational
AMQ4535
No retained publication exists for this topic.
Severity
0 : Informational
AMQ4536I
The object was deregistered successfully.
Severity
0 : Informational
AMQ4537W
There are no subscription identities to remove.
Severity
10 : Warning
AMQ4538I
Retained publication on topic <insert_0> cleared successfully.
Severity
0 : Informational
AMQ4539E
Could not export test results to <insert_0>.
Severity
20 : Error
Explanation
An error occurred when attempting to write test results to the specified file.
Response
Check that the path specified is correct and accessible.
AMQ4540W
We have selected the option to grant <insert_0> full administrative authority on queue manager <insert_1>.
Are you sure that <insert_0> requires this level of authority?
Severity
10 : Warning
Explanation
Confirmation is required before this level of authority is granted.
Response
Ensure that the user or group specified requires this level of authority before you proceed.
AMQ4541
MQ Explorer has successfully imported your settings.
Severity
0 : Informational
AMQ4542
MQ Explorer has successfully exported your settings to <insert_0>.
Severity
0 : Informational
AMQ4543W
The selected CipherSpec is not supported by the current GSKit version.
Severity
10 : Warning
Explanation
Some CipherSpecs require the queue manager to use an alternative GSKit socket library version.
Response
Install and enable a GSKit version which supports the specified CipherSpec. Refer to the IBM MQ Security documentation for more information about CipherSpec support.
AMQ4544I
The authority was granted successfully.
Severity
0 : Informational
Explanation
This procedure grants the requested access in addition to whatever access the user or group currently has. If you grant read-only access to a user or group, that user or group does not lose any existing administrative authorities.
AMQ4545W
Are you sure that we want to delete the <insert_0> selected objects?
Severity
10 : Warning
Explanation
A confirmation is required before the selected objects are deleted.
Response
Continue only if we want to permanently delete the objects.
AMQ4546W
The object named <insert_0> is in an unknown state and may be a system object.
Are you sure that we want to continue and attempt to delete the object?
Severity
10 : Warning
Explanation
The object may be damaged and the delete operation may not be successful.
Response
Attempt to delete the object. Alternatively, examine the queue manager and client error logs for messages explaining the cause of the problem.
AMQ4547E
Inconsistent use of installations detected.
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 or LIBPATH) is set correctly.
AMQ4548E
The requested web page <insert_0> could not be displayed.
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.
AMQ4549W
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.
The Loss of coupling facility connectivity attribute can not be set to Tolerate because one of the queue managers in the queue sharing group is not at command level 710 or later.
Response
To use the Loss of connectivity function, ensure that all the queue managers in the queue sharing group are at the command level 710 or later
AMQ4551E
Incorrect Custom attribute format.
Severity
20 : Error
Explanation
This attribute is used for custom configuration parameters. The attribute can contain a list of name-value pairs which must be separated by a comma.
Each name-value pair in the list consists of a name followed by a value in parentheses, like this: ABC(XYZ).
If the value contains spaces or parentheses, the value must be enclosed in a pair of single quotation marks, like this: ABC('X(Y)').
See the IBM MQ Information Center for more information about using this attribute.
Response
Check that name-value pairs are separated by a comma, that values which contain spaces or parentheses are enclosed in single quotation marks, and that all parentheses and single quotation marks are in pairs.
AMQ4552
New attributes have been added to MQ Explorer objects and the standard scheme has been altered. Previous standard schemes have been saved and can be selected from the schemes menu. If we want your schemes to contain these new attributes, we must manually add them to each scheme.
Severity
0 : Informational
AMQ4553E
IBM MQ cannot process the request because the Generic data set name specified in the Message offload page is not unique.
Severity
20 : Error
Explanation
When creating or modifying a Coupling facility object a unique generic data set name is required which cannot be copied from an existing Coupling facility.
Response
Update the Generic data set name and try again.
AMQ4554W
There are no tests results available to export.
Severity
10 : Warning
Explanation
The table used to export the test results has no test result data available, this could be because no tests have been run or the test results data has been cleared or deleted.
Response
Check that the "WMQ Explorer Tests Data" project exists and that test result data is available.
AMQ4555E
The Suite B Strength parameter is not valid.
Severity
20 : Error
Response
Specify a valid Suite B Strength combination for this parameter and try again.
The specified queue is not allowed to be used as the default transmission queue because it is reserved for use exclusively by clustering.
Response
Specify a valid queue name.
AMQ4557E
Unexpected error saving state data to file.
Severity
30 : Error
Explanation
An error occurred attempting to write to a file in the workspace.
Response
Examine the problem determination information to see if any information has been recorded.
AMQ4558E
Unable to create topic because Publish/Subscribe clustering is disabled.
Severity
20 : Error
Explanation
Cluster topics cannot be created or altered because the queue manager attribute 'Publish/Subscribe clustering' is set to 'Disabled'.
Response
To enable Publish/Subscribe clustering change the attribute to 'Enabled' on all queue managers participating in the cluster.
AMQ4559E
Unable to modify Publish/Subscribe clustering attribute because cluster topics exist.
Severity
20 : Error
Explanation
The queue manager attribute 'Publish/Subscribe clustering' cannot be set to 'Disabled' because one or more cluster topics already exist.
Response
To disable publish/subscribe activity within this cluster, first delete all cluster topic objects.
AMQ4560E
Plug-in <insert_0> has been disabled because the following error occurred: <insert_1>.
Severity
20 : Error
Response
Examine the problem determination information for more details of the error.
AMQ4561E
The policy could not be created. Verify the SYSTEM.PROTECTION.POLICY.QUEUE has been created.
Severity
20 : Error
Response
Examine the problem determination information for more details of the error.
AMQ4562W
No response was received from the queue manager to report the outcome of the Refresh SSL operation within the timeout period. MQ Explorer is no longer monitoring the status of this operation, which can take up to 10 minutes to complete.
Severity
10 : Warning
Explanation
When the Refresh SSL operation is performed, all running SSL channels are stopped and restarted. The operation can potentially take 10 minutes for the operation to finish. MQ Explorer will only wait for 30 seconds.
Response
Check the IBM MQ queue manager error logs for messages reporting the status of the operation.
AMQ4563E
Cluster channel names attribute error.
Severity
20 : Error
Explanation
The Cluster channel names attribute is only allowed for transmission queues. On z/OS, the transmission queue must also be shareable, be indexed by correlation identifier and must not be a dynamic or a shared queue.
Response
Check that the combination specified is valid for the object and try again.
AMQ4564E
Unable to create a new durable subscription.
Severity
20 : Error
Explanation
This can be caused by any of the following reasons:
1. The topic subscribed to is defined as DURSUB(NO).
2. The queue named SYSTEM.DURABLE.SUBSCRIBER.QUEUE is not available. This can be because the queue is full, is put inhibited, or does not exist.
3. The topic subscribed to is defined as both MCAST(ONLY) and DURSUB(YES) (or DURSUB(ASPARENT) and the parent is DURSUB(YES)).
AMQ4565E
Cluster topic modification error.
Severity
20 : Error
Explanation
An attempt to modify a topic definition's cluster route or cluster name value has failed due to the topic definition currently being in a named cluster.
Response
First quiesce publish/subscribe messaging for this topic. Remove the topic from the cluster by setting the cluster name to blank before modifying the cluster route and cluster name. For a period the topic will not be clustered and as such will not propagate publications to all subscribers in the cluster during that period. Resume publish/subscribe messaging.
AMQ4566E
Clustered topic conflict.
Severity
20 : Error
Explanation
A clustered topic cannot be defined due to another clustered topic already existing above or below it in the topic tree that would conflict with this topic's attributes.
Response
Check that the combination specified is valid for the object and try again.
The queue manager attribute 'Default cluster transmission queue' cannot be set to 'Queue for each channel' because the model queue named SYSTEM.CLUSTER.TRANSMIT.MODEL.QUEUE does not exist or has been defined incorrectly. On z/OS, the model transmission queue must be shareable, be indexed by correlation identifier, have a definition type of permanent dynamic and must not be a shared queue.
Response
Check that the model queue has been defined correctly and try again. On z/OS, the definition for the model queue can be found in the supplied sample CSQ4INSX.
AMQ4568E
No response was received from the queue manager to report the outcome of the Refresh operation within the timeout period.
Severity
20 : Error
Explanation
This operation has not been completed. MQ Explorer will only wait for 30 seconds.
Response
Check the IBM MQ queue manager error logs for messages reporting the status of the operation.
AMQ4569W
Could not establish a connection to the queue manager as a connection is already in progress.
Severity
10 : Warning
Explanation
A connection to the specified remote queue manager is already in progress but has not completed.
Response
Wait until the connection has completed and then try again.
AMQ4570E
The requested application is either not installed or could not be launched.
Severity
20 : Error
Explanation
Applications such as Default Configuration and Postcard are installed by the Server feature of MQ. Applications will fail to launch from the MQ Explorer Welcome Page unless the appropriate feature has been installed.
Response
Check that the corresponding product feature has been installed successfully. If symptoms persist, contact your System Administrator.
AMQ4571W
Are you sure that we want to change the location of the Key Repository for queue manager <insert_0>?
Severity
10 : Warning
Explanation
We might prevent the queue manager from starting if we change the Key Repository field to a location which is not valid.
Response
Ensure that the location specified is correct before continuing.
AMQ4572I
The request to refresh the information about all clusters has been accepted.
Severity
0 : Informational
AMQ4573E
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
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
AMQ4574E
MQ Explorer is already running.
Severity
30 : Error
AMQ4575E
An error occurred initializing the data model.
Severity
30 : Error
AMQ4576E
The working directory <insert_0> is not valid.
Severity
30 : Error
AMQ4577E
An error occurred initializing the process.
Severity
30 : Error
AMQ4578E
An error occurred loading the messages file <insert_0>.
Severity
30 : Error
AMQ4579E
An error occurred loading the system libraries.
Severity
30 : Error
AMQ4580E
An internal method detected an unexpected system return code. The method <insert_0> returned <insert_1>.
Severity
30 : Error
Response
Examine the problem determination information on this computer to establish the cause of the error.
AMQ4581E
Parameter check failed on the internal function <insert_0>. The error was <insert_1>.
Severity
30 : Error
Response
Examine the problem determination information on this computer to establish the cause of the error.
AMQ4582E
Queue manager <insert_0> is not available for client connection.
Severity
30 : Error
Response
Ensure the queue manager is running and is configured to accept remote connections.
AMQ4583E
Queue manager <insert_0> is not available for connection.
Severity
30 : Error
Response
Ensure the queue manager is running.
AMQ4584E
Queue manager <insert_0> is not available for cluster connection.
Severity
30 : 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.
AMQ4585E
An internal method <insert_0> encountered an unexpected error.
Severity
30 : Error
Response
Examine the problem determination information on this computer to establish the cause of the error.
AMQ4586E
The attempt to create the URL for file <insert_0> failed.
Severity
30 : Error
Explanation
The file name specified was not recognized.
Response
Ensure that the file exists at the specified location and can be read.
AMQ4587E
The attempt to read from URL <insert_0> failed.
Severity
30 : 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.
AMQ4588E
The attempt to read from URL <insert_0> failed.
Severity
30 : 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.
AMQ4589W
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.
AMQ4590E
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.
If the error persists, examine the problem determination information to see if any details have been recorded.
AMQ4596W
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.
AMQ4597W
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.
AMQ4598W
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.
AMQ4599W
Change the FIPS required setting will affect all client connections using SSL and requires MQ Explorer to be restarted. Are you sure that we want to restart 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 MQ Explorer to apply this change.
AMQ4600W
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.
AMQ4601W
Do we 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.
AMQ4602W
Unable to validate the given key for password store <insert_0>.
Severity
10 : Warning
Explanation
The password store cannot be opened with the given key.
Response
Enter a different key and try the operation again.
AMQ4603W
Invalid password store <insert_0>.
Severity
10 : Warning
Explanation
The given file name is the name of a directory.
Response
Enter a valid file name.
AMQ4604W
Password store <insert_0> is read-only.
Severity
10 : Warning
Explanation
MQ Explorer only has read access to the given file name.
Response
Specify the name of a file that has both read and write access.
AMQ4605W
Format of password store <insert_0> is unknown.
Severity
10 : Warning
Explanation
The contents of the specified password store file is unknown. This might be an existing XML file which has not been created as a password store, or it might be a non-XML file.
Response
Specify an existing password store file name or specify a new XML file.
AMQ4606W
Password store <insert_0> was not opened.
Severity
10 : Warning
Explanation
The user chose not to open the password store.
Response
Restart MQ Explorer to open the password store or use the Password preference page.
AMQ4607W
The 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.
AMQ4608E
The specified destination does not exist.
Severity
30 : Error
Explanation
An error occurred trying to create a new subscription.
Response
Change the destination name and try again.
AMQ4609I
The listener was started.
Severity
0 : Informational
Explanation
The request to start a listener was successful.
AMQ4610W
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.
AMQ4611I
Applying these changes will disconnect the queue manager and reconnect with the new details. Do we want to continue?
Severity
0 : Informational
Explanation
Connection details to a connected queue manager have been changed. Without reconnecting, the current connection details cannot be seen.
Response
Select Yes to continue or No to cancel the changes.
AMQ4612I
Are you sure that we want to stop the standby instance for <insert_0>?
Severity
0 : Informational
Explanation
A confirmation is required before the specified queue manager instance is stopped.
Response
Continue only if we want to stop the object.
AMQ4613I
Please confirm <insert_0> is a multi-instance queue manager.
Severity
0 : Informational
Explanation
The connection is currently defined for a single instance queue manager. A confirmation is required before adding new instance details for the specified queue manager.
Response
Continue only if we want to add more instance details. To undo this change, we will need to remove the queue manager from the navigator view and use the Add Remote Queue Manager wizard to add the queue manager again.
AMQ4614
An older 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 : Informational
Explanation
A previous connection to this queue manager has been successful; the queue manager is the same but the command level is now lower. The version of IBM MQ has been changed.
AMQ4615W
A different queue manager identifier (UUID) has been found when connecting to <insert_0>. Do we want to replace the current connection?
Severity
10 : Warning
Explanation
A previous connection to this queue manager has been successful; the queue manager name is the same but the UUID is now different. The queue manager has been deleted and re-created with the same name.
Response
Either click Yes to replace the current connection, or remove the queue manager from the navigator view and use the Add Remote Queue Manager wizard to add the queue manager again.
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 : Informational
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 IBM MQ has been changed.
AMQ4617W
A different command level has been found when connecting to <insert_0>.
Severity
10 : Warning
Explanation
A previous connection to this queue manager has been successful; the queue manager is the same but the command level is different. The version of IBM MQ has been changed.
Response
To resolve this we need to use the Connect menu action on this individual queue manager.
AMQ4618W
A different queue manager identifier (UUID) has been found when connecting to <insert_0>.
Severity
10 : Warning
Explanation
A previous connection to this queue manager has been successful; the queue manager name is the same but the UUID is now different. The queue manager has been deleted and re-created with the same name.
Response
Remove the queue manager from the navigator view and use the Add Remote Queue Manager wizard to add the queue manager again.
AMQ4619E
The specified destination object is not a valid subscription destination.
Severity
30 : Error
Explanation
An error occurred trying to create a new subscription.
Response
Change the destination name and try again.
AMQ4620E
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.
AMQ4621E
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.
AMQ4622E
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.
AMQ4623E
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.
AMQ4624E
A Channel Authentication Record contained an invalid address.
Severity
20 : Error
Explanation
A Channel Authentication Record contained an invalid address, or invalid wildcard pattern to match against addresses.
Response
Specify a valid IP address.
AMQ4625E
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.
AMQ4626E
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.
AMQ4627E
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.
AMQ4628W
Transfer local queue manager <insert_0> to this installation? Queue managers cannot be transferred if they are running or if they are from a later version of IBM MQ.
Severity
10 : Warning
Explanation
The queue manager is currently associated with another installation of IBM MQ. In order to successfully transfer a queue manager it must be stopped.
Additionally we can only transfer queue managers to equal or later versions of IBM MQ.
Response
Continue only if we want to change the associated installation for this queue manager. Once you have started the queue manager on this installation,
it is not possible to transfer it back to earlier versions of IBM MQ.
AMQ4629W
The specified MCA User ID is not supported.
Severity
10 : Warning
Explanation
The MCA User ID value contained characters that are not allowed for program names on the platform in question.
Response
Change the property to match the supported characters and try the operation again.
AMQ4630E
Queue manager <insert_0> is not available for the intermediate queue manager connection.
Severity
30 : Error
Explanation
A queue manger with the corresponding queue manager identifier (UUID) could not be found
Response
Ensure the queue manager is running, if the problem persists remove the intermediate queue manager connection from the navigator view and use the Add Remote Queue Manager wizard to add the intermediate queue manager again.
AMQ4631E
A certificate label cannot be specified for an SSL 3.0 channel.
Severity
20 : Error
Explanation
A certificate label was provided when using an SSL 3.0 Cipher spec.
Response
Remove the certificate label. Then try the request again.
AMQ4632E
Type of remote channel not suitable for action requested.
Severity
30 : Error
Explanation
The operation requested cannot be performed because the channel definition on the remote machine is not of a suitable type.
Response
Check that the channel name is specified correctly. If it is, check that the remote channel has been defined correctly.
AMQ4633W
One or more of the queue managers selected to be updated is using a CCDT connection. When using a CCDT connection the Cipher Suite is determined by the CCDT entry and will not be updated by this wizard. Any selected queue managers using a direct client connection will be updated with the new Cipher Suite.
Severity
10 : Warning
Explanation
CCDT connections use the information selected within the CCDT to determine the SSL Cipher Suite, and so this information cannot be altered by this wizard
AMQ4634E
Could not change the attributes of the topic object.
Severity
20 : Error
Explanation
Changes to topics on the $SYS/MQ/ tree branch are restricted. One or more attributes are not supported.
Response
Modify the configuration to adhere to the documented restrictions.
AMQ4635E
The selected CipherSpec is not valid.
Severity
20 : Error
Explanation
The CipherSpec is not valid for this queue manager and may have been deprecated. Note that IBM may need to deprecate the use of CipherSpecs via product maintenance in response to a security vulnerability.
Response
Select another CipherSpec and try again.
AMQ4636I
The request to purge the channel was accepted.
Severity
0 : Informational
Explanation
A channel has been purged successfully by IBM MQ as the result of a user request.
AMQ4637E
The requested AMQP function is not available.
Severity
20 : Error
Explanation
MQ Explorer was not able to carry out the function requested.
Response
Ensure the AMQP component is installed correctly and the service running. If symptoms persist, contact your System Administrator.
AMQ4638W
The requested policy operation succeeded, however there are messages on the queue.
Severity
10 : Warning
Explanation
If the protection required by the policy has become more restrictive, this could lead to application security errors when browsing or removing the existing messages, alternatively if protection has been removed it could lead to applications retrieving an unusable message payload.
Response
Consider redefining the policy with toleration enabled to handle the existing messages.
AMQ4639E
The queue manager connection limit has been exceeded.
Severity
20 : Error
Explanation
MQ Explorer was not able to connect to the queue manager because the connection limit has been exceeded.
Response
Wait for an application to disconnect from the queue manager and try again.
AMQ4700W
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.
AMQ4701W
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.
AMQ4702W
The current filter is 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.
AMQ4808W
Unknown <insert_0> <insert_1>.
Severity
10 : Warning
Explanation
The named entity for the given type is not defined on the system.
Response
Make sure the entity is defined and it matches the type of entity.
AMQ4809W
You are about to delete the authority for <insert_0> to <insert_1>. Are you sure that we want to continue?
Severity
10 : Warning
Explanation
We must confirm that we want to delete the specified authority. The entity name and object name are provided in the message.
Response
Continue only if we want to permanently delete the authority.
AMQ4810I
The authority for <insert_0> to <insert_1> was deleted successfully.
Severity
0 : Informational
AMQ4811I
The authority was created successfully.
Severity
0 : Informational
AMQ4812W
You are about to delete all create authorities for <insert_0>. Are you sure that we want to continue?
Severity
10 : Warning
Explanation
We must confirm that we want to delete the specified authority. The entity name is provided in the message.
Response
Continue only if we want to permanently delete the authority.
AMQ4813W
You are about to refresh SSL security for <insert_0>. This might affect the running status of active channels. Are you sure that we 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.
You do not have write access to the given file name.
Response
Check that your userid has write access to the file name.
AMQ4820
A file called <insert_0> already exists. Do we want to replace this file?
Severity
0 : Informational
Response
Confirm that we want to replace the file.
AMQ4821
This action replaces an existing authority record. Are you sure that we want to continue?
Severity
0 : Informational
Explanation
An explicit authority record already exists for this entity. Creating a new authority record replaces the existing authority record.
Response
Continue only if we want replace the existing authority record.
AMQ4822I
We must enter a specific profile name when using an entity name.
Severity
0 : Informational
Response
Enter a specific profile name.
AMQ4823
Profile <insert_0> does not exist.
Severity
0 : Informational
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 : Informational
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.
AMQ4825W
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.
AMQ4826W
There is a security profile case conflict.
Severity
10 : Warning
Explanation
The security profile case attribute of the queue manager is different to 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.
AMQ4827W
The Publish/Subscribe broker is not responding within timeout period.
Severity
10 : Warning
Explanation
The Publish/Subscribe broker has not responded within the specified timeout period.
Response
Ensure that the Publish/Subscribe broker service is running.
AMQ4828I
Connection details <insert_0> to <insert_1> already exist.
Severity
0 : Informational
Explanation
The new set of connection details are already defined for the specified queue manager.
Response
Use a different host name or ip-address and port number.
AMQ4829I
You are about to remove the connection details <insert_0> to <insert_1>. Are you sure that we want to continue?
Severity
0 : Informational
Explanation
We must confirm that we want to remove the specified connection details.
Response
Continue only if we want to permanently remove the connection details used by MQ Explorer.
AMQ4830W
You are about to add authority for a generic profile name <insert_0>. Are you sure that we 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 we want to add authority for a generic profile name.
AMQ4831W
Security refresh or reverification not processed, security switch set OFF.
Severity
10 : Warning
Explanation
A Reverify Security command was issued, but either the subsystem security switch is off, so there are no internal control tables to flag for reverification, or the security switch for the requested class or the subsystem security switch is off.
AMQ4832W
A Refresh Security command was issued, but the case currently in use differs from the system setting.
Severity
10 : Warning
Explanation
A Refresh Security PCF command was issued, but the case currently in use differs from the system setting and if refreshed would result in the set of classes using different case settings.
Response
Check that the class used is set up correctly and that the system setting is correct. If a change in case setting is required, issue the REFRESH SECURITY(*) command to change all classes.
AMQ4833W
Changes made to the configuration controlling connection authentication will become effective. Are you sure that we want to continue?
Severity
10 : Warning
Explanation
A confirmation is required before the refresh command is issued.
Response
Continue only if we want to refresh the authentication service security component.
AMQ4850W
Further tests cannot be run because the MQ Explorer Test Plug-in is currently in use.
Severity
10 : Warning
Explanation
We 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.
AMQ4851I
There are no tests available to run.
Severity
0 : Informational
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 different configuration which has tests enabled, or try testing from a different point to ensure that there are appropriate tests available.
AMQ4852E
MQ Explorer Test Plug-in initialization error.
Severity
20 : Error
Explanation
An error has occurred during initialization of the Tests Plug-in. This might cause problems with running tests.
Response
Examine the problem determination information to see if any details have been recorded.
AMQ4853I
The test cannot be disabled because no configurations currently have this test enabled.
Severity
0 : Informational
Response
No further action is required; the test is already disabled.
AMQ4854I
Finished running <insert_0> tests. Review the results in the Test Results view.
Severity
0 : Informational
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
The test run has finished; review the warning and error information in the Test Results view and take appropriate action.
AMQ4855I
The test run was canceled.
Severity
0 : Informational
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.
AMQ4856W
Are you sure that we 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 we want to clear the subscription.
AMQ4857I
The Subscription was cleared.
Severity
0 : Informational
Explanation
The subscription was cleared to a well defined state. For a managed destination any messages already queued to the destination were deleted.
AMQ4858I
A parameter change has been detected.
Severity
0 : Informational
Explanation
A parameter has been changed without using MQ Explorer.
Response
Refresh the MQ Explorer view and try the operation again.
AMQ4859I
The requested function is not available.
Severity
0 : Informational
Explanation
MQ Explorer was not able to carry out the function requested.
Response
Try again. If symptoms persist, contact your System Administrator.
AMQ4860I
The queue manager is running in standby mode.
Severity
0 : Informational
Explanation
The queue manager has been started in standby mode.
AMQ4861W
IBM MQ cannot stop the listener because the listener is already stopped.
Severity
10 : Warning
AMQ4862W
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.
AMQ4863E
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.
AMQ4864E
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.
AMQ4865E
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.
AMQ4866E
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.
AMQ4867E
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.
AMQ4868E
An unexpected error has occurred.
Severity
20 : Error
Explanation
An unexpected error has occurred.
Response
Contact the system administrator.
AMQ4869W
The export location <insert_0> already exists. Do we 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 we want you overwrite files at the chosen export location.
AMQ4870W
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.
AMQ4871W
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.
AMQ4999W
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.