RDF System Management Manual for H-Series RVUs (RDF 1.8)

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 35), Chapter 3 (page 73), Chapter 8
(page 173), and Chapter 9 (page 245).
RETAINCOUNT
The RETAINCOUNT purger process configuration parameter specifies how many image trail
files must be retained on disk for each image trail.
PURGETIME
The PURGETIME purger process configuration parameter specifies the number of minutes the
purger process waits between attempts to purge redundant image trail files. Altering this
parameter causes the purger to perform a purge pass immediately.
UPDATERDELAY
The UPDATERDELAY global configuration parameter specifies how many seconds the updater
processes should delay upon reaching the logical EOF in the image trail before attempting a new
read.
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
Previous RDF products directed their messages to a log device and a log file. RDF/IMP and IMPX,
however, 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).
To isolate RDF messages from the rest of the EMS log, you can use the standard EMS filter
RDFFLTO to produce an intermediate entry-sequenced file which you then can scan using the
RDFSCAN utility.
As noted earlier in this chapter, when you access RDFSCAN, this utility displays current
information about the RDF message file, including the number of the last record. This number,
presented in the following format, indicates the size of the message file so you can estimate where
to begin your scanning:
File: $SYSTEM.RDF.RDFLOG, current record: 9454, last record: 9466
Performing Routine Operational Tasks 117