|
On Wed, Feb 26, 2025 at 8:35?AM M Verpelli via <marco.verpelli=[email protected]> wrote:
Yes.? That's specifically because CMS keeps a copy of the file directory of the S and Y disks in the saved system, so if you don't do this, the CMS users won't see the change.? CMS refers to these directory copies as the "shared S-stat" and "shared Y-stat" accordingly. ?
As Dave has already?mentioned, any file you put on the S or Y disks needs to be mode 2 (e.g., TYPE MODULE S2).? That's because when CMS creates the shared S and Y stats, it only puts the mode-2 files in them.
You don't need to do VMSETUP, and in fact the next command shuts CMS down and undoes it :-)\
CP should respond: STORAGE = 16384K CP ENTERED; DISABLED WAIT PSW '00020000 00000000' ?
At which point CMS puts out the "greeting message": VM Community Edition V1 R1.2
You need to type that exactly as seen - no #CP, no other words or punctuation (but upper/lower case doesn't matter), and no pressing ENTER beforehand.? CMS checks the line entered in response to the greeting message for several special cases, including the SAVESYS response. ?Note that if you accidentally issue the CP SAVESYS command instead of responding SAVESYS to the greeting, it's anybody's guess what will happen.? When you do it correctly, CMS prepares itself for saving and then issues the actual CP SAVESYS command itself, via Diagnose 8.
That's not necessary.? After your SAVESYS, any user (including MAINT) that does IPL CMS will get the newly-saved system.
My best guess is that CP got the SAVESYS, not CMS, and that it was processed at an inopportune moment.? The proper sequence looks like this (just captured from my on VM/CE 1.1.2 system):
Note that "SYSTEM SAVED" message - CMS issues that when it saves the system.? If you don't get that, it didn't happen correctly. Ross |
