Re: Embedded SQL weirdness

[Mark Lazarus <mlazarus@xxxxxxxx>]

Bruce,

At 08:38 AM 1/14/99 -0500, you wrote:

>> 2)  If the program is not under commitment control but the program is
>> compiled with the default COMMIT( *CHANGE ), should this affect the results
>> of the update?

>Only if the transaction is rolled back instead of commited.  Best to
define in
>the program your intention with EXEC COMMIT WORK.If the file is not
journaled, it
>won't work anyway.  If it was created by CREATE TABLE in a *real*
collection, the
>journal will be there.

 Again, this is not the behavior I experienced.  When the program was
compiled w/ CRTSQLRPG COMMIT( *CHANGE ), the updates did not occur.  After
compiling w/ COMMIT( *NONE ) it worked.

 -mark

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---