WebSphere MQ Explorer messages

AMQ4000
New object not created because the default object for the object type could not be found.
Severity:

10 : Warning

Explanation:

The creation of an object requires a default template for each object type. The required default template for this object type could not be found.

Response:

Determine why the default object is not available, or create a new one. Then try the request again.

AMQ4001
The queue manager specified is already shown in the console.
Severity:

0 : Information

Response:

Message for information only.

AMQ4002
Are you sure you want to delete the <insert_0> named <insert_1>?
Severity:

10 : Warning

Explanation:

A confirmation is required before the specified object is deleted. The type of object and name are provided in the message.

Response:

Continue only if you want to permanently delete the object.

AMQ4003
WebSphere MQ system objects are used internally by WebSphere MQ. You are advised not to delete them. Do you want to keep the WebSphere MQ system object?
Severity:

0 : Information

Explanation:

A confirmation is required before an internal WebSphere MQ system object (for example SYSTEM.DEFAULT.LOCAL.QUEUE) is deleted.

Response:

Continue only if you want to permanently delete the system object.

AMQ4004
Clear all messages from the queue?
Severity:

10 : Warning

Explanation:

The removal of the messages from the queue is an irreversible action. If the command is allowed to proceed the action cannot be undone.

Response:

Continue only if you want to permanently delete the messages.

AMQ4005
The object has been replaced or deleted. The properties could not be applied.
Severity:

10 : Warning

Explanation:

During the process of updating the properties of the object, it was determined that the object has either been deleted or replaced by another instance. The properties have not been applied.

AMQ4006
WebSphere MQ successfully sent data to the remote queue manager and received the data returned.
Severity:

0 : Information

Explanation:

An open channel has been successfully verified by WebSphere MQ as the result of a user request.

Response:

Message for information only.

AMQ4007
The message sequence number for the channel was reset.
Severity:

0 : Information

Explanation:

A channel has had its sequence number successfully reset by WebSphere MQ as the result of a user request.

Response:

Message for information only.

AMQ4008
The request to start the channel was accepted.
Severity:

0 : Information

Explanation:

A channel has been started successfully by WebSphere MQ as the result of a user request.

Response:

Message for information only.

AMQ4009
The request to stop the channel was accepted.
Severity:

0 : Information

Explanation:

A channel has been stopped successfully by WebSphere MQ as the result of a user request.

Response:

Message for information only.

AMQ4010
The 'in-doubt' state was resolved.
Severity:

0 : Information

Explanation:

A channel has had its 'in-doubt' state resolved successfully by WebSphere MQ as the result of a user request.

Response:

Message for information only

AMQ4011
The queue has been cleared of messages.
Severity:

0 : Information

Explanation:

The CLEAR command completed successfully and has removed all messages from the target queue. If the CLEAR was performed using the MQGET API command, uncommitted messages might still be on the queue.

AMQ4012
The object was created successfully but it is not visible with the current settings for visible objects.
Severity:

0 : Information

Response:

Message for information only.

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

10 : Warning

AMQ4015
Supply a non-blank name.
Severity:

0 : Information

Response:

Enter a valid name.

AMQ4016
The test message was put successfully.
Severity:

0 : Information

Explanation:

The request to place a message on the target queue has completed successfully. The queue now contains the message.

Response:

Message for information only.

AMQ4019
An object called <insert_0> already exists. Do you want to replace the definition of the existing object?
Severity:

0 : Information

Response:

Confirm that you want to replace the definition.

AMQ4020
The changes you are making to the attributes of page "<insert_0>" will affect the operation of the queue manager or another program currently using the object. Do you want to force the change to the object's attributes?
Severity:

10 : Warning

Explanation:

You are trying to change a object that cannot be changed because the object is in use, or the change will affect other programs or queue managers. Some changes can be forced anyway.

Response:

Select Yes to try forcing the changes, or No to abandon the change.

AMQ4021
Failed to access one or more WebSphere MQ objects.
Severity:

10 : Warning

Explanation:

The objects' icons have been marked to indicate the objects in error.

AMQ4022
The name specified for the initiation queue is the same as the name of the queue itself.
Severity:

0 : Information

Response:

Specify a different name to that of the object being created or altered.

AMQ4023
The queue manager <insert_0> does not exist on this computer.
Severity:

0 : Information

Response:

Message for information only.

AMQ4024
The object cannot be replaced.
Severity:

0 : Information

Explanation:

The request to replace the object was unsuccessful.

Response:

To define this object, delete the existing object and try the operation again.

AMQ4025
The changes made to the cluster attributes of the queue will take effect once they have propagated across the network.
Severity:

0 : Information

Response:

Refresh any views containing the cluster queues in the affected clusters to show the changes.

AMQ4026
You have created a queue which is shared in one or more clusters. The queue will be available as a cluster queue once its definition has propagated across the network.
Severity:

0 : Information

Response:

Refresh any views containing the cluster queues in the affected clusters to show the cluster queue.

AMQ4027
An error occurred connecting to the queue manager. Are you sure you want to show this queue manager in the folder anyway?
Severity:

10 : Warning

Explanation:

A connection could not be made to the specified remote queue manager.

Response:

Ensure that the named queue manager is running on the host and port specified, and has a channel corresponding to the specified name. Ensure that you have the authority to connect to the remote queue manager, and ensure that the network is running. Select Yes if you believe that the problem can be resolved later. Select No if you want to correct the problem now and try again.

AMQ4028
Platform not supported. This queue manager cannot be administered by the WebSphere MQ Explorer because it is running on an unsupported platform. The value <insert_0> for the Platform attribute of the queue manager is not supported by the WebSphere MQ Explorer.
Severity:

20 : Error

AMQ4029
Command level too low. This queue manager cannot be administered by the WebSphere MQ Explorer because the command level of the queue manager is less than <insert_0>.
Severity:

20 : Error

Response:

If you want to administer this queue manager, upgrade it to a newer version of WebSphere MQ.

