View previous topic :: View next topic
|
Author |
Message |
mkarmegam
New User
Joined: 28 May 2006 Posts: 13 Location: USA
|
|
|
|
We have a requirement that when the nightly batch runs and updates the DB2 tables, the CICS-COBOL-DB2 programs should not be able to update the data as well as it should not pickup any updated data via the batch process.
Once the batch update process is over we can turn on the CICS-DB2-COBOL programs to update (and read) mode from being able to just read.
I am wondering is there anybody have the same kind of requirement... How this could be achieved without much implications. Is there any implications on the CICS front that the transactions which has update statements becoming read only and back.
Any thoughts , ideas appreciated
WARNING: Do not Repost the same topic |
|
Back to top |
|
|
UmeySan
Active Member
Joined: 22 Aug 2006 Posts: 771 Location: Germany
|
|
|
|
Hi !
1.) Shut down CICS, Run Batch, Start CICS
2.) Disable the CICS-transactions which do the updates before Batch-Start
then run the Batch and then Enable the transactions again.
Regards, UmeySan |
|
Back to top |
|
|
mkarmegam
New User
Joined: 28 May 2006 Posts: 13 Location: USA
|
|
|
|
Thanks for the reply.
There is a 24/7 requirement, so the user should be see the data(not the partially updated data) while batch process is happening.
Additionally there are programs which has both update and read logic. |
|
Back to top |
|
|
|