LOCAL statement

The LOCAL statement is used to specify a local (that is, on the LPAR on that BMC AMI Defender is running) data set that receives a copy of syslog messages, and the options for that data set. The LOCAL statement is optional. Any LOCAL statement is ignored by CZASEND. When the parameter file is re-processed because of a MODIFY command (see MODIFY-command) the LOCAL data set is not closed and re-opened unless the operand of the DATASET parameter has been changed.

Important

You can modify the $$$SERVR member in the amihlq.CZAGENT.PARM data set.

If you code more than one LOCAL statement – or, if your LOCAL statements are qualified with FOR, more than one LOCAL statement that applies to a particular LPAR – then a subsequent LOCAL statement replaces any LOCAL statement(s) that came before.

Syslog messages appear in the local data set in the format:

11103 16:18:36 UUCP       NOTICE TCP/IP: Subtype: Connect init – Stack: TCPIP -
               AS: TCPIP – ResName: PCRR220B – RemtIP: ::ffff:17.32.0.135

11103 16:18:43 UUCP       NOTICE TCP/IP: Subtype: Connect init – Stack: TCPIP -
               AS: TCPIP – ResName: FTPD1 – RemtIP: ::ffff:17.32.8.66

If you a setting up a short-term display of syslog messages to solve a particular problem, by far the easiest way to use LOCAL is,

LOCAL DATASET(*)

Directing the LOCAL data set to spool eliminates the need to anticipate the space required and also eliminates ENQ issues, allowing the data to be browsed while BMC AMI Defender is still running.

Parameter

Description

LOCal

Must be specified as shown

For and/or if

See FOR-and-IF-statements.

DATASet(dataset specification)

Data set to receive the local copy of the syslog messages

See Data-set-specification.

Note

* is supported, but default PDS member names are not. The output variable symbols are supported for LOCAL DATASET.

If DATASET is omitted, it defaults to * (SYSOUT).

For LOCAL, BMC AMI Defender allocates SYSOUT data sets and new MVS data sets specified by data set name with the following attributes, depending on the value specified or defaulted on the FOLD parameter (as shown). (For zFS files these attributes are irrelevant; for data sets specified with DD: BMC AMI Defender provides no attributes: you should specify the desired attributes on the DD statement. Attributes similar to those in the following table are recommended.)

FOLD()	LRECL	RECFM
133	137	VBA
No	1100	VB
80	84	VB

You can see the actual z/OS data set name constructed by examining the CZAPRINT listing for the following message:
CZA0274I LOCAL file: actual.dataset.name.here.

FOLD(length)

Format of the syslog messages in the data set

FOLD(133) specifies that the messages are to be folded to overflow lines at 133 characters. Records begin with an ASA carriage control character: 0 (double space) for the initial line of each message and blank (single space) for the subsequent lines, if any. FOLD(No) specifies that the lines are simply to be written to the data set as individual records without ASA control characters. FOLD(80) specifies that messages are to be folded to overflow lines at 80 characters. There are no carriage control characters. If FOLD is omitted, it defaults to FOLD(133).

MOD

Data set is to be opened DISP=MOD, that is, any additional records are to be appended to any existing records in the data set

The use of MOD with a data set name that includes a member is not recommended unless you are familiar with how z/OS handles PDS member names and DISP=MOD. MOD is recommended if you are using a data set name that does not include &HHMMSS. As otherwise, a restart of BMC AMI Defender probably causes an existing data set to be overwritten.

Note

Language Environment does not allow you to open a data set MOD with a different LRECL or RECFM (controlled by the FOLD parameter).

REOPen(MIDNight)

Data set is to be closed and reopened each day immediately after midnight

REOPEN is probably best used in conjunction with SYSOUT or data set names that include one of the date variable symbols (&YYMMDD Or &YYYYDDD).

SPACE(unit primary secondary directory)

Space to be allocated to the data set

For a description of the meaning of the operands of SPACE, see the IBM documentation. Each DASD track holds a little less than 56 Kbytes; each cylinder a little less than 850 Kbytes. SPACE(TRK 10 10) allows for somewhat less than 560K of messages in the first extent and in each of up to 15 additional extents, for a total of somewhat less than nine megabytes. Be careful not to specify a non-zero directory value unless you also specify a member name in DATASET. For existing data sets, zFS files and SYSOUT, SPACE is checked for validity but otherwise ignored. If SPACE is omitted, it defaults to SPACE(TRK 10 10 0).

LOCAL statement

On this page