10 : Warning
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.
Determine why the default object is not available, or create a new one. Then try the request again.
0 : Information
Message for information only.
10 : Warning
A confirmation is required before the specified object is deleted. The type of object and name are provided in the message.
Continue only if you want to permanently delete the object.
0 : Information
A confirmation is required before an internal WebSphere MQ system object (for example SYSTEM.DEFAULT.LOCAL.QUEUE) is deleted.
Continue only if you want to permanently delete the system object.
10 : Warning
The removal of the messages from the queue is an irreversible action. If the command is allowed to proceed the action cannot be undone.
Continue only if you want to permanently delete the messages.
10 : Warning
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.
0 : Information
An open channel has been successfully verified by WebSphere MQ as the result of a user request.
Message for information only.
0 : Information
A channel has had its sequence number successfully reset by WebSphere MQ as the result of a user request.
Message for information only.
0 : Information
A channel has been started successfully by WebSphere MQ as the result of a user request.
Message for information only.
0 : Information
A channel has been stopped successfully by WebSphere MQ as the result of a user request.
Message for information only.
0 : Information
A channel has had its 'in-doubt' state resolved successfully by WebSphere MQ as the result of a user request.
Message for information only
0 : Information
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.
0 : Information
Message for information only.
10 : Warning
0 : Information
Enter a valid name.
0 : Information
The request to place a message on the target queue has completed successfully. The queue now contains the message.
Message for information only.
0 : Information
Confirm that you want to replace the definition.
10 : Warning
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.
Select Yes to try forcing the changes, or No to abandon the change.
10 : Warning
The objects' icons have been marked to indicate the objects in error.
0 : Information
Specify a different name to that of the object being created or altered.
0 : Information
Message for information only.
0 : Information
The request to replace the object was unsuccessful.
To define this object, delete the existing object and try the operation again.
0 : Information
Refresh any views containing the cluster queues in the affected clusters to show the changes.
0 : Information
Refresh any views containing the cluster queues in the affected clusters to show the cluster queue.
10 : Warning
A connection could not be made to the specified remote queue manager.
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.
20 : Error
20 : Error
If you want to administer this queue manager, you must upgrade it to a newer version of WebSphere MQ.
20 : Error
This queue manager cannot be administered by the WebSphere MQ Explorer because a codepage conversion table was not found.
Install a codepage conversion table from CCSID <insert_0> to CCSID <insert_1> on the computer on which the WebSphere MQ Explorer is running.
20 : Error
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.
10 : Warning
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.
0 : Information
A reason code returned when the object was opened for input indicated that the queue is disabled for MQGET request.
To get messages from this queue, enable it for GET requests.
10 : Warning
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.
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.
0 : Information
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.
10 : Warning
The queue manager's security mechanism has indicated that the userid associated with this request is not authorized to access the object.
0 : Information
Object definitions that affect this object have been changed since the Hobj handle used on this call was returned by the MQOPEN call.
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.
10 : Warning
The object is damaged and cannot be accessed.
The object should be deleted. Alternatively, it might be possible to recover it from a media image or backup.
10 : Warning
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).
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.
0 : Information
MQPUT and MQPUT1 calls are currently inhibited for the queue, or for the queue to which this queue resolves.
10 : Warning
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.
10 : Warning
Ensure that the queue manager is running. If the queue manager is running on another computer, ensure it is configured to accept remote connections.
0 : Information
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.
You cannot issue any more MQI calls.
0 : Information
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.
20 : Error
20 : Error
20 : Error
While executing the requested operation, an unexpected return code was received. This has resulted in the operation not completing as expected.
Use the appropriate documentation to determine why the reason code was returned.
10 : Warning
A command or API request was issued, but the object cannot be found.
10 : Warning
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.
10 : Warning
10 : Warning
10 : Warning
The operation could not complete because the channel was in doubt.
10 : Warning
An attempt was made to perform an operation on a channel, but the channel is currently active.
10 : Warning
No channel status is available for this channel. This might indicate that the channel has not been used.
10 : Warning
10 : Warning
Allocation of a conversation is not possible.
10 : Warning
The connection to a remote system has unexpectedly broken while receiving data.
10 : Warning
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.
Try the operation again. If the error persists, examine the problem determination information to see if any information has been recorded.
10 : Warning
The Scope attribute of the queue was set to MQSCO_CELL but this is not allowed for a dynamic queue.
10 : Warning
The error might be transitory; try again later.
10 : Warning
Check the queue manager's error log for more information about the error.
10 : Warning
Check the queue manager's error log for more information about the error.
10 : Warning
Check the queue manager's error log for more information about the error.
10 : Warning
The message sequence number parameter was not valid.
10 : Warning
20 : Error
The communications subsystem is not available.
10 : Warning
The queue specified in the channel definition was not a transmission queue.
10 : Warning
Could not create object because the object already existed.
10 : Warning
An attempt was made to delete, change or clear an object that is in use.
Wait until the object is not in use, then try again.
10 : Warning
10 : Warning
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.
10 : Warning
10 : Warning
10 : Warning
10 : Warning
The channel stopped because the remote queue manager was terminating.
10 : Warning
The channel could not be started because the remote queue manager was not available.
Ensure that the remote queue manager is started, and that it is configured to accept incoming communication requests.
10 : Warning
10 : Warning
10 : Warning
There is no definition of this channel on the remote system.
10 : Warning
The channel was closed because the user exit specified does not exist.
20 : Error
10 : Warning
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.
10 : Warning
The Scope attribute of the queue was set to MQSCO_CELL but no name service supporting a cell directory has been configured.
Configure a name service to support the cell directory.
10 : Warning
Supply a non-blank transmission queue name for this channel type.
10 : Warning
Supply a non-blank connection name for this channel type.
10 : Warning
Check that the queues whose names start with 'SYSTEM.CLUSTER.' are not full and that messages are allowed to be put on them.
10 : Warning
The queue is a transmission queue and cannot be shared in a cluster.
10 : Warning
10 : Warning
WebSphere MQ Explorer uses the queue called 'SYSTEM.ADMIN.COMMAND.QUEUE' to administer the queue manager.
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.
10 : Warning
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.
10 : Warning
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.
0 : Information
10 : Warning
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.
0 : Information
To administer a cluster, the WebSphere MQ Explorer needs a connection to the repository queue manager.
0 : Information
Check with the user before clearing the password from the channel. Continue only if you really want to clear the password.
10 : Warning
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.)
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.)
10 : Warning
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.)
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.)
10 : Warning
The WebSphere MQ Explorer can only establish connections to remote queue managers using TCP/IP.
To complete removal of the queue manager from the cluster, issue the RESET CLUSTER ACTION(FORCEREMOVE) command from the repository queue manager.
10 : Warning
A connection could not be made to the specified remote queue manager.
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.
10 : Warning
The given channel definition table is not in the correct format.
Specify a file in the correct format.
10 : Warning
Other plug-ins have responded to the attempted removal of this queue manager by indicating that they are still using it.
Ensure that the other plug-ins have finished using the queue manager before trying to delete it again.
10 : Warning
A confirmation is required before the queue manager is deleted.
Continue only if you want to permanently delete the queue manager.
10 : Warning
An unexpected reason code was returned from a MQGET API request. Use the reason code to determine the underlying reason why the request failed.
The MQGET request was not successful. Some messages might not have been retrieved.
10 : Warning
An unexpected reason code was returned from a MQPUT API request. Use the reason code to determine the underlying reason why the request failed.
MQPUT processing was unsuccessful. No message was placed on the queue.
0 : Information
The object of the specified type and name has been successfully deleted.
none.
10 : Warning
An unexpected reason code was returned from an MQOPEN API request. The queue has not been opened.
Use the reason code to determine the underlying reason for the failure.
10 : Warning
One of the underlying API requests was unsuccessful. The test message was not placed on the queue.
20 : Error
Specify a different value.
20 : Error
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.
Ensure that the Eclipse workspace has not been corrupted.
30 : Severe error
An error was encountered when trying to execute the iKeyMan program.
Try again, and if symptoms persist contact the System Administrator.
10 : Warning
The Java API System.getProperty("user.id") threw a SecurityException.
Configure your Java security environment using the 'policytool' to allow WebSphere MQ Explorer to query the 'user.id'.
10 : Warning
The SWT Browser control depends on Mozilla being installed.
Ensure that the Mozilla browser is correctly installed.
10 : Warning
The SWT Browser control depends on the system browser being installed.
Ensure that the system browser is correctly installed.
10 : Warning
A confirmation is required before the specified object is stopped. The type of object and name are provided in the message.
Continue only if you want to stop the object.
10 : Warning
Continue only if you want to remove the queue manager.
0 : Information
Select Yes to create the channel.
0 : Information
Select Yes to delete the channel.
10 : Warning
Deleting all FFSTs and Trace from this machine means that any historical error logs and trace will be lost.
Select Yes to clear FFSTs and Trace
0 : Information
Message for information only.
10 : Warning
Importing settings into the WebSphere MQ Explorer will overwrite the current settings.
Continue only if you want to overwrite the current settings.
0 : Information
Message for information only.
10 : Warning
10 : Warning
10 : Warning
A problem has occurred when issuing a command to the command server to create the channel.
Try again, and if symptoms persist contact the Systems Administrator.
10 : Warning
A problem has occurred with the underlying data model, and the channel could not be created.
Try again, and if symptoms persist contact the Systems Administrator.
10 : Warning
A problem has occurred issuing a command to the command server to delete the channel.
Ensure that the channel is not in use and try again. If symptoms persist, contact the Systems Administrator.
10 : Warning
A connection could not be made to the specified remote queue manager.
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.
40 : Stop Error
To load the WebSphere MQ Explorer, a valid workspace is required.
Ensure that you can write to the Eclipse workspace.
40 : Stop Error
To load the WebSphere MQ Explorer, write access to the workspace is required.
Ensure that you can write to the Eclipse workspace.
0 : Information
Message for information only.
0 : Information
A user request to start the listener was accepted by WebSphere MQ.
Message for information only.
0 : Information
A user request to stop the listener was accepted by WebSphere MQ.
Message for information only.
0 : Information
A user request to start the service was accepted by WebSphere MQ.
Message for information only.
0 : Information
A user request to stop the service was accepted by WebSphere MQ.
Message for information only.
10 : Warning
10 : Warning
Ensure that the service has a start command specified.
10 : Warning
Ensure that the service has a stop command specified.
10 : Warning
10 : Warning
10 : Warning
10 : Warning
Ensure that the client connection has the correct queue manager name and connection name before trying to start.
10 : Warning
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.
Check the Queue Manager error logs for further details on the cause of the failure, correct the problem and try again.
20 : Error
The parameter specified when trying to create or alter an object is not valid.
Ensure that valid parameters are specified, then try again.
0 : Information
Try to clear the password again later.
10 : Warning
The attempt to change the password failed because of an error.
Try a different password
0 : Information
Message for information only.
10 : Warning
You must enter a new password in both the new and confirm password fields.
Enter a new password in the new password field.
10 : Warning
You must enter a new password in both the new and confirm password fields.
Re-enter the new password in the confirm new password field.
10 : Warning
You must enter the same new password in both the new and confirm password fields.
Ensure that the passwords in the new and confirm fields match.
20 : Error
No objects will be displayed in the currently selected view.
Check the problem determination information, and ensure that WebSphere MQ and the queue manager in question are both running correctly.
20 : Error
The WebSphere MQ Explorer cannot listen for objects, so no objects will be displayed in the currently selected view.
Check the problem determination information, and ensure that WebSphere MQ and the queue manager in question are both running correctly.
20 : Error
The object name specified when trying to create or alter an object is not valid.
Ensure that a valid object name is specified, then try again.
20 : Error
A request for information from the queue manager failed.
Try the operation again. If the error persists, examine the problem determination information to see if any details have been recorded.
20 : Error
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.
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.
10 : Warning
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.
Check that tracing is disabled, and that the WebSphere MQ Explorer has appropriate access permission to delete the Trace and FFST files.
0 : Information
Message for information only.
20 : Error
Only certain combinations and values are valid for the object your are trying to alter or create. Please check the values and try again.
Specify a valid value and try again.
20 : Error
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.
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.
20 : Error
The connection to WebSphere MQ is quiescing, so no new information can be queried.
Wait for the connection to end, then try reconnecting.
20 : Error
A disposition conflict was detected. Please ensure that all disposition related fields are correct for this type of object.
Ensure that all disposition related fields are correct for this type of object and try again.
20 : Error
A string value has been modified or supplied that is too long when creating or modifying an object.
Check the values being supplied and try again.
20 : Error
When creating or modifying an object, the combination of parameters specified is not valid.
Check that the combination specified is valid for the object and try again.
10 : Warning
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.
If you choose not to continue waiting, restart the WebSphere MQ Explorer, if the problem persists check for problem determination information.
10 : Warning
The query did not find any objects.
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.
10 : Warning
WebSphere MQ issued a query that required the queue manager to be a member of a queue-sharing group.
Try the operation again, if the problem persists check the problem determination information for more details.
20 : Error
20 : Error
Try again. If the error persists, examine the problem determination information to see if any details have been recorded.
20 : Error
Try again. If the error persists, examine the problem determination information to see if any details have been recorded.
0 : Information
Restart WebSphere MQ explorer to apply the imported settings
10 : Warning
A confirmation is required before the queue manager is removed from the cluster.
Continue only if you want to permanently remove the queue manger from the cluster.
20 : Error
The queue manager has not been removed from the cluster.
Try the operation again. If the error persists, examine the problem determination information to see if any information has been recorded.
20 : Error
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.
Try the operation again. If the error persists, examine the problem determination information to see if any information has been recorded.
20 : Error
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.
To completely remove the queue manager, ensure that all the CLUSTER fields of associated cluster channels are cleared.
10 : Warning
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.
20 : Error
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.
Change the characters used, then try the operation again.
20 : Error
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.
Check that the queue manager's default transmission queue property (DefXmitQName) specifies a valid local queue.
10 : Warning
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.
Restart the WebSphere MQ Explorer and try the operation again. If the problem persists check for problem determination information.
20 : Error
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.
Retry the command or operation against an object or queue whose type is valid for the operation requested.
20 : Error
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.
Correct the queue definitions.
20 : Error
Check the path specified and try again.
10 : Warning
Explorer uses the queue <insert_0> to administer queue managers.
Define the queue <insert_0> and retry.
10 : Warning
Explorer uses the queue <insert_0> to administer this queue manager.
Allow Explorer to open the queue <insert_0> and retry.
10 : Warning
Explorer uses the queue <insert_0> to administer this queue manager.
Allow Explorer to open the queue <insert_0> and retry.
10 : Warning
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.
Continue only if you want to forcibly remove the queue manager.
0 : Information
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.
10 : Warning
To make the queue available to the members of this cluster, you must join the queue manager to the cluster.
10 : Warning
The list of values that you have entered is too long. The maximum number of characters allowed for this value is <insert_0>.
10 : Warning
You have entered a value containing too many characters. The maximum number of characters allowed for each value of this attribute is <insert_0>.
10 : Warning
You have entered too many values in the list. The maximum number of values is <insert_0>.
10 : Warning
Try the operation again when the queue manager is available. If the queue manager no longer exists, you can choose to forcibly remove the queue manager from the cluster.
10 : Warning
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.
If the queue manager no longer exists, you can choose to forcibly remove the queue manager from the cluster.
0 : Information
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.
0 : Information
Message for information only.
0 : Information
Message for information only.
0 : Information
Message for information only.
0 : Information
Message for information only.
10 : Warning
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.
10 : Warning
Views showing cluster queues in this cluster might not be complete.
10 : Warning
The queue manager's cluster workload exit failed unexpectedly or did not respond in time.
10 : Warning
The definition of the cluster queue could not be resolved correctly because a response from a repository queue manager was not available.
10 : Warning
The queue manager's cluster workload exit rejected a call to open or put a message onto a cluster queue.
10 : Warning
At the time that the message was put, there were no longer any instances of the queue in the cluster.
10 : Warning
10 : Warning
This value does not accept lists.
If you want to use a comma as part of a value, enclose the value in double quotes.
10 : Warning
A problem occurred while defining objects or modifying the queue manager's properties.
Ensure that the default objects exist for the queue manager.
10 : Warning
A problem occurred while defining objects or modifying one of the queue managers' properties.
Ensure that the default objects exist for the queue manager.
10 : Warning
You might prevent the queue manager from starting if you change the Key Repository field to a location which is not valid.
Ensure that the location specified is correct before continuing.
0 : Information
Message for information only.
30 : Severe error
30 : Severe error
30 : Severe error
30 : Severe error
30 : Severe error
30 : Severe error
30 : Severe error
Examine the problem determination information on this computer to establish the cause of the error.
30 : Severe error
Examine the problem determination information on this computer to establish the cause of the error.
30 : Severe error
Ensure the queue manager is running and is configured to accept remote connections.
30 : Severe error
Ensure the queue manager is running.
30 : Severe error
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.
30 : Severe error
Examine the problem determination information on this computer to establish the cause of the error.
30 : Severe error
The file name specified was not recognized.
Ensure that the file exists at the specified location and can be read.
30 : Severe error
There was an error when the system tried to read the Client channel definition table.
Ensure that the file exists at the specified location and can be read.
30 : Severe error
There was an error when the system tried to read the file.
Ensure that the file exists at the specified location and can be read.
10 : Warning
The connection was not found. Possibly the connection was closed before the command was issued.
Check that the application connection has not been closed in the background.
20 : Error
The connection could not be closed due to a PCF error.
Check for FFSTs.
30 : Severe error
The command server has stopped for some reason, so the request cannot be processed.
Start the command server. If the error persists, examine the problem determination information to see if any details have been recorded.
0 : Information
The request to close the connection to an application was successful.
Message for information only.
0 : Information
WebSphere MQ explorer is about to stop a connection, stopping the connection will prevent further communication between MQ and the application in question.
Select yes if you want to stop the connection.
10 : Warning
The specified PCF command is not supported by this queue manager.
30 : Severe error
An error occurred while starting this application.
Check that the WebSphere MQ runtime libraries are available.
Check that the PATH system environment variable includes the directory for these runtime libraries.)
10 : Warning
To launch the standalone Eclipse help system, the WebSphere MQ file transfer application needs to know where it is installed.
Check that Eclipse has been installed with WebSphere MQ.
10 : Warning
The WebSphere MQ file transfer application failed to create an instance of the Eclipse standalone help system.
Check that Eclipse has been installed with WebSphere MQ.
10 : Warning
The WebSphere MQ file transfer application failed to start the standalone Eclipse system.
Check that Eclipse has been installed with WebSphere MQ.
10 : Warning
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
Check that the read/write properties on this file allow you to write to it.
10 : Warning
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
Check that the read/write properties on this file allow you to write to it.
10 : Warning
Specify a value of 1000 to 100 000 000.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
wmqem |