9000-9999 - Remote

 

See Reading a message for an explanation of how to interpret these messages.

AMQ9001
Channel <insert_3> ended normally.
Severity:

0 : Information

Explanation:

Channel <insert_3> ended normally.

Response:

None.

AMQ9002
Channel <insert_3> is starting.
Severity:

0 : Information

Explanation:

Channel <insert_3> is starting.

Response:

None.

AMQ9003 (iSeries)
Channel <insert_3> last message sequence number is <insert_1>.
Severity:

0 : Information

Explanation:

Channel <insert_3> last message sequence number is <insert_1>.

Response:

None.

AMQ9004 (iSeries)
Channel <insert_3> status information.
Severity:

0 : Information

Explanation:

Channel <insert_3> status information: Number of Messages in Doubt - <insert_1> In Doubt Sequence Number - <insert_2> In Doubt Logic Unit of Work ID - <insert_4>

Response:

None.

AMQ9181
The response set by the exit is not valid.
Severity:

30 : Severe error

Explanation:

The user exit <insert_3> returned a response code <insert_1> that is not valid in the ExitResponse field of the channel exit parameters (MQCXP). Message AMQ9190 is issued giving more details, and the channel stops.

Response:

Investigate why the user exit program set a response code that is not valid.

AMQ9182
The secondary response set by the exit is not valid.
Severity:

30 : Severe error

Explanation:

The user exit <insert_3> returned a secondary response code <insert_1> in the ExitResponse2 field of the channel exit parameters (MQCXP) that is not valid. Message AMQ9190 is issued giving more details, and the channel stops.

Response:

Investigate why the user exit program set a secondary response code that is not valid.

AMQ9184
The exit buffer address set by the exit is not valid.
Severity:

30 : Severe error

Explanation:

The user exit <insert_3> returned an address <insert_1> for the exit buffer that is not valid, when the secondary response code in the ExitResponse2 field of the channel exit parameters (MQCXP) is set to MQXR2_USE_EXIT_BUFFER. Message AMQ9190 is issued giving more details, and the channel stops.

Response:

Investigate why the user exit program set an exit buffer address that is not valid. The most likely cause is the failure to set a value, so that the value is 0.

AMQ9185
The exit space set by the exit is not valid.
Severity:

30 : Severe error

Explanation:

The user exit <insert_3> returned an exit space value <insert_1> that is not valid in the ExitSpace field of the channel exit parameters (MQCXP). Message AMQ9190 is issued giving more details, and the channel stops.

Response:

Investigate why the user exit program set an exit space value that is not valid. Correct the error.

AMQ9186
Too much exit space reserved by send exits.
Severity:

30 : Severe error

Explanation:

At exit initialization the send exits in the send exit chain for channel <insert_3> returned values in the ExitSpace field of the channel exit parameters (MQCXP). The total of these ExitSpace values is <insert_1>. The maximum number of bytes that can be sent in a single transmission is <insert_2>. Room must be left for at least 1024 bytes of message data in each transmission. So too much exit space has been reserved by the send exits. The channel stops.

Response:

Investigate why the send exit programs set exit space values that are too large. Correct the error.

AMQ9187
The header compression value set by the exit is not valid.
Severity:

30 : Severe error

Explanation:

The user exit <insert_3> returned a header compression value <insert_1> in the CurHdrCompression field of the channel exit parameters (MQCXP) that was not one of the negotiated supported values specified in the HdrCompList field of the channel description (MQCD). Message AMQ9190 is issued giving more details, and the channel stops.

Response:

Investigate why the user exit program specified a header compression value that was not one of the negotiated supported values.

AMQ9188
The message compression value set by the exit is not valid.
Severity:

30 : Severe error

Explanation:

The user exit <insert_3> returned a message compression value <insert_1> in the CurMsgCompression field of the channel exit parameters (MQCXP) that was not one of the negotiated supported values specified in the MsgCompList field of the channel description (MQCD). Message AMQ9190 is issued giving more details, and the channel stops.

Response:

Investigate why the user exit program specified a message compression value that was not one of the negotiated supported values.

AMQ9189
The data length set by the exit is not valid.
Severity:

30 : Severe error

Explanation:

The user exit <insert_3> returned a data length value <insert_1> that was not greater than zero. Message AMQ9190 is issued giving more details, and the channel stops.

Response:

Investigate why the user exit program set a data length that is not valid.

AMQ9190
Channel stopping because of an error in the exit.
Severity:

30 : Severe error

Explanation:

The user exit <insert_3>, invoked for channel <insert_4> with id <insert_1> and reason <insert_2>, returned values that are not valid, as reported in the preceding messages. The channel stops.

Response:

Investigate why the user exit program set values that are not valid.

AMQ9195
Data length larger than maximum segment length.
Severity:

30 : Severe error

Explanation:

The data length <insert_1> set by send exit <insert_3> is larger than the maximum segment length (<insert_2>). The maximum segment length is the maximum number of bytes that can be sent in a single transmission minus the user exit space required by all the send exits subsequent to the current one in the send exit chain. Message AMQ9190 is issued giving more details, and the channel stops.

Response:

Investigate why the user exit program set a data length that is not valid. Correct the error.

AMQ9196
Data length is larger than the agent buffer length.
Severity:

30 : Severe error

Explanation:

The data length <insert_1> set by exit <insert_3> is larger than the agent buffer length. The user exit returned data in the supplied agent buffer, but the length specified is greater than the length of the buffer. Message AMQ9190 is issued giving more details, and the channel stops.

Response:

Investigate why the user exit program set a data length that is not valid. Correct the error.

AMQ9197
Data length is larger than the exit buffer length.
Severity:

30 : Severe error

Explanation:

The data length <insert_1> set by exit <insert_3> is larger than the exit buffer length. The user exit returned data in the supplied exit buffer, but the length specified is greater than the length of the buffer. Message AMQ9190 is issued giving more details, and the channel stops.

Response:

Investigate why the user exit program set a data length that is not valid.

AMQ9201
Allocate failed to host <insert_3>.
Severity:

30 : Severe error

Explanation:

The attempt to allocate a conversation using <insert_4> to host <insert_3> was not successful.

Response:

The error may be due to an incorrect entry in the <insert_4> parameters contained in the channel definition to host <insert_3>. Correct the error and try again. If the error persists, record the error values and contact your systems administrator. The return code from the <insert_4><insert_5> call was <insert_1> (X<insert_2>). It may be possible that the listening program at host <insert_3> is not running. If this is the case, perform the relevant operations to start the listening program for protocol <insert_4> and try again.

AMQ9202
Remote host <insert_3> not available, retry later.
Severity:

30 : Severe error

Explanation:

The attempt to allocate a conversation using <insert_4> to host <insert_3> was not successful. However the error may be a transitory one and it may be possible to successfully allocate a <insert_4> conversation later.

Response:

Try the connection again later. If the failure persists, record the error values and contact your systems administrator. The return code from <insert_4> is <insert_1> (X<insert_2>). The reason for the failure may be that this host cannot reach the destination host. It may also be possible that the listening program at host <insert_3> was not running. If this is the case, perform the relevant operations to start the <insert_4> listening program, and try again.

AMQ9203
A configuration error for <insert_4> occurred.
Severity:

30 : Severe error

Explanation:

Error in configuration for communications to host <insert_3>. Allocation of a <insert_4> conversation to host <insert_3> was not possible.

Response:

The configuration error may be one of the following:

1.If the communications protocol is LU 6.2, it may be that one of the transmission parameters (Mode, or TP Name) is incorrect. Correct the error and try again. The mode name should be the same as the mode defined on host <insert_3>. The TP name on <insert_3> should be defined.

2.If the communications protocol is LU 6.2, it may be that an LU 6.2 session has not been established. Contact your systems administrator.

3.If the communications protocol is TCP/IP, it may be that the host name specified is incorrect. Correct the error and try again.

4.If the communications protocol is TCP/IP, it may be that the host name specified cannot be resolved to a network address. The host name may not be in the nameserver.
The return code from the <insert_4><insert_5> call was <insert_1> (X<insert_2>).
Record the error values and tell the system administrator.

AMQ9204
Connection to host <insert_3> rejected.
Severity:

30 : Severe error

Explanation:

Connection to host <insert_3> over <insert_4> was rejected.

Response:

The remote system may not be configured to allow connections from this host. Check the <insert_4> listener program has been started on host <insert_3>.
If the conversation uses LU 6.2, it is possible that either the User ID or Password supplied to the remote host is incorrect.
If the conversation uses TCP/IP, it is possible that the remote host does not recognize the local host as a valid host.
The return code from the <insert_4><insert_5> call was <insert_1> X(<insert_2>).
Record the error values and tell the systems administrator.

AMQ9205
The host name supplied is not valid.
Severity:

30 : Severe error

Explanation:

The supplied <insert_4> host name <insert_3> could not be resolved into a network address. Either the name server does not contain the host, or the name server was not available.

Response:

Check the <insert_4> configuration on your host.

AMQ9206
Error sending data to host <insert_3>.
Severity:

30 : Severe error

Explanation:

An error occurred sending data over <insert_4> to <insert_3>. This may be due to a communications failure.

Response:

The return code from the <insert_4><insert_5> call was <insert_1> X(<insert_2>). Record these values and tell your systems administrator.

AMQ9207
The data received from host <insert_3> is not valid.
Severity:

30 : Severe error

Explanation:

Incorrect data format received from host <insert_3> over <insert_4>. It may be that an unknown host is attempting to send data. An FFST file has been generated containing the invalid data received.

Response:

Tell the systems administrator.

AMQ9208
Error on receive from host <insert_3>.
Severity:

30 : Severe error

Explanation:

An error occurred receiving data from <insert_3> over <insert_4>. This may be due to a communications failure.

Response:

The return code from the <insert_4><insert_5> call was <insert_1> (X<insert_2>). Record these values and tell the systems administrator.

AMQ9209
Connection to host <insert_3> closed.
Severity:

30 : Severe error

Explanation:

An error occurred receiving data from <insert_3> over <insert_4>. The connection to the remote host has unexpectedly terminated.

Response:

Tell the systems administrator.

AMQ9210
Remote attachment failed.
Severity:

30 : Severe error

Explanation:

There was an incoming attachment from a remote host, but the local host could not complete the bind.

Response:

The return code from the <insert_4><insert_5> call was <insert_1> (X<insert_2>). Record these values and tell the systems administrator who should check the <insert_4> configuration.

AMQ9211
Error allocating storage.
Severity:

30 : Severe error

Explanation:

The program was unable to obtain enough storage.

Response:

Stop some programs which are using storage and retry the operation. If the problem persists contact your systems administrator.

AMQ9212
A TCP/IP socket could not be allocated.
Severity:

30 : Severe error

Explanation:

A TCP/IP socket could not be created, possibly because of a storage problem.

Response:

The return code from the <insert_4><insert_5> call was <insert_1> (X<insert_2>). Try the program again. If the failure persists, record the error values and tell the systems administrator.

AMQ9213
A communications error for <insert_4> occurred.
Severity:

30 : Severe error

Explanation:

An unexpected error occurred in communications.

Response:

The return code from the <insert_4><insert_5> call was <insert_1> (X<insert_2>). Record these values and tell the systems administrator.

AMQ9214
Attempt to use an unsupported communications protocol.
Severity:

30 : Severe error

Explanation:

An attempt was made to use an unsupported communications protocol type <insert_2>.

Response:

Check the channel definition file. It may be that the communications protocol entered is not a currently supported one.

AMQ9215
Communications subsystem unavailable.
Severity:

30 : Severe error

Explanation:

An attempt was made to use the communications subsystem, but it has not been started.

Response:

Start the communications subsystem, and rerun the program.

AMQ9216
Usage: <insert_3> [-m QMgrName] [-n TPName]
Severity:

20 : Error

Explanation:

Values passed to the responder channel program are not valid. The parameters that are not valid are as follows :-
<insert_4>
The responder channel program exits.

Response:

Correct the parameters passed to the channel program and retry the operation.

AMQ9216 (AIX)
Usage: <insert_3> [-m QMgrName]
Severity:

20 : Error

Explanation:

Values passed to the responder channel program are not valid. The parameters that are not valid are as follows :-
<insert_4>
The responder channel program exits.

Response:

Correct the parameters passed to the channel program and retry the operation.

AMQ9216 (HP-UX)
Usage: <insert_3> [-m QMgrName]
Severity:

20 : Error

Explanation:

Values passed to the responder channel program are not valid. The parameters that are not valid are as follows :-
<insert_4>
The responder channel program exits.

Response:

Correct the parameters passed to the channel program and retry the operation.

AMQ9217
The TCP/IP listener program could not be started.
Severity:

30 : Severe error

Explanation:

An attempt was made to start a new instance of the listener program, but the program was rejected.

Response:

The failure could be because either the subsystem has not been started (in this case you should start the subsystem), or there are too many programs waiting (in this case you should try to start the listener program later).

AMQ9218
The <insert_4> listener program could not bind to port number <insert_1>.
Severity:

30 : Severe error

Explanation:

An attempt to bind the <insert_4> socket to the listener port was unsuccessful.

Response:

The failure could be due to another program using the same port number. The return code from the <insert_3> call for port <insert_5><insert_1> was <insert_2>. Record these values and tell the systems administrator.

AMQ9219
The TCP/IP listener program could not create a new connection for the incoming conversation.
Severity:

30 : Severe error

Explanation:

An attempt was made to create a new socket because an attach request was received, but an error occurred.

Response:

The failure may be transitory, try again later. If the problem persists, record the return code <insert_1> and tell the systems administrator. It may be necessary to free some jobs, or restart the communications system.

AMQ9220
The <insert_4> communications program could not be loaded.
Severity:

30 : Severe error

Explanation:

The attempt to load the <insert_4> library or procedure <insert_3> failed with error code <insert_1>.

Response:

Either the library must be installed on the system or the environment changed to allow the program to locate it.

AMQ9221
Unsupported protocol was specified.
Severity:

30 : Severe error

Explanation:

The specified value of <insert_3> was not recognized as one of the protocols supported.

Response:

Correct the parameter and retry the operation.

AMQ9222
Cannot find the configuration file.
Severity:

10 : Warning

Explanation:

The configuration file <insert_3> cannot be found. This file contains default definitions for communication parameters. Default values will be used.

Response:

None.

AMQ9223
Enter a protocol type.
Severity:

30 : Severe error

Explanation:

The operation you are performing requires that you enter the type of protocol.

Response:

Add the protocol parameter and retry the operation.

AMQ9224
Unexpected token detected.
Severity:

30 : Severe error

Explanation:

On line <insert_1> of the INI file, keyword <insert_3> was read when a keyword was expected.

Response:

Correct the file and retry the operation.

AMQ9224 (Windows)
Unexpected token detected.
Severity:

30 : Severe error

Explanation:

Keyword <insert_3> was read when a keyword was expected.

Response:

Correct the configuration data and retry the operation.

AMQ9225
File syntax error.
Severity:

30 : Severe error

Explanation:

A syntax error was detected on line <insert_1> while processing the INI file.

Response:

Correct the problem and retry the operation.

AMQ9225 (Windows)
File syntax error.
Severity:

30 : Severe error

Explanation:

A syntax error was detected while processing the configuration data.

Response:

Correct the problem and retry the operation.

AMQ9226
Usage: <insert_3> [-m QMgrName] -t (TCP | LU62 | NETBIOS | SPX) [ProtocolOptions]
Severity:

10 : Warning

Explanation:

Values passed to the listener program were invalid.
The parameter string passed to this program is as follows:
[-m QMgrName] ( -t TCP [-p Port] |
-t LU62 [-n TPName] |
-t NETBIOS [-l LocalName] [-e Names] [-s Sessions]
[-o Commands] [-a Adaptor] |
-t SPX [-x Socket])
Default values will be used for parameters not supplied.

Response:

Correct the parameters passed to the listener program and retry the operation.

AMQ9226 (AIX)
Usage: <insert_3> [-m QMgrName] -t TCP [ProtocolOptions]
Severity:

10 : Warning

Explanation:

Values passed to the listener program were invalid.
The parameter string passed to this program is as follows:
[-m QMgrName] -t TCP [-p Port]
Default values will be used for parameters not supplied.

Response:

Correct the parameters passed to the listener program and retry the operation.

AMQ9226 (Unix)
Usage: <insert_3> [-m QMgrName] -t TCP [ProtocolOptions]
Severity:

10 : Warning

Explanation:

Values passed to the listener program were invalid.
The parameter string passed to this program is as follows:
[-m QMgrName] -t TCP [-p Port]
Default values will be used for parameters not supplied.

Response:

Correct the parameters passed to the listener program and retry the operation.

AMQ9227
<insert_3> local host name not provided.
Severity:

30 : Severe error

Explanation:

A name is required for the <insert_3> process to register with the network.

Response:

Add a local name to the configuration file and retry the operation.

AMQ9228
The <insert_4> responder program could not be started.
Severity:

30 : Severe error

Explanation:

An attempt was made to start an instance of the responder program, but the program was rejected.

Response:

The failure could be because either the subsystem has not been started (in this case you should start the subsystem), or there are too many programs waiting (in this case you should try to start the responder program later). The <insert_5> reason code was <insert_1>.

AMQ9229
The application has been ended.
Severity:

30 : Severe error

Explanation:

You have issued a request to end the application.

Response:

None.

AMQ9230
An unexpected <insert_4> event occurred.
Severity:

30 : Severe error

Explanation:

During the processing of network events, an unexpected event <insert_1> occurred.

Response:

None.

AMQ9231
The supplied parameter is not valid.
Severity:

30 : Severe error

Explanation:

The value of the <insert_4> <insert_5> parameter has the value <insert_3>. This value has either not been specified or has been specified incorrectly.

Response:

Check value of the <insert_5> parameter and correct it if necessary. If the fault persists, record the return code (<insert_1>,<insert_2>) and <insert_4> and tell the systems administrator.

AMQ9232
No <insert_3> specified
Severity:

30 : Severe error

Explanation:

The operation requires the specification of the <insert_3> field.

Response:

Specify the <insert_3> and retry the operation.

AMQ9233
Error creating <insert_3> thread.
Severity:

30 : Severe error

Explanation:

The process attempted to create a new thread. The most likely cause of this problem is a shortage of an operating system resource (for example: memory). Use any previous FFSTs to determine the reason for the failure. The WebSphere MQ internal return code describing the reason for the failure is <insert_1>.

Response:

Contact the systems administrator. If the problem persists contact your IBM support center.

AMQ9235
The supplied local communications address cannot be resolved.
Severity:

30 : Severe error

Explanation:

The local communications address (LOCLADDR) value <insert_3> cannot be resolved into an IP address.