AMQ4030
Queue manager cannot be administered because codepage conversion table not found.
Severity:

20 : Error

Explanation:

This queue manager cannot be administered by the WebSphere MQ Explorer because a codepage conversion table was not found.

Response:

Install a codepage conversion table from CCSID <insert_0> to CCSID <insert_1> on the computer on which the WebSphere MQ Explorer is running.

AMQ4031
Queue manager cannot be administered because CCSID not found.
Severity:

20 : Error

Explanation:

This queue manager cannot be administered by the WebSphere MQ Explorer because CCSID <insert_0> cannot be found in the CCSID table. The WebSphere MQ Explorer cannot convert character data to or from the unrecognized CCSID.

AMQ4032
Command server not responding within timeout period.
Severity:

10 : Warning

Response:

Ensure that the command server is running and that the queue called 'SYSTEM.ADMIN.COMMAND.QUEUE' is configured to enable programs to get messages from it.

AMQ4033
Cannot get messages from the queue.
Severity:

0 : Information

Explanation:

A reason code returned when the object was opened for input indicated that the queue is disabled for MQGET request.

Response:

To get messages from this queue, enable it for GET requests.

AMQ4034
Message too long. You tried to put a message on a queue that was bigger than the maximum allowed for the queue or queue manager.
Severity:

10 : Warning

Explanation:

The request to put a message on a queue returned a reason code indicating that the data length of the message exceeds the maximum allowed in the definition of the queue.

Response:

Either change the MAXMSGL attribute of the queue so that it is equal to or greater than the length of the message, or reduce the length of the message being put on the queue.

AMQ4035
No message available. The response message did not arrive within a reasonable amount of time.
Severity:

0 : Information

Explanation:

The request to get a message from a queue returned a reason code indicating that there are currently no messages on the queue that meet the selection criteria specified on the GET request.

AMQ4036
Access not permitted. You are not authorized to perform this operation.
Severity:

10 : Warning

Explanation:

The queue manager's security mechanism has indicated that the userid associated with this request is not authorized to access the object.

AMQ4037
Object definition changed since it was opened.
Severity:

0 : Information

Explanation:

Object definitions that affect this object have been changed since the Hobj handle used on this call was returned by the MQOPEN call.

Response:

Issue an MQCLOSE call to return the handle to the system. It is then usually sufficient to reopen the object and try the operation again.

AMQ4038
Object damaged.
Severity:

10 : Warning

Explanation:

The object is damaged and cannot be accessed.

Response:

The object should be deleted. Alternatively, it might be possible to recover it from a media image or backup.

AMQ4039
Object in use. The object is already opened by another application.
Severity:

10 : Warning

Explanation:

An MQOPEN call was issued, but the object in question has already been opened by this 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.

AMQ4040
Cannot put messages on this queue.
Severity:

0 : Information

Explanation:

MQPUT and MQPUT1 calls are currently inhibited for the queue, or for the queue to which this queue resolves.

AMQ4042
Queue full. The queue contains the maximum number of messages.
Severity:

10 : Warning

Explanation:

On an MQPUT or MQPUT1 call, the call failed because the queue is full; that is, it already contains the maximum number of messages possible.

AMQ4043
Queue manager not available for connection.
Severity:

10 : Warning

Response:

Ensure that the queue manager is running. If the queue manager is running on another computer, ensure it is configured to accept remote connections.

AMQ4044
Queue manager stopping.
Severity:

0 : Information

Explanation:

An MQI call was issued, but the call failed because the queue manager is shutting down. If the call was an MQGET call with the MQGMO_WAIT option, the wait has been canceled.

Response:

We cannot issue any more MQI calls.

AMQ4045
Queue not empty. The queue contains one or more messages or uncommitted PUT or GET requests.
Severity:

0 : Information

Explanation:

An operation that requires the queue to be empty has failed because the queue either contains messages or has uncommitted PUT or GET requests outstanding.

AMQ4046
Insufficient system resources available.
Severity:

20 : Error

AMQ4047
Insufficient storage available.
Severity:

20 : Error

AMQ4048
The request received an unexpected reason code from an underlying API or command request. The reason code was <insert_0>
Severity:

20 : Error

Explanation:

While executing the requested operation, an unexpected return code was received. This has resulted in the operation not completing as expected.

Response:

Use the appropriate documentation to determine why the reason code was returned.

AMQ4049
Unknown object name.
Severity:

10 : Warning

Explanation:

A command or API request was issued, but the object cannot be found.

AMQ4050
Allocation failed. An attempt to allocate a conversation to a remote system failed.
Severity:

10 : Warning

Explanation:

The error might be due to an incorrect entry in the channel definition or it might be that the listening program on the remote system was not running.

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

10 : Warning

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

10 : Warning

AMQ4053
Channel in doubt. Operation not completed.
Severity:

10 : Warning

Explanation:

The operation could not complete because the channel was in doubt.

AMQ4054
Channel in use.
Severity:

10 : Warning

Explanation:

An attempt was made to perform an operation on a channel, but the channel is currently active.

AMQ4055
Channel status not found.
Severity:

10 : Warning

Explanation:

No channel status is available for this channel. This might indicate that the channel has not been used.

AMQ4056
Command failed.
Severity:

10 : Warning

AMQ4057
Configuration error in the channel definition or communication subsystem.
Severity:

10 : Warning

Explanation:

Allocation of a conversation is not possible.

AMQ4058
Connection closed.
Severity:

10 : Warning

Explanation:

The connection to a remote system has unexpectedly broken while receiving data.

AMQ4059
Could not establish a connection to the queue manager.
Severity:

10 : Warning

Explanation:

The attempt to connect to the queue manager failed. This 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.

AMQ4060
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.

AMQ4061
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.

AMQ4062
An MQINQ call failed when the queue manager inquired about a WebSphere MQ object.
Severity:

10 : Warning

Response:

Check the queue manager's error log for more information about the error.

AMQ4063
An MQOPEN call failed when the queue manager tried to open a WebSphere MQ object.
Severity:

