START command

Specifies the name of the BMC AMI Defender cataloged procedure in the SYS1.PROCLIB concatenation.

Specifies the name of the primary fields definitions file. For more information, see Field-definition-file-statements. As the fields definitions file is an input file, a specification of * (SYSOUT) is invalid, and the output variable symbols are not supported. z/OS command processing uppercases unquoted command operands, so to specify a zFS file specify, such as,

The default PDS(E) is DD:CZAPARMS, that is, the library specified by the CZAPARMS DD statement. If DEFines is omitted, it defaults to DD:CZAPARMS(CZDEFINE).

Should be used with extreme caution and only after an unrecoverable failure (see Restarting zDefender after an Unrecoverable Failure) or as directed by BMC Support.

FORCE does not cause any harm if used unnecessarily assuming BMC AMI Defender is not already running as the specified INSTANCE. Avoid using FORCE habitually or routinely because if you inadvertently use FORCE when BMC AMI Defender is already running as the specified INSTANCE it causes unpredictable problems.

If START CZAGENT with FORCE runs into certain unexpected situations, it attempts to clean them up. It also reports them and then terminates with an error. However, a second attempt at FORCE might succeed because the unexpected situation has previously been resolved. So if FORCE fails, you should try it again up to two or three times. You should see a different error on the subsequent failure; if not, further retries are pointless.

INSTALL=FORCE is ignored with INSTANCE=*; you must specify an explicit instance number.

INSTANCE=instance

Specifies a BMC AMI Defender instance number between 0 and 7 inclusive, or * (asterisk) to use the next available instance number. The use of the default, * (an asterisk) is generally recommended. Instances allow you to start more than one copy of BMC AMI Defender in a single LPAR. The multiple instances run completely independently and could specify different SIEM collectors, different SMF records, different formatting options, and so forth. If you specify the number of an instance that is already running you receive an error message. If you omit INSTANCE it defaults to *, the next available instance number.

Specifies a single SSID for the SMF DAM or SMF DB2 parameter. The variable symbol &SSID. (note terminating period) might be used as the operand of SMF DAM or DB2 SSIDs() and the operand is processed as though ssid had been coded.

This option is intended especially for use with BMC AMI Defender for Db2.

Specifies that BMC AMI Defender is to output additional diagnostic messages and the types of diagnostic messages, in the CZAPRINT data set. TRACE might be useful for diagnosing certain problems. If TRACE is completely omitted then all tracing is turned off.

Specify zero or more of the trace types described in section 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. For instance, TRACE(ALL –XL –ENV) indicates all TRACE output except what is related to translation and the operating environment.

Specifies that BMC AMI Defender is to scan the field definition and parameter files and log any errors, and then terminate. TYPERun=SCANonly might be useful for validating parameter file changes before putting them into production.

If BMC AMI Defender initialization is successful the response to the START command is:

In the event of errors diagnostic, messages are issued to the console and to CZAPRINT. For some errors additional information might be available in CZAPRINT beyond what is displayed on the console.