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.

DEFINE (Spooling Device)<br />

Examples<br />

Responses<br />

7. There is no Channel Comm<strong>and</strong> Word (CCW) validation performed for VAFP<br />

devices. Therefore, spool files for VAFP devices may contain CCWs that do<br />

not appear for other devices (for example: SENSE ID <strong>and</strong> READ FCB).<br />

Specifically, when performing CCW I/O operations to a VAFP printer, most<br />

CCWs in the channel program are treated as a write operation CCW. The<br />

exceptions are X'08' which is treated as a transfer in channel comm<strong>and</strong>, X'03'<br />

with a byte count of one which is treated as a no operation instruction, <strong>and</strong><br />

X'04' which is treated as a sense comm<strong>and</strong>.<br />

The flags in the CCW flag field (for example, comm<strong>and</strong> chaining <strong>and</strong> data<br />

chaining flags) will be respected for VAFP devices as they are for other virtual<br />

printers with one exception. The SKIP flag will be ignored because most CCWs<br />

are treated as write operations by these devices. The SKIP flag will be<br />

preserved in the CCW that is placed in the spool file.<br />

8. VAFP spool files with skip to channel other than 1 will not be rejected.<br />

9. There is no corresponding real device type for a VAFP.<br />

10. VAFP spool files are intended for use by AFP* printers <strong>and</strong> real printers<br />

managed by RSCS. VAFP printers are not intended for normal use as a virtual<br />

printer.<br />

Print files created on <strong>VM</strong> using the VAFP support can be chosen for printing by<br />

the <strong>CP</strong> real printer system. Care must be taken by the application which<br />

creates these files. If the file is to be printed on a <strong>VM</strong> system printer, the<br />

application must only use st<strong>and</strong>ard impact printer CCWs to create the file.<br />

11. Files created on a VAFP device can be read by the virtual card reader using<br />

either an assembler I/O instruction or DIAGNOSE code X'A8'. However, the<br />

data in these files may be truncated. With respect to the read operation, these<br />

files are treated like a file created on a virtual 3800 printer. That is, the file is<br />

treated as if it has a logical record length of 204 <strong>and</strong> the records are truncated<br />

at that point. The data in these files can be accessed without truncation by<br />

using DIAGNOSE X'14' or the IUCV *SPL system service.<br />

12. For more information, see “Usage Notes” on page 113.<br />

define reader as 00c<br />

You can specify the oper<strong>and</strong>s after vdev in any order <strong>and</strong> repeatedly. However, the<br />

last specification of a repeatedly defined oper<strong>and</strong> is the one used. For example, if<br />

you enter:<br />

define 3800 as 00a cfs datck size 07 22 2wcgm bts<br />

BTS is the value used instead of CFS because it was specified after CFS.<br />

Response 1:<br />

type vdev DEFINED<br />

confirms that the device has been defined.<br />

type<br />

identifies a reader, printer, or punch.<br />

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

vdev<br />

identifies the virtual number of the spool device.

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

Saved successfully!

Ooh no, something went wrong!