I wrote:

> True as far as it goes, but HourGlass 2000 *will* let you set the date
> past 2027 if you so desire (hey, we figure if you want to, why should we
> stand in your way?).
>
> We've tried it (and so have some of our users) and the machine doesn't
> actually catch fire.  Some parts of MPE produce "interesting" results, but
> nothing that would keep you from testing your applications to see how
> they'll behave.
>
> When I set the date to 11/25/2099, I get the following dates returned from
> various MPE utilities and INTRINSICs:
>
> NOV 25, 1971
> NOV 25, 2027
>
> and my favourite: Sun Oct 20 08:16:58 PDT 1963
>
Shawn responded:
> That would appear to be a good argument for not doing it.  If you are
> going to get "interesting" but incorrect results, then the value of the
> capability seems to be diminished.
>
> Shawn

So your argument is: "you know MPE has problems past the year 2027, so there
isn't any need to test your applications for dates >2027"?  I can't agree
with that.  Knowing that there are problems isn't the same as knowing what
the problems are; and, the results you get in your application code may be
different than the results returned by various MPE utilities and commands.
Finally, I never said the ability to set the date >2027 had great value -- I
merely said that HourGlass would let you do so, should you so desire.

<plug>
The greatest value that HourGlass provides is it's unique ability to
intercept ALL date/time calls.  It's the only date simulation tool on the
market that enables you to really, fully, test how your applications will
behave when the system clock clicks over on January 1, 2000.
</plug>

---
Michael D. Hensley       | mailto:[log in to unmask]
Allegro Consultants Inc. | Visit scenic http://www.allegro.com
408/252-2330             | "Support Bill of Rights Enforcement"