RE: How do I share an open file handle across procedures?

I feel for you.  That standard is about as sensible as mandating all inline
code in a monolithic source member. Only advantage I can see is avoiding
having to deal with signatures in service programs.  One size fits all never
is as good as it sounds. <g>

> -----Original Message-----
> From: Doc [mailto:Doc6502@yahoo.com]
> Sent: Friday, February 14, 2003 10:06 AM
> To: rpg400-l@midrange.com
> Subject: Re: How do I share an open file handle across procedures?
> 
> 
> DeLong, Eric wrote:
> > Ok, so this begs the question, why wouldn't you define the related
> > procedures in the same module?  File resources can easily 
> be defined in the
> > service program, if defined in a single module. 
> 
> Don't beg Eric, it's degrading ;)
> 
> I have no problems with defining the related procedures in a single 
> service program as you suggest.  However, it's a shop 
> standard at this 
> client site that you break down procedures as far as they can 
> go-- the 
> ideal is one function per source member.
> 
> -Doc
> 
> 
>