Re: Re: Wait State 00050064

On Sat, 2019-09-21 at 08:39 -0700, ''Fish' (David B. Trout)'
[email protected] [H390-MVS] wrote:
> Dave Wade wrote:
> 
> [...]
> > was the LPAR number hidden from the OS....
> > .... do S/370 OS's know about LPARs and how should
> > Hercules behave when one is defined.
> > 
> > Perhaps Hercules is behaving badly...
> 
> I would tend to agree.
> 
> I personally questioned the behavior (by Mark Gaubtaz (dasdman) back
> in Sept. 2013) which is what lead to my eventual introduction of the
> "Limited automatic LPARNUM updating when setting certain architecture
> modes" change in Hyperion 4.1 (https://sdl-hercules-390.github.io/htm
> l/hercrnot.html#4.1), but he insisted such handling was correct, and
> I felt he was in a better position to know than me (having worked at
> Amdahl for many years and having access to documents unavailable to
> the general public).
> 
> <shrug>
> 

The issue is not Hercules.  It is performing correctly.  The issue here
is the operating system and what it supports, in this case, MVS 3.8J.

The mismatch is between the "hardware" options selected for Hercules
vs. the software option actually being run on that "hardware."

Typically the Hercules configuration is about the emulated hardware.
 It assumes the end user knows what he or she is doing when it comes to
the software.  Without factoring in the OS planned for the given
system, it is difficult for the Hercules configuration to recognize
inconsistencies.  Note, I said difficult, but maybe not impossible.

I certainly encourage the GUI to factor that into what it generates.

Harold Grovesteen