|
Good choice... i'm sure it's PROBABLY ok to do it during the DST change weekend, but it would be far from my first choice! Especially since this is more of a major DST change... it's obvious that some vendors are still scrambling and their suggested fixes are still changing every so often (Domino suggestions changed several times in the past month). Jerry Adams <jerry@bwwholesal e.com> To Sent by: Midrange Systems Technical midrange-l-bounce Discussion s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx> cc 03/09/2007 09:49 Subject AM Re: Upgrading from 5.3 to 5.4 this weekend Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com> I have been spending the better part of this week reading the Memo to Users and the Software Installation manuals. Those that do this kind of thing over and over for a client base probably have the steps memorized by now, but I only do it every couple of years - and the gotcha's seem to change with every release. Speaking to the image catalogue question, the Software Installation manual (SC41-5120-09) has a synopsis of the process. That's the way I intend to go, but there are a few more steps than "just" ADDIMGCLG. At least in my case I have the advantage of having a backup server to which I'll install V5R4 first. If it blows, I should be able to recover V5R3 from my backups and start over. But my preferred method is to write down all of the steps from the Memo and SW manuals in sequence, desk check them over and over often making changes/additions. I like to let the plan sit for a day or two and then come back to it; helps me see if the plan is as understandable as I thought originally! And, even if I was ready, this would not be the weekend I would choose for the install. First thing Monday morning I'll check to see if the new DST PTF's work as advertised. * Jerry C. Adams *IBM System i5/iSeries Programmer/Analyst B&W Wholesale Distributors, Inc.* * voice 615.995.7024 fax 615.995.1201 email jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx> ChadB@xxxxxxxxxxxxxxxxxxxx wrote:
If you are asking those questions on a Thursday evening, it does not
sound
like you are ready for the upgrade this weekend! Not meaning to offend, but the advice given below is the bare minimum of preparation... take a step back and get as familiar with the IBM docs and process as you can!
"Jim Franz"
<franz400@xxxxxxx
r.com>
To
Sent by: "Midrange Systems Technical
midrange-l-bounce Discussion"
s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx>
cc
03/08/2007 07:43
Subject
PM Re: Upgrading from 5.3 to 5.4 this
weekend
Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>
You need to read to documents - one is the Memo to Users and make sure
you
don't have a show-stopper. 2. There are explicit pre-install planning docs to go through, which lead you though how to prepare a machine, including the pre-ptfs that are INCREDIBLY important (can u say crash & restore whole system from
backup?).
Plan on spending hours getting "ready". Have you done a release upgrade in the V5 days? There are way too many variations on machines, products, lpars, x-series, etc for us to point you thru this - you gotta follow the IBM path, as boring as it is... Ask questions if you don't understand the docs. Should be a "Start Here...: page with the cd's. and I would not be running a release update during the hours in the Sun
am
time shift. jim franz ----- Original Message ----- From: "Ron Adams" <rondadams@xxxxxxxxx> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: Thursday, March 08, 2007 7:26 PM Subject: Upgrading from 5.3 to 5.4 this weekendA few questions. First, is this a good idea for this weekend considering the time change? Second, I was reading some other threads and I kept seeing "pre-upgrade PTFs". What is this referring to? Third, I have CDs, can I load them in as Image Catalogs? If so, how do I do it? Is it as simple as "QSYS/ADDIMGCLGE IMGCLG(V54RUPG) FROMDEV(OPT01)"
?
- Ron Adams -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx 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@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
_____________________________________________________________________________
Scanned by IBM Email Security Management Services powered by MessageLabs. For more information please visit http://www.ers.ibm.com
_____________________________________________________________________________
ForwardSourceID:NT00065E96
-- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. _____________________________________________________________________________ Scanned by IBM Email Security Management Services powered by MessageLabs. For more information please visit http://www.ers.ibm.com _____________________________________________________________________________ ForwardSourceID:NT00065F0E
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.