History
IBM proclaimed JES1 to be "the single most important addition" to the job scheduling provided by VS1. IBM Systems Journal defined JES1's services as Spooling and scheduling, adding "Its three major components are peripheral services, central services, and queue management." JES1 was not popular, because HASP and ASP users often had made local modifications (edits), and wanted to retain their investment.Features
JES1 permitted operators to submit batch jobs from localNew Features
* In MFT a reader or writer task tied up a partition; in JES1 a separate partition was required only while starting or stopping the task. * In MFT each SPOOL file was a separate physical sequential (PS) dataset on public DASD; in JES1 SPOOL files are kept in a common SPOOL dataset managed by JES1. * In MFT a reader task could be delayed by interpreting tasks; in OS/VS1 the interpretation is done when the job is initiated. * The JOB Card JCL was given a new option: TYPRUN=SCAN, whereby a job could be submitted for quick feedback, and - if no errors were detected - be submitted again (without TYPRUN=SCAN on the JOB Card. * JES1 used a SubSystem Interface (SSI) similar to that in MVS.References
{{Reflist IBM software IBM mainframe software