Controlling sharing of the RTCS Subsystem SYSTEM Registry

You must have an RTCS started task on each LPAR where a product or component is being executed.  You can share the RTCS Subsystem SYSTEM Registry among all or some of the LPARs in a sysplex. Products that require the LGC or NGL agents, run on the DBC subsystem and require an RTCS started task on each LPAR where the DBC subsystem resides.

You can control the sharing of the RTCS Subsystem SYSTEM Registry during the installation of RTCS.

Related topic

Modifying-infrastructure-components

To control sharing of the new RTCS Subsystem SYSTEM Registry

If you are installing RTCS for the first time, perform the following steps to control sharing of the RTCS Subsystem SYSTEM Registry:

Important

BMC products work with both a SHARED and non-SHARED RTCS Subsystem SYSTEM Registry. However, we recommend using a SHARED RTCS Subsystem SYSTEM Registry. For more information, see Avoiding-ZDBCssid.

  1. Complete the following tasks:

    1. Run the $310VZMC job while configuring your product that you want to install for generating the configuration JCL.

      The CHKZMC1 step creates the backing VLDS for the RTCS Subsystem SYSTEM Registry. The SREGVLDS parameter in the OSZINInn member of logical PARMLIB specifies the VSAM data set CLUSTER name. 

    2. In the UBMCPARM data set, in the OSZINIT member, review the startup INI parameter.

      Important

      The OSZINI member uses the INI parameter value as a suffix.

      For example, the Installation System generates an OSZINInn member where nn is the SYSCLONE value. The generated parameter in OSZINIT member is INI and INI paramter value is &SYSCLONE.

  2. Perform one of the following actions:
    • If you want to share the RTCS Subsystem SYSTEM Registry across some or all LPARs in a sysplex, make sure that:
      1. The MEMBER instances executing in LPARs are members of the same Sysplex.
      2. The VSAM CLUSTER name of the backing VLDS specified for the SREGVLDS parameter in OSZINInn for each MEMBER is identical. 
      3. Each MEMBER instance is sharing the registry using XCF. Also, make sure that the registry is in SHARED status.

      4. Each MEMBER instance is sharing the registry using the same XCF GROUP Name.  

        You can specify the same value for REGISTRY-XCF-GROUP in OSZINInn for each MEMBER instance.

    • If you do not want to share theRTCS Subsystem SYSTEM Registry, make sure that the REGISTRY-XCF-GROUP parameter value in the RTCS Initialization Member is set to blank as shown in the following:

      REGISTRY-XCF-GROUP=' '

Important

For more information, see Administering-Runtime-Component-System-RTCS.

