|
> So, That means it is okay to say that every time we have a new version of > operating system we upgrade our hardware ...... If you look at the history of EVERY computing system, upgrades of OS features have always required more memory, more disk, & more processor speed. Same for pc (windoze & dos), unix, mac, mainframe, s34, s36, s38 & os/400. Why the shock? When I upgraded my B10 to a D10 in '90 or 91 - it took more memory & disk. No big shock. Also, as I pointed out in a very early post on this, your query problem may have been due to a missing ptf (which ibm documented in the psp since Oct 2000 as a definite fix to query performance). IBM provides the tools to determine what you need "before" the upgrade, so you can make an informed decision. Jim Franz ----- Original Message ----- From: "Basit Khan" <Bkhan@medexassist.com> To: <midrange-l@midrange.com> Sent: Wednesday, October 10, 2001 9:26 AM Subject: RE: Will Upgrading to V4R5 impact performance??? > So, That means it is okay to say that every time we have a new version of > operating system we upgrade our hardware - someone is talking "M S > "'s language here. I thought that is not the case with IBM's AS/400 - well I > guess I was wrong. > > We were running our billion dollar business on 436 without a single problem > and just the version upgrade will make it obsolete box - I am sorry but > there is something wrong with this picture. > > > > B Khan > > -----Original Message----- > From: rob@dekko.com [mailto:rob@dekko.com] > Sent: Tuesday, October 09, 2001 10:42 AM > To: midrange-l@midrange.com > Subject: RE: Will Upgrading to V4R5 impact performance??? > > > > So, as the other gentleman said, if you would have had Windows 3.1 running > on an older PC and upgraded it to Win NT or W2K then you could have > expected about the same results. A 436 is a teeny weensie box. IBM has > said that the follow on to V5R1 will not run on some older boxes - like a > 40S that we have. > > And if you have such a machine you are partially right. Before you decide > to upgrade OS, maybe you should think about upgrading hardware. But then > we have a P40 that is: > % CPU used . . . . . . . : 3.0 > (Above was a snapshot from DSPSYSSTS at 9:38am our time) > So we are going to upgrade it to a P50. > > Rob Berendt > > ================== > A smart person learns from their mistakes, > but a wise person learns from OTHER peoples mistakes. > > > > Basit Khan > <Bkhan@medexassist. To: > "'midrange-l@midrange.com'" <midrange-l@midrange.com> > com> cc: > Sent by: Fax to: > midrange-l-admin@mi Subject: RE: Will > Upgrading to V4R5 impact performance??? > drange.com > > > 10/09/2001 08:12 AM > Please respond to > midrange-l > > > > > > > I had no performance issues before the upgrade however after I upgraded to > v4r5 it was a disaster - every time we have a single user running query it > will basically stop processing every thing else. We ended up moving to > another box. > I will say if you have an older box and it has no performance issues just > leave it alone - unless you have have a more robust box. We had 436 which > was an old box but it was performing very well with v4r3 - now that we > migrated to 170 and it is working fine with v4r5 ( but it has more DASD and > memory is almost double than older box) > > > > B Khan > > > > -----Original Message----- > From: rob@dekko.com [mailto:rob@dekko.com] > Sent: Monday, October 08, 2001 5:50 PM > To: midrange-l@midrange.com > Subject: RE: Will Upgrading to V4R5 impact performance??? > > > > Basit, > > What are your measurements, before and after the upgrade? > > > Rob Berendt > > ================== > A smart person learns from their mistakes, > but a wise person learns from OTHER peoples mistakes. > > > > Basit Khan > <Bkhan@medexassist. To: > "'midrange-l@midrange.com'" <midrange-l@midrange.com> > com> cc: > Sent by: Fax to: > midrange-l-admin@mi Subject: RE: Will > Upgrading to V4R5 impact performance??? > drange.com > > > 10/08/2001 03:37 PM > Please respond to > midrange-l > > > > > > > be ready for Slow performance... > > B Khan > > > -----Original Message----- > From: Jim Franz [mailto:franz400@triad.rr.com] > Sent: Monday, October 08, 2001 1:35 PM > To: midrange-l@midrange.com > Subject: Re: Will Upgrading to V4R5 impact performance??? > > > Just did two upgrades this weekend. > model 600 (smallest processor) V4R3 w/128 meg memory 12 gig disk > model S10 2119 V4R4 w/256memory 32 gig disk > > model 600 took forever - about 16 hours total including cum ptf > model S10 was done in 9 including cum. > no performance degradation so far (model 600 already was slow for users) > I would recommend more memory for your box. > Also - for the 600, just OS, RPG, Dev Tools, took addtl 800 meg disk. > be sure to read the Preventive Service Plan (PSP) for this upgrade. > (not listed in release instructions)at 4.3, your machine needs to have ptf > MF25727 (product 5769999) already installed (or a supersede) > we also loaded SF99105 Group PTF for Database > SF99096 Hiper ptf's after v4r5 cum ptf > hth > jim franz > > ----- Original Message ----- > From: "Barb Nash" <Barb.Nash@phbcorp.com> > To: <midrange-l@midrange.com> > Sent: Monday, October 08, 2001 1:31 PM > Subject: Will Upgrading to V4R5 impact performance??? > > > > Hello, > > I am planning on upgrading our 9402 (model 400, feature 2131)from > V4R3 > > to V4R5 in the near future. We have 194MB of RAM and 31GB, 43% is used. > We > > are running MAPICS, with approximately 50 users, both green screen and > > client access. > > From what I have been reading on various web sites, postings... is > > that when we upgrade to V4R5 there may be diminished performance. I have > > spoken with IBM and they assure me that we will be OK, however our CE > tends > > to differ. I was wondering if anyone with our configuration has done such > an > > upgrade and what impact it has had. > > > > Thanks for your help. > > Barb > > > > > > > > _______________________________________________ > > 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. > > > > > > _______________________________________________ > 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. > _______________________________________________ > 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 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.