10 : Warning

Response:

Check the queue manager's error log for more information about the error.

AMQ4064
An MQSET call failed when the queue manager tried to set the values of the attributes of a WebSphere MQ object.
Severity:

10 : Warning

Response:

Check the queue manager's error log for more information about the error.

AMQ4065
Message sequence number error.
Severity:

10 : Warning

Explanation:

The message sequence number parameter was not valid.

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

10 : Warning

AMQ4067
Communications manager not available.
Severity:

20 : Error

Explanation:

The communications subsystem is not available.

AMQ4068
Queue is not a transmission queue.
Severity:

10 : Warning

Explanation:

The queue specified in the channel definition was not a transmission queue.

AMQ4069
Object already exists.
Severity:

10 : Warning

Explanation:

Could not create object because the object already existed.

AMQ4070
Object is open.
Severity:

10 : Warning

Explanation:

An attempt was made to delete, change or clear an object that is in use.

Response:

Wait until the object is not in use, then try again.

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

10 : Warning

AMQ4072
Queue already exists in cell.
Severity:

10 : Warning

Explanation:

Cannot define a queue with cell scope or change the scope of an existing queue from queue-manager scope to cell scope, because a queue with that name already exists in the cell.

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

10 : Warning

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

10 : Warning

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

10 : Warning

AMQ4076
Remote queue manager terminating.
Severity:

10 : Warning

Explanation:

The channel stopped because the remote queue manager was terminating.

AMQ4077
Remote queue manager not available.
Severity:

10 : Warning

Explanation:

The channel could not be started because the remote queue manager was not available.

Response:

Ensure that the remote queue manager is started, and that it is configured to accept incoming communication requests.

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

10 : Warning

AMQ4079
Channel closed by security exit.
Severity:

10 : Warning

AMQ4080
Remote channel not known.
Severity:

10 : Warning

Explanation:

There is no definition of this channel on the remote system.

AMQ4081
User exit not available.
Severity:

10 : Warning

Explanation:

The channel was closed because the user exit specified does not exist.

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

20 : Error

AMQ4083
Queue manager name not known.
Severity:

10 : Warning

Explanation:

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

AMQ4084
Cell directory is not available.
Severity:

10 : Warning

Explanation:

The Scope attribute of the queue was set to MQSCO_CELL but no name service supporting a cell directory has been configured.

Response:

Configure a name service to support the cell directory.

AMQ4085
No name supplied for transmission queue.
Severity:

10 : Warning

Response:

Supply a non-blank transmission queue name for this channel type.

AMQ4086
No connection name supplied.
Severity:

10 : Warning

Response:

Supply a non-blank connection name for this channel type.

AMQ4087
An error occurred while trying to use a cluster resource.
Severity:

10 : Warning

Response:

Check that the queues whose names start with 'SYSTEM.CLUSTER.' are not full and that messages are allowed to be put on them.

AMQ4088
Cannot share transmission queue in cluster.
Severity:

10 : Warning

Explanation:

The queue is a transmission queue and cannot be shared in a cluster.

AMQ4089
PUT commands inhibited for system command queue called 'SYSTEM.ADMIN.COMMAND.QUEUE'.
Severity:

10 : Warning

AMQ4090
Are you sure you want to inhibit PUT and GET commands for the queue called 'SYSTEM.ADMIN.COMMAND.QUEUE'? If you do, you will no longer be able to administer the queue manager using the WebSphere MQ Explorer.
Severity:

10 : Warning

Explanation:

WebSphere MQ Explorer uses the queue called 'SYSTEM.ADMIN.COMMAND.QUEUE' to administer the queue manager.

Response:

Continue only if you really want to inhibit PUT or GET commands for this queue and stop using the WebSphere MQ Explorer to administer the queue manager.

AMQ4091
Cannot connect to remote queue manager.
Severity:

10 : Warning

Explanation:

The remote queue manager is using an unsupported protocol for connections. The WebSphere MQ Explorer only supports connections to remote queue managers using the TCP/IP protocol.

AMQ4092
The queue manager could not be removed from the cluster because its membership of the cluster is defined using namelist <insert_0>.
Severity:

10 : Warning

Response:

To remove the queue manager from the cluster, remove it from the namelist. Ensure that you do not inadvertently affect the definitions of other objects using the namelist.

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

0 : Information

AMQ4094
An error occurred adding this cluster to the console. Are you sure you want to show this cluster in the console anyway?
Severity:

10 : Warning

Response:

Select Yes if you believe that the problem can be resolved later. Select No if you want to correct the problem now and try again.

AMQ4095
Queue manager <insert_0> is not a repository queue manager for cluster <insert_1>.
Severity:

0 : Information

Explanation:

To administer a cluster, the WebSphere MQ Explorer needs a connection to the repository queue manager.

AMQ4096
Are you sure you want to clear the password for this channel?
Severity:

0 : Information

Response:

Check with the user before clearing the password from the channel. Continue only if you really want to clear the password.

AMQ4097
Unmatched quotation mark.
Severity:

10 : Warning

Explanation:

An unmatched quotation mark has been found in a list of attributes. Each value in the list can be enclosed in a pair of single or double quotation marks. (Only required for values which contain spaces, commas or quotation marks.)

Response:

Check that all opening and closing quotation marks are in pairs. (To include a quotation mark within an attribute, use two together with no space between.)

AMQ4098
Incorrect list format.
Severity:

10 : Warning

Explanation:

The attribute can contain a list of values which must be separated by a space or a comma. Each value in the list can be enclosed in a pair of single or double quotation marks. (Only required for values which contain spaces, commas or quotation marks.)

Response:

Check that values are separated by a space or a comma, and that all opening and closing quotation marks are in pairs. (To include a quotation mark within an attribute, use two together with no space between.)

AMQ4099
Cannot communicate with one or more repository queue managers. Cluster <insert_0> is configured to use one or more repository queue managers which communicate using a protocol other than TCP/IP.
Severity:

10 : Warning

