AutoSYNC Software User's Guide (Update 18)

Problem Resolution
HP AutoSYNC User’s Guide—522580-019
B-8
Events in the EMS Log
Events in the EMS Log
The AutoSYNC monitor and the synchronization processes report informational and
critical events to the EMS log on the source system. The Monitor events are sent to the
Monitor’s home terminal. To direct all AutoSYNC events (from ASYSYNC processes
and the Monitor) to the same collector, configure the Monitor’s home terminal to the
local collector.
The events logged are the following:

Synchronization process START and STOP messages

Monitor START and STOP messages

Configuration changes made by the administrator to a syncfileset or a batchid

Exception and error conditions
You can tailor the generation of EMS events to the requirements of individual
syncusers:

To generate EMS events when file access errors occur during a synchronization
(for example, error 48 or error 45), set the syncuser option EMSFILEEVENTS. The
EMS message displays the name of the log file SLggguuu, the key of the log
record, the SYNCfileset ID, the file error and the filename portion of the file. You
can then refer to the log file for details.

To generate an EMS event if a syncfileset was synchronized to completion but
contained files that were not synchronized, set the syncuser option
EMSFILENOTSYNCED. This event does not necessarily signal an error condition;
for example, in a syncfileset configured with OPENUPDATE, a file will not be
synchronized if it was being updated during the synchronization.

To suppress informational messages such as synchronization START and STOP
messages and configuration changes, set the syncuser option or global parameter
EMSSUPPRESS. To suppress these optional messages for synchronizations done
over TCP/IP, set the global EMSSUPPRESS on both the source and destination
systems, instead of setting the SYNCUSER option.
Note that EMSUPPRESS overrides both EMSFILENOTSYNCED and
EMSFILEEVENTS. See command ALTER SYNCUSER
for details on how to set these
options.
As mentioned above, both the destination and the source sync processes normally log
events to the source EMS collector. But if the destination sync process cannot access
the SLggguuu log file or the EMS log on the source system (because of a security error
for example), the destination sync process will log an event to the destination EMS
collector to report the error.
The default EMS collector is $0. To send events to an alternate collector, change the
EMSCOLLECTOR global parameter value. See the AUTOSYNC command ALTER
GLOBAL for a description of global parameters and details about changing them.