Technical article 110166

What is addressed by SLS OSS603A, the Year 2000 Supplement for SCO OpenServer 5.0.0 with rs500d and net100?

OpenServer 5.0.0

Written · Last revised

Problem

There are a number of date and time processing issues found with SCO OpenServer 5.0.0, many of which are associated with Year 2000 (Y2K) and century problems.

What issues are addressed by Support Level Supplement (SLS) OSS603A, the Year 2000 Supplement for SCO OpenServer 5.0.0 with Release Supplement 5.0.0d (rs500d) and the Networking Supplement 1.0.0 (net100)?

Solution

SLS OSS603A addresses a number of known date and time issues with SCO OpenServer 5.0.0.

See the attached cover letter for more information about this SLS, including a list of specific problems addressed and installation instructions.

See also

ta110079, "What is addressed by SLS OSS600A, the Y2K SLS for SCO OpenServer 5.0.5 and RS505A?"

ta110077, "What is addressed by SLS OSS601A, the Year 2000 Supplement for SCO OpenServer 5.0.2 and 5.0.4?"

Dear SCO Customer,
Support Level Supplement (SLS) OSS603A, the Year 2000 Supplement for SCO
OpenServer 5.0.0 with Release Supplement 5.0.0d (rs500d) and the Networking
Supplement 1.0.0 (net100), corrects a number of problems in date and time
processing in SCO OpenServer Release 5.0.0.  See the list below for more
information on specific problems addressed by this SLS.
Software Notes and Recommendations
----------------------------------

SLS OSS603A should only be installed on these releases with Release Supplement 5.0.0d (rs500d) and the Networking Supplement 1.0.0 (net100) applied:

SCO OpenServer Enterprise System Release 5.0.0 SCO OpenServer Host System Release 5.0.0 SCO OpenServer Desktop System Release 5.0.0

In addition, there is some optional software which must NOT be applied after SLS OSS603A:

- UnixWare/OpenServer Development Kit 7.0.0 - SLS OSS465B, the Scomail Supplement for SCO OpenServer 5.0.0

If you want to apply any of the above optional software at any time after
applying SLS OSS603A, you must remove OSS603A, install the optional software,
and then reinstall OSS603A.  Otherwise, the above software will either
overwrite some of the fixes that are included in SLS OSS603A, or will fail
to install.  (If you are using the UnixWare/OpenServer Development Kit 7.0.0,
see the SCO Year 2000 Web Page for Y2K information about that product.)
IMPORTANT NOTE: After applying SLS OSS603A, 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.
SLS OSS603A 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
-------------------------
1. Prepare the media for installation.

Download the OSS603A VOL files from the SCO Retired Products web page located at:

https://wdb1.sco.com/clbk_web/owa/y2k_region

Place the files in the /tmp directory on the local system. The files should include:

VOL.000.000
VOL.001.000
VOL.002.000
oss603a.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 "Patch Management -> Apply Patch".

4. You will see the "Begin Apply Patch" menu.  Be sure the local
   machine name is selected and choose "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 select "OK".

7. Next you will be prompted as to whether you wish to do a full
   or partial installation of the "Year 2000 Supplement for SCO
   OpenServer 5.0.0."  Choose "Full".
8. Once the installation finishes, select "Exit" from the "Host"
   menu.  Installation of SLS OSS603A to your hard disk is complete.
9. After applying OSS603A, 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 OSS603A.  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
--------------------
Note: Patches must be removed in the reverse order in which they were
installed on a per-component basis.  SLS OSS603A patches the BaseX,
Desktop, MailUA, TclX, TclXds, Unix, WServer, adminfw, tcp, and unixds
components on SCO OpenServer 5.0.0.  If any of these components were
patched after OSS603A was installed, you must remove those later patches
before removing OSS603A.
To remove SLS OSS603A:
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 the removal finishes, repeat steps 3 through 6 for each component of OSS603A.

8. Once the last removal finishes, select "Exit" from the "Host" menu.

9. In order for the removal of OSS603A 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.

From the Xinuos technical article database, record 110166. Reproduced with permission. The original is at www.sco.com/ta/110166, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.