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
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.
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.
AMQ3635I
Failed to initialize replicated data queue manager <insert_3>.
Severity
0 : Informational
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.
AMQ3696E
System directory <insert_3> has incorrect permissions.
Severity
20 : Error
Explanation
The replicated data subsystem requires system directory <insert_3> to have permissions <insert_5>.
Response
Modify the permissions on <insert_3> and rerun the command.
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 a 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.
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
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
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
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
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 to 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
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]
[-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.
-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
AMQ3764E
Queue manager <insert_3> is already the DR primary on this node.
Severity
20 : Error
AMQ3765E
Queue manager <insert_3> is already the DR secondary on this node.
Severity
20 : Error
AMQ3766E
IBM MQ queue manager <insert_3> is not a DR replicated data queue manager.
Severity
20 : Error
AMQ3767I
Usage: rdqmdr -m QMgrName ( -p | -s | -d )
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
AMQ3775E
Duplicate attribute <insert_4> with value <insert_5> on line <insert_1> of ini file <insert_3>.
Severity
20 : Error
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
AMQ3781E
The <insert_3> address <insert_4> does not correspond to a local network interface.
Severity
20 : Error
AMQ3782E
Replicated data ini file <insert_3> not found.
Severity
20 : Error
AMQ3783I
Floating IP address <insert_3> is already bound to local interface <insert_4>.
Severity
0 : Informational
Explanation
The floating IP address must be a valid IPv4 address that is not already bound to a local network interface.
Response
Correct the command so that the floating IP address used is one that is not already bound to a local network interface.
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
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
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
AMQ3813E
Failed to enable replicated data queue manager.
Severity
20 : Error
AMQ3814I
You need to run command <insert_3> on node <insert_4>.
Severity
0 : Informational
AMQ3815I
You need to run command <insert_3> on nodes <insert_4> and <insert_5>.
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 stopped 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
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>.
Replicated data DR secondary queue manager:
crtmqm -rr s
-rl DRLocalIP -ri DRRemoteIP -rn DRRemoteName -rp DRPort
[-rt (a|s)] [-fs FilesystemSize]
[-z] 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.
-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.
-rl Replicated data DR local IP address.
-rn Replicated data DR remote name.
-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 primary queue manager.
-sxs Replicated data 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
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
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.
AMQ3932E
High availability resource failed for <insert_3>.
Severity
20 : Error
Explanation
The high availability queue manager <insert_3> has stopped due to a failed resource. This could be caused by changes to the network interfaces used by the high availability configuration for this queue manager.
Response
Correcting changes to the network interfaces will allow the high availability resource to recover. The high availability configuration must be removed before making changes to the appliance name or network interfaces used by the high availability configuration.
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.
AMQ3944E
The floating IP address parameter '-f' is required for HA queue managers.
Severity
20 : Error
Explanation
The specified queue manager has been configured for high availability but the floating IP address parameter was not specified to the crtdrprimary command.
A floating IP address is required to establish a disaster recovery configuration for a queue manager that has been configured for high availability. The floating IP address is used to replicate queue manager data from whichever HA appliance the queue manager is currently running on to the queue manager on the recovery appliance.
Response
Rerun the crtdrprimary command with corrected parameters.
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 the Knowledge Center.
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)
-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> was successfully restored from backup file.
Severity
0 : Informational
Explanation
This message is issued when the mqrestore command succeeds. It includes the name of the restored queue manager.
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>
-f Name of the backup file to restore queue manager from.
Only name of the file must be provided, not the path.
Severity
0 : Informational
Response
None.
AMQ3993I
Usage: <insert_3>
Severity
0 : Informational
Response
None.
AMQ3994I
Usage: createbackupfs -s <size>
-s Size of the backup storage to create. Allowed size modifiers are:
m - megabytes;
g - gigabytes.
By default the size is assumed in gigabytes.
Severity
0 : Informational
Response
None.
AMQ3995E
The command failed because 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
Make sure the specified file name is valid (contains only a-z, A-Z, 0-9 and '-', '_', '.' characters) and 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.