November 10, 2006, 03:01 AM
marnixRmainframe connection using iWay connector
over the years we have been using EDAODBC for accessing our mainframe through VB applications, using EDA Client version 3.2.5 (which was originally designed for Windows 3.x operating systems)
when we encountered some problems with data retrieval the diagnosis was that it might be related to us using an outdated version, but since this version is no longer supported by IB nothing more could be done about it
however, we are in the process of migrating our hub from 4.3 to 5.3 and i have been told that the 3.2.5 version of EDA Client will no longer work when the migration is complete and the 4.3 hub has been removed
as a result of this the local IB team sent us a CD containing "iWay Connector for Windows 98,2000,NT,ME,and UNIX Version 5 Release 1"
i managed to install this no problem, but then had no instructions on how to set up the connection
the code currently used for recognising the server is located in C:\EDA\shared\EDALINK.CFG, the only live bit being the one concerning EDAPNHUB (IP address blanked out) :
;***********************************************************************
; EDA/Client Configuration File
; Generated by Installation on 6-16-2005 at 11:11:20
;***********************************************************************
NAME = EDACLIENT
;**********************************************************************
; Protocol block for MQSeries Message Queues
;**********************************************************************
;PROTOCOL = MQIS
;BEGIN
; QUEUE MANAGER = EDA
;END
;***********************************************************************
; OUTBOUND Communications Resource Definitions
;***********************************************************************
;NODE = NETSERVE
;BEGIN
; PROTOCOL = NETBIOS
; CLASS = CLIENT
; LOCAL NAME = edalocal
; REMOTE NAME = edaremote
; SEND TIMEOUT = 0
; RECEIVE TIMEOUT = 0
;END
;NODE = SPXSERVE
;BEGIN
; PROTOCOL = SPX
; CLASS = CLIENT
; NAME = eda
; BLOCK SIZE = 534
;END
;NODE = TCPSERVE
;BEGIN
; PROTOCOL = TCP
; CLASS = CLIENT
; HOST = eda
; SERVICE = eda
;END
;NODE = LU6SERVE
;BEGIN
; PROTOCOL = LU62
; CLASS = CLIENT
; LOCAL LU NAME = eda
; PARTNER LU NAME = eda
; TP NAME = eda
; MODE NAME = eda
;END
;NODE = LU2SERVE
;BEGIN
; PROTOCOL = LU2
; CLASS = CLIENT
; SHORTNAME = eda
; VENDOR = eda
; DLLNAME = eda
; SERVER VERSION = eda
;END
NODE = EDAPNHUB
BEGIN
PROTOCOL = TCP
CLASS = CLIENT
HOST = xx.xx.xx.xxx
SERVICE = 8400
END
;**********************************************************************
; Nodes for Asynchronous Clients
;
; Each node identifies an asynchronous client
; to which EDA/API client applications running on the
; EDA/Message Hub workstation can connect.
;
; There must be one Asynchronous Client node
; definition for each Synchronous Partner node
; defined below.
;**********************************************************************
;NODE = ASYNCSV1
;BEGIN
; PROTOCOL = MQIS
; CLASS = ASYNC(EDASERVE)
; LOCALQ = EDA.CLIENT
; REMOTEQ = MSGSRV.SERVER1
; TRACE = 23
;END
anyone out there with some suggestions on setting up a connection using iWay5.1 ?
November 14, 2006, 10:02 AM
KerryHi marnixR,
Here are the steps to get to the client configurator:
From the Start menu, select Programs, iWay Software, iWay Connectors 5.1, iWay Connector, and Configurator.
The node block syntax has not changed from the 43 to the 51.
Hope it helps.
Cheers,
Kerry
November 14, 2006, 11:21 AM
marnixRthanks for the reply, kerry
will try it out and let you know how it went
November 15, 2006, 03:34 AM
marnixRi wonder whether i've received the correct disk : i can't find "iWay Software" under "Programs", only "EDA Client 51", and no option to configure the connector
the disk i've received is called "iWay51 EDA Client" where i ran setup.exe from the main directory - there doesn't seem to be an obvious alternative for defining connectors
does this sound like i got the wrong disk, or am i missing something ?
December 01, 2006, 10:22 AM
KerryHi marnixR,
I am not very sure what is on the CD.
If the server is being upgraded to 5.3 then the client should also be 5.3. This is available for download from the
TechSupport site under downloads. You will need to have an InfoResponse username/password to access the downloads.
Hope this helps.
Cheers,
Kerry
December 01, 2006, 12:59 PM
marnixRthanks
will pass this info on to a business analyst, see if he can sort things out