Remote job entry

Last updated

Remote job entry, or Remote Batch, 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.

Contents

The RJE workstation is called a remote because it usually is located some distance from the host computer. The workstation connects to the host through a modem, digital link, packet-switching network [lower-alpha 1] or local area network (LAN). RJE is similar to uux and SSH, except that the workstation sends a complete job stream [lower-alpha 2] rather than a single command and that the user does not receive any output until the completion of the job.. The terms Remote Batch, Remote Job System[ citation needed ] and Remote Job Processing are also used for RJE facilities.

Examples

Remote Job Entry (RJE) is also the name of an OS/360 component [1] that provided RJE services. An RJE workstation operator may have complete console control of the job flow between the workstation and mainframe, depending on local configuration and policy.

Houston Automatic Spooling Priority (HASP) initially supported job entry from terminals using Synchronous transmit-receive (STR); eventually HASP II [2] supported only Binary Synchronous Communications (BSC), and added the Multi-leaving [3] protocol for BSC programmable work stations; this protocol is incompatible with that used by OS/360 RJE and is the basis for protocols used for job submission from programmable work stations for, e.g., Attached Support Processor (ASP), JES2, JES3, OS/VS1 Remote Entry Services (RES), VM RSCS, as well as the later protocols for Network Job Entry (NJE) [4] in, e.g., JES2, JES3, VM RSCS.

Conversational Remote Job Entry (CRJE) [5] is a component of OS/360 and OS/VS1 that provides job submission, job retrieval and editing for a user at an interactive terminal.

Remote Entry Services] [6] [7] (RES) is a component of OS/VS1 that provides RJE services. An RES workstation operator may have complete console control of the job flow between the workstation and mainframe, depending on local configuration and policy.

Remote Spooling Communications Subsystem (RSCS) [8] is, depending on the release, a component of or extra cost product in VM that provides RJE services. The RSCS in the free VM/370 only supported BSC; [lower-alpha 3] IBM added support for Systems Network Architecture (SNA), NJE and TCP/IP over several chargeable versions.

Network Job Entry (NJE) [4] is Store and forward networking for transmitting, e.g., card files, jobs, printed output, among peers. The initial versions of NJE for JES2, JES3, VSE POWER and VM RSCS used BSC multileaving, but IBM quickly added support for Channel-to-channel adapters. IBM later added support for SNA and, ultimately, TCP/IP. [9]

NETRJS is the protocol developed by the Campus Computing Network at UCLA to deliver batch jobs to the Remote Job Service (RJS) on their IBM 360 Model 91. [10] [11] This protocol was originally assigned to ARPANET Initial Connection Protocol sockets 71, 73, and 75, [12] and later reassigned to Internet ports 71–74. [13] RJS is a subsystem of OS/360 MVS written by UCLA to support remote batch from card-reader/printer terminals. [10]

RJE workstations

Early RJE workstations were "dumb" (non-programmable) devices using byte-synchronous communications protocols such as IBM BISYNC or STR, or equivalents from other vendors. Later, programmable devices or small computers were used, and IBM developed a protocol called HASP multileaving for use with HASP, and later, e.g., ASP, JES2, JES3, RSCS. The IBM System/360 Model 20 and 1130, the Mohawk Data MDS 2400 and the UNIVAC 1004, were popular. Later still RJE workstations switched to bit-oriented full duplex protocols such as IBM Synchronous Data Link Control, HDLC, or X.25. The Internet Engineering Task Force has defined RFCs for internet remote job entry protocols, but they are now considered obsolete or legacy. [14]

The 200 USER Terminal is a remote batch terminal and protocol [15] developed by the Control Data Corporation for their CDC 6000 series and CDC 3000 series mainframe computers in the 1960s. A 200 USER Terminal consisted of a low speed punched card reader, a line printer, and a CRT operators console. It typically communicated with a remote mainframe via synchronous modem. The software subsystem on the mainframe side was called Export-Import 200, and later, the Remote Batch Facility (RBF). Other remote batch terminals using the UT200 protocol included the CDC 731, 732, and 734. [16] Software emulators for the UT200 protocol were also written for a number of minicomputer systems.

