Chuck:

I have the MBFoster console. What I cannot do is identify the actual #S for which each thread is executing. Maybe you can't do this but I dunno why I can't...

What I get is the #J info which tells me squat. I laready KNOW the Job Numbers..

Kindest

JP

>>> <[log in to unmask]> 05/09/02 11:35AM >>>
John,

Like Liz said, :showconn should do the trick.  I'd also recommend you look 
at the MBFoster
Console product.  It lets you see who is doing what...




Chuck Ciesinski
Hughes Network Systems
Germantown, MD
p  301 601 2608
f   301 601 6303
email  [log in to unmask] 
"Oh well, chocolate is GOOD"  Chuck Ciesinski




John Penney <[log in to unmask]>
Sent by: HP-3000 Systems Discussion <[log in to unmask]>
05/09/2002 02:08 PM
Please respond to John Penney

 
        To:     [log in to unmask] 
        cc: 
        Subject:        Re: [HP3000-L] 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 *