RTE_USS_RTEDIR
This parameter specifies the main Hierarchical File System/zSeries File System (HFS/zFS) directory name for the runtime environment, if a product to be configured in the runtime environment requires that z/OS® UNIX System Services directories be created.
- Required or optional
- Optional
- Location where the parameter value is stored
- The KDSENV member of the rhilev.midlev.rtename.RKANPARU
library
- Parameter name and syntax
TEMS_MANIFEST_PATH=#rtedir/LPARRTE/kds/support/TEMS
- Default value
/rtehome
- Permissible values
- See description.
- PARMGEN name
- RTE_USS_RTEDIR
- Description
- This parameter is conditional. If any products in this runtime environment require that z/OS
UNIX directories be created, specify the RTE HFS/zFS home directory (#rtedir).Note:
- Specify the main RTE HFS/zFS home directory name if you are enabling the Self-Describing Agent (SDA) function in the z/OS TEMS and Agents. SDA is applies to Tivoli Management Services V6.2.3 or later.
- Set up required authorizations and files for SDA.
- Create a user ID with superuser authority (a TSO ID with an OMVS segment defined to it) if you
do not already have one. Product configuration z/OS UNIX jobs (KCIJ%USP/KCIJ%USS) that use the
RTE_USS_RTEDIR home directory parameter must be run by a user ID that has superuser authority
(UID=0), or a user ID with read access to resource BPX.SUPERUSER under the FACILITY profile with
superuser authority activated. Both the user ID of the KCIJPUS* z/OS UNIX job submitter and the
%KDS_TEMS_STC% TEMS started task name must have superuser authority.
For more information about assigning superuser authority, see Superusers in z/OS UNIX.
- Choose an existing file system or create a new one for products that use the RTE_USS_RTEDIR home directory parameter. This file system must be created, mounted, and in read/write mode before the z/OS UNIX jobs that define the file system paths are submitted. Select a name for your RTE that establishes or fits a naming convention that can be used as you install additional RTEs.
- In the MOUNT FILESYSTEM command, the MOUNTPOINT() parameter equates to the value you specify for
the RTE_USS_RTEDIR. For example:
An example of this using RTE name TSTEST might beMOUNT FILESYSTEM('&hlq_rte_home') TYPE(ZFS) MODE(RDWR) MOUNTPOINT('/rtehome') PARM('AGGRGROW')
MOUNT FILESYSTEM('OMVS.TSTEST.ZFS') TYPE(ZFS) MODE(RDWR) MOUNTPOINT('/tstest') PARM('AGGRGROW')
- Create a user ID with superuser authority (a TSO ID with an OMVS segment defined to it) if you
do not already have one. Product configuration z/OS UNIX jobs (KCIJ%USP/KCIJ%USS) that use the
RTE_USS_RTEDIR home directory parameter must be run by a user ID that has superuser authority
(UID=0), or a user ID with read access to resource BPX.SUPERUSER under the FACILITY profile with
superuser authority activated. Both the user ID of the KCIJPUS* z/OS UNIX job submitter and the
%KDS_TEMS_STC% TEMS started task name must have superuser authority.
- The RTE_USS_RTEDIR value (#rtedir) is used in this TEMS parameter in the
xKANPARU library:
The TEMS_MANIFEST_PATH parameter is the name of the z/OS UNIX home directory where agent-uploaded jar files and other application support files will be stored by the TEMS. The #rtedir value is also used in the KDS* members in RKANDATV. These members contain the commands that create the z/OS UNIX directories and send files to the z/OS UNIX subdirectories.TEMS_MANIFEST_PATH=\ #rtedir/%RTE_NAME%/kds/support/TEMS
- Customize RTE_USS_MKDIR_MODE parameter if you must secure access mode to be used in the PARMGEN composite z/OS UNIX-related jobs (KCIJPUSP/KCIJPUSS). The default is "755" which generates "MODE(7,5,5)" in the mkdir commands to create the new TEMS SDA directories. PARMGEN KCIJPUSP z/OS UNIX preparation job creates the RTE RKANDATV(KDSRMKDB) TEMS Self-Describing Agent (SDA) member that contains the SDA z/OS UNIX RTEDIR mkdir commands. MODE() is customized to site's security audit requirements based on the value supplied in the RTE_USS_MKDIR_MODE parameter. The RTE_USS_MKDIR_MODE parameter is used only to creating new z/OS UNIX directories. If the z/OS UNIX directories already exist and you want a different access mode for the directories and files, use the CHMOD command or delete the old directories before regenerating and rerunning the KCIJPUSS/KCIJPUSP jobs. For additional security considerations, see "Checklist: Prepare the system" on-line README topic on the "Welcome to the z/OS Installation and Configuration Tools for IBM Tivoli Management Services (TMS) dependent products" KCIP@PGW panel.
- Related parameters
- GBL_HFS_JAVA_DIRn (typically in WCONFIG($GBL$USR))
- GBL_DSN_SYS1_SBPXEXEC (typically in WCONFIG($GBL$USR))
- GBL_USS_TKANJAR_PATH (for products that deliver TKANJAR)
- RTE_USS_MKDIR_MODE
- KDS_KMS_SDA
- KDS_KMS_SDA_NO_GRANULAR (applicable to ITM6.3.0 or later)
- KDS_TEMA_SDA
- Kpp_AGT_TEMA_SDA (per Kpp Agent exploiting SDA)