[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

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

1147.0. "Reduce Customization Time ?" by TOOHOT::PRIKLY::MEAGHER (The New Contributor System) Thu Jul 30 1992 15:55

Howdy.
    
My customer has asked me to look into any useful ways to reduce the time 
he spends applying customizations to ALL-IN-1 after version upgrades.

We understand that there will be some new capabilities with CART, but 
are unsure if they will really be a timesaver.

This customer has about 165 forms, of which 1/2 are customized.  Most 
customizations are additions.  It took this customer about sixty (60) 
hours to apply all the customizations (to a running, production system)
in trickle-mode over two weeks from V2.3 to 2.4.  

Will CART easily flag these custom forms differences in the SITE area as
compared with the DEC area's V3.0 forms ?  

Will it be easy (or easier than running VMS DIFFERENCES to identify where 
to apply the customizations ?  

Do the V3.0 forms follow the V2.4 forms named data paragraph organization 
..e.g. the code, is it organized the same ? 

Is there any existing (printable) on-line documentation on CART ?  All I
could find was the Bookreader On-Line Documentation CD, under the
heading of ALL-IN-1 Management, entitled, "ALL-IN-1 Differences between
ALL-IN-1 V2.4 and ALL-IN-1 V3.0", and Chapter 5 of the ALL-IN-1 V3.0
Installation Guide, Part I. 

Thanks in advance for any pointers.  In the meanwhile, I'm considering 
proposing a single user ALL-IN-1 license (~$700) so they can load 
ALL-IN-1 on another of their (non-ALL-IN-1) 6000 systems and use that 
for a test environment.

/Kent
T.RTitleUserPersonal
Name		DateLines
1147.1Only hardcopyAIMTEC::WICKS_ADEC Mail Works for ME sometimesThu Jul 30 1992 17:5615
    Kent,
    
    The CART book (AA-PNZLA-TE) only shipped hardcopy so it's not on the CD
    and you might like to obtain a copy as it might answer some of your
    questions.
    
    The CART's main purpose is to flag conflicts between a DIGITAL v3.0
    change and a customer's customisation. If the customer has 60
    customised forms and none of them are in conflict then they don't
    have to reapply their customisations at all.
    
    Regards,
    
    Andrew.D.Wicks
1147.2CM Differences, Merge elements, VBC, etc.47215::EIJSAll in 1 PieceFri Jul 31 1992 09:0729
    Hi Kent,
    
> Will it be easy (or easier than running VMS DIFFERENCES to identify where 
> to apply the customizations ?  

If your elements are modifications of standard OA code then CM allows you to 
run differences between different files. Yes, it uses VMS differences, but it 
has a nicer UI ;-). 

In case CMS is available you can use the ME / MBE options (Merge with element / 
Merge with Base element) to merge differences between files into your code. The 
MBE option requires the new (V3.0) or old (v2.4) Base elements to be available 
as some place, either in CM (in a different application area) or on VMS. This 
is a very short explanation, but it's just a pointer.

If you ran the CART before the upgrade, a file called 
[ALLIN1.SITE]CM$CART$BASE$CHANGES$OA$V30$xxx.DAT will be available and can be 
accessed via the option VBC on the CM main menu. This is the on-line access to 
(written) changes as will appear in the Full report also.
 
> Do the V3.0 forms follow the V2.4 forms named data paragraph organization 
> ..e.g. the code, is it organized the same ? 

Yes.

Ciao,

	Simon
1147.3Atlanta, next month, anyone?SIOG::T_REDMONDThoughts of an Idle MindFri Jul 31 1992 13:515
    Maybe your customer should attend the ALL-IN-1 Advanced Technical
    Seminar in Atlanta next month?  I'm sure we can solve all their
    problems if we meet there...
    
    Tony ;-)
1147.4Mod's to CM to beautify difference resultsSANFAN::LESLIE_DAGreetings & SolutionsFri Jul 31 1992 19:5023
    I did some custom work at Macy's where I customized the V2.3 CM scripts
    that perform differences.  Specifically, I modified them to print out
    using WPS-PLUS boilerplates (and output formats) that include headers,
    etc.  Also, I modified the text file used for performing form
    differences to use the first part of the description file (which
    specifies form text, highlighting, and field locations and names) and
    then use the named data text formatting as used in editing named data. 
    
    With these 2 modifications, you could perform differences on forms and
    really see where the differences exist.  Though this doesn't really
    handle the situation of what changed with V3.0, it does answer the
    question of what did I change from the current release.
    
    The other step I did was to extract from the V2.4 kit (we were
    upgrading from 2.3 to 2.4) the files marked customized in CM.  I did
    the same differences tests (from the live area) to obtain a list of
    files that would require further modifications.  Granted, Macy's only
    had about 40 items TOTAL in the CM database, but this mechanism proved
    to resolve all customization issues BEFORE the upgrade was performed...
    
    If there's interest in this, I'll post the saveset location for
    retrieval...
Dan
1147.5Order the CART Guide/Single User Lic for TestingSMOKN::MEAGHERThe New Contributor SystemSat Aug 01 1992 22:2212
re -.1 - I've recommended they order the guide ($36)
   -.2 - Thanks for the detail on the report name, etc and on the similar format
	of the new forms
   -.3 - As with most customers these days, travel/lodging for training not 
	identified as absolutely mission-critical will not be approved :>(

Thanks to all for your immediate inputs.  I've recommended the single-user
license for the test environment, too.

Regards.

/Kent