AMQ9xxx: Remote

AMQ9001: Channel <insert_3> ended normally.
Severity: 0 : Informational
Explanation: Channel <insert_3> to host <insert_5> ended normally.
Response: None.

AMQ9002: Channel <insert_3> is starting.
Severity: 0 : Informational
Explanation: Channel <insert_3> is starting.
Response: None.

AMQ9003 (IBM i): Channel <insert_3> last message sequence number is <insert_1>.
Severity: 0 : Informational
Explanation: Channel <insert_3> last message sequence number is <insert_1>.
Response: None.

AMQ9004 (IBM i): Channel <insert_3> status information.
Severity: 0 : Informational
Explanation: Channel <insert_3> status information: Number of Messages in Doubt - <insert_1> In Doubt Sequence Number - <insert_2> In Doubt Logic Unit of Work ID - <insert_4>
Response: None.

AMQ9005: The IBM MQ security policy interceptor failed to access the Public-Key Cryptography Standards (PKCS) #11 hardware token.
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor failed in an attempt to open a Public-Key Cryptography Standards (PKCS) #11 token. Check GSKit ACME GSS minor reason <insert_1> for <insert_3>.
Response: Make sure that the PKCS #11 token is present and configured correctly, and retry the operation. Verify that the token label, PIN, and library name are configured correctly.

AMQ9006: The IBM MQ security policy interceptor did not attempt to open a PKCS #11 token because it did not have all required configuration information.
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor did not attempt to open a Public-Key Cryptography Standards (PKCS) #11 token because one or more of the token label, PIN, or shared library name were not configured.
Response: If you want to use a PKCS #11 token, make sure that the token label, PIN, and library name are configured correctly.

AMQ9007: The IBM MQ security policy interceptor failed to convert a Public-Key Cryptography Standards (PKCS) #11 key certificate label.
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor failed to convert a Public-Key Cryptography Standards (PKCS) #11 key certificate label needed to identify a key certificate item stored in a PKCS #11 token. Check GSKit ACME GSS minor reason <insert_1>.
Response: Make sure that the PKCS #11 key certificate label is defined correctly.

AMQ9008: Cannot acquire the certificate for the label: <insert_3> in the keystore file <insert_4>. GSKit ACME GSS minor reason is <insert_1>.
Severity: 20 : Error
Explanation: IBM MQ security policy interceptor was unable to read the certificate for the given label from keystore.
Response: Make sure the label is correctly set as the cms.certificate entry of the configuration file. Check if the keystore contains the certificate for the given label.

AMQ9009: Cannot acquire credentials. GSKit ACME GSS minor reason is <insert_1>.
Severity: 20 : Error
Explanation: IBM MQ security policy interceptor was unable to acquire credentials.
Response: Review the configuration to make sure the keystore database and stash files are not broken.

AMQ9010: IBM MQ security policy internal error: message could not be protected because specified encryption algorithm is not valid <insert_1>.
Severity: 20 : Error
Explanation: The value identifier is specified to unexpected value.
Response: This is an internal error. Contact your IBM service representative.

AMQ9011: The IBM MQ security policy interceptor failed to turn on the Public-Key Cryptography Standards (PKCS) #11 hardware RSA private key algorithm for this ACME environment. Check GSKit ACME GSS minor reason <insert_1>.
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor failed to register the Public-Key Cryptography Standards (PKCS) #11 cryptographic algorithm with the ACME environment.
Response: Make sure that the PKCS #11 token is functioning properly and retry the operation. If the problem persists, contact your IBM service representative.

AMQ9012: The IBM MQ security policy interceptor could not acquire the public key credential.
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor could not perform a public key infrastructure (PKI) login.
Response: Check the error messages related to acquiring public key credentials to determine the cause of the failure. Check whether user has the permission to read the kdb and stash files and verify whether the kdb file contains a certificate with the label specified. Finally, check whether the certificate has not expired.

AMQ9013: IBM MQ security policy internal error: the Independent Data Unit Protection (IDUP) environment could not be terminated. GSKit reason code <insert_1>.
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor could not release the GSKit IDUP environment because an internal error occurred.
Response: Consult the GSKit appendix in the Information Center for the explanation of the GSKit reason code and take corrective action. If the problem persists, contact your IBM service representative.

AMQ9014: The IBM MQ security policy interceptor failed to close a Public-Key Cryptography Standards (PKCS) #11 token. Check GSKit ACME GSS minor reason <insert_1>.
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor failed to close a Public-Key Cryptography Standards (PKCS) #11 token.
Response: Make sure that the PKCS #11 token is functioning properly and retry the operation. If the problem persists, contact your IBM service representative.

AMQ9015: IBM MQ security policy internal warning: GSKit could not release <insert_3>. GSKit reason code <insert_1>.
Severity: 20 : Error
Explanation: The IBM MQ security policy GSKit call with the indicated reason code failed because it could not release resources back to the system.
Response: No action is required. If the problem persists, contact your IBM service representative.

AMQ9016: IBM MQ security policy internal error: GSKit could not allocate <insert_3>. GSKit reason code <insert_1>.
Severity: 20 : Error
Explanation: The IBM MQ security policy GSKit call with the indicated reason code failed because the system could not allocate resources.
Response: Make sure the system meets hardware and software requirements necessary to execute the application, then restart the application.

AMQ9017: IBM MQ security policy internal error: message could not be unprotected: GSKit error code <insert_1>, reason <insert_2>.
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor could not verify or decrypt a message because the indicated GSKit error occurred. This can happen for several reasons, all of which are internal failures: (1) the message is not a valid PKCS#7 message; (2) the sender's certificate does not have the required key usage bit to be able to encrypt the message; (3) the sender's certificate was not recognized as a trusted certificate; (4) receiver is not among the recipients of the message.
Response: Consult the GSKit information in the Information Center for the explanation of the GSKit reason code and take corrective action. If the problem persists, contact your IBM service representative.

AMQ9018: The specified SHA-2 algorithm <insert_3> is not supported on this platform.
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor failed to apply a policy as this platform lacks support for SHA-2 signing algorithm.
Response: Check that all platforms that open a queue with a policy that specifies a SHA-2 signing algorithm have the required cryptographic library support.

AMQ9019: IBM MQ security policy internal error: message could not be protected because specified signature algorithm is not valid <insert_1>
Severity: 20 : Error
Explanation: The value identifier is specified to unexpected value.
Response: This is an internal error. Contact your IBM service representative.

AMQ9020: IBM MQ security policy internal error: message could not be protected because no recipients' DN is specified.
Severity: 20 : Error
Explanation: The policy is set to privacy but does not contain any recipient DN.
Response: This is an internal error. Contact your IBM service representative.

AMQ9021: An error occured during the certificate import for the following DN: <insert_3>, result: <insert_1>
Severity: 20 : Error
Explanation: The distinguished name is not present in the keystore or invalid.
Response: Consult the GSKit appendix in the Information Center for the explanation of the GSKit reason code and take corrective action. If the problem persists, contact your IBM service representative.

AMQ9022: An error occured during the certificate import for the following DN: <insert_3>, result: <insert_1>, reason: <insert_2>.
Severity: 20 : Error
Explanation: The distinguished name is not present in the keystore or invalid.
Response: Consult the GSKit appendix in the Information Center for the explanation of the GSKit reason code and take corrective action. If the problem persists, contact your IBM service representative.

AMQ9023: The name of the keystore file <insert_3> was incorrectly provided with the file extension <insert_4>
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor was unable to find the keystore file. It seems the value of the keystore configuration entry incorrectly contains the file extension.
Response: Ensure the keystore file name specified in the configuration file does not contain a file extension.

AMQ9024: The keystore file <insert_3> does not exist and the keystore configuration entry incorrectly ends with <insert_4>. Make sure the value of the keystore configuration does not contain the file extension and it points to an existing file.
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor was unable to find the keystore file. The value of the keystore configuration entry incorrectly contains the file extension of <insert_4> and the resultant filename of <insert_3> does not exist.
Response: Make sure the value of the keystore configuration does not contain the file extension and it points to an existing file.

AMQ9025: The keystore file <insert_3><insert_4> does not exist. Make sure the value of the keystore configuration entry points to an existing file.
Severity: 20 : Error
Explanation: IBM MQ security policy interceptor was unable to find the keystore database file.
Response: Make sure the value of the keystore configuration entry points to an existing file.

AMQ9026: Cannot read the keystore file <insert_3><insert_4>. Check the file permissions.
Severity: 20 : Error
Explanation: IBM MQ security policy interceptor was unable to read the keystore database file.
Response: Set the proper permissions for the keystore database file.

AMQ9027: Cannot access the keystore file <insert_3><insert_4>. Error code <insert_1>.
Severity: 20 : Error
Explanation: IBM MQ security policy interceptor was unable to open the keystore database file.
Response: Ensure the application accessing the keystore file has appropriate permissions to access the keystore file.

AMQ9028: The keystore stash file <insert_3><insert_4> does not exist.
Severity: 20 : Error
Explanation: IBM MQ security policy interceptor was unable to find the keystore stash file.
Response: Ensure the application accessing the keystore stash file has appropriate permissions to access the file.

AMQ9029: Cannot read the keystore stash file <insert_3><insert_4>.
Severity: 20 : Error
Explanation: IBM MQ security policy interceptor was unable to read the keystore stash file.
Response: Check the permissions for the keystore stash file.

AMQ9030: IBM MQ security policy internal error: queue information could not be resolved from the current queue object handle (<insert_1>).
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor could not resolve queue information from the current queue object handle because the object handle is invalid or unrecognised.
Response: Make sure that the queue has not already been opened by another IBM MQ application and that it has not been previously closed. If the problem persists, contact your IBM service representative.

AMQ9031: IBM MQ security policy interceptor has detected an error prior to callback exit execution. IBM MQ compcode <insert_1> : reason <insert_2>.
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor received an IBM MQ completion code indicating an error prior to interceptor execution.
Response: Consult the Information Center for the completion code and reason code, take corrective action. If the problem persists, contact your IBM service representative.

AMQ9032: IBM MQ security policy interceptor could not find queue manager CodedCharSetId (<insert_1>). Make sure you have permission to inquire about queue manager properties.
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor could not find the local queue manager's CodedCharSetId because an internal error occurred.
Response: Make sure that the application has inquire permission to the queue manager. If the problem persists, contact your IBM service representative.

AMQ9033: IBM MQ security policy internal error: could not find local queue manager CodedCharSetId (<insert_1>).
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor could not find the local queue manager's CodedCharSetId because an internal error occurred.
Response: If the problem persists, contact your IBM service representative.

AMQ9034: Message does not have a valid protection type.
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor detected an invalid protection type in a message header. This usually occurs because the IBM MQ message header is not valid.
Response: Retry the operation. If the problem persists, contact your IBM service representative.

AMQ9035: Message signer is not in the list of authorised signers.
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor detected that the message is signed by an unauthorised party.
Response: Establish whether the identity associated with the sender of the message is authorized to send messages to this application. Ensure the sender is named in the list of allowed signers on the security policy for the queue.

AMQ9036: MQOPEN() call failed: reason code (<insert_1>).
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor call to the IBM MQ MQOPEN() call failed with the indicated error.
Response: Consult the Information Center for an explanation of the error code and suggested corrective action. Ensure that the queue manager is operational and the queue exists.

AMQ9037: The IBM MQ security policy interceptor failed to process a message on queue <insert_3> with CompCode <insert_1> Reason code <insert_2>
Severity: 20 : Error
Explanation: An unexpected error was encountered whilst applying a security policy to queue <insert_3>.
Response: This is an internal error. Contact your IBM service representative.

AMQ9038: The IBM MQ security policy interceptor failed to convert the <insert_3> field of the IBM MQ header from CCSID <insert_1> to CCSID <insert_2>. Verify that default data conversion has been enabled in IBM MQ.
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor internal error: data conversion failed. This is usually a problem with incompatible character sets.
Response: Enable default data conversion in IBM MQ. If the problem persists, contact your IBM service representative.

AMQ9039: <insert_3> - message was signed by <insert_4> using <insert_5>.
Severity: 0 : Informational
Explanation: This is an informational message used to indicate that a message was signed, and to display the signer's name, message timestamp and signature algorithm used.
Response: None.

AMQ9040: <insert_3> - message was signed and encrypted by <insert_4> using <insert_5>.
Severity: 0 : Informational
Explanation: This is an informational message used to indicate that a message was signed and encrypted, and to display the signer's name and encryption algorithm name.
Response: None.

AMQ9041: Message was not protected.
Severity: 0 : Informational
Explanation: This is an informational message used to indicate that a message was neither signed nor encrypted.
Response: None.

AMQ9042: IBM MQ security policy internal error: unprotected message size <insert_1> bytes does not match the original message size <insert_2> bytes.
Severity: 20 : Error
Explanation: After unprotecting, the message size does not match the original message size. The message header might have been corrupted or tampered with.
Response: Check the message which has been put on the SYSTEM.PROTECTION.ERROR.QUEUE queue to find the cause of the error and the origin of the message. If the problem persists, contact your IBM service representative.

AMQ9043: Message protection algorithm <insert_3> is different than the required <insert_4>.
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor detected that a message did not meet the encryption strength required by the queue. This usually occurs when encryption strength for a queue is changed while there were still messages in the queue.
Response: Make sure that the same encryption strength is used for the message MQPUT and MQGET. When the queue encryption strength is changed, remove all messages in the queue before resuming normal operation.

AMQ9044: The IBM MQ security policy interceptor has put a defective message on error handling queue <insert_3>.
Severity: 20 : Error
Explanation: This is an informational message that indicates the IBM MQ security policy put a message it could not interpret onto the specified error handling queue, or returned the message to the original queue if the MQGET of the message was part of a Unit of Work.
Response: Make sure only valid messages are put onto queues protected by IBM MQ security policies.

AMQ9045: The IBM MQ security policy interceptor failed to put a defective message on error handling queue. IBM MQ reason code (<insert_1>)
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor was unable to put a message it could not interpret on the error handling queue because the indicated IBM MQ error occurred.
Response: Consult the Information Center for more information about the reason code. If the problem persists, contact your IBM service representative.

AMQ9046: The 'PDMQ' format header from the current message is invalid.
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor did not find a valid IBM MQ security policy header in the the current message.
Response: If the QoP setting for the queue is not set to 'none', make sure that no unprotected messages are routed to this queue.

AMQ9047: IBM MQ security policy found a valid 'PDMQ' format header in the current message.
Severity: 0 : Informational
Explanation: IBM MQ security policy interceptor found a valid IBM MQ security policy header in the current message.
Response: None.

AMQ9048: Message quality of protection (<insert_1>) does not match the quality of protection (<insert_2>) set for the queue <insert_3>.
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor detected a quality of protection (QoP) mismatch between the queue and a message in the queue. QoP mismatches usually occur because the queue QoP is changed between the message put and get.
Response: Make sure that the same queue quality of protection is used for the message put and get. When the queue QoP is changed, clean up all messages in the queue before resuming normal operation.

AMQ9049: Message with quality of protection (<insert_1>) higher than (<insert_2>) set for the queue <insert_3> has been accepted.
Severity: 0 : Informational
Explanation: The IBM MQ security policy interceptor detected a quality of protection (QoP) mismatch between the queue and a message in the queue. QoP mismatch usually occurs when the QoP of the queue is changed between the message put and get.
Response: Make sure that the same queue quality of protection is used for the message put and get. When the QoP of the queue is changed, remove all messages from the queue before resuming any operation.

AMQ9050: IBM MQ security policy could not access the security policy definitions. Major code <insert_1> : Minor code <insert_2>
Severity: 20 : Error
Explanation: The security policy definitions cannot be accessed.
Response: The security policy definitions must be accessible to this application. Check the object authority manager access control for this application to access the SYSTEM.PROTECTION.POLICY.QUEUE.

AMQ9051: IBM MQ could not find the security policy definition. Compcode <insert_1> : reason <insert_2>
Severity: 20 : Error
Explanation: The security policy definition is not defined.
Response: Security policy definition must be defined before this action.

AMQ9052: Message with no protection has been put into the queue <insert_3>.
Severity: 0 : Informational
Explanation: The IBM MQ security policy interceptor has successfully put a message with a QoP of 'none' onto the selected queue.
Response: None.

AMQ9053: Message with integrity protection has been put into the queue <insert_3>.
Severity: 0 : Informational
Explanation: The IBM MQ security policy interceptor has successfully put a message with a QoP of 'integrity' onto the selected queue.
Response: None.

AMQ9054: Message with privacy protection has been put into the queue <insert_3>.
Severity: 0 : Informational
Explanation: The IBM MQ security policy interceptor has successfully put a message with a QoP of 'privacy' onto the selected queue.
Response: None.

AMQ9055: Quality of protection (QoP) <insert_1> for queue <insert_3> is invalid
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor detected that the quality of protection specified in the security policy for the queue is invalid.
Response: Ensure that the encryption and signature algorithms specified for the queue in the IBM MQ security policy definition have valid values.

AMQ9056: IBM MQ security policy internal error: message could not be protected because the specified signature algorithm <insert_1> is not valid.
Severity: 20 : Error
Explanation: An unexpected signature algorithm has been specified.
Response: This is an internal error. Contact your IBM service representative.

AMQ9057: IBM MQ security policy internal error: message could not be processed because the specified encryption algorithm <insert_1> is not valid.
Severity: 20 : Error
Explanation: An unexpected encryption algorithm has been specified.
Response: This is an internal error. Contact your IBM service representative.

AMQ9058: The IBM MQ security policy interceptor cannot inquire the attributes for queue manager <insert_3>.
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor failed to inquire queue manager attributes, compcode <insert_1>, reason code <insert_2>.
Response: Make sure that the application has appropriate access control permissions to inquire the queue manager object.

AMQ9059: The IBM MQ security policy interceptor failed to generate a configuration event for queue manager <insert_3>.
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor failed to generate a configuration event, comp code <insert_1>, reason code <insert_2>.
Response: Ensure that the SYSTEM.ADMIN.CONFIG.EVENT queue is available for output from this process.

AMQ9060: The IBM MQ security policy keystore configuration file contains duplicate key: <insert_3>.
Severity: 20 : Error
Explanation: The IBM MQ security policy keystore configuration file contains duplicate key: <insert_3>.
Response: Make sure the keystore configuration file contains all required keys and does not contain duplicate keys.

AMQ9061: The IBM MQ security policy keystore configuration file does not contain key <insert_3>.
Severity: 20 : Error
Explanation: The IBM MQ security policy keystore configuration file does not contain key <insert_3>.
Response: Make sure the keystore configuration file contains all required keys and does not contain duplicate keys.

AMQ9062: The IBM MQ security policy interceptor could not read the keystore configuration file: <insert_3>.
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor could not read the keystore configuration file: <insert_3>.
Response: Make sure that the user who executes the IBM MQ application has permissions to read the configuration file. Check if the configuration file is not corrupted or empty. If the problem persists, contact your local IBM service representative.

AMQ9063: The IBM MQ security policy interceptor could not parse the keystore configuration file.
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor could not parse the keystore configuration file.
Response: Make sure the keystore configuration file contains all required keys and does not contain duplicate keys.

AMQ9064: The IBM MQ security policy interceptor failed to enable OCSP checking.
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor encountered an error while configuring OCSP checking.
Response: Check the OCSP configuration, making sure that all parameters are specified correctly.

AMQ9065: The IBM MQ security policy interceptor failed to process the OCSP configuration.
Severity: 20 : Error
Explanation: The OCSP configuration for IBM MQ is incorrect.
Response: Check the OCSP configuration, making sure that all mandatory parameters are specified.

AMQ9066: The IBM MQ security policy interceptor failed to enable CRL checking.
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor encountered an error while configuring CRL checking.
Response: Check the CRL configuration, making sure that all parameters are correctly specified.

AMQ9067: The IBM MQ security policy interceptor failed to process the CRL configuration.
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor failedto process the CRL configuration information.
Response: Check the CRL configuration, making sure that all mandatory parameters are specified.

AMQ9068: The IBM MQ security policy interceptor could not enable revocation checking.
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor could not enable OCSP or CRL because the required functionality is not supported by the version of GSKit that is currently being used.
Response: The currently enabled version of GSKit does not meet the minimum requirements for IBM MQ security policy revocation checking. Install a newer version of GSKit that does meet the minimum requirements.

AMQ9069: The IBM MQ security policy interceptor failed to validate a certificate.
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor could not validate a certificate when attempting to protect or unprotect a message. The cryptographic provider failed to verify the certificate with a distinguished name of <insert_3>. The validation may have failed for this certificate, or another certificate in the validation chain. The return code from the cryptographic provider was <insert_1>.
Response: Ensure that all certificates required to validate the identify of valid message signers are available.

AMQ9070: The IBM MQ security policy interceptor failed to validate a certificate.
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor could not validate a certificate when attempting to unprotect a message. If the message was subject to a browse operation it will remain on its queue, otherwise it will be moved to the SYSTEM.PROTECTION.ERROR.QUEUE. The return code from the cryptographic provider was <insert_1>.
Response: Ensure that all certificates required to validate the identify of valid message signers are available.

AMQ9071: IBM MQ security policy interceptor internal error: could not read GSKit attribute <insert_3>, GSKit reason code: <insert_1>.
Severity: 20 : Error
Explanation: The GSKit gskacme_cred_get function failed.
Response: Make sure you are using the correct version of GSKit for this installation of IBM MQ.

AMQ9072: The certificate revocation status is UNKNOWN, GSKit log: <insert_3>.
Severity: 20 : Error
Explanation: The IBM MQ security policy interceptor failed to determine the certificate revocation status.
Response: Read the GSKit log to find out the certificate DN and serial number.

AMQ9073: The certificate revocation status is UNKNOWN, GSKit log: <insert_3>.
Severity: 10 : Warning
Explanation: The IBM MQ security policy interceptor failed to determine the certificate revocation status.
Response: Read the GSKit log to find out the certificate DN and serial number.

AMQ9074: The Trial Period license for this copy of IBM MQ AMS has expired.
Severity: 20 : Error
Explanation: This copy of IBM MQ AMS was licensed to be used in trial mode for a limited period only. This period has expired.
Response: Install a Production license for this copy of IBM MQ AMS.

AMQ9075: The Beta license for this copy of IBM MQ AMS has expired.
Severity: 20 : Error
Explanation: This copy of IBM MQ AMS was licensed to be used for Beta testing for a limited period only. This period has expired.
Response: Install a Production license for this copy of IBM MQ AMS.

AMQ9076: There are <insert_1> days left in the trial period for this copy of IBM MQ AMS.
Severity: 0 : Informational
Explanation: This copy of IBM MQ AMS is licensed for a limited period only.
Response: None.

AMQ9077: This is the final day of the trial period for this copy of IBM MQ AMS.
Severity: 10 : Warning
Explanation: This copy of IBM MQ AMS is licensed for a limited period only.
Response: Install a Production license for this copy of IBM MQ AMS.

AMQ9078: There is one day left in the trial period for this copy of IBM MQ AMS.
Severity: 0 : Informational
Explanation: This copy of IBM MQ AMS is licensed for a limited period only.
Response: None.

AMQ9079: There are <insert_1> days left in the beta test period for this copy of IBM MQ AMS.
Severity: 0 : Informational
Explanation: This copy of IBM MQ AMS is licensed for a limited period only.
Response: None.

AMQ9080: There is one day left in the Beta test period for this copy of IBM MQ AMS.
Severity: 0 : Informational
Explanation: This copy of IBM MQ AMS is licensed for a limited period only.
Response: None.

AMQ9081: This is the final day of the Beta test period for this copy of IBM MQ AMS.
Severity: 10 : Warning
Explanation: This copy of IBM MQ AMS is licensed for a limited period only.
Response: Install a Production license for this copy of IBM MQ AMS.

AMQ9082: No policies found.
Severity: 0 : Informational
Explanation: There are no policies defined.
Response: None.

AMQ9083 (UNIX and Linux): Missing environment variables are required by IBM MQ AMS to locate %3.
Severity: 20 : Error
Explanation: IBM MQ AMS needs to access configuration information to initialize, however the location of the %3 file cannot be determined as environment variables are incorrectly configured for this process.
Response: Unless explicitly overridden by the presence of the MQS_KEYSTORE_CONF environment variable IBM MQ AMS requires the HOME environment variable to be set. Set either MQS_KEYSTORE_CONF or HOME environment variables to identify the location of the %3 file.

AMQ9083 (Windows): Missing environment variables are required by IBM MQ AMS to locate %3.
Severity: 20 : Error
Explanation: IBM MQ AMS needs to access configuration information to initialize, however the location of the %3 file cannot be determined as environment variables are incorrectly configured for this process.
Response: Unless explicitly overridden by the presence of the MQS_KEYSTORE_CONF environment variable IBM MQ AMS requires either HOMEDRIVE and HOMEPATH environment variables to be set. Set either MQS_KEYSTORE_CONF or HOMEDRIVE and HOMEPATH environment variables to identify the location of the %3 file.

AMQ9084: IBM MQ AMS policy set.
Severity: 0 : Informational
Explanation: The IBM MQ AMS policy was set.
Response: None.

AMQ9085: IBM MQ AMS policy deleted.
Severity: 0 : Informational
Explanation: The IBM MQ AMS policy was deleted.
Response: None.

