Re: Main Procedure -- 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.

Kurt,

I tend to name my main procedure for what the _program_ does. So if the program's purpose is to, for example, print the "aged trial balance" report, then I call my main procedure something like "AgedTrialBal".

It doesn't matter that the main procedure does very little on it's own (just calls subprocedures) -- it does still do something, even if that something is just use subprocedures in the right way to each the programs' goals.

On 4/7/2014 10:09 AM, Kurt Anderson wrote:

For those who use the Control Statement (H-Spec) MAIN, do you usually give the main procedure a name unique to the program, or do you have a standard name such as mainProcedure? I find that sometimes I struggle to name the main procedure. In the program I'm working in now I settled on mainProcedure, which made me wonder how other people were naming their main procedures.

Kurt Anderson
Sr. Programmer/Analyst - Application Development, Service Delivery Platform
[cid:image002.jpg@01CD16F9.25D27630]
web: www.customcall.com<http://www.customcall.com/> | email: kurt.anderson@xxxxxxxxxxxx<mailto:kurt.anderson@xxxxxxxxxxxx>

A Division of Enghouse Systems Ltd.<http://www.enghouse.com/> (TSX:ESL)

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.