ENF cancelled an active Endevor Web service task
Article ID: 190527
Updated On:
Products
Issue/Introduction
Common Services ENF task spawned and Endevor Web service task but cancelled it 23 minutes later even though the task was actively performing an Endevor action.
Why some tasks are cancelled and some end normally?
Environment
Release : 14.1 or 15.0
CA COMMON SERVICES FOR Z/OS
Resolution
It is not uncommon to see in the ENF log the tasks being cancelled by spawn. From a SPAWN perspective, a cancel can be issued by CCI when either CCI detects that the "spawner" went away, or if the "spawner" issues a spawn cancel.
The only way to know more would be to look at a SPNDEBUG. The SPNDEBUG output would shed light on to what requested the cancel...whether it be CCI or the "spawner".
The SPNDEBUG is just a starting point, but the only way to determine where it came from first.
To get a SPNDEBUG, add the following DD to the ENF proc and recycle ENF to pick it up.
//SPNDEBUG DD SYSOUT=*
Similarly, the only way to disable it would be to remove it from the proc and recycle ENF. There is no way to dynamically turn this on/off.
The SPNDEBUG can generate many lines of information depending on overall CCI SPAWN activity.
From an Endevor perspective...the spawn tasks can be recycled depending if STC pooling is on, and depending on the configuration file timeout parameters.
The time parameters that can be affecting the spawn tasks are PoolreapTime, Unused Timeout, Aged Timeout and Connection Timeout.
As the problem might be caused by one of these parameters, it may be necessary to increase the timeouts or modify them accordingly to meet your current needs.
Any questions or additional guidance on these timeout settings would have to be addressed by Broadcom Endevor Support Team.
Feedback