Network Job Entry

RJE is well suited to organizations that had a single large central computer center. However, in large organizations with multiple data centers, there was an interest in a peer-to-peer transfer of, e.g., submitted jobs, printer output. Following customer requests, IBM developed a suite of facilities, derived from BITNET and VNET, known as Network Job Entry. As part of that software, IBM provided commands to transmit datasets among nodes (complexes of computers with a collective name). NJE allows a batch job to control where it would run and where its output would be processed; similarly, NJE allows an interactive user to send printed or punched output to a different node.

IBM has integrated NJE facilities into its mainframe software, and it is no longer available as separate products. However, the NJE support in JES3 requires the Batch Data Transmission (BDT) program product and the NJE support in z/VM requires the Remote Spooling Communications Subsystem (RSCS) program product. NJE supports Binary Synchronous Communications (BSC), Channel-to-channel adapter (CTCA), Systems Network Architecture (SNA) and TCP/IP [17] connections among its nodes. [9]

See also

Notes

  1. ↑ E.g., Internet, X.25
  2. ↑ One or more STDIN streams in Unix terminology
  3. ↑ including multi-leaving

Related Research Articles

<span class="mw-page-title-main">MVS</span> Operating system for IBM mainframes

Multiple Virtual Storage, more commonly called MVS, is the most commonly used operating system on the System/370, System/390 and IBM Z 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 a method of running software programs called jobs in batches automatically. While users are required to submit the jobs, no other interaction by the user is required to process the batch. Batches may automatically be run at scheduled times as well as being run contingent on the availability of computer resources.

Systems Network Architecture (SNA) is IBM's proprietary networking architecture, created in 1974. It is a complete protocol stack for interconnecting computers and their resources. SNA describes formats and protocols but, in itself, is not a piece of software. The implementation of SNA takes the form of various communications packages, most notably Virtual Telecommunications Access Method (VTAM), the mainframe software package for SNA communications.

<span class="mw-page-title-main">VM (operating system)</span> Family of IBM operating systems

VM is a family of IBM virtual machine operating systems used on IBM mainframes System/370, System/390, zSeries, System z and compatible systems, including the Hercules emulator for personal computers.

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. The purpose of JCL is to say which programs to run, using which files or devices for input or output, and at times to also indicate under what conditions to skip a step. Parameters in the JCL can also provide accounting information for tracking the resources used by a job as well as which machine the job should run on.

<span class="mw-page-title-main">Spooling</span> Form of multitasking in computers

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.

VNET is an international computer networking system deployed in the mid-1970s and still in current, but highly diminished use. It was developed inside IBM and provided the main email and file-transfer backbone for the company throughout the 1980s and 1990s. Through it, a number of protocols were developed to deliver email amongst time sharing computers over alternative transmission systems.

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.

<span class="mw-page-title-main">SDSF</span> Component of the z/OS operating system

The System Display and Search Facility (SDSF) is a component of IBM's mainframe operating system, z/OS, is an interactive user interface that allows users and administrators to view and control various aspects of the mainframe's operation and system resources. Some of the information displayed in SDSF includes Batch job output, Unix processes, scheduling environments, and the status of external devices such as printers and network lines, batch and system log files and dumps.

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.

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."

The IBM 2780 and the IBM 3780 are devices developed by IBM to perform remote job entry (RJE) and other batch functions over telephone lines; they communicate with the mainframe via Binary Synchronous Communications and replaced older terminals using synchronous transmit-receive (STR). In addition, IBM has developed workstation programs for the 1130, 360/20, 2922, System/360 other than 360/20, System/370 and System/3.

<span class="mw-page-title-main">OS/VS1</span> IBM operating system

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 IBM mainframe operating systems is significant within the history of mainframe operating systems, because of IBM's long-standing position as the world's largest hardware supplier of mainframe computers. IBM mainframes run operating systems supplied by IBM and by third parties.

