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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

SPXTAPE<br />

The activities of each SPXTAPE comm<strong>and</strong> are recorded in at least two spool files:<br />

a comm<strong>and</strong> summary log <strong>and</strong> one or more volume logs. These logs are created by<br />

the SPXTAPE DUMP, LOAD, <strong>and</strong> SCAN comm<strong>and</strong>s.<br />

Both logs have the same routing <strong>and</strong> disposition as the virtual console of the user<br />

who enters the SPXTAPE comm<strong>and</strong> (or causes the SPXTAPE operation to begin).<br />

If you enter the comm<strong>and</strong> spool cons * before you enter the SPXTAPE comm<strong>and</strong>,<br />

all logs are sent to your virtual reader. If you want to change the spooling of your<br />

console, you should do it before you enter the SPXTAPE comm<strong>and</strong>, or the logs<br />

may be sent to different destinations.<br />

Comm<strong>and</strong> Summary Log: The comm<strong>and</strong> summary log records the progress <strong>and</strong><br />

status of an SPXTAPE DUMP, LOAD, or SCAN operation. Most comm<strong>and</strong><br />

responses, as well as any error messages, are recorded in this log. A new<br />

comm<strong>and</strong> summary log is created for each SPXTAPE DUMP, LOAD, or SCAN<br />

comm<strong>and</strong>, unless the comm<strong>and</strong> is appended to a previous SPXTAPE comm<strong>and</strong>.<br />

Each comm<strong>and</strong> summary log has a unique name. The file name <strong>and</strong> file type have<br />

the following format:<br />

aabbcccc hhmmss<br />

aa is the month the SPXTAPE comm<strong>and</strong> is issued.<br />

bb is the day the SPXTAPE comm<strong>and</strong> is issued.<br />

cccc<br />

is the SPXTAPE operation: DUMP, LOAD, or SCAN.<br />

hh is the hour the SPXTAPE comm<strong>and</strong> is issued.<br />

mm<br />

is the minute the SPXTAPE comm<strong>and</strong> is issued.<br />

ss is the second the SPXTAPE comm<strong>and</strong> is issued.<br />

The comm<strong>and</strong> summary log contains a header (response 1) for the comm<strong>and</strong> that<br />

creates the log. If the comm<strong>and</strong> that creates the log is issued with the APPEND<br />

oper<strong>and</strong>, a header is also written in the log for each appended comm<strong>and</strong>.<br />

Volume Log:<br />

1464 z/<strong>VM</strong>: <strong>CP</strong> <strong>Comm<strong>and</strong>s</strong> <strong>and</strong> <strong>Utilities</strong> <strong>Reference</strong><br />

The volume log records information about the files processed by an SPXTAPE<br />

DUMP, LOAD, or SCAN comm<strong>and</strong> that are associated with a particular tape<br />

volume. There is one volume log for each tape volume for each SPXTAPE<br />

comm<strong>and</strong>. For example, if you use the SPXTAPE DUMP comm<strong>and</strong> with the LEAVE<br />

oper<strong>and</strong> 10 times to save files on a single tape volume, 10 volume logs are<br />

created. If you use a single SPXTAPE DUMP comm<strong>and</strong> to dump files to 10 different<br />

tape volumes (<strong>and</strong> all 10 are actually used), 10 volume logs are created.<br />

The volume log is a record of what is dumped to, loaded from, or scanned on a<br />

tape volume. For an SPXTAPE LOAD operation, the volume log may record more<br />

than what is actually loaded from the tape. A failure or operator action that occurs<br />

after a file has been read from the tape <strong>and</strong> logged (such as spool space being<br />

exhausted, or the SPXTAPE CANCEL comm<strong>and</strong> being used against the tape drive)<br />

may prevent the file from being stored in the spooling system. The files that are not<br />

loaded successfully are reported with messages sent to the SPXTAPE user <strong>and</strong><br />

recorded in the comm<strong>and</strong> summary log.

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

Saved successfully!

Ooh no, something went wrong!