×
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.
At least one of the commercial packages I have worked with uses non-standard source file names. Any CMS he would attempt to sell to customers with source like that would have to support non-standard names.
Mark Murphy
STAR BASE Consulting, Inc.
mmurphy@xxxxxxxxxxxxxxx
-----Bob Cagle <bcagle@xxxxxxxxxxx> wrote: -----
To: "RPG400-L@xxxxxxxxxxxx" <RPG400-L@xxxxxxxxxxxx>
From: Bob Cagle <bcagle@xxxxxxxxxxx>
Date: 03/30/2015 04:00PM
Subject: Standard source file names?
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.
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
