IND$defender configuration parameters


See BMC AMI Defender API. For a discussion of general parameter syntax, see Parameter-file-statements. The IND$defender parameters do not use a statement type name or continuations.

Tip

The configuration statement can be as long as necessary.


image2019-2-25_14-4-33.png

ALLOCwith("additional BPXWDYN parameters")

Specifies additional BPXWDYN parameters for use in allocating the library that contains IBM IND$FILE.

Example

If the library were an uncatalogued data set on volume SYS002, you would code ALLOC(VOLSER(SYS002)).

Separate multiple BPXWDYN parameters with a space, and enclose the entire string in quotation marks (double quotes). Do not code any BPXWDYN parameters that include or conflict with ALLOC, DD, DSN, REUSE, SHR or MSG. BPXWDYN is documented in the IBM manual z/OS Using REXX and z/OS UNIX System Services. If you omit ALLOCwith, it defaults to "", the null string, or no additional parameters.

INSTance(instance)

Specifies BMC AMI Defender for z/OS instance number for the API. This parameter is validated but otherwise ignored, unless you also specify SENDto(API). See BMC AMI Defender for z/OS Installation and Operation. The Start or S Command for a discussion of BMC AMI Defender for z/OS instances. Code a number between 0 and 7 inclusive. If you omit INSTance, it defaults to 0 (zero).

LIBrary(library-name)

Specifies the name of the PDS or PDSE containing IBM IND$FILE, APVUFILE, or both. Code a z/OS data set name of one to forty-four characters. If you omit LIBrary, it defaults to SYS1.CMDLIB.

PROGram(program-name)

Specifies the name of the IBM IND$FILE or APVUFILE program. Specify this parameter only if you have renamed IBM IND$FILE, APVUFILE or both. Code a name of one to eight characters. If you omit PROGram, it defaults to the alias name under that IND$defender is invoked, normally IND$FILE or APVUFILE.

SENDto(destinations)

Specifies the destinations to which IND$FILE events are to be sent. Code API, SMF, or both, separated by one or more blanks. API means that events sent to the specified or defaulted BMC AMI Defender for z/OS instance as API1 events of Major Type CZ1MajCorMisc, Minor Type 2, subtype 1. SMF means that events are to be written as user SMF records of the type specified or defaulted and subtype 1. If you omit SENDto, it defaults to SMF.

SMF(record-type)

Specifies the SMF record type number for IND$FILE events. This parameter is validated but otherwise ignored, unless you specify SENDto(SMF) or allow it to default. Code a number between 128 and 255 inclusive. You might code the number as a decimal integer, or in hex using either mainframe (X'CA') or C format (0xca). If you omit SMF, it defaults to 202.

TRACE(trace_specifications)

Specifies that IND$defender is to output trace messages to the 3270 screen.

Note

The use of trace messages is intended only for diagnostic purposes and is generally inconsistent with actual use of IND$FILE. Particularly, the specification of TRACE(PARMS) might interfere with effective usage of IND$FILE. See BMC AMI Defender documentation. The OPTIONS Statement for a general discussion of TRACE. The two trace options that might be relevant to IND$defender are MISC and PARMs. Code one or both of MISC and PARMs separated by one or more blanks.

 

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