SCF Reference Manual for G-Series RVUs (G06.24+)

Using SCF
SCF Reference Manual for G-Series RVUs520413-004
4-6
Modes of Operation
°
Using TACL INLINE. TACL INLINE (discussed in the TACL Reference Manual)
allows a user to write a TACL program to simulate a user at a terminal. The
INLINE facility is a special case of INV, in which the input variable is implicitly
formed by TACL from the lines with the INLPREFIX that is in effect.
°
Using TACL /INV/ as an alias. For example:
1. You push a variable on to the stack; for example:
#PUSH TEMP
2. You set the value for the variable; for example:
#SET TEMP CPUS \EAST
3. Then you can use the variable, for example, in an SCF command:
SCF /INV TEMP/
This causes SCF to run as if the command were
SCF CPUS \EAST
The mode is or becomes noninteractive
°
If you use an SCF command file as the / IN filename / parameter within the
command to run SCF. SCF command files are usually EDIT files that contain a
series of SCF commands.
°
If you use an OBEY command. The mode is noninteractive unless a line does
not contain a command. If a line invokes a command-mode utility but does not
supply a command, the mode becomes interactive and the user is prompted
for input.
Command file usage is explained under Changing the Input Source on
page 4-8.
°
If you use the OUT command or the / OUT file-spec / parameter within an
SCF command. For more information, refer to Changing the Output
Destination on page 4-9.
°
If you enter one or more SCF commands separated by semicolons; for
example:
> SCF LOG MYFILE; CPUS; LISTPM
This command is an example of what is sometimes called command-line
mode. Command-line mode is defined as a series of noninteractive mode
commands that have the same IN and OUT file; when command execution is
finished, control is returned to the same TACL prompt from where execution
started.
There are several differences between interactive and noninteractive mode:
Interactive mode defaults to ALLOW ALL errors and warnings.
Noninteractive mode defaults to ALLOW NO errors or warnings.