Joe and Jon,

Thanks much for your recommendations. The good news is that adding the *CALLLVL option to the OVRDBF commands has resolved the library problem when running the job from batch. :-)

Since I am hoping to be able to run these program in batch as well as call them from a CGI program, the following CRTPGM statement was used for the CL program:


For the first COBOL program the CRTPGM command used was:


I'm still working on the CGI program that will call the CL program. Jon, do you think I still have something to be concerned about?


Jon Paris wrote:

>> Is there a problem with ILE and OVRDBF? Any help would be appreciated.

Not if you understand ILE scoping <grin>

You do not mention what activation group you specified for the programs.  By
default CRTPGM will use *New - which is rarely a good idea and never a good
idea if you don't mean to do it.  Since by default any OVR issued in an ILE
AG applies only to that group, none of the COBOL programs will see anything
the CL does in this regard.  You should really run COBOL programs in a named
AG (the compiler defaults to QILE) AND specify the same AG for your CL
program.  Although Joe's suggestion of using *CALLLVL may work for you -
with COBOL you really need to get the AG bit right unless you want other
severe problems - like Run Units collapsing when you hadn't issued a STOP
RUN etc.

Jon Paris

This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing list
To post a message email: COBOL400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: COBOL400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

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