Re: QCLSRC, QRPGSRC, etc... best practice?

Using this example:

* I need to set the appropriate library list with the production/test
environment.
* I need to copy all of the source members that I will be updating
into file QDEV.
* I need test data so I don't mess with real data.

In other words, I have had, until now, only one *PF-SRC. I am trying
to keep it that way, without getting ridiculous and wildly off track.

Service programs, prototypes, and binder source members are probably
going to blow my one-file solution out of the water.



On 10/29/2018 2:43 PM, Buck Calabro wrote:

But... can you describe the
convention you use for your source members? Say we're adding the Twitter
handle to a customer contact file. Particularly helpful would be:

Physical file
Service program
Prototypes
Binder source
Inquiry program that needs this service program
Display file for inquiry program

I think this is fairly representative of a simple ILE application. I see
at least 6 source members; where do you store them?

-- --buck http://wiki.midrange.com Your updates make it better!

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD