ENDEVOR WSEWSSTC S522 abend

Products

• Endevor

Issue/Introduction

Installed Endevor V19 web services, enabled STC pooling,  passed the health check verification, later found S522 abend in WSEWSSTC:

 13.42.33 STC17269  IEF450I WSEWSSTC WSEWSSTC - ABEND=S522 U0000 REASON=00000000
 13.42.33 STC17269  IEF404I WSEWSSTC - ENDED
 13.42.33 STC17269  $HASP395 WSEWSSTC ENDED - ABEND=S522

Environment

Endevor V19

Cause

The problem with the abend is that Endevor STC is waiting longer than it's allowed on the system. When there is no actual request, STC is idle and waiting for the request.

It's controlled by 3 parameters in the ENDEVOR.cfg file: UnusedTimeout, AgedTimeout and PoolReapTime.

Endevor.cfg parameters documentation is available here.

Resolution

STC configuration should be based on how often Web Services is used:
- If Web Services is used by a few users, either completely disable STC pooling (by setting PoolInitSize,PoolIncrSize,PoolMaxSize to 0) or make it ad-hoc (by setting PoolInitSize="0",  PoolIncrSize="1", PoolMaxSize="10") and both Unused/Aged timeout may set to 600 (10 minutes). That means STC will be active at most for 10 minutes + PoolReapTime

- If Web Services is used by many users, enable the STC pooling, set UnusedTimeout and AgedTimeout to a higher value and keep the TIME=NOLIMIT parameter in the WSEWSSTC JCL. PoolReapTime could be set to default value (180).