|
> From: Scott Mildenberger > > Joe, > > Before you try this you have to investigate how this works. If I remember > correctly, if it finds the data area it ignores any H specs that > are in the > program. A better option is to have the default H specs you want > in a /copy > (which can be located through library list), this way allows you to add > other H specs in the program on an individual basis as needed. Thanks for the heads-up, Scott. I was really more thinking out loud than really suggesting anything, and I'm sure you're probably right. My problem is that, for historical reasons, I really dislike /COPY members. The biggest reason is that I write tools that modify other programs, and /COPY members tend to make that job a lot harder. But since my dislike is purely personal and I recognize that fact, I rarely voice my opinion on the issue. More and more, though, as RPG begins to require large amounts of standard code (primarily in the realm of prototypes), the old /COPY concept is coming back into vogue, and I may have to rethink my personal position. No matter what, though, I *STILL* don't like CRTRPTPGM <grin>. Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.