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.

ENTER key as input to the virtual machine at the initial <strong>VM</strong> READ. Your<br />

PROFILE EXEC is automatically executed if it exists on your file mode A.<br />

BATCH<br />

indicates that the CMS IPL is being performed in a batch instead of an<br />

interactive virtual machine.<br />

Use of this parameter does not affect execution of the SYSPROF EXEC.<br />

Execution of the SYSPROF EXEC is suppressed only if the NOSPROF<br />

parameter was specified.<br />

At the beginning of each job, the batch facility work disk is accessed <strong>and</strong><br />

immediately erased, preventing the current user job from accessing files that<br />

might remain from the previous job. Because of this, execution of the PROFILE<br />

EXEC is disabled for the CMS Batch Facility machine. However, if the<br />

BATPROF EXEC exists on an accessed system disk, it is invoked instead of<br />

the PROFILE EXEC.<br />

FILEPOOL filepoolid<br />

specifies the default file pool that is established as the user’s file mode A. If<br />

FILEPOOL is not specified, 191 is established as the file mode A.<br />

The following parameters are ignored by the SYSPROF EXEC, but processed by<br />

CMS initialization.<br />

NOSPROF<br />

indicates that the SYSPROF EXEC is bypassed. You must specify NOSPROF if<br />

you intend to enter the CMSBATCH comm<strong>and</strong> when the initial <strong>VM</strong> READ is<br />

issued. When the SYSPROF EXEC does not exist, you do not have to specify<br />

NOSPROF to enter the CMSBATCH comm<strong>and</strong>.<br />

INSTSEG YES<br />

links the default CMS installation saved segment for this CMS session. The<br />

CMS installation saved segment is an optional shared segment that contains<br />

EXECS <strong>and</strong> editor macros that your installation provides.<br />

INSTSEG NO<br />

indicates that you do not want to use the CMS installation saved segment<br />

during this CMS session.<br />

INSTSEG name<br />

links the named CMS installation saved segment for this CMS session. The<br />

segment may be a physical or a logical saved segment.<br />

SAVESYS sysname<br />

is used in the process of creating named systems. The SAVESYS parameter is<br />

available only to Class E users. It saves a virtual machine storage space with<br />

registers <strong>and</strong> PSW as they currently exist. The oper<strong>and</strong> sysname must be a<br />

predefined name representing a definition of installation requirements of the<br />

named system. The definition indicates the number of pages to be saved, the<br />

DASD volume on which the system is to be saved, <strong>and</strong> the shared segments, if<br />

any.<br />

After the system is saved, initialization continues, all CMS parameters entered<br />

on the IPL comm<strong>and</strong> are ignored, <strong>and</strong> SYSPROF EXEC is processed. The<br />

parameters entered on the original IPL comm<strong>and</strong> are not passed to SYSPROF<br />

EXEC.<br />

IPL<br />

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

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

Saved successfully!

Ooh no, something went wrong!