Explanation:

The WebSphere MQ Explorer can only establish connections to remote queue managers using TCP/IP.

Response:

To complete removal of the queue manager from the cluster, issue the RESET CLUSTER ACTION(FORCEREMOVE) command from the repository queue manager.

AMQ4103
An error occurred connecting to the queue manager. Are you sure you want to show this queue manager in the folder?
Severity:

10 : Warning

Explanation:

A connection could not be made to the specified remote queue manager.

Response:

Ensure that the named queue manager is running on the machine specified in the selected channel definition table. Ensure that you have the authority to connect to the remote queue manager, and ensure that the network is up and running. Select Yes if you believe that the problem can be resolved later. Select No if you want to correct the problem now and try again.

AMQ4104
The specified file <insert_0> does not contain a client definition table in the correct format.
Severity:

10 : Warning

Explanation:

The given channel definition table is not in the correct format.

Response:

Specify a file in the correct format.

AMQ4105
The remote queue manager has not been removed because it is still required by other plug-ins.
Severity:

10 : Warning

Explanation:

Other plug-ins have responded to the attempted removal of this queue manager by indicating that they are still using it.

Response:

Ensure that the other plug-ins have finished using the queue manager before trying to delete it again.

AMQ4117
This action cannot be undone. Are you sure you want to delete the WebSphere MQ queue manager <insert_0> from your system?
Severity:

10 : Warning

Explanation:

A confirmation is required before the queue manager is deleted.

Response:

Continue only if you want to permanently delete the queue manager.

AMQ4121
The MQGET request received an unexpected reason code of <insert_0>.
Severity:

10 : Warning

Explanation:

An unexpected reason code was returned from 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.

AMQ4122
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.

AMQ4123
The <insert_0> <insert_1> was deleted successfully.
Severity:

0 : Information

Explanation:

The object of the specified type and name has been successfully deleted.

Response:

none.

AMQ4124
The MQOPEN request received an unexpected reason code of <insert_0>.
Severity:

10 : Warning

Explanation:

An unexpected reason code was returned from an MQOPEN API request. The queue has not been opened.

Response:

Use the reason code to determine the underlying reason for the failure.

AMQ4125
Putting a test message on the queue received an unexpected reason code <insert_0>.
Severity:

10 : Warning

Explanation:

One of the underlying API requests was unsuccessful. The test message was not placed on the queue.

AMQ4126
The value of one of the properties specified is not valid. The request was not processed.
Severity:

20 : Error

Response:

Specify a different value.

AMQ4127
WebSphere MQ failed to read queue manager information from disk because the file format is not valid. The request was not processed.
Severity:

20 : Error

Explanation:

The format of the WebSphere MQ_Handles file is incorrect. This file has been backed up and removed, meaning that any remote queue manager definitions are lost. All local queue managers should be detected automatically and displayed in the WebSphere MQ Explorer.

Response:

Ensure that the Eclipse workspace has not been corrupted.

AMQ4128
Could not start the iKeyMan program.
Severity:

30 : Severe error

Explanation:

An error was encountered when trying to execute the iKeyMan program.

Response:

Try again, and if symptoms persist contact the System Administrator.

AMQ4129
Could not query the user ID from Java.
Severity:

10 : Warning

Explanation:

The Java API System.getProperty("user.id") threw a SecurityException.

Response:

Configure your Java security environment using the 'policytool' to allow WebSphere MQ Explorer to query the 'user.id'.

AMQ4130
A Browser Control could not be opened. Make sure Mozilla has been installed.
Severity:

10 : Warning

Explanation:

The SWT Browser control depends on Mozilla being installed.

Response:

Ensure that the Mozilla browser is correctly installed.

AMQ4131
A Browser Control could not be opened.
Severity:

10 : Warning

Explanation:

The SWT Browser control depends on the system browser being installed.

Response:

Ensure that the system browser is correctly installed.

AMQ4132
Are you sure you want to stop the <insert_0> named "<insert_1>"?
Severity:

10 : Warning

Explanation:

A confirmation is required before the specified object is stopped. The type of object and name are provided in the message.

Response:

Continue only if you want to stop the object.

AMQ4133
When a queue manager is removed, WebSphere MQ Explorer destroys the connection information for that queue manager.
To see the queue manager at a later date use the Add Queue Manager wizard.
Remove the queue manager <insert_0> ?
Severity:

10 : Warning

Response:

Continue only if you want to remove the queue manager.

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

0 : Information

Response:

Select Yes to create the channel.

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

0 : Information

Response:

Select Yes to delete the channel.

AMQ4136
Are you sure you want to clear all FFSTs and Trace from this machine? This operation cannot be undone.
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 FFSTs and Trace

AMQ4137
The default remote administration channel SYSTEM.ADMIN.SVRCONN has been deleted successfully.
Severity:

0 : Information

Response:

Message for information only.

AMQ4138
Are you sure you want to import new settings that will overwrite the current settings? This operation cannot be undone.
Severity:

10 : Warning

Explanation:

Importing settings into the WebSphere MQ Explorer will overwrite the current settings.

Response:

Continue only if you want to overwrite the current settings.

AMQ4139
The default remote administration channel SYSTEM.ADMIN.SVRCONN was created successfully.
Severity:

0 : Information

Response:

Message for information only.

AMQ4140
The custom CipherSpec is not valid.
Severity:

10 : Warning

AMQ4141
The Distinguished Names specification is not valid.
Severity:

10 : Warning

AMQ4142
The default remote administration channel SYSTEM.ADMIN.SVRCONN could not be created.
Severity:

10 : Warning

Explanation:

A problem has occurred when issuing a command to the command server to create the channel.

Response:

Try again, and if symptoms persist contact the Systems Administrator.

AMQ4143
The default remote administration channel SYSTEM.ADMIN.SVRCONN could not be created.
Severity:

10 : Warning

Explanation:

A problem has occurred with the underlying data model, and the channel could not be created.

Response:

Try again, and if symptoms persist contact the Systems Administrator.

