I can only warn against just changing the system clock, which may be
suggested. Passwords and software licenses don't know better than to
expire, and some software is reluctant to believe you when you change
the date back.

>----------
>From:  jim calkins[SMTP:[log in to unmask]]
>Sent:  Tuesday, May 13, 1997 9:47 AM
>To:    [log in to unmask]
>Subject:       [HP3000-L] changing system date for testing
>
>Problem:
>Our users will be doing YR2K testing on a shared 3000 for multiple
>systems.  They will want to be able to test the aplications using
>different 'System dates' according to where they are in their respective
>test plans.  I have a way of setting the 'system date' for different
>users in Transact, but need a way to do it for Cobol, or better for
>everything that a specific user would be doing.  The Transact solution
>takes advantage of the way that Transact calls CALENDAR.  Anyone have a
>way to intercept COBOL system date calls, or better yet a way to set it
>for a particular user or set of users?
>
>
>
>Opinions expressed herein are my own and may not represent those of my
>employer.
>