RE: [COBOL400-L] SQLCBL and COMMIT

["A. Sivasubrahmanian" <sivasubrahmanian.ananthakrishnan@xxxxxxxxx>]

Hi Geir

The file KILFIL should be under commitment control if you want to user
COMMIT(*CHG) option.

Regards 
Siva

-----Original Message-----
From: cobol400-l-bounces@xxxxxxxxxxxx
[mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of
geir.kildal@xxxxxxxxxxxxxxx
Sent: Friday, January 09, 2004 3:27 PM
To: cobol400-l@xxxxxxxxxxxx
Subject: [COBOL400-L] SQLCBL and COMMIT

Hello.

I'm testing out embedded SQL in a small OPM-COBOL-pgm, and I end up with
a 
thing I can't sort out:  If I compile my SQLCBL-pgm with COMMIT(*NONE),
it 
all works fine.  My testfile is updated immideatly. I call my testpgm
from 
a command line.

But, if i compile with COMMIT(*CHG), I never see any results in my 
testfile.  I had expected to see the canges when the program ended(stop 
run/goback)??
I have tried issuing a COMMIT in the pgm and outside the pgm from the 
command-line after execution, but nothing helps.
Here is my code:

PROCEDURE DIVISION. 
HUVUD SECTION. 
START-000. 
 
    EXEC SQL 
    UPDATE DF90TST/KILFIL   SET ADRBES = "xxxxxxxxxxxxxxxxxx"    
    END-EXEC. 
    GOBACK. 



Mvh.

Geir 

 
_______________________________________________
This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing
list
To post a message email: COBOL400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/cobol400-l.


Confidentiality Notice 

The information contained in this electronic message and any attachments to 
this message are intended
for the exclusive use of the addressee(s) and may contain confidential or 
privileged information. If
you are not the intended recipient, please notify the sender at Wipro or 
Mailadmin@xxxxxxxxx immediately
and destroy all copies of this message and any attachments.