home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Shareware 1 2 the Maxx
/
sw_1.zip
/
sw_1
/
TEXT
/
PDX_ALL.ZIP
/
TI598.ASC
< prev
next >
Wrap
Text File
|
1991-09-11
|
2KB
|
67 lines
PRODUCT : Paradox NUMBER : 598
VERSION : 1.0
OS : DOS
DATE : September 11, 1991 PAGE : 1/1
TITLE : CONNECTING TO VAX/VMS RDB V4.0
The access methods for VAX Rdb/VMS V4.0 have been modified to
increase the performance of VAX SQL/Services. These methods are
provided in three modes: 1. Explicit, 2. Proxy and, 3. Default.
When a VAX Rdb/VMS V4.0 client accesses a VAX Rdb/VMS V4.0
server, an explicit access method is used. To provide backward
compatibility and reliable connections between VAX Rdb/VMS V3.1B
clients and VAX Rdb/VMS V4.0 servers, the proxy access method
must be used.
For non-secure systems, the default access method is provided
for both VAX Rdb/VMS V3.1B clients and VAX Rdb/VMS 4.0 clients.
This provides access to the SQLSRV$SRV default account if the
default account has been enabled on the server.
Because Paradox SQL-Link operates as a V3.1B client, proxy access
must be created on the server.
Proxy access permits SQL-Link to access the server when the node
name is specified in a sqlsrv_associate routine call and an
entry exists for the incoming application request in the
SQLSRV$PROXY.DAT file. The proxy file resides in the
SYS$STARTUP directory on the server system. What needs to be
defined in the SQLSRV$PROXY.DAT file on the server is for all
users from a node to have access to the server. This is done by
defining access as follows in the SQLSRV$PROXY.DAT file on the
VAX Rdb/VMS V4.0 Server system:
ADD/PROXY REMOTE_NODENAME::REMOTE_USERNAME LOCAL_USERNAME
This allows user LOCAL_USERNAME to access REMOTE_NODENAME under
the proxy of REMOTE_USERNAME.
To initialize proxy access you must first shut down SQL/Services,
edit the SQLSRV$PROXY.DAT file as suggested above, then restart
SQL/Services.
For additional information, please refer to your VAX Rdb/V4.0
Accessing SQL/Services documentation.