AMQ9086: Display IBM MQ AMS policy details.
Severity: 0 : Informational

AMQ9087: Invalid environment for IBM MQ AMS.
Severity: 20 : Error
Explanation: IBM MQ AMS is unable to initialize in the current application environment. On HP-UX, a possible reason is that the application is linked to unthreaded MQ libraries which are not supported when opening IBM MQ AMS protected queues.
Response: Either relink the application with threaded MQ libraries, or do not attempt to open queues that are protected by IBM MQ AMS security policies from within this application.

AMQ9181: The response set by the exit is not valid.
Severity: 30 : Error
Explanation: The user exit <insert_3> returned a response code <insert_1> that is not valid in the ExitResponse field of the channel exit parameters (MQCXP). Message AMQ9190 is issued giving more details, and the channel stops.
Response: Investigate why the user exit program set a response code that is not valid.

AMQ9182: The secondary response set by the exit is not valid.
Severity: 30 : Error
Explanation: The user exit <insert_3> returned a secondary response code <insert_1> in the ExitResponse2 field of the channel exit parameters (MQCXP) that is not valid. Message AMQ9190 is issued giving more details, and the channel stops.
Response: Investigate why the user exit program set a secondary response code that is not valid.

AMQ9184: The exit buffer address set by the exit is not valid.
Severity: 30 : Error
Explanation: The user exit <insert_3> returned an address <insert_1> for the exit buffer that is not valid, when the secondary response code in the ExitResponse2 field of the channel exit parameters (MQCXP) is set to MQXR2_USE_EXIT_BUFFER. Message AMQ9190 is issued giving more details, and the channel stops.
Response: Investigate why the user exit program set an exit buffer address that is not valid. The most likely cause is the failure to set a value, so that the value is 0.

AMQ9185: The exit space set by the exit is not valid.
Severity: 30 : Error
Explanation: The user exit <insert_3> returned an exit space value <insert_1> that is not valid in the ExitSpace field of the channel exit parameters (MQCXP). Message AMQ9190 is issued giving more details, and the channel stops.
Response: Investigate why the user exit program set an exit space value that is not valid. Correct the error.

AMQ9186: Too much exit space reserved by send exits.
Severity: 30 : Error
Explanation: At exit initialization the send exits in the send exit chain for channel <insert_3> returned values in the ExitSpace field of the channel exit parameters (MQCXP). The total of these ExitSpace values is <insert_1>. The maximum number of bytes that can be sent in a single transmission is <insert_2>. Room must be left for at least 1024 bytes of message data in each transmission. So too much exit space has been reserved by the send exits. The channel stops.
Response: Investigate why the send exit programs set exit space values that are too large. Correct the error.

AMQ9187: The header compression value set by the exit is not valid.
Severity: 30 : Error
Explanation: The user exit <insert_3> returned a header compression value <insert_1> in the CurHdrCompression field of the channel exit parameters (MQCXP) that was not one of the negotiated supported values specified in the HdrCompList field of the channel description (MQCD). Message AMQ9190 is issued giving more details, and the channel stops.
Response: Investigate why the user exit program specified a header compression value that was not one of the negotiated supported values.

AMQ9188: The message compression value set by the exit is not valid.
Severity: 30 : Error
Explanation: The user exit <insert_3> returned a message compression value <insert_1> in the CurMsgCompression field of the channel exit parameters (MQCXP) that was not one of the negotiated supported values specified in the MsgCompList field of the channel description (MQCD). Message AMQ9190 is issued giving more details, and the channel stops.
Response: Investigate why the user exit program specified a message compression value that was not one of the negotiated supported values.

AMQ9189: The data length set by the exit is not valid.
Severity: 30 : Error
Explanation: The user exit <insert_3> returned a data length value <insert_1> that was not greater than zero. Message AMQ9190 is issued giving more details, and the channel stops.
Response: Investigate why the user exit program set a data length that is not valid.

AMQ9190: Channel stopping because of an error in the exit.
Severity: 30 : Error
Explanation: The user exit <insert_3>, invoked for channel <insert_4> with id <insert_1> and reason <insert_2>, returned values that are not valid, as reported in the preceding messages. The channel stops.
Response: Investigate why the user exit program set values that are not valid.

AMQ9195: Data length larger than maximum segment length.
Severity: 30 : Error
Explanation: The data length <insert_1> set by send exit <insert_3> is larger than the maximum segment length (<insert_2>). The maximum segment length is the maximum number of bytes that can be sent in a single transmission minus the user exit space required by all the send exits subsequent to the current one in the send exit chain. Message AMQ9190 is issued giving more details, and the channel stops.
Response: Investigate why the user exit program set a data length that is not valid. Correct the error.

AMQ9196: Data length is larger than the agent buffer length.
Severity: 30 : Error
Explanation: The data length <insert_1> set by exit <insert_3> is larger than the agent buffer length. The user exit returned data in the supplied agent buffer, but the length specified is greater than the length of the buffer. Message AMQ9190 is issued giving more details, and the channel stops.
Response: Investigate why the user exit program set a data length that is not valid. Correct the error.

AMQ9197: Data length is larger than the exit buffer length.
Severity: 30 : Error
Explanation: The data length <insert_1> set by exit <insert_3> is larger than the exit buffer length. The user exit returned data in the supplied exit buffer, but the length specified is greater than the length of the buffer. Message AMQ9190 is issued giving more details, and the channel stops.
Response: Investigate why the user exit program set a data length that is not valid.

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

AMQ9202: Remote host <insert_3> not available, retry later.
Severity: 30 : Error
Explanation: The attempt to allocate a conversation using <insert_4> to host <insert_3> for channel <insert_5> was not successful. However the error may be a transitory one and it may be possible to successfully allocate a <insert_4> conversation later.
In some cases the remote host cannot be determined and so is shown as '????'.
Response: Try the connection again later. If the failure persists, record the error values and contact your systems administrator. The return code from <insert_4> is <insert_1> (X<insert_2>). The reason for the failure may be that this host cannot reach the destination host. It may also be possible that the listening program at host <insert_3> was not running. If this is the case, perform the relevant operations to start the <insert_4> listening program, and try again.

AMQ9203: A configuration error for <insert_4> occurred.
Severity: 30 : Error
Explanation: Error in configuration for communications to host <insert_3>. Allocation of a <insert_4> conversation to host <insert_3> was not possible.
Response: This error can be reported by channels using a communications protocol of TCP/IP, defined by TRPTYPE(TCP), or by channels using a communications protocol of LU6.2, defined by TRPTYPE(LU62).
For a channel using a communications protocol of TCP/IP. the configuration error may be one of the following:

1.It may be that the host name specified is incorrect. Correct the error and try again.

2.It may be that the host name specified cannot be resolved to a network address. The host name may not be in the nameserver.
For a channel using a communications protocol of LU6.2. the configuration error may be one of the following:

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

4.It may be that an LU 6.2 session has not been established. Contact your systems administrator.
The return code from the <insert_4><insert_5> call was <insert_1> (X<insert_2>).
Record the error values and tell the system administrator.

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

AMQ9205: The host name supplied is not valid.
Severity: 30 : Error
Explanation: The supplied <insert_4> host name <insert_3> could not be resolved into a network address. Either the name server does not contain the host, or the name server was not available.
Response: Check the <insert_4> configuration on your host.

AMQ9206: Error sending data to host <insert_3>.
Severity: 30 : Error
Explanation: An error occurred sending data over <insert_4> to <insert_3>. This may be due to a communications failure.
Response: The return code from the <insert_4><insert_5> call was <insert_1> X(<insert_2>). Record these values and tell your systems administrator.

AMQ9207: The data received from host <insert_3> on channel <insert_5> is not valid.
Severity: 30 : Error
Explanation: Incorrect data format received from host <insert_3> over <insert_4>. It may be that an unknown host is attempting to send data.
An FFST file might be generated containing the invalid data received. It will not be generated if this is the beginning of a conversation with the remote side, and the format is a simple known format (example: a GET request from an HTTP web browser). If you want to override this, to cause FFST files to be written for any bad data, including simple known formats, then set the environment variable AMQ_BAD_COMMS_DATA_FDCS=TRUE and restart the queue manager.
The channel name is <insert_5>; in some cases it cannot be determined and so is shown as '????'.
Response: Tell the systems administrator.

AMQ9208: Error on receive from host <insert_3>.
Severity: 30 : Error
Explanation: An error occurred receiving data from <insert_3> over <insert_4>. This may be due to a communications failure.
Response: The return code from the <insert_4><insert_5> call was <insert_1> (X<insert_2>). Record these values and tell the systems administrator.

AMQ9209: Connection to host <insert_3> for channel <insert_5> closed.
Severity: 30 : Error
Explanation: An error occurred receiving data from <insert_3> over <insert_4>. The connection to the remote host has unexpectedly terminated.
The channel name is <insert_5>; in some cases it cannot be determined and so is shown as '????'.
Response: Tell the systems administrator.

AMQ9210: Remote attachment failed.
Severity: 30 : Error
Explanation: There was an incoming attachment from a remote host, but the local host could not complete the bind.
Response: The return code from the <insert_4><insert_5> call was <insert_1> (X<insert_2>). Record these values and tell the systems administrator who should check the <insert_4> configuration.

AMQ9211: Error allocating storage.
Severity: 30 : Error
Explanation: The program was unable to obtain enough storage.
Response: Stop some programs which are using storage and retry the operation. If the problem persists contact your systems administrator.

AMQ9212: A TCP/IP socket could not be allocated.
Severity: 30 : Error
Explanation: A TCP/IP socket could not be created, possibly because of a storage problem.
Response: The return code from the <insert_4><insert_5> call was <insert_1> (X<insert_2>). Try the program again. If the failure persists, record the error values and tell the systems administrator.

AMQ9213: A communications error for <insert_4> occurred.
Severity: 30 : Error
Explanation: An unexpected error occurred in communications.
Response: The return code from the <insert_4><insert_5> call was <insert_1> (X<insert_2>). Record these values and tell the systems administrator.

AMQ9214: Attempt to use an unsupported communications protocol.
Severity: 30 : Error
Explanation: An attempt was made to use an unsupported communications protocol type <insert_2>.
Response: Check the channel definition file. It may be that the communications protocol entered is not a currently supported one.

AMQ9215: Communications subsystem unavailable.
Severity: 30 : Error
Explanation: An attempt was made to use the communications subsystem, but it has not been started.
Response: Start the communications subsystem, and rerun the program.

AMQ9216: Usage: <insert_3> [-m QMgrName] [-n TPName]
Severity: 20 : Error
Explanation: Values passed to the responder channel program are not valid. The parameters that are not valid are as follows :-
<insert_4>
The responder channel program exits.
Response: Correct the parameters passed to the channel program and retry the operation.

AMQ9216 (AIX): Usage: <insert_3> [-m QMgrName]
Severity: 20 : Error
Explanation: Values passed to the responder channel program are not valid. The parameters that are not valid are as follows :-
<insert_4>
The responder channel program exits.
Response: Correct the parameters passed to the channel program and retry the operation.

AMQ9216 (HP-UX): Usage: <insert_3> [-m QMgrName]
Severity: 20 : Error
Explanation: Values passed to the responder channel program are not valid. The parameters that are not valid are as follows :-
<insert_4>
The responder channel program exits.
Response: Correct the parameters passed to the channel program and retry the operation.

AMQ9217: The TCP/IP listener program could not be started.
Severity: 30 : Error
Explanation: An attempt was made to start a new instance of the listener program, but the program was rejected.
Response: The failure could be because either the subsystem has not been started (in this case you should start the subsystem), or there are too many programs waiting (in this case you should try to start the listener program later).

AMQ9218: The <insert_4> listener program could not bind to port number <insert_1>.
Severity: 30 : Error
Explanation: An attempt to bind the <insert_4> socket to the listener port was unsuccessful.
Response: The failure could be due to another program, including other MQ listeners, using the same port number. The return code from the <insert_3> call for port <insert_5><insert_1> was <insert_2>. Record these values and tell the systems administrator.

AMQ9219: The TCP/IP listener program could not create a new connection for the incoming conversation.
Severity: 30 : Error
Explanation: An attempt was made to create a new socket because an attach request was received, but an error occurred.
Response: The failure may be transitory, try again later. If the problem persists, record the return code <insert_1> and tell the systems administrator. It may be necessary to free some jobs, or restart the communications system.

AMQ9220: The <insert_4> communications program could not be loaded.
Severity: 30 : Error
Explanation: The attempt to load the <insert_4> library or procedure <insert_3> failed with error code <insert_1>.
Response: Either the library must be installed on the system or the environment changed to allow the program to locate it.

AMQ9221: Unsupported protocol was specified.
Severity: 30 : Error
Explanation: The specified value of <insert_3> was not recognized as one of the protocols supported.
Response: Correct the parameter and retry the operation.

AMQ9222: Cannot find the configuration file.
Severity: 10 : Warning
Explanation: The configuration file <insert_3> cannot be found. This file contains default definitions for communication parameters. Default values will be used.
Response: None.

AMQ9223: Enter a protocol type.
Severity: 30 : Error
Explanation: The operation you are performing requires that you enter the type of protocol.
Response: Add the protocol parameter and retry the operation.

AMQ9224: Unexpected contents in .ini file entry <insert_3> in stanza <insert_4> on line <insert_1> in file <insert_5>.
Severity: 30 : Error
Explanation: The entry with name <insert_3> in stanza <insert_4> on line <insert_1> in .ini file <insert_5> is either not a valid keyword or has an invalid value.
Response: Correct the .ini file and retry the operation.

AMQ9225: File syntax error.
Severity: 30 : Error
Explanation: A syntax error was detected on line <insert_1> while processing the INI file.
Response: Correct the problem and retry the operation.

AMQ9225 (Windows): File syntax error.
Severity: 30 : Error
Explanation: A syntax error was detected while processing the configuration data.
Response: Correct the problem and retry the operation.

AMQ9226: Usage: <insert_3> [-m QMgrName] [-t Protocol] [ProtocolOptions]
-m Queue manager name.
-t Protocol: TCP (default), LU62, NETBIOS, SPX.
TCP [-p Port] [-i IPAddr] [-b Backlog]
LU62 [-n TPName]
NETBIOS [-l LocalName] [-e Names] [-s Sessions]
[-o Commands] [-a Adaptor]
SPX [-x Socket] [-b Backlog]
Severity: 10 : Warning
Explanation: This shows the correct usage.
Response: Correct the parameters passed to the listener program and retry the operation.

AMQ9226 (UNIX and Linux): Usage: <insert_3> [-m QMgrName] [-t TCP] [ProtocolOptions]
-m Queue manager name.
-t Protocol: TCP (default).
TCP [-p Port] [-i IPAddr] [-b Backlog]
Severity: 10 : Warning
Explanation: This shows the correct usage.
Response: Correct the parameters passed to the listener program and retry the operation.

AMQ9227: <insert_3> local host name not provided.
Severity: 30 : Error
Explanation: A name is required for the <insert_3> process to register with the network.
Response: Add a local name to the configuration file and retry the operation.

AMQ9228: The <insert_4> responder program could not be started.
Severity: 30 : Error
Explanation: An attempt was made to start an instance of the responder program, but the program was rejected.
Response: The failure could be because either the subsystem has not been started (in this case you should start the subsystem), or there are too many programs waiting (in this case you should try to start the responder program later). The <insert_5> reason code was <insert_1>.

AMQ9229: The application has been ended.
Severity: 30 : Error
Explanation: You have issued a request to end the application.
Response: None.

AMQ9230: An unexpected <insert_4> event occurred.
Severity: 30 : Error
Explanation: During the processing of network events, an unexpected event <insert_1> occurred.
Response: None.

AMQ9231: The supplied parameter is not valid.
Severity: 30 : Error
Explanation: The value of the <insert_4> <insert_5> parameter has the value <insert_3>. This value has either not been specified or has been specified incorrectly.
Response: Check value of the <insert_5> parameter and correct it if necessary. If the fault persists, record the return code (<insert_1>,<insert_2>) and <insert_4> and tell the systems administrator.

AMQ9232: No <insert_3> specified
Severity: 30 : Error
Explanation: The operation requires the specification of the <insert_3> field.
Response: Specify the <insert_3> and retry the operation.

AMQ9233: Error creating <insert_3> thread.
Severity: 30 : Error
Explanation: The process attempted to create a new thread. The most likely cause of this problem is a shortage of an operating system resource (for example: memory). Use any previous FFSTs to determine the reason for the failure. The IBM MQ internal return code describing the reason for the failure is <insert_1>.
Response: Contact the systems administrator. If the problem persists save any generated output files and use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.

AMQ9235: The supplied local communications address cannot be resolved.
Severity: 30 : Error
Explanation: The local communications address (LOCLADDR) value <insert_3> cannot be resolved into an IP address.
Response: Enter a local communications address value which can be resolved into an IP address, and try again.

AMQ9236: The supplied Partner LU was invalid.
Severity: 30 : Error
Explanation: The <insert_4> Partner LU name <insert_3> was invalid.
Response: Either the Partner LU name was entered incorrectly or it was not in the <insert_4> communications configuration. Correct the error and try again.

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

2. It may be that an LU 6.2 session has not been established. Contact your systems administrator.
The return code from <insert_4> is <insert_1> with associated <insert_5> <insert_2>.
Response: Record the error values and tell the system administrator.

AMQ9238: A communications error for <insert_4> occurred.
Severity: 30 : Error
Explanation: An unexpected error occurred in communications.
Response: The return code from the <insert_4><insert_3> call was <insert_1> with associated <insert_5> <insert_2>.

AMQ9239: Usage: <insert_3> [-m QMgrName] -n TpName -g Gateway-name
Severity: 10 : Warning
Explanation: Values passed to the listener program were invalid. The parameter string passed to this program is as follows, default values being used for parameters not supplied: [-m QMgrName] -n TpName -g Gateway-name
Response: Correct the parameters passed to the listener program and retry the operation.

AMQ9240: An SPX socket was already in use.
Severity: 30 : Error
Explanation: The listener received return code <insert_1> when attempting to open socket <insert_2>.
Response: The specified socket is already in use by another process. To use another socket, specify another socket on the command line to runmqlsr or update the default in the qm.ini file.

AMQ9240 (IBM i): An SPX socket was already in use.
Severity: 30 : Error
Explanation: The listener received return code <insert_1> when attempting to open socket <insert_2>.
Response: The specified socket is already in use by another process. To use another socket specify another socket on the command line to STRMQMLSR or update the default in the qm.ini file.

AMQ9240 (Windows): An SPX socket was already in use.
Severity: 30 : Error
Explanation: The listener received return code <insert_1> when attempting to open socket <insert_2>.
Response: The specified socket is already in use by another process. To use another socket, specify a different socket on the command line to the runmqlsr command, or update the default in the configuration data.

AMQ9241: SPX is not available.
Severity: 30 : Error
Explanation: IBM MQ received return code <insert_1> when attempting to start SPX communications.
Response: Ensure that IPX/SPX support is installed on the machine and that it is started before trying to start an IBM MQ SPX channel.

AMQ9242: SPX resource problem.
Severity: 30 : Error
Explanation: IBM MQ received return code <insert_1> when attempting to start SPX communications, indicating a resource problem.
Response: Ensure that sufficient IPX/SPX resources are available before commencing communications over IPX/SPX.

AMQ9243: The queue manager <insert_3> does not exist.
Severity: 30 : Error
Explanation: You tried to perform an action against a queue manager that does not exist. You may have specified the wrong queue manager name.
Response: If you specified the wrong name, correct the name and submit the command again. If the queue manager does not exist, create the queue manager and submit the command again.

AMQ9244: The default queue manager does not exist.
Severity: 30 : Error
Explanation: You tried to perform an action against a queue manager that does not exist.
Response: Create the default queue manager and submit the command again.

AMQ9245 (Windows): Unable to obtain account details for channel MCA user ID.
Severity: 10 : Warning
Explanation: IBM MQ was unable to obtain the account details for MCA user ID <insert_3>. This user ID was the MCA user ID for channel <insert_4> on queue manager <insert_5> and may have been defined in the channel definition, or supplied either by a channel exit or by a client.
Response: Ensure that the user ID is correct and that it is defined on the Windows local system, the local domain or on a trusted domain. For a domain user ID, ensure that all necessary domain controllers are available.

AMQ9246: The TCP/IP listener on port <insert_1> could not start a new channel.
Severity: 30 : Error
Explanation: An attempt has been made to connect to the queue manager by starting a new channel within the TCP/IP listener which is listening on port <insert_1>. The maximum socket number which can be used by a channel running on this listener is <insert_2>. A socket number beyond this maximum was allocated for the new channel. This connection attempt has been rejected, but the listener continues to listen for further connection requests. The socket number allocated for a new listener channel is related to the number of channels currently running within that listener process. The problem has arisen because too many channels are directed at the port on which this listener is listening.
Response: An extra listener process should be started to listen on a different port. Some of the channels to the queue manager should be redirected from the port on which the existing listener is listening to the new port.

AMQ9247: SSPI Security: bad return from SSPI call.
Severity: 30 : Error
Explanation: Channel <insert_3> has been closed because the SSPI channel exit received a bad return code from SSPI.
Response: Consult the appropriate SSPI manuals to find out the meaning of status <insert_4> on call <insert_5>, and correct the error.

AMQ9248: The program could not bind to a <insert_3> socket.
Severity: 30 : Error
Explanation: The attempt to bind to socket <insert_4> failed with return code <insert_1>. The failing <insert_3> call was <insert_5>. The most likely cause of this problem is incorrect configuration of the <insert_3> local address or incorrect start and end port parameters.
Response: Contact the system administrator. If the problem persists save any generated output files and use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.

AMQ9255: Listener already running.
Severity: 30 : Error
Explanation: The request to start the IBM MQ listener failed because there is already a listener running against the specified network resources.
Response: None.

AMQ9259: Connection timed out from host <insert_3>.
Severity: 30 : Error
Explanation: A connection from host <insert_3> over <insert_4> timed out.
Response: The <insert_5> call 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.

AMQ9264: Usage: <insert_3> -m QMgrName -c ChannelName [-n | -q]
-c Generic channel name.
-m Queue manager name.
-n Do not move messages to the new transmission queue.
-q Query the current configuration.
Severity: 10 : Warning
Explanation: Values passed to the <insert_3> program are not valid. The parameters that are not valid are as follows :-
<insert_4>
The <insert_3> program exits.
Response: Correct the parameters passed to the <insert_3> program and retry the operation.

AMQ9265: Switching transmission queues for channel <insert_3> is not required.
Severity: 0 : Informational
Explanation: Transmission queue configuration is up-to-date for cluster sender channel <insert_3>. No switching is currently required.
Response: None.

AMQ9266: Cluster sender channel <insert_3> is currently switching the transmission queues.
Severity: 10 : Warning
Explanation: Transmission queue switching from queue <insert_4> to queue <insert_5> for cluster sender channel <insert_3> is currently in progress.
Response: None.

AMQ9267: Switch to transmission queue <insert_5> is pending for channel <insert_3>. The current transsmission queue <insert_4> has <insert_1> messages queued for the channel.
Severity: 10 : Warning
Explanation: There are remaining transmission queue configuration changes from queue <insert_4> to <insert_5> for cluster sender channel <insert_3>.
Response: Start the specified cluster sender channel or repeat the command without the query option to to complete the switching process.

AMQ9268: Cluster sender channel <insert_3> successfully switched to use XMITQ <insert_5>.
Severity: 0 : Informational
Explanation: The XMITQ for cluster sender channel <insert_3> was successfully switched from <insert_4> to <insert_5>.
Response: None.

AMQ9269: The switch of XMITQ for the cluster sender channel <insert_3> has failed to complete due to reason code <insert_1>. Review the Queue Manager error logs for further details of the failure.
Severity: 0 : Informational
Explanation: The switch of XMITQ for cluster sender channel <insert_3> from queue <insert_4> to queue <insert_5> has failed to complete with reason code <insert_1>.
Response: None.

AMQ9270: Sharing conversation could not start.
Severity: 30 : Error
Explanation: The attempt to start sharing conversation <insert_1> on socket <insert_2> (channel <insert_3>) was rejected at the server-connection end of the channel.
Response: Examine diagnostic information at the server-connection end of channel <insert_3> to see why the conversation did not start. If possible, correct the error causing the failure and retry.

AMQ9271: Channel <insert_3> timed out.
Severity: 30 : Error
Explanation: A timeout occurred while waiting to receive from the other end of channel <insert_3>. The address of the remote end of the connection was <insert_4>.
Response: The return code from the <insert_5> call was <insert_1> (X<insert_2>). Record these values and tell the systems administrator.

AMQ9272: Thread mutex semaphore error.
Severity: 30 : Error
Explanation: The process attempted an operation on a thread mutex semaphore. 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 IBM MQ function involded was <insert_3> and the internal return code describing the reason for the failure is <insert_1>.
Response: Contact the systems administrator. If the problem persists save any generated output files and use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.

AMQ9273: Thread event error.
Severity: 30 : Error
Explanation: The process attempted an operation on a thread event. 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 IBM MQ function involved was <insert_3> and the internal return code describing the reason for the failure is <insert_1>.
Response: Contact the systems administrator. If the problem persists save any generated output files and use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.

