APAR status
Closed as program error.
Error description
IBM Application Discovery Connector for Mainframe v5.0.3 FMID HALT503 plus any and all previous PTFs. While repeatedly calling the Endevor API ENA$NDVR, it was observed that storage was being exhausted, possibly a memory leak, and this was causing the API to abend. The side effect seemed to be that the Connector started task did not release the exclusive ENQ it had acquired on the Endevor dataset and other jobs which required access were not able to run until the started task was stopped. Observed error messages in the AD connector started task joblog: IAYCONN ZLG1029E ERROR returned from ENDEVOR RC=0020, REASON=0015 NDVPROD CEE0813S Insufficient storage was available to satisfy a get storage (CEECZST) request.
Local fix
n.a
Problem summary
Storage leak caused by Endevor API 12/03/2018 07:47:07 IAYCONN ZLG1029E ERROR returned from ENDEVOR RC=0020, REASON=0015 NDVPROD REGUL TXTINFO PGMCB2B ####### TCP ERROR 2018/03/09 16:10:06 SEND1 ERRNO: 00032 ####### TCP ERROR 2018/03/10 05:02:59 SEND1 ERRNO: 00032 CEE0813S Insufficient storage was available to satisfy a get storage (CEECZST) request. The traceback information could not be determined. <> LEAID ENTERED (LEVEL 02/26/2016 AT 17.55) <> LEAID PROCESSING COMPLETE. RC=4
Problem conclusion
CA was unable to provide a fix for the storage leak caused by the Endevor API. The code change in this PTF calls the Endevor API using a batch job submitted by the AD Connect started task instead of a direct program call. When the batch job completes, any user region storage not freed by the Endevor API is released by the system, so this prevents the AD connect address space from slowly leaking storage. This workaround is not a general solution and should only be used for cases where a customer site experiences the same problems when retrieving source from Endevor.
Temporary fix
n.a
Comments
APAR Information
APAR number
PI99768
Reported component name
EXP FOR Z/OS HO
Reported component ID
5655EXP23
Reported release
300
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-06-29
Closed date
2018-10-11
Last modified date
2019-02-21
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
EXP FOR Z/OS HO
Fixed component ID
5655EXP23
Applicable component levels
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSBDYH","label":"IBM Explorer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.0.0","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.0.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
21 February 2019