From: Deepak Mohapatra To: All
I have an AS/400 with V1R2 installed. I would like to do the following:
Swap out all the DASD and add new, faster 9336's.
Install V2R1M1 of OS/400.
Restore all the user profiles, configurations and data files.
I plan to approach this the following way:
1. Do a SAVSYS and SAVLIB *NONSYS before everything.
2. Vendor would then swap out the existing DASD and install new DASD.
3. Install the operating system as described in the manual Licensed Programs & New Release Instal-lation Guide (SC41-9878-00), Chapter 5.
4. Install all the licensed programs.
5. Restore all my profiles, communications configurations, etc.
6. Restore all my data files.
Is there anything I am missing or do I have to take special considerations because my present level is Release 2?
From: Molex Inc. To: Deepak Mohapatra
While you are doing your saves, you also need to perform a SAVDLO. To review the steps IBM recommends for recovering your system from a disaster when a reload is necessary, consult Appendix B of the Basic Backup & Recovery Guide for V2R1M1. It really helped us.
From: Pete Hall To: Deepak Mohapatra
I'm not sure, but I think you might end up restoring old versions of some IBM code if you try to restore your system after upgrading to V2R1M1. I would think it would be safer to upgrade to your new release first, then save everything (you can run the option to "Save the entire system" on the BACKUP menu), then do your DASD swap and restore from your "entire system" save (you can IPL from the tapes that it creates). This is essentially the procedure that IBM recommended for a B to E upgrade which I did a couple of months back, which also involved a DASD swap.
From: Karon Clancy To: Deepak Mohapatra
I would proceed a little slower. If possible, you should install the operating system before you swap out the DASD. What I mean is install the operating system one week and the next week install the DASD. Too many steps together is just asking for problems.
From: Willie Moore To: Deepak Mohapatra
I agree with Karon. We went from a B45 to an E60. Our CE suggested we do it in stages. The first was a complete system backup, then the operating system upgrade. After we ran for two weeks, we then went to the new DASD and E60. With the changes to the operating system, it was nice to have some time to work through any problems.
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online