Remote job entry

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]

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.

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]

• Job control
• Job stream
• Houston Automatic Spooling Priority (HASP)[2]
• Asymmetric Multiprocessing System, 360A-CX-15X,[18] previously known as Attached Support Processor (ASP)
• Remote Spooling Communications Subsystem (RSCS)[8]

• Barr/RJE Host Definition Guide
• cq-comm.com - CQ Communications CQEE