× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



what if you limit the length and width of the page segment? because I see
that one printer file is 8.5 x 11, and the other is 11 x 8.5.


On Wed, Jun 15, 2016 at 1:02 PM, James H. H. Lampert <
jamesl@xxxxxxxxxxxxxxxxx> wrote:

I'm working on a customer project involving PDF generation via AFP. It's a
reworking of an earlier version that used RPG O-specs in a flat SCS print
file, and an overlay.

I created a PAGSEG, and dropped it into the print file. According to the
PDF size, it's in there, but if you open the PDF, it's not visible.

I considered the possibility that I was somehow putting it off the page,
and so I changed the PAGSEG statement to

PAGSEG(FOOBAR/FOOTER 1 1)


I considered the possibility that the page segment source was bad, and so
I stuck a known-good page segment source file (from another customer) on
the system, and created the page segment from that. Same results.

I also tried adding the overlay from the older version to the OVRPRTF.
Same result, even though the overlay still works fine with the old version.

Both customers are on V7R1.

CRTPF paramters for this print file are
Printer device type . . . . . . DEVTYPE > *AFPDS
Length--lines per page . . . . > 8.5
Width--positions per line . . > 11
Measurement method . . . . . . > *UOM

The OVRPRTF statement is

OVRPRTF FILE(WTQUOTE) DEVTYPE(*AFPDS) PAGESIZE(8.5 +
11 *UOM) PRTTXT(*BLANK) UOM(*INCH) +
TOSTMF(&PDFPATH) WSCST(*PDF) +
OVRSCOPE(*CALLLVL)


For comparison, the OVRPRTF statement at the other customer whose page
segments work is

OVRPRTF FILE(WTQUOTE) DEVTYPE(*AFPDS) PAGESIZE(11 +
8.5 *UOM) LPI(8) PRTTXT(*BLANK) +
UOM(*INCH) TOSTMF(&PDFPATH) WSCST(*PDF) +
SECURE(*YES) OVRSCOPE(*CALLLVL)


I'm at wits end on this one.

--
JHHL
--
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.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.