Response:

Enter a local communications address value which can be resolved into an IP address, and try again.

AMQ9236
The supplied Partner LU was invalid.
Severity:

30 : Severe error

Explanation:

The <insert_4> Partner LU name <insert_3> was invalid.

Response:

Either the Partner LU name was entered incorrectly or it was not in the <insert_4> communications configuration. Correct the error and try again.

AMQ9237
A configuration error for <insert_4> occurred.
Severity:

30 : Severe error

Explanation:

Allocation of a <insert_4> conversation to host <insert_3> was not possible. The configuration error may be one of the following:
1. It may be that one of the transmission parameters (Mode, or TP Name) was incorrect. Correct the error and try again. The mode name should be the same as the mode defined on host <insert_3>. The TP name on <insert_3> should be defined.

2. It may be that an LU 6.2 session has not been established. Contact your systems administrator.
The return code from <insert_4> is <insert_1> with associated <insert_5> <insert_2>.

Response:

Record the error values and tell the system administrator.

AMQ9238
A communications error for <insert_4> occurred.
Severity:

30 : Severe error

Explanation:

An unexpected error occurred in communications.

Response:

The return code from the <insert_4><insert_3> call was <insert_1> with associated <insert_5> <insert_2>.

AMQ9239
Usage: <insert_3> [-m QMgrName] -n TpName -g Gateway-name
Severity:

10 : Warning

Explanation:

Values passed to the listener program were invalid. The parameter string passed to this program is as follows, default values being used for parameters not supplied: [-m QMgrName] -n TpName -g Gateway-name

Response:

Correct the parameters passed to the listener program and retry the operation.

AMQ9240
An SPX socket was already in use.
Severity:

30 : Severe error

Explanation:

The Listener received return code <insert_1> when attempting to open socket <insert_2>.

Response:

The specified socket is already in use by another process. To use another socket specify another socket on the command line to RUNMQLSR or update the default in the qm.ini file.

AMQ9240 (iSeries)
An SPX socket was already in use.
Severity:

30 : Severe error

Explanation:

The Listener received return code <insert_1> when attempting to open socket <insert_2>.

Response:

The specified socket is already in use by another process. To use another socket specify another socket on the command line to STRMQMLSR or update the default in the qm.ini file.

AMQ9240 (Windows)
An SPX socket was already in use.
Severity:

30 : Severe error

Explanation:

The listener received return code <insert_1> when attempting to open socket <insert_2>.

Response:

The specified socket is already in use by another process. To use another socket, specify a different socket on the command line to the runmqlsr command, or update the default in the configuration data.

AMQ9241
SPX is not available.
Severity:

30 : Severe error

Explanation:

WebSphere MQ received return code <insert_1> when attempting to start SPX communications.

Response:

Ensure that IPX/SPX support is installed on the machine and that it is started before trying to start a WebSphere MQ SPX channel.

AMQ9242
SPX resource problem.
Severity:

30 : Severe error

Explanation:

WebSphere MQ received return code <insert_1> when attempting to start SPX communications, indicating a resource problem.

Response:

Ensure that sufficient IPX/SPX resources are available before commencing communications over IPX/SPX.

AMQ9243
The queue manager <insert_3> does not exist.
Severity:

30 : Severe error

Explanation:

You tried to perform an action against a queue manager that does not exist. You may have specified the wrong queue manager name.

Response:

If you specified the wrong name, correct the name and submit the command again. If the queue manager does not exist, create the queue manager and submit the command again.

AMQ9244
The default queue manager does not exist.
Severity:

30 : Severe error

Explanation:

You tried to perform an action against a queue manager that does not exist.

Response:

Create the default queue manager and submit the command again.

AMQ9245 (Windows)
Unable to obtain account details for channel MCA user ID.
Severity:

10 : Warning

Explanation:

WebSphere MQ was unable to obtain the account details for MCA user ID <insert_3>. This user ID was the MCA user ID for channel <insert_4> on queue manager <insert_5> and may have been defined in the channel definition, or supplied either by a channel exit or by a client.

Response:

Ensure that the user ID is correct and that it is defined on the Windows local system, the local domain or on a trusted domain. For a domain user ID, ensure that all necessary domain controllers are available.

AMQ9246
The TCP/IP listener on port <insert_1> could not start a new channel.
Severity:

30 : Severe error

Explanation:

An attempt has been made to connect to the queue manager by starting a new channel within the TCP/IP listener which is listening on port <insert_1>. The maximum socket number which can be used by a channel running on this listener is <insert_2>. A socket number beyond this maximum was allocated for the new channel. This connection attempt has been rejected, but the listener continues to listen for further connection requests. The socket number allocated for a new listener channel is related to the number of channels currently running within that listener process. The problem has arisen because too many channels are directed at the port on which this listener is listening.

Response:

An extra listener process should be started to listen on a different port. Some of the channels to the queue manager should be redirected from the port on which the existing listener is listening to the new port.

AMQ9247
SSPI Security: bad return from SSPI call.
Severity:

30 : Severe error

Explanation:

Channel <insert_3> has been closed because the SSPI channel exit received a bad return code from SSPI.

Response:

Consult the appropriate SSPI manuals to find out the meaning of status <insert_4> on call <insert_5>, and correct the error.

AMQ9248
The program could not bind to a <insert_3> socket.
Severity:

30 : Severe error

Explanation:

The attempt to bind to socket <insert_4> failed with return code <insert_1>. The failing <insert_3> call was <insert_5>. The most likely cause of this problem is incorrect configuration of the <insert_3> local address or incorrect start and end port parameters.

Response:

Contact the system administrator. If the problem persists contact your IBM support center.

AMQ9255
Listener already running.
Severity:

30 : Severe error

Explanation:

The request to start the WebSphere MQ listener failed because there is already a listener running against the specified network resources.

Response:

None.

AMQ9259
Connection timed out from host <insert_3>.
Severity:

30 : Severe error

Explanation:

A connection from host <insert_3> over <insert_4> timed out.

Response:

Check to see why data was not received in the expected time. Correct the problem. Reconnect the channel, or wait for a retrying channel to reconnect itself.

AMQ9401
Channel <insert_3> autodefined.
Severity:

0 : Information

Explanation:

Channel <insert_3> which did not previously exist has been autodefined.

Response:

None.

AMQ9402
Autodefinition exit for Channel <insert_3> failed to load.
Severity:

30 : Severe error

Explanation:

Autodefinition of Channel <insert_3> failed because <insert_4> would not load.

Response:

Ensure that the user exit is specified correctly in the queue manager definition, and that the user exit program is correct and available.

AMQ9403
Autodefinition of Channel <insert_3> suppressed by user exit.
Severity:

30 : Severe error

Explanation:

Autodefinition exit <insert_4> for Channel <insert_3> returned a failure code.

Response:

None.

AMQ9404
REFRESH CLUSTER REPOS(YES) command processed, cluster <insert_4>, <insert_1> objects changed.
Severity:

0 : Information

Explanation:

The queue manager successfully processed a REFRESH CLUSTER command with the REPOS(YES) option for the indicated cluster.

Response:

None.

AMQ9405
FORCEREMOVE QUEUES(YES) command processed, cluster <insert_3> target <insert_4>.
Severity:

0 : Information

Explanation:

The repository queue manager successfully processed a RESET ACTION(FORCEREMOVE) command with the QUEUES(YES) option for the indicated cluster and target queue manager.

Response:

None.

AMQ9406
REFRESH CLUSTER REPOS(YES) command failed, this queue manager is a full repository for cluster <insert_4>.
Severity:

30 : Severe error

Explanation:

The repository queue manager could not process a REFRESH CLUSTER command with the REPOS(YES) option for the indicated cluster, because the local queue manager provides full repository management services for the cluster. The command is ignored.

Response:

Either
1) Reissue the command without REPOS(YES), or
2) Issue the command on a queue manager which is not a full repository, or
3) Change this queue manager definition so that it is not a full repository.

AMQ9407
Cluster queue <insert_3> is defined inconsistently.
Severity:

10 : Warning

Explanation:

The definition of cluster queue <insert_3> on the queue manager with UUID <insert_4> has different DEFPRTY, DEFPSIST and DEFBIND values from the definition of the same cluster queue on the queue manager with UUID <insert_5>. Both definitions now exist in the local repository. All definitions of the same cluster queue should be identical. In particular, problems arise if your applications rely on a queue default value which is defined inconsistently to determine messaging behavior. This applies, for example, if the applications open a cluster queue with option MQOO_BIND_AS_Q_DEF. If different instances of the queue have different DEFBIND values the behavior of the message transfer differs depending on which instance of the queue is selected when it is opened. In general the instance selected varies across opens.

Response:

For each inconsistency decide which of the values is the correct one. Alter the definitions of cluster queue <insert_3> so that all definitions have correct DEFPRTY, DEFPSIST and DEFBIND values.

AMQ9408
BIND_ON_OPEN messages for channel <insert_3> to dead-letter queue.
Severity:

0 : Information

Explanation:

The remote CLUSRCVR for channel <insert_3> was deleted while undelivered BIND_ON_OPEN messages associated with that channel existed on the local SYSTEM.CLUSTER.TRANSMIT.QUEUE. These messages could not be allocated to another channel because they were put BIND_ON_OPEN, but were very unlikely to ever flow along the channel with which they were associated as this has now been deleted. An attempt has therefore been made to move them from the transmission queue to the local dead-letter queue. The MQDLH reason is MQFB_BIND_OPEN_CLUSRCVR_DEL. Note that any internal WebSphere MQ Clustering messages for the deleted channel will also have been removed from the SYSTEM.CLUSTER.TRANSMIT.QUEUE (these are discarded) so the current depth of the queue may have decreased by more than the number of user messages moved to the dead-letter queue.

Response:

Examine the contents of the dead-letter queue. Each message is contained in an MQDLH structure that includes the reason why it was written and where it was originally addressed. Also look at previous error messages to see if the attempt to put messages to the dead-letter queue failed.

AMQ9409
Repository manager ended abnormally.
Severity:

30 : Severe error

Explanation:

The repository manager ended abnormally.

Response:

Look at previous error messages for the repository manager in the error files to determine the cause of the failure.

AMQ9410
Repository manager started
Severity:

0 : Information

Explanation:

The repository manager started successfully.

Response:

None.

AMQ9411
Repository manager ended normally.
Severity:

0 : Information

Explanation:

The repository manager ended normally.

Response:

None.

AMQ9412
Repository command received for <insert_3>.
Severity:

30 : Severe error

Explanation:

The repository manager received a command intended for some other queue manager, whose identifier is <insert_3>. The command was sent by the queue manager with identifier <insert_4>.

Response:

Check the channel and cluster definitions of the sending queue manager.

AMQ9413
Repository command format error, command code <insert_1>
Severity:

30 : Severe error

Explanation:

An internal error has occurred.

Response:

Collect the items listed in the 'Problem determination' section of the System Administration manual and contact your IBM support center.

AMQ9415
Repository command unexpected, command code <insert_1>, cluster object <insert_3>, sender <insert_4>
Severity:

30 : Severe error

Explanation:

An internal error has occurred.

Response:

Collect the items listed in the 'Problem determination' section of the System Administration manual and contact your IBM support center.

AMQ9415 (iSeries)
An internal error has occurred.
Severity:

30 : Severe error

Explanation:

Repository command unexpected, command code <insert_1>, cluster object <insert_3>, sender <insert_4>

Response:

Collect the items listed in the 'Problem determination' section of the System Administration manual and contact your IBM support center.

AMQ9416
Repository command processing error, RC=<insert_2>, command code <insert_1>, cluster object <insert_3>, sender <insert_4>.
Severity:

30 : Severe error

Explanation:

An internal error has occurred.

Response:

Collect the items listed in the 'Problem determination' section of the System Administration manual and contact your IBM support center.

AMQ9416 (iSeries)
An internal error has occurred.
Severity:

30 : Severe error

Explanation:

Repository command processing error, RC=<insert_2>, command code <insert_1>, cluster object <insert_3>, sender <insert_4>.

Response:

Collect the items listed in the 'Problem determination' section of the System Administration manual and contact your IBM support center.

AMQ9417
Manually defined CLUSSDR channels have been forcibly removed.
Severity:

0 : Information

Explanation:

The administrator has asked for the queue manager <insert_3> to be deleted, or forcibly removed, but has not yet deleted the manually defined CLUSSDR channels to <insert_3>. The auto-defined channels to <insert_3> have been deleted, but <insert_3> continues to receive updates until the manually defined CLUSSDR channels have been deleted.

Response:

Delete the manually defined CLUSSDR channels to <insert_3>.

AMQ9418
Only one repository for cluster <insert_3>.
Severity:

0 : Information

Explanation:

The queue manager has received information about a cluster for which it is the only repository.

Response:

Alter the REPOS or REPOSNL attribute of the queue manager, that is to have the second full repository for the cluster, to specify the cluster name.

AMQ9419
No cluster-receiver channels for cluster <insert_3>
Severity:

0 : Information

Explanation:

The repository manager has received information about a cluster for which no cluster-receiver channels are known.

Response:

Define cluster-receiver channels for the cluster on the local queue manager.

AMQ9420
No repositories for cluster <insert_3>.
Severity:

0 : Information

Explanation:

The queue manager has received information about a cluster for which no repositories are known.

Response:

Alter the REPOS or REPOSNL attribute of the queue manager, that is to have a full repository for the cluster, to specify the cluster name.

AMQ9421
Invalid cluster record action code detected
Severity:

30 : Severe error

Explanation:

An invalid record was read from the SYSTEM.CLUSTER.REPOSITORY.QUEUE. An FFST record has been generated containing the invalid record. was

Response:

Collect the items listed in the Problem Determination section of the System Administration manual and contact your IBM support center.

AMQ9422
Repository manager error, RC=<insert_1>
Severity:

30 : Severe error

Explanation:

An internal error has occurred.

Response:

Collect the items listed in the 'Problem determination' section of the System Administration manual and contact your IBM support center.

AMQ9425
An internal error has occurred.
Severity:

30 : Severe error

Explanation:

Repository command merge error, command code <insert_1>, cluster object <insert_3>, sender <insert_4>

Response:

Collect the items listed in the 'Problem determination' section of the System Administration manual and contact your IBM support center.

AMQ9426
Repository command recipient unknown.
Severity:

30 : Severe error

Explanation:

The repository manager tried to send a command to another queue manager using channel <insert_4>. The recipient queue manager, whose identifier is <insert_3>, could not be found. Command code <insert_1>.

Response:

Check the channel and cluster definitions of the sending and receiving queue managers.

AMQ9427
CLUSSDR channel does not point to a repository queue manager.
Severity:

30 : Severe error

Explanation:

A CLUSSDR channel must point to a queue manager that hosts repositories for all clusters of which the channel is a member. In addition, the CLUSRCVR for the channel must be a member of all the same clusters as the CLUSSDR channel. The queue manager pointed to by CLUSSDR channel <insert_3> does not meet these criteria for cluster <insert_4>. The remote queue manager has a QMID of <insert_5>.

Response:

Check the definitions on the local and remote queue managers to ensure that the CLUSSDR channel points to a queue manager that hosts a repository for the cluster, and that the CLUSRCVR for the channel is a member of the cluster.

AMQ9428
Unexpected publication of a cluster queue object received.
Severity:

30 : Severe error

Explanation:

The local queue manager has received a publication of a cluster queue object from a remote queue manager on cluster <insert_3>. The local queue manager discards the request because it does not host a repository for cluster <insert_3> and has not subscribed to the published object. The remote CLUSSDR channel used to access the local queue manager has a channel name of <insert_4> and the remote queue manager has a QMID of <insert_5>.

Response:

Check the definitions on the local and remote queue managers to ensure that the CLUSSDR channel points to a repository queue manager for the cluster.

AMQ9429
Unexpected publication of a cluster queue deletion received.
Severity:

30 : Severe error

Explanation:

The local queue manager has received a publication of a cluster queue deletion from a remote queue manager on cluster <insert_3>. The local queue manager discards the request because it does not host a repository for cluster <insert_3> and has not subscribed to the published object. The remote CLUSSDR channel used to access the local queue manager has a channel name of <insert_4> and the remote queue manager has a QMID of <insert_5>.

Response:

Check the definitions on the local and remote queue managers to ensure that the CLUSSDR channel points to a repository queue manager for the cluster.

AMQ9430
Unexpected cluster queue manager publication received.
Severity:

30 : Severe error

Explanation:

The local queue manager has received a cluster queue manager publication on cluster <insert_3>. The local queue manager should not have received the publication because it does not host a repository for cluster <insert_3>, it has not subscribed to information concerning the published object, and the published object does not match any of its CLUSSDRs. The queue manager that sent the publication to the local queue manager has QMID <insert_4> (note that this is not necessarily the queue manager which originated the publication). CLUSSDR channel <insert_5> was used to send the publication.

Response:

Check the CLUSSDR definition on the sending queue manager to ensure that it points to a repository queue manager for the cluster.

AMQ9431
Remote queue manager no longer hosts a repository for cluster
Severity:

0 : Information

Explanation:

The local queue manager has received a message from remote queue manager QMID <insert_3> indicating that it no longer hosts a repository for cluster <insert_4>. CLUSSDR channel <insert_5> is altered so that it can no longer be used to access queue manager <insert_3> within cluster <insert_4>. If the local queue manager does not host a repository for cluster <insert_4> the relevant subscriptions and publications are remade if possible.

Response:

None.

AMQ9432
Query received by a non-repository queue manager
Severity:

30 : Severe error

Explanation:

The local queue manager has received a query from a remote queue manager on cluster <insert_3>. The local queue manager discards the query because it does not host a repository for cluster <insert_3>. The remote CLUSSDR channel used to access the local queue manager has a channel name of <insert_4> and the remote queue manager has a QMID of <insert_5>.

Response:

Check the definitions on the local and remote queue managers to ensure that the CLUSSDR channel points to a repository queue manager for the cluster.

AMQ9433
CLUSRCVR must be in the same cluster as its matching CLUSSDR.
Severity:

30 : Severe error

Explanation:

CLUSRCVR channel <insert_3> is not defined as a member of cluster <insert_4>. The local queue manager has received a command that indicates that CLUSSDR channel <insert_3> on the remote queue manager with QMID <insert_5> is defined as a member of cluster <insert_4>.

Response:

Alter the CLUSRCVR or CLUSSDR definitions for channel <insert_3>, so that they are both members of the same cluster.

AMQ9434
Unrecognized message on <insert_3>.
Severity:

30 : Severe error

Explanation:

The repository manager found a message on one of its queues having, either a format that could not be recognized, or that did not come from a queue manager or repository manager. The message was put on the dead-letter queue.

