HP 3000 Manuals HP 3000 Manuals
Information Access Server: Planning and Configuring Printed in U.S.A. HP Part No. B1716-90024 Edition Third Edition E0290
(c) 1987, 1988, 1990 by HEWLETT-PACKARD COMPANY Printed 19900201 Notice The information contained in this document is subject to change without notice. HEWLETT-PACKARD PROVIDES THIS MATERIAL "AS IS" AND MAKES NO WARRANTY OF ANY KIND, EXPRESSED OR IMPLIED, 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 FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE OR USE OF THIS MATERIAL WHETHER BASED ON WARRANTY, CONTRACT, OR OTHER LEGAL THEORY. Hewlett-Packard assumes no responsibility for the use or reliability of its software on equipment that is not furnished by Hewlett-Packard. This document contains proprietary information which is protected by copyright. All rights are reserved. No part of this document may be photocopied, reproduced or translated to another language without the prior written consent of Hewlett-Packard Company. ________________________________________________________________________ Company or product names followed by (R) are U.S. registered trademarks of the respective company. Company or product names followed by (TM) are registered trademarks of the respective company. Lotus 1-2-3(R), Symhpony(R), and VisiCalc(R) are U.S. registered trademarks of Lotus Development Corporation. Omnidex(TM), and IMSAM(TM) are U.S. trademarks of Dynamic Information Systems Corporation. CONDOR(TM) is a U.S. trademark of Condor Computer Corporation. dBASE II(R), dBASEIII(R), and dBASE IV(R), are U.S. registered trademarks of Ashton-Tate Corp. IBM(R), PC(TM), XT(TM), AT(TM), PC-DOS(R), and DisplayWrite 3 are trademarks of International Business Machines Corp. MS-DOS(R), Microsoft(R), and Multiplan(R) are U.S. registered trademarks of Microsoft Corporation. Data Management Systems Division 8010 Foothills Boulevard Roseville, CA 95678, U.S.A. Printing History New editions are complete revisions of a manual. Update packages are issued between editions. They contain additional and replacement pages to be merged into the manual by the customer. The following print dates are in effect for this manual: Printed in: ________________________________________________________________________ First Edition, April, 1987 .............................. U.S.A. Second Edition, June, 1988 ................................... . Third Edition, February, 1990 ................................ . Conventions Convention Description This symbol represents a labeled key on the keyboard. For example, Shift is the shift key, Y is the Y key, etc. Exceptions Keyboard Instructions: The Enter and Return keys discussed in our procedures and examples specifically refer to the Enter and Return keys on a terminal. If you are using an HP Vectra, IBM, Compaq, or IBM-compatible personal computer with a terminal emulator, use the keys that are the equivalent of Enter and Return. Function Label f1 Function Labels correspond to function keys labeled f1 through f8 on the keyboard. If your keyboard has another set of keys labeled f1 through f10, these keys will not work for utilities on the HP 3000. To choose a Function Press the corresponding function key on your keyboard. Label... Although PC users can choose function labels using HP Touch or a mouse, these input devices are not active for utilities on the HP 3000. SCREEN TEXT Screen text represents text, examples, or syntax statements displayed on the screen. Examples and syntax statements may include a program prompt, COMMANDS, ELEMENTS, variables, symbols, and punctuation. For example: :HELLO username.accountname :FILE T;DEV=TAPE;DEN=1600 :STORE filename.group.account;*T;SHOW Table Front-0. (cont.) Convention Description COMMANDS and are displayed in UPPERCASE to indicate that ELEMENTS they are to be typed as shown. variables represent parameters you MUST replace with appropriate information. ``;,". punctuation are typed as shown except for {} braces and and [] brackets which are used to indicate *!@= symbols alternates and options. {ALTERNAMES} are COMMANDS, ELEMENTS, or variables within {braces}. At least one is required. { ALTERNATE A} Type A or B { ALTERNATE B} [OPTIONS] are commands, elements, or variables within [brackets]. All are optional. [ OPTION A] Type A, B, or neither [ OPTION B] SCREEN HIGHLIGHT Represents highlighted text or data entry fields on the screen. _______________________________________ | | | | | Screen Title | | Instructions | | | | Field data entry | | | | | | | _______________________________________ This screen image represents your workstation screen. Our example includes a Screen Title displayed on the top banner line. This may be followed by a single line of Instructions. Within the body of the screen we have an example of a Field name and an associated data entry field where you would type in your data. Function labels along the bottom of the screen display operations you can perform, or provide assistance. Before You Begin Information Access in Brief Information Access is a component of HP NewWave Office. It consists of Information Access Server, Information Access SQL/XL, Information Access SQL/UX, and Information Access PC. Information Access allows users on PC workstations to access information resident on HP 3000 and HP 9000 computers, depending on which server is used, as well as to access PC-resident databases. * Information Access Server is the HP 3000-based data server running on MPE/V and MPE/XL. * Information Access SQL/XL is the HP 3000-based SQL server running only on MPE/XL. * Information Access SQL/UX is the HP 9000-based SQL server running on HP-UX. * Information Access PC is the PC-based software with which users retrieve, manipulate, and save information, locally or on the HP 3000 or HP 9000.
NOTE For U-based (and later) MITs, Information Access Server works with TurboIMAGE/3000 on the host HP 3000. Remote databases accessed by Information Access Server can be either IMAGE/3000 or TurboIMAGE/3000 databases. Throughout this manual, the term IMAGE is used as a shorthand term for IMAGE/3000 and TurboIMAGE/3000. Access PC and Access Server are used as shorthand terms for Information Access PC and Information Access Server, respectively.
Who Should Read This Manual This manual is used to plan and configure Information Access Server. If you are a primary or secondary Database Administrator (DBA) or someone working in that capacity, you'll be doing the planning and configuring of Information Access Server. Certain phases of the configuration process are only available to primary DBAs. These phases are marked "Primary DBA only." Some instructions may require that you consult with your System Manager. We assume that both primary and secondary DBAs have an understanding or working knowledge of: * Database administration concepts and practices * Programming in commercial applications * PCs and their applications * HP 3000 * IMAGE databases * Data file structure * Dictionary/3000 (optional) Primary and Secondary DBA Capabilities Information Access allows more than one DBA to run the Administrator Utility. However, only the primary DBA can perform all the Administrator functions or have unlimited access to all data in the Information Access data dictionary. The primary DBA has complete control of the Administrator Utility and its functions and can delegate certain responsibilities to one or more secondary DBAs. The primary DBA has control of all the tables within Information Access, regardless of who configured them or who controls the data source. A secondary DBA has control over only those access groups, users, tables, and data sources that were configured by him or her or that have been transferred from another DBA. The primary DBA is preconfigured in the data dictionary with the user name ADMIN, which cannot be changed or deleted. The password for ADMIN can be changed or modified at any time. See "Securing the Administrator Utility," later in this chapter. Secondary DBAs are designated by the primary DBA at the Add User screen in the Administrator Utility. See "Phase J, Configuring Users" in Chapter 2 of this manual. Primary DBA Capabilities * Has full Administrator Utility capabilities * Has unlimited access to data dictionary * Configures tables from all data sources * Configures users and access groups * Defines certain users as secondary DBAs * Has override power over secondary DBAs * Configures remote systems * Controls entries in the data dictionary that are not controlled by a secondary DBA * Can synchronize any table in the data dictionary * Can produce reports showing entire system configuration Secondary DBA Capabilities * Controls data sources either configured by self or transferred from another DBA * Configures tables from data sources they control * Configures table and item security for tables they control * Configures access groups and users * Can transfer control of a data source to another DBA * Can synchronize tables they control * Can produce reports showing portions of the system configuration that they control Rules for DBAs * The controller of an IMAGE or file table must control the data source from which the table is configured. * To control view tables, a secondary DBA must control all of the tables from which the view table is configured. * View tables created from tables that are controlled by more than one DBA can only be configured and controlled by the primary DBA. * Data sources and tables can be changed, deleted, or displayed by the primary DBA or the controlling secondary DBA. * Secondary DBAs can configure users but cannot define a user as a secondary DBA. For descriptions of how the primary DBA and secondary DBAs perform specific Administrator Utility functions, see the appropriate chapters in the Information Access Server: Database Administration manual. Setting Up Planning and configuring are two important stages in the five-stage process of setting up Access Server. Figure 1 shows where you'll find the written instructions and reference material for each stage.Figure 1. Setting Up Access Server: Five Stages Here is a summary of what you will be doing to set up Access Server. Read through these stages. Then carry each one out, in order, by referring to the manual and chapter listed. 1. Installing Access Server. If Access Server is being installed on the HP 3000 by HP NewWave Office System Services, the installation is performed by an HP Systems Engineer (SE). If Access Server is being installed on the HP 3000 as a standalone system, the installation is performed by the System Manager. As part of the installation, the AUTOINSTL program streams a job that builds and initializes (for a first-time installation) or restructures (for an update to a new release) the Information Access data dictionary. * If this is an initial installation, the SE or System Manager is encouraged to accept the defaults which come with the product. Later, once you've learned the tutorial in the Information Access Server: Learning the Administrator Utility manual, you'll be in a position to decide whether the data dictionary needs to be adjusted (see the next stage). * If this installation updates a previous version of the product, you or your System Manager (or SE) can adjust dataset capacities and data dictionary passwords during installation. For the installation steps, see Chapter 3 of the Information Access Server: System Management manual. Securing the Administrator Utility. After the product is installed, we recommend that you secure the Administrator Utility by following the instructions in "Securing the Administrator Utility," later in this chapter. 2. Learning the Administrator Utility. If you are new to the product, use the DBA tutorial part of the Information Access Server: Learning the Administrator Utility manual. It will teach you how to use the Administrator Utility to configure databases, files, tables, access groups, users, and data security. Even if you have used the product before, you may find it useful to redo the tutorial or to read through it for new information. After you do the tutorial, we suggest reading Chapters 1 and 2 of the Information Access Server: Database Administration manual. These chapters will provide a detailed overview of the configuration process. When you've finished, return to this manual and use the information in Chapters 1 and 2 to plan your system, modify the installation if necessary, and configure Access Server to suit your needs. 3. Planning Your Configuration. In this stage, you use the worksheets in this manual to gather information about PC users' data needs. Once the information is gathered, you need to analyze it to see if the default capacity of any of the datasets in the data dictionary should be adjusted. Then you and the System Manager decide on the allocation of system resources for Access Server, such as the disc space that can be used for saved tables. For a discussion of the planning process, see Chapter 1 of this manual. 4. Adjusting the data dictionary, if necessary. Once you've determined what needs to be configured, you'll know whether you need to raise or lower the default capacities of any of the datasets in the data dictionary. Changes can also be made, if you like, to the database passwords in the schema files for HDPDIC and HDPENV, the two IMAGE databases that comprise the data dictionary. For instructions on how to modify the data dictionary, see the beginning of Chapter 2. If necessary, you can consult Appendix A in the Information Access Server: Database Administration manual for the structure, size, rules, and schemas for the HDPDIC and HDPENV databases. 5. Configuring Access Server. In this stage, you take the completed worksheets and use the Administrator Utility to configure Access Server. Configuration involves adding entries to the data dictionary that define remote systems (if any), data sources, tables, access groups, users, and table and item security. If you have Dictionary/3000, you may want to use the Translator Utility to take information from Dictionary/3000 data dictionaries and add the corresponding IMAGE database and IMAGE table definitions to the Information Access data dictionary. For the configuration steps, see Chapter 2 of this manual. More detailed information on configuration can be found in the Information Access Server: Database Administration manual. Securing the Administrator Utility (Primary DBA Only) After Access Server has been installed, there are four security measures you (the primary DBA) should take before beginning the configuration process or learning the tutorial in the Information Access Server: Learning the Administrator Utility manual. You should make Access Server unavailable to users, give the program file ADMIN a lockword, give the primary DBA a password, and give the user OPERATOR a password. The instructions on the following pages guide you through this process. Making Access Server Unavailable --------------------------------------------------------------------------------------------- | | | | What You Do | What Happens | | | | --------------------------------------------------------------------------------------------- | | | | After installation, Access Server is | All users are prevented from using Access | | available for use to users. Before making | Server until you use the UDC command | | configuration changes, you should make it | ENABLEAC (or run the same program with | | unavailable to other users. | PARM=1). | | | | | 1. Use the UDC command DISABLEAC, or type | Any currently active users are terminated. | | RUN ADMIN.PPC.SYS;PARM=2; INFO="ADMIN" and | | | press Return. | | | | | --------------------------------------------------------------------------------------------- Giving File ADMIN a Lockword --------------------------------------------------------------------------------------------- | | | | What You Do | What Happens | | | | --------------------------------------------------------------------------------------------- | | | | At this point, we recommend protecting the | | | program file ADMIN by giving it a lockword. | | | This will prevent anyone who doesn't know | | | the lockword from running the Administrator | | | Utility or turning Access Server on and | | | off. | | | | | | 2. If you're not already logged on to the | You're logged on to PPC.SYS. | | group and account PPC.SYS, type HELLO | | | MANAGER.SYS,PPC at the MPE prompt and press | | | Return. Provide passwords for user, group, | | | and account, as required. | | | | | --------------------------------------------------------------------------------------------- | | | | 3. At the MPE prompt, type RENAME | The program file ADMIN now has the lockword | | ADMIN,ADMIN/lockword (where lockword is the | you've given it. Anyone running ADMIN will | | lockword you want the file to have), then | be prompted for the lockword before the | | press Return. | request to run is granted. | | | | --------------------------------------------------------------------------------------------- Giving the Primary DBA a Password --------------------------------------------------------------------------------------------- | | | | What You Do | What Happens | | | | --------------------------------------------------------------------------------------------- | | | | When Access Server is first installed, the | | | primary DBA is defined as user ADMIN with a | | | password that is a string of spaces. So | | | the next thing you should do is to enter | | | the Administrator Utility and give yourself | | | (user ADMIN) a password. Thereafter, | | | anyone will need to provide a password to | | | get beyond the Entry screen for the | | | Administrator Utility or the Translator | | | Utility. | | | | | | Secondary DBAs can be given passwords when | | | they are configured as users and given DBA | | | capability. See "Phase J" in Chapter 2. | | | | | | Once secondary DBAs have been defined, they | | | use their own user name and password to | | | access the two utilities. | | | | | --------------------------------------------------------------------------------------------- | | | | 4. Run the Administrator Utility, either | The Entry screen appears. | | by using the UDC command ADMIN, or by | | | typing RUN ADMIN.PPC.SYS and pressing | | | Return. | | | | | | If you've added a lockword to the file, | | | you'll be prompted for it. Type it in and | | | press Return. | | | | | --------------------------------------------------------------------------------------------- | | | | 5. Type ADMIN in the User field and press | The Administrator Utility Main Menu | | Enter. | appears. | | | | --------------------------------------------------------------------------------------------- | | | | You enter a password for user ADMIN at the | | | Change User screen. Go there in three | | | steps: | | | | | | 6. Choose Config f1. | The Configuration Main Menu appears. | | | | | Choose Users f4. | The User Menu appears. | | | | | Choose Change User f2. | The Change User screen appears. | | | | --------------------------------------------------------------------------------------------- | | | | 7. Type ADMIN in the User field and press | The Change User screen displays the current | | Enter. | user definition for the user ADMIN. | | | | --------------------------------------------------------------------------------------------- Table Front-0. (cont.) --------------------------------------------------------------------------------------------- | | | | What You Do | What Happens | | | | --------------------------------------------------------------------------------------------- | | | | 8. Type a password in the User Password | | | field. | | | | | | The password must begin with an alphabetic | | | character, followed by alphanumeric | | | characters and/or hyphens in any | | | combination. | | | | | | Upper and lower case are significant in the | | | password. | | | | | | Press Enter. | The requested change is made in the data | | | dictionary. | | | | | Once you have a password as the primary | | | DBA, you or your System Manager can modify | | | the commands ENABLEAC and DISABLEAC in the | | | UDC file (ACUDC.PPCUTIL.HPOFFICE) to | | | include ;INFO="ADMIN/password" if you want. | | | If you don't want to include the password | | | in the UDCs, you will be prompted for them | | | when you run the Administrator Utility. | | | | | - - | | | | 9. If you want to change the configuration | | | for OPERATOR, go on to 10. If not, go to | | | 14. | | | | | --------------------------------------------------------------------------------------------- Giving User OPERATOR a New Password --------------------------------------------------------------------------------------------- | | | | What You Do | What Happens | | | | --------------------------------------------------------------------------------------------- | | | | When Access Server is first installed, the | | | user OPERATOR's password is OPERATOR. This | | | allows a system operator to enable or | | | disable the system, but not to gain access | | | to Access Server. After the initial | | | startup, you can change the password for | | | OPERATOR. Thereafter, anyone other than a | | | primary DBA will need to provide this | | | password to enable or disable the system. | | | | | | 10. Type OPERATOR in the User field and | The Administrator Utility Main Menu | | press Enter. | appears. | | | | --------------------------------------------------------------------------------------------- | | | | You enter a password for user OPERATOR at | | | the Change User screen. Go there in three | | | steps: | | | | | | 11. Choose Config f1. | The Configuration Main Menu appears. | | | | | Choose Users f4. | The User Menu appears. | | | | | Choose Change User f2. | The Change User screen appears. | | | | --------------------------------------------------------------------------------------------- | | | | 12. Type OPERATOR in the User field and | The Change User screen displays the current | | press Enter. | user definition for the user OPERATOR. | | | | --------------------------------------------------------------------------------------------- | | | | 13. Type a password in the User Password | | | field. | | | | | | The password must begin with an alphabetic | | | character, followed by alphanumeric | | | characters and/or hyphens in any | | | combination. | | | | | | Upper and lower case are significant in the | | | password. | | | | | | Press Enter. | The requested change is made in the data | | | dictionary. | | | | --------------------------------------------------------------------------------------------- Table Front-0. (cont.) --------------------------------------------------------------------------------------------- | | | | What You Do | What Happens | | | | --------------------------------------------------------------------------------------------- | | | | 14. Choose Done f8 to return to the User | The User Menu appears. | | Menu. | | | | | | Choose Done f8 to return to the | The Configuration Main Menu appears. | | Configuration Main Menu. | | | | | | Choose Done f8 to return to the | The Administrator Utility Main Menu | | Administrator Utility Main Menu. | appears. | | | | | Choose Exit ADMIN f8 to exit from the | The Administrator Utility completes its | | utility. | operation and the MPE prompt returns. | | | | ---------------------------------------------------------------------------------------------
NOTE We recommend, at this point, that you take the tutorial in the Information Access Server: Learning the Administrator Utility manual before going on with the rest of this manual. When you've finished the tutorial, read Chapters 1 and 2 of the Information Access Server: Database Administration manual. These chapters will provide a detailed overview of the configuration process outlined in the remainder of this manual. When you finished the tutorial and the two chapters recommended, return to this manual and go on to Chapters 1 and 2.
![[]](../../pic3k/M012041/FFN23c50.gif)