End of supportThis version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.BMC recommends upgrading to the latest version of the product. To see documentation for that version, seeBMC Discovery for z/OS 1.8.

Specify RTCS initialization parameters

This step describes how to update or create the following z/OS Logical PARMLIB members for RTCS:

  • Authorized program facility list
  • Program properties table
  • Subsystem name table
  • RTCS initialization member

Authorized Program Facility (APF) list

Add the RTCS subsystem program library and RTCS product program library to the APF list by using one of the following methods:

  • To temporarily authorize these libraries if they are not SMS-managed, issue the following command for each library:

    SETPROG APF,ADD,LIBRARY=dsnPrefix.library,VOLUME=volser

  • To temporarily authorize these libraries if they are SMS-managed, issue the following command for each library:

    SETPROG APF,ADD,LIBRARY=dsnPrefix.library,SMS

  • To permanently authorize these libraries:
    • Add their DSNAMEs to the appropriate PROGxx member of SYS1.PARMLIB (or the appropriate system image-specific Logical PARMLIB data set)
    • IPL the system image or issue the SET PROG=xx operator command, which rebuilds the list of authorized data sets in storage

Program properties table (PPT) —TOSZCNTL member OSZSCHED

Use member OSZSCHED to add RTCS programs to the PPT. 

The RTCS Initiator, the RTCS subsystem, and the RTCS Generalized Server generally need to be executed in a started task address space with certain system-assigned special attributes. Definitions for the job step program used in these PROCs in the PPT cause the required attributes to be assigned. 

Before RTCS can be started, the PPT must be updated by using one of the following methods:

  • Update an existing SCHEDxx member:
    1. Merge the contents of member OSZSCHED into an existing SCHEDxx member.
    2. Refresh the PPT by issuing the following operator command:SET SCH=(xx)
  • Create a new SCHEDyy member:
    1. Copy the OSZSCHED member into SYS1.PARMLIB or a logical parameter library data set, and name it SCHEDyy.
    2. Update the appropriate IEASYSn n member to specify this new SCHEDyy member and any existing SCH members.

    3. Refresh the PPT by issuing the following operator command: SET SCH=(xx,yy)The variable xx is the suffix of any existing SCH member (named SCHEDyy).

      Note

      The contents of all SCH member suffixes in a SET command replace any existing entries in storage. Therefore, any existing PPT member suffixes must be included in the list in addition to any new suffixes that you add.

Subsystem name (SSN) table

To guarantee the availability of a subsystem ID (SSID) for exclusive use by the RTCS subsystem control address space, update the subsystem name (SSN) table.

To update the SSN table

  1. Select an available, four-character SSID for use by the RTCS subsystem.

    The selected SSID becomes the CSCB name of the RTCS subsystem address space, which means that it will be specified after the RTCS subsystem address space PROC name in the START command that is generated by the RTCS Initiator.

    The name must:

      • Be valid in a START command and in JCL
      • Be exactly four characters in length
      • Be valid as a CSCB name

      • Begin with an alphabetic character and contain only alphabetic and numeric characters

        Note

        BMC recommends the you use RTCS for the SSID.

  2. Add the SSID to the IEFSSNxx member in SYS1.PARMLIB (or a Logical PARMLIB data set that is currently in effect for the z/OS system image).

    For example, to add an entry with the SSID of RTCS, add the following statement to the IEFSSNxx member in SYS1.PARMLIB:

    Example

    SUBSYS SUBNAME(RTCS)

  3. To update the subsystem name table, IPL the system image or issue the SETSSI ADD,SUBNAME=RTCS operator command.
  4. If you have an SSID other than RTCS, specify its value in the SSID parameter in the RTCS initialization member from the Logical PARMLIB data set that is used by the RTCS Initiator started task procedure, as described by "RTCS Initiator—TOSZCNTL member OSZ$INIT" in Add RTCS entries. The default SSID that RTCS selects if no value is specified is RTCS. If that SSID is acceptable, no modification of the default RTCS initialization member of Logical PARMLIB is required.

RTCS initialization member —TOSZCNTL member OSZ$PARM

The RTCS Initiator started task reads the RTCS initialization parameters from a member of the z/OS system image Logical PARMLIB. The default member name is OSZINI00. You can use a different member name or a name with a different suffix, but you must indicate that name explicitly in the START command for the RTCS Initiator address space.

To create a new OSZINInn member

  1. Copy the OSZ$PARM member into SYS1.PARMLIB or the appropriate system image Logical PARMLIB data set, and name it OSZINInn.

  2. Update the new OSZINInn member according to your specific z/OS and sysplex requirements. Normally, the default parameter specifications that are provided in the sample member OSZ$PARM are sufficient. However, pay attention to the following RTCS initialization parameters to ensure that RTCS uses the proper values:

    • OSZRTCS-PROC= OSZRTCS

    • OSZEXEC-PROC= SZEXEC

    • POSZLINK= RTCSProductProgramLibraryDSNAME

    • POSZHTML= RTCSHypertextDocumentLibraryDSNAME

    • POSZPSWD= RTCSProductAuthorizationTableLibraryDSNAME

    • SREGVLDS= RTCSSystemRegistryVLDSClusterDSNAME

    • SHARED-REGISTRY or PRIVATE-REGISTRY

    • REGISTRY-XCF-GROUP= OSZRTCSR

    All of the production library and registry VLDS DSNAMEs default to the DSNAME prefix of the OSZINIT PROC STEPLIB DD statement-specified RTCS subsystem program library DSNAME plus their individual recommended low-level index. 

    Consequently, if the RTCS subsystem program library DSNAME low-level index is POSZRTCS or OSZRTCS and all of the other data sets are allocated with their recommended low-level index, none of these DSNAMEs will need to be explicitly specified in the RTCS initialization member. Because the DSNAME of the RTCS subsystem program library is specified only in the STEPLIB DD statement of the RTCS Initiator address space PROC (by default, member name OSZINIT), if the BMC low-level DSNAME index recommendations are followed, no specific RTCS production library or registry DSNAME parameters, such as the ones above, need be specified in the RTCS initialization member. In most instances, this means that the default RTCS initialization member can be used as is by most customers.

    If you use a Logical PARMLIB RTCS initialization member other than OSZINI00, be sure to indicate which one is to be used in the START command that is used to start the RTCS Initiator address space (in the second subsequent step).

Related topic

Mainframe-customization-steps-for-z-OS

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*