× 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 file QSRC. Simplified lots of stuff. I know we gave up a display file
and a command having the same name as a pgm, but consistent naming
conventions handled that. In the long run that became a good thing.



On Mon, Mar 30, 2015 at 6:42 PM, <rpg400-l-request@xxxxxxxxxxxx> wrote:

Send RPG400-L mailing list submissions to
rpg400-l@xxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.midrange.com/mailman/listinfo/rpg400-l
or, via email, send a message with subject or body 'help' to
rpg400-l-request@xxxxxxxxxxxx

You can reach the person managing the list at
rpg400-l-owner@xxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of RPG400-L digest..."


*** NOTE: When replying to this digest message, PLEASE remove all text
unrelated to your reply and change the subject line so it is meaningful.

Today's Topics:

1. Re: Standard source file names? (Charles Wilt)
2. Re: Standard source file names? (Booth Martin)
3. RE: Standard source file names? (Gary Thompson)
4. Re: Standard source file names?
(Mark Murphy/STAR BASE Consulting Inc.)
5. RE: Standard source file names? (Marc Couture)
6. RE: Standard source file names? (Marc Couture)
7. Re: Standard source file names? (Vernon Hamberg)
8. Re: Standard source file names? (Vernon Hamberg)


----------------------------------------------------------------------

message: 1
date: Mon, 30 Mar 2015 16:56:38 -0400
from: Charles Wilt <charles.wilt@xxxxxxxxx>
subject: Re: Standard source file names?

That's one of those "religious" questions...

I've got a mis-mash.

I can tell you that at least one (if not all) commercial CM tools don't
care :)

Charles

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.




------------------------------

message: 2
date: Mon, 30 Mar 2015 16:19:02 -0500
from: Booth Martin <booth@xxxxxxxxxxxx>
subject: Re: Standard source file names?

My preference is one source file for related source. QARSRC (Accounts
Receivable), QAPSRC (Accounts Payable), QBRMDEVSRC (my development
source).

I really do like having the DSPF source and the CL source, and the RPG
source all right together, no bouncing around.

On 3/30/2015 3:00 PM, Bob Cagle 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.



------------------------------

message: 3
date: Mon, 30 Mar 2015 20:13:43 +0000
from: Gary Thompson <gthompson@xxxxxxxxxxx>
subject: RE: Standard source file names?

We use SRC as our standard source file name and combine "CL" and "RPG"
program, data file, display file, SQL and etc. in one source file.
We have copies of SRC for production, test and various projects.

I tend to group source members by an "application id" which I put in the
first few characters of the source member text.
For example, Text for EDI 856 ASN source members all start with "EDI856:"

BUT, we never had the luxury of a change management system, so we made-up
"standard rules" like this . . .




-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Bob
Cagle
Sent: Monday, March 30, 2015 2:00 PM
To: RPG400-L@xxxxxxxxxxxx
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.

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



------------------------------

message: 4
date: Mon, 30 Mar 2015 18:45:13 -0400
from: "Mark Murphy/STAR BASE Consulting Inc."
<mmurphy@xxxxxxxxxxxxxxx>
subject: Re: Standard source file names?

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.

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


------------------------------

message: 5
date: Mon, 30 Mar 2015 19:10:28 -0400
from: Marc Couture <couturem@xxxxxxxxxxx>
subject: RE: Standard source file names?

I uses standard source file names. It allows to have the same display file
name and the same RPG program name.

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark
Murphy/STAR BASE Consulting Inc.
Sent: Monday, March 30, 2015 6:45 PM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: Re: Standard source file names?

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.

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



------------------------------

message: 6
date: Mon, 30 Mar 2015 19:14:29 -0400
from: Marc Couture <couturem@xxxxxxxxxxx>
subject: RE: Standard source file names?

I really don't like having all sources together, with RDI no need to bounce
all over the place...


-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Booth
Martin
Sent: Monday, March 30, 2015 5:19 PM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: Re: Standard source file names?

My preference is one source file for related source. QARSRC (Accounts
Receivable), QAPSRC (Accounts Payable), QBRMDEVSRC (my development source).

I really do like having the DSPF source and the CL source, and the RPG
source all right together, no bouncing around.

On 3/30/2015 3:00 PM, Bob Cagle 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.



------------------------------

message: 7
date: Mon, 30 Mar 2015 18:42:18 -0500
from: Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
subject: Re: Standard source file names?

Hi Jerry

I find that using a change management system such as Turnover or
Implementer or Aldon takes care of the "jumping around", because they
pull source from disparate "sources" into what amounts to a unified work
space.

Having said that, I understand the draw of single source files - I am a
bit leary of this, due to the need at times for different record lengths
- many source types CAN use whatever "long-enough" record length, others
specify an exact length - QMQRY source says 91 - QMFORM source says 162
- admittedly, those are not on everyone's horizon.

Anyhow, just some thoughts.
Vern

On 3/30/2015 3:11 PM, (WalzCraft) Jerry Forss wrote:
I switched to a single source file many years ago.
All my programs follow the same naming convention like APIACTJOBC,
APIACTJOBP APIACTJOBR.
They are always grouped together.

I hated jumping around changing the source file.

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Bob
Cagle
Sent: Monday, March 30, 2015 3:00 PM
To: RPG400-L@xxxxxxxxxxxx
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.

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

Subject to Change Notice:

WalzCraft reserves the right to improve designs, and to change
specifications without notice.

Confidentiality Notice:

This message and any attachments may contain confidential and privileged
information that is protected by law. The information contained herein is
transmitted for the sole use of the intended recipient(s) and should "only"
pertain to "WalzCraft" company matters. If you are not the intended
recipient or designated agent of the recipient of such information, you are
hereby notified that any use, dissemination, copying or retention of this
email or the information contained herein is strictly prohibited and may
subject you to penalties under federal and/or state law. If you received
this email in error, please notify the sender immediately and permanently
delete this email. Thank You;

WalzCraft PO Box 1748 La Crosse, WI. 54602-1748
www.walzcraft.com Phone... 608-781-6355



------------------------------

message: 8
date: Mon, 30 Mar 2015 18:44:00 -0500
from: Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
subject: Re: Standard source file names?

Crazy for one = logical for another - what IS this world coming to?

:)

On 3/30/2015 3:52 PM, Alan Campin wrote:
I use one one source file name QSRCF. Crazy to use all those different
names and have to switch between them.
On Mar 30, 2015 1:48 PM, "James Rich" <james@xxxxxxxxxxx> wrote:

On Mon, 30 Mar 2015, Bob Cagle wrote:

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?

We use the standard IBM names for several reasons:

1. Many IBM commands already default to using them.
2. Different record lengths for different source types makes sense.
3. Improves organization for us. For example, a typical C open source
project might have header files in directories like config,
documentation
in doc, XML in xml, C code in src, etc. So splitting source code up
between several source files on the i seems logical.

James Rich

if you want to understand why that is, there are many good books on
the design of operating systems. please pass them along to redmond
when you're done reading them :)
- Paul Davis on ardour-dev
--
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.





------------------------------

Subject: Digest Footer

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
digest 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.



------------------------------

End of RPG400-L Digest, Vol 14, Issue 129
*****************************************



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.