The setting for the SYSVIEW for DB2 in multiple DB2 versions

book

Article ID: 132466

calendar_today

Updated On:

Products

CA Bind Analyzer for DB2 for z/OS CA SQL-Ease for DB2 for z/OS CA Sysview Performance Management Option for DB2 for z/OS CA Plan Analyzer for DB2 for z/OS CA Subsystem Analyzer for DB2 for z/OS

Issue/Introduction

DB2 subsystems are being upgraded from V10 NFM to V11 CM. There are several DB2 subsystems in a system, and those DB2 subsystems will be upgraded to V11 CM and tested sequentially. So, both DB2 versions will exist in the same system for a while.

The SYSVIEW for DB2 R19.0/0000 is used in a system and several DB2 subsystems will be upgraded from V10 NFM to V11 CM sequentially in the system.  So, both DB2 versions will exist in the same system for a while.

Q1.
If the both DB2 versions exist in the same system, can both DB2 versions be monitored in the same SYSVIEW for DB2? If it is possible, how should it be done?  (How should the SYSVIEW for DB2 be set?)

Q2.
One Xmanager is needed per a z/OS system. If the both DB2 versions exist in the same system, which DB2 version load library should be specified to the STEPLIB DD of the Xmanager?

Q3.
If the same CDBAPRM library is used for all subsystems in a system, are there any considerations if both DB2 versions exist?
If both DB2 versions exist in a system, which DB2 version load library should be specified in the DSNAME00 member?
 

Environment

z/OS, Sysview for DB2, IDB2, R19.0, R20.0, 19.0, 20.0, DB2 V10, DB2 V11, V10, V11, V10 NFM, V11 CM

Resolution

A1.
To use the SYSVIEW for DB2 for multiple versions of DB2 (Multiple subsystem exist);

The both DB2 Subsystems, V10 NFM to V11 CM, have to been defined in Prefix.CDBAPARM(SETUPxx) member.
For V10 NFM:
SSIDVER (V10)
SSIDMODE (NFM)

For V11 CM:
SSIDVER (V11)
SSIDMODE (CM)

The Post-Install Tasks for both DB2 Subsystems have to be run and update Prefix.IDB2.SOURCE Library accordingly.
Specially for APPLS member and create the data sets for each DB2 Subsystem.

A2.
In the Xmanager, the DSNLOAD of the oldest DB2 version should be specified as it is described in the xmanager JCL.
This consideration is for Detector/Subsystem Analyzer, it is not for CA SYSVIEW for DB2.
CA SYSVIEW for DB2 only works with Xmanager if some of the interfaces to work with Xnet is installed, and even in this case it does not work with the DB2 DSNLOAD Library.

A3.
For the DB2 Libraries in the DSNAME00 member;
In the DSNAME00 member, hardcoded names for DB2 Libraries are not needed. *DB2LIBn variables can be specified instead.
See the following sample
EPLIB (Prefix.CDBALOAD
*DB2LIB1
*DB2LIB2
*DB2LIB3)

Values for *DB2LIBn variables will be replaced at run time depending on the DB2 Subsystem you are connected and they are  picked up from the DB2 Subsystem definition in SETUP00 member.