Since you are using an ODBC listener all you get will be
a PIN and IP address. The clients connecting to the listener
do not "logon" as in session.

Do a showconn job=job# of ODBCLNSE job.

To get rid of the offending process you should be able to use abortproc,
available with the right patches.

HTH

-----Original Message-----
From: John Penney [mailto:[log in to unmask]]
Sent: Thursday, May 09, 2002 12:08
To: [log in to unmask]
Subject: Re: IP address mapping to session number


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 *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *