| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
Sanity check here, please. Andrew- no snide remarks allowed! 8^) I installed a V3.0 Co-Ex system at the customer site to allow migration of critical CART-coded elements. We haver all the critical pieces fixed now. Does the following scenario sound reasonable?: 1. On co-ex system, run Store Application for all (customized) OA elements and then Package into a .FGN element. 2. Send the .FGN element as a mail message to MANAGER @A1 @NODE 3. On actual Upgrade Day, reboot with No Co-Ex startup (so its totally out of the picture) 4. Do the V2.4 -> V3.0 upgrade and the -1 patch 5. Read the waiting mail message with the saveset attachment 6. Receive/Process the .FGN element into CM on top of what was left in place after the Upgrade. 7. We now have a functional V3.0-1 system (hopefully!) All the remaining elements that our CART report flagged prior to the upgrade are non-critical that they can knock off over a period of time. Any gotcha's in the above approach? Regards, Al
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3147.3 | The procedure worked fine | GANTRY::HULL | Digital Consulting [Delivery]/Motown | Thu Sep 02 1993 05:05 | 15 |
In general, the procedure I outlined in .0 worked well. The co-ex changes were packaged and mailed to the Manager V2.4 acct. After the upgrade and the 3.0-1 patch were finished, we read the pending mail, processed the attached saveset and it was all loaded into CM. Worked very well. Unfortunately we had many other nasty issues pop up. The customer didn't have time to get ALL customizations worked out under the co-ex, so only the mandatory (CART code M,etc) were done. Things like customized CM$SITELOG forms from V2.4 and lots of "RECOMMENDED" CART-code files have caused many problems. Add EARS V2.2 and Lotus 1-2-3 for A1 V1.5 on top of all this and it's almost too much to deal with. Regards, Al | |||||
| 3147.4 | SIOG::T_REDMOND | Thoughts of an Idle Mind | Thu Sep 02 1993 15:20 | 4 | |
A customized CM$SITELOG form is a mandatory item that must be resolved
prior to the upgrade. How did this cause a problem?
T
| |||||
| 3147.5 | Hindsight is wonderful... | CUSTOM::HULL | Digital Consulting [Delivery]/Motown | Thu Sep 02 1993 17:12 | 11 |
We had only done a Remove from Live on those 2 forms, so they were still in Develop, and when we entered CM we were then seeing them, etc. Once we saw the problems, etc, we just killed off the old forms completely. In retrospect, it would have been far better to make the customer move ALL code over on a co-ex system making sure everything worked as it used to. Then move all the fixed code over on an upgraded system, using all the co-ex CM files to replace the upgraded CM files. That's basically what we did at Ford and it worked well. I had 6 months to do the co-ex move. Al | |||||