Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
VM/370 Hercules Optimisation
Gregg,
toggle quoted message
Show quoted text
Sorry Gregg this is not something I have ever done, somewhere along the way, someone else added it, and it became part of the n-packs. That is the idea of the 9-packs, to allow you to use VM. I don't think any system mods are involved so you could just dump the minidisk Dave -----Original Message----- |
On Sat, 1 Feb 2020 at 20:22, Drew Derbyshire <swhobbit@...> wrote:
Full screen CMS was/is a awful hack -- all the native CM/SP line Tony H. |
Drew,
A model 158 had an AP and an MP option.? With AP, you could get at least 6 MB of real main storage on there...? (ask me how I know this ...) ;-)?? (With a 158-MP, I think 8MB was the max.) Also, VM/370 could be configured for an AP environment.? Unlike MVS, with a hierarchy of "locks" I think VM had just a single "global" lock that CP would acquire, as needed, when updating any of the CP control blocks, so that both CPUs did not try to update the same control blocks at the same time. MVS 3.8J also fully supported both the AP and MP configurations of the 158 and 168, back in those days. Folks who want to use more "cores" on modern processors running under Hercules-390 can emulate a 158-AP/MP, 168-AP/MP, or 3031/3033 AP/MP configuration, in the SYSGEN of VM/370 Rel.6 or MVS 3.8J. Cheers, Mark S. Waterbury |
to navigate to use esc to dismiss