TCPIP LPR/LPD separator pages?
Randy Kenyon
when printing via TCPIP LPR/LPD? I have set the number of separators in the
output queue attributes and spool file attributes to 1 but do not get a
separator page.
My LPD server will not honor a separator page request so I need the AS400 to
create one like it would for a twinax connected printer.
Thanks.
Bengt Persson
Hm, V3R1. That was a long time ago, but I remember a reverse
type of problem! We wanted to get rid of the "banner-pages" between
every spoolfile and found out that a DTAARA named QTMPLPR in
QTCP vith a "N" in position 1 stopped them!
Perhaps You have a QTMPLPR DTAARA ?
Regards,
Bengt Persson.
Randy Kenyon <rke...@idirect.com> wrote in message
news:uE3z3.8451$Vr1.2...@quark.idirect.com...
Rodney Johnson
printer writer. The ONLY option it supports is the banner page as defined in
the RFC 1179 (revised one).
If you have the ability to, move to a RISC and at minimum V3R7 and you could
use the printer driver exit example that implements a simple LPR/LPD protocol
that includes the ability to have AS/400 generated separator pages (for SCS
spooled files only). The example can be found in QUSRTOOL on a V4R4 system,
but will run and compile on V3R7. Take a look at member TSPLPRDI in file
QATTINFO. If you don't have access to V4R4, but still can upgrade to V3R7,
repost. I can send you the source for the printer driver exit example.
Randy Kenyon wrote:
> Is it possible on an AS/400 V3R1 to have the AS400 generate a separator page
> when printing via TCPIP LPR/LPD? I have set the number of separators in the
> output queue attributes and spool file attributes to 1 but do not get a
> separator page.
> My LPD server will not honor a separator page request so I need the AS400 to
> create one like it would for a twinax connected printer.
> Thanks.
--
Rodney A Johnson
Technical Team Lead for AS/400 Spool
Dept GJC
IBM Rochester, Minnesota
The contents of this message express only the sender's opinion.
This message does not necessarily reflect the policy or views of
my employer, IBM. All responsibility for the statements
made in this Usenet posting resides solely and completely with the
sender.
Randy Kenyon
Thank you for your response regrading my comp.sys.ibm.as400.misc newsgroup
question on TCPIP LPR/LPD separator pages.
If you could send me the source for the the example LPR/LPD you mention that
can print separator pages (found in QUSRTOOL on a V4R4 system, but will run
and
compile on V3R7) that would be great (rke...@idirect.com).
I don't want to abuse your generosity in helping me out but I might as well
tell you my overall objective.
I am implementing an AS400 printing solution where I have a PC that emulates
a printer. The PC will run high end print spooling and job management
software. The PC can receive print jobs via LPD or with socket printing
(which I believe is known as PJL printing on the AS400, i.e. printing to
port 2500 or 9100). For job management purposes, the PC software honors the
LPR control file, and, can extract job information from the report data
itself (ex. extract a string from line 10 and columns 15-25 of the first
page for the FORMTYPE).
My customer needs to be able to identify individual jobs on the PC that have
been received from the AS400. The best method is to capture the spool file
attribute FORMTYPE, but I could also possibly use USERDATA. The USER, FILE,
JOB, DATE and TIME spool file attributes may also be useful. Here is the
problem:
(i) The AS400 implementation of LPR/LPD does not insert the FORMTYPE or
USERDATA attributes into the LPR control file. Also, my LPD only supports
the standard control file parameters specified in the RFC1179, which means
that even if the AS400 could place more parameters in the control file I
would not be able to read them.
(ii) As you have said the AS400 with LPR/LPD does not support generating
separator pages, therefore I cannot use the PC software's ability to extract
the FORMTYPE information from the separator page since it has not been
printed.
I also believe that even if the AS400 separator page could be printed that
it normally does include the spool file attribute FORMTYPE.
So, overall I need to somehow capture the FORMTYPE or USERDATA spool file
attribute of each print job.
If you have any suggestions please let me know.
Would you know if with PJL printing the AS400 supports generating separator
page? Since it is a true As400 device it may. I would also need to define a
PJL printer that prints plain ASCII text (i.e. no PCL printer escape
sequences).
Would you know if the QUSRTOOL LPR/LPD you mention supports placing the
FORMTYPE or USERDATA in the separator page?
Sorry for the long email. Any ideas are welcome.
Thanks in advance.
Regards,
Randy Kenyon
rke...@idirect.com
Rodney Johnson <rjoh...@rchland.ibm.com> wrote in message
news:37CD6363...@rchland.ibm.com...
Rodney Johnson
your questions here, as others may be interested in the responses:
The printer driver exit example implements a subset of the LPR/LPD and uses the
build separator page API to build a separator page for SCS spooled files. The
printer driver exit example uses the banner page method for AFPDS spooled files
(and I think for all other spooled file printer device types...been a while
since I wrote it). To get the separator page built and sent down, the printer
writer must be started with FILESEP(>0), or set to *FILE (in which case only
spooled files with FILESEP attributes set >0 will have separators).
The HP PJL driver support does support separator pages. What goes on the
separator page depends upon whether you are using a separator exit program or
not (specified on device description). If you want extra attributes put onto a
separator page, you would need to write a separator page exit program. This
would also allow you to control where the attributes were located on the page.
An example of a separator exit program (the source) resides in QUSRTOOL. Check
out member TBSINFO in file QATTINFO (available on all currently supported
releases).
As to the printer controls, that is controlled by the Workstation Customizing
object and MfrTypMdl parameters specified on the output queue (for remote
writers) or the printer device description (for printer writers). The system
workstation customizing object that may work for you is QWPDEFAULT in QSYS.
You will have to set your MFRTYPMDL parameter to *WSCSTxxxx.