| 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 |
Does anyone have any neat programs for packaging 2.3 elements together
as a 3.0-ready CM "application"? I have over 400 new modules that I
want to move en masse to my 3.0 test system. (After testing, of course,
I will use the standard 3.0 functions to package the application for
transport to the upgraded system.)
Thanks for any help.
Bruce
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2390.1 | No? | SWAM2::RHODEWALT_BR | Pillage pillage, loot loot | Mon Mar 15 1993 18:37 | 3 |
No one has had to do this?
Bruce
| |||||
| 2390.2 | No tool, just workarounds | UTES09::EIJS | Simon Eijs @Utrecht; 838-2558 | Thu Mar 25 1993 07:54 | 29 |
Hi Bruce,
Sorry, I'm a bit behind in notes.
I'm not aware of such a program.
As you know there used to be an ASSET called GIP which could package
V2.3/V2.4 CM applications, but GIP won't 'unpack' the elements
correctly under V3.0. Neither does ALL-IN-1 V3.0 understand a package
from GIP.
I think there are a few alternatives:
1) Move V2.3 to your test system, upgrade to V3.0 and (with some post
processing) your application should still be available to be tested
2) Either create a new Application and the necessary application areas
(or use the OA application) and copy your V2.3 elements into the
Receive areas. Then include them into CM via 'CM AM RV (Receive from
VMS). Then move them to Live (again) as on V2.3.
3) I won't mention GIP as it is retired.
I guess these are not easy workarounds, but they would prevent writing
a tool just to do that.
Ciao,
Simon
| |||||