Until any of these files are processed, or in the case of files in the
hold status, until they are released, you can change the spool file name and spool file type (this information appears on the first page or first
card of output), the distribution code, the number of copies, the class,
or the hold status, using the CP CHANGE command. For example:
cp change printer all nohold
changes all printer files that are in a hold status to a Dohold status.
The CP CHANGE command can also change the spooling class, distribution
code, and so on.
If you decide that you do not want to print a particular printer
file, you can delete it with the CP PURGE command:
cp purge printer 7615
After you have punched a file to some other user, you cannot change
its characteristics or delete it unless you restore it to your own
virtual reader. You can do this with the TRANSFER command:
cp transfer all from usera
This command returns to your virtual card reader all punch files that
you spooled to USERA's virtual card reader. You can determine, for your reader or printer files, in what order
they should be read or printed. If you issue the command:
cp order printer 8195 6547
Then, the file with spoolid of 8195 is printed before the file with a
spoolid of 6547.
The CP spooling system is very flexible, and can be a useful tool, if
you understand and use it properly. The £2£ contains complete format and operand descriptions for the CP commands you can use to modify spool files. USING YOUR CARD PUNCH AND CARD READER IN CMS The CMS READCARD command reads cards from your virtual card reader at
address OOC. Cards can be placed in the reader in one of two ways: • By reading real punched cards into the system card reader. A CP ID
card tells the CP spooling system which virtual card reader is to
receive the card images. • By transferring a file from another virtual machine. Cards are
transferred as a result of a virtual punch or printer being spooled
with the TO operand, or as a result of the TRANSFER command. Virtual card images are created with the CMS PUNCH command, or from user
programs or EXEC procedures.
If you have a deck of punched cards that you want read into your virtual
machine card reader, you should punch, preceding the deck, a CP ID card:
ID HAPPY 116 IBM VM/370 eMS User's Guide

If you plan to use the READCARD command to read this file onto a CMS disk, you can also punch a READ control card that specifies the filename
and filetype you want to have assigned to the file:
:READ PROG6 ASSEMBLE Then, to read this file onto your CMS A-disk, you can enter the command:
readcard *
If a file named PROG6 ASSEMBLE already exists, it is reFlaced.
If you do not punch a READ control card, you can specify a filename
and filetype on the READCARD command:
readcard prog6 assemble
If this spool file contained a READ control card, the card is not read,
but remains in the file; if you edit the file, you can use the DELETE
subcommand to delete it.
If a file does not have a READ control card, and if you do not
specify a filename and filetype when you read the file, CMS names the
file READCARD CMSUT18 If you are reading many files into the real system card reader, and
you want to read them in as separate spool files (or you want to spool
them to different userids), you must separate the cards and read the
decks onto disk individually. The CP system, after reading an ID card,
continues reading until it reaches a physical end of file. When you use the CMS PUNCH command to punch a spool file, a READ control
card is punched to precede the deck, so that it can be read with the READCARD command. If you do not wish to punch a READ control card (also
referred to as a header card), you can use the NOHEADER option on the PUNCH command:
punch prog8 assemble * noheader You should use the NOHEADER option whenever you punch a file that is not
going to be read by the READCARD command.
The PUNCH command can only punch records of up to 80 characters in
length. If you need to punch or to transfer to another user a file that
has records greater than 80 characters in length, you can use the DISK DUMP command:
disk dump prog9 data
If your virtual card punch has been spooled to another user, that user
can read this file using the DISK LOAD command:
disk load Unlike the READCARD command, DISK LOAD does not allow you to specify a
file identification for a file you are reading; the filename and
filetype are always the same as those specified by the DISK DUMP command that created the spool file.
A card file created by the DISK DUMP command can only be read onto
disk by the DISK LOAD command. Section 7. Using Real Printers, Punches, Readers, and Tapes 117