AMQ9280: Parameter requesting Suite B contains an invalid value.
Severity: 30 : Error
Explanation: An SSL or TLS channel running on an MQ client has failed to start. This is because the MQSUITEB environment variable, or the MQSCO EncryptionPolicySuiteB field, contains an invalid value. The values specified were <insert_3>.
The channel is <insert_4>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.
Response: Set the MQSUITEB environment variable, or the MQSCO EncryptionPolicySuiteB field, to a valid value. Restart the channel.
Refer to the IBM MQ Security documentation for more information on Suite B configuration.

AMQ9281: Parameter requesting Suite B contains an invalid combination of values.
Severity: 30 : Error
Explanation: An SSL or TLS channel running on an MQ client has failed to start. This is because the MQSUITEB environment variable, or the MQSCO EncryptionPolicySuiteB field, contains mutually exclusive values. All of the values are valid, but some of them cannot be used together. The values specified were <insert_3>.
The channel is <insert_4>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.
Response: Set the MQSUITEB environment variable, or the MQSCO EncryptionPolicySuiteB field, to a valid combination of values. Restart the channel.
Refer to the IBM MQ Security documentation for more information on Suite B configuration.

AMQ9282: Invalid CipherSpec for the configured Suite B security level.
Severity: 30 : Error
Explanation: The user is attempting to start a channel on a queue manager or MQ client which has been configured to run in Suite B mode. The user has specified a CipherSpec which does not meet the configured Suite B security level.
The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.
The remote host is <insert_4>.
Response: Redefine the channel to run with a Suite B compliant CipherSpec which satisfies the configured Suite B security level. Alternatively, the channel may be defined with the correct CipherSpec and the queue manager or MQ client should not be running in Suite B mode; if this is the case, ensure that Suite B mode is not configured. Once the error is corrected, restart the channel.
Refer to the IBM MQ Security documentation for more information on Suite B security levels and CipherSpecs.
This message might occur after applying IBM MQ maintenance because the FIPS and Suite B standards are updated periodically. When such changes occur, IBM MQ is also updated to implement the latest standard. As a result, you might see changes in behavior after applying maintenance. For more information about the versions of FIPS and Suite B standards enforced by IBM MQ, refer to the readme:
http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27006097

AMQ9285: The proposed CipherSpec is incompatible with a certificate.
Severity: 30 : Error
Explanation: The SSL or TLS handshake failed because the proposed CipherSpec is incompatible with one of the certificates.
It is necessary for both the local and remote systems to use a certificate which is suitable for use with the channel CipherSpec. Common causes of this error include:
(a) An RSA-based CipherSpec was specified when using a certificate which contains a non-RSA public key.
(b) An Elliptic Curve-based CipherSpec was specified when using a certificate which contains a non-EC public key.
The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.
The remote host is <insert_4>.
Response: Specify a different CipherSpec which is suitable for use with the digital certificates used on both the local and remote systems. Restart the channel.
Refer to the IBM MQ Security documentation for more information on CipherSpecs.

AMQ9286: The revocation status of a certificate chain supplied by an SSL or TLS client could not be checked.
Severity: 10 : Warning
Explanation: At least one certificate in a certificate chain supplied by the remote end of the channel does not contain an Authority Information Access extension with an OCSP URL and no other certificate revocation checking method is enabled. IBM MQ was unable to check the revocation status of the certificate chain.
The channel name is <insert_5>. In some cases the channel name cannot be determined and so is shown as '????'.
The details of the certificate chain are: <insert_3>
The OCSPAuthentication configuration option for unknown revocation status is currently set to: <insert_4>
The SSL or TLS handshake will be stopped if the OCSPAuthentication option is set to 'Required' or will continue if it is set to 'AllowNoCheck' or 'Warn'.
Response: To enable revocation checking for certificates without an Authority Information Access extension that contains an OCSP URL, an alternative revocation checking method should be configured.

AMQ9287: Invalid certificate validation policy.
Severity: 30 : Error
Explanation: An SSL or TLS channel running on an MQ client has failed to start. This is because the MQCERTVPOL environment variable, or the MQSCO CertificateValPolicy field, contains an invalid value. The value specified was <insert_3>.
The channel is <insert_4>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.
Response: Set the MQCERTVPOL environment variable, or the MQSCO CertificateValPolicy field, to a valid value. Restart the channel.
Refer to the IBM MQ Security documentation for more information on certificate validation policy configuration.

AMQ9288: Secure data transfer limit for channel <insert_3> exceeded.
Severity: 30 : Error
Explanation: CipherSpec <insert_4> has reached a data transfer limit of <insert_2> (the transfer limit is expressed in terms of TLS records for GCM ciphers, or MB for all other ciphers). Session keys using this CipherSpec must be used only to encrypt a limited quantity of data to reduce the risk of key compromise.
The channel <insert_3> terminated because it exceeded the allowed data transfer limit for its CipherSpec.
Response: This error can be avoided in one of the following ways:
(a) Use secret key reset to ensure that the session key is reset before the data transfer limit is exceeded.
(b) Use a stronger CipherSpec which is not subject to a data transfer limit.

AMQ9289: Message move complete - no messages moved.
Severity: 0 : Informational
Explanation: No messages were moved whilst switching the XMITQ for cluster sender channel <insert_3>. The message move operation is complete.
Response: None.

AMQ9290: Message move in progress - <insert_1> messages moved.
Severity: 0 : Informational
Explanation: <insert_1> messages were moved whilst switching the XMITQ for cluster sender channel <insert_3>. The message move operation is in progress.
Response: None.

AMQ9291: Message move complete - <insert_1> messages moved.
Severity: 0 : Informational
Explanation: <insert_1> messages were moved whilst switching the XMITQ for cluster sender channel <insert_3>. The message move operation is complete.
Response: None.

AMQ9292: Switch to transmission queue <insert_5> is pending for channel <insert_3> but the current transmission queue <insert_4> could not be accessed due to error code <insert_1>.
Severity: 20 : Error
Explanation: The current transmission queue for the channel could not be accessed for the given reason code. In order to switch the transmission queue for a channel it must be possible to access the original transmission queue or you must elect to switch transmission queue without moving messages.
Response: Restore access to the original transmission queue or issue the command using the '-n' parameter.

AMQ9296: Password protection negotiation failed.
Severity: 30 : Error
Explanation: The channel <insert_3> could not be established because it failed to agree a password protection algorithm with the remote machine <insert_5>.
The channel did not start.
Response: Check whether the PasswordProtection attribute in the Channels stanza of <insert_4> prevents interoperability with the remote machine. Consider changing the PasswordProtection attribute.
Alternatively, consider using SSL or TLS to protect passwords instead. You must use a non-null CipherSpec to protect passwords.

AMQ9401: Channel <insert_3> autodefined.
Severity: 0 : Informational
Explanation: Channel <insert_3> which did not previously exist has been autodefined.
Response: None.

AMQ9402: Autodefinition exit for channel <insert_3> failed to load.
Severity: 30 : Error
Explanation: Autodefinition of channel <insert_3> failed because <insert_4> would not load.
Response: Ensure that the user exit is specified correctly in the queue manager definition, and that the user exit program is correct and available.

AMQ9403: Autodefinition of channel <insert_3> suppressed by user exit.
Severity: 30 : Error
Explanation: Autodefinition exit <insert_4> for channel <insert_3> returned a failure code.
Response: None.

AMQ9404: Phase one of REFRESH CLUSTER REPOS(YES) has completed.
Severity: 0 : Informational
Explanation: Phase one of REFRESH CLUSTER REPOS(YES) has completed. The Refresh Cluster(<insert_4>) command caused <insert_1> objects to be refreshed and republished to <insert_2> queue managers. Applications attempting to access cluster resources may see failures to resolve cluster resources until phase two of REFRESH CLUSTER is complete. Phase two is complete once all new information has been received from other members of the cluster. Monitor your SYSTEM.CLUSTER.COMMAND.QUEUE to determine when it has reached a consistently empty state to indicate that the refresh process has completed.
Response: None.

AMQ9405: FORCEREMOVE QUEUES(YES) command processed, cluster <insert_3> target <insert_4>.
Severity: 0 : Informational
Explanation: The repository queue manager successfully processed a RESET ACTION(FORCEREMOVE) command with the QUEUES(YES) option for the indicated cluster and target queue manager.
Response: None.

AMQ9406: REFRESH CLUSTER REPOS(YES) command failed, this queue manager is a full repository for cluster <insert_4>.
Severity: 30 : Error
Explanation: The repository queue manager could not process a REFRESH CLUSTER command with the REPOS(YES) option for the indicated cluster, because the local queue manager provides full repository management services for the cluster. The command is ignored.
Response: Either
1) Reissue the command without REPOS(YES), or
2) Issue the command on a queue manager which is not a full repository, or
3) Change this queue manager definition so that it is not a full repository.

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

AMQ9408: BIND_ON_OPEN messages for channel <insert_3> to dead-letter queue.
Severity: 0 : Informational
Explanation: The remote CLUSRCVR for channel <insert_3> was deleted while undelivered BIND_ON_OPEN messages associated with that channel existed on the local SYSTEM.CLUSTER.TRANSMIT.QUEUE. These messages could not be allocated to another channel because they were put BIND_ON_OPEN, but were very unlikely to ever flow along the channel with which they were associated as this has now been deleted. An attempt has therefore been made to move them from the transmission queue to the local dead-letter queue. The MQDLH reason is MQFB_BIND_OPEN_CLUSRCVR_DEL. Note that any internal IBM MQ Clustering messages for the deleted channel will also have been removed from the SYSTEM.CLUSTER.TRANSMIT.QUEUE (these are discarded) so the current depth of the queue may have decreased by more than the number of user messages moved to the dead-letter queue.
Response: Examine the contents of the dead-letter queue. Each message is contained in an MQDLH structure that includes the reason why it was written and where it was originally addressed. Also look at previous error messages to see if the attempt to put messages to the dead-letter queue failed.

AMQ9409: Repository manager ended abnormally.
Severity: 30 : Error
Explanation: The repository manager process ended abnormally. Termination of this process will cause the queue manager to terminate unless the tuning parameter TolerateRepositoryFailure has been set to 'TRUE'. If the queue manager does not terminate, further cluster management activity will not occur, this will effect the availability of cluster resources accessed or hosted by this queue manager.
Response: Look at previous error messages for the repository manager in the queue manager and system error logs to determine the cause of the failure or contact your IBM support center. Restart the queue manager to restart the repository manager process.

AMQ9410: Repository manager started.
Severity: 0 : Informational
Explanation: The repository manager started successfully.
Response: None.

AMQ9411: Repository manager ended normally.
Severity: 0 : Informational
Explanation: The repository manager ended normally.
Response: None.

AMQ9412: Repository command received for <insert_3>.
Severity: 30 : Error
Explanation: The repository manager received a command intended for some other queue manager, whose identifier is <insert_3>. The command was sent by the queue manager with identifier <insert_4>.
Response: Check the channel and cluster definitions of the sending queue manager.

AMQ9413: Repository command format error, command code <insert_1>
Severity: 30 : Error
Explanation: An internal error has occurred.
Response: Collect the items listed in the 'Problem determination' section of the System Administration manual and use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.

AMQ9415: Repository command unexpected, command code <insert_1>, cluster object <insert_3>, sender <insert_4>
Severity: 30 : Error
Explanation: An internal error has occurred.
Response: Collect the items listed in the 'Problem determination' section of the System Administration manual and use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.

AMQ9415 (IBM i): An internal error has occurred.
Severity: 30 : Error
Explanation: Repository command unexpected, command code <insert_1>, cluster object <insert_3>, sender <insert_4>
Response: Collect the items listed in the 'Problem determination' section of the System Administration manual and use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.

AMQ9416: Repository command processing error, RC=<insert_2>, command code <insert_1>, cluster object <insert_3>, sender <insert_4>.
Severity: 30 : Error
Explanation: An internal error has occurred.
Response: Collect the items listed in the 'Problem determination' section of the System Administration manual and use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.

AMQ9416 (IBM i): An internal error has occurred.
Severity: 30 : Error
Explanation: Repository command processing error, RC=<insert_2>, command code <insert_1>, cluster object <insert_3>, sender <insert_4>.
Response: Collect the items listed in the 'Problem determination' section of the System Administration manual and use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.

AMQ9417: Manually defined CLUSSDR channels have been forcibly removed.
Severity: 0 : Informational
Explanation: The administrator has asked for the queue manager <insert_3> to be deleted, or forcibly removed, but has not yet deleted the manually defined CLUSSDR channels to <insert_3>. The auto-defined channels to <insert_3> have been deleted, but <insert_3> continues to receive updates until the manually defined CLUSSDR channels have been deleted.
Response: Delete the manually defined CLUSSDR channels to <insert_3>.

AMQ9418: Only one full repository for cluster <insert_3> has been defined.
Severity: 0 : Informational
Explanation: The queue manager has received information about a cluster for which it is the only full repository. It is recommended for fault tolerance and availability reasons that every cluster has two queue managers defined as full repositories.
Response: Configure a second queue manager in the cluster to be a full repository and define a cluster sender channel from that queue manager to this queue manager and vice versa.

AMQ9419: No cluster-receiver channels for cluster <insert_3>
Severity: 0 : Informational
Explanation: The repository manager has received information about a cluster for which no cluster-receiver channels are known.
Response: Define cluster-receiver channels for the cluster on the local queue manager.

AMQ9420: No repositories for cluster <insert_3>.
Severity: 0 : Informational
Explanation: The queue manager has received information about a cluster for which no repositories are known.
Response: Alter the REPOS or REPOSNL attribute of the queue manager, that is to have a full repository for the cluster, to specify the cluster name.

AMQ9421: Invalid cluster record action code detected
Severity: 30 : Error
Explanation: An invalid record was read from the SYSTEM.CLUSTER.REPOSITORY.QUEUE. An FFST record has been generated containing the invalid record.
Response: Collect the items listed in the Problem Determination section of the System Administration manual and use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.

AMQ9422: Repository manager error, RC=<insert_1>
Severity: 30 : Error
Explanation: An internal error has occurred.
Response: Collect the items listed in the 'Problem determination' section of the System Administration manual and use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.

AMQ9425: An internal error has occurred.
Severity: 30 : Error
Explanation: Repository command merge error, command code <insert_1>, cluster object <insert_3>, sender <insert_4>
Response: Collect the items listed in the 'Problem determination' section of the System Administration manual and use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.

AMQ9426: Repository command recipient unknown.
Severity: 30 : Error
Explanation: The repository manager tried to send a command to another queue manager using channel <insert_4>. The recipient queue manager, whose identifier is <insert_3>, could not be found. Command code <insert_1>.
Response: Check the channel and cluster definitions of the sending and receiving queue managers.

AMQ9427: CLUSSDR channel does not point to a repository queue manager.
Severity: 30 : Error
Explanation: A CLUSSDR channel must point to a queue manager that hosts repositories for all clusters of which the channel is a member. In addition, the CLUSRCVR for the channel must be a member of all the same clusters as the CLUSSDR channel. The queue manager pointed to by CLUSSDR channel <insert_3> does not meet these criteria for cluster <insert_4>. The remote queue manager has a QMID of <insert_5>.
Response: Check the definitions on the local and remote queue managers to ensure that the CLUSSDR channel points to a queue manager that hosts a repository for the cluster, and that the CLUSRCVR for the channel is a member of the cluster.

AMQ9428: Unexpected publication of a cluster queue object received.
Severity: 30 : Error
Explanation: The local queue manager has received a publication of a cluster queue object from a remote queue manager on cluster <insert_3>. The local queue manager discards the request because it does not host a repository for cluster <insert_3> and has not subscribed to the published object. The remote CLUSSDR channel used to access the local queue manager has a channel name of <insert_4> and the remote queue manager has a QMID of <insert_5>.
Response: Check the definitions on the local and remote queue managers to ensure that the CLUSSDR channel points to a repository queue manager for the cluster.

AMQ9429: Unexpected publication of a cluster queue deletion received.
Severity: 30 : Error
Explanation: The local queue manager has received a publication of a cluster queue deletion from a remote queue manager on cluster <insert_3>. The local queue manager discards the request because it does not host a repository for cluster <insert_3> and has not subscribed to the published object. The remote CLUSSDR channel used to access the local queue manager has a channel name of <insert_4> and the remote queue manager has a QMID of <insert_5>.
Response: Check the definitions on the local and remote queue managers to ensure that the CLUSSDR channel points to a repository queue manager for the cluster.

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

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

AMQ9432: Query received by a non-repository queue manager
Severity: 30 : Error
Explanation: The local queue manager has received a query from a remote queue manager on cluster <insert_3>. The local queue manager discards the query because it does not host a repository for cluster <insert_3>. The remote CLUSSDR channel used to access the local queue manager has a channel name of <insert_4> and the remote queue manager has a QMID of <insert_5>.
Response: Check the definitions on the local and remote queue managers to ensure that the CLUSSDR channel points to a repository queue manager for the cluster.

AMQ9433: CLUSRCVR must be in the same cluster as its matching CLUSSDR.
Severity: 30 : Error
Explanation: CLUSRCVR channel <insert_3> is not defined as a member of cluster <insert_4>. The local queue manager has received a command that indicates that CLUSSDR channel <insert_3> on the remote queue manager with QMID <insert_5> is defined as a member of cluster <insert_4>.
Response: Alter the CLUSRCVR or CLUSSDR definitions for channel <insert_3>, so that they are both members of the same cluster.

AMQ9434: Unrecognized message on <insert_3>.
Severity: 30 : Error
Explanation: The repository manager found a message on one of its queues having, either a format that could not be recognized, or that did not come from a queue manager or repository manager. The message was put on the dead-letter queue.
Response: Examine the message on the dead-letter queue to determine the originator of the message.

AMQ9435: Unable to put repository manager message.
Severity: 30 : Error
Explanation: The repository manager tried to send a message to the SYSTEM.CLUSTER.COMMAND.QUEUE on another queue manager whose identifier is <insert_3>, but the MQPUT call was unsuccessful. MQCC=<insert_1>, MQRC=<insert_2>. Processing continues, but the repository information may be out of date.
Response: Refer to the Application Programming Reference manual for information about MQCC <insert_1> and MQRC <insert_2>. Check the channel and cluster definitions on the local and target queue managers, and ensure that the channels between them are running. When the problem is corrected, the repository information will normally be updated automatically. The REFRESH CLUSTER command can be used to ensure that the repository information is up to date.

AMQ9436: Unable to send repository manager message.
Severity: 30 : Error
Explanation: The repository manager tried to send a message to the SYSTEM.CLUSTER.COMMAND.QUEUE on a queue manager that has the full repository for the specified cluster(<insert_3>), but the MQPUT call was unsuccessful. MQCC=<insert_1>, MQRC=<insert_2>. Processing continues, but repository information may be out of date.
Response: Refer to the Application Programming Reference manual for information about MQCC <insert_1> and MQRC <insert_2>. Check the channel and cluster definitions on the local and target queue managers, and ensure that the channels between them are running. When the problem is corrected, the repository information will normally be updated automatically. The REFRESH CLUSTER command can be used to ensure that the repository information is up to date.

AMQ9437: Unable to commit repository manager changes.
Severity: 20 : Error
Explanation: The repository manager tried to commit some internal operations but was unsuccessful. The reason code from the MQCMIT call was <insert_1>.
Response: Inspect the reason code. If it does not seem reasonable in the context of the other queue manager operations taking place at the time, then save any generated output files and use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.

AMQ9438: CONNAME could not be discovered for CLUSRCVR <insert_3>.
Severity: 30 : Error
Explanation: TCP/IP CLUSRCVR <insert_3> was validly specified with a blank or absent CONNAME parameter. However when the repository process, amqrrmfa, attempted to obtain the CONNAME (IP address) for itself it was unable to. If there is an existing matching CLUSRCVR object in the cache its CONNAME is used. The CONNAME used was <insert_4>.
Response: Check the error log for a message arising from an associated TCP/IP call (gethostname, gethostbyname or inet_ntoa). Pass all the error information to your systems administrator.

AMQ9439: Repository corruption: bad CLQMGR object for channel <insert_3>.
Severity: 30 : Error
Explanation: An internal error has occurred.
Response: Collect the items listed in the 'Problem determination' chapter in the System Administration guide and use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.

AMQ9440: Reset command failed.
Severity: 0 : Informational
Explanation: RESET CLUSTER(<insert_3>) QMNAME(<insert_4>) command failed. To issue this command, queue manager <insert_5> must be a repository for cluster <insert_3>. Alter the queue manager attributes REPOS, or REPOSNL, to include cluster <insert_3> and retry the command.
Response: None.

AMQ9441: Reset command processed.
Severity: 0 : Informational
Explanation: The reset Cluster(<insert_3>) Qmname(<insert_4>) command has processed on this repository and <insert_1> other queue managers have been sent notification.
Response: None.

AMQ9442: Phase one of REFRESH CLUSTER has completed.
Severity: 0 : Informational
Explanation: Phase one of REFRESH CLUSTER has completed. The Refresh Cluster(<insert_4>) command caused <insert_1> objects to be refreshed and republished to <insert_2> queue managers. Applications attempting to access cluster resources may see failures to resolve cluster resources until phase two of REFRESH CLUSTER is complete. Phase two is complete once all new information has been received from other members of the cluster. Monitor your SYSTEM.CLUSTER.COMMAND.QUEUE to determine when it has reached a consistently empty state to indicate that the refresh process has completed.
Response: None.

AMQ9443: Suspend Qmgr Cluster command processed.
Severity: 0 : Informational
Explanation: The Suspend Qmgr Cluster(<insert_4>) command completed. <insert_1> objects suspended. In the case of suspending a list of clusters, the cluster name shown is the first name in the list.
Response: None.

AMQ9444: Resume Qmgr Cluster command processed.
Severity: 0 : Informational
Explanation: The Resume Qmgr Cluster(<insert_4>) command completed. <insert_1> objects resumed. In the case of resuming a list of clusters, the cluster name shown is the first name in the list.
Response: None.

AMQ9445: Error creating channel <insert_3>.
Severity: 30 : Error
Explanation: Channel <insert_4> tried to replace itself by creating channel <insert_3>. The attempt to create the channel was unsuccessful for the following reason: "<insert_5>". A previous message may give further information.
Response: Rectify the problem which prevented successful creation of channel <insert_3>. Restart channel <insert_4>.

AMQ9446: Error deleting channel <insert_3>.
Severity: 30 : Error
Explanation: Channel <insert_3> tried to delete itself after creating channel <insert_4> to replace it. The attempt to delete the channel was unsuccessful for the following reason: "<insert_5>".
Response: If channel <insert_3> still exists rectify the problem which prevented its deletion and then manually delete the channel.

AMQ9447: Unable to backout repository manager changes.
Severity: 20 : Error
Explanation: The repository manager tried to back out some internal operations but was unsuccessful. The reason code from the MQBACK call was <insert_1>.
Response: Inspect the reason code. If it does not seem reasonable in the context of the other queue manager operations taking place at the time, then save any generated output files and use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.

AMQ9448: Repository manager failed. Retry in <insert_1> minutes, queue manager will terminate in <insert_2> minutes
Severity: 30 : Error
Explanation: Repository manager encountered a severe problem. See the earlier messages in the queue manager or system error logs for details. The repository manager will retry the command in <insert_1> minutes. If the problem is not rectified in <insert_2> minutes the queue manager will terminate. Until this problem is rectified no further cluster management activity will occur, this will affect the availability of cluster resources accessed or hosted by this queue manager.
Response: If possible, rectify the identified problem, otherwise contact your IBM support center. To postpone the queue manager from terminating due to this problem set the SYSTEM.CLUSTER.COMMAND.QUEUE queue to be GET(DISABLED). Once the problem has been rectified, set the queue to be GET(ENABLED) and wait for the repository manager to retry the command or restart the queue manager.

AMQ9449: The repository manager is restarting following an error.
Severity: 0 : Informational
Explanation: The repository manager is restarting following an error, see earlier error messages for details of the failure.
Response: If the failure re-occurs contact your IBM support center and follow any instructions in the subsequent error messages.

AMQ9450: Usage: <insert_3> [-m QMgrName] -f OutputFile [-v OutputFileVersion]
Severity: 10 : Warning
Explanation: Values passed to the channel table writer program were invalid.
The parameter string passed to this program is as follows:
[-m QMgrName] -f OutputFile [-v OutputFileVersion]

where OutputFileVersion can be either 2 or 5 (5 is the default)
Default values will be used for parameters not supplied.
Response: Correct the parameters passed to the channel table writer program and retry the operation.

AMQ9453: FORCEREMOVE command failed, cluster <insert_3> target <insert_4> is not unique.
Severity: 0 : Informational
Explanation: The repository queue manager could not process a RESET ACTION(FORCEREMOVE) command for the indicated cluster and target queue manager, because there is more than one queue manager with the specified name in the cluster. The command is ignored.
Response: Reissue the command specifying the identifier (QMID) of the queue manager to be removed, rather than its name.

