27.12.2012 Views

z/VM: CP Commands and Utilities Reference - z/VM - IBM

z/VM: CP Commands and Utilities Reference - z/VM - IBM

z/VM: CP Commands and Utilities Reference - z/VM - IBM

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

SAVESYS<br />

►►<br />

SAVESYS<br />

Authorization<br />

Purpose<br />

Oper<strong>and</strong>s<br />

name<br />

Usage Notes<br />

Privilege Class: E<br />

SAVESYS<br />

Use SAVESYS to save a named saved system (NSS) into a previously defined<br />

system data file (SDF).<br />

name<br />

is the name of the NSS to be saved. This is the file name of a class S<br />

(skeleton) system data file previously defined with the DEFSYS comm<strong>and</strong>.<br />

1. <strong>CP</strong> can process only one DEFSYS or SAVESYS comm<strong>and</strong> for a particular<br />

name at any given time. If <strong>CP</strong> is already processing a DEFSYS or SAVESYS<br />

comm<strong>and</strong>, a subsequent DEFSYS or SAVESYS request for the same name is<br />

delayed.<br />

2. You can interrupt <strong>and</strong> end a SAVESYS operation before it completes by using<br />

the PURGE NSS comm<strong>and</strong>. This will not leave a partially-saved system data<br />

file on the system. The skeleton system data file will be purged <strong>and</strong> must be<br />

redefined before the named saved system can be resaved.<br />

3. After the execution of this comm<strong>and</strong>, the system data file is designated class A<br />

or class R. Class A indicates that it is in the unrestricted available state, <strong>and</strong><br />

may be accessed by any user. Class R indicates that the NSS is restricted <strong>and</strong><br />

the users must have a NAMESAVE statement for the NSS in their directory<br />

entries in order to load it.<br />

4. Only one available NSS (Class A or R) with a particular name may exist at a<br />

given time. If any Class A or R NSS already exists with the same name as the<br />

one being saved, <strong>and</strong> there are no virtual machine users associated with the<br />

NSS, then the old copy of the NSS is purged <strong>and</strong> the new one is made<br />

available.<br />

If there are users associated with the old copy <strong>and</strong> neither the old copy nor the<br />

new copy of the NSS is a <strong>CP</strong> system service NSS (that is, no page ranges<br />

were defined with the SC page descriptor code), the old copy is marked as<br />

pending purge, <strong>and</strong> the new copy is saved. Any users associated with the old<br />

copy continue to reference the old (now pending purge) NSS. Subsequent<br />

users are associated with the new copy.<br />

If there are users associated with the old copy <strong>and</strong> either the old copy or the<br />

new copy of the NSS is a <strong>CP</strong> system service NSS (that is, one or more page<br />

ranges were defined with the SC page descriptor code), the SAVESYS<br />

comm<strong>and</strong> is not accepted.<br />

5. If there is a <strong>CP</strong> NSS with the specified name that is class P pending purge<br />

(the PURGE NSS comm<strong>and</strong> was used to purge it while there were users<br />

associated with it), the same rules apply as described in 4:<br />

►◄<br />

Chapter 2. <strong>CP</strong> <strong>Comm<strong>and</strong>s</strong> 1181

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!