I administer a small installation with a 935.  I've noted the recent
discussion of HP's lack of commitment to support post-2000 operating
system support for our particular box because it will officially be obsolete
by the time the year 2000 rolls around.  It does not look like it is in the
cards that we will be upgrading the box any time soon (variety of
reasons not relevant to this post).

We've done some testing, though not to the level of restarting our
machine with a post-2000 date.  All we have found (so far) that may not
work on that fateful Saturday, the first of January, 2000, are two
operational things.

The first is the :STREAM command which seems not to want to
recognize a post-2000 date.  The issue are for those jobs that are
scheduled prior to the "witching hour" of 23:59, 31Dec1999.  I assume
that later the next day, on 1Jan2000, if a job is scheduled, ":STREAM
MYJOB;DATE=01/23/00" that the job will wait to run on 23Jan2000 and
not execute immeadiately thinking that the job was to be run 23Jan1900.
Is that a good assumption?

The workaround is to use the ";IN=days" parameter.  If, on 15Dec1999, I
stream the same job, I should do it so - ":STREAM MYJOB;IN=39".  The
interesting thing about this is that this :STREAM problem seems to be a
general MPE/ix problem, not a specific 935 box problem.  Am I right in
thinking that the rest of you who have managed to afford to stay current
with HP3k technology will face the same problem?

The second "gotcha" is more of a problem for us.  We use Sleeper
(version 3.0) for our automated job scheduling.  This Sleeper doesn't
want to deal with post-2000 dates.  We want to make sure that our
Sleeper doesn't turn into a Rip VanWinkle.  Is there another version of
Sleeper out there that can handle the transition of centuries?