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.

queue, but simply indicates whether a file is purged or retained after being<br />

read, <strong>and</strong> if it is retained, whether the file remains eligible for immediate<br />

reprocessing.<br />

SPOOL<br />

The files in your reader queue are controlled through a combination of file<br />

characteristics <strong>and</strong> the options in effect for the virtual reader on which they are<br />

processed. Input files do not derive their characteristics from the reader, except<br />

for hold status, which is set as a function of the KEEP option. Table 19<br />

summarizes the disposition of a reader file after it has been processed,<br />

depending on the hold/keep settings specified for the reader, <strong>and</strong> the keep<br />

setting of the file.<br />

For output devices (virtual printers, punches, <strong>and</strong> consoles) use the SPOOL<br />

comm<strong>and</strong> to define the characteristics of the spool files you are creating. You<br />

can use the SPOOL comm<strong>and</strong> to indicate whether files are to be held from<br />

further processing, <strong>and</strong> whether they are to be retained after they have been<br />

processed. This information is associated with the spool file itself, regardless of<br />

the characteristics of the device on which the file is to be processed. In<br />

addition, use SPOOL to direct the output files that you are creating to unit<br />

record devices (readers, printers, <strong>and</strong> punches) associated with other virtual<br />

machines.<br />

Table 19. Disposition of Reader Files Depending upon HOLD/KEEP Settings<br />

File<br />

Status<br />

Device Options Disposition<br />

NOKEEP NOHOLD/NOKEEP The file is purged.<br />

NOKEEP NOHOLD/KEEP The file is retained in user hold status. KEEP is not set<br />

on the file.<br />

NOKEEP HOLD/NOKEEP The file is retained <strong>and</strong> remains eligible for processing<br />

on your virtual reader.<br />

NOKEEP HOLD/KEEP The file is retained in user hold status. KEEP is not set<br />

on the file.<br />

KEEP Any setting The file is retained in user hold status. KEEP status<br />

remains on the file.<br />

All of your output files derive their characteristics from the virtual device on<br />

which they were created. If the output device is spooled with the KEEP <strong>and</strong><br />

NOHOLD options, the file is printed or punched, <strong>and</strong> then placed in HOLD<br />

status, retaining its KEEP characteristics. If you change the file status to<br />

NOHOLD, the file is processed at the real device one more time <strong>and</strong> once<br />

again is placed in HOLD status. If you do not want to retain the file, you must<br />

change both its NOHOLD status <strong>and</strong> NOKEEP characteristic, or purge it using<br />

the PURGE comm<strong>and</strong>.<br />

6. Unless you reset these values, the following options are the default values for<br />

your spool files:<br />

Device Default Options<br />

Reader<br />

NOHOLD NOKEEP NOCONT NORESCAN EOF CLASS A ¹<br />

Punch<br />

NOHOLD NOKEEP NOCONT CLASS A¹ OFF COPY 001 NOMSG<br />

NONAME NOEOF DEST OFF<br />

Printer<br />

NOHOLD NOKEEP NOCONT CLASS A¹ OFF COPY 001 NOMSG<br />

NONAME NOEOF DEST OFF<br />

Console<br />

NOHOLD NOKEEP NOCONT CLASS T¹ OFF COPY 001 TERM TO *<br />

PRINTER NOMSG STOP NONAME NOEOF DEST OFF<br />

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

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

Saved successfully!

Ooh no, something went wrong!