SOLVE / Netmaster DAYLIGHT SAVING TIME

Products

• NetSpy Network Performance
• NetMaster Network Automation
• SOLVE
• NetMaster Network Management for SNA
• NetMaster Network Management for TCP/IP
• NetMaster File Transfer Management
• SOLVE:Operations Automation
• SOLVE:Access Session Management
• SOLVE:FTS

Issue/Introduction

Problems with SOLVE:Operations 5.0 - continued working with the old time and changed internal time next day midnight. So one hour is missing on the next day (0.00 - 1.00 a.m.), some defined timer commands weren't executed.

IMPORTANT: SEE ENVIRONMENT SECTION FOR AFFECTED RELEASES

 

Environment

SOLVE:Operations 5.0

Netmaster 11.7 and below

SOLVE:Access 4.1 and below

Resolution

When the System Timer is changed (i.e : for daylight saving), the region MUST be restarted to get the timers in sync. Otherwise, no action is submitted for ANY timer set before the system clock change. The Timer used in Solve or Netmaster product is based on AT and EVERY command

The Eventview Timer follows the same rule.

The correct method is to restart Solve or Netmaster region after the system timer change.

Additional Information

For handling of current releases during time change please see KB 48651