RE: Performance of *MAX4GB files vs *MAX1TB

Actually - my company has.  We had some real performance problems with a
particular program.  Our users would stop and wait for 5-15 minutes when
this program ran.  It was a maintenance program that many users ran at the
same time.  After much investigation by IBM and us...IBM told us to change
the accpthsiz on the physical file and all the logicals attached to the
file.  It absolutely made a major difference.   I haven't  seen this
documented anywhere.  

        -----Original Message-----
        From:   Scott.Lindstrom@zenith.com [SMTP:Scott.Lindstrom@zenith.com]
        Sent:   Monday, November 22, 1999 4:16 PM
        To:     midrange-l@midrange.com
        Subject:        Performance of *MAX4GB files vs *MAX1TB



        I think I remember John Sears stating at a COMMON presentation that
physical
        files created with the parameter ACCPTHSIZ(*MAX1TB) will perform
better than
        'old' files created at *MAX4GB since they execute a different (newly
written)
        code path when they are accessed.

        Has anyone had a chance to see if it's worthwhile changing old
physical files to
        *MAX1TB to realize a performance benefit?  (Perhaps someone with a
standalone
        machine for testing)?

        Scott Lindstrom
        Zenith Electronics


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