|
Your WHERE sounds good to me. Got an index on that, right?
Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin
"Chevalier, Rick" <Rick.Chevalier@xxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
03/28/2003 03:47 PM
Please respond to Midrange Systems Technical Discussion
To: "Midrange Mailing List (E-mail)" <midrange-l@xxxxxxxxxxxx>
cc:
Fax to:
Subject: Selectively process records from an SQL view in
RPG
I need to know how to only read records from an SQL view that have not
already been processed by this RPG program.
Here's the gory details:
I am replacing a physical file in an RPG program with an SQL view that
creates a subset of the physical based on active accounts in the account
master file. The view is being read as a physical file not using SQL
SELECT. Currently the program reads the physical by account number (key)
and stores the current account number in a data area. If the program
abends
for any reason the next time it is called it begins with the account in
the
data area. I can't create an index over the view which means the records
probably aren't even read from the view in account order anyway and a
SETLL
process is out. I am thinking about changing to a SELECT and using the
account number from the data area in a WHERE account <= clause.
Anyone have any suggestions?
Rick
_______________________________________________
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.