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.
22-629: NJE may refer to: Network Job Entry (NJE), an IBM protocol Nje , a letter of the Cyrillic script Topics referred to by the same term [REDACTED] This disambiguation page lists articles associated with the title NJE . If an internal link led you here, you may wish to change the link to point directly to the intended article. Retrieved from " https://en.wikipedia.org/w/index.php?title=NJE&oldid=1143467318 " Category : Disambiguation pages Hidden categories: Short description
44-805: 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 connections among its nodes. Store and forward Store and forward
66-426: A physical storage , and forwarded to the destination user, i.e., receiver, in accordance with the priority placed upon the message by the originating user and the availability of an outgoing channel . Store and forward switching centers are usually implemented in mobile service stations where the messages that are sent from the sender is first sent to these centers. If the destination address isn't available, then
88-630: 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 . The 200 USER Terminal
110-514: A relay center. A human operator at the center removed the message tape from the receiving machine, read the addressing information, and then sent it toward its destination on appropriate outbound point-to-point teleprinter link. If the outbound link was in use, the operator placed the message in tape in a physical queue, usually consisting of a set of clips or hooks. A major relay center in the mid 1900s might have dozens of inbound and outbound teleprinters, scores of operators, and thousands of messages in
132-500: A user at an interactive terminal. Remote Entry Services ] (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) is, depending on the release, a component of or extra cost product in VM that provides RJE services. The RSCS in
154-414: Is a telecommunications technique in which information is sent to an intermediate station where it is kept and sent at a later time to the final destination or to another intermediate station. The intermediate station, or node in a networking context, verifies the integrity of the message before forwarding it. In general, this technique is used in networks with intermittent connectivity, especially in
176-466: Is 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
198-426: Is different from Wikidata All article disambiguation pages All disambiguation pages Remote job entry#Network Job Entry 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 (LAN). RJE is similar to uux and SSH , except that
220-482: 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) in, e.g., JES2, JES3, VM RSCS. Conversational Remote Job Entry (CRJE) is a component of OS/360 and OS/VS1 that provides job submission, job retrieval and editing for
242-805: 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 . This protocol was originally assigned to ARPANET Initial 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. 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
SECTION 10
#1732872688654264-414: The center stores this message and tries sending it later. This improves the probability of the message to be delivered. In the other case, if the destination is available at that time, then the message is immediately sent. Store and forward networks predate the use of computers. Point-to-point teleprinter equipment was used to send messages which were stored at the receiving end on punched paper tape at
286-498: The deployment of the Internet , computers were connected via a variety of point-to-point techniques, with many smaller computers using dial-up connections . The UUCP store-and-forward protocols allowed a message (typically e-mail) to move across the collection of computers and eventually reach its destination. Late in the 20th century, store and forward techniques evolved into packet switching which replaced it for most purposes. FidoNet
308-505: The free VM/370 only supported BSC; IBM added support for Systems Network Architecture (SNA), NJE and TCP/IP over several chargeable versions. Network Job Entry (NJE) 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 . NETRJS
330-456: 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 supported only Binary Synchronous Communications (BSC), and added the Multi-leaving protocol for BSC programmable work stations; this protocol
352-475: The queues during peak periods. Operators referred to these centers as "torn- tape relay centers", a reference to removing the received message from the inbound teleprinter by tearing the paper tape to separate one message from the next. The U.S. military term for such a center was "Non-Automated Relay Center" (NARC). In 1948, Western Union introduced Plan 55-A , the first automatic electromechanical store and forward message switching system. All message storage
374-410: The wilderness or environments requiring high mobility. It may also be preferable in situations when there are long delays in transmission and error rates are variable and high, or if a direct, end-to-end connection is not available. A store-and-forward switching center is a message switching center in which a message is accepted from the originating user , i.e., sender, when it is offered, held in
396-425: 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. Remote Job Entry (RJE) is also the name of an OS/360 component that provided RJE services. An RJE workstation operator may have complete console control of
418-438: Was an email store-and-forward system for bulletin board systems that peaked at 45,000 systems with millions of users across the world. The system was highly efficient, using the latest file compression and file transfer systems to aggressively drive down the cost of transmission on what was largely a hobby network. The system was later modified to support public messages ( forums ) called EchoMail, which grew to about 8 MB
440-517: 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
462-574: 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. 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
SECTION 20
#1732872688654484-423: Was performed by paper tape punches paired with paper tape readers, with a bin in between. It is very common for an email system using SMTP to accept a message, store it and then forward it on elsewhere. Although fully open mail relays are no longer common, not only does simple server-based forwarding work this way, but also many email filtering and automated electronic mailing lists services. Prior to
#653346