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 |
I have 2 upgrade schedules. Firstly,I want to describe the customer environment. One customer have used ALL-IN-1 V2.3 local language and EARS V1.1 and customzed most parts. And we tried to upgrade ALL-IN-1 V2.4 local language(HANGUL) and after installation I tested the new image. But I got some errors like belows. I can't use CSZ,ESM,MM options on the SM2 menu,and I got some undefined symbol errors. If I use digital area only (ALLIN1/NOCUSTOM) , and I can use the above options and any symbol error doesn't occur. How can I sove the above problem? And the oter case is like belows. Another customer have used ALL-IN-1 V2.3 local language and MESSAGE ROUTER on VAX 4000. And they want to change the system to VAX 6000 series and want to use ALL-IN-1 V2.4 and MESSAGE ROUTER and customized parts. In this case , I don't know the easy way to migrate the VAX 4000 to 6000. Pls let me show the guideline describing installation procedure and backup procedure and order. Hope your help ASAP. - DaeHee
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
1689.1 | EARS V2.0? | CESARE::EIJS | All in 1 Piece | Fri Oct 30 1992 08:33 | 25 |
DaeHee, Sounds familiar to same type of problems with ALL-IN-1 V2.3 and Lotus installed, and then an upgrade to V2.4 would give error messages due to missing symbols. As far as I remember the SM and SM2 menus use new symbols (or better, ALL-IN-1 V2.4 removed some menu symbols). I don't know which ones, but these are the ones I have on my (unpatched) V2.4: SM2.FLX ------- ;;OA$_SM_MO_MANAGE_PRINTERS;; MPR ;;OA$_SM_MO_MAINTAIN_FORMATS;; MFT ;;OA$_SM_MO_MESAGING_MANAGEMENT;; MM ;;OA$_SM_MO_COMMS;; COM ;;OA$_SM_MO_SYS_CUSTOM_MANAG;; CSZ ;;OA$_SM_MO_MANAGE_MASTER_FILES;; MMF I guess when you install EARS V2.0 this problem will be solved Ciao, Simon |