CA Global SubSystem Configuration › Customize CA-GSS › Customize CA-GSS for CA Insight Database Performance Monitor for DB2 for z/OS

Customize CA-GSS for CA Insight Database Performance Monitor for DB2 for z/OS

CA Insight Database Performance Monitor for DB2 for z/OS uses CA‑GSS for various logging, access, and auditing capabilities. REXX‑based IMODs are used for all CA Insight Database Performance Monitor for DB2 for z/OS functions that access CA‑GSS.

Look at your CA Insight Database Performance Monitor for DB2 for z/OS documentation to determine whether this product supplies IMOD libraries (ISETs). If ISETs are supplied, you need to load them into DASD.

You can use the CA‑GSSIMOD member of CA Insight Database Performance Monitor for DB2 for z/OS libraries to load ISETs. Before you submit the JCL in this member, make sure the unit and volser number match those on your CA Insight Database Performance Monitor for DB2 for z/OS tape.

To customize CA Insight Database Performance Monitor for DB2 for z/OS

1. Allocate ILOGs.

   ILOGs are VSAM linear data sets that CA‑GSS uses to record information about a subsystem. Each ILOG is composed of two subfiles (data sets)-one primary, and one backup that is used when the primary becomes full.

   For each DB2 subsystem that CA‑GSS will be monitoring, you need to allocate two data sets. To do this, modify and submit an SRVMAINT job that contains one or more ALLOC_ILOG commands. Each ALLOC_ILOG statement allocates a pair of VSAM linear data sets. Another way of allocating these data sets is to modify and submit the BYSIALI member of the CAW0JCL data set.

   Make these changes for your allocation job:

   • Provide the volser of the DASD volume on which the ILOG files should reside.
   • Make sure there is one DEFINE step for each of your DB2 subsystems.
   • Provide data set names. You may choose to use the naming convention LOGnn#0 for primary subfiles and LOGnn#1 for backup subfiles, where nn represents a DB2 subsystem. For example, here are the files for a set of three DB2 subsystems:

• If you are using the BYSIALI method, do not change the values for either the LINEAR or SHAREOPTIONS parameters.

1. Identify ILOGs to CA Insight Database Performance Monitor for DB2 for z/OS.

   Identify your ILOG data sets to CA‑GSS through the INSIGHT member of the CAW0OPTN data set.

   Each ILOG statement identifies one ILOG file and one subfile. An ILOG statement contains this information:

   • A unique ILOG number that is not being used by any other application
   • The dsname of a data set that you allocated for ILOG use
   • The subfile for the ILOG
2. Modify your GSSA system PROCLIB member by adding the following DD statement:

   //DB2SSID DD DSN=CAI.CAW0OPTN(DB2SSID),DISP=SHR
   

   This DD statement points to the DB2SSID member of the CAW0OPTN data set.

   CA‑GSS reads the DB2SSID member at initialization time to determine what DB2 address spaces it should monitor and which ILOGs it should use to record information about those address spaces.

3. Identify DB2 subsystems to CA‑GSS.

   In the DB2SSID member referenced in your GSSA system CA‑GSS PROCLIB member, you need to define an ILOG statement for each DB2 subsystem that CA‑GSS will be monitoring.

   The ILOG numbers in this member must match the ILOG numbers in the INSIGHT member of the CAW0OPTN data set (which was discussed in step 2).

4. Modify CA‑GSS parameters.

   As needed, modify the CA‑GSS initialization parameters that affect the CA‑GSS support. Examples of these parameters are contained in the DBDEL member of the CAW0OPTN data set.

   The following parameters may need to be modified:

   • COMMAND-Defines the INSIGHT console command to CA‑GSS.

     CA Insight Database Performance Monitor for DB2 for z/OS distributes a set of IMODs with a name prefix of $DBGL_. These IMODs process operator console commands to provide additional functions to the operator.

     ILOG-Defines an ILOG file. Specify this parameter once for each ILOG that you have defined.

   • ISET-Identifies an ISET (IMOD Library) that is included on the distribution tape of CA Insight Database Performance Monitor for DB2 for z/OS.
   • PRODUCT-Activates the CA‑GSS support for CA Insight Database Performance Monitor for DB2 for z/OS.
   • This parameter does not conflict with other specifications of the PRODUCT parameters.
   • WTO-Executes a particular IMOD whenever a WTO that you identify is issued.
   • Use the WTO parameter to execute the IDB2_IDB2309E IMOD in response to the IDB2309 message (which indicates the FLASHBACK file needs to be backed up).

   You will need to modify the IMOD to meet the requirement of your installation.

5. Provide an IMOD for logging.

   When you are logging large volumes of data, you need to provide a $USER_ILOG_FULL IMOD so that CA‑GSS can automatically switch or reset ILOGs that become full.

   Note: For more information about this special‑purpose IMOD, see the Reference Guide.

6. Activate GoalNet.

   If you are using CA Insight Database Performance Monitor for DB2 for z/OS and you are operating in a multi‑CPU environment, with or without shared DASD, you may want to activate GoalNet so that CA Insight Database Performance Monitor for DB2 for z/OS can gather information from multiple systems and can consolidate displays.

   In order to use the CA Insight Database Performance Monitor for DB2 for z/OS System Condition Monitor on external systems, you must install CA‑GSS on all CPUs. CA Insight Database Performance Monitor for DB2 for z/OS is required on the systems where information is to be displayed.