HP 3000 Manuals HP 3000 Manuals
SQL.INI File
When you install PC API, the installed copy of the SQL.INI file contains
a router section delimited by the section [ALLBASE]. You store the
connection information for all available DBEnvironments and valid
ALLBASE/SQL users under the [ALLBASE] section.
Following is a sample SQL.INI file:
; sqlbase initialization file
[ALLBASE]
mpedbname=server1,hp3000:data.pub.myacct,ip
mpedbname=server2,hp3000:mfg.pub.prod,ip
mpedbname=demo,demopc,source:ps.ps.p,ip
mpeuser=user3,pcuser3,who.myacct/?
mpeuser=user2,pcuser2,who.myacct/?
mpeuser=user1,pcuser1,who.myacct/?
mpeuser=sysadm,user1/userpass.acct/acctpass
Using Other Routers
You should have only one copy of the SQL.INI file on each PC client, even
if you are using other routers besides the ALLBASE Router. The SQL.INI
file can describe several routers, any of which may be active at a given
time. The [winclient.dll] section of the SQL.INI file identifies routers
to various databases. In the following example, the first two routers,
ALLBASE/SQL and Gupta SQLBase, are active:
[winclient.dll]
comdll=sqlawin
comdll=sqldbw
;comdll=sqlowin
;comdll=sqlnbiow
The last two lines are commented out and can be deleted.
Additional sections can be appended to the SQL.INI file as you install
additional routers. For example, SQLBase has connection string
information under a [sqldemo] section.
ALLBASE Connection String Syntax
After changing the SQL.INI file, if PC API is running, you need to reset
SQL.INI by clicking once on the PC API icon and selecting Close from the
menu.
The complete syntax for the SQL.INI [ALLBASE] entry is as follows:
mpedbname=DBCode,NodeName:DBEName[,NetworkType][,ConvertFlag]
mpeuser=UserCode,LogonString
where
mpedbname is the keyword that maps DBCode to NodeName and
DBEnvironmentName. Each DBEnvironment you wish to
connect to must be defined by the mpedbname. For
more information, refer to the section "Executing
VIEWS.SCP for Multiple DBEnvironments" later in
this chapter.
DBCode is the database code passed by the application
software to PC API. It can be up to eight bytes
long. The default database code used by the Views
Script is server1. When you install PC API use
server1. This database code references the next
two fields:
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]]
Unless you 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 communications software residing
on the PC that is to be used to communicate with
the server. You can optionally specify three
different values for NetworkType:
nw directs PC API to use NetWare
sk directs PC API to use sockets (HP ARPA 2.1)
ip directs PC API to use NetIPC (HP Network
Services 2.1)
Typically, you specify NetworkType only when you
have more than one type of supported data
communications software loaded on the client.
Enter the NetworkType in lower case.
The default order that PC API uses to search for
data communications software is shown in the above
list. For example, suppose you have both NetWare
and NetIPC loaded on your PC client. Using the
default search order, PC API always attempts to use
NetWare to communicate with the database server.
In order to direct PC API to use NetIPC rather than
NetWare, you need to override this default by
specifying a NetworkType of ip.
__________________________________________________
NOTE If you specify nw, NetWare/XL must be running
on the database server.
__________________________________________________
ConvertFlag turns conversion on.
an 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.
r8 is the default. There is no conversion.
For more information, refer to the section "Using
the ANSI Character Set" later in this chapter.
mpeuser is the entry name that maps the UserCode to the
logon string for the user.
UserCode is the user code passed by the application
software. The default user code name is sysadm and
is used by Views Script during installation. The
user code references the logon string:
LogonString is the MPE/iX logon. The syntax for LogonString
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 creating
the system catalog views (to
be owned by SYSSQL) in the
final step of the
installation.
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.
Refer to the manual Using the 900 Series HP 3000:
Fundamental Skills for a complete explanation of
the logon string, and the account structure.
Adding a New DBEnvironment Name
To add a new DBEnvironment name, add an mpedbname entry to the SQL.INI
file, under the [ALLBASE] section, as described in the "ALLBASE
Connection String Syntax" section in this chapter. Each DBEnvironment
needs a set of SYSSQL views. To add the SYSSQL views, use the Views
Script.
Adding a New User Logon
To add a new user logon, add an mpeuser entry to the SQL.INI file under
the [ALLBASE] section in the SQL.INI file.
Improving Performance
You may not need all the information contained in the SQL.INI file. You
can reduce the file to include only the following sections:
* dbrouter
* dbwindow
* sqlrtrw
* winclient.dll
* dbdfault
* winservr
* ALLBASE