Job Entry Subsystem 1 (JES1)

Last updated

Job Entry Subsystem (JES), [1] aka Job Entry Subsystem 1 (JES1), 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.

Contents

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 operators to submit batch jobs from local unit record equipment.

In addition, Remote Entry Service (RES) permitted remote operators to submit jobs from remote sites [6] to JES. The printed and punched output of jobs running on OS/VS1, whether submitted locally or remotely, is handled by JES and may be routed to local devices, to the originating site or to 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

Related Research Articles

MVS Operating system for IBM mainframes

Multiple Virtual Storage, more commonly called MVS, was the most commonly used operating system on the System/370 and System/390 IBM mainframe computers. IBM developed MVS, along with OS/VS1 and SVS, as a successor to OS/360. It is unrelated to IBM's other mainframe operating system lines, e.g., VSE, VM, TPF.

Computerized batch processing is the running of "jobs that can run without end user interaction, or can be scheduled to run as resources permit."

Job Control Language (JCL) is a name for scripting languages used on IBM mainframe operating systems to instruct the system on how to run a batch job or start a subsystem.

Spooling

In computing, spooling is a specialized form of multi-programming for the purpose of copying data between different devices. In contemporary systems, it is usually used for mediating between a computer application and a slow peripheral, such as a printer. Spooling allows programs to "hand off" work to be done by the peripheral and then proceed to other tasks, or to not begin until input has been transcribed. A dedicated program, the spooler, maintains an orderly sequence of jobs for the peripheral and feeds it data at its own rate. Conversely, for slow input peripherals, such as a card reader, a spooler can maintain a sequence of computational jobs waiting for data, starting each job when all of the relevant input is available; see batch processing. The spool itself refers to the sequence of jobs, or the storage area where they are held. In many cases, the spooler is able to drive devices at their full rated speed with minimal impact on other processing.

This article discusses support programs included in or available for OS/360 and successors. IBM categorizes some of these programs as utilities and others as service aids; the boundaries are not always consistent or obvious. Many, but not all, of these programs match the types in utility software.

The Job Entry Subsystem (JES) is a component of IBM's MVS mainframe operating systems that is responsible for managing batch workloads. In modern times, there are two distinct implementations of the Job Entry System called JES2 and JES3. They are designed to provide efficient execution of batch jobs.

Remote job entry is the procedure for sending requests for non-interactive data processing tasks (jobs) to mainframe computers from remote workstations, and by extension the process of receiving the output from such jobs at a remote workstation.

Binary Synchronous Communication is an IBM character-oriented, half-duplex link protocol, announced in 1967 after the introduction of System/360. It replaced the synchronous transmit-receive (STR) protocol used with second generation computers. The intent was that common link management rules could be used with three different character encodings for messages. Six-bit Transcode looked backwards to older systems; USASCII with 128 characters and EBCDIC with 256 characters looked forward. Transcode disappeared very quickly but the EBCDIC and USASCII dialects of Bisync continued in use.

Queued Telecommunications Access Method (QTAM) is an IBM System/360 communications access method incorporating built-in queuing. QTAM was an alternative to the lower level Basic Telecommunications Access Method (BTAM).

Conversational Programming System or CPS was an early Time-sharing system offered by IBM which ran on System/360 mainframes circa 1967 through 1972 in a partition of OS/360 Release 17 MFT II or MVT or above. CPS was implemented as an interpreter, and users could select either a rudimentary form of BASIC or a reasonably complete version of PL/I. A third option provided remote job entry (RJE) features allowing users to submit JCL job streams for batch processing. A fourth option was called control mode. Normally, only the system operator would be permitted to use control mode. The available features in control mode included:

The Houston Automatic Spooling Priority Program, commonly known as HASP, is an extension of the IBM OS/360 operating system and its successors providing extended support for "job management, data management, task management, and remote job entry."

OS/VS1

Operating System/Virtual Storage 1, or OS/VS1, is a discontinued IBM mainframe computer operating system designed to be run on IBM System/370 hardware. It was the successor to the Multiprogramming with a Fixed number of Tasks (MFT) option of System/360's operating system OS/360. OS/VS1, in comparison to its predecessor, supported virtual memory. OS/VS1 was generally available during the 1970s and 1980s, and it is no longer supported by IBM.

The history of operating systems running on IBM mainframes is a notable chapter of history of mainframe operating systems, because of IBM's long-standing position as the world's largest hardware supplier of mainframe computers.

OS/360 and successors Operating system for IBM S/360 and later mainframes

OS/360, officially known as IBM System/360 Operating System, is a discontinued batch processing operating system developed by IBM for their then-new System/360 mainframe computer, announced in 1964; it was influenced by the earlier IBSYS/IBJOB and Input/Output Control System (IOCS) packages for the IBM 7090/7094 and even more so by the PR155 Operating System for the IBM 1410/7010 processors. It was one of the earliest operating systems to require the computer hardware to include at least one direct access storage device.

Edos is a discontinued operating system based upon IBM's original mainframe DOS. The name stood for extended disk operating system.

System Generation (SysGen) is a two-stage process for installing or updating OS/360, OS/VS1, OS/VS2 (SVS), OS/VS2 (MVS) and chargeable systems derived from them. There are similar processes for, e.g., DOS/360, which this article does not cover. Also, some of the details have changed between releases of OS/360 and many details do not carry over to later systems.

OS/VS2 (SVS)

Single Virtual Storage (SVS) refers to Release 1 of Operating System/Virtual Storage 2 (OS/VS2); it is the successor system to the MVT option of Operating System/360. OS/VS2 (SVS) was a stopgap measure pending the availability of MVS, although IBM provided support and enhancements to SVS long after shipping MVS.

The IBM Administrative Terminal System, also known as ATS/360, provided text- and data-management tools for working with documents to users of IBM System/360 systems.

Remote Spooling Communications Subsystem or RSCS is a subsystem of IBM's VM/370 operating system which accepts files transmitted to it from local or remote system and users and transmits them to destination local or remote users and systems. RSCS also transmits commands and messages among users and systems.

Attached Support Processor (ASP) was an implementation of loosely coupled multiprocessing for IBM's OS/360 operating system. IBM later changed the name to Asymmetrical multiProcessor but retained the acronym ASP.

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. 1 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. 1 2 3 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 page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.