RDF System Management Manual for J-series and H-series RVUs (RDF 1.10)

To redirect messages from the current EMS log to the log named $EMSC (on the control subvolume
CHICAGO), enter:
]ALTER RDF LOGFILE $EMSC
The specified collector must reside on the local system. For example, if you are in an RDFCOM
session on the system \SANFRAN, you cannot specify something like \CHICAGO.$EMSC as the
log.
For more information about the EMS log, see Chapter 1 (page 27), Chapter 3 (page 62), Chapter 8
(page 176), and Chapter 9 (page 250).
RETAINCOUNT
The RETAINCOUNT purger process configuration attribute specifies how many image trail files
must be retained on disk for each image trail.
PURGETIME
The PURGETIME purger process configuration attribute specifies the number of minutes the purger
process waits between attempts to purge redundant image trail files. Altering this attribute causes
the purger to perform a purge pass immediately.
UPDATERDELAY
The UPDATERDELAY global configuration attribute specifies how many seconds the updater
processes should delay upon reaching the logical EOF in the image trail before attempting a new
read.
UPDATEROPEN
The UPDATEROPEN global configuration attribute specifies how the updaters open database files.
By default it is PROTECTED, but PROTECTED OPEN and SHARED are alternatives. See the discussion
on UPDATEROPEN in “Installing and Configuring RDF” (page 62). When you change
UPDATEROPEN online, the updater closes all its files and then restarts using the new UPDATEROPEN
attribute.
Reading Log Messages
RDF messages are sent to the EMS log (collector) specified during RDF configuration.
If RDF encounters an error while attempting to open or send a message to the configured log, RDF
takes the following actions:
1. RDF writes either of the following messages to the local $0 process:
"705 File Open Error error# filename"
"700 File System Error error# filename"
2. RDF then closes the log (if it is open). The log remains as configured.
The next time RDF needs to write a message to the log, RDF attempts to reopen the configured log.
If the error condition persists, RDF repeats the steps just described.
Examining RDF Messages
RDF/IMP and IMPX direct their command, event, warning, and error messages to an EMS collector
in the form of fully-tokenized messages.
You can peruse messages in the EMS log on your terminal screen by using Viewpoint or whatever
other tool you normally use for monitoring $0. When you do this, you are dealing with the entire
EMS log (not just RDF messages).
Each RDF event has Cause, Effect, and Recovery text associated with it. You can view this text from
the EMS collector's interface, or you can enter HELP and the RDF event number to an RDFCOM
prompt. For example,
Performing Routine Operational Tasks 109