HP 3000 Manuals HP 3000 Manuals
The HDPDIC Database The HDPDIC database contains all the information needed to allow access to databases as relational tables. Structure of HDPDIC Database The following figure shows how the datasets in the HDPDIC database are related.Figure A-1. The Structure of the HDPDIC Database Size Considerations The schema of the Access Server HDPDIC database defines the following information: ------------------------------------------------------------------------------------------------- - Attributes - Dataset(s) - Default - Minimum - ------------------------------------------------------------------------------------------------- - Remote systems - REMOTE-SYSTEM - 130 - 2 - - Data sources - DATA-SRC-INDEX - 50 - 4 - - - DATA-SRC-NAME - 50 - 4 - - - DATA-SOURCE - 50 - 4 - - Tables - TABLE - 250 - 4 - - - TABLE-SOURCE - 500 - 4 - - - VIEW-DEFINITION - 250 - 4 - - - TABLE-SECURITY - 1250 - 5 - - Items - ITEM - 5000 - 15 - - Access groups - ACCESS-GROUP - 200 - 5 - ------------------------------------------------------------------------------------------------- The size of this default database is roughly 9,400 sectors. Configuration Rules Remote Systems. Up to 128 remote system names can be configured. (One of the additional entries in the REMOTE-SYSTEM dataset handles the host system definition.) Data Sources. If you change the maximum number of configured data sources, set the capacity of each of the datasets DATA-SRC-INDEX, DATA-SRC-NAME, and DATA-SOURCE to the new value. The default number of data sources is 50. Tables. If you change the maximum number of configured tables, change the capacities of each of the following datasets: Dataset Definition TABLE Set the capacity of the dataset TABLE to the maximum number of tables you want to configure. The default number of tables is 250. TABLE-SOURCE Set the capacity of the TABLE-SOURCE dataset to twice the capacity of the TABLE dataset. (For example, 250 doubled is 500.) VIEW-DEFINITION Set the capacity of the VIEW-DEFINITION dataset to the same as that of the TABLE dataset. TABLE-SECURITY There is one entry in this dataset for each ACCESS-GROUP assigned to a table. Public tables use one entry each. The default capacity for the dataset TABLE-SECURITY allows (on the average) five access groups assigned to each table. (The capacity of TABLE-SECURITY is five times the capacity of TABLE.) If you need more than five access groups for each table, increase the capacity of TABLE-SECURITY accordingly. Items. If you want to change the maximum number of table items, change the capacity of the ITEM dataset. The default capacity allows (on the average) 20 entries for each entry in the TABLE dataset. The maximum number of items per table is 64. Access Groups. If you want to change the maximum number of access groups, you must change the capacity of the ACCESS- GROUP dataset. The default number of access groups is 200. Schema for HDPDIC Database $TITLE "Information Access Data Dictionary" $CONTROL BLOCKMAX=2048 BEGIN DATA BASE HDPDIC; <<**** Passwords ****>> << WARNING - Installation jobs may change PASSWORDS: and/or >> << CAPACITY: specifications. PASSWORDS: and CAPACITY: spec- >> << ifications must each be self-contained within 1 record. >> PASSWORDS: 1 WEDIDIT; <<**** Items ****>> ITEMS: VERSION-ID, X16; DATA-SOURCE-IX, I; YEAR-DATE, X2; MONTH-DATE, X2; ACCESS-GR-NAME, X16; ACCESS-GR-NAME1, X16; ACCESS-GR-NAME2, X16; ACCESS-GR-NAME3, X16; ACCESS-GR-NAME4, X16; ACCESS-GR-NAME5, X16; ACCESS-GR-NAME6, X16; ACCESS-GR-NAME7, X16; ACCESS-GR-NAME8, X16; ADD-DB-CAP, I; DEL-TBL-CAP, I; OTHER-CAP, I; ENTRY-TYPE, I; SYSTEM-NAME, X8; SYSTEM-DESCR, X50; ACCESS-METHOD-01, X50; ACCESS-METHOD-02, X8; ACCESS-METHOD-03, X8; ACCESS-METHOD-04, X8; ACCESS-METHOD-05, X8; ACCESS-METHOD-06, X8; ACCESS-METHOD-07, X8; ACCESS-METHOD-08, X8; DATA-SOURCE-NAME, X8; LOCATION-FLD-01, X8; LOCATION-FLD-02, X8; USER-NAME, X32; PASSWORD, X8; OPEN-MODE, I; DATA-SRC-DESCR, X50; TABLE-NAME, X16; TABLE-KIND, X2; TABLE-DESCR, X50; RECORD-LENGTH, I; NUM-ITEMS, I; SAMPLE-VALUES, I; PART-OF-VIEW, I; ALL-ITEMS, I; SRC-OBJECT-NAME, X98; NUM-ACCESS-GRS, I; ITEM-NAME, X16; ITEM-KIND, X2; TYPE-DESIGNATOR, X4; CONVERSION-TYPE, X2; LENGTH, I; DECIMALS, I; ARRAY-BOUND, I; OFFSET, K; MISSING-VALUE, X2; SOURCE-ITEM-NAME, X32; SOURCE-ITEM-INFO, X4; SOURCE-OFFSET, I; ITEM-CLAUSE, 64X16; USING-CLAUSE, 4X160; WHERE-CLAUSE, 4X160; SORT-CLAUSE, X160; GROUP-CLAUSE, X160; OWNER-NAME, X16; <<**** Sets ****>> SETS: <<**********************>> << >> << DEFN detail >> << >> <<**********************>> <<Used to store global information. >> <<PATHS - None. >> NAME: DEFN, DETAIL ( /1 ); ENTRY: VERSION-ID, <<V.UU indicating dictionary version. >> DATA-SOURCE-IX,<<Current data source index. >> YEAR-DATE, <<Format for year. >> MONTH-DATE; <<Format for month. >> << WARNING - Installation jobs may change PASSWORDS: and/or >> << CAPACITY: specifications. PASSWORDS: and CAPACITY: spec- >> << ifications must each be self-contained within 1 record. >> CAPACITY: 1; <<*****************************>> << >> << REMOTE-SYSTEM manual >> << >> <<*****************************>> <<Used for remote HP 3000. >> <<PATHS - Linked to DATA-SOURCE and DATA-SRC-SYSTEM. A remote >> <<HP 3000 system cannot be deleted if databases or files are >> <<configured for the remote system. >> NAME: REMOTE-SYSTEM, MANUAL ( /1 ); ENTRY: ENTRY-TYPE, <<HP 3000 (01). >> SYSTEM-NAME (2), <<Key item. HP 3000 remote system name; >> SYSTEM-DESCR, <<HP 3000 unused; >> ACCESS-METHOD-01, <<HP 3000 node name; >> ACCESS-METHOD-02, <<HP 3000 user name; >> ACCESS-METHOD-03, <<HP 3000 user password; >> ACCESS-METHOD-04, <<HP 3000 account name; >> ACCESS-METHOD-05, <<HP 3000 account password; >> ACCESS-METHOD-06, <<Reserved for future use. >> ACCESS-METHOD-07, <<Reserved for future use. >> ACCESS-METHOD-08, <<Reserved for future use. >> OWNER-NAME; <<Owner of this entry. >> << WARNING - Installation jobs may change PASSWORDS: and/or >> << CAPACITY: specifications. PASSWORDS: and CAPACITY: spec- >> << ifications must each be self-contained within 1 record. >> CAPACITY: 130; <<**********************************>> << >> << DATA-SRC-INDEX automatic >> << >> <<**********************************>> <<Every database or file has a unique index associated >> <<with it. The index allows all data sources to be opened >> <<easily without having to know where they are physically >> <<located. Also allows easy access to remote files. >> <<DATA-SRC-INDEX is kept in other datasets to uniquely identify >> <<the data source. The index is kept as a positive number. >> <<PATHS - Linked to DATA-SOURCE, DATA-SRC-SYSTEM, and >> <<table-SOURCE. >> NAME: DATA-SRC-INDEX, AUTOMATIC ( /1 ); ENTRY: DATA-SOURCE-IX(3); <<Key item. List of database and file. >> << WARNING - Installation jobs may change PASSWORDS: and/or >> << CAPACITY: specifications. PASSWORDS: and CAPACITY: spec- >> << ifications must each be self-contained within 1 record. >> CAPACITY: 50; <<*********************************>> << >> << DATA-SRC-NAME automatic >> << >> <<*********************************>> <<This dataset contains a list of all of the databases and files.>> <<This allows the DATA-SOURCE dataset to have duplicate >> <<DATA-SOURCE-NAME search items. >> <<PATHS - Linked to DATA-SOURCE. >> NAME: DATA-SRC-NAME, AUTOMATIC ( /1 ); ENTRY: DATA-SOURCE-NAME (1); <<Key item. List of databases and files.>> << WARNING - Installation jobs may change PASSWORDS: and/or >> << CAPACITY: specifications. PASSWORDS: and CAPACITY: spec- >> << ifications must each be self-contained within 1 record. >> CAPACITY: 50; <<**********************************>> << >> << DATA-SRC-SYSTEM detail >> << >> <<**********************************>> <<PATHS - Linked to REMOTE-SYSTEM and DATA-SRC-INDEX. >> <<Reserved for future use. >> NAME: DATA-SRC-SYSTEM, DETAIL ( /1); ENTRY: ENTRY-TYPE, <<Reserved for future use. >> DATA-SOURCE-IX (DATA-SRC-INDEX), <<Reserved for future use. >> SYSTEM-NAME(REMOTE-SYSTEM); <<Reserved for future use. >> << WARNING - Installation jobs may change PASSWORDS: and/or >> << CAPACITY: specifications. PASSWORDS: and CAPACITY: spec- >> << ifications must each be self-contained within 1 record. >> CAPACITY: 1; <<****************************>> << >> << DATA-SOURCE detail >> << >> <<****************************>> <<Each configured database or file has an entry in this dataset >> <<describing the location of and access to that data source. >> <<PATHS - Linked to REMOTE-SYSTEM, DATA-SRC-INDEX, and >> <<DATA-SRC-NAME. >> NAME: DATA-SOURCE, DETAIL ( /1 ); ENTRY: ENTRY-TYPE, <<IMAGE (01), File (03) >> DATA-SOURCE-IX (DATA-SRC-INDEX), <<HP 3000 database index >> <<or file index; >> DATA-SOURCE-NAME (DATA-SRC-NAME), <<HP 3000 database name >> <<or file name; >> LOCATION-FLD-01, <<HP 3000 group where database or >> <<file resides; >> LOCATION-FLD-02, <<HP 3000 account where database or >> <<file resides; >> SYSTEM-NAME (REMOTE-SYSTEM), <<HP 3000 DS device name or number >> <<(blank for local); >> USER-NAME, <<Reserved for future use. >> PASSWORD, <<HP 3000 database password or file >> <<lockword;>> OPEN-MODE, <<IMAGE DBOPEN mode (5 through 8); >> <<MPE file type =>> << 0 - Unknown file type (does not >> << exist) >> << 1 - KSAM file >> << 2 - BRW/IRF file >> << 3 - SD file >> << 4 - Regular flat file >> DATA-SRC-DESCR, <<Reserved for future use. >> OWNER-NAME; <<Owner of this entry. >> << WARNING - Installation jobs may change PASSWORDS: and/or >> << CAPACITY: specifications. PASSWORDS: and CAPACITY: spec- >> << ifications must each be self-contained within 1 record. >> CAPACITY: 50; <<**********************>> << >> << TABLE manual >> << >> <<**********************>> <<This set contains information for each configured table. >> <<PATHS - Linked to TABLE-SOURCE, VIEW-DEFINITION, ITEM and >> <<table-SECURITY. >> NAME: TABLE, MANUAL ( /1 ); ENTRY: TABLE-NAME (4), <<Key item. Table name. >> TABLE-KIND, <<Type: view, manual/detail, file. >> << V : view table >> << M3: manual master dataset 3000 table >> << A3: automatic master dataset 3000 table >> << D3: detail dataset 3000 table >> << FI: MPE file table >> TABLE-DESCR, <<Description of the table. >> RECORD-LENGTH, <<Record length of table in bytes. >> NUM-ITEMS, <<Number of items in the table. >> SAMPLE-VALUES, <<1 if Where Clause must be used, else 0. >> PART-OF-VIEW, <<1 if part of a view table, else 0. >> ALL-ITEMS, <<1 if all items in dataset, else 0. >> << For IMAGE tables, 1 means that all the >> << items in the dataset are in this table >> << and we can send a '@' for the item list>> OWNER-NAME; <<Owner of this entry. >> << WARNING - Installation jobs may change PASSWORDS: and/or >> << CAPACITY: specifications. PASSWORDS: and CAPACITY: spec- >> << ifications must each be self-contained within 1 record. >> CAPACITY: 250; <<******************************>> << >> << TABLE-SOURCE detail >> << >> <<******************************>> <<This dataset associates tables with databases and datasets >> <<or with files. >> <<PATHS - Each record in the TABLE dataset must have at least>> <<one record in TABLE-SOURCE linked to it. Each table must >> <<also have at least one data source from DATA-SRC-INDEX >> << associated with it. >> NAME: TABLE-SOURCE, DETAIL ( /1 ); ENTRY: ENTRY-TYPE, <<Database (01), file (03) >> TABLE-NAME (TABLE), <<table name. >> DATA-SOURCE-IX (DATA-SRC-INDEX), <<Database or file used to assembe the >> <<table. >> SRC-OBJECT-NAME; <<Dataset used to assemble the table; >> <<unused for files. >> << WARNING - Installation jobs may change PASSWORDS: and/or >> << CAPACITY: specifications. PASSWORDS: and CAPACITY: spec- >> << ifications must each be self-contained within 1 record. >> CAPACITY: 500; <<*********************************>> << >> << VIEW-DEFINITION detail >> << >> <<*********************************>> <<If the table is a view table, this dataset contains the >> <<special view definition of the table. It contains the items >> <<in the table, the other tables that make up the view table >> <<and the Where Clause that indicates how the table is to be >> <<loaded and assembled. It also contains the Sort Clause. >> <<PATHS - Linked to TABLE dataset by TABLE-NAME. >> NAME: VIEW-DEFINITION, DETAIL ( /1 ); ENTRY: TABLE-NAME (TABLE), <<Name of view table. >> ITEM-CLAUSE, <<The ITEM-CLAUSE, USING-CLAUSE, >> USING-CLAUSE, <<WHERE-CLAUSE, and SORT-CLAUSE >> WHERE-CLAUSE, <<as they appear on the Add View Table >> SORT-CLAUSE, <<screens in the Administrator Utility. >> GROUP-CLAUSE; <<Reserved for future use. >> << WARNING - Installation jobs may change PASSWORDS: and/or >> << CAPACITY: specifications. PASSWORDS: and CAPACITY: spec- >> << ifications must each be self-contained within 1 record. >> CAPACITY: 250; <<*****************************>> << >> << ACCESS-GROUP manual >> << >> <<*****************************>> <<This dataset contains all of the access groups in the system.>> <<PATHS - Linked to TABLE-SECURITY and ITEM datasets >> <<by ACCESS-GR-NAME. >> NAME: ACCESS-GROUP, MANUAL ( /1 ); ENTRY: ACCESS-GR-NAME (9), <<Key item. Contains access group names. >> ADD-DB-CAP, <<Contains Add Database and Add Table capability. >> DEL-TBL-CAP, <<Contains Delete Table capability. >> OTHER-CAP, <<Other capabilities flags. >> OWNER-NAME; <<Owner of this entry. >> << WARNING - Installation jobs may change PASSWORDS: and/or >> << CAPACITY: specifications. PASSWORDS: and CAPACITY: spec- >> << ifications must each be self-contained within 1 record. >> CAPACITY: 200; <<*******************************>> << >> << TABLE-SECURITY detail >> << >> <<*******************************>> <<This dataset contains at least one entry for each configured >> <<table. For public tables, the sole entry has a "blank" access >> <<group associated with it. For non-public tables, there is one >> <<entry for each access group assigned to the table. >> <<PATHS - Linked to TABLE by TABLE-NAME. Linked to ACCESS-GROUP >> <<by ACCESS-GR-NAME. >> NAME: TABLE-SECURITY, DETAIL ( /1 ); ENTRY: TABLE-NAME (TABLE), <<table name for security. >> ACCESS-GR-NAME (ACCESS-GROUP); <<Access group name. >> << WARNING - Installation jobs may change PASSWORDS: and/or >> << CAPACITY: specifications. PASSWORDS: and CAPACITY: spec- >> << ifications must each be self-contained within 1 record. >> CAPACITY: 1250; <<*********************>> << >> << ITEM detail >> << >> <<*********************>> <<Every item in every table has an entry in this dataset that>> <<describes the item in detail. All the items in a table are>> <<linked in this dataset. >> <<PATHS - Linked to TABLE by TABLE-NAME to describe all items>> <<in the table. Linked to ACCESS-GROUP by ACCESS-GR-NAME to >> <<describe item security. No more than eight access groups >> <<can be assigned to any one item. >> NAME: ITEM, DETAIL ( /1 ); ENTRY: NUM-ACCESS-GRS, <<Number of security access groups >> <<(0 through 8). >> ACCESS-GR-NAME1 (ACCESS-GROUP), <<List of access groups that >> ACCESS-GR-NAME2 (ACCESS-GROUP), <<can access this item. >> ACCESS-GR-NAME3 (ACCESS-GROUP), <<If no access groups are >> ACCESS-GR-NAME4 (ACCESS-GROUP), <<specified, all access >> ACCESS-GR-NAME5 (ACCESS-GROUP), <<groups that can access the >> ACCESS-GR-NAME6 (ACCESS-GROUP), <<associated table >> ACCESS-GR-NAME7 (ACCESS-GROUP), <<can access >> ACCESS-GR-NAME8 (ACCESS-GROUP), <<this item. >> TABLE-NAME (TABLE(OFFSET)), <<Pointed to by TABLE, sorted by >> <<OFFSET. >> ITEM-NAME, <<The name of this item. >> ITEM-KIND, <<View, search, key, normal, KSAM, other. >> << V: view item >> << S: IMAGE search item >> << K: IMAGE key item >> << N: IMAGE non-search item >> << K: KSAM file item >> << : other file item >> TYPE-DESIGNATOR, <<I = Integer, R = Real, P = Packed, >> <<Z = Zoned, L = Logical, C = Character, >> <<N = Numeric. >> CONVERSION-TYPE, <<Convert Z, P, or I to C = Character, >> <<R = Real, or I = Integer. (Also, >> <<internally, R = Real2-to-Real4 >> <<conversion; I = L-to-I conversion.) >> LENGTH, <<In words for I (1 or 2), R (2 or 4) and >> <<L (always 1); in bytes for C (1 to 256),>> <<Z (2 to 26); in nibbles (4 bits) for >> <<P (1 to 28). Value is 0 for special date>> <<and time types since their length is >> <<fixed. >> DECIMALS, <<Decimal point for data conversions. >> ARRAY-BOUND, <<Number of sub-items if item is an IMAGE >> <<array, 0 if the item is a scalar type. >> OFFSET, <<Sort item, byte offset of item into table.>> MISSING-VALUE, <<Reserved for future use. >> SOURCE-ITEM-NAME, <<Reserved for future use. >> SOURCE-ITEM-INFO, <<HP 3000 to identify IMSAM keys (I) >> <<and IMSAM composite keys (IC); >> SOURCE-OFFSET; <<Offset in original record for file tables.>> << WARNING - Installation jobs may change PASSWORDS: and/or >> << CAPACITY: specifications. PASSWORDS: and CAPACITY: spec- >> << ifications must each be self-contained within 1 record. >> CAPACITY: 5000; END.
![[]](../../pic3k/M012039/FFN1363c50.gif)