Response:

Examine the message on the dead-letter queue to determine the originator of the message.

AMQ9435
Unable to put repository manager message.
Severity:

30 : Severe error

Explanation:

The repository manager tried to send a message to the SYSTEM.CLUSTER.COMMAND.QUEUE on another queue manager whose identifier is <insert_3>, but the MQPUT call was unsuccessful. MQCC=<insert_1>, MQRC=<insert_2>. Processing continues, but the repository information may be out of date.

Response:

Refer to the Application Programming Reference manual for information about MQCC <insert_1> and MQRC <insert_2>. Check the channel and cluster definitions on the local and target queue managers, and ensure that the channels between them are running. When the problem is corrected, the repository information will normally be updated automatically. The REFRESH CLUSTER command can be used to ensure that the repository information is up to date.

AMQ9436
Unable to send repository manager message.
Severity:

30 : Severe error

Explanation:

The repository manager tried to send a message to the SYSTEM.CLUSTER.COMMAND.QUEUE on a queue manager that has the full repository for the specified cluster(<insert_3>), but the MQPUT call was unsuccessful. MQCC=<insert_1>, MQRC=<insert_2>. Processing continues, but repository information may be out of date.

Response:

Refer to the Application Programming Reference manual for information about MQCC <insert_1> and MQRC <insert_2>. Check the channel and cluster definitions on the local and target queue managers, and ensure that the channels between them are running. When the problem is corrected, the repository information will normally be updated automatically. The REFRESH CLUSTER command can be used to ensure that the repository information is up to date.

AMQ9437
Unable to commit repository changes.
Severity:

30 : Severe error

Explanation:

The repository manager tried to commit some updates to the repository but was unsuccessful. Processing continues, but repository information may be out of date.

Response:

If this occurs when the repository manager is stopping, this message can be ignored, because the repository information will normally be updated automatically when the repository manager is restarted. If there is an isolated occurrence at other times, use the REFRESH CLUSTER command to bring the repository information up to date. If the problem persists, contact your IBM support center for assistance.

AMQ9438
CONNAME could not be discovered for CLUSRCVR <insert_3>.
Severity:

30 : Severe error

Explanation:

TCP/IP CLUSRCVR <insert_3> was validly specified with a blank or absent CONNAME parameter. However when the repository process, amqrrmfa, attempted to obtain the CONNAME (IP address) for itself it was unable to. If there is an existing matching CLUSRCVR object in the cache its CONNAME is used. The CONNAME used was <insert_4>.

Response:

Check the error log for a message arising from an associated TCP/IP call (gethostname, gethostbyname or inet_ntoa). Pass all the error information to your systems administrator.

AMQ9439
Repository corruption: bad CLQMGR object for channel <insert_3>.
Severity:

30 : Severe error

Explanation:

An internal error has occurred.

Response:

Collect the items listed in the 'Problem determination' chapter in the System Administration guide and contact your IBM support center.

AMQ9440
Reset command failed.
Severity:

0 : Information

Explanation:

Reset Cluster(<insert_3>) Qmname(<insert_4>) command failed. To issue this command, queue manager <insert_5> must be a repository for cluster <insert_3>. Alter the queue manager attributes Repos, or Reposnl, to include cluster <insert_3> and retry the command.

Response:

None.

AMQ9441
Reset command processed.
Severity:

0 : Information

Explanation:

The reset Cluster(<insert_3>) Qmname(<insert_4>) command has processed on this repository and <insert_1> other queue managers have been sent notification.

Response:

None.

AMQ9442
Refresh Cluster command processed.
Severity:

0 : Information

Explanation:

The Refresh Cluster(<insert_4>) command caused <insert_1> objects to be refreshed and <insert_2> objects to be republished.

Response:

None.

AMQ9443
Suspend Qmgr Cluster command processed.
Severity:

0 : Information

Explanation:

The Suspend Qmgr Cluster command completed. <insert_1> objects suspended.I n the case of a name list the cluster name is the first name in the list.

Response:

None.

AMQ9444
Resume Qmgr Cluster command processed.
Severity:

0 : Information

Explanation:

The Resume Qmgr Cluster(<insert_4>) command completed. <insert_1> objects resumed. In the case of a name list the cluster name is the first name in the list.

Response:

None.

AMQ9445
Error creating channel <insert_3>.
Severity:

30 : Severe error

Explanation:

Channel <insert_4> tried to replace itself by creating channel <insert_3>. The attempt to create the channel was unsuccessful for the following reason: "<insert_5>". A previous message may give further information.

Response:

Rectify the problem which prevented successful creation of channel <insert_3>. Restart channel <insert_4>.

AMQ9446
Error deleting channel <insert_3>.
Severity:

30 : Severe error

Explanation:

Channel <insert_3> tried to delete itself after creating channel <insert_4> to replace it. The attempt to delete the channel was unsuccessful for the following reason: "<insert_5>".

Response:

If channel <insert_3> still exists rectify the problem which prevented its deletion and then manually delete the channel.

AMQ9447
Unable to backout repository changes.
Severity:

30 : Severe error

Explanation:

Following an error, the repository manager tried to backout some updates to the repository, but was unsuccessful. The repository manager terminates.

Response:

If the repository manager subsequently restarts successfully, this message can be ignored. If the repository manager does not restart, contact your IBM support center for assistance.

AMQ9448
Repository manager stopping because of errors. Restart in <insert_1> seconds.
Severity:

30 : Severe error

Explanation:

A severe error, as reported in the preceding messages, occurred during repository manager processing. The repository manager was unable to continue and terminates. The repository manager will try to restart after the specified interval.

Response:

Correct the problem reported in the preceding messages.

AMQ9449
Repository manager restarted.
Severity:

0 : Information

Explanation:

The repository manager restarted successfully following an error.

Response:

None.

AMQ9450
Usage: <insert_3> [-m QMgrName] -f OutputFile [-v OutputFileVersion]
Severity:

10 : Warning

Explanation:

Values passed to the channel table writer program were invalid.
The parameter string passed to this program is as follows:
[-m QMgrName] -f OutputFile [-v OutputFileVersion]

where OutputFileVcan be either 2 or 5 (5 is the default)
Default values will be used for parameters not supplied.

Response:

Correct the parameters passed to the channel table writer program and retry the operation.

AMQ9453
FORCEREMOVE command failed, cluster <insert_3> target <insert_4> is not unique.
Severity:

0 : Information

Explanation:

The repository queue manager could not process a RESET ACTION(FORCEREMOVE) command for the indicated cluster and target queue manager, because there is more than one queue manager with the specified name in the cluster. The command is ignored.

Response:

Reissue the command specifying the identifier (QMID) of the queue manager to be removed, rather than its name.

AMQ9455
FORCEREMOVE command failed, cluster <insert_3>, target <insert_4>, not found.
Severity:

0 : Information

Explanation:

The repository queue manager could not process a RESET ACTION(FORCEREMOVE) command for the indicated cluster and target queue manager, because no information about that queue manager was found in the local repository. The command is ignored.

Response:

Reissue the command, specifying the correct queue manager name or identifier.

AMQ9456
Update not received for queue <insert_3>, queue manager <insert_4> from full repository for cluster <insert_5>.
Severity:

0 : Information

Explanation:

The repository manager detected a queue that has been used in the last 30 days for which updated information should have been sent from a full repository. However, this has not occurred.
The repository manager will keep the information about this queue for a further 60 days.

Response:

If the queue is still required, check that:
1) The cluster channels to and from the full repository and the queue manager that hosts the queue, are able to run.
2) The repository managers running on these queue managers have not ended abnormally.

AMQ9456 (iSeries)
Update not received from full repository.
Severity:

0 : Information

Explanation:

Update not received for queue <insert_3>, queue manager <insert_4> from full repository for cluster <insert_5>.
The repository manager detected a queue that has been used in the last 30 days for which updated information should have been sent from a full repository. However, this has not occurred.
The repository manager will keep the information about this queue for a further 60 days.

Response:

If the queue is still required, check that:
1) The cluster channels to and from the full repository and the queue manager that hosts the queue, are able to run.
2) The repository managers running on these queue managers have not ended abnormally.

AMQ9457
Repository available, cluster <insert_4>, channel <insert_5>, sender <insert_3>.
Severity:

0 : Information

Explanation:

The repository queue manager received a command from another queue manager, whose identifier is <insert_3>, reporting that it is again a repository for cluster <insert_4>. The cluster-sender channel <insert_5> is changed so that it can be used to access the other queue manager in relation to the the cluster.

Response:

None.

AMQ9491
Transmission Queue <insert_3> set to NOSHARE.
Severity:

20 : Error

Explanation:

The channel <insert_4> on queue manager <insert_5> cannot start because this queue manager has a setting for PipeLineLength greater than 1, and so multiple threads will run in this channel's MCA. Only the first thread would be able to open the Transmission Queue <insert_3> because it is set to be non-shareable.

Response:

Check the definition of the Transmission Queue <insert_3> on queue manager <insert_5> and set it to be SHARE instead of NOSHARE. Alternatively, we can set all channels on this queue manager to use only a single thread, by using the PipeLineLength parameter.

AMQ9492
The <insert_3> responder program encountered an error.
Severity:

30 : Severe error

Explanation:

The responder program was started but detected an error.

Response:

Look at previous error messages in the error files to determine the error encountered by the responder program.

AMQ9494
A protocol error was detected for channel <insert_3>.
Severity:

30 : Severe error

Explanation:

During communications with the remote queue manager, a TCP/IP read and receive call returned EINTR, indicating that it had been interrupted. Immediately after this the channel program detected a protocol error. The failure type was <insert_1> with associated data of <insert_2>.

Response:

If you are running an AIX client you will avoid problems arising from EINTRs on TCP/IP reads, by writing your application so that system calls interrupted by signals are restarted. You must establish the signal handler with sigaction(2) and set the SA_RESTART flag in the sa_flags field of the new action structure. If you are running on a platform other than AIX, an AIX server, or an AIX client with an application that adheres to the restart guidelines provided above, contact the systems administrator who should examine the error logs to determine the cause of the failure.

AMQ9495
The CLWL exit <insert_3> is inconsistent with a dynamic cache.
Severity:

30 : Severe error

Explanation:

When the CLWL exit <insert_3> was called for the ExitReason MQXR_INIT, the value <insert_1> was returned in the ExitResponse2 field. This indicates the CLWL exit is incompatible with the Queue Manager cache type which is dynamic. Either change the Queue Manager cache type to static (using the Tuning Parameter, ClusterCacheType=STATIC) or rewrite the CLWL exit to be compatible with a dynamic cache". The CLWL exit has been suppressed.

Response:

None.

AMQ9496
Channel ended by a remote exit.
Severity:

30 : Severe error

Explanation:

Channel program <insert_3> was ended because the channel exit at the remote end requested it.

Response:

Examine the error logs at the remote end of the channel to see the reason why the remote exit ended the channel.

AMQ9498
The MQCD structure supplied was not valid.
Severity:

30 : Severe error

Explanation:

The value of the <insert_3> field has the value <insert_4>. This value is invalid for the operation requested.

Response:

Change the parameter and retry the operation.

AMQ9499
A WebSphere MQ listener will end shortly.
Severity:

0 : Information

Explanation:

One listener detected in the system is scheduled for shutdown.

Response:

None.

AMQ9500
No Repository storage
Severity:

10 : Warning

Explanation:

An operation failed because there was no storage available in the repository. An attempt was made to allocate <insert_1> bytes from <insert_3>.

Response:

Reconfigure the Queue Manager to allocate a larger repository.

AMQ9501
Usage: <insert_3> [-m QMgrName] -c ChlName.
Severity:

10 : Warning

Explanation:

Values passed to the channel program are not valid. The parameter string passed to this program is as follows :- [-m QMgrName] -c ChlName Default values will be used for parameters not supplied.

Response:

Correct the parameters passed to the Channel program and retry the operation.

AMQ9502
Type of channel not suitable for action requested.
Severity:

30 : Severe error

Explanation:

The operation requested cannot be performed on channel <insert_3>. Some operations are only valid for certain channel types. For example, we can only ping a channel from the end sending the message.

Response:

Check whether the channel name is specified correctly. If it is check that the channel has been defined correctly.

AMQ9503
Channel negotiation failed.
Severity:

30 : Severe error

Explanation:

Channel <insert_3> between this machine and the remote machine could not be established due to a negotiation failure.

Response:

Tell the systems administrator, who should attempt to identify the cause of the channel failure using problem determination techniques. For example, look for FFST files, and examine the error logs on the local and remote systems where there may be messages explaining the cause of failure. More information may be obtained by repeating the operation with tracing enabled.

AMQ9504
A protocol error was detected for channel <insert_3>.
Severity:

30 : Severe error

Explanation:

During communications with the remote queue manager, the channel program detected a protocol error. The failure type was <insert_1> with associated data of <insert_2>.

Response:

Contact the systems administrator who should examine the error logs to determine the cause of the failure.

AMQ9505
Channel sequence number wrap values are different.
Severity:

30 : Severe error

Explanation:

The sequence number wrap value for channel <insert_3> is <insert_1>, but the value specified at the remote location is <insert_2>. The two values must be the same before the channel can be started.

Response:

Change either the local or remote channel definitions so that the values specified for the message sequence number wrap values are the same.

AMQ9506
Message receipt confirmation failed.
Severity:

30 : Severe error

Explanation:

Channel <insert_3> has ended because the remote queue manager did not accept the last batch of messages.

Response:

The error log for the channel at the remote site will contain an explanation of the failure. Contact the remote Systems Administrator to resolve the problem.

AMQ9507
Channel <insert_3> is currently in-doubt.
Severity:

30 : Severe error

Explanation:

The requested operation cannot complete because the channel is in-doubt with host <insert_4>.

Response:

Examine the status of the channel, and either restart a channel to resolve the in-doubt state, or use the RESOLVE CHANNEL command to correct the problem manually.

AMQ9508
Program cannot connect to the queue manager.
Severity:

30 : Severe error

Explanation:

The connection attempt to queue manager <insert_4> failed with reason code <insert_1>.

Response:

Ensure that the queue manager is available and operational.

AMQ9509
Program cannot open queue manager object.
Severity:

30 : Severe error

Explanation:

The attempt to open either the queue or queue manager object <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.

Response:

Ensure that the queue is available and retry the operation.

AMQ9510
Messages cannot be retrieved from a queue.
Severity:

30 : Severe error

Explanation:

The attempt to get messages from queue <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.

Response:

If the reason code indicates a conversion problem, for example MQRC_SOURCE_CCSID_ERROR, remove the message(s) from the queue. Otherwise, ensure that the required queue is available and operational.

AMQ9511
Messages cannot be put to a queue.
Severity:

30 : Severe error

Explanation:

The attempt to put messages to queue <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.

Response:

Ensure that the required queue is available and operational.

AMQ9512
Ping operation is not valid for channel <insert_3>.
Severity:

30 : Severe error

Explanation:

Ping may only be issued for SENDER, SERVER or CLUSSDR channel types. Also, it may not be issued for an SSL channel on the HP-UX or Linux platforms.

Response:

If the local channel is a receiver channel, issue the ping from the remote queue manager.

AMQ9513
Maximum number of channels reached.
Severity:

30 : Severe error

Explanation:

The maximum number of channels that can be in use simultaneously has been reached. The number of permitted channels is a configurable parameter in the queue manager configuration file.

Response:

Wait for some of the operating channels to close. Retry the operation when some channels are available.

AMQ9514
Channel <insert_3> is in use.
Severity:

30 : Severe error

Explanation:

The requested operation failed because channel <insert_3> is currently active.

Response:

Either end the channel manually, or wait for it to close, and retry the operation.

AMQ9515
Channel <insert_3> changed.
Severity:

10 : Warning

Explanation:

The statistics shown are for the channel requested, but it is a new instance of the channel. The previous channel instance has ended.

Response:

None.

AMQ9516
File error occurred.
Severity:

30 : Severe error

Explanation:

The filesystem returned error code <insert_1> for file <insert_3>.

Response:

Record the name of the file <insert_3> and tell the systems administrator, who should ensure that file <insert_3> is correct and available.

AMQ9516 (iSeries)
File error occurred.
Severity:

30 : Severe error

Explanation:

The filesystem returned error code <insert_4> for file <insert_3>.

Response:

Record the name of the file <insert_3> and tell the systems administrator, who should ensure that file <insert_3> is correct and available.

AMQ9517
File damaged.
Severity:

30 : Severe error

Explanation:

The program has detected damage to the contents of file <insert_3>.

Response:

Record the values and tell the systems administrator who must restore a saved version of file <insert_3>. The return code was <insert_1> and the record length returned was <insert_2>.

AMQ9518
File <insert_3> not found.
Severity:

30 : Severe error

Explanation:

The program requires that the file <insert_3> is present and available.

Response:

This may be caused by invalid values for the optional environment variables MQCHLLIB, MQCHLTAB or MQDATA. If these variables are valid or not set then record the name of the file and tell the systems administrator who must ensure that file <insert_3> is available to the program.

AMQ9519
Channel <insert_3> not found.
Severity:

30 : Severe error

Explanation:

The requested operation failed because the program could not find a definition of channel <insert_3>.

Response:

Check that the name is specified correctly and the channel definition is available.

AMQ9520
Channel not defined remotely.
Severity:

30 : Severe error

Explanation:

There is no definition of channel <insert_3> at the remote location.

Response:

Add an appropriate definition to the remote hosts list of defined channels and retry the operation.

AMQ9521
Host is not supported by this channel.
Severity:

30 : Severe error

Explanation:

The connection across channel <insert_5> was refused because the remote host <insert_4> did not match the host <insert_3> specified in the channel definition.

Response:

Update the channel definition, or remove the explicit mention of the remote machine connection name.

AMQ9522
Error accessing the status table.
Severity:

30 : Severe error

Explanation:

The program could not access the channel status table.

Response:

A value of <insert_1> was returned from the subsystem when an attempt was made to access the Channel status table. Contact the systems administrator, who should examine the log files to determine why the program was unable to access the status table.

AMQ9523
Remote host detected a protocol error.
Severity:

30 : Severe error

Explanation:

During communications through channel <insert_3>, the remote queue manager channel program detected a protocol error. The failure type was <insert_1> with associated data of <insert_2>.

Response:

Tell the systems administrator, who should examine the error files to determine the cause of the failure.

AMQ9524
Remote queue manager unavailable.
Severity:

30 : Severe error

Explanation:

Channel <insert_3> cannot start because the remote queue manager is not currently available.

Response:

Either start the remote queue manager, or retry the operation later.

AMQ9525
Remote queue manager is ending.
Severity:

30 : Severe error

Explanation:

