InnovationQ/InnovationQ Plus content will be updated on Sunday, June 25, 10am ET, with new patent and non-patent literature collections. Click here to learn more.
Browse Prior Art Database

Remote Job Entry Protocol (RFC0407)

IP.com Disclosure Number: IPCOM000003580D
Original Publication Date: 1972-Oct-16
Included in the Prior Art Database: 2000-Sep-13
Document File: 19 page(s) / 47K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R.D. Bressler: AUTHOR [+3]

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 7% of the total text.

(Oct. 16, 1972)

RFC 407 NIC 12112

Robert Bressler, MIT-DMCG Obsoletes RFC 360

Richard Guida, MIT-DMCG

Alex McKenzie, BBN-NET


REMOTE Job Entry Protocol

(Oct. 16, 1972)

RFC 407 NIC 12112



Remote job entry is the mechanism whereby a user at one location

causes a batch-processing job to be run at some other location. This

protocol specifies the Network standard procedures for such a user to

communicate over the Network with a remote batch-processing server,

causing that server to retrieve a job-input file, process the job,

and deliver the job's output file(s) to a remote location. The

protocol uses a TELNET connection (to a special standardized logger,

not socket 1) for all control communication between the user and the

server RJE processes. The server-site then uses the File Transfer

Protocol to retrieve the job-input file and to deliver the output


There are two types of users: direct users (persons) and user

processes. The direct user communicates from an interactive terminal

attached to a TIP or any host. This user may cause the input and/or

output to be retrieved/sent on a specific socket at the specified

host (such as for card readers or printers on a TIP), or the user may

have the files transferred by file-id using File Transfer Protocol.

The other type of user is a RJE User-process in one remote host

communicating with the RJE Server-process in another host. This type

of user ultimately receives its instructions from a human user, but

through some unspecified indirect means. The command and response

streams of this protocol are designed to be readily used and

interpreted by both the human user and the user process.

A particular user site may choose to establish the TELNET control

connection for each logical job or may leave the control connection

open for extended periods. If the control connection is left open,

then multiple job-files may be directed to be retrieved or optionally

(to servers that are able to determine the end of one logical job by

the input stream and form several jobs out of one input file) one

continuous retrieval may be done (as from a TIP card reader). This

then forms a "hot" card reader to a particular server with the TELNET

connection serving as a "job monitor". Since the output is always

transferred job at a time per connection to the output socket, the

output from this "hot" reader would appear when ready as if to a

"hot" printer. Another possibility for more complex hosts is to

attach an RJE User-process to a card reader and take ins...