Endevor 19.0 at the base GA release as well as endevor 18.1 with fix LU02753 applied leaks a small amount of storage below the 16 MB line each time that endevor is terminated and restarted in a job step or TSO session.
Since the storage leak is small (36 KB), this symptom is normally not noticed and will surface only when endevor is initiated and terminated many times in the same jobstep or TSO session. Over time, the storage below the line is exhausted.
Release : 19.0
Due to a bug introduced by fix LU02753 for release 18.1 (which was incorporated into the 19.0 GA level), the termination of endevor neglects to release a small control block which is used for SVC screening, which is a technique used by endevor to implement, for example, alternate ID or component monitoring.
This is normally not a problem, but might surface in a jobstep where endevor is initialized and terminated many many times, for example:
Apply fix LU10116 for release 19.0 or LU10115 for release 18.1
The description of these fixes mentions a S0C4 abend running the endevor dialog in ISPF with split screen. That was the symptom reported in the support case which originated the fixes.
However, during investigation of a later case which reported a storage abend, it was found that the fix also corrects the storage leak described in this article.
There are many possible symptoms of a storage leak because they depends on the component that fails to acquire storage because of the leak.
Common ones are system abends related to storage which are accompanied by error message IEA705I ERROR DURING GETMAIN
The symptom observed when this storage leak was discovered was an U4093 abend with reason code 1C as the IBM Language Environment failed to get storage to initialize the environment for an endevor exit written in COBOL.