Sparse parameter tables: The first row sets the default values for subsequent rows

For parameters that are arranged in tables, IBM Z® Monitoring Configuration Manager uses the first row to set the defaults for subsequent rows.

You can use this behavior to specify sparse parameter tables. You only need to specify parameters whose values differ from the first row. Sparse parameter tables are especially useful for configuring the Db2® monitoring agent.

As with PARMGEN, you can also specify complete parameter tables: every parameter in every row.

Example: Db2 profile configuration

The following example shows a sparse parameter table that configures three Db2 profiles (PROD, TEST, and DEV):

KD2_PF                     BEGIN 
                                             
KD2_PF01_ROW               01 
KD2_PF01_PROFID            "PROD"
* Configure and autostart Near-Term History (NTH)
KD2_PF01_HIS_START         Y
* Store NTH data to VSAM data sets for e3270UI thread history
KD2_PF01_HIS_STORE         THVSAM
KD2_PF01_THRDHIS_LOG_NUM   10
* Storage units
KD2_PF01_HIS_VSAM_SU       CYLS
KD2_PF01_HIS_VSAM_MB       50
 
KD2_PF02_ROW               02 
KD2_PF02_PROFID            "TEST"
* TEST requires fewer resources for NTH than PROD
KD2_PF02_THRDHIS_LOG_NUM   3
KD2_PF02_HIS_VSAM_MB       10 

KD2_PF03_ROW               03
KD2_PF03_PROFID            "DEV"
* No NTH in DEV
KD2_PF03_HIS_START         N
 
KD2_PF                     END

The first row configures the PROD profile and sets the default values for subsequent rows (profiles).

The TEST profile omits the following parameters, falling back to the values from the first row:

  • KD2_PFnn_HIS_START
  • KD2_PFnn_HIS_STORE
  • KD2_PFnn_HIS_VSAM_SU

The TEST profile sets different, lower values than PROD for the following parameters, because TEST requires fewer resources for Near-Term History:

  • KD2_PF02_THRDHIS_LOG_NUM
  • KD2_PF02_HIS_VSAM_MB

The DEV profile does not configure Near-Term History.

Example: Db2 subsystem configuration

The following example shows a sparse parameter table that configures the Db2 monitoring agent to monitor three Db2 subsystems (DB2P, DB2T, and DB2D):

KD2_DB                     BEGIN
                                                    
KD2_DB01_ROW               01 
KD2_DB01_DB2_SSID          "DB2P"
KD2_DB01_DB2_DESCRIPTION   "PROD Db2 subsystem" 
KD2_DB01_DB2_PROFID        "PROD"
KD2_DB01_DB2_VER           "12" 
KD2_DB01_DB2_SYSNAME       "ZOSP" 
KD2_DB01_DB2_DS_GROUP      "N" 
KD2_DB01_DB2_MONITOR_START "Y" 
KD2_DB01_DB2_PORT_NUM      "2000" * OMEGAMON Db2 PE Server TCP/IP port number
KD2_DB01_DB2_DSNTIAD       "DSNTIAD" 

KD2_DB02_ROW               02
KD2_DB02_DB2_SSID          "DB2T"
KD2_DB02_DB2_DESCRIPTION   "TEST Db2 subsystem" 
KD2_DB02_DB2_PROFID        "TEST"
KD2_DB02_DB2_SYSNAME       "ZOST" 
KD2_DB02_DB2_PORT_NUM      "2001" 

KD2_DB03_ROW               03 
KD2_DB03_DB2_SSID          "DB2D"
KD2_DB03_DB2_DESCRIPTION   "DEVT Db2 subsystem" 
KD2_DB03_DB2_PROFID        "DEVT"
KD2_DB03_DB2_SYSNAME       "ZOSD" 
KD2_DB03_DB2_PORT_NUM      "2002" 
KD2_DB03_DB2_LOADLIB       "DSN.VC10.SDSNLOAD"
KD2_DB03_DB2_RUNLIB        "DSN.VC10.RUNLIB.LOAD"

KD2_DB                     END

The first row configures the agent to monitor the DB2P subsystem and sets the default values for subsequent rows (subsystems).

The second row falls back to the values set by the first row for Db2 version, LOADLIB, and RUNLIB, but sets its own values for the profile, system (LPAR) name, and port number.

The third row specifies its own values for LOADLIB and RUNLIB.