Re: TSMManager and clock change
-Eric van Loon wrote: - >From the TSMManager website: > >After starting the program you will have 30 days in which to >evaluate the program, after that time it will only work if .supplied with a license file that is purchased from us. > >So, when there is no license (or the license has expired) you >have one month to extend it. Apparently rebooting the Collector >gave you another month. TSMManager always reports the license >expiration date in the titlebar of your TSMManager Viewer window. We have a paid license with an expiration date a bit over six months into the future.
Re: TSMManager and clock change
Hi Thomas! From the TSMManager website: After starting the program you will have 30 days in which to evaluate the program, after that time it will only work if supplied with a license file that is purchased from us. So, when there is no license (or the license has expired) you have one month to extend it. Apparently rebooting the Collector gave you another month. TSMManager always reports the license expiration date in the titlebar of your TSMManager Viewer window. Kind regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Thomas Denier Sent: donderdag 18 maart 2010 17:09 To: ADSM-L@VM.MARIST.EDU Subject: TSMManager and clock change We are using TSMManager 4.4. It stopped working just after the clock change on March 14. Most of the operations staff members on duty at the time reported that logon attempts failed with messages stating that the viewer was unable to connect to the collector. One staff member reported a message stating that no licenses were available. TSMManager returned to normal operation after the host system for the collector was rebooted. Did this happen at other TSMManager sites? Is it going to keep happening at every transition to or from daylight saving time? ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 **
TSMManager and clock change
We are using TSMManager 4.4. It stopped working just after the clock change on March 14. Most of the operations staff members on duty at the time reported that logon attempts failed with messages stating that the viewer was unable to connect to the collector. One staff member reported a message stating that no licenses were available. TSMManager returned to normal operation after the host system for the collector was rebooted. Did this happen at other TSMManager sites? Is it going to keep happening at every transition to or from daylight saving time?
Re: Clock Change
Besides that on 5.2 aix server worry if your libc version is lower than stated. We are now patching a lot of servers -Original Message- From: David Longo [mailto:[EMAIL PROTECTED] Sent: Saturday, October 18, 2003 9:33 PM To: [EMAIL PROTECTED] Subject: Re: Clock Change I think this was something that popped up in AIX 4.3.3 somewhere around Maint Level 9 - 10 or so. We had that last Fall here. David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5509 [EMAIL PROTECTED] >>> [EMAIL PROTECTED] 10/18/03 11:58AM >>> IF you are running AIX, you should heed the following warning emailed by IBM. More than just ITSM can become loused up. In a nutshell, type echo $TZ and if there are two trailing commas, worry! Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] = Time is nature's way of making sure == === that everything doesn't happen at once. On Fri, 17 Oct 2003, Herkenrath, Wolfgang wrote: >Hi everybody, > >does anyone know wether I have to do something before clock change on October, 25. I have a TSM-Server on OS/390 and one on Unix. TSM-Version 5.1.6.2. >TIA > >Gruß, Herkenrath > forwarded note below -- >From [EMAIL PROTECTED] Sat Oct 18 10:49:40 2003 Date: Thu, 16 Oct 2003 10:56:39 AM CST From: [EMAIL PROTECTED] Subject: SPECIAL NOTICE: Technical Support Bulletin [IMAGE] [IMAGE] [IMAGE] You have received this email because [EMAIL PROTECTED] is subscribed to support bulletins for selected topics. Following are updates for one or more of the topics you requested. System clock may become incorrect during daylight savings time changes. IBM recommends you take immediate action. Customers running AIX 4.3 or AIX 5.1 need to read ITEM 1. Customers running AIX 5.2 need to read both ITEM 1 and ITEM 2. The information in this bulletin is not available for viewing via the web. If this information is important to you, please retain this email. ITEM 1 IBM released fixes in 2002 for AIX 4.3, AIX 5.1, and AIX 5.2 but some customers may not have applied the fixes. We recommend you verify all your AIX systems have the fix applied. Without the fix applied, the daylight savings time change may not occur properly which could cause time sensitive applications to malfunction. Run lslpp -L bos.rte.date and compare the output with the following list. The fileset should be at or above the level in this list. AIX 4.3.3 bos.rte.date 4.3.3.77 AIX 5.1 bos.rte.date 5.1.0.26 AIX 5.2 bos.rte.date 5.2.0.1 The fixes are available for immediate downloading at the AIX Fix Delivery Center located at https://techsupport.services.ibm.com/server/aix.fdc IMPORTANT The fix corrects the programs that created the error but does not fix the variable setting itself. After applying the fix you must take the following actions. Action 1 Reset the time zone variable TZ if "echo $TZ" output includes one or more commas. To reset the variable, run smitty chtz. Action 2 If you reset the time zone variable because it included one or more commas, then either refresh the cron daemon and restart all applications that read the time zone environment variable -or- reboot the system. Reference information: 4.3 APAR IY34798 SMITTY CHTZ APPENDING 2 COMMAS AFTER TZ 5.1 APAR IY34203 SMITTY CHTZ APPENDING 2 COMMAS AFTER TZ 5.2 APAR IY35629 SMITTY CHTZ APPENDING 2 COMMAS AFTER TZ ITEM 2 IBM relased a fix in March 2003 for AIX 5.2 but some customers may not have applied the fix. We recommend you verify all your AIX systems have the fix applied. Without the fix applied, systems that use daylight savings time offsets may not properly change time at the correct time. This could cause time sensitive applications to malfunction. An offset in DST is not widely used. You do not need to apply the fix if you do not use a DST offset. Run lslpp -L bos.rte.libc and compare the output with the following list. The fileset should be at or above the level in this list. AIX 5.2 bos.rte.libc 5.2.0.10 The fixes are available for immediate downloading at the AIX Fix Delivery Center located at https://techsupport.services.ibm.com/server/aix.fdc IMPORTANT After applying the fix you must take the following action. Action 1 Restart all applications -or- reboot the system. Reference information: 5.2 APAR IY39159 DEFAULT DST TZ SETTINGS WITH AN OFFSET FAILS TO RETURN TO STD IBM, eServer and pSeries are trademarks or registered trademarks of International Business Machines Corporation in the United States or other countries, or both. ## This message is for the named person's use only. It may contain confidential, prop
Re: Clock Change
I think this was something that popped up in AIX 4.3.3 somewhere around Maint Level 9 - 10 or so. We had that last Fall here. David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5509 [EMAIL PROTECTED] >>> [EMAIL PROTECTED] 10/18/03 11:58AM >>> IF you are running AIX, you should heed the following warning emailed by IBM. More than just ITSM can become loused up. In a nutshell, type echo $TZ and if there are two trailing commas, worry! Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] = Time is nature's way of making sure == === that everything doesn't happen at once. On Fri, 17 Oct 2003, Herkenrath, Wolfgang wrote: >Hi everybody, > >does anyone know wether I have to do something before clock change on October, 25. I have a TSM-Server on OS/390 and one on Unix. TSM-Version 5.1.6.2. >TIA > >Gruß, Herkenrath > forwarded note below -- >From [EMAIL PROTECTED] Sat Oct 18 10:49:40 2003 Date: Thu, 16 Oct 2003 10:56:39 AM CST From: [EMAIL PROTECTED] Subject: SPECIAL NOTICE: Technical Support Bulletin [IMAGE] [IMAGE] [IMAGE] You have received this email because [EMAIL PROTECTED] is subscribed to support bulletins for selected topics. Following are updates for one or more of the topics you requested. System clock may become incorrect during daylight savings time changes. IBM recommends you take immediate action. Customers running AIX 4.3 or AIX 5.1 need to read ITEM 1. Customers running AIX 5.2 need to read both ITEM 1 and ITEM 2. The information in this bulletin is not available for viewing via the web. If this information is important to you, please retain this email. ITEM 1 IBM released fixes in 2002 for AIX 4.3, AIX 5.1, and AIX 5.2 but some customers may not have applied the fixes. We recommend you verify all your AIX systems have the fix applied. Without the fix applied, the daylight savings time change may not occur properly which could cause time sensitive applications to malfunction. Run lslpp -L bos.rte.date and compare the output with the following list. The fileset should be at or above the level in this list. AIX 4.3.3 bos.rte.date 4.3.3.77 AIX 5.1 bos.rte.date 5.1.0.26 AIX 5.2 bos.rte.date 5.2.0.1 The fixes are available for immediate downloading at the AIX Fix Delivery Center located at https://techsupport.services.ibm.com/server/aix.fdc IMPORTANT The fix corrects the programs that created the error but does not fix the variable setting itself. After applying the fix you must take the following actions. Action 1 Reset the time zone variable TZ if "echo $TZ" output includes one or more commas. To reset the variable, run smitty chtz. Action 2 If you reset the time zone variable because it included one or more commas, then either refresh the cron daemon and restart all applications that read the time zone environment variable -or- reboot the system. Reference information: 4.3 APAR IY34798 SMITTY CHTZ APPENDING 2 COMMAS AFTER TZ 5.1 APAR IY34203 SMITTY CHTZ APPENDING 2 COMMAS AFTER TZ 5.2 APAR IY35629 SMITTY CHTZ APPENDING 2 COMMAS AFTER TZ ITEM 2 IBM relased a fix in March 2003 for AIX 5.2 but some customers may not have applied the fix. We recommend you verify all your AIX systems have the fix applied. Without the fix applied, systems that use daylight savings time offsets may not properly change time at the correct time. This could cause time sensitive applications to malfunction. An offset in DST is not widely used. You do not need to apply the fix if you do not use a DST offset. Run lslpp -L bos.rte.libc and compare the output with the following list. The fileset should be at or above the level in this list. AIX 5.2 bos.rte.libc 5.2.0.10 The fixes are available for immediate downloading at the AIX Fix Delivery Center located at https://techsupport.services.ibm.com/server/aix.fdc IMPORTANT After applying the fix you must take the following action. Action 1 Restart all applications -or- reboot the system. Reference information: 5.2 APAR IY39159 DEFAULT DST TZ SETTINGS WITH AN OFFSET FAILS TO RETURN TO STD IBM, eServer and pSeries are trademarks or registered trademarks of International Business Machines Corporation in the United States or other countries, or both. ## This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender
Re: Clock Change
IF you are running AIX, you should heed the following warning emailed by IBM. More than just ITSM can become loused up. In a nutshell, type echo $TZ and if there are two trailing commas, worry! Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] = Time is nature's way of making sure == === that everything doesn't happen at once. On Fri, 17 Oct 2003, Herkenrath, Wolfgang wrote: >Hi everybody, > >does anyone know wether I have to do something before clock change on October, 25. I have a TSM-Server on OS/390 and one on Unix. TSM-Version 5.1.6.2. >TIA > >Gruß, Herkenrath > forwarded note below -- From [EMAIL PROTECTED] Sat Oct 18 10:49:40 2003 Date: Thu, 16 Oct 2003 10:56:39 AM CST From: [EMAIL PROTECTED] Subject: SPECIAL NOTICE: Technical Support Bulletin [IMAGE] [IMAGE] [IMAGE] You have received this email because [EMAIL PROTECTED] is subscribed to support bulletins for selected topics. Following are updates for one or more of the topics you requested. System clock may become incorrect during daylight savings time changes. IBM recommends you take immediate action. Customers running AIX 4.3 or AIX 5.1 need to read ITEM 1. Customers running AIX 5.2 need to read both ITEM 1 and ITEM 2. The information in this bulletin is not available for viewing via the web. If this information is important to you, please retain this email. ITEM 1 IBM released fixes in 2002 for AIX 4.3, AIX 5.1, and AIX 5.2 but some customers may not have applied the fixes. We recommend you verify all your AIX systems have the fix applied. Without the fix applied, the daylight savings time change may not occur properly which could cause time sensitive applications to malfunction. Run lslpp -L bos.rte.date and compare the output with the following list. The fileset should be at or above the level in this list. AIX 4.3.3 bos.rte.date 4.3.3.77 AIX 5.1 bos.rte.date 5.1.0.26 AIX 5.2 bos.rte.date 5.2.0.1 The fixes are available for immediate downloading at the AIX Fix Delivery Center located at https://techsupport.services.ibm.com/server/aix.fdc IMPORTANT The fix corrects the programs that created the error but does not fix the variable setting itself. After applying the fix you must take the following actions. Action 1 Reset the time zone variable TZ if "echo $TZ" output includes one or more commas. To reset the variable, run smitty chtz. Action 2 If you reset the time zone variable because it included one or more commas, then either refresh the cron daemon and restart all applications that read the time zone environment variable -or- reboot the system. Reference information: 4.3 APAR IY34798 SMITTY CHTZ APPENDING 2 COMMAS AFTER TZ 5.1 APAR IY34203 SMITTY CHTZ APPENDING 2 COMMAS AFTER TZ 5.2 APAR IY35629 SMITTY CHTZ APPENDING 2 COMMAS AFTER TZ ITEM 2 IBM relased a fix in March 2003 for AIX 5.2 but some customers may not have applied the fix. We recommend you verify all your AIX systems have the fix applied. Without the fix applied, systems that use daylight savings time offsets may not properly change time at the correct time. This could cause time sensitive applications to malfunction. An offset in DST is not widely used. You do not need to apply the fix if you do not use a DST offset. Run lslpp -L bos.rte.libc and compare the output with the following list. The fileset should be at or above the level in this list. AIX 5.2 bos.rte.libc 5.2.0.10 The fixes are available for immediate downloading at the AIX Fix Delivery Center located at https://techsupport.services.ibm.com/server/aix.fdc IMPORTANT After applying the fix you must take the following action. Action 1 Restart all applications -or- reboot the system. Reference information: 5.2 APAR IY39159 DEFAULT DST TZ SETTINGS WITH AN OFFSET FAILS TO RETURN TO STD IBM, eServer and pSeries are trademarks or registered trademarks of International Business Machines Corporation in the United States or other countries, or both.
Re: Clock Change
I know with MVS after the IPL and the TSM Server is back up I have to do a; ACCept Date the TSM Server picks up the new system date. Shannon
Clock Change
Hi everybody, does anyone know wether I have to do something before clock change on October, 25. I have a TSM-Server on OS/390 and one on Unix. TSM-Version 5.1.6.2. TIA Gruß, Herkenrath
