×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




Buzz,

You can't use CTDATA or PERRCD in subprocedures.  If you think about it,
it makes sense:   CTDATA means that there is data at the bottom of the
*program* that the array is to be initialized with.   Since you can't
do it on a per-subprocedure basis, the keyword really doesn't make sense
in a subprocedure.

Instead, use an alternate method of initializing that table.
Perhaps using the INZ keyword on a D-spec...


On Fri, 24 Jan 2003, Buzz Fenner wrote:

> Hi all, ILE newbie here.  I've converted an RPGIII program and I want to
> change into a procedure module that I can then bind together with other
> modules.  The code has several arrays utilizing compile-time data.  Module
> creation fails stating that the use of CTDATA is not allowed in a
> subprocedure.  Where can I find out what I'm doing wrong?
>
>      19 D TAB1A           S              1    DIM(18) CTDATA PERRCD(18)
>  ======>                                                      aaaaaa bbbbbb
>  *RNF3757 20 a      001900  The keyword is not valid for definitions in
> subprocedures.
>  *RNF3757 20 b      001900  The keyword is not valid for definitions in
> subprocedures.
>


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2026 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.