Issues Using Printer Escape Sequences in Reports

The Windows Printer Spooling mechanism does not allow escape sequences to be passed through to the printer for printing from Windows. To get around this, it is necessary to avoid using the standard printing mechanism. This may be accomplished in one of four ways:

Access the printer using the Windows Spooler direct output option. LP0 in example below.
Specify the printer port (using the Windows Spooler redirection option). LP1 below, with LPT1 redirected.
Specify the printer port bypassing the Windows Spooler. An error is generated if the port is in use. For example, LP1 below– but without redirection of the port.
Specify printer definition LP0:RAW in the Report Device Name field in $SPOOL or $SYSDEF. RAW allows you to bypass Windows spooler thereby maintaining escape sequences to be output to the print device. When processing the name length, if dev type 4 (i.e. Spool = Y and Network =Y) and if there are any report options, then the name length should include the options.

Logical Dev	Report Dev Name	Spool OK	Que Name	File Name	Phys Dev	Ntwk Dev
LP0	\\computer\printer				Y
LP1	LPT1:				Y
LP2	LP9	Y	Y
LP3	LP5	Y				Y
LP4	LP6	Y				Y
LP5	LP7	Y				Y

Printer Port Mapping/Names

The LP2 mapping above uses the standard printing mechanism, and does not support escape sequences.

The actual printer to use is specified using the PROIV Service Manager Printer Management tab.

The LP3, LP4, and LP5 examples above will be routed to the Client (because Network Device = Y has been used).

The Client’s View | Printer Mapping options for the above may be:

PROIV Printer	Windows Printer	Device/File Name	Comment
LP5	HP LJ 4M Plus on LPT1:		uses the standard printing mechanism and does not support escape sequences.
LP6	DEVICE:	LPT1:	uses the standard printing mechanism and does not support escape sequences.
LP7	DEVICE:	\\computer\printer	is spooled directly. It will support escape sequences.

Comment on this topic

Topic ID: 730073