Controlling sharing of the RTCS system registry

Controlling whether a new RTCS system registry is shared

If you are installing RTCS for the first time, use this procedure to control sharing of the RTCS system registry.

1. Review the CHKZMC1 step from the $310VZMC job and the OSZINInn member in your JCL data set (where nn is your SYSCLONE value). The $INCINF member in the JCL data set contains the values used for the symbolics in the job.

   The CHKZMC1 step creates the RTCS system registry; this data set name is referenced on the SREGVLDS parameter in the OSZINInn member that RTCS uses at startup.

2. Take the appropriate action based on whether you want to share the RTCS system registry:

   • If you want to share the registry across some or all LPARs in a sysplex, ensure that OZIINInn contains:

     • An SREGVLDS parameter that references the same system registry data set for those RTCS instances

     • The NOPRIVATE-REGISTRY and SHARED-REGISTRY parameters

     • The same REGISTRY-XCF-GROUP value for those RTCS instances to allow communication

   • If you do not want to share the registry, ensure that OZIINInn contains:

     • An SREGVLDS parameter that refers to a unique data set

     • The PRIVATE-REGISTRY and NOSHARED-REGISTRY parameters

     • No REGISTRY-XCF-GROUP value

Determining whether an existing RTCS system registry is shared

1. Issue the following console command:

    RO *ALL,F RTCS,REGISTRY STATUS

2. Look for message OSZ0240I in the output.

   • If the message shows the same data set name from each LPAR, the registry is shared.

   • If the data set names differ, the registry is not shared.

3. (If generated) Run steps LGCDFLT and LGCRGRP from the $463LGCD job as follows, based on whether the registry is shared:

   • If the registry is shared, run the steps from any LPAR in the sysplex to register all DBC groups.

   • If the registry is not shared, run the steps on each LPAR where the DBC has a member.