AMQ4144
The default remote administration channel SYSTEM.ADMIN.SVRCONN could not be deleted.
Severity:

10 : Warning

Explanation:

A problem has occurred issuing a command to the command server to delete the channel.

Response:

Ensure that the channel is not in use and try again. If symptoms persist, contact the Systems Administrator.

AMQ4145
An error occurred connecting to the remote queue manager using the intermediate queue manager. Are you sure you want to show this queue manager in the folder anyway?
Severity:

10 : Warning

Explanation:

A connection could not be made to the specified remote queue manager.

Response:

Ensure that the intermediate queue manager is available and that the named remote queue manager is running, and is accessible from the intermediate queue manager. Ensure that you have the authority to connect to the remote queue manager, and ensure that the network is up and running. Select Yes if you believe that the problem can be resolved later. Select No if you want to correct the problem now and try again.

AMQ4146
Eclipse cannot create or read the workspace for WebSphere MQ Explorer.
Severity:

40 : Stop Error

Explanation:

To load the WebSphere MQ Explorer, a valid workspace is required.

Response:

Ensure that we can write to the Eclipse workspace.

AMQ4147
Eclipse cannot write to the workspace for WebSphere MQ Explorer in <insert_0>.
Severity:

40 : Stop Error

Explanation:

To load the WebSphere MQ Explorer, write access to the workspace is required.

Response:

Ensure that we can write to the Eclipse workspace.

AMQ4148
The object was created successfully.
Severity:

0 : Information

Response:

Message for information only.

AMQ4149
The request to start the listener was accepted.
Severity:

0 : Information

Explanation:

A user request to start the listener was accepted by WebSphere MQ.

Response:

Message for information only.

AMQ4150
The request to stop the listener was accepted.
Severity:

0 : Information

Explanation:

A user request to stop the listener was accepted by WebSphere MQ.

Response:

Message for information only.

AMQ4151
The request to start the service was accepted.
Severity:

0 : Information

Explanation:

A user request to start the service was accepted by WebSphere MQ.

Response:

Message for information only.

AMQ4152
The request to stop the service was accepted.
Severity:

0 : Information

Explanation:

A user request to stop the service was accepted by WebSphere MQ.

Response:

Message for information only.

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

10 : Warning

AMQ4154
WebSphere MQ cannot start the service because no start command has been specified.
Severity:

10 : Warning

Response:

Ensure that the service has a start command specified.

AMQ4155
WebSphere MQ cannot stop the service because no stop command has been specified.
Severity:

10 : Warning

Response:

Ensure that the service has a stop command specified.

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

10 : Warning

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

10 : Warning

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

10 : Warning

AMQ4159
WebSphere MQ cannot start the client connection channel because one or more of the properties are incorrectly specified.
Severity:

10 : Warning

Response:

Ensure that the client connection has the correct queue manager name and connection name before trying to start.

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

10 : Warning

Explanation:

The requested was unsuccessful because the program which was defined to be run to complete the action could not be started.
Reasons why the program could not be started are :-
The program does not exist at the specified location.
The WebSphere MQ user does not have sufficient access to execute the program.
If StdOut or StdErr are defined for the program, the WebSphere MQ user does not have sufficient access to the locations specified.

Response:

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

AMQ4161
The parameter specified is not valid.
Severity:

20 : Error

Explanation:

The parameter specified when trying to create or alter an object is not valid.

Response:

Ensure that valid parameters are specified, then try again.

AMQ4162
The password cannot be cleared.
Severity:

0 : Information

Response:

Try to clear the password again later.

AMQ4163
The password cannot be changed.
Severity:

10 : Warning

Explanation:

The attempt to change the password failed because of an error.

Response:

Try a different password

AMQ4164
The password was successfully changed.
Severity:

0 : Information

Response:

Message for information only.

AMQ4165
No password entered in the new password field. No change applied.
Severity:

10 : Warning

Explanation:

You must enter a new password in both the new and confirm password fields.

Response:

Enter a new password in the new password field.

AMQ4166
No password entered in the confirm new password field. No change applied.
Severity:

10 : Warning

Explanation:

You must enter a new password in both the new and confirm password fields.

Response:

Re-enter the new password in the confirm new password field.

AMQ4167
Passwords do not match. No change applied.
Severity:

10 : Warning

Explanation:

You must enter the same new password in both the new and confirm password fields.

Response:

Ensure that the passwords in the new and confirm fields match.

AMQ4168
WebSphere MQ failed to start listening for objects.
Severity:

20 : Error

Explanation:

No objects will be displayed in the currently selected view.

Response:

Check the problem determination information, and ensure that WebSphere MQ and the queue manager in question are both running correctly.

AMQ4169
WebSphere MQ failed to set the object filter.
Severity:

20 : Error

Explanation:

The WebSphere MQ Explorer cannot listen for objects, so no objects will be displayed in the currently selected view.

Response:

Check the problem determination information, and ensure that WebSphere MQ and the queue manager in question are both running correctly.

AMQ4170
The object name specified is not valid.
Severity:

20 : Error

Explanation:

The object name specified when trying to create or alter an object is not valid.

Response:

Ensure that a valid object name is specified, then try again.

AMQ4171
There was an error when communicating with the queue manager.
Severity:

20 : Error

Explanation:

A request for information from the queue manager failed.

Response:

Try the operation again. If the error persists, examine the problem determination information to see if any details have been recorded.

AMQ4172
There was an error when trying to set or retrieve information.
Severity:

20 : Error

Explanation:

There was an error when trying to set or retrieve information from the queue manager. This might have happened because you specified incorrect or inconsistent attributes when trying create or update an object.

Response:

If this error occurred during object creation or modification, ensure that the attributes specified are correct for this type of object. If the error persists, examine the problem determination information to see if any details have been recorded.

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

10 : Warning

Explanation:

WebSphere MQ cannot clear some files, possibly because these files are currently in use, or the WebSphere MQ Explorer does not have the appropriate access permission.

