Abstract
Information about the impact of the US Energy Policy Act of 2005, which changes the effective dates of US Daylight Saving Time (DST) in 2007 for the US. Actions are required to address this issue in Tivoli Compliance Insight Manager.
Content
A provision of the United States Energy Policy Act of 2005 extends DST by four weeks, beginning in 2007. Other countries (Australia, Canada, Bermuda) are making similar changes to DST rules.
Beginning in 2007, the new DST start and end dates for the US will be:
- Start date: Second Sunday of March (11 March 2007)
- End date: First Sunday of November (4 November 2007)
Systems or applications that process dates and times could be affected by this change. If not addressed, time and date calculations could be incorrect.
How do I know if my systems could be affected?
All software which makes date or time calculations may be effected, including the operating system.
What could happen if I do not update my systems?
Essentially, the system clocks will simply be off by an hour for the few weeks between the new DST start date (in the US) and the old DST start date (March 11 to April 1, 2007 in the US). Other than log file time stamps being 1 hour off for those 3 weeks, there should be no noticeable impact.
What do I need to do to protect my Tivoli Compliance Insight Manager installation?
Like most software, the Tivoli Compliance Insight Manager (TCIM) relies upon 2 main systems to provide time and date services:
- The operating system runtime environment
- The JAVA Runtime Environment (JRE)
Fixes for the operating system and JAVA Runtime Environment (JRE) must be applied separately.
Fixes for the Operating System:
Please consult your operating system vendor for the required updates.
Fixes for the Java Runtime Environment (JRE):
Tivoli Compliance Insight Manager (TCIM) depends on the underlying Java Virtual Machine in the JRE to interpret times in reports. Currently the product ships with a JRE that does not support the DST changes detailed above. The cumulative fixpacks for TCIM 8.0 and TCIM 8.5 include the appropriate JRE version that supports the DST change. Customers must apply this fixpack to ensure the reports reflect the correct daylight saving times. Please refer to the link below for the TCIM Recommended Fixes page to access the latest fixpack. Note: If you are using the mainframe agent (Enabler for RACF, Enabler for ACF2 or Enabler for Top Secret) for Tivoli Compliance Insight Manager, please refresh the CKFREEZE data set shortly after the DST change. This will help ensure that the mainframe agent continues to pass the correct time zone of the target system to the Insight Server. |
|
|
|
|
|
Related information
Fixes for the JAVA JRE:
TCIM Recommended Fixes
Product Alias/Synonym
TCIM
Consul Insight Manager
ISM
InSight Security Manager
Insight