Channel <insert_3> is closing because the remote queue manager is ending.

Response:

None.

AMQ9526
Message sequence number error for channel <insert_3>.
Severity:

30 : Severe error

Explanation:

The local and remote queue managers do not agree on the next message sequence number. A message with sequence number <insert_1> has been sent when sequence number <insert_2> was expected.

Response:

Determine the cause of the inconsistency. It could be that the synchronization information has become damaged, or has been backed out to a previous version. If the situation cannot be resolved, the sequence number can be manually reset at the sending end of the channel using the RESET CHANNEL command.

AMQ9527
Cannot send message through channel <insert_3>.
Severity:

30 : Severe error

Explanation:

The channel has closed because the remote queue manager cannot receive a message.

Response:

Contact the systems administrator who should examine the error files of the remote queue manager, to determine why the message cannot be received, and then restart the channel.

AMQ9528
User requested closure of channel <insert_3>.
Severity:

10 : Warning

Explanation:

The channel is closing because of a request by the user.

Response:

None.

AMQ9529
Target queue unknown on remote host.
Severity:

30 : Severe error

Explanation:

Communication using channel <insert_3> has ended because the target queue for a message is unknown at the remote host.

Response:

Ensure that the remote host contains a correctly defined target queue, and restart the channel.

AMQ9530
Program could not inquire queue attributes.
Severity:

30 : Severe error

Explanation:

The attempt to inquire the attributes of queue <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.

Response:

Ensure that the queue is available and retry the operation.

AMQ9531
Transmission queue specification error.
Severity:

30 : Severe error

Explanation:

Queue <insert_4> identified as a transmission queue in the channel definition <insert_3> is not a transmission queue.

Response:

Ensure that the queue name is specified correctly. If so, alter the queue usage parameter of the queue to that of a transmission queue.

AMQ9532
Program cannot set queue attributes.
Severity:

30 : Severe error

Explanation:

The attempt to set the attributes of queue <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.

Response:

Ensure that the queue is available and retry the operation.

AMQ9533
Channel <insert_3> is not currently active.
Severity:

10 : Warning

Explanation:

The channel was not stopped because it was not currently active. If attempting to stop a specific instance of a channel by connection name or by remote queue manager name this message indicates that the specified instance of the channel is not running.

Response:

None.

AMQ9534
Channel <insert_3> is currently not enabled.
Severity:

30 : Severe error

Explanation:

The channel program ended because the channel is currently not enabled.

Response:

Issue the START CHANNEL command to re-enable the channel.

AMQ9535
User exit not valid.
Severity:

30 : Severe error

Explanation:

Channel program <insert_3> ended because user exit <insert_4> is not valid.

Response:

Ensure that the user exit is specified correctly in the channel definition, and that the user exit program is correct and available.

AMQ9536
Channel ended by an exit.
Severity:

30 : Severe error

Explanation:

Channel program <insert_3> was ended by exit <insert_4>.

Response:

None.

AMQ9537
Usage: <insert_3> [-m QMgrName] [-q InitQ]
Severity:

10 : Warning

Explanation:

Values passed to the Channel Initiator program are not valid. The parameters should be passed as follows: [-m QMgrName] [-q InitQ] Default values are used for parameters that are not supplied.

Response:

Correct the parameters passed to the program and retry the operation.

AMQ9538
Commit control error.
Severity:

30 : Severe error

Explanation:

An error occurred when attempting to start commitment control. Either exception <insert_3> was received when querying commitment status, or commitment control could not be started.

Response:

Refer to the error log for other messages pertaining to this problem.

AMQ9539
No channels available.
Severity:

30 : Severe error

Explanation:

The channel initiator program received a trigger message to start an MCA program to process queue <insert_3>. The program could not find a defined, available channel to start.

Response:

Ensure that there is a defined channel, which is enabled, to process the transmission queue.

AMQ9540
Commit failed.
Severity:

30 : Severe error

Explanation:

The program ended because return code <insert_1> was received when an attempt was made to commit change to the resource managers. The commit ID was <insert_3>.

Response:

Tell the systems administrator.

AMQ9541
CCSID supplied for data conversion not supported.
Severity:

30 : Severe error

Explanation:

The program ended because, either the source CCSID <insert_1> or the target CCSID <insert_2> is not valid, or is not currently supported.

Response:

Correct the CCSID that is not valid, or ensure that the requested CCSID can be supported.

AMQ9542
Queue manager is ending.
Severity:

10 : Warning

Explanation:

The program will end because the queue manager is quiescing.

Response:

None.

AMQ9543
Status table damaged.
Severity:

30 : Severe error

Explanation:

The channel status table has been damaged.

Response:

End all running channels and issue a DISPLAY CHSTATUS command to see the status of the channels. Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ9544
Messages not put to destination queue.
Severity:

10 : Warning

Explanation:

During the processing of channel <insert_3> one or more messages could not be put to the destination queue and attempts were made to put them to a dead-letter queue. The location of the queue is <insert_1>, where 1 is the local dead-letter queue and 2 is the remote dead-letter queue.

Response:

Examine the contents of the dead-letter queue. Each message is contained in a structure that describes why the message was put to the queue, and to where it was originally addressed. Also look at previous error messages to see if the attempt to put messages to a dead-letter queue failed. The program identifier (PID) of the processing program was <insert_4>.

AMQ9545
Disconnect interval expired.
Severity:

0 : Information

Explanation:

Channel <insert_3> closed because no messages arrived on the transmission queue within the disconnect interval period.

Response:

None.

AMQ9546
Error return code received.
Severity:

30 : Severe error

Explanation:

The program has ended because return code <insert_1> was returned from function <insert_3>

Response:

Correct the cause of the failure and retry the operation.

AMQ9547
Type of remote channel not suitable for action requested.
Severity:

30 : Severe error

Explanation:

The operation requested cannot be performed because channel <insert_3> on the remote machine is not of a suitable type. For example, if the local channel is defined as a sender the remote machine must define its channel as either a receiver or requester.

Response:

Check that the channel name is specified correctly. If it is, check that the remote channel has been defined correctly.

AMQ9548
Message put to the 'dead-letter queue'.
Severity:

10 : Warning

Explanation:

During processing a message has been put to the dead-letter queue.

Response:

Examine the contents of the dead-letter queue. Each message is contained in a structure that describes why the message was put to the queue, and to where it was originally addressed.

AMQ9549
Transmission Queue <insert_3> inhibited for MQGET.
Severity:

20 : Error

Explanation:

An MQGET failed because the transmission queue had been previously inhibited for MQGET.

Response:

None.

AMQ9550
Channel program <insert_3> cannot be stopped at this time.
Severity:

30 : Severe error

Explanation:

The channel program can not be terminated immediately but should end shortly.

Response:

If the channel does not end in a short time issue the STOP CHANNEL command again.

AMQ9551
Protocol not supported by remote host
Severity:

30 : Severe error

Explanation:

The operation you are performing over Channel <insert_3> to the host at <insert_4> is not supported by the target host.

Response:

Check that the connection name parameter is specified correctly and that the levels of the products in use are compatible.

AMQ9552
Security flow not received.
Severity:

30 : Severe error

Explanation:

During communications through channel <insert_3> the local security exit requested security data from the remote machine. The security data has not been received so the channel has been closed.

Response:

Tell the systems administrator who should ensure that the security exit on the remote machine is defined correctly.

AMQ9553
The function is not supported.
Severity:

30 : Severe error

Explanation:

The <insert_3> function <insert_4> attempted is not currently supported on this platform.

Response:

None.

AMQ9554
User not authorized.
Severity:

30 : Severe error

Explanation:

You are not authorized to perform the Channel operation.

Response:

Tell the systems administrator who should ensure that the correct access permissions are available to you, and then retry the operation.

AMQ9555
File format error.
Severity:

30 : Severe error

Explanation:

The file <insert_3> does not have the expected format.

Response:

Ensure that the file name is specified correctly.

AMQ9556
Channel synchronization file missing or damaged.
Severity:

30 : Severe error

Explanation:

The channel synchronization file <insert_3> is missing or does not correspond to the stored channel information for queue manager <insert_4>.

Response:

Rebuild the synchronization file using the rcrmqmobj command rcrmqmobj -t syncfile (-m q-mgr-name)

AMQ9556 (iSeries)
Channel synchronization file missing or damaged.
Severity:

30 : Severe error

Explanation:

The channel synchronization file <insert_3> is missing or does not correspond to the stored channel information for queue manager <insert_4>.

Response:

Rebuild the synchronization file using the RCRMQMOBJ command.

AMQ9557
Queue Manager User ID initialization failed.
Severity:

30 : Severe error

Explanation:

The call to initialize the User ID failed with CompCode <insert_1> and Reason <insert_2>.

Response:

Correct the error and try again.

AMQ9558
Remote Channel is not currently available.
Severity:

30 : Severe error

Explanation:

The channel program ended because the channel <insert_3> is not currently available on the remote system. This could be because the channel is disabled or that the remote system does not have sufficient resources to run a further channel.

Response:

Check the remote system to ensure that the channel is available to run, and retry the operation.

AMQ9560
Rebuild Synchronization File - program started
Severity:

0 : Information

Explanation:

Rebuilding the Synchronization file for Queue Manager <insert_3> .

Response:

None.

AMQ9561
Rebuild Synchronization File - program completed normally
Severity:

0 : Information

Explanation:

Rebuild Synchronization File program completed normally.

Response:

None.

AMQ9562
Synchronization file in use.
Severity:

30 : Severe error

Explanation:

The Synchronization file <insert_3> is in use and cannot be recreated.

Response:

Stop any channel activity and retry the rcrmqmobj command.

AMQ9562 (iSeries)
Synchronization file in use.
Severity:

30 : Severe error

Explanation:

The Synchronization file <insert_3> is in use and cannot be recreated.

Response:

Stop any channel activity and retry the RCRMQMOBJ command.

AMQ9563
Synchronization file cannot be deleted
Severity:

30 : Severe error

Explanation:

The filesystem returned error code <insert_1> for file <insert_3>.

Response:

Tell the systems administrator who should ensure that file <insert_3> is available and not in use.

AMQ9564
Synchronization File cannot be created
Severity:

30 : Severe error

Explanation:

The filesystem returned error code <insert_1> for file <insert_3>.

Response:

Tell the systems administrator.

AMQ9565
No dead-letter queue defined.
Severity:

30 : Severe error

Explanation:

The queue manager <insert_4> does not have a defined dead-letter queue.

Response:

Either correct the problem that caused the program to try and write a message to the dead-letter queue or create a dead-letter queue for the queue manager.

AMQ9566
Invalid MQSERVER value
Severity:

30 : Severe error

Explanation:

The value of the MQSERVER environment variable was <insert_3>. The variable should be in the format 'ChannelName/Protocol/ConnectionName'.

Response:

Correct the MQSERVER value and retry the operation.

AMQ9572
Message header is not valid.
Severity:

30 : Severe error

Explanation:

Channel <insert_3> is stopping because a message header is not valid. During the processing of the channel, a message was found that has a header that is not valid. The dead-letter queue has been defined as a transmission queue, so a loop would be created if the message had been put there.

Response:

Correct the problem that caused the message to have a header that is not valid.

AMQ9573
Maximum number of active channels reached.
Severity:

30 : Severe error

Explanation:

There are too many channels active to start another. The current defined maximum number of active channels is <insert_1>.

Response:

Either wait for some of the operating channels to close or use the stop channel command to close some channels. Retry the operation when some channels are available. The maximum number of active channels is a configurable parameter in the queue manager configuration file.

AMQ9574
Channel <insert_3> can now be started.
Severity:

30 : Severe error

Explanation:

Channel <insert_3> has been waiting to start, but there were no channels available because the maximum number of active channels was running. One, or more, of the active channels has now closed so this channel can start.

AMQ9575
DCE Security: failed to get the user's login name.
Severity:

30 : Severe error

Explanation:

System call <insert_4> to get the login name of the user running WebSphere MQ client application process <insert_1> failed with error value <insert_2>. This occurred in security exit function create_cred. The exit will now attempt to open channel <insert_3> using the DCE default login context.

Response:

If you wish to run using the DCE default login context take no action. If you wish to run using the user's login name as the DCE security exit principal examine the documentation for the operating system on which you are running MQ clients and reconfigure the operating system as necessary to allow the <insert_4> call to succeed.

AMQ9576
DCE Security: an exit could not allocate memory.
Severity:

30 : Severe error

Explanation:

A DCE exit was unsuccessful in obtaining the memory it needed. The failure occurred in exit function <insert_4>. Channel <insert_3> is closed.

Response:

Make more memory available to the WebSphere MQ system and restart the relevant channel.

AMQ9577
DCE security exit: no partner name.
Severity:

30 : Severe error

Explanation:

Channel <insert_3> has not been opened because the DCE security exit which initiates the security context was not passed a valid partner name. When the DCE security exit is called to initiate the security context it is essential that the PartnerName field in the MQCXP structure contains a valid partner name. On this call it did not. This can arise as a result of a usage error, for instance only specifying the security exit on one end of the channel. The error was reported from security exit function savePartnerName.

Response:

Check your usage of the DCE security exit for errors, such as only specifying the exit in one of the matching channel definitions. Correct any errors found and retry.

AMQ9578
DCE Security: bad return from DCE call.
Severity:

30 : Severe error

Explanation:

Channel <insert_3> has been closed because one of the DCE channel exits received a bad return code from DCE.

Response:

Consult the appropriate DCE manuals to find out the meaning of major_status <insert_1> and minor_status <insert_2> on call <insert_5>. Then rectify the error. The exit function name is <insert_4>.

AMQ9579
DCE Security: partner name does not match target.
Severity:

30 : Severe error

Explanation:

The DCE Security exit was requested to perform a trusted channel check: target partner name <insert_4> was specified in the SCYDATA field of channel <insert_3>. The actual partner name associated with channel <insert_3> was <insert_5>, so the security exit suppressed the channel.

Response:

Examine the channel definition of channel <insert_3> and alter it so that the relevant name on the partner system matches that specified in the SCYDATA field.

AMQ9580
DCE Security: invalid message received.
Severity:

30 : Severe error

Explanation:

An IBM-supplied DCE exit on channel <insert_3> received a message that was not generated by a matching exit, or was not the expected type of message. The header.mechanism field had value <insert_1>. The header.msgtype field had value <insert_2>. The name of the exit function in which the error was discovered is <insert_4>.

Response:

Make sure that the exits at both ends of the channel generate compatible flows.

AMQ9581
DCE Security: wrong exit called.
Severity:

30 : Severe error

Explanation:

Exit <insert_4> on channel <insert_3> was called for use as a WebSphere MQ exit of the wrong type. DCE_SEC_SCY_CHANNELEXIT functions as a security exit; DCE_SEC_SRM_CHANNELEXIT functions as a send, receive or message exit. The ExitId parameter passed to the exit was <insert_1>.

Response:

Alter the exit definitions to ensure that exit <insert_4> is called correctly.

AMQ9582
DCE Security: invalid exit function requested.
Severity:

30 : Severe error

Explanation:

Exit <insert_4> on channel <insert_3> was called with an invalid ExitReason (value <insert_1>).

Response:

Check that the exit is being run with a compatible release of WebSphere MQ base code. If not then correct it. If it is, contact your IBM support center for help.

AMQ9583
The DCE security exit was not run.
Severity:

30 : Severe error

Explanation:

The DCE_SEC_SRM_CHANNELEXIT exit was called on channel <insert_3>; the value of pContext->mechanism (<insert_1>) passed was not valid.

Response:

This is probably because the DCE_SEC_SRM_CHANNELEXIT exit has been called without first calling the DCE_SEC_SCY_CHANNELEXIT security exit. Alter the system so that either both or neither are run.

AMQ9584
DCE Security: message too short.
Severity:

30 : Severe error

Explanation:

The DCE_SEC_SRM_CHANNELEXIT receive or message exit was called on channel <insert_3> to process an incoming message. The pDataLength parameter supplied to the exit indicated that the message received was too short to be a valid message for the relevant exit. The *pDataLength value was <insert_1>.

Response:

Configure the system so that compatible send/receive/message exits are run at both ends of the channel.

AMQ9585
Maximum number of channel initiators reached.
Severity:

30 : Severe error

Explanation:

The maximum number of channels initiators that can be in use simultaneously has been reached. The number of permitted channel initiators is a configurable parameter in the queue manager configuration file.

Response:

Wait for one or more channel initiators to close and retry the operation or modify the configuration file to allow more initiators and restart the Queue Manager.

AMQ9586
Program cannot create queue manager object.
Severity:

30 : Severe error

Explanation:

The attempt to create object <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.

Response:

Use the standard facilities supplied with your system to record the problem identifier. Contact your IBM support center.

AMQ9587
Program cannot open queue manager object.
Severity:

30 : Severe error

Explanation:

The attempt to open object <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.

Response:

Use the standard facilities supplied with your system to record the problem identifier. Contact your IBM support center.

AMQ9588
Program cannot update queue manager object.
Severity:

30 : Severe error

Explanation:

The attempt to update object <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.

Response:

Use the standard facilities supplied with your system to record the problem identifier. Contact your IBM support center.

AMQ9589
Program cannot query queue manager object.
Severity:

30 : Severe error

Explanation:

The attempt to query object <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.

Response:

Use the standard facilities supplied with your system to record the problem identifier. Contact your IBM support center.

AMQ9590
Program cannot close queue manager object.
Severity:

30 : Severe error

Explanation:

The attempt to close object <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.

Response:

Use the standard facilities supplied with your system to record the problem identifier. Contact your IBM support center.

AMQ9591
Program cannot prepare queue manager object.
Severity:

30 : Severe error

Explanation:

The attempt to prepare object <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.

Response:

Use the standard facilities supplied with your system to record the problem identifier. Contact your IBM support center.

AMQ9592
Program cannot resolve queue manager object.
Severity:

30 : Severe error

Explanation:

The attempt to resolve object <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.

Response:

Use the standard facilities supplied with your system to record the problem identifier. Contact your IBM support center.

AMQ9593
Program cannot delete queue manager object.
Severity:

30 : Severe error

Explanation:

The attempt to delete object <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.

Response:

Use the standard facilities supplied with your system to record the problem identifier. Contact your IBM support center.

AMQ9594
Usage: runmqfmt [filename].
Severity:

0 : Information

Explanation:

Syntax for the usage of runmqfmt.

Response:

None.

AMQ9595
Usage: endmqlsr [-w] [-m QMgrName]
Severity:

10 : Warning

Explanation:

The correct usage is shown.

Response:

Correct the parameters passed to the endmqlsr program and retry the operation.

AMQ9596
Queue Manager <insert_3> still running
Severity:

30 : Severe error

