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.
Job processing is divided into several phases to provide parallelism through pipelining. These phases include input processing where jobs are read and interpreted, the execution phase where jobs run, and output processing where job output is printed or stored on DASD. Jobs that are in the same phase of execution are usually said to reside on a particular queue; for example, jobs that are currently executing are on the execution queue.
To improve I/O efficiency, JES performs spooling, which provides multiple jobs with simultaneous access to a common storage volume. JES uses a structure called a checkpoint to backup information about currently executing jobs and their associated output. The checkpoint can be used to restore jobs and output in the event of unexpected hardware or software failures.
Although JES2 and JES3 provide the same core functionality, there are certain features that may be present in one JES but not the other. Because of these differences, one JES may be favored over the other in certain customer installations. JCL is used to define jobs to both JES2 and JES3, but small changes usually need to be made to the JCL to get a job written for one JES to run on the other. A common issue was that JES3 checked that all datasets listed in the JCL existed before execution or that there was a prior step where the dataset was defined as NEW,CATLG. JES2 did not insist on this, allowing the job to run even though it would fail when the step using it failed to find it.
OS/360's batch job processing had limited operational flexibility and performance, which was addressed by two field-developed packages called the Houston Automatic Spooling Priority (HASP) and the Attached Support Processor (ASP).
|
Main article: Houston Automatic Spooling Priority |
HASP was developed by IBM Federal Systems Division contractors at the Johnson Space Center in Houston.[1][2] It originally managed job scheduling and print and punch output for a single OS/360 computer. Multi Access Spool capability was added to let peer computers share a common job queue and print/punch output queues.[citation needed]
With the introduction of System/370 in 1972, IBM rewrote HASP to become a standard part of the system and renamed it Job Entry Subsystem 2. JES2 was introduced in OS/VS2 in Release 2, also known as MVS, in 1973.[3] It was many years before the HASP labels were removed from the source code, and the messages issued by JES2 are still prefixed with $HASP. Several JES2 commands continue to support specification of either JES2 or HASP to maintain backwards compatibility.[4]
|
Main article: Attached Support Processor |
ASP initially stood for Attached Support Processor,[a][5] and was developed to provide efficient use of multiple systems with a shared workload. It allowed one central system to distribute jobs to multiple connected systems; ASP could run a mixture of OS/360, SVS and 7090 emulation on a 360/65 main processor, but only[b] OS/360 and SVS on other S/360 and S/370 models.. ASP was announced in March 1967,[6]: p.710 and that year was reported to be "running very stably".[7]
ASP evolved from the design of the 7094/7040 Direct Coupled System, using data channel to data channel communication.[8] By attaching an IBM 7040 as a peripheral, processor throughput was more than doubled.[citation needed]
In a typical ASP configuration, a small mainframe such as a 360/40 called the support system controlled one or more 360/65 or larger processors called main systems. The computers were connected through selector channels on each host attached to channel-to-channel adapters in an early form of short distance, point-to-point computer networking.
ASP required the purchase of an additional computer to manage input and output of the hosts running the job workload, which was economically justified by the high cost of standalone byte-multiplexor channels needed to drive printers and punched card reader devices;[citation needed] the 360/50 and smaller systems had a built-in byte multiplexor channel, whereas the faster 360/65 and larger systems required a relatively expensive standalone unit. Using ASP made it possible to avoid the cost of the byte multiplexor channel, and offloading the job scheduling, print, and card handling also offloaded those functions from the larger machines.[citation needed]
Increased reliability was another advantage to offset the added hardware cost.[citation needed] One or more main systems could fail or be taken offline for maintenance without taking down the whole complex.
ASP was primarily targeted at large government agencies and defense contractors that might have as many as six 360/65s all being scheduled and managed by a separate ASP machine.[citation needed] An uncommon variant, local ASP (LASP), was a single large machine with the ASP functions running on the same machine.
In the 1970s, a notable installation of ASP was at Princeton University controlling an IBM 360/91 mainframe.[citation needed]
In 1973, IBM rewrote ASP and renamed it JES3, supporting MVS only.[3]
There was also a JES in OS/VS1 that was often referred to as JES1.[9][10] In addition, the master (MSTR) subsystem, which is built into MVS, can start jobs that run outside of the control of the primary JES, including the Master Scheduler and the primary JES itself.[11] Originally the JCL for the Master subsystem was in an IBM provided load modules, but in current versions of MVS through z/OS, it can be provided as a member of the system parameter library (PARMLIB).
Source code was provided to IBM customers for both ASP and HASP, and many customers made substantial enhancements to these programs, some of which were incorporated into the official product.[citation needed] Far more installations made use of HASP than ASP, and in contemporary z/OS systems, there are many more JES2 installations than JES3.[citation needed] Because of their unique history, IBM continues to ship JES2 and JES3 source code instead of object code, unlike most components of the operating system.[citation needed]
To improve maintainability and serviceability of user-written enhancements, JES provides a set of exit points that pass control from the JES to user programs at key points of processing.[citation needed] These extensions can provide custom functionality such as special commands, custom print page headings, and non-standard job processing.
In 2017, IBM released a statement of direction for JES2 to be the "strategic" JES, meaning that all future development efforts will be focused on JES2 rather than JES3.[12] IBM has reassured customers that JES3 will continue to be supported until an end-of-support date is announced.[13][14] In February 2019, IBM announced that z/OS 2.5 (expected to be released in 2021) will be the last version of z/OS to include JES3.[15] In October 2019, Phoenix Software International announced that it had licensed the JES3 source code from IBM and would be taking over its maintenance and enhancement.[16]