Dear SCO Customer, Support Level Supplement (SLS) CMW489B, the Year 2000 Supplement, corrects date-related problems reported on SCO CMW+ Release 3.0.1. SLS CMW489B resolves several separate and specific date-related problems, described below, in the above operating systems and SCO products. Other SCO products, third party applications, or SCO SLSs may be affected by the same date-related problems: 1. The "century" problem. Some binaries and utilities will not correctly recognize the switch over from the 20th century to the 21st century when the system's date changes from 1999 to the year 2000. This can cause other utilities, such as the script asktime(ADM), which make use of one or more of the affected binaries and/or utilities to incorrectly revert back to the beginning of the 20th century. The binaries and utilities affected by this problem are: /bin/touch /etc/setclock /lib/cvtdate /usr/bin/X11/XIsso /usr/bin/at To correct the century problem SLS CMW489B installs fixed versions of the binaries and utilities listed above. 2. The "leap year" problem. Many commands and utilities do not display dates after February 28, 2000 correctly. For example, running the following command to set the date to Tuesday, February 29, 2000: # date 0229101000 will set the date to Tuesday March 1, 2000 instead. The affected binaries and utilities do not correctly recognize the year 2000 as a leap year, hence a day is skipped over. The problem was found to be a bug in a version of an SCO development system library used to build the affected binaries and utilities. To correct this problem, SLS CMW489B installs a binary patch, fix2000, which is run to find all affected binaries and utilities and patch in the corrected code. 3. Incorrect date in mail headers. On systems where the date is set to the year 2000 and beyond, the date reported in the mail headers will be incorrect. To correct this problem SLS CMW489B installs fixed versions of the affected mailer binaries. The mailer binaries affected by this problem are: /usr/bin/mail /usr/bin/mlist /usr/bin/rmail /usr/bin/rcvfile /usr/bin/rcvtrip /usr/bin/resend /usr/lib/sendmail 4. Some lp interface scripts have the wrong date format. The following lp interface utility is restricted to displaying years in 2-digit format: /usr/spool/lp/bin/text2post To correct this problem SLS CMW489B installs a fixed version of this utility with the date correctly coded to use 4 digits. 5. SCCS delta/get functions do not handle dates in year 2000 correctly. When the system date is set to the year 2000 or beyond, and you insert a new version of a program into SCCS, SCCS will subsequently display an incorrect date for the insertion of the new program into SCCS and will report an error. To correct this problem SLS CMW489B installs fixed versions of a number of SCCS binaries. All SCCS binaries except for 'help' are affected. The affected SCCS binaries are: /usr/bin/admin /usr/bin/cdc /usr/bin/comb /usr/bin/delta /usr/bin/get /usr/bin/prs /usr/bin/rmdel /usr/bin/sact /usr/bin/sccsdiff /usr/bin/unget /usr/bin/val /usr/bin/vc /usr/bin/what (NOTE: This problem will only be seen if the SCO UNIX System V/386 Development System is installed on the system.) INSTALLING SLS CMW489B Note: Remove any previous versions of CMW489 before installing CMW489B. To install SLS CMW489B, follow the attached procedure. It is important that you read the "Notes" section first before installing SLS CMW489B. 1. Bring the system into single-user mode, and log in as root. 2. Prepare the media for installation. Download the CMW489B media image file (cmw489b.Z file), place the file in the /tmp directory, uncompress anddd the file to a formatted floppy by typing the following commands: uncompress /tmp/cmw489b.Z dd if=/tmp/cmw489b of=/dev/rfd0135ds18 3. At the shell prompt, invoke custom(ADM): custom Insert the SLS floppy when prompted to do so. 3. Choose the option: Install->A New Product->Entire Product 4. At the following prompt: Insert CMW489B : SCO CMW+ Year 2000 SLS Floppy Volume 1 check to ensure that the floppy is still in the floppy drive and press . Insert the second SLS floppy volume when prompted to do so. 5. After several messages indicating the progress of the installation of this SLS, you will see a message informing you that files are now being fixed by the binary fix2000(ADM) installed by SLS CMW489B. At this stage, the binary is being applied to all files and utilities that are known to be broken for the operating system and any products installed on your system. NOTE: Depending on the speed of the machine and how many files will require correcting, this part of the installation may take some time. 6. After the binary has found and corrected all the required files, a message will be displayed to say that all files corrected have first been saved to a backup directory. The script will display how much disk space has been taken by the backup files and you will be prompted as to whether you want to archive the backup or keep the backup files on the hard disk. Enter "y" if you want to archive the backup files to a backup medium, or "n" if you want to keep the backup directory on the system. Refer to (2) in the Notes section for more details. The installation is now complete. Once SLS CMW489B has been installed, the binary supplied with this SLS, fix2000(ADM), is left on the system as /usr/bin/fix2000. This binary can be used to check for other applications whose files may require correcting. The list of known broken files and utilities in SCO operating systems and known affected SCO products are kept in the directory: /usr/lib/custom/cmw489/fix Lists are provided for SCO CMW+ (uod), SCO MPX (mpx), SCO Office Portfolio (op2) and Microsoft Word for UNIX systems (wrd). (NOTE: The file list for SCO CMW+, uod, also includes the list of affected SCCS binaries from the development system.) If necessary, fix2000(ADM) can be run against these lists to recheck the files, or to check and correct any file that has been reinstalled after SLS CMW489B. If any parts of the operating system, or one of the known affected SCO applications, is reinstalled, it is highly recommended that fix2000(ADM) is run against the appropriate list(s). Additionally, should other SCO products or applications, and any non-SCO products or applications, be installed either before or after SLS CMW489B, it is advisable to check these as well. For further information on the binary fix2000(ADM), see the supplied manual page. This is available online, and a hard copy is provided in the Notes section below, under Note (1). REMOVING SLS CMW489B To remove SLS CMW489B from your system: 1. Log in as "root" in single-user mode. 2. At the shell prompt, invoke custom(ADM): custom 3. Choose the option Remove, highlight the SCO CMW+ Year 2000 SLS to select it, and press . 4. Choose the package "ALL" from the list of packages. 5. Answer "Yes" when prompted if you wish to continue with the removal. 6. If you had previously archived the saved files in the backup directory to a backup medium and removed the backed up files from the system, you will be prompted to insert the backup medium to restore the backup area. See note (3) in the Notes section for further details. 7. All the original files previously saved during the installation of SLS CMW489B are now restored, and the binary fix2000(ADM) and its manual page is removed from the system. The removal is now complete. Notes ===== 1. fix2000(ADM) Provided below is a copy of the manual page for the fix2000(ADM) binary. Note This is not available as part of the standard SCO operating system environment. fix2000(ADM) was specially produced for SLS CMW489B. fix2000(ADM) 15 January 1996 fix2000(ADM) Name fix2000 - Check for and fix known bug which causes dates after 28th February, 2000 to be printed incorrectly. Syntax fix2000 [ -ipv ] file ... Description The command without options will scan the specified 'file'(s) to determine whether a known bug is present in 'file'(s) which causes the command to handle dates after 28th February, 2000 incorrectly. Its exit status indicates whether or not the bug is present in any of the 'file'(s), and so it is generally more useful to run it on a single 'file' at a time. The following options are recognized: -v Prints name of 'file'(s) which contain the bug on standard output. -p Attempts to fix the bug where present. This will fail if the 'file'(s) cannot be opened for writing. -i Interactive version of '-p' above. Will prompt for confirmation before attempting to fix each 'file' containing the bug. Examples A list of all binaries in the system containing this bug can be printed using the following: find / -type f -exec fix2000 -v {} \; Diagnostics Exit status is 0 if any occurrences of the bug are found, 1 if no occurrences of the bug are found, and 2 for usage errors or inaccessible files. Notes The fix2000 utility knows about five different variations of the same bug. There may be more, in which case the command will need to be updated to cater for these. 2. Archiving the backup directory The backup directory, /usr/lib/custom/cmw489, is a backup of all the files that have been corrected by SLS CMW489B. At the end of the installation procedure, you will be told how much space is taken up by the entire backup directory. You can choose whether or not to archive the backup directory to an archive medium of your choice, and whether or not to leave the backup directory in place. Archiving the backup directory to an archive medium will allow you to remove the backup directory, thus freeing up the extra hard disk space. Should you choose to archive the backup directory, this can be done either during the installation of SLS CMW489B, or afterwards. Choosing to archive the backup directory after SLS CMW489B has been installed allows any further applications (whether SCO or non-SCO) that were not checked and corrected during the installation of SLS CMW489B to be backed up. If you choose to archive the backup directory during the installation of SLS CMW489B, you can choose to remove the backup files at the same time, or leave the backup directory in place. Choosing the option to remove the backup files at the same time as archiving them will not completely remove the entire backup directory. You will be left with just the lists of known broken files and utilities. If you choose to remove the backup afterwards, the entire backup directory will be removed. It is recommended that you choose to archive the backup directory during installation, then answer 'yes' to remove the backup files. The files that are left, the lists of known broken files and utilities, take up a negligible amount of space on the hard disk and can be used by fix2000(ADM) to recheck the corrected files. It is also recommended that the backup directory be archived to a tape or DAT device, although any valid device can be specified. Free disk space requirements for installing SLS CMW489B will depend on the default software installed and the total number of files requiring correction. You should ensure you have a minimum of 20MB free disk space for the full SCO CMW+ system and development system. This figure needs to be increased if you have additional products installed. 3. Removing SLS CMW489B If removing SLS CMW489B, you must have a valid backup directory present on the system, or a valid archive. SLS CMW489B will not be removed if no backup is available. Please ensure that any archive of the backup directory taken is valid, can be read, and is kept in a safe location. 4. SLS CMW489B logfile A logfile is created by SLS CMW489B if this is the first installation. The logfile is found in /usr/lib/custom/cmw489.log. If SLS CMW489B has been installed before and is being installed for a subsequent time, the previous logfile is backed up to /usr/lib/custom/cmw489.log.bck. The logfile can be used to check the installation and removal of SLS CMW489B. It is useful to see what files have been saved and modified, and to debug the installation or removal of SLS CMW489B should there be problems. 5. Using fix2000(ADM) If fix2000(ADM) is to be used after SLS UOD426C has been installed to check files from any SCO products and/or non-SCO products, it is important to note that fix2000(ADM) does not automatically back up files to be patched. fix2000(ADM) only patches the affected files. You must ensure that you first back up any files to be patched before running fix2000(ADM). You should first use fix2000(ADM) to generate a list of the files to be patched, then create a simple script to back up files to be patched before running fix2000(ADM). If you do not do this, any files that are patched by fix2000(ADM) will not be saved and you will not be able to restore the original files. If you have questions regarding this SLS, or the product on which it is installed, please contact your software supplier.