If an IMS™ TCP/IP server program abnormally ends (for example, because of an S0Cx condition), database changes in progress are backed out and the transaction task is terminated, which breaks the TCP/IP connection. When the connection is broken, the client receives a negative status code and an error number that indicates that the connection has been broken. Upon receipt of this indication, the client should assume that the transaction did not complete and that the database changes have not been made. The client could reschedule the transaction, but the IMS TM will have probably stopped it from further running as a result of the abnormal end.

The solution is to correct the reason for the abnormal end and restart the transaction.