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.

QUERY READER/PRINTER/PUNCH<br />

Response 9: (QUERY PRINTER only)<br />

When <strong>CP</strong> manages a real 3800 system printer, it maintains a delayed purge queue<br />

for each 3800 system printer. If the files have already been printed, but are being<br />

held in this delayed purge queue, the text **PRINTED** will be displayed in the<br />

column that usually contains the date <strong>and</strong> time.<br />

ORIGINID FILE CLASS RECORDS <strong>CP</strong>Y HOLD DATE TIME NAME<br />

userid spid c typ nnnnnnnn nnn SYS **PRINTED** filename<br />

TYPE DIST<br />

filetype distcode<br />

The delayed purge queue for each printer is limited, so this file should eventually be<br />

purged by the system when it gets 'pushed' off the queue by subsequent print jobs.<br />

A file marked **PRINTED** cannot be changed, transferred, ordered, tagged, or<br />

dumped by SPXTAPE. It can be deleted by the PURGE comm<strong>and</strong>, which can be<br />

issued by the operator, or by the owner of the file.<br />

These files may become detached from the delayed purge queue by events like an<br />

abnormal system shutdown or CSE synchronization. When this happens, the file will<br />

not be automatically deleted by the system. It should be deleted by the operator or<br />

the owner of the file.<br />

Response 10:<br />

If no files of the specified type exist, one of the following responses is given,<br />

corresponding to the specified file type:<br />

NO RDR FILES<br />

- or -<br />

NO PRT FILES<br />

- or -<br />

NO PUN FILES<br />

Response 11:<br />

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

In a CSE complex, one response to this comm<strong>and</strong> differs from the response in a<br />

non-CSE complex. The comm<strong>and</strong> QUERY RDR/PRT/PUN ALL shows whether a file<br />

is unavailable for processing. LOCK sysname means the file is locked by (another)<br />

system sysname. When a spool file is requested <strong>and</strong> the file is unavailable to the<br />

inquiring system because it is in use by another system, a status of LOCK appears<br />

under DATE, <strong>and</strong> the system that is using the spool file appears under TIME. For<br />

example:<br />

ORIGINID FILE CLASS RECORDS <strong>CP</strong>Y HOLD DATE TIME NAME TYPE DIST<br />

userid spid c typ nnnnnnnn nnn NONE LOCK- sysname fnft distcode<br />

COPY systemid means this system’s SPFBK is a copy, <strong>and</strong> the lock cannot be<br />

obtained because communication is not available to the system that owns the<br />

original. When the requested spool file is a copy <strong>and</strong> the file cannot be processed<br />

because communications with the owning system are impossible, a status of COPY<br />

appears under DATE, <strong>and</strong> the system that owns the spool file appears under TIME.<br />

For example,<br />

ORIGINID FILE CLASS RECORDS <strong>CP</strong>Y HOLD DATE TIME NAME TYPE DIST<br />

userid spid c typ nnnnnnnn nnn NONE COPY- sysname fnft distcode

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

Saved successfully!

Ooh no, something went wrong!