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



On 9/26/2023 3:49 PM, Howie, Bill wrote:

This question may have been asked a thousand times here on the list. Is there a native way to embed printer file compile options within the printer file source so that one doesn't always have to look at the current printer file object to see how it was compiled and then match that? It would be SO much simpler. Thanks for any info!

The definition of 'native' is a matter for discussion, but some ideas:

Create a CL program for each *PRTF which handles the DLT/CRTPRTF with the proper options. One possible implementation is to put them in a separate library, named the same as the *PRTF.

You could drive this with a single *CMD front end that runs your own specific commands by creating the appropriate one and feeding it to QCMDEXC. This would more or less automate PDM and RDi compilation.

If you use RDi, the excellent iSphere plugin has a STRPREPRC command that will allow you to embed parameters into the source itself, and create the appropriate CRTPRTF command at compile-time.
https://isphere.sourceforge.io/help/html/utilities/strpreprc/usage.html
He also has a standalone version: http://www.tools400.de/English/english.html

Scott Klement has a tool he calls BUILD which does the same thing: https://www.scottklement.com/build/


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.