[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

3026.0. "UNOB and standard default delimiters (the ones for UNOA)" by ATYISA::LEBRUN () Mon Feb 24 1997 09:48

        DEC/EDU UNIX 3.1 - URGENT
        
        As you know it is possible to use the UNOB character set and 
        other default demimiters as the ones used for the UNOA 
        one(.,:,+,',?)
        
        In that case on outbound you generate:
        
        UNA+:. '
        UNB+UNOB:2+.......
        
        In a FTX segment you could have the special characters appearing 
        in the leading UNA segment
        
        Question: If such characters have to appear as simple characters 
        in such segments as FTX do they have to be preceded with the '?' 
        (release character one) or not ?
        
        I do think they have not to confuse the receiver when they have 
        to really interpret them as delimiters
        
        I know than for UNOB the special default characters are Us1, US2, 
        US3 but it's not the question here
        
        Basically the product in 3.1 doen't generate such characters 
        ahead 
T.RTitleUserPersonal
Name
DateLines
3026.1SYSTEM::NELSONDavid, http://samedi.reo.dec.com/Mon Feb 24 1997 11:2610
    
    I'm not sure if I understand the question.
    
    If the data in the FTX segment contains 
    any of the characters defined in the UNA segment, they
    should be preceeded by the release character ('?').
    
    And you are saying this is not done when you use the delimiters
    from syntax level A, with an interchange defined to be at syntax
    level B?
3026.2Yes it's exactly the case : Bug ?ATYISA::LEBRUNMon Feb 24 1997 22:176
        Yes , and the most annoying problem is that doesn't hurt at all 
        the partner that receives such FTX with the special characters 
        without '?'.
        
        That happens when we set "Character validation = yes" and I hope 
        that doesn't happen with OpenVMS