Explanation:

The requested operation can not complete because queue manager <insert_3> is still running.

Response:

End the queue manager and retry the operation.

AMQ9597
No WebSphere MQ listeners for Queue Manager <insert_3>.
Severity:

0 : Information

Explanation:

No listener processes were found in the system for Queue Manager <insert_3>.

Response:

None.

AMQ9598
<insert_1> WebSphere MQ listeners will end shortly.
Severity:

0 : Information

Explanation:

<insert_1> listeners detected in the system are scheduled for shutdown.

Response:

None.

AMQ9599
Program could not open queue manager object.
Severity:

30 : Severe error

Explanation:

The attempt to open either the queue or queue manager object <insert_4> on queue manager <insert_5> by user <insert_3> failed with reason code <insert_1>.

Response:

Ensure that the queue is available and retry the operation. If the message is from a remote Queue Manager, check the Message Channel Agent User Identifier has the correct authority.

AMQ9601
Program could not inquire on queues on this queue manager.
Severity:

30 : Severe error

Explanation:

The WebSphere MQ clustering repository program was attempting to find out about the queues on queue manager <insert_3>. One of the calls failed with reason code <insert_1>. The repository command was backed out and the repository process went into a timed wait.

Response:

Correct the error. When the repository process restarts it processes the backed out command again and continues.

AMQ9602
Maximum number of channel processes reached.
Severity:

30 : Severe error

Explanation:

The channel can not start because the number of channel processes has already reached the maximum allowable value. The maximum number of channels processes is configured as <insert_1>. This value is a configurable parameter in the queue manager configuration file.

Response:

Wait for some of the operating channels to close. Retry the operation when some channels are available.

AMQ9603
Error accessing the process pool shared segment.
Severity:

30 : Severe error

Explanation:

The program could not access the process pool shared segment

Response:

A value of <insert_1> was returned from the subsystem when an attempt was made to access the Channel process pool shared memory. Contact the systems administrator, who should examine the log files to determine why the program was unable to access the process pool shared segment.

AMQ9604
Channel <insert_3> terminated unexpectedly
Severity:

30 : Severe error

Explanation:

The process or thread executing channel <insert_3> is no longer running. The check process system call returned <insert_1> for process <insert_2>.

Response:

No immediate action is required because the channel entry has been removed from the list of running channels. Inform the system administrator who should examine the operating system procedures to determine why the channel process has terminated.

AMQ9605
<insert_1> WebSphere MQ listeners have been ended.
Severity:

0 : Information

Explanation:

<insert_1> listeners detected in the system have been ended.

Response:

None.

AMQ9606
A WebSphere MQ listener has ended.
Severity:

0 : Information

Explanation:

One listener detected in the system has been ended.

Response:

None.

AMQ9608
Remote resources in recovery
Severity:

30 : Severe error

Explanation:

Channel <insert_3> could not establish a successful connection with the remote Queue Manager because resources are being recovered.

Response:

Restart the channel at a later time. If the problem persists then examine the error logs of the remote Queue Manager to see the full explanation of the cause of the problem.

AMQ9610
AMQ<insert_1> messages suppressed
Severity:

0 : Information

Explanation:

<insert_2> messages of type AMQ<insert_1> were suppressed

Response:

Message suppression is controlled by MQ_CHANNEL_SUPPRESS_MSGS and MQ_CHANNEL_SUPPRESS_INTERVAL environment variables.

AMQ9611
Rebuild Client Channel Table - program completed normally
Severity:

0 : Information

Explanation:

Rebuild Client Channel Table program completed normally.

Response:

None.

AMQ9612
<insert_1> WebSphere MQ listeners could not be ended.
Severity:

0 : Information

Explanation:

The request to the end the WebSphere MQ listeners for specified Queue Manager was completed however <insert_1> listeners could not be stopped. Reasons why listener may not be stopped are:
The listener process contains channels which are still active.

Response:

Active channels may be stopped using the 'STOP CHANNEL' command or by ending the Queue Manager, and reissuing the end-listener request.

AMQ9614 (iSeries)
Certificate is not signed by a trusted Certificate Authority.
Severity:

0 : Information

Explanation:

The attempt to start channel <insert_3> failed because the certificate used in the SSL handshake is not signed by a Certificate Authority (CA) listed in the certificate trust list for this queue manager. This error occurs when the SSL key repository for the queue manager is specified as '*SYSTEM' and the application definition in Digital Certificate Manager has been modified to specify a CA trust list.

Response:

Use Digital Certificate Manager to add the required Certificate Authority (CA) certificates to the application definitions CA trust list.

AMQ9615 (iSeries)
Queue Manager is not registered with DCM.
Severity:

0 : Information

Explanation:

The attempt to start channel <insert_3> failed because the queue manager is not registered as a SSL server application with Digital Certificate Manager (DCM). This error occurs when the SSL key repository for the queue manager is specified as '*SYSTEM' but WebSphere MQ cannot register the queue manager as an SSL server application with DCM, or alternatively when the application definition for the queue manager has been manually removed from DCM.

Response:

Attempt to re-register the queue manager with Digital Certificate Manager by issuing CHGMQM SSLKEYR(*SYSTEM). If this is unsuccessful you may need to manually add the application definition through Digital Certificate Manager, see the WebSphere MQ Security manual for more details.

AMQ9616
The CipherSpec proposed is not enabled on the SSL server.
Severity:

30 : Severe error

Explanation:

The SSL subsystem at the SSL server end of a channel been configured in such a way that it has rejected the CipherSpec proposed by an SSL client. This rejection occured during the SSL handshake (i.e. it happened before the proposed CipherSpec was compared with the CipherSpec in the SSL server channel definition). This error most commonly occurs when the choice of acceptable CipherSpecs has been limited by setting the SSLFipsRequired attribute on the SSL server queue manager while the SSL client is trying to connect with a CipherSpec which is not FIPS-certified on the SSL server. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.

Response:

Analyse why the proposed CipherSpec was not enabled on the SSL server. Alter the client CipherSpec, or reconfigure the SSL server to accept the original client CipherSpec. Restart the channel.

AMQ9617
Parameter requesting FIPS has an invalid value.
Severity:

30 : Severe error

Explanation:

An SSL channel running on an MQ client has failed to start. This is because the value specified for the MQSSLFIPS environment variable, or in the MQSCO FipsRequired field, is invalid. The value specified was "<insert_3>"; valid values are "YES" or "NO".

Response:

Set the value specified for the MQSSLFIPS environment variable, or in the MQSCO FipsRequired field, to "YES" or "NO". Restart the channel.

AMQ9618
SSLCRLNL attribute points to a namelist with no names.
Severity:

30 : Severe error

Explanation:

An SSL channel has failed to start because the SSLCRLNL queue manager attribute points to a namelist with an empty list of names.

Response:

If CRL checking is required, set up the namelist referenced by SSLCRLNL with a non-empty list of authentication information object names. If no CRL checking is required, clear the SSLCRLNL queue manager attribute. Restart the failing channel.

AMQ9619
SSL cannot be run from an unthreaded HP-UX MQ client.
Severity:

30 : Severe error

Explanation:

On HP-UX, SSL cannot be run from a WebSphere MQ client which was linked with the unthreaded client libraries.

Response:

Either relink your client application with the threaded client libraries, or do not attempt to use SSL from this application.

AMQ9620
Internal error on call to SSL function on channel <insert_3>.
Severity:

30 : Severe error

Explanation:

An error indicating a software problem was returned from a function which is used to provide SSL support. The error code returned was <insert_1>. The function call was <insert_4>. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.

Response:

Collect the items listed in the 'Problem determination' section of the System Administration manual and contact your IBM support center.

AMQ9620 (iSeries)
Unexpected SSL error on call to <insert_4>.
Severity:

0 : Information

Explanation:

An unexpected SSL error was returned from function <insert_4> for channel <insert_3>. The error code returned was <insert_1>. GSKit error codes are documented in the MQ manuals and also in the GSKSSL member of the H file in library QSYSINC.

Response:

Collect the items listed in the 'Problem determination' section of the System Administration manual and contact your IBM support center.

AMQ9621
Error on call to SSL function ignored on channel <insert_3>.
Severity:

10 : Warning

Explanation:

An error indicating a software problem was returned from a function which is used to provide SSL support. The error code returned was <insert_1>. The function call was <insert_4>. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. This error is not regarded as sufficiently serious to interrupt channel operation; channel operation was not affected.

Response:

None.

AMQ9622
AUTHINFO object <insert_3> does not exist.
Severity:

30 : Severe error

Explanation:

A channel or channel process has failed to start because the namelist of CRL AUTHINFO objects includes the name <insert_3>, but no AUTHINFO object of that name exists.

Response:

Ensure all the names in the namelist specified on the SSLCRLNL queue manager attribute correspond to AUTHINFO objects which are to be used on the SSL channels. Restart the failing channel or channel process.

AMQ9623
Error inquiring on AUTHINFO object <insert_3>.
Severity:

30 : Severe error

Explanation:

A channel or channel process has failed to start because reason code <insert_1> was returned when an inquire was performed on AUTHINFO object <insert_3>.

Response:

Look at the MQRC_ values in the WebSphere MQ Application Programming Reference to determine the meaning of reason code <insert_1>, correct the error, and restart the failing channel or channel process.

AMQ9624
AUTHINFO object <insert_3> is not of type CRLLDAP.
Severity:

30 : Severe error

Explanation:

A channel or channel process has failed to start because one of the AUTHINFO objects specified in the SSLCRLNL namelist is not of AUTHTYPE CRLLDAP. Instead the type value is <insert_1>.

Response:

Only include CRLLDAP AUTHINFO objects in the namelist specified on the SSLCRLNL queue manager attribute. Restart the channel or channel process.

AMQ9625
AUTHINFO object <insert_3> was specified with an invalid CONNAME.
Severity:

30 : Severe error

Explanation:

A channel or channel process has failed to start because one of the AUTHINFO objects specified in the SSLCRLNL namelist has an invalid CONNAME parameter. The invalid value is <insert_4>.

Response:

Correct the invalid parameter. Restart the channel or channel process.

AMQ9626
Channel hanging while initializing SSL.
Severity:

30 : Severe error

Explanation:

The current channel cannot start because another channel is hanging while initializing the SSL subsystem.

Response:

Investigate the reason for the hang on the other channel. Once this is rectified, restart this channel.

AMQ9627
The path and stem name for the SSL key repository have not been specified.
Severity:

30 : Severe error

Explanation:

The directory path and file stem name for the SSL key repository have not been specified. On a MQ client system there is no default location for this file. SSL connectivity is therefore impossible as this file cannot be accessed.

Response:

Use the MQSSLKEYR environment variable or MQCONNX API call to specify the directory path and file stem name for the SSL key repository.

AMQ9628
An LDAP server containing CRLs was specified with an invalid CONNAME.
Severity:

30 : Severe error

Explanation:

The WebSphere MQ client has failed to connect because an invalid CONNAME was found for one of the LDAP servers containing CRLs. The invalid value is <insert_3>.

Response:

Correct the invalid parameter. If the LDAP details were defined on a queue manager system, regenerate the client definitions. Reconnect.

AMQ9629
Bad SSL cryptographic hardware parameters.
Severity:

30 : Severe error

Explanation:

The following string was supplied to specify or control use of SSL cryptographic hardware: <insert_4>. This string does not conform to any of the MQ SSL cryptographic parameter formats. The channel is <insert_3>. The channel did not start.

Response:

Correct your SSL cryptographic hardware parameters and restart the channel.

AMQ9630
An expired SSL certificate was loaded.
Severity:

30 : Severe error

Explanation:

An SSL certificate that was loaded was not corrupt, but failed validation checks on its date fields. The certificate has either expired, or its date is not valid yet (that is, the from date is later than today), or the validity date range is incorrect (for example, the to date is earlier than the from date).

Response:

Ensure that the specified SSL certificate has a valid expiry date.

AMQ9631
The CipherSpecs on the two ends of channel <insert_3> do not match.
Severity:

30 : Severe error

Explanation:

There is a mismatch between the CipherSpecs on the local and remote ends of channel <insert_3>. The channel will not run until this mismatch is resolved.

Response:

Change the channel definitions for <insert_3> so the two ends have matching CipherSpecs and restart the channel.

AMQ9631 (iSeries)
The CipherSpecs at the ends of channel <insert_3> do not match.
Severity:

30 : Severe error

Explanation:

There is a mismatch between the CipherSpecs on the local and remote ends of channel <insert_3>. The channel will not run until this mismatch is resolved. The local CipherSpec is <insert_4> and the remote CipherSpec is <insert_5>.

Response:

Change the channel definition for <insert_3> so that both ends have matching CipherSpecs and restart the channel.

AMQ9633
Bad SSL certificate for channel <insert_3>.
Severity:

30 : Severe error

Explanation:

A certificate encountered during SSL handshaking is regarded as bad for one of the following reasons:
(a) it was formatted incorrectly and could not be validated, or
(b) it was formatted correctly but failed validation against the Certification Authority (CA) root and other certificates held on the local system, or
(c) it was found in a Certification Revocation List (CRL) on an LDAP server.
(d) a CRL was specified but the CRL could not be found on the LDAP server.
The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.

Response:

Check which of the three possible causes applies on your system. Correct the error, and restart the channel.

AMQ9634
SSL security context expired.
Severity:

30 : Severe error

Explanation:

During an SSL operation to encrypt or decrypt a secured message, the SSL security context, which is used to secure communications and was previously established with the remote party, has expired because the remote party has shut down. The secured message has not been encrypted or decrypted. This failure has closed WebSphere MQ channel name <insert_3>. If the name is '????', the name is unknown. The SSL operation was <insert_4> and its completion code was <insert_5>.

Response:

Determine why the remote party has shut down and if necessary re-start the channel. The shut down might be the result of controlled termination by a system administrator, or the result of an unexpected termination due to an error. The SSL operation is described in the Windows Schannel reference manual.

AMQ9635
Channel <insert_3> did not specify a valid CipherSpec.
Severity:

30 : Severe error

Explanation:

Channel <insert_3> did not specify a valid CipherSpec.

Response:

Change channel <insert_3> to specify a valid CipherSpec.

AMQ9635 (iSeries)
Channel <insert_3> did not specify a valid CipherSpec.
Severity:

30 : Severe error

Explanation:

Channel <insert_3> did not specify a valid CipherSpec, or it specified a CipherSpec that is not available from the IBM Cryptographic Access Provider product installed on this machine. CipherSpecs that use 128-bit encryption algorithms are only available in 5722-AC3 (128-bit) IBM Cryptographic Access Provider.

Response:

Change channel <insert_3> to specify a valid CipherSpec that is available from the IBM Cryptographic Access Provider product installed on this machine. Check that the CipherSpec you are using is available on this machine in either the 5722-AC2 (56-bit) IBM Cryptographic Access Provider or 5722-AC3 (128-bit) IBM Cryptographic Access Provider licensed program.

AMQ9636
SSL distinguished name does not match peer name, channel <insert_3>.
Severity:

30 : Severe error

Explanation:

The distinguished name, <insert_4>, contained in the SSL certificate for the remote end of the channel does not match the local SSL peer name for channel <insert_3>. The distinguished name at the remote end must match the peer name specified (which can be generic) before the channel can be started.

Response:

If this remote system should be allowed to connect, either change the SSL peer name specification for the local channel so that it matches the distinguished name in the SSL certificate for the remote end of the channel, or obtain the correct certificate for the remote end of the channel. Restart the channel.

AMQ9637
Channel is lacking a certificate.
Severity:

30 : Severe error

Explanation:

The channel is lacking a certificate to use for the SSL handshake. The channel name is <insert_3> (if '????' it is unknown at this stage in the SSL processing). The channel did not start.

Response:

Make sure the appropriate certificates are correctly configured in the key repositories for both ends of the channel.
If you have migrated from WebSphere MQ V5.3 to V6, it is possible that the missing certificate is due to a failure during SSL key repository migration. Check the relevant error logs. If these show that an orphan certificate was encountered then you should obtain the relevant missing certification authority (signer) certificates and then import these and the orphan certificate into the WebSphere MQ V6 key repository, and then re-start the channel.

AMQ9638
SSL communications error for channel <insert_3>.
Severity:

30 : Severe error

Explanation:

An unexpected SSL communications error occurred for a channel, as reported in the preceding messages. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.

Response:

Investigate the problem reported in the preceding messages. Review the local and remote console logs for reports of network errors. Correct the errors and restart the channel.

AMQ9639
Remote channel <insert_3> did not specify a CipherSpec.
Severity:

30 : Severe error

Explanation:

Remote channel <insert_3> did not specify a CipherSpec when the local channel expected one to be specified. The channel did not start.

Response:

Change the remote channel <insert_3> to specify a CipherSpec so that both ends of the channel have matching CipherSpecs.

AMQ9640
SSL invalid peer name, channel <insert_3>, attribute <insert_5>.
Severity:

30 : Severe error

Explanation:

The SSL peer name for channel <insert_3> includes a distinguished name attribute key <insert_5> which is invalid or unsupported. The channel did not start.

Response:

Correct the SSL peer name for the channel. Restart the channel.

AMQ9641
Remote CipherSpec error for channel <insert_3>.
Severity:

30 : Severe error

Explanation:

The remote end of channel <insert_3> has had a CipherSpec error. The channel did not start.

Response:

Review the error logs on the remote system to discover the problem with the CipherSpec.

AMQ9642
No SSL certificate for channel <insert_3>.
Severity:

30 : Severe error

Explanation:

The channel <insert_3> did not supply a certificate to use during SSL handshaking, but a certificate is required by the remote queue manager. The channel did not start.

Response:

Ensure that the key repository of the local queue manager or MQ client contains an SSL certificate which is associated with the queue manager or client. Alternatively, if appropriate, change the remote channel definition so that its SSLCAUTH attribute is set to OPTIONAL and it has no SSLPEER value set.
If you have migrated from WebSphere MQ V5.3 to V6, it is possible that the missing certificate is due to a failure during SSL key repository migration. Check the relevant error logs. If these show that an orphan certificate was encountered then you should obtain the relevant missing certification authority (signer) certificates and then import these and the orphan certificate into the WebSphere MQ V6 key repository, and then re-start the channel.

AMQ9642 (iSeries)
No SSL certificate for channel <insert_3>.
Severity:

0 : Information

Explanation:

The channel <insert_3> did not supply a certificate to use during SSL handshaking, but a certificate is required by the remote queue manager. The channel did not start.

Response:

If the SSL key repository for the queue manager has been specified as '*SYSTEM' ensure that a certificate has been associated with the application description for the queue manager in Digital Certificate Manager. Alternatively, if appropriate, change the remote channel definition so that its SSLCAUTH attribute is set to OPTIONAL and it has no SSLPEER value set.

