Conference iosg::all-in-1_v30

    Georges,
    
    Having no A's is definitely very strange but isn't something that
    should prevent you from upgrading. Perhaps there is something wrong
    with the SDC elements file on that system - were there any errors
    during the CART run - either written to the screen or logged into
    the CART report. what happend if you go to ADE (access digital
    elements) and try and select ACTIONSEL FRM ENGLISH.
    
    Having no K's is good and i'm not sure I understand why you were
    expecting any.
    
    Regards,
    
    Andrew.D.Wicks
    
    

    
    George,
    
    Did any message appear like:
    
      %CART-I-PROC xx:xx Processing deleted element <name> <type> <area> 
    
    If not, then something must have gone wrong before this part of the
    CART and the CART should have 'stopped' in the first place.
    If these messages appeared, but no elements with status A were
    reported then the only reason why this might have happened is that all
    deleted elements in V3.0 (as mentioned in CM$CART$BASE$CHANGES*.DAT)
    did have an entry in CM$SITELOG, meaning they had been modified.
    Obviously these elements then should have had status "H" (element found
    in CM$SITELOG as modification of a Base element, and Base element will
    now be deleted). However, this sityuation seems a bit odd.
    
    Ciao,
    
    	Simon

Hello Andrew, ciao Simon,

Thanks for your assistance. 
For the moment the customer is working on a CoExistent installation. But the
upgrade has still to be done and the problem is still there.
 
   The status of the A-element problem is as follows:

CM$SITELOG	 does not contain any e.g ACTIONSEL, AICLOS etc
cm$sdc_elements	 does contain e.g. ACTIONSEL, AICLOS etc


In addition to the lack of status A elements we discovered other anomalies:

The customer has modified e.g. his MAIN FRM. I think somewhere in the CART 
report this element should appear with some status (,may be as status P) 
since MAIN is one of the modified BASE elements.

Checks:
Looking more closly at CM$CART$BASE$CHANGES*.DAT the customer reported:
- It is only 138 BLOCKs in size (3525 on our reference system). 
- The result of a dump/record is empty!
 The file has a 'Revised:' date of "24-Feb-1993" although on the 5-Mar-1993 
the CART has been rerun to check if the changes applied on B and C status 
elements were successful.

As [ALLIN1.SITE]CM$CART$BASE$CHANGES$OA$V30$PRIMARY.dat is created during the 
CART installation the lack of completeness could indicate some anomalies in
the kit.


Do you have some suggestions for further checks, how to locate/remove 
the problem?


Kind regards
Georges


Follow some lines of the CART installation logfile:

a) around %CART-I-PROC xx:xx Processing deleted elements 
   NB: There is no such statement at customersite!
 
b) around MAIN FRM
   The element does appear with the same number as in CM$SITELOG

 
* Which option do you wish to perform [1]: rc

   You have chosen the CART pre-installation option. Please specify the
   installation type you wish to pre-check.

   Your current system is ALL-IN-1 V2.4. Using the FULL ALL-IN-1 V3.0 kit, 
   the CART can be run to pre-check the following installation types :- 

	(1)	Check before FULL upgrade of ALL-IN-1 V2.4 to ALL-IN-1 V3.0
	(2)	Check before upgrade of existing ALL-IN-1 V2.4 language

 
* Which option do you wish to perform [1]: 1
 
* Enter language code for this installation (2 characters): us
%A1LUS-I-RELANK, Restoring the LANGUAGE kit savesets
%VMSINSTAL-I-RESTORE, Restoring product save set B ...

    If you wish to install a dialectal variation of ENGLISH language,
    enter the code for the dialect component you wish to use.  If you do
    not wish to install a dialectal variation of ENGLISH language,
    then accept the answer of NO_DIALECT.
 
