[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

3140.0. "Attachments and PEDI ??" by JOBURG::BERETTA () Tue May 27 1997 13:38

    Hi,
    
    A customer of ours has been trying to send an attachment with his
    edifact message via the PEDI gateway using EDI 2.1c on Alpha VMS. This causes the
    transmission file to get stuck in the "identifying" state and causes
    the decedi$scheduler process to crash, after which no other
    transmission files will go through until we delete the transmission
    file using sql. Should this work? I thought X435 supported attachments?
    has this been implimented in the PEDI gateway?
    
    Peter.
T.RTitleUserPersonal
Name
DateLines
3140.1We dont support multi-bodytpart SYSTEM::HELLIARhttp://samedi.reo.dec.com/Tue May 27 1997 16:069
    Peter,
    
    'identifying' is an inbound state, so the customer must be RECEIVING a
    X.435 message. We dont quite understand what you mean by attachment? Is
    this a multi-bodypart X.435 message ?
    
    Graham
    
    
3140.2Multi-Bodypart is the problemJOBURG::BERETTAWed May 28 1997 13:4518
    Hi Graham,
    
    I apologise for not being more explanatory. What the customer is
    actually doing is sending a message from an X400 mailbox to his EDI
    system as a test. He basically enters some text, then attaches some
    more text and sends this message to DEC/EDI, so yes DEC/EDI is
    receiving the message. From what I can ascertain,
    the message arrives at the decedi system with two body parts (1 and
    14). What he was trying to test, was to see if DEC/EDI could handle an
    attachment.  So I guess you have answered the question - DEC/EDI does not
    support multi-bodypart messages. 
    
    What he is now concerned about is, what if a customer accidentally
    sends a message like this. Shouldnt decedi just fail the document,
    rather than choke on it?
    
    
    Peter.
3140.3IPMT itSYSTEM::HELLIARhttp://samedi.reo.dec.com/Thu May 29 1997 11:165
    Peter,
    
    Any crash, for whatever reason, is just cause for an IPMT.
    
    Graham