03 beginningBatch

This document, "BEGINNER'S GUIDE TO MULTIPROGRAM BATCH" for the DECsystem-10, is written for inexperienced or casual users to understand and utilize the Multiprogram Batch system.

The core purpose of Multiprogram Batch is to allow users to submit jobs (combinations of programs, data, and commands) for non-interactive, background processing on a "leave-it basis." This is particularly useful for routine production tasks, large or long-running jobs, those requiring significant data, or jobs that don't need real-time user interaction.

The guide details two primary methods for submitting jobs:

1. From Cards: Users prepare a physical card deck containing their program, data, and special Batch control cards (e.g., $JOB, $ALGOL, $FORTRAN, $DATA, $EOD). These control cards simplify the process by automatically generating COMPILE and EXECUTE commands and managing program/data files on disk.
2. From an Interactive Terminal: Users create a "control file" on disk using an editor, which contains all necessary monitor commands, system program commands, and data. Jobs are then submitted using SUBMIT or QUEUE INP: commands, accompanied by various switches to specify job name, resource limits (e.g., CPU time, memory, pages of output, number of cards punched), scheduling preferences, and file disposition.

Key aspects covered include:

• Control Files: Essential for defining the sequence of operations Batch should perform.
• Job Processing: Jobs wait in a queue and are scheduled based on factors like size, resource requirements, and specified deadlines. Batch logs all commands and system responses in a "log file."
• Output Handling: Output from Batch jobs (including the log file, compilation listings, loader maps, and user-requested program output) is typically sent to peripheral devices like line printers, card punches, or magnetic tapes, and is never returned directly to a timesharing terminal. Users must specify resource estimates for printed or punched output.
• Error Recovery: The document explains how to specify error recovery procedures within the control file using Batch commands like $ERROR, $NOERROR, .IF (ERROR), .IF (NOERROR), .GOTO, and .BACKTO to prevent job termination and manage program behavior upon errors or successful execution. Without specified recovery, errors typically lead to job termination and a core dump.

The guide also provides a glossary of technical terms and numerous examples for setting up and interpreting output for common programming languages like ALGOL, COBOL, FORTRAN, and MACRO.