HP3000-L Archives

October 1998, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Glenn J. Koster, Sr." <[log in to unmask]>
Reply To:
Date:
Wed, 28 Oct 1998 11:13:01 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (34 lines)
After searching the archives, I found a message thread back in February
(and into March) regarding a bug with MPEX and February 29, 2000.   MPEX
aborted with a system date of 2/29/2000 on version "26N70813".

This past weekend we upgraded to the latest patch level of MPE/iX 5.5.
At the same time we upgraded to a newer patch of MPEX.  Now we have the
problem again - kind of.  If we use TimeMachine to set the date to
2/29/2000, MPEX aborts (on a call to DATEBUILD - invalid parameter).
However, if we actually set all of the appropriate machine clocks to
2/29/2000 (with SETCLOCK), everything is fine.  All other Y2K dates work
fine under both scenarios.

Has anyone else had any experience with this type of problem since the
original posting in February.  I guess what we are really trying to
determine at this point is where the problem lies - TimeMachine or
MPEX.  My initial reactions aside, I suspect TimeMachine...

BTW:  We went to release 27N80324 of MPEX - which is supposed to be a
Y2K compliant version.

Glenn
--
 ______________
|  Navigators  | Under contract to Hewlett-Packard ISG (Greeley, CO)
|     |)       |
|     | )      | Glenn J. Koster, Sr.             [log in to unmask]
|     |  )     | Managed Business Solutions    http://www.mbsnav.com
|     |   )    | 214 S. College, Suite 201              970 350-5337
|     |----    | Fort Collins, CO  80524                970 224-1016
| ============ |
| \__________/ |
|   of Change  | aka:  [log in to unmask]
|______________| home: http://members.aol.com/MichiTex

ATOM RSS1 RSS2