z/VM: CP Commands and Utilities Reference - z/VM - IBM
27.12.2012 • Views
Share Embed Flag

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
ePAPER READ
DOWNLOAD ePAPER
vm.ibm.com

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

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

START NOW

Messages<br />

H<strong>CP</strong>002E Invalid oper<strong>and</strong> - oper<strong>and</strong><br />

H<strong>CP</strong>850I UNABLE TO READ DUMP<br />

8. Before you enter the DUMPLOAD comm<strong>and</strong>, be sure that you have sufficient<br />

space at a read/write file mode or enough SFS file space to hold the CMS<br />

dump. Forty-two hundred 4K blocks of SFS file space are needed for each 16<br />

MB of dumped real storage. The following chart indicates how many cylinders<br />

for CKD/ECKD or blocks for FBA devices of free DASD space you will need for<br />

each 16 MB of dumped real storage, based upon the device type <strong>and</strong> the block<br />

size of the formatted minidisk. For dumps of less than 16 MB, the number of<br />

cylinders or blocks is proportional.<br />

BLKSIZE 3380 3390 FB-512<br />

512 34 36 52,700<br />

1024 36 34 48,960<br />

2048 31 27 38,880<br />

4096 28 23 33,120<br />

H<strong>CP</strong>852E FATAL I/O ERROR WRITING DUMP,<br />

FSWRITE|FSERASE|FSTATE|<br />

CMSCALL RC = rc<br />

H<strong>CP</strong>853E NO DUMP FILES EXIST<br />

H<strong>CP</strong>8150I PROCESSING THE DUMP fileid<br />

H<strong>CP</strong>8152E INVALID DEVICE NUMBER<br />

H<strong>CP</strong>8156A DO YOU WANT TO PROCESS THIS<br />

DUMP? (YES/NO)<br />

H<strong>CP</strong>8157A ENTER THE TAPE UNIT ADDRESS<br />

(181-184)<br />

DUMPLOAD<br />

The DASD space requirement shown assumes the dump was produced using a<br />

single invocation of <strong>VM</strong>DUMP. The CMS blocks listed is also the number of free<br />

CMS blocks of each size (512, 1024, etc.). When <strong>VM</strong>DUMP operates in<br />

continuous output mode, <strong>and</strong> page ranges are not dumped in strict ascending<br />

sequence, DUMPLOAD must allocate additional DASD space for one or more<br />

work files, named xxxxxxxx $DUMPLD$, in order to create a merged output file.<br />

Be sure the space allocated for the dump file allows for discontiguous saved<br />

segments, if they were requested with the dump. If the dumped address ranges<br />

include unreferenced (never used) storage, those pages are excluded,<br />

decreasing the storage requirement. Use the number of records in the<br />

<strong>VM</strong>DUMP spool file, which you can obtain using the QUERY RDR comm<strong>and</strong>, to<br />

estimate the amount of storage actually dumped. The size of <strong>VM</strong>DUMP spool<br />

file records is 4 KB.<br />

H<strong>CP</strong>8159A PLEASE MOUNT dumptype TAPE VOL<br />

num ON TAPE DRIVE dev<br />

H<strong>CP</strong>8160I DUMP FROM code (dumptype) nodeid<br />

product release<br />

H<strong>CP</strong>8161E CONFLICT BETWEEN OPERANDS<br />

oper<strong>and</strong> AND oper<strong>and</strong><br />

H<strong>CP</strong>8162 FATAL I/O ERROR READING DUMP,<br />

FSREAD RC = rc<br />

H<strong>CP</strong>8164E DUMP FILE NAME filename IS NOT A<br />

VALID CMS FILE NAME<br />

H<strong>CP</strong>8166E WRONG INPUT TAPE MOUNTED<br />

H<strong>CP</strong>8167E oper<strong>and</strong> OPERAND IS NOT VALID FOR<br />

A VIRTUAL MACHINE DUMP<br />

H<strong>CP</strong>8167I VIRTUAL MACHINE DUMP FROM<br />

product release<br />

Chapter 3. <strong>CP</strong> <strong>Utilities</strong> 1827

logo

products

Resources

Company

Terms of service
Privacy policy
Cookie policy
Cookie settings
Imprint
Change language
Made with love in Switzerland
© 2024 Yumpu.com all rights reserved

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

Saved successfully!

Ooh no, something went wrong!