AMQ9643
Remote SSL peer name error for channel <insert_3>.
Severity:

30 : Severe error

Explanation:

The remote end of channel <insert_3> has had an SSL peer name error. The channel did not start.

Response:

Review the error logs on the remote system to discover the problem with the peer name.

AMQ9645
Correctly labelled SSL certificate missing on channel <insert_3>.
Severity:

30 : Severe error

Explanation:

The key database file in use has not been set up with a correctly labelled SSL certificate. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.

Response:

Add a correctly labelled SSL certificate to the current key database file. Restart the channel.

AMQ9646
Channel <insert_3> could not connect to any LDAP CRL servers.
Severity:

30 : Severe error

Explanation:

LDAP Certification Revocation List (CRL) servers were specified but a connection could not be established to any of them. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.

Response:

Check that the LDAP CRL server specifications are correct. If they are, check that the servers are running and that the networking to access them is working correctly. Fix any errors found and restart the channel.

AMQ9647
I/O error on SSL key repository.
Severity:

30 : Severe error

Explanation:

An I/O error was encountered when attempting to read the SSL key repository. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.

Response:

Analyse why there is a I/O problem when reading the key repository. Fix the error if one is found, or it may be a temporary problem. Restart the channel.

AMQ9648
The SSL key repository has an invalid internal format.
Severity:

30 : Severe error

Explanation:

The SSL key repository has an invalid internal format. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.

Response:

Recreate the SSL key repository and restart the channel.

AMQ9649
The SSL key repository contains duplicate keys.
Severity:

30 : Severe error

Explanation:

The SSL key repository contains two or more entries with the same key. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.

Response:

Use your key management tool to remove the duplicate keys. Restart the channel.

AMQ9650
The SSL key repository contains entries with duplicate labels.
Severity:

30 : Severe error

Explanation:

The SSL key repository contains two or more entries with the same label. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.

Response:

Use your key management tool to remove the duplicate entries. Restart the channel.

AMQ9651
The SSL key repository is corrupt or has a bad password.
Severity:

30 : Severe error

Explanation:

The SSL key repository has become corrupted or its password id is incorrect. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.

Response:

Use your key management tool to recreate the key repository with a new password. Restart the channel.

AMQ9652
The remote SSL certificate has expired.
Severity:

30 : Severe error

Explanation:

The SSL certificate used by MQ on the remote end of the channel has expired. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.

Response:

Use your key management tool to provide MQ with a current SSL certificate on the remote end of the channel. Restart the channel.

AMQ9653
An SSL trace file could not be opened.
Severity:

10 : Warning

Explanation:

An SSL trace file could not be opened. The SSL trace files are created in directory /var/mqm/trace and have names AMQ.SSL.TRC and AMQ.SSL.TRC.1. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. This error is not regarded as sufficiently serious to interrupt channel operation; channel operation was not affected.

Response:

Check that you have a directory called /var/mqm/trace and that the userid under which WebSphere MQ runs has permissions and space to create and open a file in that directory. Fix the problem and you will get SSL trace output.

AMQ9654
An invalid SSL certificate was received from the remote system.
Severity:

30 : Severe error

Explanation:

An SSL certificate received from the remote system was not corrupt but failed validation checks on something other than its ASN fields and date. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.

Response:

Ensure that the remote system has a valid SSL certificate. Restart the channel.

AMQ9655
Problem loading GSKit SSL support.
Severity:

30 : Severe error

Explanation:

MQ SSL support is provided on this platform using a component called GSKit which is installed as part of MQ. GSKit had an internal problem loading one if its dynamic link libraries. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.

Response:

Uninstall MQ and reinstall. Restart the channel.

AMQ9656
An invalid SSL certificate was received from the remote system.
Severity:

30 : Severe error

Explanation:

An SSL certificate received from the remote system was not corrupt but failed validation checks on its ASN fields. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.

Response:

Ensure that the remote system has a valid SSL certificate. Restart the channel.

AMQ9657
The key repository could not be opened (channel <insert_3>).
Severity:

30 : Severe error

Explanation:

The key repository could not be opened. The key repository either does not exist or has incorrect permissions associated with it. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.

Response:

Ensure that the key repository you specify exists and that its permissions are such that the MQ process involved can read from it. Restart the channel.

AMQ9658
An invalid SSL certificate has been encountered.
Severity:

30 : Severe error

Explanation:

An SSL certificate has been encountered which was not corrupt but which failed validation checks on its date fields. The certificate has either expired, or its date is not valid yet (i.e. the from date is later than today), or the validity date range is incorrect (e.g. the to date is earlier than the from date). The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.

Response:

Ensure that both the local and remote systems have valid, current SSL certificates. Restart the channel.

AMQ9659
A failure occurred during SSL handshaking.
Severity:

30 : Severe error

Explanation:

During SSL handshaking, or associated activities, a failure occurred. The failure is <insert_4> and has caused WebSphere MQ channel name <insert_3> to be closed. If the name is '????' then the name is unknown.

Response:

Refer to prior message in the WebSphere MQ error log for information related to this problem.

AMQ9660
SSL key repository: password stash file absent or unusable.
Severity:

30 : Severe error

Explanation:

The SSL key repository cannot be used because MQ cannot obtain a password to access it. Reasons giving rise to this error include:
(a) the key database file and password stash file are not present in the location configured for the key repository,
(b) the key database file exists in the correct place but that no password stash file has been created for it,
(c) the files are present in the correct place but the userid under which MQ is running does not have permission to read them,
(d) one or both of the files are corrupt.
The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.

Response:

Ensure that the key repository variable is set to where the key database file is. Ensure that a password stash file has been associated with the key database file in the same directory, and that the userid under which MQ is running has read access to both files. If both are already present and readable in the correct place, delete and recreate them. Restart the channel.

AMQ9661
Bad SSL data from peer on channel <insert_3>.
Severity:

30 : Severe error

Explanation:

An SSL channel has stopped because bad SSL data was received from the remote end of the channel. More detail on the nature of the corruption can be found from the GSKit return value of <insert_1> (the GSKit return values are documented in the MQ manuals). The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'.

Response:

Ensure you are connecting to a version of MQ which supports SSL at the remote end of the channel. Check your network between the two ends of the channel, and consider whether any possible causes of message corruption could be present. Fix any problems which may exist and restart the channel.

AMQ9661 (iSeries)
Bad SSL data from peer on channel <insert_3>.
Severity:

0 : Information

Explanation:

An SSL channel has stopped because bad SSL data was received from the remote end of the channel. More detail on the nature of the corruption can be found from the GSKit return value of <insert_1> (the GSKit return values are documented in the MQ manuals and also in the GSKSSL member of the H file in library QSYSINC). The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'.

Response:

Ensure the remote queue manager and channel listener are running and that you are connecting to a version of MQ which supports SSL at the remote end of the channel. Check your network between the two ends of the channel, and consider whether any possible causes of message corruption could be present. Fix any problems which may exist and restart the channel.

AMQ9662
SSL has encountered something it does not support.
Severity:

30 : Severe error

Explanation:

This error can arise for a number of reasons: 1) The platform does not support a given type of cryptographic hardware, e.g. Ncipher and Rainbow are/were not supported on the Linux/390 platform. 2) The cryptographic hardware cryptography has returned an error. 3) Unsupported X509 General Name format when checking the remote certificate. The GSKit SSL provider incorporated in MQ only supports formats rfc822, DNSName, directoryname, uniformResourceID, and IPAddress. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.

Response:

Check that your cryptographic hardware is supported on your platform and test it to see that it is working correctly. Check that the remote certificates you are using conform to the X509 General Name formats listed. Fix the problem and restart the channel.

AMQ9663
An invalid SSL certificate was received from the remote system.
Severity:

30 : Severe error

Explanation:

An SSL certificate received from the remote system failed validation checks on its signature. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.

Response:

Ensure that the remote system has a valid SSL certificate. Restart the channel.

AMQ9664
Bad userid for CRL LDAP server; SSL channel <insert_3>.
Severity:

30 : Severe error

Explanation:

Certification Revocation List (CRL) checking on an LDAP server or servers has been configured on the local MQ system. The userid information configured for the LDAP server or servers is incorrect. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.

Response:

Check the userid information for the CRL LDAP server or servers you have configured locally. Correct any problems found and restart the channel.

AMQ9665
SSL connection closed by remote end of channel <insert_3>.
Severity:

30 : Severe error

Explanation:

The SSL connection was closed by the remote end of the channel during the SSL handshake. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.

Response:

Check the remote end of the channel for SSL-related errors. Fix them and restart the channel.

AMQ9666
Error accessing CRL LDAP servers; SSL channel <insert_3>.
Severity:

30 : Severe error

Explanation:

CRL checking on LDAP servers has been configured on the local MQ system. An error was found when trying to access the CRL LDAP servers when validating a certificate from the remote system. Possible causes are:
(a) cannot connect to any of the LDAP servers, or
(b) invalid login user id or password for an LDAP server, or
(c) the certificate issuer's Distinguished Name (DN) is not defined in the DIT of an LDAP server.
The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.

Response:

Check access to the CRL LDAP server(s) you have configured locally. Put right any problems found and restart the channel.

AMQ9667
Bad password for CRL LDAP server; SSL channel <insert_3>.
Severity:

30 : Severe error

Explanation:

Certification Revocation List (CRL) checking on an LDAP server or servers has been configured on the local MQ system. The password information configured for the LDAP server or servers is incorrect. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.

Response:

Check the password information for the CRL LDAP server or servers you have configured locally. Correct any problems found and restart the channel.

AMQ9668
The specified PKCS #11 shared library could not be loaded.
Severity:

30 : Severe error

Explanation:

A failed attempt was made to load the PKCS #11 shared library specified to MQ in the PKCS #11 driver path field of the GSK_PKCS11 SSL CryptoHardware parameter. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.

Response:

Ensure that the PKCS #11 shared library exists and is valid at the location specified. Restart the channel.

AMQ9669
The PKCS #11 token could not be found.
Severity:

30 : Severe error

Explanation:

The PKCS #11 driver failed to find the token specified to MQ in the PKCS #11 token label field of the GSK_PKCS11 SSL CryptoHardware parameter. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.

Response:

Ensure that the PKCS #11 token exists with the label specified. Restart the channel.

AMQ9670
PKCS #11 card not present.
Severity:

30 : Severe error

Explanation:

A PKCS #11 card is not present in the slot. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.

Response:

Ensure that the correct PKCS #11 card is present in the slot. Restart the channel.

AMQ9671
The PKCS #11 token password specified is invalid.
Severity:

30 : Severe error

Explanation:

The password to access the PKCS #11 token is invalid. This is specified to MQ in the PKCS #11 token password field of the GSK_PKCS11 SSL CryptoHardware parameter. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.

Response:

Ensure that the PKCS #11 token password specified on GSK_PKCS11 allows access to the PKCS #11 token specified on GSK_PKCS11. Restart the channel.

AMQ9672
An SSL security call failed.
Severity:

30 : Severe error

Explanation:

An SSPI call to the Secure Channel (Schannel) SSL provider failed. The failure has caused WebSphere MQ channel name <insert_3> to be closed. If the name is '????' then the name is unknown.

Response:

Consult the Windows Schannel reference manual to determine the meaning of status <insert_5> for SSPI call <insert_4>. Correct the failure and if necessary re-start the channel.

AMQ9673
SSL client handshaking failed.
Severity:

30 : Severe error

Explanation:

During an SSL client's handshaking, an SSPI call to the Secure Channel (Schannel) SSL provider failed. The failure has caused WebSphere MQ channel name <insert_3> to be closed. If the name is '????' then the name is unknown.

Response:

Consult the Windows Schannel reference manual to determine the meaning of status <insert_4> for SSPI call <insert_5>. Correct the failure and if necessary re-start the channel.

AMQ9674
An unknown error occurred during an SSL security call.
Severity:

30 : Severe error

Explanation:

An unknown error occurred during an SSPI call to the Secure Channel (Schannel) SSL provider. The error may be due to a Windows SSL problem or to a general Windows problem or to invalid WebSphere MQ data being used in the call. The WebSphere MQ error recording routine has been called. The error has caused WebSphere MQ channel name <insert_3> to be closed. If the name is '????' then the name is unknown.

Response:

Consult the Windows Schannel reference manual to determine the meaning of status <insert_5> for SSPI call <insert_4>. If the problem can be resolved using the manual, correct the failure and if necessary re-start the channel. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ9675
The requested certificate could not be found.
Severity:

30 : Severe error

Explanation:

A request for a certificate identified as <insert_4> <insert_5> in the store <insert_3> has failed, because the certificate could not be found. The Windows error code has been set to <insert_1>. The WebSphere MQ error recording routine has been called.

Response:

Consult the Windows reference manual to determine the meaning of error <insert_1> if this value is non-zero. Check to see whether the specified certificate has been copied to the correct certificate store and has not been deleted. Use the amqmcert command line utility or the WebSphere MQ Explorer administration application to configure certificate store for use with WebSphere MQ. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ9676
The Windows cryptographic services library could not be loaded.
Severity:

30 : Severe error

Explanation:

WebSphere MQ requires crypt32.dll to be available in order to carry out cryptographic functionality. The attempt to load this library returned the Windows error code <insert_1>. The WebSphere MQ error recording routine has been called.

Response:

Consult the Windows reference manual to determine the meaning of error code <insert_1>. Check that the crypt32.dll file is available and not corrupt. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ9677
The Windows security services library could not be loaded.
Severity:

30 : Severe error

Explanation:

WebSphere MQ requires <insert_3> to be available in order to run or configure SSL functionality. The attempt to load this library returned the Windows error code <insert_1>. The WebSphere MQ error recording routine has been called.

Response:

Consult the Windows reference manual to determine the meaning of error code <insert_1>. Check that the <insert_3> file is available and not corrupt. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ9678
The certificate <insert_4>/<insert_5> already exists in the store <insert_3>.
Severity:

10 : Warning

Explanation:

The certificate store <insert_3> already contains the specified certificate, identified by the issuer name of <insert_4>, serial number <insert_5>. The existing certificate has not been replaced.

AMQ9679
The certificate store <insert_3> could not be opened.
Severity:

30 : Severe error

Explanation:

The certificate store <insert_3> could not be opened, and failed with the Windows error code <insert_1>. The WebSphere MQ error recording routine has been called.

Response:

Consult the Windows reference manual to determine the meaning of error <insert_1> if this value is non-zero. Check that either your MQSSLKEYR environment variable (for client connections), or SSLKEYR queue manager attribute (for WebSphere MQ queue managers) has been defined correctly, and that the file path specified is valid. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ9680
A problem was encountered with the specified certificate file.
Severity:

30 : Severe error

Explanation:

A problem occurred when attempting to read the certificate from the file <insert_3>. The file may be corrupt or incorrectly formatted. The Windows error code reported is <insert_1>. The WebSphere MQ error recording routine has been called.

Response:

Ensure that the certificate file is valid and complete, and in one of the file formats supported by WebSphere MQ. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ9681
The requested functionality is not supported on this system.
Severity:

30 : Severe error

Explanation:

An SSL function was attempted that is not supported on this system. a) importing pfx format certificate files with private key data is only supported on Windows 2000 or greater. b) a the security library installed on your system is not of the correct level and does not contain the pre-requisite functions. On pre Windows 2000 systems, Internet Explorer 4.1 or greater must be installed. The WebSphere MQ error recording routine has been called.

Response:

If pre-requisite software is missing, please install the necessary levels of software and retry the operation. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ9682
The WebSphere MQ SSL library has not been initialized.
Severity:

30 : Severe error

Explanation:

The WebSphere MQ SSL library 'amqcssln.dll' has been called without it first being initialized by the calling process.

Response:

Ensure that the initialization function has been called prior to issuing any amqcssln function calls.

AMQ9683
The private key data for this certificate is not exportable.
Severity:

30 : Severe error

Explanation:

An attempt has been made to export the private key data from a certificate, but the properties of the certificate will not allow this. WebSphere MQ needs to be able to export private key data when copying personal certificates between certificate stores. The Windows cryptographic API returned the error code <insert_1>.

Response:

When requesting the certificate from the certificate authority, the private key data must be marked as exportable to enable WebSphere MQ to be able to copy the certificate and private key data into a WebSphere MQ store. The certificate file may need to be requested again to resolve this problem. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ9684
A problem occurred while attempting to access the certificate's properties.
Severity:

30 : Severe error

Explanation:

The certificate issued by <insert_3> with serial number <insert_4>, or it's private key data, appears to be unusable and may be corrupt. The Windows return code <insert_1> was generated when attempting to use this certificate. The WebSphere MQ error recording routine has been called.

Response:

Consult the Windows reference manual to determine the meaning of error <insert_1>. Check that the certificate is valid and has not been corrupted. If it is possible that the certificate or private key data is corrupt, try to remove the certificate from your system and re-import it. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ9685
A problem occured while accessing the registry.
Severity:

30 : Severe error

Explanation:

An error occured while attempting to load or unload the personal registry hive (HKEY_LOCAL_USER) for the user who launched this process. The WebSphere MQ error recording routine has been called.

Response:

If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ9686
An unexpected error occured while attempting to manage a certificate store.
Severity:

30 : Severe error

Explanation:

The Windows cryptographic API returned error code <insert_1> when calling the function <insert_3> for certificate store <insert_4>. The error may be due to a certificate store problem or to a general Windows problem or to a problem with a certificate in the store. The WebSphere MQ error recording routine has been called.

Response:

Consult the Windows reference manual to determine the meaning of error <insert_1>. Check that the certificate store is valid and not corrupt. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ9687
The pfx password provided is invalid.
Severity:

30 : Severe error

Explanation:

The password supplied for importing or copying the certificate is incorrect, and the operation could not be completed.

Response:

Make sure the password is correct and try again. If the password has been forgotten or lost, the certificate will need to be regenerated or exported from the original source.

AMQ9688
The private key data for this certificate is unavailable.
Severity:

30 : Severe error

Explanation:

The private key data associated with this certificate is reported as being present on the system, but has failed, returning the Windows error code <insert_1>. The WebSphere MQ error recording routine has been called.

Response:

Consult the Windows reference manual to determine the meaning of error code <insert_1>. If the problem can be resolved using the manual, correct the failure and if necessary re-try the operation. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ9689
An unknown error occurred deleting the store <insert_3>.
Severity:

30 : Severe error

Explanation:

The WebSphere MQ certificate store for queue manager <insert_3> could not be deleted. The filename for the certificate store is <insert_4>. The Windows error code has been set to <insert_1>. The WebSphere MQ error recording routine has been called.

Response:

