Problem
What Year 2000 problems are fixed if SCO OpenServer 5.0.5 Release Supplement 505A (rs505a) is applied to my system?
Solution
The following Year 2000 time and date processing problems have been addressed by the SCO OpenServer Release Supplement 505A:
1. mktime(S) does not recognize February 29, 2000 as a leap year and, in some circumstances, does not normalize the tm data structure correctly.
Note: tm is a data structure used by UNIX APIs. The structure is defined in /usr/include/time.h. tm_year is the year element of the structure.
2. asktime(ADM) does not allow entry of a 4-digit year.
3. The System Time Manager does not support entry of 4-digit years.
4. The calstat utility writes tm_year to its log file resulting in 3-digit years after 1999.
5. dclock(XC) is hardwired to display 19<yy> from within the show_date() function of the binary.
6. lastlogin(ADM) does not write a 4-digit year to /usr/adm/acct/sum/loginlog.
7. The Node Check Manager does not write a 4-digit year to its log file and the screen.
8. prfpf(ADM) does not write a 4-digit year to its date stamps.
9. ftpd(ADMN) has 19 hardcoded into some of the localized message catalogs that come with the binary.
10. The rtc(HW) does not write the CMOS century byte.
11. The Backup Manager does not support 4-digit dates.
12. auditsh(ADM) interprets 99 as 2099 once the date on the system is beyond 1999.
13. mailx(C) hardwires email with 2-digit year headers to 19.
14. setclk(ADM) and getclk(ADM) do not support setting of the CMOS Century byte.
15. scomail(XC) only used a 2-digit year in its email summary window.
16. prs(CP) uses tm_year to display file creation dates resulting in a value of 100 in the year 2000.
17. strptime(S) writes %y values directly into tm_year. This means that a 00 value is interpreted as 00+1900.
See also
For more background on Year 2000, see:
http://www.sco.com/year2000