Restructuring the ORDERS Database [ DBChange Plus User's Guide ] MPE/iX 5.0 Documentation
DBChange Plus User's Guide
Restructuring the ORDERS Database
Following is an example of the messages the DBAPLUS program sends to your
terminal when it is performing the restructure interactively. In this
example, the DBAPLUS program is restructuring the ORDERS database:
>perform commands
Please wait.....change file is being verified.
PERFORM COMMANDS now or create job file [job/y/N]? y
Please wait ...
HP36386 (A.00.00) DBALTER (c) COPYRIGHT Hewlett-Packard Co. 1985
MON, JAN 8, 1990, 11:18 AM
Database has been modified since last DBSTORE (DBA 220).
Continue [y/N] ? y
PAGE 1 HEWLETT-PACKARD 30391C.00.52 TurboIMAGE/3000: DBSCHEMA
MON, JAN 8, 1990, 11:18 AM (C) HEWLETT-PACKARD CO. 1987
BEGIN DATABASE ORDERS;
PASSWORDS:
11 CREDIT ;
:
NUMBER OF ERROR MESSAGES: 0
ITEM NAME COUNT: 26 DATA SET COUNT: 6
ROOT LENGTH: 1176 BUFFER LENGTH: 561 TRAILER LENGTH: 256
ROOT FILE ORDERS CREATED.
New database schema is saved as temporary file ORDERSSC
Data set CUSTOMER : No conversion necessary.
Data set DATE-MASTER : No conversion necessary.
Data set PRODUCT : No conversion necessary.
Data set SUP-MASTER : No conversion necessary.
Data set SALES : No conversion necessary.
Data set INVENTORY : No conversion necessary.
HP36386 (A.00.00) DBCHANGE (c) COPYRIGHT Hewlett-Packard Co. 1985
>
In the previous example, the DBAPLUS program was able to find enough disk
space to create all the temporary files before beginning the restructure.
However, if the DBAPLUS program is unable to create all the temporary
files before beginning the restructure, the message delivered to the
terminal reveals at what point in the process the DBAPLUS program ran out
of disk space. The message the DBAPLUS program displays will be exactly
the same as the previous message until the DBAPLUS program begins to
build temporary files.
The following example illustrates what happens when the DBAPLUS program
attempts to create a temporary file for the data set BRANCH-STORES. The
example begins just after the new schema has been displayed on the
screen.
:
DATA SET TYPE FLD PT ENTR MED CAPACITY BLK BLK DISC
NAME CNT CT LGTH REC FAC LGTH SPACE
CUSTOMER M 9 1 43 54 221 10 541 128
DATE-MASTER A 1 3 3 26 211 19 496 64
PRODUCT M 3 2 16 33 307 16 529 112
SALES D 9 4 24 40 504 14 561 192
SUP-MASTER M 5 1 31 42 211 12 505 80
INVENTORY D 6 3 20 32 450 15 481 128
BRANCH-STORES D 5 2 24 32 225 15 481 64
TOTAL DISC SECTORS INCLUDING ROOT: 768
NUMBER OF ERROR MESSAGES: 0
ITEM NAME COUNT: 26 DATA SET COUNT: 6
ROOT LENGTH: 1176 BUFFER LENGTH: 561 TRAILER LENGTH: 256
ROOT FILE ORDERS CREATED.
New database schema is saved as temporary file ORDERSSC
Data set CUSTOMER : No conversion necessary.
Data set DATE-MASTER : No conversion necessary.
Data set PRODUCT : No conversion necessary.
Data set SUP-MASTER : No conversion necessary.
Data set SALES : No conversion necessary.
Data set INVENTORY : No conversion necessary.
DBAPLUS has tried to create all the necessary temporary data sets
before beginning the restructuring process and has run out of disk
space. You can:
1) exit DBAPLUS and obtain more disk space or remove some of the
changes in the change file with DBChange and run DBAPLUS again.
2) ask DBAPLUS to try again using a second restructuring method.
This method creates one temporary data set at a time. The
original data set is purged when the changes for that set are
successfully processed. Although this requires less disk space,
there is no guarantee that there is enough disk space for the
entire restructure.
If you receive the preceding message, choose one of the two options given
to complete the restructure. If you choose method 2, be sure you have a
backup copy of the database.
MPE/iX 5.0 Documentation