Procedures/Sub-Procedures

[HwaRangRon@xxxxxxx]

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