To check whether the existing RTCS Subsystem SYSTEM Registry is shared

  1. Issue the following console command:

    RO *ALL,F RTCS,REGISTRY STATUS

  2. Search for the OSZ0240I message in the output. 

    If the DSN value between two LPARs is same and those LPARs have shared DASD, then the RTCS Subsystem SYSTEM Registry is shared; otherwise, RTCS Subsystem SYSTEM Registry is not shared.

    The following is a sample output:

    RO *ALL,F RTCS,REGISTRY STATUS                                         
    IEE421I RO *ALL,F RTCS,REGISTRY 823   
    SJSC     RESPONSES ---------------------------------------------------     
    OSZ0232I REGISTRY STATUS                                                   
    OSZ0233I REMOTE, SHARED, VLDS-BACKED                                       
    OSZ0235I SCOPE=ALL                                                         
    OSZ0236I SYSTEM, SECURED, HRECALL                                          
    OSZ0237I *READY*, OWNERUP, LOAVAIL                                         
    OSZ0238I DIV-SAVE-MIN  =           5, DIV-SAVE-MAXIMUM =          30       
    OSZ0239I DIV-SAVE-IDLE =         900, DIV-SAVE-LIMIT   =         500       
    OSZ0257I APPROXIMATELY  2,147,483,648 BYTES ALLOCATED,   0% FORMATTED      
    OSZ0240I DSN=SYSO.RTCS$.SHARED.REGISTRY                   SER=             
    OSZ0242I XCF MBR=RTCS003FSJSC     GROUP=OSZSJSCD OWNER=RTCS0045SJSD        
    OSZ0243I MEMBER            SYSID     JOB NAME                              
    OSZ0244I RTCS0045SJSD      SJSD      DC$RTCS                               
    OSZ0244I RTCS003FSJSC      SJSC      DC$RTCS                               
    OSZ0245I END OF STATUS DISPLAY                                             
    SJSD     RESPONSES ---------------------------------------------------     
    OSZ0232I REGISTRY STATUS                                                   
    OSZ0233I LOCAL, EXPOSED, SHARED, AVAILABLE, VLDS-BACKED, VLDS OWNER        
    OSZ0234I WAS OWNED, ACQUIRED                                               
    OSZ0235I SCOPE=ALL                                                         
    OSZ0236I SYSTEM, SECURED, HRECALL                                          
    OSZ0237I VLDS_DD, DIV_MAP, *READY*, OWNERUP, LOAVAIL, DATASPC              
    OSZ0238I DIV-SAVE-MIN  =           5, DIV-SAVE-MAXIMUM =          30       
    OSZ0239I DIV-SAVE-IDLE =         900, DIV-SAVE-LIMIT   =         500       
    OSZ0257I APPROXIMATELY    537,526,272 BYTES ALLOCATED,  99% FORMATTED      
    OSZ0240I DSN=SYSO.RTCS$.SHARED.REGISTRY                   SER=SMS013       
    OSZ0241I DDN=SYS00001                                                      
    OSZ0242I XCF MBR=RTCS0045SJSD     GROUP=OSZSJSCD OWNER=RTCS0045SJSD        
    OSZ0243I MEMBER            SYSID     JOB NAME                              
    OSZ0244I RTCS0045SJSD      SJSD      DC$RTCS                               
    OSZ0244I RTCS003FSJSC      SJSC      DC$RTCS                               
    OSZ0245I END OF STATUS DISPLAY           
    DB2A     RESPONSES ---------------------------------------------------  
    OSZ0232I REGISTRY STATUS                                                
    OSZ0233I LOCAL, EXPOSED, SHARED, AVAILABLE, VLDS-BACKED, VLDS OWNER     
    OSZ0234I WAS OWNED                                                      
    OSZ0235I SCOPE=ALL                                                      
    OSZ0236I SYSTEM, SECURED, HRECALL                                       
    OSZ0237I VLDS_DD, DIV_MAP, *READY*, OWNERUP, LOAVAIL, DATASPC           
    OSZ0238I DIV-SAVE-MIN  =           5, DIV-SAVE-MAXIMUM =          30    
    OSZ0239I DIV-SAVE-IDLE =         100, DIV-SAVE-LIMIT   =        2000    
    OSZ0257I APPROXIMATELY    537,526,272 BYTES ALLOCATED,  99% FORMATTED   
    OSZ0240I DSN=CSGI.RTCS.BMCPLEX1.REGISTRY                  SER=DVL349    
    OSZ0241I DDN=SYS00001                                                   
    OSZ0242I XCF MBR=RTCS0047DB2A     GROUP=RTCSDB2  OWNER=RTCS0047DB2A     
    OSZ0243I MEMBER            SYSID     JOB NAME                           
    OSZ0244I RTCS0047DB2A      DB2A      MV$RTCS                            
    OSZ0244I RTCS0034DB2B      DB2B      MV$RTCS                            
    OSZ0244I RTCS004ESYSN      SYSN      MV$RTCS                            
    OSZ0245I END OF STATUS DISPLAY                                          
    DB2B     RESPONSES ---------------------------------------------------
    OSZ0232I REGISTRY STATUS                                               
    OSZ0233I REMOTE, SHARED, VLDS-BACKED                                   
    OSZ0235I SCOPE=ALL                                                     
    OSZ0236I SYSTEM, SECURED, HRECALL                                      
    OSZ0237I *READY*, OWNERUP, LOAVAIL                                     
    OSZ0238I DIV-SAVE-MIN  =           5, DIV-SAVE-MAXIMUM =          30   
    OSZ0239I DIV-SAVE-IDLE =         100, DIV-SAVE-LIMIT   =        2000   
    OSZ0257I APPROXIMATELY  2,147,483,648 BYTES ALLOCATED,   0% FORMATTED  
    OSZ0240I DSN=CSGI.RTCS.BMCPLEX1.REGISTRY                  SER=         
    OSZ0242I XCF MBR=RTCS0034DB2B     GROUP=RTCSDB2  OWNER=RTCS0047DB2A    
    OSZ0243I MEMBER            SYSID     JOB NAME                          
    OSZ0244I RTCS0047DB2A      DB2A      MV$RTCS                           
    OSZ0244I RTCS0034DB2B      DB2B      MV$RTCS                           
    OSZ0244I RTCS004ESYSN      SYSN      MV$RTCS                           
    OSZ0245I END OF STATUS DISPLAY                                         
    SYSN     RESPONSES ---------------------------------------------------
    OSZ0232I REGISTRY STATUS                                               
    OSZ0233I REMOTE, SHARED, VLDS-BACKED                                   
    OSZ0235I SCOPE=ALL                                                     
    OSZ0236I SYSTEM, SECURED, HRECALL                                      
    OSZ0237I *READY*, OWNERUP, LOAVAIL                                     
    OSZ0238I DIV-SAVE-MIN  =           5, DIV-SAVE-MAXIMUM =          30   
    OSZ0239I DIV-SAVE-IDLE =         100, DIV-SAVE-LIMIT   =        2000   
    OSZ0257I APPROXIMATELY  2,147,483,648 BYTES ALLOCATED,   0% FORMATTED  
    OSZ0240I DSN=CSGI.RTCS.BMCPLEX1.REGISTRY                  SER=         
    OSZ0242I XCF MBR=RTCS004ESYSN     GROUP=RTCSDB2  OWNER=RTCS0047DB2A    
    OSZ0243I MEMBER            SYSID     JOB NAME                          
    OSZ0244I RTCS0047DB2A      DB2A      MV$RTCS                           
    OSZ0244I RTCS0034DB2B      DB2B      MV$RTCS                           
    OSZ0244I RTCS004ESYSN      SYSN      MV$RTCS                           
    OSZ0245I END OF STATUS DISPLAY                                      



 

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