Re: Service program / procedure design and naming conventions -- RPG400-L

Subject: Re: Service program / procedure design and naming conventions
From: Booth Martin <booth@xxxxxxxxxxxx>
Date: Fri, 4 Aug 2017 16:50:36 -0500
List-archive: <http://archive.midrange.com/rpg400-l/>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: "RPG programming on the IBM i \(AS/400 and iSeries\)" <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

My choice is to use F4 in the name. Thats pretty well understood by everyone, and if you make it the standard it will be picked up real fast.

Parm = SCRFIELD;
F4Org(Parm);
SCRFIELD = Parm;

should be all you need. Why would you need to test? I am not clear as to what "Do stuff" stuff there is ever to do? You're just filling the field for the user. Any validity checking would need to be done when the field is processed, regardless of whether the field was filled by F4 or from the keyboard.

On 8/4/2017 4:37 PM, Brian May wrote:

As to how to name it, you can ask 5 different developers and get 5 different answers.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Service program / procedure design and naming conventions , Jon Paris

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.