×
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.
So I had this what I thought to be great idea to dynamically attach signatures to overlays - as opposed to the current process of having hundreds of overlays - one for each signature.
So I created an external printer file with keywords of PAGSEG, OVERLAY, etc.
And write to the external printer file instead of an internal printer file.
Everything works beautifully - I only need one overlay now, and the signatures are simple to add to the system as *PAGSEG instead of creating a new overlay for each signature.
During testing, I got burned.
Apparently a few old *IPDS printers are still out there - the external printer files cannot use the DDS OVERLAY, ENDPAGE, PAGSEG commands.
Does this mean I have to drop this project and go back to one overlay for each signature?
Any idea how I can get around this?
Apparently the old process did an OVRPRTF FRNTOVL(name-of-overlay-with-signature-attached) which IPDS printers could handle.
Or maybe IPDS printers can't handle an overlay at all?? - even as part of an OVRPRTF ???
Is it possible to use an *IPDS printer and combine the overlay with the *pagseg signature at run time? It doesn't seem possible without an external printer file, which *IPDS printer doesn't seem to support.
Thanks!
______________________________________________________________________
This outbound email has been scanned for all viruses by the MessageLabs Skyscan service.
For more information please visit
http://www.symanteccloud.com
______________________________________________________________________
As an Amazon Associate we earn from qualifying purchases.