This application has ended. See above for any problems found.
Severity
0 : Informational
Explanation
If there are problems then resolve these and run this tool again.
AMQ3001E
No Certificate could be found for the Queue Manager <insert_3>
Severity
20 : Error
Explanation
Queue managers will use a certificate with the label set in the Queue Manager's CERTLABL attribute. There is no certificate with the label <insert_4> in the key repository being used by the queue manager The Key repository being used is located at <insert_5>.
Response
A valid certificate with the label <insert_4> needs to be added to the key repository.
AMQ3001E (IBM MQ Appliance)
No Certificate could be found for the Queue Manager <insert_3>
Severity
20 : Error
Explanation
Queue managers will use a certificate with the label set in the Queue Manager's CERTLABL attribute. There is no certificate with the label <insert_4> in the key repository being used by the queue manager
Response
A valid certificate with the label <insert_4> needs to be added to the key repository.
AMQ3002E
No personal certificate could be found for the client in the client's key repository.
Severity
20 : Error
Explanation
There is no certificate with the label <insert_3> in the key repository being used by the client. The key repository referenced is located at <insert_4>.
Response
A valid certificate with the label <insert_3> needs to be added to the key repository. The client repository does not need to contain a personal certificate if the server-connection channel on the queue manager that it is connecting to has SSLCAUTH (SSL client authentication) set to OPTIONAL the SSLPEER parameter is empty.
AMQ3003E
No key repository could be found for the queue manager <insert_3>
Severity
20 : Error
Explanation
Queue managers use the SSLKEYR attribute to identify the location of the SSL key repository to use. No key repository file could be found at the location specified in the queue manager's SSLKEYR attribute The key repository referenced is <insert_4>.
Response
Alter the queue manager's SSLKEYR attribute to point at the correct key repository or create a key repository at the specified location.
AMQ3004E
No key repository could be found for the client
Severity
20 : Error
Explanation
No key repository file could be found at the location provided for the client. The key repository referenced is <insert_3>.
Response
Alter the MQSSLKEYR environment variable or -clientkeyr option to point at the correct key repository or create a key repository at the specified location.
AMQ3005E
No stash file could be found for the key repository in use by <insert_3>
Severity
20 : Error
Explanation
Queue managers use an encoded stash file to determine the password to use to access the key repository. No stash file could be found at the location specified from the queue manager's SSLKEYR attribute. The stash file referenced is <insert_4>.
Response
Key repositories need to be created with the 'stash' option. Either recreate the key repository or use the key database tools to create the missing stash file.
AMQ3006E
No stash file could be found for the key repository in use by the client
Severity
20 : Error
Explanation
No stash file could be found at the location provided for the client. The stash file referenced is <insert_3>.
Response
Key repositories need to be created with the 'stash' option. Either recreate the key repository or use the key database tools to create the missing stash file.
AMQ3007E
The SSLKEYR attribute of the queue manager is blank.
Severity
20 : Error
Explanation
Queue managers use the SSLKEYR attribute to identify the location of the SSL key repository to use. It is a required attribute if SSL is to be used.
Response
Alter the queue manager's SSLKEYR attribute to point at the correct key repository.
AMQ3008E
No key repository could be found for the queue manager <insert_3>
Severity
20 : Error
Explanation
Queue managers use the SSLKEYR attribute to identify the location of the SSL key repository to use. The location is determined by adding the file extension .kdb to the value of the SSLKEYR attribute. No key repository file could be found at the location <insert_4>.kdb
Response
The SSLKEYR attribute of the queue manager has incorrectly included the .kdb file extension. Alter the queue manager attribute to remove this file extension.
AMQ3009E
No key repository could be found for the Client
Severity
20 : Error
Explanation
No key repository file could be found at the location provided for the client. This application looked for <insert_3>.kdb
Response
The MQSSLKEYR environment variable or -clientkeyr option has incorrectly included the .kdb file extension. Alter the attribute to remove this file extension.
AMQ3010E
Invalid access rights found for the key repository in use by queue manager <insert_3>
Severity
20 : Error
Explanation
The userid 'mqm' needs read-access to the queue managers key repository <insert_4>. This should be enabled for both the .kdb file itself, and every parent directory between the kdb and the root directory.
Response
Alter file access to the key repository so that mqm has read access. Ensure mqm has access to every parent directory above the key repository, or move the kdb to a location that mqm has access to.
AMQ3011E
Invalid access rights found for the stash file in use by queue manager <insert_3>
Severity
20 : Error
Explanation
The userid 'mqm' needs read-access to the queue managers stash file <insert_4>. This should be enabled for both the .sth file itself, and every parent directory between the stash file and the root directory.
Response
Alter file access to the stash file so that mqm has read access. Ensure mqm has access to every parent directory above the stash file, or move the stash file to a location that mqm has access to.
AMQ3012E
Invalid access rights found for the key repository in use by the client
Severity
20 : Error
Explanation
The userid 'mqm' needs read-access to the clients key repository <insert_4>. This should be enabled for both the .kdb file itself, and every parent directory between the kdb and the root directory.
Response
Alter file access to the key repository so that mqm has read access. Ensure mqm has access to every parent directory above the key repository, or move the kdb to a location that mqm has access to.
AMQ3013E
Invalid access rights found for the stash file in use by the Client
Severity
20 : Error
Explanation
The userid 'mqm' needs read-access to the clients stash file <insert_4>. This should be enabled for both the .sth file itself, and every parent directory between the stash file and the root directory.
Response
Alter file access to the stash file so that mqm has read access. Ensure mqm has access to every parent directory above the stash file, or move the stash file to a location that mqm has access to.
AMQ3014E
Invalid password found in the stash file for key repository <insert_3>
Severity
20 : Error
Explanation
IBM MQ uses an encoded stash file to determine the password to use to access the key repository. The password found in the stash file <insert_4> was incorrect.
Response
Alter the key repository password to match the value in the stash file or recreate the stash file.
AMQ3015E
Certificate has a 'valid-from' time in the future.
Severity
20 : Error
Explanation
The certificate with the label <insert_4> in <insert_3> cannot be used until the valid-from date.
Response
Create a new certificate with valid date attributes.
AMQ3015E (IBM MQ Appliance)
Certificate has a 'valid-from' time in the future.
Severity
20 : Error
Explanation
The certificate with the label <insert_4> cannot be used until the valid-from date.
Response
Create a new certificate with valid date attributes.
AMQ3016E
Certificate has expired.
Severity
20 : Error
Explanation
The certificate with the label <insert_4> in <insert_3> is no longer valid.
Response
Create a new certificate with valid date attributes.
AMQ3016E (IBM MQ Appliance)
Certificate has expired.
Severity
20 : Error
Explanation
The certificate with the label <insert_4> is no longer valid.
Response
Create a new certificate with valid date attributes.
AMQ3017E
<insert_3> certificate failed authentication with the <insert_4> key repository
Severity
20 : Error
Explanation
Authentication involves a chain of trusted certificates. The digital signature of the <insert_3>s certificate needs to be verified by the <insert_4>s key repository,with the public key from the certificate of the issuing Certification Authority (CA). If the <insert_3>s certificate is itself also a root CA (self-signed) then this certificate needs to be present in the <insert_4>s repository. If the <insert_3>s CA certificate is a root certificate, then this root certificate needs to be present in the <insert_4>s key repository. If the <insert_3>s CA certificate was issued by an intermediate CA, the intermediate CA certificate must itself be verified. This continues along a chain of CA certificates until a root certificate is reached. All certificates in the chain must be verified correctly. The <insert_4>s repository does not contain a valid chain leading to a root certificate.
Response
Verify the authentication chains for each certificate. Ensure that the <insert_3>s certificate or signer certificate has been added to the <insert_4>s Key repository. Alternatively, the client's key repository does not need to contain a personal certificate if the server-connection channel on the queue manager that it is connecting to has SSLCAUTH (SSL client authentication) set to OPTIONAL and no SSLPEER parameter set. The fact that one is present means that IBM MQ will use it. Therefore, an alternative approach may be to remove the personal certificate for the client from the client's key repository, and ensure that one or more SSL-enabled channels have SSLCAUTH (SSL client authentication) set to OPTIONAL and no SSLPEER value.
AMQ3018E
Client connection refused by server.
Severity
20 : Error
Explanation
This test tool attempts to validate the SSL certificates by using them to establish an SSL-protected connection between a client and server thread. This failed. The reason for the failure was that the client connection was refused by the server. This is unrelated to the SSL setup, and is most likely because a firewall running on this machine prevented the connection.
Response
Ensure that no firewall is preventing access to local ports and try again.
AMQ3019E
Unable to connect to queue manager <insert_3>.
Severity
20 : Error
Explanation
A connection to the queue manager is required in order to examine SSL configuration parameters. The MQCONN attempt failed with return code <insert_4>.
Response
Ensure that the queue manager name has been spelt correctly and that the queue manager is running.
AMQ3020E
Unable to open the queue manager <insert_3>.
Severity
20 : Error
Explanation
A connection to the queue manager is required in order to examine SSL configuration parameters. The MQOPEN attempt failed with return code <insert_4>.
Response
Ensure that the current user has permission to query the queue manager attributes.
AMQ3021E
Unable to open the queue <insert_4> on <insert_3>.
Severity
20 : Error
Explanation
A temporary dynamic queue is opened in order to collect responses to a command used to get channel definitions. This is required in order to examine SSL configuration parameters for channels on <insert_3>. The MQOPEN attempt failed with return code <insert_5>
Response
Ensure that the current user has permission to open a temporary dynamic queue.
AMQ3022E
Unable to inquire the queue manager <insert_3>
Severity
20 : Error
Explanation
A connection to the queue manager is required in order to examine SSL configuration parameters. The MQINQ attempt to examine a queue manager parameter (<insert_4>) failed with return code <insert_5>.
Response
Ensure that the current user has permission to query the queue manager attributes.
AMQ3023E
Unable to put to queue <insert_4> on <insert_3>.
Severity
20 : Error
Explanation
A message containing a PCF command is put on <insert_4> requesting channel definitions. This is required in order to examine SSL configuration parameters for channels on <insert_3>. The MQPUT attempt failed with return code <insert_5>
Response
Ensure that the specified queue exists, and that the current user has permission to open and put to it.
AMQ3024E
Unable to get from queue <insert_4> on <insert_3>.
Severity
20 : Error
Explanation
A message containing a PCF command is put on <insert_4> requesting channel definitions. This is required in order to examine SSL configuration parameters for channels on <insert_3>. This appeared to complete successfully, however the attempt to get the responses from the expected reply-to queue failed with return code <insert_5>.
Response
Ensure that the command server is running on <insert_3>.
AMQ3025W
Unable to close PCF reply queue
Severity
10 : Warning
Explanation
A message containing a PCF command is put to the command queue, with a request for channel definitions. This is required in order to examine SSL configuration parameters for channels. This appeared to complete successfully, however the attempt to close the reply queue (after examining the replies) failed with return code <insert_3>.
Response
No action required.
AMQ3026W
Unable to disconnect from <insert_3>.
Severity
10 : Warning
Explanation
A connection to the queue manager is required in order to examine SSL configuration parameters. The MQDISC used to disconnect failed with return code <insert_4>.
Response
No action required.
AMQ3027W
SSL Certificate Revocation List parameter found (SSLCRLNL = <insert_3>)
Severity
10 : Warning
Explanation
During an SSL 'handshake', the queue manager and client authenticate each other with digital certificates. Authentication can include a check that the certificate received can still be trusted. Certification Authorities can revoke personal certificates by publishing them in a Certificate Revocation List (CRL). This application currently does not have functionality to check CRLs.
Response
Verify the CRL parameters for <insert_4> manually.
AMQ3028E
Relative path given for client key repository.
Severity
20 : Error
Explanation
This application currently requires absolute paths for the client key repository file. The relative path <insert_3> was provided.
Response
Run this application again, giving the full path.
AMQ3029E
Value specified in Queue Manager CERTLABL attribute is not valid.
Severity
20 : Error
Explanation
IBM MQ Queue Managers will use the certificate that has been set in the Queue Manager's CERTLABL attribute. This value must be a valid value consisting of alpha-numeric characters. Additionally the CERTLABL can contain symbols and spaces, however the CERTLABL value can not be blank and should not start or end with space characters.
Response
The Queue Manager CERTLABL value was found to be <insert_3>. Change this to a valid value following the advice above.
AMQ3030E
Value specified in Client CERTLABL attribute is not valid.
Severity
20 : Error
Explanation
IBM MQ Clients will attempt to use the certificate that has been provided to them. This value must be a valid value consisting of alpha-numeric characters. Additionally the CERTLABL can contain symbols and spaces, however the CERTLABL value can not be blank and should not start or end with space characters. Finally the provided CERTLABL length can not be longer than 64 characters long.
Response
The Client CERTLABL value was found to be <insert_3>. Change this to a valid value following the advice above.
AMQ3031S
This program encountered a internal error and had to quit.
Severity
40 : Severe
Explanation
Check above for any additional information and try again. Additionally check the global error logs for any error messages and resolve any issues found.
Response
If this problem persists contact IBM Support for assistance.
AMQ3032E
There was a problem with the arguments supplied for the client checks.
Severity
20 : Error
Explanation
Both a -clientuser and -clientlabel value were supplied. This Program only allows one of the arguments to be provided.
Response
Run this application again only supplying one of the parameters.
AMQ3033E
There was a problem with the arguments supplied.
Severity
20 : Error
Explanation
The argument <insert_3> was not recognised. Please refer to the usage statement for available arguments.
Response
Run this application again only supplying valid parameters.
AMQ3034E
There was a problem with the arguments supplied.
Severity
20 : Error
Explanation
The required argument <insert_3> is missing.
Response
Run this application again supplying the missing parameter.
AMQ3035W
No Client user name or Client Certificate label provided.
Severity
10 : Warning
Explanation
This application will be unable to identify client's certificate and cannot test Queue Manager to Client connections. If you plan to connect this client to a channel with SSLCAUTH(REQUIRED) you will be UNABLE to connect.
Response
No action required.
AMQ3036W
The Channel <insert_3> is not SSL enabled but has a CERTLABL value of <insert_4>.
Severity
10 : Warning
Response
If the channel <insert_3> is supposed to be SSL enabled set a CipherSpec in the channel SSLCIPH attribute to enable SSL. If the channel is not supposed to be SSL enabled alter the Channel definition to remove the CERTLABL value.
AMQ3037E
No certificate could be found for the channel <insert_3>.
Severity
20 : Error
Explanation
This tool looked in the Queue Manager's key repository located at <insert_5> for a certificate with label <insert_4>, which is the certificate specified in the channel's CERTLABL attribute, but was unable to find one.
Response
A valid certificate with the label <insert_4> needs to be added to the key repository. Alternatively, alter the channel definition to remove the CERTLABL value.
AMQ3037E (IBM MQ Appliance)
No certificate could be found for the channel <insert_3>.
Severity
20 : Error
Explanation
This tool looked in the Queue Manager's key repository for a certificate with label <insert_4>, which is the certificate specified in the channel's CERTLABL attribute, but was unable to find one.
Response
A valid certificate with the label <insert_4> needs to be added to the key repository. Alternatively, alter the channel definition to remove the CERTLABL value.
AMQ3038E
Unable to find a channel called <insert_4> on Queue Manager <insert_3>.
Severity
20 : Error
Response
Check for the existence of the channel and create if necessary or correct the spelling in this applications argument. Alternatively do not provide the argument -clientchannel when running this application.
AMQ3039E
No personal certificate could be found for the client in the client's key repository and the channel requires a client certificate.
Severity
20 : Error
Explanation
There is no certificate with the label <insert_3> in the key repository being used by the client (<insert_4>) The channel <insert_5> has been configured to require a client certificate either by setting SSLCAUTH(REQUIRED) or by setting a value in SSLPEER.
Response
A valid certificate with the label <insert_3> needs to be added to the key repository. Alternatively, alter the channel <insert_5> definition so that SSLCAUTH is set to OPTIONAL and no SSLPEER value is set.
AMQ3040E
The user running this program does not have access rights to examine a directory
Severity
20 : Error
Explanation
The user running this program does not have access rights to examine the directory identified in <insert_3> and so cannot determine the containing file permissions.
Response
Please run this application as a user with access to the directory or change the directory permissions to allow access for the user running this application.
AMQ3041E
A filename is longer than this application can handle.
Severity
20 : Error
Explanation
The filename <insert_3> is too long for this application.
Response
Please shorten the filename and retry.
AMQ3042E
The user running this program does not have access rights to examine a file
Severity
20 : Error
Explanation
The user running this program does not have access rights to examine the file <insert_3> and so cannot determine the file permissions.
Response
Please run this application as a user with access to the file or change the file permissions to allow access for the user running this application.
AMQ3043E
An unknown error was encountered while trying to access a file.
Severity
20 : Error
Explanation
An unknown error was encountered while trying to access the file <insert_4>. This file is of type <insert_3>, the return code was <insert_1>.
Response
Please try again. If this problem persists contact IBM Support with details of this error. Internal Error - amqT_MQCERTCK_STAT_ERROR. Function Error - <insert_1>
AMQ3044W
Unable to verify if the mqm user can access a file.
Severity
10 : Warning
Explanation
Unable to check the whether the 'mqm' user has read access to file. <insert_3>. In order for MQ to perform TLS operations it must be able to access this file.
Response
Please confirm that the mqm user or group has access to this file manually.
AMQ3045E
Unable to retrieve a password.
Severity
20 : Error
Explanation
Unable to retrieve the password from <insert_3>.
Response
Please ensure that this application will be able to obtain the password for the repository and try again.
AMQ3046E
<insert_3>s certificate failed validation.
Severity
20 : Error
Response
Please verify that the certificate is a valid TLS certificate and try again. If this problem persists contact IBM Support for assistance.
AMQ3047E
Invalid access rights found for the parent directory of the key repository in use by queue manager <insert_3>.
Severity
20 : Error
Response
Alter directory access to the parent directory so that mqm has read access. Or move the kdb and stash file to a location that mqm has access to.
AMQ3048E
Invalid access rights found for the parent directory of the key repository in use by the client.
Severity
20 : Error
Response
Alter directory access to the parent directory so that mqm has read access. Or move the kdb and stash file to a location that mqm has access to.
AMQ3049E
The queue manager is not registered as an application with Digital Certificate Manager (DCM).
Severity
20 : Error
Explanation
Queue managers will use the certificate assigned via Digital Certificate Manager to this queue manager.
Response
Issue CHGMQM to set the SSLYKEYR value to blanks and then reissue CHGMQM to set SSLKEYR(*SYSTEM) to register the queue manager again with Digital Certificate Manager.
AMQ3050E
The port number <insert_3> was invalid.
Severity
20 : Error
Explanation
The port number supplied must be an integer value between 1 and 65535.
Response
Please check the value you supplied and try again.
AMQ3051E
A certificate failed authentication.
Severity
20 : Error
Explanation
Authentication involves a chain of trusted certificates. The digital signature of the client or server's certificate needs to be verified by the other's key repository, with the public key from the certificate of the issuing Certification Authority (CA). If the certificate is itself also a root CA (self-signed) then this certificate needs to be present in the key repository. If the CA certificate is a root certificate, then this root certificate needs to be present in the key repository. If the CA certificate was issued by an intermediate CA, the intermediate CA certificate must itself be verified. This continues along a chain of CA certificates until a root certificate is reached. All certificates in the chain must be verified correctly. The client or server's key repository does not contain a valid chain leading to a root certificate.
Response
Verify the authentication chains for each certificate. Ensure that the necessary certificate(s) or signer certificate(s) have been added to the Key repositories. Alternatively, the client's key repository does not need to contain a personal certificate if the server-connection channel on the queue manager that it is connecting to has SSLCAUTH (SSL client authentication) set to OPTIONAL and no SSLPEER parameter set. The fact that one is present means that IBM MQ will use it. Therefore, an alternative approach may be to remove the personal certificate for the client from the client's key repository, and ensure that one or more SSL-enabled channels have SSLCAUTH (SSL client authentication) set to OPTIONAL and no SSLPEER value.
AMQ3052E
A certificate label has been specified on channel <insert_3> while system store is in use.
Severity
20 : Error
Explanation
Certificate labels can not be used when using System Store to manage your SSL certificates.
Response
Remove the certificate label definition from the channel or if you wish to use certificate labels configure your Queue Manager to use key repositories instead of System Store.
AMQ3053I
The usage of <insert_3> is incorrect.
Severity
0 : Informational
Explanation
Usage: <insert_3> QMgrName [-clientkeyr client_key_repository]
[-clientchannel channel_name]
[-clientuser client_username | -clientlabel client_certlabel]
[-clientport portNumber]
-clientkeyr Location of the Client's Key Repository.
-clientchannel Name of the channel the client application will connect to.
-clientuser User that will be running the client application. Cannot be used with -clientlabel.
-clientlabel Label of the Client's Certificate. Cannot be used with -clientuser.
-clientport Port for <insert_3> to use during client connection tests. Must be available. Default is <insert_1>.
AMQ3054I
The usage of <insert_3> is incorrect.
Severity
0 : Informational
Explanation
Usage: <insert_3> QMgrName
AMQ3055I
Usage: <insert_3> [-sf <path>] [-sp 1|2]
-sf File containing key used for protection of credentials
-sp Protection mode. Defaults to 2
Enter password to encrypt when prompted. Password must not be zero length.
Severity
0 : Informational
AMQ3056I
Usage: runamscred [-f <path>] [-o <path>] [-sf <path>] [-sp 1|2]
-f Input configuration file with plaintext credentials
-o Output configuration file. If not set, input file is overwritten
-sf File containing key used for protection of credentials
-sp Protection mode. Defaults to 2
Severity
0 : Informational
AMQ3057I
Usage: runqmcred [-sf <path>]
-sf File containing key used for protection of credentials
Enter the password to encrypt when prompted. The password must be 1-1024 characters long.
Severity
0 : Informational
AMQ3069E
An internal error occurred while running command mqperfck.
Severity
20 : Error
Explanation
Check previous messages and global error logs for errors. Resolve any issues found and try again.
-h|-? Show this usage text and exit
-m Queue manager name
-q Name of queue(s) to analyze (repeat up to <insert_1> times)
-s Name of sender channel(s) to analyze (repeat up to <insert_2> times)
-n Number of sampling iterations to perform (defaults to 6)
-u User name for connection (the tool will prompt for password)
-d Name of directory where output will be written
-N Suppress translation of HTML report
-h|-? Show this usage text and exit
-m Queue manager name
-q Name of queue(s) to analyze (repeat up to <insert_1> times)
-s Name of sender channel(s) to analyze (repeat up to <insert_2> times)
-n Number of sampling iterations to perform (defaults to 6)
-u User name for connection (the tool will prompt for password)
Severity
0 : Informational
AMQ3072E
Could not validate queue <insert_3>. Ensure that the queue exists, is a local queue, and that you have authority to open the queue for inquire.
Severity
20 : Error
AMQ3073E
Channel <insert_3> not found. Ensure a channel exists with the required channel type.
Severity
20 : Error
AMQ3074I
Connected to queue manager <insert_3>.
Severity
0 : Informational
AMQ3075W
<insert_3> failed on object <insert_4> type <insert_5> with CompCode=<insert_1> Reason=<insert_2>
Severity
10 : Warning
Explanation
The MQI operation failed.
Response
Use the Completion and Reason codes shown in the message to determine the cause of the failure, then re-try the command.
AMQ3076E
Failed to inquire queue manager.
Severity
20 : Error
AMQ3077I
Waiting for messages.
Severity
0 : Informational
AMQ3078W
Command terminating because because queue manager is quiescing.
Severity
10 : Warning
AMQ3079W
Attempt to inquire channel <insert_3> failed with CompCode=<insert_1> Reason=<insert_2>
Severity
10 : Warning
Explanation
Error in response to PCF MQCMD_INQUIRE_CHANNEL command.
AMQ3080E
Monitoring is not enabled for channel <insert_3>.
Severity
20 : Error
Explanation
The channel's MONCHL attribute value must ether be set to LOW, MEDIUM, HIGH, or if the channel's MONCHL attribute is set to QMGR, then the queue manager's MONCHL attribute must be set to LOW, MEDIUM, HIGH.
Response
Set the MONCHL value and try again.
AMQ3081I
Processing iteration <insert_1> of <insert_2>.
Severity
0 : Informational
AMQ3082E
Number of iterations must be greater than zero.
Severity
20 : Error
AMQ3083I
Enter password:
Severity
0 : Informational
AMQ3084I
Writing report summary.
Severity
0 : Informational
AMQ3085I
Creating file: <insert_3>
Severity
0 : Informational
AMQ3086E
Failed to open <insert_3>. error=<insert_1> (<insert_4>)
Severity
20 : Error
AMQ3201E
An unexpected error has been detected in the Native HA configuration data in qm.ini.
Severity
20 : Error
Explanation
Errors in the Native HA configuration data would normally be associated with a more specific error message and user action.
Response
Review the Native HA configuration and resolve any issues.
AMQ3202E
A duplicate <insert_3> stanza with key attribute <insert_4>=<insert_5> was found in the Native HA configuration data in qm.ini.
Severity
20 : Error
Explanation
Native HA configuration does not permit a <insert_3> stanza to be duplicated with the same <insert_4> key attribute, but the configuration data includes multiple stanzas with the same attribute key value of <insert_5>.
Response
Identify the extraneous stanza in the Native HA configuration and correct so that only a single stanza with the key <insert_4>=<insert_5> remains.
AMQ3203E
More than one value for the attribute <insert_4> in the <insert_3> stanza specified in the Native HA data in qm.ini.
Severity
20 : Error
Explanation
Native HA configuration only supports a single <insert_4> attribute in the <insert_3> stanza, but the configuration data includes multiple <insert_4> attributes.
Response
Identify the extraneous attributes in the Native HA configuration and remove, so that only a single attribute remains.
AMQ3204E
The value <insert_5> specified for attribute <insert_4> in the <insert_3> stanza is not valid.
Severity
20 : Error
Explanation
The value specified is outside the permissible range for this attribute.
Response
Correct the value of the <insert_4> attribute to contain a permissible value.
AMQ3205E
A required keyed stanza of type <insert_3> with attribute <insert_4> and value <insert_5> was not found in the Native HA configuration data in qm.ini.
Severity
20 : Error
Explanation
Some aspects of the configuration imply that the queue manager is configured to use Native HA, however a required stanza of type <insert_3> is missing from the configuration. The <insert_3> stanza is keyed and may be repeated with unique <insert_4> key values. This error is reported when a stanza with a specific key value of <insert_5> was found to be missing.
Response
Correct the Native HA configuration to provide the missing <insert_3> stanza configuration.
AMQ3206E
Attribute <insert_4> was not found in the <insert_3> stanza.
Severity
20 : Error
Explanation
Some aspects of the configuration imply that the queue manager is configured to use Native HA, however a required <insert_3> stanza attribute of <insert_4> was not found.
Response
Correct the Native HA configuration to provide the required <insert_4> attribute in the <insert_3> stanza.
AMQ3208E
Native HA network connection to <insert_3> could not be established.
Severity
20 : Error
Explanation
An attempt to establish a network connection to a remote Native HA instance failed. The ReplicationAddress of <insert_4> in the NativeHAInstance stanza of qm.ini may be incorrect, or the remote Native HA instance may not have been started. The error code associated with the connection failure is <insert_5>.
Response
Check the ReplicationAddress is correct and ensure that the remote Native HA instance is started.
AMQ3209E
Native HA connection rejected due to configuration mismatch of <insert_3>.
Severity
20 : Error
Explanation
The Native HA replication connection received from instance <insert_4> failed to match the local instance configuration of <insert_5>.
Response
Correct the Native HA configuration to resolve the discrepancy.
AMQ3210E
Native HA connection failed to negotiate with instance <insert_4>.
Severity
20 : Error
Explanation
The network connection to instance <insert_4> failed, the local instance configuration of <insert_5> did not match the remote instance configuration of <insert_3>.
Response
Correct the Native HA configuration to resolve the discrepancy.
AMQ3211I
Native HA outbound connection established to <insert_3>.
Severity
0 : Informational
Explanation
The outbound network connection to instance <insert_3> was successfully established. The connection to <insert_4> is not using any transport level security. This instance must also accept an inbound connection from instance <insert_3>. Successful acceptance of an inbound connection is identified by an AMQ3213 message. The current status of replica connections can be queried by issuing 'dspmq -o nativeha -x'.
Response
None.
AMQ3212I
Native HA outbound secure connection established to <insert_3>.
Severity
0 : Informational
Explanation
The outbound secure network connection to instance <insert_3> was successfully established. The connection to <insert_4> is using the <insert_5> CipherSpec. This instance must also accept an inbound secure connection from instance <insert_3>. Successful acceptance of an inbound secure connection is identified by an AMQ3214 message. The current status of replica connections can be queried by issuing 'dspmq -o nativeha -x'.
Response
None.
AMQ3213I
Native HA inbound connection accepted from <insert_3>.
Severity
0 : Informational
Explanation
An inbound network connection from instance <insert_3> was successfully accepted. The connection from <insert_4> is not using any transport level security. This instance must also make a successful outbound connection to instance <insert_3>. A successful outbound connection is identified by a AMQ3211 message. The current status of replica connections can be queried by issuing 'dspmq -o nativeha -x'.
Response
None.
AMQ3214I
Native HA inbound secure connection accepted from <insert_3>.
Severity
0 : Informational
Explanation
An inbound secure network connection from instance <insert_3> was successfully accepted. The connection from <insert_4> is using the <insert_5> CipherSpec. This instance must also make a successful outbound secure connection to instance <insert_3>. A successful outbound secure connection is identified by a AMQ3212 message. The current status of replica connections can be queried by issuing 'dspmq -o nativeha -x'.
Response
None.
AMQ3215I
The local Native HA instance <insert_3> is now the active instance of queue manager <insert_4>.
Severity
0 : Informational
Explanation
The native HA instance named <insert_3> running locally is now the active instance of queue manager <insert_4>.
Response
None.
AMQ3216E
Native HA instance <insert_3> cannot bind to TCP port <insert_1>.
Severity
30 : Error
Explanation
Native HA instance <insert_3> attempted to bind to replication port <insert_1>, but was unsuccessful. Typically a bind failure is due to another program using this TCP port. Another MQ Native HA queue manager could be configured to use the same port for replication traffic. The queue manager cannot start until the problem is resolved and will now end.
Response
Use networking tools such as netstat (for example on Linux "netstat -tlnp") to identify the program that is already bound to port <insert_1> and either end the program or change the port used for replication in qm.ini for this queue manager instance.
AMQ3217E
Active MQ Native HA instance <insert_3> is not connected to enough replica instances for queue manager <insert_4>.
Severity
30 : Error
Explanation
The active MQ Native HA instance <insert_3> was unable to connect to enough replica instances for queue manager <insert_4> to continue to function as the active instance. <insert_1> replica instances are currently connected, the minimum is <insert_2>.
The queue manager will now end.
Response
Use error logs and other diagnostic information to determine why this instance is unable to connect to other instances.
AMQ3218E
Native HA queue manager <insert_3> does not support redefining system objects.
Severity
30 : Error
Explanation
Queue manager <insert_3> is a Native HA instance and does not support redefining system objects using strmqm -c.
Response
Use an alternative approach to redefine the system objects, for example using runmqsc. If it is not possible to use alternate tooling, consider removing the queue manager from the Native HA configuration, redefine the system objects using strmqm -c and then place the queue manager back under Native HA control.
AMQ3219E
Less than <insert_1> Native HA instances have been configured.
Severity
30 : Error
Explanation
The minimum number of Native HA instances that must be configured is <insert_1>, only <insert_2> instance(s) were found.
Response
Increase the number of <insert_3> stanzas to configure a minimum of <insert_1> Native HA instances.
AMQ3221E
MQ Native HA instance <insert_3> has received data from instance <insert_5> indicating that it has taken over as the active instance.
Severity
30 : Error
Explanation
MQ Native HA instance <insert_3> was the active instance for queue manager <insert_4> but received data from instance <insert_5> which indicates that it has taken over as the active instance.
Instance <insert_3> will now end.
Response
This situation might indicate that there has been a network issue between some of the instances. Use error logs and other diagnostic information to determine why instance <insert_5> took over as the active instance.
AMQ3222E
Native HA network connection from <insert_3> ended unexpectedly.
Severity
20 : Error
Explanation
The Native HA network connection that instance <insert_3> established to the local instance of queue manager <insert_4> has ended unexpectedly. The error code associated with the failure is <insert_5>.
Response
Check that remote instance <insert_3> did not terminate unexpectedly. Restart the remote instance if necessary.
AMQ3223E
Native HA network connection to <insert_3> ended unexpectedly.
Severity
20 : Error
Explanation
The Native HA network connection that the local instance of queue manager <insert_4> established to remote instance <insert_3> has ended unexpectedly. The error code associated with the failure is <insert_5>.
Response
Check that remote instance <insert_3> did not terminate unexpectedly. Restart the remote instance if necessary.
AMQ3224I
Native HA instance <insert_3> of queue manager <insert_4> is ending.
Severity
0 : Informational
Explanation
The remote Native HA instance is ending normally. Network connections between the local instance and <insert_3> are ending.
Response
None.
AMQ3225E
More than <insert_1> Native HA instances have been configured.
Severity
20 : Error
Explanation
The maximum number of Native HA instances that can be configured is <insert_1> and at least <insert_2> instances were found.
Response
Reduce the number of <insert_3> stanzas to configure a maximum of <insert_1> Native HA instances.
AMQ3227I
The remote Native HA instance <insert_3> is the active instance of queue manager <insert_4>.
Severity
0 : Informational
Explanation
The Native HA instance named <insert_3> running remotely has been identified as the active instance of queue manager <insert_4>.
Response
None.
AMQ3228E
Native HA cannot initialize secure communications resources.
Severity
20 : Error
Explanation
The local Native HA instance failed to initialize secure communications resources. The queue manager cannot continue startup until the configuration error is corrected.
Response
Check that the keystore specified in the 'NativeHALocalInstance' stanza of qm.ini is accessible and that the correct keystore password has been set in the stash file. Check that a correctly labelled and valid certificate are held in the keystore.
AMQ3229E
Native HA requires <insert_3> stanza configuration <insert_4>=<insert_5>.
Severity
20 : Error
Explanation
The local Native HA instance failed to initialize as the required <insert_3> stanza attribute <insert_4> does not have the required value of <insert_5>.
Response
Correct the queue manager ini configuration of the <insert_3> stanza and restart the queue manager.
AMQ3230E
Native HA network connection attempt from network address <insert_3> failed.
Severity
20 : Error
Explanation
The Native HA network connection attempt from network address <insert_3> to the local instance of queue manager <insert_4> failed. The error code associated with the failure is <insert_5>.
Response
Check that the connection attempt from <insert_3> is being initiated from another Native HA instance and ensure that it is configured to connect to this instance.
AMQ3231E
The CipherSpec negotiated during a handshake with <insert_3> does not match the CipherSpec required by the local Native HA instance.
Severity
30 : Error
Explanation
There is a mismatch between the CipherSpecs configured on the local and remote Native HA instances. The Native HA replication connection will not start until an acceptable CipherSpec is negotiated. The CipherSpec required by the local Native HA instance is <insert_4>. The CipherSpec negotiated during the handshake is <insert_5>.
Response
Ensure the CipherSpec configuration in the NativeHALocalInstance stanza of qm.ini on each Native HA queue manager instance all state identical CipherSpecs. Correct any differences and restart each Native HA queue manager instance.
AMQ3232E
Certificate rejected by Native HA.
Severity
30 : Error
Explanation
A certificate encountered during handshaking was rejected 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
(f) The digital signature is not compliant with NSA Suite B restrictions (if enabled)
The remote host is <insert_5>. The Native HA replication connection did not start.
The details of the certificate which could not be validated are <insert_4>.
The certificate validation error was <insert_2>.
Response
Correct the error with the certificate validation and restart the Native HA queue manager instance.
This error might indicate that the remote Native HA instance is configured to use the wrong certificate. Check both the local and remote NativeHALocalInstance stanza configuration in qm.ini to identify the certificate keystores and labels that are currently in use.
AMQ3233E
Native HA connection rejected from unknown instance <insert_4>.
Severity
30 : Error
Explanation
A Native HA connection received from instance <insert_4> was rejected because the instance name was not recognised. The Native HA instance names that are considered valid are configured in repeating NativeHAInstance stanzas in qm.ini.
Response
This error indicates a configuration mismatch between the instance name specified in the remote NativeHALocalInstance stanza and the local NativeHAInstance stanzas. Correct the configuration mismatch and restart each queue manager instance.
AMQ3234E
A duplicate Native HA connection was received from instance <insert_4>.
Severity
30 : Error
Explanation
A Native HA connection received from instance <insert_4> has been rejected because there is already a connection from this instance.
Response
This error could be an indication that an unexpected network error has occurred on the existing Native HA connection. The existing network connection between remote instance <insert_4> and the local instance <insert_3> is now considered by Native HA to be unreliable and the connection will be restarted.
AMQ3235I
Native HA instance <insert_3> is not connected to enough other instances to start the process of selecting the active instance.
Severity
0 : Informational
Explanation
To initiate the process of selecting the active instance, <insert_3> must be connected to a minimum of another <insert_2> instance(s) for queue manager <insert_4>. Currently <insert_3> has a membership state of <insert_5> and is connected to <insert_1> instance(s).
Response
Ensure that other instances of the queue manager are correctly configured and started.
AMQ3236E
The outbound network connection closed unexpectedly during security negotiation with instance <insert_3>.
Severity
30 : Error
Explanation
The outbound network connection closed unexpectedly whilst negotiating transport level security parameters with its peer. The connection was established to instance <insert_3> using a network address of <insert_4> and a CipherSpec of <insert_5>, however the network connection was closed remotely before any log replication parameters could be negotiated.
Response
Check the error logs of queue manager instance <insert_3> for any errors relating to negotiation of a secure connection, such as incompatible protocols, CipherSpecs or certificates. Ensure the CipherSpec configuration in the NativeHALocalInstance stanza of qm.ini on each Native HA queue manager instance all state identical CipherSpecs. Ensure each queue manager instance has a suitable certificate for the CipherSpec (RSA or ECDSA). Correct any configuration differences and restart each Native HA queue manager instance.
AMQ3237I
Native HA instance <insert_3> is starting to rebase from extent <insert_5> using log data from the active instance.
Severity
0 : Informational
Explanation
Native HA instance <insert_3> and the active instance <insert_4> have no overlap of log data and so a log rebase is required. Log records starting from extent <insert_5> will be replicated to Native HA instance <insert_3> until a sufficient amount of data is available to rebuild the queue manager. Currently <insert_1> KB of log data must be replicated, however this could increase as more log data is written by the active instance.
Response
None.
AMQ3238I
Native HA instance <insert_3> completed a log rebase.
Severity
0 : Informational
Explanation
Native HA instance <insert_3> has replicated the log records required to rebuild the queue manager. The queue manager has been rebuilt and is running as a replica instance.
Response
None.
AMQ3239E
MQ Native HA instance <insert_3> has received a request from instance <insert_5> to select a new active instance.
Severity
30 : Error
Explanation
MQ Native HA instance <insert_3> is the active instance for queue manager <insert_4> but instance <insert_5> wants to select a new active instance.
Instance <insert_3> will now end.
Response
This situation might indicate that there has been a network issue between some of the instances. It can also occur if the active instance (<insert_3>) has not confirmed its active status to <insert_5> before <insert_5> started the process of selecting a new active instance. Use error logs and other diagnostic information to determine why instance <insert_5> has made the request.
AMQ3240I
Native HA instance <insert_3> did not complete a log rebase (reason: <insert_1>).
Severity
0 : Informational
Explanation
Native HA instance <insert_3> started a rebase using log data from the active instance but the operation could not complete for reason <insert_1>. Possible reasons include:
1) The log data required by the replica was not replicated before the data became superfluous to the active instance, and the log extents were reused.
2) A communications error between the active instance and the replica occurred during the rebase, causing the operation to be aborted.
3) The active instance has changed or reconnected.
4) The replica instance ended the rebase because it was not able to determine a valid log location for the data supplied.
5) The replica instance stopped the rebase early, for example, because the instance was ending.
6) An unexpected error occurred on the replica during the rebase, causing the operation to be aborted. Check this log for any previous related messages.
7) The replica instance ended during the rebase.
8) The replica instance has insufficient disk space.
The log rebase will restart when a suitable log extent is identified, a connection is established and sufficient disk space is available.
Response
None.
AMQ3241E
MQ Native HA instance <insert_3> has discovered that another instance has taken over as the active instance.
Severity
30 : Error
Explanation
MQ Native HA instance <insert_3> was the active instance for queue manager <insert_4> but received data indicating that another instance has taken over as the active instance.
Instance <insert_3> will now end.
Response
This situation might indicate that there has been a network issue between some of the instances. Use error logs and other diagnostic information to determine why another instance took over as the active instance.
AMQ3242E
MQ Native HA instance <insert_3> received no response from Native HA instance <insert_4>.
Severity
30 : Error
Explanation
MQ Native HA instance <insert_4> failed to respond to a communications request within <insert_1> milliseconds, so the existing connection is not viable. The network connection is ending and the connection will be retried.
Response
This situation might indicate that there has been a network issue between the two instances or that an error has occurred on instance <insert_4> that has caused it to become unresponsive. Data was last sent to instance <insert_4> at <insert_5>.
AMQ3243E
A communications sequence error has been detected between MQ Native HA instances <insert_3> and <insert_4>.
Severity
30 : Error
Explanation
A sequencing error has been detected on the MQ Native HA communications link between active instance <insert_3> and replica instance <insert_4>. This type of sequencing error could occur if the two instances are connected via an intermediate network proxy, router or firewall that is failing to pass through all network traffic.
Response
MQ Native HA will perform a log consistency check and resend any log data needed to make the replica consistent with the active. Check the network route between the two MQ Native HA instances, including router and firewall logs to identify the cause of this error and correct any configuration issues that are found.
AMQ3244E
The MQ Native HA connection from <insert_3> timed out with TCP/IP error <insert_1>.
Severity
30 : Error
Explanation
The Native HA network connection that instance <insert_3> established to the local instance of queue manager <insert_4> has ended with TCP/IP error <insert_1> indicating that data sent on the connection had not been acknowledged within the configured timeout period.
Response
Check for TCP/IP communications problems between the two Native HA instances.
AMQ3245E
The MQ Native HA connection to <insert_3> timed out with TCP/IP error <insert_1>.
Severity
30 : Error
Explanation
The Native HA connection that the local instance of <insert_4> established to remote instance <insert_3> has ended with TCP/IP error <insert_1> indicating that data sent on this connection had not been acknowledged within the configured timeout period.
Response
Check for TCP/IP communications problems between the two Native HA instances.
AMQ3246E
The MQ Native HA self connection check for instance <insert_3> failed.
Severity
30 : Error
Explanation
As part of initialization each Native HA instance will attempt to create a connection to itself using the configuration provided to confirm that the configuration provides a route to this instance.
This check has failed with error code <insert_1>, indicating that the configuration is not correct and either it was not possible to connect to <insert_3> or the instance to which the connection was made is not instance <insert_3> of queue manager <insert_4>.
Response
Check the configuration being used is correct, in particular, ensure that the ReplicationAddress value in the NativeHA stanza for instance <insert_3> provides a correct address.
AMQ3247W
Native HA active instance <insert_5> has not sent anything for <insert_2> milliseconds and is assumed to have ended.
Severity
10 : Warning
Explanation
The active Native HA instance must communicate regularly to confirm it is still running. Local instance <insert_3> for queue manager <insert_4> has not received anything from <insert_5> for <insert_2> milliseconds, and so <insert_5> is assumed to have ended.
The local instance will attempt to start the process of selecting a new active instance.
Response
This situation can arise if the active instance has ended, there has been a problem on the active instance, or if communication between the active instance and the local instance has failed.
Check the error logs to determine what has happened.
AMQ3248I
Native HA instance <insert_3> is prepared to receive rebase log data from the active instance.
Severity
0 : Informational
Explanation
Native HA instance <insert_3> is now prepared to receive the log data sufficient for rebuilding the queue manager. The active instance will now send log data to this replica instance.
Response
None.
AMQ3249I
Native HA instance <insert_3> has sufficient data to rebuild the queue manager.
Severity
0 : Informational
Explanation
Native HA instance <insert_3> has received enough log data from the active instance so that it can rebuild all queue manager objects. This replica instance will now start the rebuilding process.
Response
None.
AMQ3250I
Native HA instance <insert_3> has rebuilt the queue manager.
Severity
0 : Informational
Explanation
Native HA instance <insert_3> has rebuilt all the queue manager objects from the replicated log data sent by the active instance. This replica instance is now ready to continue normal log replication.
Response
None.
AMQ3269E
Native HA instance <insert_3> has insufficient disk space for a log rebase.
Severity
20 : Error
Explanation
Native HA instance <insert_3> and the active instance <insert_4> have no overlap of log data and so a log rebase is required. Currently <insert_1> KB of log data must be replicated, however this could increase as more log data is written by the active instance. Only <insert_2> KB is available on the filesystem containing <insert_5> and it is anticipated that the available disk space is insufficient to contain the data.
Response
More disk space must be made available to the instance since replication cannot continue until a log rebase can be completed. The active instance will periodically attempt to retry the log rebase.
AMQ3303W
There is a mismatch between the MQ versions being used by two Native HA instances.
Severity
10 : Warning
Explanation
The active Native HA instance is running MQ version <insert_5> but instance <insert_3> is running MQ version <insert_4>. The data being sent by the active instance might not be compatible with the data expected by instance <insert_3>.
Native HA instance <insert_3> must be updated to MQ version <insert_5> before it can accept the data being sent by the active instance.
Response
This situation might be temporary, caused when the version of MQ is being updated and the update of one instance has not yet completed.
If this message is seen repeatedly, ensure that all of the instances of the queue manager are configured to use the same version of MQ.
AMQ3485E
The command failed because the DR Appliance names are not unique.
Severity
20 : Error
Explanation
This error occurs when two of the DR Appliance names passed to the crtdrprimary/crtdrsecondary command are the same.
Response
Ensure that the Appliance names provided to the DR command are not the same.
AMQ3486E
The command failed because the DR Replication IP addresses are not unique.
Severity
20 : Error
Explanation
This error occurs when two of the DR Replication IP addresses passed to the crtdrprimary/crtdrsecondary command are the same.
Response
Ensure that the Replication IP addresses provided to the DR command are not the same.
AMQ3487I
Abort detected. Please issue the command <insert_3> to clean up any leftover configuration from this command.
Severity
0 : Informational
Explanation
This message is issued when an MQ Appliance command has been aborted that could leave some leftover configuration on the Appliance.
Response
The user should issue the command <insert_3> if they wish to clean up any configuration leftover by the command they aborted.
AMQ3488E
The network address of the DR interface on the remote appliance could not be determined.
Severity
20 : Error
Explanation
This message is issued when IBM MQ cannot get the remote DR network address.
Response
Ensure that the DR network interface and address on the remote appliance are configured correctly and enabled before reissuing the command.
AMQ3489W
HA status for queue manager <insert_3> is 'Paused'
Severity
10 : Warning
Explanation
This message indicates the specified queue manager has the HA secondary role on both appliances. Synchronization will start when one appliance is promoted to the HA primary role.
AMQ3490W
DR status for queue manager <insert_3> is 'Paused'
Severity
10 : Warning
Explanation
This message indicates the specified queue manager has the DR secondary role on both appliances.
Response
Promote one appliance to the DR primary role to start synchronization.
AMQ3491E
Could not find local DR address <insert_3> in validation list provided to crtdrsecondary.
Severity
20 : Error
Explanation
The address/es passed to crtdrsecondary through "-v" did not match the local DR replication address
Response
The user should check that the crtdrprimary command was issued with the correct remote DR address/es or that the DR replicated interface is configured with the correct IP address. If not, then the user should delete their DR setup on the DR primary using dltdrprimary and reissue crtdrprimary with the correct remote DR address/es.
AMQ3492E
Could not find remote DR address <insert_3> in validation list provided to crtdrsecondary.
Severity
20 : Error
Explanation
The address/es passed to crtdrsecondary through "-v" did not match the remote DR replication address
Response
The user should check that the crtdrprimary command was issued with the correct remote DR address/es or that the remote HA's DR replicated interface is configured with the correct IP address. If not, then the user should delete their DR setup on the DR primary using dltdrprimary and reissue crtdrprimary with the correct remote DR address/es.
AMQ3493I
Execute the following command on appliance <insert_3> or <insert_4>: <insert_5>
Severity
0 : Informational
Explanation
This message is issued by dspdrsecondary. It includes the crtdrsecondary command that should be executed on one of the remote DR appliances.
Response
The user should execute the crtdrsecondary command on one of the remote appliances.
AMQ3494I
Queue manager <insert_3> is prepared for Disaster Recovery replication.
Now execute the following command on appliance <insert_4> or <insert_5>:
Severity
0 : Informational
Explanation
This message is issued when the crtdrprimary command succeeds. It is followed by the crtdrsecondary command that should be executed on one of the remote appliances.
Response
The user should execute the follow on crtdrsecondary command on one of the remote appliances.
AMQ3495I
The HA queue manager (<insert_3>) will be restarted.
Severity
0 : Informational
Explanation
A configuration changing command has been issued which will restart the HA queue manager (<insert_3>) to complete.
Response
None.
AMQ3496E
IBM MQ queue manager <insert_3> cannot be restored by this installation. It has previously been started by a newer release of IBM MQ. The queue manager requires a minimum version of <insert_4>.
Severity
20 : Error
Explanation
The queue manager has previously been started by a newer release of IBM MQ at version <insert_5>. This installation is not compatible with the newer release's data. Migration between these releases is not possible.
Response
The queue manager can be restored by installing a release of IBM MQ at version <insert_4> or higher.
AMQ3497I
Key <insert_3> was successfully updated for the global stanza <insert_4>.
Severity
0 : Informational
Explanation
IBM MQ successfully updated a key in the mqs.ini file.
Response
None.
AMQ3498E
The MQ <insert_3> file system is not available.
Severity
20 : Error
Explanation
The operation could not be completed because the MQ <insert_3> file system is not available.
Response
Investigate why the file system is not available.
AMQ3499E
The HA replication IP <insert_3> is invalid.
Severity
20 : Error
Explanation
The configured HA replication IP <insert_3> does not match any local network interface.
Response
Use sethalink to correct the replication IP.
AMQ3500E
The remote HA replication IP <insert_3> is invalid.
Severity
20 : Error
Explanation
The configured HA replication IP <insert_3> on the remote appliance does not match any network interface.
Response
Use sethalink on the remote Appliance to correct the replication IP.
AMQ3501I
The file system passphrase has been stored, but it cannot be validated for a queue manager that has the HA or DR secondary role. The stored passphrase will be validated when a failover occurs and the queue manager has the primary role on this appliance.
Severity
0 : Informational
AMQ3502I
It is recommended that you save a copy of the file system passphrase in a secure location. You will require the passphrase to access the file system if the RAID storage is transferred to a replacement appliance or the stored passphrase on this appliance is cleared.
Severity
0 : Informational
AMQ3503I
Clearing the stored passphrase for an encrypted file system prevents access to the file system when it next needs to be mounted. If the file system is currently available then it will remain available until it is unmounted. The file system will then be unavailable on this appliance until its passphrase has been stored again by using the setfspass command.
Access to a queue manager file system on a remote appliance in a high availability or a disaster recovery configuration is unaffected.
If the passphrase for a required system file system is unavailable at boot then the appliance will enter failsafe mode and all queue managers will remain unavailable until the passphrase is stored and the appliance can resume startup.
Are you sure you wish to continue (yes/no)?
Severity
0 : Informational
Response
None.
AMQ3504E
The specified passphrase file is not valid or does not exist.
Severity
20 : Error
Explanation
The file that contains the passphrase for the file system is not valid or does not exist.
Response
Correct the passphrase file argument, then reissue the command.
AMQ3505S
The file system is too small.
Severity
40 : Severe
Explanation
The operation cannot be completed because the file system is too small.
Response
Increase the size of the file system or reduce the amount of data it needs to store.
AMQ3506S
The logical volume for the MQ <insert_3> file system is missing.
Severity
40 : Severe
Explanation
The logical volume for the MQ <insert_3> file system is missing.
Response
Contact IBM Support for assistance.
AMQ3507I
Recovery of the MQ <insert_3> file system is <insert_1>% complete.
Severity
0 : Informational
Explanation
Recovery of the MQ <insert_3> file system is <insert_1>% complete. Message AMQ3509I is output when the file system has been recovered.
AMQ3508I
Recovery of the MQ <insert_3> file system has started.
Severity
0 : Informational
Explanation
Recovery of the MQ <insert_3> file system has started. Message AMQ3507I is periodically output to indicate progress and message AMQ3509I is output when recovery of the file system is complete. If an error occurs then message AMQ3510S is output to report the problem.
AMQ3509I
Recovery of the MQ <insert_3> file system has completed.
Severity
0 : Informational
Explanation
Recovery of the MQ <insert_3> file system has completed.
AMQ3510S
Recovery of the MQ <insert_3> file system has failed (phase <insert_1>, reason <insert_4>).
Severity
40 : Severe
Explanation
Recovery of the MQ <insert_3> file system has failed.
Response
Contact IBM Support for assistance and provide IBM with diagnostic information that exists in the mqtemporary: file system, including MQSystem.log and any FDC files that have been created.
AMQ3511I
Decryption of the MQ <insert_3> file system has started.
Severity
0 : Informational
Explanation
Decryption of the MQ <insert_3> file system has started. Message AMQ3512I is output when decryption of the file system is complete. If an error occurs then message AMQ3513E is output to report the problem and the appliance attempts to recover the file system. Other messages might also be output to provide additional information about the error for problem diagnosis.
AMQ3512I
Decryption of the MQ <insert_3> file system has completed.
Severity
0 : Informational
Explanation
Decryption of the MQ <insert_3> file system has completed.
AMQ3513E
Decryption of the MQ <insert_3> file system has failed (phase <insert_1>, reason <insert_4>).
Severity
20 : Error
Explanation
Decryption of the MQ <insert_3> file system has failed. Other messages might also be output to provide additional information about the error for problem diagnosis. The appliance attempts to recover the file system.
AMQ3514I
Encryption of the MQ <insert_3> file system has started.
Severity
0 : Informational
Explanation
Encryption of the MQ <insert_3> file system has started. Message AMQ3515I is output when encryption of the file system is complete. If an error occurs then message AMQ3516E is output to report the problem and the appliance attempts to recover the file system. Other messages might also be output to provide additional information about the error for problem diagnosis.
AMQ3515I
Encryption of the MQ <insert_3> file system has completed.
Severity
0 : Informational
Explanation
Encryption of the MQ <insert_3> file system has completed.
AMQ3516E
Encryption of the MQ <insert_3> file system has failed (phase <insert_1>, reason <insert_4>).
Severity
20 : Error
Explanation
Encryption of the MQ <insert_3> file system has failed. Other messages might also be output to provide additional information about the error for problem diagnosis. The appliance attempts to recover the file system.
AMQ3517E
Converting the MQ <insert_3> file system requires <insert_4>, but only <insert_5> disk space is currently available.
Severity
20 : Error
AMQ3518E
No action is scheduled for the file system.
Severity
20 : Error
Explanation
The file system is not scheduled to be encrypted or decrypted.
AMQ3519E
File system already scheduled for encryption.
Severity
20 : Error
Explanation
The file system is already scheduled to be encrypted when the appliance next restarts.
AMQ3520E
File system already scheduled for decryption.
Severity
20 : Error
Explanation
The file system is already scheduled to be decrypted when the appliance next restarts.
AMQ3521I
The required IBM MQ file systems are now available.
Severity
0 : Informational
Explanation
The required IBM MQ file systems are now available and the MQ Management Task is starting the MQ subsystem.
Response
Restart the MQ CLI to exit failsafe mode.
AMQ3522I
Usage: dspfspass - Display stored file system passphrase status
Display the status of stored passphrases for system file systems
dspfspass
Display the status of a stored passphrase for a system file system
dspfspass -f diag|errors|root|trace
Severity
0 : Informational
Response
None
AMQ3523I
Usage: setfspass - Configure file system passphrases
Update a file system passphrase
setfspass -u -f FileSystem [-p Passphrase] [-n NewPassphrase]
Clear a stored file system passphrase
setfspass -c -f FileSystem
Store a file system passphrase
setfspass -s -f FileSystem [-p Passphrase]
-c Clear a file system passphrase
-f MQ system file system:
diag, errors, root, trace
-n New file system passphrase
-p File system passphrase
-s Store a file system passphrase
-u Update a file system passphrase
Severity
0 : Informational
Response
None
AMQ3524I
Usage: status
Severity
0 : Informational
Explanation
This message displays usage for the IBM MQ status command.
AMQ3525I
The following MQ commands are available in failsafe mode.
Type help <command> for more information.
dspfspass Displays information about stored file system passphrases
setfspass Configures file system passphrases
status Displays status information
Severity
0 : Informational
Explanation
This message is issued when a user types help within the IBM MQ CLI in failsafe mode.
Response
None.
AMQ3526I
The backup storage is encrypted, but an encrypted file system has not been requested for the restored queue manager. Are you sure you wish to continue (yes/no)?
Severity
0 : Informational
Response
None.
AMQ3527S
A required IBM MQ file system is unavailable.
Severity
40 : Severe
Explanation
The MQ Management Task cannot initialize the MQ subsystem because a required IBM MQ file system is unavailable.
Response
Use the MQ CLI to determine which file system is unavailable.
An encrypted file system might be unavailable if its passphrase is not stored or its stored passphrase is not valid. The setfspass command can be used to store a required passphrase.
A transient failure to mount a file system might be resolved by rebooting the appliance. If the problem persists consult the error logs for more information then contact your IBM support center if you require assistance.
AMQ3528W
The passphrase could not be stored on remote appliance <insert_3>.
Severity
10 : Warning
Explanation
This message is issued when IBM MQ failed to store the passphrase for an encrypted queue manager file system on remote appliance <insert_3>. This might be because remote appliance <insert_3> is unavailable.
Response
Use the setfspass command to store the passphrase on remote appliance <insert_3> when it becomes available.
AMQ3529E
The backup for queue manager <insert_3> cannot be restored due to a resource conflict with queue manager <insert_4>.
Severity
20 : Error
Explanation
The queue manager backup cannot be restored because it requires a resource to be allocated that is already in use by another queue manager.
Response
Restore the queue manager backup on a different system, or contact IBM Support for assistance.
AMQ3530I
The queue manager file system is encrypted, but the backup storage is not encrypted. Are you sure you wish to continue (yes/no)?
Severity
0 : Informational
Response
None.
AMQ3531I
No stored passphrases found.
Severity
0 : Informational
AMQ3532E
Encryption is not supported for SAN queue managers.
Severity
20 : Error
AMQ3533E
File system is already encrypted.
Severity
20 : Error
AMQ3534E
File system is not encrypted.
Severity
20 : Error
AMQ3535E
The <insert_3> resource has failed for queue manager <insert_4> on this appliance.
Severity
20 : Error
Explanation
This message indicates that a resource associated with the specified high availability queue manager has failed, or a required network interface has been reconfigured. The high availability queue manager cannot be started on the impacted appliance(s) until the error has been resolved.
Response
View the failed resource actions for the queue manager with 'status <insert_4> -a'. Then fix the underlying issue, if it is still present. Once the issue has been fixed, clear the failed resource actions with 'cleanha -m <insert_3>.
AMQ3536I
File system scheduled action cancelled.
Severity
0 : Informational
AMQ3537E
Passphrases do not match.
Severity
20 : Error
Response
Re-issue the command with correct passphrases.
AMQ3538I
Re-enter new file system passphrase:
Severity
0 : Informational
AMQ3539I
Enter new file system passphrase:
Severity
0 : Informational
AMQ3540I
Enter current file system passphrase:
Severity
0 : Informational
AMQ3541I
Enter file system passphrase:
Severity
0 : Informational
AMQ3542I
File system scheduled for encryption.
Severity
0 : Informational
Explanation
The file system will be encrypted when the appliance next restarts.
Response
The status command can be used to confirm the action was completed after a restart.
AMQ3543I
File system scheduled for decryption.
Severity
0 : Informational
Explanation
The file system will be decrypted when the appliance next restarts.
Response
The status command can be used to confirm the action was completed after a restart.
AMQ3544E
File system passphrase not stored.
Severity
20 : Error
Response
None
AMQ3545I
File system passphrase cleared.
Severity
0 : Informational
Response
None
AMQ3546I
File system passphrase updated.
Severity
0 : Informational
Response
None
AMQ3547E
Invalid or incorrect passphrase.
Severity
20 : Error
Response
None
AMQ3548I
File system passphrase stored.
Severity
0 : Informational
Response
None
AMQ3549I
Usage: dspfspass - Display stored file system passphrase status
Display the status of all stored passphrases
dspfspass
Display the status of a specific stored passphrase
dspfspass (-f FileSystem | -m QMgrName)
-f MQ system file system:
backup, diag, errors, root, trace
-m Queue manager name
Severity
0 : Informational
Response
None
AMQ3550I
Usage: setfspass - Configure file system passphrases
Update a file system passphrase
setfspass -u (-f FileSystem | -m QMgrName)
[-p Passphrase] [-n NewPassphrase]
Clear a stored file system passphrase
setfspass -c (-f FileSystem | -m QMgrName)
Store a file system passphrase
setfspass -s (-f FileSystem | -m QMgrName)
[-p Passphrase]
Schedule a file system to be encrypted at restart
setfspass -e -f FileSystem [-p Passphrase]
Schedule a file system to be decrypted at restart
setfspass -d -f FileSystem [-p Passphrase]
Cancel a scheduled file system action
setfspass -x -f FileSystem
-c Clear a file system passphrase
-d Schedule a file system to be decrypted
-e Schedule a file system to be encrypted
-f MQ system file system:
backup, diag, errors, root, trace
-m Queue manager name
-n New file system passphrase
-p File system passphrase
-s Store a file system passphrase
-u Update a file system passphrase
-x Cancel a scheduled action
Severity
0 : Informational
Response
None
AMQ3551I
Usage: cleanha < -a | -m QMgrName >
-a Clear failed resource actions for all HA queue managers.
-m Clear failed resource actions for the specific HA queue manager.
Severity
0 : Informational
Response
None
AMQ3552I
Usage: dspdrsecondary -m QMgrName
-m Queue manager name
Severity
0 : Informational
Response
None
AMQ3553E
This command must be issued on an HA appliance for queue manager <insert_3>.
Severity
20 : Error
Explanation
It is not possible to run the command for queue manager <insert_3> on this appliance. The command can only be issued on an HA appliance.
AMQ3554I
Execute the following command on appliance <insert_4> <insert_5>
Severity
0 : Informational
Explanation
This message is issued by dspdrsecondary. It includes the crtdrsecondary command that should be executed on the remote DR appliance.
Response
The user should execute the command on the remote appliance.
AMQ3555E
Synchronous DR replication type not permitted for HA queue manager.
Severity
20 : Error
Explanation
The DR replication link type of an HA queue manager is only permitted to be asynchronous. types
AMQ3556E
DR status for queue manager <insert_3> is 'Failed negotiation'
Severity
20 : Error
Explanation
The replication type of the DR replication link is not consistent for the DR primary and DR secondary appliances. types
Response
Decide the replication type to be used for this queue manager and correct the definition. Use the 'dltdrprimary' and 'dltdrsecondary' commands to remove the current configuration then use 'crtdrprimary' and 'crtdrsecondary' to create a new configuration with consistent replication type.
AMQ3557E
The queue manager is running outside of HA control.
Severity
20 : Error
Explanation
The command is unable to complete as the queue manager has been started outside of HA control using 'strmqm -ns'.
Response
Issue 'endmqm' to stop the queue manager.
AMQ3558E
HA replication link mismatch for the replacement appliance <insert_3>. Expected <insert_4>.
Severity
20 : Error
Explanation
The HA replication link on the appliance <insert_3> must be configured to the IP address <insert_4>. The HA replication link is either configured to the wrong interface or the interface is configured with the wrong IP address.
Response
Decide which interface to use for the HA replication link and ensure it is configured to the correct IP address (<insert_4>). Use the 'dsphalink' command to display the current settings for the link. After selecting and configuring the link correctly, use the 'sethalink' command to update the HA replication link settings.
AMQ3559E
Partner appliance <insert_3> is still online and active in the HA group.
Severity
20 : Error
Explanation
Cannot recreate the HA group, as the original partner appliance <insert_3> is still online and active in the HA group.
Response
If you wish to replace the original partner appliance with a new appliance, then ensure the original partner appliance is powered off, before retrying the command.
AMQ3560E
This appliance is not online in the HA group.
Severity
20 : Error
Explanation
This message is issued when a command could not be completed as it requires this appliance to be online in the HA group.
This error is most commonly caused by this appliance being in standby mode.
Response
Ensure this appliance is online in the HA group and retry the command.
Use 'dsphagrp' or the MQ Console to view the status of this appliance in the HA group.
If this appliance is in standby mode, use 'sethagrp -r' or the MQ Console to resume it.
AMQ3561I
Removed configuration for queue manager <insert_3> on appliance <insert_4>.
Severity
0 : Informational
AMQ3562I
Removing disaster recovery configuration for queue manager <insert_3> on appliance <insert_4>.
Severity
0 : Informational
AMQ3563I
Removing high availability configuration for queue manager <insert_3> on appliance <insert_4>.
Severity
0 : Informational
AMQ3564I
Recreation completed for queue manager <insert_3> on appliance <insert_4>.
Severity
0 : Informational
AMQ3565I
Recreating disaster recovery configuration for queue manager <insert_3> on appliance <insert_4>.
Severity
0 : Informational
AMQ3566I
Recreating high availability configuration for queue manager <insert_3> on appliance <insert_4>.
Severity
0 : Informational
AMQ3567E
Network interface configuration mismatch for the replacement appliance <insert_3>. Expected <insert_5> on interface <insert_4>.
Severity
20 : Error
Explanation
The interface <insert_4> on the appliance <insert_3> must be configured to have the IP address <insert_5>.
Response
Make the appropriate configuration changes and then try the command again.
AMQ3568E
System name mismatch for the replacement appliance. Expected <insert_3>.
Severity
20 : Error
Explanation
The replacement appliance's system name must be configured to <insert_3>.
Response
Make the appropriate configuration changes and then try the command again.
AMQ3569I
HA role for queue manager <insert_3> is none
Severity
0 : Informational
Explanation
This message indicates a queue manager has no HA role on the local appliance, because the high availability subsystem has been suspended on the local appliance.
AMQ3570E
Unable to contact partner appliance at address <insert_3> from appliance <insert_4>.
Severity
20 : Error
Explanation
The specified appliance was unable to establish a network connection to the partner appliance.
Response
Check that the partner address is correct. Verify the network connection between the two appliances.
AMQ3571E
The network address of <insert_3> on remote appliance <insert_4> could not be determined.
Severity
20 : Error
Explanation
This message is issued when IBM MQ cannot determine a local network address for the specified network interface on a remote appliance.
Response
Ensure that the network interface is configured and enabled before reissuing the command.
AMQ3572E
The name of the local appliance is not valid.
Severity
20 : Error
Explanation
This message is issued when IBM MQ detects that the name of the local appliance is not valid. The name must be between 1 and 127 characters in length, containing only 7-bit US-ASCII letters, numbers, underscore, dash or dot. The name must not start with a dash or a dot. The name must be unique for each appliance in an HA cluster or DR configuration.
Response
Ensure that the name of the local appliance is valid then reissue the command. The appliance name is a system setting that can be configured using either the command interface or the web UI.
AMQ3573E
The name of the remote appliance is not valid.
Severity
20 : Error
Explanation
This message is issued when IBM MQ detects that the name of the remote appliance is not valid. The name must be between 1 and 127 characters in length, containing only 7-bit US-ASCII letters, numbers, underscore, dash or dot. The name must not start with a dash or a dot. The name must be unique for each appliance in an HA cluster or DR configuration.
Response
Ensure that the name of the remote appliance is valid then reissue the command. The appliance name is a system setting that can be configured using either the command interface or the web UI.
AMQ3574E
DR replication to remote appliance <insert_3> for queue manager <insert_4> using interface <insert_5> is unavailable
Severity
20 : Error
Explanation
This message indicates that DR replication to the remote appliance for the named queue manager is not available.
AMQ3575I
DR replication to remote appliance <insert_3> for queue manager <insert_4> using interface <insert_5> is available
Severity
0 : Informational
Explanation
This message indicates that DR replication to the remote appliance for the named queue manager is available.
AMQ3576E
HA replication to remote appliance <insert_3> for queue manager <insert_4> using interface <insert_5> is unavailable
Severity
20 : Error
Explanation
This message indicates that HA replication to the remote appliance for the named queue manager is not available.
AMQ3577I
HA replication to remote appliance <insert_3> for queue manager <insert_4> using interface <insert_5> is available
Severity
0 : Informational
Explanation
This message indicates that HA replication to the remote appliance for the named queue manager is available.
AMQ3578E
DR status for queue manager <insert_3> is 'UNKNOWN'
Severity
20 : Error
Explanation
This message indicates the status of the disaster recovery configuration for the specified queue manager cannot be determined.
AMQ3579W
DR status for queue manager <insert_3> is 'Reverting to snapshot'
Severity
10 : Warning
Explanation
This message indicates that the data for the specified queue manager is reverting to the snapshot that was taken before the queue manager entered the inconsistent disaster recovery state. The queue manager cannot be started on the appliance until the process completes.
AMQ3580E
DR status for queue manager <insert_3> is 'Inconsistent'
Severity
20 : Error
Explanation
This message indicates that the data for the specified queue manager is inconsistent because synchronization for the disaster recovery configuration was interrupted before it could complete. If the queue manager is started on the recovery appliance the queue manager data is reverted to the snapshot that was taken before it entered the inconsistent state.
AMQ3581W
DR status for queue manager <insert_3> is 'Remote appliance not configured'
Severity
10 : Warning
Explanation
This message indicates that the disaster recovery configuration for the specified queue manager has not been configured on the remote appliance.
Response
Issue crtdrsecondary on remote appliance to complete disaster recovery configuration.
AMQ3582E
DR status for queue manager <insert_3> is 'Remote appliance unavailable'
Severity
20 : Error
Explanation
This message indicates that the disaster recovery replication connection for the specified queue manager has been lost.
AMQ3583W
DR status for queue manager <insert_3> is 'Inactive'
Severity
10 : Warning
Explanation
This message indicates the specified queue manager has the DR secondary role on both appliances.
Response
Promote one appliance to the DR primary role to resume replication.
AMQ3584S
DR status for queue manager <insert_3> is 'Partitioned'
Severity
40 : Severe
Explanation
This message indicates that the data for the specified queue manager is out of step on the appliances in the disaster recovery configuration and cannot be automatically resolved.
Response
Issue makedrsecondary on the appliance containing the data to be discarded then issue makedrprimary on the appliance containing the data to be retained. Refer to the Troubleshooting section in IBM Documentation for more information.
AMQ3585W
DR status for queue manager <insert_3> is 'Synchronization in progress'
Severity
10 : Warning
Explanation
This message indicates that data is being synchronized for the specified queue manager. This status indicates that initial synchronization is in progress, or there has been a failure of the disaster recovery replication connection and replication for the queue manager has switched to synchronization mode to catch up as quickly as possible. The queue manager cannot be started on the recovery appliance until initial synchronization has completed. If subsequent synchronization is interrupted the queue manager on the recovery appliance enters the inconsistent state.
AMQ3586I
DR status for queue manager <insert_3> is 'Normal'
Severity
0 : Informational
Explanation
This message indicates the disaster recovery configuration for the specified queue manager is operating normally.
AMQ3587E
HA status for queue manager <insert_3> is 'UNKNOWN'
Severity
20 : Error
Explanation
This message indicates the high availability status for the specified queue manager cannot be determined.
AMQ3588W
HA status for queue manager <insert_3> is 'Migration pending'
Severity
10 : Warning
Explanation
This message indicates that migration is pending for the specified high availability queue manager. The high availability queue manager cannot be started on the local appliance until migration completes.
AMQ3590W
HA status for queue manager <insert_3> is 'Secondary appliance in standby mode'
Severity
10 : Warning
Explanation
This message indicates that the high availability subsystem on the secondary appliance has been suspended by an administrator. The specified high availability queue manager cannot be started on the secondary appliance until the subsystem is resumed.
AMQ3591W
HA status for queue manager <insert_3> is 'This appliance in standby mode'
Severity
10 : Warning
Explanation
This message indicates that the high availability subsystem on the local appliance has been suspended by an administrator. The specified high availability queue manager cannot be started on the local appliance until the subsystem is resumed.
AMQ3592E
HA status for queue manager <insert_3> is 'Inconsistent'
Severity
20 : Error
Explanation
This message indicates that the data for the specified high availability queue manager is inconsistent because synchronization was interrupted before it could complete. The high availability queue manager cannot be started on the secondary appliance until synchronization has completed.
AMQ3593W
HA status for queue manager <insert_3> is 'Remote appliance not configured'
Severity
10 : Warning
Explanation
This message indicates that the remote appliance is not configured for the specified high availability queue manager.
AMQ3594E
HA status for queue manager <insert_3> is 'Remote appliance unavailable'
Severity
20 : Error
Explanation
This message indicates that the replication connection for the specified high availability queue manager has been lost.
AMQ3595W
HA status for queue manager <insert_3> is 'Inactive'
Severity
10 : Warning
Explanation
This message indicates a high availability queue manager is inactive on all appliances. Replication will start when one appliance is promoted to the HA primary role.
AMQ3596S
HA status for queue manager <insert_3> is 'Partitioned'
Severity
40 : Severe
Explanation
This message indicates that the data for the specified high availability queue manager is out of step on the appliances and cannot be automatically resolved.
Response
Issue makehaprimary on the appliance containing the data to be retained. Refer to the Troubleshooting section in IBM Documentation for more information.
AMQ3597E
HA status for queue manager <insert_3> is 'Secondary appliance unavailable'
Severity
20 : Error
Explanation
This message indicates that the heartbeat connections for the specified high availability queue manager have been lost.
AMQ3598W
HA status for queue manager <insert_3> is 'Synchronization in progress'
Severity
10 : Warning
Explanation
This message indicates that data is being synchronized for the specified high availability queue manager. The high availability queue manager cannot be started on the secondary appliance until initial synchronization has completed.
AMQ3599I
HA status for queue manager <insert_3> is 'Normal'
Severity
0 : Informational
Explanation
This message indicates a high availability queue manager is operating normally.
AMQ3632I
Usage: modver [ [-?|-h] | ([-m|-M] [-v] [kernelLevel]) ]
-?|-h \t Show this usage text and exit
-m \t Print the minimum IBM MQ <insert_3> Long Term Support maintenance level compatible with the appropriate kernel module kernel level
-M \t Only print the minimum compatible IBM MQ <insert_3> Long Term Support maintenance level, do not print the kernel module
-v \t Print verbose output
kernelLevel \t A RHEL <insert_1> kernel level to test, if omitted the currently running kernel level returned by 'uname -a' is used
Severity
0 : Informational
AMQ3633E
Pacemaker user 'hacluster' does not exist or does not have 'haclient' as its primary group
Severity
20 : Error
Explanation
The 'hacluster' user that is required by Pacemaker and RDQM does not exist on the local machine, or it does not have 'haclient' as its primary group.
Response
Investigate why the 'hacluster' user is not defined correctly, and either create it manually, correct its definition, or reinstall Pacemaker.
AMQ3634E
Pacemaker group 'haclient' does not exist.
Severity
20 : Error
Explanation
The 'haclient' group that is required by Pacemaker and RDQM does not exist on the local machine.
Response
Investigate why the 'haclient' group is not defined, and either create it manually or reinstall Pacemaker.
AMQ3635E
Failed to initialize replicated data queue manager <insert_3>.
Severity
20 : Error
AMQ3636I
DRBD kernel module status: <insert_3>
Severity
0 : Informational
AMQ3637I
Previously installed version still loaded
Severity
0 : Informational
AMQ3638I
Partially loaded
Severity
0 : Informational
AMQ3639I
Loaded
Severity
0 : Informational
AMQ3640I
Not loaded
Severity
0 : Informational
AMQ3641I
OS kernel version: <insert_3>
Severity
0 : Informational
AMQ3642I
DRBD OS kernel version: <insert_3>
Severity
0 : Informational
AMQ3643I
DRBD version: <insert_3>
Severity
0 : Informational
AMQ3644I
Failed resource action <insert_3> found for queue manager <insert_4>.
Severity
0 : Informational
AMQ3645I
No failed resource actions found.
Severity
0 : Informational
AMQ3646I
HA last in sync: <insert_3>
Severity
0 : Informational
AMQ3647I
Timed out
Severity
0 : Informational
AMQ3648I
Blocked location: <insert_3>
Severity
0 : Informational
AMQ3649I
Usage: rdqmclean ( -a | -m QMgrName )
-a Clean all failed resource actions.
-m Clean failed resource actions for the specific replicated data queue manager.
Severity
0 : Informational
AMQ3650E
Failed to clean up failed resource actions.
Severity
20 : Error
AMQ3651I
Failed resource actions cleaned up.
Severity
0 : Informational
AMQ3652I
Failed resource action: <insert_3>
Severity
0 : Informational
AMQ3653I
Failure node: <insert_3>
Severity
0 : Informational
AMQ3654I
Failure time: <insert_3>
Severity
0 : Informational
AMQ3655I
Failure reason: <insert_3>
Severity
0 : Informational
AMQ3656I
Resource type: <insert_3>
Severity
0 : Informational
AMQ3657I
HA replication
Severity
0 : Informational
AMQ3658I
DR replication
Severity
0 : Informational
AMQ3659I
Filesystem
Severity
0 : Informational
AMQ3660I
Queue manager
Severity
0 : Informational
AMQ3661I
Floating IP
Severity
0 : Informational
AMQ3662I
RDQM control
Severity
0 : Informational
AMQ3663I
Monitor
Severity
0 : Informational
AMQ3664I
Start
Severity
0 : Informational
AMQ3665I
Stop
Severity
0 : Informational
AMQ3666I
Promote
Severity
0 : Informational
AMQ3667I
Demote
Severity
0 : Informational
AMQ3668I
A replicated data communications error has occurred to remote host <insert_3> (reason: <insert_4>).
Severity
0 : Informational
AMQ3669I
HA blocked location: <insert_3>
Severity
0 : Informational
AMQ3670I
All nodes
Severity
0 : Informational
AMQ3671I
Generic error
Severity
0 : Informational
AMQ3672I
Invalid configuration
Severity
0 : Informational
AMQ3673I
Not implemented
Severity
0 : Informational
AMQ3674I
Not configured
Severity
0 : Informational
AMQ3675I
Not running
Severity
0 : Informational
AMQ3676I
DR last in sync: <insert_3>
Severity
0 : Informational
AMQ3677I
Replicated data diagnostic information has been generated in <insert_3>.
Severity
0 : Informational
AMQ3678E
The node name <insert_3> specified on line <insert_1> of ini file <insert_4> must match the local host name <insert_5>.
Severity
20 : Error
Explanation
The specified node name must match the host name, i.e. 'uname -n'.
Response
Check the contents of the ini file and make sure it contains valid node name.
AMQ3679I
Secondary pending
Severity
0 : Informational
AMQ3680E
The HA subsystem was unable to start replicated data queue manager <insert_3>.
Severity
20 : Error
Explanation
The HA subsytem is managing the replicated data queue manager but was unable to start the queue manager.
Response
Query the HA subsystem with a "crm status" command to determine the cause of the issue. Resolve the issue and cleanup any failed actions with a "crm resource cleanup" command.
AMQ3681E
The HA subsystem is already managing replicated data queue manager <insert_3>.
Severity
20 : Error
Explanation
The HA subsytem is managing the replicated data queue manager but the queue manager is not running. This may be a transitory state.
Response
Recheck the status of the queue manager. If the queue manager is still not running query the HA subsystem with a "crm status" command to determine the cause of the issue. Resolve the issue and cleanup any failed actions with a "crm resource cleanup" command.
AMQ3682I
Waiting for initial connection
Severity
0 : Informational
AMQ3683E
The <insert_4> stanza starting at line <insert_1> of ini file <insert_3> must contain <insert_2> instances of the <insert_5> attribute.
Severity
20 : Error
Explanation
The mentioned stanza must contain certain number of the specified attribute instances.
Response
Check the contents of the ini file and make sure it contains required number of the specified attributes.
AMQ3684E
Unknown stanza key <insert_4> on line <insert_1> of ini file <insert_3>.
Severity
20 : Error
Explanation
Line <insert_1> of the configuration file <insert_3> contained a stanza called <insert_3>. This stanza is not recognized.
Response
Check the contents of the file and retry the operation.
AMQ3685E
Found multiple <insert_4> stanzas with the same value of <insert_5> attribute in ini file <insert_3>.
Severity
20 : Error
Explanation
The mentioned attribute must have unique value across all stanzas of the type.
Response
Make sure the ini file contains unique value for the mention attribute of the stanza type.
AMQ3686E
The command failed because the initial synchronization has not started for queue manager <insert_3>.
Severity
20 : Error
Explanation
This message is issued from a command when it failed because the initial synchronization has not started.
Response
Reissue the command when the initial synchronization starts.
AMQ3687E
The command failed because the <insert_3> kernel module is not loaded.
Severity
20 : Error
Explanation
The command failed because it appears that the <insert_3> kernel module is not loaded or not installed into the system.
Response
Make sure the <insert_3> kernel module is installed into the system and issue the command again.
AMQ3688I
Not authorized
Severity
0 : Informational
AMQ3689E
The command failed because it was not issued on node <insert_3> which contains the snapshot for queue manager <insert_4>.
Severity
20 : Error
Explanation
Since DR synchronization with remote site did not finish, the issued command must run on the node where snapshot for queue manager's volume was created.
Response
Run the previous command on the specified node.
AMQ3690I
You should ensure this command is also run on node <insert_3>.
Severity
0 : Informational
AMQ3691I
You should ensure this command is also run on nodes <insert_3> and <insert_4>.
Severity
0 : Informational
AMQ3692I
The DR replicated data queue manager might also need to be deleted on the remote HA group.
Severity
0 : Informational
AMQ3693E
Permission denied copying the file <insert_3> to remote node <insert_4>.
Severity
20 : Error
Explanation
Failed copying the mentioned file to remote node due to denied permission.
Response
Check the remote node and make sure the IBM MQ userid has permission to write the mentioned file.
AMQ3694E
Failed to create secondary queue manager on <insert_3>. To see the reason for the failure, run the following command on node <insert_3>:
Severity
20 : Error
Explanation
Failed creating secondary queue manager on remote node via OpenSSH.
Response
To see the failure reason, run 'crtmqm' command directly on the remote node and check its response.
AMQ3695E
The <insert_3> address <insert_4> corresponds to multiple local network interfaces.
Severity
20 : Error
Explanation
Only one IP address of a local network interface is allowed in the specified list of addresses.
Response
Review the specified list of addresses and make sure it contains only one IP address of a local network interface. Issue the command again once corrected.
AMQ3696E
System file or directory <insert_3> does not have required permissions <insert_4>.
Severity
20 : Error
Explanation
The replicated data subsystem requires system file or directory <insert_3> to have permissions <insert_4>.
Response
Modify the permissions on <insert_3> and rerun the command.
AMQ3697I
See <insert_3>
Severity
0 : Informational
AMQ3698I
Replicated data queue manager <insert_3> will be migrated when it is next restarted.
Severity
0 : Informational
AMQ3699I
Found <insert_4> out of sync blocks for the <insert_3> replicated data queue manager.
Severity
0 : Informational
AMQ3700I
Replicated data queue manager <insert_3> has been verified.
Severity
0 : Informational
AMQ3701I
DR current remote IP address: <insert_3>
Severity
0 : Informational
AMQ3702I
DR remote IP address list: <insert_3>
Severity
0 : Informational
AMQ3703E
Stanza <insert_4> with Name <insert_5> not found in ini file <insert_3>.
Severity
20 : Error
Explanation
The mentioned ini file is missing the required stanza.
Response
Make sure the required stanza is configured in the mentioned ini file, then issue the command again.
AMQ3704E
The HA primary node for queue manager <insert_3> could not be determined.
Severity
20 : Error
AMQ3705E
The command failed because it was not issued on the HA primary node for queue manager <insert_3>.
Severity
20 : Error
Explanation
The command must be run on the HA primary node for the queue manager.
Response
Run the command on the HA primary node for the queue manager.
AMQ3706E
HA queue manager <insert_5> already exists with <insert_3> set to <insert_4>.
Severity
20 : Error
Explanation
All instances of the replicated data queue manager must be created with the same value of the mentioned attribute.
Response
Create all instances of the replicated data queue manager with the same value of the attribute.
AMQ3707E
The replicated data subsystem configuration on node <insert_3> does not match the local node.
Severity
20 : Error
AMQ3708I
Issue the following command on the remote HA group to create the DR/HA secondary queue manager:
Severity
0 : Informational
AMQ3709E
HA queue manager <insert_3> must be recreated as an HA secondary.
Severity
20 : Error
Explanation
HA queue managers on replacement nodes need to be recreated as HA secondaries.
Response
Recreate the queue manager as an HA secondary.
AMQ3710E
Creating replicated-data queue managers is not supported into file path containing symbolic links <insert_3>.
Severity
20 : Error
Explanation
Target folder for replicated data queue managers is not allowed to contain symbolic links.
Response
Make sure queue managers' target folder does not contain symbolic links.
AMQ3711E
Required system command <insert_3> not found.
Severity
20 : Error
Explanation
The mentioned system command is required in order to complete the invoked MQ command.
Response
Make sure the required system command is installed in the system.
AMQ3712I
Upgraded replicated data subsystem.
Severity
0 : Informational
AMQ3713E
Failed to upgrade replicated data subsystem.
Severity
20 : Error
AMQ3714I
Migrated replicated data queue manager <insert_3>.
Severity
0 : Informational
AMQ3715E
Failed to migrate replicated data queue manager <insert_3>.
Severity
20 : Error
AMQ3716I
unconfigured
Severity
0 : Informational
AMQ3717E
Unable to load <insert_3> kernel module built for kernel version <insert_4> into current kernel <insert_5>.
Severity
20 : Error
AMQ3718I
Starting
Severity
0 : Informational
AMQ3719E
Configured attribute <insert_4> with value <insert_5> not found in ini file <insert_3>.
Severity
20 : Error
Explanation
The mentioned ini file is missing configuration of the required attribute.
Response
Make sure the required attribute is configured in the mentioned ini file.
AMQ3720E
The local <insert_3> UID <insert_1> does not match the <insert_3> UID <insert_2> on node <insert_4>.
Severity
20 : Error
Explanation
The local UID does not match the UID on a remote node. The UIDs should be consistent across the nodes.
Response
Ensure the UIDs are consistent across the nodes.
AMQ3721E
The local <insert_3> GID <insert_1> does not match the <insert_3> GID <insert_2> on node <insert_4>.
Severity
20 : Error
Explanation
The local GID does not match the GID on a remote node. The GIDs should be consistent across the nodes.
Response
Ensure the GIDs are consistent across the nodes.
AMQ3722I
Not installed
Severity
0 : Informational
AMQ3723E
Replicated data negotiation failed.
Severity
20 : Error
Explanation
The initial replicated data negotiation failed. This can happen when incompatible attributes are used to create the replicated data queue manager on the two nodes. The remote node will be in failed negotiation state.
Response
The replicated data queue manager should be created on the two nodes with compatible attributes. If the remote node is the primary, the command 'rdqmadm -p -m QMgrName' can be used to clear the failed negotiation state.
AMQ3724I
Released replicated data control command lock.
Severity
0 : Informational
AMQ3725E
Failed to release replicated data control command lock.
Severity
20 : Error
AMQ3726E
<insert_3> must be permissive when SELinux mode is Enforcing.
Severity
20 : Error
AMQ3727E
IBM MQ queue manager <insert_3> is not an HA replicated data queue manager.
Severity
20 : Error
Explanation
The command cannot run for the queue manager as it is not an HA replicated data queue manager.
Response
Make sure the command is run for an HA replicated data queue manager.
AMQ3728I
Replicated data diagnostic information has been generated.
Severity
0 : Informational
AMQ3729E
Failed to generate replicated data diagnostic information.
Severity
20 : Error
AMQ3730E
The replicated data directory <insert_3> is not empty.
Severity
20 : Error
AMQ3731I
Failed negotiation
Severity
0 : Informational
AMQ3732I
The DR replicated data queue manager might also need to be deleted on remote node <insert_3>.
Severity
0 : Informational
AMQ3733I
Initializing replicated data queue manager <insert_3>.
Severity
0 : Informational
AMQ3734I
Partitioned
Severity
0 : Informational
AMQ3735E
The replicated data DR remote IP address is not valid.
Severity
20 : Error
Explanation
An invalid replicated data DR remote IP address was specified.
Response
Review and correct the DR remote IP address then reissue the command.
AMQ3736E
The replicated data DR local IP address is not valid.
Severity
20 : Error
Explanation
An invalid replicated data DR local IP address was specified.
Response
Review and correct the DR local IP address then reissue the command.
AMQ3737E
The replicated data DR port is not valid.
Severity
20 : Error
Explanation
An invalid replicated data DR port was specified.
Response
Review and correct the DR port then reissue the command.
AMQ3738E
The replicated data DR replication type is not valid.
Severity
20 : Error
Explanation
An invalid replicated data DR replication type was specified. Valid values are "a" for asynchronous and "s" for synchronous.
Response
Review and correct the DR replication type then reissue the command.
AMQ3739E
The replicated data DR role is not valid.
Severity
20 : Error
Explanation
An invalid replicated data DR role was specified. Valid values are "p" for primary and "s" for secondary.
Response
Review and correct the DR role then reissue the command.
AMQ3740I
Remote node not configured
Severity
0 : Informational
AMQ3741I
Snapshot reversion progress: <insert_3>
Severity
0 : Informational
AMQ3742I
Reverting to snapshot
Severity
0 : Informational
AMQ3743I
Started reversion to snapshot.
Severity
0 : Informational
AMQ3744I
DR type: <insert_3>
Severity
0 : Informational
AMQ3745I
DR local IP address: <insert_3>
Severity
0 : Informational
AMQ3746E
The command failed because it was not issued on the DR primary node for the queue manager.
Severity
20 : Error
Explanation
The command failed because it was not issued on the DR primary node for the queue manager.
Response
Issue the command on the DR primary node for the queue manager if that is required.
AMQ3747E
Replicated data systemd initialization failed.
Severity
20 : Error
AMQ3748I
Replicated data systemd initialization complete.
Severity
0 : Informational
AMQ3749I
Usage: rdqmd -s
Severity
0 : Informational
AMQ3750E
The <insert_3> address <insert_4> corresponds to a local network interface.
Severity
20 : Error
Explanation
The specified address must belong to a remote node, not a local network interface.
Response
Review the specified address and make sure it belongs to a remote node. Issue the command again once corrected.
AMQ3751E
The replicated data DR remote name is not valid.
Severity
20 : Error
Explanation
An invalid replicated data DR remote name was specified. The remote name corresponds to the value reported by the 'uname -n' command on the remote host. The remote name must be different to the value reported by the 'uname -n' command on the local host.
Response
Review and correct the DR remote name then reissue the command.
AMQ3752E
Insufficient space in volume group <insert_3>, <insert_4> required but only <insert_5> is available.
Severity
20 : Error
Explanation
The system does not have enough storage to complete the command.
Response
Make sure enough storage is available to complete the command.
AMQ3753I
DR role: <insert_3>
Severity
0 : Informational
AMQ3754I
DR status: <insert_3>
Severity
0 : Informational
AMQ3755I
DR port: <insert_1>
Severity
0 : Informational
AMQ3756I
DR remote IP address: <insert_3>
Severity
0 : Informational
AMQ3757I
DR synchronization progress: <insert_3>%
Severity
0 : Informational
AMQ3758I
DR estimated time of completion: <insert_3>
Severity
0 : Informational
AMQ3759I
DR out of sync data: <insert_3>KB
Severity
0 : Informational
AMQ3760W
The queue manager will not start or replicate until this node is resumed.
Severity
10 : Warning
Explanation
The queue manager will not be started, or replicated to other nodes, until the current node is resumed.
Response
Make sure the current node is resumed to get the queue manager started and replicated to other nodes.
AMQ3761W
This replicated data node is suspended.
Severity
10 : Warning
AMQ3762I
Usage: dspmq [-m QMgrName] [-o status | -s] [-o default]
[-o standby] [-o installation] [-o ha] [-o dr]
[-o nativeha] [-o all] [-x] [-n] [-a]
-a Display information about the active queue managers only.
-m Queue manager name.
-n Suppress translation of output strings.
-o all
Display all status information for the queue managers.
-o status
Display the operational status of the queue managers.
-o default
Display whether any of the queue managers are the default.
-o standby
Display whether a queue manager currently permits a standby instance.
-o installation
Display the installation details of the queue managers.
-o ha
Display the high availability information for the queue managers.
-o dr
Display the disaster recovery information for the queue managers.
-o nativeha
Display the Native HA status (available only in supported environments).
-s Display the operational status of the queue managers.
-x Display information about instances of queue managers.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ3763E
Queue manager <insert_3> is already the DR primary on the remote node.
Severity
20 : Error
AMQ3764I
Queue manager <insert_3> is already the DR primary on this node.
Severity
0 : Informational
AMQ3765I
Queue manager <insert_3> is already the DR secondary on this node.
Severity
0 : Informational
AMQ3766E
IBM MQ queue manager <insert_3> is not a DR replicated data queue manager.
Severity
20 : Error
Explanation
The command cannot run for the queue manager as it is not a DR replicated data queue manager.
Response
Make sure the command is run for a DR replicated data queue manager.
AMQ3767I
Usage: rdqmdr -m QMgrName ( -p | -s | -d )
-d Display the crtmqm command to configure the DR secondary instance of a queue manager.
-p Change DR role to primary.
-s Change DR role to secondary.
Severity
0 : Informational
AMQ3768E
Failed to display DR secondary command.
Severity
20 : Error
AMQ3769E
Failed to make queue manager <insert_3> the DR primary on this node.
Severity
20 : Error
AMQ3770E
Failed to make queue manager <insert_3> the DR secondary on this node.
Severity
20 : Error
AMQ3771I
Issue the following command on node <insert_3> to create the DR secondary queue manager:
Severity
0 : Informational
AMQ3772I
Queue manager <insert_3> has been made the DR primary on this node.
Severity
0 : Informational
AMQ3773I
Queue manager <insert_3> has been made the DR secondary on this node.
Severity
0 : Informational
AMQ3774E
Floating IP address <insert_3> is already in use.
Severity
20 : Error
Explanation
Failed adding the specified floating IP address as it is already in use.
Response
Run the command specifying a floating IP address which is not in use.
AMQ3775E
Duplicate attribute <insert_4> with value <insert_5> on line <insert_1> of ini file <insert_3>.
Severity
20 : Error
Explanation
Found duplicate attributes in the mentioned ini file, which is not allowed.
Response
Review the mentioned ini file and make sure it does not contain duplicate attributes.
AMQ3776E
The replicated data node <insert_3> is not online.
Severity
20 : Error
AMQ3777E
The replicated data node <insert_3> is not suspended.
Severity
20 : Error
AMQ3778E
The replicated data node <insert_3> is already suspended.
Severity
20 : Error
AMQ3779E
The replicated data subsystem has already been configured.
Severity
20 : Error
AMQ3780E
The remote <insert_3> address <insert_4> is not available.
Severity
20 : Error
Explanation
Failed reaching the mentioned remote address, which could be caused by network related issues.
Response
Review the network configuration of the system and make sure the remote address is reachable (ping is successful).
AMQ3781E
The <insert_3> address <insert_4> does not correspond to a local network interface.
Severity
20 : Error
Explanation
The specified address does not correspond to any of the local network interface. If the command expects a list of addresses, then none of those correspond to a local network interface.
Response
Review the specified address and make sure it corresponds to one of the local network interfaces. If the command expects a list of addresses, make sure one of them corresponds to a local network interface. Issue the command again once corrected.
AMQ3782E
Replicated data ini file <insert_3> not found.
Severity
20 : Error
Explanation
The mentioned ini file is required for configuration of replicated data queue managers.
Response
Make sure the replicated data ini file is present on the system and has a valid configuration.
AMQ3783I
Floating IP address <insert_3> is the address of local interface <insert_4>.
Severity
0 : Informational
AMQ3784I
The replicated data subsystem has been restarted.
Severity
0 : Informational
AMQ3785E
The replicated data subsystem has not been started.
Severity
20 : Error
AMQ3786I
Node <insert_3> is <insert_4>
Severity
0 : Informational
AMQ3787I
Queue manager name: <insert_3>
Severity
0 : Informational
AMQ3788I
HA current location: <insert_3>
Severity
0 : Informational
AMQ3789I
HA floating IP address: <insert_3>
Severity
0 : Informational
AMQ3790I
HA floating IP interface: <insert_3>
Severity
0 : Informational
AMQ3791E
None of the <insert_3> addresses correspond to a local network interface.
Severity
20 : Error
Explanation
One of the addresses in the mentioned list must correspond to a local network interface.
Response
Make sure the list contains an address of a local network interface.
AMQ3792I
A previous instance of the queue manager must first be deleted on the other replicated data nodes.
Severity
0 : Informational
AMQ3793E
The replicated data subsystem was unable to take the control command lock after <insert_1> seconds.
Severity
20 : Error
AMQ3794E
Prerequisite attribute <insert_4> missing for attribute <insert_5> in ini file <insert_3>.
Severity
20 : Error
AMQ3795E
Attribute <insert_4> should be set in all or none of the <insert_5> stanzas in ini file <insert_3>.
Severity
20 : Error
Explanation
The mentioned attribute must be configured for all instances of the stanza or not configured at all.
Response
Make sure the attribute is configured for all instances of the stanza or remove it completely.
AMQ3796I
The replicated data subsystem unconfiguration is complete.
Severity
0 : Informational
AMQ3797I
The replicated data subsystem should be unconfigured on all replicated data nodes.
Severity
0 : Informational
AMQ3798I
The replicated data subsystem configuration is complete.
Severity
0 : Informational
AMQ3799I
The replicated data subsystem should be configured on all replicated data nodes.
Severity
0 : Informational
AMQ3800E
Replicated data queue manager <insert_3> still exists.
Severity
20 : Error
Explanation
You cannot unconfigure the replicated data subsystem when a replicated data queue manager still exists.
Response
Delete the queue manager and reissue the command.
AMQ3801I
The replicated data subsystem has been configured on this node.
Severity
0 : Informational
AMQ3802I
The replicated data subsystem has been unconfigured on this node.
Severity
0 : Informational
AMQ3803I
The preferred replicated data node has been set to <insert_3> for queue manager <insert_4>.
Severity
0 : Informational
AMQ3804I
The replicated data node <insert_3> has been suspended.
Severity
0 : Informational
AMQ3805I
The replicated data node <insert_3> has been resumed.
Severity
0 : Informational
AMQ3806I
The floating IP address <insert_3> has been added to queue manager <insert_4>.
Severity
0 : Informational
AMQ3807I
The floating IP address has been deleted from queue manager <insert_3>.
Severity
0 : Informational
AMQ3808I
Creating replicated data queue manager configuration.
Severity
0 : Informational
AMQ3809I
Enabling replicated data queue manager.
Severity
0 : Informational
AMQ3810I
Replicated data queue manager enabled.
Severity
0 : Informational
AMQ3811I
Replicated data queue manager disabled.
Severity
0 : Informational
AMQ3812E
Failed to create replicated data queue manager configuration.
Severity
20 : Error
Explanation
Failed creating the replicated data queue manager due to the previously reported error.
Response
Examine the previously reported error to find the reason of the failure to create the replicated data queue manager.
AMQ3813E
Failed to enable replicated data queue manager.
Severity
20 : Error
AMQ3814I
You need to run the following command on node <insert_3>:
Severity
0 : Informational
AMQ3815I
You need to run the following command on nodes <insert_3> and <insert_4>:
Severity
0 : Informational
AMQ3816I
Removing replicated data queue manager configuration.
Severity
0 : Informational
AMQ3817E
Replicated data subsystem call <insert_3> failed with return code <insert_1>.
Severity
20 : Error
AMQ3818E
The replicated data subsystem has not been configured.
Severity
20 : Error
AMQ3819E
Failed to create logical volume <insert_3> in volume group <insert_4>.
Severity
20 : Error
AMQ3820E
Device <insert_3> not available after <insert_1> seconds.
Severity
20 : Error
AMQ3821E
Failed to unmount filesystem <insert_4> for queue manager <insert_3> after <insert_1> seconds.
Severity
20 : Error
AMQ3822E
Replicated data resource <insert_3> not in expected state <insert_4> after <insert_1> seconds.
Severity
20 : Error
AMQ3823E
The replicated data node <insert_3> does not exist.
Severity
20 : Error
AMQ3824I
Usage: rdqmadm ( -p -m QMgrName [ -n NodeName | -d ] |
-s [ -n NodeName ] |
-r [ -n NodeName ] |
-c |
-u )
-c Initialize the Pacemaker cluster, using the settings specified in
/var/mqm/rdqm.ini.
-d Clear the preferred location.
-m Queue manager name.
-n Node name.
-p Assign the local or specified node as the preferred location for
the named queue manager.
-r Resume the local or specified node.
-s Suspend the local or specified node.
-u Delete the Pacemaker cluster configuration.
Severity
0 : Informational
AMQ3825I
Usage: rdqmint -m QmgrName [ -a -f FloatingIP -l LocalInterface |
-d ]
-a Add a floating IP address.
-d Delete a floating IP address.
-f Floating IP address.
-l Local network interface.
-m Queue manager name.
Severity
0 : Informational
AMQ3826I
The secondary queue manager must first be created on the other replicated data nodes.
Severity
0 : Informational
AMQ3827I
The preferred replicated data node has been unset for queue manager <insert_3>.
Severity
0 : Informational
AMQ3828E
IBM MQ queue manager <insert_3> is not a replicated data queue manager.
Severity
20 : Error
Explanation
The command is valid only for replicated data queue managers.
Response
Reissue the command specifying the name of a replicated data queue manager.
AMQ3829E
The local host <insert_3> could not be found in the replicated data configuration.
Severity
20 : Error
AMQ3830E
Unknown attribute <insert_4> on line <insert_1> of ini file <insert_3>.
Severity
20 : Error
Explanation
An unknown attribute was found in the replicated data ini file, which cannot be handled.
Response
Remove configuration of the unsupported attribute from the replicated data ini file.
Usage: rdqmstatus [ -n | -m QMgrName [ -a ] ]
-a Include details of any failed resource actions.
-m Display the status of the specific replicated data queue manager.
-n Display the status of the nodes in the HA group.
If no options are specified, a summary of all replicated data queue managers is displayed.
Severity
0 : Informational
AMQ3845I
Unknown
Severity
0 : Informational
AMQ3846I
Primary
Severity
0 : Informational
AMQ3847I
Secondary
Severity
0 : Informational
AMQ3848I
Enabled
Severity
0 : Informational
AMQ3849I
Disabled
Severity
0 : Informational
AMQ3850I
This node
Severity
0 : Informational
AMQ3851I
None
Severity
0 : Informational
AMQ3852I
Mixed
Severity
0 : Informational
AMQ3853I
Normal
Severity
0 : Informational
AMQ3854I
Synchronization in progress
Severity
0 : Informational
AMQ3855I
Remote unavailable
Severity
0 : Informational
AMQ3856I
Inconsistent
Severity
0 : Informational
AMQ3857I
Paused
Severity
0 : Informational
AMQ3858I
This node in standby
Severity
0 : Informational
AMQ3859I
Remote node in standby
Severity
0 : Informational
AMQ3860I
All nodes in standby
Severity
0 : Informational
AMQ3861I
online
Severity
0 : Informational
AMQ3862I
offline
Severity
0 : Informational
AMQ3863I
standby
Severity
0 : Informational
AMQ3864I
The secondary queue manager has already been created on the other replicated data nodes.
Severity
0 : Informational
AMQ3865E
Invalid value <insert_5> for attribute <insert_4> on line <insert_1> of ini file <insert_3>.
Severity
20 : Error
Explanation
The mentioned attribute is set to an invalid value in the replicated data ini file.
Response
Review acceptable values for the attribute and update the replicated data ini file with the correct setting.
AMQ3866E
Unexpected number of stanza <insert_4> in ini file <insert_3>. Expected <insert_1>. Found <insert_2>.
Severity
20 : Error
Explanation
The replicated data ini file is expected to contain a certain number of instances of the mentioned stanza.
Response
Review the content of the replicated data ini file and make sure it contains the expected number of instances of the stanza.
AMQ3867E
Attribute <insert_4> of Node <insert_1> has the same value as attribute <insert_5> of Node <insert_2> in ini file <insert_3>.
Severity
20 : Error
Explanation
The mentioned attributes are not allowed to be set to the same value in the replicated data ini file.
Response
Review the content of the replicated data ini file and make sure these attributes are set to unique values.
AMQ3868W
IBM MQ queue manager running on node <insert_3>.
Severity
10 : Warning
AMQ3869E
Failed to disable replicated data queue manager.
Severity
20 : Error
AMQ3870E
Failed to set preferred replicated data node for queue manager <insert_3>.
Severity
20 : Error
AMQ3871E
Failed to suspend replicated data node.
Severity
20 : Error
AMQ3872E
Failed to resume replicated data node.
Severity
20 : Error
AMQ3873E
Failed to add floating IP address <insert_3> to queue manager <insert_4>.
Severity
20 : Error
AMQ3874E
Failed to delete floating IP address from queue manager <insert_3>.
Severity
20 : Error
AMQ3875E
Failed to configure replicated data subsystem.
Severity
20 : Error
AMQ3876E
Failed to unconfigure replicated data subsystem.
Severity
20 : Error
AMQ3877E
Floating IP address already exists for queue manager <insert_3>.
Severity
20 : Error
Explanation
Replicated data queue managers can have only one floating IP address configured.
Response
No action required.
AMQ3878E
Floating IP address does not exist for queue manager <insert_3>.
Severity
20 : Error
Explanation
The command failed because a floating IP address is not configured for the queue manager.
Response
No action required.
AMQ3879E
Resource <insert_3> not connected to <insert_4> after <insert_1> seconds.
Severity
20 : Error
Explanation
The specified RDQM resource failed to connect within the time limit, which is most likely caused by network connectivity issues.
Response
Check the HA Replication interface on the remote node is accessible from the local node and issue the command again.
AMQ3880E
A secondary queue manager has already been created with a filesystem size of <insert_1> megabytes.
Severity
20 : Error
Explanation
All instances of the replicated data queue manager must be created with the same filesystem size.
Response
Create all instances of the replicated data queue manager with the same filesystem size.
AMQ3881E
Failed to SSH to <insert_3> on address <insert_4>.
Severity
20 : Error
AMQ3882I
SSH is configured for this node.
Severity
0 : Informational
AMQ3883E
SSH is not fully configured for this node.
Severity
20 : Error
AMQ3884I
Secondary queue manager created on <insert_3>.
Severity
0 : Informational
AMQ3885I
Secondary queue manager deleted on <insert_3>.
Severity
0 : Informational
AMQ3886I
Configuring the replicated data subsystem.
Severity
0 : Informational
AMQ3887I
Unconfiguring the replicated data subsystem.
Severity
0 : Informational
AMQ3888I
The replicated data subsystem has been configured on <insert_3>.
Severity
0 : Informational
AMQ3889I
The replicated data subsystem has been unconfigured on <insert_3>.
Severity
0 : Informational
AMQ3890E
The replicated data subsystem was not available after <insert_1> seconds.
Severity
20 : Error
AMQ3891E
Unknown local interface name <insert_3>.
Severity
20 : Error
Explanation
Failed finding a local network interface with the name specified.
Response
Review network configuration of the node and reissue the command with a valid name of a local network interface.
AMQ3892E
Invalid floating IP address <insert_3>.
Severity
20 : Error
Explanation
The specified value of a floating IP address does not represent a valid IPv4 address.
Response
Reissue the command with a valid setting for the floating IPv4 address.
AMQ3893E
Floating IP address <insert_3> not in interface <insert_4> subnet.
Severity
20 : Error
Explanation
The specified floating IP address does not belong to the subnet of the network interface.
Response
Reissue the command specifying a floating IP address which belongs to the subnet of the chosen network interface.
AMQ3894I
Usage: crtmqm [-z] [-q] [-c Text] [-d DefXmitQ] [-h MaxHandles]
[-md DataPath] [-g ApplicationGroup] [-oa user|group]
[-t TrigInt] [-u DeadQ] [-x MaxUMsgs] [-lp LogPri] [-ls LogSec]
[-lc | -ll | -lla | -lln] [-lf LogFileSize] [-ld LogPath]
[-ii Path] [-ic Path] [-iv Name=Value[;Name=Value]]
[-fs FilesystemSize] [-sx | -sxs] [-rrp | -rrs] [-rta | -rts]
[-rl DRLocalIP] [-ri RemoteIP] [-rn DRRemoteName] [-rp DRPort]
[-p Port] QMgrName
-c Descriptive text.
-d Default transmission queue name.
-fs Replicated data queue manager filesystem size.
-g Restrict use of the queue manager to this group.
-h Maximum number of handles per connection handle.
-ii Autoconfiguration INI url/path/directory
-ic Autoconfiguration MQSC url/path/directory
-iv Autoconfiguration user variables.
-lc Use circular logging.
-ld Directory used to hold the log files for the queue manager.
-lf Log file size, specified in units of 4 KB pages.
-ll Use linear logging.
-lla Use linear logging with automatic management of log extents.
-lln Use linear logging with user archive management of log extents.
-lp Primary log files allocated when the queue manager is created.
-ls Secondary log files allocated when the primary files are exhausted.
-md Directory used to hold the data files for the queue manager.
-oa Authorization policy for the queue manager.
-p Create listener configured for TCP/IP on the specified port.
-q Make this queue manager the default queue manager.
-ri Replicated data DR remote IP address (DR) or addresses (DR/HA).
-rl Replicated data DR local IP address (DR) or addresses (DR/HA).
-rn Replicated data DR remote name (DR) or group (DR/HA).
-rp Replicated data DR port.
-rr Replicated data DR role ((p)rimary|(s)econdary).
-rt Replicated data DR replication type ((a)synchronous|(s)ynchronous).
-sx Replicated data HA primary queue manager.
-sxs Replicated data HA secondary queue manager.
-t Trigger interval in milliseconds.
-u Dead-letter queue name.
-x Maximum number of uncommitted messages under any one syncpoint.
-z Suppress error messages.
Severity
0 : Informational
AMQ3895I
The queue manager should be deleted on all replicated data nodes.
Severity
0 : Informational
AMQ3896E
Resource <insert_3> disk states unknown after <insert_1> seconds.
Severity
20 : Error
AMQ3897I
The replicated data subsystem has been verified.
Severity
0 : Informational
AMQ3898E
The replicated data subsystem verification failed.
Severity
20 : Error
AMQ3899E
Resource <insert_3> has no associated queue manager.
Severity
20 : Error
AMQ3900I
DR role for queue manager <insert_3> is primary
Severity
0 : Informational
Explanation
This message indicates a queue manager has the primary DR role on the local appliance.
AMQ3901I
DR role for queue manager <insert_3> is secondary
Severity
0 : Informational
Explanation
This message indicates a queue manager has the secondary DR role on the local appliance.
AMQ3902I
HA role for queue manager <insert_3> is primary
Severity
0 : Informational
Explanation
This message indicates a queue manager has the primary HA role on the local appliance.
AMQ3903I
HA role for queue manager <insert_3> is secondary
Severity
0 : Informational
Explanation
This message indicates a queue manager has the secondary HA role on the local appliance.
AMQ3904E
HA heartbeat connection to secondary appliance <insert_3> using interface <insert_4> is unavailable
Severity
20 : Error
Explanation
This message indicates the HA heartbeat connection to the secondary appliance using the named interface is not available.
AMQ3905I
HA heartbeat connection to secondary appliance <insert_3> using interface <insert_4> is available
Severity
0 : Informational
Explanation
This message indicates the HA heartbeat connection to the secondary appliance using the named interface is available.
AMQ3906S
HA secondary appliance <insert_3> is unavailable
Severity
40 : Severe
Explanation
This message indicates that an HA heartbeat connection to the secondary appliance is not available.
AMQ3907I
HA secondary appliance <insert_3> is available
Severity
0 : Informational
Explanation
This message indicates that an HA heartbeat connection to the secondary appliance is available.
AMQ3908I
HA group resumed on remote appliance <insert_3>
Severity
0 : Informational
Explanation
This message indicates the high availability group has been resumed on the remote appliance.
AMQ3909I
HA group resumed on the local appliance
Severity
0 : Informational
Explanation
This message indicates the high availability group has been resumed on the local appliance.
AMQ3910W
HA group suspended on remote appliance <insert_3>
Severity
10 : Warning
Explanation
This message indicates the high availability group has been suspended on the remote appliance.
AMQ3911W
HA group suspended on the local appliance
Severity
10 : Warning
Explanation
This message indicates the high availability group has been suspended on the local appliance.
AMQ3912I
HA preferred appliance for queue manager <insert_3> is <insert_4>
Severity
0 : Informational
Explanation
This message indicates the preferred appliance for the specified HA queue manager has been set to the named appliance.
AMQ3913I
HA control for queue manager <insert_3> is enabled
Severity
0 : Informational
Explanation
This message indicates an HA queue manager has been administratively started and the HA subsystem for the queue manager has been enabled.
AMQ3914W
HA control for queue manager <insert_3> is disabled
Severity
10 : Warning
Explanation
This message indicates an HA queue manager has been administratively ended and the HA subsystem for the queue manager has been disabled.
AMQ3915I
Backing up queue manager files. This may take a while ...
Severity
0 : Informational
Explanation
This message is issued when queue manager backup has started.
Response
Queue manager backup operation may take quite some time depending on its size. Don't interrupt the command and let it complete.
AMQ3916E
An important system process <insert_1> has ended due to signal <insert_2>
Severity
20 : Error
Explanation
An important system process has ended. Network adaptors are restarting. This might cause HA queue managers to be partitioned; check their status.
Response
This is an internal error. Contact your IBM service representative
AMQ3917E
The group id is not valid.
Severity
20 : Error
Explanation
This message is issued when you attempt to perform an operation that refers to a groupid that is not syntactically correct.
Response
Revise the command to use a valid groupid.
AMQ3918W
Unable to complete the requested command. Stanza <insert_3> with the name key set to <insert_4> does not exist.
Severity
10 : Warning
Explanation
IBM MQ has detected that a stanza with the name key supplied for the operation, does not exist. The command is unable to process the request.
Response
Check the spelling of the supplied Stanza and Name values and review the set of stanzas that do exist using the dspmqini command.
AMQ3919I
Stanza <insert_3> was successfully deleted.
Severity
0 : Informational
Explanation
IBM MQ has successfully deleted stanza <insert_3>.
Response
No action required.
AMQ3920I
The replication link for queue manager <insert_3> is IP address (<insert_4>) interface (<insert_5>)
Severity
0 : Informational
Response
None.
AMQ3921E
A network interface does not exist on the local appliance with the IP address <insert_3>
Severity
20 : Error
Explanation
This message is issued when IBM MQ cannot determine a local network interface for the specified network address.
Response
Ensure that a network interface is configured with the network address and that the interface is enabled, then reissue the command.
AMQ3922I
The default replication link is IP address (<insert_3>) interface (<insert_4>)
Severity
0 : Informational
Response
None.
AMQ3923E
SAN support is not available on this platform.
Severity
20 : Error
Explanation
SAN support is only available on the MQ Appliance M2000 and M2001 hardware models.
Response
Reissue the command without specifying SAN storage options so that local storage is used instead.
Usage: setdrlink -r <replication IP> | -d
-r IP address of local interface to be used for replication.
-d Reset to the default replication interface for this appliance.
Modifies the network interface which will be used for data replication by subsequently created DR queue managers.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ3926I
Usage: dspdrlink [-m QMName]
Displays the replication link that has been configured for the named queue manager.
If the -m parameter is omitted the command reports the replication link that has been configured for each disaster recovery (DR) queue manager. It also reports the default replication link that has been configured, which is used when a new DR queue manager instance is created.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ3927I
Usage: sethalink -r <replication IP> | -d
-r IP address of local interface to be used for replication.
-d Reset to the default replication interface for this appliance.
Modifies the network interface which will be used for data replication by any subsequently configured HA group.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ3928I
Usage: dsphalink
Displays the replication link currently configured for use when a High Availability group is created.
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ3929W
The selected interface (<insert_3>) might not provide sufficient replication bandwidth.
Severity
10 : Warning
Explanation
The interface specified to a sethalink or setdrlink command might not provide optimal performance when used as a data replication link.
Response
Consider use of 10GB or higher network interfaces for data replication.
AMQ3930E
Local (<insert_3>) and remote (<insert_4>) DR replication interfaces do not match.
Severity
20 : Error
Explanation
When adding Disaster Recovery to a queue manager which is a member of an HA group, the local and partner machines have been configured to use differing DR replication interfaces.
Response
Use the setdrlink command to ensure that the same DR replication interface will be used on both members of the HA group.
AMQ3931E
Could not modify network configuration as HA group already established.
Severity
20 : Error
Explanation
An attempt was made to modify the default HA network configuration, but an HA group already exists.
Response
Before modifying the network configuration used for High Availability the appliance must be removed from any HA group. To remove the existing HA configuration issue the dlthagrp command.
AMQ3933I
High availability configuration of <insert_3> already migrated
Severity
0 : Informational
Response
None.
AMQ3934I
Migrating high availability configuration of <insert_3>
Severity
0 : Informational
Response
None.
AMQ3935I
userrestore completed successfully.
Severity
0 : Informational
Explanation
The restore of user data completed successfully
Response
No action required.
AMQ3936I
<insert_1> users and <insert_2> groups have been added to the system, <insert_3> users and <insert_4> groups have been deleted from the system and mqm group membership has been modified.
Severity
0 : Informational
Explanation
This message lets the user know how many users and groups were added and deleted in order to carry out restore.
AMQ3937E
HA operation is not available on this appliance because the IP configuration for the HA Interfaces has changed.
Severity
20 : Error
Explanation
The IP address of at least one of the HA interfaces has been modified. As a result HA operations are no longer available on this appliance.
Response
Recovery steps are listed below.
1) Re-configure the HA interfaces to use the IP address that was used originally to set up the HA configuration.
2) Reboot the appliance and remove the HA configuration on both appliances by removing queue managers from HA control.
3) Delete the HA group.
4) Allocate new IP addresses to the HA ports as required.
5) Re-create the HA group
AMQ3938I
Do you wish to proceed? [Y/N]
Severity
0 : Informational
Explanation
This message asks the user if they should proceed with restore users and groups.
AMQ3939I
<insert_1> users and <insert_2> groups will be added to the system, <insert_3> users and <insert_4> groups will be deleted and mqm group membership will be modified.
Severity
0 : Informational
Explanation
This message lets the user know how many users and groups were found to add and delete in order to carry out restore.
AMQ3940E
The specified network interface does not exist (<insert_3>).
Severity
20 : Error
Explanation
The network interface specified for 'sethaint' cannot be found in the system.
Response
Make sure a name of existing network interface is specified.
AMQ3941E
Link aggregation interface appears to be disabled.
Severity
20 : Error
Explanation
The specified link aggregation appears to be disabled and so can not be used with 'sethaint' command.
Response
Make sure the specified link aggregation interface is enabled.
AMQ3942E
The named link aggregation cannot be configured for floating IP.
Severity
20 : Error
Explanation
Not all interface names are compatible with MQ floating IP configurations. The name specified is not in the permitted set.
Response
Review the HA floating IP documentation and recreate the Link Aggregation interface definition with an object name which meets the rules for floating IP interface naming.
AMQ3943E
The prepareha command cannot execute because another instance is already running
Severity
20 : Error
Explanation
An attempt has been made to run the prepareha command when another instance of prepareha is already active.
Response
Wait for the instance that is already running to complete.
AMQ3945E
The operation failed because it required <insert_4>, but only <insert_3> disk space is currently available.
Severity
20 : Error
AMQ3946E
The queue manager file system cannot be resized due to the queue manager's configuration.
Severity
20 : Error
Explanation
The command failed because it is not permitted to resize a queue manager file system if the file system resides on SAN storage, or if the queue manager has been configured for either high availability or disaster recovery.
Response
Ensure the 'setmqsize' command is run for a queue manager that has not been configured to use SAN storage. If the queue manager has been configured for high availability or disaster recovery then that configuration must be removed first. The high availability or disaster recovery configuration can be restored after the file system has been resized.
AMQ3947E
The queue manager file system size can only be increased.
Severity
20 : Error
Explanation
The command failed because the new file system size is less than the current size.
Response
Review the current size of the queue manager file system, then rerun the command specifying a larger size.
AMQ3948I
Usage: setmqsize -m <qmname> -s <size>
-m Queue manager name.
-s New file system size.
Optional size modifiers that can be appended are:
m - megabytes
g - gigabytes (default)
Severity
0 : Informational
Response
None.
AMQ3949E
SAN volume <insert_3> is not accessible to queue manager <insert_4>.
Severity
20 : Error
Explanation
Queue manager cannot access its file system located on a SAN volume.
Response
Make sure the SAN volume containing queue manager's file system is available - the corresponding FibreChannelVolume object must be correctly configured and enabled.
AMQ3950E
Disaster recovery queue managers on SAN volumes are not supported.
Severity
20 : Error
Explanation
Queue managers on SAN volumes cannot be configured for disaster recovery.
Response
The 'crtdrprimary' command cannot be used to configure a SAN queue manager for Disaster Recovery. For DR options in SAN configurations review the 'addmqm' documentation in IBM Documentation.
AMQ3951E
The command <insert_3> cannot be issued against queue manager <insert_4> because that queue manager is not attached to a SAN volume.
Severity
20 : Error
Explanation
Command <insert_3> is only available for queue managers with SAN volumes attached. The queue manager <insert_4> does not have a SAN volume attached and therefore the command is invalid.
Response
No action required.
AMQ3952I
IBM MQ Appliance queue manager <insert_3> added.
Severity
0 : Informational
Explanation
An existing queue manager configuration was successfully added to this appliance.
Response
No action required.
AMQ3953E
Invalid queue manager name.
Severity
20 : Error
Explanation
The queue manager name given is not valid for the data found in the specified volume.
Response
The same queue manager name must be provided to the 'addmqm' command as was used when this queue manager was originally created. Issue 'addmqm' again with the correct -m parameter.
AMQ3954E
Queue manager not found in SAN volume.
Severity
20 : Error
Explanation
The specified SAN volume does not contain a valid queue manager file system.
Response
Make sure the SAN volume specified contains a valid MQ Appliance queue manager file system and reissue the command.
AMQ3955I
Usage: addmqm -m QMgrName -fc SANVolume
-m Queue manager name
-fc SAN volume name containing the queue manager
Severity
0 : Informational
Response
None.
AMQ3956E
The specified SAN volume is already in use by another queue manager.
Severity
20 : Error
Explanation
A SAN volume can host only one queue manager - multiple queue managers in a single volume are not allowed.
Response
Run the command again specifying a SAN volume which is not in use by any other queue manager.
AMQ3957E
Backup of SAN queue managers is not supported.
Severity
20 : Error
Explanation
Backup of queue managers created in SAN volumes is not supported.
Response
Make sure the queue manager being backed up is not created in SAN volume and then retry the command again.
AMQ3958E
The specified SAN volume is not empty.
Severity
20 : Error
Explanation
SAN volumes are supposed to contain data of a single queue manager. Therefor the specified SAN volume must be empty.
Response
Make sure the specified SAN volume is empty and then retry the command again.
AMQ3959E
The specified SAN volume does not exist or is not valid.
Severity
20 : Error
Explanation
The message is issued if the specified SAN volume does not exist or is not valid.
Response
Make sure the specified SAN volume exists and then retry the command again.
AMQ3960E
High availability queue managers on SAN volumes are not supported.
Severity
20 : Error
Explanation
Queue managers on SAN volumes cannot be configured for high availability.
Response
If you are creating new queue manager, issue the 'crtmqm' command without simultaneously supplying High availability and SAN options. The 'sethagrp' command cannot be used to configure a SAN queue manager for High Availability.
AMQ3961E
The environment variable <insert_3> is immutable.
Severity
20 : Error
Explanation
The environment variable specified is not permitted to be changed by the user.
Response
None.
AMQ3962I
MCA interception rule for channel <insert_3> added successfully.
Severity
0 : Informational
Explanation
An MCA interception rule for the channel was added successfully.
Response
None.
AMQ3963I
MCA interception rule for channel <insert_3> deleted successfully.
Severity
0 : Informational
Explanation
The AMS MCA interception rule was deleted successfully.
Response
None.
AMQ3964E
Could not find an MCA interception rule for channel <insert_3>.
Severity
20 : Error
Explanation
No MCA interception rule exists for the channel specified.
Response
None.
AMQ3965I
No MCA interception rules are defined for the queue manager.
Severity
0 : Informational
Explanation
MCA interception rules were requested to be displayed but none have been defined for the queue manager
Response
Use setamschl -m QMgr -n Channel -c Cert to create an MCA interception rule.
AMQ3966I
Usage: dspamschl -m QMgrName (-n ChannelName)
-m Queue manager name
-n Channel Name
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ3967E
Unable to complete the requested command. MCA interception rule does not exist for channel <insert_3>.
Severity
20 : Error
Explanation
An attempt was made to delete the AMS interception rule for channel <insert_3> but no matching rule was found.
Response
Use setamschl -m QMgr -n Channel -c Cert to create an MCA interception rule.
AMQ3968E
MCA interception rule already exists for channel <insert_3>.
Severity
20 : Error
Explanation
A new MCA interception rule has been requested for channel <insert_3> but a rule for the channel has already been defined. It is only possible to have one MCA interception rule per channel. Delete the existing rule then redefine it.
Response
Use setamschl -m QMgr -n Channel -d to delete the rule then add the new one.
AMQ3969I
Usage: setamschl -m QMgrName -n ChannelName ( -c CertificateName | -d [ -c CertificateName ] )
-m Queue manager name
-n Channel Name
-c Certificate Name
-d Delete AMS Interception on channel
Severity
0 : Informational
Explanation
This shows the correct usage.
Response
None.
AMQ3970I
Ping of DR secondary appliance replication interface <insert_3> was successful.
Severity
0 : Informational
AMQ3971I
Ping of DR secondary appliance replication interface <insert_3> was unsuccessful.
Severity
0 : Informational
Explanation
This appliance was unable to ping the DR secondary appliance. The queue manager may move to the HA secondary appliance if it is able to ping the DR secondary appliance.
Response
None.
AMQ3972E
Cannot backup DR queue manager, it is currently synchronizing or its data is inconsistent.
Severity
20 : Error
Explanation
A backup of a queue manager that is configured for disaster recovery (DR) has been requested on the appliance which has the DR secondary role. The backup operation cannot be performed because the DR status of the queue manager is either 'Inconsistent' or 'Synchronization in progress'.
Response
Ensure queue manager synchronization completes then retry the command.
AMQ3973I
SSH key generation time: <insert_3>
Severity
0 : Informational
Explanation
Displayed by dsphakeys.
Response
None.
AMQ3974E
The command could not be completed as the appliance is not in standby mode.
Severity
20 : Error
Explanation
This message is issued when a command could not be completed as it requires the appliance to be in standby mode.
Response
Ensure the appliance is in standby mode and retry the command.
AMQ3975I
Taking snapshot backup of active queue manager <insert_3>.
Severity
0 : Informational
Explanation
This message is issued when making backup of an active queue manager.
Response
If making backup of an active queue manager was not a planned action, stop queue manager and make its backup again.
AMQ3976E
The command failed because a floating IP address does not exist for the queue manager.
Severity
20 : Error
Explanation
A floating IP address does not exist for the queue manager.
Response
None.
AMQ3977E
The command failed because a floating IP address (<insert_3>) already exists for the queue manager.
Severity
20 : Error
Explanation
A floating IP address (<insert_3>) already exists for the queue manager.
Response
To replace the existing floating IP address the sethaint -d command should first be used to delete the existing floating IP address.
AMQ3978I
Usage: sethaint -m QMgrName (-a -f FloatingIP -l LocalInterface | -d)
-m Queue manager name
-a Add floating IP address
-f Floating IP address
-l Local network interface
-d Delete floating IP address
Severity
0 : Informational
Response
None.
AMQ3979E
The specified backup file is corrupted. Cannot restore from it.
Severity
20 : Error
Explanation
The 'mqrestore' command has failed since it found inconsistency in the specified backup file. The backup file could be modified/altered since it was created.
Response
Run the command again for another backup file.
AMQ3980E
Cannot create backup storage, since a user file/folder exists with its name: mqbackup:///QMgrs
Severity
20 : Error
Explanation
The 'createbackupfs' command cannot create backup storage, if there is already a file/folder exists with the name used for the storage (mqbackup:///QMgrs). reason.
Response
Delete the 'QMgrs' file/folder from 'mqbackup:' and run the command again.
AMQ3981E
Backup operation for <insert_3> queue manager has failed. Reason: <insert_4>
Severity
20 : Error
Explanation
This message is issued when the mqbackup command fails to create backup of a queue manager. It provides name of the queue manager and failure reason.
Response
This message is provided to indicate the failure of backup operation.
AMQ3982I
Backup operation for <insert_3> queue manager has started.
Severity
0 : Informational
Explanation
This message is issued when the mqbackup command is started.
Response
This message is provided to indicate the start of backup operation.
AMQ3983E
Backup storage contains files.
Severity
20 : Error
Explanation
The 'deletebackupfs' command failed, because backup storage is not empty.
Response
Delete all files from backup storage and then run the command again.
AMQ3984E
The command <insert_3> was aborted.
Severity
20 : Error
Explanation
The command was aborted and any of its changes are rolled back (no changes are done to the system).
Response
Rerun the command with correct parameters and let it complete.
AMQ3985I
Queue manager <insert_3> successfully restored from backup file <insert_4>.
Severity
0 : Informational
Explanation
This message is issued when the mqrestore command succeeds. It includes the name of the restored queue manager and the name of the backup file.
Response
The restored queue manager is now ready to be used with other MQ commands.
AMQ3986E
The command failed because another backup restore is in progress.
Severity
20 : Error
Explanation
Only single running queue manager backup restore operation is allowed. mqrestore command fails if run before completion of another instance of the running command.
Response
Make sure another backup operation completes and issue the command again.
AMQ3987E
The specified backup file name (<insert_3>) does not exist.
Severity
20 : Error
Explanation
The command failed because the specified backup file name does not exist.
Response
Specify existing backup file name and issue the command again. Specify only the file name part, without extension.
AMQ3988I
Backup operation for <insert_3> queue manager has completed successfully. Created backup file: <insert_4>
Severity
0 : Informational
Explanation
This message is issued when the mqbackup command succeeds. It includes the name of the created backup file.
Response
The provided file name can be used for reference to download backup file from the MQ appliance or for later queue manager restore operation.
AMQ3989E
The specified backup file name (<insert_3>) already exists.
Severity
20 : Error
Explanation
The command failed because the specified backup file name (or default backup file name based on queue manager's name) already exists.
Response
Specify alternate backup file name and issue the command again.
AMQ3990E
The command failed because the queue manager is being backed up.
Severity
20 : Error
Explanation
The command failed because the queue manager is locked for the duration of backup operation.
Response
Make sure backup operation is complete for the queue manager and try the command again.
AMQ3991I
Usage: mqbackup -m <qmname> [-o outfile]
-m Name of the queue manager to create backup for
-o Name of the backup file to create
Severity
0 : Informational
Response
None.
AMQ3992I
Usage: mqrestore -f <filename> [-e [-p Passphrase]] [-s FileSystemSize]
-f The name of a queue manager backup file to restore.
Specify only the name of the file, not its path.
-e Encrypt the file system.
-p Passphrase for the encrypted file system.
-s File system size.
Allowed size modifiers are m (megabytes) and g (gigabytes).
A size in gigabytes is assumed if a modifier is not specified.
The original file system size is used by default.
Severity
0 : Informational
Response
None.
AMQ3993I
Usage: <insert_3>
Severity
0 : Informational
Response
None.
AMQ3994I
Usage: createbackupfs -s FileSystemSize [-e [-p Passphrase]]
-s File system size.
Allowed size modifiers are m (megabytes) and g (gigabytes).
A size in gigabytes is assumed if a modifier is not specified.
-e Encrypt the file system.
-p Passphrase for the encrypted file system.
Severity
0 : Informational
Response
None.
AMQ3995E
The command failed because an invalid backup file name was specified.
Severity
20 : Error
Explanation
The command failed because the specified name of the backup file is not valid.
Response
Ensure the specified file name is valid (it contains only the characters a-z, A-Z, 0-9, '-', '_' and '.'), then issue the command again.
AMQ3996E
The command failed because backup storage already exists.
Severity
20 : Error
Explanation
The command failed because storage for creating backups of queue managers already exist.
Response
It is not allowed to create backup storage when one already exists. If its size needs to be changed, the existing backup storage must be deleted first.
AMQ3997E
The command failed because backup storage does not exist.
Severity
20 : Error
Explanation
The command failed because storage for creating backups of queue managers does not exist.
Response
Make sure backup storage exists and then issue the command again.
AMQ3998E
It is not permitted to change the value of the key <insert_3> for the queue manager <insert_4>.
Severity
20 : Error
Explanation
The specified key cannot be altered for queue managers that are a member of a high availability (HA) group.
Response
Review the supplied parameters then issue the command again, specifying a different key or a queue manager that is not a member of a high availability (HA) group.
AMQ3999E
Invalid value (<insert_4>) specified for the key <insert_3>.
Severity
20 : Error
Explanation
The supplied value is not permitted for the specified key.
Response
Review and correct the supplied parameters then issue the command again.