QAOIVP EXEC

Use the QAOIVP driver EXEC to initiate the IVP. The QAOIVP driver EXEC is located in the BBPROC data set. You must either include the BBPROC data set in your BBI-SS PAS JCL SYSPROC concatenation, or copy the the EXEC to a data set that is is included in the SYSPROC DD.

You can specify the following (optional) input keywords to the QAOIVP EXEC:

MSGDEST – specifies that the output messages are sent to the Journal, WTOs, or ALL
LEVEL – specifies the level of verification (basic, configuration, or optimization)
ALERT – specifies the name of the ALERT queue to send any ALERTs that are generated for failed tests
DEBUG – produces a trace of the EXEC
HELP – displays information about the IVP EXEC

The following is an example of the QAOIVP EXEC and all of its keywords:

%QAOIVP MSGDEST() LEVEL() ALERT() DEBUG() HELP

Keyword	Description
MSGDEST	Specifies the destination for the output messages from the QAOIVP EXEC The default value is: JRNL The following values are valid: JRNL: output messages will be issued as Journal messages WTO: output messages will be issued as WTOs ALL: output messages will be issued to all supported destinations
LEVEL	Specifies which installation verification categories to invoke. The default value is: B The following values are valid: B: the EXEC performs basic functionality analysis C: the EXEC performs configuration analysis O: the EXEC performs optimization analysis ALL: the EXEC to perform all levels of analysis You can also specify more than one option separated with a comma; for example: LEVEL(B,C) invokes both the basic functionality and the configuration level of analysis.
ALERT	Specifies an ALERT queue name and causes MainView AutoOPERATOR to generate ALERT messages for all WARN and FAIL level test results to that queue There is no default value for this parameter. If you do not specify this parameter, MainView AutoOPERATOR does not generate any ALERT messages. The following values are valid: Queue_name: A 1 to 8-characters ALERT queue name. The queue does not have to preexist. For example: ALERT(MAIN) The QAOIVP EXEC does not delete these ALERTs when it completes running.
DEBUG	Specifies whether the QAOIVP EXEC writes a trace of the invoked EXECs to the BBI-SS PAS Journal Log. The default value is: N The following values are valid: Y: the QAOIVP EXEC writes trace messages N: the QAOIVP EXEC does not write trace messages If DEBUG(Y) is specified, MainView AutoOPERATOR might produce a very large number of output messages. BMC recommends specifying this keyword and value only when customer support requests that you do.
HELP	Specifies that information about this EXEC is written to the BBI-SS PAS Journal Log

The following is an example of invoking the QAOIVP EXEC which sends the results messages to both the Journal and WTOs, and also performs the basic and configuration analysis levels:

%QAOIVP MSGDEST(ALL) LEVEL(B,C)

QAOIVP EXEC

Comments