开云体育

Not necessarily VM/370, it could be some other virtual machine. For example the MTS virtual machine also sets the first byte of the CPU ID to FF. If MTS is going to close its printers when a job is

Tony Harminc wrote: No. I was talking about VM print spool handshaking. The guest (in this case MTS), when run under VM, being able to close its VM printer to cause its printouts to appear as

[email protected]> wrote: No - the VM we have is of roughly the same vintage as the OS/VS and DOS OSs. Are you sure you're not think

René Ferland wrote: Really? Wow. Maybe the ones we have were before VM's time? REALLY?! Again, WOW. I specifically recall the option being there when I was working with DOS/VS(E) back in the day. I

Except for MUSIC/SP, none of the vintage systems we have implement handshaking. If I am not mistaken, George Shedlock added handshaking to DOS/VS R34, and Bob Polmanter did so for MVS 3.8J. To my

Adding in: QUERY CPUID = aabbbbbbccccdddd Where: aabbbbbbccccdddd is the 16-digit processor identification associated with the virtual machine. aa is the version code; these

If I remember correctly you can use the STIDP store processor ID instruction and the info you get back (I think it's high values at the end X'FF' means it's running under VM.

Mike Alexander wrote: Most operating systems are largely, but not completely, unaware that they are running under a virtual machine such as VM, and rightly so. BUT... in a few specific places they,

No. It has no special support for VM. It treats VM like a funny sort of real machine. Mike

Will it implement handshaking? That is, will MTS automatically close the spooled printer files so it will be printed by the real printer of VM? Cheers, Rene FERLAND, Montreal

This should work fine. MTS sometimes ran in production under VM back in the day although I don't think it ever did so at UM. It will be aware that it is running under VM and may change its behavior

I have a Multiprise 3000 system and, now, lots of spare disk space. It struck me a few moments ago that I can now run MTS on it. The system currently runs VM/ESA 2.4, z/OS 1.5, VSE/ESA 2.4, and MVS/XA

Fish's description is correct, but unfortunately it's only half the story. It wxplains how to configure HIM support in Hercules, but you also have to configure it in MTS. The D6.0 MTS device

John Palmer wrote: [...] Hi John! While Mike would certainly be the person to provide a definitive answer to that, I believe I might be able to help you, having reviewed his code before having

Looks like your pull request has been committed to the development branch of Hercules. It looks like the d6.0 distribution has support for TCP/IP. The Telnet manager is running (*TCM file job). Do

Thanks for your effort on this,? Mike.? I'm sure just about everything else takes precedence over this. John

I just submitted a pull request for the HIM code. I'm sure there will be issues with it. I'll fix them as soon as I can, but note that I will be out of town with limited network access from this

Just wondering about the status of the code merge for Hercules. Are there still unresolved issues with getting the HIM code to work with modern Hercules? If the current code with HIM support is

Does anyone know if there was an effort to create a Java JVM for MTS? If so, does anyone know if the effort was a success and is its available somewhere? ------- Forwarded Message ------- From: Lucien

No release date has been set yet. I'll let you know when we get closer. Mike