AMQ9455: FORCEREMOVE command failed, cluster <insert_3>, target <insert_4>, not found.
Severity: 0 : Informational
Explanation: The repository queue manager could not process a RESET ACTION(FORCEREMOVE) command for the indicated cluster and target queue manager, because no information about that queue manager was found in the local repository. The command is ignored.
Response: Reissue the command, specifying the correct queue manager name or identifier.

AMQ9456: Update not received for object <insert_3>, queue manager <insert_4> from full repository for cluster <insert_5>.
Severity: 0 : Informational
Explanation: The repository manager detected a cluster object that had been used sometime 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 object for a further 60 days from when the error first occurred.
Response: There are several possible responses:
1) There is a long-running problem with the local queue manager's CLUSRCVR in cluster <insert_5>. If this is true, then correct the problem urgently, to ensure that updates for the cluster are received.
2) There is a long-running problem on the remote queue manager's CLUSSDR in cluster <insert_5>. If this is true, then correct the problem urgently, to ensure that updates for the cluster are sent.
3) Check that the repository manager on the remote queue manager has not ended abnormally.
4) The remote queue manager is out of step with this queue manager, potentially due to a restore of the remote queue manager from a backup. The remote queue manager must issue REFRESH CLUSTER to synchronize with other queue managers in the cluster.
5) The remote queue manager is out of step with this queue manager, potentially due to a Disaster Recovery exercise in which a replacement queue manager with the same CLUSRCVR channel name was created, was run for a while, then ended. If this has happened, then the remote queue manager <insert_4> must now issue REFRESH CLUSTER to synchronize with other queue managers in the cluster.
6) If the above items have been checked, and this problem persists over several days (causing repeats of this error message in the local queue manager's error logs) then contact your IBM support center.

AMQ9457: Repository available, cluster <insert_4>, channel <insert_5>, sender <insert_3>.
Severity: 0 : Informational
Explanation: The repository queue manager received a command from another queue manager, whose identifier is <insert_3>, reporting that it is again a repository for cluster <insert_4>. The cluster-sender channel <insert_5> is changed so that it can be used to access the other queue manager in relation to the the cluster.
Response: None.

AMQ9458: Unable to access the repository cache exclusively.
Severity: 30 : Error
Explanation: A process remains registered as requiring access to the repository cache during an operation that must have exclusive access to the cache. The queue manager <insert_3> issues this message after waiting for the process to remove its registration, but the registration is still present. The process preventing exclusive access to the repository cache has <insert_2> outstanding registrations.
Response: The registered process identifier (PID) accessing the repository cache is <insert_1>. Determine if this process is still running or terminated. If the process is not running or if the problem persists collect the items listed in the 'Problem determination' section of the System Administration manual and contact your IBM support center.

AMQ9459: Cluster topic <insert_3> from <insert_4> rejected due to PSCLUS(DISABLED)
Severity: 10 : Warning
Explanation: Queue manager attribute PSCLUS has been set to DISABLED to indicate that Publish/Subscribe activity is not expected between queue managers in this cluster. However, information regarding cluster topic <insert_3> has been sent to this queue manager over a channel from <insert_4>. The cluster topic definition is ignored and will not be visible from this queue manager.
Response: If you wish to enable publish/subscribe clustering, alter the PSCLUS attribute on all queue managers in the cluster to ENABLED. You may also need to issue REFRESH CLUSTER and REFRESH QMGR commands as detailed in the PSCLUS documentation. If you are not using publish/subscribe clusters you should delete the clustered topic object, and ensure PSCLUS is DISABLED on all queue managers.

AMQ9461: Internal record for cluster object name <insert_3> has been checked and found to have incorrect contents
Severity: 0 : Informational
Explanation: Internal checks for data consistency have found a problem with object name <insert_3>. Please contact your IBM Support representative.
Response: Keep this error message and provide it to your IBM Support representative. An additional command amqrfdm -mQMNAME -b can also be run, and this will dump extra data into FFST records. Again, provide these to IBM Support.

AMQ9465: New cluster topic definition inconsistent.
Severity: 10 : Warning
Explanation: The definition of cluster topic <insert_3> on the queue manager with UUID <insert_4> has a different <insert_5> attribute value than one or more cluster topics that already exist in the cluster cache. The existing topic objects are reported by message AMQ9466. All definitions of the same cluster topic should be identical, otherwise, problems may arise if your applications rely on one of these attributes to determine messaging behavior. For example, if an application opens a cluster topic and the different instances of the topic have different TOPICSTR values, the behavior of the message transfer depends on which instance of the topic happens to be selected when it is opened.
Response: Alter the definitions of the topic on the various queue managers so that they have identical values for all attributes.

AMQ9466: Cluster topic definitions inconsistent.
Severity: 10 : Warning
Explanation: The definition of cluster topic <insert_3> on the queue manager with UUID <insert_4> has a different <insert_5> attribute value than a cluster topic being added to the cluster cache. The topic object being added is reported by message AMQ9465. All definitions of the same cluster topic should be identical, otherwise, problems may arise if your applications rely on one of these attributes to determine messaging behavior. For example, if an application opens a cluster topic and the different instances of the topic have different TOPICSTR values, the behavior of the message transfer depends on which instance of the topic happens to be selected when it is opened.
Response: Alter the definitions of the topic on the various queue managers so that they have identical values for all attributes.

AMQ9467: Repository error updating topic
Severity: 20 : Error
Explanation: The cluster repository manager received an unexpected error code from the queue manager while updating topic <insert_3>. The Completion code was <insert_1>, reason code was <insert_2>.
Response: Refer to the IBM MQ product documentation about reason code <insert_2>. Collect the items listed in the Troubleshooting and support section of the IBM MQ product documentation, and use either the IBM MQ Support site, or the IBM Support Assistant (ISA), to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.

AMQ9468: Cluster receiver channel <insert_3> has been configured by multiple queue managers
Severity: 0 : Informational
Explanation: Queue manager <insert_4> has joined a cluster using a cluster receiver channel with the same name as one that has already been defined by queue manager <insert_5>. All cluster receiver channels used within a cluster must be uniquely named. Only the last queue manager to join the cluster will use the named channel, Queue manager <insert_5> will not successfully participate in the cluster while the newer queue manager is a member.
Response: The use of a channel name currently associated with a different queue manager in the cluster may be intentional, for example the original queue manager may have been deleted and re-created as a new queue manager. However, accidental duplication of a channel name across multiple queue managers would also result in this behaviour. If this was not intended, further investigation into the configuration of the queue managers should be performed.

AMQ9469: Update not received for CLUSRCVR channel <insert_3> hosted on queue manager <insert_4> in cluster <insert_5>.
Severity: 10 : Warning
Explanation: The repository manager detected that the CLUSRCVR channel has not been re-published by its owning queue manager. This re-publish action should have happened automatically <insert_1> days ago, or in the time between then and now.
The repository manager will check for this condition approximately every hour, continuing for a period of approximately <insert_2> days from now. If an update for the CLUSRCVR channel is received during this period, these messages will stop. If no update is received, these messages will continue to be written. However, after this period has elapsed, if no update has been received, the local queue manager will discard its knowledge of this channel, and these messages will stop. You should be aware that Partial Repository queue managers in this cluster will cease to be able to use the channel at about that time.
Response: There are several possible responses:
1) If the channel had been removed intentionally, and is no longer required, you should consider removing it fully via the RESET CLUSTER command.
2) There is a long-running problem with the local queue manager's CLUSRCVR in cluster <insert_5>. If this is true, then correct the problem urgently, to ensure that updates for the cluster are received.
3) There is a long-running problem on the remote queue manager's CLUSSDR in cluster <insert_5>. If this is true, then correct the problem urgently, to ensure that updates for the cluster are sent.
4) Check that the repository manager on the remote queue manager has not ended abnormally.
5) The remote queue manager is out of step with this queue manager, potentially due to a restore of the remote queue manager from a backup. The remote queue manager must issue REFRESH CLUSTER to synchronize with other queue managers in the cluster.
6) The remote queue manager is out of step with this queue manager, potentially due to a Disaster Recovery exercise in which a replacement queue manager with the same CLUSRCVR channel name was created, was run for a while, then ended. If this has happened, then the remote queue manager <insert_4> must now issue REFRESH CLUSTER to synchronize with other queue managers in the cluster.
7) If the above items have been checked, and this problem persists over several days (causing repeats of this error message in the local queue manager's error logs) then contact your IBM support center.

AMQ9487: Remote queue manager is a standby queue manager instance.
Severity: 30 : Error
Explanation: Channel <insert_3> is closing because the remote queue manager at address <insert_5> is currently a standby queue manager instance.
Response: None.

AMQ9488: Program cannot connect to a standby queue manager instance.
Severity: 30 : Error
Explanation: The connection attempt to queue manager <insert_4> failed with reason code <insert_1> because it is a standby queue manager instance.
Response: Standby queue manager instances do not accept connections. Connect to the active queue manager instance instead.

AMQ9489: The maximum number of instances, <insert_1>, of channel <insert_3> was reached.
Severity: 30 : Error
Explanation: The server-connection channel <insert_3> is configured so that the maximum number of instances that can run at the same time is <insert_1>. This limit was reached.
Response: Try the operation again when a new instance can be started.
If the limit has been reached because there are too many connections from one or more of your client applications, consider changing the applications to make fewer connections.
If you are not making use of sharing conversations, consider switching to this mode of operation because several client connections can then share one channel instance.

AMQ9490: The maximum number of instances, <insert_1>, of channel <insert_3> was reached for an individual client.
Severity: 30 : Error
Explanation: The server-connection channel <insert_3> is configured so that the maximum number of instances that can run at the same time for any individual client is <insert_1>. This limit was reached for the client with remote network address <insert_4>.
Response: Try the operation again when a new instance can be started for this client.
If the limit has been reached because there are too many connections from the relevant client application, consider changing the application to make fewer connections.
If you are not making use of sharing conversations, consider switching to this mode of operation because several client connections can then share one channel instance.

AMQ9491: Transmission queue <insert_3> set to NOSHARE.
Severity: 20 : Error
Explanation: The channel <insert_4> on queue manager <insert_5> cannot start because this queue manager has a setting for PipeLineLength greater than 1, and so multiple threads will run in this channel's MCA. Only the first thread would be able to open the transmission queue <insert_3> because it is set to be non-shareable.
Response: Check the definition of the transmission queue <insert_3> on queue manager <insert_5> and set it to be SHARE instead of NOSHARE. Alternatively, you can set all channels on this queue manager to use only a single thread, by using the PipeLineLength parameter.

AMQ9492: The <insert_3> responder program encountered an error.
Severity: 30 : Error
Explanation: The responder program was started but detected an error.
The host name was <insert_5>; in some cases the host name cannot be determined and so is shown as '????'.
Response: Look at previous error messages in the error files to determine the error encountered by the responder program.

AMQ9494: A protocol error was detected for channel <insert_3>.
Severity: 30 : Error
Explanation: During communications with the remote queue manager, a TCP/IP read and receive call returned EINTR, indicating that it had been interrupted. Immediately after this the channel program detected a protocol error. The failure type was <insert_1> with associated data of <insert_2>.
Response: If you are running an AIX client you will avoid problems arising from EINTRs on TCP/IP reads, by writing your application so that system calls interrupted by signals are restarted. You must establish the signal handler with sigaction(2) and set the SA_RESTART flag in the sa_flags field of the new action structure. If you are running on a platform other than AIX, an AIX server, or an AIX client with an application that adheres to the restart guidelines provided above, contact the systems administrator who should examine the error logs to determine the cause of the failure.

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

AMQ9496: Channel ended by a remote exit.
Severity: 30 : Error
Explanation: Channel program <insert_3> was ended because the channel exit at the remote host <insert_4> requested it.
Response: Examine the error logs at the remote end of the channel to see the reason why the remote exit ended the channel.

AMQ9498: The MQCD structure supplied was not valid.
Severity: 30 : Error
Explanation: The value of the <insert_3> field has the value <insert_4>. This value is invalid for the operation requested.
Response: Change the parameter and retry the operation.

AMQ9499: An IBM MQ listener will end shortly.
Severity: 0 : Informational
Explanation: One listener detected in the system is scheduled for shutdown.
Response: None.

AMQ9500: No Repository storage
Severity: 10 : Warning
Explanation: An operation failed because there was no storage available in the repository. An attempt was made to allocate <insert_1> bytes from <insert_3>.
Response: Reconfigure the Queue Manager to allocate a larger repository.

AMQ9501: Usage: <insert_3> [-m QMgrName] -c ChlName
-c Channel name.
-m Queue manager name.
Severity: 10 : Warning
Explanation: This shows the correct usage.
Response: Correct the parameters passed to the channel program and retry the operation.

AMQ9502: Type of channel not suitable for action requested.
Severity: 30 : Error
Explanation: The operation requested cannot be performed on channel <insert_3>. Some operations are only valid for certain channel types. This channel is a <insert_4> channel type. For example, you can only ping or trigger a channel from the initiating end.
Response: Check whether the channel name is specified correctly. If it is check that the channel has been defined correctly.

AMQ9503: Channel negotiation failed.
Severity: 30 : Error
Explanation: Channel <insert_3> between this machine and the remote machine <insert_4> could not be established due to a negotiation failure. In some cases the channel name can not be determined and so is shown as '????'.
The last control data received was type <insert_1> with associated error code <insert_2>.
Response: Tell the systems administrator, who should attempt to identify the cause of the channel failure using problem determination techniques. For example, look for FFST files, and examine the error logs on the local and remote systems where there may be messages explaining the cause of failure. More information may be obtained by repeating the operation with tracing enabled.

AMQ9504: A protocol error was detected for channel <insert_3>.
Severity: 30 : Error
Explanation: During communications with the remote queue manager, the channel program detected a protocol error. The failure type was <insert_1> with associated data of <insert_2>.
Response: Contact the systems administrator who should examine the error logs to determine the cause of the failure.

AMQ9505: Channel sequence number wrap values are different.
Severity: 30 : Error
Explanation: The sequence number wrap value for channel <insert_3> is <insert_1>, but the value specified at the remote location is <insert_2>. The two values must be the same before the channel can be started.
Response: Change either the local or remote channel definitions so that the values specified for the message sequence number wrap values are the same.

AMQ9506: Message receipt confirmation failed.
Severity: 30 : Error
Explanation: Channel <insert_3> has ended because the remote queue manager on host <insert_4> did not accept the last batch of messages.
Response: The error log for the channel at the remote site will contain an explanation of the failure. Contact the remote Systems Administrator to resolve the problem.

AMQ9507: Channel <insert_3> is currently in-doubt.
Severity: 30 : Error
Explanation: The requested operation cannot complete because the channel is in-doubt with host <insert_4>.
Response: Examine the status of the channel, and either restart a channel to resolve the in-doubt state, or use the RESOLVE CHANNEL command to correct the problem manually.

AMQ9508: Program cannot connect to the queue manager.
Severity: 30 : Error
Explanation: The connection attempt to queue manager <insert_4> failed with reason code <insert_1>.
Response: Ensure that the queue manager is available and operational.

AMQ9509: Program cannot open queue manager object.
Severity: 30 : Error
Explanation: The attempt to open either the queue or queue manager object <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.
Response: Ensure that the queue is available and retry the operation.

AMQ9510: Messages cannot be retrieved from a queue.
Severity: 30 : Error
Explanation: The attempt to get messages from queue <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.
Response: If the reason code indicates a conversion problem, for example MQRC_SOURCE_CCSID_ERROR, remove the message(s) from the queue. Otherwise, ensure that the required queue is available and operational.

AMQ9511: Messages cannot be put to a queue.
Severity: 30 : Error
Explanation: The attempt to put messages to queue <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.
Response: Ensure that the required queue is available and operational.

AMQ9512: Ping operation is not valid for channel <insert_3>.
Severity: 30 : Error
Explanation: Ping may only be issued for SENDER, SERVER or CLUSSDR channel types.
Response: If the local channel is a receiver channel, you must issue the ping from the remote queue manager.

AMQ9513: Maximum number of channels reached.
Severity: 30 : Error
Explanation: The maximum number of channels that can be in use simultaneously has been reached. The current defined maximum number of channels is <insert_1>. The number of permitted channels is a configurable parameter in the queue manager configuration file.
Response: Wait for some of the operating channels to close. Retry the operation when some channels are available.

AMQ9514: Channel <insert_3> is in use.
Severity: 30 : Error
Explanation: The requested operation failed because channel <insert_3> is currently active.
Response: Either end the channel manually, or wait for it to close, and retry the operation.

AMQ9515: Channel <insert_3> changed.
Severity: 10 : Warning
Explanation: The statistics shown are for the channel requested, but it is a new instance of the channel. The previous channel instance has ended.
Response: None.

AMQ9516: File error occurred for file <insert_3>.
Severity: 30 : Error
Explanation: The filesystem returned error code <insert_1> for file <insert_3>.
Response: Record the name of the file and tell the systems administrator, who should ensure that file is correct and available, for example that the current user has appropriate access to the file for reading or writing.

AMQ9516 (IBM i): File error occurred.
Severity: 30 : Error
Explanation: The filesystem returned error code <insert_4> for file <insert_3>.
Response: Record the name of the file <insert_3> and tell the systems administrator, who should ensure that file <insert_3> is correct and available.

AMQ9517: File damaged.
Severity: 30 : Error
Explanation: The program has detected damage to the contents of file <insert_3>.
Response: Record the values and tell the systems administrator who must restore a saved version of file <insert_3>. The return code was <insert_1> and the record length returned was <insert_2>.

AMQ9518: File <insert_3> not found.
Severity: 30 : Error
Explanation: The program requires that the file <insert_3> is present and available.
Response: This may be caused by invalid values for the optional environment variables MQCHLLIB, MQCHLTAB or MQDATA. If these variables are valid or not set then record the name of the file and tell the systems administrator who must ensure that file <insert_3> is available to the program.

AMQ9519: Channel <insert_3> not found.
Severity: 30 : Error
Explanation: The requested operation failed because the program could not find a definition of channel <insert_3>.
Response: Check that the name is specified correctly and the channel definition is available.

AMQ9520: Channel not defined remotely.
Severity: 30 : Error
Explanation: There is no definition of channel <insert_3> at the remote location.
Response: Add an appropriate definition to the remote hosts list of defined channels and retry the operation. The remote host is <insert_4>.

AMQ9521: Host is not supported by this channel.
Severity: 30 : Error
Explanation: The connection across channel <insert_5> was refused because the remote host <insert_4> did not match the host <insert_3> specified in the channel definition.
Response: Update the channel definition, or remove the explicit mention of the remote machine connection name.

AMQ9522: Error accessing the status table.
Severity: 30 : Error
Explanation: The program could not access the channel status table.
Response: A value of <insert_1> was returned from the subsystem when an attempt was made to access the channel status table. Contact the systems administrator, who should examine the log files to determine why the program was unable to access the status table.

AMQ9523: Remote host detected a protocol error.
Severity: 30 : Error
Explanation: During communications through channel <insert_3>, the remote queue manager channel program detected a protocol error. The failure type was <insert_1> with associated data of <insert_2>.
Response: Tell the systems administrator, who should examine the error files to determine the cause of the failure.

AMQ9524: Remote queue manager unavailable.
Severity: 30 : Error
Explanation: Channel <insert_3> cannot start because the remote queue manager on host <insert_4> is not currently available.
Response: Either start the remote queue manager, or retry the operation later.

AMQ9525: Remote queue manager is ending.
Severity: 30 : Error
Explanation: Channel <insert_3> is closing because the remote queue manager on host <insert_4> is ending.
Response: None.

AMQ9526: Message sequence number error for channel <insert_3>.
Severity: 30 : Error
Explanation: The local and remote queue managers do not agree on the next message sequence number. A message with sequence number <insert_1> has been sent when sequence number <insert_2> was expected. The remote host is <insert_4>.
Response: Determine the cause of the inconsistency. It could be that the synchronization information has become damaged, or has been backed out to a previous version. If the situation cannot be resolved, the sequence number can be manually reset at the sending end of the channel using the RESET CHANNEL command.

AMQ9527: Cannot send message through channel <insert_3>.
Severity: 30 : Error
Explanation: The channel has closed because the remote queue manager cannot receive a message.
Response: Contact the systems administrator who should examine the error files of the remote queue manager, to determine why the message cannot be received, and then restart the channel.

AMQ9528: User requested channel <insert_3> to be stopped.
Severity: 10 : Warning
Explanation: The channel is stopping because of a request by the user.
Response: None.

AMQ9529: Target queue unknown on remote host.
Severity: 30 : Error
Explanation: Communication using channel <insert_3> has ended because the target queue for a message is unknown at the remote host.
Response: Ensure that the remote host contains a correctly defined target queue, and restart the channel.

AMQ9530: Program could not inquire queue attributes.
Severity: 30 : Error
Explanation: The attempt to inquire the attributes of queue <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.
Response: Ensure that the queue is available and retry the operation.

AMQ9531: Transmission queue specification error.
Severity: 30 : Error
Explanation: Queue <insert_4> identified as a transmission queue in the channel definition <insert_3> is not a transmission queue.
Response: Ensure that the queue name is specified correctly. If so, alter the queue usage parameter of the queue to that of a transmission queue.

AMQ9532: Program cannot set queue attributes.
Severity: 30 : Error
Explanation: The attempt to set the attributes of queue <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.
Response: Ensure that the queue is available and retry the operation.

AMQ9533: Channel <insert_3> is not currently active.
Severity: 10 : Warning
Explanation: The channel was not stopped because it was not currently active. If attempting to stop a specific instance of a channel by connection name or by remote queue manager name this message indicates that the specified instance of the channel is not running.
Response: None.

AMQ9534: Channel <insert_3> is currently not enabled.
Severity: 30 : Error
Explanation: The channel program ended because the channel is currently not enabled.
Response: Issue the START CHANNEL command to re-enable the channel.

AMQ9535: User exit not valid.
Severity: 30 : Error
Explanation: Channel program <insert_3> ended because user exit <insert_4> is not valid.
Architecture of the exit library does not match the process's architecture which is <insert_5> bit.
Response: Ensure that the user exit is specified correctly in the channel definition, and that the user exit program is correct and available.

AMQ9535 (IBM i): User exit not valid.
Severity: 30 : Error
Explanation: Channel program <insert_3> ended because user exit <insert_4> is not valid.
Response: Ensure that the user exit is specified correctly in the channel definition, and that the user exit program is correct and available.

AMQ9536: Channel ended by an exit.
Severity: 30 : Error
Explanation: Channel program <insert_3> was ended by exit <insert_4>.
Response: None.

AMQ9537: Usage: <insert_3> [-m QMgrName] [-q InitQ]
-m Queue manager name.
-q Initiation queue name.
Severity: 10 : Warning
Explanation: This shows the correct usage.
Response: Correct the parameters passed to the program and retry the operation.

AMQ9538: Commit control error.
Severity: 30 : Error
Explanation: An error occurred when attempting to start commitment control. Either exception <insert_3> was received when querying commitment status, or commitment control could not be started.
Response: Refer to the error log for other messages pertaining to this problem.

AMQ9539: No channels available.
Severity: 30 : Error
Explanation: The channel initiator program received a trigger message to start an MCA program to process queue <insert_3>. The program could not find a defined, available channel to start.
Response: Ensure that there is a defined channel, which is enabled, to process the transmission queue.

AMQ9540: Commit failed.
Severity: 30 : Error
Explanation: The program ended because return code <insert_1> was received when an attempt was made to commit change to the resource managers. The commit ID was <insert_3>.
Response: Tell the systems administrator.

AMQ9541: CCSID supplied for data conversion not supported.
Severity: 30 : Error
Explanation: The program ended because, either the source CCSID <insert_1> or the target CCSID <insert_2> is not valid, or is not currently supported.
Response: Correct the CCSID that is not valid, or ensure that the requested CCSID can be supported.

AMQ9542: Queue manager is ending.
Severity: 10 : Warning
Explanation: The program will end because the queue manager is quiescing.
Response: None.

AMQ9543: Status table damaged.
Severity: 30 : Error
Explanation: The channel status table has been damaged.
Response: End all running channels and issue a DISPLAY CHSTATUS command to see the status of the channels. Use the standard facilities supplied with your system to record the problem identifier and to save any generated output files. Use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved.

AMQ9544: Messages not put to destination queue.
Severity: 10 : Warning
Explanation: During the processing of channel <insert_3> one or more messages could not be put to the destination queue and attempts were made to put them to a dead-letter queue. The location of the queue is <insert_1>, where 1 is the local dead-letter queue and 2 is the remote dead-letter queue.
Response: Examine the contents of the dead-letter queue. Each message is contained in a structure that describes why the message was put to the queue, and to where it was originally addressed. Also look at previous error messages to see if the attempt to put messages to a dead-letter queue failed. The program identifier (PID) of the processing program was <insert_4>.

AMQ9545: Disconnect interval expired.
Severity: 0 : Informational
Explanation: Channel <insert_3> closed because no messages arrived on the transmission queue within the disconnect interval period.
Response: None.

AMQ9546: Error return code received.
Severity: 30 : Error
Explanation: The program has ended because return code <insert_1> was returned from function <insert_3>
Response: Correct the cause of the failure and retry the operation.

AMQ9547: Type of remote channel not suitable for action requested.
Severity: 30 : Error
Explanation: The operation requested cannot be performed because channel <insert_3> on the remote machine is not of a suitable type. For example, if the local channel is defined as a sender the remote machine must define its channel as either a receiver or requester.
Response: Check that the channel name is specified correctly. If it is, check that the remote channel has been defined correctly.

AMQ9548: Message put to the 'dead-letter queue'.
Severity: 10 : Warning
Explanation: During processing a message has been put to the dead-letter queue.
Response: Examine the contents of the dead-letter queue. Each message is contained in a structure that describes why the message was put to the queue, and to where it was originally addressed.

AMQ9549: Transmission Queue <insert_3> inhibited for MQGET.
Severity: 20 : Error
Explanation: An MQGET failed because the transmission queue had been previously inhibited for MQGET.
Response: None.

AMQ9550: Channel program <insert_3> cannot be stopped at this time.
Severity: 30 : Error
Explanation: The channel program can not be terminated immediately but should end shortly.
Response: If the channel does not end in a short time issue the STOP CHANNEL command again.

AMQ9551: Protocol not supported by remote host.
Severity: 30 : Error
Explanation: The operation you are performing over channel <insert_3> to the host at <insert_4> is not supported by the target host.
Response: Check that the connection name parameter is specified correctly and that the levels of the products in use are compatible.

AMQ9552: Security flow not received.
Severity: 30 : Error
Explanation: During communications through channel <insert_3> the local security exit requested security data from the remote machine. The security data has not been received so the channel has been closed.
Response: Tell the systems administrator who should ensure that the security exit on the remote machine is defined correctly.

AMQ9553: The function is not supported.
Severity: 30 : Error
Explanation: The <insert_3> function <insert_4> attempted is not currently supported on this platform.
Response: None.

AMQ9554: User not authorized.
Severity: 30 : Error
Explanation: You are not authorized to perform the channel operation.
Response: Tell the systems administrator who should ensure that the correct access permissions are available to you, and then retry the operation.

AMQ9555: File format error.
Severity: 30 : Error
Explanation: The file <insert_3> does not have the expected format.
Response: Ensure that the file name is specified correctly.

AMQ9556: Channel synchronization file missing or damaged.
Severity: 30 : Error
Explanation: The channel synchronization file <insert_3> is missing or does not correspond to the stored channel information for queue manager <insert_4>.
Response: Rebuild the synchronization file using the rcrmqobj command rcrmqobj -t syncfile (-m q-mgr-name)

AMQ9556 (IBM i): Channel synchronization file missing or damaged.
Severity: 30 : Error
Explanation: The channel synchronization file <insert_3> is missing or does not correspond to the stored channel information for queue manager <insert_4>.
Response: Rebuild the synchronization file using the RCRMQMOBJ command.

AMQ9557: Queue Manager User ID initialization failed for <insert_3>.
Severity: 30 : Error
Explanation: The call to initialize the User ID <insert_3> failed with CompCode <insert_1> and Reason <insert_2>. If an MQCSP block was used, the User ID in the MQCSP block was <insert_4>.
Response: Correct the error and try again.

AMQ9558: The remote channel <insert_3> on host <insert_4> is not currently available.
Severity: 30 : Error
Explanation: The channel program ended because an instance of channel <insert_3> could not be started on the remote system. This could be for one of the following reasons:
The channel is disabled.
The remote system does not have sufficient resources to run another instance of the channel.
In the case of a client-connection channel, the limit on the number of instances configured for the remote server-connection channel was reached.
Response: Check the remote system to ensure that the channel is able to run. Try the operation again.

AMQ9560: Rebuild Synchronization File - program started
Severity: 0 : Informational
Explanation: Rebuilding the Synchronization file for Queue Manager <insert_3> .
Response: None.

AMQ9561: Rebuild Synchronization File - program completed normally
Severity: 0 : Informational
Explanation: Rebuild Synchronization File program completed normally.
Response: None.

AMQ9562: Synchronization file in use.
Severity: 30 : Error
Explanation: The Synchronization file <insert_3> is in use and cannot be recreated.
Response: Stop any channel activity and retry the rcrmqobj command.

AMQ9562 (IBM i): Synchronization file in use.
Severity: 30 : Error
Explanation: The Synchronization file <insert_3> is in use and cannot be recreated.
Response: Stop any channel activity and retry the RCRMQMOBJ command.

AMQ9563: Synchronization file cannot be deleted
Severity: 30 : Error
Explanation: The filesystem returned error code <insert_1> for file <insert_3>.
Response: Tell the systems administrator who should ensure that file <insert_3> is available and not in use.

AMQ9564: Synchronization File cannot be created
Severity: 30 : Error
Explanation: The filesystem returned error code <insert_1> for file <insert_3>.
Response: Tell the systems administrator.

AMQ9565: No dead-letter queue defined.
Severity: 30 : Error
Explanation: The queue manager <insert_4> does not have a defined dead-letter queue. A message cannot be transferred across channel <insert_5>. The reason code is <insert_1>. The destination queue is <insert_3>.
Response: Either correct the problem that caused the channel to try and write a message to the dead-letter queue or create a dead-letter queue for the queue manager.

AMQ9566: Invalid MQSERVER value
Severity: 30 : Error
Explanation: The value of the MQSERVER environment variable was <insert_3>. The variable should be in the format 'ChannelName/Protocol/ConnectionName'.
Response: Correct the MQSERVER value and retry the operation.

AMQ9567: Unable to convert the user identifier <insert_3> into bytes, using the queue manager requested CCSID <insert_2>.
Severity: 30 : Error
Explanation: Unable to send the user identifier <insert_3> to the queue manager, as it cannot be encoded within the queue manager's CCSID character encoding scheme.
Response: Check that the queue manager CCSID supports the characters used within the user identifier, and consider changing the queue manager's CCSID if appropriate.

AMQ9568: Unable to convert the user password into bytes, using the queue manager character encoding scheme of CCSID <insert_2>.
Severity: 30 : Error
Explanation: Unable to send the user password to the queue manager, as it cannot be encoded into the queue manager's character encoding scheme of CCSID <insert_2>.
Response: Check that the queue manager CCSID supports the characters used within the user password, and consider changing the queue manager's CCSID if appropriate.

AMQ9572: Message header is not valid.
Severity: 30 : Error
Explanation: Channel <insert_3> is stopping because a message header is not valid. During the processing of the channel, a message was found that has a header that is not valid. The dead-letter queue has been defined as a transmission queue, so a loop would be created if the message had been put there.
Response: Correct the problem that caused the message to have a header that is not valid.

AMQ9573: Maximum number of active channels reached.
Severity: 30 : Error
Explanation: There are too many channels active to start another. The current defined maximum number of active channels is <insert_1>.
Response: Either wait for some of the operating channels to close or use the stop channel command to close some channels. Retry the operation when some channels are available. The maximum number of active channels is a configurable parameter in the queue manager configuration file.

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

AMQ9575: Negotiation failed for channel
Severity: 30 : Error
Explanation: A channel between the local queue manager and the remote end could not be established due to a negotiation failure. The failure was such that the channel name could not be determined.
Response: Examine the remote queue manager error logs for messages explaining the cause of the negotiation failure.

AMQ9576: DCE Security: an exit could not allocate memory.
Severity: 30 : Error
Explanation: A DCE exit was unsuccessful in obtaining the memory it needed. The failure occurred in exit function <insert_4>. Channel <insert_3> is closed.
Response: Make more memory available to the IBM MQ system and restart the relevant channel.

AMQ9577: DCE security exit: no partner name.
Severity: 30 : Error
Explanation: Channel <insert_3> has not been opened because the DCE security exit which initiates the security context was not passed a valid partner name. When the DCE security exit is called to initiate the security context it is essential that the PartnerName field in the MQCXP structure contains a valid partner name. On this call it did not. This can arise as a result of a usage error, for instance only specifying the security exit on one end of the channel. The error was reported from security exit function savePartnerName.
Response: Check your usage of the DCE security exit for errors, such as only specifying the exit in one of the matching channel definitions. Correct any errors found and retry.

AMQ9578: DCE Security: bad return from DCE call.
Severity: 30 : Error
Explanation: Channel <insert_3> has been closed because one of the DCE channel exits received a bad return code from DCE.
Response: Consult the appropriate DCE manuals to find out the meaning of major_status <insert_1> and minor_status <insert_2> on call <insert_5>. Then rectify the error. The exit function name is <insert_4>.

AMQ9579: DCE Security: partner name does not match target.
Severity: 30 : Error
Explanation: The DCE Security exit was requested to perform a trusted channel check: target partner name <insert_4> was specified in the SCYDATA field of channel <insert_3>. The actual partner name associated with channel <insert_3> was <insert_5>, so the security exit suppressed the channel.
Response: Examine the channel definition of channel <insert_3> and alter it so that the relevant name on the partner system matches that specified in the SCYDATA field.

AMQ9580: DCE Security: invalid message received.
Severity: 30 : Error
Explanation: An IBM-supplied DCE exit on channel <insert_3> received a message that was not generated by a matching exit, or was not the expected type of message. The header.mechanism field had value <insert_1>. The header.msgtype field had value <insert_2>. The name of the exit function in which the error was discovered is <insert_4>.
Response: Make sure that the exits at both ends of the channel generate compatible flows.

AMQ9581: DCE Security: wrong exit called.
Severity: 30 : Error
Explanation: Exit <insert_4> on channel <insert_3> was called for use as an IBM MQ exit of the wrong type. DCE_SEC_SCY_CHANNELEXIT functions as a security exit; DCE_SEC_SRM_CHANNELEXIT functions as a send, receive or message exit. The ExitId parameter passed to the exit was <insert_1>.
Response: Alter the exit definitions to ensure that exit <insert_4> is called correctly.

AMQ9582: DCE Security: invalid exit function requested.
Severity: 30 : Error
Explanation: Exit <insert_4> on channel <insert_3> was called with an invalid ExitReason (value <insert_1>).
Response: Check that the exit is being run with a compatible release of IBM MQ base code. If not then correct it. If it is, save any generated output files and use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.

AMQ9583: The DCE security exit was not run.
Severity: 30 : Error
Explanation: The DCE_SEC_SRM_CHANNELEXIT exit was called on channel <insert_3>; the value of pContext->mechanism (<insert_1>) passed was not valid.
Response: This is probably because the DCE_SEC_SRM_CHANNELEXIT exit has been called without first calling the DCE_SEC_SCY_CHANNELEXIT security exit. Alter the system so that either both or neither are run.

AMQ9584: DCE Security: message too short.
Severity: 30 : Error
Explanation: The DCE_SEC_SRM_CHANNELEXIT receive or message exit was called on channel <insert_3> to process an incoming message. The pDataLength parameter supplied to the exit indicated that the message received was too short to be a valid message for the relevant exit. The *pDataLength value was <insert_1>.
Response: Configure the system so that compatible send/receive/message exits are run at both ends of the channel.

AMQ9585: Maximum number of channel initiators reached.
Severity: 30 : Error
Explanation: The maximum number of channels initiators that can be in use simultaneously has been reached. The number of permitted channel initiators is a configurable parameter in the queue manager configuration file.
Response: Wait for one or more channel initiators to close and retry the operation or modify the configuration file to allow more initiators and restart the Queue Manager.

AMQ9586: Program cannot create queue manager object.
Severity: 30 : Error
Explanation: The attempt to create object <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.
Response: Use the standard facilities supplied with your system to record the problem identifier. Save any generated output files and use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.

AMQ9587: Program cannot open queue manager object.
Severity: 30 : Error
Explanation: The attempt to open object <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.
Response: Use the standard facilities supplied with your system to record the problem identifier. Save any generated output files and use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.

AMQ9588: Program cannot update queue manager object.
Severity: 30 : Error
Explanation: The attempt to update object <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.
Response: Use the standard facilities supplied with your system to record the problem identifier. Save any generated output files and use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.

AMQ9589: Program cannot query queue manager object.
Severity: 30 : Error
Explanation: The attempt to query object <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.
Response: Use the standard facilities supplied with your system to record the problem identifier. Save any generated output files and use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.

AMQ9590: Program cannot close queue manager object.
Severity: 30 : Error
Explanation: The attempt to close object <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.
Response: Use the standard facilities supplied with your system to record the problem identifier. Save any generated output files and use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.

AMQ9591: Program cannot prepare queue manager object.
Severity: 30 : Error
Explanation: The attempt to prepare object <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.
Response: Use the standard facilities supplied with your system to record the problem identifier. Save any generated output files and use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.

AMQ9592: Program cannot resolve queue manager object.
Severity: 30 : Error
Explanation: The attempt to resolve object <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.
Response: Use the standard facilities supplied with your system to record the problem identifier. Save any generated output files and use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.

AMQ9593: Program cannot delete queue manager object.
Severity: 30 : Error
Explanation: The attempt to delete object <insert_4> on queue manager <insert_5> failed with reason code <insert_1>.
Response: Use the standard facilities supplied with your system to record the problem identifier. Save any generated output files and use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.

AMQ9594: Usage: runmqfmt [filename].
Severity: 0 : Informational
Explanation: Syntax for the usage of runmqfmt.
Response: None.

AMQ9595: Usage: endmqlsr [-w] [-m QMgrName]
-m Queue manager name.
-w Wait for listeners to end.
Severity: 10 : Warning
Explanation: This shows the correct usage.
Response: Correct the parameters passed to the endmqlsr program and retry the operation.

AMQ9596: Queue Manager <insert_3> still running
Severity: 30 : Error
Explanation: The requested operation can not complete because queue manager <insert_3> is still running.
Response: End the queue manager and retry the operation.

AMQ9597: No IBM MQ listeners for queue manager <insert_3>.
Severity: 0 : Informational
Explanation: No listener processes were found in the system for queue manager <insert_3>.
Response: None.

AMQ9598: <insert_1> IBM MQ listeners will end shortly.
Severity: 0 : Informational
Explanation: <insert_1> listeners detected in the system are scheduled for shutdown.
Response: None.

AMQ9599: Program could not open a queue manager object.
Severity: 30 : Error
Explanation: The attempt to open either the queue or queue manager object <insert_4> on queue manager <insert_5> by user <insert_3> failed with reason code <insert_1>.
Response: Ensure that the queue is available and retry the operation. If the message is from a remote queue manager, check the message channel agent user identifier has the correct authority.

AMQ9601: Program could not inquire on queues on this queue manager.
Severity: 30 : Error
Explanation: The IBM MQ clustering repository program was attempting to find out about the queues on queue manager <insert_3>. One of the calls failed with reason code <insert_1>. The repository command was backed out and the repository process went into a timed wait.
Response: Correct the error. When the repository process restarts it processes the backed out command again and continues.

AMQ9602: Maximum number of channel processes reached.
Severity: 30 : Error
Explanation: The channel can not start because the number of channel processes has already reached the maximum allowable value. The maximum number of channels processes is configured as <insert_1>. This value is a configurable parameter in the queue manager configuration file.
Response: Wait for some of the operating channels to close. Retry the operation when some channels are available.

AMQ9603: Error accessing the process pool shared segment.
Severity: 30 : Error
Explanation: The program could not access the process pool shared segment
Response: A value of <insert_1> was returned from the subsystem when an attempt was made to access the Channel process pool shared memory. Contact the systems administrator, who should examine the log files to determine why the program was unable to access the process pool shared segment.

AMQ9604: Channel <insert_3> terminated unexpectedly
Severity: 30 : Error
Explanation: The process or thread executing channel <insert_3> is no longer running. The check process system call returned <insert_1> for process <insert_2>.
Response: No immediate action is required because the channel entry has been removed from the list of running channels. Inform the system administrator who should examine the operating system procedures to determine why the channel process has terminated.

AMQ9605: <insert_1> IBM MQ listeners have been ended.
Severity: 0 : Informational
Explanation: <insert_1> listeners detected in the system have been ended.
Response: None.

AMQ9606: An IBM MQ listener has ended.
Severity: 0 : Informational
Explanation: One listener detected in the system has been ended.
Response: None.

AMQ9608: Remote resources in recovery.
Severity: 30 : Error
Explanation: Channel <insert_3> could not establish a successful connection with the remote queue manager because resources are being recovered.
Response: Restart the channel at a later time. If the problem persists then examine the error logs of the remote queue manager to see the full explanation of the cause of the problem.

AMQ9610: AMQ<insert_1> messages suppressed
Severity: 0 : Informational
Explanation: <insert_2> messages of type AMQ<insert_1> were suppressed
Response: Message suppression is controlled by MQ_CHANNEL_SUPPRESS_MSGS and MQ_CHANNEL_SUPPRESS_INTERVAL environment variables.

AMQ9611: Rebuild Client Channel Table - program completed normally
Severity: 0 : Informational
Explanation: Rebuild Client Channel Table program completed normally.
Response: None.

AMQ9612: <insert_1> IBM MQ listeners could not be ended.
Severity: 0 : Informational
Explanation: The request to the end the IBM MQ listeners for specified queue manager was completed however <insert_1> listeners could not be stopped. Reasons why listener may not be stopped are:
The listener process contains channels which are still active.
Response: Active channels may be stopped using the 'STOP CHANNEL' command or by ending the queue manager, and reissuing the request to end the listener.

AMQ9614 (HP NSS): Certificate is not signed by a trusted Certificate Authority.
Severity: 0 : Informational
Explanation: The attempt to start channel <insert_3> failed because the certificate used in the SSL handshake is not signed by a Certificate Authority (CA) listed in the certificate trust list for this queue manager. This error can occur when;
(a) The trust.pem store being used contains an incomplete set of certificates to validate the peer certificate.
(b) One or more certificates in the the peer certificate chain have failed verification.
Response: Check that all of the required signer certificates are present in the trust.pem, adding any missing certificates. Use the openssl verify command line utility to verify the certificate chains being used are suitable.

AMQ9614 (IBM i): Certificate is not signed by a trusted Certificate Authority.
Severity: 0 : Informational
Explanation: The attempt to start channel <insert_3> failed because the certificate used in the SSL handshake is not signed by a Certificate Authority (CA) listed in the certificate trust list for this queue manager. This error can occur when;
(a) The SSL key repository does not contain a copy of the Certificate Authority certificate.
(b) 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, excluding this CA.
(c) The remote end of the channel is configured to send a certificate for which the CA certificate is not in the local key repository.
Response: Use Digital Certificate Manager to ensure the appropriate Certification Authority certificates are present, and if applicable, add the required Certificate Authority (CA) certificates to the queue managers CA trust list.
Check that the remote certificate label configuration is correct.

AMQ9615 (IBM i): Queue manager or Client user profile is not registered with DCM.
Severity: 0 : Informational
Explanation: The attempt to start channel <insert_3> failed because the queue manager or client user profile 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 or for IBM MQ client product is specified as '*SYSTEM' but IBM MQ cannot register the queue manager or client user profile as an SSL server application with DCM. Alternatively this error could occur when the application definition for the queue manager has been manually removed from DCM.
Response: For IBM MQ Base product attempt to re-register the queue manager with Digital Certificate Manager by issuing CHGMQM SSLKEYR(*SYSTEM). For IBM MQ client product attempt to set MQSSLKEYR environment to *SYSTEM. If this is unsuccessful you may need to manually add the application definition through Digital Certificate Manager. See the IBM MQ information center for more details.

AMQ9616: The CipherSpec proposed is not enabled on the server.
Severity: 30 : Error
Explanation: The SSL or TLS subsystem at the server end of a channel been configured in such a way that it has rejected the CipherSpec proposed by an SSL or TLS client. This rejection occurred during the secure socket handshake (i.e. it happened before the proposed CipherSpec was compared with the CipherSpec in the server channel definition).
This error most commonly occurs when the choice of acceptable CipherSpecs has been limited in one of the following ways:
(a) The server queue manager SSLFipsRequired attribute is set to YES and the channel is using a CipherSpec which is not FIPS-certified on the server.
(b) The server queue manager EncryptionPolicySuiteB attribute has been set to a value other than NONE and the channel is using a CipherSpec which does not meet the server's configured Suite B security level.
(c) The protocol used by the channel has been deprecated. Note that IBM may need to deprecate a protocol via product maintenance in response to a security vulnerability, for example SSLv3 has been deprecated. Continued use of SSLv3 protocol is not recommended but may be enabled by setting environment variable AMQ_SSL_V3_ENABLE=TRUE.
(d) The requested CipherSpec has been deprecated. Note that IBM may need to deprecate a CipherSpec via product maintenance in response to a security vulnerability, for example RC4_MD5_US has been deprecated. Continued use of deprecated CipherSpecs is not recommended but may be enabled by setting environment variable AMQ_SSL_WEAK_CIPHER_ENABLE=<CipherSpec>. For example, AMQ_SSL_WEAK_CIPHER_ENABLE=RC4_MD5_US
The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.
The remote host name is <insert_5>.
Response: Analyse why the proposed CipherSpec was not enabled on the server. Alter the client CipherSpec, or reconfigure the server to accept the original client CipherSpec. Restart the channel.
This message might occur after applying IBM MQ maintenance because the FIPS and Suite B standards are updated periodically. When such changes occur, IBM MQ is also updated to implement the latest standard. As a result, you might see changes in behavior after applying maintenance. For more information about the versions of FIPS and Suite B standards enforced by IBM MQ, refer to the readme:
http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg27006097

AMQ9617: Parameter requesting FIPS has an invalid value.
Severity: 30 : Error
Explanation: An SSL channel running on an MQ client has failed to start. This is because the value specified for the MQSSLFIPS environment variable, or in the MQSCO FipsRequired field, is invalid. The value specified was "<insert_3>".
Response: Set the MQSSLFIPS environment variable, or the MQSCO FipsRequired field, to a valid value. Restart the channel.

AMQ9618: SSLCRLNL attribute points to a namelist with no names.
Severity: 30 : Error
Explanation: An SSL channel has failed to start because the SSLCRLNL queue manager attribute points to a namelist with an empty list of names.
Response: If OCSP or CRL checking is required, set up the namelist referenced by SSLCRLNL with a non-empty list of authentication information object names. If no OCSP or CRL checking is required, clear the SSLCRLNL queue manager attribute. Restart the failing channel.

AMQ9619: SSL cannot be run from an unthreaded HP-UX MQ client.
Severity: 30 : Error
Explanation: On HP-UX, SSL cannot be run from an IBM MQ client which was linked with the unthreaded client libraries.
Response: Either relink your client application with the threaded client libraries, or do not attempt to use SSL from this application.

AMQ9620: Internal error on call to SSL function on channel <insert_3> to host <insert_5>.
Severity: 30 : Error
Explanation: An error indicating a software problem was returned from a function which is used to provide SSL or TLS 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.
The remote host name is <insert_5>.
Response: Collect the items listed in the 'Problem determination' section of the System Administration manual and use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.

AMQ9620 (IBM i): Unexpected SSL error on call to <insert_4>.
Severity: 0 : Informational
Explanation: An unexpected SSL error was returned from function <insert_4> for channel <insert_3>. The error code returned was <insert_1>. GSKit error codes are documented in the MQ manuals and also in the GSKSSL member of the H file in library QSYSINC.
Response: Collect the items listed in the 'Problem determination' section of the System Administration manual and use either the MQ Support site: http://www.ibm.com/software/integration/wmq/support/, or IBM Support Assistant (ISA): http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center.

AMQ9621: Error on call to SSL function ignored on channel <insert_3> to host <insert_5>.
Severity: 10 : Warning
Explanation: An error indicating a software problem was returned from a function which is used to provide SSL support. The error code returned was <insert_1>. The function call was <insert_4>.
The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'.
The remote host is <insert_5>.
This error is not regarded as sufficiently serious to interrupt channel operation; channel operation was not affected.
Response: None.

AMQ9622: AUTHINFO object <insert_3> does not exist.
Severity: 30 : Error
Explanation: A channel or channel process has failed to start because the namelist of AUTHINFO objects includes the name <insert_3>, but no AUTHINFO object of that name exists.
Response: Ensure all the names in the namelist specified on the SSLCRLNL queue manager attribute correspond to AUTHINFO objects which are to be used on the SSL channels. Restart the failing channel or channel process.

AMQ9623: Error inquiring on AUTHINFO object <insert_3>.
Severity: 30 : Error
Explanation: A channel or channel process has failed to start because reason code <insert_1> was returned when an inquire was performed on AUTHINFO object <insert_3>.
Response: Look at the MQRC_ values in the IBM MQ Application Programming Reference to determine the meaning of reason code <insert_1>, correct the error, and restart the failing channel or channel process.

AMQ9624: AUTHINFO object <insert_3> is not of type CRLLDAP or OCSP.
Severity: 30 : Error
Explanation: A channel or channel process has failed to start because one of the AUTHINFO objects specified in the SSLCRLNL namelist does not have a valid AUTHTYPE. Instead the type value is <insert_1>.
Response: Include only AUTHINFO objects with AUTHTYPE CRLLDAP or AUTHTYPE OCSP in the namelist specified on the SSLCRLNL queue manager attribute. Restart the channel or channel process.

AMQ9625: AUTHINFO object <insert_3> was specified with an invalid CONNAME.
Severity: 30 : Error
Explanation: A channel or channel process has failed to start because one of the AUTHINFO objects specified in the SSLCRLNL namelist has an invalid CONNAME parameter. The invalid value is <insert_4>.
Response: Correct the invalid parameter. Restart the channel or channel process.

AMQ9626: Channel hanging while initializing SSL.
Severity: 30 : Error
Explanation: The current channel cannot start because another channel is hanging while initializing the SSL subsystem.
Response: Investigate the reason for the hang on the other channel. Once this is rectified, restart this channel.

AMQ9627: The path and stem name for the SSL key repository have not been specified.
Severity: 30 : Error
Explanation: The directory path and file stem name for the SSL key repository have not been specified. On a MQ client system there is no default location for this file. SSL connectivity is therefore impossible as this file cannot be accessed.
Response: Use the MQSSLKEYR environment variable or MQCONNX API call to specify the directory path and file stem name for the SSL key repository.

AMQ9628: An LDAP server containing CRLs was specified with an invalid CONNAME.
Severity: 30 : Error
Explanation: The IBM MQ client has failed to connect because an invalid CONNAME was found for one of the LDAP servers containing CRLs. The invalid value is <insert_3>.
Response: Correct the invalid parameter. If the LDAP details were defined on a queue manager system, regenerate the client definitions. Reconnect.

AMQ9629: Bad SSL cryptographic hardware parameters.
Severity: 30 : Error
Explanation: The following string was supplied to specify or control use of SSL cryptographic hardware: <insert_4>. This string does not conform to any of the MQ SSL cryptographic parameter formats. The channel is <insert_3>. The channel did not start.
Response: Correct your SSL cryptographic hardware parameters and restart the channel.

AMQ9631: The CipherSpec negotiated during the SSL handshake does not match the required CipherSpec for channel <insert_3>.
Severity: 30 : Error
Explanation: There is a mismatch between the CipherSpecs on the local and remote ends of channel <insert_3>. The channel will not run until this mismatch is resolved. The CipherSpec required in the local channel definition is <insert_4>. The name of the CipherSpec negotiated during the SSL handshake is <insert_5>. A code is displayed if the name of the negotiated CipherSpec cannot be determined.
Response: Change the channel definitions for <insert_3> so the two ends have matching CipherSpecs and restart the channel. If the certificate in use by one end of the channel is a Global Server Certificate, then the negotiated CipherSpec may not match that specified on either end of the channel. This is because the SSL protocol allows a Global Server Certificate to automatically negotiate a higher level of encryption. In these cases specify a CipherSpec which meets the requirements of the Global Server Certificate.

AMQ9631 (IBM i): The CipherSpecs at the ends of channel <insert_3> do not match.
Severity: 30 : Error
Explanation: There is a mismatch between the CipherSpecs on the local and remote ends of channel <insert_3>. The channel will not run until this mismatch is resolved. The local CipherSpec is <insert_4> and the remote CipherSpec is <insert_5>.
Response: Change the channel definition for <insert_3> so that both ends have matching CipherSpecs and restart the channel.

AMQ9633: Bad SSL certificate for channel <insert_3>.
Severity: 30 : Error
Explanation: A certificate encountered during SSL handshaking is regarded as bad for one of the following reasons:
(a) it was formatted incorrectly and could not be validated
(b) it was formatted correctly but failed validation against the Certification Authority (CA) root and other certificates held on the local system
(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
(e) an OCSP responder has indicated that it is revoked
The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The remote host is <insert_5>. The channel did not start.
The details of the certificate which could not be validated are <insert_4>.
The certificate validation error was <insert_2>.
Response: Check which of the possible causes applies on your system. Correct the error, and restart the channel.
This error might indicate that the remote end of the channel is configured to send the wrong certificate. Check the certificate label configuration at the remote end of the channel and ensure that the local key repository contains all of the necessary CA certificates.

AMQ9633 (IBM i): Bad SSL certificate for channel <insert_3>.
Severity: 30 : Error
Explanation: A certificate encountered during SSL handshaking is regarded as bad for one of the following reasons:
(a) it was formatted incorrectly and could not be validated
(b) it was formatted correctly but failed validation against the Certification Authority (CA) root and other certificates held on the local system
(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
(e) an OCSP responder has indicated that it is revoked
The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The remote host is <insert_5>. The channel did not start.
Response: Check which of the possible causes applies on your system. Correct the error, and restart the channel.

AMQ9635: Channel <insert_3> did not specify a valid CipherSpec.
Severity: 30 : Error
Explanation: Channel <insert_3> did not specify a valid CipherSpec.
Response: Check product documentation to confirm that the CipherSpec specified in the channel definition is valid. Note that IBM may need to deprecate the use of CipherSpecs via product maintenance in response to a security vulnerability.
All CipherSpecs that use the SSLv3 protocol have been deprecated. Continued use of SSLv3 CipherSpecs is not recommended but may be temporarily enabled by setting environment variable AMQ_SSL_V3_ENABLE=TRUE, or via the 'AllowSSLV3' attribute under the SSL stanza in the qm.ini file.
All CipherSpecs that use NULL, RC4 and EXPORT ciphers have also been deprecated. Continued use of weak CipherSpecs is not recommended but may be temporaily enabled by setting the AMQ_SSL_WEAK_CIPHER_ENABLE environment variable, or via the 'AllowWeakCipherSpec' attribute under the SSL stanza in the qm.ini file.
It may be necessary to set both sets of environment variables/stanza if temporary use of a CipherSpec that utilizes both the SSLv3 protocol and a weak cipher (e.g. RC4_MD5_US) is required.
Change channel <insert_3> to specify a valid CipherSpec.

AMQ9636: SSL distinguished name does not match peer name, channel <insert_3>.
Severity: 30 : Error
Explanation: The distinguished name, <insert_4>, contained in the SSL certificate for the remote end of the channel does not match the local SSL peer name for channel <insert_3>. The distinguished name at the remote host <insert_5> must match the peer name specified (which can be generic) before the channel can be started.
Response: If this remote system should be allowed to connect, either change the SSL peer name specification for the local channel so that it matches the distinguished name in the SSL certificate for the remote end of the channel, or obtain the correct certificate for the remote end of the channel.
This error might indicate that the remote end of the channel is configured to use the wrong certificate. Check the certificate label for the remote end of the channel.
Restart the channel.

AMQ9637: Channel is lacking a certificate.
Severity: 30 : Error
Explanation: The channel is lacking a certificate to use for the SSL handshake. The channel name is <insert_3> (if '????' it is unknown at this stage in the SSL processing).
The remote host is <insert_5>.
The channel did not start.
Response: Make sure the appropriate certificates are correctly configured in the key repositories for both ends of the channel.

AMQ9638: SSL communications error for channel <insert_3>.
Severity: 30 : Error
Explanation: An unexpected SSL communications error occurred for a channel, as reported in the preceding messages. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.
Response: Investigate the problem reported in the preceding messages. Review the local and remote console logs for reports of network errors. Correct the errors and restart the channel.

AMQ9639: Remote channel <insert_3> did not specify a CipherSpec.
Severity: 30 : Error
Explanation: Remote channel <insert_3> did not specify a CipherSpec when the local channel expected one to be specified.
The remote host is <insert_4>.
The channel did not start.
Response: Change the remote channel <insert_3> on host <insert_4> to specify a CipherSpec so that both ends of the channel have matching CipherSpecs.

AMQ9640: SSL invalid peer name, channel <insert_3>, attribute <insert_5>.
Severity: 30 : Error
Explanation: The SSL peer name for channel <insert_3> includes a distinguished name attribute key <insert_5> which is invalid or unsupported. The channel did not start.
Response: Correct the SSL peer name for the channel. Restart the channel.

AMQ9641: Remote CipherSpec error for channel <insert_3> to host <insert_4>.
Severity: 30 : Error
Explanation: The remote end of channel <insert_3> on host <insert_4> has had a CipherSpec error. The channel did not start.
Response: Review the error logs on the remote system to discover the problem with the CipherSpec.

AMQ9642: No SSL or TLS certificate for channel <insert_3>.
Severity: 30 : Error
Explanation: The channel <insert_3> did not supply a certificate to use during SSL or TLS handshaking, but a certificate is required by the remote queue manager.
The remote host is <insert_4>.
The channel did not start.
Response: Ensure that the key repository of the local queue manager or MQ client contains a certificate which is associated with the queue manager or client. If you have configured a certificate label, check that the certificate exists.
Alternatively, if appropriate, change the remote channel definition so that its SSLCAUTH attribute is set to OPTIONAL and it has no SSLPEER value set.

AMQ9642 (IBM i): No SSL certificate for channel <insert_3>.
Severity: 0 : Informational
Explanation: The channel <insert_3> did not supply a certificate to use during SSL handshaking, but a certificate is required by the remote queue manager. The channel did not start.
Response: If the SSL key repository for the queue manager has been specified as '*SYSTEM' ensure that a certificate has been associated with the application description for the queue manager in Digital Certificate Manager. Alternatively, if appropriate, change the remote channel definition so that its SSLCAUTH attribute is set to OPTIONAL and it has no SSLPEER value set.

AMQ9643: Remote SSL peer name error for channel <insert_3> on host <insert_4>.
Severity: 30 : Error
Explanation: The remote end of channel <insert_3> on host <insert_4> has had an SSL peer name error. The channel did not start.
Response: Review the error logs on the remote system to discover the problem with the peer name.

AMQ9645: Certificate <insert_4> missing on channel <insert_3>.
Severity: 30 : Error
Explanation: The local key database repository does not contain the certificate <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.
In some cases this message will appear multiple times, once for each affected channel.
Response: Add a correctly labelled certificate to the current key database file. Alternatively, change the certificate label configuration so that the channel uses a valid certificate.
Restart the channel.

AMQ9646: Channel <insert_3> could not connect to any LDAP CRL servers.
Severity: 30 : Error
Explanation: LDAP Certification Revocation List (CRL) servers were specified but a connection could not be established to any of them. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.
Response: Check that the LDAP CRL server specifications are correct. If they are, check that the servers are running and that the networking to access them is working correctly. Fix any errors found and restart the channel.

AMQ9647: I/O error on SSL key repository.
Severity: 30 : Error
Explanation: An I/O error was encountered when attempting to read the SSL key repository. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.
Response: Analyse why there is a I/O problem when reading the key repository. Fix the error if one is found, or it may be a temporary problem. Restart the channel.

AMQ9648: The SSL key repository has an invalid internal format.
Severity: 30 : Error
Explanation: The SSL key repository has an invalid internal format. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.
Response: Recreate the SSL key repository and restart the channel.

AMQ9649: The SSL key repository contains duplicate keys.
Severity: 30 : Error
Explanation: The SSL key repository contains two or more entries with the same key. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.
Response: Use your key management tool to remove the duplicate keys. Restart the channel.

AMQ9650: The SSL key repository contains entries with duplicate labels.
Severity: 30 : Error
Explanation: The SSL key repository contains two or more entries with the same label. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.
Response: Use your key management tool to remove the duplicate entries. Restart the channel.

AMQ9651: The SSL key repository is corrupt or has a bad password.
Severity: 30 : Error
Explanation: The SSL key repository has become corrupted or its password id is incorrect. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.
Response: Use your key management tool to recreate the key repository with a new password. Restart the channel.

AMQ9652: The remote SSL certificate has expired.
Severity: 30 : Error
Explanation: The SSL certificate used by MQ on the remote end of the channel has expired. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.
Response: Use your key management tool to provide MQ with a current SSL certificate on the remote end of the channel. Restart the channel.

AMQ9653: An SSL trace file could not be opened.
Severity: 10 : Warning
Explanation: An SSL trace file could not be opened. The SSL trace files are created in directory <insert_4> and have names AMQ.SSL.TRC and AMQ.SSL.TRC.1. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. This error is not regarded as sufficiently serious to interrupt channel operation; channel operation was not affected.
Response: Check that you have a directory called <insert_4> and that the userid under which IBM MQ runs has permissions and space to create and open a file in that directory. Fix the problem and you will get SSL trace output.

AMQ9654: Validation checks for the remote personal certificate failed. The channel did not start.
Severity: 30 : Error
Explanation: An SSL certificate received from the remote system was not corrupt but failed validation checks on something other than its ASN.1 fields and date. It is possible that the certificate chain could not be built for for one of the following reasons: - The certificate Subject DN is more than 1024 characters long. - The DN contains unsupported duplicate attribute values. - The DN is missing.
The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'.
Response: Ensure that the remote system has a valid personal certificate and restart the channel.

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

AMQ9655 (HP NSS): Problem loading OpenSSL support.
Severity: 30 : Error
Explanation: MQ SSL support is provided on this platform using a component called OpenSSL which is installed as part of MQ. OpenSSL had an internal problem loading one if its dynamic link libraries. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.
Response: Uninstall MQ and reinstall. Restart the channel.

AMQ9656: An invalid SSL certificate was received from the remote system.
Severity: 30 : Error
Explanation: An SSL certificate received from the remote system was not corrupt but failed validation checks on its ASN fields. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.
Response: Ensure that the remote system has a valid SSL certificate. Restart the channel.

AMQ9657: The key repository could not be opened (channel <insert_3>).
Severity: 30 : Error
Explanation: The key repository could not be opened. The key repository either does not exist or has incorrect permissions associated with it. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.
Response: Ensure that the key repository you specify exists and that its permissions are such that the MQ process involved can read from it. Restart the channel.

AMQ9658: An invalid SSL certificate has been encountered.
Severity: 30 : Error
Explanation: An SSL certificate has been encountered which was not corrupt but which failed validation checks on its date fields. The certificate has either expired, or its date is not valid yet (i.e. the from date is later than today), or the validity date range is incorrect (e.g. the to date is earlier than the from date). The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.
Response: Ensure that both the local and remote systems have valid, current SSL certificates. Ensure that changes to certificate stores are effective by refreshing the security cache by issuing REFRESH SECURITY TYPE(SSL). Restart the channel.

AMQ9659: A failure occurred during SSL handshaking.
Severity: 30 : Error
Explanation: During SSL handshaking, or associated activities, a failure occurred. The failure is <insert_4> and has caused IBM MQ channel name <insert_3> to be closed. If the name is '????' then the name is unknown.
Response: Refer to prior message in the IBM MQ error log for information related to this problem.

AMQ9660: SSL key repository: password stash file absent or unusable.
Severity: 30 : Error
Explanation: The SSL key repository cannot be used because MQ cannot obtain a password to access it. Reasons giving rise to this error include:
(a) the key database file and password stash file are not present in the location configured for the key repository,
(b) the key database file exists in the correct place but that no password stash file has been created for it,
(c) the files are present in the correct place but the userid under which MQ is running does not have permission to read them,
(d) one or both of the files are corrupt.
The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.
Response: Ensure that the key repository variable is set to where the key database file is. Ensure that a password stash file has been associated with the key database file in the same directory, and that the userid under which MQ is running has read access to both files. If both are already present and readable in the correct place, delete and recreate them. Restart the channel.

AMQ9661: Bad SSL data from peer on channel <insert_3>.
Severity: 30 : Error
Explanation: An SSL channel has stopped because bad SSL data was received from the remote end of the channel. More detail on the nature of the corruption can be found from the GSKit return value of <insert_1> (the GSKit return values are documented in the MQ manuals). The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'.
Response: Ensure you are connecting to a version of MQ which supports SSL at the remote end of the channel. Check your network between the two ends of the channel, and consider whether any possible causes of message corruption could be present. Fix any problems which may exist and restart the channel.

AMQ9661 (HP NSS): Bad SSL data from peer on channel <insert_3>.
Severity: 30 : Error
Explanation: An SSL channel has stopped because bad SSL data was received from the remote end of the channel. More detail on the nature of the corruption can be found from the OpenSSL return value of <insert_1> (the OpenSSL return values are documented in the MQ manuals). The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'.
Response: Ensure you are connecting to a version of MQ which supports SSL at the remote end of the channel. Check your network between the two ends of the channel, and consider whether any possible causes of message corruption could be present. Fix any problems which may exist and restart the channel.

AMQ9661 (IBM i): Bad SSL data from peer on channel <insert_3>.
Severity: 0 : Informational
Explanation: An SSL channel has stopped because bad SSL data was received from the remote end of the channel. More detail on the nature of the corruption can be found from the GSKit return value of <insert_1> (the GSKit return values are documented in the MQ manuals and also in the GSKSSL member of the H file in library QSYSINC). The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'.
Response: Ensure the remote queue manager and channel listener are running and that you are connecting to a version of MQ which supports SSL at the remote end of the channel. Check your network between the two ends of the channel, and consider whether any possible causes of message corruption could be present. Fix any problems which may exist and restart the channel.

AMQ9662: SSL has encountered something it does not support.
Severity: 30 : Error
Explanation: This error can arise for a number of reasons: 1) The platform does not support a given type of cryptographic hardware, e.g. nCipher nFast and Rainbow Cryptoswift are no longer supported. 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. 4) System wide settings or environment variables have restricted support for a protocol or cipher, e.g. IBM i system values QSSLPCL and QSSLCSL. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.
Response: Check that your cryptographic hardware is supported on your platform and test it to see that it is working correctly. Check that the remote certificates you are using conform to the X509 General Name formats listed. Fix the problem and restart the channel.

AMQ9662 (HP NSS): SSL has encountered something it does not support.
Severity: 30 : Error
Explanation: This error can arise for a number of reasons: 1) The platform does not support a given type of cryptographic hardware, e.g. nCipher nFast and Rainbow Cryptoswift are no longer supported. 2) The cryptographic hardware cryptography has returned an error. 3) Unsupported X509 General Name format when checking the remote certificate. The OpenSSL SSL provider incorporated in MQ only supports formats rfc822, DNSName, directoryname, uniformResourceID, and IPAddress. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.
Response: Check that your cryptographic hardware is supported on your platform and test it to see that it is working correctly. Check that the remote certificates you are using conform to the X509 General Name formats listed. Fix the problem and restart the channel.

