Completing the runtime environment configuration

Edit online

Depending on your user privileges, you might need to ask someone else to perform some or all of the following steps. For example, only z/OS® system administrators are typically allowed to write to system libraries.

About this task

These complete the configuration steps depend on your site-specific procedures and the requirements of the components, such as the monitoring agents, that you have chosen to configure in the runtime environment. The requirements of each component are described in the separate product documentation for each component.

Typically, at this point in the procedure for creating a runtime environment, you would need to refer to that separate documentation. However, to help make this first runtime environment procedure stand-alone, and because in this procedure we have selected a fixed set of specific components, the complete the configuration steps are presented here.

Procedure

Use your site-specific procedures to copy the runtime members for started tasks and VTAM® definitions to your system libraries.
Copy the members from the following libraries to your corresponding PROCLIB, VTAMLIB, and VTAMLST system libraries:
- rte_hilev.SYS1.PROCLIB
- rte_hilev.SYS1.VTAMLIB
- rte_hilev.SYS1.VTAMLST
The default value of the RTE_HILEV parameter is the value of RTE_PLIB_HILEV.
If you followed the earlier tip to set the RTE_X_STC_INAPF_INCLUDE_FLAG parameter to Y, then you can skip this step. However, you should still read this information to understand the requirements of the runtime environment for VTAM resources and APF-authorized libraries.
1. Activate the VTAM resources defined by this runtime environment.
  Issue the following VARY ACT MVS™ system command:
```
VARY NET,ACT,ID=rte_vtam_applid_prefixNODE,SCOPE=ALL
```
  The ID parameter of the VARY ACT command must match the value of the runtime environment parameter RTE_VTAM_GBL_MAJOR_NODE.
  
  The default value of RTE_VTAM_GBL_MAJOR_NODE is the value of RTE_VTAM_APPLID_PREFIX followed by the string NODE. If you use the RTE_VTAM_APPLID_PREFIX initial value of OMxx, then the default value of RTE_VTAM_GBL_MAJOR_NODE is OMxxNODE, where xx is the value of the z/OS static system symbol SYSCLONE. For example, if the system (LPAR) name is ZOS1, then specify ID=OMS1NODE.
2. APF-authorize libraries.
  Add the following data sets to the authorized program facility (APF) list:
  - The following runtime environment library:
    - rte_hilev.rte_name.RKANMODU
  - The following target libraries, under the high-level qualifiers of the STEPLIB of the Configuration Manager job:
    - TKANMOD
    - TKANMODL
    - TKANMODP
    - TKANMODR
  The runtime member rte_hilev.SYS1.PROCLIB(rte_stc_prefixAPF) contains VARY ACT and SETPROG APF commands for this runtime environment. Different runtime environments require different VTAM resources and APF-authorized libraries, depending on the configured products.
  
  If you specify the parameter RTE_X_STC_INAPF_INCLUDE_FLAG Y in the RTEDEF(rte_name) member, and then perform the GENERATE action, some started tasks will contain an INCLUDE statement to include that member, so that you do not need to issue these commands separately. Whether started tasks are allowed to perform such commands depends on your local site practices.
  
  Setting RTE_X_STC_INAPF_INCLUDE_FLAG can be expedient for initial testing. However, typical best practice is to activate VTAM resources and APF-authorize libraries during system initialization rather than each time you start a task. Use the generated SYS1.PROCLIB(rte_stc_prefixAPF) member to identify which libraries you need to add to the APF list at system initialization.
Authorize the monitoring programs.
1. Authorize the product started tasks:
  1. Update RACF® or equivalent security system for the user ID (with OMVS segment) you will use for these started tasks:
    - Hub and remote monitoring servers (the default started task is named OMEGDS)
    - Enhanced 3270 user interface (the default started task is named OMEGTOM)
    - OMEGAMON AI for JVM (the default started task is OMEGJJ)
  2. Identify the user ID you created as a Superuser:
```
ALU <user ID> OMVS(UID(0) HOME(/) PROGRAM(/bin/sh))
```
  3. Use the RDEFINE commands to associate the ID with the following started tasks:
    - OMEGDS (the started task of the monitoring server)
    - OMEGTOM (the started task of the enhanced 3270 user interface)
    - OMEGJJ (the started task of the OMEGAMON AI for JVM agent)
    - OMEGJT (the started task of the OMEGAMON AI for JVM collector)
```
*/associate the user ID with started tasks
RDEFINE STARTED IBMDS.* STDATA(USER(userID) GROUP(SYS1)) 
RDEFINE STARTED IBMTOM.* STDATA(USER(userID) GROUP(SYS1))
RDEFINE STARTED IBMJJ.* STDATA(USER(userID) GROUP(SYS1))
RDEFINE STARTED IBMJT.* STDATA(USER(userID) GROUP(SYS1))
```
  4. After you issue all the RDEFINE commands, issue the refresh command:
```
SETROPTS RACLIST(STARTED) REFRESH
```
Update IKJTSOnn with the names of authorized monitoring programs.
You might request your site's authorized system programmers to perform this step so it can be scheduled with the LPAR's change control processes.
- Add programs KPDDSCO, KOBROUTR, and KOBSPFAU to the system PARMLIB member IKJTSOnn under the AUTHPGM section.
- Refresh the IKJTSOnn member by issuing the set command (T IKJTSO=nn).
Start at least the following tasks: rte_stc_prefixCN, rte_stc_prefixDS, rte_stc_prefixTOM, rte_stc_prefixJJ, and rte_stc_prefixJT.
The user ID that you associate with these started tasks must have z/OS UNIX superuser privileges and access to the runtime member.
rte_stc_prefixCN
OMEGAMON® subsystem.
The OMEGAMON subsystem does not belong to a runtime environment. You only need one OMEGAMON subsystem per LPAR.
If the OMEGAMON subsystem has already been started, the job for this started task will fail. The JESMSGLG output data set for the failed job will contain the following messages:
```
CNDL018I  OMEGAMON SUBSYSTEM ALREADY ACTIVE ... 
CNDL002I  OMEGAMON SUBSYSTEM Vvrm TERMINATED ...
```
This is not a problem: your runtime environment will use the already-active subsystem.
rte_stc_prefixDS

Monitoring server.

rte_stc_prefixTOM

Enhanced 3270 user interface.

rte_stc_prefixJJ

The default OMEGAMON AI for JVM monitoring agent name is OMEGJJ. OMEGAMON AI for JVM started task names are specified in the RTEDEF(KJJ$PARM) member or the LPAR-specific RTEDEF(KJJ$lpar) member.

rte_stc_prefixJT

The default OMEGAMON AI for JVM collector name is OMEGJT. OMEGAMON AI for JVM started task names are specified in the RTEDEF(KJJ$PARM) member or the LPAR-specific RTEDEF(KJJ$lpar) member.

What to do next

Complete the post-configuration steps for OMEGAMON AI for JVM: Completing the configuration for the OMEGAMON AI for JVM agent.