Xmanager STC PROC - optional parms - GROUP parameter usage
search cancel

Xmanager STC PROC - optional parms - GROUP parameter usage

book

Article ID: 203835

calendar_today

Updated On:

Products

Database Management for DB2 for z/OS - Performance Suite Database Management for DB2 for z/OS - SQL Performance Suite Database Management for DB2 for z/OS - Recovery Suite Database Management for DB2 for z/OS - Utilities Suite DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS

Issue/Introduction

One of our regions use the GROUP option on the Xmanager proc, for example:
OPT='GROUP(group)' where group is the Db2 Data Sharing Group Attach name.

Apparently this was done in the past during the initial install but cannot obtain any more details on why this was done.  

 
Would like to understand why this was recommended.
 
Can see that the Xmanager references this group:
PXM4710 XMANAGER PLEXCNTL GRP=group     MEM=XMANnnnnlpar

Resolution

Detector, Subsystem Analyzer, and Thread Termination/Dynamic DSNZPARM support remote DB2 subsystems, i.e. DB2 subsystems running on other LPARs,
by utilizing Sysplex services support built into Xmanager. In order for Xmanagers running on different LPARs to communicate with each other via Sysplex
services, the Xmanagers must be in the same Sysplex services group. The Xmanager GROUP parameter is used to specify the Sysplex services group
explicitly and thereby limit which Xmanagers can communicate with each other across LPARs.

There is no need for the name specified via the Xmanager GROUP parameter to match a DB2 data sharing group attach name;
the Xmanager GROUP parameter has nothing to do with DB2 data sharing groups.
 
The Xmanager GROUP parameter is optional because when one is not specified, a default Sysplex services group is used. However, in some cases,
preventing certain Xmanagers from communicating with each other may be desirable.

Additional Information

More information related to the Xmanager GROUP parameter can be located here:
Prepare the Xmanager Started Task Procedure