DSI 5.0.3 and iSeries disconnects

amwalshjde

Well Known Member
We recently upgraded from DSI dclink 4.x to 5.0.3 We are getting periodic failues where our NT DSI server can longer talk to our iSeries running V5R4. Our JDE enviroment is Xe Update 6 (so we have no XML ability with DSI, as that came with Update 7).

We dont know what else we can look at to futher trouble shoot the issue. It occurs a couple of times each week. Has anyone else seen something similar?

Here are some logs:
On our NT DSI Server, the DClink50 system log shows this:
The description for Event ID ( 1 ) in Source ( DSI_AFC ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: DSI_AFC:DSI_COMMSHARED.CPP:LINE[98]
Service Stop.

--and--

The description for Event ID ( 1 ) in Source ( DSI_AFC ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: DSI_AFC:DSI_COMM.CPP:LINE[353]
5.0.3.0.

The windows application log shows this as an application error:
Faulting application dsi_e1fcp50.exe, version 5.0.0.3, faulting module ntdll.dll, version 5.2.3790.4455, fault address 0x0004cde2.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


The DSI Log itself shows this (DSI_AFC.txt):
02/04/2011 6:54:37.295
XXXXXXXXX:DSI_AFC:DSI_COMM.CPP:1371:90
AFC[DSI_E1FC50] API Call Error; Function[WorkOrderIssue]; RecordID[26255736]; Device/User[MTCTRL-XX]; Message[Time-out communicating with API caller object for function[WorkOrderIssue]]


When we turned jdedebug on, when we got the failure, the jdedebug.log only had this:
Feb 04 00:31:11 ** 3060/4040 **** jdeDebugInit -- output to file.
Feb 04 00:31:11 ** 3060/4040 Entering GetSystemDecimalSep.....
Feb 04 00:31:11 ** 3060/4040 jdedlg: Debug version of jdedlg installed.
Feb 04 00:31:11 ** 3060/4040 Entering JDB_InitEnv
Feb 04 00:31:11 ** 3060/4040 Entering JDB_SetEnv
Feb 04 00:31:11 ** 3060/4040 Entering JDB_InitUser with commit mode 0.
Feb 04 00:31:11 ** 3060/4040 Entering JDB_BeginTransaction
Feb 04 00:31:11 ** 3060/4040 Entering JDB_FreeUser


While normally, it shows this (only showing first bit):
Feb 04 07:21:01 ** 3700/1960 **** jdeDebugInit -- output to file.
Feb 04 07:21:01 ** 3700/1960 Entering GetSystemDecimalSep.....
Feb 04 07:21:01 ** 3700/1960 jdedlg: Debug version of jdedlg installed.
Feb 04 07:21:01 ** 3700/1960 Entering JDB_InitEnv
Feb 04 07:21:01 ** 3700/1960 Entering JDB_SetEnv
Feb 04 07:21:01 ** 3700/1960 Entering JDB_InitUser with commit mode 0.
Feb 04 07:21:01 ** 3700/1960 Entering JDB_BeginTransaction
Feb 04 07:21:01 ** 3700/1960 Entering JDB_FreeUser
Feb 04 07:21:03 ** 3700/1960 Entering JDB_InitUser with commit mode 0.
Feb 04 07:21:03 ** 3700/1960 Entering JDB_BeginTransaction
Feb 04 07:21:03 ** 3700/1960 Entering JDB_InitUser with commit mode 0.
Feb 04 07:21:03 ** 3700/1960 Entering JDB_BeginTransaction
Feb 04 07:21:03 ** 3700/1960 Entering JDB_OpenTable( Table = F986101)
Feb 04 07:21:03 ** 3700/1960 Database driver name is 'JDBODBC.DLL'
Feb 04 07:21:03 ** 3700/1960 ODBC DBInitDriver envr=039314E8 pool=N platform=WIN32
Feb 04 07:21:03 ** 3700/1960 ODBC version which the Driver Manager conforms : 03.52.0000
ODBC version which the driver supports : 03.51
The DBMS product accessed by the driver : - DB2/400 SQL
Feb 04 07:21:03 ** 3700/1960 ODBC:I DBInitConnection envr=039314E8 conn=03931590 cur=6 sep=/ act=0 yyyyy A (xxxxx@System - B7333)
..etc
 
We experienced timeouts with DSI and our iSeries, but it stemmed from the TranServer being in the DMZ of our network. Once this was corrected, the timeouts went away. Did any of your hardware move during this upgrade?
 
no. Both the DSI server and the iSeries exist on the same internal subnet.
 
Back
Top