Using a product XL Release to invoke Endevor actions on the z system. The Endevor actions run as a started task EDVRWSA, kicked off by CAIENF. In the normal case, EDVRWSA will run to completion with no problem. Several times per day however, CAIENF will cancel the STC while it is running for seemingly no reason and the task abends S222.
If the STC has been customized with additional steps after the REST API action it may experience a timing issue explained below.
The first job step sends a response back to the Tomcat server > then the Tomcat server will start shutting down the CCI connection to the STC.
If the STC pooling is off in the .cfg file, then each STC is single-use and there is no reason to keep it alive.
If the additional job steps manages to finish before CCI gets around to cleaning up the STC everything seems to work, but if not it will have a S222 abend.
The best way to solve the issue would be to put the remaining job steps into a separate job and submit it after the REST API response is received by the caller (XL Release).