
Xprint F.A.Q. Document revision 10 (16.09.2008)
Page 52/89
You can check it with the "netstat –a | grep 9999" command, which returns you the list of the
connections
using this port.
K.5 How to define a RSO printer using the protocol LPD ?
Configuration of RSO printers
Connecting a printer to BSD-LPD :
A printer that is connected to a BSD-LPD must be defined with the SPSERVE statement
ADD-SPOOL-DEVICE or MODIFY-SPOOL-DEVICE. To do this, the following operands are
used. These operands are described in the "SPSERVE" [21] manual.
DEVICE-ACCESS = *TCP-ACCESS(...)
ACCESS-TYPE = *LPD(...)
LPD-PRINTER-NAME = *STD / <c-string 1..8>
,FROM-PORT-NUMBER = <integer 0..1024>
,TO-PORT-NUMBER = <integer 0..1024>
INTERNET-ADDRESS = *STD / <alphanum-name 1..32> /<composed-name 7..15>
PORT-NAME = *STD / <alphanum-name 1..8>
Interdependencies with other operands :
SYNCHRONIZATION=*PRINTER is not rejected but simply ignored. RSO automatically assumes the setting
SYNCHRONIZATION=*NETWORK. RSO does not receive any infor-mation direct from the printer.
The dialog takes place exclusively between RSO and the BSD-LPD, i.e. synchronization is not possible between
the sending of two messages (within the same print job). Similarly, POLLING=*YES is not rejected but simply
ignored.
RSO automatically assumes POLLING=*NO, as printers administered by BSD-LPD cannot return information to
RSO.
DISCONNECTION=*YES or DISCONNECTION=*NO is likewise not rejected but simply ignored. RSO
automatically
assumes DISCONNECTION=*FORCE, in order to request the closing of the connection at the end of each print
job.
Completeness of printouts, restarting printouts :
BSD-LPD printers and servers are supported only by the transfer of print jobs to the BSD-LPD server.
This is because RSO cannot monitor the processing of the print jobs. As soon as RSO receives a print request
that is to be forwarded to a BSD-LPD server, the first thing RSO does is to create a temporary file containing
all the data to be printed (header page, user data, trailer page, ...). This file is used to determine the value for the
size of the print job. Once the temporary file has been created, RSO checks whether there is a BSD-LPD
printer/server ready for a print job. If so, RSO reads the print data from the temporary file and sends it to the BSD-
LPD
printer/server together with certain BSD-LPD protocol commands. If a DMS error occurs while creating the
temporary
file, the print request is returned to the KEEP queue. If the print request is rejected by the BSD-LPD printer/server,
RSO resumes processing of the print request from the beginning.
Configuration of RSO printers
If the print job is processed without errors, RSO clears the connection to the BSD-LPD printer/server and
considers
the print job to have been successfully completed. Never-theless, the BSD-LPD printer/sesrver does not check
through its internal print request queue until the connection to RSO has been cleared. This means that RSO has
no possi-bility of monitoring the printing of the data once it has been passed to the BSD-LPD printer/server.
Warning
When printing to BSD-LPD protocol printers it is not possible to guarantee either a correct restart of the print
operation
or a complete printout of the data. This is because RSO has no possibility of communicating with the printer.
As a result, it may happen that RSO regards a print job as successfully processed even though not a single page
Komentáře k této Příručce