Conference iosg::all-in-1_v30

    From DCL try:
    
    $ VIEW [/INTERFACE=DECWINDOWS] wpl-file-spec/FORMAT=WPL
    
    and see if the presentation is acceptable.  Don't recall, but the
    WPL-to-DDIF converter may be supplied with DECwrite rather than
    ALL-IN-1.
    
    dh�

    Thanks for your reply.
    
    Well, that's what we considered first, but the conversion does not meet
    our expectations. What the customers want, is to save *a* document
    (regardless what format) in the archiving system, and retrieve/print it
    some times later (months, years) with the same attributes/layout.
    		
    Any other ideas?
    
    Thanks in advance.
    Viktor

It is not possible to call ALL-IN-1 functions from outside of ALL-IN-1.

When you have an archived .WPL file why can't you run ALL-IN-1 and DT RV
(Document Transfer, Receive file from VMS) it into ALL-IN-1 in order to
read or print it?  

WPS-PLUS/VMS has 'invokeable' components which can read and print WPS-PLUS 
files.  These are not supplied as part of ALL-IN-1.


Richard

    Richard,
    
    	The question of the Callable interface to ALL-IN-1 came up because
    	the archiving system can be started from ALL-IN-1 or from $,
    	so the DCLMAILBOX/OAMAILBOX technique of the subprocess to get
    	ALL-IN-1 functionality is not always useable. 
    
    	ALL-IN-1/WPS-PLUS is just one of many sources from where documents
    	can be stored into the archiving system. ALL-IN-1 users can 
    	store WPS-PLUS documents through an interface provided by the 
    	archiving system. But what about all the users which have no 
    	ALL-IN-1 account or started the application from $ and 
    	wish to view/print a certain .WPL document? 
    
    	If I understand correctly, we have the following choices:
    
    	o	Only one access point to the Application (through ALL-IN-1)
    	o	Sell WPS-PLUS/VMS
    	o	Use VIEWer
    	o 	Do not store .WPL but convert to ASCII before archiving
    
    
    	Thanks,
    	Viktor		
    

re: .5

>    	o 	Do not store .WPL but convert to ASCII before archiving

You would not necessarily need to convert to ASCII but could convert to
any supported text data set (e.g. DX).  If you wanted to write your own
data set action routine then you could create your own data set and
make sure that it was in a format that could be read by all of your users.

This, of course, is not a trivial task but if you are interested in all
the possibilities it may be worth considering.  See the
ASIAGO::ALL-IN-1_CLI conference if you are interested in pursuing this
further.

Just a thought ...

John

    Bit rushed, but basically correct.
    
    Store document in original .WPL format or converted to DDIF
    
    1) For viewing:
    
    	a) Use CDA Viewer (e.g. $VIEW/....)
    	b) Run up ALL-IN-1 or WPS-PLUS to view
    	c) Print a hardcopy ;^)
    
    2) For printing:
    
    	a) Convert to text/postscript/etc. via CDA library (e.g.
    	   $CONVERT/DOCUMENT ...) and print.
    	b) Pass document to ALL-IN-1/WPS-PLUS background formatter for
    	   formatting and printing (model after printing subsystem).
    	c) Pass request to batch job running ALL-IN-1 for processing.
    
    Please note that what is actually seen as a result of any of these is a
    final form document.  Some more faithful than others.

    Well, lots of ideas, ways...
    
    Personally I prefer the idea of storing the document as .WPL, 
    using VIEWer for viewing and the background formatter for printing. At
    least they would get the document in its original layout as hardcopy.
    
    Lets try.
    Thanks to all.
    Viktor