开云体育

Now that VM has the correct day and time, my guest DOSVS machine has the correct time but is off one day in the future (plus 24 hours).? I tried the 'SET DATE=' command at IPL time and receive an INVALID RESPONSE message but the SET command with no parameters works fine.? For example, right now the date shows 10/19/22 when it is actually 10/18/22.? Where or how do I correct this?

I stopped the printer task via POWER via 'P 00E'.? I then restart it with 'S LST,00E,A,,VM' to indicate that output should be spooled to VM, but I get no output until I shutdown the DOSVS guest and logoff.? Shouldn't the above create a printer file in VM?? I am using HercPRT v1.8.0.5692 which should generate a PDF file.? Also, the printer device is defined as:
000E? ? 1403? ? 127.0.0.1:3213 sockdev cctape=(1=1,7=2,13=3,19=4,25=5,31=6,37=7,43=8,63=9,49=10,55=11,61=12)

BTW, VM files print just fine producing beautiful PDF files.

I keep getting the message

?

? ? ? ? ? ?SNS=0? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ??
whenever I start POWER.? I respond with 'CANCEL' and all is well with POWER startup.? Why am I getting this message?? Finally, how do I edit the POWERV job executed in F1 (when 'ASSGN SYSIN,SYSRES' is entered)?? I want to see if/where/how the device 02C is being specified and also to start the LST task by spooling the output to VM.

Hello Jim,

Below some answers.

>> [...] my guest DOSVS machine has the correct time but is off one day in the future (plus 24 hours).

?

This issue was raised in the past (in 2010). The best explanation comes from Bill Carlborg:

?

"DOS/VS is not "century aware" and the problem is in the date routines.? They calculate the number of years since 1900 since the TOD clock starts then.? It's fine until the year 2000 when that makes 100 years in the TOD clock.? If the date is in the form MMDDYY that one in the 100 will be in the day position.? DOS/VS adds a month field (MM0000) to a day? field (00DD00) to the year field (0000YY).? Except the year field is now more than 2 digits with a one in the position that belongs to the day.? So when it adds the three fields together to make MMDDYY the day is increased by one."

?

Bill proposed a "solution" if you don't want to start patching/updating system routines:

?

"What I did on my system was include a YROFFSET -100 in my Hercules config file.? This moves the TOD clock back a hundred years.? So the TOD clock might think it is 1922 but DOS/VS never uses the century part anyway so it doesn't even know or care.? And without the century it never could do any day of the week calculations so that is not an issue.? This seemed to be the easiest solution."

?

I tried it on VM/370 CE and it seems to work.

?

?

?

?

?

Because the DOS/VS system you use (see below) probably has not handshaking implemented.

?

?

?

?

?

Because you are possibly using the DOS/VS system customized by Michel Beaulieu, instead of the original 5-pack of George Shedlock, to which the DOSVS directory entry of VM/370 CE applies. Here's a link to the "right" DOS/VS system:

?

http://dosvs.31bits.net/DOSVS_5Pack_V1.0-full.zip

?

If you use the DASDs in the ZIP above, you should not need to change the POWER job, and handshaking is implemented, so printing will work fine. It is certainly the case for me.

?

Cheers,

?

Rene FERLAND, Montreal

?