Consult the Windows reference manual to determine the meaning of error <insert_1>. If the problem can be resolved using the manual, correct the failure and if necessary re-try the operation. Check that the store file exists and that other processes (such as queue managers) that may be accessing the store are not running. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ9690
The public key in the issuer's certificate has failed to validate the subject certificate.
Severity:

30 : Severe error

Explanation:

The public key in the issuer's certificate (CA or signer certificate), is used to verify the signature on the subject certificate assigned to channel <insert_3>. This verification has failed, and the subject certificate therefore cannot be used. The WebSphere MQ error recording routine has been called.

Response:

Check that the issuer's certificate is valid and available, and that it is up to date. Verify with the certificate's issuer that the subject certificate and issuer certificate should still be valid. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ9691
The WebSphere MQ MQI library could not be loaded.
Severity:

30 : Severe error

Explanation:

The library file <insert_3> is expected to be available on your system, but attempts to load it have failed with Windows return code <insert_1>. The WebSphere MQ error recording routine has been called.

Response:

Ensure that the WebSphere MQ <insert_3> library file exists and is available on your system. Consult the Windows reference manual to determine the meaning of error code <insert_1>. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ9692
The SSL library has already been initialized.
Severity:

20 : Error

Explanation:

The SSL library has already been initialized once for this process, any changes to SSL attributes will not take affect, and the original values will remain in force.

Response:

If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ9693
The password provided for the LDAP server is incorrect.
Severity:

30 : Severe error

Explanation:

One or more of the LDAP servers used for providing CRL information to WebSphere MQ has rejected a login attempt because the password provided is incorrect. The WebSphere MQ error recording routine has been called. The error has caused WebSphere MQ channel name <insert_3> to be closed. If the name is '????' then the name is unknown.

Response:

Ensure that the passwords specified in the AuthInfo objects are correct for each server name provided. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ9694
The DN syntax provided for an LDAP search is invalid.
Severity:

30 : Severe error

Explanation:

The distinguished name provided in one or more AuthInfo object definitions is invalid, and the request to a CRL LDAP server has been rejected. The WebSphere MQ error recording routine has been called. The error has caused WebSphere MQ channel name <insert_3> to be closed. If the name is '????' then the name is unknown.

Response:

Verify that the details supplied in the AuthInfo object definitions for this channel are correct. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ9695
The username provided for the LDAP server is incorrect.
Severity:

30 : Severe error

Explanation:

One or more of the LDAP servers used for providing CRL information to WebSphere MQ has rejected a login attempt because the username provided does not exist. The WebSphere MQ error recording routine has been called. The error has caused WebSphere MQ channel name <insert_3> to be closed. If the name is '????' then the name is unknown.

Response:

Ensure that the usernamed specified in the AuthInfo objects for this channel are correct for each LDAP server name provided. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ9696
Usage: amqmcert [SERVERNAME] [-a handle]
[-k SSLKeyR|CA|ROOT|MY] [-m QueueMgr]
[-s CertFile] [-p PersonalCertFile] [-z Password]
[-x handle] [-l] [-d handle] [-r handle] [-u]
[-h]
Severity:

0 : Information

Explanation:

This shows the correct usage.

Response:

None.

AMQ9697
WebSphere MQ Services could not be contacted on the target server.
Severity:

30 : Severe error

Explanation:

An attempt was made to contact the WebSphere MQ Services on the target server <insert_3>. The call failed with return code <insert_1>. The WebSphere MQ error recording routine has been called.

Response:

Ensure that the target server name specified is correct and that you have sufficient access rights on that server to be able to administer WebSphere MQ. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ9698
An SSL security call failed during SSL handshaking.
Severity:

30 : Severe error

Explanation:

An SSPI call to the Secure Channel (Schannel) SSL provider failed during SSL handshaking. The failure has caused WebSphere MQ channel name <insert_3> to be closed. If the name is '????' then the name is unknown.

Response:

Consult the Windows Schannel reference manual to determine the meaning of status <insert_5> for SSPI call <insert_4>. Correct the failure and if necessary re-start the channel.

AMQ9699
An unknown error occurred during an SSL security call during SSL handshaking.
Severity:

30 : Severe error

Explanation:

An unknown error occurred during an SSPI call to the Secure Channel (Schannel) SSL provider during SSL handshaking. The error may be due to a Windows SSL problem or to a general Windows problem or to invalid WebSphere MQ data being used in the call. The WebSphere MQ error recording routine has been called. The error has caused WebSphere MQ channel name <insert_3> to be closed. If the name is '????' then the name is unknown.

Response:

Consult the Windows Schannel reference manual to determine the meaning of status <insert_5> for SSPI call <insert_4>. If the problem can be resolved using the manual, correct the failure and if necessary re-start the channel. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ9710
SSL security refresh failed.
Severity:

30 : Severe error

Explanation:

The request to refresh SSL security was unsuccessful.

Response:

Look at previous error messages in the error files to determine the cause of the failure.

AMQ9711
SSL security refresh succeeded but channel restarts failed.
Severity:

30 : Severe error

Explanation:

The SSL environments for this queue manager have been refreshed so current values and certificates are in use for all SSL channels. However, not all the outbound SSL channels which were running when the security refresh was initiated could be restarted after the refresh had completed.

Response:

Look at previous error messages in the error files to determine which channels could not be restarted. Restart these if necessary.

AMQ9712
SSL security refresh timed out waiting for channel <insert_3>.
Severity:

30 : Severe error

Explanation:

The system was performing a security refresh for SSL. This function requests all outbound and inbound SSL channels to stop. It then waits for these channels to actually stop. SSL channel <insert_3> did not stop within the timeout period.

Response:

Investigate why channel <insert_3> is hung. Terminate the hung channel. Rerun the SSL security refresh.

AMQ9713
Channel <insert_3> ended: SSL refresh in progress.
Severity:

0 : Information

Explanation:

The SSL support on this queue manager is in the middle of a security refresh. An attempt was made to start outbound SSL channel <insert_3>. It cannot start while the SSL security refresh is in progress. The channel is restarted automatically once the SSL security refresh is complete.

Response:

None.

AMQ9714
SSL refresh on receiving queue manager: channel did not start.
Severity:

30 : Severe error

Explanation:

An SSL security refresh is in progress on the queue manager at the receiving end of this SSL channel. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.

Response:

Restart the channel once the SSL refresh is complete. The channel will restart automatically if it is configured to retry the connection.

AMQ9715
Unexpected error detected in validating SSL session ID.
Severity:

30 : Severe error

Explanation:

This error can arise when the GSKit SSL provider is missing one or more pre-requisite PTFs on the OS/400 platform. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'.

Response:

Ensure the GSKit SSL provider is at the latest level of maintenance and restart the channel.

AMQ9719
Invalid CipherSpec for FIPS mode.
Severity:

30 : Severe error

Explanation:

The user is attempting to start a channel on a queue manager or MQ client which has been configured to run in FIPS mode. The user has specified a CipherSpec which is not FIPS-compliant. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'.

Response:

Redefine the channel to run with a FIPS-compliant CipherSpec. Alternatively, the channel may be defined with the correct CipherSpec and the queue manager or MQ client should not be running in FIPS mode; if this is the case, ensure that FIPS mode is not configured. Once the error is corrected, restart the channel.

AMQ9720


QUEUE MANAGERS:
Severity:

0 : Information

Explanation:

None.

Response:

None.

AMQ9721

Queue Manager Name: <insert_3>
Severity:

0 : Information

Explanation:

None.

Response:

None.

AMQ9722


CLIENTS:
Severity:

0 : Information

Explanation:

None.

Response:

None.

AMQ9723

Client Certificate Store: <insert_3>
Severity:

0 : Information

Explanation:

None.

Response:

None.

AMQ9724

Expiry Time: <insert_1>
Migration Status: To be migrated
Password: ********
Severity:

0 : Information

Explanation:

None.

Response:

None.

AMQ9725

Expiry Time: <insert_1>
Migration Status: Failed
Password: ********
Severity:

0 : Information

Explanation:

None.

Response:

None.

AMQ9726
A certificate failed to be migrated because it has an invalid date.
The certificate's details are:
[Microsoft Certificate Store], [Subject], [Issuer], [Serial Number]:
<insert_3>.
Severity:

30 : Severe error

Explanation:

During the migration of a certificate, the certificate's date fields have been found to be invalid. The certificate has either expired or its "from" date is later than today's date or its "to" date is earlier than the "from" date.
The certificate has not been migrated.

Response:

If the certificate is required for migration then obtain a valid replacement before importing it into the GSKit key database <insert_5>.

AMQ9727
A certificate failed to be migrated because it has an incomplete certification path.
The certificate's details are:
[Microsoft Certificate Store], [Subject], [Issuer], [Serial Number]:
<insert_3>.
Severity:

30 : Severe error

Explanation:

During the migration of a certificate, the certificate's certification authority (signer) certificate could not be found. The certificate is therefore regarded as an orphan certificate.
A copy of the certificate has been written to the file name <insert_4>.
If file name is suffixed ".cer" then the certificate is a certification authority (signer) certificate. If file name is suffixed ".pfx" then the certificate is a personal certificate and it has a password which is the same as that specified for the GSKit key database <insert_5>. The certificate has not been migrated.

Response:

If the certificate is required for migration then ensure that a complete certification path exists in the GSKit key database <insert_5> before importing the certificate.

AMQ9728
A certificate failed to be migrated because it could not be imported into the GSKit key database <insert_5>.
The certificate's details are:
[Microsoft Certificate Store], [Subject], [Issuer], [Serial Number]:
<insert_3>.
Severity:

30 : Severe error

Explanation:

A certificate failed to be imported because there was a problem during the migration of the certificate.
A copy of the certificate has been written to the file name <insert_4>.
If file name is suffixed ".cer" then the certificate is a certification authority (signer) certificate. If file name is suffixed ".pfx" then the certificate is a personal certificate and it has a password which is the same as that specified for the GSKit key database <insert_5>. The certificate has not been migrated.

Response:

Refer to the previous message in the error log to determine the cause of the failure. If appropriate, refer to the Windows or GSKit reference documentation to determine the cause.

AMQ9729
Unable to create certificate file <insert_3>.
Severity:

30 : Severe error

Explanation:

A certificate failed to be imported because there was a problem during the migration of the certificate. In addition to this first problem, a second problem occurred when trying to create a copy of the certificate by writing it to the file <insert_3>. The certificate is located in the Microsoft Certificate Store <insert_4>. The certificate is intended for the GSKit key database <insert_5>. If file name is suffixed ".cer" then the certificate is a certification authority (signer) certificate. If file name is suffixed ".pfx" then the certificate is a personal certificate. The certificate has not been migrated.

Response:

Determine the cause of the 2 problems. Refer to the previous message in the error log to determine the cause of the first failure. If appropriate, refer to the Windows or GSKit reference documentation to determine the cause. The second failure occurred during a call to the Windows 'CreateFile' function with a return code of <insert_1>. For this failure, check that file does not already exist and that you have authority to create this file.

AMQ9730
Certificate migration has completed with no failures. The number of certificates migrated was <insert_1>.
Severity:

0 : Information

Explanation:

The migration of certificates from the Microsoft Certificate Store <insert_3> to the GSKit key database <insert_4> has completed and there were no migration failures. The number of certificates migrated was <insert_1>.

Response:

If any certificates were migrated, use the GSKit iKeyman GUI to verify that the GSKit key database contains all the certificates required to support the intended SSL channel. If no certificates were migrated then this is probably because <insert_3> contained only a default set of certification authority (signer) certificates. The default set is not migrated because the newly created GSKit key database will have its own set which will be the same or more up to date.
Although there were no failures which caused certificates not to be migrated, there may have been other failures and these must be resolved otherwise the SSL channel may subsequently fail to start. Refer to the error log and check for any failures.

AMQ9731
The Transfer Certificates (amqtcert) command has completed.
Severity:

0 : Information

Response:

None.

AMQ9732
A registry entry already exists for <insert_3>.
Severity:

30 : Severe error

Explanation:

The command has been used to request automatic migration for a queue manager's or a client's Microsoft Certificate Store. However, there is already an entry in the registry for this store. If the request was for a queue manager then <insert_3> is the queue manager name, otherwise it is the name of the client's Microsoft Certificate Store.

Response:

List, and then check, the contents of the registry by running the Transfer Certificates (amqtcert) command with the options "-a -l". If it is necessary to replace the entry then firstly remove it, by using amqtcert with the "-r" option, then use amqtcert to request automatic migration.

AMQ9733
The request to automatically migrate certificates has completed successfully.
Severity:

0 : Information

Explanation:

A request was made to automatically migrate SSL certificates. This request may have been made during the installation of WebSphere MQ or by using the Transfer Certificates (amqtcert) command. The request has now been performed and the migration has completed successfully.

Response:

Use the GSKit iKeyman GUI to verify that the GSKit key database contains all the certificates required to support the intended SSL channel. If no certificates were migrated then this is because the Microsoft Certificate Store contained only a default set of certification authority (signer) certificates. The default set is not migrated because the newly created GSKit key database will have its own set which will be the same or more up to date.

AMQ9734
There was a failure during the automatic migration of certificates.
Severity:

30 : Severe error

Explanation:

A request was made to automatically migrate SSL certificates. This request may have been made during the installation of WebSphere MQ or by using the Transfer Certificates (amqtcert) command. The request has now been performed but there was a failure during the migration process.

Response:

Refer to previous messages in the error log to determine the cause of the failure. It may be the case that all certificates have successfully migrated and that the failure did not affect this part of the migration process. In this case, use the GSKit iKeyman GUI to verify that the GSKit key database contains all the certificates required to support the intended SSL channel.

AMQ9735
Certificate migration has terminated unexpectedly. A failure occured during GSKit initialization.
Severity:

30 : Severe error

Explanation:

The certificate migration process has terminated unexpectedly. The migration requires the GSKit environment to be successfully initialized. This involves the GSKit operations of initialization, creation of the key database and stashing of the key database password. There was a failure during one of these operations. No certificates have been migrated. If the stashing of the password failed then the key database <insert_4> will have been created. The failure occurred during the GSKit operation <insert_3> and the GSKit return code <insert_1> was generated.

Response:

If the key database has been created then, after the cause of the failure has been resolved, delete it, remove the relevant registry state information and then re-try the certificate migration process. Use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ9736
The library <insert_3> was not found.
Severity:

30 : Severe error

Explanation:

An attempt to dynamically load the library <insert_3> failed because the library was not found. If this an WebSphere MQ library, it is only available on WebSphere MQ server installations and is required when the Transfer Certificates (amqtcert) command is used to perform a queue manager operation. If this a GSKit library, it should have been installed during the WebSphere MQ installation.

Response:

Do not use the command to perform a queue manager operation on a WebSphere MQ client-only installation. If the command has been made on a WebSphere MQ server installation, or if it is a GSKit library which is missing, then record the problem identifier, save any generated output files and then contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ9737
Unable to allocate memory.
Severity:

30 : Severe error

Explanation:

An attempt to allocate memory failed.

Response:

Make more memory available to the command.

AMQ9738
Unable to obtain the MQSSLKEYR environment variable value.
Severity:

30 : Severe error

Explanation:

An attempt to obtain the MQSSLKEYR environment variable value failed. When using the command to specify all clients then the MQSSLKEYR environment variable must be defined with the name of a Microsoft Certificate Store file containing certificates for all clients.

Response:

Ensure that the MQSSLKEYR environment variable is defined with an appropriate value.

AMQ9739
The certificate store <insert_3> could not be accessed.
Severity:

30 : Severe error

Explanation:

The certificate store <insert_3> could not be accessed, and failed with Windows error code <insert_1>. If you are using the -c parameter check that the name given to amqtcert is correct. If you are using the -m parameter check the SSLKEYR value on the queue manager specified.

Response:

Consult the Windows reference manual to determine the meaning of error <insert_1> if this value is non-zero. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ9740
The certificate store <insert_3> could not be opened.
Severity:

30 : Severe error

Explanation:

The certificate store <insert_3> could not be opened, and failed with Windows error code <insert_1>.

Response:

Consult the Windows reference manual to determine the meaning of error <insert_1> if this value is non-zero. If the problem cannot be resolved then use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ9741
A problem occurred during a Windows operation.
Severity:

30 : Severe error

Explanation:

During operation <insert_3>, the Windows return code <insert_1> was generated.

Response:

Consult the Windows reference manual to determine the meaning of return code <insert_1> for operation <insert_3>.

AMQ9742
A problem occured during a GSKit operation.
Severity:

30 : Severe error

Explanation:

During operation <insert_3>, the GSKit return code <insert_1> was generated.

Response:

Use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ9743
A certificate failed to be migrated and failed to be logged.
The certificate's details are:
[Microsoft Certificate Store], [Subject], [Issuer], [Serial Number]:
<insert_3>.
Severity:

30 : Severe error

Explanation:

There was a problem trying to migrate a certificate to the GSKit key database <insert_5>.

Response:

Refer to the previous message in the error log to determine why the migration failed.

AMQ9744
No matching automatic migration registry entry.
Severity:

10 : Warning

Explanation:

There is no automatic certificate migration entry in the registry which matches the input provided.

Response:

None, if the entry to be removed was correctly specified. Otherwise, input the command again with correct parameters.

AMQ9745
amqtcert: insufficient memory to migrate certificates.
Severity:

30 : Severe error

Explanation:

An attempt to allocate memory failed while amqtcert was migrating certificate file <insert_3>.sto'. The migration did not complete successfully.

Response:

Do not delete <insert_3>.sto', but delete all other files called <insert_4>.*' (these were created as a result of the failed migration). Also, if you want to rerun this migration automatically, use the -r flag on amqtcert to remove the automatic migration registry entry for this .sto file. Then use the -a flag on amqtcert to create a new automatic migration registry entry for this .sto file.
Make more memory available. Rerun the migration.

AMQ9746
File <insert_3> not found.
Severity:

30 : Severe error

Explanation:

The file specified as a command argument has not been found. The characters ".sto" have been automatically appended to the file name.

Response:

Check that file exists and that it is specified as the absolute (rather than relative) directory path and file name (excluding the .sto suffix) of the Microsoft Certificate Store.

AMQ9747
Usage: amqtcert [-a] [-c [Filename | *]] [-e ExpirationTime] [-g FileName]
[-i ListNumber] [-l] [-m [QMgrName | *]] [-p Password]
[-r] [-u ClientLogonID] [-w FileName]
Severity:

0 : Information

Response:

None.

AMQ9748
A problem occurred accessing the Windows registry.
Severity:

30 : Severe error

Explanation:

An attempt to access a key or value or data field in the Windows registry key failed. The failure may be due to part of the registry being in an invalid state or may be due to insufficient authority to access that part. The WebSphere MQ error recording routine has been called.

