APAR status
Closed as program error.
Error description
Using Application Discovery Connect for Mainframe 5.1.0.5, the STC suddenly began using a very large amount of CPU, in the period of an hour it used +/- 2380 CPU seconds. The task done on AD server side during this event wasloading the Application discovery projects with DB2 and other sources.
Local fix
n/a
Problem summary
This problem was caused by a bug in the existing code that mis-interpreted a TCP/IP return code. The bug was dormant until the new communications layer was added in v5.1.0.5
Problem conclusion
The bug was caused by a failure to save registers properly in a subroutine. After this was corrected the problem was resolved. Fix is available in AD Connect for Mainframe v5.1.0.7.
Temporary fix
Comments
APAR Information
APAR number
PH26294
Reported component name
AD MAINFRAME
Reported component ID
5737B1610
Reported release
510
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2020-06-11
Closed date
2020-10-12
Last modified date
2020-10-12
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
[{"Line of Business":{"code":"LOB35","label":"Mainframe SW"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSRR9Q","label":"IBM Application Discovery for IBM Z"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"510"}]
Document Information
Modified date:
13 October 2020