AMQ9663: An invalid SSL certificate was received from the remote system.
Severity: 30 : Error
Explanation: An SSL certificate received from the remote system failed validation checks on its signature. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.
Response: Ensure that the remote system has a valid SSL certificate. Restart the channel.

AMQ9664: Bad userid for CRL LDAP server; SSL channel <insert_3>.
Severity: 30 : Error
Explanation: Certification Revocation List (CRL) checking on an LDAP server or servers has been configured on the local MQ system. The userid information configured for the LDAP server or servers is incorrect. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.
Response: Check the userid information for the CRL LDAP server or servers you have configured locally. Correct any problems found and restart the channel.

AMQ9665: SSL connection closed by remote end of channel <insert_3>.
Severity: 30 : Error
Explanation: The SSL or TLS connection was closed by the remote host <insert_5> during the secure socket handshake. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.
Response: Check the remote end of the channel for SSL and TLS errors. Fix them and restart the channel.

AMQ9666: Error accessing CRL LDAP servers; SSL channel <insert_3>.
Severity: 30 : Error
Explanation: CRL checking on LDAP servers has been configured on the local MQ system. An error was found when trying to access the CRL LDAP servers when validating a certificate from the remote system. Possible causes are:
(a) cannot connect to any of the LDAP servers, or
(b) the certificate issuer's Distinguished Name (DN) is not defined in the DIT of an LDAP server.
The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.
Response: Check access to the CRL LDAP server(s) you have configured locally. Put right any problems found and restart the channel.

