× 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.


  • Subject: Re: How to debug client server applications?
  • From: Kirk Goins <kgoins@xxxxxxxxxxx>
  • Date: Fri, 05 May 2000 11:31:21 -0700

Buck Calabro wrote:

>
> Is there an easy way to find out what server jobs are servicing a particular
> user profile?  WRKUSRJOB is useless as is WRKACTJOB.  I could use QUSLJOB
> and QUSRJOBI and brute force search each job (which is what I'm starting on
> now.) <grrrrr>
>
> Buck Calabro
> Aptis; Albany, NY

The problem being that each of those QZD.... jobs can service multiple users 
it's not a one to one.
You might try using the STRDBMON cmd. It can be started for a single job or 
*ALL. Try using *ALL for about 5min then end it with ENDDBMON
*ALL. Depending on the option taken and what's going on in the system these 
files can be H U G E especially with *ALL for jobs. Once you end
it do something like runqry *none filename and browse the file. It will show 
all db transactions and even the sql statement itself.

This is used mainly has a performance tool but can be handy looking for other 
problems.

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.