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 ?
Joined: 06 Jun 2008 Posts: 8526 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.