RE: Procedures/Sub-Procedures

[Alan Campin <Alan.Campin@xxxxxxxxxxxxx>]

>> It's only a
>> couple of lines of code, but I thought it made sense to put it into >> a
sub-procedure. 

Excellent idea!

>> a sub-procedure. However, I can not define a data area in a sub-
>> procedure

Just define the data area in the D specs at the top of the module. Data
areas like files are global. Your storage to read it into can be local to
the procedure. 


-----Original Message-----
From: Chris Bipes [mailto:rpg@cross-check.com]
Sent: Tuesday, November 16, 1999 12:02 PM
To: 'MIDRANGE-L@midrange.com'
Subject: RE: Procedures/Sub-Procedures


It is so nice to "EVAL CoName = GetCoName(CoNumber)" so I would say it is
worth it.  Just create a full blow module to retrieve the data area or what
ever.  Put that module into your binding directory or add it to a service
program.  Yes it was worth it for me.  Now to teach other programmers here
how to use all this stuff and document it up the ying yang.

Christopher K. Bipes     mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst   mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.         http://www.cross-check.com
6119 State Farm Drive    Phone: 707 586-0551 x 1102
Rohnert Park CA  94928 Fax: 707 586-1884

*Note to Recruiters
Neither I, nor anyone that I know of, is interested in any new and/or
exciting positions. Please do not contact me.


-----Original Message-----
From: HwaRangRon@aol.com [mailto:HwaRangRon@aol.com]
Sent: Tuesday, November 16, 1999 9:22 AM
To: MIDRANGE-L@midrange.com
Subject: Procedures/Sub-Procedures


We are starting the next release of our software, which is all in ILE RPG.
Now, I want to start taking common functions out of programs, change them
into sub-procedures accessed via a service program(s). Put the service
programs in a common binding directory and away we go..

One common function that all of our programs do is to get the current
company that they are working with by accessing a data area. It's only a
couple of lines of code, but I thought it made sense to put it into a
sub-procedure. However, I can not define a data area in a sub-procedure
(this also makes sense). 

So, I would have to create a full blown procedure (I assume not accessed via
a service program). So, my question is, Is this still worth doing - given
that it's only a couple of line of code retrieving a data area?

Anybody have any comments?

Ron 
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---