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.

Responses<br />

user PROFILE EXEC is invoked after the SYSPROF EXEC. You can bypass the<br />

SYSPROF EXEC by specifying the NOSPROF parameter on the IPL comm<strong>and</strong>.<br />

5. If you have defined disks with virtual device numbers 190 <strong>and</strong> 19E in the<br />

system directory, or if they are defined before you IPL CMS, these disks are<br />

accessed as the S- <strong>and</strong> Y-disks, respectively. After you IPL CMS, you must<br />

enter explicit ACCESS comm<strong>and</strong>s to access other disks. Ordinarily, you have<br />

access only to files with a file mode number of 2 on the system disk.<br />

If you have defined disk address 191 <strong>and</strong> the FILEPOOL parameter is omitted,<br />

the 191 disk is accessed as file mode A. However, if the FILEPOOL parameter<br />

is specified, your top directory in the identified file pool is accessed as file mode<br />

A, even if you also have a 191 minidisk defined. If the access of the top<br />

directory fails (perhaps because the file pool is unavailable), the 191 minidisk is<br />

accessed. If there is no 191 minidisk, nothing is accessed as file mode A.<br />

When ACCESS is the first comm<strong>and</strong> issued after an IPL of the CMS system, file<br />

mode A is not automatically defined. Another ACCESS comm<strong>and</strong> must be<br />

issued to define file mode A.<br />

For more information on the CMS ACCESS comm<strong>and</strong>, see z/<strong>VM</strong>: CMS<br />

<strong>Comm<strong>and</strong>s</strong> <strong>and</strong> <strong>Utilities</strong> <strong>Reference</strong>.<br />

6. If you have a disk defined as virtual device number 192, the following special<br />

rules apply when CMS is IPLed:<br />

v If 192 is an unformatted temporary minidisk or virtual disk in storage, CMS<br />

formats it <strong>and</strong> accesses it as file mode D.<br />

v If 192 is a <strong>CP</strong>-formatted temporary minidisk or virtual disk in storage, CMS<br />

reformats it for CMS use <strong>and</strong> accesses it as file mode D.<br />

v If 192 is a CMS-formatted temporary minidisk, virtual disk in storage, or<br />

permanent minidisk that is accessed as a file mode other than D, CMS<br />

reaccesses it as file mode D.<br />

v If 192 is an unformatted or <strong>CP</strong>-formatted permanent minidisk, CMS does not<br />

automatically format, reformat, access, or reaccess it.<br />

When CMS accesses a 192 minidisk as file mode D, any minidisk or SFS<br />

directory already accessed as D is released.<br />

Usually, after a successful IPL, any responses you receive are those from the<br />

operating system that was loaded <strong>and</strong> initialized.<br />

Response 1:<br />

Trace active at IPL<br />

is issued when tracing is active.<br />

Response 2:<br />

Trace active at IPL<br />

This may cause some architectured facilities to<br />

not be available at your virtual machine. Turn Trace<br />

off <strong>and</strong> re-IPL to recover use of these facilities.<br />

is issued when a trace set is found during the IPL of a preferred guest. This will<br />

result in the disablement of assists which interpret the SIE instruction. These assists<br />

can only be used when TRACE is not in effect for a guest.<br />

Response 3:<br />

IPL stop at xxxxxxxx<br />

IPL<br />

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

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

Saved successfully!

Ooh no, something went wrong!