Parameter file statements

The BMC AMI Defender parameter file controls the overall operation of BMC AMI Defender and CZASEND by providing parameters such as the TCP/IP address of the BMC Defender Server or syslog console.

The Parameter file must be accessible to BMC AMI Defender and all jobs that use CZASEND.

See Format-of-parameter-and-field-definition-files.

This section provides information about the following topics:

Statements relevant to a DAM configuration

Only the following statements described are relevant to a DAM configuration:

The BMC AMI Defender product requires an SMF DAM statement.

OPTIONS parameters for the BMC AMI Defender product

The following OPTIONS parameters are supported by, or are relevant to, BMC AMI Defender package:

FOR
QUEUE
SWAPpable
TCPname
NOTCPWait
TRACE
XLATE

You should omit the remaining parameters of OPTIONS and allow the default value to appear.

Effect of duplicated statement types

You might code a given parameter statement type multiple times. The parameter file is processed sequentially. If you code more than one OPTIONS statement—or, if your OPTIONS statements are qualified with FOR, more than one OPTIONS statement that applies to a particular LPAR—then the effect is cumulative.

Example

If you were to code,

OPTIONS FORMAT(ALL) HOST(CPUID) TAGCASE(LOWER)
OPTIONS TIMESTAMP HOST(SMFID)

then the effect is exactly as if you had coded

OPTIONS FORMAT(ALL) TAGCASE(LOWER) TIMESTAMP HOST(SMFID)

SELECT statements are similarly cumulative. If you code

SELECT SMF(15 42)
SELECT SMF(30 80 DB2)

then the effect is exactly as if you had coded

SELECT SMF(15 42 30 80 DB2)

For all other statement types (LOCAL, SERVER, SMF nn and TIME) a duplicate statement type replaces any equivalent statement type that came before. For instance if you were to code

SERVER 172.33.10.5:1514
SERVER 172.33.11.2

then the effect is exactly the same as if the first SERVER statement had been omitted.

Parameter processing starts over each time you read in a parameter file with MODIFY CZAGENT,PARMS with the exception of OPTIONS TRACE, SUBSYS, and QUEUE64. Every parameter assumes its default value except for the three parameters named. So if BMC AMI Defender is running with a LOCAL data set, FORMAT(ALL), and an SMF 119 statement, and you read in a new Parameter file with FORMAT, LOCAL, and SMF 119 omitted, then FORMAT assumes its default value of ERGONOMIC, the LOCAL data set is closed, and no further SMF 119 records are formatted and transmitted.

Generally speaking, parameters are processed sequentially from left to right, and a parameter that is specified a second or subsequent time overrides the first specification, with no error reported.

Example

If you were to code,

SMF 80 EVENT(7 SEV(WARN)) EVENT(7 SEV(ERR))

then SMF 80 event code 7 records would be forwarded with a severity of Error.

Statements common to the parameter file and the field definitions file

You can use the following statements in the Parameter file and the field definitions files:

INCLUDE-statement—Logically copies another file into the fields definitions or parameters at the point of the %INCLUDE statement.
SAY-statement—Identifies a particular parameter or field definition file by displaying the SAY operand in CZAPRINT.