Eh...the sysprog in me is cringing about not shutting JES2 down cleanly. You'll probably be able to get away with it, but the one time you shut things down in the middle of a checkpoint write and clobber it to the point of needing a cold start is the one time you want to keep the contents of the spool...
On Mon, Nov 27, 2023 at 10:37?AM Bob Polmanter <
wably@...> wrote:
Daniel,
I was a system programmer back then and I ran VM/370 with a VS1 guest on a S/370-148.? Later we had a 4341 and VM/SP and VS1.? Later still we had a 4381 running VM/SP and MVS as a V=R guest.? Then after a while on the same 4381 we ran VM/HPO with MVS/SP as a V=R guest in PMA mode (Preferred Machine Assist, that Tony H mentioned earlier).? We had a 16M real machine and 60-80 VM/CMS users depending on the time of day.? MVS had 8M of the real memory in the V=R area.? We ran this way in production until 1994.? Performance was always a challenge (mostly the CP paging rate) but "we got 'er done".? So I did this for years and I still remember a lot about it.
Regarding the JES2 shutdown, I have the same issue and Jay is right about the reader being the cause.? I simply don't shut down JES2 and avoid the whole issue.? If I am shutting down the machine, I force MVS with the CP command before I shutdown VM/370.? This allows CP to complete any MVS i/o that might have been in progress.? Wait a second or two then SHUTDOWN.? I've never had any problems ever, by not stopping JES2 completely.
Regards,
Bob
