开云体育

2305 was nice because of no seek time. In an Hercules emulated environment, probably doesn't make a difference. I was on the periphery of a 360/75 MVT -> 4341 MVT under VM transition (I got to do some

Share file, didn’t want to undo existing stuff Dave Sent: 29 January 2020 22:33 To: [email protected] Subject: Re: [h390-vm] CP Query

Indeed, and I was just wondering how to report CMSLIB version, and of course GCC brexx etc all have versions. As for the distribution ... why not just have a version in a file on a shared drive and

General Hercules discussions should be on the hercules-390 group… <https://hercules-390.groups.io/g/group/topics> https://hercules-390.groups.io/g/group/topics the history of how the forks occurred

Spinhawk is also the version which Linux

Note the while VM/370 supports 16M of real memory, only the largest machines had that much installed.?? For example, the S/370 158 only supported 4M, and the uniprocessor 168 only supported 8M.??

On Wed, 29 Jan 2020 at 18:30, Peter Coghlan <groups@...> wrote: > > > > We have: > > > > - Version 3.13 - http://www.hercules-390.eu/ > > - SDL Version 4.2.1 -

I thought there was a bias towards 2305 devices for paging, but too much time hanging out with the documents for a certain 4361 and it's VM/SP flavor, my brain is probably fogged. -ahd-

Since the SixPakc include CP changes, it's definitively of? one the right places. Both CP and CMS should be report what their build level and their build date; so should the other components. Why

Peter, Thanks I don't especially want to continue, but I don't want to write more code. I saw that code and wondered what to tweak. Dave. p.s. As for "is this the right place" well not sure, but I

My opinion is that of the choices given, 3.13 is the only one that has sufficient stability for me to attempt to develop code for. I also find it to be the only game in town if building for any

Adrian, I would compare the performance of 3.13 and 4.2.1. the released 3.13 code is getting a little long in the tooth. I think Roger may had added some fixes to the source (see the GitHub

And further to this ubuntu provides Hercules 3.13 - so this is the easy option (however not a biggy - I can always run CMAKE and wait ...)

We have: - Version 3.13 - http://www.hercules-390.eu/ - SDL Version?4.2.1 - https://github.com/sdl-hercules-390/hyperion - Version 4.0.0 - https://github.com/hercules-390/hyperion Having done no

Folks CPWATCH reports paging rate. Dave Sent: 29 January 2020 12:44 To: [email protected] Subject: Re: [h390-vm] VM/370 Hercules Optimisation Adrian, In my experience, I doubt you are doing all that

Peter, I suspect that EPCS:VM produces a much bigger performance gain than AP or MP. ECPS:VM is the start of what eventually became SIE and microcode virtualization. So VM (aka CP) is a software

Adrian, In my experience, I doubt you are doing all that much paging.? First off, the VM/370 CP IND command doesn't show paging stats like it did in later releases, so it is difficult to know how

Honestly, the best improvement is going to come from ECPS:VM. https://github.com/sdl-hercules-390/hyperion/blob/master/readme/README.ECPSVM.md And i would highly recommend to get on fish's Hyperion

Adrian, I'm not going to say whether you should run a Hyperion release or not; that is up to you.? There are pros and cons of Hercules 3.13 vs. Hyperion. As for ECPS, it is not a scheduling

Noted - I will follow your advice and not bother yet.