RE: upgrade from 4.2 to 4.4 -- MIDRANGE-L

If you always treat upgrades as a big deal, they never will be.  Since I
started here 6.5 yrs ago, we have upgraded from a B40 @ 2.2 to a F50 @ 3.1
to 3.2 to a 510 @ 3.7 to a 720 @ 4.3  This is the main system only.  Our
transaction processor has gone from a D10 to a 200 to a 400.  The 200 went
to a D/R site that was then upgraded to a 170.  This company started on a
S36 17 years ago.  The worst upgrade was from the F50 to the 510 in a side
by side upgrade.  (We had an operations staff at that time that did not know
much more that how to run the applications and do report distribution.)

IBM has always done an excellent job when it comes to upgrades and
documentation.

Christopher K. Bipes     mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst   mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.         http://www.cross-check.com
6119 State Farm Drive    Phone: 707 586-0551 x 1102
Rohnert Park CA  94928 Fax: 707 586-1884

If consistency is the hobgoblin of little minds, only geniuses work here.
Karen Herbelin - Readers Digest 3/2000


-----Original Message-----
From: b shaw [mailto:crashshw@ix.netcom.com]
Sent: Thursday, April 06, 2000 9:37 PM
To: MIDRANGE-L@midrange.com
Subject: RE: upgrade from 4.2 to 4.4


On a 620-2180 with 63% disk usage :
I just did an 4.3 to 4.4 upgrade. We used an earlier (3 day earlier) Full
backup and (previous night)  Differential backups to cutdown our total
downtime. Plus, I only did a SAVSYS after the install as we're a 24-7 Call
Center and I had to limit the downtime. My system was down from 8:30 PM and
up at 1:45AM with the SAVSYS. Plus, we had to account for all our TCPIP
services starting up, etc. The upgrade was absolutely smooth, no problems,
whatsoever.

Read the Installation manuals, talked to the CE a little. Checked off the
task lists, made sure our apps were supported under 4.4. No problems. Even
added SQL to the system. Went like a charm; of course, we were still a
little nervous. You'd think that after going from 2.3 to 3.1 and 3.1 to 3.2
and 3.2 to 4.3, it wouldn't be such a big deal.....

-----Original Message-----
From: owner-midrange-l@midrange.com
[mailto:owner-midrange-l@midrange.com]On Behalf Of dbryant@banpharm.com
Sent: Tuesday, April 04, 2000 2:13 PM
To: MIDRANGE-L@midrange.com
Subject: Re: upgrade from 4.2 to 4.4




Don,  about how long did your conversion from 4.3 to 4.4 take?  We are
getting
ready to upgrade this weekend.  We are currently on a 500 box.

Just curious.....




|--------+----------------------->
|        |          Don          |
|        |          <dr2@cssas400|
|        |          .com>        |
|        |                       |
|        |          04/04/2000   |
|        |          04:24 PM     |
|        |          Please       |
|        |          respond to   |
|        |          MIDRANGE-L   |
|        |                       |
|--------+----------------------->
  >--------------------------------------------------------|
  |                                                        |
  |       To:     "Dawn L. Detz" <ddetz@sgi.net>           |
  |       cc:     MIDRANGE-L@midrange.com, (bcc: Darlene H |
  |       Bryant/Banpharm)                                 |
  |       Subject:     Re: upgrade from 4.2 to 4.4         |
  >--------------------------------------------------------|








Dawn,

4.3 > 4.4 was smooth...just make SURE you follow the CUM install
instructions...you need to lod/apy one before you do the package...

Don in DC

On Tue, 4 Apr 2000, Dawn L. Detz wrote:

> Have an AS/400 620 - 1 processor.  I run JDEdwards (8.1.2) on it.  Has
> anyone run into any problems w/ the 4.4 upgrade.  I'm not doing anything
> extra like adding drives or disk part.
>
> Any tips would be appreciated..
>
> +---
> | 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
+---



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