HP 3000 Manuals HP 3000 Manuals
Prepare the Database Server If you haven't done so already, review the software and hardware requirements for both client and server environments in the "System Requirements" section in the "Getting Started" chapter.
NOTE You must have DBA authority for the DBEnvironment to complete the installation of PC API. The creator of a DBEnvironment automatically has DBA authority and can grant DBA authority to others. Refer to the ALLBASE/SQL Database Administration Guide for information about DBA authority.
Before you install PC API on the PC client, do the following on the database server: * Verify that supporting software is running. * Gather information. * Create the DBEnvironment. Verify That Supporting Software Is Running Check that the correct software is installed and then start the network. 1. Verify that you have the correct supporting software. Review the "Getting Started" chapter. If you do not have the correct software, there are two ways that you can order the supporting software for PC API: a. With a new HP 3000 If your HP 3000 is a 9X7, 9X7LX, or 99X and you selected the Preload Option, then all of the required supporting HP 3000 software has been preloaded. No installation is required. However, you must configure the system and the network. If your HP 3000 is not a 9X7 or 9X7LX, or 99X all of the required supporting HP 3000 software is shipped on the SLT, FOS, and subsystem tapes accompanying your system. b. As an add-on or update to an existing HP 3000 Series 900 If the supporting software for PC API was ordered with a system update, or as an add-on to an existing sytem, follow the instructions in the installation guides shipped with your updates. _________________________________________________________________ NOTE You do not need to configure the ALLBASE/NET AliasDB files or NetUsers files to use PC API. _________________________________________________________________ 2. Prepare the database server to run jobs. a. Check that the spooler is started and STREAMS is enabled. These commands should be in the SYSSTART file. b. Set the job limit to a level that will accomodate the normal number of batch jobs plus the number of concurrent PC API connections. For example: : JOBFENCE JobInputPriority : LIMIT #OfJobs, #OfSessions You may need to use SYSGEN to set the job limit high enough. 3. Start the network and the listener process on the database server. There are two listeners for PC API. Both the listeners can be active at the same time. Each listener has a different process to activate it. Follow the steps for the listener you are using. a. NS Listener. This listener works with NS3000/XL and ThinLAN 3000/XL data communications software and works with either NS or ARPA. When you start the network, NS Listener starts automatically when the first PC client application initiates a connection to ALLBASE/SQL on the server. To verify that NS Listener is running, type: :HELLO MANAGER.SYS :NSCONTROL STATUS If NS Listener is running, HPIP Listener is listed on the screen as one of the available services. When ThinLAN 3000/XL and ALLBASE/SQL were first installed, a job called JCONFJOB.NET.SYS was run. This job enabled the listener process to be started automatically by the first request. To verify that the JCONFJOB.NET.SYS has been run, type: : PRINT ALLMAST.NET.SYS Look for the entry: Remote Client/Server Allbase NetIPC Service (HPIP). For more information about JCONFJOB.NET.SYS, refer to the ThinLAN 3000/XL installation guide. b. NetWare Listener. This listener works with NetWare/XL and ThinLAN 3000/XL data communications software. When NetWare is active, a NetWare job should be running. If it is not running, refer to the NetWare/XL documentation. Titles and part numbers are listed at the front of this user's guide. After the NetWare/XL network has been started, you must start the NetWare Listener on the database server. You must have node manager (NM) capability to do this. To start the NetWare Listener, follow these steps: : HELLO MANAGER.SYS : NWSTART - NETWARE LISTENER HAS BEEN STARTED SUCCESSFULLY. To check that the NetWare Listener is running, type: : NWSTAT - NETWARE LISTENER ALREADY STARTED. To stop the NetWare Listener, type: : NWSTOP - NETWARE LISTENER HAS BEEN STOPPED. Ensure that users can use the NetWare/XL product. For more information, refer to the NetWare documentation accompanying the NetWare/XL product. Titles and part numbers are listed at the front of this guide. Gather Information When you install PC API on the PC client, you will need information about the database server environment. Now is a good time to note it. The database administrator will have information about the database. * Node name of the database server: (For example: DBSERVER) * Fully qualified name of the DBEnvironment on the server: (For example: PartsDBE.SomeGrp.SomeAcct) * Logon string used to connect to the DBEvironment: (For example: SomeUser/passwd.SomeAcct/AcctPass,SomeGrp/GrpPass) Create the DBEnvironment on the Database Server To enable a connection between a PC client and database server, you must set up an ALLBASE/SQL DBEnvironment. If you do not have an existing database for testing purposes, you can use the ALLBASE/SQL SQLSetup tool to create a DBEnvironment called PartsDBE. Follow these steps: 1. Logon to the group and account where you want to create the DBEnvironment. 2. From the command prompt, enter the following command: :SQLSETUP.SAMPLEDB.SYS A menu like the one in Figure 2-1 appears on your screen: ________________________________________________________________________________ | | | | | Options for Setting Up ALLBASE/SQL Sample DBEnvironments | | | | =============================================================== | | | | Choose one: | | | | 1. Create PartsDBE without sample programs | | 2. Create PartsDBE, copy, preprocess and compile sample programs | | 3. Copy, preprocess and compile sample programs only | | 4. Generate a schema for PartsDBE | | 5. Display schema for PartsDBE | | 6. Purge PartsDBE and sample programs | | 7. Help | | 0. Exit | | | | =============================================================== | | | | Enter your choice=> | | | ________________________________________________________________________________ Figure 2-1. SQLSetup Menu 3. Choose option 1 to create PartsDBE. This option creates the DBEnvironment, defines all of its tables, views, indexes, and security structure, and then loads it with data. As the system creates PartsDBE, you see several messages displayed. At the end of the creation process, you see the following message: Creation and Loading of PartsDBE is now complete! Press Return to continue... 4. Choose 0 to exit the menu. If you have designed your own database for testing purposes, you can consult your database administrator and complete the following tasks: 1. Plan the security structure of the DBEnvironment. Decide which users will be granted access to the DBEnvironment, databases within the DBEnvironment, and tables within the databases. 2. Create the account where the DBEnvironment is to reside. 3. Grant authorizations to users who will be using the test DBEnvironment. 4. Create the DBEnvironment, including databases and tables. After you setup the DBEnvironment, ensure that you can connect to it. For example, : HELLO mysession, SomeUser/passwd.SomeAcct/acctpass : isql isql=> CONNECT TO 'PartsDBE.SomeGrp.SomeAcct'; isql=> SELECT * FROM SYSTEM.TABLE; : At this point you should see the system table information. : U[p], d[own], l[eft], r[ight], t[op], b[ottom], pr[int] <n>, or e[nd] >e; isql=> exit; For a complete explanation of the procedures necessary to create the PartsDBE DBEnvironment, refer to the appendix "Sample DBEnvironment" in the ALLBASE/SQL Reference Manual.