APAR status
Closed as program error.
Error description
AD zOS started task has timestamps in EUROPEAN TIMEZONE ============================================================ The reason for this is mentioned below:- "The timestamps displayed by the AD DEBUG trace are taken from the system clock using the storeclock (STCK) function. System clocks are usually set to GMT/UTC, and the local time zone relative to UTC is then set in the CLOCK00 member in PARMLIB. AD uses the STCKCONV service, which does not take the local time zone into account when formatting the date/time from STCK. So the customer is correct - the date/time is displayed by the AD trace are GMT / UTC. "
Local fix
NO WORK around
Problem summary
The AD agent was using GMT (UTC actually) for all date / timestamps in the debug trace
Problem conclusion
As part of the 5.1.0.2 release in March 2019, there will now be the option to set the debug trace timestamps to use the local time. This fix will also be made available in the 5.0.5.* fix PTF - UI60938
Temporary fix
Comments
APAR Information
APAR number
PH03806
Reported component name
APPL DISCOVERY
Reported component ID
5737B1600
Reported release
505
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-10-09
Closed date
2019-03-11
Last modified date
2019-03-11
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
APPL DISCOVERY
Fixed component ID
5737B1600
Applicable component levels
[{"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:
11 March 2019