See Reading a message for an explanation of how to interpret these messages.
0 : Information
Channel <insert_3> ended normally.
None.
0 : Information
Channel <insert_3> is starting.
None.
0 : Information
Channel <insert_3> last message sequence number is <insert_1>.
None.
0 : Information
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>
None.
30 : Severe error
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.
Investigate why the user exit program set a response code that is not valid.
30 : Severe error
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.
Investigate why the user exit program set a secondary response code that is not valid.
30 : Severe error
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.
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.
30 : Severe error
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.
Investigate why the user exit program set an exit space value that is not valid. Correct the error.
30 : Severe error
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.
Investigate why the send exit programs set exit space values that are too large. Correct the error.
30 : Severe error
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.
Investigate why the user exit program specified a header compression value that was not one of the negotiated supported values.
30 : Severe error
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.
Investigate why the user exit program specified a message compression value that was not one of the negotiated supported values.
30 : Severe error
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.
Investigate why the user exit program set a data length that is not valid.
30 : Severe error
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.
Investigate why the user exit program set values that are not valid.
30 : Severe error
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.
Investigate why the user exit program set a data length that is not valid. Correct the error.
30 : Severe error
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.
Investigate why the user exit program set a data length that is not valid. Correct the error.
30 : Severe error
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.
Investigate why the user exit program set a data length that is not valid.
30 : Severe error
The attempt to allocate a conversation using <insert_4> to host <insert_3> was not successful.
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.
30 : Severe error
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.
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.
30 : Severe error
Error in configuration for communications to host <insert_3>. Allocation of a <insert_4> conversation to host <insert_3> was not possible.
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.
30 : Severe error
Connection to host <insert_3> over <insert_4> was rejected.
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.
30 : Severe error
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.
Check the <insert_4> configuration on your host.
30 : Severe error
An error occurred sending data over <insert_4> to <insert_3>. This may be due to a communications failure.
The return code from the <insert_4><insert_5> call was <insert_1> X(<insert_2>). Record these values and tell your systems administrator.
30 : Severe error
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.
Tell the systems administrator.
30 : Severe error
An error occurred receiving data from <insert_3> over <insert_4>. This may be due to a communications failure.
The return code from the <insert_4><insert_5> call was <insert_1> (X<insert_2>). Record these values and tell the systems administrator.
30 : Severe error
An error occurred receiving data from <insert_3> over <insert_4>. The connection to the remote host has unexpectedly terminated.
Tell the systems administrator.
30 : Severe error
There was an incoming attachment from a remote host, but the local host could not complete the bind.
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.
30 : Severe error
The program was unable to obtain enough storage.
Stop some programs which are using storage and retry the operation. If the problem persists contact your systems administrator.
30 : Severe error
A TCP/IP socket could not be created, possibly because of a storage problem.
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.
30 : Severe error
An unexpected error occurred in communications.
The return code from the <insert_4><insert_5> call was <insert_1> (X<insert_2>). Record these values and tell the systems administrator.
30 : Severe error
An attempt was made to use an unsupported communications protocol type <insert_2>.
Check the channel definition file. It may be that the communications protocol entered is not a currently supported one.
30 : Severe error
An attempt was made to use the communications subsystem, but it has not been started.
Start the communications subsystem, and rerun the program.
20 : Error
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.
Correct the parameters passed to the channel program and retry the operation.
20 : Error
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.
Correct the parameters passed to the channel program and retry the operation.
20 : Error
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.
Correct the parameters passed to the channel program and retry the operation.
30 : Severe error
An attempt was made to start a new instance of the listener program, but the program was rejected.
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).
30 : Severe error
An attempt to bind the <insert_4> socket to the listener port was unsuccessful.
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.
30 : Severe error
An attempt was made to create a new socket because an attach request was received, but an error occurred.
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.
30 : Severe error
The attempt to load the <insert_4> library or procedure <insert_3> failed with error code <insert_1>.
Either the library must be installed on the system or the environment changed to allow the program to locate it.
30 : Severe error
The specified value of <insert_3> was not recognized as one of the protocols supported.
Correct the parameter and retry the operation.
10 : Warning
The configuration file <insert_3> cannot be found. This file contains default definitions for communication parameters. Default values will be used.
None.
30 : Severe error
The operation you are performing requires that you enter the type of protocol.
Add the protocol parameter and retry the operation.
30 : Severe error
On line <insert_1> of the INI file, keyword <insert_3> was read when a keyword was expected.
Correct the file and retry the operation.
30 : Severe error
Keyword <insert_3> was read when a keyword was expected.
Correct the configuration data and retry the operation.
30 : Severe error
A syntax error was detected on line <insert_1> while processing the INI file.
Correct the problem and retry the operation.
30 : Severe error
A syntax error was detected while processing the configuration data.
Correct the problem and retry the operation.
10 : Warning
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.
Correct the parameters passed to the listener program and retry the operation.
10 : Warning
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.
Correct the parameters passed to the listener program and retry the operation.
10 : Warning
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.
Correct the parameters passed to the listener program and retry the operation.
30 : Severe error
A name is required for the <insert_3> process to register with the network.
Add a local name to the configuration file and retry the operation.
30 : Severe error
An attempt was made to start an instance of the responder program, but the program was rejected.
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>.
30 : Severe error
You have issued a request to end the application.
None.
30 : Severe error
During the processing of network events, an unexpected event <insert_1> occurred.
None.
30 : Severe error
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.
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.
30 : Severe error
The operation requires the specification of the <insert_3> field.
Specify the <insert_3> and retry the operation.
30 : Severe error
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>.
Contact the systems administrator. If the problem persists contact your IBM support center.
30 : Severe error
The local communications address (LOCLADDR) value <insert_3> cannot be resolved into an IP address.
Enter a local communications address value which can be resolved into an IP address, and try again.
30 : Severe error
The <insert_4> Partner LU name <insert_3> was invalid.
Either the Partner LU name was entered incorrectly or it was not in the <insert_4> communications configuration. Correct the error and try again.
30 : Severe error
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>.
Record the error values and tell the system administrator.
30 : Severe error
An unexpected error occurred in communications.
The return code from the <insert_4><insert_3> call was <insert_1> with associated <insert_5> <insert_2>.
10 : Warning
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
Correct the parameters passed to the listener program and retry the operation.
30 : Severe error
The Listener received return code <insert_1> when attempting to open socket <insert_2>.
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.
30 : Severe error
The Listener received return code <insert_1> when attempting to open socket <insert_2>.
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.
30 : Severe error
The listener received return code <insert_1> when attempting to open socket <insert_2>.
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.
30 : Severe error
WebSphere MQ received return code <insert_1> when attempting to start SPX communications.
Ensure that IPX/SPX support is installed on the machine and that it is started before trying to start a WebSphere MQ SPX channel.
30 : Severe error
WebSphere MQ received return code <insert_1> when attempting to start SPX communications, indicating a resource problem.
Ensure that sufficient IPX/SPX resources are available before commencing communications over IPX/SPX.
30 : Severe error
You tried to perform an action against a queue manager that does not exist. You may have specified the wrong queue manager name.
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.
30 : Severe error
You tried to perform an action against a queue manager that does not exist.
Create the default queue manager and submit the command again.
10 : Warning
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.
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.
30 : Severe error
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.
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.
30 : Severe error
Channel <insert_3> has been closed because the SSPI channel exit received a bad return code from SSPI.
Consult the appropriate SSPI manuals to find out the meaning of status <insert_4> on call <insert_5>, and correct the error.
30 : Severe error
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.
Contact the system administrator. If the problem persists contact your IBM support center.
30 : Severe error
The request to start the WebSphere MQ listener failed because there is already a listener running against the specified network resources.
None.
30 : Severe error
A connection from host <insert_3> over <insert_4> timed out.
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.
0 : Information
Channel <insert_3> which did not previously exist has been autodefined.
None.
30 : Severe error
Autodefinition of Channel <insert_3> failed because <insert_4> would not load.
Ensure that the user exit is specified correctly in the queue manager definition, and that the user exit program is correct and available.
30 : Severe error
Autodefinition exit <insert_4> for Channel <insert_3> returned a failure code.
None.
0 : Information
The queue manager successfully processed a REFRESH CLUSTER command with the REPOS(YES) option for the indicated cluster.
None.
0 : Information
The repository queue manager successfully processed a RESET ACTION(FORCEREMOVE) command with the QUEUES(YES) option for the indicated cluster and target queue manager.
None.
30 : Severe error
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.
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.
10 : Warning
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.
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.
0 : Information
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.
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.
30 : Severe error
The repository manager ended abnormally.
Look at previous error messages for the repository manager in the error files to determine the cause of the failure.
0 : Information
The repository manager started successfully.
None.
0 : Information
The repository manager ended normally.
None.
30 : Severe error
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>.
Check the channel and cluster definitions of the sending queue manager.
30 : Severe error
An internal error has occurred.
Collect the items listed in the 'Problem determination' section of the System Administration manual and contact your IBM support center.
30 : Severe error
An internal error has occurred.
Collect the items listed in the 'Problem determination' section of the System Administration manual and contact your IBM support center.
30 : Severe error
Repository command unexpected, command code <insert_1>, cluster object <insert_3>, sender <insert_4>
Collect the items listed in the 'Problem determination' section of the System Administration manual and contact your IBM support center.
30 : Severe error
An internal error has occurred.
Collect the items listed in the 'Problem determination' section of the System Administration manual and contact your IBM support center.
30 : Severe error
Repository command processing error, RC=<insert_2>, command code <insert_1>, cluster object <insert_3>, sender <insert_4>.
Collect the items listed in the 'Problem determination' section of the System Administration manual and contact your IBM support center.
0 : Information
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.
Delete the manually defined CLUSSDR channels to <insert_3>.
0 : Information
The queue manager has received information about a cluster for which it is the only repository.
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.
0 : Information
The repository manager has received information about a cluster for which no cluster-receiver channels are known.
Define cluster-receiver channels for the cluster on the local queue manager.
0 : Information
The queue manager has received information about a cluster for which no repositories are known.
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.
30 : Severe error
An invalid record was read from the SYSTEM.CLUSTER.REPOSITORY.QUEUE. An FFST record has been generated containing the invalid record. was
Collect the items listed in the Problem Determination section of the System Administration manual and contact your IBM support center.
30 : Severe error
An internal error has occurred.
Collect the items listed in the 'Problem determination' section of the System Administration manual and contact your IBM support center.
30 : Severe error
Repository command merge error, command code <insert_1>, cluster object <insert_3>, sender <insert_4>
Collect the items listed in the 'Problem determination' section of the System Administration manual and contact your IBM support center.
30 : Severe error
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>.
Check the channel and cluster definitions of the sending and receiving queue managers.
30 : Severe error
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>.
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.
30 : Severe error
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>.
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.
30 : Severe error
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>.
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.
30 : Severe error
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.
Check the CLUSSDR definition on the sending queue manager to ensure that it points to a repository queue manager for the cluster.
0 : Information
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.
None.
30 : Severe error
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>.
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.
30 : Severe error
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>.
Alter the CLUSRCVR or CLUSSDR definitions for channel <insert_3>, so that they are both members of the same cluster.
30 : Severe error
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.
Examine the message on the dead-letter queue to determine the originator of the message.
30 : Severe error
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.
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.
30 : Severe error
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.
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.
30 : Severe error
The repository manager tried to commit some updates to the repository but was unsuccessful. Processing continues, but repository information may be out of date.
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.
30 : Severe error
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>.
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.
30 : Severe error
An internal error has occurred.
Collect the items listed in the 'Problem determination' chapter in the System Administration guide and contact your IBM support center.
0 : Information
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.
None.
0 : Information
The reset Cluster(<insert_3>) Qmname(<insert_4>) command has processed on this repository and <insert_1> other queue managers have been sent notification.
None.
0 : Information
The Refresh Cluster(<insert_4>) command caused <insert_1> objects to be refreshed and <insert_2> objects to be republished.
None.
0 : Information
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.
None.
0 : Information
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.
None.
30 : Severe error
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.
Rectify the problem which prevented successful creation of channel <insert_3>. Restart channel <insert_4>.
30 : Severe error
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>".
If channel <insert_3> still exists rectify the problem which prevented its deletion and then manually delete the channel.
30 : Severe error
Following an error, the repository manager tried to backout some updates to the repository, but was unsuccessful. The repository manager terminates.
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.
30 : Severe error
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.
Correct the problem reported in the preceding messages.
0 : Information
The repository manager restarted successfully following an error.
None.
10 : Warning
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 OutputFileVersion can be either 2 or 5 (5 is the default)
Default values will be used for parameters not supplied.
Correct the parameters passed to the channel table writer program and retry the operation.
0 : Information
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.
Reissue the command specifying the identifier (QMID) of the queue manager to be removed, rather than its name.
0 : Information
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.
Reissue the command, specifying the correct queue manager name or identifier.
0 : Information
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.
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.
0 : Information
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.
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.
0 : Information
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.
None.
20 : Error
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.
Check the definition of the Transmission Queue <insert_3> on queue manager <insert_5> and set it to be SHARE instead of NOSHARE. Alternatively, you can set all channels on this queue manager to use only a single thread, by using the PipeLineLength parameter.
30 : Severe error
The responder program was started but detected an error.
Look at previous error messages in the error files to determine the error encountered by the responder program.
30 : Severe error
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>.
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.
30 : Severe error
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.
None.
30 : Severe error
Channel program <insert_3> was ended because the channel exit at the remote end requested it.
Examine the error logs at the remote end of the channel to see the reason why the remote exit ended the channel.
30 : Severe error
The value of the <insert_3> field has the value <insert_4>. This value is invalid for the operation requested.
Change the parameter and retry the operation.
0 : Information
One listener detected in the system is scheduled for shutdown.
None.
10 : Warning
An operation failed because there was no storage available in the repository. An attempt was made to allocate <insert_1> bytes from <insert_3>.
Reconfigure the Queue Manager to allocate a larger repository.
10 : Warning
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.
Correct the parameters passed to the Channel program and retry the operation.
30 : Severe error
The operation requested cannot be performed on channel <insert_3>. Some operations are only valid for certain channel types. For example, you can only ping a channel from the end sending the message.
Check whether the channel name is specified correctly. If it is check that the channel has been defined correctly.
30 : Severe error
Channel <insert_3> between this machine and the remote machine could not be established due to a negotiation failure.
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.
30 : Severe error
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>.
Contact the systems administrator who should examine the error logs to determine the cause of the failure.
30 : Severe error
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.
Change either the local or remote channel definitions so that the values specified for the message sequence number wrap values are the same.
30 : Severe error
Channel <insert_3> has ended because the remote queue manager did not accept the last batch of messages.
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.
30 : Severe error
The requested operation cannot complete because the channel is in-doubt with host <insert_4>.
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.
30 : Severe error
The connection attempt to queue manager <insert_4> failed with reason code <insert_1>.
Ensure that the queue manager is available and operational.
30 : Severe error
The attempt to open either the queue or queue manager object <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.
Ensure that the queue is available and retry the operation.
30 : Severe error
The attempt to get messages from queue <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.
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.
30 : Severe error
The attempt to put messages to queue <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.
Ensure that the required queue is available and operational.
30 : Severe error
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.
If the local channel is a receiver channel, you must issue the ping from the remote queue manager.
30 : Severe error
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.
Wait for some of the operating channels to close. Retry the operation when some channels are available.
30 : Severe error
The requested operation failed because channel <insert_3> is currently active.
Either end the channel manually, or wait for it to close, and retry the operation.
10 : Warning
The statistics shown are for the channel requested, but it is a new instance of the channel. The previous channel instance has ended.
None.
30 : Severe error
The filesystem returned error code <insert_1> for file <insert_3>.
Record the name of the file <insert_3> and tell the systems administrator, who should ensure that file <insert_3> is correct and available.
30 : Severe error
The filesystem returned error code <insert_4> for file <insert_3>.
Record the name of the file <insert_3> and tell the systems administrator, who should ensure that file <insert_3> is correct and available.
30 : Severe error
The program has detected damage to the contents of file <insert_3>.
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>.
30 : Severe error
The program requires that the file <insert_3> is present and available.
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.
30 : Severe error
The requested operation failed because the program could not find a definition of channel <insert_3>.
Check that the name is specified correctly and the channel definition is available.
30 : Severe error
There is no definition of channel <insert_3> at the remote location.
Add an appropriate definition to the remote hosts list of defined channels and retry the operation.
30 : Severe error
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.
Update the channel definition, or remove the explicit mention of the remote machine connection name.
30 : Severe error
The program could not access the channel status table.
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.
30 : Severe error
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>.
Tell the systems administrator, who should examine the error files to determine the cause of the failure.
30 : Severe error
Channel <insert_3> cannot start because the remote queue manager is not currently available.
Either start the remote queue manager, or retry the operation later.
30 : Severe error
Channel <insert_3> is closing because the remote queue manager is ending.
None.
30 : Severe error
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.
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.
30 : Severe error
The channel has closed because the remote queue manager cannot receive a message.
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.
10 : Warning
The channel is closing because of a request by the user.
None.
30 : Severe error
Communication using channel <insert_3> has ended because the target queue for a message is unknown at the remote host.
Ensure that the remote host contains a correctly defined target queue, and restart the channel.
30 : Severe error
The attempt to inquire the attributes of queue <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.
Ensure that the queue is available and retry the operation.
30 : Severe error
Queue <insert_4> identified as a transmission queue in the channel definition <insert_3> is not a transmission queue.
Ensure that the queue name is specified correctly. If so, alter the queue usage parameter of the queue to that of a transmission queue.
30 : Severe error
The attempt to set the attributes of queue <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.
Ensure that the queue is available and retry the operation.
10 : Warning
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.
None.
30 : Severe error
The channel program ended because the channel is currently not enabled.
Issue the START CHANNEL command to re-enable the channel.
30 : Severe error
Channel program <insert_3> ended because user exit <insert_4> is not valid.
Ensure that the user exit is specified correctly in the channel definition, and that the user exit program is correct and available.
30 : Severe error
Channel program <insert_3> was ended by exit <insert_4>.
None.
10 : Warning
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.
Correct the parameters passed to the program and retry the operation.
30 : Severe error
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.
Refer to the error log for other messages pertaining to this problem.
30 : Severe error
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.
Ensure that there is a defined channel, which is enabled, to process the transmission queue.
30 : Severe error
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>.
Tell the systems administrator.
30 : Severe error
The program ended because, either the source CCSID <insert_1> or the target CCSID <insert_2> is not valid, or is not currently supported.
Correct the CCSID that is not valid, or ensure that the requested CCSID can be supported.
10 : Warning
The program will end because the queue manager is quiescing.
None.
30 : Severe error
The channel status table has been damaged.
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.
10 : Warning
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.
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>.
0 : Information
Channel <insert_3> closed because no messages arrived on the transmission queue within the disconnect interval period.
None.
30 : Severe error
The program has ended because return code <insert_1> was returned from function <insert_3>
Correct the cause of the failure and retry the operation.
30 : Severe error
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.
Check that the channel name is specified correctly. If it is, check that the remote channel has been defined correctly.
10 : Warning
During processing a message has been put to the dead-letter queue.
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.
20 : Error
An MQGET failed because the transmission queue had been previously inhibited for MQGET.
None.
30 : Severe error
The channel program can not be terminated immediately but should end shortly.
If the channel does not end in a short time issue the STOP CHANNEL command again.
30 : Severe error
The operation you are performing over Channel <insert_3> to the host at <insert_4> is not supported by the target host.
Check that the connection name parameter is specified correctly and that the levels of the products in use are compatible.
30 : Severe error
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.
Tell the systems administrator who should ensure that the security exit on the remote machine is defined correctly.
30 : Severe error
The <insert_3> function <insert_4> attempted is not currently supported on this platform.
None.
30 : Severe error
You are not authorized to perform the Channel operation.
Tell the systems administrator who should ensure that the correct access permissions are available to you, and then retry the operation.
30 : Severe error
The file <insert_3> does not have the expected format.
Ensure that the file name is specified correctly.
30 : Severe error
The channel synchronization file <insert_3> is missing or does not correspond to the stored channel information for queue manager <insert_4>.
Rebuild the synchronization file using the rcrmqmobj command rcrmqmobj -t syncfile (-m q-mgr-name)
30 : Severe error
The channel synchronization file <insert_3> is missing or does not correspond to the stored channel information for queue manager <insert_4>.
Rebuild the synchronization file using the RCRMQMOBJ command.
30 : Severe error
The call to initialize the User ID failed with CompCode <insert_1> and Reason <insert_2>.
Correct the error and try again.
30 : Severe error
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.
Check the remote system to ensure that the channel is available to run, and retry the operation.
0 : Information
Rebuilding the Synchronization file for Queue Manager <insert_3> .
None.
0 : Information
Rebuild Synchronization File program completed normally.
None.
30 : Severe error
The Synchronization file <insert_3> is in use and cannot be recreated.
Stop any channel activity and retry the rcrmqmobj command.
30 : Severe error
The Synchronization file <insert_3> is in use and cannot be recreated.
Stop any channel activity and retry the RCRMQMOBJ command.
30 : Severe error
The filesystem returned error code <insert_1> for file <insert_3>.
Tell the systems administrator who should ensure that file <insert_3> is available and not in use.
30 : Severe error
The filesystem returned error code <insert_1> for file <insert_3>.
Tell the systems administrator.
30 : Severe error
The queue manager <insert_4> does not have a defined dead-letter queue.
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.
30 : Severe error
The value of the MQSERVER environment variable was <insert_3>. The variable should be in the format 'ChannelName/Protocol/ConnectionName'.
Correct the MQSERVER value and retry the operation.
30 : Severe error
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.
Correct the problem that caused the message to have a header that is not valid.
30 : Severe error
There are too many channels active to start another. The current defined maximum number of active channels is <insert_1>.
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.
30 : Severe error
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.
30 : Severe error
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.
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.
30 : Severe error
A DCE exit was unsuccessful in obtaining the memory it needed. The failure occurred in exit function <insert_4>. Channel <insert_3> is closed.
Make more memory available to the WebSphere MQ system and restart the relevant channel.
30 : Severe error
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.
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.
30 : Severe error
Channel <insert_3> has been closed because one of the DCE channel exits received a bad return code from DCE.
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>.
30 : Severe error
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.
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.
30 : Severe error
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>.
Make sure that the exits at both ends of the channel generate compatible flows.
30 : Severe error
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>.
Alter the exit definitions to ensure that exit <insert_4> is called correctly.
30 : Severe error
Exit <insert_4> on channel <insert_3> was called with an invalid ExitReason (value <insert_1>).
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.
30 : Severe error
The DCE_SEC_SRM_CHANNELEXIT exit was called on channel <insert_3>; the value of pContext->mechanism (<insert_1>) passed was not valid.
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.
30 : Severe error
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>.
Configure the system so that compatible send/receive/message exits are run at both ends of the channel.
30 : Severe error
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.
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.
30 : Severe error
The attempt to create object <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.
Use the standard facilities supplied with your system to record the problem identifier. Contact your IBM support center.
30 : Severe error
The attempt to open object <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.
Use the standard facilities supplied with your system to record the problem identifier. Contact your IBM support center.
30 : Severe error
The attempt to update object <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.
Use the standard facilities supplied with your system to record the problem identifier. Contact your IBM support center.
30 : Severe error
The attempt to query object <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.
Use the standard facilities supplied with your system to record the problem identifier. Contact your IBM support center.
30 : Severe error
The attempt to close object <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.
Use the standard facilities supplied with your system to record the problem identifier. Contact your IBM support center.
30 : Severe error
The attempt to prepare object <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.
Use the standard facilities supplied with your system to record the problem identifier. Contact your IBM support center.
30 : Severe error
The attempt to resolve object <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.
Use the standard facilities supplied with your system to record the problem identifier. Contact your IBM support center.
30 : Severe error
The attempt to delete object <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.
Use the standard facilities supplied with your system to record the problem identifier. Contact your IBM support center.
0 : Information
Syntax for the usage of runmqfmt.
None.
10 : Warning
The correct usage is shown.
Correct the parameters passed to the endmqlsr program and retry the operation.
30 : Severe error
The requested operation can not complete because queue manager <insert_3> is still running.
End the queue manager and retry the operation.
0 : Information
No listener processes were found in the system for Queue Manager <insert_3>.
None.
0 : Information
<insert_1> listeners detected in the system are scheduled for shutdown.
None.
30 : Severe error
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>.
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.
30 : Severe error
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.
Correct the error. When the repository process restarts it processes the backed out command again and continues.
30 : Severe error
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.
Wait for some of the operating channels to close. Retry the operation when some channels are available.
30 : Severe error
The program could not access the process pool shared segment
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.
30 : Severe error
The process or thread executing channel <insert_3> is no longer running. The check process system call returned <insert_1> for process <insert_2>.
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.
0 : Information
<insert_1> listeners detected in the system have been ended.
None.
0 : Information
One listener detected in the system has been ended.
None.
30 : Severe error
Channel <insert_3> could not establish a successful connection with the remote Queue Manager because resources are being recovered.
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.
0 : Information
<insert_2> messages of type AMQ<insert_1> were suppressed
Message suppression is controlled by MQ_CHANNEL_SUPPRESS_MSGS and MQ_CHANNEL_SUPPRESS_INTERVAL environment variables.
0 : Information
Rebuild Client Channel Table program completed normally.
None.
0 : Information
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.
Active channels may be stopped using the 'STOP CHANNEL' command or by ending the Queue Manager, and reissuing the end-listener request.
0 : Information
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.
Use Digital Certificate Manager to add the required Certificate Authority (CA) certificates to the application definitions CA trust list.
0 : Information
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.
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.
30 : Severe error
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.
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.
30 : Severe error
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".
Set the value specified for the MQSSLFIPS environment variable, or in the MQSCO FipsRequired field, to "YES" or "NO". Restart the channel.
30 : Severe error
An SSL channel has failed to start because the SSLCRLNL queue manager attribute points to a namelist with an empty list of names.
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.
30 : Severe error
On HP-UX, SSL cannot be run from a WebSphere MQ client which was linked with the unthreaded client libraries.
Either relink your client application with the threaded client libraries, or do not attempt to use SSL from this application.
30 : Severe error
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.
Collect the items listed in the 'Problem determination' section of the System Administration manual and contact your IBM support center.
0 : Information
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.
Collect the items listed in the 'Problem determination' section of the System Administration manual and contact your IBM support center.
10 : Warning
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.
None.
30 : Severe error
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.
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.
30 : Severe error
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>.
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.
30 : Severe error
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>.
Only include CRLLDAP AUTHINFO objects in the namelist specified on the SSLCRLNL queue manager attribute. Restart the channel or channel process.
30 : Severe error
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>.
Correct the invalid parameter. Restart the channel or channel process.
30 : Severe error
The current channel cannot start because another channel is hanging while initializing the SSL subsystem.
Investigate the reason for the hang on the other channel. Once this is rectified, restart this channel.
30 : Severe error
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.
Use the MQSSLKEYR environment variable or MQCONNX API call to specify the directory path and file stem name for the SSL key repository.
30 : Severe error
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>.
Correct the invalid parameter. If the LDAP details were defined on a queue manager system, regenerate the client definitions. Reconnect.
30 : Severe error
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.
Correct your SSL cryptographic hardware parameters and restart the channel.
30 : Severe error
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).
Ensure that the specified SSL certificate has a valid expiry date.
30 : Severe error
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.
Change the channel definitions for <insert_3> so the two ends have matching CipherSpecs and restart the channel.
30 : Severe error
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>.
Change the channel definition for <insert_3> so that both ends have matching CipherSpecs and restart the channel.
30 : Severe error
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.
Check which of the three possible causes applies on your system. Correct the error, and restart the channel.
30 : Severe error
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>.
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.
30 : Severe error
Channel <insert_3> did not specify a valid CipherSpec.
Change channel <insert_3> to specify a valid CipherSpec.
30 : Severe error
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.
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.
30 : Severe error
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.
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.
30 : Severe error
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.
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.
30 : Severe error
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.
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.
30 : Severe error
Remote channel <insert_3> did not specify a CipherSpec when the local channel expected one to be specified. The channel did not start.
Change the remote channel <insert_3> to specify a CipherSpec so that both ends of the channel have matching CipherSpecs.
30 : Severe error
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.
Correct the SSL peer name for the channel. Restart the channel.
30 : Severe error
The remote end of channel <insert_3> has had a CipherSpec error. The channel did not start.
Review the error logs on the remote system to discover the problem with the CipherSpec.
30 : Severe error
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.
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.
0 : Information
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.
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.
30 : Severe error
The remote end of channel <insert_3> has had an SSL peer name error. The channel did not start.
Review the error logs on the remote system to discover the problem with the peer name.
30 : Severe error
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.
Add a correctly labelled SSL certificate to the current key database file. Restart the channel.
30 : Severe error
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.
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.
30 : Severe error
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.
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.
30 : Severe error
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.
Recreate the SSL key repository and restart the channel.
30 : Severe error
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.
Use your key management tool to remove the duplicate keys. Restart the channel.
30 : Severe error
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.
Use your key management tool to remove the duplicate entries. Restart the channel.
30 : Severe error
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.
Use your key management tool to recreate the key repository with a new password. Restart the channel.
30 : Severe error
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.
Use your key management tool to provide MQ with a current SSL certificate on the remote end of the channel. Restart the channel.
10 : Warning
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.
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.
30 : Severe error
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.
Ensure that the remote system has a valid SSL certificate. Restart the channel.
30 : Severe error
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.
Uninstall MQ and reinstall. Restart the channel.
30 : Severe error
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.
Ensure that the remote system has a valid SSL certificate. Restart the channel.
30 : Severe error
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.
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.
30 : Severe error
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.
Ensure that both the local and remote systems have valid, current SSL certificates. Restart the channel.
30 : Severe error
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.
Refer to prior message in the WebSphere MQ error log for information related to this problem.
30 : Severe error
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.
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.
30 : Severe error
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 '????'.
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.
0 : Information
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 '????'.
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.
30 : Severe error
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.
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.
30 : Severe error
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.
Ensure that the remote system has a valid SSL certificate. Restart the channel.
30 : Severe error
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.
Check the userid information for the CRL LDAP server or servers you have configured locally. Correct any problems found and restart the channel.
30 : Severe error
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.
Check the remote end of the channel for SSL-related errors. Fix them and restart the channel.
30 : Severe error
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.
Check access to the CRL LDAP server(s) you have configured locally. Put right any problems found and restart the channel.
30 : Severe error
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.
Check the password information for the CRL LDAP server or servers you have configured locally. Correct any problems found and restart the channel.
30 : Severe error
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.
Ensure that the PKCS #11 shared library exists and is valid at the location specified. Restart the channel.
30 : Severe error
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.
Ensure that the PKCS #11 token exists with the label specified. Restart the channel.
30 : Severe error
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.
Ensure that the correct PKCS #11 card is present in the slot. Restart the channel.
30 : Severe error
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.
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.
30 : Severe error
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.
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.
30 : Severe error
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.
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.
30 : Severe error
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.
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.
30 : Severe error
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.
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.
30 : Severe error
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.
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.
30 : Severe error
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.
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.
10 : Warning
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.
30 : Severe error
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.
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.
30 : Severe error
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.
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.
30 : Severe error
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.
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.
30 : Severe error
The WebSphere MQ SSL library 'amqcssln.dll' has been called without it first being initialized by the calling process.
Ensure that the initialization function has been called prior to issuing any amqcssln function calls.
30 : Severe error
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>.
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.
30 : Severe error
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.
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.
30 : Severe error
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.
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.
30 : Severe error
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.
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.
30 : Severe error
The password supplied for importing or copying the certificate is incorrect, and the operation could not be completed.
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.
30 : Severe error
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.
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.
30 : Severe error
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.
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.
30 : Severe error
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.
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.
30 : Severe error
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.
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.
20 : Error
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.
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.
30 : Severe error
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.
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.
30 : Severe error
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.
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.
30 : Severe error
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.
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.
0 : Information
This shows the correct usage.
None.
30 : Severe error
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.
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.
30 : Severe error
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.
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.
30 : Severe error
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.
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.
30 : Severe error
The request to refresh SSL security was unsuccessful.
Look at previous error messages in the error files to determine the cause of the failure.
30 : Severe error
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.
Look at previous error messages in the error files to determine which channels could not be restarted. Restart these if necessary.
30 : Severe error
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.
Investigate why channel <insert_3> is hung. Terminate the hung channel. Rerun the SSL security refresh.
0 : Information
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.
None.
30 : Severe error
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.
Restart the channel once the SSL refresh is complete. The channel will restart automatically if it is configured to retry the connection.
30 : Severe error
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 '????'.
Ensure the GSKit SSL provider is at the latest level of maintenance and restart the channel.
30 : Severe error
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 '????'.
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.
0 : Information
None.
None.
0 : Information
None.
None.
0 : Information
None.
None.
0 : Information
None.
None.
0 : Information
None.
None.
0 : Information
None.
None.
30 : Severe error
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.
If the certificate is required for migration then obtain a valid replacement before importing it into the GSKit key database <insert_5>.
30 : Severe error
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.
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.
30 : Severe error
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.
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.
30 : Severe error
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.
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.
0 : Information
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>.
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.
0 : Information
None.
30 : Severe error
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.
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.
0 : Information
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.
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.
30 : Severe error
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.
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.
30 : Severe error
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.
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.
30 : Severe error
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.
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.
30 : Severe error
An attempt to allocate memory failed.
Make more memory available to the command.
30 : Severe error
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.
Ensure that the MQSSLKEYR environment variable is defined with an appropriate value.
30 : Severe error
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.
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.
30 : Severe error
The certificate store <insert_3> could not be opened, and failed with Windows error code <insert_1>.
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.
30 : Severe error
During operation <insert_3>, the Windows return code <insert_1> was generated.
Consult the Windows reference manual to determine the meaning of return code <insert_1> for operation <insert_3>.
30 : Severe error
During operation <insert_3>, the GSKit return code <insert_1> was generated.
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.
30 : Severe error
There was a problem trying to migrate a certificate to the GSKit key database <insert_5>.
Refer to the previous message in the error log to determine why the migration failed.
10 : Warning
There is no automatic certificate migration entry in the registry which matches the input provided.
None, if the entry to be removed was correctly specified. Otherwise, input the command again with correct parameters.
30 : Severe error
An attempt to allocate memory failed while amqtcert was migrating certificate file <insert_3>.sto'. The migration did not complete successfully.
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.
30 : Severe error
The file specified as a command argument has not been found. The characters ".sto" have been automatically appended to the file name.
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.
0 : Information
None.
30 : Severe error
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.
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.
30 : Severe error
The command syntax is incorrect because of an invalid combination of arguments.
Re-try the command using a valid combination of arguments.
30 : Severe error
The file <insert_3> cannot be created because it already exists.
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.
30 : Severe error
You tried to issue a command for which you are not authorized.
Contact your system administrator to perform the command for you or to request authority to perform the command.
30 : Severe error
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.
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>.
30 : Severe error
The file <insert_3> cannot be used because it is empty.
Ensure that the correct file has been used and if necessary investigate the reason for it being empty.
30 : Severe error
During operation <insert_3>, the GSKit return code <insert_1> was generated.
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.
0 : Information
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>.
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.
0 : Information
Provides a count of the number of certificates in the Microsoft Certificate Store <insert_3>.
None.
0 : Information
None.
None.
0 : Information
None.
None.
0 : Information
None.
None.
0 : Information
None.
None.
0 : Information
None.
None.
0 : Information
None.
None.
0 : Information
None.
None.
0 : Information
None.
None.
30 : Severe error
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.
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.
30 : Severe error
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.
Check that you have sufficient authority and that there is sufficient disk space available.
0 : Information
None.
30 : Severe error
The directory specified as a command argument has not been found.
Check that the directory exists and that it is specified as an absolute (rather than relative) directory path.
0 : Information
None.
30 : Severe error
An attempt to resolve the local address hostname to an IP address has failed.
Check that the local address hostname is correct and has an entry in the DNS database.
30 : Severe error
An attempt to use a local address that is incompatible with the IP protocol used.
Make sure that the local address specified is of the same type (IPv4 or IPV6) as the IP Protocol.
30 : Severe error
An attempt to use an IP protocol that is not present on the system has been made.
Install the required IP protocol or use an IP protocol that is available on the system.
30 : Severe error
A SOAP method encountered a problem and has thrown an exception. Details of the exception are:
<insert_3>
Investigate why the SOAP method threw the exception.
30 : Severe error
An error was encountered when an attempt was made to write a message to Dead Letter Queue <insert_3>. The message was <insert_4>.
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.
30 : Severe error
The maximum time waiting for a message to arrive on queue <insert_3> has been exceeded.
Ensure that the queue is not put inhibited. Ensure that messages are being written to the queue.
30 : Severe error
The SOAP command has been issued with insufficient paramaters.
Supply the correct number of parameters and reissue the command.
0 : Information
This shows the correct usage.
None.
30 : Severe error
A SOAP application or the SOAP listener cannot connect to the queue manager <insert_3> using <insert_4> bindings.
Ensure the bindings are set to the correct value and that the queue manager exists. Check any error messages from the Java MQQueueManager class.
30 : Severe error
A NULL soap action has been specified in the SOAP message <insert_3>. The message will not be processed.
Include the appropriate SOAP action in the SOAP message.
30 : Severe error
The WebSphere MQ backout threshold value has been exceeded for queue <insert_3>, processing message <insert_4>.
Correct the backout threshold value for queue <insert_3> and resend the SOAP message.
30 : Severe error
The target service or the target URI is missing from SOAP message <insert_3>.
Supply a target service or the target URI in the SOAP message.
30 : Severe error
Backout for a message has failed.
Investigate the reason for the backout failure.
30 : Severe error
The SOAP command was issued with manadatory option <insert_3> missing.
Reissue the SOAP command supplying the missing option.
30 : Severe error
THE SOAP command was issued with an invalid value for an option.
Reissue the SOAP command supplying the correct option value.
30 : Severe error
Application host class <insert_3> has not been found.
Specify the correct application host class in the SOAP message.
30 : Severe error
The SOAP command was issued with incompatible options <insert_3> and <insert_4>.
Reissue the SOAP command supplying compatible options.
30 : Severe error
.Could not parse URL <insert_3>.MQCC_FAILED(2) MQRC_SOAP_URL_ERROR(2212).
Correct the URL and retry.
30 : Severe error
.The URL <insert_3> failed validation.. MQCC_FAILED(2) MQRC_SOAP_URL_ERROR(2212).
Correct the URL and retry.
30 : Severe error
.Cannot get connection using <insert_3> bindings. MQCC_FAILED(2) MQRC_CONNECTION_ERROR(2273).
Check that the queue manager is available and running.
30 : Severe error
.The asyncResult is null. MQCC_FAILED(2) MQRC_SOAP_DOTNET_ERROR.(2210).
Check why the SOAP responses are not being received.
30 : Severe error
.The MQGET operation timed out. MQCC_FAILED(2) MQRC_SOAP_DOTNET_ERROR.(2210).
Check why the SOAP responses are not being received. MQCC_FAILED(2) MQRC_SOAP_DOTNET_ERROR.(2210).
30 : Severe error
.A SOAP error was detected. MQCC_FAILED(2) MQRC_SOAP_DOTNET_ERROR.(2210).
Check the WMQ logs for the reason of the failure.
30 : Severe error
.Report message returned in MQWebResponse. MQCC_FAILED(2) MQRC_SOAP_DOTNET_ERROR.(2210).
Check the report message for the reason of the failure.
30 : Severe error
.No RFH2 header recognised. MQCC_FAILED(2) MQRCCF_MD_FORMAT_ERROR(3023).
Check why the message is being sent with no RFH2 header.
30 : Severe error
.Message format is not MQFMT_NONE. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421).
Correct the message format and retry.
30 : Severe error
.Unrecognised RFH2 version. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421).
Correct the version in the RFH2 message and retry.
30 : Severe error
.Invalid RFH2 length. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421).
Correct the RFH2 length and retry.
30 : Severe error
.Illegal RFH2 <insert_3> folder length. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421).
Correct the RFH2 message and retry.
30 : Severe error
.Invalid actual message length. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421).
Correct the RFH2 message and retry.
30 : Severe error
.Illegal RFH2 Folder <insert_3> <insert_4>. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421).
Correct the RFH2 folder syntax/format and retry.
30 : Severe error
.Backout Threshold exceeded. MQCC_FAILED(2) MQRC_BACKOUT_THRESHOLD_REACHED(2362).
Correct the backout threshold limit and retry.
30 : Severe error
.<insert_3> missing from RFH2. MQCC_FAILED(2) MQRC_RFH_PARM_MISSING(2339).
Correct the RFH2 message and retry.
30 : Severe error
.Target service missing from SOAP URL. MQCC_FAILED(2) MQRC_SOAP_URL_ERROR(2212).
Correct the URL and retry.
30 : Severe error
.Asynchronous request queued successfully. MQCC_OK(0).
Wait for response if any is expected.
30 : Severe error
.A message of the wrong type was received; for instance, a report message was received when one had not been requested.
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.
30 : Severe error
.Either the ContentType or the TransportVersion in the RFH2 header have the wrong value. MQCC_FAILED(2) MQRC_RFH_HEADER_FIELD_ERROR(2228)
Correct the message format and retry.
30 : Severe error
.ViaTran.Redirect called out of transaction MQCC_FAILED(2) MQRC_SOAP_DOTNET_ERROR(2410)
Make sure ViaTran.Redirect is only called in a transaction.
0 : Information
This shows the correct usage.
None.
40 : Stop Error
The command is incomplete, or an invalid keyword was specified, or the parameter value of the keyword was not specified.
Complete the command, or correct the keyword, or add the parameter value, and then try the command again.
40 : Stop Error
<insert_3> not valid for parameter <insert_4>.
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.
40 : Stop Error
A matching left or right parenthesis is missing.
Add the missing parenthesis or remove the extra parenthesis.
30 : Severe error
Channel program <insert_3> ended abnormally.
Look at previous error messages for channel program <insert_3> in the error files to determine the cause of the failure.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
rem |