Conference iosg::all-in-1_v30

    If it's getting occasional upsidedown ?'s then it could be the serial
    port setup, and the printer setup don't quite match. check baud, parity
    stop and no of bits.
    
    Richards

    There have been similar problems with other characters on a PC.  Most
    DEC display/print devices will display/print the rest of an "escape"
    sequence once they receive a character that is not part of a known
    sequence.  
    
    For example, let's say you send the printer "ESC [AB\".  If "ESC [A" is
    the start of a known sequence, but "ESC [AB" is not, then the printer
    will simply display the "\", but not the "B".  This sounds like what is
    happening.  "Why?" is the real question.  If, for example, the terminal
    line is set to Wrap (SET TERM/WRAP), then the VMS terminal could be
    inserting a CRLF in the middle of the sequence.  Generally, this won't
    happen if the terminal is set to /SCOPE.  It could be the VXT that is
    intercepting the sequence, just sending a "\" to the printer, or it
    could be the printer getting the wrong information.  
    
    You might want to look at the notes, probably in the archived
    conference, which deal with "6i" being displayed on the printer when
    using a PC.  Extract the directory from note 3 of that conference and
    search it.  
    
    I hope that I have not just restated the obvious, but it is dangerous
    to assume that people know this much.  I've never used a VXT.
    
    Ben

I don't have any solutions to your problem or access to a VXT 2000 but
perhaps explaining how ALL-IN-1 performs port printing might help to
isolate the cause of the problem. 

An ALL-IN-1 print operation normally involves formatting revisable
documents, such as WPS-PLUS, to create listing files which can be printed. 
The listing files are then processed in different ways depending on the
type of printer destination, e.g. port printer, queued printer, document,
etc. 

For port printing ALL-IN-1 calls the script OA$DO:WPPPORT.SCP, and this
uses an API function called COPY_TO_PORT to print listing files to an
attached terminal port printer. 

The COPY_TO_PORT function sends the control sequence <ESC>5i to the
terminal to turn the port printer on, and if a VT125 terminal it also sends
<ESC>6i to turh the screen off.  The listing file is then read and output
to the terminal. When complete <ESC>4i is sent to turn the port printer
off, plus <ESC>7i for a VT125 terminal. 


You can perform a COPY_TO_PORT function directly by doing the following 
from DCL.

	Create a simple ASCII text file (FILE.TXT)
	
	$ ALLIN1/NOINIT
	Enter CMD: COPY_TO_PORT 'FILE.TXT'
	Enter CMD: EXIT
	$

If you still get the extra '/' character then this shows that problem is 
occuring in the COPY_TO_PORT function, and not somewhere else in ALL-IN-1.
COPY_TO_PORT is designed to work with DEC ANSI terminals.  It may be that 
the VXT 2000 does not completely emulate a DEC ANSI terminal, or requires 
some other way of turning the port printer on and off.


Richard
	

I tested the procedure:

	$ALLIN1/NOINIT
	Enter CMD: COPY_TO_PORT 'filename.txt'
	Enter CMD: EXIT

and the output printed to my LN03 without the "\" or an additional trailing page.
Per Note 351.3, it appears that the COPY_TO_PORT function is not the problem, and
that something else in ALL-IN-1 is the cause.

Any more ideas?  Thanks.

Regards,

Steve

Re: .4

The next thing to try is:

    1.  Run ALL-IN-1

    2.  Use DT RV to import the ascii text file into ALL-IN-1 and create an 
	ASCII document.

    3.  Print the ASCII document to the port printer - is the '\' character
	generated?


This will show if some other part of the ALL-IN-1 print operation is 
generating the '\' character.


Also, has any part of the Print sub-system been customized, in particular 
WPPPORT and WPPRINT?


Richard

Re:  .5

I tried the suggestions in Note 351.5 and the results are as follow:

	- DT RV a .txt file into a WPS Doc	=> '\' & extra page appear

	- Converted it to ASCII			=> worked OK (i.e. no '\')
						   but no bolding (as expected)

Also,

	- In printing a WPS Doc to destination 'Port' or 'Port LA100' the
	  the output appears as in the ASCII test above.

My system manager informs me that he has not customized WPPORT or WPPRINT.

I hope this helps.

Regards,

Steve

From the information in .6 it seems that the problem occurs only when a
document is formatted with the WPS-PLUS formatter with an LN03 device type. 

The listing files created by the WPS-PLUS formatter for LN03s contain
control sequences to initialize and set-up the LN03 printer.  Perhaps the
VXT 2000 is reacting to one of these control sequences, and is either 
changing some characters or generating some additional characters.  To 
determine if this is the case you could do the following:

1.  Create a simple WPS-PLUS document.

2.  From ALL-IN-1 print this document to FILE with a format style of LN03.

3.  Use the <COPY_TO_PORT function to print the file created at step 2 to 
    the port printer - the problem should occur.

4.  Use ANALYZE/RECORD to see the control sequences sent to the printer.

5.  Create files which selectively eliminate the control sequences and 
    print them to the port printer to see if a particular sequence causes
    the problem.
 

Richard

Re: .7

I completed steps 1 - 3 suggested in .7 and the problem did occur.  I could
not find a VMS 'ANALYZE/RECORD' command to perform step 4.  Has the command
been renamed?

Regards,

Steve

    I think Richard meant $DUMP/RECORD ... 

    You might find it helpful to have handy the LN03 book that describes all
    the escape sequences.

    Cheers,
        Paul.

Re: .8 and .9

I meant $ DUMP/RECORD.


Richard