HP 3000 Manuals

HP PC API User's Guide for ALLBASE/SQL and IMAGE/SQL

Configuring the Gupta Interface 

After you have prepared the database server and PC client and installed
PC API, follow these steps to configure PC API for the Gupta interface.

   *   Edit the SQL.INI file.

   *   Check for duplicate files in other directories.

   *   Use Scriptor to verify the connection and create the views.

   *   Test the application software.

The above steps are explained in this section.  When you have completed
these steps, you are ready to run your application software.

Edit the SQL.INI File 

Each PC client has one copy of the PC API SQL.INI file.  This file was
added to the installation directory when you installed PC API. Entries in
the file provide router and connection string information to the
application software.

Use the editor of your choice and find the [ALLBASE] section in the
SQL.INI file.  Remove the semicolons at the beginning of the entries for
mpedbname and mpeuser.  Update the ALLBASE connection string entry,
supplying the appropriate variable names which you wrote down in the
"Gather Information" section in the "Getting Started" chapter.  Refer to
the ALLBASE Connection String Syntax later in this chapter in the section
"Maintaining the SQL.INI File." 


NOTE  Use the SQL.INI default code names server1 and sysadm.  These codes
      are referenced by scripts later in the installation.  After
      installation, you can change these code names.


You can add more users and DBEnvironments to the SQL.INI file in a
similar fashion.

After changing the SQL.INI file, you need to restart PC API if it is
currently running.  To do this, click once on the HP DB Router icon and
select Close from the menu.


NOTE  To specify a connection string for the HP 9000, refer to the HP PC 
      API User's Guide for ALLBASE/SQL.


Check for Duplicate Files in Other Directories 

Applications, other than PC API, may have their own SQL.INI files.
Ensure that the PC API SQL.INI file and the SQLAPIW.DLL file appear only
in the ALLBASE directory.  To avoid conflict, rename any others.

Use Scriptor to Verify the Connection and Create Views 

Scriptor and the two scripts below are installed with PC API. After
modifying the SQL.INI file, use Scriptor to execute these two scripts:

   *   VERIFY.SCP (Verify Script)

   *   VIEWS.SCP (Views Script)

After the installation is complete, you will continue to use Scriptor to
run the Views Script each time you set up a DBEnvironment for use with PC
API.

Start Scriptor from the PC API program group by double clicking on the
Scriptor icon.

When you start Scriptor, the Scriptor dialog box appears on your screen,
as shown in Figure 3-1 .


          Figure 3-1.  Scriptor Dialog Box 

Execute the Verify Script.     

The VERIFY.SCP file is installed with PC API. This script checks that the
installation has been successful.  It connects to the ALLBASE/SQL
DBEnvironment, executes a SELECT statement, then disconnects.

To execute this script, enter verify.scp in the Path/Script Filename
field and click on Execute, or press Enter as shown in Figure 3-2 .


          Figure 3-2.  Executing Verify Script 

As the Verify Script runs, it is echoed in the View Window on the bottom
half of the screen along with any error messages it may encounter.  The
HP DB Router icon appears when a first connection is attempted.

If you have error messages, note the error, click on Exit to leave the
Scriptor dialog box, and return to MS-DOS to fix the errors before
continuing on to the next step.  Refer to the appendix "Error Messages"
for a list of errors and suggestions for fixing them.

To execute Verify Script again, run Scriptor and enter verify.scp in the
Path/Script Filename field.

When Verify Script has successfully completed, do not exit from the
Scriptor dialog box; execute Views Script.

Execute the Views Script.     

The VIEWS.SCP file is installed with PC API. The Views Script installs
the SYSSQL views in the DBEnvironment.  These views map the ALLBASE/SQL
system catalog tables to the server-independent system catalog views
normally used by Gupta interface applications.  Views Script also grants
public access to the system catalog views that it installs.  For more
information about the SYSSQL views, refer to the section, "Understanding
SYSSQL System Catalog Views" later in this chapter.


NOTE  The mpeuser (sysadm), specified in the SQL.INI file, must have DBA
      authority to use Views Script.


To execute this script, enter views.scp in the Path/Script Filename field
and click on Execute, or press Enter as shown in Figure 3-3 .


          Figure 3-3.  Executing Views Script 

As described with the Verify Script, the Views Script is echoed in the
View Window at the bottom of the screen.  After the Views Script has
finished, you can scroll up to see any error messages.  Click on and hold
down the scroll button to move back through the output to see if the
connection was successful.  Comments, which provide useful information,
are preceded by a *.

Alternatively, you can install the SYSSQL views on the database server
with ALLBASE/SQL Interactive Stuctured Query Language (ISQL). For
information on using this method, refer to the section "Understanding
SYSSQL System Catalog Views" later in this chapter.

If you need to run the Views Script a second time, remove the first set
of views with the UNVIEWS.SCP script using Scriptor or execute the
UNVIEWS.SQL command file from ISQL. For information on using ISQL to do
this, refer to the section "ISQL and SYSSQL Views" later in this chapter.

Test the Application Software 

You are now ready to test your application software.  Change the path in
your AUTOEXEC.BAT file to include the directory of your application
software after the C:\ALLBASE directory.  Follow the instructions
provided with the installed application software for testing the product.

MPE/iX 5.0 Documentation