Jeff,
It looks most odd, as the time is also corrupted.
What happens if you change the order of the reply thus:-
R 0,'DATE=55.066,CLOCK=01.01.01,AUTO=N'
(that's the format in my notes for MVT).
Chris
--
<cjar1950@...>
----------------------------------------------------------------------------------------------------------------------------------
On Wed, 08 Mar 2023 15:09:31 -0800
"Jeff Snyder" <jsnyder1369@...> wrote:
Hi Uwe.? Using 28 years set the date back to 1995, which should have fit within MVT's sanity check for dates.? When I did that, MVT thought it was 1955.? I'm afraid if I go back any further, I might drop out of the early end of MVT's date range.
Using "YROFFSET -28":
VM says it's 1995
q t
14:47:30 TIME IS 14:47:30 PST TUESDAY 03/07/95
14:47:30 CONNECT= 00:04:23 VIRTCPU= 000:00.25 TOTCPU= 000:02.42
However the MVT guest thinks it's 1955!
| 00 IEE116A TOD CLOCK INVALID- REPLY WITH SET PARAMETERS
| R 00,'clock=01.01.01,date=95.057,auto=n'
| IEE600I REPLY TO 00 IS; 'clock=01.01.01,date=95.057,auto=n'
IEE118I SET PARAMETER(S) ACCEPTED
- D T
*IEE136I??? TIME=01.42.24?? DATE=55.066
* By the way, using 28 years works fine when running MVT directly under Hercules.? It's only when I try it under VM that it has issues.
