How is time stored and displayed in ACF2 rules?
Article ID: 202641
Updated On:
Products
Issue/Introduction
Noticed rules that are checked each month, before DST ended last weekend they were showing being stored on - 01/14/19-14:57
After running the list on that same rule this week it shows this timestamp - 01/14/19-13:57
Rules are below one for these are stored from 2020-11-02 (after DST end), and from 2020-10-05.
LIST ACFRPT**
ACF75052 RESOURCE RULE ACFRPT** STORED BY USER01 ON 01/14/19-13:57
$KEY(ACFRPT**) TYPE(PGM)
$MEMBER(MCFRPT##)
UID(****************USER02) ALLOW
UID(*************XXX) LOG
UID(*) PREVENT
ACF75051 TOTAL RECORD LENGTH= 472 BYTES, 5 PERCENT UTILIZED
LIST ACFRPT**
ACF75052 RESOURCE RULE ACFRPT** STORED BY USER01 ON 01/14/19-14:57
$KEY(ACFRPT**) TYPE(PGM)
$MEMBER(MCFRPT##)
UID(****************USER02) ALLOW
UID(*************XXX) LOG
UID(*) PREVENT
ACF75051 TOTAL RECORD LENGTH= 472 BYTES, 5 PERCENT UTILIZED
Environment
Release : 16.0
Component : CA ACF2 for z/OS
Resolution
ACF2 does not store that local time information in the rule.
ACF2 will store with the hardware clock that they have set to GMT.
When the decomp is done, ACF2 will look at the software clock of the time of the decompile and show the difference between the hardware and software clock on the display.
Feedback
