TurboIMAGE/XL Database Management System DBChange Plus User's Guide ABCDE HP Part No. 36386-90001 Printed in U.S.A.
The information contained in this document is subject to change without notice. HEWLETT-PACKARD MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for errors contained herein or use of this material. Hewlett-Packard assumes no responsibility for the use or reliability of its software on equipment that is not furnished by Hewlett-Packard.
Print History DRAFT 11/6/97 The following table lists the printings of this document, together with the respective release dates for each edition. The software version indicates the version of the software product at the time this document was issued. Many product releases do not require changes to the document. Therefore, do not expect a one-to-one correspondence between product releases and document editions. Edition Date Software Version First Edition December 1990 36386A.00.
Preface How to Use This Guide . . . Because DBChange Plus is designed to be used primarily by database creators, this guide is written for a user with both a thorough knowledge of the HP 3000 and the TurboIMAGE/XL database management system. This guide has two purposes: If you are a new DBChange Plus user, this guide is designed to acquaint you with DBChange Plus and to help you learn to use DBChange Plus successfully.
Chapter 5. Changing Data Sets This chapter describes how to change data sets in a TurboIMAGE/XL database. It describes the steps involved in changing data set elds and data set characteristics, such as capacity and blocking factor. This chapter also explains how to recover a data set.
Chapter 6. Changing Paths in a Database This chapter describes how to make changes to paths in a TurboIMAGE/XL database. Chapter 7. Changing Database Security This chapter describes how to change user access to a TurboIMAGE/XL database. Chapter 8. Maintaining the Database This chapter describes how to maintain a TurboIMAGE/XL database. Checking for structural integrity, xing structural problems, improving database performance, and managing database capacity are discussed. Chapter 9.
Other Information Sources Manuals In addition to this guide, you may need to consult the following manuals: Title Part Number MPE XL Intrinsics Reference Manual 32650-90028 TurboIMAGE/XL Database Management System Reference Manual 30391-90001 Training The following training courses are available: Title Course Number TurboIMAGE DBMS/3000 35053B Advanced TurboIMAGE 51480A viii DRAFT 11/6/97 20:05
Conventions UPPERCASE In a syntax statement, commands and keywords are shown in uppercase characters. The characters must be entered in the order shown; however, you can enter the characters in either uppercase or lowercase. For example: COMMAND can be entered as any of the following: command italics Command COMMAND In a syntax statement or an example, a word in italics represents a parameter or argument that you must replace with the actual value.
select OPTION or Parameter or neither. The elements cannot be repeated.
Conventions [ . .. ] (continued) In a syntax statement, horizontal ellipses enclosed in brackets indicate that you can repeatedly select the element(s) that appear within the immediately preceding pair of brackets or braces. In the example below, you can select Parameter zero or more times. Each instance of Parameter must be preceded by a comma: [, Parameter][...
Contents 1. Introduction to DBChange Plus What Is DBChange Plus? . . . . . . . . . . . . DBChange Plus Operation . . . . . . . . . . . Getting Started . . . . . . . . . . . . . . . . Running the DBCPLUS Program . . . . . . . . Getting Help . . . . . . . . . . . . . . . . . Specifying the Database to be Restructured . . . How the Change File Works . . . . . . . . . . Creating a New Change File . . . . . . . . . Updating an Existing Change File . . . . . . Purging an Existing Change File . . . . . . .
Contents-2 3. Displaying Information about the Database Summary of Commands to Display Information about the Database . . . . . . . . . . . . . . . . Printing the Schema . . . . . . . . . . . . . . Aborting the PRINT SCHEMA Command . . . Using REVIEW Commands to Display Information about the Database . . . . . . . . . . . . . Displaying User Classes and Passwords . . . . . Displaying Data Items . . . . . . . . . . . . Displaying Information about Data Sets . . . . . Displaying Data Sets . . . . . . . . . .
6. Changing Paths in a Database Summary of Commands to Change Paths . . . . Helpful TurboIMAGE/XL Information . . . . . Adding a Path to a Detail Data Set . . . . . . . Rede ning the Primary Path in a Detail Data Set Deleting a Path from a Detail Data Set . . . . . . . . . . 6-1 6-2 6-2 6-4 6-5 7. Changing Database Security Summary of Commands to Change Database Security Helpful TurboIMAGE/XL Information . . . . . . Adding a Password to the Database . . . . . . . Changing a Password in the Database . . .
How DBAPLUS Restructures a Database . . . . . Possible Restructuring Problems . . . . . . . . Restructuring the ORDERS Database . . . . . . . 10. DBChange Plus Commands DBChange Plus Command Formats . . . Summary of DBChange Plus Commands ADD FIELD . . . . . . . . . . . . ADD ITEM . . . . . . . . . . . . ADD PASSWORD . . . . . . . . . ADD PATH . . . . . . . . . . . . ADD SET . . . . . . . . . . . . . ADD SORT . . . . . . . . . . . . BASE . . . . . . . . . . . . . . . CANCEL COMMANDS . . . . . . .
REDO . . . . . . . . RENAME BASE . . . . RENAME ITEM . . . . RENAME SET . . . . REORDER FIELD . . . REORDER ITEM . . . REORDER SET . . . . REPACK SET . . . . . REVIEW BLOCKS . . . REVIEW FIELDS . . . REVIEW ITEMS . . . REVIEW PASSWORDS REVIEW PATHS . . . REVIEW SETS . . . . XEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figures 1-1. Typical DBChange Plus Command Format . . . 1-7 Tables 1-1. DBChange Plus Functions . . . . . . . . . . . 1-1 3-1. Summary of Commands to Display Information about the Database . . . . . . . . . . . . 3-2 4-1. Summary of Commands to Change Data Items . . 4-2 4-2. DBChange Plus Supported Item Type Conversions 4-3 5-1. Summary of Commands to Change Data Sets . . 5-2 6-1. Summary of Commands to Change Paths . . . . 6-1 7-1. Summary of Commands to Change Database Security 7-2 8-1.
1 Introduction to DBChange Plus This chapter introduces DBChange Plus by explaining how it operates, by demonstrating a few tasks to get you started, and by discussing the features of the command interface. If you are a new DBChange Plus user, you should read this chapter before moving on to subsequent chapters. To learn about more DBChange Plus tasks, refer to chapters 2 through 9.
DBChange Plus contains two programs: DBCPLUS and DBAPLUS. The DBCPLUS program accepts and stores your requests in a change le. The change le contains information about the database and also contains requests for changes as speci ed by the DBChange Plus commands. The DBAPLUS program performs the actual restructuring or maintenance of the database. DBAPLUS can be invoked either from within the DBCPLUS program by issuing a PERFORM COMMANDS, or it can be invoked independently.
TUE, MAY 22, 1990, > 8:46 AM The DBChange prompt (>) appears on your screen. Getting Help DBChange Plus has an online help facility, which you can access anytime you are running the DBCPLUS program in interactive mode. You can either see the entire list of DBChange Plus commands, or you can get information about a speci c command. To see a listing of all the DBChange Plus commands, issue the HELP command at the DBChange prompt as shown in the following example.
ADD ADD ADD ADD > PASSWORD PATH SET SORT Adds Adds Adds Adds a a a a password to a database. path to an existing detail data set. set to an existing database. new sort item to an existing path. To get a description of the syntax and parameters and an example of a command, use the HELP command, the DBChange command, and the keyword. For example, HELP ADD ITEM produces syntax and parameter information along with an example.
Purging an Existing Change File To purge an existing change le, use the PURGECF option with the BASE command. The change le can also be purged by using the CANCEL COMMANDS command. If you use the CANCEL COMMANDS command after issuing the BASE command with the OLD option, the current dbname CF is purged, and dbname CO is renamed dbname CF.
Deleting a Field A eld is a data item that is associated with a data set. To delete a eld, use the DELETE FIELD command. In the following example, the eld UNIT{COST is deleted from the detail data set INVENTORY: >delete field inventory unit-cost Deletion of field accepted.
Leaving the DBChange Program Use the EXIT command to leave the DBCPLUS program. When you exit, a series of messages summarizing the information stored in the change le appears on your screen. The MPE XL prompt (:) displays on your screen once the DBCPLUS program terminates. Following is an example of the EXIT command: >exit Please wait.....change file is being verified. HP36386 (A.00.00) DBCHANGE (c) COPYRIGHT Hewlett-Packard Co.
Difference Between Deferred and Immediate Commands DBChange Plus has two types of commands: immediate and deferred. Immediate commands are those commands that do not a ect the database structure, but instead give information about or help with the operation of the DBCPLUS program. They are executed immediately when they are entered.
Terminating a Command You can cause the DBCPLUS program to ignore the command you are currently entering by typing two slashes (//) and pressing the carriage return key. This returns you to the DBChange prompt (>). You might use this feature, for example, if you decide not to execute the current command or if you make an error and want to start over. For example: >change it// > This feature is only available in interactive mode.
>xeq cmdfile ><> ><> ><> ><> >base orders new <---- DBChange command Change file already exist for ORDERS, do you want to purge it [y/N] ? y Change file ORDERSCF has been purged.
HP36386 (A.00.00) DBCHANGE (c) COPYRIGHT Hewlett-Packard Co. 1985 ******************* DBCHANGE STATISTICS*************************** Number Number Number Number Number Number of of of of of of databases databases databases databases databases databases prepared prepared prepared prepared prepared prepared for for for for for for rename: restructure: erase : repack: check : fix : 0 1 0 0 0 0 : Using a Job File A job le is a text le that contains DBChange Plus and MPE XL commands.
Issuing MPE XL Commands from within the DBCPLUS Program Many MPE XL commands, including RUN commands, can be entered interactively. You can issue MPE XL commands from within the DBCPLUS program either by entering a colon (:) after the DBCPLUS prompt and then typing the command, or by using 4Break5 and RESUME.
Redirecting Input, Output, and the Schema Listing By default, command input comes from $STDIN (the user terminal interactively; the job le in batch mode). By default, output is directed to $STDLIST (the user terminal interactively or the job's $STDLIST spool le in batch mode). You can redirect input, output, and the schema listing by issuing the following formal le designators either before or during DBChange Plus operation.
Printing the Schema to an MPE XL File in Interactive Mode When you issue the PRINT SCHEMA FileName command in interactive mode, the new le is opened and the DBCPLUS program veri es if a le with the same name already exists. If one does, you are prompted and must con rm if you want the existing le purged. If a le with the same name does not exist, the new le is built and the schema is printed to the new le.
size. If you enter several of these commands, you should review the error messages before deciding which corrective action to take. For a complete description of errors, their cause, and corrective action, refer to appendix A, \DBChange Plus Messages." How DBChange Plus Helps You Avoid and Recover from Errors Every attempt is made to prevent you from inadvertently damaging the database.
!eoj 1-16 Introduction to DBChange Plus
The DBCPLUSJCW is set within the DBCPLUS program and checks for such errors as incorrect command syntax and incorrect database name. If no errors are encountered, then the JCW is set to zero and the job is successfully processed. If errors are encountered, the JCW is set to a number other than zero and the DBAPLUS program is not run. The DBAPLUSJCW is set within the DBAPLUS program. If no errors are encountered, the JCW is set to zero and the job is successfully processed.
3 Displaying Information about the Database This chapter explains how to display information about the structure of a TurboIMAGE/XL database. It provides instructions for and examples of the commands used to display information about the database. Before reading this chapter, you should be familiar with the information in chapter 1, \Introduction to DBChange Plus." To learn how to do more DBChange Plus tasks, refer to chapters 2 and 4 through 9.
Table 3-1. Summary of Commands to Display Information about the Database Command Keyword Description PRINT SCHEMA Prints the database schema. REVIEW BLOCKS Displays information about the data sets in the database. Includes data set type, eld count, path count, entry length, capacity, blocking factor, and block length. FIELDS Displays information about the elds (data items) of master and detail data sets. Includes search items, sort items, and linked data sets.
Refer to \Redirecting Input, Output, and the Schema Listing" in chapter 1, \Introduction to DBChange Plus," or refer to \PRINT SCHEMA" in chapter 10, \DBChange Plus Commands," for a detailed description of the command.
Aborting the PRINT SCHEMA Command To abort the PRINT SCHEMA command anytime during an interactive session, press 4CONTROL5 Y. The DBCPLUS program prints << CONTROL-Y >> and returns the prompt for a new command.
Using REVIEW Commands to Display Information about the Database Displaying User Classes and Passwords The DBCPLUS program has several REVIEW commands that display information about the database structure with the changes stored in a change le. The remainder of this chapter provides an example for each REVIEW command. To display one or more user classes and associated passwords in the database, use the REVIEW PASSWORDS command.
Displaying Data Items To display information about one or more data items in the database, use the REVIEW ITEMS command. The REVIEW ITEMS command displays item numbers as they appear in the schema, along with their item name, attributes, and security information. In the following example, @ is the parameter used to display all the items in the ORDERS database. Because the database has more than 20 data items, the DBCPLUS program asks if you want to continue, that is, review more data items.
Displaying Information about Data Sets This section describes the REVIEW commands used to display information about data sets. Displaying Data Sets To display information about one or more data sets in the database, use either the REVIEW SETS or REVIEW BLOCKS command. Both the REVIEW SETS and REVIEW BLOCKS commands display the data set name, the data set type, capacity, blocking factor and maximum block length.
Refer to \REVIEW SETS" and \REVIEW BLOCKS" in chapter 10, \DBChange Plus Commands," for a detailed description of the commands.
Displaying Fields To display one or more elds in a data set, use the REVIEW FIELDS command. For both master and detail data sets, the REVIEW FIELDS command displays the data set number, as it appears in the schema, and the data set name and type. However, the master data set output di ers from the detail data set output in that the master data set output displays the detail data set associated with the master data set and the search item linking that detail data set to the master data set.
In the example below, the REVIEW FIELDS command is used to display the elds in the detail data set SALES: >review fields sales REVIEW FIELDS (DETAIL SET): Data Set No.: 6 Name: SALES Type: D Fld No.
In the following example, CUSTOMER is the name of a master data set in the ORDERS database: >review paths customer REVIEW PATHS (MASTER SET): Data Set No.: 1 Name: CUSTOMER Type: M Key(Search) Item Detail Set Name Sort Item Name -----------------------------------------------------ACCOUNT SALES PURCH-DATE > In the example below, SALES is the name of a detail data set in the ORDERS database: >review paths sales REVIEW PATHS (DETAIL SET): Data Set No.
4 Changing Data Items This chapter explains how to change data items in a TurboIMAGE/XL database. It provides instructions for and examples of the various commands used to change data items. Before reading this chapter, you should be familiar with the information in chapter 1, \Introduction to DBChange Plus." To learn how to do more DBChange Plus tasks, refer to chapters 2, 3, and 5 through 9.
Table 4-1. Summary of Commands to Change Data Items Command Keyword Description ADD ITEM Adds a data item to the database. CHANGE ATTRIBUTE Changes the subitem count, type, and/or length of a data item. ITEM Changes the subitem count, type, length, security, and/or order of a data item. ITEMSECURITY Changes user class access to a data item (security command only). DELETE ITEM Deletes a data item and its elds and associated paths from the database.
The subitem length must be from 1 to 255, depending on the type designator as follows: Type Length U, X, Z Maximum is 255 bytes. P Maximum is 255 nibbles. I, J Must be 1, 2, or 4 halfwords. K Must be 1 or 2 halfwords. R Must be 2 or 4 halfwords. A compound data item is a data item with a subitem count of more than one. Search and sort items cannot be compound items. When changing data item length, reevaluate the blocking factor of the sets containing the items.
Caution Adding a Data Item When converting data item types, over ow, under ow, and truncation may occur if you are reducing data item size. Be sure to verify that data item conversions do not result in loss of data. To add a data item to the database, use the ADD ITEM command. In this section, the new data item STORE# is added to the ORDERS database. Before adding the data item, the REVIEW ITEMS output looks like this: Itm No.
In the example below, the data item STORE# is added using the ADD ITEM command. It should appear before the data item TAX in the data item list. The sub-count is 8, the type is J, and the length is 2. User classes 11 and 12 have read access, and user class 14 has write access to the new data item. The DBCPLUS program displays a message con rming that the new data item is accepted. >add item store# (tax) 8 j 2 (11,12/14) Addition of data item accepted.
23 24 UNIT-COST ZIP Deleting a Data Item P8 X6 (/12) (12,13,14/11) To delete a data item, use the DELETE ITEM command. In this section, the data item LASTSHIPDATE is deleted from the ORDERS database. When deleting data items, remember the following: If the data item to be deleted is a eld in one or more data sets, those elds are also deleted. If the data item to be deleted is associated with one or more paths, those paths are also deleted.
13 14 15 16 17 18 19 PRICE PURCH-DATE QUANTITY STATE STOCK# STREET-ADD SUPPLIER J2 X6 I1 X2 U8 X26 X16 (14/) (11/14) (/14) (12,13,14/11) (11,12,14,18/) (12,13,14/11) (12,13/) Changing Data Items 4-7
20 21 22 23 24 STORE# TAX TOTAL UNIT-COST ZIP 8J2 J2 J2 P8 X6 (11,12/14) (14/) (11,14/) (/12) (12,13,14/11) In the example below, the data item LASTSHIPDATE is deleted using the DELETE ITEM command. LASTSHIPDATE is also a eld in the detail data set INVENTORY and will be deleted from the data set. In the following interactive session, a message is displayed asking you to con rm the deletion of the data item. In batch mode, the data item is deleted without con rmation.
15 16 17 18 19 20 21 22 23 STATE STOCK# STREET-ADD SUPPLIER STORE# TAX TOTAL UNIT-COST ZIP X2 U8 X26 X16 8J2 J2 J2 P8 X6 (12,13,14/11) (11,12,14,18/) (12,13,14/11) (12,13/) (11,12/14) (14/) (11,14/) (/12) (12,13,14/11) If you want to verify that the eld LASTSHIPDATE is deleted from the detail data set INVENTORY, use the REVIEW FIELDS command, as shown in the following example: >review fields inventory REVIEW FIELDS (DETAIL SET): Data Set No.: 5 Name: INVENTORY Type: D Fld No.
In the following example, the data item LASTSHIPDATE is recovered. The DBCPLUS program returns a message con rming recovery of the deleted data item. >recover item lastshipdate Recovery of data item accepted. > Refer to \RECOVER ITEM" in chapter 10, \DBChange Plus Commands," for a detailed description of the command syntax and parameters.
If you want to verify that the deleted data item LASTSHIPDATE is recovered, use the REVIEW ITEMS command. In the following example, the @ parameter is used to display all the data items in the ORDERS database. You can see that the data item LASTSHIPDATE is recovered and inserted in its original place in the data item list. >review items @ REVIEW ITEMS: Itm No.
Before it was deleted, LASTSHIPDATE was also a eld in the detail data set INVENTORY. The RECOVER ITEM command put the data item LASTSHIPDATE back into the detail data set INVENTORY in its original place in the eld list. If you want to verify this, use the REVIEW FIELDS command, as shown in the following example: >review fields inventory REVIEW FIELDS (DETAIL SET): Data Set No.: 5 Name: INVENTORY Type: D Fld No.
13 14 15 16 17 18 19 20 21 22 23 24 PRICE PURCH-DATE QUANTITY STATE STOCK# STREET-ADD VENDOR STORE# TAX TOTAL UNIT-COST ZIP J2 X6 I1 X2 X10 X26 X16 8J2 J2 J2 P8 X6 (14/) (11/14) (/14) (12,13,14/11) (11,12,14,18/) (12,13,14/11) (12,13/) (11,12/14) (14/) (11,14/) (/12) (12,13,14/11) <---- data item to be reordered In the example below, the data item UNIT{COST is reordered to appear before the data item TAX in the data item list.
10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 LASTSHIPDATE ONHANDQTY DESCRIPTION PRICE PURCH-DATE QUANTITY STATE STOCK# STREET-ADD VENDOR STORE# UNIT-COST TAX TOTAL ZIP Renaming a Data Item X6 J2 4U25 J2 X6 I1 X2 X10 X26 X16 8J2 P8 J2 J2 X6 (12/) (14/12) (11,14/18) (14/) (11/14) (/14) (12,13,14/11) (11,12,14,18/) (12,13,14/11) (12,13/) (11,12/14) (/12) (14/) (11,14/) (12,13,14/11) <---- data item reordered To rename a data item, use the RENAME ITEM command.
19 Changing a Data Item VENDOR X16 (12,13/) Use the CHANGE ITEM command to change data item type, length, subitem count, security, and order in the data item list. In this section, the data item DESCRIPTION is changed in the ORDERS database. Before changing a data item, the REVIEW ITEMS output looks like this: Itm No.
security is changed to allow read access for user classes 11 and 14 and write access for user class 18. The DBCPLUS program displays messages con rming that the changes are accepted.
>change item description (price) 4 u 25 (11,14/18) Reorder of data items accepted. Change of item attributes accepted. Change of item security accepted. If the data item length is changed to a smaller number than the original data item length, the data may truncate or over ow the new eld. Caution Refer to \CHANGE ITEM" in chapter 10, \DBChange Plus Commands," for a detailed description of the command syntax and parameters.
21 22 23 24 TAX TOTAL UNIT-COST ZIP Changing Data Item Attributes J2 J2 P8 X6 (14/) (11,14/) (/12) (12,13,14/11) To change the subitem count, the type, and the length of a data item, use the CHANGE ATTRIBUTES command. CHANGE ATTRIBUTES and CHANGE ITEM are similar in that they both change data item attributes. However, CHANGE ITEM also changes the order of a data item in the data item list and the data item security. If you only want to change data item attributes, use the CHANGE ATTRIBUTES command.
REVIEW ITEMS: Itm No.
5 Changing Data Sets This chapter explains how to change data sets in a TurboIMAGE/XL database. It provides instructions for and examples of the various commands used to change data sets. Before reading this chapter, you should be familiar with the information in chapter 1, \Introduction to DBChange Plus." To learn to do more DBChange Plus tasks, refer to chapters 2 through 4 and 6 through 9.
Table 5-1. Summary of Commands to Change Data Sets Command ADD Keyword Description FIELD Adds a eld (data item) to a manual master or detail data set. PATH Adds a path from a detail data set to a master data set (path command only). SET Adds a new master or detail set to the database. SORT Adds a new sort item for a search item. If a sort item already exists in the data set, the ADD SORT command replaces the existing sort item. CHANGE BLOCKFACTOR Changes the blocking factor of a data set.
Helpful TurboIMAGE Information Remember the following TurboIMAGE characteristics when making changes to data sets: A data set name must be unique within the database. It must be from 1 to 16 characters long, and the rst character must be alphabetic. No more than 199 data sets can exist in a TurboIMAGE database. Data set capacity must be less than 231 01 (2,147,483,647). The blocking factor is the number of entries in one block.
Adding a Master Data Set To add an automatic or manual master data set to the database, use the ADD SET command. In this section, the new data set BINNUM{MASTER is added to the ORDERS database. Before adding a data set, the REVIEW SETS command output looks like this: Set Blk Blk Dev No.
After adding a master data set and a path, the new data set contains only one eld|the key item. To add more elds, use the ADD FIELD command discussed later in this chapter. To connect the new key item to other detail data sets, use the ADD PATH command. Refer to \ADD PATH" in chapter 6, \Changing Paths in a Detail Data Set," or in chapter 10, \DBChange Plus Commands." If you want to verify the addition of the new data set, use the REVIEW SETS command.
Deleting a Data Set To delete a master or detail data set and its associated paths from the database, use the DELETE SET command. In this section, the data set BINNUM{MASTER is deleted from the ORDERS database. Before deleting the data set, the REVIEW SETS command output looks like this: Set Blk Blk Dev No.
If you want to verify the deletion of the data set, use the REVIEW SETS command. In the following example, the @ parameter is used to display all the data sets in the ORDERS database. You can see that the data set BINNUM{MASTER is deleted. Set Blk Blk Dev No.
Recovery of data set accepted. > Refer to \RECOVER SET" in chapter 10, \DBChange Plus Commands," for a detailed description of the command syntax and parameters.
If you want to verify the recovery of the deleted data set, use the REVIEW SETS command. In the following example, the @ parameter is used to display all the data sets in the ORDERS database. Because the data set BINNUM{MASTER was in the change le and the DBAPLUS program had not been run, the data set is inserted at the end of the data set list. The path connecting the master data set BINNUM{MASTER to the detail data set INVENTORY cannot be recovered.
5 6 7 * 5-10 INVENTORY SALES BINNUM-MASTER data set to be reordered Changing Data Sets D D A 450 500 220 15 10 12 481 371 0 DISK2 DISK2 DISK1 (12,14/13,18) (11/14,18) (14/11,18) <---- *
In the example below, the data set BINNUM{MASTER is reordered to appear before the data set CUSTOMER in the data set list. (When the nextset parameter is omitted, the data set appears at the end of the data set list.) The DBCPLUS program displays a message con rming that the data sets are reordered. >reorder set binnum-master customer Reorder of data set accepted. > Refer to \REORDER SET" in chapter 10, \DBChange Plus Commands," for a detailed description of the command syntax and parameters.
Renaming a Data Set To give a new name to a data set, use the RENAME SET command. In this section, the detail data set SALES in the ORDERS database is renamed. Before renaming the data set, the REVIEW SETS command output looks like this: Set Blk Blk Dev No.
Changing the Capacity of a Data Set To change the capacity of a data set, use the CHANGE CAPACITY command. When you change the capacity of a data set, the DBCPLUS program checks to see if the new capacity is greater than or less than the high-water mark. The high-water mark is the greatest number of entries the data set has ever contained. If the new capacity is greater than the high-water mark, the capacity is changed as speci ed.
changed to 510, which can be evenly divided by 15. Note, however, that if the REVIEW SETS or REVIEW BLOCKS command is used before invoking the DBAPLUS program, the speci ed capacity, rather than the actual adjusted capacity, is displayed.
If you want to verify that the capacity of the data set INVENTORY is changed, use the REVIEW SETS command as follows. You can see that the capacity is now 510.
adjust the capacity to a multiple of the new blocking factor closest to the current capacity.
If you want to verify that the blocking factor is changed, use the REVIEW BLOCKS command as in the following example. You can see that the blocking factor for the data set INVENTORY is now 12.
>change blockmax date-master sales 1024 Change of maximum blocksize accepted.
The range speci ed must re ect the current order of the data sets; that is, if the REORDER SET command was used prior to the CHANGE BLOCKMAX command, the range of the data sets must re ect the new order. To verify the data set order, use the REVIEW BLOCKS command. Note Refer to \CHANGE BLOCKMAX" in chapter 10, \DBChange Plus Commands," for a detailed description of the command syntax and parameters.
Changing the Device Class of a Data Set To change the device on which a data set resides, use the CHANGE DEVICECLASS command. The CHANGE DEVICECLASS command actually moves the data set. In this section, a di erent device class is speci ed for the data set SUP{MASTER in the ORDERS database. Before changing the device class, the REVIEW SETS command output looks like this: Set Blk Blk Dev No.
Adding a Field to a Data Set To add a eld to a manual master or detail data set, use the ADD FIELD command. In this section, the eld STORE# is added to the INVENTORY data set in the ORDERS database. Before adding the eld, the REVIEW FIELDS output like this: Data Set No.: 6 Name: INVENTORY Type: D Fld No.
2 3 4 5 6 7 ONHANDQTY STORE# SUPPLIER UNIT-COST LASTSHIPDATE BINNUM Y Y SUP-MASTER Y Y DATE-MASTER BINNUM-MASTER <---- eld added To delete a eld from a manual master or detail data set, use the DELETE FIELD command. In this section, the eld CREDIT{RATING is deleted from the master data set CUSTOMER in the ORDERS database. Before deleting the eld, the REVIEW FIELDS output looks like this: Deleting a Field from a Data Set Data Set No.: 3 Name: CUSTOMER Type: M Fld No.
Caution Once you have deleted a eld, it cannot be recovered from the change le; you must use the ADD FIELD command to add it back in to the data set. However, if the eld contained data before it was deleted, the data cannot be recovered.
If you want to verify the deletion of the eld, use the REVIEW FIELDS command. In the following example, you can see that the eld CREDIT{RATING no longer appears in the data set CUSTOMER eld list: >review fields customer REVIEW FIELDS (MASTER SET): Data Set No.: 3 Name: CUSTOMER Type: M Fld No. Field Name Detail Set Name Path's Search Item --------------------------------------------------------------1 2 3 4 5 6 7 8 Reordering a Field in a Data Set Data Set No.
In the example below, the eld BINNUM is reordered to appear before the eld ONHANDQTY in the eld list. The DBCPLUS program displays a message con rming that the elds are reordered. >reorder field inventory binnum onhandqty Reorder of fields accepted. > To verify that the elds in the INVENTORY data set are reordered, use the REVIEW FIELDS command as shown below. You can see that the eld BINNUM now appears before the eld ONHANDQTY in the eld list.
In the example below, INVENTORY is the name of the detail data set that will contain the sort item. SUPPLIER is the name of the search item whose like values will be sorted based on the new sort item values. LASTSHIPDATE is the name of the new sort item. The DBCPLUS program displays a message con rming the addition of the new sort item. >add sort inventory supplier lastshipdate New sort item added.
Deleting a Sort Item from a Detail Data Set To remove a sort item from a search item in a detail data set, use the DELETE SORT command. In this section, a sort item is removed from the search item SUPPLIER in the detail data set INVENTORY.
LASTSHIPDATE * The sort item LASTSHIPDATE has been deleted from the data set.
6 Changing Paths in a Database This chapter explains how to change paths in a TurboIMAGE/XL database. It provides instructions for and examples of the commands used to change paths. Before reading this chapter, you should be familiar with the information in chapter 1, \Introduction to DBChange Plus." To learn how to do more DBChange Plus tasks, refer to chapters 2 through 5 and 7 through 9.
Remember the following TurboIMAGE/XL characteristics when changing paths: A search item is a data item in a detail data set that de nes a path to a related master data set. As many as 16 di erent paths can be de ned for each detail data set, but each search item can de ne only one path. A master data set can be related to as many as 16 detail data sets. A search item must be a simple item (subitem count equals 1). A sort item must be a data item of type U, K, or X.
In the example below, SALES is the name of the detail data set that will contain the new search item. FILL{DATE is the name of the search item for the new path. The exclamation point (!) indicates that the new path is to be the primary path. DATE{MASTER is the name of the master data set containing the key item to be related to the search item. STOCK# is the name of the sort item for the new path. DBChange returns a message con rming the addition of the new path.
Redefining the Primary Path in a Detail Data Set To rede ne the primary path in a detail data set containing two or more paths, use the CHANGE PRIMARYPATH command. In this section, a new primary path is rede ned in the INVENTORY detail data set of the ORDERS database.
>review paths inventory DATABASE NAME: ORDERS REVIEW PATHS (FOR DETAIL DATA SET): DATA SET NO: 6 NAME: INVENTORY SEARCH ITEM NAME ================ MASTER SET NAME ================ STOCK# SUPPLIER LASTSHIPDATE PRODUCT SUP-MASTER DATE-MASTER * STOCK# TYPE: D SORT ITEM NAME ================ LASTSHIPDATE PRIMARY ======= Y <---- * is now the search item for the primary path. > Deleting a Path from a Detail Data Set To delete a path from a detail data set, use the DELETE PATH command.
>delete path sales fill-date Deletion of path accepted. > Refer to \DELETE PATH" in chapter 10, \DBChange Plus Commands," for a detailed description of the command syntax and parameters. If you want to verify the deletion of a path, use the REVIEW PATHS command.
7 Changing Database Security This chapter explains how to change user access to a TurboIMAGE/XL database. It provides instructions for and examples of the commands used to change user access. Before reading this chapter, you should be familiar with the information in the chapter 1, \Introduction to DBChange Plus." To learn how to do more DBChange Plus tasks, refer to chapters 2 through 6, 8, and 9.
Table 7-1. Summary of Commands to Change Database Security Command ADD CHANGE DELETE PRINT Keyword ITEM Adds a data item to the database. (Multipurpose command.) PASSWORD Adds a password and user class number to the database. SET Adds a new master or detail data set to the database. (Multipurpose command.) ITEM Changes the type, length, subcount, security, and/or order of a data item. (Multipurpose command.) ITEMSECURITY Changes user class access to a data item. PASSWORD Changes a password.
Helpful TurboIMAGE/XL Information Remember the following TurboIMAGE/XL characteristics when making changes to the database security: A password is associated with a user class number from 1 to 63 in the schema. This number is used in the schema read/write lists to de ne data item and data set access for the password. A password must be from 1 to 8 ASCII characters, excluding carriage returns, slashes, semicolons, and blanks. Passwords, unlike other TurboIMAGE/XL elements, are case sensitive.
In the example below, the password MANAGER and its associated user class 15 are added to the ORDERS database. (Remember that passwords are case sensitive.) The DBCPLUS program returns a message con rming the addition of the user class and password. >add password MANAGER 15 Addition of user class and password accepted. > Refer to \ADD PASSWORD" in chapter 10, \DBChange Plus Commands," for a detailed description of the command syntax and parameters.
> Changing Database Security 7-5
In the example below, the password CLERK is changed to the password SALESREP. The DBCPLUS program returns a message con rming the change of the password. >change password CLERK SALESREP Change of password accepted. > Refer to \CHANGE PASSWORD" in chapter 10, \DBChange Plus Commands," for a detailed description of the command syntax and parameters. If you want to verify the password change, use the REVIEW PASSWORDS command.
> In the example below, the password SHIP{REC and its associated user class 13 are deleted from the ORDERS database. The DBCPLUS program asks if you want the associated user class deleted. In this example, Y is entered for yes. The DBCPLUS program then returns a message con rming the deletion of the user class and password. >delete password SHIP-REC 13 Delete password user class [y/N] ? y Deletion of user class and password accepted.
Changing Data Item Security To change data item security, use the CHANGE ITEMSECURITY command. CHANGE ITEMSECURITY changes only one user class access at a time. If you want to change more than one user class at a time, use the CHANGE ITEM command. Refer to \CHANGE ITEM" in chapter 10, \DBChange Plus Commands." In this section, the security of the data item QUANTITY is changed in the ORDERS database. Before making changes, the REVIEW ITEMS command output looks like this: Itm No.
In the example below, the security of the data item QUANTITY is changed to add user class 18 to the write access class list. The DBCPLUS program returns a message con rming the change of security. >change itemsecurity quantity 18 w Change of item security accepted. > Refer to \CHANGE ITEMSECURITY" in chapter 10, \DBChange Plus Commands," for a detailed description of the command syntax and parameters. If you want to verify that the item security is changed, use the REVIEW ITEMS command.
> Refer to \DELETE ITEMSECURITY" in chapter 10, \DBChange Plus Commands," for a detailed description of the command syntax and parameters. If you want to verify that the data item security is deleted, use the REVIEW ITEMS command. In the following example, you can see that all security speci cations are deleted from the data item STATE, resulting in an absent list. >review items STATE REVIEW ITEMS: Itm No.
>change setsecurity inventory 14 w Change of set security accepted. > Refer to \CHANGE SETSECURITY" in chapter 10, \DBChange Plus Commands," for a detailed description of the command syntax and parameters. If you want to verify that the data set security is changed, use the REVIEW SETS command. In the following example, you can see that the security of the data set INVENTORY is changed: >review sets inventory REVIEW SETS: Set Blk Blk Dev No.
Refer to \DELETE SETSECURITY" in chapter 10, \DBChange Plus Commands," for a detailed description of the command syntax and parameters. If you want to verify that the data set security is deleted, use the REVIEW SETS command.
>review sets CUSTOMER REVIEW SETS: Set Blk Blk Dev No. Data Set Name Type Capacity Fac Max Class Security -------------------------------------------------------------1 CUSTOMER M 221 10 640 <---- * > * All security speci cations have been deleted from the data set CUSTOMER. Note Deleting all security speci cations from a data set means that all users can read the data set. This is the default security assigned by DBSCHEMA when processing a data set without security speci cations.
8 Maintaining the Database This chapter explains how to use DBChange Plus to do the following maintenance and performance tuning tasks on a TurboIMAGE/XL database: Checking for structural integrity. Fixing structural problems. Improving database performance. Managing database capacity. In this chapter, the section \Guidelines for Maintaining the Database" discusses when to use DBChange Plus to optimize the performance and integrity of the database.
DBChange Plus provides speci c commands that generate statistics about the database structure to help you determine if there are any structural problems, such as broken chains, incorrect pointer linkages, and inconsistent pointers. Several of the commands correct known problems. The commands used for database maintenance are listed alphabetically in Table 8-1 along with a summary of their functions.
Guidelines for Maintaining the Database To optimize the performance and integrity of the database, you can implement a regular maintenance schedule. For example: 1. Establish baseline statistics for your database against which future statistics can be compared. To do this, use the CHECK BASE command with the QUICK parameter and archive the resulting output. Note that your database should be performing optimally and should not contain structural problems when you establish your baseline. 2.
Repacking Data Sets To repack a detail data set, use the REPACK SET command. Repacking a detail data set can improve database performance by eliminating long delete chain counts (deleted entry gaps) and optimizing chains by adjusting pointers. Repacking a detail data set physically regroups the records on disk to improve storage e ciency. To further improve performance, you can also change the capacity, blocking factor, and device class of a detail data set with the REPACK SET command.
After issuing a PERFORM COMMANDS to invoke DBAPLUS, the following output is displayed: PAGE 1 HEWLETT-PACKARD 30391C.02.00 TurboIMAGE/3000: DBSCHEMA FRI, APR 27, 1990, 10:40 AM (C) HEWLETT-PACKARD CO. 1987 BEGIN DATABASE ORDERS; PASSWORDS: 11 CREDIT ; 12 AGENT ; .. .
Checking and Fixing Paths Checking Paths This section explains how to check a data set path for inconsistencies and how to x a path that contains inconsistencies. To check a path for broken chains and incorrect pointer linkages, use the CHECK PATH command. To correct problems found after using CHECK PATH, use the FIX PATH command. You can use CHECK PATH and FIX PATH for either master or detail data sets. When used on a master data set, CHECK PATH checks the synonym chain pointers in the master set.
CHECK INFORMATION Set Name Type Search Item Message(s) -----------------------------------------------------------------------CUSTOMER M Userlabel entry count does not match bitmap entry count (CHK 560). Record 6 is not linked into the proper synonym chain (CHK 360). SALES D ACCOUNT (Path 1; linked to master CUSTOMER, path 1) Sum of chain counts in the related master set does not match bitmap entry count for this set (CHK 580). HP36386 (A.00.00) DBCHANGE (c) COPYRIGHT Hewlett-Packard Co.
The Avg Chain should not exceed 40 percent of the capacity unless it's necessary for the application program. The data item most heavily used by an application should be speci ed as the search item for a detail data set repack. This makes for a more e cient repack. Sorted chains should be less than 50 records unless key values are added in ascending order over time. For example, a date eld where the currently added date will always be greater than any of the prior dates can exceed more than 50 records.
Check file ORDERSRX exists; it will be overwritten (DBA 125). Starting data set serial reads. Tabulating statistics. CHECK PATH Pct Set Name Type Max Avg Std Far Avg Packing Search Item (PS) Chain Chain Dev Ptrs Blocks Ratio ---------------------------------------------------------------------CUSTOMER M SYNONYM CHAINS 1 1.00 0.00 0 1.00 N/A Starting data set chained reads.
Checking and Fixing Data Sets Note Checking a Master Data Set This section explains how to check data sets for internal pointer or structural inconsistency and how to x data sets that contain inconsistencies. To check a data set for internal or pointer inconsistency, use the CHECK SET command. To correct problems found after using CHECK SET, use the FIX SET command. You can use CHECK SET and FIX SET for either master data sets or detail data sets.
Sum of chain counts in the related master set does not match bitmap entry count for this set (CHK 580). HP36386 (A.00.00) DBCHANGE (c) COPYRIGHT Hewlett-Packard Co. 1985 Analyzing the CHECK SET Statistics for a Master Data Set CHECK SET performs a serial read followed by a chained read on the master data set speci ed. If you use the QUICK parameter, only a serial read is performed. The output is in two sections: CHECK SET and CHECK INFORMATION.
problems by reporting slow response time when adding records to a particular data set. Once you have determined if the range should be changed, increase or decrease the data set capacity accordingly. (Refer to \CHANGE SET" in chapter 10, \DBChange Plus Commands.") The CHECK INFORMATION section of the output identi es speci c records in the data set that contain problems. If no problems are found, the following message is displayed: No problems were detected by CHECK.
CHECK INFORMATION Set Name Type Search Item Message(s) -----------------------------------------------------------------------CUSTOMER M Userlabel entry count does not match bitmap entry count (CHK 560). SALES D ACCOUNT (Path 1; linked to master CUSTOMER, path 1) Sum of chain counts in the related master set does not match bitmap entry count for this set (CHK 580). FIX INFORMATION -----------------------------------------------------------------------All problems detected have been fixed. HP36386 (A.00.
Detail Set Name Entries Capacity Full Entry Used Chain Count ----------------------------------------------------------------------SALES 17 504 3 17 0 CHECK INFORMATION Set Name Type Search Item Message(s) -----------------------------------------------------------------------SALES D ACCOUNT (Path 1; linked to master CUSTOMER, path 1) Path Chain inconsistencies detected (CHK 400). HP36386 (A.00.00) DBCHANGE (c) COPYRIGHT Hewlett-Packard Co.
The CHECK INFORMATION section of the output identi es speci c records in the data set that contain problems. If no problems are found, the following message is displayed: No problems were detected by CHECK. Fixing a Detail Data Set Use the FIX SET command to correct problems identi ed by CHECK SET. In the following example, FIX SET is used to correct the problems found in the previous example: >fix set customer If you want to verify that the FIX SET command is pending, use the REVIEW SETS command.
CHECK INFORMATION Set Name Type Search Item Message(s) -----------------------------------------------------------------------CUSTOMER M Userlabel entry count does not match synonym chain count (CHK 570). SALES D ACCOUNT (Path 1; linked to master CUSTOMER, path 1) Sum of chain counts in the related master set does not match bitmap entry count for this set (CHK 580). FIX INFORMATION -----------------------------------------------------------------------All problems detected have been fixed.
Using the QUICK Option with CHECK Commands Note When used with the CHECK PATH, CHECK SET, and CHECK BASE commands, the QUICK option displays a summarized version of the standard CHECK output. The QUICK option performs a serial read only. This method is quicker than standard checking, which uses both serial and chained reads. The QUICK option can identify that a problem exists, but it cannot isolate the speci c records that need to be xed.
After issuing a PERFORM COMMANDS to invoke DBAPLUS, the following output is displayed: Check file ORDERSRX exists; it will be overwritten (DBA 125). Starting data set serial reads. Tabulating statistics. CHECK PATH Pct Set Name Type Max Avg Std Far Avg Packing Search Item (PS) Chain Chain Dev Ptrs Blocks Ratio ---------------------------------------------------------------------SALES D ACCOUNT ( S) 17231 2874.67 7033.14 6 1.17 6.86 Starting data set chained reads.
9 Applying Changes to the Database Structure This chapter explains how to use the DBAPLUS program to apply changes to the database structure. Before reading this chapter, you should be familiar with the information in chapter 1, \Introduction to DBChange Plus." To learn how to do more DBChange Plus tasks, refer to chapters 2 through 8. If you understand DBChange Plus tasks and only want to see command syntax information, refer to chapter 10, \DBChange Plus Commands.
2. Make sure that all security criteria have been met. To use the DBAPLUS program, you must be logged on as the database creator. The DBAPLUS program checks that the logged-on user matches the logon stored in the change le. If it does not, a security violation message is displayed and the DBAPLUS program terminates. 3. Ensure that adequate disk space is available for the DBAPLUS program to perform the restructure. To estimate how much disk space you need, rst identify the data sets being altered.
Saving the New Schema The DBAPLUS program creates a new schema based on the changes stored in the change le. This schema is used when the DBAPLUS program calls DBSCHEMA to build a new root le. The new schema is placed in a temporary le named dbname SC. (Any temporary le with the same name will be purged.) You must use the MPE XL SAVE command on this new schema le if you want to keep it as a permanent MPE XL le.
Initiating the DBAPLUS Program Interactively 9-4 The DBAPLUS program can be invoked interactively to perform a restructure from within the DBCPLUS program. To invoke the DBAPLUS program this way, do the following: 1. Run the DBCPLUS program (DBCPLUS). 2. Issue the BASE command to specify the database to be restructured. 3. Issue one or more DBCPLUS restructure commands. Issue a PERFORM COMMANDS to immediately invoke the DBAPLUS program.
>perform commands PERFORM COMMANDS now or create job file [job/y/N]? y Please wait ... HP36386 (A.00.00) DBALTER (c) COPYRIGHT Hewlett-Packard Co. 1985 THU, JAN 18, 1990 7:15 AM Database has been modified since last DBSTORE (DBA 220). Continue [y/N]? y HP36386 (A.00.00) DBCHANGE (c) COPYRIGHT Hewlett-Packard Co. 1985 Creating a DBAPLUS Job File from within the DBChange Program The DBAPLUS program can be invoked by creating a job le from within the DBCPLUS program.
For more information about PARM values, refer to \Using PARM Values" later in this chapter.
Modifying the Job File When instructed to do so, DBChange creates a job stream le for each existing change le. The name of this job stream le is the database name with JJ appended ( DatabaseName JJ). Use this job stream le to perform a restructure in batch mode. This job stream le does the following: Sets a le equation for the change le. Sets DBSLIST to $NULL to suppress the listing of the new schema.
: :comment* verify that DBALTER parmvalue is correct : :run dbaplus; parm = 1 : :comment*********************************************** :comment* :save ORDERSSC :comment*********************************************** : :tell KELLY.FINANCE; /-->End JDBALTER for ORDERS : :eoj In the example below, the ORDERS job stream le, ORDERSJJ, has been edited to add passwords, to change the parameter of the RUN DBALTER command, and to remove the \commented out" portions that save the new schema le.
Running the DBAPLUS Program Independently You can invoke the DBAPLUS program independent of the DBCPLUS program in two ways, as follows: Issue a le equation for DBCHGF, the formal le designator for the change le. Next, run the DBAPLUS program providing a parm value. For example: :hello kelly.finance,database :file dbchgf=orderscf :run dbaplus.pub.sys;parm=1 The DBAPLUS program determines the database name from the name of the change le in the le equation.
Table 9-1 describes the parameter values and which DBAPLUS questions they answer. Table 9-1. DBAPLUS Parameters PARM You do not have enough disk Value space to build all necessary temporary data sets before beginning the restructure. Do you want DBAPLUS to continue with the restructure using an alternative restructuring method? The database has been modi ed since the last DBSTORE. Do you wish to continue? Your root le is not in normal DBSCHEMA format.
Caution If one of the stored changes in the change le is the reordering of data sets, you should not have any temporary les named ALTERnn where nn is the number of one of the data sets in the database. The DBAPLUS program creates temporary les with these names and overwrites your temporary les. Do not create a database with the name TEMPDB. The DBAPLUS program creates a le name TEMPDB to restructure master data set. Your TEMPDB le will be purged and can also prevent the DBAPLUS from processing.
When a detail data set is repacked, the chain pointers in the master data set linked to the detail data set are adjusted. The pointers in the detail data set are also adjusted. 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.
> In the previous example, the DBAPLUS program was able to nd enough disk space to create all the temporary les before beginning the restructure. However, if the DBAPLUS program is unable to create all the temporary les 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.
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.
10 DBChange Plus Commands This chapter provides detailed command syntax descriptions of the DBChange Plus commands. The commands appear alphabetically. Before reading this chapter, you should be familiar with the information in chapter 1, \Introduction to DBChange Plus." To learn about more DBChange Plus tasks, refer to chapters 2 through 9. For a complete list of tasks and where to nd them in this guide, refer to the preface.
per line maximum or the 216 total maximum. If a command does not t on one line, use an ampersand (&), preceded by a blank or comma, as the last character on a line to indicate that the command is continued on the next line. Only one command per command line is allowed. A command can be up to three lines. Summary of DBChange Plus Table 10-1 summarizes the DBChange Plus commands and provides command abbreviations.
Table 10-1. Summary of DBChange Plus Commands Command ADD Keyword Abbreviation Description FIELD AF Adds a eld (data item) to a manual master or detail data set. ITEM A ITEM Adds a data item to the database. PASSWORD A PAS Adds a password to the database. PATH A PAT Adds a path from a detail data set to a master data set and de nes a search item. SET A SET Adds a master or detail data set to the database. SORT A SO Adds a sort item to a search item.
Table 10-1. Summary of DBChange Plus Commands (continued) Command CHECK Keyword Description BASE CHE BA Checks the root le, all data sets, and all paths in the database for structural integrity and reports any problems. PATH CHE PAT Checks paths for broken chains and incorrect pointer linkages and reports any problems. SET CHE SET Checks data sets for internal or pointer inconsistency and reports any problems.
Table 10-1. Summary of DBChange Plus Commands (continued) Command Keyword Abbreviation Description PERFORM COMMANDS PE COM Invokes DBAPLUS to restructure, check, or maintain the database according to the commands stored in the current change le. PRINT PR SC Prints the database schema, applying any changes stored in the current change le. REC ITEM Cancels a data item deletion. REC SET Cancels a data set deletion. R Allows a user to correct or modify the last DBChange Plus command entered.
Adds a eld (data item) to a manual master or detail data set. ADD FIELD A[DD] F[IELD] DataSetName FieldName [( NextField)] Syntax Parameters DataSetName FieldName (NextField) Description is the name of the manual master or detail data set to which the eld will be added. is the name of the eld to be added. It must already exist as a data item in either the change le or the database. is the existing eld that will follow the newly added eld in the schema.
ADD FIELD After the addition, the schema entry for the INVENTORY detail data set looks like this: NAME: ENTRY: INVENTORY STOCK# ONHANDQTY STORE# SUPPLIER UNIT-COST LASTSHIPDATE BINNUM CAPACITY: 450(15); ,D(12,14/13,18); (PRODUCT ), , , <---- new eld added (!SUPMASTER ), , ( DATE-MASTER), ; DBChange Plus Commands 10-7
Adds a data item to the database. ADD ITEM Syntax A[DD] ITEM ItemName [( NextItem)] [ SubitemCount] SubitemType SubitemLength [([ ReadClassList]/[ WriteClassList])] Parameters ItemName (NextItem) SubitemCount SubitemType SubitemLength (ReadClassList/ WriteClassList) 10-8 DBChange Plus Commands is the name of the data item to be added. Each data item within the database must have a unique name. This name must be from 1 to 16 characters, the rst of which must be alphabetic.
ADD ITEM classes can read the data item unless access is further restricted by data set security. Note that access to a data item is only possible when the data item is a eld in a data entry. The two class lists are de ned as follows: (ReadClassList) is a list of the user classes that have read-only access to the added item. It can consist of user class numbers from 0 to 63, separated by commas.
ADD ITEM example, (12,14/)], no user class has write access to the data item unless access is allowed by data set security. However, the database creator can write to the data item. Description Use this command to add a new data item to the database.
ADD ITEM After the addition, the ITEMS part of the schema looks like this: ITEMS: ACCOUNT BINNUM . . .
ADD PASSWORD Adds a password to the database. A[DD] PAS[SWORD] Password UserClass Syntax Parameters is the new password. Passwords are case sensitive and are not upshifted like other schema names. Therefore, an uppercase character is distinguished from a lowercase character. A password must be from 1 to 8 characters, excluding carriage returns, slashes, semicolons, and blanks. is the user class number associated with the new password.
ADD PASSWORD After the addition, the PASSWORDS part of the schema looks like this: PASSWORDS: 11 CREDIT 12 BUYER 13 SHIP-REC 14 CLERK 18 DO-ALL 20 MANAGER ; ; ; ; ; ; <---- password added DBChange Plus Commands 10-13
Adds a path to a detail data set. ADD PATH Syntax A[DD] PAT[H] DetailDataSetName SearchItemName [!] MasterDataSetName [ SortItemName] Parameters DetailDataSetName SearchItemName ! MasterDataSetName SortItemName Description is the name of the detail data set that will contain the new path. is the name of the search item for the new path. indicates that the new path is to be the primary path. Only one path in a detail data set can be designated as the primary path.
ADD PATH Before the addition, the schema entry for the INVENTORY data set looks like this (note that the path to SUP{MASTER is the existing primary path): NAME: ENTRY: INVENTORY ,D(12,14/13,18); STOCK# , ONHANDQTY , SUPPLIER (!SUP-MASTER ), UNIT-COST , LASTSHIPDATE (DATE-MASTER ), BINNUM ; CAPACITY: 450(15); <---- path to be added <---- path to be changed After the addition, the schema entry for the INVENTORY data set looks like this: NAME: ENTRY: INVENTORY ,D(12,14/13,18); STOCK# (!PRODUCT ), ONHANDQT
Adds a new master or detail data set to the database. ADD SET Syntax 2 2 9 : D 3 3 ; DataSetName A M D KeyItem (ReadClassList/ WriteClassList) DBChange Plus Commands 3 2 KeyItem = M KeyItem ) SetCapacity ( ReadClassList32 / WriteClassList 3 ( BlockFactor) DeviceClass (NextSet) 10-16 8 A 3< A DD SET DataSetName ( NextSet) 2 2 Parameters 2 3 is the name of the data set to be added. This name must be from 1 to 16 characters, the rst of which must be alphabetic.
ADD SET SetCapacity (BlockFactor) the new data set. It can consist of user class numbers from 0 to 63, separated by commas. If this parameter is empty [for example, (/12,14)], only users with write access can read the data set. However, the database creator can read the data set. (WriteClassList) is a list of user classes that have write access to the new data set. It can consist of user class numbers from 0 to 63, separated by commas.
ADD SET DeviceClass Description words or for a block size speci ed by the DBSchema $CONTROL command or by the CHANGE BLOCKMAX command. is the disk on which the data set will reside. If this parameter is omitted, DBSCHEMA defaults to device class DISK. Use this command to add a new data set to the database. When adding master data sets, the KeyItem parameter must be used. Also remember that all master data sets must appear in the schema before their related detail data sets.
ADD SET SETS: NAME: ENTRY: CUSTOMER ,M(14/11,18); ACCOUNT (1) LAST-NAME FIRST-NAME INITIAL STREET-ADD CITY STATE CREDIT-RATING CAPACITY: 221(10); , , , , , , , ; NAME: DATE-MASTER ,A(0,11,12,13,14,18/) ENTRY: DATE (3) CAPACITY: 211(9); NAME: ENTRY: PRODUCT ,M(13,14/12,18) STOCK# (2) DESCRIPTION CAPACITY: 307(16) NAME: ENTRY: SALES ,D(11/14,18) ACCOUNT ( CUSTOMER (PURCH-DATE) STOCK# (!PRODUCT QUANTITY PRICE TAX TOTAL PURCH-DATE ( DATE-MASTER DELIV-DATE ( DATE-MASTER CAPACITY: 504(14); NAME: ENTRY: SUP
ADD SET BINNUM CAPACITY: 450(15); END.
ADD SET After the addition, the SETS part of the schema looks like this: SETS: NAME: ENTRY: CUSTOMER ,M(14/11,18); ACCOUNT (1) LAST-NAME FIRST-NAME INITIAL STREET-ADD CITY STATE CREDIT-RATING CAPACITY: 221(10); , , , , , , , ; NAME: DATE-MASTER ,A(0,11,12,13,14,18/); ENTRY: DATE (2) CAPACITY: 211(19); ; NAME: ENTRY: PRODUCT ,M(13,14/12,18); STOCK# (1) DESCRIPTION CAPACITY: 307(16); NAME: ENTRY: SALES ,D(11/14,18); ACCOUNT ( CUSTOMER (PURCH-DATE) STOCK# (!PRODUCT QUANTITY PRICE TAX TOTAL PURCH-DATE (
ADD SET NAME: ENTRY: INVENTORY ,D(12,14/13,18); STOCK# (PRODUCT ONHANDQTY SUPPLIER (!SUP-MASTER UNIT-COST LASTSHIPDATE ( DATE-MASTER BINNUM CAPACITY: 450(15); END.
ADD SORT Adds a new sort item to a search item of a path. ADD SORT Syntax A[DD] SO[RT] DetailDataSetName SearchItemName SortItemName Parameters DetailDataSetName SearchItemName SortItemName Description Example is the name of the detail data set for the new sort item. is the name of the search item whose chains are sorted based on the new sort item values. is the name of the new sort item. It must be an existing eld in the data set.
ADD SORT After the addition, the SALES data set entry in the schema looks like this: NAME: ENTRY: CAPACITY: 10-24 DBChange Plus Commands SALES ,D(11/14,18); ACCOUNT ( CUSTOMER (PURCH-DATE)), <---- sort item added STOCK# (!PRODUCT ), QUANTITY , PRICE , TAX , TOTAL , PURCH-DATE ( DATE-MASTER ), DELIV-DATE ( DATE-MASTER ); 504(14);
BASE Speci es the database to be modi ed. BASE Syntax Parameters 2 3 DatabaseName NEW OLD PURGECF Description 3 NEW 5 B ASE DatabaseName 4 OLD PURGECF 2 is the name of the database to be modi ed. It cannot be quali ed with the group and account names. creates a new change le ( DatabaseName CF). If an old change le exists, it is purged. This parameter is the default. uses the existing change le and adds to it. purges the existing change le without creating a new change le.
BASE >base orders purgecf To purge change file, confirm purge [y/N] ? y Change file ORDERSCF has been purged. Example No old change file. Create new file [y/N] ? y Creating new change file: Creating new change file: item information records Creating new change file: set information records Creating new change file: security table Creating new change file: control record > In this example, the existing change le for the ORDERS database is purged.
CANCEL COMMANDS Cancels all changes entered in the change le since the last BASE command. CANCEL COMMANDS CA[NCEL] COM[MANDS] Syntax Description Use this command to cancel all changes entered since the last BASE command. After issuing CANCEL COMMANDS, the change le returns to the state it was in just after the most recent BASE command. To continue using the DBCPLUS program after issuing CANCEL COMMANDS, you must issue a new BASE command.
CANCEL COMMANDS STATE STOCK# STREET-ADD SUPPLIER TAX TOTAL UNIT-COST ZIP , , , , , , , , X2(12,13,14/11); U8(0,11,12,14,18/); X26(12,13,14/11); X16(12,13/); J2(14/); J2(11,14/); P8(/12); X6(12,13,14/11); SETS: . . .
CANCEL COMMANDS TOTAL UNIT-COST ZIP SHIP-COST , , , , J2(11,14/); P8(/12); X6(12,13,14/11); J4(/12,13,14,18); <---- data item added SETS: .. .
CANCEL COMMANDS SETS: . . .
CANCEL ERASE CANCEL ERASE Syntax Cancels the previous ERASE SET command. CAN[CEL] E[RASE] DataSetName is the name of the data set which should not be erased. Parameters DataSetName Description Use this command to cancel a previous ERASE SET command stored in the change le for a speci ed data set. Note that once DBAPLUS has been run, the erased data set entries cannot be recovered. Example >erase set inventory To confirm erase of data set, enter [y/N].y Erase Set issued for data set.
CANCEL REPACK Cancels the previous REPACK SET command. CAN[CEL] RE[PACK] DataSetName Syntax is the name of the data set which should not be repacked. Parameters DataSetName Description Use this command to cancel a previous REPACK SET command stored in the change le for a speci ed data set. Note that once DBAPLUS has been run, the REPACK SET command cannot be canceled. >repack set sales chained REPACK SET issued for data set. Example >cancel repack sales Cancel repack of data set.
CHANGE ATTRIBUTES Changes the subitem count, type, and/or length of a data item. CHANGE ATTRIBUTES Syntax CHA[NGE] A[TTRIBUTES] DataItemName [ SubitemCount] SubitemType SubitemLength Parameters DataItemName SubitemCount SubitemType SubitemLength Description is the name of the data item whose attributes are changed. Each data item within the database must have a unique name. This name must be from 1 to 16 characters, the rst of which must be alphabetic.
CHANGE ATTRIBUTES >change attributes store# X 4 Example In this example, the attributes of the data item STORE# are changed. The subitem type is changed to X and the subitem length to 4. Because the SubitemCount parameter is not speci ed, the subitem count does not change.
CHANGE ATTRIBUTES After attributes change, the ITEMS part of the schema looks like this: ITEMS: ACCOUNT BINNUM CITY CREDIT-RATING DATE DELIV-DATE DESCRIPTION FIRST-NAME INITIAL LAST-NAME LASTSHIPDATE ONHANDQTY PRICE PURCH-DATE QUANTITY STATE STOCK# STREET-ADD SUPPLIER TAX TOTAL UNIT-COST ZIP STORE# , , , , , , , , , , , , , , , , , , , , , , , , J2(0,11,12,13,14,18/); Z2(/13); X12(12,13,14,/11); R2(/14); X6(0,11,12,13,14,18/); X6((/14); X20(0,11,12,13,14,18/); X10(14/11); U2(14/11); X16(14/11); X6(12/);
Changes the blocking factor of a data set. CHANGE BLOCKFACTOR CHA[NGE] BLOCKF[ACTOR] DataSetName NewBlockFactor Syntax Parameters DataSetName NewBlockFactor Description is the name of the data set to be reblocked. is the number of data set records in one block. If zero is speci ed, it takes the value calculated by DBSCHEMA. Use this command to change the blocking factor of a data set.
CHANGE BLOCKFACTOR CAPACITY: 504(14); <---- blocking factor to be changed DBChange Plus Commands 10-37
CHANGE BLOCKFACTOR After the change, the SALES data set entry in the schema looks like this: NAME: ENTRY: SALES ACCOUNT STOCK# QUANTITY PRICE TAX TOTAL PURCH-DATE DELIV-DATE CAPACITY: 504(16); 10-38 DBChange Plus Commands ,D(11/14,18); ( CUSTOMER ( PURCH-DATE )), (!PRODUCT ), , , , , ( DATE-MASTER ), ( DATE-MASTER ); <---- blocking factor changed
CHANGE BLOCKMAX Changes the maximum block length of one or more data sets. CHANGE BLOCKMAX Syntax 2 3 2 CHA NGE BLOCKM AX BlockMaxNumber Parameters DataSetName FirstDataSetName / LastDataSetName @ BlockMaxNumber Description 8 DataSetName 3< : 9 = FirstDataSetName/LastDataSetName ; @ is the name of the data set to be assigned the new maximum block length. are names that de ne a range of data sets to be assigned the new maximum block length.
CHANGE BLOCKMAX Before the change, the SALES data set entry in the schema looks like this: $CONTROL BLOCKMAX = 640 NAME: SALES ,D(11/14,18); ENTRY: ACCOUNT ( CUSTOMER (PURCH-DATE STOCK# (!PRODUCT QUANTITY PRICE TAX TOTAL PURCH-DATE ( DATE-MASTER DELIV-DATE ( DATE-MASTER CAPACITY: 504(14); <---- block length to be changed )), ), , , , , ), ); After the change, the SALES data set entry in the schema looks like this: $CONTROL BLOCKMAX = 1024 NAME: SALES ,D(11/14,18); ENTRY: ACCOUNT ( CUSTOMER (PURCH-DATE ST
CHANGE CAPACITY CHANGE CAPACITY Syntax Parameters Changes the capacity of a data set. CHA[NGE] CA[PACITY] DataSetName NewCapacity DataSetName NewCapacity is the name of the data set whose capacity is to be changed. is the new capacity of the data set. It must be less than 231 01 (2,147,483,647), but cannot be less than the current number of entries in the data set. Description Use this command to change the capacity of a data set.
CHANGE CAPACITY After the change, the INVENTORY data set entry in the schema looks like this: NAME: ENTRY: INVENTORY ,D(12/13,14,18); STOCK# ( PRODUCT ), ONHANDQTY , SUPPLIER (!SUP-MASTER ), UNIT-COST , LASTSHIPDATE ( DATE-MASTER ), BINNUM ; CAPACITY: 510(15); <---- capacity changed 10-42 DBChange Plus Commands
CHANGE DEVICECLASS Moves a data set from one device (disk) to another. CHANGE DEVICECLASS Syntax Parameters CHA[NGE] D[EVICECLASS] DataSetName NewDeviceClass DataSetName NewDeviceClass Description Example is the name of the data set whose device class is to be changed. is the class of the device where the data set will reside. Use this command to move a data set to another device. A device class can span multiple disk drives.
CHANGE ITEM Changes the subitem count, type, length, security, and/or order of a data item. (For information about supported item type conversions, refer to Table 10-2 later in this section.) Syntax CHA[NGE] ITEM DataItemName [( NextItem)] [ SubitemCount] SubitemType SubitemLength [([ ReadClassList]/[ WriteClassList])] Parameters DataItemName (NextItem) SubitemCount SubitemType SubitemLength 10-44 DBChange Plus Commands is the name of the data item to be changed.
CHANGE ITEM (ReadClassList/ WriteClassList) de nes user class access to the data set. If this entire parameter is omitted, the data item security remains unchanged. The class lists are de ned as follows: (ReadClassList) is a list of user classes having read access to the data set. It can consist of user class numbers from 0 to 63, separated by commas. If this parameter is empty [for example, (/12,14)], read access to the data set remains unchanged.
CHANGE ITEM Description Use this command when making several data item changes at the same time. Note Several parameters are interrelated. For example, if you enter the subitem count, you must enter the subitem type and the subitem length, even if the last two parameters have not changed. The SubitemType and SubitemLength parameters are also interrelated. If you enter one, you must enter the other, even if only one has changed.
CHANGE ITEM Example >change item deliv-date 2 u 6 (/11,14) In this example, the subitem count of the data item DELIV{DATE is changed to 2, the subitem type to U, and the subitem length to 6. User class 11 has also been given write access to the data item. Note that the subitem length must be entered even though it has not been changed. Because NextItem was not entered, the data item order remains the same.
CHANGE ITEM LASTSHIPDATE ONHANDQTY PRICE PURCH-DATE QUANTITY STATE STOCK# STREET-ADD SUPPLIER TAX TOTAL UNIT-COST ZIP STORE# 10-48 DBChange Plus Commands , , , , , , , , , , , , , , X6(12/); J2(14/12); J2(14/); X6(11/14); I1(/14); X2(12,13,14,/11); U8(0,11,12,13,14,18/); S26(12,13,14/11); X16(12,13/); J2(14/); J2(11,14); P8(/12); X6(12,13,14/11); J2(11,12/14);
CHANGE ITEMSECURITY Changes user class access to a data item. CHANGE ITEMSECURITY 2 Parameters 3 DataItemName UserClassNumber R W N Description Example 2 3 CHA NGE ITEMSE CURITY DataItemName UserClassNumber 8 9
CHANGE ITEMSECURITY DESCRIPTION FIRST-NAME INITIAL LAST-NAME LASTSHIPDATE ONHANDQTY PRICE PURCH-DATE QUANTITY STATE STOCK# STREET-ADD SUPPLIER TAX TOTAL UNIT-COST ZIP , , , , , , , , , , , , , , , , , X20(0,11,12,13,14,18/); X10(14/11); U2(14/11); X16(14/11); X6(12/); J2(14/12); J2(14/); X6(11/14); I1(/14); <---- security to be changed X2(12,13,14,/11); U8(0,11,12,13,14,18/); S26(12,13,14/11); X16(12,13/); J2(14/); J2(11,14); P8(/12); X6(12,13,14/11); After the change, the ITEMS part of the schema looks
CHANGE PASSWORD Changes a password. CHANGE PASSWORD Syntax CHA[NGE] PAS[SWORD] OldPassword NewPassword [ UserClass] Parameters is the password to be changed. is the new password. Passwords are case sensitive; that is, uppercase is distinguished from lowercase by TurboIMAGE/XL. A password must be from 1 to 8 characters long. It cannot include carriage returns, slashes (/ or n), semicolons (;), or blanks. is the user class to be changed.
Changes the primary path of a detail data set. CHANGE PRIMARYPATH CHA[NGE] PRI[MARYPATH] DataSetName SearchItemName Syntax Parameters DataSetName SearchItemName Description is the name of the detail data set whose primary path is to be changed. is the name of the search item for the new primary path. Use this command to change the primary path of a detail data set.
CHANGE SETSECURITY Changes user class access to a data set. CHANGE SETSECURITY Syntax Parameters 2 3 3 CHA NGE SETSE CURITY DataSetName UserClassNumber DataSetName UserClassNumber R W N Description 2 8 9
CHANGE SETSECURITY After the changes, the data set entry in the schema looks like this: INVENTORY ,D(14/13,18); <---- security changed STOCK# ( PRODUCT ), ONHANDQTY , SUPPLIER (!SUP-MASTER ), UNIT-COST , LASTSHIPDATE ( DATE-MASTER ), BINNUM ; CAPACITY: 450(15); NAME: ENTRY: 10-54 DBChange Plus Commands
CHECK BASE Checks all data sets and all paths in the database for structural integrity and reports any problems. CHECK BASE Syntax Parameters CHE[CK] BA[SE] [ Quick] Quick is a fast method of checking the database to validate pointer integrity. If you specify the Quick parameter, the database is examined using a serial read. Using this option, the command reports if the database has a problem, but it does not indicate the location.
CHECK BASE ..... Tabulating statistics. CHECK SET (MASTER) Pct Pct Longest Average Master Set Name Type Entries Capacity Full Sec Cluster Cluster ----------------------------------------------------------------------CUSTOMER M 9 221 4 11.1 0 0.0 PRODUCT M 32 307 10 6.3 0 0.0 SUP-MASTER M 6 211 3 0.0 0 0.
CHECK BASE CHECK INFORMATION Set Name Type Search Item Message(s) -----------------------------------------------------------------------CUSTOMER M Userlabel entry count does not match synonym chain count (CHK 570). Record 6 is not linked into the proper synonym chain (CHK 360). SALES D ACCOUNT (Path 1; linked to master CUSTOMER, path 1) Path Chain inconsistencies detected (CHK 400). Sum of chain counts in the related master set does not match bitmap entry count for this set (CHK 580).
CHECK BASE Following is a description of the CHECK BASE output: CHECK SET (Master) Output Master Set Name Type Entries Capacity Pct Full Pct Sec Longest Cluster Average Cluster is the name of the master data set being checked. is the type of master data set being checked. A is for automatic master; M is for manual master. is the number of entries the data set contains. is the capacity of the data set.
CHECK BASE Search Item Name Type Max Chain Avg Chain Std Dev Pct Far Ptrs Avg Blocks Packing Ratio is the name of the search item. Because master data sets do not contain search items, but rather key items, the text SYNONYM CHAINS appears in the eld instead. For detail data sets, the search item name appears in the eld. is the data set type. Valid data set types are as follows: M is for manual master data sets. A is for automatic master data sets. D is for detail data sets.
CHECK BASE Example 2 In the example below, the ORDERS database is checked using the CHECK BASE command with the Quick parameter. A description of the output follows the example. >base orders >check base quick CHECK BASE (CHECK ROOT, CHECK SET and CHECK PATH) pending for 5 set(s). >perform commands PERFORM COMMANDS now or create job file [job/y/N]? y Please wait ... HP36386 (A.00.00) DBALTER (c) COPYRIGHT Hewlett-Packard Co.
CHECK BASE CHECK SET (MASTER) Pct Pct Longest Average Master Set Name Type Entries Capacity Full Sec Cluster Cluster ----------------------------------------------------------------------CUSTOMER M 9 221 4 11.1 0 0.0 PRODUCT M 32 307 10 6.3 0 0.0 SUP-MASTER M 6 211 3 0.0 0 0.
CHECK BASE CHECK INFORMATION Set Name Type Search Item Message(s) -----------------------------------------------------------------------ROOT FILE Root file inconsistency in area other than path sequence. This cannot be fixed by DBChange (CHK 220). CUSTOMER M Userlabel entry count does not match synonym chain count (CHK 570). SALES D ACCOUNT (Path 1; linked to master CUSTOMER, path 1) Path Chain inconsistencies detected (CHK 400).
CHECK PATH Checks paths for broken chains and incorrect pointer linkages and reports any problems. CHECK PATH Syntax 2 3 2 CHE CK PAT H 2 Parameters Quick 3 @ MasterSetName DetailSetName Quick 3 8 @ > > < MasterSetName > > : DetailSetName (@) (SearchItemName) 9 > > = > > ; indicates that you want to check all paths in all data sets in the database. is the name of the master data set whose synonym chains should be checked.
CHECK PATH Example 1 In the example below, all the paths in the ORDERS database are checked using the CHECK PATH command without the Quick parameter. A description of the output follows the example. >base orders >check path @ Check Path issued for 5 set(s). >perform commands PERFORM COMMANDS now or create job file [job/y/N]? y Please wait ... HP36386 (A.00.00) DBALTER (c) COPYRIGHT Hewlett-Packard Co. 1985 FRI, MAY 25, 1990, 11:12 AM Database has been modified since last DBSTORE (DBA 220).
CHECK PATH Starting data set chained reads. ...... CHECK INFORMATION Set Name Type Search Item Message(s) -----------------------------------------------------------------------CUSTOMER M Userlabel entry count does not match synonym chain count (CHK 570). Record 6 is not linked into the proper synonym chain (CHK 360). SALES D ACCOUNT (Path 1; linked to master CUSTOMER, path 1) Path Chain inconsistencies detected (CHK 400).
CHECK PATH Max Chain Avg Chain Std Dev Pct Far Ptrs Avg Blocks Packing Ratio Example 2 Other codes that appear in this column are as follows: P designates primary paths. S designates sort items. is the maximum number of entries in the longest synonym or detail chain. is the average number of entries per chain. is the standard deviation, which indicates the accuracy of the Avg Chain statistic. The closer to 0.00 this number is, the more accurate the Avg Chain statistic is. is percent far pointers.
CHECK PATH Set Name Type Max Avg Std Far Avg Packing Search Item (PS) Chain Chain Dev Ptrs Blocks Ratio ---------------------------------------------------------------------INVENTORY D STOCK# 1 1.00 0.00 0 1.00 1.00 SUPPLIER (P ) 5 5.00 0.00 0 1.00 1.00 Starting data set chained reads.
CHECK PATH CHECK INFORMATION Set Name Type Search Item Message(s) -----------------------------------------------------------------------No problems were detected by CHECK. HP36386 (A.00.00) DBCHANGE (c) COPYRIGHT Hewlett-Packard Co. 1985 The output for the CHECK PATH command using the Quick parameter is the same as the standard CHECK PATH output; however, a summary version of the standard CHECK INFORMATION output is displayed.
CHECK SET Checks data sets for internal or pointer inconsistency and reports any problems. CHECK SET 2 Syntax Parameters 3 CHE CK SET DataSetName @ DataSetName @ Quick 2 Quick 3 is the name of the data set which should be checked. indicates that all data sets in the database should be checked. is a fast method of checking data sets to validate pointer integrity. If you specify the Quick parameter, the data sets are examined using a serial read.
CHECK SET Database has been modified since last DBSTORE (DBA 220). Continue [y/N] ? y Starting data set serial reads. Tabulating statistics.
CHECK SET Example 2 In the example below, the master data set CUSTOMER in the ORDERS database is checked using the CHECK SET command without the Quick parameter. A description of the output follows the example. >base orders >check set customer CHECK SET issued for 1 set(s). >perform commands PERFORM COMMANDS now or create job file [job/y/N]? y Please wait ... HP36386 (A.00.00) DBALTER (c) COPYRIGHT Hewlett-Packard Co.
CHECK SET Following is a description of the CHECK SET output for a master data set: Master Set Name is the name of the master data set being checked. Type is the type of master data set being checked. A is for automatic master; M is for manual master. Entries is the number of entries the data set contains. Capacity is the capacity of the data set. Pct Full is the percentage of the data set capacity, rounded to the nearest whole percentage, that is not available.
CONTROL Speci es the setting of several options controlling the way DBChange operates. Automatically adjusts data set capacities. CONTROL Syntax Parameters 2 3 CON TROL 3 2 LIST 5 4 NOLIST 3 2 PERCENTFULL DataSet MinFull MaxFull NewFull LIST NOLIST PERCENTFULL writes all commands, their parameters, and any messages to $STDLIST or the designated output device according to the le equation that is set for DBCOUT. This parameter is the default. displays messages and program output only.
CONTROL MinFull MaxFull NewFull data sets in the database. @ indicates that the CONTROL PERCENTFULL command applies to all data sets in the database. is the percent of the data set capacity at which the speci ed data set(s) is agged for reduction. If the data set capacity falls below the MinFull amount, DBChange Plus immediately prints a warning. Zero is a valid value. is the percent of the data set capacity at which the speci ed data set(s) is agged for expansion.
CONTROL Description Use this command to control the following DBChange operations: To suppress commands and their parameters to $STDLIST during DBChange command execution, whether interactively or batch. To determine minimum and maximum data set capacity for reduction or expansion. To determine user access to the database while checking is in progress. The CONTROL command can be issued multiple times. However, each command overrides the previous command.
Copies a database. COPY COPY OldBaseName [ NewBaseName] [(REPLACE)] Syntax Parameters OldBaseName NewBaseName (REPLACE) Description is the name of the existing database to be copied. The OldBaseName can be fully quali ed using the MPE XL le name conventions of Name.Group.Account . is the name of the new copy of the database. The NewBaseName can only be quali ed with the MPE XL Group name. If this parameter is omitted, the OldBaseName is used, and the database is placed in the logon group.account.
COPY When copying a database from another account with only OP+PM capabilities, you must rst pass MPE XL security or have the database released. Example :hello kelly.testacct.testgrp :dbcplus HP36386 (A.00.00) DBCHANGE (c) COPYRIGHT Hewlett-Packard Co. 1985 FRI, JUN 15, 1990, 3:00 PM >copy orders.shipping.database copy ORDERS.SHIPPING.DATABASE ==> ORDERS.TESTGRP.TESTACCT [y/N]? y Database ORDERS.TESTGRP.TESTACCT already exists. Replace [y/N]? y HP36386 (A.00.00) DBALTER (c) COPYRIGHT Hewlett-Packard Co.
Deletes a eld from a manual master or detail data set. DELETE FIELD D[ELETE] F[IELD] DataSetName FieldName Syntax Parameters DataSetName FieldName Description Caution is the name of the data set from which the eld is to be deleted. is the name of the eld to be deleted. Use this command to delete a eld from a manual master or detail data set. The deletion of a eld will cause loss of data. If you are deleting a search item, you must delete the path before you can delete the eld.
DELETE ITEM Deletes a data item and its associated elds and paths from the database. DELETE ITEM D[ELETE] ITEM DataItemName Syntax is the name of the data item to be deleted. Parameters DataItemName Description Use this command to delete a data item from the ITEMS part of the schema and from any data set in which it is used as a eld. The deletion of a data item causes loss of data and, if the data item is a search item, deletion of paths associated with the search item.
DELETE ITEM CAPACITY: 221(10); NAME: DATE-MASTER ,A(0,11,12,13,14,18/); ENTRY: DATE (3) CAPACITY: 211(9); ; NAME: ENTRY: PRODUCT ,M(13,14/12,18); STOCK# (2) DESCRIPTION CAPACITY: 307(16); , ; . . . NAME: ENTRY: SUP-MASTER ,M(13/12,18); SUPPLIER (1) , . . . ZIP CAPACITY: 211(12); ; <---- to be deleted . . . END. After the deletion, the ITEMS and SETS parts of the schema look like this: ITEMS: ACCOUNT BINNUM , J2(0,11,12,13,14,18/); , Z2(/13); . . .
DELETE ITEM ENTRY: DATE CAPACITY: 211(19); (3) NAME: ENTRY: PRODUCT ,M(13,14/12,18); STOCK# (2) DESCRIPTION CAPACITY: 307(16); ; , ; . . . NAME: ENTRY: SUP-MASTER SUPPLIER ,M(13/12,18); (1) , . . . STATE CAPACITY: 211(12); ; <---- ZIP deleted here . . . END.
Deletes all security speci cations from a data item. DELETE ITEMSECURITY D[ELETE] ITEMSE[CURITY] DataItemName Syntax is the name of the data item whose security speci cations are to be removed. Parameters DataItemName Description Use this command to delete all security speci cations from a data item, which results in an absent list. This command is necessary because without it, you can only delete user classes from the security list, creating a null (or empty) list (/), not an absent list.
DELETE PASSWORD DELETE PASSWORD Deletes a password and its associated user class from the database. D[ELETE] PAS[SWORD] Password UserClass Syntax Parmeters Password UserClass Description is the name of the password to be deleted from the database. is the associated user class to be deleted. Use this command to delete a password and its associated user class from the PASSWORDS section of the schema list. In interactive mode, a con rmation message asks you to con rm the deletion of the password.
Deletes a path from a detail data set to a master data set. DELETE PATH D[ELETE] PAT[H] DataSetName SearchItemName Syntax Parameters DataSetName SearchItemName Description is the name of the detail data set of the path to be deleted. is the name of the search item de ning the path to be deleted. Use this command to delete a path between a detail data set and a master data set. This command also changes the search item to a non-key item.
DELETE PATH After the deletion, the schema entry for the data set INVENTORY looks like this: NAME: ENTRY: INVENTORY ,D(12,14/13,18); STOCK# , ONHANDQTY , SUPPLIER ), UNIT-COST (!SUP-MASTER ), LASTSHIPDATE ( DATE-MASTER ), BINNUM ; CAPACITY: 450(15); <---- path deleted After the deletion, STOCK# is still a data item in the data set INVENTORY; however, it is no longer a search item.
Deletes a master or detail data set and all associated paths from a database. DELETE SET D[ELETE] SET DataSetName Syntax is the name of the data set to be deleted. Parameters DataSetName Description Use this command to delete a data set and its associated paths from a database. The deletion of a data set causes loss of data. If the data set contains the only path to an automatic master, the path and the automatic master are also deleted. Therefore, use caution when deleting data sets.
DELETE SET NAME: ENTRY: SALES ACCOUNT STOCK# QUANTITY PRICE TAX TOTAL PURCH-DATE DELIV-DATE CAPACITY: 504(14); ,D(11/14,18); ( CUSTOMER (PURCH-DATE )), (!PRODUCT ), , , , , ( DATE-MASTER ), ( DATE-MASTER ); NAME: ENTRY: ,M(13/12,18); (1) SUP-MASTER SUPPLIER STREET-ADD CITY STATE ZIP CAPACITY: 211(12); NAME: ENTRY: INVENTORY ,D(12,14/13,18); STOCK# (PRODUCT ONHANDQTY SUPPLIER (!SUP-MASTER UNIT-COST LASTSHIPDATE ( DATE-MASTER BINNUM CAPACITY: 450(15); , , , , ; ), , ), , ), ; <---- path count to cha
DELETE SET After the deletion, the SETS part of the schema looks like this: SETS: NAME: ENTRY: CUSTOMER ,M(14/11,18); ACCOUNT (1) LAST-NAME FIRST-NAME INITIAL STREET CITY STATE ZIP CREDIT-RATING CAPACITY: 221(10); , , , , , , , , ; NAME: DATE-MASTER ,A(0,11,12,13,14,18/); ENTRY: DATE (2) ; CAPACITY: 211(9); NAME: ENTRY: PRODUCT ,M(13,14/12,18); STOCK# (1) DESCRIPTION CAPACITY: 307(16); NAME: ENTRY: SALES ,D(11/14,18); ACCOUNT ( CUSTOMER (PURCH-DATE STOCK# (!PRODUCT QUANTITY PRICE TAX TOTAL PURCH-DATE
DELETE SETSECURITY Deletes all security speci cations from a master or detail data set. DELETE SETSECURITY Syntax D[ELETE] SETSE[CURITY] DataSetName is the name of the data set whose security speci cations are to be removed. Parameters DataSetName Description Use this command to remove the security list from the data set. The absence of a security list (an absent list) allows any user read access to the data set.
Deletes a sort item from a search item in a detail data set. DELETE SORT D[ELETE] SO[RT] DataSetName SearchItemName Syntax Parameters DataSetName SearchItemName Description is the name of the data set containing the sort item to be deleted. is the name of the search item associated with the sort item to be deleted. Use this command to delete a sort item from a path in a detail data set.
ERASE SET Erases entries in manual master and detail data sets. ERASE SET Syntax Parameters 2 3 ER ASE SET DetailSetName ManualMasterSetName DetailSetName is the name of the detail data set which contains entries to be erased. For a standalone detail data set, all entries are erased.
ERASE SET more paths to detail data sets which contain entries (path counts are not zero). Description Use the ERASE SET command to erase entries in manual master and detail data sets. In session mode, a con rmation message is displayed to con rm the erasure of the data set entries. In batch mode, the data set is erased without con rmation. If you want to cancel the specifed erasure, use the CANCEL ERASE command before running the DBAPLUS program.
EXIT Stops the execution of the DBCPLUS program. EXIT Syntax Description E[XIT] Use this command to leave the DBCPLUS program. A series of statistics are displayed about the status of the change le. These statistics are accumulated for every BASE command that is issued while the DBCPLUS program is running. They are displayed when you exit the DBCPLUS program, even if the DBAPLUS program has already applied the changes to the database. Example >exit HP36386 (A.00.
Examines all sets and paths in the database and attempts to correct known problems. FIX BASE F[IX] BA[SE] Syntax Description Before using the FIX BASE command, read chapter 8, \Maintaining the Database." Note Use this command to examine all sets and paths in the database and to correct known problems. The FIX BASE command is equivalent to issuing the FIX SET @ and FIX PATH @ commands simultaneously. The database xing process begins only after you issue the PERFORM COMMANDS command.
FIX BASE CHECK SET (MASTER) Pct Pct Longest Average Master Set Name Type Entries Capacity Full Sec Cluster Cluster ----------------------------------------------------------------------CUSTOMER M 9 221 4 11.1 0 0.0 PRODUCT M 32 307 10 6.3 0 0.0 SUP-MASTER M 6 211 3 0.0 0 0.
FIX BASE CHECK INFORMATION Set Name Type Search Item Message(s) -----------------------------------------------------------------------CUSTOMER M Userlabel entry count does not match synonym chain count (CHK 570). Record 6 is not linked into the proper synonym chain (CHK 360). SALES D ACCOUNT (Path 1; linked to master CUSTOMER, path 1) Path Chain inconsistencies detected (CHK 400). Sum of chain counts in the related master set does not match bitmap entry count for this set (CHK 580).
FIX PATH Examines paths for broken chains and incorrect pointer linkages and attempts to correct known problems. FIX PATH Syntax 2 3 2 F IX PAT H Parameters 3 8 @ > > < MasterDataSetName > > : DetailDataSetName @ MasterDataSetName DetailDataSetName (@) (SearchItemName) 9 > > = > > ; indicates that all paths in all data sets in the database should be examined and corrected. is the name of the master data set whose synonym chains should be examined and corrected.
FIX PATH Example In the example below, the FIX PATH command is used to x all paths in all data sets in the ORDERS database. A description of the command output follows the example. >base orders >fix path @ FIX PATH issued for 5 set(s). >perform commands PERFORM COMMANDS now or create job file [job/y/N]? y Please wait ... HP36386 (A.00.00) DBALTER (c) COPYRIGHT Hewlett-Packard Co. 1985 FRI, MAY 25, 1990, 3:13 PM Database has been modified since last DBSTORE (DBA 220).
FIX PATH CHECK INFORMATION Set Name Type Search Item Message(s) -----------------------------------------------------------------------CUSTOMER M Userlabel entry count does not match synonym chain count (CHK 570). Record 6 is not linked into the proper synonym chain (CHK 360). SALES D ACCOUNT (Path 1; linked to master CUSTOMER, path 1) Path Chain inconsistencies detected (CHK 400). Sum of chain counts in the related master set does not match bitmap entry count for this set (CHK 580).
Examines data sets for internal pointer or structural inconsistency and attempts to correct known problems. FIX SET 2 Syntax Parameters 3 F IX SET @ DataSetName @ DataSetName indicates that all data sets in the database should be examined and corrected. is the name of the data set to be examined and corrected. Description Use this command to examine one or more data sets for internal pointer or structural inconsistency and to correct known problems.
FIX SET Example In the example below, all the data sets in the ORDERS database are xed using the FIX SET command. A description of the output follows the example. >base orders >fix set @ FIX SET issued for 5 set(s). >perform commands PERFORM COMMANDS now or create job file [job/y/N]? y Please wait ... HP36386 (A.00.00) DBALTER (c) COPYRIGHT Hewlett-Packard Co. 1985 TUE, MAY 29, 1990, 8:49 AM Database has been modified since last DBSTORE (DBA 220). Continue [y/N] ? y Starting data set serial reads. .....
FIX SET CHECK INFORMATION Set Name Type Search Item Message(s) -----------------------------------------------------------------------CUSTOMER M Userlabel entry count does not match synonym chain count (CHK 570). SALES D ACCOUNT (Path 1; linked to master CUSTOMER, path 1) Path Chain inconsistencies detected (CHK 400). Sum of chain counts in the related master set does not match bitmap entry count for this set (CHK 580).
HELP Provides information about DBChange commands. HELP Syntax Parameters H[ELP] [ CommandName] CommandName is the name of a command about which you want information. The abbreviated form of the command may be used. If this parameter is omitted, a brief description of all DBChange Plus commands is displayed. Description Use this command to display information about DBChange Plus commands. Example 1 >help recover RECOVER ITEM RECOVER SET Cancels a data item deletion in change file.
HELP Example 2 >help recover item RECOVER ITEM Cancels a data item deletion stored in the change file. Syntax REC[OVER] ITEM DataItemName Parameter DataItemName is the name of the data item to be recovered. Examples RECOVER ITEM zip REC ITEM state Related Commands ADD ITEM, DELETE ITEM, REVIEW ITEM. > In this example, information about the RECOVER command and the ITEM keyword is displayed.
OUTPUT Redirects DBChange and DBAPLUS output to a le or device. OUTPUT 2 Syntax Parameters O UTPUT LP TERM Description 3 LP TERM directs output to the formal le designator DBCOUT. directs output to $STDLIST. Use this command to direct DBChange and DBAPLUS output to a le or device. If this command is not used, the output is directed to $STDLIST (the terminal in session mode and the spool le in batch mode).
Invokes the DBAPLUS program to copy, restructure, check, or maintain the database depending on the commands stored in the current change le. PERFORM COMMANDS PE[RFORM] COM[MANDS] [JOB] [ ParmValue] Syntax Parameters JOB ParmValue creates a job le ( DatabaseName JJ) to enable running the DBAPLUS program at a later time. For batch mode, this parameter is required. In session mode, if you omit this option, DBChange asks you if changes should be performed online or if a job stream le should be created.
PERFORM COMMANDS Table 10-4. DBAPLUS Parameters PARM You do not have enough disk Value space to build all necessary temporary data sets before beginning the restructure. Do you want DBAPLUS to continue with the restructure using an alternative restructuring method? The database has been modi ed since the last DBSTORE. Do you wish to continue? Your root le is not in normal DBSCHEMA format.
PERFORM COMMANDS Example >base orders >fix base Fix Base (Fix Root, Fix Set and Fix Path) issued for 6 set(s). >perform commands PERFORM COMMANDS now or create job file [job/y/N]? y Please wait ... HP36386 (A.00.00) DBALTER (c) COPYRIGHT Hewlett-Packard Co. 1985 THU, JAN 18, 1990, 7:15 AM Database has been modified since last DBSTORE (DBA 220). Continue [y/N] ? y HP36386 (X.00.02) DBCHANGE (c) COPYRIGHT Hewlett-Packard Co. 1985 > In this example, the BASE command is issued for the ORDERS database.
PRINT SCHEMA PRINT SCHEMA Syntax Prints the schema of the database, applying any changes stored in the current change le. PR[INT] SC[HEMA] FileName is the name of an MPE XL disk le to which the schema is printed. Use this parameter interactively or in batch mode. The le must adhere to MPE XL le naming conventions. (Refer to the MPE XL General Users Reference Manual .) Parameters FileName Description Use this command to print the database schema.
PRINT SCHEMA >base orders new >output lp >print schema Example 4 In this example, the schema for the ORDERS database is directed to a printer. >base orders old >:file dbcout;dev=pp,2,3 >output lp >print schema Schema is printed. >output term Example 5 In this example, the schema for the ORDERS database is directed to printer PP. The priority is two, and three copies will be printed.
RECOVER ITEM RECOVER ITEM Syntax Cancels a DELETE ITEM command stored in the change le. REC[OVER] ITEM DataItemName is the name of the data item to be recovered. Parameters DataItemName Description Use this command to recover a data item, its type and security de nitions, and all elds represented by the data item. The recovery can only take place if DBAPLUS has not yet been run against the current change le. Once DBAPLUS restructures a database, data items can no longer be recovered.
Cancels a DELETE SET command stored in the change le. RECOVER SET REC[OVER] SET DataSetName Syntax is the name of the data set to be recovered. Parameters DataSetName Description Use this command to recover a data set. The recovery can only take place if DBAPLUS has not yet been run against the current change le. Once DBAPLUS restructures a database, data sets can no longer be recovered.
REDO Allows a user to correct or modify the last DBChange command entered. REDO R[EDO] Syntax Description Subcommands Use this command to display the last DBChange command entered. Use the associated subcommands to correct or change the displayed command. The REDO command applies only to the last command entered and is available only in interactive mode. A warning is issued if REDO is used in batch mode. D H I L R U X deletes the character above the cursor.
REDO Example >print shcema Invalid command (DBC 508). >redo print shcema rch print schema <---- Incorrect command is entered <---<---<---<---- Request to REDO command Command is displayed for corrections Error is deleted and replaced by correction Corrected command is displayed In this example, the PRINT SCHEMA command is corrected using the R subcommand.
RENAME BASE RENAME BASE Syntax Renames the database. REN[AME] BA[SE] NewDatabaseName is the new database name. A database name must be from 1 to 6 alphanumeric characters, the rst of which must be alphabetic. Parameters NewDatabaseName Description Use this command to rename the database named in the previous BASE command. Note that the database is physically renamed only after DBAPLUS is run. Example >base orders >rename base order2 In this example, the database ORDERS is renamed to ORDER2.
RENAME ITEM Renames a data item. REN[AME] ITEM OldItemName NewItemName Syntax Parameters OldItemName NewItemName Description is the name of the data item to be renamed. is the new name of the data item. Each data item within a database must have a unique name. This name must be from 1 to 16 characters, the rst of which must be alphabetic. Characters after the rst must be chosen from the following set: letters A - Z, digits 0 - 9, and + * / ? ' # % & @ inclusive. Data item names are upshifted.
RENAME ITEM After renaming the data item, the ITEMS and SETS parts of the schema look like this: ITEMS: ACCOUNT BINNUM , J2(0,11,12,13,14,18/); , Z2(/13); . . . SHIPDATE <---- item renamed , X6(12/); . . . CAPACITY: SHIPDATE BINNUM 450(15); ( DATE-MASTER ), <---; eld renamed END.
Renames a data set. RENAME SET REN[AME] SET OldSetName NewSetName Syntax Parameters OldSetName NewSetName Description is the name of the data set to be renamed. is the new name of the data set. Each data set within a database must have a unique name. This name must be from 1 to 16 characters, the rst of which must be alphabetic. Characters after the rst must be chosen from the following set: letters A - Z, digits 0 - 9, and + * / ? ' # % & @ inclusive. Data set names are upshifted.
REORDER FIELD REORDER FIELD Syntax Parameters Reorders the eld sequence in a manual master or detail data set. REO[RDER] F[IELD] DataSetName FieldName [ (NextField) ] DataSetName FieldName (NextField) Description Example is the name of the data set which contains the eld to be reordered. is the name of the eld to be reordered. It must be an existing eld in the data set. is the existing eld that follows the newly reordered eld in the eld list for the data set.
REORDER ITEM Reorders the sequence in which the data item resides in the database. REO[RDER] ITEM DataItemName [( NextDataItem)] Syntax Parameters DataItemName (NextDataItem) Description is the name of the data item to be reordered. is the data item that follows the newly reordered data item in the schema data item list. If this parameter is omitted, the reordered data item is placed last. Use this command to reorder the data item sequence in the data item part of the schema.
REORDER ITEM ZIP STORE# , X6(12,13,14/11); , J2(11,12/14); <---- item to be reordered After the reorder, the ITEMS part of the schema looks like this: ITEMS: ACCOUNT BINNUM CITY CREDIT-RATING DATE DELIV-DATE DESCRIPTION FIRST-NAME INITIAL LAST-NAME LASTSHIPDATE ONHANDQTY PRICE PURCH-DATE QUANTITY STATE STOCK# STORE# STREET-ADD SUPPLIER TAX TOTAL UNIT-COST ZIP , , , , , , , , , , , , , , , , , , , , , , , , J2(0,11,12,13,14,18/); Z2(/13); X12(12,13,14,/11); R2(/14); X6(0,11,12,13,14,18/); X6((/14); X20
REORDER SET Reorders the sequence in which the data set resides in the database. REO[RDER] SET DataSetName [( NextDataSet)] Syntax Parameters DataSetName (NextDataSet) is the name of the data set to be reordered. It must be an existing data set in the database. is the existing data set that follows the newly reordered data set in the schema data set list. If this parameter is omitted, the reordered data set is placed last.
REORDER SET NAME: DATE-MASTER ,A(0,11,12,13,14,18/) ENTRY: DATE (3) CAPACITY: 211(9) NAME: ENTRY: PRODUCT ,M(13,14/12,18) STOCK# (2) DESCRIPTION CAPACITY: 307(16) NAME: ENTRY: SALES ACCOUNT STOCK# QUANTITY PRICE TAX TOTAL PURCH-DATE DELIV-DATE CAPACITY: 504(14) ,D(11/14,18) ( CUSTOMER (PURCH-DATE) ) (!PRODUCT ) NAME: ENTRY: ,M(13/12,18); (1) SUP-MASTER SUPPLIER STREET-ADD CITY STATE ZIP CAPACITY: 211(12); NAME: ENTRY: ( DATE-MASTER ( DATE-MASTER INVENTORY ,D(12,14/13,18); STOCK# (PRODUCT ONHANDQTY
REORDER SET After the reorder, the SETS part of the schema looks like this: SETS: NAME: ENTRY: CUSTOMER ,M(14/11,18); ACCOUNT (1) LAST-NAME FIRST-NAME INITIAL STREET-ADD CITY STATE CREDIT-RATING CAPACITY: 221(10); , , , , , , , ; NAME: DATE-MASTER ,A(0,11,12,13,14,18/); ENTRY: DATE (2) CAPACITY: 211(19); ; NAME: ENTRY: PRODUCT ,M(13,14/12,18); STOCK# (1) DESCRIPTION CAPACITY: 307(16); NAME: ENTRY: SUP-MASTER SUPPLIER STREET-ADD CITY STATE ZIP CAPACITY: 211(12); ,M(13/12,18); NAME: ENTRY: ,D(11/14
REORDER SET NAME: ENTRY: INVENTORY ,D(12,14/13,18); STOCK# (PRODUCT ONHANDQTY SUPPLIER (!SUP-MASTER UNIT-COST LASTSHIPDATE ( DATE-MASTER BINNUM CAPACITY: 450(15); ), , ), , ), ; END.
Rebuilds a detail data set by removing gaps left by deleted entries and by adjusting pointers. REPACK SET 2 Syntax REP ACK SET DataSetName 2 Parameters 3 SetCapacity 32 DataSetName SERIAL CHAINED (SearchItemName) SetCapacity (BlockFactor) DeviceClass 10-126 DBChange Plus Commands (BlockFactor) SERIAL 2 CHAINED (SearchItemName) 3 32 3 DeviceClass is the name of the detail data set to be repacked.
REPACK SET Description Use this command to rebuild a detail data set. This command eliminates deleted entry gaps and adjusts pointers. To verify a pending REPACK SET command, use the REVIEW SETS command. If you want to cancel the data set repack, use the CANCEL REPACK command before running the DBAPLUS program. Refer to chapter 8, \Maintaining the Database," for more information about repacking data sets. Example 1 >base orders >repack set sales serial Repack Set issued for data set.
REPACK SET Example 2 >base orders >repack set inventory chained (lastshipdate) 100 (4) REPACK SET issued for data set. >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 WED, MAY 30, 1990, 10:00 AM Database has been modified since last DBSTORE (DBA 220). Continue [y/N] ? y PAGE 1 HEWLETT-PACKARD 30391C.02.
REPACK SET SETS: .. . NAME: INVENTORY ENTRY: STOCK# ONHANDQTY SUPPLIER UNIT-COST LASTSHIPDATE BINNUM CAPACITY: 100(4); ,D(12,14/13,18); ( PRODUCT ), , (!SUP-MASTER ), , ( DATE-MASTER ), ; <---- capacity and blocking factor changed END. .. .
REPACK SET > 10-130 DBChange Plus Commands
REPACK SET In this example, the BASE command is issued for the ORDERS database. The REPACK SET command is issued, specifying a chained repack for the detail data set INVENTORY on the search item LASTSHIPDATE. The capacity is changed to 100 and the blocking factor is changed to 4. After issuing a PERFORM COMMANDS to actually repack the data set, the schema is printed along with messages about the status of the repack. In this case, ve entries were successfully repacked.
REVIEW BLOCKS Displays information about the blocking factor of one or more data sets. 2 Syntax Parameters DataSetName @ Description 3 2 REV IEW BLOCK S 3 DataSetName @ is the name of the data set to be reviewed. indicates you want to review the blocking factor of all data sets in the database. This parameter is the default. Use this command to review the following information about one or more data sets: Data Set is the name of the master or detail data set being Name reviewed.
REVIEW BLOCKS Example >review blocks @ REVIEW BLOCKS: Fld Pth Entr Med Blk Blk Blk Data Set Name Type Cnt Cnt Len Rec Capacity Fac Len Max ----------------------------------------------------------------CUSTOMER DATE-MASTER PRODUCT SALES SUP-MASTER INVENTORY M A M D M D 9 1 2 8 5 6 1 3 2 4 1 3 43 3 14 21 31 20 54 26 31 37 42 32 221 211 307 504 211 450 10 19 16 14 12 15 541 496 498 519 505 481 640 496 498 640 505 481 > In this example, all the data sets in the ORDERS database are reviewed using t
REVIEW FIELDS Displays information about the elds (data items) in a master and detail data set. REV[IEW] F[IELDS] DataSetName Syntax is the name of a data set that contains elds to be reviewed. Parameters DataSetName Description Use this command to review elds (data items) in a data set. For a master data set, the following information is displayed: Data Set No. is the sequence in which the data set appears in the SETS part of the schema. Name is the data set name. Type is the type of data set.
REVIEW FIELDS Example >review fields product REVIEW FIELDS (MASTER SET): Data Set No.: 3 Name: PRODUCT Type: M Fld No. Field Name Detail Set Name Path's Search Item --------------------------------------------------------------1 STOCK# 2 3 DESCRIPTION DISC-PRICE SALES INVENTORY STOCK# STOCK# > In this example, the elds in the master data set PRODUCT are reviewed. The data set PRODUCT contains three elds, STOCK#, DESCRIPTION, and DISC{PRICE.
REVIEW ITEMS Displays information about the data items in the database. 2 Syntax Parameters 3 2 REV IEW ITEM S @ DataItemName indicates you want to review all data items. This parameter is the default. is the name of a data item to be reviewed. @ DataItemName Description 3 Use this command to review data items in the database. The following information is displayed: Itm No. is the sequence in which the data item resides in the database.
REVIEW PASSWORDS Displays information about user classes and associated passwords in the database. REVIEW PASSWORDS 2 Syntax Parameters 3 2 REV IEW PAS SWORDS Example UserClass @ is the name of the user class whose security you want to review. indicates you want to review all user classes and their associated passwords. This parameter is the default. UserClass @ Description 3 Use this command in interactive mode to review user classes and passwords in the database.
REVIEW PATHS Displays information about the paths in a data set. REV[IEW] PAT[HS] DataSetName Syntax is the name of the master or detail data set whose paths you want to review. Parameters DataSetName Description Use this command in interactive and batch mode to review the paths in a data set. For detail data sets, the following information is displayed: Data Set No. is the sequence in which the data set appears in the SETS part of the schema. Name is the name of the detail data set being reviewed.
REVIEW PATHS All changes stored in the the current change le are included in the REVIEW PATHS output. The REVIEW PATHS command also displays status messages if a CHECK PATH or FIX PATH command is pending.
REVIEW PATHS Example 1 >review paths inventory REVIEW PATHS (DETAIL SET): Data Set No.: 6 Name: INVENTORY Type: D Search Item Name Master Set Name Sort Item Name Primary ---------------------------------------------------------------STOCK# SUPPLIER LASTSHIPDATE PRODUCT SUP-MASTER DATE-MASTER Y > In this example, the paths for the detail data set INVENTORY are reviewed. The data set number is 6. The search item SUPPLIER represents the primary path. No sort items are identi ed for any of the paths.
REVIEW SETS Displays information about the data sets in the database. REVIEW SETS 2 Syntax Parameters 3 @ DataSetName Description 2 REV IEW SET S 3 @ DataSetName indicates you want to review all data sets. This parameter is the default. is the name of a data set to be reviewed. Use this command to review data sets in the database. For each data set, the following information is displayed: Set No. is the sequence in which the data set appears in the SETS part of the schema.
REVIEW SETS Example >review sets inventory REVIEW SETS: Set Blk Blk Dev No. Data Set Name Type Capacity Fac Max Class Security -------------------------------------------------------------6 INVENTORY D 450 15 481 DISK1 (12,14/18) > In this example, the detail data set INVENTORY is reviewed. It is data set number 6 on device class identi ed as DISK1 with a capacity of 450 and a blocking factor of 15. The maximum block size is 481.
XEQ Executes DBChange commands from a le instead of the terminal or batch les. XEQ Syntax X[EQ] FileName is the name of an ASCII le containing commands and parameters. Parameters FileName Description Use this command to execute DBChange commands from a le instead of the standard input device. All commands that are accepted by DBChange Plus are allowed in an XEQ le. To create an XEQ le, use a text editor.
XEQ Example >xeq xeqfile ><> ><< and stores the addition of the data item REGION in the change file >> > >base orders <---- DBChange command >delete item date <---- DBChange command Deleting this data item will cause loss of data, delete [y/N]? y Deletion of data item accepted. >add item region j 2 (11,12/14) <---- DBChange command Addition of data item accepted. > > XEQ file is at end-of-file.
A DBChange Plus Messages This appendix lists the DBChange Plus error and information messages. In the case of error messages, the cause of the error and user action to resolve the error are supplied for each message. Note All messages are arranged in numerical order. Duplicate message numbers exist. In those cases, refer to the code in parentheses following the message to determine the correct message. For example, (DBC 500) is a DBCPLUS message, and (DBA 500) is a DBAPLUS message.
6 MESSAGE Cannot read the change file (FSERR n ) (DBC 6). MEANING The MPE intrinsic FREADDIR failed while reading the change le. Refer to the MPE Intrinsics Reference Manual , where FSERR n is the le system error number returned from the FCHECK intrinsic.
7 MESSAGE Cannot write to the change file (FSERR n ) (DBC 7). MEANING The MPE intrinsic FWRITEDIR failed while writing to the change le. Refer to the MPE Intrinsics Reference Manual , where FSERR n is the le system error number returned from the FCHECK intrinsic. ACTION |||||||||||||||||||||||||||||| |||||||||8 MESSAGE Cannot open the change file (FSERR n ) (DBC 8). MEANING The MPE intrinsic FOPEN failed while opening the change le.
11 MESSAGE Cannot close the root file (FSERR n ) (DBC 11). MEANING The MPE intrinsic FCLOSE failed while closing the database root le. Refer to the MPE Intrinsics Reference Manual , where FSERR n is the le system error number returned from the FCHECK intrinsic. ACTION |||||||||||||||||||||||||||||| |||||||||12 MESSAGE Cannot read the root file (FSERR n ) (DBC 12). MEANING ACTION The MPE intrinsic FREAD or FREADDIR failed while reading the database root le.
14 MESSAGE Cannot close the database (IMAGERR n ) (FSERR n ) (DBC 14). MEANING The TurboIMAGE/XL intrinsic DBCLOSE failed while closing the database. Refer to the TurboIMAGE/XL DBMS Reference Manual , where IMAGERR n is the error number returned in the status array. Refer to the MPE Intrinsics Reference Manual , where FSERR n is the le system error number returned from the FCHECK intrinsic. An asterisk (*) means no le system error occurred.
17 MESSAGE The change file is full (DBC 17). MEANING The DBCPLUS program failed to nd any empty records in the change le for the new change. Run the DBAPLUS program to restructure the database with the current changes. Then run the DBCPLUS program to create a new change le for the remaining changes. ACTION Caution Review the changes in the change le before running the DBAPLUS program. Make sure that the changes will leave the database in a consistent state.
21 MESSAGE Invalid control record in change file (DBC 21). MEANING The database name, or the group and account stored in an existing change le does not match the logon group and account or the database name. Verify that you have logged on correctly and entered the correct database name. ACTION |||||||||||||||||||||||||||||| |||||||||22 MESSAGE Internal item information is inconsistent (DBC 22). MEANING The change le contains an inconsistent or invalid item name or number.
26 MESSAGE Insufficient stack space available to initialize change file (DBC 26). MEANING The stack could not be expanded enough to hold the root le information. Set and item information must be read from the root le to initialize tables stored in the change le. Notify the system manager. ACTION |||||||||||||||||||||||||||||| |||||||||27 MESSAGE Cannot initiate DBAPLUS (create failed) (DBC 27). MEANING The MPE intrinsic CREATE failed. Notify the system manager.
52 MESSAGE This is not a TurboIMAGE database (DBC 52). MEANING The database is an IMAGE/3000 database. DBChange Plus can only be used on TurboIMAGE/XL databases. Use DBCONV.PUB.SYS to convert the IMAGE/3000 database to a TurboIMAGE/XL database. Run DBChange Plus again. ACTION |||||||||||||||||||||||||||||| |||||||||56 MESSAGE The master data set is not in the database (DBC 56). MEANING The master data set has not been de ned for this database. Enter the name of an existing master data set.
59 MESSAGE Enter new database name if copying to logon group and account (DBC 59). MEANING When making a copy of the database that will reside in the logon group and account, you must specify a di erent name for the database copy. Specify a new name for the database copy. ACTION |||||||||||||||||||||||||||||| |||||||||61 MESSAGE Job stream file FileName cannot be opened (FSERR n ) (DBC 61). MEANING Could not open the job stream le FileName that would run the DBAPLUS program in batch mode.
64 MESSAGE The user class does not exist (DBC 64). MEANING The speci ed user class does not exist. Specify an existing user class. ACTION |||||||||||||||||||||||||||||| |||||||||65 MESSAGE Database copy must be done independently of any other changes (DBC 65). MEANING When copying a database, you cannot specify any other DBChange Plus function, except HELP or EXIT.
68 MESSAGE No more data sets can be added; max. of 199 has been reached (DBC 68). MEANING The TurboIMAGE/XL limit of 199 data sets per database has been reached. To add this data set, you must rst delete a data set from the database. ACTION |||||||||||||||||||||||||||||| |||||||||69 MESSAGE Search item must be a non-compound item (DBC 69). MEANING The subitem count of a search item cannot be changed because a search item cannot be a compound data item. A search item must have a subitem count of 1.
72 MESSAGE No more fields can be added; max. of 255 has been reached (DBC 72). MEANING The TurboIMAGE/XL limit of 255 items ( elds) per data set has been reached. To add this eld, you must rst delete a eld from the data set. ACTION |||||||||||||||||||||||||||||| |||||||||73 MESSAGE Only one primary path can be defined (DBC 73). MEANING More than one primary path for this data set was speci ed. Specify only one primary path.
76 MESSAGE Run DBAPLUS from group.account where database will reside (DBC 76). MEANING When copying a database, you must logon to the group and account where the copy will reside and run the DBAPLUS program from that group and account. Logon to the group and account where the copy will reside and run the DBAPLUS program. ACTION |||||||||||||||||||||||||||||| |||||||||77 MESSAGE This field already exists in this data set (DBC 77). MEANING The item to be added already exists in this data set.
81 MESSAGE Job stream file FileName cannot be created (FSERR n ) (DBC 81). MEANING Could not create the job stream le FileName that runs the DBAPLUS program in batch mode. Refer to the MPE Intrinsics Reference Manual , where FSERR n is the le system error number returned from FCHECK intrinsic. ACTION |||||||||||||||||||||||||||||| |||||||||82 MESSAGE This is not a data item in the database (DBC 82). MEANING The speci ed data item does not exist in the database or change le.
86 MESSAGE The device class is not configured on the system (DBC 86). MEANING The device class entered for the data set is not con gured on the system. Enter the name of a con gured device class that is valid for a disk le. ACTION |||||||||||||||||||||||||||||| |||||||||87 MESSAGE Duplicate data set name (DBC 87). MEANING A data set cannot be renamed with the name of an existing data set. Specify a new data set name. To review existing data sets, use the REVIEW SETS command.
91 MESSAGE This is a deleted data item (DBC 91). MEANING The speci ed data item has been previously deleted. Specify the name of an existing data item. ACTION |||||||||||||||||||||||||||||| |||||||||92 MESSAGE This is a deleted data set (DBC 92). MEANING The speci ed data set has been previously deleted. Specify the name of an existing data set. ACTION |||||||||||||||||||||||||||||| |||||||||93 MESSAGE Write to job stream file FileName failed (FSERR n ) (DBC 93).
95 MESSAGE Master data set cannot be moved after its related details (DBC 95). MEANING When reordering data sets, a master data set must be moved before any of its associated detail data sets. Reorder the master data set so that it is de ned before all of its associated detail data sets. ACTION |||||||||||||||||||||||||||||| |||||||||96 MESSAGE New capacity cannot be less than number of existing entries (DBC 96).
99 MESSAGE Detail data set cannot be moved before its related masters (DBC 99). MEANING When reordering data sets, a detail data set must be moved after any of its associated master data sets. Reorder the detail data set so that it is de ned after all of its associated master data sets. ACTION |||||||||||||||||||||||||||||| |||||||||100 MESSAGE The search item must be a field in this data set (DBC 100). MEANING The speci ed search item is not a eld in this detail data set.
103 MESSAGE Detail search item (length) does not match master key (DBC 103). MEANING A search item speci ed in the detail data set has a di erent length than the key item in the related master data set. Specify the same length for the search and key items that de ne the path from the detail data set to the master data set. ACTION |||||||||||||||||||||||||||||| |||||||||104 MESSAGE This is not a search item in the data set (DBC 104).
109 MESSAGE Sub-item length for item type K must be 1 or 2 (DBC 109). MEANING The speci ed length is invalid for item type K. Specify a subitem length of 1 or 2. ACTION |||||||||||||||||||||||||||||| |||||||||110 MESSAGE Product of sub-item count and length must be even (DBC 110). MEANING When adding or changing a data item of type U or X, the product of the subitem count and length must be an even number. Specify a subitem count and length for which the product is even.
114 MESSAGE The master set has to be defined before the detail (DBC 114). MEANING A detail data set was added with paths to a master data set that is de ned later in the schema. Place the new detail data set after all associated master data sets in the schema. ACTION |||||||||||||||||||||||||||||| |||||||||115 MESSAGE No more sets to display (DBC 115). MEANING You have reached the beginning or end of the data set list. No action necessary.
122 MESSAGE Only `R', `W', `N', or blank is valid (DBC 122). MEANING A character other than R, W, N, or blank was speci ed. Enter R for read access, W for read and write access, N for no access, or leave blank. ACTION |||||||||||||||||||||||||||||| |||||||||123 MESSAGE Cannot open the schema file (FSERR n ) (DBC 123). MEANING The MPE intrinsic FOPEN failed while opening the schema le.
125 MESSAGE Duplicate password (DBC 125). MEANING The speci ed password already exists for this database. Specify a new and unique password. ACTION |||||||||||||||||||||||||||||| |||||||||126 MESSAGE Change file version n not match DBChange version n (DBC 126). MEANING The change le was either created with an old version of DBChange or with a newer version than is currently executing. The change le may have been created by either DBChange/V or DBChange/CM, not by DBChange Plus.
129 MESSAGE The new name is the same as the old name (DBC 129). MEANING The name of the database has not been changed. Enter a di erent name when renaming the database. ACTION |||||||||||||||||||||||||||||| |||||||||130 MESSAGE This file already exists, please specify a new name (DBC 130). MEANING A le already exists with the same database name speci ed for the database copy or rename. Enter a di erent name.
133 MESSAGE Sort item is the same as the search item (DBC 133). MEANING The sort item speci ed is the same data item as the search item that de nes the path. Enter a sort item that is di erent from the search item. ACTION |||||||||||||||||||||||||||||| |||||||||134 MESSAGE Capacity/block factor should not exceed 8388607 (DBC 134). MEANING The maximum size of the data set was exceeded. This is a TurboIMAGE/XL limitation. Reduce the capacity or increase the blocking factor.
201 MESSAGE Block factor must be between 0 and 255 (DBC 201). MEANING The blocking factor of the data set was not between 0 and 255 inclusive. If the blocking factor is zero, DBSCHEMA calculates the most optimal blocking factor for the set and then reblocks it. Enter a blocking factor within these limits. ACTION |||||||||||||||||||||||||||||| |||||||||202 MESSAGE Invalid device class name (DBC 202).
205 MESSAGE Sub-item length must be between 1 and 255 (DBC 205). MEANING The subitem length was not between 1 and 255, inclusive. Enter a subitem length within these limits. ACTION |||||||||||||||||||||||||||||| |||||||||206 MESSAGE Set type must be A, M, or D (DBC 206). MEANING A data set type was entered that was not A for automatic master data set, M for manual master data set, or D for detail data set. Enter a valid data set type.
226 MESSAGE Fatal error checking root file (Internal Error n ) (DBA 226). MEANING Damage has occurred to the root le which prohibits le checks from completing. Restore a backup copy of the root le making sure it matches the structure of the current database and recheck the root le. ACTION |||||||||||||||||||||||||||||| |||||||||230 MESSAGE Invalid change file structure (DBA 230). MEANING The change le contains inconsistent data item and data set information.
250 MESSAGE Cannot close database DatabaseName (IMAGERR n ) (DBA 250). MEANING The TurboIMAGE/XL intrinsic DBCLOSE failed while trying to close the database DatabaseName . Refer to the TurboIMAGE/XL DBMS Reference Manual , where IMAGERR n is the error number returned in the status array. If the error was caused by a le system error, message 410 is printed instead. ACTION |||||||||||||||||||||||||||||| |||||||||252 MESSAGE Cannot close the check file FileName (FSERR n ) (DBA 252).
260 MESSAGE Cannot close the root file (DBA 260). MEANING The MPE intrinsic FCLOSE failed while closing the root le. Refer to the MPE Intrinsics Reference Manual where n is the le system error number returned from the FCHECK intrinsic. ACTION |||||||||||||||||||||||||||||| |||||||||270 MESSAGE Cannot close the data set DataSetName (DBA 270). MEANING An error occurred while closing the data set DataSetName . The MPE intrinsic FCLOSE failed. In addition to 270, message 410 is also displayed.
310 MESSAGE Cannot create the new root file (DBA 310). MEANING The new database schema contains errors that caused DBSCHEMA to fail. Check the new schema for errors. Run the DBCPLUS program again with the same change le and correct the errors. ACTION |||||||||||||||||||||||||||||| |||||||||320 MESSAGE Cannot create the data set DataSetName (DBA 320). MEANING One of the following MPE intrinsics failed while creating the data set DataSetName : FOPEN, FCLOSE, FWRITE, FWRITEDIR, FWRITELABEL.
340 MESSAGE Database has been corrupted (DBA 340). MEANING The database is in an inconsistent state due to a fatal error encountered during the restructuring process. Restore a backup copy of the database from the DBSTORE tape, and try the changes again. If the error occurs again, notify the system manager. ACTION |||||||||||||||||||||||||||||| |||||||||345 MESSAGE Set DataSetName using block factor n exceeds blockmax m (DBA 345).
365 MESSAGE CHECK/FIX event file damaged at record n (DBA 365). MEANING The le DatabaseName RX does not meet DBChange Plus internal veri cation requirements. Store the database and contact your HP representative. ACTION |||||||||||||||||||||||||||||| |||||||||366 MESSAGE CHECK/FIX event file misordered at record n (DBA 366). MEANING The le DatabaseName RX does not meet DBChange Plus internal veri cation requirements. Store the database and contact your HP representative.
DBChange Plus Messages (continued) |||||||||||||||||||||||||||||| |||||||||370 MESSAGE Root condition is value (DBA 370). MEANING Each value of the condition word is listed below with a meaning and action for each. ME MEANING ACTION DBUTIL was interrupted while creating the database. Purge the database and re-create it. MC MEANING ACTION DBUTIL was interrupted while erasing the database. Purge the database and restore a backup copy.
ID MEANING ACTION DBUTIL was interrupted while the database was being disabled for Intrinsic Level Recovery (ILR). Run DBUTIL to nish disabling the database for ILR. CN MEANING ACTION The database is being converted from an IMAGE database to a TurboIMAGE/XL database. The database conversion process cannot be continued . Purge the database and restore a backup copy. Run DBCONV again. CA MEANING ACTION The database is being converted from an IMAGE database to a TurboIMAGE/XL database.
380 MESSAGE DBCHGF file equate can only contain actual file designator (DBA 380). MEANING The le equation for DBCHGF contains options which are not allowed. Only the actual le name can be speci ed. Reenter the le equation and run the DBAPLUS program again. ACTION |||||||||||||||||||||||||||||| |||||||||390 MESSAGE FFILEINFO failed on data set DataSetName (DBA 390). MEANING The MPE intrinsic FFILEINFO failed when issued against the data set DataSetName .
413 MESSAGE Damage requires manual intervention (DBA 413). MEANING Database damage exists that cannot be repaired by DBChange Plus. In addition to 413, one of the following messages is also displayed: Capacity and blocking factor recorded in root file are inconsistent. Data set media length recorded in the root file is inconsistent. Root file inconsistency detected by DBChange (CHK 220).
416 MESSAGE Cannot return n bytes of heap space (DBA 416). MEANING An internal error occurred while deallocating memory. Copy the terminal screen and notify the system manager. ACTION |||||||||||||||||||||||||||||| |||||||||420 MESSAGE TurboIMAGE error n (DBA 420). MEANING The TurboIMAGE/XL intrinsic DBCONTROL or DBPUT failed. ACTION Refer to the TurboIMAGE/XL DBMS Reference Manual , where n is the error number returned in the status array.
450 MESSAGE Data item ItemNumber does not exist in the change file (DBA 450). MEANING The change le contains inconsistent data item information. The data item number ItemNumber was not found in the change le. Run the DBCPLUS program again, and create a new change le. If the database is corrupt, purge it and restore a backup copy. ACTION |||||||||||||||||||||||||||||| |||||||||460 MESSAGE Cannot get extra data segment needed for copy/restructure (DBA 460).
499 MESSAGE Native Language Support subsystem error n (DBA 499). MEANING Native Language Support is not functioning. Notify the system manager. ACTION |||||||||||||||||||||||||||||| |||||||||500 MESSAGE Cannot create schema file FileName (DBA 500). MEANING ACTION The MPE intrinsic FOPEN or FCLOSE failed while opening or closing the schema le. In addition to 500, message 410 is also displayed.
501 MESSAGE Detail set DataSetName still has n entries (DBA 501). MEANING The ERASE SET command was issued for a manual master data set that has one or more paths linked to detail data sets. Related detail data set entries still exist. Manual master data set entries cannot be erased until all related detail data set entries are erased. Issue the ERASE SET command for each related detail data set before issuing the ERASE SET command for the manual master data set.
502 MESSAGE Cannot erase manual set DataSetName due to detail entries (DBA 502). MEANING The ERASE SET command was issued for a manual master data set that has one or more paths linked to detail data sets. Related detail data set entries still exist. Manual master data set entries cannot be erased until all related detail data set entries are erased. Issue the ERASE SET command for each related detail data set before issuing the ERASE SET command for the manual master data set.
503 MESSAGE LP or TERM must be used for OUTPUT command (DBC 503). MEANING A parameter other than LP or TERM was speci ed for the OUTPUT command. Enter either OUTPUT LP or OUTPUT TERM. ACTION |||||||||||||||||||||||||||||| |||||||||504 MESSAGE Path search item is invalid, cannot REPACK SET DataSetName (DBA 504). MEANING An incorrect search item name was speci ed in the REPACK SET command. The path may have been deleted after the REPACK SET command was used. Specify the correct path to be repacked.
505 MESSAGE Command exceeds 3 lines or 216 characters (DBC 505). MEANING Too many lines or characters were used when entering a command. Reenter the command using fewer than 3 lines or 216 characters. ACTION |||||||||||||||||||||||||||||| |||||||||506 MESSAGE Cannot HPFOPEN internal map file for set DataSetName (HPFERR n ) (DBA 506). MEANING The MPE intrinsic HPFOPEN failed while opening an internal le.
508 MESSAGE Invalid command (DBC 508). MEANING An incorrect command was entered. Enter a valid command or use the correct command abbreviation. Use HELP to nd the correct command. ACTION |||||||||||||||||||||||||||||| |||||||||509 MESSAGE Command valid only in session mode (DBC 509). MEANING A command that is valid only during a session (interactive) mode was entered in a job stream le. Delete this command from the job stream le.
511 MESSAGE Correct BASE command is required before continuing (DBC 511). MEANING The BASE command was not entered before processing the database. The only commands that can be issued before the BASE command are HELP, OUTPUT, REDO, and XEQ. The BASE command is required after issuing the PERFORM COMMANDS command. Enter the appropriate BASE command. ACTION |||||||||||||||||||||||||||||| |||||||||512 MESSAGE Fatal error occurred. DBChange cannot continue (DBC 512).
514 MESSAGE Old change file cannot be renamed to be saved (FSERR n ) (DBC 514). MEANING The MPE intrinsic FCLOSE failed while trying to save the old change le with a name other than FileName CO or FileName CF. Refer to the MPE Intrinsics Reference Manual , where FSERR n is the le system error number returned from the FCHECK intrinsic. Verify that there is su cient disk space to save the change le and that no other CO or CF change le exists. Rerun the DBCPLUS program.
517 MESSAGE Cannot PERFORM COMMANDS due to errors (DBC 517). MEANING Errors were detected in the DBCPLUS run for the database. The PERFORM COMMANDS command cannot be executed. Correct the errors, then run the PERFORM COMMANDS command. ACTION |||||||||||||||||||||||||||||| |||||||||518 MESSAGE Use CHANGE PRIMARYPATH or DELETE PATH then ADD PATH (DBC 518). MEANING CHANGE PATH command was entered. No CHANGE PATH command exists. Use other suggested commands.
521 MESSAGE No recover command for field, password, path or sort (DBC 521). MEANING No RECOVER command exists for the command keywords FIELD, PASSWORD, PATH, and SORT. Use the ADD command to re-add elds, passwords, paths, or sort items after they have been deleted. ACTION |||||||||||||||||||||||||||||| |||||||||522 MESSAGE Invalid XEQ file name (DBC 522). MEANING An incorrect XEQ le name was entered. Enter the correct XEQ le name.
525 MESSAGE File system error n opening file FileName (DBA 525). MEANING The MPE intrinsic FOPEN failed while opening the le FileName . Refer to the MPE Intrinsics Reference Manual , where n is the le system error number returned from the FCHECK intrinsic. ACTION |||||||||||||||||||||||||||||| |||||||||525 MESSAGE Another XEQ file is already opened. Nested XEQ file not allowed (DBC 525). MEANING A second XEQ command was issued. Only one XEQ le can be processed at a time.
530 MESSAGE Cannot open the root file (DBA 530). MEANING The MPE intrinsic FOPEN failed while opening the root le. In addition of 530, message 410 is also displayed. Refer to the MPE Intrinsics Reference Manual , where n is the le system error number returned from the FCHECK intrinsic. ACTION |||||||||||||||||||||||||||||| |||||||||530 MESSAGE Blockmax must be between 128 and 2048 (DBC 530). MEANING The maximum block size entered is not between 128 and 2048.
533 MESSAGE For set DataSetName the block size n exceeds 2560 words (DBC 533). MEANING The blocking factor for the data set DataSetName is too large causing the block size to exceed 2560 words. Decrease the block factor for the data set. ACTION |||||||||||||||||||||||||||||| |||||||||534 MESSAGE For set DataSetName entry length n exceeds 2047 words. (DBC 534).
536 MESSAGE Set name is required for this command (DBC 536). MEANING The data set name is required but was not entered. Use HELP to check the command syntax, and enter the data set name. ACTION |||||||||||||||||||||||||||||| |||||||||537 MESSAGE A value must be entered for a required parameter (DBC 537). MEANING A required value is missing from the command. Use HELP to check the command syntax, and enter the correct command.
540 MESSAGE Cannot open the data set DataSetName (DBA 540). MEANING The MPE intrinsic FOPEN failed to open the data set. In addition to 540, message 410 is also displayed. Refer to the MPE Intrinsics Reference Manual , where n is the le system error number returned from the FCHECK intrinsic. ACTION |||||||||||||||||||||||||||||| |||||||||540 MESSAGE DBCOUT file equate error in HPFEQINFO (HPQERR n ) (DBC 540).
544 MESSAGE Cannot open data set file FileName (FSERR n ) (DBC544). MEANING The MPE intrinsic FOPEN failed while opening the data set le FileName . Refer to the MPE Intrinsics Reference Manual , where FSERRn is the le system error number returned from the FCHECK intrinsic. ACTION |||||||||||||||||||||||||||||| |||||||||545 MESSAGE File system error 46: out of disc space (DBA 545).
547 MESSAGE No fields defined for data set DataSetName (DBC 547). MEANING A data set was added without any elds added, or all elds in the data set were deleted. Add at least one eld to the data set or delete the data set. ACTION |||||||||||||||||||||||||||||| |||||||||548 MESSAGE No paths defined for auto master set DataSetName (DBC 548). MEANING An automatic master data set was added without any paths de ned. Add at least one path for the automatic master data set, or delete the data set.
550 MESSAGE Set DataSetName entry length n less than 2 words (DBC 550). MEANING The detail data set DataSetName has no paths and an entry length less than two words (MPE/V words or MPE/XL halfwords), which is not allowed by DBSCHEMA. Add more elds to the data set, or increase the item length of the existing elds. ACTION |||||||||||||||||||||||||||||| |||||||||551 MESSAGE Cannot CHECK/FIX this new set until added by DBAlter (DBC 551).
553 MESSAGE Cannot erase automatic master data set (DBC 553). MEANING The ERASE SET command was issued for an automatic master data set. The data in an automatic master data set cannot be explicitly erased. An automatic master data set entry is erased once the detail data set entries are erased. Use the ERASE SET command to erase the related detail data sets linked to the automatic master data set.
555 MESSAGE Cannot erase manual set with existing related detail entries (DBC 555). MEANING The ERASE SET command was issued for a manual master data set that has one or more paths linked to detail data sets where related detail data entries still exist. Issue ERASE SET for each of the detail data set entries with paths linked to the manual master data set, then issue ERASE SET for the manual master data set.
557 MESSAGE ERASE SET has already been issued for the data set (DBC 557). MEANING ERASE SET was issued a second time for the same data set. Erase the data set entries and reissue the ERASE SET command. ACTION |||||||||||||||||||||||||||||| |||||||||558 MESSAGE Data set has not been set to erase. Cannot CANCEL ERASE (DBC 558). MEANING CANCEL ERASE was issued for a data set that was not agged to be erased by ERASE SET. No action necessary if you do not intend to erase the data set entries.
560 MESSAGE Data set has not been set to repack. Cannot CANCEL REPACK (DBC 560). MEANING CANCEL REPACK was issued for a data set without issuing a previous REPACK SET command. No action necessary if you do not want to repack the data set. ACTION |||||||||||||||||||||||||||||| |||||||||561 MESSAGE CTL_REPACK_SETS less than zero. Cannot CANCEL REPACK (DBC 561). MEANING CANCEL REPACK was issued for a data set.
564 MESSAGE REPACK SET has already been issued for the data set (DBC 564). MEANING REPACK SET was issued a second time for the same data set. If the repack option is to be changed for the data set, use CANCEL REPACK then REPACK SET with the correct repack option. Otherwise, no action is necessary. ACTION |||||||||||||||||||||||||||||| |||||||||565 MESSAGE REPACK SET option must be serial or chained (DBC 565).
567 MESSAGE Path search item is invalid, cannot REPACK SET DataSetName (DBC 567). MEANING The path speci ed by the search item used in the REPACK SET command does not exist. The path may have been deleted after the REPACK SET command was used. Verify that the path still exists by using the REVIEW PATHS command. If not, use the CANCEL REPACK and REPACK SET commands for another path.
570 MESSAGE Cannot read the root file label (DBA 570). MEANING The MPE intrinsic FREADLABEL failed while trying to read the le label of the root le. In addition to 570, message 410 is also displayed. Refer to the MPE Intrinsics Reference Manual , where n is the le system error number returned from the FCHECK intrinsic. ACTION |||||||||||||||||||||||||||||| |||||||||570 MESSAGE Cannot close the schema file (FSERR n ) (DBC 570). MEANING The MPE intrinsic FCLOSE failed while closing the schema le.
573 MESSAGE AM capability or CREATOR access required to copy within account (DBC 573). MEANING You do not have the required MPE capabilities to copy a database within an account. Acquire AM capability or CREATOR access. ACTION |||||||||||||||||||||||||||||| |||||||||574 MESSAGE SF (save file) capability required to copy a database (DBC 574). MEANING You do not have the required MPE capability to copy a database. Acquire SF capability.
577 MESSAGE Data set DataSetName has capacity less than one (DBC 577). MEANING The capacity for the data set DataSetName in the current database is less than one. CONTROL PERCENTFULL cannot be calculated for the set. Change the capacity using the CHANGE CAPACITY command. ACTION |||||||||||||||||||||||||||||| |||||||||578 MESSAGE Cannot calculate PERCENTFULL for a new data set (DBC 578). MEANING The data set speci ed in the CONTROL PERCENTFULL command is not yet added to the database.
580 MESSAGE Cannot read the data set DataSetName (DBA 580). MEANING The MPE intrinsic FREADDIR failed while reading the data set DataSetName . In addition to 580, message 410 is also displayed. Refer to the MPE Intrinsics Reference Manual , where n is the le system error number returned from the FCHECK intrinsic. ACTION |||||||||||||||||||||||||||||| |||||||||580 MESSAGE NewBaseName already exists and REPLACE not requested (DBC 580).
601 MESSAGE Invalid characters after delete (D) command (DBC 601). MEANING An invalid character or too many characters were entered when using the REDO command with the delete option. Only D or I (for insert) is allowed after the rst D in the REDO command. Redo the command line. ACTION |||||||||||||||||||||||||||||| |||||||||602 MESSAGE More than 80 characters on the line (DBC 602). MEANING Too many characters were inserted when using the REDO command.
615 MESSAGE Cannot reset condition word or root file label (DBA 615). MEANING The condition word in the root le label could not be reset to a value that would allow subsequent access to the database. Run DBUTIL and purge the database. Restore a backup copy. ACTION |||||||||||||||||||||||||||||| |||||||||620 MESSAGE Cannot restructure database while recovery in progress (DBA 620). MEANING Database recovery has not been completed.
645 MESSAGE Database contains errors and no "FIX" requested (DBA 645). MEANING The database contains errors. The DBCPLUS JCW is set to 210 so that a batch job can detect the damaged database. Use the FIX command to correct errors. ACTION |||||||||||||||||||||||||||||| |||||||||650 MESSAGE Security violation (DBA 650). MEANING Either the logon user, group, or account do not match what is in the change le or you do not have MPE access to the change le.
670 MESSAGE Data set DataSetNum does not exist in the change file (DBA 670). MEANING The change le contains inconsistent data set information. The data set number DataSetNum was not found in the change le. Run the DBCPLUS program again and create a new change le. If the database is corrupt, purge it, and restore a backup copy. ACTION |||||||||||||||||||||||||||||| |||||||||675 MESSAGE Error returned from SORT subsystem (SORTERR n ) (DBA 675). MEANING An error occurred in the SORT subsystem.
685 MESSAGE Unknown event number encountered in check file (DBA 685). MEANING Either the le DatabaseName RX is damaged or a DBChange Plus error exists. Contact your HP representative. ACTION |||||||||||||||||||||||||||||| |||||||||687 MESSAGE Cannot write to the check file FileName RX (FSERR n ) (DBA 687). MEANING The MPE intrinsic FWRITE failed while writing to the check le FileName RX.
710 MESSAGE Cannot write to the data set DataSetName (DAB 710). MEANING The MPE intrinsic FWRITE failed while writing to the data set DataSetName . In addition to 710, message 410 is also displayed. Refer to the MPE Intrinsics Reference Manual , where n is the le system error number returned from the FCHECK intrinsic. ACTION |||||||||||||||||||||||||||||| |||||||||720 MESSAGE Cannot write to file label of data set DataSetName (DBA 720).
750 MESSAGE Cannot write to change file (DBA 750). MEANING The MPE intrinsic FWRITEDIR failed while writing to the change le. In addition to 750, message 410 is also displayed. Refer to the MPE Intrinsics Reference Manual , where n is the le system error number returned from the FCHECK intrinsic. ACTION |||||||||||||||||||||||||||||| |||||||||900 MESSAGE Data set DataSetName : expected N entries, processed only M entries (DBA 900).
B ORDERS Schema The ORDERS database schema that is used for examples throughout this guide is reproduced below before any DBChange Plus modi cations.
SETS: NAME: DATE-MASTER ENTRY: DATE CAPACITY: 365(19); ,A; (3) $CONTROL BLOCKMAX = 640 NAME: CUSTOMER ,M(14/11,18); ENTRY: ACCOUNT (1) LAST-NAME FIRST-NAME INITIAL STREET-ADD CITY STATE ZIP CREDIT-RATING CAPACITY: 201(10); $CONTROL BLOCKMAX = 512 NAME: PRODUCT ,M(13,14/12,18); ENTRY: STOCK# (2) DESCRIPTION CAPACITY: 300(16); NAME: ENTRY: SUP-MASTER SUPPLIER STREET-ADD CITY STATE ZIP CAPACITY: 201(12); NAME: ENTRY: ,M(13/12,18); (1) INVENTORY ,D(12,14/13,18); STOCK# ( PRODUCT ONHANDQTY SUPPLIER (!SUP-MA
NAME: ENTRY: SALES ACCOUNT STOCK# QUANTITY PRICE TAX TOTAL PURCH-DATE DELIV-DATE CAPACITY: 500(10); ,D(11/14,18); ( CUSTOMER (PURCH-DATE )), (!PRODUCT ), , , , , ( DATE-MASTER ), ( DATE-MASTER ); END.
