BBPARM member AAOPLX00 parameters

(optional) Provides the name to identify this PAS within the AOPlex

This name is used when identifying the PAS in the Valid PAS List (VPL) and in AGS messages and reports.

The default value is the target name from the TYPE=MVS entry in the BBIJNT00 member for this PAS, also known as the MVAO service point. In addition, the name must also be:

• Unique within the AOPLEX.
• 1 to 8-alphanumeric characters and national characters:    
  • Dollar sign ($)
  • Pound sign (#)
  • At sign (@)

Using the default value (the PAS target name) might simplify the configuration of multiple PASes that share the same registry in an AOPlex configuration.         

(required) Provides the name of the AOPlex to which this PAS belongs

This name must be the same for all BMC AMI Ops Automation PASes that share a rules registry. In addition, this value must be unique to the AOPlex and cannot be the same value as any TOMPLEX_NAME value.

This name can contain only alpha or numeric characters. No special characters are allowed.

(required) Provides the name of the XCF group that the AOPlex will use to communicate

This name must be the same for all PASes that share the same registry dataset.

This value must be 1 to 8-characters long. This name can contain only alphanumeric characters. No special characters are allowed.

This value cannot be the same as AOPLEX_NAME and cannot be the same XCF group name specified in the XCFGROUP= parameter in BBPARM member BBISSPx.

(required) Informs the PAS how to use the registry

Valid values are:

OFF: The BMC AMI OpsA PAS will not use a registry for Rules in any way. Rules Management is not functioning for the PAS. Rules are read from the BBIPARM DD concatenation.

ADMIN: The BMC AMI OpsA PAS opens the registry and allows you to perform administrative tasks, which the registry records. However, BMC AMI OpsA is not using the Rules from the registry for any automation in the PAS. Rules are read from the BBIPARM DD concatenation.

FULL: The BMC AMI OpsA PAS uses the Rules from the registry, allows you to perform adinistrative tasks on the registry, and also reads from the registry to supply all the Rules and Rule Sets for automation in the PAS. No Rules are used from the BBIPARM DD concatenation and the full-screen Rules editor is disabled.

The default is OFF.

(optional) Specifies whether the BMC AMI OpsA Generalized Services (AGS) messages are sent to the BMC AMI Ops Infrastructure Logger

Valid values are:

YES: (recommended) Messages are sent to the Logger. If the Logger becomes unavailable for any reason, and AGSJRNL=NO and FORCEWTO=NO are also specified, the value on the AGSLOG_FAILOVER parameter determines what happens to the message.

NO: Messages are not be sent to the Logger

(optional) Specifies whether an empty registry in the PAS and running in ADMIN mode is automatically loaded (initialized) with Rules and Rules Sets from the local BBPARM data set

There are two prerequisites to use the AUTOLOAD_REGISTRY parameter. If both conditions are not met, BMC AMI OpsA ignores the parameter during the PAS start (COLD or WARM):

• The PAS must be running in ADMIN mode where the parameter USAGE_MODE_RULES=ADMIN is specified.
• The PAS registry must be a newly defined VLDS that is empty and has never been used in any other PAS startup since it was last defined by VSAM.

Valid values are:

• NO (default) BMC AMI OpsA will not attempt to initialize an empty Rules registry, even if all the conditions are met.
  If you specify NO, and the other conditions criteria are met, BMC AMI OpsA issues an informational message to the PAS job log to remind you that the option exists.
• ENABLED When you specify ENABLED, BMC AMI OpsA loads the Rule Sets that are currently in ENABLED status in the local PAS into the registry and designates these Rule Sets (and only these Rule Sets) ENABLED for subsequent COLD starts of the PAS when USAGE_MODE_RULES=FULL is specified.
  
  This group of Rule Sets might or might not match the Rule Sets specified on the RULESET= parameter in the AAOPRMxx member used when the PAS was last started COLD. It is also possible that Rule Sets might have been manually ENABLED or DISABLED since the last COLD start. In addition, BMC AMI OpsA does not load the Rule Sets that are in TEST or LOADED status when you specify ENABLED.
  
  
• COLDSTART Specify this option when you want to load the Rule Sets that were used when the PAS was last started COLD. BMC AMI OpsA loads only the Rule Sets that are specified with the RULESET= parameter in the AAOPRMxx member. This group of Rule Sets might or might not match the Rule Sets specified on the RULESET= parameter in the AAOPRMxx member when this PAS was last started COLD. If you made any changes to the RULESET= parameter after the last COLD start, there will be a difference in the Rule Sets BMC AMI OpsA loads between COLD starts. Be sure to verify that the Rule Sets listed in the current AAOPRMxx member are the Rule Sets that you want to load.
  
  
• ALL Specifies the following actions:
  • Imports all of the Rule Sets that are specified in the local PAS's BBIPARM DDname concatenation
  • Sets any Rule Sets specified in RULESET= found in AAOPRMxx as ENABLED

Only Rule Sets that are a member of the PASDef used for the PAS are eligible for use in the local PAS.     

(optional) Overrides the default naming pattern that is used for the Rule pool names used during AutoLoad processing

By default, the Rule pools are named using a pattern of:                                             

where <%p> is substituted with the name of the Rule Set (and so on).

When you specify % within the name (and not at the end of the name), you must separate it with a period (.). BMC AMI OpsA resolves the value as a node in the name and includes the period.                                        

For example, if you have a Rule Set named MVSAUTO and you use the default pattern, the resulting Rule pool name is MVSAUTO.RULE.POOL.

You can use this parameter to override the default pattern by specifying a new pattern. The derived name, after all substitutions, must not exceed 32 characters. The pattern can include constants, MVS symbolic symbols (starting with an ampersand (&)), and the private symbol <%p>.    

For example, if you have a Rule Set named MVSAUTO. &SYSNAME is set to SYSA, and specify the following pattern, the resulting Rule pool name is SYSA.Rule.Pool.MVSAUTO:                                                 

&SYSNAME..Rule.Pool.%p

This optional parameter is used if the AUTOLOAD_REGISTRY= parameter does not specify NO. In other cases, the value is parsed and accepted but is not used.