CA SOLVE and CA Netmaster and Daylight Savings Time Change.

book

Article ID: 48651

calendar_today

Updated On:

Products

CA CMDB for z/OS CA NetSpy Network Performance CA NetMaster Network Automation CA SOLVE CA NetMaster Network Management for SNA CA NetMaster Network Management for TCP/IP CA NetMaster File Transfer Management CA SOLVE:Operations Automation SOLVE:Access Session Management CA SOLVE:CA Mainframe Connector CA SOLVE:FTS CA SOLVE

Issue/Introduction

The SOLVE:Operations, SOLVE:Access and Netmaster Suite  regions do not need to be cycled when Daylight Savings time changes take affect.

The product manuals do note certain items to be aware of, and various minor issues have been found affecting EventView timer rules and transient log displays. 

These fixes affect SOLVE:Operations Automation and Netmaster.

No fixes are needed for SOLVE:Access.

 

 

 



Environment

Netmaster Suite 12.0 and above

SOLVE:Operations 11.9
SOLVE:Access 5.0

Resolution

Please review the doc for the product(s) you are running.

NETMASTER
For Netmaster,  our Reference Guide addresses supportability and options that you may want to set if you use timer commands either in NMINIT or NMREADY: 

Support for Local Time Changes 
Last update April 19, 2018 
You do not need to recycle the product or SSI regions when a local time changes, for example, because of daylight saving time. 

The timer commands AFTER, AT, and EVERY support the FTC and BTC parameters to control whether the system skips or repeats actions after it detects a time change. 

The FTC and BTC parameters apply when the timer specifies the timezone with TZ=LOCAL. They do not apply when TZ=UTC or TZ=GMT. 

Forward Time Change: 
FTC=S skips the action. 
FTC=T trips (repeats) the action. 
Backward Time Change: 
BTC=S skips the action. 
BTC=T trips (repeats) the action. 


The link to the doc is here for 12.1
https://docops.ca.com/ca-netmaster-shared-content-library/12-1/en/reference/support-for-local-time-changes

And here for 12.2
https://docops.ca.com/ca-netmaster-shared-content-library/12-2/en/reference/support-for-local-time-changes
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-mainframe-software/performance-and-storage/ca-netmaster-shared-content-library/12-2/reference/support-for-local-time-changes.html

Please ensure that the fixes noted below are applied on your system prior to the next time change.
 



For CA NetMaster Network Management for TCP/IP 12.2 , CA NetMaster File Transfer Management 12.2 and CA NetMaster Network Automation 12.2 -
  - No PTFs are needed if you installed or upgraded to the complete GA version.
  - Please ensure these PTFs are applied if an incremental version is still in use
     SO05347  N23610 PROCEDURE $RETM100 NCLID IN ERROR, STMT NO: 212500
     RO98947  UNABLE TO CLOSE REMOTE ALERT AFTER A TIME CHANGE


For CA NetMaster Network Management for TCP/IP 12.1 , CA NetMaster File Transfer Management 12.1 and CA NetMaster Network Automation 12.1 -
     SO05346  NMS    7.6   N23610 PROCEDURE $RETM100 NCLID IN ERROR, STMT NO: 212500
     RO98946  NMS    7.6   UNABLE TO CLOSE REMOTE ALERT AFTER A TIME CHANGE
     RO63568  NMS    7.6   EVENTVIEW TIMER NEXT EXECUTION DISPLAY INCORRECT




For CA NetMaster Network Management for TCP/IP 12.0 , CA NetMaster File Transfer Management 12.0 and CA NetMaster Network Automation 12.0 -
     RO63333 EVENTVIEW TIMER NEXT EXECUTION DISPLAY INCORRECT





SOLVE:ACCESS 5.0
The SOLVE:Access 5.0 Release Notes state 

Tolerance to Time Offset Changes
You no longer have to recycle a region when time changes (for example, because of daylight saving). 

And regarding the online activity log, the Admin Guide states 

Format of Log After Time Change 
A time change can cause the time to go backward. The activity log differentiates the records that 
overlap in time by adding a plus sign (+) after the time for the newer records. The feature is only 
available when you are viewing the log in the default or NORMAL format. 

The links to those sections are here 
https://docops.ca.com/ca-solve-access-session-management/5-0/en/release-notes/new-features#NewFeatures-TolerancetoTimeOffsetChanges  

and here 
https://docops.ca.com/ca-solve-access-session-management/5-0/en/administering/implementing-activity-logs/implementing-hardcopy-activity-logs  





SOLVE:Operations Automation

The Release Notes provide guidelines for how the time change is handled:



Tolerance to Time Offset Changes



You no longer need to recycle a region when time changes (for example, because of daylight saving).



Activity Log



A time change can cause the time to go backward. The activity log differentiates the records that overlap in time by adding a plus sign (+) after the time for the newer records. The feature is only available when you are viewing the log in the default or NORMAL format.



Alert Monitor



If a time change causes the time to go backward, the Alert Monitor differentiates the records that overlap in time by adding a plus sign (+) after the time for the newer records.



Timers



Actions that are triggered by timers (for example, EventView timer rules) follow the following general rules:



  • If a time change causes the time to go backward, the affected actions are not repeated.
  • If a time change causes the time to go forward, the affected actions are triggered.


The link is here.
https://docops.ca.com/ca-solve-operations-automation/11-9/en/release-notes#ReleaseNotes-NewFeatures



The additional information regarding Timer Commands is the same as for Netmaster 12.1, so please see above or go to this link:
https://docops.ca.com/ca-netmaster-shared-content-library/12-1/en/reference/support-for-local-time-changes

Please ensure that the fixes noted below are applied on your system prior to the next time change.

For CA SOLVE:Operations Automation 11.9 and CA SOLVE:Operations Automation for CICS r11.9 - 
     SO05317   N23610 PROCEDURE $RETM100 NCLID IN ERROR, STMT NO: 212500
     RO81981   INCORRECT EVENT TIMESTAMP IN TRANSIENT LOG
     RO81980    INCORRECT EVENT TIMESTAMP IN TRANSIENT LOG
     RO65037    N23610 PROCEDURE $RETM100 NCLID IN ERROR, STMT NO: 212500
     RO63332   EVENTVIEW TIMER NEXT EXECUTION DISPLAY INCORRECT


The DBCS version for CA SOLVE:Operations Automation 11.9 and CA SOLVE:Operations Automation for CICS r11.9
     SO05318   N23610 PROCEDURE $RETM100 NCLID IN ERROR, STMT NO: 212500
     RO86237   INCORRECT EVENT TIMESTAMP IN TRANSIENT LOG
     RO65038   N23610 PROCEDURE $RETM100 NCLID IN ERROR, STMT NO: 212500
     RO63334   EVENTVIEW TIMER NEXT EXECUTION DISPLAY INCORRECT