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.
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. |
//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. |
//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. |
//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:
|
//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. |
MVADIV=dsname | This parameter identifies a data set to be used by Alert Manager for storing data across product restarts. |
BBLINK= | (optional) This parameter defines the name to be assigned to BBLINK. |
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. |