Re: RUNSQLSTM Question -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

How are you "sorting" with a RUNSQLSTM?

That doesn't make any sense.

Unless the statement being run is an INSERT INTO TEMPFILE (SELECT
<...> FROM FILEA)?

If so, are you by chance using the default COMMIT(*CHG) on the
RUNSQLSTM and not commiting? Thus teh records added to TEMPFILE get
rolled back?

Charles

On Wed, Aug 19, 2009 at 12:30 PM, Kelley
Shaddrick<kshaddrick@xxxxxxxxxxxxxxxx> wrote:

I have a CLLE that has two RUNSQLSTM's in it. The first RUNSQLSTM sorts file A a certain way (there are no where clauses). Then program A runs. The second RUNSQLSTM sorts file A again a slightly different way (again. no where clauses). Then program B runs.

The second RUNSQLSTM always fails. It does not select any records. I'm guesing there is a pointer that has not been reset but it is not clear to me how do to so. Any ideas?

Kelley
--
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.

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.