HP 3000 Manuals HP 3000 Manuals
The HDPENV Database The HDPENV database contains all information having to do with Access Server users. Structure of HDPENV Database The following figure shows how the datasets in the HDPENV database are related.Figure A-2. The Structure of the HDPENV Database Size Considerations The schema of the Access Server HDPENV database defines the following information: ------------------------------------------------------------------------------------------------ - Attributes - Dataset(s) - Default - Minimum - ------------------------------------------------------------------------------------------------ - Saved tables - SAVE-NAME-INDEX - 500 - 1 - - - SAVE - 500 - 1 - - - TABLE-FILE - 500 - 1 - - Saved table items - ITEM - 10,000 - 1 - - Users - USER-ID-INDEX - 40 - 1 - - - USER - 200 - 5 - - - JOB-STATUS - 500 - 1 - - Active users - USER-MONITOR - 40 - 1 - - Screens - CFG-TXN - 211 - 2 - ------------------------------------------------------------------------------------------------ The size of this default database is roughly 2,300 sectors. If you want to change the size of the database, change the capacity of the datasets that are affected. The capacity of each manual master dataset should be a prime number to improve the performance of IMAGE. Configuration Rules Users. If you change the maximum number of users, the capacity of the USER dataset should be set to the new value. The default number of users is 211. Saved Tables. If you change the maximum number of saved tables, set the capacities of the SAVE-NAME-INDEX, SAVE and TABLE-FILE datasets to the new value. The default number of saved tables is 500. Items. If you change the maximum number of Saved Table items, change the capacity of the ITEM dataset. The default capacity of 10,000 represents (on the average) 20 entries for each item in the SAVE dataset. The maximum number of items per table is 64. Active Users. If you change the maximum number of active users, the capacity of the USER-MONITOR and USER-ID-INDEX datasets must be changed. The default number of active users is 40. Screens. The CFG-TXN dataset is used for utility screen information. You should not change its capacity. Schema for HDPENV Database $TITLE "Information Access Data Dictionary" BEGIN DATA BASE HDPENV; <<**** 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: SAVE-NAME, X16 (/1); SAVE-DESCR, X50 (/1); USER-NAME, X16 (0/1); USER-PASSWORD, X16 (/1); ACCESS-GROUP, X16 (0/1); MAX-ACTIVE-USERS, I (/1); NUM-ACTIVE-USERS, I (/1); PRIORITY-QUEUE, X2 (/1); USER-PARM-FILE, X8 (/1); HDP-ID, I (/1); VERSION-ID, X12 (/1); TABLE-FILE-NAME, X8 (/1); RECORD-LENGTH, I (/1); NUM-RECORDS, I2 (/1); NUM-SECTORS, I2 (/1); NUM-ITEMS, I (/1); ITEM-NAME, X16 (/1); ITEM-TYPE, I (/1); ITEM-OFFSET, K (/1); ITEM-LENGTH, I (/1); DECIMAL-PLACE, I (/1); ARRAY-BOUND, I (/1); CONV-TYPE, I (/1); USER-ID, I (/1); LOGON-DATE, I1 (/1); LOGON-TIME, I2 (/1); MAX-NUM-SAVE, I (/1); CURRENT-NUM-SAVE, I (/1); MAX-NUM-SECT, I2 (/1); CURRENT-NUM-SECT, I2 (/1); USER-FLAGS, I (/1); SYSTEM-FLAGS, I (/1); MAX-TBL-RECORDS, I2 (/1); CFG-TXN-NAME, X16 (/1); CFG-TXN-NBR, I (/1); DISPLAY-PWS, I (/1); PRINT-PWS, I (/1); JOB-NUMBER, X8 (0/1); JOB-NAME, X8 (0/1); DATE-STAMP, X14 (0/1); TIME-STAMP, X8 (0/1); STATUS-MESSAGE, X80 (0/1); JS-DATE, I (0/1); CHAR-CONV-TBL, 2X128 (/1); OWNER-NAME, X16 (/1); PRIV-TAB-SEC, X16 (/1); EDITOR-FILE, X8 (/1); EDITOR-GROUP, X8 (/1); EDITOR-ACCOUNT, X8 (/1); EDITOR-LOCKWORD, X8 (/1); EDITOR-INFO, X16 (/1); EDITOR-PARM, X6 (/1); <<**** Sets ****>> SETS: <<***************************************>> << >> << SAVE-NAME-INDEX automatic >> << >> <<***************************************>> <<This dataset exists so that the SAVE dataset can have >> <<duplicate Save names as search items under different users. >> <<PATHS - Linked to SAVE dataset by SAVE-NAME. >> NAME: SAVE-NAME-INDEX, AUTOMATIC(/1); ENTRY: SAVE-NAME(1); <<Key item. >> << 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; <<***************************************>> << >> << USER-ID-INDEX automatic >> << >> <<***************************************>> <<This dataset enables duplicate user names to exist in the >> <<USER-MONITOR dataset as search items. >> <<PATHS - Linked to USER-MONITOR by USER-ID. >> NAME: USER-ID-INDEX, AUTOMATIC(/1); ENTRY: USER-ID(1); <<Key item. >> << WARNING - Installation jobs may change PASSWORDS: and/or >> << CAPACITY: specifications. PASSWORDS: and CAPACITY: spec- >> << ifications must each be self-contained within 1 record. >> CAPACITY: 40; <<***************************************>> << >> << USER manual >> << >> <<***************************************>> <<This dataset contains detailed information about each user. >> <<PATHS - This dataset is linked to the SAVE dataset by USER-NAME>> <<so that all the tables the user previously saved can be >> <<retrieved, based on the user's name. >> NAME: USER, MANUAL(/1); ENTRY: USER-NAME(3), <<Logon user name. >> USER-PASSWORD, <<User password. >> ACCESS-GROUP, <<User access group. >> MAX-NUM-SAVE, <<Maximum number of Save files for user. >> CURRENT-NUM-SAVE, <<Current number of Save files for user. >> MAX-NUM-SECT, <<Maximum number of sectors for user. >> CURRENT-NUM-SECT, <<Current number of sectors for user. >> PRIORITY-QUEUE, <<Server's MPE priority (CS,DS,ES). >> USER-PARM-FILE, <<Not currently used. >> USER-FLAGS, <<User capabilities. >> OWNER-NAME, <<Owner of this entry. >> PRIV-TAB-SEC, EDITOR-FILE, EDITOR-GROUP, EDITOR-ACCOUNT, EDITOR-LOCKWORD, EDITOR-INFO, EDITOR-PARM; << 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-FILE manual >> << >> <<***************************************>> <<This dataset contains an entry for each table file created. >> <<PATHS - This dataset is linked to ITEM by TABLE-FILE-NAME so>> <<that each item in the table has a detailed item description >> <<associated with it in ITEM. This dataset is also linked to >> <<SAVE because each Saved table has a Table file associated >> <<with it. It's possible to have multiple entries in the SAVE >> <<dataset linked to one entry in this dataset. >> NAME: TABLE-FILE, MANUAL(/1); ENTRY: TABLE-FILE-NAME(2), <<Key item. Unique MPE file name. >> RECORD-LENGTH, <<Record length of table row, in bytes. >> NUM-RECORDS, <<Number of records or rows in table. >> NUM-SECTORS, <<Number of MPE sectors allowed for table.>> NUM-ITEMS; <<Number of items in the table. >> << 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; <<***************************************>> << >> << ITEM detail >> << >> <<***************************************>> <<Each item of each table has an entry in this dataset. Each >> <<item is described in complete detail by the records in this>> <<dataset. >> <<PATHS - Every entry in TABLE-FILE has a chain of items >> <<in this dataset. >> NAME: ITEM, DETAIL(/1); ENTRY: TABLE-FILE-NAME(TABLE-FILE(ITEM-OFFSET)), <<Name of table file this item is in. >> ITEM-NAME, <<Name of the item. >> ITEM-TYPE, <<Type of the item: 1 = Logical, 2 = Integer1, >> << 3 = Integer2, 4 = Real2, 5 = Real4, >> << 6 = Character, 7 = Packed, 8 = Zoned, >> << 16 = Free-form numeric, 17 = Integer4. >> ITEM-OFFSET, <<Byte offset of item in record of table. >> ITEM-LENGTH, <<Length of item in bytes. >> DECIMAL-PLACE, <<Decimal place for converted items. >> ARRAY-BOUND, <<Number of sub-items if in an IMAGE array. >> CONV-TYPE; <<Conversion Type for item: 3(I2), 5(R4), 6(C).>> << WARNING - Installation jobs may change PASSWORDS: and/or >> << CAPACITY: specifications. PASSWORDS: and CAPACITY: spec- >> << ifications must each be self-contained within 1 record. >> CAPACITY: 10000; <<***************************************>> << >> << SAVE detail >> << >> <<***************************************>> <<Contains information about each saved table. >> <<PATHS - Linked to TABLE-FILE so that the Table file can be >> <<accessed based on the Save name. Linked to USER because >> <<each Saved table was created by a particular user. >> <<Also linked to SAVE-NAME-INDEX. >> NAME: SAVE, DETAIL(/1); ENTRY: USER-NAME(USER), <<Creator of Saved table. >> SAVE-NAME(SAVE-NAME-INDEX), <<Allows duplicate names. >> SAVE-DESCR, <<50-character description of table.>> TABLE-FILE-NAME(TABLE-FILE); <<table file of save. >> << 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; <<***************************************>> << >> << USER-MONITOR detail >> << >> <<***************************************>> <<One record is added to this dataset each time a user logs on to>> <<Information Access. The Database Administrator can use this to >> <<monitor who is using the system. >> <<PATHS - Linked to USER-ID-INDEX by USER-ID. Linked to USER >> <<by USER-NAME. >> NAME: USER-MONITOR, DETAIL(/1); ENTRY: USER-NAME(USER), <<Name of user who is logged on. >> USER-ID(USER-ID-INDEX), <<Allows duplicate names. >> LOGON-DATE, <<CALENDAR intrinsic format - yyddd. >> LOGON-TIME, <<CLOCK intrinsic format - hours, minutes, >> <<seconds, tenths of seconds. >> PRIORITY-QUEUE; <<Server's MPE priority (CS,DS,ES). >> << WARNING - Installation jobs may change PASSWORDS: and/or >> << CAPACITY: specifications. PASSWORDS: and CAPACITY: spec- >> << ifications must each be self-contained within 1 record. >> CAPACITY: 40; <<***************************************>> << >> << JOB-STATUS detail >> << >> <<***************************************>> <<Contains status information about host batch jobs. >> <<PATHS - Linked to USER by JOB-NUMBER. >> NAME: JOB-STATUS, DETAIL (0/1); ENTRY: USER-NAME (USER (JOB-NUMBER)), <<Name of user. >> JOB-NUMBER, <<Job number of host batch job. >> JOB-NAME, <<Name of host batch job. >> DATE-STAMP, <<Date when status record is posted. >> TIME-STAMP, <<Time when status record is posted. >> STATUS-MESSAGE, <<Status text. >> ACCESS-GROUP, <<User's access group. >> JS-DATE; <<Date in calendar format. >> << 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; <<***************************************>> << >> << HDP-INFO detail >> << >> <<***************************************>> <<Contains global information about the system. >> <<PATHS - None. >> NAME: HDP-INFO, DETAIL(/1); ENTRY: MAX-ACTIVE-USERS, <<Maximum number of active users. >> NUM-ACTIVE-USERS, <<Current number of active users. >> HDP-ID, <<Value from ENABLEAC, indicating if >> <<Information Access Server is available >> <<or unavailable. >> VERSION-ID, <<Format V.UU of dictionary. >> DISPLAY-PWS, <<Show passwords for screens & Print key >> PRINT-PWS, <<Show passwords for reports. >> SYSTEM-FLAGS, <<The site character set. >> CHAR-CONV-TBL, <<IMF Character conversion table. >> MAX-TBL-RECORDS; <<Maximum records allowed in a table. >> << 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; <<***************************************>> << >> << CFG-TXN manual >> << >> <<***************************************>> <<This dataset is used by the Administrator Utility >> <<to retain the screen names. >> <<PATHS - None. >> NAME: CFG-TXN, MANUAL(/1); ENTRY: CFG-TXN-NAME(0), <<Key name. Admin Utility screen name. >> CFG-TXN-NBR; <<Screen number. >> << WARNING - Installation jobs may change PASSWORDS: and/or >> << CAPACITY: specifications. PASSWORDS: and CAPACITY: spec- >> << ifications must each be self-contained within 1 record. >> CAPACITY: 211; END.
![[]](../../pic3k/M012039/FFN1503c50.gif)