View previous topic :: View next topic
|
Author |
Message |
Vijay Vemuri
New User
Joined: 25 Feb 2009 Posts: 2 Location: Bangalore
|
|
|
|
Hi,
I have a cobol-db2 program calling a cobol-db2 stored procedure.
Is there any way to commit the updates done only by stored procedure.
I need to know that is there a possibility of autonomous commit in DB2?
Please provide your ideas..
Thanks in advance,
Vijay,
IBM India |
|
Back to top |
|
|
ashimer
Active Member
Joined: 13 Feb 2004 Posts: 551 Location: Bangalore
|
|
|
|
If your main program updates data and then calls sub routine which commits ; all the changes will be committed ....because the entire process is a single unit of work ... |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
Suggest you consider a different design approach that will not allow/require interleaving multiple uits of work. . .
If you explain what the process needs to do, someone may have a suggestion. |
|
Back to top |
|
|
Vijay Vemuri
New User
Joined: 25 Feb 2009 Posts: 2 Location: Bangalore
|
|
|
|
My requirement is
need to store the displays of stored procedure in DB2 table instead of WLM log.
Can any one provide suggesions how to do this?
Thanks,
Vijay. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
Quote: |
need to store the displays of stored procedure in DB2 table instead of WLM log. |
I believe this needs some clarification.
If the sp inserts some rows in a table and does not issue a commit what will be the problem having the unit-of-work controlled by the main program? When the main program issues a commit, all uncommitted actions will be committed. Similarly, if the main program rolls back the work, the entire unit of work will be rolled back. |
|
Back to top |
|
|
|