EMS Manual

Configuring EMS
EMS Manual426909-005
12-27
Logging After a Subvolume Switch
ROTATEFILES = TRUE
MAXFILE = 4
PROTECTION = COOO
DISCACCESSID = SUPER.SUPER
BLOCKING = ON
These attributes can be changed programmatically by sending a CONTROL command
message, or interactively by using the EMSCCTRL utility program. The maximum
number of extents is always 16.
Logging After a Subvolume Switch
If you change the log subvolume (LOGSUBVOL) for either a primary or alternate
collector, the log-file name is selected as:
If a context file (ZZEVCONF) exists in the new 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 in this subvolume.
The previous log file is located by retrieving its name from the ZEMS-MAP-COL-
STATUS token in the FILESWITCH event message. 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 new 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 in this subvolume, and it
creates ZZEV0000 as its first log file.
The attribute values used to create log files in the new subvolume are established as:
Any attributes specified in the CONTROL command message or the EMSCCTRL
parameters are always used.
If a ZZEVCONF file exists in the new subvolume, attributes not specified in the
CONTROL command message or EMSCCTRL parameters are taken from that file.
DISCACCESSID is not saved in the ZZEVCONF file, so this possibility does not
apply to DISCACCESSID.
If no ZZEVCONF file exists in the new subvolume, attributes not specified in the
CONTROL command message or EMSCCTRL parameters keep their current
values. DISCACCESSID always keeps its current value across a subvolume switch
unless it is explicitly specified in the CONTROL command message or as an
EMSCCTRL parameter.
Changing subvolumes might unexpectedly change the settings of one or more
attributes if a ZZEVCONF file exists in the new subvolume and contains different
attribute settings than those previously in effect. For this reason, explicitly specify any
attributes that you are concerned might have undesirable settings in the ZZEVCONF
file.