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

6-37
4 Running the SDCONV Program
Running the Program
Enter the following command to run the conversion utility:
RUN SDCONV.PUB.SYS
No file equations are required. However, if you wish to redirect input and/or report output, you may use
the file equations provided by the program.
When the program is successfully loaded, it issues the following banner
System Dictionary SDCONV HP32254v.uu.ff - (c) Hewlett Packard Co. 1985
You can start entering commands at the '>' prompt.
SDCONV Files
The Input File
As mentioned above, SDCONV can take input from an MPE file instead of $STDINX if a file exists with
the formal designator, SDIN. SDCONV takes input from this file one record at a time. SDIN should be a
fixed length record ASCII file with record size 80. The whole line of record is used for input; therefore, the
file should be unnumbered.
Note that the file output format for SDLOG (see "The Log File", next page) is fully compatible with the
input format of SDIN. Therefore, you can run a session of SDCONV, save and rename the log file, and
immediately use it as input without having to modify anything.
When file input is used, that particular session of SDCONV is considered to have a non-interactive input/
list pair with non-duplicative input. Therefore, the CONTROL Y trap is disabled, and the input is echoed
by SDCONV.
The List File
SDCONV opens $STDLIST for the output of the error and prompt messages. When running the program,
the "STDLIST = " clause can be used on the RUN command to redirect the $STDLIST output to a disc file.
When specifying "STDLIST = <old file name >", you should make sure that the file exists in the permanent
domain and that it is large enough to contain all the output. If you are creating a new file through
"STDLIST = <new file name >, NEW", make sure that the file does not exist either in the temporary
domain or in the permanent domain. When the program terminates, the file will be created both in the
temporary and permanent domain. The one in the temporary domain mainly contains the MPE file system
error messages, while the one in the permanent domain contains all the other output made by the
program.
The Output File
When the definition loading process begins, the destination System Dictionary domain is assumed to be
empty. Therefore, no conflict should occur during the loading process. However, if the domain is not empty
and conflicts do occur, SDCONV issues an error message for each conflict, and summarizes the error into a
file with formal designator SDOUT. When opening SDOUT, SDCONV first sees if a file equate exists for
SDOUT, or if SDOUT itself exists. If so, and if the input/list pair is interactive, a prompt is issued asking
whether or not to overwrite the old file. If the input/list pair is non-interactive, the old file is automatically
overwritten. If the old file does not exist, then the file equate, if any, is used to create an SDOUT file as a