AMQ9667: Bad user name or password for CRL LDAP server; SSL channel <insert_3>.
Severity: 30 : Error
Explanation: Certification Revocation List (CRL) checking on an LDAP server or servers has been configured on the local MQ system. The user name or password information configured for the LDAP server or servers is incorrect. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.
Response: Check the user name and password information for the CRL LDAP server or servers you have configured locally. Correct any problems found and restart the channel.

AMQ9668: The specified PKCS #11 shared library could not be loaded.
Severity: 30 : Error
Explanation: A failed attempt was made to load the PKCS #11 shared library specified to MQ in the PKCS #11 driver path field of the GSK_PKCS11 SSL CryptoHardware parameter. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.
Response: Ensure that the PKCS #11 shared library exists and is valid at the location specified. Restart the channel.

AMQ9669: The PKCS #11 token could not be found.
Severity: 30 : Error
Explanation: The PKCS #11 driver failed to find the token specified to MQ in the PKCS #11 token label field of the GSK_PKCS11 SSL CryptoHardware parameter. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.
Response: Ensure that the PKCS #11 token exists with the label specified. Restart the channel.

AMQ9670: PKCS #11 card not present.
Severity: 30 : Error
Explanation: A PKCS #11 card is not present in the slot. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.
Response: Ensure that the correct PKCS #11 card is present in the slot. Restart the channel.

AMQ9671: The PKCS #11 token password specified is invalid.
Severity: 30 : Error
Explanation: The password to access the PKCS #11 token is invalid. This is specified to MQ in the PKCS #11 token password field of the GSK_PKCS11 SSL CryptoHardware parameter. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.
Response: Ensure that the PKCS #11 token password specified on GSK_PKCS11 allows access to the PKCS #11 token specified on GSK_PKCS11. Restart the channel.

AMQ9672 (IBM i): A certificate label is not permitted when using the system key repository.
Severity: 30 : Error
Explanation: The SSL or TLS channel <insert_3> was started using certificate label <insert_4> and the queue manager is using the IBM i system key repository. Configuring certificate labels in IBM MQ is not supported when using the IBM i system key repository.
The channel did not start.
Response: Assign a certificate using the IBM i Digital Certificate Manager instead. Alternatively, use a non-system key repository.

AMQ9673: The channel <insert_3> did not send the correct certificate to the remote peer.
Severity: 30 : Error
Explanation: The SSL or TLS channel <insert_3> is configured to use certificate label <insert_4>. However, the remote peer did not send the necessary information to allow the local channel to use the correct certificate. The remote host is <insert_5>.
This error occurs when the local channel definition has a certificate label and the remote peer does not support selection of certificates.
The channel did not start.
Response: Ensure that the remote peer supports certificate label configuration. Refer to the Security section of the IBM MQ Information Center for details of certificate label requirements. Alternatively, alter the local channel definition so that it does not specify a certificate label.

AMQ9674: The channel <insert_3> specified a weak or broken CipherSpec.
Severity: 30 : Error
Explanation: The SSL or TLS channel <insert_3> is configured to use a weak or broken CipherSpec <insert_4>.
This error occurs when the channel has requested to use a CipherSpec that utilizes cryptographic algorithms or protocols that are now considered to be broken or weak.
The channel did not start.
Response: Ensure that the channel is configured to use a CipherSpec that uses a stronger set of cryptographic algorithms or a stronger protocol.
Alternatively, configure the queue manager to re-enable the weaker CipherSpec <insert_4> using the AMQ_SSL_WEAK_CIPHER_ENABLE environment variable, or via the 'AllowWeakCipherSpec' attribute under the SSL stanza in the qm.ini file.

AMQ9707: Unsupported <insert_3> version <insert_4>.
Severity: 30 : Error
Explanation: IBM MQ SSL and TLS channel support is provided using a component called <insert_3>. IBM MQ has detected that <insert_3> version <insert_4> is loaded in the current process. However, the minimum <insert_3> version required by IBM MQ is <insert_5>.
The channel did not start because the <insert_3> version does not meet the minimum version requirements.
Response: Check which versions of <insert_3> are being used by IBM MQ and any other products in this process and ensure that all products are using version <insert_5> or later.

AMQ9710: SSL security refresh failed.
Severity: 30 : Error
Explanation: The request to refresh SSL security was unsuccessful.
Response: Look at previous error messages in the error files to determine the cause of the failure.

AMQ9711: SSL security refresh succeeded but channel restarts failed.
Severity: 30 : Error
Explanation: The SSL environments for this queue manager have been refreshed so current values and certificates are in use for all SSL channels. However, not all the outbound SSL channels which were running when the security refresh was initiated could be restarted after the refresh had completed.
Response: Look at previous error messages in the error files to determine which channels could not be restarted. Restart these if necessary.

AMQ9712: SSL security refresh timed out waiting for channel <insert_3>.
Severity: 30 : Error
Explanation: The system was performing a security refresh for SSL. This function requests all outbound and inbound SSL channels to stop. It then waits for these channels to actually stop. SSL channel <insert_3> did not stop within the timeout period.
Response: Investigate why channel <insert_3> is hung. Terminate the hung channel. Rerun the SSL security refresh.

AMQ9713: Channel <insert_3> ended: SSL refresh in progress.
Severity: 0 : Informational
Explanation: The SSL support on this queue manager is in the middle of a security refresh. An attempt was made to start outbound SSL channel <insert_3>. It cannot start while the SSL security refresh is in progress. The channel is restarted automatically once the SSL security refresh is complete.
Response: None.

AMQ9714: SSL refresh on receiving queue manager: channel did not start.
Severity: 30 : Error
Explanation: An SSL security refresh is in progress on the queue manager at the receiving end of this SSL channel. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.
Response: Restart the channel once the SSL refresh is complete. The channel will restart automatically if it is configured to retry the connection.

AMQ9715: Unexpected error detected in validating SSL session ID.
Severity: 30 : Error
Explanation: This error can arise when the GSKit SSL provider is missing one or more pre-requisite PTFs on the OS/400 platform. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'.
Response: Ensure the GSKit SSL provider is at the latest level of maintenance and restart the channel.

