HOB Database Gateway Extension - Installation

Overview

HOB Database Gateway Extension (IBIPGW04) runs under Windows NT. The client side connections are performed over TCP/IP, the server side connections over SNA APPC. IBIPGW04 translates DRDA protocol from TCP/IP to SNA/APPC.

IBIPGW04 is neccessary, if DRDA clients like HOBLink DRDA or IBM DB2-Connect are to be connected over TCP/IP to a DB2-Database in an SNA network. Additionally HOB Database Gateway Extension allows SSL encryption on the client side.

IBIPGW04 requires an SNA gateway product which does the SNA protocol.

This may be:

  • Microsoft SNA Server
  • IBM eNetwork Communications Server for Windows
  • HOBLink SNA Stack

 

Running IBIPGW04

The program IBIPGW04 should be installed on Windows NT as a service. It can also be started from the command prompt. IBIPGW04 reads its configuration parameters from an .ini-file. The .ini-file can be edited with any usual ASCII-editor under Windows NT. Please obey the rules for Windows .ini-files.

When IBIPGW04 is started, there is a parameter to specify the name of the .ini-file. Please notice that Windows will not search the file in the path currently active. To start IBIPGW04 with an .ini-file (example xyz.ini) in the current directory, use ./ to specify the current directory, or use the total path name.

Example:

IBIPGW04 xyz.ini

Sections and Parameters in the .ini file

IBIPGW04 can open more than one port on TCP/IP for incoming connection calls from clients. Each open port can connect to a different database or can use another MODE.

There is one section for every port to be opened, the name starts with HOST. In each section, there may be the following parameters:

GATEPORT Mandatory, number of the TCP/IP-port to be opened.
GATEFUNC Mandatory, function to be used on this port, must be DRDA.
GATEPROT Specifies the TCP/IP stack to be used. 
Possible values:
AF_INET
the Windows TCP/IP stack is used.
1005
HOBLink Secure will be used. In this case the HOBLink Secure Client has to be installed.
LUNS Mandatory, APPC-LU-Name of Server, LU-Name of the database to connect. This may also be CICS or IMS/DC, AVM or DDF depending on the installation. This may be the fully-specified SNA Network-Name including Netid (dot included in the name), or it may be the ALIAS-Name used for a APPC-LU (no dot included in the name).
MODE  Mandatory, Name of Mode to be used for every connection, means session or transaction.
TPNAME Mandatory, Name of Database to be connected. This parameter has to be filled in hexa, means 2 characters from 0-9 or A-F for every single Byte. Normally this will be an EBCDIC-Name.
CLLU Optional, Name of APPC-LU to be used on Client-Side.
TIMEOUT timeout (value 0 up to nnn seconds of inactivity). Note: As IP is a connectionless protocol a timeout should be set. We recommend a timeout from one hour to one day. If the value 0 is used, the connection will not be watched.

 

Example:

[HOST0001]
GATEPORT=4224
GATEPROT=AF_INET
GATEFUNC=DRDA
LUNS=BRAND.VM09KB94
MODE=IBMRDB
TPNAME=E2D8D3C8D6C2
TIMEOUT1=180
[HOST0002]
GATEPORT=4225
GATEPROT=AF_INET
GATEFUNC=DRDA
LUNS=BRAND.HT0EICCF
MODE=#INTER
TPNAME=06F6C4C2
TIMEOUT1=14400
[HOST0003]
GATEPORT=4226
GATEPROT=AF_INET
GATEFUNC=DRDA
LUNS=BRAND.VM09KB94
MODE=IBMRDB
TPNAME=D2C2F9F4
[HOST0004]
GATEPORT=4227
GATEFUNC=DRDA
LUNS=BRAND.VS12CICS
MODE=#INTER
TPNAME=07F6C4C2
TIMEOUT1=14400
[HOST0005]
GATEPORT=4228
GATEFUNC=DRDA
LUNS=BRAND.MV14DB2
MODE=IBMRDB
TPNAME=07F6C4C2
[HOST0010]
GATEPORT=4233
GATEFUNC=DRDA
LUNS=BRAND.H9OBX
MODE=IBMRDB
TPNAME=C8D6C2E2D8D3F9F7

 

webmaster@hobsoft.com, Last Updated: 03. Jul 07

 


| Home | News | Products | Software tests | Sitemap | Feedback |

Imprint