27.12.2012 Views

The Virtualization Cookbook for SLES 10 SP2 - z/VM - IBM

The Virtualization Cookbook for SLES 10 SP2 - z/VM - IBM

The Virtualization Cookbook for SLES 10 SP2 - 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.

list. Normal virtual processors in the dispatch list will be Q x (x=1,2,3). Eligible list would be<br />

marked as E x . <strong>The</strong> third column in the example also gives state of virtual processor. This can<br />

be helpful to get a idea of how the virtual processors might be constrained. Virtual processors<br />

that are actually running in the snapshot period are marked with and RNN where NN is the<br />

processor number they are on. An R without a number means the virtual processor is ready to<br />

run but there is not an available processor. (Note: the virtual machine that issues the<br />

INDICATE command will always be one of the running machines). Other states are<br />

documented in the help <strong>for</strong> IND Q EXP. One doesn't have to be concerned about the other<br />

columns unless detailed analysis is required or if <strong>IBM</strong> support requests it. Also, always<br />

remember that is just a snapshot in time so often repeating this command over time can give<br />

a more accurate picture of your z/<strong>VM</strong> system, a single snapshot cannot be regarded as<br />

indicative.<br />

14.1.2 Using other basic commands<br />

Some other useful basic commands are briefly mentioned. All examples are shown from the<br />

MAINT user ID. <strong>The</strong> results will be different <strong>for</strong> users with fewer privileges.<br />

Getting help<br />

To get help on the system use the HELP command. Sometimes it’s hard to find help <strong>for</strong> exactly<br />

the command you’re looking <strong>for</strong>. Some useful help commands are as follow<br />

==> help // <strong>for</strong> basic help<br />

==> help menus // <strong>for</strong> menu of all z/<strong>VM</strong> help menus<br />

==> help cp menu // <strong>for</strong> a menu of all CP commands<br />

==> help cpquery // <strong>for</strong> a menu of all CP QUERY command<br />

==> help cpset // <strong>for</strong> a menu of all CP SET commands<br />

Determining who is logged on<br />

To see who is logged on to the system use the QUERY NAMES command. For example:<br />

==> q n<br />

FTPSERVE - DSC , LINUX04 - DSC , LINUX03 - DSC , LINUX02 - DSC<br />

LINUX01 - DSC , S11S1CLN - DSC , DTCVSW2 - DSC , DTCVSW1 - DSC<br />

<strong>VM</strong>SERVR - DSC , <strong>VM</strong>SERVU - DSC , <strong>VM</strong>SERVS - DSC , TCPIP - DSC<br />

OPERSYMP - DSC , DISKACNT - DSC , EREP - DSC , OPERATOR - DSC<br />

MAINT -L0003<br />

VSM - TCPIP<br />

Determining storage or memory<br />

To see how much central and expanded storage (memory) are installed and allocated to a<br />

system use the QUERY STORAGE and QUERY XSTOR commands. For example:<br />

==> q stor<br />

STORAGE = 16G CONFIGURED = 16G INC = 256M STANDBY = 0 RESERVED = 0<br />

==> q xstor<br />

XSTORE= 2048M online= 2048M<br />

XSTORE= 2048M userid= SYSTEM usage= 0% retained= 0M pending= 0M<br />

XSTORE MDC min=0M, max=0M, usage=0%<br />

XSTORE= 2048M userid= (none) max. attach= 2048M<br />

Determining processors or CPUs<br />

To see how many processors (CPs, IFLs, CPUs) you have allocated at system level, use the<br />

QUERY PROCESSORS command. For example:<br />

==> q proc<br />

PROCESSOR 00 MASTER CP<br />

PROCESSOR 01 ALTERNATE CP<br />

226 <strong>The</strong> <strong>Virtualization</strong> <strong>Cookbook</strong> <strong>for</strong> RHEL 6

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

Saved successfully!

Ooh no, something went wrong!