[prev in list] [next in list] [prev in thread] [next in thread] 

List:       hpux-admin
Subject:    [HPADM] [SUMMARY] HP-UX is Y2K compliant
From:       mlazar () mobility ! com
Date:       1997-08-29 21:17:00
[Download RAW message or body]

Thanks to all for responding, I received around 9 replies.

The overwhelming response was that HP-UX v 10.01 is not Y2K compliant
without patches.
Bill Hassell provided the following helpful message:


                Year 2000: How HP-UX Calculates Time
                ------------------------------------

HP-UX and the year 2000
 -----------------------

Virtually every company will be affected by the year 2000 problems.  For
the most part, the issues are with legacy programs and datafiles which
used only 2 digit or single byte values to represent the year with an
assumption that the current century is 1900.  Unfortunately, these
programs and/or the datafiles cannot handle the year 2000 and beyond.
Ideally, all these programs will be scrapped and rewritten by that time.

However, there are some operating system limitations that will affect
even
correctly written programs.  HP-UX versions prior to 10.20 will not
handle
the year 2000 correctly.  This includes all versions of 9.xx and
earlier.

The objective of the 2000 Rollover Program in 10.30 is to ensure HP-UX
becoming Year 2000 Safe (work beyond year 2000).  The scope of this
program
is at the opsystem core level.  It does NOT imply that all applications
that
are HP-UX based will be year 2000 safe.  Here are some of the reasons
why:

 -- It is clear at this point that during the 2000 Rollover Program, one
of
   the major problems was the misinterpretation of the date field by
HP-UX
   code at the core level.  Thus, it is highly possible the same kind
error
   lies in the application level code.

 -- Applications may have their own defined "date" data field.  These
date
   fields as well as all of their dependent applications would have to
be
   rewritten in order to avoid the year 2000 problem.

So, in order to determine if a particular application is 2000 safe or
not,
the programmer really needs to look at the code that is built on top of
the
opsystem calls.  This includes date calculations which may overflow or
undeflow due to inadequate choices for numeric precision.



How HP-UX calculates time
 -------------------------

HP-UX converts dates from applications to seconds, with 1970 as the
starting
point (more specifically, January 1, 1970, 0:00:00).  In a 32-bit OS,
this
means that the time counter is "maxed out" in year 2038, with 2037 as
the
highest year HP-UX supports.

Presently, HP-UX 10.20 and earlier will not always calculate dates after
2000
correctly.  This shortcoming will be corrected in HP-UX 10.30, due out
in
late 1997.  However, because 10.30 is still based on 32-bits internally,
it is
still subject to the 2037 time maximum.  Keep in mind that 2037 is about
40
years away, a time frame where the design of future computers and
opsystems
can only be guessed.

Once HP-UX goes to 64-bit, this maximum time constraint goes away,
because the allowed time range increases by 2^32, a very large number.
It is doubtful that any HP-UX systems will exist when that 64 bit value
reaches the maximum.


In summary, the current (unpatched) HP-UX opsystem status is:



9.xx  10.01/.10  10.20  10.30 64-bit+

----   -------------   -------   -------  -------
Calculates post-2000 dates correctly         no      no             no
yes   yes
Handles dates 2037 and beyond                no      no             no
no      yes
Patches to meet Year-2000 compliance   no      yes     yes


------------------------------------------------------------------------
--

    Year 2000 patches for 10.01
    ---------------------------

    1.   cron/at     PHCO_10112
    2.   date        PHCO_10111
    3.   rlog/co     PHCO_10110
    4.   libc        PHCO_9419
    5.   inet/mailx  PHNE_9379
    6.   inet/elm    PHNE_9859
    7.   inet/ftp    PHNE_9181
    8.   netTL       PHNE_9424
    9.   SSHA/mkboot PHCO_9012
    10.  SSHA/sar    PHCO_8819
    11.  LVM         PHCO_8624
    12.  audisp      PHCO_7933
    13.  SAM         PHCO_8131
    14.  Cold Inst   PHCO_9648
    15.  kermit      PHCO_9497
    16.  kernel/HIL  PHKL_10143 (s700 only, no s800 patch required)
    17.  libc        PHCO_10175 (Compatibility White Paper)


    Year 2000 patches for 10.10
    ---------------------------

    1.   cron/at     PHCO_10120
    2.   date        PHCO_10121
    3.   rlog/co     PHCO_10122
    4.   libc        PHCO_8981
    5.   inet/mailx  PHNE_9379
    6.   inet/elm    PHNE_9859
    7.   inet/ftp    PHNE_9181
    8.   netTL       PHNE_9425
    9.   SSHA/mkboot PHCO_9013
    10.  SSHA/sar    PHCO_8819
    11.  LVM         PHCO_8625
    12.  audisp      PHCO_7934
    13.  SAM         PHCO_8130
    14.  Cold Inst   PHCO_9648
    15.  kermit      PHCO_9507
    16.  kernel/HIL  PHKL_10142 (s700 only, no s800 patch required)
    17.  libc        PHCO_10175 (Compatibility White Paper)

    Year 2000 patches for 10.20
    ---------------------------

    1.   cron/at     PHCO_10123
    2.   date        PHCO_10124
    3.   rlog/co     PHCO_10125
    4.   libc        PHCO_8979
    5.   inet/mailx  PHNE_9381
    6.   inet/elm    PHNE_9860
    7.   inet/ftp    PHNE_9785
    8.   netTL       PHNE_9081
    9.   SSHA/mkboot PHCO_9014
    10.  SSHA/sar    PHCO_8820
    11.  LVM         PHCO_8626
    12.  SAM         PHCO_8133
    13.  kermit      PHCO_9508
    14.  kernel/HIL  PHKL_9921 (s700 only, no s800 patch required)
    15.  kftpd       PHNE_9786
    16.  libc        PHCO_10175 (Compatibility White Paper)

--
             ---> Please post QUESTIONS and SUMMARIES only!! <---
        To subscribe/unsubscribe to this list, contact majordomo@cv.ruu.nl
  Name: hpux-admin@cv.ruu.nl                 Owner: owner-hpux-admin@cv.ruu.nl
 
 Archive:     ftp.cv.ruu.nl/pub/digests/hpux-admin       (FTP, browse only):
   *NEW*:     http://www.dutchworks.nl/htbin/hpsysadmin   (Web, browse & search)

[prev in list] [next in list] [prev in thread] [next in thread]