Re: ILE and OVRDBF

[Margaret Rozmarynowycz <mrozmary@xxxxxxxxxxxxx>]

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:

CRTPGM  PGM(MARGE/JSTDSTMT) MODULE(MARGE/JSTDSTMT)     
       BNDDIR(CGICBLDEV/TISRVPGM) ACTGRP(CGI) AUT(*USE)

For the first COBOL program the CRTPGM command used was:

CRTPGM  PGM(MARGE/STMT010) MODULE(MARGE/STMT010)     
       BNDDIR(CGICBLDEV/TISRVPGM) ACTGRP(CGI) AUT(*USE)

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?  

Marge

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
> Partner400
> www.Partner400.com
>
> _______________________________________________
> 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,
> visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
> or email: COBOL400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/cobol400-l.
>
>
>