Re: QCMDEXC (or) user written CLP program ?

[Bob Larkin <blarkin@xxxxxx>]

Simon,
Since an OVRDBF done by QCMDEXC is in effect on the calling program, many would
believe the call is at the same invocation level. In reality, I don't know why 
it
works, except that IBM coded it that way :)
Bob

Simon Coulter wrote:

> M
> Hello Scott,
>
> You wrote:
> >If you do need to use the CHGDTAARA command, I'd certainly recommend
> >using QCMDEXC.  It will be slightly faster, since QCMDEXC will run your
> >command at the same call-level as your program, whereas calling a CL
> >program will need to make a new call level for the CL program.
>
> Where did you get that idea from?  The call to QCMDEXC is the same as a call 
>to
> any other program.  An invocation level is created for each call.  QCMDEXC 
>does
> APPLY overrides at the caller's invocation level but that's a different thing.
>
> You can prove this by looking at the call stack when QCMDEXC is running a
> command.
>
> Regards,
> Simon Coulter.
>
> «»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»
> «» FlyByNight Software         AS/400 Technical Specialists       «»
> «» Eclipse the competition - run your business on an IBM AS/400.  «»
> «»                                                                «»
> «» Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\   «»
> «» Fax:   +61 3 9419 0175   mailto: shc@flybynight.com.au   \ /   «»
> «»                                                           X    «»
> «»               ASCII Ribbon campaign against HTML E-Mail  / \   «»
> «»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.