One difference between Gumbo (while I really like) and your HP printer is
that
there is both the HPT and the Workstation Customizing Object. They only come
into use during the printer process, not the generation of the spool.
Also, CHRSIZ is for *ipds printers (from infocenter: Use this record- or
field-level keyword to expand the width and height of a record or field.
CHRSIZ is valid only for IPDS printers and only for printer files with
device type *IPDS or *AFPDS specified.
I suspect your WCST is changing the margins, causing the overlap.
If you change the CHRSIZ to instead use a font - this may do it for you (try
point sizes 11,12,13,14 etc to see what you get and 2305 for bold - 2304 is
helvetica).
A R $PRT12B FONT(2304 (*POINTSIZE 12))
A DATA 20 1
Try this without the WCST.
hth
Jim Franz
----- Original Message -----
From: "Steve Richter" <stephenrichter@xxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, February 13, 2013 2:00 PM
Subject: *afpds spooled file not printing correctly on ip attached printer
I have an *AFPDS spooled file, that is produced using a DDS PRTF, The
PRTF uses the CHRSIZ keywork to print the report heading in a large
font. And then the BARCODE keyword to print a barcode. When I use
Gumbo to email this spooled file to me as a PDF document the document
prints as it should. However, when I print the spooled file to a
connection type *IP output queue the output is off. Text overlaps
other text. The heading line with the CHRSIZ keyword does not print.
But the barcode prints.
Why would this *AFPDS spooled file not print correctly on an *IP
attached laser printer? When I WRKOUTQD I see that host transform is
set to *YES and there is a workstation customizing object for an HP
printer.
thanks,
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
