Customizing the global configuration profile
After all the settings in the RTE configuration profile have been updated, the next step is to review and customize the global parameters that will be used by this runtime environment (RTE). This step is required if you have not cloned the $GBL$USR profile from another runtime environment.
About this task
The
following are the key parameters to check:
- Common system library values
- GBL_DSN_SYS1_PARMLIB
- GBL_DSN_SYS1_PROCLIB
- GBL_DSN_SYS1_SAXREXEC
- GBL_DSN_SYS1_VTAMLIB
- GBL_DSN_SYS1_VTAMLST
- Health check configuration valueThis library is used to set up the health check elements, if health checks are enabled:
This parameter specifies the name of a load library that is usable by the Health Checker started task HZSPROC for assembling and linking health check modules. This library can be in the HZSPROC STEPLIB or it can be a library in LNKLIST.GBL_DSN_HZSPROC_LOADLIB
- ICSF system libraryIf you are enabling password encryption (KAES256) across the enterprise, you must set the value for the ICSF system library:
GBL_DSN_CSF_SCSFMOD0
- z/OS®
UNIX System Services Java™ directoryIf any of the components that you are configuring within this RTE require Java support or if you are planning to enable the self-describing agent feature, a valid path to a Java installation on HFS or zFS must be specified. Note that /bin is automatically appended:
Also, if you are enabling the self-describing agent feature or any other function that uses z/OS, check the value of the CLIST/EXEC library name. This EXEC library is used during the creation of z/OS UNIX directories running on either the Hierarchical File System (HFS) or on the zSeries File System (zFS):GBL_HFS_JAVA_DIR1
GBL_DSN_SYS1_SBPXEXEC
If a monitoring server is using any of the IP.UDP-related
or IP.PIPE-related communication protocols for connection, but the
IP domain name resolution is not fully configured on the z/OS system, the SYSTCPD statement must be supported
by the monitoring server and all monitoring agents that report to
it. SYSTCPD explicitly identifies which data set to use to obtain
the parameters defined by TCPIP.DATA when no GLOBALTCPIPDATA statement
is configured. To support SYSTCPD, uncomment and set the following
parameter:
GBL_DSN_TCP_SYSTCPD_TCPDATA
The
name of the SYSTCPD data set is installation-specific. Get the correct
specification from your network administrator. At a minimum,
customize the following parameters for the specific products.
- If OMEGAMON® XE for Db2® on z/OS Performance Monitor or Performance Expert
is configured in the RTE:
- Uncomment and customize the following parameters as applicable
to your Db2 environment:
- *GBL_DSN_DB2_SDSNLOAD
- *GBL_DSN_DB2_LOADLIB_V8
- *GBL_DSN_DB2_LOADLIB_V9
- *GBL_DSN_DB2_LOADLIB_V10
- *GBL_DSN_DB2_LOADLIB_V11
- *GBL_DSN_DB2_LOADLIB_V12
- *GBL_DSN_DB2_RUNLIB_V8
- *GBL_DSN_DB2_RUNLIB_V9
- *GBL_DSN_DB2_RUNLIB_V10
- *GBL_DSN_DB2_RUNLIB_V11
- *GBL_DSN_DB2_RUNLIB_V12
- *GBL_DSN_DB2_DSNEXIT
- Uncomment and customize the following parameters as applicable
to your Db2 environment:
- If OMEGAMON for CICS® TG is configured, uncomment and customize the following parameter:
- *GBL_DSN_CICS_CTG_DLL
- If OMEGAMON for IMS on z/OS is configured, uncomment and customize the
following parameter:
- *GBL_DSN_IMS_RESLIB
- If OMEGAMON for Messaging on z/OS is configured, uncomment and customize the following parameters:
- *GBL_DSN_WMQ_SCSQANLE
- *GBL_DSN_WMQ_SCSQAUTH
- *GBL_DSN_WMQ_SCSQLOAD