Fixes are available
APAR status
Closed as program error.
Error description
Rational Developer for System z - RDz - v9.1 The timestamp used to create the RSEDAEMON log file name is 2 hours off when TZ=Israel. It seems that GMT time is used instead of IST. For example, the log file is created with the name rsedaemon.RSED#20151105120310.log. However, the first entry in the log file has a timestamp of 2015.11.05 14:03:10.417 IST. Conversely, the RSE server log file time is created with the same time as the first entry in the log file. For example, the RSE server log is created with this name: RSED#20151105140310.log. The first entry in the RSE server log file is: 2015.11.05 14:03:28:185 IST
Local fix
None available.
Problem summary
**************************************************************** * USERS AFFECTED: 01.All RDz users * **************************************************************** * PROBLEM DESCRIPTION: 01.Incorrect timestamp added as log * * file name and a PDS member for * * TZ=Israel * **************************************************************** * RECOMMENDATION: * **************************************************************** 01.The timestamp used to create the RSEDAEMON log file name is 2 hours off when TZ=Israel. GMT time is used instead of IST. For example, the log file is created with the name rsedaemon.RSED#20151105120310.log. However, the first entry in the log file has a timestamp of 2015.11.05 14:03:10.417 IST. Further, the 'Changed' timestamp for a PDS member is written in GMT time zone in some host configurations.
Problem conclusion
01.There are several logics to calculate timestamps in native host modules. All of the logics in the native host modules are updated to calculate timestamps based on the time zone offset information provided from java modules. All of timestamp information generated from RDz should be controlled by Java after applying the fix.
Temporary fix
Comments
APAR Information
APAR number
PI57237
Reported component name
RD/Z HOST
Reported component ID
5724T0723
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-02-15
Closed date
2016-09-28
Last modified date
2016-10-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
FEKFCORE FEKFCOR6 FEKFENVR FEKFMAIN FEKFMAI6 FEKFZOS FEKRSEDE
Fix information
Fixed component name
RD/Z HOST
Fixed component ID
5724T0723
Applicable component levels
R910 PSY UI41212
UP16/10/01 I 1000
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSJK49","label":"IBM Developer for z Systems"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"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":"9.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
27 October 2020