HP 3000 Manuals HP 3000 Manuals
SDUTIL's Files
SDUTIL uses the formal file designators SDIN as the input file, SDOUT as
the output file, and SDLOG as the response log file. File equates are
allowed for all of these files.
SDIN SDUTIL accepts input from the file SDIN. The default for
SDIN is $STDINX. Redirecting SDIN to a file causes
SDUTIL, whether executed in session or batch mode, to
accept input from the specified file. The specified
file must be an unnumbered file or SDUTIL will not
execute correctly. Redirection is achieved by using the
following MPE file equation:
:FILE SDIN = <command file>
The next time SDUTIL is executed, the input will be
accepted from the file, command file.
SDOUT SDUTIL's reporting information is written to the output
file called SDOUT. The default for this file is
$STDLIST, which for sessions is the terminal. The
reporting information may be redirected via the
following file equation:
:FILE SDOUT = <output file>
If the file does not exist, then SDUTIL will create a
permanent ASCII file with a record size of 80 bytes. If
the file already exists, then SDUTIL will ask for
permission to overwrite it.
SDLOG When SDUTIL is executed, all valid commands except the
REDO command are logged to the file SDLOG. A valid
command is a command without parse errors. If <Control
Y> is entered in the middle of a command, then the
entire command is not logged. SDLOG gives you the
foundation for running SDUTIL with previously inputted
commands.
When SDLOG is redirected to a file other than itself,
all input entered for that session will be saved in the
specified file. If the file does not exist, then SDUTIL
will build it as a temporary ASCII file with a
fixed-length record size 80 bytes. If the file already
exists, SDUTIL will ask for permission to overwrite it.
To improve performance, logging can be disabled by
redirecting SDLOG to $NULL. To redirect SDLOG to a file,
use the following MPE commands:
:FILE SDLOG = <command file>
:RUN SDUTIL.PUB.SYS
If SDLOG is not redirected, or is redirected to a
temporary file, it is only session temporary. An MPE
SAVE command may be used to save SDLOG as a permanent
file, as shown in the following example.
:RUN SDUTIL.PUB.SYS
:SAVE SDLOG
:RENAME SDLOG,LOGFILE
The file LOGFILE now contains the previously entered
input.
SDMCOM When you are merging a version to another existing
version, the target version may contain extra
occurrences that do not exist in the source version. If
you preview the merge process, SDMAIN commands to delete
the extra occurrences will be generated and stored in
the file SDMCOM. This file may then be used as input to
SDMAIN to delete the extra occurrences without having to
enter SDMAIN commands manually.
If SDMCOM does not exist, SDUTIL will create it as a
fixed length permanent file with record size 80 bytes.
If it does already exist, SDUTIL will ask for permission
to purge and re-create it. Note that this command
generation feature can be disabled by redirecting SDMCOM
to $NULL. SDCOM may be redirected to a file via the
following file equation:
:FILE SDMCOM = <command file>