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

To run RDFCOM and execute the commands in this file, supply the command file name in the IN
option of the command to start RDFCOM:
4> RDFCOM /IN RDFSET/ control-subvolume
When it uses a command file in this way, RDFCOM works in batch mode: RDFCOM begins the
session, reads and executes each command from the command file, and displays the associated
output at your terminal. When RDFCOM reaches the end of the command file or encounters an
EXIT command within that file, RDFCOM terminates the session and returns control to TACL. If
RDFCOM encounters an error while reading the command file, RDFCOM displays an error message,
terminates the session, and returns control to TACL.
If you include both the IN and OUT options in the RDFCOM command, RDFCOM reads commands
from the command file specified by the IN option and directs all output to the destination specified
by the OUT option. For example, the following command causes RDFCOM to read commands
from the command file COMFILE1 and list the output to the printer $LP:
5> RDFCOM/IN COMFILE1, OUT $LP/ control-subvolume
In addition, you can execute the contents of a command file within an interactive RDFCOM session
by using the RDFCOM OBEY command. If you regularly use a series of sequential RDF operations
in your interactive sessions, for instance, you might want to specify these in a command file. Then
each time you need these operations, you can execute them with a single OBEY command rather
than with multiple individual RDFCOM commands.
As an example, many users find that initializing RDF is much easier and more consistent when
done using command files. Suppose you have created a command file named RDFINIT that contains
the commands for initializing the subsystem. You could execute all these commands by simply
entering:
]OBEY RDFINIT
If you decide later that you want to use different installation attributes, you can change the command
file and then enter the OBEY command again. Using command files makes performing repeated
tasks very convenient.
During processing of an OBEY command, when RDFCOM reaches the end of the command file,
RDFCOM prompts you for another RDFCOM command. If RDFCOM encounters an EXIT command
within the command file, RDFCOM terminates the session and returns control to TACL. If RDFCOM
encounters an error while reading the command file, RDFCOM displays an error message, and
prompts you for another RDFCOM command.
NOTE: Previously you could not put the RDFCOM takeover command into an RDFCOM script
file because that command prompted the user several times before it executed. By using the new
! option to the takeover command, you can now put the takeover command into a script file with
the ! option because the ! option eliminates the prompts. For more information, see the Takeover
command in “Entering RDFCOM Commands” (page 176) .
Using Scripts for Easy and Fast RDF Initialization and Configuration
In the discussion above, you have learned how to use RDF command scripts for RDFCOM operations
and how to use an IN file to execute a list of RDFCOM commands. Here is a highly convenient
way to use both of these methods to initialize and configure an RDF subsystem. You create an EDIT
file with the following TACL commands that you want executed on your primary system \Boston.
fup purge $system.BOSTON.*!
fup purge \SF.$system.BOSTON.*!
rdfcom; initialize rdf,backupsystem \SF!
rdfcom /in $system.boston.rdfcfg/
rdfcom; start rdf
You would execute this command as an OBEY file to your TACL prompt. For this example, assume
you have been running an RDF subsystem where \Boston is your primary system and \SF is your
Running RDFCOM 95