Re: QCLSRC, QRPGSRC, etc... best practice? -- RPG400-L

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

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