RE: SQL vs. traditional I/O?

Another thing to consider.  Traditional I/O has some default blocking.  And
by specifying I for input only no locking is done, etc.
Look at the SQL  SET OPTION statement.  What are the defaults, and their
ramifications for some of the following:
ALWBLK
COMMIT
SQLCA

Or, for that matter, is there some way to tailor the "isolation clause" on
the SELECT INTO to enhance this:
>>-WITH--+-NC-----------------+--------------------------------><
         +-UR-----------------+
         +-CS--+------------+-+
         |     '-KEEP LOCKS-' |
         +-RS-----------------+
         '-RR-----------------'

And back when Joe had it in a cursor he didn't specify FOR FETCH
ONLY.  That can make a difference.

You may argue that this is a lot of baggage.  Look at it this way.  If you
were coming from a SQL background and had to learn all the possible
options, and keywords, for the RPG 'F' spec might that not be
daunting?  Like update versus input only, how to add additional records,
etc.  I seem to remember some intense threads on blocking.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com