EMS Manual

Configuring EMS
EMS Manual—426909-005
12-25
Primary Collector Logging After a System Load
See the FILTER (PLF) and SUPPRESS (BDS) process attribute descriptions in
Collector Process Attributes on page 12-10.
Primary Collector Logging After a System Load
When primary collector logging starts after a system load, the collector must determine
where to start logging event messages. It continues logging in the previous log file, if
one existed, or creates a new log file if it determines no previous logging took place.
The primary collector must also determine collector attributes. It uses previously
defined attributes if it can determine what they are. If it cannot, it uses default values.
Determining Primary Collector Log-File Names
The first log-file name used at system load is:

If a context file (ZZEVCONF) exists in the default subvolume and if the first record
in that file is a ZEMS-EVT-FILESWITCH event message, the collector assumes
that logging was previously in progress.
The previous log file is located by retrieving its name from the ZEMS-MAP-COL-
STATUS token in the FILESWITCH event message. If that file name corresponds
to the file name in the $SYSTEM.SYSTEM.ZZEVCONF file, logging resumes in
that log file. If the file names do not agree, the integer portion of the file name (the
nnnn part of ZZEVnnnn) is incremented by one, and logging is started in a new file
with that name.

If no files exist in the default subvolume, or if a ZZEVCONF file exists but the first
record in the file is not a ZEMS-EVT-FILESWITCH event message, the collector
assumes that logging has not previously been in progress, and it creates
$SYSTEM.ZLOGnn.ZZEV0000 as its first log file.