Conference iosg::all-in-1_v30

    Re: .1
    A1V30START.COM already does that!

    Re: .0
    Any converters you wish to use with ALL-IN-1 have to be "known" to the
    system, otherwise you'll get `privinstal' errors. Use the $INSTALL utility
    (and preferably install them /shared - though some converters can't be.)

    As for FORMAT entries, the `DDIF' & `PS' entries are good guidelines.
    However, you should leave the `Data set name' field blank.

    HTH,
       Paul.

    .0�	I installed CDA Converter Library 2.0 on a system running
    .0�	ALL-IN-1 US 3.0.
    
    As a matter of interest, did you do anything about the license
    arrangements for running ALL-IN-1 and CDA??
    
    I am trying to discover (officially, at the moment) whether CDA V2 is
    actually licensed with ALL-IN-1 V3 - so far there seems to be no
    accurate conclusion.... I was wondering if you had done anything, or if
    you have just ignored the problem?
    
    Below is some more information that you may find useful.... It talks
    about customising some of the macro modules with ALL-IN-1 V3 to include
    automatic links to CDA, as well as the link through the FORMAT file
    mentioned earlier....
    
    
    

Subject: MAILworks and WPS-PLUS / RTF

See Notes:  ALL-IN-1 - 1036,
            TeamLinks - 1061,
            DECmailworks - 2739.


Sending from TeamLinks to ALL-IN-1 V3.0:
========================================

      The document from the PC is sent as an RTF (Rich Text Format) 
      document. ALL-IN-1 V3.0 understands CDA. The CDA V2 Converter Library 
      can read and write RTF. Therefore, the logic says, ALL-IN-1 V3.0 can 
      read RTF documents.

   How can this be done?

      The document when it is delivered to ALL-IN-1 is marked as a FOREIGN 
      document. The FOREIGN text dataset is used to read this document. 
      This dataset looks to see if the document file has an RMS semantic 
      tag, and if it does, it reads the file via the CDA TEXT display 
      routine specifying the name of the tag as the name of the CDA 
      front-end to use. (This handles CDA documents created on, or copied 
      from, VMS systems).

      If the document file does not have an RMS semantic tag the dataset 
      looks at the CDATYPES table in OAET which maps file types to CDA 
      front-ends. The V3.0 version of this table has an entry for the 
      different file types supported by the CDA Converter Library V1.1. 
      E.g. AFS, CGM or DCA.

      Only after attempting the above two ways of trying to read the file 
      does the FOREIGN text dataset display the message 'FOREIGN document 
      type cannot be displayed'.

      When the CDA Converter Library V2.0 is installed, the CDATYPES 
      entries can be added to (using Customisation Management). This table 
      can have extra formats added, e.g. to process files of RTF format.

      The above change requires the ALL-IN-1 image to be re-linked, and 
      then requires no further work.

      ALTERNATIVELY:

      The FORMAT master file can be modified to include an entry for the 
      RTF documents. 
      This entry requires a LIST FUNCTION and PRINT FUNCTION script to be 
      identified and written to ensure the documents are converted and then 
      displayed correctly.

      This change requires ensuring the tag for the RTF documents is 
      consistent - or more than one entry will be required in the FORMAT 
      file.


Sending from ALL-IN-1 to TeamLinks
==================================

      The DEC MAILworks server can perform incoming translations on behalf 
      of its users.
      Each user can identify the types of documents that they are prepared 
      to receive.
      With the TeamLinks client, documents of type RTF, WPS-PLUS and 
      WORDPERFECT can be read (double clicking on the attachment displays 
      the document). Therefore all documents created within the BG network 
      should be readable.

      If, however, other document types are delivered, conversions can be 
      achieved by:


<<<<<<<<<<<<<<<<<< thats as far as I have got!! >>>>>>>>>>>>>>>>


    Cheers, Chris

    Hi, 
    
    I didn't want to create a new topic herein, I'Ve a question here coming
    up from an ALL-IN-1 training.
    
    When I install the CDA Converter Library V2.0 on a system running
    ALL-IN-1 v3.0. Must I install the CDA Interoperability Kit V1.1 again, 
    which comes with the ALL-IN-1 Kit. 
    
    Or is it enough to install only the CDA Converter Library V2.0.
    
    Regards
    Charly  

    Charly,
    
    My admittedly feeble understanding of CDA tells me that the
    functionality including in the Interoperability kit was an advance
    copy/release of functionality included in CDA 2.0.
    
    have you asked in the CDA conference.
    
    Regards,
    
    Andrew.D.Wicks

    Hello all,
    
    CDA Converter Library 2.0 has CDA Runtime Services V1.4 as
    a (minimum) prerequisite. 
    
    CDA Runtime Services is a seperate product but also integrate in:
    
    Product         CDA Runtime version  
    
    DECW055         CDA V1.3
    DECW$MOTIF010   CDA V1.5
    DECW$MOTIF011   CDA V1.6
                                                                                   
    DECWRITE020     CDA V1.4
    DECWRITEEFT021  CDA V1.4
    CDAPAT011       CDA V1.4 (with ALL-IN-1 V3.0)   
    
    So when a customer runs DECW055, not all of his converters will work.
    the releasenotes of CDA 2.0 specifies the minimum Runtime version
    for each converter. 
    
    Hope this helps,
    
    Jan

    Does anyone know if the V2.0 CDA converter library is 'supported' with
    ALL-IN-1 V3.0A (or even V3.1) yet. If it is what is the situation
    regarding licenses for INTERNAL systems.


    Thanks,

    Pete P - IME IS

    Pete,
    
    The question is more accurately phrased how to customers get it without
    having to pay for it? CDA 2.0 works fine with v3.0 -- v3.0A
    
    Ask David Holt@REO the political questions - that's why he's paid the
    big money (:==:)
    
    Regards,
    
    Andrew.D.Wicks