And, if you're doing a sql
create table xxx as (
select this union that....)
That new table is going to be created with reuse deleted records yes.
That's going to be interesting. Unless it's only for read and not for
your existing applications to update. Otherwise your purge routines might
be as fun as the old tape methods of reading a table and writing to tape
to merge data.
Maybe, with a lot of work and a desire to learn and have fun you could
create a combination of a view and an index that would somehow still pass
record format level checks. Thus allowing your combined new table to have
a proper sequence number for each memo row yet your applications would
read this new view/index that would somehow put it in order but not pass
the sequencing column? Might not be doable though.