Everyone,
I have a client that is running on a DEC Alpha platform using ACMS, Cobol and Rdb. We are getting an infrequent error when a ACMS Task starts. It is not consistent for the tasks, but it happens almost everyday and is being logged. At this point, I need to reach out for some assistance.
When the transaction starts, the first command is a SET TRANSACTION… But the task will abort, we have error handling, stating that the transaction is already started and aborts. In the abort module, we write out error information, execute a ROLLBACK and then exit. When the user comes back into the ACMS task, they are fine.
Of course, I looked up the error and recommended solutions, but do not want to assume I should do a COMMIT or ROLLBACK, since I am not sure what was going on and this could be fatal, depending on what was happening. What I have recommended so far, is when the transaction is a read-only, then trap the error and do a rollback, but what to do is the transaction is an update transaction. The client really wants to find out why this is happening and not just figure out a work around. They believe it is in the code. There are over 50 modules that belong to the server, where this transaction is running under.
Can someone provide guidance or direction on how to determine, why this is happening or what should we be doing in the cobol modules to handle this situation.
Plz send responses to ballj_35@yahoo.com. Thanx in advance.
Jerome Ball
