Customizing the configuration profiles
The configuration profiles have been tailored with the values you provided in the previous step. They also contain default values for all required parameters and some optional parameters. The amount of additional customization required depends upon how you are creating the runtime environment (RTE) and how much your environment differs from the model or product-provided defaults. At a minimum, you must supply site-specific values (such as any subsystems you want to monitor, protocols other than the IPPIPE and SNA defaults, and the like). You must also enable and configure any features you want to exploit (such as event forwarding or support for self-describing agents). In this scenario, you must also edit the variables configuration profile %GBL_USER_JCL%.(%RTE_NAME%) to specify resolution values for any user-defined variables.
About this task
In the global profile, you can assign symbolics to any of the parameters. At a minimum, you must assign a symbolic value to the GBL_HFS_JAVA_DIR1 parameter, for example, &GBL_HFS_JAVA_DIR1. or change the literal default to a site-appropriate one. You must also edit the value for load library parameters GBL_DSN_CSF_SCSFMOD0 and any of the product-specific parameters listed in Customizing the global configuration profile, as appropriate.
- RTE_NAME
- RTE_HILEV
- RTE_VSAM_HILEV
- RTE_X_HILEV_SHARING
- RTE_SHARE
- Kpp_*_VTAM_APPL_*
- GBL_DSN_DB2_*
- GBL_DSN_IMS_*
- GBL_DSN_CICS_CTG_DLL
- GBL_DSN_WMQ_*
- GBL_DSN_CSF_SCSFMOD0
- GBL_DSN_TCP_SYSTCPD_TCPDATA
- RTE_USS_RTEDIR
- GBL_HFS_JAVA_DIR1