Subject: | |
From: | |
Reply To: | |
Date: | Fri, 20 Jun 1997 15:49:54 GMT |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
We have someone here who has gotten the dubious privilege of determining
Year-2000 compliance in just about anything and everything that runs on our
HP3000s.
She came to me to ask if there where any way she could set the session date
to some desired date and then back again without messing around with the
system date. (I am, you probably understand, somewhat reluctant to pop the
system date ahead a few years, run stuff, then set it back to present.
<Shudder - Just Shoot Me Now.>)
Soooo, here I am, asking if anyone has found some really nifty ways to do
this?
Does anyone have any suggestions on doing Year 2000 compliance testing?
At the risk of proving my ignorance, is there any way to trap a date
intrinsic call and report something else?
(I came across the SETDATE program at Jazz, which works Pretty Darn Nicely,
but I need something more.)
Many many TIA,
Curtis
|
|
|