Type III C lass A Program

CMS BATCH MONITOR
The Batch Monitor can be run from a terminal like
conversational CMS. The Batch Monitor permits use of the
FORTRAN (G), ASSEMBLER (F). and PL/I (F) compilers.
Temporary work files, referred to as FORTRAN logical files,
are stored on disk and should be of limited size. The Batch
Monitor's permanent disk is erased and CMS is re 9 IPLed
whenever a JOB card i's processed.
SAMPLE BATCH JOB
Source, object" or data cards included in the job stream are
stored as separate CMS files. Each file is identified by a
filename and filetype. FORTRAN, ASSEMBLE, and TEXT control
cards indicate the filetypes FORTRAN, SYSIN, and TEXT.
respectively. If unspecified, the filename is chosen by the
system,.
When a FORTRAN file is compiled or a SYSIN file is
assembled, an object module is generated as a file with a
filetype of TEXT and the same filename as the source file.
Data files to be read as a FORTRAN logical unit must be
identified as FILE FTOnFOOl where n is 1, 2, 3, 4, or 8.
Files created by writing on one of the above FORTRAN logical
units are identified, in the same way. These files may be
PRINT'ed or PUNCHeed using the appropriate control card and
specifying the filename and filetype,.
Execution of object modules (TEXT files) is initiated by the
GO control card. The control card causes all TEXT files to
be loaded into core. Execution begins at the entry point
specified in the GO control card or at the first program
encountered in the job stream. If a program interruption
occurs during program execution, the programmer gets a
complete core dump and the job is terminated. Data cards
following the GO control card can be read as FORTRAN logical
unit 5 (sysin). Any data cards following the GO control
card which are not read are ignored. An example of a CMS
Batch job deck is shown in Figure 48.
526 CMS Batch Monitor