| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 1020.1 | Found a work around | GIDDAY::SETHI | Man from Downunder | Fri Jul 10 1992 05:42 | 41 | 
|  |     Hi,
    
    I have managed to get a hold of OA$DATA_LLV:DATASPELL.DAT from a
    Version 3.0 kit.  I copied this file into OA$DATA_LLV and I can spell
    check.
    
    The information you need to enter when you call the form DATASPELL is
    :-) 
    
                         Spell Information for Supported Languages
    
        Language Name : BRITISH
    
        Dictionaries Folder Translation : ENGLISH DICTIONARIES
        Personal Dictionary Translation : BRITISH PERSONAL
    
        Language Name Translation : BRITISH
    
        Personal Dictionary File Spec : [.DOC0]PERSONALBRI.LGP
    
        Old Language Entry : ENGLISH
    
    For the US kit it's
    
        Language Name : AMERICAN
    
        Dictionaries Folder Translation : ENGLISH DICTIONARIES
        Personal Dictionary Translation : AMERICAN PERSONAL
    
        Language Name Translation : AMERICAN
    
        Personal Dictionary File Spec :
            [.DOC0]PERSONAL.LGP
    
        Old Language Entry : ENGLISH
        
    ALL-IN-1 Version 3.0 is still not installed I cannot tell you why
    because a few people may have to put a paper bag on their heads ;-). 
    It's all this walking upside down that causes the problems ;-) ;-)
    
    Sunil
 | 
| 1020.2 | Scripts are quite OK in OA$LIB! | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Fri Jul 10 1992 08:52 | 13 | 
|  |     Re .0
    
    <<<< solve this problem ?   The Scripts to look at are LNGSPLSC2 and
    <<<< LNGSPLINI according to Customisation Management sub-system these are
    <<<< ment to be DO script but they are not found in OA$DO but OA$LIB.
    
    For the record, there's no absolute requirement for DO scripts to be in
    OA$DO. Only the scripts that we want to be included in the TXL because
    they are used very commonly are in OA$DO. There's loads (811!!) of
    scripts in OA$LIB...
    
    Graham
    
 | 
| 1020.3 | Incorrect location | GIDDAY::SETHI | Man from Downunder | Mon Jul 13 1992 00:41 | 29 | 
|  |     Hi Graham,
    
    I got the following error message when I did a CM ADE SEL CO, for the 
    elements LNGSPLSC2 and LNGSPLINI.  
    
    %OA-I-LASTLINE, Error occurred when copying element to development area
    
    Setting the trace on gave the following information
    
    114     ! [SCP/TRACE] COPY CM$SDC.DISK_LOCATION[$CM_SDC_KEY]
    #CM_FILENAME << CM_SDC_EDIT 0030
    115     ! GET Symbol: $CM_SDC_KEY
    115     !      Value: LNGSPLINI                              DO  
    BRITISH
    115     ! DSAB Name: CM$SDC                          Requests :GET_BY_KEY
    115     ! GET Symbol: CM$SDC.DISK_LOCATION[$CM_SDC_KEY]
    115     !      Value: OA$DO_BRITISH:LNGSPLINI.SCP
    115     ! GET Symbol: #CM_FILENAME
    116     !      Value: OA$SITE_DEV_BRITISH:LNGSPLINI.SCP
    119     ! Text DSAB Name: TXT$TXL_DO                      Requests :GET_NEXT
    119     ! [SCP/TRACE] .IF OA$STATUS NE 1 THEN .GOTO NOT_COPIED <<
              CM_SDC_EDIT 0031
    
    As you can see it's looking for OA$DO_BRITISH:LNGSPLINI.SCP where as
    the script is actually in OA$LIB_BRITISH.  All I want to point out is
    that Customisation Management system is pointing to the incorrect
    location.       
    
    Sunil
 | 
| 1020.4 | Oh, I see! - Yes, there does seem to be a problem... | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Mon Jul 13 1992 09:07 | 19 | 
|  |     Sunil,
    
    Sorry, I misunderstood your problem. More research reveals that:
    
    	V2.4: LNGSPLSC2.SCP was in OA$LIB, and LNGSPLINI.SCP was in OA$DO.
    	      Unfortunately, the SDC file shows them both being in OA$DO...
    
    	V3.0: Both scripts are put in OA$DO, and the SDC file agrees.
    
    So this explains part of the problem, but it doesn't fit your facts
    completely! I don't have ready access to the V2.3 files without
    trawling through the CMS, but maybe the scripts were moved between V2.3
    and V2.4. We don't handle the updating of SDC element records too well
    in that case.
    
    Obviously you can easily update the SDC elements file to match the
    "real" world!
    
    Graham
 | 
| 1020.5 | The final chapter | GIDDAY::SETHI | Man from Downunder | Tue Jul 14 1992 01:07 | 19 | 
|  |     Hi,      
    
    Final chapter to the story ...... :-)
    
    You must have the INTERNATIONAL Language Name in DATASPELL otherwise
    you get the Null Pointer problem.   The following is required.
    
        Language Name : INTERNATIONAL
    
        Dictionaries Folder Translation : INTERNATIONAL DICTIONARIES
        Personal Dictionary Translation : INTERNATIONAL PERSONAL
    
        Language Name Translation : INTERNATIONAL
      
        Personal Dictionary File Spec : [.DOC0]GLOBAL.LGP
    
        Old Language Entry :            <------- This is blank
      
	Sunil
 |