RE: System Date - can it be 'intercepted' ?

["Harman, Roger" <Roger.Harman@xxxxxxxxxx>]

I believe HelpSystems is marketing their AnyDate product again.  We used it extensively for Y2K and it disappeared shortly thereafter.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Thursday, February 10, 2011 12:24 PM
To: Midrange Systems Technical Discussion
Subject: Re: System Date - can it be 'intercepted' ?

It can be done...I recall seeing lots of products in the late 1990's
that would do this...a google search turned up
http://www.inprointernational.com/tt4slk.htm

But I don't know how to do it myself....

HTH,
Charles

On Thu, Feb 10, 2011 at 2:59 PM, Jim Wiant <Jim.Wiant@xxxxxxxxxxxxxxxx> wrote:
> Due to architectural decisions I can't control, developers continue to
> use %date as the usual way to get the date into a program. But from a
> testing standpoint this makes things very difficult. Many things are
> date-dependant but need to be tested before that date occurs. And I am
> trying to emphasize automated testing so the advice recently given to me
> of 'run it in debug and change the date' isn't good enough. That's bad
> testing form anyway...
>
> I did some digging and I can't find a way to override or control the
> system date other than changing the date, which again is not my first
> choice because it will affect all testing not just the one I want and
> the impact on the journals scare me anyway.
>
> I need to be able to programmatically control the system date a program
> gets whether it be CL, COBOL or RPG without actually changing the system
> date itself.
>
> Thanks
>
> James P. Wiant
> Test System Administrator
> Foodstuffs, Auckland, Ltd.
> 60 Roma Road
> Mt Roskill
> Auckland, New Zealand 1041
> 09-621-0774
> jim.wiant@xxxxxxxxxxxxxxxx
>
> Quicker by taking more time.
> Proverb
>
>
> This message has been sent from Foodstuffs (Auckland) Limited ("Foodstuffs").
>
> The information contained in this message and or attachments
> is intended only for the person or entity to which it is
> addressed and may contain confidential and/or privileged
> material. Any review, retransmission, dissemination or other
> use of, or taking of any action in reliance upon, this
> information by persons or entities other than the intended
> recipient is prohibited. If you received this in error,
> please contact the sender and delete the material from any
> system and destroy any copies.
>
> The views and opinions expressed in this message may be those
> of the individual and not necessarily those of Foodstuffs,
> and are not given or endorsed by it.
>
> Please note that this communication does not designate an
> information system for the purposes of the Electronic
> Transactions Act 2002.
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.