Dear SCO Customer, Support Level Supplement (SLS) OSS601A, the Year 2000 Supplement for SCO OpenServer 5.0.2 and 5.0.4, corrects a number of problems in date and time processing in SCO OpenServer Release 5.0.2 and 5.0.4. See the list below for more information on specific problems addressed by this SLS. Software Notes and Recommendations ---------------------------------- SLS OSS601A should be installed only on: SCO OpenServer Enterprise System Release 5.0.2, 5.0.4 SCO OpenServer Host System Release 5.0.2, 5.0.4 SCO OpenServer Desktop System Release 5.0.2, 5.0.4 SCO OpenServer Internet FastStart Release 5.0.4 SCO Internet FastStart Release 1.1.0 SCO OpenServer Development System Release 5.0.2b, 5.1.0Ac There are no required patches that must be applied before SLS OSS601A. Some patches are recommended for each release; please see the note below. However, there is some software that must NOT be applied after SLS OSS601A: - Release Supplement 504C (rs504c) for SCO OpenServer 5.0.4 - SLS OSS465B: Scomail Supplement for SCO OpenServer 5.0.2, 5.0.4 - SLS OSS449F: Network Maintenance Supplement for SCO OpenServer 5.0.2, 5.0.4 - UnixWare/OpenServer Development Kit 7.0.0 If you want to apply any of the above software at any time after applying SLS OSS601A, you must remove OSS601A, install the desired software, and then reinstall OSS601A. Otherwise, the above software will either overwrite some of the fixes that are included in SLS OSS601A, or will fail to install. (If you are using the UnixWare/OpenServer Development Kit 7.0.0, please see the SCO Year 2000 Web Page for Y2K information about that product.) IMPORTANT NOTE: After applying SLS OSS601A, you must reboot your system in order for the Y2K fixes in the dynamic shared C language library to become fully active. See the Installation Instructions for more information. Note: A list of recommended patches for these and other SCO products, is located off of the SCO Support Toolbox webpage at: http://www.sco.com/support/toolbox/patch.html SLS OSS601A corrects these problems: asktime(ADM) does not support entry of a four-digit year. Associated SCO tracking number: RUS-1-26 auditsh(ADM) parses two-digit dates incorrectly after 1999. It treats 99 as 2099 instead of 1999. Associated SCO tracking number: RUS-1-35 The Backup Manager fails with the error 'Fatal error: Unable to convert date-time string "00:00"' in the year 2000. Associated SCO tracking number: SCO-59-8679 The Backup Manager displays two-digit years. Associated SCO tracking number: RUS-1-25 The calstats utility (part of scocal(XC)) displays the year 20YY as 1YY instead of YY. Associated SCO tracking number: RUS-1-31 The convertclock(TCL) function in /bin/tcl and /bin/osavtcl fails with the error 'Fatal error: Unable to convert date-time string "00:00"' in the year 2000. Associated SCO tracking number: SCO-59-9295 The convertclock(VTCL) function in /bin/vtcl fails with the error 'Fatal error: Unable to convert date-time string "00:00"' in the year 2000. Associated SCO tracking number: SCO-247-141 The Date Accessory on the IXI GUI Desktop displays the year 20YY as 19YY. Associated SCO tracking number: SCO-237-162 dclock(XC) hardwires the century to 19 when using the "-date "%Y"" option to the command. Associated SCO tracking number: RUS-1-3 The ftp(TC) "newer" command does not work correctly if the remote file is modified after 1999. Associated SCO tracking number: RUS-1-4 fptd(NADM) hardwires the first two digits of the year to 19 when creating date stamps for the ftp(TC) mdtm command. Associated SCO tracking number: RUS-1-32 getdate(S) generates unreliable results if "%y" is used in the DATEMSK for the API, and dates, which are not in the current century, are processed. Associated SCO tracking number: RUS-1-39 lastlogin(ADM) has been updated to process two-digit years correctly in 2000 and beyond. Associated SCO tracking number: RUS-1-22 brand(ADM) dumps core when used after September 2015. Associated SCO tracking number: SCO-236-772 localtime(S) produces unreliable results when used with pre-Epoch dates, (dates before the 1st of January 1970). Associated SCO tracking number: SCO-59-9366 Printer banner pages for the standard(ADM) and ph.daps(ADM) printer interface hardwire the first two digits of the year to 19 by representing the date as "19%y" instead of "%Y". Associated SCO tracking number: DAV-2-14 text2post(ADM) has a hardwired date of "19%y". Associated SCO tracking number: RUS-1-23 mail(C) and mailx(C) display the year 20YY as 1YY in email date headers. Associated SCO tracking number: SCO-236-1298 mailx(C) incorrectly processes incoming mail headers that contain a two-digit year representing a year greater than 1999. Associated SCO tracking number: RUS-1-11 mktime(S) does not recognize the year 2000 as a leap year. Associated SCO tracking number: LTD-246-1290 mktime(S) does not normalize the tm data structure correctly. Associated SCO tracking number: LTD-246-1314 The Network Node Check Manager writes the date as a two-digit value on the "Alert" window and in the history logfile when the node is unreachable. Associated SCO tracking number: RUS-1-5 passwd(C) -s displays the modification date of a password as dd/mm/1YY if the password was last modified in 20YY. Associated SCO tracking number: LTD-246-1272 prfpr(ADM) uses a two-digit year format in its date stamps. Associated SCO tracking number: RUS-1-8 prs(CP) prints the creation date of SCCS files created in 20YY as 1YY. Associated SCO tracking number: RUS-1-7 sar(ADM) report header displays the year 20YY as 1YY. Associated SCO tracking number: SCO-244-167 SCCS s.* files maintain the year as two digits and do not treat two-digit years as per the X/Open specification. Modified sccs(CP) to treat 00-69 as 2000-2069. Associated SCO tracking number: SCO-59-8645 scomail(XC) displays a one-digit value in the "Date:" field of the message summary window for email sent between 2000 and 2009. Associated SCO tracking number: RUS-1-34 scosh(C) email summary window displays the year as "-9" for a message with a year of 101 (2001 with the mail(C) bug). Associated SCO tracking number: SCO-59-9801 strptime(S) converts a two-digit year (%y) to a year offset from 1900. So, for example, if you input a year value of 00, strptime would set tm_year to 00, which is interpreted as 00+1900 or 1900. Associated SCO tracking number: RUS-1-38 The System Time Manager does not accept or display four-digit years in the year input field. Associated SCO tracking number: SCO-59-8655 Installation Instructions ------------------------- Note: The SLS installation and removal processes differ significantly between SCO OpenServer 5.0.4 and SCO OpenServer 5.0.2. Please follow the appropriate instructions for the version of the operating system that you are using. Installing SLS OSS601A on SCO OpenServer 5.0.4 ---------------------------------------------- 1. Prepare the media for installation. Download the OSS601A VOL files from the SLS/oss601a directory on SCO's ftp site. Place the files in the /tmp directory on the local system. The files should include: VOL.000.000 VOL.001.000 VOL.002.000 VOL.003.000 VOL.004.000 oss601a.ltr 2. Log in as root and run the Software Manager with the command: # scoadmin software or double-click on the Software Manager icon in the desktop. 3. Pull down the "Software" menu and select "Install New". 4. When prompted for which host to install from, choose the local machine and then "Continue". 5. In the "Select Media" window, pull down the "Media Device" menu. Select "Media Images", then "Continue". 6. When prompted for the "Image Directory", enter "/tmp" (or the directory where you placed the VOL files in step 1) and choose "OK". Note: If you are installing from the Year 2000 Resource CD-ROM, the location of this supplement is: /patches/oss601a/ 7. Next you will be prompted to select the software to install. SLS OSS601A contains two components: the Year 2000 Supplement and a Software Manager patch which is only for OpenServer 5.0.4. If your system is running OpenServer 5.0.4, you MUST install the new version of the Software Manager BEFORE you can install the Year 2000 Supplement. Make sure that ONLY the "oss601a Software Manager patch for OSR 5.0.4" entry is highlighted and choose "Install". When the installation of the Software Manager patch is complete, you will see a message instructing you to exit and restart the Software Manager before installing any other software. Press . 8. In the Installation Complete window, click on "OK". The Software Manager should now list the Software Manager patch. 9. Exit the Software Manager by selecting "Exit" from the "Host" menu. Then restart the Software Manager, now patched by the new version you just installed. 10. Pull down the "Software" menu and select "Install New". 11. When prompted for which host to install from, choose the local machine and then "Continue". 12. In the "Select Media" window, pull down the "Media Device" menu. Select "Media Images", then "Continue". 13. When prompted for the "Image Directory", enter "/tmp" (or the directory where you placed the VOL files in step 1) and then select "OK". 14. You will be prompted to select the software to install. Make sure that only the "Year 2000 Supplement for SCO OpenServer 5.0.2 and 5.0.4" entry is highlighted and choose "Install". 15. You will see a message informing you that certain components of OSS601A cannot be installed. (For example, if you do not have French language support installed, you cannot install the French language components of OSS601A.) Choose "Continue". 16. Once the installation finishes, select "Exit" from the "Host" menu. Installation of SLS OSS601A to your hard disk is complete. 17. After applying OSS601A, you must reboot your system in order for the Y2K fixes in the dynamic shared C language library (libc.so.1) to become fully active. You do not have to reboot immediately. However, you MUST reboot before January 1, 2000. We strongly recommend that you reboot as soon as possible after installing OSS601A. There are no problems that are currently known to occur when the system is in the state of having the patch applied, but not having been rebooted. However, we have not conducted any methodical testing of a system in this state. Therefore, we recommend that you avoid leaving your system in this state for an extended length of time. Removal Instructions for SCO OpenServer 5.0.4 --------------------------------------------- Note: Patches must be removed in the reverse order in which they were installed on a per-component basis. The "Year 2000 Supplement for SCO OpenServer 5.0.2 and 5.0.4" patches the BaseX, Desktop, MailUA, TclX, TclXds, Unix, WServer, adminfw, tcp, and unixds components. In addition, on OpenServer 5.0.4, the smp component is patched. The "oss601a Software Manager patch for OSR 5.0.4" updates the Software Manager component. If any of these components were patched after OSS601A was installed, you must remove those later patches before removing OSS601A. To remove SLS OSS601A: 1. Log in as root. 2. Execute the command: # scoadmin software or double-click on the Software Manager icon in the desktop. 3. Highlight the title of the software you want to remove. 4. Pull down the "Software" menu and select "Remove Software". 5. You will be prompted to confirm whether you wish to remove the selected software. Choose "Remove" to continue. 6. Once the removal finishes, select "Exit" from the "Host" menu or repeat steps 3 through 5 to remove another patch. 7. In order for the removal of OSS601A to take full effect, you must reboot the system. Installing SLS OSS601A on SCO OpenServer 5.0.2 ---------------------------------------------- 1. Prepare the media for installation. Download the OSS601A VOL files from the SLS/oss601a directory on SCO's ftp site. Place the files in the /tmp directory on the local system. The files should include: VOL.000.000 VOL.001.000 VOL.002.000 VOL.003.000 VOL.004.000 oss601a.ltr 2. Log in as root and run the Software Manager with the command: # scoadmin software or double-click on the Software Manager icon in the desktop. 3. It is STRONGLY RECOMMENDED that you DO NOT LOAD SLS OSS601A before applying it. There is a known problem with SLS OSS601A where if you load the SLS and then apply it, and then later unload it BEFORE rolling it back, you will lose your libc.so.1 and your system will become unusable. So the best way to avoid this problem is to NOT load SLS OSS601A. Instead, follow the steps given below and apply the SLS directly from the media images. 4. Pull down the "Software" menu and select "Patch Management -> Apply Patch". 5. You will see the "Begin Apply Patch" menu. Be sure the local machine name is selected and choose "Continue". 6. In the "Select Media" window, pull down the "Media Device" menu. Select "Media Images", then "Continue". 7. When prompted for the "Image Directory", enter "/tmp" (or the directory where you placed the VOL files in step 1) and select "OK". Note: If you are installing from the Year2000 Resource CD the location of this supplement is: /patches/oss601a/ 8. Next you will be prompted to select the software to install. SLS OSS601A contains two components: the Year 2000 Supplement and a Software Manager patch FOR SCO OPENSERVER 5.0.4 ONLY. If your system is running OpenServer 5.0.2, you do not need to, and will not be able to, install the Software Manager patch. Make sure that ONLY the "Year 2000 Supplement for SCO OpenServer 5.0.2 and 5.0.4" entry is highlighted and choose "Full" to continue. 9. You may see a message informing you that verification errors were found for the files .../pack.d/crllry/Driver.a and/or .../pack.d/str/Driver.o. You may safely ignore this message. Choose "Continue". 10. Once the installation finishes, select "Exit" from the "Host" menu. Installation of SLS OSS601A to your hard disk is complete. 11. After applying OSS601A, you must reboot your system in order for the Y2K fixes in the dynamic shared C language library (libc.so.1) to become fully active. You do not have to reboot immediately. However, you MUST reboot before January 1, 2000. We strongly recommend that you reboot as soon as possible after installing OSS601A. There are no problems that are currently known to occur when the system is in the state of having the patch applied, but not having been rebooted. However, we have not conducted any methodical testing of a system in this state. Therefore, we recommend that you avoid leaving your system in this state for an extended length of time. Removal Instructions for SCO OpenServer 5.0.2 --------------------------------------------- Note: Patches must be removed in the reverse order in which they were installed on a per-component basis. The "Year 2000 Supplement for SCO OpenServer 5.0.2 and 5.0.4" patches the BaseX, Desktop, MailUA, TclX, TclXds, Unix, WServer, adminfw, tcp, and unixds components on OpenServer 5.0.2. If any of these components were patched after OSS601A was installed, you must remove those later patches before removing OSS601A. To remove SLS OSS601A: 1. Log in as root. 2. Execute the command: # scoadmin software or double-click on the Software Manager icon in the desktop. 3. Pull down the "Software" menu and select "Patch Management -> Rollback Patch". 4. You will see the "Begin Rollback Patch" window, which allows you to select the patched software to remove. Select the component you wish to remove and choose "Continue". 5. You will see the "Patch Selection" window. Make sure the Y2K patch for the component that you have chosen is selected and choose "Continue". 6. You will see the "Confirm Selected Patches" window. Choose "Rollback" to confirm removal of the Y2K patch for the selected component. 7. When you roll back the "SCO UNIX System V Operating System" component, you may see a message informing you that verification errors were found for the files .../pack.d/crllry/Driver.a and/or .../pack.d/str/Driver.o. You may safely ignore this message. Choose "Continue". 8. When the removal finishes, repeat steps 3 through 6 for each component of OSS601A. 9. Once the last removal finishes, select "Exit" from the "Host" menu. 10. In order for the removal of OSS601A to take full effect, you must reboot the system. If you have questions regarding this SLS, or the product on which it is installed, please contact your software supplier.