The following examples illustrate different configurations for the RTCS system registry. The examples contain only the statements in the RTCS initialization member (OSZINIxx) that configure the sharing of the RTCS system registry. For an example of an entire RTCS initialization member, see RTCS-initialization-member.
Example: Separating production and test systems
The following statements would be used in OSZINIxx for the production systems to indicate that the production systems will:
- Communicate only with other production systems using XCF group RTCSPROD
- Share registry hilevel.PRODUCTION.REGISTRY
SREGVLDS=hilevel.PRODUCTION.REGISTRY
REGISTRY-XCF-GROUP=RTCSPROD
ELIGIBLE-OWNER
NOPRIVATE-REGISTRY
SHARED-REGISTRY
The following statements would be used in OSZINIxx for the test systems to indicate that the test systems will:
- Communicate only with other test systems using XCF group RTCSTEST
- Share registryhilevel.TEST.REGISTRY
SREGVLDS=hilevel.TEST.REGISTRY
REGISTRY-XCF-GROUP=RTCSTEST
ELIGIBLE-OWNER
NOPRIVATE-REGISTRY
SHARED-REGISTRY
Example: Adding an additional XCF group
The following statements would be used in OSZINIxx to define an additional XCF group that will:
- Communicate only with other systems using XCF group RTCSGRPn
- Share registry hilevel.GRPn.REGISTRY
SREGVLDS=hilevel.GRPn.REGISTRY
REGISTRY-XCF-GROUP=RTCSUSER
ELIGIBLE-OWNER
NOPRIVATE-REGISTRY
SHARED-REGISTRY
Exampe: Nonshared RTCS system registry
The following statements would be used in OSZINIxx to define an RTCS system registry that will:
- Co-exist with any other RTCS in a sysplex
- Communicate with no other RTCS
- Allocate and open but not expose, a product-specific registry unique to the image where this RTCS is started
SREGVLDS=hilevel.&SYSID..BMCMQ.REGISTRY
ELIGIBLE-OWNER
PRIVATE-REGISTRY
NOSHARED-REGISTRY