×
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.
Check the attributes of the work file. It sounds like it is set to reuse
deleted records.
-----Original Message-----
From: Koester, Michael
Sent: Monday, September 12, 2011 10:30 AM
To: RPG400-L@xxxxxxxxxxxx
Subject: SQL Insert Row as last RRN
I have a very simple 1-column workfile created on the fly with embedded SQL.
As I add rows to the table, some situations require that some rows need to
be deleted, which works just fine. But the next row added then gets stuffed
into the workfile in the position (relative-record-number-wise) of the first
row vacated by the delete. I didn't anticipate this when I designed my
process, so I didn't build in a sequence number column. All the access to
this workfile is through SQL - no RLA in this program.
Is there a way to specify on the INSERT statement that the new row is to
have an RRN greater than that of the greatest RRN already written? If not,
is there a simple way to re-sequence (compress) out the deleted rows after
my DELETE statement, so that the result has contiguous RRNs (thereby leaving
no gaps, and a subsequent INSERT would have to go to the "end" of the
workfile)?
Thanks.
Michael Koester
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