AMQ9715 (HP NSS): Unexpected error detected in validating SSL session ID.
Severity: 30 : Error
Explanation: The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'.
Response: Ensure the SSL provider is at the latest level of maintenance and restart the channel.

AMQ9716: Remote SSL certificate revocation status check failed for channel <insert_5>.
Severity: 30 : Error
Explanation: IBM MQ failed to determine the revocation status of the remote SSL certificate for one of the following reasons:
(a) The channel was unable to contact any of the CRL servers or OCSP responders for the certificate.
(b) None of the OCSP responders contacted knows the revocation status of the certificate.
(c) An OCSP response was received, but the digital signature of the response could not be verified.
The details of the certificate in question are <insert_3>.
The channel name is <insert_5>. In some cases the channel name cannot be determined and so is shown as '????'. The channel did not start.
IBM MQ does not allow the channel to start unless the certificate revocation status can be determined.
Response: If the certificate contains an AuthorityInfoAccess extension, ensure that the OCSP server named in the certificate extension is available and is correctly configured.
If the certificate contains a CrlDistributionPoint extension, ensure that the CRL server named in the certificate extension is available and is correctly configured.
If you have specified any CRL or OCSP servers to IBM MQ, check that those servers are available and are correctly configured.
Ensure that the local key repository has the necessary SSL certificates to verify the digital signature of the response from the OCSP server.

AMQ9717: Remote SSL certificate revocation status is unknown for channel <insert_5>.
Severity: 10 : Warning
Explanation: IBM MQ was unable to determine the revocation status of the remote SSL certificate for one of the following reasons:
(a) The channel was unable to contact any of the CRL servers or OCSP responders for the certificate.
(b) None of the OCSP responders contacted knows the revocation status of the certificate.
(c) An OCSP response was received, but the digital signature of the response could not be verified.
The details of the certificate in question are <insert_3>.
The channel name is <insert_5>. In some cases the channel name cannot be determined and so is shown as '????'.
The channel was allowed to start, but the revocation status of the remote SSL certificate has not been checked.
Response: If the certificate contains an AuthorityInfoAccess extension, ensure that the OCSP server named in the certificate extension is available and is correctly configured.
If the certificate contains a CrlDistributionPoint extension, ensure that the CRL server named in the certificate extension is available and is correctly configured.
If you have specified any CRL or OCSP servers to IBM MQ, check that those servers are available and are correctly configured.
Ensure that the local key repository has the necessary SSL certificates to verify the digital signature of the response from the OCSP server.
If you require certificate revocation checks to be enforced, you should configure IBM MQ to require certificate revocation checking. Refer to the security section of the IBM MQ Information Center for more information on configuring certificate revocation checking.

AMQ9718: Invalid OCSP URL <insert_3>.
Severity: 30 : Error
Explanation: IBM MQ was unable to start an SSL channel because one of the AUTHINFO objects specified in the SSLCRLNL namelist has an invalid OCSPURL parameter.
The OCSP URL is <insert_3> and the channel name is <insert_4>. In some cases the channel name cannot be determined and so is shown as '????'.
Response: The OCSP URL cannot be blank and must be a valid HTTP URL. Correct the OCSP URL and restart the channel or channel process.
Refer to the security section of the IBM MQ Information Center for details of how to use OCSP URLs.

AMQ9719: Invalid CipherSpec for FIPS mode.
Severity: 30 : Error
Explanation: The user is attempting to start a channel on a queue manager or MQ client which has been configured to run in FIPS mode. The user has specified a CipherSpec which is not FIPS-compliant. The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'.
Response: Redefine the channel to run with a FIPS-compliant CipherSpec. Alternatively, the channel may be defined with the correct CipherSpec and the queue manager or MQ client should not be running in FIPS mode; if this is the case, ensure that FIPS mode is not configured. Once the error is corrected, restart the channel.

AMQ9741: A problem occurred during a Windows operation.
Severity: 30 : Error
Explanation: During operation <insert_3>, the Windows return code <insert_1> was generated.
Response: Consult the Windows reference manual to determine the meaning of return code <insert_1> for operation <insert_3>.

AMQ9767: Usage: strmqikm [iKeymanWorkingDirectory]
Severity: 0 : Informational
Response: None.

AMQ9768: Directory <insert_3> not found.
Severity: 30 : Error
Explanation: The directory specified as a command argument has not been found.
Response: Check that the directory exists and that it is specified as an absolute (rather than relative) directory path.

AMQ9769: Usage: runmqckm
Object Action Description
------ ------ -----------
-keydb -changepw Change the password for a key database
-convert Convert the format of a key database
-create Create a key database
-delete Delete a key database
-expiry Display password expiry
-list Currently supported types of key database.
-stashpw Stash the password of a key database into a file
-cert -add Add a CA Certificate
-create Create a self-signed certificate
-delete Delete a certificate
-details Show the details of a specific certificate
-export Export a personal certificate and associated private key
into a PKCS12 file or a key database
-extract Extract a certificate from a key database
-getdefault Show the default personal certificate
-import Import a certificate from a key database or a PKCS12 file
-list List certificates in a key database
-listsigners List signer certificates delivered with iKeycmd
-modify Modify a certificate (NOTE: the only field that may be
modified is the trust field)
-populate Populate with included CA Certificates
-receive Receive a certificate
-rename Rename a certificate
-setdefault Set the default personal certificate
-sign Sign a certificate
-certreq -create Create a certificate request
-delete Delete a certificate request from a certificate request
database
-details Show the details of a specific certificate request
-extract Extract a certificate from a certificate request database
-list List all certificate requests in a certificate request
database
-recreate Recreate a certificate request
-seckey -create Create a secret key
-delete Delete a secret key
-details Show the details of a specific secret key
-export Export secret keys to a file
-import Import secret keys from a file
-list List all secret keys in a key database
-rename Rename a secret key
-version Display iKeycmd version information
-help Display this help text
Severity: 0 : Informational
Response: None.

AMQ9770: The SSL key repository password has expired.
Severity: 30 : Error
Explanation: The SSL key repository cannot be used because the password has expired.
The channel is <insert_3>; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.
Response: Use your key management tool to reset the password of the SSL key repository, ensuring that a new password stash file is generated.

AMQ9771: SSL handshake failed.
Severity: 30 : Error
Explanation: The SSL handshake with host <insert_3> failed. The SSL handshake was performed using the Java Secure Socket Extension (JSSE).
Response: The SSLSocketFactory used was <insert_5>, where 'default' indicates that the JVM's default SSLSocketFactory was used.
The exception thrown by the <insert_4> call was <insert_1>. Review the exception message for a description of the failure.
Also examine the error logs at the remote end of the channel. These may contain additional information on why the SSL handshake failed.

AMQ9772: <insert_3> failed with MQRC=<insert_1>.
Severity: 30 : Error
Explanation: The indicated IBM MQ API call failed for the specified reason code.
Response: Refer to the Application Programming Reference manual for information about Reason Code <insert_1>.

AMQ9773: Usage: runmqakm
Object Action Description
------ ------ -----------
-locale Set the display language
-fips Set FIPS mode
-trace Set the trace file name
-keydb -changepw Change the password for a key database
-convert Convert the format of a key database
-create Create a key database
-delete Delete a key database
-expiry Display password expiry
-list Currently supported types of key database.
-stashpw Stash the password of a key database into a file
-cert -add Add a CA Certificate
-create Create a self-signed certificate
-delete Delete a certificate
-details Show the details of a specific certificate
-export Export a personal certificate and associated private key
into a PKCS12 file or a key database
-extract Extract a certificate from a key database
-getdefault Show the default personal certificate
-import Import a certificate from a key database or a PKCS12 file
-list List certificates in a key database
-modify Modify a certificate (NOTE: the only field that may be
modified is the trust field)
-receive Receive a certificate
-rename Rename a certificate
-setdefault Set the default personal certificate
-sign Sign a certificate
-validate Validate a certificate
-certreq -create Create a certificate request
-delete Delete a certificate request from a certificate request
database
-details Show the details of a specific certificate request
-extract Extract a certificate from a certificate request database
-list List all certificate requests in a certificate request
database
-recreate Recreate a certificate request
-random -create Create a random password
-version Display program version information
-help Display this help text
Severity: 0 : Informational
Response: None.

AMQ9774: Error accessing the Channel authentication table
Severity: 30 : Error
Explanation: The program could not access the channel authentication table.
Response: A value of <insert_1> was returned from the subsystem when an attempt was made to access the channel authentication table. Contact the systems administrator, who should examine the log files to determine why the program was unable to access the authentication table.

AMQ9775: Channel would have been blocked by userid
Severity: 30 : Error
Explanation: The inbound channel <insert_3> would have been blocked from address <insert_4> because the active values of the channel were mapped to a userid which should be blocked. Access is allowed as the channel authentication rule is in warning mode. The active values of the channel were <insert_5>.
Response: Contact the systems administrator, who should examine the channel authentication records to ensure that the correct settings have been configured. If the channel authentication record was not in warning mode the channel would be blocked. The ALTER QMGR CHLAUTH switch is used to control whether channel authentication records are used. The command DISPLAY CHLAUTH can be used to query the channel authentication records.

AMQ9776: Channel was blocked by userid
Severity: 30 : Error
Explanation: The inbound channel <insert_3> was blocked from address <insert_4> because the active values of the channel were mapped to a userid which should be blocked. The active values of the channel were <insert_5>.
Response: Contact the systems administrator, who should examine the channel authentication records to ensure that the correct settings have been configured. The ALTER QMGR CHLAUTH switch is used to control whether channel authentication records are used. The command DISPLAY CHLAUTH can be used to query the channel authentication records.

AMQ9777: Channel was blocked
Severity: 30 : Error
Explanation: The inbound channel <insert_3> was blocked from address <insert_4> because the active values of the channel matched a record configured with USERSRC(NOACCESS). The active values of the channel were <insert_5>.
Response: Contact the systems administrator, who should examine the channel authentication records to ensure that the correct settings have been configured. The ALTER QMGR CHLAUTH switch is used to control whether channel authentication records are used. The command DISPLAY CHLAUTH can be used to query the channel authentication records.

AMQ9778: Address <insert_3> is invalid.
Severity: 30 : Error
Explanation: The address <insert_3> is invalid and the processing of the command has stopped.
Response: Reissue the command with the address parameter specified correctly. Note that the BLOCKADDR list may contain only IP addresses: host name addresses are not permitted.
See the Commands section of the IBM MQ Information Center for more information about the specification of the address parameter.

AMQ9779: IP address range error.
Severity: 30 : Error
Explanation: The IP address <insert_3> contains an invalid range. For example the first number is higher or equal to the second number in the range.
Response: The processing of the command is terminated. Reissue the command with the IP address parameter specified correctly. Refer to the commands section of the IBM MQ Information Center for more information on the specification of the IP address parameter.

AMQ9780: Channel to remote machine <insert_4> is ending due to an error.
Severity: 30 : Error
Explanation: Channel <insert_3> between this machine and the remote machine <insert_4> encountered an error and will now end. In some cases the channel name can not be determined and so is shown as '????'.
This message will be accompanied by other messages which explain the cause of the error.
Response: Tell the systems administrator, who should attempt to identify the cause of the channel failure using problem determination techniques. For example, look for FFST files, and examine the error logs on the local and remote systems where there may be messages explaining the cause of failure. More information may be obtained by repeating the operation with tracing enabled.

AMQ9781: IP address overlaps with previous definition.
Severity: 30 : Error
Explanation: The IP address <insert_3> overlaps an existing IP address <insert_4>. For example the addresses 1.2.3.4-7 and 1.2.3.6-8 overlap each other.
Response: The processing of the command is terminated. Reissue the command with an IP address parameter that does not overlap a previous definition or remove the existing record and then reissue the command. Refer to the commands section of the IBM MQ Information Center for more information on the specification of the IP address parameter.

AMQ9782: Remote connection blocked.
Severity: 30 : Error
Explanation: A connection from IP address <insert_3> was blocked because it matched the blocking address rule <insert_4>.
Response: Verify that the channel authentication blocking rules are correct. If necessary modify the rules to allow the inbound connection using the SET CHLAUTH command. The ALTER QMGR CHLAUTH switch is used to control whether channel authentication records are used. Refer to the commands section of the IBM MQ Information Center for more information on the specification of the IP address parameter.

AMQ9783: Channel will run using MCAUSER(<insert_3>).
Severity: 0 : Informational
Explanation: No matching channel authentication (CHLAUTH) records were found that match the given fields. Note:
1) The returned MCAUSER value does not take into account possible actions by a channel security exit.
2) Channel authentication rules that match the host name apply only if the queue manager REVDNS attribute is enabled and the DNS server returns a valid host name for the IP address.
Response: None.

AMQ9784: Match runcheck found a generic value in <insert_3>.
Severity: 30 : Error
Explanation: Match runcheck found a generic value in <insert_3>. When using MATCH(RUNCHECK) all input fields must not contain generic values.
Response: Reissue the command with all fields containing fully specified values.

AMQ9785: Channel is configured to not use the dead-letter queue.
Severity: 30 : Error
Explanation: A message cannot be transferred across channel <insert_5> from address <insert_4> and the channel is configured to not use the dead-letter queue. The reason code is <insert_1> and the destination queue is <insert_3>.
Response: Either correct the problem that caused the channel to try and write a message to the dead-letter queue or enable the channel to use the dead-letter queue.

AMQ9786: Remote connection would have been blocked.
Severity: 30 : Error
Explanation: A connection from IP address <insert_3> would have been blocked because it matched the blocking address rule <insert_4>. Access is allowed as the channel authentication rule is in warning mode.
Response: Verify that the channel authentication blocking rules are correct. If necessary modify the rules to allow the inbound connection using the SET CHLAUTH command. If the channel authentication record was not in warning mode the connection would be blocked. The ALTER QMGR CHLAUTH switch is used to control whether channel authentication records are used. Refer to the commands section of the IBM MQ Information Center for more information on the specification of the IP address parameter.

AMQ9787: Channel would have been blocked
Severity: 30 : Error
Explanation: The inbound channel <insert_3> would have been blocked from address <insert_4> because the active values of the channel matched a record configured with USERSRC(NOACCESS). Access is allowed as the channel authentication rule is in warning mode. The active values of the channel were <insert_5>.
Response: Contact the systems administrator, who should examine the channel authentication records to ensure that the correct settings have been configured. If the channel authentication record was not in warning mode the channel would be blocked. The ALTER QMGR CHLAUTH switch is used to control whether channel authentication records are used. The command DISPLAY CHLAUTH can be used to query the channel authentication records.

AMQ9788: Slow DNS lookup for address <insert_3>.
Severity: 10 : Warning
Explanation: An attempt to resolve address <insert_3> using the <insert_4> function call took <insert_1> seconds to complete. This might indicate a problem with the DNS configuration.
Response: Ensure that DNS is correctly configured on the local system.
If the address was an IP address then the slow operation was a reverse DNS lookup. Some DNS configurations are not capable of reverse DNS lookups and some IP addresses have no valid reverse DNS entries. If the problem persists, consider disabling reverse DNS lookups until the issue with the DNS can be resolved.

AMQ9789: The failed authentication check was caused by a CHLAUTH record with CHCKCLNT(REQDADM).
Severity: 0 : Informational
Explanation: The user ID <insert_3> and its password were checked because the user ID is privileged and the inbound connection matched a channel authentication record with CHCKCLNT(REQDADM).
The active values of the channel were <insert_5>. The MATCH(RUNCHECK) mode of the DISPLAY CHLAUTH MQSC command can be used to identify the relevant CHLAUTH record.
This message accompanies a previous error to clarify the reason for the user ID and password check.
Response: Refer to the previous error for more information.
Ensure that a password is specified by the client application and that the password is correct for the user ID. The authentication configuration of the queue manager connection determines the user ID repository. For example, the local operating system user database or an LDAP server.
To avoid the authentication check, you can either use an unprivileged user ID or change the authentication configuration of the queue manager to CHCKCLNT(NONE). You can amend the CHCKCLNT attribute in the CHLAUTH record.

AMQ9790: The failed authentication check was caused by a CHLAUTH record with CHCKCLNT(<insert_4>).
Severity: 0 : Informational
Explanation: The user ID <insert_3> and its password were checked because the inbound connection matched a channel authentication record with CHCKCLNT(<insert_4>).
The active values of the channel were <insert_5>. The MATCH(RUNCHECK) mode of the DISPLAY CHLAUTH MQSC command can be used to identify the relevant CHLAUTH record.
This message accompanies a previous error to clarify the reason for the user ID and password check.
Response: Refer to the previous error for more information.
Ensure that a password is specified by the client application and that the password is correct for the User ID. The queue manager's connection authentication configuration determines the User ID repository, for example the local operating system user database or an LDAP server.
Alternatively, to avoid the authentication check you can amend the CHLAUTH record CHCKCLNT attribute. However, allowing unauthenticated remote access is not recommended.

AMQ9791: The client application did not supply a user ID and password.
Severity: 30 : Error
Explanation: The client application <insert_3> running on host <insert_4> did not supply a user ID and password. The channel authentication (CHLAUTH) record for the connection requires a user ID and password, but none was supplied.
The active values of the channel were <insert_5>. The MATCH(RUNCHECK) mode of the DISPLAY CHLAUTH MQSC command can be used to identify the relevant CHLAUTH record.
Response: Ensure that the application provides a valid user ID and password, or change the queue manager connection authority (CONNAUTH) configuration to OPTIONAL to allow client applications to connect which have not supplied a user ID and password.

AMQ9792: The client application did not supply a password for its privileged user ID.
Severity: 30 : Error
Explanation: The client application <insert_3> running on host <insert_4> is using a privileged user ID but did not supply a password. The channel authentication (CHLAUTH) record for the connection has CHCKCLNT(REQDADM), so a password is required for the user ID.
The active values of the channel were <insert_5>. The MATCH(RUNCHECK) mode of the DISPLAY CHLAUTH MQSC command can be used to identify the relevant CHLAUTH record.
Response: Take one of the following actions:
a) Ensure that the application provides both the user ID and password.
b) Ensure that the application uses an unprivileged user ID.
c) Change the queue manager connection authority (CONNAUTH) configuration to OPTIONAL to allow client applications to connect which have not supplied both a user ID and password.

AMQ9793: The client application user ID and password cannot be checked by the queue manager.
Severity: 30 : Error
Explanation: The user ID and password for the client application <insert_3> running on host <insert_4> cannot be checked. The channel authentication (CHLAUTH) record for the connection requires an authentication check, but the queue manager is not configured to use connection authentication for clients.
The active values of the channel were <insert_5>. The MATCH(RUNCHECK) mode of the DISPLAY CHLAUTH MQSC command can be used to identify the relevant CHLAUTH record.
Response: Change the CHLAUTH configuration so that client authentication is not required, or alter the queue manager connection authority (CONNAUTH) configuration to enable client authentication checks.

AMQ9816 (HP NSS): Invalid process name <insert_3> provided for TMF/Gateway
Severity: 20 : Error
Explanation: IBM MQ client for HP Integrity NonStop Server is unable to enlist with the TMF/Gateway for queue manager <insert_4> due to an invalid process name provided in the MQTMF_GATEWAY_NAME environment variable.
Response: Ensure the TMF/Gateway is running and the MQTMF_GATEWAY_NAME environment variable is correctly set to the Guardian process name of the TMF/Gateway.

AMQ9817 (HP NSS): No PATHMON process name provided to allow enlisting with TMF/Gateway
Severity: 20 : Error
Explanation: IBM MQ client for HP Integrity NonStop Server has detected the presence of a TMF transaction and is attempting to enlist with the TMF/Gateway to allow correct participation of the queue manager in the transaction. IBM MQ client for HP Integrity NonStop Server has been unable to find a process name for the PATHMON process hosting the TMF/Gateway server class for queue manager <insert_3> in an mqclient.ini file.
Response: Ensure an mqclient.ini file is available for use by the IBM MQ client for HP Integrity NonStop Server containing a TMF stanza providing the Guardian process name of a PATHMON that is hosting a TMF/Gateway server class for queue manager <insert_3>. The mqclient.ini file also requires a TMFGateway stanza providing the server class name to be used for queue manager <insert_3>. Refer to the IBM MQ information center for further information on using an mqclient.ini file with the IBM MQ client for HP Integrity NonStop Server.

AMQ9818 (HP NSS): No server class provided to allow enlisting with TMF/Gateway for queue manager <insert_3>
Severity: 20 : Error
Explanation: IBM MQ client for HP Integrity NonStop Server has detected the presence of a TMF transaction and is attempting to enlist with the TMF/Gateway to allow correct participation of the queue manager in the transaction. IBM MQ client for HP Integrity NonStop Server has been unable to find a server class name in an mqclient.ini file for queue manager <insert_3> hosted by PATHMON process <insert_4>.
Response: Ensure an mqclient.ini file is available for use by the IBM MQ client for HP Integrity NonStop Server which contains a TMFGateway stanza providing the server class name to be used for queue manager <insert_3>. Refer to the IBM MQ information center for further information on using an mqclient.ini file with the IBM MQ client for HP Integrity NonStop Server.

AMQ9819 (HP NSS): Error encountered while enlisting with TMF/Gateway for queue manager <insert_5>
Severity: 20 : Error
Explanation: IBM MQ client for HP Integrity NonStop Server has detected the presence of a TMF transaction and is attempting to enlist with the TMF/Gateway server class <insert_4> hosted by PATHMON process <insert_3> to allow correct participation of the queue manager in the transaction. IBM MQ client for HP Integrity NonStop Server has encountered an error while establishing contact with the TMF/Gateway. Pathsend error (<insert_1>), file system error (<insert_2>).
Response: These errors are typically the result of configuration problems with the PATHMON process <insert_3> or the server class <insert_4>. Refer to the HP NonStop TS/MP Pathsend and Server Programming Manual for the appropriate corrective action based on the pathsend error (<insert_1>) and file system error (<insert_2>).

AMQ9820 (HP NSS): Participation in TMF transactions is not supported by queue manager <insert_3>
Severity: 20 : Error
Explanation: IBM MQ client for HP Integrity NonStop Server has detected the presence of a TMF transaction but IBM MQ for z/OS queue manager <insert_3> does not support participation in TMF transactions.
Response: The version of z/OS queue manager that you are connecting to does not support the TMF Gateway, please upgrade to a supported release.

AMQ9821 (HP NSS): Unable to locate PATHMON process <insert_3>
Severity: 20 : Error
Explanation: IBM MQ client for HP Integrity NonStop Server is unable to locate PATHMON process <insert_3>.
Response: The configuration error might be one of the following:
1. The mqclient.ini TMF stanza contains an invalid process name.
2. The PATHMON process <insert_3> is not currently running.

AMQ9822 (HP NSS): Unable to locate server class <insert_4>
Severity: 20 : Error
Explanation: IBM MQ client for HP Integrity NonStop Server is unable to locate server class <insert_4> hosted by PATHMON process <insert_3>.
Response: The configuration error may be one of the following:
1. The mqclient.ini TMFGateway stanza contains an invalid server class name for queue manager <insert_5>.
2. The PATHMON process <insert_3> has not been configured with server class <insert_4>.
3. Server class <insert_4> has not been started or is currently frozen.

AMQ9823 (HP NSS): Not authorized to use server class <insert_4> hosted by PATHMON process <insert_3>
Severity: 20 : Error
Explanation: IBM MQ client for HP Integrity NonStop Server is not authorized to use server class <insert_4> hosted by PATHMON process <insert_3>.
Response: Check with your systems administrator to ensure you have the correct access permissions. When confirmed you have the correct access permissions, retry the operation.

AMQ9824 (HP NSS): TMF/Gateway server class <insert_4> has not been configured appropriately
Severity: 20 : Error
Explanation: The TMF/Gateway server class <insert_4> hosted by PATHMON process <insert_3> has not been configured appropriately.
Response: The configuration error may be one of the following:
1. The server class has not been configured with TMF enabled.
2. The server class has been configured with MAXLINKS set too low for the number of IBM MQ client for HP Integrity NonStop Server applications needing to concurrently enlist with the TMF/Gateway.
3. The server class has been configured with TIMEOUT set too low for the time taken by the TMF/Gateway to process a request. Ideally TIMEOUT should not be set, but if it is then it needs to account for the time taken for the TMF/Gateway's associated remote queue manager to respond.

AMQ9825: Usage: runmqwkm
Action Description
------ -----------
createcert Creates a self-signed certificate
createcertrequest Creates a a certificate request
addcert Adds a CA certificate
deletecert Deletes a certificate
deletecertrequest Deletes a certificate request
detailcert Shows details of a specific certificate
detailcertrequest Shows details of a specific certificate request
receivecert Receives a certificate
recreatecertrequest Recreates a certificate request
listcert Lists certificates
listcertrequest Lists all certificate requests
keybackup Backs up key repository
keyrestore Restores key repository
Severity: 0 : Informational
Response: None.

