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

Planning Considerations for CMS You can write EXEC procedures to control the operation of a batch
facility virtual machine. See the VM/J70 for examples
of these EXEC procedures. Saving eMS CMS is designed so that it can be saved easily and so that the second
segment of CMS can be shared by CMS users. Also, CMS is designed so
that CMS/DOS, CMS VSAM and access method services, the CMS Editor, eMS EXEC processor, and CMS OS simulation routines can be placed in
discontiguous saved segments. The VM/370 starter system has entries in
the system name table (DMKSNT) and CP system control file (DMKSYS) so
that you can save CMS (and the CMS discontiguous saved segments) at the
end of the system generation procedure for eMS. For more information about saved systems, see the "Saved Systems" sect.ion of this mannal and. see the !M/370 30 IBM VM/370 Planning and System Generation