Conference iosg::all-in-1_v30

3264.0. "mrx2.2g,a1, bodypart 14 question" by MSDOA::DAVISST () Mon Sep 13 1993 16:43

Customer is in midst of expanding from ALL-IN-1 to LAN-based mail using 
MAILbus 400 as the switch.  The following is a surprise that concerns 
them.  Customer is asking for confirmation that the following is correct.

  The only type of ALL-IN-1 documents that will be converted to binarydata
  bodypart 14 are those ALL-IN-1 documents with ...

     ... data type of FOREIGN with a sequential file organization that have 
           either a stream record format or a fixed length record format.

That is, it is not possible to send ALL-IN-1 documents that have data type
of WPCORP as binarydata bodypart 14.

(I suppose that they can do a customization to make the document of the 
correct type before attaching and sending to others, but that will make 
them need to know who is on which mail system, etc -- this is not the 
best solution.)

Any confirmation, ideas, help?

Thanks.

    Wouldn't this be more appropriate in the MAILbus conference on node
    FORTY2?
    
    regards,
    
    Andrew.D.Wicks

    I believe that this is an ALL-IN-1 question concerning the use of DEC
    bodypart 1 (or the like).  The question is getting ALL-IN-1 to permit
    an attachment to be treated as a binary file and still be accessible
    from ALL-IN-1 -- such as with WPCORP.
    
    Thanks.

    We're looking at this problem right now for various reasons. What we
    want to do is to get WPCORP using binary file for transfer rather than
    a specific bodypart type (in fact they hijack the DecText one at the
    moment).  

    Customer will be willing to elevate with WPCORP -- might help your
    discussion.  Who are you talking to?