×
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')
 
 

Space banner

   

This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.
MainView Infrastructure 6.2 Customizing after installation

MainView Alert Manager PAS library member

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

MainView Alert Manager PAS started task procedure statements describes the MainView Alert Manager PAS startup JCL statements. These statements can be found in BBSAMP member BBHPAS.

MainView Alert Manager PAS PROC parameters describes the parameters for the MainView Alert Manager PAS PROC statement.

Tip

MainView Alarm Management (the new version of MainView Alert Manager) is integrated into the CAS. Alarm Management no longer requires its own PAS. For more information, see Using MainView Alarm Management.

MainView Alert Manager PAS started task procedure statements

JCL statement

Description

// procname PROC

This statement identifies the started task procedure and its parameters. See MainView Alert Manager PAS PROC parameters for 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 MainView Alert Manager PAS PROC parameters.

//STEPLIB DD

This statement defines a partitioned data set that contains the MainView 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 MainView Alert.

//BBIPARM DD

This statement contains the parameter members for MainView Alert Manager.

//BBSECURE DD

This statement defines the data set that contains MainView 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 the Managing security for MainView products.

//BBVDEF DD

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

//BBIJRNL1 DD

//BBIJRNL2 DD

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

  • Commands and responses that are issued by the Alert Management 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 MainView Alert Manager restarts.

MainView Alert Manager PAS PROC parameters

Proc parameter

Description

MVALSS=ssid

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

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

START=WARM | COLD | FREE

This parameter specifies the type of MainView 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 Customer Support.

MVAJRNL=dsname

This parameter identifies the MainView 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 MainView 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 MainView Alert Manager user parameter library.

Was this page helpful? Yes No Submitting... Thank you
Last modified by Benjie Wolicki on Aug 08, 2019
mainview_alert_manager proc_statement reference

Comments

SPACE parameter
Using MainView Alarm Management
© Copyright 2005 - 2019 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2021 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.