PH03995: IBM Application Discovery Connector for Mainframe v5.0.5 F

APAR status

• Closed as program error.

Error description

• IBM Application Discovery Connector for Mainframe v5.0.5
  FMID HALT505 and any 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

Problem summary

• For IBM AD Connect for Mainframe, v5.0.5.*. When retrieving
  PDS/PDSE members for which the user data field in the directory
  entries does not contain ISPF stats but data written by another
  software product, this situation can sometimes lead to S0C4
  abends, or cause the IBM AD started task to not retrieve the
  member.
  
  This can in turn cause the AD build client to indicate that the
  retreived PDS/PDSE members have length 0.If a user tries to view
  the members, they will be empty.
  

Problem conclusion

• We added 2 checks:
  
  -first if the user data field in the PDS directory is *not* 30
  bytes but some other length, do not perform any check on the
  "records updated" field - just go ahead and process the member
  under the assumption that it is required.
  -if the user data field is 30 bytes (in other words, it appears
  to contain ISPF stats) - first do some sanity checks on
  individual fields to ensure they are reasonable for ISPF stats -
  eg. date/time fields are in proper packed format.  If the user
  data does not appear to be valid ISPF stats - for example - a
  string of hex 0 - skip the remaining check on "records updated"
  and just process the member (as in the first check).  This will
  avoid the false positive classification for ISPF stats.
  

Temporary fix

Comments

APAR Information

• 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

  AD MAINFRAME

• Fixed component ID

  5737B1610

Applicable component levels