AMQ9826: Usage: createcert -m QMgrName -dn DistinguishedName [-label Label]
[-expire Expiry] [-size KeySize]
[-sig_alg SignatureAlgorithm] [-format ascii|binary]
[-ku KeyUsageList] [-eku ExtendedKeyUsageList]
[-san_dnsname sanDNSName] [-san_ipaddr sanIPAddr]
-m The queue manager to create the self-signed certificate for.
-dn The X.500 distinguished name that uniquely identifies the
certificate.
-label The label attached to the certificate.
The default value is ibmwebspheremq<QMgrName in lower case>.
-size The size of the new key pair. The default value is 2048 for
all RSA signature algorithms. For elliptic curve signature
algorithms use 256, 384 or 512 to match the selected
algorithm.
-expire The expiration time of the certificate in days. The default
value is 365.
-ku and -eku The lists of valid uses for the certificate.
-sig_alg The signing algorithm that is used to create the signature
that is associated with the new self-signed certificate.
-format The format of output file. The default value is ascii.
-san_dnsname The Subject Alternative Name (SAN) DNS name(s) for the entry
that is created.
-san_ipaddr The Subject Alternative Name (SAN) IP address(es) for the
entry that is created.
Severity: 0 : Informational
Response: None.

AMQ9827: Usage: createcertrequest -m QMgrName -dn DistinguishedName [-label Label]
[-size KeySize] [-sig_alg SignatureAlgorithm]
[-ku KeyUsageList] [-eku ExtendedKeyUsageList]
[-san_dnsname sanDNSName] [-san_ipaddr sanIPAddr]
-m The queue manager to create the certificate request for.
-dn The X.500 distinguished name that uniquely identifies the
certificate.
-label The label attached to the certificate. The default value is
ibmwebspheremq<QMgrName in lower case>.
-size The size of the new key pair. The default value is 2048 for
all RSA signature algorithms. The elliptic curve signature
algorithms use 256, 384 or 512 to match the selected
algorithm.
-ku and -eku The lists of valid uses for the certificate.
-sig_alg The signing algorithm that is used to create the signature
that is associated with the new certificate.
-san_dnsname The Subject Alternative Name (SAN) DNS name(s) for the entry
that is created.
-san_ipaddr The Subject Alternative Name (SAN) IP address(es) for the
entry that is created.
Severity: 0 : Informational
Response: None.

AMQ9828: Usage: receivecert -m QMgrName -file FileName [-format ascii|binary]
-m The queue manager to receive the certificate.
-file The file that contains the certificate.
-format The format of the certificate. The default value is ascii.
Severity: 0 : Informational
Response: None.

AMQ9829: Usage: addcert -m QMgrName -label Label -file FileName
[-format ascii|binary]
-m The queue manager to add the certificate for.
-label The label for certificate.
-file The file that contains the certificate.
-format The format of the output file. The default value is ascii.
Severity: 0 : Informational
Response: None.

AMQ9830: Usage: deletecert -m QMgrName -label Label
-m The queue manager to delete the certificate from.
-label The label of the certificate to be deleted.
Severity: 0 : Informational
Response: None.

AMQ9831: Usage: deletecertrequest -m QMgrName -label Label
-m The queue manager to delete the certificate request from.
-label The label of the certificate request to be deleted.
Severity: 0 : Informational
Response: None.

AMQ9833: Usage: recreatecert -m QMgrName [-dn DistinguishedName] [-label Label]
[-expire Expiry] [-size KeySize]
[-sig_alg SignatureAlgorithm] [-format ascii|binary]
[-ku KeyUsageList] [-eku ExtendedKeyUsageList]
[-san_dnsname sanDNSName] [-san_ipaddr sanIPAddr]
-m The queue manager to recreate the self-signed certificate for.
-dn The X.500 distinguished name that uniquely identifies the
certificate.
-label The label of the certificate to be recreated. The default
value is ibmwebspheremq<QMgrName in lower case>.
-size The size of the new key pair. The default value is 2048 for
all RSA signature algorithms. The elliptic curve signature
algorithms use 256, 384 or 512 to match the selected
algorithm.
-expire The expiration time of the certificate in days. The default
value is 365.
-ku and -eku The lists of valid uses for the certificate.
-sig_alg The signing algorithm that is used to create the signature
that is associated with the new self-signed certificate.
-format The format of output file. The default value is ascii.
-san_dnsname The Subject Alternative Name (SAN) DNS name(s) for the entry
that is recreated.
-san_ipaddr The Subject Alternative Name (SAN) IP address(es) for the
entry that is recreated.
Severity: 0 : Informational
Response: None.

AMQ9834: Usage: recreatecertrequest -m QMgrName [-label Label]
[-sig_alg SignatureAlgorithm] [-ku KeyUsageList]
[-eku ExtendedKeyUsageList] [-san_dnsname sanDNSName]
[-san_ipaddr sanIPAddr]
-m The queue manager to recreate the certificate request for.
-label The label of the certificate request to recreate. The default
value is ibmwebspheremq<QMgrName in lower case>.
-ku and -eku The lists of valid uses for the certificate.
-sig_alg The signing algorithm that is used to create the signature that
is associated with the new certificate.
-san_dnsname The Subject Alternative Name (SAN) DNS name(s) for the entry
that is recreated.
-san_ipaddr The Subject Alternative Name (SAN) IP address(es) for the entry
that is recreated
Severity: 0 : Informational
Response: None.

AMQ9835: Usage: listcert -m QMgrName [-expiry [days]]
-m The queue manager to list all certificates for.
-expiry Display the valid-from and valid-to dates for certificates.
Severity: 0 : Informational
Response: None.

AMQ9836: Usage: listcertrequest -m QMgrName
-m The queue manager to list all certificates requests for.
Severity: 0 : Informational
Response: None.

AMQ9837: Usage: detailcert -m QMgrName [-label Label]
-m The queue manager to show certificate detail from.
-label The label of certificate to be shown. Default is
ibmwebspheremq<QMgrName in lower case>.
Severity: 0 : Informational
Response: None.

AMQ9838: Usage: detailcertrequest -m QMgrName [-label Label]
-m The queue manager to show certificate request detail from.
-label The label of the certificate request to be shown. Default is
ibmwebspheremq<QMgrName in lower case>.
Severity: 0 : Informational
Response: None.

AMQ9839: Usage: keybackup -m QMgrName [-force]
-m The queue manager to back up the key repository for.
-force Suppress security warnings.
Severity: 0 : Informational
Response: None.

AMQ9840: Usage: keyrestore -m QMgrName -file FileName -password Password [-defer]
-m The queue manager to restore the key repository for.
-file The file which the key repository is restored.
-password The password to use with the restored key repository.
-defer Do not refresh SSL security.
Severity: 0 : Informational
Response: None.

AMQ9841: Usage: runmqwkm keycreate -m QMgrName
-m The queue manager to create the key repository for.
Severity: 0 : Informational
Response: None.

AMQ9842: Command has used option <insert_4> with an invalid value <insert_3>
Severity: 30 : Error
Explanation: The command <insert_5> was issued specifying an invalid option value. The <insert_3> value for option <insert_4> is either missing or of an incorrect format.
Response: None.

AMQ9843: Certificate has been extracted to <insert_3>.
Severity: 0 : Informational

AMQ9844: Key repository has been backed up to <insert_3>.
Password for key repository is:
Severity: 0 : Informational

AMQ9845: Unable to access file <insert_3>
Severity: 30 : Error

AMQ9846: This operation will generate a copy of your queue manager key repository, which may include private keys. Although encrypted, you should take appropriate security precautions in handling this file. The password required if you ever need to modify or restore this file will be displayed after the copy has been created.
Do you wish to continue? [Y/N]
Severity: 10 : Warning

AMQ9847: Certificate label <insert_3> already in use for queue manager <insert_4>.
Severity: 30 : Error
Explanation: The supplied certificate label <insert_3> is already in use for queue manager <insert_4>
Response: Provide an alternative certificate label.

AMQ9848: No certificate present with label <insert_3> for queue manager <insert_4>.
Severity: 30 : Error
Explanation: Key repository for queue manager <insert_4> does not contain a certificate with the supplied label <insert_3>.
Response: None.

AMQ9849: The operation could not be completed as a key repository back up is already in progress.
Severity: 20 : Error
Explanation: The key repository back up cannot be completed as operation is already in progress.
Response: Retry the operation once the existing key repository back up is complete.

AMQ9871: Cluster maintenance has been running for <insert_1> minutes. Phase <insert_3> has so far made <insert_2> checks
Severity: 0 : Informational
Explanation: A queue manager will periodically perform a maintenance cycle to refresh and remove state associated with the clusters that it is a member of. This message gives an indication of the progress that is being made.
Response: For large clusters this maintenance process may take a significant period of time, in such situations this message will be periodically repeated until maintenance has completed. When the maintenance cycle has completed message AMQ9872 will be written to this log.

AMQ9872: Cluster maintenance has completed after <insert_1> minutes, <insert_2> checks were made
Severity: 0 : Informational
Explanation: A queue manager will periodically perform a maintenance cycle to refresh and remove state associated with the clusters that it is a member of. This message indicates that that cycle has now completed. This message corresponds with one or more instances of message AMQ9871 previously reported.
Response: This message is for informational purposes only, no user response is required.

AMQ9873: An error occurred while restoring the cluster repository cache, reason=<insert_1>
Severity: 30 : Error
Explanation: An error was detected while restoring the cluster cache. The cluster cache held by this queue manager is now incomplete which may result in inconsistencies in cluster resources visible to and owned by this queue manager. See messages in the queue manager and system error logs for details of the error encountered.
Response: Contact your IBM support center to resolve the problem.

AMQ9874: Repository manager failed. Retry in <insert_1> minutes.
Severity: 30 : Error
Explanation: Repository manager encountered a problem. See the earlier messages in the queue manager or system error logs for details. The repository manager will retry the command in <insert_1> minutes. If the problem is not rectified no further cluster management activity will occur. This will affect the availability of cluster resources accessed or hosted by this queue manager.
Response: If possible, rectify the identified problem, otherwise contact your IBM support center. Once the problem has been rectified, if the SYSTEM.CLUSTER.COMMAND.QUEUE queue has been set to GET(DISABLED) set the queue to be GET(ENABLED) and wait for the repository manager to retry the command. If the repository manager process has terminated, restart the queue manager.

AMQ9875: REFRESH CLUSTER processing started for cluster.
Severity: 0 : Informational
Explanation: Refresh cluster processing started for cluster(<insert_3>) A REFRESH CLUSTER command has been issued on this queue manager. In phase one this will discard all locally cached information for the cluster and request new information from other members of the cluster when necessary. Phase two processes the information received. For large cluster configurations this process can take a significant time, especially on full repository queue managers, and during this time applications attempting to access cluster resources may see failures to resolve cluster resources. In addition, cluster configuration changes made on this queue manager may not be processed until the refresh process has completed.
Response: Defer any cluster related work on this queue manager until both phases are complete. Message AMQ9442 or message AMQ9404 will be issued to this log at the end of phase one. Completion of phase two can be determined when SYSTEM.CLUSTER.COMMAND.QUEUE has reached a consistently empty state.

AMQ9876: Cluster management is about to compress a large number of cache records.
Severity: 0 : Informational
Explanation: Periodically cluster management will compress its local cache. Compression can take a significant period of time for certain operations, such as performing a CLUSTER REFRESH. During the compression task, cluster management commands will not be processed. Once the compression task has completed message AMQ9877 will be written to this log.
Response: None.

AMQ9877: Cluster cache compression has completed.
Severity: 0 : Informational
Explanation: A large cache compression has completed. This message corresponds to message AMQ9876 being previously reported.
Response: None.

AMQ9878: Cluster repository command <insert_3> for <insert_5> encountered a problem
Severity: 0 : Informational
Explanation: An internal cluster repository command failed to complete successfully, reporting error reason <insert_1>. Earlier messages in the log will contain details of the problem. The command originated from queue manager <insert_4>, relating to object <insert_5>. Failure to successfully process a command may leave your cluster in an inconsistent state.
Response: Investigate the problems reported. Use the information provided when contacting MQ support.

AMQ9879: Conflicting clustered topic <insert_3>
Severity: 10 : Warning
Explanation: When conflicting clustered topic definitions are detected one or more of the definitions will have a CLSTATE of INVALID and those will not be used by this queue manager. The clustered topic <insert_3> from queue manager <insert_4> has been marked as INVALID. Conflicting clustered topics are those that relate to the same topic string but have different settings for their topic name, cluster route or cluster name. Additionally, clustered topics that are above or below another clustered topic in the topic tree (based on their topic strings) may conflict.
Response: View the clustered topics visible to this queue manager and determine which are the required definitions. Delete or modify the others to remove any conflict. Following this, ensure all clustered topics have a CLSTATE of ACTIVE on all queue managers in the cluster.

AMQ9880: Object <insert_3> in cluster <insert_4> inserted after blanking of description characters.
Severity: 10 : Warning
Explanation: The repository manager received a command to insert object <insert_3> in cluster <insert_4> from the queue manager with QMID <insert_5>. The description characters could not be converted from their source CCSID <insert_1> to the local CCSID <insert_2>. The repository manager has inserted the record in the local cache with a blank description.
Response: You can choose to do nothing. The object is successfully inserted to the local cluster cache, and is usable.
You can choose to go to the queue manager that hosts this object, and change its description to something that includes only a limited set of characters that will convert successfully on the local queue manager.

AMQ9913: The specified local address <insert_3> cannot be resolved to an IP address. The return code is <insert_1>.
Severity: 30 : Error
Explanation: An attempt to resolve the local address hostname to an IP address has failed.
Response: Check that the local address hostname is correct and has an entry in the DNS database.

AMQ9914: The type of local address specified is incompatible with the IP protocol (<insert_3>) used.
Severity: 30 : Error
Explanation: An attempt to use a local address that is incompatible with the IP protocol used.
Response: Make sure that the local address specified is of the same type (IPv4 or IPv6) as the IP Protocol.

AMQ9915: The IP protocol <insert_3> is not present on the system.
Severity: 30 : Error
Explanation: An attempt to use an IP protocol that is not present on the system has been made.
Response: Install the required IP protocol or use an IP protocol that is available on the system. This error can also occur if the system is short of memory or other system resources.

AMQ9920: A SOAP Exception has been thrown.
Severity: 30 : Error
Explanation: A SOAP method encountered a problem and has thrown an exception. Details of the exception are:
<insert_3>
Response: Investigate why the SOAP method threw the exception.

AMQ9921: An error was encountered writing to the dead-letter queue.
Severity: 30 : Error
Explanation: An error was encountered when an attempt was made to write a message to dead-letter queue <insert_3>. The message was <insert_4>.
Response: Ensure that dead-letter queue <insert_3> exists and is put enabled. Ensure that the queue manager attribute DEADQ is set up correctly. Resend the SOAP message.

AMQ9922: Maximum wait time exceeded on queue <insert_3>.
Severity: 30 : Error
Explanation: The maximum time waiting for a message to arrive on queue <insert_3> has been exceeded.
Response: Ensure that the queue is not put inhibited. Ensure that messages are being written to the queue.

AMQ9923: Insufficient parameters on command.
Severity: 30 : Error
Explanation: The SOAP command has been issued with insufficient paramaters.
Response: Supply the correct number of parameters and reissue the command.

AMQ9924: Usage: amqwSOAPNETListener -u wmqUri
[-w WebServiceDirectory] [-n MaxThreads]
[-d StayAlive] [-i IdContext]
[-x TransactionalControl] [-a Integrity] [-? ThisHelp]
Severity: 0 : Informational
Explanation: This shows the correct usage.
Response: None.

AMQ9925: Cannot connect to queue manager <insert_3>.
Severity: 30 : Error
Explanation: A SOAP application or the SOAP listener cannot connect to the queue manager <insert_3> using <insert_4> bindings.
Response: Ensure the bindings are set to the correct value and that the queue manager exists. Check any error messages from the Java MQQueueManager class.

AMQ9926: Null SOAP action specified in a received SOAP message.
Severity: 30 : Error
Explanation: A NULL soap action has been specified in the SOAP message <insert_3>. The message will not be processed.
Response: Include the appropriate SOAP action in the SOAP message.

AMQ9927: MQ queue backout threshold exceeded.
Severity: 30 : Error
Explanation: The IBM MQ backout threshold value has been exceeded for queue <insert_3>, processing message <insert_4>.
Response: Correct the backout threshold value for queue <insert_3> and resend the SOAP message.

AMQ9928: Target service or URI is missing from a SOAP message.
Severity: 30 : Error
Explanation: The target service or the target URI is missing from SOAP message <insert_3>.
Response: Supply a target service or the target URI in the SOAP message.

AMQ9929: Message backout for message (<insert_3>) failed.
Severity: 30 : Error
Explanation: Backout for a message has failed.
Response: Investigate the reason for the backout failure.

AMQ9930: Required Option <insert_3> missing from command.
Severity: 30 : Error
Explanation: The SOAP command was issued with manadatory option <insert_3> missing.
Response: Reissue the SOAP command supplying the missing option.

AMQ9931: Invalid value <insert_3> specified for option <insert_4>.
Severity: 30 : Error
Explanation: THE SOAP command was issued with an invalid value for an option.
Response: Reissue the SOAP command supplying the correct option value.

AMQ9932: Application host class not found
Severity: 30 : Error
Explanation: Application host class <insert_3> has not been found.
Response: Specify the correct application host class in the SOAP message.

AMQ9933: Options <insert_3> and <insert_4> are mutually exclusive
Severity: 30 : Error
Explanation: The SOAP command was issued with incompatible options <insert_3> and <insert_4>.
Response: Reissue the SOAP command supplying compatible options.

AMQ9934: Could not parse URL <insert_3>. MQCC_FAILED(2) MQRC_SOAP_URL_ERROR(2212).
Severity: 30 : Error
Explanation: Could not parse URL <insert_3>. MQCC_FAILED(2) MQRC_SOAP_URL_ERROR(2212).
Response: Correct the URL and retry.

AMQ9935: Illegal URL <insert_3>. MQCC_FAILED(2) MQRC_SOAP_URL_ERROR(2212).
Severity: 30 : Error
Explanation: .The URL <insert_3> failed validation.. MQCC_FAILED(2) MQRC_SOAP_URL_ERROR(2212).
Response: Correct the URL and retry.

AMQ9936: Cannot get connection using <insert_3> bindings. MQCC_FAILED(2) MQRC_CONNECTION_ERROR(2273).
Severity: 30 : Error
Explanation: .Cannot get connection using <insert_3> bindings. MQCC_FAILED(2) MQRC_CONNECTION_ERROR(2273).
Response: Check that the queue manager is available and running.

AMQ9937: The asyncResult is null. MQCC_FAILED(2) MQRC_SOAP_DOTNET_ERROR.(2210).
Severity: 30 : Error
Explanation: .The asyncResult is null. MQCC_FAILED(2) MQRC_SOAP_DOTNET_ERROR.(2210).
Response: Check why the SOAP responses are not being received.

AMQ9938: SOAP/MQ Timeout.
Severity: 30 : Error
Explanation: .The MQGET operation timed out. MQCC_FAILED(2) MQRC_NO_MSG_AVAILABLE.(2033).
Response: Check why the SOAP responses are not being received. MQCC_FAILED(2) MQRC_NO_MSG_AVAILABLE.(2033).

AMQ9939: SOAP/MQ Error. MQCC_FAILED(2) MQRC_SOAP_DOTNET_ERROR.(2210).
Severity: 30 : Error
Explanation: .A SOAP error was detected. MQCC_FAILED(2) MQRC_SOAP_DOTNET_ERROR.(2210).
Response: Check the MQ logs for the reason of the failure.

AMQ9940: Report message returned in MQWebResponse. MQCC_FAILED(2) MQRC_SOAP_DOTNET_ERROR.(2210).
Severity: 30 : Error
Explanation: .Report message returned in MQWebResponse. MQCC_FAILED(2) MQRC_SOAP_DOTNET_ERROR.(2210).
Response: Check the report message for the reason of the failure.

AMQ9941: No RFH2 header recognised. MQCC_FAILED(2) MQRCCF_MD_FORMAT_ERROR(3023).
Severity: 30 : Error
Explanation: .No RFH2 header recognised. MQCC_FAILED(2) MQRCCF_MD_FORMAT_ERROR(3023).
Response: Check why the message is being sent with no RFH2 header.

AMQ9942: Message format is not MQFMT_NONE. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421).
Severity: 30 : Error
Explanation: .Message format is not MQFMT_NONE. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421).
Response: Correct the message format and retry.

AMQ9943: Unrecognised RFH2 version. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421).
Severity: 30 : Error
Explanation: .Unrecognised RFH2 version. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421).
Response: Correct the version in the RFH2 message and retry.

AMQ9944: Invalid RFH2 length. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421).
Severity: 30 : Error
Explanation: .Invalid RFH2 length. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421).
Response: Correct the RFH2 length and retry.

AMQ9945: Illegal RFH2 <insert_3> folder length. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421).
Severity: 30 : Error
Explanation: .Illegal RFH2 <insert_3> folder length. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421).
Response: Correct the RFH2 message and retry.

AMQ9946: Invalid actual message length. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421).
Severity: 30 : Error
Explanation: .Invalid actual message length. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421).
Response: Correct the RFH2 message and retry.

AMQ9947: Illegal RFH2 Folder <insert_3> <insert_4>. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421).
Severity: 30 : Error
Explanation: .Illegal RFH2 Folder <insert_3> <insert_4>. MQCC_FAILED(2) MQRC_RFH_FORMAT_ERROR(2421).
Response: Correct the RFH2 folder syntax/format and retry.

AMQ9948: Backout Threshold exceeded. MQCC_FAILED(2) MQRC_BACKOUT_THRESHOLD_REACHED(2362).
Severity: 30 : Error
Explanation: .Backout Threshold exceeded. MQCC_FAILED(2) MQRC_BACKOUT_THRESHOLD_REACHED(2362).
Response: Correct the backout threshold limit and retry.

AMQ9949: <insert_3> missing from RFH2. MQCC_FAILED(2) MQRC_RFH_PARM_MISSING(2339).
Severity: 30 : Error
Explanation: .<insert_3> missing from RFH2. MQCC_FAILED(2) MQRC_RFH_PARM_MISSING(2339).
Response: Correct the RFH2 message and retry.

AMQ9950: Target service missing from SOAP URL. MQCC_FAILED(2) MQRC_SOAP_URL_ERROR(2212).
Severity: 30 : Error
Explanation: .Target service missing from SOAP URL. MQCC_FAILED(2) MQRC_SOAP_URL_ERROR(2212).
Response: Correct the URL and retry.

AMQ9951: Asynchronous request queued successfully. MQCC_OK(0).
Severity: 30 : Error
Explanation: .Asynchronous request queued successfully. MQCC_OK(0).
Response: Wait for response if any is expected.

AMQ9952: Unexpected message type received. MQCC_FAILED(2) MQRC_UNEXPECTED_MSG_TYPE.(2215).
Severity: 30 : Error
Explanation: .A message of the wrong type was received; for instance, a report message was received when one had not been requested.
Response: If you are running MQ SOAP using the IBM supplied SOAP/MQ sender, please contact IBM. If you are running MQ SOAP using a bespoke sender, please check that the SOAP/MQ request message has the correct options.

AMQ9953: Either the ContentType or the TransportVersion in the RFH2 header have the wrong value. MQCC_FAILED(2) MQRC_RFH_HEADER_FIELD_ERROR(2228)
Severity: 30 : Error
Explanation: .Either the ContentType or the TransportVersion in the RFH2 header have the wrong value. MQCC_FAILED(2) MQRC_RFH_HEADER_FIELD_ERROR(2228)
Response: Correct the message format and retry.

AMQ9954: ViaTran.Redirect called out of transaction MQCC_FAILED(2) MQRC_SOAP_DOTNET_ERROR(2410)
Severity: 30 : Error
Explanation: .ViaTran.Redirect called out of transaction MQCC_FAILED(2) MQRC_SOAP_DOTNET_ERROR(2410)
Response: Make sure ViaTran.Redirect is only called in a transaction.

AMQ9955: Usage: amqswsdl [?] Uri inputFile outputFile
Severity: 0 : Informational
Explanation: This shows the correct usage.
Response: None.

AMQ9990 (IBM i): Keyword <insert_3> not valid for this command or the command is incomplete.
Severity: 40 : Severe
Explanation: The command is incomplete, or an invalid keyword was specified, or the parameter value of the keyword was not specified.
Response: Complete the command, or correct the keyword, or add the parameter value, and then try the command again.

AMQ9991 (IBM i): The value specified is not allowed by the command.
Severity: 40 : Severe
Explanation: <insert_3> not valid for parameter <insert_4>.
Response: Enter one of the values that is defined for the parameter, and try the command again. More information on parameters and commands can be found in the CL reference manual or the appropriate licensed program manual.

AMQ9992 (IBM i): A matching parenthesis not found.
Severity: 40 : Severe
Explanation: A matching left or right parenthesis is missing.
Response: Add the missing parenthesis or remove the extra parenthesis.

AMQ9999: Channel <insert_3> to host <insert_5> ended abnormally.
Severity: 30 : Error
Explanation: The channel program running under process ID <insert_4> for channel <insert_3> ended abnormally. The host name is <insert_5>; in some cases the host name cannot be determined and so is shown as '????'.
Response: Look at previous error messages for the channel program in the error logs to determine the cause of the failure. Note that this message can be excluded completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage" attributes under the "QMErrorLog" stanza in qm.ini. Further information can be found in the System Administration Guide.