× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: Procedure and data area ??$*%
  • From: Scott Mildenberger <Smildenber@xxxxxxxxxxxx>
  • Date: Wed, 2 May 2001 09:34:54 -0600

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

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.