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



James:

Are you using the PAGESIZE parameter on the CRTDSPF command to set the page size?

This would seem to be a job perfectly suited for using Alan Campin's COMPILE / MAKE tool, available at:

http://www.think400.dk/downloads/

With this tool, you can include the CRTDSPF command right in the source code, as comments, near the beginning of the member,, to tell the COMPILE tool how to "MAKE" the corresponding object ...And that way, you can, in effect, "hard-code" the desired page size "in the source"... so it stays with the source, and then instead of using PDM option 14, you create a PDM user defined option like "CR" for "Create" or "MK" for "Make", to invoke Alan's COMPILE tool. -- This also works with WDSCi and RDi, etc. -- /"And Bob's your Uncle..."/

Hope that helps,

Mark S. Waterbury

> On 3/10/2015 6:32 PM, James H. H. Lampert wrote:
I may have mentioned that, in my latest PDF generation project, I've taken my first step into externally-described print files, and my first step into AFPDS.

But I have a question: It seems like every time this print file gets regen'd from PDM, unless I explicitly set the paper size, I end up with a print file that's set up for 132-column greenbar.

I don't see a way to specify the paper size in the source member. Is there a way, that I'm just not seeing?

--
JHHL


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.