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



jt,

Exporting to ifs directories (non QSYS.LIB) as .txt is no problem.

I created a share to a file called BUBBA in library ROB.  This file has a
record length of 150 - no DDS.  Exporting to this did not generate an error
but neither did it work.  I suspect it is because there is no .mbr option -
just .csv, .txt and a few others.

I hope you didn't make me go through this work just so you could rant on
about the evils of GUI tools again.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin



                    "jt" <jt@ee.net>
                    Sent by:                  To:     <midrange-l@midrange.com>
                    midrange-l-admin@mi       cc:
                    drange.com                Fax to:
                                              Subject:     RE: Interactive 
Response Time

                    12/18/2001 08:17 AM
                    Please respond to
                    midrange-l






Rob,

Ya...!  Can you *OUTFILE this stuff to a 400 DB file...?  (.txt is OK,
though)

jt

| -----Original Message-----
| From: midrange-l-admin@midrange.com
| [mailto:midrange-l-admin@midrange.com]On Behalf Of rob@dekko.com
| Sent: Tuesday, December 18, 2001 8:06 AM
| To: midrange-l@midrange.com
| Subject: Re: Interactive Response Time
|
|
|
| I fired up Operations Navigator's performance features on our newly
| upgraded P50-840-12way.  Then I exported these graphs to txt files.  Here
| are the results.  Would knowing this information from your system
| help you?
|
| CPU Utilization (Average)
|
| Date           Time           System     Value
| ----------     ----------     -----      -----
| 12/17/2001     4:00:00 PM     Gdihq      6.00
| 12/17/2001     4:01:00 PM     Gdihq      7.00
| 12/17/2001     4:01:30 PM     Gdihq      7.00
| 12/17/2001     4:02:00 PM     Gdihq      8.00
| 12/17/2001     4:02:30 PM     Gdihq      17.00
| 12/17/2001     4:03:00 PM     Gdihq      10.00
| 12/17/2001     4:03:30 PM     Gdihq      6.00
| 12/17/2001     4:04:00 PM     Gdihq      8.00
| 12/17/2001     4:04:30 PM     Gdihq      12.00
| 12/17/2001     4:05:00 PM     Gdihq      10.00
| 12/17/2001     4:05:30 PM     Gdihq      13.00
|
|
| CPU Utilization (Interactive Feature)
|
| Date           Time           System     Value
| ----------     ----------     -----      ------
| 12/17/2001     4:00:00 PM     Gdihq      3.00
| 12/17/2001     4:01:00 PM     Gdihq      4.00
| 12/17/2001     4:01:30 PM     Gdihq      4.00
| 12/17/2001     4:02:00 PM     Gdihq      44.00
| 12/17/2001     4:02:30 PM     Gdihq      146.00
| 12/17/2001     4:03:00 PM     Gdihq      76.00
| 12/17/2001     4:03:30 PM     Gdihq      4.00
| 12/17/2001     4:04:00 PM     Gdihq      4.00
| 12/17/2001     4:04:30 PM     Gdihq      53.00
| 12/17/2001     4:05:00 PM     Gdihq      14.00
| 12/17/2001     4:05:30 PM     Gdihq      5.00
|
| Interactive Response Time (Average)
|
| Date           Time           System     Value
| ----------     ----------     -----      ----
| 12/17/2001     4:00:00 PM     Gdihq      0.11
| 12/17/2001     4:01:00 PM     Gdihq      0.11
| 12/17/2001     4:01:30 PM     Gdihq      0.12
| 12/17/2001     4:02:00 PM     Gdihq      0.13
| 12/17/2001     4:02:30 PM     Gdihq      0.29
| 12/17/2001     4:03:00 PM     Gdihq      0.60
| 12/17/2001     4:03:30 PM     Gdihq      0.70
| 12/17/2001     4:04:00 PM     Gdihq      0.09
| 12/17/2001     4:04:30 PM     Gdihq      0.24
| 12/17/2001     4:05:00 PM     Gdihq      0.17
| 12/17/2001     4:05:30 PM     Gdihq      0.11
| ...
| 12/17/2001     4:16:30 PM     Gdihq      0.27
| 12/17/2001     4:17:00 PM     Gdihq      7.24
| 12/17/2001     4:17:30 PM     Gdihq      0.12
|
|
| Interactive Response Time (Maximum)
|
| Date           Time           System     Value
| ----------     ----------     -----      ------
| 12/17/2001     4:00:00 PM     Gdihq      0.65
| 12/17/2001     4:01:00 PM     Gdihq      1.47
| 12/17/2001     4:01:30 PM     Gdihq      0.92
| 12/17/2001     4:02:00 PM     Gdihq      0.92
| 12/17/2001     4:02:30 PM     Gdihq      5.15
| 12/17/2001     4:03:00 PM     Gdihq      57.63
| 12/17/2001     4:03:30 PM     Gdihq      46.25
| 12/17/2001     4:04:00 PM     Gdihq      0.69
| 12/17/2001     4:04:30 PM     Gdihq      3.69
| 12/17/2001     4:05:00 PM     Gdihq      2.40
| 12/17/2001     4:05:30 PM     Gdihq      0.63
|
|
| Disk Arm Utilization (Average)
|
| Date           Time           System     Value
| ----------     ----------     -----      ----
| 12/17/2001     4:13:00 PM     Gdihq      1.00
| 12/17/2001     4:13:30 PM     Gdihq      1.00
| 12/17/2001     4:14:00 PM     Gdihq      2.00
| 12/17/2001     4:14:30 PM     Gdihq      2.00
| 12/17/2001     4:15:00 PM     Gdihq      2.00
| 12/17/2001     4:15:30 PM     Gdihq      2.00
| 12/17/2001     4:16:00 PM     Gdihq      1.00
| 12/17/2001     4:16:30 PM     Gdihq      1.00
| 12/17/2001     4:17:00 PM     Gdihq      2.00
|
|
| Disk IOP Utilization (Average)
|
| Date           Time           System     Value
| ----------     ----------     -----      -----
| 12/17/2001     4:13:00 PM     Gdihq      5.00
| 12/17/2001     4:13:30 PM     Gdihq      5.00
| 12/17/2001     4:14:00 PM     Gdihq      6.00
| 12/17/2001     4:14:30 PM     Gdihq      9.00
| 12/17/2001     4:15:00 PM     Gdihq      6.00
| 12/17/2001     4:15:30 PM     Gdihq      6.00
| 12/17/2001     4:16:00 PM     Gdihq      7.00
| 12/17/2001     4:16:30 PM     Gdihq      6.00
|
|
| Communications IOP Utilization (Maximum)
|
| Date           Time           System     Value
| ----------     ----------     -----      -----
| 12/17/2001     4:13:00 PM     Gdihq      14.00
| 12/17/2001     4:13:30 PM     Gdihq      14.00
| 12/17/2001     4:14:00 PM     Gdihq      14.00
| 12/17/2001     4:14:30 PM     Gdihq      14.00
| 12/17/2001     4:15:00 PM     Gdihq      14.00
| 12/17/2001     4:15:30 PM     Gdihq      14.00
| 12/17/2001     4:16:00 PM     Gdihq      14.00
| 12/17/2001     4:16:30 PM     Gdihq      14.00
| 12/17/2001     4:17:00 PM     Gdihq      23.00
|
|
| User Pool Faults (Average)
|
| Date           Time           System     Value
| ----------     ----------     -----      ----
| 12/17/2001     4:12:30 PM     Gdihq      1.00
| 12/17/2001     4:12:45 PM     Gdihq      1.00
| 12/17/2001     4:13:00 PM     Gdihq      1.00
| 12/17/2001     4:13:15 PM     Gdihq      1.00
| 12/17/2001     4:13:30 PM     Gdihq      1.00
| 12/17/2001     4:13:45 PM     Gdihq      1.00
| 12/17/2001     4:14:00 PM     Gdihq      1.00
| 12/17/2001     4:14:15 PM     Gdihq      1.00
|
|
| Communications Line Utilization (Average)
|
| Date           Time           System     Value
| ----------     ----------     -----      ----
| 12/17/2001     4:11:00 PM     Gdihq      1.00
| 12/17/2001     4:12:00 PM     Gdihq      1.00
| 12/17/2001     4:13:00 PM     Gdihq      1.00
| 12/17/2001     4:14:00 PM     Gdihq      1.00
| 12/17/2001     4:15:00 PM     Gdihq      1.00
| 12/17/2001     4:16:00 PM     Gdihq      1.00
| 12/17/2001     4:17:00 PM     Gdihq      1.00
| 12/17/2001     4:18:00 PM     Gdihq      1.00
| 12/17/2001     4:19:00 PM     Gdihq      1.00
| 12/17/2001     4:20:00 PM     Gdihq      6.00
|
|
| LAN Utilization (Average)
|
| Date           Time           System     Value
| ----------     ----------     -----      ----
| 12/17/2001     4:11:00 PM     Gdihq      1.00
| 12/17/2001     4:12:00 PM     Gdihq      1.00
| 12/17/2001     4:13:00 PM     Gdihq      1.00
| 12/17/2001     4:14:00 PM     Gdihq      1.00
| 12/17/2001     4:15:00 PM     Gdihq      2.00
| 12/17/2001     4:16:00 PM     Gdihq      2.00
|
| There's several more charts available.
|
|
|
| Rob Berendt
|
| ==================
| "They that can give up essential liberty to obtain a little temporary
| safety deserve neither liberty nor safety."
| Benjamin Franklin
|
|
|
|                     prumschlag@phdinc.c
|                     om                        To:
| midrange-l@midrange.com
|                     Sent by:                  cc:
|                     midrange-l-admin@mi       Fax to:
|                     drange.com                Subject:     Re:
| Interactive Response Time
|
|
|                     12/17/2001 04:01 PM
|                     Please respond to
|                     midrange-l
|
|
|
|
|
|
|
|
| Mike,
|
| (jt:  You might want to read this, too.)
|
| I really like the format you are using with the various time buckets.
| After
| running down several dead-end paths,  the only performance file (QAPM*) I
| see
| that has this kind of information is QAPMRESP which is for twinax
attached
| workstations only.  The Performance Tools Manual shows a report
| for Locally
| Attached Workstations as well as one for Remote Workstations.  I am not
| finding
| this type of info for LAN attached Client Access type workstations.
|
| Is your report showing the Client Access workstations or just the twinax
| type?
|
| If I understand correctly, Performance Tools presents reports and screens
| based
| on the data that is collected by the QPFRMON job that starts when
| you run a
| STRPFRMON command.  (I am not sure if/how this is related to the
CRTPFRDTA
| job
| that is always running in QSYSWRK.)  We don't have Performance Tools, but
| before
| I spend money, I would like to have some assurance PT can actually
provide
| the
| info I need.
|
| Phil
|
|
|    <snip>
|    Enough of my stories.  My thought is that you use another metric for
|    response time.  This assumes you can get someone to buy into the idea
| that
|    sometimes response time is an application problem or design issue.  I
| think
|    this is real critical.   What we measure is the 'distribution curve of
|    response times'.  Everyone is going to be slightly different
| but what we
|    measure is the standard 4 buckets: 0-1 second, 1-2, seconds, 2-4
| seconds,
|    4+ seconds.  95% of our transactions fall within sub-second, 98%
within
| 2
|    seconds, and so on.   Right now I forget how we track that but I am
| pretty
|    sure it is a component of performance tools.
|    <end snip>
|
|
| _______________________________________________
| This is the Midrange Systems Technical Discussion (MIDRANGE-L)
| mailing list
| To post a message email: MIDRANGE-L@midrange.com
| To subscribe, unsubscribe, or change list options,
| visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
| or email: MIDRANGE-L-request@midrange.com
| Before posting, please take a moment to review the archives
| at http://archive.midrange.com/midrange-l.
|
|
|
|
|
| _______________________________________________
| This is the Midrange Systems Technical Discussion (MIDRANGE-L)
| mailing list
| To post a message email: MIDRANGE-L@midrange.com
| To subscribe, unsubscribe, or change list options,
| visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
| or email: MIDRANGE-L-request@midrange.com
| Before posting, please take a moment to review the archives
| at http://archive.midrange.com/midrange-l.
|

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.







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.