|
No significance to number.
Just doing a regression test between a file updated with the current prod version of a pgm and a modified version of same pgm.
Need to force the seq# field to 1,2,3,4, etc so it is the same between files, and it is a unique key so I cant simply clear it out.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Roger Harman
Sent: Tuesday, April 30, 2013 5:10 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: update column with a sequential #
Any significance to the number?
I had to do something similar a long time ago. RGZPFM to get rid of deleted
records and then just used the RRN as the value for my update.
How do you plan to maintain it going forward?
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Stone, Joel
Sent: Tuesday, April 30, 2013 3:01 PM
To: midrange-l@xxxxxxxxxxxx
Subject: SQL: update column with a sequential #
Is it possible to update a column with a sequential # ?
So that for this particular column, each row has a value 1 higher than the
prior row?
Something like
UPDATE filename set SEQCOL to prior SEQCOL + 1
(This is a DDS created file that does NOT have an identity column.)
Thanks!
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.