PH01815: S0C4 and S0C7 in IBM Application Discovery Connect for Mainframe during PDS retrieval

APAR status

• Closed as program error.

Error description

• IBM Application Discovery Connect for Mainframe
  FMID HALT503, FMID HALT505, and all existing fixes.
  
  IBM AD agent started task is abending on S0C4-04 in module
  IAYCONN at offset 3DE3A when attempting to retrieve PDS
  members.  S0C7 abends are also observed in IEANUC01, though
  these are reported in the logrec and not in the AD started task
  
  This error condition only occurs when the directory entries
  for the PDS(E) members have been altered in a non standard way.
  If the SMDE block user data contains anything other than
  the standard 30 bytes for ISPF stats (or is empty - no stats ),
  then S0C7 can be triggered when the AD agent calls the CONVTOD
  routine.  The S0C4 is triggered if the last directory entry
  contains a user data string less than 30 bytes long.
  

Local fix

Problem summary

• Users Affected:  Some users of IBM AD Connect for Mainframe with
  non-standard data in user data field of PDS(E) directory
  entries.
  
  Problem Description
  IBM AD agent started task is abending on S0C4-04 in module
  IAYCONN at offset 3DE3A when attempting to retrieve PDS
  members.  S0C7 abends are also observed in IEANUC01, though
  these are reported in the logrec and not in the AD started task
  This error condition only occurs when the directory entries
  for the PDS(E) members have been altered in a non standard way.
  If the SMDE block user data contains anything other than
  the standard 30 bytes for ISPF stats (or is empty - no stats ),
  then S0C7 can be triggered when the AD agent calls the CONVTOD
  routine.  The S0C4 is triggered if the last directory entry
  contains a user data string less than 30 bytes long.
  
  Recommendation:  Apply this fix
  
  Problem Summary:
  IBM AD Connect for Mainframe started task abend on S0C4-04 in
  module
  IAYCONN at offset 3DE3A when attempting to retrieve PDS
  members.
  
  Problem Conclusion
  Code changed to handle this case.
  

Problem conclusion

• Fixed in version 5.1
  

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:

Modules/Macros

• IAYCONN
  

Fix information

• Fixed component name

  AD MAINFRAME

• Fixed component ID

  5737B1610

Applicable component levels