Registry considerations

Registry allocation

Use the sample JCL found in BBSAMP member AAOAGSAL to allocate a registry.

The JCL includes comments at the top that you should review to determine the size of the registry and describes the other JCL modifications you will need to make. Submit the JCL to create the VSAM Linear data set (VLDS) and specify the data set name of the registry in BBPARM member AAOPLXxx with the REGISTRY_DSN parameter.

Registry organization

The registry is organized into three areas:

• PAS definition (PASDef)

  The PASDef is the part of the registry that controls aspects of Rules and Rule Sets the way some of the definitions in BBPARM member AAOPRMxx controls full-screen mode Rules. For example, the PASDef defines which Rule Sets are available to a BMC AMI Ops Automation PAS, the automation strategy that a Rule Set has when it is started (FIRST, ALL, INDIVIDUAL, and so on), and the automation status.

  You can define a single PASDef to be shared by as many PASes as needed. So, for example if your system has one PAS on each of five different LPARs and you want all the PASes to have the same Rules and Rule Sets, you create one PASDef and define the names of the five PASes that will use it.

  To define a new Rule Set for each of the five PASes, you can add the Rule Set to the PASDef and deploy the PASDef (with the new Rule Set) to all five LPARs with a single command.

• Setbase

  A setbase is a collection of Rule Sets. A setbase might include Rule Sets for a single application, a single geographical location, or a business unit of your company. The setbase can include Rules Sets for anything that makes sense in your environment. If you do not need to organize Rule Sets this way, you can put all your Rule Sets into the supplied default setbase. You can implement multiple setbases at anytime.

• Rule Pools

  When Rules were created in full-screen mode, a Rule is a part of a Rule Set, which is a member of a partitioned data set (PDS). With this structure, you can not share a Rule between multiple Rule Sets to meet different requirements. You can only copy a Rule into multiple Rule Sets and then maintain them individually. With the registry, Rules are now stored in groups that are called Rule Pools. With these registry-based Rules, you create a single Rule and assign it to multiple Rule Sets but the Rule itself is not duplicated. Assigning a single Rule to multiple Rule Sets eliminates the need to individually maintain a copied Rule.