×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
All,
We set up a specific subsystem to service ODBC/JDBC/ect jobs from a
particular set of IP address as describe in the following Centerfield
Newsletter:
http://www.centerfieldtechnology.com/publications/archive/August%202005%20Newsletter.pdf
Part of the process is to use iNav to specify the IP addresses whose
connections will be routed to the new custom subsystem.
Everything has been working fine for months.
Today we noticed that the QZDASOINIT jobs in that subsystem are
servicing a connection from an IP address other than the ones
specified for the subsystem.
I've doubled checked that the custom subsystem still has just the
original two IP address specified, so why is a connection from this
other IP address going to the custom subsystem instead of the default
QUSRWRK susbsystem?
I though perhaps when the connection first came in, the QUSRWRK jobs
were not available, so the connections went to the custom subsystem
jobs. However, after ending the two connected jobs, I got two new
connections in from the problem server still going to the custom
subsystem. I know the QUSRWRK subsystem jobs are there and I've got
lots of other connections going to them properly.
Does anybody have a clue as to what's going on?
Thanks!
Charles Wilt
midrange.com
