Job Entry Subsystem 1 (JES1)

Job Entry Subsystem 1 (JES1)[1]was released by IBM as an integral part of OS/VS1 as an enhancement to the basic functions that users of VS1's predecessor, MFT, had.

History

IBM proclaimed[2] JES1 to be "the single most important addition" to the job scheduling provided by VS1. IBM Systems Journal[3] 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,[4]:5 because HASP and ASP users often had made local modifications (edits),[4]:9 and wanted to retain their investment.[5]


Features

JES1 permitted batch jobs to be submitted from remote sites,[6] executed on an IBM mainframe, then produce printed and punched output either at the originating site or, if desired, at the main site or another remote site.[4][7] The Remote Entry Services (RES)[8] of OS/VS1 is similar to Remote Job Entry (RJE) on OS/360 but the protocol for programmable workstations is that used by HASP II and ASP rather than that used by RJE.

New 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 interpretatuon 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.[2]:399
  • JES1 used a SubSystem Interface (SSI) similar to that in MVS.
gollark: I should really check more.
gollark: It has Risk of Rain or something.
gollark: Oh, we expanded the EM playlist a little bit recently.
gollark: The system is also able to detect when there is no prefix available from an upstream interface and can switch into relaying mode automatically to extend the upstream interface configuration onto its downstream interfaces. This is useful for putting the target router behind another IPv6 router which doesn't offer prefixes via DHCPv6-PD.
gollark: OpenWrt features a versatile RA & DHCPv6 server and relay. Per default SLAAC and both stateless and stateful DHCPv6 are enabled on an interface. If there are any prefixes of size /64 or shorter present then addresses will be handed out from each prefix. If all addresses on an interface have prefixes shorter than /64 then DHCPv6 Prefix Delegation is enabled for downstream routers. If a default route is present the router advertises itself as default router on the interface.

References

  1. IBM 3800 Printing Subsystem Programmer's Guide (PDF) (Fourth ed.). IBM. January 1980. GC26-3846-3. JES1, the job entry subsystem for OS/VS1.
  2. T. F. Wheeler, Jr. (1973). IBM OS/VS1 - An evolutionary growth system. International Workshop on Managing Requirements Knowledge. New York, NY: AFIPS. p. 395. doi:10.1109/AFIPS.1973.92.
  3. Baily, J. H.; Howard, J. A.; Szczygielski, T. J. (1974). "The job entry subsystem of OS/VS1". IBM Systems Journal. 13 (3): 253–269. doi:10.1147/sj.133.0253. ISSN 0018-8670.
  4. Tom Wasik. "JES2 Bootcamp - Part 1 of 3: What is JES2 and what does it do" (PDF).
  5. above IBM document, page 5. Also, there was a HASP modification "clearinghouse" at University of Chicago, from which other HASP users "downloaded" (actually printed via RJE and rekeyed ("Keypunched"); this was before the term download was in use).
  6. J. M. Hutchinson (March 1980). Job Networking Facilities (PDF). Redbooks. IBM. GG22-9042-00. RJE is usually part of the system or job entry subsystem
  7. which also (p.7) describes this as being an "early 'client server' which "Uses BSC and SNA protocols," adding "still used today." (2013)
  8. "Remote Entry Services (RES)". OS/VS1 Planning and Use Guide (PDF) (Second ed.). IBM. January 1973. p. 18. GC24-5090-1.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.