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

Recovery: Consult the description of the PROCESS_CREATE_
procedure in the Guardian Procedure Calls Reference
Manual to determine the cause of the failure.
Once the underlying cause is corrected, RDF
can be restarted.
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
NOTE: The record numbers reflected by RDFSCAN are approximate and might not exactly
match the record numbers that would be displayed by a FUP INFO RDFLOG, STAT command.
With RDFSCAN you can specify:
• A starting point within the message file
• The number of records to retrieve
• Text to search for in the message file
RDFSCAN displays those RDF messages that meet the criteria you specify.
The following is a sample display for a primary system. (The column numbers in the top line do
not appear in the display, and are included only for reference. )
(1) (2) (3) (4) (5) (6)
2004/06/09 16:10:51 \LA $MON1 731 RDF Monitor Started
2004/06/09 16:11:08 \LA $Z333 774 RDF Local Extractor Started
The following is a sample display for a backup system. (The column numbers in the top line do not
appear in the display, and are included only for reference. )
(1) (2) (3) (4) (5) (6)
2004/06/09 16:11:02 \NYC $Z011 771 RDF Remote Receiver Started
2004/06/09 16:11:25 \NYC $Z012 773 RDF Remote Updater Started
$LOST -> $BLOST
2004/06/09 16:11:32 \NYC $Z013 773 RDF Remote Updater Started
$BIG -> $BBIG
2004/06/09 16:11:52 \NYC $Z014 773 RDF Remote Updater Started
$POPPY -> $BPOPPY
In the preceding displays, the individual columns present this information:
Date-—is the date the message occurred, as reflected on the sending system.(1)
Time—is the time the message occurred, as reflected on the sending system.(2)
System—is the name of the system where the RDF process to which this message pertains is running.(3)
RDF Process—is the name of the RDF process to which the message pertains.(4)
Message Number—is the number that identifies the RDF message and its meaning.(5)
Message Text—is the descriptive text that appears in the message.(6)
The following sample RDFSCAN session shows another example of how you might use RDFSCAN
to examine messages in an RDF message file. The actual line length for RDFSCAN is 132 columns
(not 58 as shown in this example). On the terminal screen, lines over 80 columns long wrap to
108 Operating and Monitoring RDF