RE: Re: Wait State 00050064

Robert Schreiber wrote:

[...]
> Perhaps it might have been nice for Hercules to flag
> the LPARNUM 01 since it's inconsistent with ARCHLVL
> S/370?

https://sdl-hercules-390.github.io/html/hercconf.html#ARCHLVL
https://sdl-hercules-390.github.io/html/hercconf.html#LPARNUM


https://sdl-hercules-390.github.io/html/hercrnot.html#4.1


   "Limited automatic LPARNUM updating when setting
    certain architecture modes"

   [...]

   "For the unusual case where users actually do want to run a
    System/370 Operating System within an LPAR, you will need
    to manually re-set your LPARNUM and CPUIDFMT values back to
    their numeric values after setting ARCHLVL S/370. That is
    to say, one should always follow their ARCHLVL S/370 statement
    with a LPARNUM n|nn statement (and CPUIDFMT statement too
    if needed) if LPAR mode for S/370 is truly desired."


Your downfall sounds like it was likely caused by your setting LPARNUM after having set ARCHLVL S/370.  Am I right?  Since 'A' comes before 'L' this is not entirely unexpected.

However, I would have thought the messages that are automatically issued when ARCHLVL is set to S/370 should have been enough of a clue:

   HHC01603I archlvl s/370
   HHC00811I Processor CP00: architecture mode S/370
   HHC02204I ARCHLVL        set to S/370
   HHC02204I LPARNUM        set to BASIC


'Tis wise to closely review one's Hercules logfile before submitting problem reports. ;-)

-- 
"Fish" (David B. Trout)
Software Development Laboratories
http://www.softdevlabs.com
mail: [email protected]