<span class="mw-page-title-main">OS/360 and successors</span> 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.

BITNET was a co-operative U.S. university computer network founded in 1981 by Ira Fuchs at the City University of New York (CUNY) and Greydon Freeman at Yale University. The first network link was between CUNY and Yale.

<span class="mw-page-title-main">OS/VS2 (SVS)</span>

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.

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.

The European Academic and Research Network (EARN) was a computer network connecting universities and research institutions across Europe, and was connected in 1983 via transatlantic circuits and a gateway funded by IBM to BITNET, its peer in the United States.

Job Entry Subsystem (JES), 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.

References

  1. ↑ IBM System/360 Operating System Remote Job Entry Program Number 360S-RC-536 (PDF). IBM. November 1968. C30-2006-2.
  2. 1 2 OS/VS2 HASP II Version 4 System Programmer's Guide Program 370H-TX-001. IBM. GC27-6992.
  3. ↑ "Appendix B MULTI-LEAVING" (PDF). OS/VS2 HASP II Version 4 Logic - Program Number 370H-TX-001 VS2 - SVS Release 1.7 (PDF) (First ed.). IBM. September 15, 1976. p. 7-59-7-68. GY27-7255. Retrieved March 17, 2022.
  4. 1 2 Network Job Entry (NJE) Formats and Protocols (First ed.). IBM. 2014. SA32-0988-00.
  5. ↑ IBM System/36D Operating System: Conversational Remote Job Entry Concepts and Facilities (PDF). IBM. GC30-2012-0.
  6. ↑ "Remote Entry Services". OS/Virtual Storage 1 Features Supplement (PDF) (First ed.). IBM. August 1972. p. 33. GC20-1752-0.
  7. ↑ "Remote Entry Services (RES)". OS /VS1 Planning and Use Guide VS1 Release 2 (PDF) (Second ed.). January 1973. p. 18. GC24-5090-1.
  8. 1 2 Remote Spooling Communications Subsystem Networking Program Reference and Operations Manual (PDF) (Third ed.). April 1982. SH24-5005-2.
  9. 1 2 z/OS Network Job Entry (NJE) Format and Protocols (PDF). Version 2 Release 3. IBM. March 12, 2018. SA32-0988-30. Retrieved April 30, 2023.
  10. 1 2 Braden, R.; Wolfe, S. (January 1971). NETRJS - A THIRD LEVEL PROTOCOL FOR REMOTE JOB ENTRY. IETF. doi: 10.17487/RFC0088 . RFC 88.
  11. ↑ Braden, R. T. (January 1971). CCN AS A NETWORK SERVICE CENTER. IETF. doi: 10.17487/RFC0090 . RFC 90.
  12. ↑ Postel, J. (November 1977). ASSIGNED NUMBERS. IETF. doi: 10.17487/RFC0739 . RFC 739.
  13. ↑ Postel, J.; Vernon, J. (January 1983). ASSIGNED NUMBERS. IETF. doi: 10.17487/RFC0820 . RFC 820.
  14. ↑ Bressler, R.D.; Guida, R.; McKenzie, A.M. "Remote Job Entry Protocol". RFC Editor. IETF. doi:10.17487/RFC0407. RFC   407 . Retrieved Mar 12, 2022.
  15. ↑ 200 User Terminal - Hardware Reference Manual (PDF). July 1968. 82128000. Retrieved March 13, 2022.
  16. ↑ 731-12 - 732-12 - Batch Terminals - Operating and Programming Guide (PDF). November 1972. 82163400B-1. Retrieved March 13, 2022.
  17. ↑ "NJE/IP". Sine Nomine Associates. Retrieved March 8, 2023.
  18. ↑ IBM System/360 and System/370 Asymmetric Multiprocessing System: General Information Manual, Program Number 360A-CX-15X. IBM. GH20-1173.
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.