Re: CALLPRC & CRTBNDCL

[Vernon Hamberg <vhamberg@xxxxxxxxxxx>]

Why would (B) mean a lot of I/O? You'd use selection criteria, just as you 
do with OPNQRYF. I mean, OPNQRYF and all SQL used to use the same code 
under the covers, as well as Query/400.

You can have an embedded SQL that is exactly the same as what OPNQRYF gets 
you. Show us your OPNQRYF command and I'll put up the SQL equivalent - it's 
pretty easy.

As someone else said in a recent post, OPNQRYF is always dynamic in its 
execution, embedded is static and usually faster.

Vern

At 01:41 PM 9/13/2005, you wrote:

> O.K., I admit that I am not the sharpest tool in the shed when it comes
> to SQL so here is what I am trying to do. I have a history file that I
> need to read for a certain time period to see if certain parts have been
> received during that time period. Ordinarily I would use embedded sql to
> join the two files together and print out which parts from the exception
> file were found in the history file. However, the requirements of this
> project are to print a "part not received" line if the part in the
> exception file was not received during the time period selected. The
> only way I know to do this would be to either:
>
> A.) create an OPNQRYF over the history file in a CL and chain to it or
>
> B.) use embedded sql to pull the information out of the history file and
> use that to chain to the exception file.
>
> I don't particularly like (B) in this instance because it seems like an
> awful lot of I/O for the 4 or 5 parts in the exception file. I was going
> to use (A) and that is where I ran into problems with the CALLPRC
> command not knowing where the procedure was no matter how the cl was
> compiled.
>
>
>
> If any one has other ideas, I am all ears.
>
>
>
> Thanks,
>
> Terry
>
> > ------------------------------
> >
> > message: 4
> > date: Tue, 13 Sep 2005 11:24:37 -0500 (CDT)
> > from: Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>
> > subject: Re: CALLPRC & CRTBNDCL
> >
> > > Thanks to all who replied. It looks like I will only be able to use
> > > CALLPRC with the CRTCLMOD or CRTPGM commands. Of course if I knew an SQL
> > > alternative to the OPNQRYF command, I wouldn't need the CLLE in the
> > > first place. ;-)
> >
> > Huh?
> >
> > a) You don't need CL to use OPNQRYF.
> >
> > b) SQL _is_ an alternative to OPNQRYF.
> >
> > c) You can also use CALLPRC with CRTBNDCL, you just have to call a a
> > procedure that the program already knows about, for example, MI builtins,
> > the CEExxxx APIs, etc.
> >
> >
> >
> >
> > ------------------------------
> >
> > message: 5
> > date: Tue, 13 Sep 2005 11:29:29 -0500
> > from: rob@xxxxxxxxx
> > subject: Re: CALLPRC & CRTBNDCL
> >
> > 1 - Did you try CRTBNDCL ... DFTACTGRP(*NO) ACTGRP(*CALLER)
> >
> > 2 - Are you adverse to imbedded sql in your HLL instead?
> >
> > Rob Berendt
> > --
> > Group Dekko Services, LLC
> > Dept 01.073
> > PO Box 2000
> > Dock 108
> > 6928N 400E
> > Kendallville, IN 46755
> > http://www.dekko.com
> >
> >
> >
> >
> >
>
> --
> http://www.fastmail.fm - Same, same, but different?
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.