Conference iosg::all-in-1_v30

    
>>    I am actualy doing some tests for a customer demo and came to the
>>    "Internal error in File Cabinet Server" message. This appends when i
>>    want to refile a attached received document i sended to myself. This
>>    document is supposed to be a DDIF document with live links, at least
>>    the original. It seems that when sending the document, it is still
>>    beeing packed in DOTS format (like in V2.4), even if asking for pack or
>>    unpack document after typing FA (File attachment as document).
    
    
    Firstly, DDIF documents that have live links and are packed in the
    ALL-IN-1 filecabinet will have a DOTS extension (at least my tests
    suggest that). If the DDIF document is stored unpacked then you will
    have the two separate DDIF documents in you filecabinet (but linked). 
    
    Sending the root DDIF file will cause a pack operation to take place,
    incorporating the linked DDIF into a DOTS document for sending.
    
    Unfortuntely, right at this minute I can't retest any further as my
    machine has just be taken for something. However, I have seen FCS
    errors similar to the ones you describe for some other more obscure 
    operations. I can't really say much more until my machine returns!
    
    
    Any comments Bob ?
    
    Kevin.
    
    
     
    

    Hi Kevin,
    
    I just found the solution to my problem. As the FCS error was
    reproduceable all the time, i come to the idea that the FCS image needs to
    be relinked. ( this is recommanded somwhere when CDA is installed
    afterwords) The next question was how to do it? I found the answer in
    STARS:
    
    The FCS is re-linked by running A1LNKDRV in the same way as for any
    other ALL-IN-1 image, however the FCS will only be linked during an
    installation or if the VMS version has changed since the last time
    it was linked.
    
    The VMS version last time it was linked is determined by a symbol
    defined in OA$BUILD:A1LINK.ANS. To force the FCS to be linked edit
    this file and change the definition of the symbol A1$LAST_VMS_VER.
    
    
    Since the relink, it is working perfectly.
    
    Felix

    
    
    Felix,
    
    BTW - you can also relink the FCS separately by running
    OAFC$SERVER_LINK.COM (In OA$BUILD_SHARE). 
    
    However, the process you mentioned is perhaps the cleaner way of doing 
    things as it relinks all the necessary images.
    
    Kevin.
    
    

    Kev,
    
    Don't suppose you know off-hand whether the FCS has to be relinked
    after installing CDA v2.0 - if you had already had CDA v1.1 of course
    
    regards,
    
    Andrew.D.Wicks

    
    It is not quite as simple an answer as one would think, the safe 
    answer is yes, relink, never hurts and could save trouble.
    
    The real answer is, it depends on what you had before putting the
    new installation on.
    
    CDA is a sharable image, so as long as you had a previous
    cda$access.exe on the system, the server image will startup and 
    use either the one that is physically installed (with the INSTALL
    utility) or the most recent one in sys$share.
    
    If you did not have a CDA version before the installation then
    by all means you MUST relink the server. This is due to the way the
    server handles CDA symbol resolution when CDA is not present. Basically
    it links in a dummy object file that contains the symbols we need but
    no code. Since this is an object file, not a sharable image, the server
    must be relinked to get rid of it.
    
    Like I said, it never hurts to do the relink and it only takes a 
    couple of seconds.
    
    --Bob
    

    Bob,
    
    Thanks - I was fishing for enough info so that I could get Faith to
    "ghost-write" a STARS article for me (:==:).
    
    I was just trying to figure whether there would be any incompatibilty
    problems with a FCS running linked against a cda$access from CDA v1.1
    when a customer had upgraded to CDA v2.0 (since this doesn't require
    any part of ALL-IN-1 to be relinked)
     
    I guess that the answer is that there are no problems that we yet know 
    about?
    
    Regards,
    
    Andrew.D.wicks