Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support. BMC recommends upgrading to the latest version of the product.

CONFIG statement

The CONFIG statement is used to specify certain infrequently-modified parameters that (other than TRACE) might not be altered during BMC AMI Datastream execution. A CONFIG statement is processed only during product startup.

CONFIG_statement.png

For more information about traceSpecification, see Using-the-TRACE-facility.

A CONFIG statement might be placed anywhere in the Field Definitions file. A user-specified CONFIG statement is most appropriately placed in the member CZDUSER2. For more information, see Preserving your modifications across BMC maintenance in Defining-fields.

The effect of CONFIG statements is cumulative: any CONFIG statement parameters override any specification earlier in the Field Definition files.

Option

Description

ENRICH(ACF2(length))

Applies only to installations running the CA System Authorization Facility (SAF) product ACF2. (For non-ACF2 installations the parameter is ignored and forced to No.) ENRICH(ACF2 specifies the number of bytes of ACF2 fields that are to be included with every queued SMF event. Specify the length of the user LID fields that are to be included. BMC AMI Datastream supports both the original user LID and the extended user LID; specify a single length as though the two areas were contiguous. Specify No to include no ACF2 enrichment fields; specify 0 to include only the standard ACF2 fields (see SMF-ACF2-common-fields). ENRICH(ACF2 is optional; if omitted, it defaults to ACF2(80); that is, the standard ACF2 fields plus 80 bytes of custom user LID.

Important

There is no RE- form of CONFIG and there is no RECONFIG statement.

MAXEVENTLENgth(length)

Specifies the maximum length of any event (SMF or API1) record. You need to specify this parameter only if you are using an API1 program that generates records in excess of 32768 bytes. (No SMF record exceeds 32768 bytes, the MAXEVENTLENgth default.) This requirement applies to you only if you are writing API1 programs  as described in Developing, or if you are using a supplementary BMC product. Consult with BMC Support for instructions about how to code this parameter. MAXEVENTLENgth is optional; if omitted, it defaults to 32768.

TRACE(traceSpecifications)

Specifies that BMC AMI Datastream and CZASEND are to output additional diagnostic messages and the types of diagnostic messages, or not to output additional diagnostic messages, in the CZAPRINT data set. TRACE might be useful for diagnosing certain problems. If TRACE is completely omitted, then it defaults to the previous state of TRACE; if TRACE() or TRACE(-ALL) is specified, then all tracing is turned off.

Specify zero or more of the trace types described in Using-the-TRACE-facility (in any order). Prefix any of the specifications with (-) (a minus sign or hyphen) to indicate negation. The specifications are processed left to right.

Example

TRACE(ALL –XL –ENV) indicates all TRACE output except that related to translation and the operating environment.


Related topics

Field-definition-file-statements

General-type-specifiers-for-definition-statements

 

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