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), including variable resolution values. You must also enable and configure any features you want to exploit (such as support for self-describing agents).

About this task

The RTE profile inherits the symbolics specified on the KCIP@PG3 panel. However, you must replace all instances of the actual RTE name in the RTE profile with a symbolic (for example, &SYSNAME.), except for the RTE_NAMESV parameter instance. You can assign symbolics to additional parameters, but see Parameters ineligible to use variables for parameters that must be excluded from use of symbolics. You must also edit the variables profile to set the resolution value of the symbolic assigned to the RTE name.

If you assign symbolics in either the RTE or the global configuration profile to parameters that are concatenated in or part of started task procedures, you must follow the MVS rules governing the use of symbolics in started task procedures and JCL. In the RTE profile, these are the following parameters:
  • RTE_NAME
  • RTE_HILEV
  • RTE_VSAM_HILEV
  • RTE_X_HILEV_SHARING
  • RTE_SHARE
  • Kpp_*_VTAM_APPL_*
In the global profiles, these are the following parameters:
  • GBL_DSN_DB2_*
  • GBL_DSN_IMS_*
  • GBL_DSN_CICS_CTG_DLL
  • GBL_DSN_WMQ_*
  • GBL_DSN_CSF_SCSFMOD0
  • GBL_DSN_TCP_SYSTCPD_TCPDATA

Procedure

  1. From the Workflow - Primary Option Menu, select 2 (Customize PARMGEN configuration profiles).

    The Customize PARMGEN Configuration Profile Members panel (KCIP@PG6) is displayed.

  2. Type DLAJOB in the command line and press Enter to review the composite KCIJPDLA job that auto-discovers the values to some parameters in the configuration profiles. Submit the job after you review the job settings.
    For more information about the KCIJPDLn jobs, see Preparing the configuration profiles by running the KCIJPDLn jobs, and PARMGEN z/OS DLA utility jobs and commands.
  3. Select 1 to edit the RTE profile.
    • Configure the components in this RTE to connect to a TEMS. Provide values to the following parameters to specify the communication protocols, ports, TEMS host, TEMS node, TEMS VTAM, and agent's local VTAM and logon information.
      • Kpp_AGT_COMM_PROTOCOLn: Specify the communication protocols in priority sequence, for example, IPPIPE, and SNA.
      • Kpp_TEMS_TCP_PIPE_PORT_NUM: Specify protocol port numbers for the agents to connect to TEMS.
      • Kpp_TEMS_LOCAL_CONNECT_FLAG: Because the primary TEMS that this agents connect to is configured on another RTE, or running on a non-z/OS platform, specify N to this parameter.
      • Kpp_TEMS_NAME_NODEID: Specify the node ID of the non-local primary TEMS that the agents connect to, for example, SYSA:CMS.
      • Kpp_TEMS_TCP_HOST: Specify the host of the TEMS that the agents connect to, for example, SYSA.
      • Kpp_AGT_TCP_HOST: Specify the agent local TCP/IP information.
      • Kpp_TEMS_VTAM_*: Specify the primary TEMS VTAM information.
      • Kpp_AGT_VTAM_*: Specify the agent's local VTAM information and APPLIDs.
    • If you want to use the self-describing agent (SDA) feature, set the resolution value for KDS_KMS_SDA to Y, and provide site-specific values for RTE_USS_RTEDIR.
    • If one or more of the following products are configured in this RTE, see Configure OMEGAMON monitoring agents and other components for the parameters that you must configure at a minimum.
      • OMEGAMON for Db2 on z/OS Performance Expert and Performance Monitor
      • OMEGAMON for IMS on z/OS
      • OMEGAMON for Networks
    • You can configure any monitoring server features that you want to enable (Configure a Tivoli Enterprise Monitoring Server).
  4. Select 2 to edit the $GBL$USR global profile.
    At a minimum, if you enabled SDA, you must provide a value to the GBL_HFS_JAVA_DIR1 parameter. You must also edit the value for load library parameter GBL_DSN_CSF_SCSFMOD0 and any of the product-specific parameters listed in Customizing the global configuration profile, as appropriate.
  5. Select 3 to edit the variables profile.
    Provide values for any user-defined variables that you add, any variables that whose values differ from the IBM-provided default resolution values, and any variables whose values cannot be automatically discovered from the system IPL PARMLIB data set. See Customizing the variables profile for more information on customizing variables.

What to do next

If you need to further customize the configuration using the override embed members, customize the embed files before you run the $PARSE job to create the RTE members and jobs. To edit the embed files, select option 4 on the Customize PARMGEN Configuration Profile Members panel. You can also edit the files by entering UTIL on the command line of any Workflow panel to access the Access PARMGEN Utilities panel, then selecting option 7. For more information on customizing embed files, see Customizing the override embed members.