Response:

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

AMQ4174
FFSTs and Trace were cleared successfully.
Severity:

0 : Information

Response:

Message for information only.

AMQ4175
WebSphere MQ cannot process your request because the value specified is not valid.
Severity:

20 : Error

Explanation:

Only certain combinations and values are valid for the object your are trying to alter or create. Please check the values and try again.

Response:

Specify a valid value and try again.

AMQ4176
WebSphere MQ cannot process your request because the object name specified is not valid.
Severity:

20 : Error

Explanation:

Only certain combinations and values are valid for the object your are trying to alter or create. You might also see this message if you have specified an invalid QSG disposition.

Response:

Check all values are valid for this type of object and try again. If you have altered the disposition of this object, check that the value is correct.

AMQ4177
The WebSphere MQ Explorer cannot process your request because the connection to WebSphere MQ is quiescing.
Severity:

20 : Error

Explanation:

The connection to WebSphere MQ is quiescing, so no new information can be queried.

Response:

Wait for the connection to end, then try reconnecting.

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

20 : Error

Explanation:

A disposition conflict was detected. 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.

AMQ4179
WebSphere MQ cannot process your request because the string provided was of an incorrect length.
Severity:

20 : Error

Explanation:

A string value has been modified or supplied that is too long when creating or modifying an object.

Response:

Check the values being supplied and try again.

AMQ4180
WebSphere MQ cannot process your request because there was a parameter conflict.
Severity:

20 : Error

Explanation:

When creating or modifying an object, the combination of parameters specified is not valid.

Response:

Check that the combination specified is valid for the object and try again.

AMQ4181
WebSphere MQ is not responding. Do you want to continue waiting?
Severity:

10 : Warning

Explanation:

WebSphere MQ does not appear to be responding. This could be because of a heavily loaded remote system, or a slow network connection. However there could have been a system failure. Choosing not to continue could leave the WebSphere MQ Explorer in an unknown state, so you should restart it.

Response:

If you choose not to continue waiting, restart the WebSphere MQ Explorer, if the problem persists check for problem determination information.

AMQ4182
No objects were found.
Severity:

10 : Warning

Explanation:

The query did not find any objects.

Response:

If you were expecting objects to be found, check the problem determination information, and ensure that WebSphere MQ and the queue manager in question are both running correctly.

AMQ4183
Query failed because the queue manager is not in a queue-sharing group.
Severity:

10 : Warning

Explanation:

WebSphere MQ issued a query that required the queue manager to be a member of a queue-sharing group.

Response:

Try the operation again, if the problem persists check the problem determination information for more details.

AMQ4184
WebSphere MQ is unable to perform your request because the channel is not active.
Severity:

20 : Error

AMQ4185
WebSphere MQ failed to import your settings.
Severity:

20 : Error

Response:

Try again. If the error persists, examine the problem determination information to see if any details have been recorded.

AMQ4186
WebSphere MQ failed to export your settings.
Severity:

20 : Error

Response:

Try again. If the error persists, examine the problem determination information to see if any details have been recorded.

AMQ4187
WebSphere MQ has succesfully imported your settings. (You must restart WebSphere MQ Explorer to apply the imported settings.)
Severity:

0 : Information

Response:

Restart WebSphere MQ explorer to apply the imported settings

AMQ4188
Are you sure you want to remove queue manager <insert_0> from cluster <insert_1>?
Severity:

10 : Warning

Explanation:

A confirmation is required before the queue manager is removed from the cluster.

Response:

Continue only if you want to permanently remove the queue manger from the cluster.

AMQ4189
The queue manager could not be suspended from the cluster. The operation failed with error <insert_0>.
Severity:

20 : Error

Explanation:

The queue manager has not been removed from the cluster.

Response:

Try the operation again. If the error persists, examine the problem determination information to see if any information has been recorded.

AMQ4190
An error occurred when clearing the queue manager's REPOS field. The operation failed with error <insert_0>.
Severity:

20 : Error

Explanation:

The queue manager has only partially been removed from the cluster. The queue manager has been suspended from the cluster. The REPOS field of the queue manager and the CLUSTER fields of the associated cluster channels have not been cleared.

Response:

Try the operation again. If the error persists, examine the problem determination information to see if any information has been recorded.

AMQ4191
An error occurred when clearing the CLUSTER field of channel <insert_0>. The operation failed with error <insert_1>.
Severity:

20 : Error

Explanation:

The queue manager has only partially been removed from the cluster. The queue manager has been suspended from the cluster and the queue manager's REPOS field has been cleared. Some of the CLUSTER fields of other associated cluster channels might also have been cleared.

Response:

To completely remove the queue manager, ensure that all the CLUSTER fields of associated cluster channels are cleared.

AMQ4192
The queue manager could not be removed from a cluster because channel <insert_0> is using cluster namelist <insert_1>.
Severity:

10 : Warning

Response:

Remove the cluster channel from the cluster namelist. Ensure that you do not inadvertently affect the definitions of other objects using the namelist. Then try removing the queue manager again.

AMQ4193
The information supplied could not be correctly converted to the required code page.
Severity:

20 : Error

Explanation:

All or part of the information entered required conversion to a different code page. One or more characters could not be converted to an equivalent character in the new code page.

Response:

Change the characters used, then try the operation again.

AMQ4194
Request failed because the queue manager attempted to use a default transmission queue which is not valid.
Severity:

20 : Error

Explanation:

An MQOPEN or MQPUT1 call specified a remote queue as the destination. The queue manager used the default transmission queue, as there is no queue defined with the same name as the destination queue manager, but the attempt failed because the default transmission queue is not a valid local queue.

Response:

Check that the queue manager's default transmission queue property (DefXmitQName) specifies a valid local queue.

AMQ4195
WebSphere MQ Explorer is now in an unknown state and should be restarted. Do you want to restart WebSphere MQ Explorer?
Severity:

10 : Warning

Explanation:

You have chosen not to wait for WebSphere MQ to respond to a request. WebSphere MQ Explorer is therefore in an unknown state and should be restarted.

