HP 3000 Manuals HP 3000 Manuals
DICTDBL
Database Load Utility
The Database Load utility (DICTDBL) reloads the contents of an IMAGE
database. A comparison between the old and the new schemes is made
before the loading process begins. If changes have been made, you are
prompted to enter the changed information. Additionally, you can
selectively reload the database, that is, you are given a choice to load
or not to load a particular data set.
When the utility program completes the loading process, you are provided
an audit report containing information about the database load. The
following description tells how to execute the DICTDBL utility program
and gives an explanation of each prompt.
To execute this utility enter the following MPE command:
RUN DICTDBL.PUB.SYS
After an acknowledgement message, the utility program issues the
following prompt:
STORE FILE>
If the store file is a disc file, enter the file's name as your response
to the prompt. An error message is issued if the named file cannot be
found and the prompt is reissued. If the store file is a tape file,
press [[RETURN]] as your response to this prompt. Before generating a
tape request at the system console, the utility prompts you as follows:
TAPE FILE REQUESTED(Y/N)?>
If you enter a "Y" or [[RETURN]], a request to mount a tape is issued on
the system console; otherwise, the prompt for STORE FILE is reissued.
When the utility completes the loading process, it generates an audit
report of the loading process. You can specify where the report is to be
sent with the following prompt:
LIST FILE>
Enter one of the following options in response to the above prompt:
LP sends the audit listing to the line printer. If there
is no device LP configured on your system, use a file
equation to redirect DICTLIST to another device.
NULL suppresses the audit listing.
filename sends the audit listing to the existing or to a new disc
file. Before over-writing an existing file, you are
prompted to approve purging the existing file's
contents.
*filename sends the listing to the file identified in the back
referenced equation.
Pressing [[RETURN]] in response to this prompt sends the audit listing to
your terminal.
After accepting your response to the prompt for LIST FILE, the utility
displays the stored database's name, then prompts you to select a RUN
MODE for the loading process. The RUN MODE is the operating mode to be
used to load the database. The prompt is as follows:
RUN MODE(LOAD/EDIT/SHOW/EXIT)>
In response to the prompt, you can choose one of four options, which have
the following meaning:
LOAD indicates the named database is to be loaded.
EDIT indicates the named database is to be loaded and editing
prompts issued for each data set.
SHOW indicates the named database is not to be loaded, but
the schema and set entry counts are to be displayed.
EXIT indicates the utility is to be terminated.
Pressing [[RETURN]] in response to this prompt indicates that the default
for RUN MODE is used, which is LOAD. In an operating mode of LOAD, you
are prompted for information only when schema changes are encountered.
In the EDIT mode, you can select an operating mode for the data sets. An
operating mode for a data set is similar to the operating mode for a
database. Next, the utility prompts you to enter the new name for the
data base with the following prompt:
NEW BASE NAME>
If the name of the stored database has not changed, including qualifier
information such as MPE group and account, press [[RETURN]] as your
response; otherwise, enter the new name for the database.
If the named database cannot be found, the following prompt is issued:
BASE NOT FOUND>
This prompt indicates that the identified database, either from the
stored file or entered in response to NEW BASE NAME, cannot be found.
You should re-enter the base name in response to this prompt. If the
prompt is reissued, terminate the program by entering [[RETURN]] and make
sure the database is where you think it is.
When the named database is found, you are prompted for additional
database information as follows:
BASE PASSWORD>
MODE>
The password you enter in response to the password prompt should be one
that allows modify access to the database. This password is not
displayed as you enter it. If the password grants only partial access to
the database, the utility will load only those parts of the database to
which it has access; no warning is given. If the password is entered
incorrectly or does not grant modify access, a database operation error
occurs during the loading process. The utility issues the following
questions if a database operation error occurs:
DISPLAY INPUT RECORD(Y/N)?>
CONTINUE SET LOAD(Y/N)?>
CONTINUE LOAD PROCESS(Y/N)?>
You can write the contents of the record to the indicated LIST FILE by
entering a "Y" or [[RETURN]].
If you choose to continue the set load, the data entry in error is not
loaded. If you choose not to continue, the utility allows you to
continue loading the remaining sets in the database with the last prompt.
Your response to MODE indicates the access mode to be used to open the
database. Valid responses include 1, 2, 3, 4, and [[RETURN]]. Pressing
[[RETURN]] indicates acceptance of the default mode, which is 3. (See
the IMAGE/3000 Reference Manual for "Access Modes" .)
With the next prompt, you are given the choice to load in a fast I/O mode
or not. The prompt is:
FAST I/O(Y/N)?>
FAST I/O means that the database buffers are not written at each
modification.
The program begins to load the database after the FAST I/O prompt. If
you chose LOAD as the operating mode for the database, you are prompted
only when a difference between the old and new schema is encountered. If
you chose EDIT as the operating mode, the following prompt is issued
before the program loads each data set:
SET MODE(LOAD/EDIT/SKIP/CONT/EXIT)>
You can choose only one of the modes. A description for each is as
follows:
LOAD indicates that if a difference between the old and new
schema occurs, issue prompts for the changed
information.
EDIT allows you to change the name of the data set and/or
data elements during the loading operation.
SKIP allows you to indicate that a data set is not to be
loaded.
CONT cancels the EDIT operation mode for the database, in
which case the default of LOAD is used.
EXIT indicates the utility program is to be terminated.
Pressing [[RETURN]] in response to this prompt indicates
the default of LOAD is used.
When the message LOAD COMPLETED is displayed, the program execution is
terminated and the audit report is sent to the file indicated with the
LIST FILE prompt.
The following examples show how to execute the Database Load utility
program with an explanation of the responses given to the prompts. The
examples show choosing a database operating mode of LOAD and of EDIT. The
example using an operating mode of EDIT also shows choosing a data set
operating mode of EDIT and of LOAD. The last example shows the audit
report generated by the utility program for the database load.
Example
The following is an example of LOAD Run Mode:
:RUN DICTDBL.PUB.SYS How to execute this utility.
<The Dictionary/3000 DB Loader program banner appears here.>
STORE FILE> TEMP Name of file containing the
contents of the stored base.
LIST FILE> [[RETURN]] sends report to terminal.
BASE: SHPMGT.PUB.HOWE Utility identifies base to load.
RUN MODE(LOAD/EDIT/SHOW/EXIT)> LOAD LOAD selected.
NEW BASE NAME> SHPMGT.DEMO Changing the MPE group for base.
BASE PASSWORD> MANAGER was the password used.
MODE> 1 Opened for shared modify access.
PRODUCT-MASTER M 22/101 First data set to be loaded.
PRODUCT-NO : ITEM NOT FOUND, NEW ITEM NAME> PROD-NO LOAD issues
22 ENTRIES LOADED IN <1 CPU-SEC prompt when old
and new schemes
ITEM-MASTER M 44/311 differ.
44 ENTRIES LOADED IN 1 CPU-SEC
EXPLODE D 397/1054
PRODUCT-NO : ITEM NOT FOUND, NEW ITEM NAME> PROD-NO
397 ENTRIES LOADED IN 20 CPU-SECS
LOAD COMPLETED
END OF PROGRAM
The following is an example of EDIT Run Mode:
:RUN DICTDBL.PUB.SYS How to execute this utility.
<The Dictionary/3000 DB Loader program banner appears here.>
STORE FILE> TEMP Name of store file.
LIST FILE> [[RETURN]] sends report to terminal.
BASE: SHPMGT.PUB.HOWE Program identifies base to load.
RUN MODE(LOAD/EDIT/SHOW/EXIT)> EDIT Editing prompts at set level
requested.
NEW BASE NAME> SHPMGT.DEMO Loading to a different MPE group.
BASE PASSWORD> MANAGER is password used.
MODE> 1 Opened for shared modify access.
PRODUCT-MASTER M 22/101 First data set to be loaded.
SET MODE(LOAD/EDIT/SKIP/CONT/EXIT)> EDIT Set level editing capability.
PRODUCT-MASTER : NEW SET NAME> If the data set and/or items
PRODUCT-NO : NEW ITEM NAME> PROD-NO have new names, enter new
DESCRIPTION : NEW ITEM NAME> name after prompt as for
QTY-ON-HAND : NEW ITEM NAME> PROD-NO.
QTY-ALLOCATED : NEW ITEM NAME>
UNIT-COST : NEW ITEM NAME>
LIST-PRICE : NEW ITEM NAME>
22 ENTRIES LOADED IN <1 CPU-SEC
ITEM-MASTER M 44/311 Next data set to be loaded.
SET MODE(LOAD/EDIT/SKIP/CONT/EXIT)> LOAD No editing prompts generated
44 ENTRIES LOADED IN 1 CPU-SEC by choosing LOAD.
EXPLODE D 397/1023 Next data set to be loaded.
SET MODE(LOAD/EDIT/SKIP/CONT/EXIT)> LOAD
PRODUCT-NO : ITEM NOT FOUND, NEW ITEM NAME> PROD-NO LOAD causes
397 ENTRIES LOADED IN 20 CPU-SECS prompts when
old and new
LOAD COMPLETED schemes differ.
END OF PROGRAM
The following is an example of Audit Listing:
<The Dictionary/3000 DB Loader program banner appears here.>
DATABASE LOAD FROM STORE FILE TEMP.PUB.MARTIN
BASE: SHPMGT.PUB.HOWE
LOADED TO: SHPMGT.DEMO.MARTIN
PRODUCT-MASTER M 22/101
ITEM PRODUCT-NO LOADED TO PROD-NO
22 ENTRIES LOADED IN <1 CPU-SEC
ITEM-MASTER M 44/311
44 ENTRIES LOADED IN 1 CPU-SEC
EXPLODE D 397/1023
ITEM PRODUCT-NO LOADED TO PROD-NO
397 ENTRIES LOADED IN 19 CPU-SECS
LOAD COMPLETED