Re: Procedures within procedures?

[Dave Murvin <davem@xxxxxxxx>]

Thanks Joep.  This is what I was looking for.  The manuals were clear on 
where to add the procedures within a program, but not too clear on 
multiple procedures in a single module.

Dave

Joep Beckeringh wrote:
> Dave,
>
> Your problem is that you are trying to define a procedure within another 
> procedure. That is not possible.
>
> Instead of:
>
> GetFileInf B
> GetFileInf PI
>    <code>
>    BitIsOn B
>    BitIsOn PI
>      <code>
>    BitIsOn E
> GetFileInf E
>
> You need:
>
> GetFileInf B
> GetFileInf PI
>    <code>
> GetFileInf E
>
> BitIsOn B
> BitIsOn PI
>    <code>
> BitIsOn E
>
> Another potential problem is that you are defining prototypes within a 
> procedure, which makes them invisible outside of that procedure. In 
> general it makes more sense to define prototypes globally.
>
> Joep Beckeringh
>
>
> Dave Murvin schreef:
>   
> > James,
> >
> > The things not defined seem to be fields in some standard /copy members 
> > for standard fields and the procedure prototypes.  Perhaps I do not 
> > understand the sequence of source records.  My latest try is as follows:
> >
> > GetFileInf prototype
> >
> > GetFileInf B
> > GetFileInf PI
> >
> > BitIsOn prototype
> > KeyTools prototypes
> > MsgTools prototypes
> >
> > /copy PgmConstants
> > /copy UsrSpc structures
> >
> > Local D spec defines
> >
> > GetFIleInf code and a few subroutines here
> >
> > More subprocedures here, such as
> >
> > BitIsOn B
> > BitIsOn PI
> > some procedure code
> > BitIsOn E
> >
> > Then finally
> >
> > GetFileInf E
> >
> >
> > One of the typical things not found is BitIsOn and the message is linked 
> > to the BitIsOn B statement.  I have tried moving the specs around in 
> > different sequences, but I have not found anything that seems to work 
> > very well.
> >