I am notably NOT a printer output expert, but I am totally stumped why you would need to convert a PDF into an overlay. This seems like a complete waste of time and effort... A PDF is a composite document, which would already imbed any page segments and overlays referenced during its creation.
You mention about document size, I suppose in relation to the imbedded graphical overlays, but with PDF, there's no such concept as caching of page segments and overlay resources. IPDS handles that on behalf of the HPT engine, but a similar caching concept for PDFs is foreign to the PDF document specification. PDF is intended to be completely self contained, an so all resources used in the production of output is encapsulated into the PDF document.
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Marco Facchinetti
Sent: Saturday, November 30, 2013 12:59 PM
To: Midrange Systems Technical Discussion
Subject: Create an Overlay from a PDF
we have implemented the use of AFPRSC in DDS defined printer files using
single page PDF (object type *PDFSPO) and it's working, the PDF is nicely
rendered in the print out. The problem is that Afprsc behaves differently
from overlay when the spool is transofrmed in PDF using Infoprint Server.
Overlay is included by reference, AFPRSC by value. The effect is in PDF's
size: it's increased from 300 Mb to 12/15 Gb.
As usual IBM labs told "works as designed".
Since the procedure of converting PC docs using AFP driver and System I
Navigator is not user friendly (the main reason we implemented AFPRSC was
to avoid it) now I'm looking for something to automate the conversion from
PDF to Overlay.
This mailing list archive is Copyright 1997-2019 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