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
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
► Use the SERVICE ALL command specifying the envelope files you downloaded. Many,<br />
many screens of output will scroll by and will automatically be cleared. Important<br />
messages will be saved to the 500 disk. This process may take many minutes. Following is<br />
an example:<br />
90 <strong>The</strong> <strong>Virtualization</strong> <strong>Cookbook</strong> <strong>for</strong> RHEL 6<br />
==> service all d8873674<br />
...<br />
<strong>VM</strong>FSUT2760I <strong>VM</strong>FSUFTB processing completed successfully<br />
<strong>VM</strong>FSRV2760I SERVICE processing completed successfully<br />
==> service all s8873674<br />
...<br />
<strong>VM</strong>FSUT2760I <strong>VM</strong>FSUFTB processing completed successfully<br />
<strong>VM</strong>FSRV2760I SERVICE processing completed successfully<br />
If you see no number in parenthesis after the Ready; prompt, then the return code is 0.<br />
Any non-zero return code will be in parenthesis. A return code of 0 is ideal. In general a<br />
return code of 4 is acceptable - it means that only warnings were issued. A return code of<br />
8 or greater generally means that errors were encountered.<br />
► <strong>The</strong> output files are of the <strong>for</strong>m $<strong>VM</strong>F* $MSGLOG. You may wish to inspect these files.<br />
==> filel $vmf* $msglog<br />
$<strong>VM</strong>FSRV $MSGLOG A1 V 80 728 14 12/15/09 13:43:34<br />
$<strong>VM</strong>FBLD $MSGLOG A1 V 80 787 11 12/15/09 13:41:47<br />
$<strong>VM</strong>FAPP $MSGLOG A1 V 80 252 4 12/15/09 13:41:37<br />
$<strong>VM</strong>FREC $MSGLOG A1 V 80 56 1 12/15/09 13:41:36<br />
$<strong>VM</strong>FMRD $MSGLOG A1 V 80 231 4 12/15/09 13:41:35<br />
$<strong>VM</strong>FP2P $MSGLOG A1 V 80 805 15 11/19/09 13:52:09<br />
$<strong>VM</strong>FINS $MSGLOG A1 V 80 163 3 11/19/09 13:47:25<br />
► Invoke the <strong>VM</strong>FVIEW SERVICE command to review the results of the previous SERVICE<br />
command. Press the F3 key to quit. Following is an example:<br />
==> vmfview service<br />
===> <strong>VM</strong>FVIEW - Message Log Browse of $<strong>VM</strong>FSRV $MSGLOG A1 F3<br />
Ideally there will be no output. If there are errors they must be addressed. If there are<br />
warnings, they may be acceptable but should be investigated.<br />
5.4.5 Putting the service into production<br />
To put the service into production, per<strong>for</strong>m the following steps:<br />
► Use the PUT2PROD command to put the service into production.<br />
==> put2prod<br />
...<br />
<strong>VM</strong>FP2P2760I PUT2PROD processing completed successfully<br />
Again, watch <strong>for</strong> a return code of 0.<br />
► Your PTF should now be put into production. You may or may not have to reIPL the<br />
system, depending on the nature of the PTF applied. If you are in a position to re-IPL your<br />
system it may be safest to reIPL using the SHUTDOWN REIPL command in order to<br />
completely test the changes:
Change language