HP 3000 Manuals HP 3000 Manuals
Install PC API on the PC Client
After you have prepared the database server and PC client for
installation, follow these steps:
* Setup PC API.
* Edit the AUTOEXEC.BAT file.
* 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.
Setup PC API
To setup PC API, you must be running Microsoft Windows. Follow these
steps:
1. Insert the HP ALLBASE/SQL PC API Setup Disk into drive A: (or
other desired drive).
2. From the Program Manager, choose the File Run command. In the
Command Line box, type a:\setup.
3. Click the OK button.
Edit the AUTOEXEC.BAT File
1. Use the editor of your choice to edit the path command in your
AUTOEXEC.BAT file. The path points to the drive and directory
where the PC API files are installed.
Insert the drive and directory for PC API before the application
software in the path statement. The following example shows a
path statement containing the drive and directory for PC API, the
directory for the application software, and the directory for LAN
Manager 1.2:
path c:\allbase;c:\;c:\gupta;c:\3open\doswksta\lanman\netprog;
The example above shows the HP LAN 1.X directory; it is different
for MS LAN 2.X.
2. Reboot your PC.
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.
Find the [ALLBASE] section in the SQL.INI file and use the editor of your
choice to update the following entry, supplying the appropriate variable
names which you wrote down in the "Gather Information" section earlier in
this chapter:
[ALLBASE]
mpedbname=server1,NodeName:DBEName[,NetWorkType][,ConvertFlag]
mpeuser=sysadm,LogonString
[ALLBASE] is the section header and identifies the router
type. There must be only one entry for each router
in the SQL.INI file. Include the square brackets.
mpedbname is the keyword that maps server1, the database
code, to the NodeName and DBEnvironmentName.
server1 is the default database code used by the Views
Script (described later in this chapter) during
installation.
NodeName is the node name of the database server. This is a
character string containing up to 8 characters.
DBEName is the name of the DBEnvironment containing one or
more databases. The syntax for the fully qualified
DBEName is:
DBEName[.Group[.Account]]
The brackets in the syntax indicate that the group
and account are optional. If you do not specify a
group and account name, ALLBASE/SQL assumes the
name is relative to the group and account specified
in the logon. Refer to the "Logical Design"
chapter of the ALLBASE/SQL Database Administration
Guide for more information about the DBEnvironment.
NetworkType specifies the data communication software on the PC
client and is used only when you have more than one
type of supported data communications software
loaded on the client. This is an optional
parameter. Refer to the complete syntax in the
chapter "Maintaining PC API."
ConvertFlag converts the ROMAN8 character set to the ANSI
character set on the PC client and then converts
the data to ROMAN8 when returned to the database
server. This is an optional parameter. Refer to
the complete syntax in the chapter "Maintaining PC
API."
mpeuser identifies the user installing PC API.
sysadm is the default user code used by Views Script
(described later in this chapter) during
installation.
LogonString is the logon of the user installing the SYSSQL
views used in the final step of the installation.
The complete syntax is:
[SessionId],User[/UserPass].Account[/AcctPass][,Group[/GrpPass]]
SessionId is the name that identifies
the current MPE/iX session.
Although optional, it is
recommended that you use
SessionId to enable unique
tracking of each session on
the MPE/iX system.
User is the MPE/iX user name.
UserPass is the optional user
password. You can use a ?
as a placeholder. The ?
placeholder causes a dialog
box to appear on the screen
when the logon string is
validated. The user then
enters the password into the
dialog box.
Account is the MPE/iX user account.
AcctPass is the optional account
password. You can use a ?
as a placeholder. The ?
placeholder causes a dialog
box to appear on the screen
when the logon string is
validated. The user then
enters the password into the
dialog box.
Group is the optional group name
associated with the account
name.
GrpPass is the optional group
password. You can use a ?
as a placeholder. The ?
placeholder causes a dialog
box to appear on the screen
when the logon string is
validated. The user then
enters the password into the
dialog box.
NOTE Use the 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. Refer to the chapter "Maintaining PC API" for more
information about the SQL.INI file.
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. 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 View Script each time you set up a DBEnvironment for use with PC
API.
Start Scriptor from the Windows Program Manager by double clicking on the
Scriptor icon.
When you start Scriptor, the Scriptor Dialog Box appears on your screen,
as shown in Figure 2-2 .
![[]](../../pic3k/M012150/FFN53c50.gif)
Figure 2-2. Scriptor Dialog Box
Execute the Verify Script.
The VERIFY.SCP file is installed with PC API. This script connects and
then disconnects to the ALLBASE/SQL DBEnvironment to check that the
installation has been successful up to this point.
To execute this script, enter verify.scp in the Path/Script Filename
field and click on Execute, or press Enter as shown in Figure 2-3 :
![[]](../../pic3k/M012150/FFN63c50.gif)
Figure 2-3. 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. After
the Verify 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 *.
The PC API icon appears when a 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
from the PC Client" 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 tables
normally used by Gupta C/API 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, "SYSSQL System
Catalog Views" in the chapter "Maintaining PC API."
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 2-4 :
![[]](../../pic3k/M012150/FFN73c50.gif)
Figure 2-4. 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 "SYSSQL System
Catalog Views" in the chapter "Maintaining PC API."
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" in the "Maintaining PC
API" 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.