Planning Considerations for CMS Multivolume tape files are not supported by CMS. These restrictions only apply when you run CMS. DOS and as
systems running in virtual machines can continue to read and write tapes
with standard labels, non-standard labels, and no labels on single and
multireel tape files.
The VM/370 operator must attach tapes to your CMS virtual machine
before any tape operation can take place.
For information about tape handling in the CMS/DOS environment, see
"Planning Considerations for CMS/DOS." eMS Unit Record Support CMS supports one virtual card reader at virtual address OOC, one virtual
card punch at virtual address OOD, and one virtual printer at virtual are spcolea. does not support real or dedicated unit record devices, nor does it support a
virtual 2520 Card Punch. Figure 2 lists the devices supported as
virtual devices by CMS. CARD READER
The READCARD command reads data records from the spooled card reader to
a CMS disk. Input records of 151 or fewer characters are accepted.
Column binary data is not acceptable. Your card decks must be read into
the virtual reader before a READCARD command can be issued. Do one of
the following: • Place a card deck, containing only one file, in a real card reader
and have CP read it. The card images are placed on a spool file in
the specified virtual machine's virtual card reader. If you are not
logged on when data is spooled to your virtual card reader, the deck
remains in your virtual card reader until you log on and issue the
READCARD command. • Transfer records from your virtual card punch or printer to a virtual
card reader (your own or that of another virtual machine).
For more information on reading files from the CMS card reader, see
the VML170 CARD PUNCH The eMS PUNCH command causes the specified file to be punched to the
spooled card punch. Records up to 80 characters long are accepted. Shorter records are padded to 80 characters with blanks filled in to the
right. The following are not supported: • Punch stacker select • Punch feed read • 3525 Multiline Card Print feature 28 IBM VM/310 Planning and System Generation Guide

Planning Considerations for PRINTER
The PRINT command prints the specified disk file on the spooled printer. You can specify whether the first character of each record is to be
interpreted as a carriage control character or as data. Both AS! and
machine code carriage control characters are supported. The file may
have either fixed-or variable-length records.
Editing Using the CMS Editor, you can create new files online or modify or
display portions of existing files.
The CMS Editor operates on fixed-and variable-length records. The
maximum record length accepted by the editor is 160 characters. You can
specify file characteristics, such as record length, format, and tab
locations. The system includes defaults for certain filetypes (such as ASSEMBLE and EXEC). Files are edited in virtual storage. The maximum size file that can
be edited is determined by the amount of virtual storage available to
you, minus that used by the CKS nucleus.
If the file does not fit into virtual storage, it must be divided
into smaller files, and each file edited separately. Sufficient disk
space must be available to accommodate both parts of the file.
Alternately, you can temporarily increase the size of your virtual
storage by issuing the CP DEFINE STORAGE command.
For more information about the editing facilities of CMS, see the User's eMS Batch Facility The eMS Batch Facility is a VM/370 programming facility that executes under CMS. It allows you to execute jobs in batch mode. You can submit
jobs from a virtual machine or from a real card reader. You do not have
to be logged on to submit jobs to the batch virtual machine. If you
want to use the batch facility you must define a C8S batch virtual
machine when you create your directory. You should include a
read/write disk at virtual address 195 in the directory entry.
Information about the CMS Batch Facility is in the User'2 There must be an entry in the VM/370 directory for any user who wants
to submit jobs to the CMS Batch Facility. This entry can be the
minimum: userid, password, and one device. Alternatively, you can
provide entries for users who will not be logging on to the system, but
submitting jobs through the real card reader. For these users, you can
code the password in the directory as NOLOG; these users do not ne'ed any devices defined for their virtual machines. The eMS Batch Facility uses
the FOR operand of the CP SPOOL command to identify their output files.
The batch facility provides two entry points so you can add support
that your installation may require. BATEXIT1 is provided so you can
write your own routine to check non-eMS control statements. BATEXIT2 is
provided so you can process additional information on the IJOB card.
These entry points are described in the VM/31Q PrQgrammer'2 Guide. Part 1. Planning for System Generation 29