QIO Configuration and Management Manual

QIO Subsystem SCF Commands
QIO Configuration and Management Manual—424717-008
4-5
Output Destinations
system name and volume name are the default names currently in use by the TACL
command interpreter through which the RUN command was entered):
19> SCF / IN $DATA.SCF.STARTUP /
If you run SCF from TACL without specifying an input file, SCF assumes that the input
is coming from your terminal.
Output Destinations
SCF can direct output to a disk file, an application process, a terminal, or a printer. The
initial output destination is determined by the form of the RUN command used to
initiate SCF. The output destination can be changed dynamically during an SCF
session.
To specify an initial output destination for an SCF session, use the OUT option of the
RUN command. You can specify a terminal (identified by its logical-device name), a
disk file, an application process, or a printer. For example, the following RUN command
initiates SCF and directs it to send its output to a disk file named $DATA.SCF.DISPLAY
(if not specified, the system name and volume name are the default names currently in
use by the TACL command interpreter through which the RUN command was entered):
20> SCF / OUT $DATA.SCF.DISPLAY /
If you run SCF without specifying an output file, SCF assumes that the output is being
sent to your terminal.
Running SCF
This section describes how to start SCF, how to control its input and output files, and
the general format of SCF commands.
You can start SCF interactively by using the TACL command interpreter RUN
command or by using a command (OBEY) file (or TACL macro or routine). The RUN
command used to start SCF is described in this section. The QIO SCF commands are
described later in this section.
SCF can accept input from a terminal or a disk file. You can change the input source
dynamically by using the OBEY command.
SCF resides in a file named $SYSTEM.SYSTEM.SCF. To start SCF, use the TACL
RUN command. For more information on RUN command, see the TACL Reference
Manual.
General Command Format
An SCF command always begins with a keyword identifying the command (such as
START, VERSION, or TRACE).
If the command pertains only to the current SCF session, the keyword is followed
immediately by whatever additional parameters are required to specify the action to be
taken by SCF. For example, the SYSTEM command can be entered as