The equivalent SQL would be to declare an update-able cursor with appropriate
isolation, fetch the record using it then do an UPDATE WHERE CURRENT OF
CURSOR <...> then commit...
Only other option would be to do a LOCK TABLE prior to the SELECT INTO and
UPDATE..
Personally, I'd consider using SQL identity or sequence columns...
Otherwise, just use your RPG as a UDF or SP.
Charles
On Wed, Mar 20, 2013 at 2:30 PM, Steve Richter <stephenrichter@xxxxxxxxx>wrote:
in rpg record I/O I lock a control record, increment a control number, then
update the control record. Which reliably gives me a unique value.
C** GET NEXT SID NUMBER FROM WCMAST
C inwacd CHAIN WCREC
C EVAL WCNSID += 1
C UPDATE WCREC
/free
outSid = wcnsid ;
/end-free
Can I use SQL to do the same thing?
thanks,
--
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.
