Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Ops Infrastructure 7.1 .

Alert Manager PAS library member

BBSAMP member BBHPAS contains statements for customizing or creating a Alert Manager PAS startup procedure in your system started task procedure library.

The Started task procedure statements table describes the Alert Manager PAS startup JCL statements. These statements can be found in BBSAMP member BBHPAS.

The PROC parameters table describes the parameters for the Alert Manager PAS PROC statement.

Tip

Alert Manager is integrated into the CAS. Alarm Management does not require its own PAS. For more information, see Using-Alarm-Management.


Started task procedure statements

JCL statement

Description

// procname PROC

This statement identifies the started task procedure and its parameters. See PROC parametersfor an explanation of each PROC statement parameter.

Note

You can override these parameters with the START command for the PAS, as described in Managing-the-BBI-SS-product-address-space-PAS .

//PAS EXEC

This statement specifies the program name as PGM=SSLOAD.

The PARM subparameters are all symbolic and use the same values that were defined for the corresponding parameter in the PROC statement. For a detailed explanation of each parameter, see PROC parameters.

//STEPLIB DD

This statement defines a partitioned data set that contains the Alert Manager load modules.

The partitioned data set must be an authorized library, such as hlq.BBLINK.

Note

This statement should be deleted if BBLINK was added to your system link list concatenation.

//BBACTDEF DD

This statement defines the library containing all action and view tables for Alert Manager.eee

//BBIPARM DD

This statement contains the parameter members for Alert Manager.

//BBSECURE DD

This statement defines the data set that contains Alert Manager security resource definitions.

These definitions are used by the CAS and PAS to determine whether security checking should occur for access to systems, products, views, and actions. The same data set name must be defined for the CAS started task procedure BBSECURE statement and the PAS started task procedure BBSECURE statement.

Note

Defining a BBSECURE data set is only one part of setting up security to function with your external security manager (ESM). For more information, see Managing-security-for-BMC-AMI-Ops-products.

//BBVDEF DD

This statement defines the view library that contains all default views for Alert Manager.

//BBIJRNL1 DD

//BBIJRNL2 DD

This statement defines the journal log data sets that Alert Manager uses to record:

  • Commands and responses that are issued by the Alert Manager component
  • Product alerts, warnings, and messages

//BBIDIV DD

This statement defines the data-in-virtual (DIV) data set that is used to store binary large objects and data across Alert Manager restarts.


PROC parameters

Proc parameter

Description

MVALSS=ssid

This parameter specifies a one- to four-character subsystem ID for the Alert Manager started task procedure.

This ID must be unique within the MVS image where Alert Manager will be started.

START=WARM | COLD | FREE

This parameter specifies the type of Alert Manager PAS startup.

Use the default, WARM, whenever possible.

A cold start might occur automatically after the system is IPLed or maintenance is applied. Otherwise, do not request START=COLD or START=FREE unless instructed to do so by BMC Support.

MVAJRNL=dsname

This parameter identifies the Alert Manager journal log data sets.

The data set names are derived by adding a suffix of 1 or 2 to the value of this parameter.

Example

If you specify MVAJRNL=‘BMC.MVAJRNL’, the started task procedure looks for two data sets called ‘BMC.MVAJRNL1’ and ‘BMC.MVAJRNL2’.

Note

The data sets that you identify must be allocated by using the BBIJRNL1 and BBIJRNL2 DD statements in the PAS startup JCL.

MVADIV=dsname

This parameter identifies a data set to be used by Alert Manager for storing data across product restarts.

Note

The data set that you identify must be allocated by using the BBIDIV DD statement in the PAS startup JCL.

BBLINK=

(optional) This parameter defines the name to be assigned to BBLINK.

Note

If BBLINK is in your system link list, this parameter and the STEPLIB DD statement should be removed.

BBCHILV=

This parameter defines the high-level qualifier for the product libraries.

MVAPARM=

This parameter defines the name to be assigned to the Alert Manager user parameter library.

 

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