Listers:
Thanks! to all of you who replied.
Now, I'll be a little more specific as your ideas, although sound, don't address my situation:
I have 2 ODBC listeners jobs - MBFoster - running on our 3000. Occasionally, like 7PM on a Wednesday evening, I get paged because one of the jobs has 'locked up' the system.
What I need is the ability to translate the Pin and IP address to a Session # so that I can locate the rogue "SQL from Hell" that is beating the HP into submission and call the offending Session. More info required?
TIA
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *