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



One source file, QSRC. In addition to the ease of navigating to source of
different types by keeping it in the same source file, it helps ensure that
object names are not duplicated across different object types.

- Dan

On Mon, Mar 30, 2015 at 4:00 PM, Bob Cagle <bcagle@xxxxxxxxxxx> wrote:

A friend of mine has gifted me a copy of his home-grown change management
tool, but it requires the standard IBM names for source files, and has
hard-coded them in all of the tool's programs.

He was shocked when I informed him that I don't use the standard names,
and so this tool won't work as is.
I was shocked that he didn't allow for different names since the original
intent was to sell this tool on the open market.

So I'm curious - what is your stance on source files? Do you use the
standard IBM convention QDDSSRC, QRPGSRC, QRPGLESRC, etc., etc.?

Or custom names?

Single or multiple files for different source types?

Why?



Thanks

Bob Cagle
IT Manager
Lynk, Inc.

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

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.