Viewing the status of Native HA queue managers for IBM MQ certified containers

For IBM® MQ certified containers, you can view the status of the Native HA instances by running the dspmq command inside one of the running Pods.

About this task

Important:

You can use the dspmq command in one of the running Pods to view the operational status of a queue manager instance. The information returned depends on whether the instance is active or a replica. The information supplied by the active instance is definitive, information from replica nodes might be out of date.

You can perform the following actions:

View whether the queue manager instance on the current node is active or a replica.
View the Native HA operational status of the instance on the current node.
View the operational status of all three instances in a Native HA configuration.

The following status fields are used to report Native HA configuration status:

ROLE: Specifies the current role of the instance and is one of Active, Replica, or Unknown.
INSTANCE: The name provided for this instance of the queue manager when it was created using the -lr option of the crtmqm command.
INSYNC: Indicates whether the instance is able to take over as the active instance if required.
QUORUM: Reports the quorum status in the form number_of_instances_in-sync/number_of_instances_configured.
REPLADDR: The replication address of the queue manager instance.
CONNACTV: Indicates whether the node is connected to the active instance.
BACKLOG: Indicates the number of KB that the instance is behind.
CONNINST: Indicates whether the named instance is connected to this instance.
ALTDATE: Indicates the date on which this information was last updated (blank if it has never been updated).
ALTTIME: Indicates the time at which this information was last updated (blank if it has never been updated).

Procedure

Find the pods that are part of your queue manager.

oc get pod --selector app.kubernetes.io/instance=nativeha-qm

Run the dspmq in one of the pods
```
oc exec -t Pod dspmq
```
```
oc rsh Pod
```
for an interactive shell, where you can run dspmq directly.
To determine whether a queue manager instance is running as the active instance or as a replica:
```
oc exec -t Pod dspmq -o status -m QMgrName
```
An active instance of a queue manager named BOB would report the following status:
```
QMNAME(BOB)                 STATUS(Running)
```
A replica instance of a queue manager named BOB would report the following status:
```
QMNAME(BOB)                 STATUS(Replica)
```
An inactive instance would report the following status:
```
QMNAME(BOB)                 STATUS(Ended Immediately)
```
To determine Native HA operational status of the instance in the specified pod:
```
oc exec -t Pod dspmq -o nativeha -m QMgrName
```
The active instance of a queue manager named BOB might report the following status:
```
QMNAME(BOB)               ROLE(Active) INSTANCE(inst1) INSYNC(Yes) QUORUM(3/3)
```
A replica instance of a queue manager named BOB might report the following status:
```
QMNAME(BOB)               ROLE(Replica) INSTANCE(inst2) INSYNC(Yes) QUORUM(2/3)
```
An inactive instance of a queue manager named BOB might report the following status:
```
QMNAME(BOB)               ROLE(Unknown) INSTANCE(inst3) INSYNC(no) QUORUM(0/3)
```

To determine the Native HA operational status of all the instances in the Native HA configuration:

oc exec -t Pod dspmq -o nativeha -x -m QMgrName

If you issue this command on the node running the active instance of queue manager BOB, you might receive the following status:

QMNAME(BOB)			ROLE(Active) INSTANCE(inst1) INSYNC(Yes) QUORUM(3/3)
 INSTANCE(inst1) ROLE(Active)  REPLADDR(9.20.123.45) CONNACTV(Yes) INSYNC(Yes) BACKLOG(0) CONNINST(Yes) ALTDATE(2022-01-12) ALTTIME(12.03.44)
 INSTANCE(inst2) ROLE(Replica) REPLADDR(9.20.123.46) CONNACTV(Yes) INSYNC(Yes) BACKLOG(0) CONNINST(Yes) ALTDATE(2022-01-12) ALTTIME(12.03.44)
 INSTANCE(inst3) ROLE(Replica) REPLADDR(9.20.123.47) CONNACTV(Yes) INSYNC(Yes) BACKLOG(0) CONNINST(Yes) ALTDATE(2022-01-12) ALTTIME(12.03.44)

If you issue this command on a node running a replica instance of queue manager BOB, you might receive the following status, which indicates that one of the replicas is lagging behind:

QMNAME(BOB)			ROLE(Replica) INSTANCE(inst2) INSYNC(Yes) QUORUM(2/3)
 INSTANCE(inst2) ROLE(Replica) REPLADDR(9.20.123.46) CONNACTV(Yes) INSYNC(Yes) BACKLOG(0) CONNINST(Yes) ALTDATE(2022-01-12) ALTTIME(12.03.44)
 INSTANCE(inst1) ROLE(Active)  REPLADDR(9.20.123.45) CONNACTV(Yes) INSYNC(Yes) BACKLOG(0) CONNINST(Yes) ALTDATE(2022-01-12) ALTTIME(12.03.44)
 INSTANCE(inst3) ROLE(Replica) REPLADDR(9.20.123.47) CONNACTV(Yes) INSYNC(No)  BACKLOG(435) CONNINST(Yes) ALTDATE(2022-01-12) ALTTIME(12.03.44)

If you issue this command on a node running an inactive instance of queue manager BOB, you might receive the following status:

QMNAME(BOB)			ROLE(Unknown) INSTANCE(inst3) INSYNC(no) QUORUM(0/3)
 INSTANCE(inst1) ROLE(Unknown) REPLADDR(9.20.123.45) CONNACTV(Unknown) INSYNC(Unknown) BACKLOG(Unknown) CONNINST(No) ALTDATE() ALTTIME()
 INSTANCE(inst2) ROLE(Unknown) REPLADDR(9.20.123.46) CONNACTV(Unknown) INSYNC(Unknown) BACKLOG(Unknown) CONNINST(No) ALTDATE() ALTTIME()
 INSTANCE(inst3) ROLE(Unknown) REPLADDR(9.20.123.47) CONNACTV(No) INSYNC(Unknown) BACKLOG(Unknown) CONNINST(No) ALTDATE() ALTTIME()

If you issue the command when the instances are still negotiating which is active and which are replicas, you would receive the following status:

QMNAME(BOB)              STATUS(Negotiating)