HP 3000 Manuals HP 3000 Manuals
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 permanent file. If all of the
above fails, i.e., if no such a file exists, the error report information
is collected in a temporary file and listed to $STDLIST upon termination
of the program.
Conflicting entities will be reported in the following format:
< entity name > < entity type > < error message >
On the other hand, conflicting relationships are reported as follows:
< list of entities involved >< relationship class > < error message >
With the error report information in SDOUT, you are expected to make
necessary corrections to System Dictionary via the SDMAIN program. The
program is explained in the HP System Dictionary/XL SDMAIN Reference
Manual (32256-90001).
The Log File
SDCONV is equipped with a logging facility. The log file has the formal
designator SDLOG. It records your input, so that the same set of input
can later be used as input to SDCONV. You can also examine SDLOG to see
what commands were issued in the previous session of SDCONV. SDCONV first
searches the temporary domain for SDLOG. If it finds the file, it issues
a prompt asking whether or not to overwrite the old file. If you respond
negatively to the prompt, the logging facility is disabled during that
session of SDCONV.
If SDCONV finds no SDLOG in the temporary domain, it searches the
permanent domain. Again, if it is found, a prompt is issued asking
whether to overwrite it. If no SDLOG was found, it is created in the
temporary domain.
Note that, if you issue the REDO command (see Chapter 3) in an
interactive session, then the REDO command itself is not logged.
Instead, the command which was edited through the REDO command is logged.
Furthermore, invalid commands and passwords entered through password
prompting are not logged into SDLOG. If the log file was newly created, a
message informing you to save the temporary file is issued upon
termination of the program.