HP 3000 Manuals HP 3000 Manuals
Schema Processor Output
The Schema Processor prints the following heading on the first page of
the listing:
[REV BEG]
PAGE 1 HEWLETT-PACKARD 30391C.05.00 TurboIMAGE/3000: DBSCHEMA
MON, JAN 10, 1994, 3:32 PM (C) HEWLETT-PACKARD CO. 1987
[REV END]
If your standard output device ($STDLIST) is different from the list
file, an abbreviated product identification is also printed on $STDLIST.
Subsequent pages of the list file are headed by a page number, the
database name if it has been encountered, and the title most recently
specified by a $TITLE or $PAGE command.
If the LIST option is active, a copy of each record of the schema is sent
to the list file. However, if the text file and list file are the same,
as for example they are when you enter the schema source from your
terminal in session mode, the records are not listed. If you are
entering the schema in this way, the Schema Processor prompts for each
line of input with a right angle bracket (>).
Summary Information
After the entire schema has been scanned, several types of summary
information can be printed on the list file.
* If some of the items defined in the item part are not referenced
in the set part, and if no errors are encountered, the message
UNREFERENCED ITEMS:list of items is printed to the list file. The
list includes all items defined but not referenced in a data set.
Although they are not considered errors, these extraneous items
should be removed to reduce the size of the tables in the root
file and the size of the control blocks used by the library
procedures.
* If no errors are detected in the schema, the Schema Processor
prints a table of summary information about the data sets. Figure
3-4 contains a sample printout of this information. Table 3-7
describes the information contained in the summary. The
NOTABLE parameter of the $CONTROL command suppresses printing of
this table.
[REV BEG]
_________________________________________________________________________
| |
| DATA SET TYPE FLD PT ENTR MED MAXIMUM BLK BLK DISC |
| NAME CNT CT LGTH REC CAPACITY FAC LGTH SPACE|
| |
| |
| EMPLOYEE M 4 1 7 17 500 30 512 72 |
| PROJECT-MASTER M 2 1 10 20 75 19 382 15 |
| LABOR D 4 2 10 18 20048 28 506 1436 |
| INITIAL CAPACITY: 10024 INCREMENT ENTRIES: 2016 |
| |
| |
| TOTAL DISC SECTORS INCLUDING ROOT: 1532 |
| |
_________________________________________________________________________
Figure 3-4. Data Set Summary Table
[REV END]
Table 3-7. Data Set Summary Table Information
--------------------------------------------------------------------------------------------
| | |
| Headings | Description |
| | |
--------------------------------------------------------------------------------------------
| | |
| DATA SET NAME | The name of the data set. |
| | |
--------------------------------------------------------------------------------------------
| | |
| TYPE | A for automatic, M for manual, or D for detail. |
| | |
--------------------------------------------------------------------------------------------
| | |
| FLD CNT | The number of data items (fields) in each entry of the data |
| | set. |
| | |
--------------------------------------------------------------------------------------------
| | |
| PT CT | Path count. For a master data set, this is the number of |
| | paths specified for the data set key item. For a detail |
| | data set, it is the number of search items defined for the |
| | data set. |
| | |
--------------------------------------------------------------------------------------------
| | |
| ENTR LNGTH | The length in halfwords of the data portion of the data |
| | entry (not including any of the TurboIMAGE/XL pointers or |
| | structure information associated with a data entry). |
| | |
--------------------------------------------------------------------------------------------
| | |
| MED REC | The total length in halfwords of a media record of the data |
| | set. This length includes the entry length plus any of the |
| | TurboIMAGE/XL pointers associated with the data entry. |
| | Media records are discussed in chapter 10.[REV BEG] |
| | |
--------------------------------------------------------------------------------------------
| | |
| MAXIMUM CAPACITY | The maximum number of entries allowed in the data set. For |
| | detail data sets, this number can differ from the number of |
| | entries specified in the schema itself, because the capacity |
| | of each detail is adjusted to represent an even multiple of |
| | the blocking factor (see below). |
| | |
--------------------------------------------------------------------------------------------
| | |
| BLK FAC | The number of media records that are blocked together for |
| | transfer to and from the disk. |
| | |
--------------------------------------------------------------------------------------------
| | |
| BLK LGTH | The total length in halfwords of the physical block as |
| | defined in BLK FAC. This includes the media records and a |
| | bit map. Bit maps are discussed in chapter 10. |
| | |
--------------------------------------------------------------------------------------------
| | |
| DISC SPACE | The amount of disk space occupied by the MPE/iX file |
| | containing the data set. |
| | |
--------------------------------------------------------------------------------------------
| | |
| INITIAL CAPACITY | The number of entries for which space will be initialized |
| | when the detail data set is created. |
| | |
--------------------------------------------------------------------------------------------
| | |
| INCREMENT ENTRIES | The number of entries by which the detail data set will be |
| | expanded each time its space is exhausted. |
| | |
--------------------------------------------------------------------------------------------
| | |
| TOTAL DISC SECTORS | The total number of disk sectors that will be occupied by |
| INCLUDING ROOT: nnnn | the database when created using the DBUTIL program. |
| | |
--------------------------------------------------------------------------------------------
[REV END]
* Two lines of summary totals are printed on the list file. For
example:
NUMBER OF ERROR MESSAGES: 0
ITEM NAME COUNT: 23 DATA SET COUNT: 6
The error count includes both errors in the schema and in the
Schema Processor commands. The error count is also sent to
$STDLIST if it is different from the list file.
* If no schema syntax or logical errors are encountered, a third
line is printed. The form of this line is:
ROOT LENGTH: r BUFFER LENGTH: b TRAILER LENGTH: t
ROOT LENGTH is the length in halfwords of the body of the root
file. BUFFER LENGTH is the length in halfwords of each of the
data buffers (unused by TurboIMAGE/XL but provided for
compatibility with TurboIMAGE on MPE V; refer to the discussion on
buffer specifications in appendix H). TRAILER LENGTH is the length
in halfwords of an area in the control block used by TurboIMAGE/XL
to transfer information to and from a calling program's stack.
* If no errors are detected and the ROOT option is active, the
following message is sent to the list file:
ROOT FILE database name CREATED
where database name is the name given in the BEGIN DATABASE
statement in the schema.
[REV BEG]
* The initial capacity and increment entries are optional
parameters. If dynamic expansion is required, include these
parameters when defining the detail data set (See chapter 3.) For
existing databases, use DBChange Plus or other third-party tools
you may be using to specify the expansion parameters. For more
information, refer to MPE/iX Release 5.0 Communicator.
[REV END]
Schema Errors
When the Schema Processor detects an error, it prints a message to the
list file. If the LIST option is active, it is printed immediately after
the offending statement. If NOLIST is active, the current line of the
schema is printed, followed by the error message.
Schema Processor error messages are explained in appendix A. The root
file is not created if any of the listed errors are detected. However,
the Schema Processor attempts to continue checking the schema for logical
and syntactical correctness.
One error can obscure detection of subsequent errors, particularly if it
occurs early in a data set. It may be necessary to process the schema
again after the error is corrected to find subsequent errors.
Conversely, some errors early in the schema can generate subsequent
apparent errors which will disappear after the original error has been
corrected.
If schema errors prohibit creation of the root file, the following
message is sent to the list file and to $STDLIST if it is not the same as
the list file:
PRECEDING ERRORS -- NO ROOT FILE CREATED
A few conditions, including the number of errors exceeding the total
number allowed, cause immediate termination of the Schema Processor
without the normal summary lines. In this case, the following message is
printed:
SCHEMA PROCESSING TERMINATED
Schema Processor Example
Figure 3-5 contains the list file output printed when the schema of
the sample ORDERS database is processed. The database has 5 passwords
and contains 23 data item definitions and 6 data set definitions. The
Schema Processor summary information is printed following the schema.
[REV BEG]
_____________________________________________________________________________
| |
| PAGE 1 HEWLETT-PACKARD 30391C.05.00 TurboIMAGE/3000: DBSCHEMA |
| MON, JAN 10, 1994, 3:32 PM (C) HEWLETT-PACKARD CO. 1987 |
| |
| $CONTROL LIST,LINES=46 |
| $PAGE "SCHEMA FOR DATABASE ORDERS" |
| |
| BEGIN DATABASE ORDERS; |
| |
| PASSWORDS: |
| 11 CREDIT; << CUSTOMER CREDIT OFFICE >> |
| 12 BUYER; << BUYER - RESPONSIBLE FOR PARTS INVENTORY >> |
| 13 SHIP-REC; << WAREHOUSE - SHIPPING AND RECEIVING >> |
| 14 CLERK; << SALES CLERK >> |
| 18 DO-ALL; << FOR USE BY MGMT >> |
| |
| ITEMS: << IN ALPHABETICAL ORDER FOR CONVENIENCE >> |
| ACCOUNT, J2 ; << CUSTOMER ACCOUNT NUMBER>> |
| BINNUM, Z2 (/13); << STORAGE LOCATION OF PROD>> |
| CITY, X12 (12,13,14/11); << CITY>> |
| CREDIT-RATING, R2 (/14); << CUSTOMER CREDIT RATING>> |
| DATE, X6 ; << DATE (YYMMDD)>> |
| DELIV-DATE, X6 (/14); << DELIVERY DATE (YYMMDD)>> |
| DESCRIPTION, X20 ; << PRODUCT DESCRIPTION>> |
| FIRST-NAME, X10 (14/11); << CUSTOMER GIVEN NAME>> |
| INITIAL, U2 (14/11); << CUSTOMER MIDDLE INITIAL>> |
| LAST-NAME, X16 (14/11); << CUSTOMER SURNAME>> |
| LASTSHIPDATE, X6 (12/ ); << DATE LAST REC D(YYMMDD)>> |
| ONHANDQTY, J2 (14/12); << TOTAL PRODUCT INVENTORY>> |
| PRICE, J2 (14/); << SELLING PRICE (PENNIES)>> |
| PURCH-DATE, X6 (11/14); << PURCHASE DATE (YYMMDD)>> |
| QUANTITY, I (/14); << SALES PURCHASE QUANTITY>> |
| STATE, X2 (12,13,14/11); << STATE -- 2 LETTER ABB>> |
| STOCK#, U8 ; << PRODUCT STOCK NUMBER>> |
| STREET-ADDRESS, X26 (12,13,14/11); << NUMBER AND STREET ADDRESS>> |
| SUPPLIER, X16 (12,13/); << SUPPLYING COMPANY NAME>> |
| TAX, J2 (14/); << SALES TAX (PENNIES)>> |
| TOTAL, J2 (11,14/); << TOTAL AMOUNT OF SALE(PENNIES)>>|
| UNIT-COST, P8 (/12); << UNIT COST OF PRODUCT>> |
| ZIP, X6 (12,13,14/11); << ZIP CODE>> |
| |
| SETS: |
| NAME: DATE-MASTER,AUTOMATIC,DISC1; <<DATE MASTER>> |
| ENTRY: DATE(3); |
| CAPACITY: 365; |
_____________________________________________________________________________
Figure 3-5. ORDERS Database Schema
[REV END][REV BEG]
_____________________________________________________________________________
| |
| PAGE 2 SCHEMA FOR DATABASE ORDERS |
| |
| NAME: CUSTOMER,MANUAL(14/11,18),DISC1; <<CUSTOMER MASTER>> |
| ENTRY: ACCOUNT(1), |
| LAST-NAME, |
| FIRST-NAME, |
| INITIAL, |
| STREET-ADDRESS, |
| CITY, |
| STATE, |
| ZIP, |
| CREDIT-RATING; |
| CAPACITY: 201; |
| |
| NAME: PRODUCT,MANUAL(13,14/12,18),DISC1;<<PRODUCT MASTER>> |
| ENTRY: STOCK#(2), |
| DESCRIPTION; |
| CAPACITY: 300; |
| |
| NAME: SUP-MASTER,MANUAL(13/12,18),DISC1; <<SUPPLIER MASTER>> |
| ENTRY: SUPPLIER(1), |
| STREET-ADDRESS, |
| CITY, |
| STATE, |
| ZIP; |
| CAPACITY: 201; |
| |
| NAME: INVENTORY,DETAIL(12,14/13,18),DISC2; <<INVENTORY DETAIL>>|
| ENTRY: STOCK#(PRODUCT), |
| ONHANDQTY, |
| SUPPLIER(!SUP-MASTER), <<PRIMARY PATH>> |
| UNIT-COST, |
| LASTSHIPDATE(DATE-MASTER), |
| BINNUM; |
| |
| CAPACITY: 1800,450,10%; |
| |
| NAME: SALES,DETAIL(11/14,18),DISC2; <<SALES DETAIL>> |
| ENTRY: ACCOUNT(CUSTOMER(PURCH-DATE)), |
| STOCK#(PRODUCT), |
| QUANTITY, |
| PRICE, |
| TAX, |
| TOTAL, |
| PURCH-DATE(DATE-MASTER), |
| DELIV-DATE(DATE-MASTER); |
| CAPACITY: 1008,504,112; |
| |
| |
| END. |
_____________________________________________________________________________
Figure 3-5. ORDERS Database Schema (Continued)
[REV END][REV BEG]
_________________________________________________________________________
| |
| PAGE 3 SCHEMA FOR DATABASE ORDERS |
| |
| DATA SET TYPE FLD PT ENTR MED MAXIMUM BLK BLK DISC |
| NAME CNT CT LGTH REC CAPACITY FAC LGTH SPACE|
| |
| DATE-MASTER A 1 3 3 26 365 19 496 96 |
| CUSTOMER M 9 1 41 52 201 7 365 96 |
| PRODUCT M 2 2 14 31 300 16 497 80 |
| SUP-MASTER M 5 1 31 42 201 12 505 80 |
| INVENTORY D 6 3 20 32 1800 15 481 128 |
| INITIAL CAPACITY: 450 INCREMENT ENTRIES: 45 |
| SALES D 8 4 19 35 1008 14 491 160 |
| INITIAL CAPACITY: 504 INCREMENT ENTRIES: 112 |
| |
| TOTAL DISC SECTORS INCLUDING ROOT: 672 |
| |
| NUMBER OF ERROR MESSAGES: 0 |
| ITEM NAME COUNT: 23 DATA SET COUNT: 6 |
| ROOT LENGTH: 1176 BUFFER LENGTH: 505 TRAILER LENGTH: 256 |
| ROOT FILE ORDERS CREATED. |
_________________________________________________________________________
Figure 3-5. ORDERS Database Schema (Continued)
[REV END]