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

["Jim Wiant" <Jim.Wiant@xxxxxxxxxxxxxxxx>]

Thanks Rob. I haven't messed with TRCJOB instead of relying on looking
at the program stack while the program is running. I'll give that a go.
I've looked at some of those vendors and it appears that's how they
solved the problem - by using CHGSYSLIBL to get their own API versions
in place ahead of the system ones. Done that myself to get around
certain problems, so if I can pin down what routine(s) are in charge
that will be my attempt.

It's clear something changes in V6R1 about the date and time though -
haven't been able to figure out exactly what, but since we're still on
V5R4 that's academic for the moment.

Thanks

Jim 


 
 
If you forget you have to struggle for improvement you go backward. 
Hickson, Geoffrey

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Friday, 11 February 2011 10:20
To: Midrange Systems Technical Discussion
Subject: Re: System Date - can it be 'intercepted' ?

I don't suppose there's some common routine used to extract system date?

For example, if you run a TRCJOB against a program that retrieves the 
system date (while running in debug) can you see what routine was used
to 
extract that?  Anyway to handle that?  Like a copy of the routine?

You might have better luck with the Y2K vendors previously mentioned.


Rob Berendt