View previous topic :: View next topic
|
Author |
Message |
dwijadas
New User
Joined: 20 Sep 2005 Posts: 17
|
|
|
|
Hi,
I have a situation where roll back is issued but log file shouldn't roll back.
All files are VSAM. At this moment I am thinking of coding the log file update outside of the SYNC-COMMIT block.
Any other idea ?
Thank you. |
|
Back to top |
|
|
prino
Senior Member
Joined: 07 Feb 2009 Posts: 1315 Location: Vilnius, Lithuania
|
|
|
|
Tell the auditors what you're doing. They will be well pleased! |
|
Back to top |
|
|
dwijadas
New User
Joined: 20 Sep 2005 Posts: 17
|
|
|
|
Well .. Thanks but I need idea.
The CICS program is initiated by a MQ trigger. Multiple file is needed to update. As part of the process once a result is sent out to requesting system. If the requesting system did not acknowledge the update. CICS should roll back all update.
Here roll back is fine. but the message log file should be kept as proof that request came to CICS.
Any idea ? is there any concept of SYNCPOINT/COMMIT nesting ? |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8700 Location: Dubuque, Iowa, USA
|
|
|
|
Have you talked to your site CICS support group? If not, start there and see what they say. The CICS manual description of SYNCPOINT ROLLBACK states that ALL resources are rolled back together; leaving the log while rolling back everything else would seem to me to leave the system in an inconsistent state --NOT a good thing. |
|
Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
|
|
|
|
since you (should) know how the system operates,
application is responsible for appropriate application messaging,
which this situation clearly is.
do not forget that cics messages and logs have to do with cics behavior
and
not application decisions. |
|
Back to top |
|
|
|