× 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.



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?

Try compiling with OPTION(*SECLVL), then check the "Message Summary" at
the bottom of your compiler listing.  The messages will be expanded to
show the help for each message.  Most CRT commands that produce listings
support OPTION(*SECLVL).

Here's what it says for RNF3757.  (Only somewhat helpful, in this case. 
It does suggest the two alternatives Scott and Jon gave, but if you take
the "remove the keyword" path, it doesn't help with what to do after you
remove the keyword.)

The keyword is not valid for definitions in subprocedures.
  Cause . . . . . :   The following keywords are allowed in
    Definition specifications in subprocedures: ALT, ALTSEQ,
    ASCEND, BASED, CONST, DATFMT, DESCEND, DIM, EXTFLD,
    EXTNAME, EXTPGM, EXTPROC, INZ, LIKE, NOOPT, OCCURS,
    OPDESC, OVERLAY, OPTIONS, PACKEVEN, PREFIX, PROCPTR,
    STATIC, TIMFMT, VALUE. The keyword is ignored.
  Recovery  . . . :   Remove the keyword, or move the
    definition to the Definition specifications in the main
    source section. Compile again.


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