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 number
PH01815
Reported component name
AD MAINFRAME
Reported component ID
5737B1610
Reported release
505
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-08-19
Closed date
2018-12-14
Last modified date
2018-12-14
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
[{"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":"505","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSRR9Q","label":"IBM Application Discovery for IBM Z"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"505","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
14 December 2018