This post is more than 5 years old
5 Posts
0
958
Support Networker Module for Informix
Who in this community is using the NM for Informix ?
Legato still has no plans to support the IDS version 10.0,
and I am looking for people who might be affected from this missing support in the near future
Regards
Rainer
Legato still has no plans to support the IDS version 10.0,
and I am looking for people who might be affected from this missing support in the near future
Regards
Rainer
ble1
14.3K Posts
0
January 19th, 2006 01:00
ble1
14.3K Posts
1
January 19th, 2006 01:00
vobo123
5 Posts
0
January 19th, 2006 01:00
The comment from legato on this:
The current state of LGTpa75042 is : unevaluated.
That means that this RFE have been assigned to an engineer but we don't know yet if it will be accepted ( and then what the planned release is refused.
As this statement is very dissatisfying, I am looking for people who are or might be affected by this
Regards
Rainer
vobo123
5 Posts
0
January 19th, 2006 01:00
the onbar loops somewhere in the XBSA library and netver contacts the networker server.
ble1
14.3K Posts
1
January 19th, 2006 01:00
This leads me to an idea I did once - ask them to send you list of tests to be performed for verification of the module (if existing module is capable to handle IDS 10) and if all is fine it should be added to compatibility matrix. However, such thing usually works with LGTO/EMC partners. For end users I'm not sure... perhaps if big enough... Give it a try - test first existing module and if it seems to work approach Legato support with this idea (unless they will test it themselves before).
ble1
14.3K Posts
0
January 19th, 2006 02:00
http://listserv.temple.edu/archives/networker.html
vobo123
5 Posts
0
January 27th, 2006 01:00
Networker server is a WIN 2000 box.
Doing an onbar -b -L 0
with BAR_DEBUG=5
logs the following:
2006-01-27 10:10:48 4908 4906 do_args: return 0 (0x00)
2006-01-27 10:10:48 4908 4906 bar_siginit: enter
2006-01-27 10:10:48 4908 4906 bar_siginit: return
2006-01-27 10:10:48 4908 4906 bar_alarm: enter
2006-01-27 10:10:48 4908 4906 bar_alarm: return 0 (0x00)
2006-01-27 10:10:48 4908 4906 bar_exec: enter
2006-01-27 10:10:48 4908 4906 BSAQueryApi: enter
2006-01-27 10:10:48 4908 4906 bar_loadXBSA: enter
2006-01-27 10:10:48 4908 4906 bar_loadXBSA: return 0 (0x00)
2006-01-27 10:10:48 4908 4906 BSAQueryApiVersion: enter
2006-01-27 10:10:48 4908 4906 BSAQueryApiVersion: return
2006-01-27 10:10:48 4908 4906 bar_alarm: enter
2006-01-27 10:10:48 4908 4906 bar_alarm: return 240 (0xf0)
2006-01-27 10:10:48 4908 4906 BSAGetLastError: enter
2006-01-27 10:10:48 4908 4906 BSAGetLastError: return 132 (0x84)
2006-01-27 10:10:48 4908 4906 barQueryApi: return 0 (0x00)
2006-01-27 10:10:48 4908 4906 get_a_connection: enter
2006-01-27 10:10:48 4908 4906 bar_api_connect: enter
2006-01-27 10:10:48 4908 4906 bar_srv_status: enter
2006-01-27 10:10:48 4908 4906 bar_srv_status: return 5 (0x05)
2006-01-27 10:10:48 4908 4906 bar_alarm: enter
2006-01-27 10:10:48 4908 4906 bar_alarm: return 240 (0xf0)
2006-01-27 10:10:48 4908 4906 bar_api_connect: return 0 (0x00)
2006-01-27 10:10:48 4908 4906 get_a_connection: return 0 (0x00)
2006-01-27 10:10:48 4908 4906 bar_db_connect: enter
2006-01-27 10:10:48 4908 4906 bar_srv_status: enter
2006-01-27 10:10:48 4908 4906 bar_srv_status: return 5 (0x05)
2006-01-27 10:10:48 4908 4906 bar_db_connect: return 0 (0x00)
2006-01-27 10:10:48 4908 4906 bar_full_logs: enter
and onbar never leaves this state
Tracing the onbar_d with tusc shows the loop it takes:
send(7, "\001\001\0Y s e l e c t i s ".., 142, 0)
recv(7, "\0\b\002\0\0\0\0\0\0\0\f\003\0\0".., 4096, 0)
send(7, "\001\001\0Y s e l e c t i s ".., 142, 0)
recv(7, "\0\b\002\0\0\0\0\0\0\0\f\003\0\0".., 4096, 0)
send(7, "\001\001\0Y s e l e c t i s ".., 142, 0)
.
.
.
.
ble1
14.3K Posts
0
January 27th, 2006 01:00
the onbar loops somewhere in the XBSA library and
netver contacts the networker server.
Can you let me know what OS did you use? My colleague just did a test with IDS 10 on Solaris 9 with current Informix module by Legato and it works without any problems. After that we corrupted the dbs and with onbar -r we were able to bring back whole thing back to its feet as expected. In our case both IDS server and NW server were same machine (it was test setup).
ble1
14.3K Posts
0
January 27th, 2006 02:00
ble1
14.3K Posts
0
January 27th, 2006 02:00
vobo123
5 Posts
0
January 27th, 2006 02:00