• Subject: RCLSTG: The Timings
  • From: PaulMmn <PaulMmn@xxxxxxxxxxxxx>
  • Date: Mon, 8 Dec 1997 22:03:56 -0500

For those who have asked the age-old question, "How long will a RCLSTG take
on my machine," I have 2 possible answers.  Of course, your mileage may
vary:  the number of objects on your system, jobs in the system, size of
the objects, etc., etc. may cause your performance to be different.

With that said, here are 2 times:

System 'A'
        Approximately 8 hours to RCLSTG

        AS/400 Model 320
        Aux Storage 256 Gigabytes       82.3598% occupied; 827 libraries
                108 model 6606, 20 model 6607 disk drives
                System drive is Mirrored; all other drives RAID
        Memory: 1.57 Gigabytes
        Jobs in System:  Approx. 11000 (mostly on OUTQs)
        % Perm addresses used: 42%
        % temp addresses used: .308
        Pools: Machine- 200 Meg
                *Base - 1373 Meg

        System 'A' has been installed for about 2-3 years and has NEVER
        had a RCLSTG run on it.

System 'B'
        Approximately 3 hrs, 45 minutes

        AS/400 Model 640/2239
        Aux Storage: 436.2 Gigabytes    55% used
                RAID
        Memory: 4.194 Gigabytes
        Jobs in System:   7568  (how quickly printouts accumulate)
        % Perm:  .009
        % termp: .013
        Pools:  I didn't check    ):

        System 'B' is brand-new


--Paul E Musselman
PaulMmn@ix.netcom.com


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@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 thread ...

Follow-Ups:

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

This mailing list archive is Copyright 1997-2019 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].