226 IBM VM/370 CMS User's Guide

Section 12. Using the eMS Batch Facility
The eMS batch facility provides a way of submitting jobs for batch
processing in CMS. You can use the CMS batch facility when: • You have a job (like an assembly or execution) that takes a lot of
time, and you want to be able to use your terminal for other work
while the time-consuming job is being run. • You do not have access to a terminal.
The CMS batch facility is really a virtual machine, generated and
controlled by the system operator, who logs on VM/370 using the batch
userid and invoking the CMSBATCH command. All jobs sutmitted for batch
processing are spooled to the userid of this virtual machine, which
executes the jobs sequentially. To use the CMS batch facility at your
location, you must ask the systea operator what the userid of the batch
virtual machine is.
Submitting Jobs to the eMS Batch Facility Under a real as or DOS system, jobs submitted in batch mode are
controlled by JCL specifications. Batch jobs submitted to the CMS batch
facility are controlled by the control cards IJOB, ISET, and 1*, and by CMS commands.
Any application or development program written in a language
supported by YM/370 may be executed on the batch facility virtual
machine. However, there are restrictions on programs using certain CP and CMS commands, as described later in this section. INPUT TO TEE BATCH MACHINE Input records must be in card-image format, and may be punched on real
cards, placed in a CMS file with fixed-length, SO-character records, or
punched to your virtual card punch. These jobs are sent to the batch
virtual machine in one of two ways: • By reading the real punched card input into the system card reader • By spooling your virtual card punch to the virtual reader of the
batch virtual machine When you submit a real card deck to the batch machine, the first card
in the deck must be a CP ID card. The ID card takes the form: I lID userid
where ID must begin in card column one and be separated from userid (the
batch facility virtual machine userid) by one or more blanks. Section 12. Using the CMS Batch Facility 227