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

Conference rocks::dec_edi

Title:DEC/EDI
Notice:DEC/EDI V2.1 - see note 2002
Moderator:METSYS::BABER
Created:Wed Jun 06 1990
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:3150
Total number of notes:13466

3134.0. "2.1d fbr$runtime.exe" by JOBURG::BERETTA () Wed May 21 1997 15:26

    Hi,
    
    I think there is a bug in the 2.1d fbr$runtime.exe. After I had
    upgraded an Alpha VMS 6.2 system running edi 2.1c to 2.1d and object
    broker 2.5a to 2.7-10. We experienced the following error when doing a
    filebridge send:
    
    $    file send fbr$top:[fbr$tables.cyberbill]CYBERBILL_SEND.FBO -
         INTERNAL:[EADS_OUT]EDG00000000000020.;2 -
          /appl=cyberbill-outgoing /doc=cyberbill /partner=EDGARS-CYBERBILL
    -
          /test=LIVE
    %CLI-F-SYNTAX, error parsing 'REPROCESS'
    -CLI-E-ENTNF, specified entity not found in command tables
    
    When I changed back to the 2.1c fbr$runtime.exe image this problem went
    away.
T.RTitleUserPersonal
Name		DateLines
3134.1This is documentedJOBURG::BERETTAWed May 21 1997 18:1745
    Oops,
    
    I just noticed the following statement, no reasons given, in the
    $$readme.txt for 2.1d. (my humble apologies, I skim read this before
    doing the upgrade and missed that phrase)
    
        DO NOT INSTALL THIS IMAGE ON A V2.1C SYSTEM!
    
    
    ---------------------------------------------------------------------------
        Image                   :   SYS$SHARE:FBR$RUNTIME.EXE
    
    ------------------------------------------------------------------------------
    
        Identification          :   DECEDI V2.1D
        AXP Link Date/Time      :   14-May-1997 14:48:49.90
        VAX Link Date/Time      :   14-May-1997 16:30:37.99
    
        Added to Directory Date :   14-May-1997
        Added By                :   Richard Johnson
    
    ->>> DO NOT INSTALL THIS IMAGE ON A V2.1C SYSTEM!
    
        14-May-1997
    
        This patch fixes the fault that can occur after a map fails to send
        one document; further documents may not be processed correctly.
        
        Also fixed in this patch: The previous patch would produce no
    output
        data on incoming if a map has set context to an area i.e. heading
    
        26-Feb-1997
    
        This image corrects a problem occuring during inbound mapping.
    
        If a map 'B' sets context to a segment (its context segment) that
        is defined in the doc-def as being at least two levels lower than
        the segment to which the previous map 'A' was set, then under
    certain
        circumstances data can be ignored during mapping. In an attempt to
    
    ==============================================================================