HP 3000 Manuals HP 3000 Manuals
SDDBD'S FILES
The Input File
SDDBD accepts input from the file, SDIN. It can also take input from
another MPE file by redirecting SDIN with a file equation prior to
issuing the RUN command:
:FILE SDIN=input file
If SDIN does not exist, or has not been redirected to another file,
$STDINX (or your terminal) will be used as the input file.
The log file (see "The Log File" below) can be saved and renamed and then
used as the input file the next time SDDBD is run.
SDOUT Report File
SDDBD records the summarized information about the entities added,
replaced, etc., in a file with the formal file designator, SDOUT. SDOUT
can also be redirected to another MPE file by using the following file
equation:
:FILE SDOUT = output file
When SDDBD is run, if SDOUT is not found and there is no file equation
for SDOUT, then SDDBD creates SDOUT as a temporary file. Upon
termination of the program, the contents of this temporary file will be
output to $STDLIST, and the file is deleted thereafter.
On the other hand, if an old SDOUT is found, the user in session mode
will be asked to confirm overwriting of the old file. In jobs, the old
file is automatically overwritten.
SDOUT Report
When the output is formatted, each record in the report has the following
format:
<Entity name> <IMAGE Alias> <Entity type> <Attributes> <Action>
Attribute Output Format. Attributes are listed for the IMAGE data items,
data sets, and records. The format for each of these attribute types is
shown below.
Data Item Attribute Format. For IMAGE data items, the attributes are
formatted as follows:
<element-type> (<byte-length>, <display-length>, <count>)
Data Set Attribute Format. The attributes for data sets are formatted as
follows:
<image-dataset-type>
The available data set types are:
M for manual master data sets
A for automatic master data sets
D for detail data sets
Record Attribute Format. The attributes for records are formatted as
follows:
<blanks> (<byte-length>)
Action Report. SDOUT report lists the action that occurred for each
entity as it was encountered during the loading process. The Action
column in the report may show one of the values listed below:
SKIPPED The new definition was skipped because a SKIP was
requested for conflict occurrences.
REPLACED The existing definition was modified to the new
definitions' attribute values.
ADDED The new definition was successfully added to the System
Dictionary.
TERMINATED The loading process terminated at this entity because of
a conflict.The entity with the TERMINATED action was not
loaded.
ERROR An error has occurred while loading the definition.This
usually represents a more serious error.
OLD USED A compatible entity definition was found in the
dictionary, and the new entity definition was not
loaded. The relationships were still established using
the old definition.
The Log File
When SDDBD is executed, all valid commands are logged to a file with the
formal file designator, SDLOG. This enables you to save the commands and
use them at a later date.
The REDO command and any invalid commands are not logged, but the command
edited and executed through REDO is logged. In addition, any responses
to prompts (either valid or invalid) will be omitted from the log file.
When SDDBD is run in a session, if SDLOG already exists, SDDBD will ask
for permission to overwrite the old log file. If the response is
negative, logging is disabled. In batch mode, the old file is
automatically overwritten. If no old log file is found and no file
equation for SDLOG is found, SDDBD will create the file. This file is
temporary, however, and must be saved to become a permanent file. If
SDLOG is newly created, you will receive a message telling you to save
the file upon termination of the program.