Remote job entry is the procedure for sending requests for non-interactive data processing tasks to mainframe computers from remote workstations, and by extension the process of receiving the output from such jobs at a remote workstation. 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 or local area network. RJE is similar to uux and SSH, except that the workstation sends a complete job stream 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 and Remote Job Processing are also used for RJE facilities.
Examples
Remote Job Entry is also the name of an OS/360 component 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 initially supported job entry from terminals using Synchronous transmit-receive ; eventually HASP II supported only Binary Synchronous Communications, and added the Multi-leaving protocol for BSC programmable work stations; this protocol was 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., JES2, JES3, OS/VS1 RES, VM RSCS, as well as the later protocols for Network Job Entry in, e.g., JES2, JES3, VM RSCS. Conversational Remote Job Entry 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 is a component of OS/VS1 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. Remote Spooling Communications Subsystem 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; IBM added support for Systems Network Architecture, NJE and TCP/IP over several chargeable versions. Network Job Entry is Store and forward networking for transmitting, e.g., card files, jobs, printed output, among peers. The initial versions of NJE for JES2, JES3 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. NETRJS is the protocol developed by the Campus Computing Network at UCLA to deliver batch jobs to the Remote Job Service on their IBM 360 Model 91. This protocol was originally assigned to ARPANETInitial Connection Protocol sockets 71, 73, and 75, and later reassigned to Internet ports 71–74. RJS is a subsystem of OS/360 MVS written by UCLA to support remote batch from card-reader/printer terminals. 200 USER Terminal was a remote batch terminal and protocol 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. Other remote batch terminals using the UT200 protocol included the CDC 731, 732, and 734. Software emulators for the UT200 protocol were also written for a number of minicomputer systems.
