RE: SQL Insert Row as last RRN

Chgpf filename REUSEDLT(*NO) (Reuse deleted records)

That ought to solve your problem.

Paul Therrien
Andeco Software, LLC
2233 St. Charles Ave
# 405
New Orleans, LA 70130
225-229-2491
paultherrien@xxxxxxxxxxxxxxxxxx
www.andecosoftware.com

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Robert J. Mullis
Sent: Monday, September 12, 2011 9:38 AM
To: RPG400-L@xxxxxxxxxxxx
Subject: Re: SQL Insert Row as last RRN

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