* Enter dialect code for this installation (5 characters) [NO_DIALECT]: 
%A1LUS-I-RESCARTSS, Restoring ENGLISH CART kit saveset
%VMSINSTAL-I-RESTORE, Restoring product save set L ...
%A1LUS-I-RESCARTSS, Restoring ENGLISH CART datafiles saveset
%VMSINSTAL-I-RESTORE, Restoring product save set M ...
%A1LUS-I-RUNNINGA1, Running ALL-IN-1
%CART-I-CRE 10:35 Creating CART datafiles
%CART-I-FILL 10:35 Building site directories
%CART-I-FILL 10:35 Listing site elements
%CART-I-INIT 10:35 Initializing CART environment
%CART-I-READ Reading base changes for deleted elements
%CART-I-CHECK 10:35 PROCESSING A1WPSPLUS_LOGIN COM SHARE NUMBER = 1
%CART-I-SCNNG 10:35 Scanning A1WPSPLUS_LOGIN COM SHARE

%CART-I-CHECK 10:35 PROCESSING BA FRM ENGLISH NUMBER = 2
%CART-I-SCNNG 10:35 Scanning BA FRM ENGLISH
...


-> b)

%CART-I-CHECK 10:40 PROCESSING MAIL_DIR_CONVERT DO SHARE NUMBER = 56
%CART-I-SCNNG 10:40 Scanning MAIL_DIR_CONVERT DO SHARE

%CART-I-CHECK 10:40 PROCESSING MAIN FRM ENGLISH NUMBER = 57
%CART-I-SCNNG 10:40 Scanning MAIN FRM ENGLISH

%CART-I-CHECK 10:40 PROCESSING MORE$SCROLL$KEYS$INDEX FRM ENGLISH NUMBER = 58
%CART-I-SCNNG 10:41 Scanning MORE$SCROLL$KEYS$INDEX FRM ENGLISH

%CART-I-CHECK 10:41 PROCESSING MUA_CANCEL_TRANSFER COM SHARE NUMBER = 59
%CART-I-SCNNG 10:41 Scanning MUA_CANCEL_TRANSFER COM SHARE
%CART-I-STATS 10:41 Writing MUA_CANCEL_TRANSFER COM SHARE with status E
%CART-I-STATS 10:41 Writing MUA_CANCEL_TRANSFER COM SHARE with status E
...


%CART-I-CHECK 10:50 PROCESSING WPPXAVER DO SHARE NUMBER = 174
%CART-I-SCNNG 10:50 Scanning WPPXAVER DO SHARE
...

    138 blocks is the size you get from the initial sizes in the FDL if you
    create a new file.
    
    Graham

    Once the file has been "created" during the installation, it should
    never be modified. All subsequent accesses to it should be read only.
    
    The V2.4 upgrade version of the file in the kit has the following
    creation and modified dates:
    
    	V24$CM$CART$BASE$CHANGES.DAT  16-MAR-1992 14:19  4-AUG-1992 11:48
    
    The file name in the kit is changed during the installation.
    
    It looks like someone has either recreated this file from the FDL, or
    we somehow gave you an empty one. Perhaps we always do that for fresh
    installations - Co-ex is mostly a fresh installation.
    
    Graham

    Form MAIN should have status code P.  It's a non-mandatory change.
    
    You seem to have a bad CART base changes file.  Why not copy the
    version from your system onto the customer's system and try to rerun
    the CART there?
    
    Tony

    Thanks for your assistance.
    We will rerun the CART after having exchanged A1LUS030.M
    The file at customer site was only of 522 BLOCKs  in size (instead of
    9450 BLOCKs)
    
    Georges

    Georges,
    
    	Which kit does the customer have?   This sounds like he has a
    British kit, but has installed using the English language i.e.
    no dialect was specified.
    
    The A1LUS030.M saveset in the British kit contains empty cart files.
    When the British Dialect is selected, populated cart files are taken
    from the A1DUS_GB030.A saveset.  
    
    If the customers V2.4 system is British, the English cart files from
    'your' A1LUS030.M will give incorrect results.  This is because the
    language is part of the key used to look up each element. 
    
    
    Martin.