Problem
What date and time processing problems are fixed in Support Level Supplement (SLS) OSS601A?
Solution
SLS OSS601A addresses a number of date and time processing issues on SCO OpenServer 5.0.2 and SCO OpenServer 5.0.4 based systems.
The issues addressed by this SLS are:
asktime(ADM) does not support entry of a 4-digit year. Associated SCO tracking number: RUS-1-26
auditsh(ADM) parses 2-digit dates incorrectly past 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 2-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 year to 19YY 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
Localized fptd(NADM) hardwires the first 2 digits of the year to 19 when creating date stamps. Associated SCO tracking number: RUS-1-32
getdate(S) can generate unreliable results if "%y" is used in the DATEMSK for the API and the year is 2000. Associated SCO tracking number: RUS-1-39
lastlogin(ADM) has been updated to interpret 2-digit years correctly in 2000 and beyond. Associated SCO tracking number: RUS-1-22
brand(ADM) dumps core in the year 2015 and beyond. Associated SCO
tracking number: SCO-236-772localtime(S) produces unreliable results when used with pre-Epoch dates, that is, 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 2 digits of the year to 19 by
representing the date as "19%y" instead of "%Y". Associated SCO
tracking number: DAV-2-14text2post(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 2-digit year representing a year greater than 1999. Associated
SCO tracking number: RUS-1-11mktime(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
RUS-1-5: The Network Node Check Manager writes the date as a 2-digit
value on the "Alert" window and in the history logfile when the node
is unreachable. Associated SCO tracking number: RUS-1-5passwd(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-1272prfpr(ADM) uses a 2-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-7sar(ADM) report header displays the year 20YY as 1YY. Associated
SCO tracking number: SCO-244-167SCCS s.* files maintain the year as 2 digits and do not treat
2-digit years as per the X/Open specification. Modified sccs(CP)
to treat 00-69 as 2000-2069. Associated SCO tracking number:
SCO-59-8645scomail(XC) displays a 1-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 2-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-38The System Time Manager does not accept/display 4-digit years in
the year input field. Associated SCO tracking number: SCO-59-8655 See also
ta109280, "OpenServer 5.0.4 mktime(S) doesn't correctly handle the leap year in year 2000."
ta109721, "mktime(S) does not normalize the tm structure correctly."
ta110050, "What Date and Time processing fixes are included in SLS OSS600A?"