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



Ok, I'm glad I'm not alone in not subscribing to the single repository of prototypes.

After reading the response of what people do and why, I feel comfortable that the method I'm using isn't entirely against the grain. (Not to say other methods are wrong.)

Thanks for the responses,
Kurt
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of David Gibbs
Sent: Thursday, June 30, 2011 9:25 AM
To: RPG programming on the IBM i / System i
Subject: Re: Copybooking PRs

On 6/30/2011 9:11 AM, Kurt Anderson wrote:
In this list and in presentations I often hear about people putting
_all_ of their prototypes into _one_ copybook. This has always
boggled my mind and I feel like maybe there's something I'm not
grasping.

I put all the prototypes for a single service program into one source member. This way they are logically grouped together.

So if I have a service program 'IMENV', I have a copy book 'IMENVPR'.

david
--
IBM i on Power Systems - For when you can't afford to be out of business
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.