HP System Dictionary/XL General Reference Manual Vol 2 - Part 1 SDINIT (32256-90005)

10- 79

8 Running the SDUTIL Program

Overview

This chapter provides infor mation about the ﬁles needed to run SDUTIL and detailed instructions on

using SDUTIL in either session or batch mode, entering SDUTIL commands, and how to use the compile

and merge functions of the SDUTIL program.

SDUTIL's Files

SDUTIL uses the formal ﬁle designators SDIN as th e input ﬁle, SDOUT as the output ﬁle, and SDLOG as

the response log ﬁle. File equates are allowed for all of these ﬁles.

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 ex-

ecute correctly. Redirection is achieved by using the following MPE file equation:

:FILE SDIN = <command ﬁle>

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 ﬁle>

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

forpermission to overwrite it.Toimprove performance, logging canbe disabled by redirecting

SDLOG to $NULL. To redirect SDLOG to a file, use the following MPE commands:

:FILE SDLOG = <command ﬁle>

:RUN SDUTIL.PUB.SYS

If SDLOG is not redirected, o r 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