RE: V5Rx Nuances

Bill,

The issue with the access path size *MAX1TB has been around for years.  We
had to address this on V4R4 years ago.

Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-898-7863 or ext. 1863



-----Original Message-----
From: Bill [mailto:billzbubb@subdimension.com]
Sent: Friday, December 06, 2002 4:31 PM
To: midrange-l@midrange.com
Subject: V5Rx Nuances


This is a multi-part message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Another division in our corporation jumped from V4R4 to V5R1 earlier in the
year and they experienced massive performance problems.  They eventually
performed the StrObjCnv on everything and they changed all of the Access
path size from *MAX4G to *MAX1TB in all keyed files and logicals files, they
were told by IBM to do this because the data from some database monitor jobs
showed high contention for keys.

We are planning to go from V4R5 to V5R2 this weekend.  After reading the IBM
upgrade manuals, they specifically state that a StrObjCnv on everything
would not be necessary, that the conversion would only delay things about
one second per file.

I believe I've read earlier that many people actually recommend running
StrObjCnv on everything, but I don't think I've read about anyone changing
access path sizes.

What has been your experience with these two issues?

Bill
--

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