Problem
I have source files that are under SCCS (Source Code Control System)
control. After recording a change in a source file ("s-file") with
the delta(CP) command, or creating a new s-file with the admin(CP)
command, I find that subsequent attempts to get(CP) the file fail
with the error:format error at line 3 (co4)If I examine the contents of the s-file, I find that the previous
delta was recorded with a corrupted date stamp. Specifically, I
have recorded the change after 01 January 2000 at 12:00 AM and ":0"
appears in the two-digit year field instead of "00". A subsequent
get(CP) on this file therefore fails with the above error.I have either loaded or applied the appropriate Year 2000 Supplement for my product configuration and the problem still persists.
Cause
The development system components of the appropriate year 2000 Supplement have not been properly applied.
The delta(CP) and admin(CP) commands have a known problem writing correct date stamps to the s-file after 01 January 2000 on SCO OpenServer Release 5.0.0 with Development System Release 5.0.0, SCO OpenServer Release 5.0.2 with Development System Release 5.0.2, and SCO UNIX Release 3.2v4.2-based operating systems with their corresponding Development Systems. For each of these product combinations, the problem is fixed by the Year 2000 Supplement for that combination (see SOLUTION below).
In the vast majority of reported cases, the problem persists because
of an inadvertent failure to properly apply the Development System
portion of the appropriate Year 2000 Supplement. Among the frequent
types of failures are the following:(a) Installing OSS601A, OSS603A, or UOD426D before installing the Development System.
(b) Installing the OpenServer Development System Release 5.0.0 on
OpenServer Release 5.0.2; subsequent installation of OSS601A
has no effect since this supplement does not patch 5.0.0
Development System components.(c) LOADING the patch but not APPLYING it; the patch is configured for network install to other systems, but has not actually patched the software on the present system.
NOTES: SCO OpenServer Release 5.0.0, 5.0.2, and SCO UNIX Version 4.2
products are currently not supported. SCO OpenServer Release 5.0.0
is currently not year 2000 warranted.Since SCO OpenServer 5.0.0 is a retired product, OSS603A can only be obtained from Retired Products web page at:
https://wdb1.sco.com/clbk_web/owa/y2k_region Solution
These problems are fixed by the existing year 2000 supplements for
these product configurations, when these are installed properly
after installation of the Development System is complete. The
supported product combinations are listed below:Product Combination Supplement required
after install of product
combination
------------------- ------------------------OpenServer Release 5.0.2 + OSS601A
Development System Release 5.0.2OpenServer Release 5.0.0 + OSS603A
Development System Release 5.0.0UNIX Release 3.2v4.2 or Open Desktop 3.0 UOD426D
+ Development System Release 3.2v4.2 or
Open Desktop Development System Release
3.0(Hereafter, "Development System" shall be abbreviated as "DS".)
The problem persists because the DS portions of the required supplement were not properly applied to the system.
To resolve this situation, please follow these steps; if any step does not apply to your particular set of products, skip over it:
(1) If you are running SCO OpenServer Release 5.0.2, start the
Software Manager or custom(ADM) utility and check the listing of
installed products for the version of the SCO DS. It should be
"ver 5.0.2b" and not "ver 5.0.0a".(2) If the 5.0.0 DS (ver 5.0.0a) is installed on OpenServer 5.0.2, you should upgrade to the 5.0.2 DS (ver 5.0.2b).
(3) If you are already running one of the supported combinations listed above, then it is likely that the supplement was applied before installing the DS, or that this patch was LOADED but not APPLIED.
NOTE: There is no notion of LOADING versus APPLYING a patch on
SCO UNIX 3.2v4.2 systems. Thus, if you are running a 3.2v4.2-based
operating system + DS, you have installed UOD426D, and continue
to experience the SCCS problem described above, it is likely that
UOD426D was installed before the DS or that UOD426D did not install
properly.To APPLY OSS603A to 5.0.0 systems or OSS601A to 5.0.2 systems
choose Software->Patch Management->Apply Patch in the Software
Manager. The available options allow you to apply a patch from the
hard disk (a loaded patch) or to perform a partial install (apply)
of the DS components.If this operation fails, then try to roll back and reapply the patch.
To reinstall UOD426D, invoke the custom(ADM) utility in single-user mode and follow the instructions in the accompanying cover letter to first remove and then install the supplement.
NOTE: On OpenServer 5.0.2 systems, do not UNLOAD OSS601A before rolling it back, as this is known to cause significant problems. See ta110335 for more information on this.
(4) Fix the corrupted s-files manually, replacing ":0" with "00", and run:
admin -z <s-file>(5) Test out further gets and deltas of existing s-files with the new binaries and see if this resolves the situation entirely.
See also
ta110715, "After installing SLS UOD426D, the get -e command fails."
ta110166, "What is addressed by SLS OSS603A, the Year 2000 Supplement for SCO OpenServer 5.0.0 with rs500d and net100?"
ta110091, "Special notes and recommendations before installing
OSS601A, the Year 2000 Supplement for SCO OpenServer 5.0.2 and
5.0.4."ta110077, "What is addressed by SLS OSS601A, the Year 2000 Supplement for SCO OpenServer 5.0.2 and 5.0.4?"
ta110051, "What Date and Time processing fixes are included in SLS OSS601A?"
ta109923, "What is contained in SLS UOD426D, the Year 2000 SLS for SCO UNIX and Open Desktop?"