Response:

Restart the WebSphere MQ Explorer and try the operation again. If the problem persists check for problem determination information.

AMQ4196
The command or operation is not valid against the type of object or queue specified
Severity:

20 : Error

Explanation:

You have attempted a command or operation against an object or queue 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.

AMQ4197
An MQOPEN or MQPUT1 call was issued specifying an alias queue as the target, but the BaseQName 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 BaseQName in the alias queue attributes is not recognized as a queue name. This reason code can also occur when BaseQName is the name of a cluster queue that cannot be resolved successfully.

Response:

Correct the queue definitions.

AMQ4207
The path specified is not valid.
Severity:

20 : Error

Response:

Check the path specified and try again.

AMQ4400
Explorer cannot administer the queue manager because the queue <insert_0> is not defined.
Severity:

10 : Warning

Explanation:

Explorer uses the queue <insert_0> to administer queue managers.

Response:

Define the queue <insert_0> and retry.

AMQ4401
Explorer cannot administer the queue manager because the user is not authorised to open the queue <insert_0>.
Severity:

10 : Warning

Explanation:

Explorer uses the queue <insert_0> to administer this queue manager.

Response:

Allow Explorer to open the queue <insert_0> and retry.

AMQ4402
The queue <insert_0> could not be opened for reason <insert_1>.
Severity:

10 : Warning

Explanation:

Explorer uses the queue <insert_0> to administer this queue manager.

Response:

Allow Explorer to open the queue <insert_0> and retry.

AMQ4500
Are you sure you want to forcibly remove queue manager <insert_0> from cluster <insert_1>?
Severity:

10 : Warning

Explanation:

You should only forcibly remove a queue manager from a cluster when it has already been deleted and cannot be removed from the cluster in the normal way. A confirmation is required before the queue manager is forcibly removed.

Response:

Continue only if you want to forcibly remove the queue manager.

AMQ4501
The queue manager was successfully removed from the cluster.
Severity:

0 : Information

Explanation:

The queue manager will still appear as a member of the cluster until the configuration changes have been sent across the network and the cluster channels to the queue manager have become inactive. This might take a long time.

AMQ4502
You have shared the queue in cluster <insert_0>. The queue manager is not a member of this cluster.
Severity:

10 : Warning

Response:

To make the queue available to the members of this cluster, join the queue manager to the cluster.

AMQ4503
The list of values is too long.
Severity:

10 : Warning

Explanation:

The list of values that you have entered is too long. The maximum number of characters allowed for this value is <insert_0>.

AMQ4504
The value is too long.
Severity:

10 : Warning

Explanation:

You have entered a value containing too many characters. The maximum number of characters allowed for each value of this attribute is <insert_0>.

AMQ4505
There are too many entries in the list.
Severity:

10 : Warning

Explanation:

You have entered too many values in the list. The maximum number of values is <insert_0>.

AMQ4506
Cannot connect to queue manager <insert_0>. It cannot be removed from the cluster in the normal way.
Severity:

10 : Warning

Response:

Try the operation again when the queue manager is available. If the queue manager no longer exists, we can choose to forcibly remove the queue manager from the cluster.

AMQ4507
The remote queue manager is not using TCP/IP.
Severity:

10 : Warning

Explanation:

The connection information available for the remote queue manager uses a communication protocol other than TCP/IP. The WebSphere MQ Explorer cannot connect to the queue manager to remove it from the cluster in the normal way.

Response:

If the queue manager no longer exists, we can choose to forcibly remove the queue manager from the cluster.

AMQ4508
The queue manager successfully left the cluster.
Severity:

0 : Information

Explanation:

The queue manager will still appear as a member of the cluster until the configuration changes have been sent across the network and the cluster channels to the queue manager have become inactive. This might take a long time.

AMQ4509
The request to suspend membership of the cluster has been accepted.
Severity:

0 : Information

Response:

Message for information only.

AMQ4510
The request to resume membership of the cluster has been accepted.
Severity:

0 : Information

Response:

Message for information only.

AMQ4511
The queue manager is not a member of the cluster.
Severity:

0 : Information

Response:

Message for information only.

AMQ4513
The request to refresh the information about the cluster has been accepted.
Severity:

0 : Information

Response:

Message for information only.

AMQ4514
The queue manager is not a member of cluster <insert_0>.
Severity:

10 : Warning

Explanation:

The object that you have shared in the cluster will not be available to other members of the cluster until you make this queue manager a member of the cluster.

AMQ4515
The repository queue manager for cluster <insert_0> is not available for connection.
Severity:

10 : Warning

Explanation:

Views showing cluster queues in this cluster might not be complete.

AMQ4516
Cluster workload exit error.
Severity:

10 : Warning

Explanation:

The queue manager's cluster workload exit failed unexpectedly or did not respond in time.

AMQ4517
Cluster resolution error.
Severity:

10 : Warning

Explanation:

The definition of the cluster queue could not be resolved correctly because a response from a repository queue manager was not available.

AMQ4518
AMQ4518=A call was stopped by the cluster exit.
Severity:

10 : Warning

Explanation:

The queue manager's cluster workload exit rejected a call to open or put a message onto a cluster queue.

AMQ4519
No destinations are available.
Severity:

10 : Warning

Explanation:

At the time that the message was put, there were no longer any instances of the queue in the cluster.

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

10 : Warning

AMQ4521
The text you entered contained a comma (,) which is used as a list separator character.
Severity:

10 : Warning

Explanation:

This value does not accept lists.

Response:

If you want to use a comma as part of a value, enclose the value in double quotes.

AMQ4522
The wizard was unable to add the queue manager to the cluster.
All changes will be rolled back.
Severity:

10 : Warning

Explanation:

A problem occurred while defining objects or modifying the queue manager's properties.

Response:

Ensure that the default objects exist for the queue manager.

AMQ4523
The wizard was unable to add one of the queue managers to the cluster.
All changes will be rolled back.
Severity:

