I haven't been following this thread so I might be missing something.

From what I hear you saying you are writing records to table during a UDF.

My question would be are you using a Global Temp Table?

Since the Global Temp table is designed to create temporary tables during
processing with low overhead I cannot imagine that it would have problems
with doing a Select Count(*) over a table you just wrote.


On Thu, Apr 19, 2018 at 2:36 PM, a4g atl <a4ginatl2@xxxxxxxxx> wrote:

Its pseudo code and the file name was a typo.

I agree its a data base issue of sorts. I cannot run a RUNQRY against the
file whilst the program is running. It sees an empty file until the program
ends.

The count is not the issue. The issue is that the records written into the
file are not visible until the program ends.

Its like I need a COMMIT statement after each INSERT??? But there is no
commitment control that I have started.

Darryl.

On Thu, Apr 19, 2018 at 5:30 PM, Dan <dan27649@xxxxxxxxx> wrote:

So, is this just pseudocode? Or did you make the change to use the right
file and now it is fixed?

If the former, try the FEOD opcode with the N extender before doing the
SELECT COUNT(*). Although I agree with Paul on this being an old issue,
it's worth a shot. Maybe the old issue was resolved with RLA but not
SQL?
I would think that issue would be at the database level and not the
language level, but that's beyond my paygrade, so...

- Dan

On Thu, Apr 19, 2018 at 5:12 PM, a4g atl <a4ginatl2@xxxxxxxxx> wrote:

Apologies, you are correct, thanks. This should be

2. use Select count(*) counting if the part number exists in the output
file.
SELECT COUNT(*) into :COUNT from OUTPUTFILE WHERE PART_NO =
:PART

Darryl

On Thu, Apr 19, 2018 at 4:44 PM, Dan <dan27649@xxxxxxxxx> wrote:

First of all, I'll beat David to the punch and suggest that this
probably
belongs in the RPG list.

Are you sure you want get the count from the INPUTFILE? Seems like
you
want to get it from the target file.

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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.