International Technical Support Organization Database Systems ...

3.2.3 RDS Parameters
RDB Name
Like any other sessions between intelligent partners, each DRDA partner has a
name that is unique in the network. This name is called the RDB name. The
definition of this name varies from platform to platform. The RDB name is used
as the first qualifier of a three-part name for each relational object (for example,
DB2CENTDIST.PROD.ORG). When an RDBMS is not exchanging data with
another RDBMS, the RDB name is not very important. But if you want to
exchange data, you need to define the RDB name and the partner RDB name.
Partner RDB Name
The partner RDB name identifies the name of the other RDBMS in a DRDA
network. This parameter includes an RDB name and an SNA partner LU name.
This SNA partner LU name is required to indicate to the system where the
partner can be found.
Transaction Program Prefix
The transaction program prefix is a 1-byte character prefixed to the transaction
program name. The default value is ′07′ in hexadecimal representation.
Transaction Program Name
The transaction program name (TPN) is the name of the transaction program
that processes the DRDA request on the target host. You should use the default
value of 6DB for all DRDA hosts except VM.
Remote Data Services is an OS/2 Database Manager private protocol that
enables OS/2 Database Manager clients and servers to access remote OS/2
Database Manager servers. Two logical connection protocols can be used to
connect the machines:
• LU 6.2
• NETBIOS.
36 DataHub Implementation and Connectivity
If you use the LU 6.2 protocol, both client and server workstations will need to be
defined in the SNA network as discussed in 3.2.1, “SNA Parameters” on
page 33. Although you do have a choice of protocols to connect OS/2 Database
Manager clients and servers to OS/2 Database Manager servers, the DataHub
implementation requires the use of the LU 6.2 protocol between the DataHub/2
workstation(s) and the managed OS/2 hosts.
If you use the NETBIOS protocol, each OS/2 Database Manager client and server
workstation must be assigned a name by the installer. Because this name must
be unique in the NETBIOS network, OS/2 Database Manager adds a prefix ($SQL
for a server and #SQL for a requester) and a suffix (00) to the workstation name.
Workstation Name
When an OS/2 Database Manager client or server wants to start a NETBIOS
session with an OS/2 Database Manager server, the requester must provide the
name of the server. This name is broadcast on the NETBIOS network.
Eventually, the server, which is always listening, acknowledges the request and
tells the requester which token-ring address to use. If the server is not up for
any reason, the local NETBIOS driver code sends a NETBIOS error code of 14
(unknown name) to the requester.