10 : Warning

Explanation:

A problem occurred while defining objects or modifying one of the queue managers' properties.

Response:

Ensure that the default objects exist for the queue manager.

AMQ4571
Are you sure you want to change the location of the Key Repository for queue manager <insert_0>?
Severity:

10 : Warning

Explanation:

You might prevent the queue manager from starting if you change the Key Repository field to a location which is not valid.

Response:

Ensure that the location specified is correct before continuing.

AMQ4572
The request to refresh the information about all clusters has been accepted.
Severity:

0 : Information

Response:

Message for information only.

AMQ4574
IBM WebSphere Explorer is already running.
Severity:

30 : Severe error

AMQ4575
An error occurred initializing the data model.
Severity:

30 : Severe error

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

30 : Severe error

AMQ4577
An error occurred initializing the process.
Severity:

30 : Severe error

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

30 : Severe error

AMQ4579
An error occurred loading the system libraries.
Severity:

30 : Severe error

AMQ4580
An internal method detected an unexpected system return code. The method <insert_0> returned <insert_1>.
Severity:

30 : Severe error

Response:

Examine the problem determination information on this computer to establish the cause of the error.

AMQ4581
Parameter check failed on the internal function <insert_0>. The error was <insert_1>.
Severity:

30 : Severe error

Response:

Examine the problem determination information on this computer to establish the cause of the error.

AMQ4582
Queue manager <insert_0> is not available for client connection.
Severity:

30 : Severe error

Response:

Ensure the queue manager is running and is configured to accept remote connections.

AMQ4583
Queue manager <insert_0> is not available for connection.
Severity:

30 : Severe error

Response:

Ensure the queue manager is running.

AMQ4584
Queue manager <insert_0> is not available for cluster connection.
Severity:

30 : Severe error

Response:

Ensure that the queue manager is running. If the queue manager has been deleted it might continue to be displayed as a member of a cluster for up to 30 days.

AMQ4585
An internal method <insert_0> encountered an unexpected error.
Severity:

30 : Severe error

Response:

Examine the problem determination information on this computer to establish the cause of the error.

AMQ4586
The attempt to create the URL for file <insert_0> failed.
Severity:

30 : Severe error

Explanation:

The file name specified was not recognized.

Response:

Ensure that the file exists at the specified location and can be read.

AMQ4587
The attempt to read from URL <insert_0> failed.
Severity:

30 : Severe error

Explanation:

There was an error when the system tried to read the Client channel definition table.

Response:

Ensure that the file exists at the specified location and can be read.

AMQ4588
The attempt to read from URL <insert_0> failed.
Severity:

30 : Severe error

Explanation:

There was an error when the system tried to read the file.

Response:

Ensure that the file exists at the specified location and can be read.

AMQ4589
No connection was found to application <insert_0>.
Severity:

10 : Warning

Explanation:

The connection was not found. Possibly the connection was closed before the command was issued.

Response:

Check that the application connection has not been closed in the background.

AMQ4590
The queue manager connection to application <insert_0> could not be closed.
Severity:

20 : Error

Explanation:

The connection could not be closed due to a PCF error.

Response:

Check for FFSTs.

AMQ4591
The command server for <insert_0> is not running.
Severity:

30 : Severe error

Explanation:

The command server has stopped for some reason, so the request cannot be processed.

Response:

Start the command server. If the error persists, examine the problem determination information to see if any details have been recorded.

AMQ4592
The connection was closed successfully.
Severity:

0 : Information

Explanation:

The request to close the connection to an application was successful.

Response:

Message for information only.

AMQ4593
Do you really want to stop the connection to application "<insert_0>"
Severity:

0 : Information

Explanation:

WebSphere MQ explorer is about to stop a connection, stopping the connection will prevent further communication between MQ and the application in question.

Response:

Select yes if you want to stop the connection.

AMQ4700
PCF command identifier (<insert_0>) not valid for queue manager <insert_1>.
Severity:

10 : Warning

Explanation:

The specified PCF command is not supported by this queue manager.

AMQ4800
Error initializing <insert_0>.
Severity:

30 : Severe error

Explanation:

An error occurred while starting this application.

Response:

Check that the WebSphere MQ runtime libraries are available.
Check that the PATH system environment variable includes the directory for these runtime libraries.)

AMQ4801
Error getting the location of the help system.
Severity:

10 : Warning

Explanation:

To launch the standalone Eclipse help system, the WebSphere MQ file transfer application needs to know where it is installed.

Response:

Check that Eclipse has been installed with WebSphere MQ.

AMQ4802
Error launching the help system.
Severity:

10 : Warning

Explanation:

The WebSphere MQ file transfer application failed to create an instance of the Eclipse standalone help system.

Response:

Check that Eclipse has been installed with WebSphere MQ.

AMQ4803
Error starting the help system.
Severity:

10 : Warning

Explanation:

The WebSphere MQ file transfer application failed to start the standalone Eclipse system.

Response:

Check that Eclipse has been installed with WebSphere MQ.

AMQ4805
Error saving the history log file.
Severity:

10 : Warning

Explanation:

The WebSphere MQ file transfer application could not read the history log file. This file is called com.ibm.mq.fta.log.ser and is in your home directory.
On Windows, this is %APPDATA%\IBM\WebSphere MQ FileTransferApp
On Unix, this is $HOME/.mqdata

Response:

Check that the read/write properties on this file allow you to write to it.

AMQ4806
Error reading the history log.
Severity:

10 : Warning

Explanation:

The WebSphere MQ file transfer application could not read the history log file. This file is called com.ibm.mq.fta.log.ser and is in your home directory.
On Windows, this is %APPDATA%\IBM\WebSphere MQ FileTransferApp
On Unix, this is $HOME/.mqdata

Response:

Check that the read/write properties on this file allow you to write to it.

AMQ4807
The message size specified (<insert_0>) is outside the permitted range.
Severity:

10 : Warning

Response:

Specify a value of 1000 to 100 000 000.