Conference iosg::all-in-1_v30

    Eileen,

>1. Was I imagining the fact that the .PS file kept its extenion under 2.3?

    You're OK, you don't need to see the shrink :-) You weren't imagining
    things.

>2. If I wasn't imagining, why has it changed to .FGN under 2.4?

    This is due to V2.4 sending PostScript files through Message Router
    as `foreign' files. Unfortunately, sometimes the receiving end does
    not realise it's really PostScript, and keeps the document as a .FGN
    file.  FWIW, this problem has been fixed in V3.0 (now shipping in
    Europe!)

>3. Why is there an extra line atop the received .TXT file?  

    Pass.

    Cheers,
        Paul.

    My recollection is that the extra line added at the top of the .TXT
    file is due to an 'improvement' in V2.4 to not corrupt or lose the
    WPS-PLUS rulers.  This 'feature' caused a bit of grief to sites using
    templates which depended upon having the correct line count as I
    recall.

    I am not aware of anyway to make this blank line go away but there may
    have been something about in in the V2.3 conference which is probably
    still out on the network unless it has caught the eye of the BO types.

    Have fun,
    don

So are we saying that all files with the .PS extension and the PS DSAB that go
 through the Message Router get converted to .FGN and FOREIGN respectively
and son't get converted back, or are they supposed to get converted back but
usually don't?

I'm already finding quite a large number of users are ringing up with "I can't
print my postscript file" and they have to be talked through sending it to
VMS and then reimporting it.  As the number of postscript files being mailed
around the system increases the impact time-wise of this could be enormous.

And no, we can't upgrade to 3.0 yet - we can't even consider it until a German
language version exists.

Jenny

You shouldn't need to send the document back to VMS and then re-import it.  I
went through the same problems, and found that if you change the document's
handling to PS (thanks to Richard Newland for explaining it all to me!), using
FC U (it's called "Update Index Information" at the UI for some obscure reason),
ALL-IN-1 should then treat it as a PostScript document.

Disclaimer: it works in V3.0, dunno about 2.4 though!

Scott

>Disclaimer: it works in V3.0, dunno about 2.4 though!

It doesn't work with 2.4 - tried that a long time ago!  The DSAB stays as 
foreign and it won't print.

Jenny

Re: .5 and .6

If you follow the suggestion in .5 your are changing the Handling and not 
the data type (or DSAB).  Therefore the data type will remain as FOREIGN.

In what way did it not print?

Do you have a 'PS' entry in the FORMAT master, and what does it contain?


Richard

    .2
     
    Don, what I ended up doing is using a .DX instead of a .TXT extension
    and Message Router left it alone.  I then did a copy from blahblah.DX
    to blahblah.TXT.  The new .TXT file didn't have an extra line
    
    .3, .4, etc.
    
    I copied the blahblah.FGN to blahblah.PS and had no problems printing.
    I realize that this is different from the problems described in that I
    am doing this with procedures I wrote rather than having the users do
    it interactively.  
    
    It looks as if the file extension is as important as the actual file
    format.
    
    Eileen

> In what way did it not print?

All I get is an END OF JOB page with the error message:

   15-APR-1992 15:20  %LPS-W-UNDEF, undefined: Name not known - offending 
 	command is Text
   15-APR-1992 15:20  %LPS-E-FLUSHING, Rest of job (to EOJ) will be ignored

(These errors also come up on my ALL-IN-1 screen.


The entry in the format file is as follows:
 
 Name:                 PS
 Description:          PostScript
 Default filename:     .PS
 Object extension:
 DSAB type:            PS
 Template Filename:

 Edit function:        N/A
                       Initialization File:
                       Purge Count:         3
                       Editor Type:

 List function:
 Print function:       DO PRINT_PS
 Standard formatting?  N

 Compile Command:
 Template Form:
 

Re: .8

The FORMAT master information for PS is correct.

The error messages from the printer appear to indicate that the PostScript 
file has been corrupted.  Could you do the following to find out when the 
corruption occurs.

1.  Check that the file as stored in the file cabinet is printable 
    PostScript.

    This can be done by getting the name of the file, making a copy of the 
    file, and from VMS printing it to a PostScript printer.


2.  If the file is printable then do the following to see how it gets 
    corrupted.

    1.  Do a $STOP/QUEUE on the printer queue

    2.  From ALL-IN-1 print the message, and wait for the job to be 
    	submitted.

    3.  Do a $ SHOW ENTRY/FULL, which will display the filenames of the 
    	print job.  Examine the PostScript file to see how it differs from 
    	the file cabinet file examine in step 1.



Richard

I have been away on holiday since I last replied and have forgotten which 
document causes the problem.  Perhaps we can resume this discussion next time 
the problem occurs (which it does semi-regularly).

Jenny