Conference iosg::all-in-1_v30

Hi,

>> print the code, using either GOLD E to 
>> change the data type or LPS40/LN03R/LPS20_POST as the Print Style.

Do you mean they still print the code even if you put "POSTSCRIPT" in the
data type field?

As the DSAB is WPS Plus, is the extension of the file in the file cabinet .WPL?

If you initially create the document from a .PS file, then there shouldn't be
any problems.  It sounds like these documents somehow weren't recognised as
PostScript when they were put in the ALL-IN-1 file cabinet.

Try setting the document's handling (U option form EM, FC, etc menu) to PS
and see if that fixes it.

Scott

The key question here is 'What is a PostScript document?'


There are two things to be considered when printing documents:

    .	the structure of the file, e.g. ASCII, WPS-PLUS and DDIF

    .	the information content of the file


The ALL-IN-1 Data type file cabinet attribute (sometimes called DSAB) shows 
the structure of the file.  The processing of a document in an ALL-IN-1 print
operation is controlled by its structure, and not by its content.

If the Data type (DSAB) of your document is WPS-PLUS then it seems that you
have created WPS-PLUS structured documents that contain PostScript text.
ALL-IN-1 processes these as a normal WPS-PLUS document, which means they
are considered to be revisable documents which are formatted by the
WPS-PLUS formatter. 

Also, a PostScript printer will only print files which have an ASCII
structure and contain PostScript.  You cannot send a WPS-PLUS file that
contains PostScript text to a PostScript printer because the printer does
not understand WPS-PLUS structured files. 


One solution to the problem is to set the handling of your documents to
'PS'.  This tells ALL-IN-1 that you want the document handled as
PostScript, regardless of what the data type says.  ALL-IN-1's PostScript
processing checks that files have the correct structure, and if necessary
converts them to an ASCII structure.  Therefore your WPS-PLUS structured
file will be automatically converted to ASCII structure (without changing
the content) before being sent to a PostScript printer. 

This solution is inefficient because a Print operation requires performing
a conversion.  Also, I have sometimes known it to fail because WPS-PLUS 
can reformat the text which results in invalid PostScript.


Another solution is to make sure the documents are known to ALL-IN-1 as
PostScript documents.  If you are importing the PostScript files with a .PS
file type into ALL-IN-1 using Document Transfer use the DT RVC option. 
This will create a document which ALL-IN-1 will recognize and process as a
final form PostScript document. 

The second solution is more efficient because the files can be sent
directly to a PostScript printer. 


Richard

    I'm now working on a different document.  My customer is saying 
    that he was able to print this document, without stripping the
    header information first, using GOLD D and changing the data type
    to postscript.  
    
    I changed the handling to ps and printed the document to a
    postscript queue and I got
    
      "Printer destination LN03R_B111_PS cannot print PS documents"
    
    So I then used a print style of LN03R_POST...and I it printed the code.
    
    I also tried to do a gold E and change the data type to Postscript, but
    got the 'cannot print PS documents error.'
    
    Where do I go from here?
    
    Sarah

ALL-IN-1 has never had a GOLD D option during printing.  Are you still 
using a customization done on the previous version?  Does running ALL-IN-1 
with the /NOCUSTOM make any difference?

The only affect Print Settings Data type field has is to add a 
/PARAMETERS=DATA_TYPE=<value> parameter to the print job.  It does not 
influence the way ALL-IN-1 formats and prints documents.

What is the Site Printers entry for the 'LN03R_B111_PS' destination.


Richard

    Hi,
    
    The site printers information is
    
      Printer Name:              LN03R_B111_PS
    
      Description:               LN03R
    
      Format Printer Type:       PS
      Destination Printer Type:  PRINT_SERVER
    
      Print queue:               LN03R_B111_POSTSCRIPT
    
      Printer level:
    
      Comments:
    
    
    I managed to print (a different) postscript document (with DSAB
    WPSPLUS), to this queue, by making the handling PS.
    
    At the moment every time one of my customers has a problem printing
    a postscript document (and I've lost count) I have to ask him/her to
    forward the document to me.  I want to be able to say if you do so and
    so, it will work.
    
    Any help would be gratefully received.
    
    Sarah
    

The Site Printers information looks ok.  

What is the data type and handling of documents you cannot print?


Richard

    Richard,
    
    Thanks for your responses.  I've copied a Printing User Guide that
    Reading I.S. have created, and posted it in a public drawer, so it
    should cut down on the telephone calls.
    
    As long as they remember to strip the header information, change the
    handling to to PS and print to a postscript queue with a print style
    of LN03R/LPS40_POST, it works ok.
    
    I guess we are just suffering version 2.4 to 3.0 adjustment problems.
    
    Thanks again.
    
    Sarah