
FUP Overview
File Utility Program (FUP) Reference Manual—523323-014
1-4
Run Options
Run Options
The TACL environment includes a set of predefined commands—including the TACL
RUN command. You must use a run option when you start a FUP process with a
command file. The two run options that FUP uses most often are IN (for specifying an
input file) and OUT (for an output file).
Type the term
FUP
and the command file and run option you want, and press
RETURN:
In this example, the FUP process starts when you use a command file (ALLSUBS) and
run option (IN). The command in this example writes to the terminal because there is
no OUT file. After FUP executes the last command in the command file, control of the
terminal returns to TACL.
Using FUP Custom Files
FUP reads two files (FUPLOCL and FUPCSTM) before it issues its first prompt. This
allows you to create a customized FUP environment before entering any commands.
Both these files are standard FUP command files that contain ASCII text with valid
FUP commands.
FUP Custom File Guidelines
The FUPLOCL file must be in the current system subvolume, $SYSTEM.SYS
nn
(or $SYSTEM.SYSTEM). FUPLOCL lets you set a site-standard FUP environment.
The FUPCSTM file must be in the user’s logon subvolume. FUPCSTM lets
individual users set their own FUP environment.
Although FUP executes each command in the FUPLOCL and FUPCSTM files and
can execute any FUP command, custom files are most useful for setting
environment commands (such as CONFIGURE and SET) for a FUP session.
FUP executes any commands from the FUPLOCL file (if present) before it
executes any commands from the FUPCSTM file (if present).
If you are running FUP on a remote node, FUP looks for the custom files in the
appropriate subvolumes on the remote node.
Note.
For more information about the TACL RUN command, see the
TACL Reference Manual
.
1> FUP / IN ALLSUBS /
Caution.
For software product revisions (SPRs) earlier than T6553ABQ, FUP can cause a
processor halt if it receives a bad startup message. This situation occurs mainly when FUP is
started programmatically and the FUP STARTUPMESSAGE is accidentally corrupted, or when
FUP is started through SCF after the “DEFAULT STARTUP MESSAGE” gets corrupted when a
SYSTEM \system-name
is executed. To avoid this situation, install T6553ABQ or a later
SPR.