RE: Procedure and data area ??$*%

[Scott Mildenberger <Smildenber@xxxxxxxxxxxx>]

The definition of the data area must be in the global section just like file
definitions.  Once the data area is defined globally then you can access it
in the subprocedures.

Scott Mildenberger

> -----Original Message-----
> From: Slava Zharichenko [mailto:Slava.Zharichenko@exel.com]
> Sent: Wednesday, May 02, 2001 9:20 AM
> To: RPG400-L@midrange.com
> Subject: Procedure and data area ??$*%
> 
> 
> 
> Here is what i got when tried to create module
> ...
> 
>    110  *Local Data Area
>    111 D                UDS                  DtaAra( *LDA )
> ======>                 a                    bbbbbb
> *RNF3758 20 a      002421  Data area data structure 
> definitions are not
> allowed in
>                            subprocedures.
> *RNF3757 20 b      002421  The keyword is not valid for definitions in
> subprocedures.
>  112 D  DateFmt                       3A
> 
> 
> Should i use bound call to the module to read local data area?
> 
> thank you
> 
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---