Download HOBLink DRDA für Windows

HOBLink DRDA
for Windows
Manual
March 2006
HOB GmbH & Co. KG
Schwadermuehlstr. 3
D-90556 Cadolzburg
5
(00 49) 9103 / 715-161
(00 49) 9103 / 715-299
E-Mail: [email protected]
Table of Contents
1. Overview
5
1.1. HOBLink DRDA ............................................................................................................................5
1.2. Open Database Connectivity (ODBC) ..........................................................................................6
1.3. Distributed Relational Database Architecture (DRDA) .................................................................6
1.4. HOBLink DRDA and SQL .............................................................................................................6
2. System Requirements
7
3. Installing HOBLink DRDA
9
3.1. Overview .......................................................................................................................................9
3.2. Definitions on the Host................................................................................................................10
3.2.1. Entries in the Mode Table .................................................................................................11
3.2.2. MVS ..................................................................................................................................11
3.2.3. VSE ...................................................................................................................................13
3.2.4. VM .....................................................................................................................................13
3.3. OS/400 ........................................................................................................................................15
3.3.1. AIX on the RS/6000 ..........................................................................................................17
4. Configuring the Connection in the APPC Subsystem
19
4.1. Configuring IBM APPC Networking Services .............................................................................19
4.1.1. Step 1................................................................................................................................19
4.1.2. Step 2................................................................................................................................19
4.1.3. Step 3................................................................................................................................19
4.2. Configuring the Microsoft SNA Server........................................................................................20
4.2.1. Defining a Local LU...........................................................................................................20
4.2.2. Defining a Remote LU.......................................................................................................21
4.2.3. Assigning a Mode to a Partner LU....................................................................................21
4.2.4. Installing Client Software ..................................................................................................21
4.3. Configuring Novell Netware for SAA...........................................................................................22
5. Running the Setup Program
23
6. Batch-Installation
25
6.1. Recording the installation............................................................................................................25
6.2. Playing the installation ................................................................................................................25
7. Configuring HOBLink DRDA
27
7.1. Adding and Configuring a Data Source ......................................................................................27
7.1.1. Configuring a New Data Source .......................................................................................28
7.2. Changing an Existing Data Source.............................................................................................31
7.3. Deleting an Existing Data Source ...............................................................................................31
7.4. Binding HOBLink DRDA to the Database...................................................................................31
7.4.1. Executing the Bind Yourself..............................................................................................31
7.4.2. Using the Package of a Different User .............................................................................31
8. Supplementary Programs
33
8.1. The Program HOBBIND............................................................................................................. 33
8.2. The Program CODEPAGE......................................................................................................... 34
8.3. The Program HOBDBM ............................................................................................................. 35
SQL commands ......................................................................................................................... 36
HOBDBM commands................................................................................................................. 36
Glossary
39
Index
41
KW3/7/2006V4.1E
HOBLink DRDA ____________________________________________________________Overview
1. Overview
1.1. HOBLink DRDA
HOBLink DRDA allows you to run application programs (e.g. MS Excel, MS Access, MS Query and
FoxPro) that access host databases. The PC applications can run under Windows 32-bit. With Visual
Basic from Microsoft you can write your own application programs that access host databases via the
ODBC interface. HOBLink DRDA offers you a cost-effective, efficient means of accessing, viewing
and maintaining enterprise data stored on a remote host database right from your desktop PC.
After installing HOBLink DRDA you need no longer a local database on your PC, because the host
database becomes your data server.
When using HOBLink DRDA the network connection can take place over TCP/IP or APPC. In the
case of an APPC connection you will need software that establishes an APPC connection between
your PC and the host. For the sake of brevity, this software is referred to as an APPC Subsystem
throughout this manual. HOBLink DRDA supports the following APPC subsystems:
•
•
•
•
•
•
HOBLink SNA Stack
Microsoft SNA Server (Client on the PC)
Novell Netware for SAA
IBM Client Access/400 (and IBM APPC Networking Services, respectively)
IBM Personal Communications
IBM Communications Server
In case the connection happens over TCP/IP respectively TCP/IP for AnyNet a TCP/IP stack on the
client PC is necessary. TCP/IP is delivered by Windows95/98 and Windows NT; by Windows 3.11 you
have to buy additional a TCP/IP stack for example Microsoft TCP/IP for Windows 3.11.
Since it accesses databases via the ODBC interface, HOBLink DRDA supports numerous commercially available PC applications.
Seamless access to the following host databases is possible:
•
•
•
•
•
•
•
•
•
•
DB2 for MVS resp. OS/390
DB2/VSE (formerly SQL/DS)
DB2/VM (formerly SQL/DS)
DB2/400
OS/400 database files
DB2/AIX (UDB)
DB2/Windows NT (UDB)
DB2/2 (UDB)
DB2 for Linux
all other databases that correspond to the DRDA architecture
5
Overview ____________________________________________________________HOBLink DRDA
1.2. Open Database Connectivity (ODBC)
ODBC (Open DataBase Connectivity) is an interface that was developed by Microsoft in 1992. ODBC
allows an application program to access relational as well as non-relational database systems in a
heterogeneous environment. It not only allows you to access data, but also to view and to process it.
ODBC supports SQL, the standard query language for relational databases.
HOBLink DRDA provides an ODBC driver which enables access to host databases that correspond to
the DRDA architecture. The ODBC driver from HOB plays an intermediary role between the application program and the host software that guarantees the connection to the network.
1.3. Distributed Relational Database Architecture (DRDA)
HOBLink DRDA connects a database client with a host database system. To do this, HOBLink DRDA
uses the DRDA (Distributed Relational Database Architecture) transmission protocol which controls
access to databases in various environments.
1.4. HOBLink DRDA and SQL
SQL is a query language for relational databases that was developed by IBM and that is supported by
all relational SAA database systems. SQL allows the user to query and change data in an SAA environment. Any SQL commands that you enter to query your database are interpreted by the HOBLink
DRDA driver.
6
HOBLink DRDA _________________________________________________ System Requirements
2. System Requirements
Hardware:
• a PC with a 486 microprocessor or higher
• diskette drive respectively CD-Rom drive
Software:
•
•
•
•
•
Microsoft Windows 3.11or
Windows 95 or
Windows 98 or
Windows NT or
Windows 2000
If the connection takes place over APPC:
• An APPC subsystem that establishes a connection to an SNA environment. For example,
• HOBLink SNA Stack
• or:
IBM Client Access/400 for Windows (or IBM APPC Networking Services for Windows)
Please note: If the host communication is to be carried out via VTAM, then VTAM Version
4 Release 2 must be installed on the host. Older versions of VTAM are not supported.
• or:
Novell Netware for SAA, Version 2.00.30 or higher
• or:
Microsoft SNA Server (the client version must be installed on the PC)
The connection to AS/400 computers is carried out via the OS/400 operating system.
If the connection takes place over TCP/IP respectively TCP/IP Anynet:
• A subsystem that allows the network connection over TCP/IP (in Windows 95/98 an Windows
NT/2000 already included)
7
System Requirements __________________________________________________HOBLink DRDA
8
HOBLink DRDA _______________________________________________ Installing HOBLink DRDA
3. Installing HOBLink DRDA
3.1. Overview
In order to be able to access databases via HOBLink DRDA, you must carry out the following steps:
• Enter the necessary definitions on the host (refer to section „3.2 Definitions on the Host“; consult
the system administrator of the host system)
• Install an APPC subsystem respectively TCP/IP subsystem (only under Windows 3.1x) on your PC
• Configure the connection with the APPC subsystem (refer to Chapter „4 Configuring the Connection in the APPC Subsystem“ on page 16) respectively configure the TCP/IP connection
• Install HOBLink DRDA on your PC (refer to Chapter „5. Running the Setup Program“ on page 23)
• Bind HOBLink DRDA to the database (refer to section „7.4. Binding HOBLink DRDA to the Database “ on page 31)
• Configure the data source in the ODBC administator (System Configuration in Windows) (see
section „7.1. Adding and Configuring a Data Source“ on page 27)
9
Installing HOBLink DRDA _______________________________________________HOBLink DRDA
3.2. Definitions on the Host
This section describes the entries that the system administrator must make on the host, so that HOBLink DRDA will be able to access the host database.
All entries appearing in this chapter and marked by an encircled number, (cdefg), must also be
entered in an entry field on your PC. You will find the corresponding number in the chapter describing
the entries to be made on the PC.
The following meanings are associated with the numbers:
c
name of the file on the host that contains the logmodes
d
name of the modes used in the communication
e
local LU
f
partner LU
g
network ID
10
HOBLink DRDA _______________________________________________ Installing HOBLink DRDA
3.2.1. Entries in the Mode Table
Example: IBMRDB entry in a mode table:
MODTABHSc MODETAB
.
.
.
MODEENT LOGMODE=IBMRDBd,
AGW (SLU) TO AGW (PLU)
IBMRDBd
PSNDPAC=X’00’,
PRIMARY SEND PACING COUNT
SRCVPAC=X’02’,
SECONDARY RECEIVE PACING COUNT
SSNDPAC=X’02’,
SECONDARY SEND PACING COUNT
TYPE=0,
NEGOTIATED BIND
FMPROF=X’13’,
FM PROFILE 19 LU 6.2
TSPROF=X’07’,
TS PROFILE 7 LU 6.2
PRIPROT=X’B0’,
PRIMARY NAU PROTOCOL
SECPROT=X’B0’,
SECONDARY NAU PROTOCOL
RUSIZES=X’8989’
8 X 2**9 = 4096
COMPROT=X’78A5’,
COMMON NAU PROT
PSERVIC=X’0602000000000000122F00’
SYSMSG/Q MODEL
.
.
.
MODEEND
END
X
X
X
X
X
X
X
X
X
X
X
3.2.2. MVS
VTAM Definitions of PUs and LUs
1. Integrated Token-Ring-Adapter (Switched major node)
H9Z3PU
PU
H9Z3Xe
H9Z30
LU
LU
ADDR=09,
CPNAME=H9Z3Xe,
DISCNT=NO,
LANACK=(0,0),LANCON=(5,2),LANINACT=4.8,
LANRESP=(5,2),LANSDWDW=(7,1),LANSW=YES,
MAXDATA=2012,
MAXPATH=4,SAPADDR=4,
SSCPFM=USSSCS,USSTAB=USSTABHS,MODETAB=MODTABHSc,
PACING=0,
VPACING=0
LOCADDR=0
LOCADDR=0
2. 3174 Local SNA major node
H9Z3PU
PU
H9Z30
H9Z3Xe
LU
LU
CUADDR=511,
MAXBFRU=8,
XID=YES,
MODETAB=MODTABHSc,
DLOGMOD=D4C32782,
ISTATUS=ACTIVE,
USSTAB=USSTABHS
LOCADDR=00
LOCADDR=00
VTAM Definition of the application under MVS
11
Installing HOBLink DRDA _______________________________________________HOBLink DRDA
Under MVS, you must enter the application name in the VTAM definitions. The PC user must enter the
name of the application (in this case : DB2APPLf) as partner LU in the setup program of HOBLink
DRDA:
DB2APPLf APPL APPC=YES,
AUTH=(ACQ),
AUTOSES=1,
DMINWNL=25,
DMINWNR=25,
DSESLIM=50,
MODETAB=MODTABHSc,
SECACPT=ALREADYV,
SRBEXIT=YES,
VERIFY=NONE,
VPACING=2
If a dependent LU is used for the access to the MVS/DB2, the following VTAM command has to be
entered:
F NET,CNOS,ID=DB2APPL,LOGMODE=IBMRDB,LUNAME=H9Z3X,SNGSESLU=YES
DB2APPL
H9Z3X
is the name of the partner LU f
is the name of the dependent LU e.
Different LU 6.2 logmodes can be used. The logmode has to correspond with the logmode d entered
in the HOBLink DRDA Setup.
12
HOBLink DRDA _______________________________________________ Installing HOBLink DRDA
3.2.3. VSE
VTAM Definitions of PUs and LUs
1. Integrated Token-Ring-Adapter (Switched major node)
H9Z3PU
PU
H9Z3Xe
H9Z30
LU
LU
ADDR=09,
CPNAME=H9Z3Xe,
DISCNT=NO,
LANACK=(0,0),LANCON=(5,2),LANINACT=4.8,
LANRESP=(5,2),LANSDWDW=(7,1),LANSW=YES,
MAXDATA=2012,
MAXPATH=4,SAPADDR=4,
SSCPFM=USSSCS,USSTAB=USSTABHS,MODETAB=MODTABHSc,
PACING=0,
VPACING=0
LOCADDR=0
LOCADDR=0
2. 3174 Local SNA major node
H9Z3PU
PU
H9Z30
H9Z3Xe
LU
LU
CUADDR=511,
MAXBFRU=8,
XID=YES,
MODETAB=MODTABHSc,
DLOGMOD=D4C32782,
ISTATUS=ACTIVE,
USSTAB=USSTABHS
LOCADDR=00
LOCADDR=00
3.2.4. VM
In VM you must likewise make the appropriate PU and LU definitions in VTAM (see the previous section). In addition, you must also enter an application in the VTAM definition, as well as entering a command in AVS:
VTAM Definition of an Application under VM
DB2APPLf APPL
APPC=YES,
AUTHEXIT=YES,
AUTOSES=10,
DSESLIM=100,
DMINWNL=50,
DMINWNR=50,
MODETAB=MODTABHSc,
PARSESS=YES,
SYNCLVL=CONFIRM,
SECACPT=ALREADYV,
VERIFY=NONE
13
Installing HOBLink DRDA _______________________________________________HOBLink DRDA
Command in AVS
The following command serves to activate a virtual gateway named „DB2APPLf “:
Example:
ACTIVATE GATEWAY DB2APPLf GLOBAL
The gateway name (in this example DB2APPLf) must also be entered by the PC user in the „Partner
LU name“ field of HOBLink DRDA.
14
HOBLink DRDA _______________________________________________ Installing HOBLink DRDA
3.3. OS/400
The OS/400 operating system contains a database system (integrated file system) which can create
database files. HOBLink DRDA can access both, OS/400 database file and DB2/400 databases. All
configurations on the PC site are equal for both manners of database access.
In the performance description, „Create automatically“ must be activated. The operating system will
then automatically create the communication controller and control unit descriptions, whenever the PC
user establishes a remote data connection via HOBLink DRDA to Client Access/400 for Windows. The
following contains an example of a communication controller and control unit definition:
• Controller Definition:
Communication description
. . . :
Choice
. . . . . . . . . . . . . :
Controller Category
. . . . . . :
H9Z3Xe
*BASIC
*APPC
Link type
. . . . .
Append at IPL
. . . . .
Character code
. . . . .
Maximum frame size
. . .
:
:
:
:
*LAN
*NO
*EBCDIC
16393
. . . . . . . . :
BRANDg
Remote network ID
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Remote control point . . . . . . . :
Connection initialization. . . . . :
Dial initialization . . . . . . . :
Disconnect switched lines . . . . :
Data connection role
. . . . . :
Remote LAN adapter address
. . . :
LAN-DSAP . . . . . . . . . . . . . :
H9Z3Xe
*DIAL
*LINKTYPE
*YES
*NEG
400000001FEA
04
---------------------Switched Lines--------------------LINTRN1
---------------------Connected Units---------------H9Z3X
APPN capability . . . . . . . . . :
*YES
APPN CP session support
. . :
*YES
APPN node type . . . . . . . . . . :
*CALC
APPN/HPR capability . . . . . . . :
*YES
APPN-transmission group number . . :
*CALC
Min. APPN switched status. . . . . :
*VRYONPND
Automatically delete unit
. . . :
1440
User defined 1
. . . . . . . :
*LIND
User defined 2
. . . . . . . :
*LIND
User defined 3
. . . . . . . :
*LIND
Model control unit
. . :
*NO
Owner of Control unit
. . . . . :
*SYS
Interrupt timer:
Minimum connection timer
. . :
170
Interrupt-delay timer
. . :
0
LAN frame repetition
. . . . . . :
*CALC
LAN connection repetition
. . . :
*CALC
LAN reply timer
. . . . . . . :
*CALC
LAN connection timer
. . . . . :
*CALC
LAN confirmation timer
. . . . :
*CALC
LAN inactivity timer
. . . . :
*CALC
LAN confirmation frequency . . . . :
*CALC
LAN max. unconfirmed frames . . . :
*CALC
LAN access priority
. . . . . . :
*CALC
15
Installing HOBLink DRDA _______________________________________________HOBLink DRDA
• Device Definition:
:
:
:
:
H9Z3Xe
*BASIC
*APPC
YES
. . . . . . . . . :
. . . . . . . . . :
H9Z3Xe
*NO
Device definition . . . .
Choise
. . . . . . . . .
Device category
. .
Automatic dreate
. . .
Remote location
Append at IPL
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Local location
. . . . . . . . . :
Remote Network ID . . . . . . . . :
DB2APPLf
*NETATR
Connected control unit
. . . :
H9Z3Xe
Message queue
. . . . . :
QSYSOPR
Library
. . . . . . . . . . . :
*LIBL
Local location address . . . . . . :
00
APPN capability . . . . . . . . . :
*YES
Single session:
single session capability
. . . :
*NO
Control unit description . . . . . :
H9Z3X
Mode
. . . . . . . . . . . . . :
*MODE
Unit category
. . . . . . . . :
*APPC
-------------------------Mode------------------------*NETATR
For the database access is besides the following input necessary. A detailed direction you´ll find in the
IBM “Application System/400 Systems Applicataion Architecture Structured Query Language/400 Programmer´s Guide” (SC41-9609-03).
The system administrator (QSECOFR) of the DB2/400 database must enter the following SQL commands, to enable a user to access the database:
• Directory Entry
In order to be able to start the Query Manager, you must first make an entry in a local directory.
The command
ADDRDBDIRE
creates a local entry with a database name of your choice. The name you choose here is to be entered as the target database in the ODBC setup (see section „6.1 Adding and Configuring the Data
Source“). The existing entries can be shown by entering the following command:
DSPRDBDIRE
• Starting SQL
Use the following command to start the SQL interpreter:
STRSQL
• Creating a Collection
Example:
CREATE COLLECTION <COLL_ID>
<COLL_ID> is the name of the collection-ID that is entered in the configuration of HOBLink DRDA in
the bind options.
If there is nothing entered so it is the user ID the user uses for announcing to the data
base.
16
HOBLink DRDA _______________________________________________ Installing HOBLink DRDA
Subsequently, exit the SQL interpreter.
• Defining (Granting) Access for a User
The user must be assigned an authorization of „CHANGE“ or higher in the COLLECTION ID.
Example:
GRTOBJAUT OBJ(QSYS/COLL_ID) OBJTYPE(*LIB) USER(<USER_ID>) AUT(*ALL)
<USER_ID> this is the user’s name
<COLL_ID> is the name of the collection-ID that is entered in the configuration of HOBLink DRDA in
the bind options.
If there is nothing entered so it is the user ID the user uses for announcing to the data
base.
Changing the Standard Parameter for the STRSQL command
Enter the following commands:
CHGCMDDFT CMD(STRSQL) NEWDFT(’NAMING(*SQL) DECPNT(*COMMA)
LANGID(*DE)’)
Instead of „*DE“ you can also choose a different language ID, according to how your AS/400 system
is configured.
3.3.1. AIX on the RS/6000
If you intend on using DB/6000 under AIX as your host database system, then you will need IBM’s
Communications Server for AIX, Version 4. Information about configuring an LU 6.2 can be found in
the documentation of this product.
17
Installing HOBLink DRDA _______________________________________________HOBLink DRDA
18
HOBLink DRDA __________________________Configuring the Connection in the APPC Subsystem
4. Configuring the Connection in the APPC
Subsystem
4.1. Configuring IBM APPC Networking Services
In order to establish the APPC connection via IBM APPC Networking Services, proceed as follows:
To configure the networking services, you must first open the configuration program. To do this, click
on the „Configure“ icon in the „IBM APPC Networking Services“ program group.
It is here that you define the parameters for the connection between the PC and the host. The configuration consists of three steps:
4.1.1. Step 1
Click on the „Step 1“ button to open the following dialog window “General Configuration”:
Enter the complete name of the logical unit (the fully qualified local LU name) in the uppermost data
field. The name consists of the network ID and the name of the local node. The two names must be
separated by a dot. The local LU name is defined for you on the remote system by the system administrator, usually in the VTAM definitions. If you are accessing a DB2/400 database, you can define the
name of the local node here yourself.
Network-ID g
Ask your system administrator for the name of your network ID
Name of the local node
Ask your system administrator for the name of your local node. This is
the name that the system administrator enters in the CP Name field of
the VTAM definitions of the remote system. Make sure to use an independent LU.
If you wish to access an AS/400 System, you define the name of the
local node yourself in this field. The name is then entered in the Communications Controller Description as a Remote Control Point.
e
In the lower data field, select the connection type, that you wish to use to establish a connection between the host and PC.
4.1.2. Step 2
Now click on the „Step 2“ button. Here you can enter the parameters for the connection type that you
selected in step 1.
Example: for the connection type „Local Area Network“ , enter a „Link Name“ of your choice. When
using HOBLink DRDA , you must select the first line (Link 1). The link name is then assigned a unique
„Remote Address“. The remote address is the network address of the system on which the remote
database resides. Ask your system administrator for the name of your „Remote address“.
4.1.3. Step 3
Click on „Step 3“ to invoke the dialog window „Definitions“:
19
Configuring the Connection in the APPC Subsystem __________________________HOBLink DRDA
The option „Modes“ is preselected. The logmodes which are available on your PC are listed here. The
logmodes contain parameters that determine how the communications are carried out. The logmode
that you select here must also be available on the remote system. Normally, you will not need to make
any entries on the „Side Information“ and „Transaction Programs“ pages.
We recommend the following logmodes (depending on the remote system):
•
•
•
•
•
•
QPCSUPP, when accessing a DB2/400 database
IBMRDB, when accessing a DB2/VM (SQL/DS) database
IBMRDB, when accessing a DB2/VSE (SQL/DS) database
IBMRDB, when accessing a DB2/MVS database
IBMRDB, when accessing a DB2/6000 database
IBMRDB, when accessing a DB2/2 database
The name of the logmode must correspond to the name entered in the logmode table (Logmode
the Modetab) on the host.
in
Defining a New Logmode
To define a new logmode, click the Define button. This opens the Define Mode window:
Sample values for using an SQL/DS database:
Mode Name
Maximum RU Size
Receive Pacing Window Size
Maximum Negotiable Sessions
Minimum Negotiable Contention Winners
IBMRDB
1920
4
8
4
4.2. Configuring the Microsoft SNA Server
If you wish to use the Microsoft SNA-Server to establish a connection, a „remote LU“ and a „local LU“
must be defined on the Server-PC. Additionally, you must install the Client Software of the SNA Server
on you local PC.
The following steps and sample figures apply to Version 2.11 of the Microsoft SNA Server.
4.2.1. Defining a Local LU
The administrator defines the LUs on the Server PC using the Administration Program of the Microsoft
SNA Server.
1. Select a Server in the „Servers and Connections“ window.
2. Select the command „Assign LUs“ in the „Services“ menu. This opens the „Insert LU“ window.
3. Click the option „APPC (Local)“.
4. Click „OK“.
5. Now you can define the entries for you local LU in the „New APPC LU Properties“ window. The LU
name
LU Alias
20
The LU-Name that has been assigned to the Server PC. The LU alias (not the
LU name in this window) must be used as the „LU name“ in the configuration
program of HOBLink DRDA .
HOBLink DRDA __________________________Configuring the Connection in the APPC Subsystem
LU 6.2 Type
For APPC connections, only independent LUs should be used.
Network Name
Ask your host system administrator for this name.
LU Name
Ask your host system administrator for this name.
The check box „Enable Automatic Partnering“ and „Member of Default Outgoing Local APPC LU Pool“
should be selected.
Implicit Incoming Remote LU
Set this option to „None“ .
Timeout for Starting Invokable TPs
Set this value to „60“ seconds.
4.2.2. Defining a Remote LU
In order to make entries for a „Remote LU“, first select an existing connection in the „Servers and Connections“ window. Then proceed as described above in defining a local LU.
4.2.3. Assigning a Mode to a Partner LU
Every local LU has one or more remote LUs assigned to it as partner LUs, each of which can use
different modes. In order to assign a partner LU a mode, proceed as follows:
1. Double click on a local LU in the list of „Servers and Connections“.
2. Click on the „Partners“ button in the „APPC Remote LU Properties“ window. This invokes the „LU
6.2 Partner LUs“ window.
Here you will find listed, the Partner LUs with their assigned modes. Assign the mode you wish to use
to communicate with the Partner LU.
We recommend using the following modes:
•
•
•
•
•
•
IBMRDB, when accessing a DB2/VM (SQL/DS) database
IBMRDB, when accessing a DB2/VSE (SQL/DS) database
IBMRDB, when accessing a DB2/MVS database
QPCSUPP, when accessing a DB2/400 database
IBMRDB, when accessing a DB2/6000 database
IBMRDB, when accessing a DB2/2 database
4.2.4. Installing Client Software
On your local PC, i.e. the PC that HOBLink DRDA is installed on, you must also install the Client Software of the Microsoft SNA Server. You will have to make the following entries during the installation:
User name
enter your user name on the SNA Server.
Domain name
enter the SNA-Server-Domain that is assigned to your SNA user. Ask your
SNA -Server administrator for this name.
21
Configuring the Connection in the APPC Subsystem __________________________HOBLink DRDA
4.3. Configuring Novell Netware for SAA
In order to establish an APPC connection via Novell NetWare for SAA (Version 2.00.30 or newer),
proceed as follows:
1. Contact the responsible administrator for the server on which Novell NetWare for SAA is to run.
The administrator must then configure the APPC connection to the host. Detailed information about
configuring APPC connections with Novell NetWare for SAA can be found in the appropriate Novell
manuals (e.g. Administration Guide for Mainframes and Peer Nodes).
2. Install „NetWare for SAA APIs“ on your PC’s hard drive.
3. Create a configuration with HOBLink DRDA (see Chapter „7.1. Adding and Configuring a Data
Source“ on page 27). You will not need to make any entries in the configuration program „NetWare
for SAA APIs“.
22
HOBLink DRDA _____________________________________________ Running the Setup Program
5. Running the Setup Program
In order to install HOBLink DRDA , insert the installation CD in the diskette drive of your PC.
If you are running a 16 bit operating system (Windows 3.1x) insert the installation diskette „HOBLink
DRDA 16 bit“.
If you are running a 32 bit operating system (Windows 95/98 or Windows NT/2000) insert the installation diskette „HOBLink DRDA 32 bit“.
Select the „Run“ command in the File menu of the Program Manager (Windows 3.1x) , or the „Run“
command from the launch pad ( Windows 95/98, NT/2000).
The following window pops-up:
Enter the following command in the command line:
A:\SETUP
A pop-up window appears in which you select the language you wish to have HOBLink DRDA installed in.
All dialog boxes and error messages issued by HOBLink DRDA will appear in the language you select
here. The error messages issued by the database application are not affected by this entry.
23
Running the Setup Program______________________________________________HOBLink DRDA
In the following dialog boxes you can confirm the HOB license agreement and enter the product key.
Finally, a window appears in which you can enter the path on the hard disk in which HOBLink DRDA
is to be installed.
In the field “path and name ...” you can enter the name and path of a HOBLink DRDA configuration file
located on a server. This file will subsequently be displayed by the HOBLink DRDA configuration program and can be activated in that program.
Enable the Add installation directory to system path check box if the system path is to be extended.
You should choose this option, if you use database applications, that use eSQL (embedded SQL), e.g.
HOB’s EasySQL Entry or HOBDBM. If you access data only over ODBC you shouldn’t enable this
check box.
Now click on the Setup button. The setup program copies the program files to the hard disk and registers the ODBC driver to the system.
If the program has been successfully installed, a pop-up window informs you about it. Now click the
„Back to Windows“ button. Windows does not need to be restarted.
Binding HOBLink DRDA
Before using HOBLink DRDA for the first time, you must first bind HOBLink DRDA to the database
(see section „7.4. Binding HOBLink DRDA to the Database “ on page 31). If you fail to execute a bind,
an error message will appear (SQL error 805 or 818).
24
HOBLink DRDA _____________________________________________________ Batch-Installation
6. Batch-Installation
HOBLink DRDA is a software that is most in use in large networks with many clients. To simplify the
installation and save time you may execute a batch installation.
For that all of the parameters that were specified by the installation of HOBLink DRDA were „recorded“. The same installation can be „played“ on a different client at a later time.
6.1. Recording the installation
The recording of the installation happens with the program „recintst.exe“, that is located in the catalog
PLREC16 (for Windows 3.1x) resp. PLREC32 (for Windows 95/98/NT/2000). For recording proceed
as follows:
1. Start the program „recinst.exe“. Alternatively the name of the recording file can be stated as parameter.
Example:
recinst instex.iss
If no parameter is stated, a dialog box is opened in which you have to specify the name of the recording file.
2. Following the setup program of HOBLink DRDA will be started automatically. Create a configuration how described in the previous chapters.
6.2. Playing the installation
The playing of a recorded installation happens with the program „playinst.exe“, that is located in the
catalog PLEREC16 (for Windows 3.1x resp. PLREC32 (for Windows 95/98/NT/2000).For playing proceed as follows:
1. Start the program „playinst.exe“. Alternatively the name of the recording file can be stated as parameter.
Example:
playinst instex1.iss
If no parameter is stated, a dialog box is opened in which you have to specify the name of the recording file.
2. Following the setup program of HOBLink DRDA will be started automatically, namely with the
parameters that were used by the previous recording.
25
Batch-Installation ______________________________________________________HOBLink DRDA
26
HOBLink DRDA _____________________________________________Configuring HOBLink DRDA
7. Configuring HOBLink DRDA
7.1. Adding and Configuring a Data Source
After installing HOBLink DRDA , you must define one or more data sources.
1. open the control panel window from the program manager
2. click on either the „ODBC“ or the „32-Bit ODBC“ (Windows 95/NT/2000) icon. (Under Windows
2000: Choose „Settings/Control Panel/Administrative Tools/Data Sources (ODBC)“ in the Windows
Start menu.)
The „Data Sources“ window appears on your screen:
All the currently registered data sources are listed in the dialog box. You may add, configure or delete
data sources to this list.
27
Configuring HOBLink DRDA _____________________________________________HOBLink DRDA
7.1.1. Configuring a New Data Source
In order to add a new data source, click the Add button of the Data Sources window. The „Add Data
Source“ window appears on your screen. All the ODBC drivers that are installed on your system are
listed here.
First click on the entry „HOBLink DRDA“, and then on the Finish button.
The pop-up window „New Configuration“ appears. You can enter the parameters for the data source
here.
Enter a unique name in the Configuration Name data field that you want assigned to this configuration
(data source).
Enter all the parameters for the connection and the data source in the appropriate fields.
28
HOBLink DRDA _____________________________________________Configuring HOBLink DRDA
Please note:
⅓⅔), must
All entries appearing in this chapter that are indicated by an encircled number (
likewise be made on the host computer. The corresponding encircled numbers can be found in Chapter „3.2. Definitions on the Host“.
Remote database
is the name of the database located on the host. The name may be up to 18 characters in length. Ask
your system administrator for this name.
User ID
is the name you use when logging on to the remote database. The user ID that you enter here, is the
default name whenever you logon to the database. You can, however, enter another name during the
logon process, in case you wish to logon using a different user’s name.
Connection Type
In this list field you determine which interface will be used for the connection to the database. If you
choose a connection type the second tab (APPC,...) changes in the “New Configuration” window. Information about entries you have to take you´ll find in the online help.
Different choices are available depending on the operating system you are using.
The following interfaces are available under Windows 3.x (16 Bit):
APPC, CPIC, EHNAPPC, TCP/IP
Under Windows 95/98 or Windows NT/2000 (32 Bit) you can choose from the following interfaces:
APPC, CPIC, EHNAPPC, TCP/IP, TCP/IP ANYNET
Depending on which subsystem you have installed on your PC to establish the connection, the following interfaces are available:
Under Windows 3.x:
Subsystem
Interface
MS SNA Server
Novell Netware for SAA
IBM APPC Networking Services for Windows
IBM Personal Communications
IBM Client Access/400
APPC
CPIC
EHNAPPC
EHNAPPC
EHNAPPC
Under Windows 95/98 or Windows NT/2000:
Subsystem
Interface
MS SNA Server
Novell Netware for SAA
IBM Personal Communications
IBM Client Access/400
HOB SNA Stack (HOB APPC)
APPC or CPIC
APPC, CPIC, NDS or EHNAPPC
APPC
EHNAPPC
APPC or CPIC
Net ID g
This name is the network ID of the network on which the remote database resides. Ask your system
administrator for this name.
29
Configuring HOBLink DRDA _____________________________________________HOBLink DRDA
LU Alias e
Enter the name of the local LU that your system administrator defined for you on the remote system
( e.g. in the VTAM definitions).
Please note: You must use the name of the LU Alias here, and not the name of the LU (in case the
two names are different).
Partner LU Name f
This is the name of the partner LU that is defined on the network on which the destination database
resides. Ask your system administrator for this name.
Please note: You must use the name of the partner LU here, and not the alias name of the partner
LU (in case the two names are different).
The LU name of your partner LU is defined by your system administrator on the remote system, e.g.
as the name of a virtual gateway in AVS.
When accessing an AS/400 system, you must enter the same name here that you defined as the
name of the partner node in the APPC subsystem. The network name and the partner LU name make
up the fully qualified partner LU name.
Log Mode d
This is the logmode (transmission mode) used to configure a DFV session between a user’s data station and a remote system. The Log mode is the name of a description that must be present and identical on both the PC and the host. This description contains information pertaining to the physical communication (e.g. block length etc.)
The log mode must correspond to the one on the host (logmode in the modetab). For convenience’s
sake, the easiest names to use on your PC are as follows (depending on the remote database):
Remote database
DB2/VM (SQL/DS)
DB2/VSE (SQL/DS)
DB2/400
DB2 for MVS
DB2/6000
DB2/2
Transmission mode
IBMRDB
IBMRDB
QPCSUPP
IBMRDB
IBMRDB
IBMRDB
Transaction Program: Prefix and Name
refers to the name of the partner program on the host and depends on the operating system installed
there.
Database
DB2/VM (SQL/DS)
DB2/VSE (SQL/DS)
DB2/400
DB2/MVS
DB2/2
DB2/6000
Prefix Name
0
Database name
07
6DB
07
6DB
07
6DB
is defined on the server
is defined on the server
Note:
The name „CAXE“ that is recommended to be used in the DB2/VSE manual should not be used as the
name of the database.
Further information about configuring a connection you will find in the online help of HOBLink DRDA.
30
HOBLink DRDA _____________________________________________Configuring HOBLink DRDA
7.2. Changing an Existing Data Source
In order to change an existing data source, click the „Install“ button in the „Data Source“ dialog box. A
dialog box containing the parameters of the existing data sources appears. Make the desired changes
to the parameters here.
To store the configuration with the new parameters, click the OK button.
If you wish to store the configuration under a new name, overwrite the configuration name and then
click the OK button. The original configuration also remains stored under its name.
7.3. Deleting an Existing Data Source
Click the „Delete“ button in the dialog box „Data Source“, in order to delete an existing data source.
7.4. Binding HOBLink DRDA to the Database
In order to allow the database program to communicate with HOBLink DRDA, you must create or enter the name of a so-called package on the database. The package contains information about the
SQL statements that HOBLink DRDA is to execute. Packages are stored under so-called collection ID
whose names you can determine by yourself.
In each and every database that you wish to access a package has to exist, that you use. Either you
create this package yourself by performing a so-called bind or you use a package, that already exists
in the collection.
7.4.1. Executing the Bind Yourself
In this case the database creates a so-called package for you, i.e. for the current user. To do this you
have to posess the appropriate user authority in the database (Bind Authority).
To execute a bind, click the bind button in the dialog box „New Configuration“ the „Bind“ button, after
you made the entries in the „bind options“ window. (see
7.4.2. Using the Package of a Different User
If you want to use an already existing package it has to be created with a bind in the concerning collection before. In this case you don´t have to execute the bind by yourself. You only have to entry the
collection ID that was used by the bind.
In order to use an existing package you have to posses the appropriate execute authority in the database (Run Authority). By using an existing package all settings are accepted that are carrried out in
the dialog box „bind options“ by the bind (isolation level, date format, time format, user group).
31
Configuring HOBLink DRDA _____________________________________________HOBLink DRDA
32
HOBLink DRDA _______________________________________________ Supplementary Programs
8. Supplementary Programs
8.1. The Program HOBBIND
The HOBBIND program binds bind files that were created with the help of a precompiler (e.g.
SQLPREP from IBM) to a database.
Syntax: HOBBIND bindfile.BND datasource
bindfile
is the name of the bind file. Bind files have the file extension „.BND”.
datasource
is the name of the data source (data source name), to which the bind file will
be bound.
When you call the program HOBBIND without any parameters or start it in the Windows Explorer a
dialog window will appear which you can use to perform the bind.
If one of the following error messages appears when you access the remote database, the version of
your application program does not match the bind file on the remote database system:
SQL0818N BIND MODULE NOT CURRENT
SQL0805N BIND MODULE NOT FOUND
In this case, install the current version of the application program on your PC or renew the bind file on
the remote system.
33
Supplementary Programs _______________________________________________HOBLink DRDA
8.2. The Program CODEPAGE
HOBLink DRDA is capable of interpreting codepages that are used by hosts. Among Codepage 273
(EBCDIC) HOBLink DRDA support the codepages 500, 277, 280, 284, 285, 297, 367 and 871. If you
use a different codepage on your host, which HOBLink DRDA cannot interpret, the following error
message will appear:
SQL00189N CODEPAGE ’XXX’ NOT FOUND
With the program CODEPAGE you can create on your PC the missing codepage for HOBLink DRDA.
To do this enter in a DOS command line:
CODEPAGE codepagenr datasource
codepagenr
is the number of the codepage that you want to create.
datasource
is the name of the data source (data source name), which you want to access.
The program CODEPAGE can be called without any parameters or be started in the Windows Explorer. In this case a dialog window will appear which you can use to create the codepage.
34
HOBLink DRDA _______________________________________________ Supplementary Programs
8.3. The Program HOBDBM
With the help of the program HOBDBM you can perform SQL queries in a database. To do this, call
the HOBDBM program in a DOS command line.
Syntax:
HOBDBM [/D:databasename [/U:Userid /P:passwort] ] [/C:“command“ |
/K:“command“ | /F:commandfile | /B:commandfile]
The parameters:
/D:
When you enter a database name HOBDBM will create a database connection to this
database immediately after the program start.
/C:
With the help of the parameter /C HOBDBM will execute the entered command after
the program start. (and after the connection). Afterward the program HOBDBM will be
closed.
/K:
like /C, but the HOBDBM program will not be closed after the command.
/F:
With the help of the parameter /F: you can hand over to the program HOBDBM the
name of a file in which SQL- and HOBDBM commands are contained. The commands
have to be separated by end-of-line (EOL). If the last character in a line is a ‘-’ character, the following line will be added. HOBDBM executes the commands line by line. If
HOBDBM is to be closed after executing the commands in the file enter the command
EXIT in the last line.
/B:
like /F, but the HOBDBM program will be closed automatically after executing the
commands.
The options /C, /K /F and /B must not be used simultaneously.
35
Supplementary Programs _______________________________________________HOBLink DRDA
SQL commands
HOBDBM supports the following SQL command:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
ACQUIRE
ALTER
CALL
COMMENT ON
CONNECT
CREATE
DELETE
DROP
GRANT
INSERT
LABEL ON
LOCK
UPDATE
SELECT
Additionally the command SELECT INTO can be used where after the key word INTO, instead of a list
of host variables the name of a file can be entered. In this file the result of the SELECT command will
be written.
Information about the syntax of the SQL commands you will find in the database’s SQL reference
manual.
The CALL command executes a stored procedure that is contained in a database. You may enter
additional parameters after the stored procedure name, which will be executed on the host/server.
Further information you will find in the file „hobdbm.txt“, which is contained in the HOBLink DRDA
installation directory.
HOBDBM commands
SET
With the help of the SET command you can change the preferences of the HOBDBM program.
The following preferences can be carried out.
OUTPUT
With this parameter the format of the output data of a SELECT command can be determined.
LIST
The data will be output as a table.
FILE
The data will be output in a format which is designated for the usage in applications like MS Excel.
*: With SET * followed by a number the maximal number of commands in the command buffer can be
determined. By default 10 commands are stored maximally.
QUERY
With the QUERY command you can display the preferences which were entered by the SET command.
The following display commands are available currently:
36
HOBLink DRDA _______________________________________________ Supplementary Programs
MODE
All preferences will be displayed.
LIST
The LIST command displays the tables resp. Packages contained in a database.
TABLES:
displays the tables
PACKAGES: displays the packages.
By default HOBDBM shows those tables/packages which the user created. In order to display the
tables of different users the following commands can be used.
FOR ALL:
displays all tables/packages
FOR USER:
is the default
FOR SYSTEM: shows system tables resp. the packages assigned to the system.
EXIT
With this command the HOBDBM program will be closed.
RUN
With the RUN command a file containing SQL and HOBDBM commands can be executed. For the
usage of this file see the command option /F. Note: If the file contains an EXIT command HOBDBM
will be closed.
#
With the # command a different program can be started.
Example: You want to view the file SELECT.TXT with the DOS Editor EDIT:
#EDIT SELECT.TXT
The DOS editor will be started and loads the file SELECT.TXT
If you want to use commands of the command line processor CMD.EXE use the following syntax:
#CMD /K“command“
If the command line processor is to be closed after the execution of „command“ e.g. when using the
COPY command, this can be carried out by the parameter /C“command“..
*: commandbuffer:
The last command can be executed once again by pressing the F3 key. (In MS Windows DOSKEY
can be used. In this case the commands are chooseable by the cursor keys.)
HOBDBM stores by default the last 10 commands. By entering * followed by a number one of these
10 commands will be executed – 1 represents the last command
The number of the stored commands can be changed by the SET * command
The command * LIST is used for displaying a list of all currently stored commands.
37
Supplementary Programs _______________________________________________HOBLink DRDA
38
HOBLink DRDA ____________________________________________________________ Glossary
Glossary
APPC and APPN
APPN (Advanced Peer-to-Peer Networking) includes functions, formats and protocols that improve the
management of SNA (Systems Network Architecture) and the use of APPC (Advanced Program-toProgram Communications) applications running in the network.
APPC (Advanced Program-to-Program Communications) is an implementation of the SNA LU 6.2
protocol (Systems Network Architecture Logical Unit ) that allows connected systems to transwith and
share program processing.
Remote Address
In order to be able to access a remote system over an LAN, you must first enter the „remote address“,
i.e. the address of the remote system, in the configuration program of the APPC subsystem. Ask your
system administrator for this name.
Local Nodes
Your local node must be assigned a unique address and /or ID in HOBLink DRDA. The local node
must be known to the remote system, in order to establish a connection (exception: OS/400, see below).
On systems running VTAM, the system administrator enters a „CP Name“ in the VTAM definitions.
This name must be used by HOBLink DRDA.
Furthermore, the system administrator can also define an additional ID for a local node.
If you wish to access an AS/400 System, you define the name of the local node in HOBLink DRDA
yourself. The name will then be entered in the Communication Controller Description as a „Remote
Control Point“.
Partner LU
The APPC Partner LU determines which remote system and its database will be accessed.
The combination of the network ID and the partner LU is known as the fully qualified Partner LU.
The name of a Partner LU can be up to 8 characters long. The following characters may be used:
• letters (A-Z, a-z)
• numbers (0-9)
• special characters (@, #, $)
The following rules apply when naming a Partner LU:
• the first character may not be a number
• no spaces may be used in the name
• no SQL reserved words may be used
39
Glossary _____________________________________________________________HOBLink DRDA
Transaction Program
is the name of the partner program on the host that interprets the SQL statements. The transaction
program is indicated by a prefix and a name and is dependent on the remote operating system.
Transmission Service Mode
Dialed calls, switched lines, packet switching or leased lines that are provided by a telecommunications private or public company.
The transmission service is the name of a description that must be present and identical on both the
PC and the host. This file contains information (e.g. block length, etc.) pertaining to the physical connection.
The transmission mode must correspond to the one implemented on the host. The easiest way to
make sure that this is the case, is by using one of the following names on your PC, since these are
provided by the database system:
Remote Database
SQL/DS
DB2/400
DB2/MVS
DB2/6000
Transmission mode
IBMRDB
QPCSUPP
IBMRDB
IBMRDB
Target Database
„Target database" is a text box in HOBLink DRDA.
Enter the name of the database here, that you wish to access.
40
HOBLink DRDA _______________________________________________________________Index
Index
A
Add Data Source..............................................................28
AIX ...................................................................................17
APPC .................................................................5, 9, 29, 39
APPC Connection ............................................................29
APPC LU Properties ........................................................20
APPC subsystem .......................................................30, 39
APPC Subsystem...............................................................5
APPN ...............................................................................39
AS/400 ...................................................................7, 17, 19
AS/400 system .................................................................30
AVS ..................................................................................14
B
Binding HOBLink DRDA ................................................24
C
Client Access/400 ..............................................................5
Client Access/400 for Windows........................................15
collection ..........................................................................16
configuration.....................................................................27
CPIC.................................................................................29
D
Data Source .....................................................................31
DB/6000 ...........................................................................17
DB2 ....................................................................................5
DB2/2 .................................................................................5
DB2/400 ...........................................................5, 15, 16, 19
DB2/6000 ...........................................................................5
DB2/VM..............................................................................5
DB2/VSE ............................................................................5
DB2APPL .........................................................................14
Defining a New Logmode ..............................................20
Definitions ........................................................................19
Distributed Relational Database Architecture ....................6
DRDA .................................................................................6
E
EBCDIC............................................................................34
F
fully qualified partner LU name ........................................30
H
HOBBIND.........................................................................33
host database .............................................................11
I
IBM APPC Networking Services ..................................5, 19
IBM Client Access/400 .......................................................5
IBM Client Access/400 for Windows ..................................7
IBM Communications Server .............................................5
IBM DATABASE 2..............................................................7
IBM Personal Communications..........................................5
IBMRDB ...............................................................11, 20, 21
L
Link Name ........................................................................19
local LU ......................................................................10, 21
Local SNA major node ...............................................11, 13
logmode .....................................................................10, 30
Logmode .......................................................................... 20
LU 11, 13
LU 6.2 .............................................................................. 17
LU 6.2 Type ..................................................................... 21
LU alias ............................................................................ 20
LU Name.......................................................................... 21
M
Microsoft SNA Server .................................................... 5, 7
Modes .............................................................................. 20
MVS ..................................................................... 11, 12, 13
N
Netware for SAA ................................................................ 5
NetWare for SAA ............................................................. 22
NetWare for SAA APIs..................................................... 22
network ID ........................................................................ 10
Network ID ....................................................................... 19
Network Name ................................................................. 21
Networking Services .......................................................... 5
Novell Netware for SAA ................................................. 5, 7
NULLID ............................................................................ 16
O
ODBC........................................................................... 6, 27
ODBC driver....................................................................... 6
Open DataBase Connectivity............................................. 6
OS/400..................................................................... 5, 7, 15
P
partner LU ............................................................ 10, 21, 30
Partner LU Name ............................................................. 14
Precompiler...................................................................... 33
Q
QPCSUPP ................................................................. 20, 21
Query Manager ................................................................ 16
R
remote address ................................................................ 39
Remote Address .............................................................. 19
Remote LU....................................................................... 21
S
SAA database systems...................................................... 6
Servers and Connections................................................. 20
Setup.................................................................................. 9
Side Information............................................................... 20
SNA Server ........................................................................ 5
SNA-Server-Domain ........................................................ 21
Software............................................................................. 7
SQL................................................................................ 5, 6
SQL Befehle..................................................................... 36
SQL/DS database ............................................................ 20
SRSLGMDE............................................................... 20, 21
Switched major node ................................................. 11, 13
system administrator........................................................ 16
T
target database ................................................................40
TCP/IP ............................................................................. 29
Token-Ring-Adapter................................................... 11, 13
Transaction Programs...................................................... 20
41
Index _______________________________________________________________HOBLink DRDA
V
VM ................................................................................... 13
VM ................................................................................... 13
42
VSE ............................................................................11, 13
VTAM ...........................................................................7, 39
VTAM definitions ........................................................11, 13
VTAM Version 4 .................................................................7