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

PROCESS process-name
specifies the process name for the receiver process; process-name is any unique, valid
process name of up to six characters; the first character must be a dollar sign ($). You cannot
specify any of the reserved process names listed in the Guardian Procedure Calls Reference
Manual. Names longer than six characters, including the $ sign, are invalid.
This parameter is not optional. You must explicitly name the receiver process.
FASTUPDATEMODE {ON | OFF}
FASTUPDATEMODE used to be known as SLOWMODE. During normal processing, the updaters’
RTD values are typically 0 to 20 seconds behind the extractor’s RTD value. This is expected
and normal behavior, although if 20 it does not necessarily mean that the updaters are in fact
running 20 seconds behind the extractor nor does it mean it will take 20 seconds for the
updaters to catch up. The updaters cannot read past what the receiver deems safe, and that
is determined by the frequency with which the receiver updates its context records. The receiver
normally updates its context records every 5 to 15 seconds, and the updaters’ RTD values
reflect that interval.
Some customers prefer the updaters to have the lowest possible RTD value at all times. This
can be accomplished by setting FASTUPDATEMODE ON.
With FASTUPDATEMODE ON, the receiver updates its context records after processing each
extractor message buffer. This enables the updaters to read and apply image records much
faster. It also, however, slows the extractor-to-receiver throughput rate. You should only specify
FASTUPDATEMODE ON if your throughput rate is typically low to moderate. In environments
with high extractor-to-receiver throughput, specifying FASTUPDATEMODE ON will cause the
extractor to fall behind TMF audit generation. See “Installing and Configuring RDF” (page 62)
for a more complete discussion of this option, and note that for FASTUPDATEMODE to achieve
what you want, you must also set the RDF UPDATERDELAY to 1 second.
The default is FASTUPDATEMODE OFF.
Where Issued
Primary system only.
Security Restrictions
None.
RDF State Requirements
None.
Usage Guidelines
The SET RECEIVER command enters the parameter values specified for the receiver in this command
into the RDF configuration table in memory. This table serves as an input buffer only, and so these
values do not affect the subsystem until they are applied to the RDF configuration file with the ADD
command.
For ATINDEX values greater than 0, the specified value must match the audit trail number of a
configured auxiliary audit trail. If you specify SET RECEIVER ATINDEX 2, for example, there must
be a configured auxiliary audit trail AUX02.
222 Entering RDFCOM Commands