SET QSG

Use the SET QSG statement to specify the queue-sharing groups that the IBM MQ Monitoring Agent on z/OS® system monitors and the queue managers that the agent uses to collect queue-sharing group data.

At any given time, for a particular queue-sharing group, IBM MQ Monitoring Agent uses only one queue manager to gather data. If that queue manager becomes unavailable, another queue manager collects the data instead.

The SET QSG statement is optional. If this statement is not specified, the default behavior of the agent is to monitor all queue-sharing groups that are associated with monitored queue managers.

You can use the SET QSG statement to specify the following behaviors:

No queue-sharing groups are monitored.
A particular queue-sharing group is monitored.
A particular queue manager is used to collect queue-sharing group data.
The sysplex name for the queue-sharing group is included in the managed system name.

Syntax

SET QSG [NAME(nnnn)]
       [MGRNAME(mmmm)]......
       [MONITOR(NO|YES|TAKEOVER)]
       [USEPLEXNAME(NO|YES)]

Parameters

NAME(nnnn)

Specifies the name of a queue-sharing group. This parameter is optional. The default value is an asterisk (*).

MGRNAME(mmmm)

Specifies a queue manager name in a particular queue-sharing group. This parameter is optional. The default value is an asterisk (*).

MONITOR(NO|YES|TAKEOVER)

Specifies whether the agent monitors the specified combination of queue-sharing group and queue manager. It also specifies whether takeover processing is performed.

This parameter is optional. The default value is YES.

NO: The IBM MQ Monitoring Agent does not monitor the indicated combination of queue-sharing group and queue manager.

YES: The IBM MQ Monitoring Agent monitors the indicated combination of queue-sharing group and queue manager. This is the default behavior.

TAKEOVER: The IBM MQ Monitoring Agent takes over monitoring the indicated queue-sharing group even if another IBM MQ Monitoring Agent is already monitoring it. (Takeover processing does not occur if the other agent also specified TAKEOVER.)

USEPLEXNAME(NO|YES)

Specifies whether to include the sysplex name for the queue-sharing group in the managed system name. Use this parameter when you have multiple queue-sharing groups with the same names in different sysplexes in your monitoring enterprise. The queue-sharing group managed system name will be of the form qsg:sysplex:MQQSG.

The USEPLEXNAME parameter cannot be set with PARMGEN. To change this parameter setting, you must specify the SET QSG statement in KMQUSER, which will override what is set in KMQSTART. For information about updating KMQUSER, see Changing KMQUSER.

If you change this parameter setting, the following guidelines apply after restarting your IBM MQ Monitoring Agent with the parameter change:

When USEPLEXNAME is set to YES, the Tivoli Enterprise Portal Navigator does not show the sysplex portion of the name. In the Tivoli Enterprise Portal, the full name will appear in other places, such as the Managed System Status workspace, the Situation Editor, and the Object Group Editor.
In the Tivoli Enterprise Portal, use the Clear offline entry feature to remove the old offline managed system names that end with :MQQSG, which will be dimmed (grayed out) in the Tivoli Enterprise Portal Navigator.
For any situations distributed to queue-sharing group managed systems, update the Distribution tab for those situations to include the new managed system names.
For any custom managed systems groups that include the old queue-sharing group managed system names, update those groups with the new managed system names produced by the agent.

This parameter is optional. The default value is NO.

NO: Do not include the sysplex name in the managed system name.

YES: Include the sysplex name for the queue-sharing group in the managed system name. The sysplex name is produced as the middle qualifier. Use this setting when you use the same names in different sysplexes for multiple queue-sharing groups in your monitoring enterprise.

Example

To monitor no queue-sharing groups, specify the following statement:
```
SET QSG MONITOR(NO)
```
To eliminate queue manager PMQ5 from queue-sharing group monitoring, specify the following statement:
```
SET QSG MONITOR(NO) MGRNAME(PMQ5)
```
To direct queue-sharing group monitoring to the PMQ6 queue manager, specify the following statement:
```
SET QSG MONITOR(TAKEOVER) MGRNAME(PMQ6)
```
To specify that a particular queue-sharing group is, or is not, monitored might require multiple SET QSG statements.
For example, suppose that you have three queue-sharing groups in your environment named QSGA, QSGB, and QSGC. To monitor only the QSGC queue-sharing group, specify the following statements:
```
SET QSG NAME(*) MONITOR(NO)
SET QSG NAME(QSGC) MONITOR(YES)
```
The following statements produce the same result:
```
SET QSG NAME(QSGA) MONITOR(NO)
SET QSG NAME(QSGB) MONITOR(NO)
SET QSG NAME(QSGC) MONITOR(YES)
```
However, if you specify only the following statement, all three queue-sharing groups, including QSGA and QSGB, are monitored. This is because the default behavior of the agent is to monitor all queue-sharing groups.
```
SET QSG NAME(QSGC) MONITOR(YES)
```
To include the sysplex name for the queue-sharing group in the managed system name, specify the following SET QSG statement in KMQUSER:
```
SET QSG NAME(*) MONITOR(YES) - 
    MGRNAME(*) USEPLEXNAME(YES)
```
The sysplex name is produced as the middle qualifier in the managed system name in the form qsg:sysplex:MQQSG.