IBM WebSphere MQ Advanced Message Security messages

AMS0000
AMS0001
{0}
AMS1000
The IBM WebSphere MQ Advanced Message Security Java interceptor failed to obtain the security policy. Reason Code: ''{0}''
Explanation
The IBM WebSphere MQ Advanced Message Security Java interceptor was not able to obtain the security policy.
Action
See subsequent messages in the exception for more details about the cause of the error.
AMS1010
The IBM WebSphere MQ Advanced Message Security Java interceptor failed to unprotect the received message.
Explanation
An error occurred when the IBM WebSphere MQ Advanced Message Security Java interceptor was unprotecting the received message.
Action
See subsequent messages in the exception for more details about the cause of the error
AMS1011
An internal error occurred: the IBM WebSphere MQ Advanced Message Security Java interceptor failed to get the character set and encoding from the incoming message.
Explanation
An error ocurred when IBM WebSphere MQ Advanced Message Security Java interceptor was getting the CCSID and encoding from the incoming message.
Action
Retry the operation. If the problem persists, contact your IBM service representative.
AMS1020
Usage: specify the keystore password and private key password java -cp{0} com.ibm.mq.ese.config. KeyStoreConfigProtector keystorepass privkeypass
AMS1030
Failed to retrieve the following system properties: ''{0}''
Explanation
An error occurred when retrieving certain system properties.
Action
Ensure that the appropriate java permissions are set up in the java.policy for the Java runtime to retrieve these system properties.
AMS1035
Unknown message code: ''{0}''
Explanation
The text for the message code could not be found in the resource bundles.
Action
Look up information about the displayed message code. Ensure that the appropriate IBM WebSphere MQ language packs are installed on this machine.
AMS1040
Failed to read keystore properties from the keystore configuration file.
Explanation
An error occurred when reading the properties from the keystore configuration file.
Action
Verify that the keystore configuration file is available and that the Java application has read access to this file.
AMS1041
Failed to retrieve the certificate for alias ''{0}'' from the keystore ''{1}''
Explanation
Certificate for the alias could not be retrieved from the keystore.
Action
Use appropriate certificate management tools to ensure that the keystore contains the certificate for the alias.
AMS1042
Failed to retrieve the certificate for alias ''{0}'' from the keystore ''{1}''
Explanation
Certificate for the alias could not be retrieved from the keystore.
Action
Use appropriate certificate management tools to ensure that the keystore contains the certificate for the alias.
AMS1043
Failed to retrieve the certificate for alias ''{0}'' from the keystore ''{1}''
Explanation
Certificate for the alias could not be retrieved from the keystore.
Action
Use appropriate certificate management tools to ensure that the keystore contains the certificate for the alias.
AMS1044
Failed to retrieve the private key for alias ''{0}'' from the keystore ''{1}''
Explanation
Private key for the alias could not be retrieved from the keystore.
Action
Use appropriate certificate management tools to ensure that the keystore contains the private key for the alias.
AMS1045
Failed to retrieve the private key for alias ''{0}'' from the keystore ''{1}''
Explanation
Private key for the alias could not be retrieved from the keystore.
Action
Use appropriate certificate management tools to ensure that the keystore contains the private key for the alias.
AMS1046
Failed to retrieve aliases from the keystore: ''{0}''
Explanation
An error occurred when retrieving aliases from the keystore.
Action
Look at subsequent messages for details on actions to perform to fix this problem.
AMS1047
Alias ''{0}'' not found in the keystore ''{1}''
Explanation
An alias is not found in the keystore.
Action
Look at subsequent messages for details on actions to perform to fix this problem.
AMS1048
Failed to retrieve the certificate chain for alias ''{0}'' from the keystore ''{1}''
Explanation
An error occurred when retrieving the certificate chain for an alias from the keystore.
Action
Look at subsequent messages for details on actions to perform to fix this problem.
AMS1049
Failed to verify whether the entry for alias ''{0}'' in the keystore ''{1}'' contains a certificate.
Explanation
An error occurred when verifying whether the entry for an alias in the keystore contains a certificate.
Action
Look at subsequent messages for details on actions to perform to fix this problem.
AMS1050
Failed to verify whether the entry for alias ''{0}'' in the keystore ''{1}'' contains a private key.
Explanation
An error occurred when verifying whether the entry for an alias in the keystore contains a private key.
Action
Look at subsequent messages for details on actions to perform to fix this problem.
AMS1051
Failed to initialize the keystore ''{0}''
Explanation
Keystore initialization failed.
Action
Look at subsequent messages for details on actions to perform to fix this problem.
AMS1052
Failed to protect the password for alias ''{0}'' in keystore ''{1}''
Explanation
An error occurred when protecting the password for an alias in the keystore.
Action
Look at subsequent messages for details on actions to perform to fix this problem.
AMS1053
Failed to unprotect the password for alias ''{0}'' in keystore ''{1}''
Explanation
An error occurred when unprotecting the password for an alias in the keystore.
Action
Look at subsequent messages for details on actions to perform to fix this problem.
AMS1054
Failed to get the certificates for these recipients: ''{0}''
Explanation
An error occurred when retrieving certificates for recipients.
Action
Verify that the certificates for these recipients are in the local keystore or in the user registry.
AMS1055
An error occurred when trying to retrieve the recipient certificates.
Explanation
An error occurred when trying to retrieve the recipient certificates.
Action
Look at subsequent messages for details on actions to perform to fix this problem.
AMS1056
The message does not contain an IBM® WebSphere® MQ Advanced Message Security header or it contains a header that is not valid.
Explanation
The message does not contain an IBM WebSphere MQ Advanced Message Security header or it contains a header that is not valid.
Action
Make sure that the IBM WebSphere MQ Advanced Message Security security policy is the same for the sender and the receiver.
AMS1057
The IBM WebSphere MQ Advanced Message Security header could not be converted from ''{0}'' to UTF8.
Explanation
An error occurred when converting the IBM WebSphere MQ Advanced Message Security header to UTF8.
Action
Make sure this character encoding is supported by your Java runtime. If the problem persists, contact your IBM service representative.
AMS1058
The IBM WebSphere MQ Advanced Message Security header could not be converted from ''{0}'' to UTF8.
Explanation
An error occurred when converting the IBM WebSphere MQ Advanced Message Security header to UTF8.
Action
Make sure this character encoding is supported by your Java runtime. If the problem persists, contact your IBM service representative.
AMS1059
An internal has error occurred. The IBM WebSphere MQ Advanced Message Security header could not be converted to an array of bytes.
Explanation
An internal error occurred when converting the IBM WebSphere MQ Advanced Message Security header to an array of bytes.
Action
Retry the failing operation. If the problem persists, contact your IBM service representative.
AMS1060
The format of the recipient name ''{0}'' is not valid.
Explanation
The format of the recipient name is not valid.
Action
Set the extended attribute for the recipients to a valid value.
AMS1061
The specified alias ''{0}'' was not found in the keystore ''{1}''
Explanation
The alias could not be located on the keystore.
Action
Use appropriate certificate management tools to ensure that the keystore contains the alias specified.
AMS1062
The specified alias ''{0}'' was not found in the keystore ''{1}''
Explanation
The alias could not be located on the keystore.
Action
Use appropriate certificate management tools to ensure that the keystore contains the alias specified.
AMS1063
The alias ''{0}'' is not a key entry. Keystore: ''{1}''
Explanation
The alias specified is not a key entry.
Action
Use appropriate certificate management tools to ensure that the alias specified is a key entry.
AMS1064
The keystore password can only contain ASCII characters.
Explanation
The keystore password contains non-ASCII characters.
Action
Change your keystore password to contain only ASCII characters.
AMS1065
Could not read following keys from keystore configuration file: ''{0}''.
Explanation
An error occurred when reading properties from the keystore configuration file.
Action
Verify that the property in the keystore configuration file has correct value.
AMS1066
The PKCS11 keystore initialized succesfully, PKCS11 configuration: ''{0}''.
Explanation
The PKCS11 hardware based keystore has been successfully initialized.
Action
No action is required.
AMS1100
The IBM WebSphere MQ Advanced Message Security interceptor could not parse the keystore configuration file.
Explanation
The IBM WebSphere MQ Advanced Message Security interceptor could not parse the keystore configuration file.
Action
Make sure the keystore configuration file contains all required keys and does not contain duplicate keys.
AMS1101
The IBM WebSphere MQ Advanced Message Security keystore configuration file contains duplicate key: ''{0}''.
Explanation
The IBM WebSphere MQ Advanced Message Security keystore configuration file contains duplicate key.
Action
Make sure the keystore configuration file contains all required keys and does not contain duplicate keys.
AMS1102
The IBM WebSphere MQ Advanced Message Security keystore configuration file must contain absolute path ''{0}''.
Explanation
IBM WebSphere MQ Advanced Message Security expected absolute path but found relative one.
Action
Make sure the keystore configuration file contains absolute path.
AMS1120
An internal error occurred: the quality of protection received by the IBM WebSphere MQ Advanced Message Security Java interceptor is not valid. Quality of protection: ''{0}''
Explanation
The quality of protection received by the Java interceptor is not valid.
Action
Retry the failing operation. If the problem persists, contact your IBM service representative.
AMS1121
An internal error occurred: the quality of protection received by the IBM WebSphere MQ Advanced Message Security Java interceptor is not valid. Quality of protection: ''{0}''
Explanation
The quality of protection received by the Java interceptor is not valid.
Action
Retry the failing operation. If the problem persists, contact your IBM service representative.
AMS1122
An internal error occurred: the encryption strength ''{0}'' received by the IBM WebSphere MQ Advanced Message Security Java interceptor is not valid.
Explanation
The encryption strength received by the Java interceptor is not valid.
Action
Retry the failing operation. If the problem persists, contact your IBM service representative.
AMS1123
An internal error occurred: the signature algorithm ''{0}'' received by the IBM WebSphere MQ Advanced Message Security Java interceptor is not valid.
Explanation
The signature algorithm received by the Java interceptor is not valid.
Action
Retry the failing operation. If the problem persists, contact your IBM service representative.
AMS1124
An internal error occurred: the signature algorithm ''{0}'' received by the IBM WebSphere MQ Advanced Message Security Java interceptor is not valid.
Explanation
The signature algorithm received by the Java interceptor is not valid.
Action
Retry the failing operation. If the problem persists, contact your IBM service representative.
AMS1125
The IBM WebSphere MQ Advanced Message Security Java interceptor failed to protect message.
Explanation
The IBM WebSphere MQ Advanced Message Security Java interceptor was not able to protect the message.
Action
See subsequent messages in the exception for more details about the cause of the error.
AMS1126
The IBM WebSphere MQ Advanced Message Security Java interceptor failed to protect message.
Explanation
The IBM WebSphere MQ Advanced Message Security Java interceptor was not able to protect the message.
Action
See subsequent messages in the exception for more details about the cause of the error.
AMS1127
An internal error occurred: the IBM WebSphere MQ Advanced Message Security Java interceptor found more than one sender certificate in the protected message.
Explanation
Only one sender certificate is expected in the protected message.
Action
Retry the failing operation. If the problem persists, contact your IBM service representative.
AMS1128
An internal error occurred: the IBM WebSphere MQ Advanced Message Security Java interceptor failed to find the certificate of the sender in the protected message.
Explanation
The Java interceptor failed to find the certificate of the sender. The protected message is expected to contain the certificate of the sender.
Action
Retry the failing operation. If the problem persists, contact your IBM service representative.
AMS1129
An internal error occurred: the syntax of the protected message received by IBM WebSphere MQ Advanced Message Security Java interceptor is not valid.
Explanation
The syntax of the protected message received by the Java interceptor is not valid.
Action
Ensure that your security policy is specified correctly and retry the failing operation. If the problem persists, contact your IBM service representative.
AMS1130
The IBM WebSphere MQ Advanced Message Security Java interceptor failed to unprotect message.
Explanation
The IBM WebSphere MQ Advanced Message Security Java interceptor was not able to unprotect the message.
Action
See subsequent messages in the exception for more details about the cause of the error.
AMS1131
An internal error occurred: the IBM WebSphere MQ Advanced Message Security Java interceptor failed to find any recipients from the received message.
Explanation
The IBM WebSphere MQ Advanced Message Security Java interceptor was not able to obtain any recipients from the received message.
Action
Retry the failing operation. If the problem persists, contact your IBM service representative.
AMS1132
The certificate of the sender with the subject name ''{0}'' is not valid.
Explanation
The certificate of the sender is not valid.
Action
See subsequent messages in the exception for more details about the cause of the error.
AMS1133
The certificate of the sender with the subject name ''{0}'' is not valid.
Explanation
The certificate of the sender is not valid.
Action
See subsequent messages in the exception for more details about the cause of the error.
AMS1134
The certificate of the recipient with the subject name ''{0}'' is not valid.
Explanation
The certificate of the recipient is not valid.
Action
See subsequent messages in the exception for more details about the cause of the error.
AMS1135
The protected message type does not match the quality of protection (QOP) specified on the objectspace. The expected QOP is ''{0}'' whereas the actual one is ''{1}''
Explanation
The protected message type does not match the QOP specified on the object space.
Action
Verify that the security policy is correctly specified.
AMS1136
The IBM WebSphere MQ Advanced Message Security Java interceptor failed to decrypt the protected message.
Explanation
The IBM WebSphere MQ Advanced Message Security Java interceptor was not able to decrypt the protected message.
Action
See subsequent messages in the exception for more details about the cause of the error.
AMS1137
The IBM WebSphere MQ Advanced Message Security Java interceptor failed to verify the protected message signature.
Explanation
The IBM WebSphere MQ Advanced Message Security Java interceptor was not able to verify the protected message signature.
Action
See subsequent messages in the exception for more details about the cause of the error.
AMS1138
The IBM WebSphere MQ Advanced Message Security Java interceptor failed to verify the certificate trust chain. The certificate subject name: ''{0}''
Explanation
The IBM WebSphere MQ Advanced Message Security Java interceptor was not able to verify the certificate trust chain.
Action
See subsequent messages in the exception for more details about the cause of the error.
AMS1139
The protected message encryption mismatch. The expected encryption strength is ''{0}'' whereas the actual encryption strength is ''{1}''
Explanation
The protected message encryption does not match the one specified on the object space.
Action
Verify that the security policy is correctly specified.
AMS1140
The receiver of this encrypted message is not on the message recipient list ''{0}''
Explanation
The certificate of a user that is receiving a message is not on the message RecipientsInfo list.
Action
Verify that the user is on a recipients list in a security policy definition.
AMS1200
The certificate with the following subject name ''{0}'' is not yet valid. The certificate will become valid after ''{1}''
Explanation
The certificate is not yet within its validity period.
Action
Retry the failing operation as soon as the certificate is valid or modify your configuration to use a valid certificate.
AMS1201
The certificate with the following subject name ''{0}'' is expired. The expiration date of the certificate is ''{1}''
Explanation
The certificate is expired.
Action
Modify your configuration to use a valid certificate.
AMS1202
The IBM WebSphere MQ Advanced Message Security Java interceptor failed to verify the validity period of the certificate. The subject name of the certificate is ''{0}''
Explanation
The IBM WebSphere MQ Advanced Message Security Java interceptor was not able to verify the validity period of a certificate.
Action
Retry the failing operation. If the problem persists, contact your IBM service representative.
AMS1203
A key usage bit that is not valid was found on the certificate with the following subject name ''{0}''. The ''{1}'' key usage bit should be set to ''{2}'' instead of ''{3}''
Explanation
A key usage bit that is not valid was found on the certificate.
Action
Modify your configuration to use a certificate that has a valid key usage extension. Consult the Administration guide for more details about certificate settings.
AMS1204
An internal error occurred: the IBM WebSphere MQ Advanced Message Security Java interceptor failed to obtain the encryption algorithm name.
Explanation
An internal error occurred: the IBM WebSphere MQ Advanced Message Security Java interceptor failed to obtain the encryption algorithm name.
Action
Retry the failing operation. If the problem persists, contact your IBM service representative.
AMS1205
The IBM WebSphere MQ Advanced Message Security Java interceptor failed to obtain any recipient certificate.
Explanation
The IBM WebSphere MQ Advanced Message Security Java interceptor attempted to encrypt a message, but it did not find certificates of recipients
Action
Make sure that a keystore contains all certificates specifed in the appropriate security policy.
AMS1206
The IBM WebSphere MQ Advanced Message Security Java interceptor failed to obtain any recipient certificate.
Explanation
The IBM WebSphere MQ Advanced Message Security Java interceptor attempted to encrypt a message, but it did not find certificates of recipients
Action
Make sure that a keystore contains all certificates specifed in the appropriate security policy.
AMS1207
An internal error occurred: the IBM WebSphere MQ Advanced Message Security Java interceptor failed to obtain the signature algorithm name.
Explanation
An internal error occurred: the IBM WebSphere MQ Advanced Message Security Java interceptor failed to obtain the signature algorithm name.
Action
Retry the failing operation. If the problem persists, contact your IBM service representative.
AMS1208
No proper key bit was found for the certificate for the subject name ''{0}''. The actual values are: ''{1}'', the proper values are: ''{2}'', the state of at least one bit should match.
Explanation
A key usage bit that is not valid was found on the certificate.
Action
Modify your configuration to use a certificate that has a valid key usage extension. Consult the Administration guide for more details about certificate settings.
AMS1209
IBM WebSphere MQ Advanced Message Security Java interceptor failed to verify CRL signature signed by ''{0}''
Explanation
IBM WebSphere MQ Advanced Message Security Java interceptor failed to verify CRL signed by the given issuer DN
Action
Make sure certificate of the issuer is present in the local keystore.
AMS1210
The Certificate Revocation List ''{0}'' could not be loaded
Explanation
The CRL cannot be found or accessed.
Action
Modify your configuration to point to a valid CRL. Make sure the CRL can be read.
AMS1211
The IBM WebSphere MQ Advanced Message Security Java interceptor could not access Certificate Revocation List.
Explanation
The CRL cannot be found or accessed.
Action
Modify your configuration to point to a valid CRL. Make sure the CRL can be read.
AMS1212
The IBM WebSphere MQ Advanced Message Security Java interceptor failed to validate the certificate. A certificate with BasicConstraint CA set to true cannot be used as End Entity. The subject name is ''{0}''
Explanation
The IBM WebSphere MQ Advanced Message Security Java interceptor was not able to verify the certificate.
AMS1213
The IBM WebSphere MQ Advanced Message Security Java interceptor failed to validate the certificate. A certificate with the subject name ''{0}'' has been revoked.
Explanation
The IBM WebSphere MQ Advanced Message Security Java interceptor was not able to verify the certificate.
AMS1300
IBM WebSphere MQ Advanced Message Security internal error: queue manager information could not be saved.(''{0}'')
Explanation
The IBM WebSphere MQ Advanced Message Security interceptor could not save the queue manager connection (hconn) information because an internal error occurred.
Action
If the problem occurs persistently, contact your IBM service representative.
AMS1310
IBM WebSphere MQ Advanced Message Security could not resolve current queue name from the object handle.(''{0}'')
Explanation
The IBM WebSphere MQ Advanced Message Security interceptor could not resolve the current queue name from the object handle. The queue might be opened by some internal WebSphere MQ application program interface (API) other than Message Queue Interface (MQI).
Action
Make sure the application does not use internal WebSphere MQ APIs to open the queue. If the problem persists, contact your IBM service representative.
AMS1311
MQOPEN() call failed: reason code (''{0}'').
Explanation
The IBM WebSphere MQ Advanced Message Security interceptor call to the WebSphere MQ MQOPEN() function failed with the indicated error.
Action
Consult the WebSphere MQ documentation for an explanation of the error code and suggested corrective action. Ensure that the queue manager is operational, the queue exists.
AMS1312
MQCLOSE() call failed, reason code (''{0}'').
Explanation
The IBM WebSphere MQ Advanced Message Security interceptor call to the WebSphere MQ MQCLOSE() function failed with the indicated WebSphere MQ reason code.
Action
Consult the IBM WebSphere MQ documentation for an explanation of the error code and suggested corrective action. Ensure that the queue manager is operational, protected object space are present and correct. Make sure that IBM WebSphere MQ Advanced Message Security are configured and running correctly.
AMS1313
IBM WebSphere MQ Advanced Message Security internal error: message could not be protected because the specified signature algorithm ''{0}'' is not valid.
Explanation
The unexpected signature algorithm has been specified
Action
This is an internal error. Contact your IBM service representative
AMS1325
IBM WebSphere MQ Advanced Message Security internal error: queue information could not be resolved from the current queue object handle. (''{0}'')
Explanation
The IBM WebSphere MQ Advanced Message Security interceptor could not resolve queue information from the current queue object handle because the current queue was not opened by IBM WebSphere MQ Advanced Message Security, or it was closed.
Action
Make sure that the queue has not already been opened by another WebSphere MQ application and that it has not been previously closed. If the problem persists, contact your IBM service representative.
AMS1326
IBM WebSphere MQ Advanced Message Security internal error: could not find local queue manager CodedCharSetId (''{0}'').
Explanation
The IBM WebSphere MQ Advanced Message Security interceptor could not find the local queue manager's CodedCharSetId because an internal error occurred.
Action
Make sure that the queue manager is connected through IBM WebSphere MQ Advanced Message Security. If the problem persists, contact your IBM service representative.
AMS1327
Quality of protection ''{0}'' for queue ''{1}'' is invalid
Explanation
The IBM WebSphere MQ Advanced Message Security interceptor detected that the quality of protection specified in the security policy for the queue is invalid.
Action
Make sure that the encryption and signature algorithms specified for the queue in the IBM WebSphere MQ Advanced Message Security security policy definition have valid values.
AMS1328
Message with no protection has been put into the queue ''{0}''.
Explanation
The IBM WebSphere MQ Advanced Message Security interceptor has successfully put a message with the 'none' protection level onto the selected queue.
Action
No action is required.
AMS1329
Message with integrity protection has been put into the queue ''{0}''.
Explanation
The IBM WebSphere MQ Advanced Message Security interceptor has successfully put a message with the 'integrity' protection level onto the selected queue.
Action
No action is required.
AMS1330
Message with privacy protection has been put into the queue ''{0}''.
Explanation
The IBM WebSphere MQ Advanced Message Security interceptor has successfully put a message with the 'privacy' protection level onto the selected queue.
Action
No action is required.
AMS1331
IBM WebSphere MQ Advanced Message Security internal error: could not inquire about queue manager properties (''{0}'').
Explanation
The IBM WebSphere MQ Advanced Message Security interceptor could not inquire about queue manager's properties because an internal error occurred.
Action
Make sure that the queue manager is connected through IBM WebSphere MQ Advanced Message Security. If the problem persists, contact your IBM service representative.
AMS1340
IBM WebSphere MQ Advanced Message Security internal error: queue information could not be resolved from the current queue object handle. (''{0}'')
Explanation
The IBM WebSphere MQ Advanced Message Security interceptor could not resolve queue information from the current queue object handle because the current queue was not opened by IBM WebSphere MQ Advanced Message Security, or it was closed.
Action
Make sure that the queue is not already been opened by another WebSphere MQ application, and that it has not been previously closed. If the problem persists, contact your IBM service representative.
AMS1341
IBM WebSphere MQ Advanced Message Security found a valid 'PDMQ' format header in the current message.
Explanation
IBM WebSphere MQ Advanced Message Security interceptor found a valid IBM WebSphere MQ Advanced Message Security header in the current message.
Action
No action is required.
AMS1342
The 'PDMQ' format header from the current message is invalid.
Explanation
The IBM WebSphere MQ Advanced Message Security interceptor did not find a valid IBM WebSphere MQ Advanced Message Security header in the the current message.
Action
Check the Quality of Protection (QoP) setting for the queue object. If the QoP setting for the queue is not 'none', make sure that no IBM WebSphere MQ plain text messages are routed to this queue.
AMS1343
Message quality of protection (''{0}'') does not match the quality of protection (''{1}'') set for the queue ''{2}''.
Explanation
The IBM WebSphere MQ Advanced Message Security 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.
Action
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.
AMS1344
''{0}'' - message was signed by ''{1}'' at ''{2}'' using ''{3}''.
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.
Action
No action is required.
AMS1345
''{0}'' - message was signed and encrypted by ''{1}'' at ''{2}'' using ''{3}'' and ''{4}''.
Explanation
This is an informational message used to indicate that a message was signed and encrypted, and to display the signer's name, message timestamp, signature algorithm name and encryption algorithm name.
Action
No action is required.
AMS1346
Message does not have a valid protection type.
Explanation
The IBM WebSphere MQ Advanced Message Security interceptor detected an invalid protection type in a message header. This usually occurs because the IBM WebSphere MQ message header is not valid.
Action
Retry the operation. If the problem persists, contact your IBM service representative.
AMS1347
The IBM WebSphere MQ Advanced Message Security interceptor has put a defective message on error handling queue ''{0}''.
Explanation
This is an informational message that indicates the IBM WebSphere MQ Advanced Message Security put a message it could not interpret on the specified error handling queue.
Action
Make sure only valid messages are put onto queues protected by IBM WebSphere MQ Advanced Message Security.
AMS1348
The IBM WebSphere MQ Advanced Message Security interceptor failed to put a defective message on error handling queue. MQ reason code (''{0}'')
Explanation
The IBM WebSphere MQ Advanced Message Security interceptor was unable to put a message it could not interpret on the error handling queue because the indicated IBM WebSphere MQ error occurred.
Action
Consult the IBM WebSphere MQ documentation for more information about the reason code. If the problem persists, contact your IBM service representativ.
AMS1349
IBM WebSphere MQ Advanced Message Security internal error: message could not be converted from source CCSID ''{0}'' to target CCSID ''{1}''. IBM WebSphere MQ compcode ''{2}'' : reason ''{3}''.
Explanation
The IBM WebSphere MQ Advanced Message Security interceptor could not convert the message from the source Coded Character Set Identifier (CCSID) to target CCSID.
Action
Consult the IBM WebSphere MQ documentation for the completion code and reason code, take corrective action. If the problem persists, contact your IBM service representative.
AMS1350
IBM WebSphere MQ Advanced Message Security internal error: message could not be retrieved from the queue. MQGET() failed. IBM WebSphere MQ compcode ''{0}'' : reason ''{1}''.
Explanation
The IBM WebSphere MQ Advanced Message Security interceptor could not get the message from the queue.
Action
Consult the IBM WebSphere MQ documentation for the completion code and reason code, take corrective action. If the problem persists, contact your IBM service representative.
AMS1351
IBM WebSphere MQ Advanced Message Security internal error: unprotected message size ''{0}'' bytes does not match the original message size ''{1}'' bytes.
Explanation
After unprotecting, the message size does not match the original message size. The message header might have been corrupted or tampered with.
Action
Check the message which has been put on the dead letter queue and the audit logs to find the cause of the error and the origin of the message. If the problem persists, contact your IBM service representative.
AMS1352
IBM WebSphere MQ Advanced Message Security internal error: unprotected message QoP does not match QoP indicated in the header. Queue manager is ''{0}'', queue is ''{1}'', msgId is ''{2}''
Explanation
During unprotecting the mismatch between the message buffer quality of protection type and the one specified by the IBM WebSphere MQ Advanced Message Security header was discovered. The message header might have been corrupted or tampered with.
Action
Check the message which has been put into the dead letter queue and the audit logs to find the cause of the error and the origin of the message. If the problem persists, contact your IBM service representative.
AMS1353
Message with quality of protection (''{0}'') higher than (''{1}'') set for the queue ''{2}'' has been accepted.
Explanation
The IBM WebSphere MQ Advanced Message Security 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.
Action
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.
AMS1354
Message signer is not in the list of authorised signers.
Explanation
The IBM WebSphere MQ Advanced Message Security interceptor detected that the message is signed by an unauthorised party.
Action
Make sure the sender is mentioned in the list of allowed signers.
AMS1355
Message could not be moved from queue (''{0}'') to error handling queue. IBM WebSphere MQ completion code (''{1}''), reason code (''{2}'').
Explanation
The IBM WebSphere MQ Advanced Message Security interceptor failed to remove the message before it attempted to put it on error handling queue.
Action
Consult the IBM WebSphere MQ documentation for the completion code and reason code, take corrective action. If the problem persists, contact your IBM service representative.
AMS1356
Message too big to fit the buffer, queue (''{0}''), MQ completion code (''{1}''), reason code (''{2}'').
Explanation
The IBM WebSphere MQ Advanced Message Security interceptor failed to unprotect data because provided buffer is too small
Action
Issue MQGET with bigger buffer
amq9001
Channel '&3' ended normally.
Explanation
Channel '&3' to host '&5' ended normally.
Action
None.
amq9002
Channel '&3' is starting.
Explanation
Channel '&3' is starting.
Action
None.
amq9005
The WebSphere MQ security policy interceptor failed to access the Public-Key Cryptography Standards (PKCS) #11 hardware token.
Explanation
The WebSphere MQ security policy interceptor failed in an attempt to open a Public-Key Cryptography Standards (PKCS) #11 token. Check GSKit ACME GSS minor reason&1 for '&3'.
Action
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 WebSphere MQ security policy interceptor did not attempt to open a PKCS #11 token because it did not have all required configuration information.
Explanation
The WebSphere 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.
Action
If you want to use a PKCS #11 token, make sure that the token label, PIN, and library name are configured correctly.
amq9007
The WebSphere MQ security policy interceptor failed to convert a Public-Key Cryptography Standards (PKCS) #11 key certificate label.
Explanation
The WebSphere 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&1.
Action
Make sure that the PKCS #11 key certificate label is defined correctly.
amq9008
Cannot acquire the certificate for the label:&3 in the keystore file&4. GSKit ACME GSS minor reason is&1.
Explanation
WebSphere MQ security policy interceptor was unable to read the certificate for the given label from keystore.
Action
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&1.
Explanation
WebSphere MQ security policy interceptor was unable to acquire credentials.
Action
Review the configuration to make sure the keystore database and stash files are not broken.
amq9010
WebSphere MQ security policy internal error: message could not be protected because specified encryption algorithm is not valid&1.
Explanation
The value identifier is specified to unexpected value.
Action
This is an internal error. Contact your IBM service representative.
amq9011
The WebSphere 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&1.
Explanation
The WebSphere MQ security policy interceptor failed to register the Public-Key Cryptography Standards (PKCS) #11 cryptographic algorithm with the ACME environment.
Action
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 WebSphere MQ security policy interceptor could not acquire the public key credential.
Explanation
The WebSphere MQ security policy interceptor could not perform a public key infrastructure (PKI) login.
Action
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
WebSphere MQ security policy internal error: the Independent Data Unit Protection (IDUP) environment could not be terminated. GSKit reason code&1.
Explanation
The WebSphere MQ security policy interceptor could not release the GSKit IDUP environment because an internal error occurred.
Action
Consult the GSKit appendix in the product documentation for the explanation of the GSKit reason code and take corrective action. If the problem persists, contact your IBM service representative.
amq9014
The WebSphere MQ security policy interceptor failed to close a Public-Key Cryptography Standards (PKCS) #11 token. Check GSKit ACME GSS minor reason&1.
Explanation
The WebSphere MQ security policy interceptor failed to close a Public-Key Cryptography Standards (PKCS) #11 token.
Action
Make sure that the PKCS #11 token is functioning properly and retry the operation. If the problem persists, contact your IBM service representative.
amq9015
WebSphere MQ security policy internal warning: GSKit could not release&3. GSKit reason code&1.
Explanation
The WebSphere MQ security policy GSKit call with the indicated reason code failed because it could not release resources back to the system.
Action
No action is required. If the problem persists, contact your IBM service representative.
amq9016
WebSphere MQ security policy internal error: GSKit could not allocate&3. GSKit reason code&1.
Explanation
The WebSphere MQ security policy GSKit call with the indicated reason code failed because the system could not allocate resources.
Action
Make sure the system meets hardware and software requirements necessary to execute the application, then restart the application.
amq9017
WebSphere MQ security policy internal error: message could not be unprotected: GSKit error code&1, reason&2.
Explanation
The WebSphere 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.
Action
Consult the GSKit information in the product documentation 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 '&3' is not supported on this platform.
Explanation
The WebSphere MQ security policy interceptor failed to apply a policy as this platform lacks support for SHA-2 signing algorithm.
Action
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
WebSphere MQ security policy internal error: message could not be protected because specified signature algorithm is not valid&1
Explanation
The value identifier is specified to unexpected value.
Action
This is an internal error. Contact your IBM service representative.
amq9020
WebSphere MQ security policy internal error: message could not be protected because no recipients' DN is specified.
Explanation
The policy is set to privacy but does not contain any recipient DN.
Action
This is an internal error. Contact your IBM service representative.
amq9021
An error occurred during the certificate import for the following DN:&3, result:&1
Explanation
The distinguished name is not present in the keystore or invalid.
Action
Consult the GSKit appendix in the product documentation for the explanation of the GSKit reason code and take corrective action. If the problem persists, contact your IBM service representative.
amq9022
An error occurred during the certificate import for the following DN:&3, result:&1, reason:&2.
Explanation
The distinguished name is not present in the keystore or invalid.
Action
Consult the GSKit appendix in the product documentation 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 '&3' was incorrectly provided with the file extension '&4'
Explanation
The WebSphere 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.
Action
Ensure the keystore file name specified in the configuration file does not contain a file extension.
amq9024
The keystore file '&3' does not exist and the keystore configuration entry incorrectly ends with '&4'. Make sure the value of the keystore configuration does not contain the file extension and it points to an existing file.
Explanation
The WebSphere MQ security policy interceptor was unable to find the keystore file. The value of the keystore configuration entry incorrectly contains the file extension of '&4' and the resultant filename of '&3' does not exist.
Action
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&3&4 does not exist. Make sure the value of the keystore configuration entry points to an existing file.
Explanation
WebSphere MQ security policy interceptor was unable to find the keystore database file.
Action
Make sure the value of the keystore configuration entry points to an existing file.
amq9026
Cannot read the keystore file&3&4. Check the file permissions.
Explanation
WebSphere MQ security policy interceptor was unable to read the keystore database file.
Action
Set the proper permissions for the keystore database file.
amq9027
Cannot access the keystore file&3&4. Error code&1.
Explanation
WebSphere MQ security policy interceptor was unable to open the keystore database file.
Action
Ensure the application accessing the keystore file has appropriate permissions to access the keystore file.
amq9028
The keystore stash file&3&4 does not exist.
Explanation
WebSphere MQ security policy interceptor was unable to find the keystore stash file.
Action
Ensure the application accessing the keystore stash file has appropriate permissions to access the file.
amq9029
Cannot read the keystore stash file&3&4.
Explanation
WebSphere MQ security policy interceptor was unable to read the keystore stash file.
Action
Check the permissions for the keystore stash file.
amq9030
WebSphere MQ security policy internal error: queue information could not be resolved from the current queue object handle (&1).
Explanation
The WebSphere MQ security policy interceptor could not resolve queue information from the current queue object handle because the object handle is invalid or unrecognised.
Action
Make sure that the queue has not already been opened by another WebSphere MQ application and that it has not been previously closed. If the problem persists, contact your IBM service representative.
amq9031
WebSphere MQ security policy interceptor has detected an error prior to callback exit execution. WebSphere MQ compcode&1 : reason&2.
Explanation
The WebSphere MQ security policy interceptor received an WebSphere MQ completion code indicating an error prior to interceptor execution.
Action
Consult the product documentation for the completion code and reason code, take corrective action. If the problem persists, contact your IBM service representative.
amq9032
WebSphere MQ security policy interceptor could not find queue manager CodedCharSetId (&1). Make sure you have permission to inquire about queue manager properties.
Explanation
The WebSphere MQ security policy interceptor could not find the local queue manager's CodedCharSetId because an internal error occurred.
Action
Make sure that the application has inquire permission to the queue manager. If the problem persists, contact your IBM service representative.
amq9033
WebSphere MQ security policy internal error: could not find local queue manager CodedCharSetId (&1).
Explanation
The WebSphere MQ security policy interceptor could not find the local queue manager's CodedCharSetId because an internal error occurred.
Action
If the problem persists, contact your IBM service representative.
amq9034
Message does not have a valid protection type.
Explanation
The WebSphere MQ security policy interceptor detected an invalid protection type in a message header. This usually occurs because the WebSphere MQ message header is not valid.
Action
Retry the operation. If the problem persists, contact your IBM service representative.
amq9035
Message signer is not in the list of authorised signers.
Explanation
The WebSphere MQ security policy interceptor detected that the message is signed by an unauthorised party.
Action
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 (&1).
Explanation
The WebSphere MQ security policy interceptor call to the WebSphere MQ MQOPEN() call failed with the indicated error.
Action
Consult the product documentation for an explanation of the error code and suggested corrective action. Ensure that the queue manager is operational and the queue exists.
amq9037
The WebSphere MQ security policy interceptor failed to process a message on queue&3 with CompCode&1 Reason code&2
Explanation
An unexpected error was encountered whilst applying a security policy to queue&3.
Action
This is an internal error. Contact your IBM service representative.
amq9038
The WebSphere MQ security policy interceptor failed to convert the&3 field of the WebSphere MQ header from CCSID&1 to CCSID&2. Verify that default data conversion has been enabled in WebSphere MQ.
Explanation
The WebSphere MQ security policy interceptor internal error: data conversion failed. This is usually a problem with incompatible character sets.
Action
Enable default data conversion in WebSphere MQ. If the problem persists, contact your IBM service representative.
amq9039
&3 - message was signed by&4 using&5.
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.
Action
None.
amq9040
&3 - message was signed and encrypted by&4 using&5.
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.
Action
None.
amq9041
Message was not protected.
Explanation
This is an informational message used to indicate that a message was neither signed nor encrypted.
Action
None.
amq9042
WebSphere MQ security policy internal error: unprotected message size&1 bytes does not match the original message size&2 bytes.
Explanation
After unprotecting, the message size does not match the original message size. The message header might have been corrupted or tampered with.
Action
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&3 is different than the required&4.
Explanation
The WebSphere 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.
Action
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 WebSphere MQ security policy interceptor has put a defective message on error handling queue&3.
Explanation
This is an informational message that indicates the WebSphere MQ security policy put a message it could not interpret on the specified error handling queue.
Action
Make sure only valid messages are put onto queues protected by WebSphere MQ security policies.
amq9045
The WebSphere MQ security policy interceptor failed to put a defective message on error handling queue. WebSphere MQ reason code (&1)
Explanation
The WebSphere MQ security policy interceptor was unable to put a message it could not interpret on the error handling queue because the indicated WebSphere MQ error occurred.
Action
Consult the product documentation 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.
Explanation
The WebSphere MQ security policy interceptor did not find a valid WebSphere MQ security policy header in the the current message.
Action
If the QoP setting for the queue is not set to 'none', make sure that no unprotected messages are routed to this queue.
amq9047
WebSphere MQ security policy found a valid 'PDMQ' format header in the current message.
Explanation
WebSphere MQ security policy interceptor found a valid WebSphere MQ security policy header in the current message.
Action
None.
amq9048
Message quality of protection (&1) does not match the quality of protection (&2) set for the queue&3.
Explanation
The WebSphere 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.
Action
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 (&1) higher than (&2) set for the queue&3 has been accepted.
Explanation
The WebSphere 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.
Action
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
WebSphere MQ security policy could not access the security policy definitions. Major code&1 : Minor code&2
Explanation
The security policy definitions cannot be accessed.
Action
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
WebSphere MQ could not find the security policy definition. Compcode&1 : reason&2
Explanation
The security policy definition is not defined.
Action
Security policy definition must be defined before this action.
amq9052
Message with no protection has been put into the queue&3.
Explanation
The WebSphere MQ security policy interceptor has successfully put a message with a QoP of 'none' onto the selected queue.
Action
None.
amq9053
Message with integrity protection has been put into the queue&3.
Explanation
The WebSphere MQ security policy interceptor has successfully put a message with a QoP of 'integrity' onto the selected queue.
Action
None.
amq9054
Message with privacy protection has been put into the queue&3.
Explanation
The WebSphere MQ security policy interceptor has successfully put a message with a QoP of 'privacy' onto the selected queue.
Action
None.
amq9055
Quality of protection (QoP)&1 for queue&3 is invalid
Explanation
The WebSphere MQ security policy interceptor detected that the quality of protection specified in the security policy for the queue is invalid.
Action
Ensure that the encryption and signature algorithms specified for the queue in the WebSphere MQ security policy definition have valid values.
amq9056
WebSphere MQ security policy internal error: message could not be protected because the specified signature algorithm&1 is not valid.
Explanation
An unexpected signature algorithm has been specified.
Action
This is an internal error. Contact your IBM service representative.
amq9057
WebSphere MQ security policy internal error: message could not be processed because the specified encryption algorithm&1 is not valid.
Explanation
An unexpected encryption algorithm has been specified.
Action
This is an internal error. Contact your IBM service representative.
amq9058
The WebSphere MQ security policy interceptor cannot inquire the attributes for queue manager&3.
Explanation
The WebSphere MQ security policy interceptor failed to inquire queue manager attributes, compcode&1, reason code&2.
Action
Make sure that the application has appropriate access control permissions to inquire the queue manager object.
amq9059
The WebSphere MQ security policy interceptor failed to generate a configuration event for queue manager&3.
Explanation
The WebSphere MQ security policy interceptor failed to generate a configuration event, comp code&1, reason code&2.
Action
Ensure that the SYSTEM.ADMIN.CONFIG.EVENT queue is available for output from this process.
amq9060
The WebSphere MQ security policy keystore configuration file contains duplicate key:&3.
Explanation
The WebSphere MQ security policy keystore configuration file contains duplicate key:&3.
Action
Make sure the keystore configuration file contains all required keys and does not contain duplicate keys.
amq9061
The WebSphere MQ security policy keystore configuration file does not contain key&3.
Explanation
The WebSphere MQ security policy keystore configuration file does not contain key&3.
Action
Make sure the keystore configuration file contains all required keys and does not contain duplicate keys.
amq9062
The WebSphere MQ security policy interceptor could not read the keystore configuration file:&3.
Explanation
The WebSphere MQ security policy interceptor could not read the keystore configuration file:&3.
Action
Make sure that the user who executes the WebSphere 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 WebSphere MQ security policy interceptor could not parse the keystore configuration file.
Explanation
The WebSphere MQ security policy interceptor could not parse the keystore configuration file.
Action
Make sure the keystore configuration file contains all required keys and does not contain duplicate keys.
amq9064
The WebSphere MQ security policy interceptor failed to enable OCSP checking.
Explanation
The WebSphere MQ security policy interceptor encountered an error while configuring OCSP checking.
Action
Check the OCSP configuration, making sure that all parameters are specified correctly.
amq9065
The WebSphere MQ security policy interceptor failed to process the OCSP configuration.
Explanation
The OCSP configuration for WebSphere MQ is incorrect.
Action
Check the OCSP configuration, making sure that all mandatory parameters are specified.
amq9066
The WebSphere MQ security policy interceptor failed to enable CRL checking.
Explanation
The WebSphere MQ security policy interceptor encountered an error while configuring CRL checking.
Action
Check the CRL configuration, making sure that all parameters are correctly specified.
amq9067
The WebSphere MQ security policy interceptor failed to process the CRL configuration.
Explanation
The WebSphere MQ security policy interceptor failedto process the CRL configuration information.
Action
Check the CRL configuration, making sure that all mandatory parameters are specified.
amq9068
The WebSphere MQ security policy interceptor could not enable revocation checking.
Explanation
The WebSphere 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.
Action
The currently enabled version of GSKit does not meet the minimum requirements for WebSphere MQ security policy revocation checking. Install a newer version of GSKit that does meet the minimum requirements.
amq9069
The WebSphere MQ security policy interceptor failed to validate a certificate, GSKit status:&3.
Explanation
The WebSphere MQ security policy interceptor failed to validate a certificate.
Action
Read the GSKit log to determine the cause of validation failure.
amq9070
The WebSphere MQ security policy interceptor failed to validate a certificate.
Explanation
The WebSphere MQ security policy interceptor could not validate a certificate.
Action
Read the GSKit logs to determine the cause of validation failure.
amq9071
WebSphere MQ security policy interceptor internal error: could not read GSKit attribute&3, GSKit reason code:&1.
Explanation
The GSKit gskacme_cred_get function failed.
Action
Make sure you are using the correct version of GSKit for this installation of WebSphere MQ.
amq9072
The certificate revocation status is UNKNOWN, GSKit log:&3.
Explanation
The WebSphere MQ security policy interceptor failed to determine the certificate revocation status.
Action
Read the GSKit log to find out the certificate DN and serial number.
amq9073
The certificate revocation status is UNKNOWN, GSKit log:&3.
Explanation
The WebSphere MQ security policy interceptor failed to determine the certificate revocation status.
Action
Read the GSKit log to find out the certificate DN and serial number.
amq9074
The Trial Period license for this copy of WebSphere MQ Advanced Message Security has expired.
Explanation
This copy of WebSphere MQ Advanced Message Security was licensed to be used in trial mode for a limited period only. This period has expired.
Action
Install a Production license for this copy of WebSphere MQ Advanced Message Security.
amq9075
The Beta license for this copy of WebSphere MQ Advanced Message Security has expired.
Explanation
This copy of WebSphere MQ Advanced Message Security was licensed to be used for Beta testing for a limited period only. This period has expired.
Action
Install a Production license for this copy of WebSphere MQ Advanced Message Security.
amq9076
There are&1 days left in the trial period for this copy of WebSphere MQ Advanced Message Security.
Explanation
This copy of WebSphere MQ Advanced Message Security is licensed for a limited period only.
Action
None.
amq9077
This is the final day of the trial period for this copy of WebSphere MQ Advanced Message Security.
Explanation
This copy of WebSphere MQ Advanced Message Security is licensed for a limited period only.
Action
Install a Production license for this copy of WebSphere MQ Advanced Message Security.
amq9078
There is one day left in the trial period for this copy of WebSphere MQ Advanced Message Security.
Explanation
This copy of WebSphere MQ Advanced Message Security is licensed for a limited period only.
Action
None.
amq9079
There are&1 days left in the beta test period for this copy of WebSphere MQ Advanced Message Security.
Explanation
This copy of WebSphere MQ Advanced Message Security is licensed for a limited period only.
Action
None.
amq9080
There is one day left in the Beta test period for this copy of WebSphere MQ Advanced Message Security.
Explanation
This copy of WebSphere MQ Advanced Message Security is licensed for a limited period only.
Action
None.
amq9081
This is the final day of the Beta test period for this copy of WebSphere MQ Advanced Message Security.
Explanation
This copy of WebSphere MQ Advanced Message Security is licensed for a limited period only.
Action
Install a Production license for this copy of WebSphere MQ Advanced Message Security.
amq9082
No policies found.
Explanation
There are no policies defined.
Action
None.