Response:

If <insert_3> includes the name of a Windows call, consult the Windows reference manual to determine the meaning of status <insert_1> for that call. Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ9749
Invalid combination of command arguments.
Severity:

30 : Severe error

Explanation:

The command syntax is incorrect because of an invalid combination of arguments.

Response:

Re-try the command using a valid combination of arguments.

AMQ9750
File <insert_3> already exists.
Severity:

30 : Severe error

Explanation:

The file <insert_3> cannot be created because it already exists.

Response:

Ensure that the file does not exist in the directory. If necessary, make a copy of the file before renaming or moving or deleting it.

AMQ9751
You are not authorized to perform the requested operation.
Severity:

30 : Severe error

Explanation:

You tried to issue a command for which you are not authorized.

Response:

Contact your system administrator to perform the command for you or to request authority to perform the command.

AMQ9752
A certificate failed to be migrated because a Windows operation failed.
The certificate's details are:
[Microsoft Certificate Store], [Subject], [Issuer], [Serial Number]:
<insert_4>.
Severity:

30 : Severe error

Explanation:

A personal certificate could not be migrated because there was a failure during the Windows operation <insert_3> with a return code of <insert_1>. A personal certificate is exported, with its private key data, from the Microsoft Certificate Store prior to being imported into the GSKit key database. The failure occurred during the export and is probably due to a problem with accessing or using the private key data assoicated with the personal certificate.

Response:

Check that the private key data is available and that you have authority to access it. Consult the Windows reference manual to determine the meaning of return code <insert_1> for operation <insert_3>.

AMQ9753
File <insert_3> is empty.
Severity:

30 : Severe error

Explanation:

The file <insert_3> cannot be used because it is empty.

Response:

Ensure that the correct file has been used and if necessary investigate the reason for it being empty.

AMQ9754
A certificate failed to be migrated because a GSKit operation failed.
The certificate's details are:
[Microsoft Certificate Store], [Subject], [Issuer], [Serial Number]:
<insert_4>.
Severity:

30 : Severe error

Explanation:

During operation <insert_3>, the GSKit return code <insert_1> was generated.

Response:

Use the standard facilities supplied with your system to record the problem identifier and save the generated output files, and then contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ9755
Certificate migration has completed with some failures. The number of certificates migrated was <insert_1>.
Severity:

0 : Information

Explanation:

The migration of certificates from the Microsoft Certificate Store <insert_3> to the GSKit key database <insert_4> has completed but there has been one or more failures. The number of certificates migrated was <insert_1>.

Response:

If any certificates were migrated, use the GSKit iKeyman GUI to verify that the GSKit key database contains all the certificates required to support the intended SSL channel. The failures must be resolved otherwise the SSL channel may subsequently fail to start. Refer to previous messages in the error log to determine the cause of such failures.

AMQ9756
The number of certificates in the Microsoft Certificate Store <insert_3> is <insert_1>.
Severity:

0 : Information

Explanation:

Provides a count of the number of certificates in the Microsoft Certificate Store <insert_3>.

Response:

None.

AMQ9757

Certificate <insert_1>
Severity:

0 : Information

Explanation:

None.

Response:

None.

AMQ9758
Subject: <insert_3>
Severity:

0 : Information

Explanation:

None.

Response:

None.

AMQ9759
Issuer: <insert_3>
Severity:

0 : Information

Explanation:

None.

Response:

None.

AMQ9760
Valid From: <insert_3> to <insert_4>
Severity:

0 : Information

Explanation:

None.

Response:

None.

AMQ9761
Certificate Usage: <All>
Severity:

0 : Information

Explanation:

None.

Response:

None.

AMQ9762
Certificate Usage: <insert_3>
Severity:

0 : Information

Explanation:

None.

Response:

None.

AMQ9763
Certificate Type: Personal
Severity:

0 : Information

Explanation:

None.

Response:

None.

AMQ9764
Certificate Type: Signer
Severity:

0 : Information

Explanation:

None.

Response:

None.

AMQ9765
Personal certificate not found for the command option "-i <insert_1>".
Severity:

30 : Severe error

Explanation:

The Transfer Certificates (amqtcert) command was executed using the "-i ListNumber" option with a value of <insert_1>. However, no personal certificate was found which corresponded to this value. Certificate migration has failed and no certificates were migrated.

Response:

Check that the option value corresponds to a correctly identified personal certificate. If it is not correct then run the command using the "-l List" option to determine the correct number. A GSKit key database, and its associated key database files, was created when the command was run using the "-i ListNumber" option. The database and associated files must be deleted before re-trying the command with the "-i" option.

AMQ9766
A failure occurred creating the GSKit key database <insert_4>.
Severity:

30 : Severe error

Explanation:

GSKit was unable to create the key database and its associated files. During the GSKit operation <insert_3>, the return code <insert_1> was generated. This is probably due to insufficient authority or to insufficient disk space being available.

Response:

Check that you have sufficient authority and that there is sufficient disk space available.

AMQ9767
Usage: strmqikm [iKeymanWorkingDirectory]
Severity:

0 : Information

Response:

None.

AMQ9768
Directory <insert_3> not found.
Severity:

30 : Severe error

Explanation:

The directory specified as a command argument has not been found.

Response:

Check that the directory exists and that it is specified as an absolute (rather than relative) directory path.

AMQ9769
Usage: runmqckm
-keydb -changepw Change the password for a key database
-convert Convert the format of a key database
-create Create a key database
-delete Delete a key database
-stashpw Stash the password of a key database into a file
-list Currently supported types of key database.
-cert -add Add a CA Certificate
-create Create a self-signed certificate
-delete Delete a certificate
-details Show the details of a specific certificate
-export Export a personal certificate and associated private key into a PKCS12 file or a key database
-extract Extract a certificate from a key database
-getdefault Show the default personal certificate
-import Import a certificate from a key database or a PKCS12 file
-list List certificates in a key database
-modify Modify a certificate (NOTE: the only field that my be modified is the trust field)
-receive Receive a certificate
-setdefault Set the default personal certificate
-sign Sign a certificate
-certreq -create Create a certificate request
-delete Delete a certificate request from a certificate request database
-details Show the details of a specific certificate request
-extract Extract a certificate from a certificate request database
-list List all certificate requests in a certificate request database
-recreate Recreate a certificate request
-version Display ikeycmd version information
-help Display this help text
Severity:

0 : Information

Response:

None.

AMQ9913
The specified local address <insert_3> cannot be resolved to an IP address. The return code is <insert_1>.
Severity:

30 : Severe error

Explanation:

An attempt to resolve the local address hostname to an IP address has failed.

Response:

Check that the local address hostname is correct and has an entry in the DNS database.

AMQ9914
The type of local address specified is incompatible with the IP protocol (<insert_3>) used.
Severity:

30 : Severe error

Explanation:

An attempt to use a local address that is incompatible with the IP protocol used.

Response:

Make sure that the local address specified is of the same type (IPv4 or IPV6) as the IP Protocol.

AMQ9915
The IP protocol <insert_3> is not present on the system.
Severity:

30 : Severe error

Explanation:

An attempt to use an IP protocol that is not present on the system has been made.

Response:

Install the required IP protocol or use an IP protocol that is available on the system.

AMQ9920
A SOAP Exception has been thrown.
Severity:

30 : Severe error

Explanation:

A SOAP method encountered a problem and has thrown an exception. Details of the exception are:
<insert_3>

Response:

Investigate why the SOAP method threw the exception.

AMQ9921
An error was encountered writing to the Dead Letter Queue.
Severity:

30 : Severe error

Explanation:

An error was encountered when an attempt was made to write a message to Dead Letter Queue <insert_3>. The message was <insert_4>.

Response:

Ensure that Dead Letter Queue <insert_3> exists and is put enabled. Ensure that the Queue Manager attribute DEADQ is set up correctly. Resend the SOAP message.

AMQ9922
Maximum wait time exceeded on queue <insert_3>.
Severity:

30 : Severe error

Explanation:

The maximum time waiting for a message to arrive on queue <insert_3> has been exceeded.

Response:

Ensure that the queue is not put inhibited. Ensure that messages are being written to the queue.

AMQ9923
Insufficient parameters on command.
Severity:

30 : Severe error

Explanation:

The SOAP command has been issued with insufficient paramaters.

Response:

Supply the correct number of parameters and reissue the command.

AMQ9924
Usage: amqwSOAPNETListener -u wmqUri
[-w WebServiceDirectory] [-n MaxThreads]
[-d StayAlive] [-i IdContext]
[-x TransactionalControl] [-a Integrity] [-? ThisHelp]
Severity:

0 : Information

Explanation:

This shows the correct usage.

Response:

None.

AMQ9925
Cannot connect to queue manager <insert_3>.
Severity:

30 : Severe error

Explanation:

A SOAP application or the SOAP listener cannot connect to the queue manager <insert_3> using <insert_4> bindings.

Response:

Ensure the bindings are set to the correct value and that the queue manager exists. Check any error messages from the Java MQQueueManager class.

AMQ9926
Null SOAP action specified in a received SOAP message.
Severity:

30 : Severe error

Explanation:

A NULL soap action has been specified in the SOAP message <insert_3>. The message will not be processed.

Response:

Include the appropriate SOAP action in the SOAP message.

AMQ9927
MQ queue backout threshold exceeded.
Severity:

30 : Severe error

Explanation:

The WebSphere MQ backout threshold value has been exceeded for queue <insert_3>, processing message <insert_4>.

Response:

Correct the backout threshold value for queue <insert_3> and resend the SOAP message.

AMQ9928
Target service or URI is missing from a SOAP message.
Severity:

30 : Severe error

Explanation:

The target service or the target URI is missing from SOAP message <insert_3>.

Response:

Supply a target service or the target URI in the SOAP message.

AMQ9929
Message backout for message (<insert_3>) failed.
Severity:

30 : Severe error

Explanation:

Backout for a message has failed.

Response:

Investigate the reason for the backout failure.

AMQ9930
Required Option <insert_3> missing from command.
Severity:

30 : Severe error

Explanation:

The SOAP command was issued with manadatory option <insert_3> missing.

Response:

Reissue the SOAP command supplying the missing option.

AMQ9931
Invalid value <insert_3> specified for option <insert_4>.
Severity:

30 : Severe error

Explanation:

THE SOAP command was issued with an invalid value for an option.

Response:

Reissue the SOAP command supplying the correct option value.

AMQ9932
Application host class not found
Severity:

30 : Severe error

Explanation:

Application host class <insert_3> has not been found.

Response:

Specify the correct application host class in the SOAP message.

AMQ9933
Options <insert_3> and <insert_4> are mutually exclusive
Severity:

30 : Severe error

Explanation:

The SOAP command was issued with incompatible options <insert_3> and <insert_4>.

Response:

Reissue the SOAP command supplying compatible options.

AMQ9934
Could not parse URL <insert_3>. MQCC_FAILED(2) MQRC_SOAP_URL_ERROR(2212).
Severity:

30 : Severe error

Explanation:

.Could not parse URL <insert_3>.MQCC_FAILED(2) MQRC_SOAP_URL_ERROR(2212).

Response:

Correct the URL and retry.

AMQ9935
Illegal URL <insert_3>. MQCC_FAILED(2) MQRC_SOAP_URL_ERROR(2212).
Severity:

30 : Severe error

Explanation:

.The URL <insert_3> failed validation.. MQCC_FAILED(2) MQRC_SOAP_URL_ERROR(2212).

Response:

Correct the URL and retry.

AMQ9936
Cannot get connection using <insert_3> bindings. MQCC_FAILED(2) MQRC_CONNECTION_ERROR(2273).
Severity:

30 : Severe error

Explanation:

.Cannot get connection using <insert_3> bindings. MQCC_FAILED(2) MQRC_CONNECTION_ERROR(2273).

Response:

Check that the queue manager is available and running.

AMQ9937
The asyncResult is null. MQCC_FAILED(2) MQRC_SOAP_DOTNET_ERROR.(2210).
Severity:

30 : Severe error

Explanation:

.The asyncResult is null. MQCC_FAILED(2) MQRC_SOAP_DOTNET_ERROR.(2210).

Response:

Check why the SOAP responses are not being received.

AMQ9938
SOAP/WMQ Timeout.
Severity:

30 : Severe error

Explanation:

.The MQGET operation timed out. MQCC_FAILED(2) MQRC_SOAP_DOTNET_ERROR.(2210).

Response:

Check why the SOAP responses are not being received. MQCC_FAILED(2) MQRC_SOAP_DOTNET_ERROR.(2210).

AMQ9939
SOAP/WMQ Error. MQCC_FAILED(2) MQRC_SOAP_DOTNET_ERROR.(2210).
Severity:

30 : Severe error

Explanation:

.A SOAP error was detected. MQCC_FAILED(2) MQRC_SOAP_DOTNET_ERROR.(2210).

Response:

Check the WMQ logs for the reason of the failure.

AMQ9940
Report message returned in MQWebResponse. MQCC_FAILED(2) MQRC_SOAP_DOTNET_ERROR.(2210).
Severity:

30 : Severe error

Explanation:

.Report message returned in MQWebResponse. MQCC_FAILED(2) MQRC_SOAP_DOTNET_ERROR.(2210).

Response:

Check the report message for the reason of the failure.

AMQ9941
No RFH2 header recognised. MQCC_FAILED(2) MQRCCF_MD_FORMAT_ERROR(3023).
Severity:

30 : Severe error

Explanation:

.No RFH2 header recognised. MQCC_FAILED(2) MQRCCF_MD_FORMAT_ERROR(3023).

Response:

Check why the message is being sent with no RFH2 header.

AMQ9942
Message format is not MQFMT_NONE. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421).
Severity:

30 : Severe error

Explanation:

.Message format is not MQFMT_NONE. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421).

Response:

Correct the message format and retry.

AMQ9943
Unrecognised RFH2 version. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421).
Severity:

30 : Severe error

Explanation:

.Unrecognised RFH2 version. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421).

Response:

Correct the version in the RFH2 message and retry.

AMQ9944
Invalid RFH2 length. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421).
Severity:

30 : Severe error

Explanation:

.Invalid RFH2 length. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421).

Response:

Correct the RFH2 length and retry.

AMQ9945
Illegal RFH2 <insert_3> folder length. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421).
Severity:

30 : Severe error

Explanation:

.Illegal RFH2 <insert_3> folder length. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421).

Response:

Correct the RFH2 message and retry.

AMQ9946
Invalid actual message length. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421).
Severity:

30 : Severe error

Explanation:

.Invalid actual message length. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421).

Response:

Correct the RFH2 message and retry.

AMQ9947
Illegal RFH2 Folder <insert_3> <insert_4>. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421).
Severity:

30 : Severe error

Explanation:

.Illegal RFH2 Folder <insert_3> <insert_4>. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421).

Response:

Correct the RFH2 folder syntax/format and retry.

AMQ9948
Backout Threshold exceeded. MQCC_FAILED(2) MQRC_BACKOUT_THRESHOLD_REACHED(2362).
Severity:

30 : Severe error

Explanation:

.Backout Threshold exceeded. MQCC_FAILED(2) MQRC_BACKOUT_THRESHOLD_REACHED(2362).

Response:

Correct the backout threshold limit and retry.

AMQ9949
<insert_3> missing from RFH2. MQCC_FAILED(2) MQRC_RFH_PARM_MISSING(2339).
Severity:

30 : Severe error

Explanation:

.<insert_3> missing from RFH2. MQCC_FAILED(2) MQRC_RFH_PARM_MISSING(2339).

Response:

Correct the RFH2 message and retry.

AMQ9950
Target service missing from SOAP URL. MQCC_FAILED(2) MQRC_SOAP_URL_ERROR(2212).
Severity:

30 : Severe error

Explanation:

.Target service missing from SOAP URL. MQCC_FAILED(2) MQRC_SOAP_URL_ERROR(2212).

Response:

Correct the URL and retry.

AMQ9951
Asynchronous request queued successfully. MQCC_OK(0).
Severity:

30 : Severe error

Explanation:

.Asynchronous request queued successfully. MQCC_OK(0).

Response:

Wait for response if any is expected.

AMQ9952
Unexpected message type received. MQCC_FAILED(2) MQRC_UNEXPECTED_MSG_TYPE.(2215).
Severity:

30 : Severe error

Explanation:

.A message of the wrong type was received; for instance, a report message was received when one had not been requested.

Response:

If you are running WMQ SOAP using the IBM supplied SOAP/WMQ sender, please contact IBM. If you are running WMQ SOAP using a bespoke sender, please check that the SOAP/WMQ request message has the correct options.

AMQ9953
Either the ContentType or the TransportVin the RFH2 header have the wrong value. MQCC_FAILED(2) MQRC_RFH_HEADER_FIELD_ERROR(2228)
Severity:

30 : Severe error

Explanation:

.Either the ContentType or the TransportVin the RFH2 header have the wrong value. MQCC_FAILED(2) MQRC_RFH_HEADER_FIELD_ERROR(2228)

Response:

Correct the message format and retry.

AMQ9954
ViaTran.Redirect called out of transaction MQCC_FAILED(2) MQRC_SOAP_DOTNET_ERROR(2410)
Severity:

30 : Severe error

Explanation:

.ViaTran.Redirect called out of transaction MQCC_FAILED(2) MQRC_SOAP_DOTNET_ERROR(2410)

Response:

Make sure ViaTran.Redirect is only called in a transaction.

AMQ9955
Usage: amqswsdl [?] Uri inputFile outputFile
Severity:

0 : Information

Explanation:

This shows the correct usage.

Response:

None.

AMQ9990 (iSeries)
Keyword <insert_3> not valid for this command or the command is incomplete.
Severity:

40 : Stop Error

Explanation:

The command is incomplete, or an invalid keyword was specified, or the parameter value of the keyword was not specified.

Response:

Complete the command, or correct the keyword, or add the parameter value, and then try the command again.

AMQ9991 (iSeries)
The value specified is not allowed by the command.
Severity:

40 : Stop Error

Explanation:

<insert_3> not valid for parameter <insert_4>.

Response:

Enter one of the values that is defined for the parameter, and try the command again. More information on parameters and commands can be found in the CL reference manual or the appropriate licensed program manual.

AMQ9992 (iSeries)
A matching parenthesis not found.
Severity:

40 : Stop Error

Explanation:

A matching left or right parenthesis is missing.

Response:

Add the missing parenthesis or remove the extra parenthesis.

AMQ9999
Channel program ended abnormally.
Severity:

30 : Severe error

Explanation:

Channel program <insert_3> ended abnormally.

Response:

Look at previous error messages for channel program <insert_3> in the error files to determine the cause of the failure.