| Newsgroups |
gmane.comp.emulators.hercules390.general |
| Message-ID |
<[email protected]> |
Paul
Everything you are describing below isn't regular MVS usage. Shutting the system down before powering off the mainframe was always common sense and is so even with today's latest z/VM and z/OS systems.
Subsecond termination? Well, fine. But you are on your own with this. I'll never "support" such a thing, it is simply not supportable, because MVS isn't designed for such usage. Power on - IPL - run one job - pull the system's power plug, and so on. Incredibly unMVSish.
From its very beginning, MVS was designed to run forever, hardware stability and maintenance requirements permitting -- and today (now being called z/OS, operating on the most reliable hardware in existance on this planet) this is one of its major competive advantages. I will never support any other concept.
Nothing more to add from my side.
Juergen
P.S.: You might want to read the TK4- documentation, particularly chapter "Parameter Controlled Startup and Shutdown Automation" in tk4-\doc\README_MVS_TK4-_v1.00_update_06.pdf. This explains among other stuff how to use a "minimal configuration". Trying this minimal configuration might be worthwhile -- it might make your weird MVS usecase work, but only, if you use it exactly as outlined. No guarantee, though!
---In [email protected], <kerravon86@...> wrote :
---In [email protected] mailto:[email protected], <winkelmann@...> wrote :
>> So I run startmvs2 and wait for the scripts to
>> complete, and then type "quit". The first time
>> I did this with the untouched TK4- it actually
>> worked, ie all the verbiage was displayed on
>> the screen and the log, like this:
> As I said: If used as designed, there is no race
> condition. However, I don't consider entering
> quit after IPL completion being "use as designed".
I think Hercules should be deterministic and
close its files, including the log file, cleanly
on response to "quit", as it *randomly* does
correctly already.
> How about shutting down MVS first, using the
> TK4- automated shutdown process?
I tried "/s shutdown" 3 times, and all 3 times it
produced a clean log file.
> This thing is there for a reason...
And there's a reason why I use "quit" instead
of "/s shutdown". I want sub-second termination,
not a one-minute termination.
It has been working fine on a modified tk3upd
for many years. I suspect the extra devices
added to TK4 are causing the issue. What I
first noticed was data that I had populated
was not sticking, until I added a pause
before the quit. It's not a clean log file I want
so much as the DASD to be flushed before
program exit.
BTW, there are delays on IPLing TK4-, like
this:
05:03:43 HHC01603I hao cmd script scripts/SCR00010A
05:03:43 HHC00077I The command was placed at index 3
05:03:47 HHC00008I /d t
05:03:47 HHC02264I Script 1: file scripts/ipl.rc processing ended
05:03:47 IEE136I TIME=20.03.47 DATE=19.172
05:04:10 +BSPPILOT - Running script STARTSTD
05:04:10 +BSPRS22I - Dataset processed: SYS1.PARMLIB
You can see a 23 second delay there.
I changed IEAIPS00 in my modified tk3upd to avoid
a similar problem, as outlined here:
https://groups.yahoo.com/neo/groups/hercules-os380/conversations/messages/11700 https://groups.yahoo.com/neo/groups/hercules-os380/conversations/messages/11700
BFN. Paul.