× 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: Response Time measurement
  • From: pytel@xxxxxxxxxx
  • Date: Wed, 29 Sep 1999 16:46:23 -0500

You should divide Total response time by Total transactions - then you will have
average response time.

Best regards
    Alexei Pytel


Lurton Keel <Lurton.Keel@serx.com> on 09/29/99 01:28:48 PM

Please respond to MIDRANGE-L@midrange.com

To:   "'MIDRANGE-L@midrange.com'" <MIDRANGE-L@midrange.com>
cc:
Subject:  RE: Response Time measurement




I wrote a program to use the QUSLJOB API, but the response time I get is the
Total Response Time.
What the heck is Total Response Time?
I ran the wrkactjob and my program and the RSP on wrkactjob for the job was
.5 while the Total Response Time was 12575.


          -----Original Message-----
          From:     R. Bruce Hoffman, Jr. [mailto:rbruceh@ibm.net]
          Sent:     Thursday, September 23, 1999 7:32 PM
          To:  MIDRANGE-L@midrange.com
          Subject:  Re: Response Time measurement

          Lurton Keel wrote:
          >
          > One of our IT objectives is for the response time on our
AS/400 620-2181 is
          > for the average response time 8-5 to be less than 2
seconds.
          > Short of buying a tool, does anyone know of a way to
programmatically get
          > the interactive response time so the data can be written
to a file.  Like
          > YYYYMMDD HHMM 3.2 seconds.  We would run the job every 15
minutes so that we
          > would get 4 timings per hour.

          API's of course. QUSLJOB. This API can list the jobs active
on the
          system and you can retrieve the response times from a list
of key values
          within a user space that is output by this API.



+---
| 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
+---



+---
| 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:

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.