Browse Prior Art Database

NETRJS Protocol (RFC0740)

IP.com Disclosure Number: IPCOM000003787D
Original Publication Date: 1977-Nov-22
Included in the Prior Art Database: 2000-Sep-13
Document File: 14 page(s) / 36K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R.T. Braden: AUTHOR

Abstract

NETRJS, a private protocol for remote job entry service, was defined and implemented by the UCLA Campus Computing Network (CCN) for batch job submission to an IBM 360 Model 91. CCN's NETRJS server allows a remote user, or a daemon process working in behalf of a user, to access CCN's RJS ("Remote Job Service") subsystem. RJS provides remote job entry service to real remote batch (card reader/line printer) terminals over direct communications lines as well as to the ARPANET.

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

RFC 740 RTB 42423 22 Nov 77

NETRJS Protocol

Network Working Group R. Braden

Request for Comments: 740 UCLA-CCN

NIC: 42423 22 November 1977

Obsoletes: 189, 599

NETRJS PROTOCOL

A. Introduction

NETRJS, a private protocol for remote job entry service, was defined

and implemented by the UCLA Campus Computing Network (CCN) for batch

job submission to an IBM 360 Model 91. CCN's NETRJS server allows a

remote user, or a daemon process working in behalf of a user, to

access CCN's RJS ("Remote Job Service") subsystem. RJS provides

remote job entry service to real remote batch (card reader/line

printer) terminals over direct communications lines as well as to the

ARPANET.

A batch user at a remote host needs a NETRJS user process to

communicate with the NETRJS server at the batch host. An active

NETRJS user process simulates a "Virtual Remote Batch Terminal", or

"VRBT".

A VRBT may have virtual card readers, printers, and punches. In

addition, every VRBT has a virtual remote operator console. Using a

virtual card reader, a Network user can transmit a stream of card

images comprising one or more batch jobs, complete with job control

language ("JCL"), to the batch server host. The NETRJS server will

cause these jobs to be spooled into the batch system to be executed

according to their priority. NETRJS will automatically return the

print and/or punch output images which are created by these jobs to

the virtual printer and/or card punch at the VRBT from which the job

was submitted. The batch user can wait for his output, or he can

signoff and signon again later to receive it.

To initiate a NETRJS session, the user process must execute a

standard ICP to a fixed socket at the server. The result is to

establish a full-duplex Telnet connection for the virtual remote

operator console, allowing the VRBT to signon to RJS. The virtual

remote operator console can then be used to issue commands to NETRJS

and to receive status, confirmation, and error messages from the

NETRJS Protocol

server. The most important remote operator commands are summarized

in Appendix D.

Different VRBT's are distinguished by 8-character terminal id's,

which are assigned by the server site to individual batch users or

user groups.

B. Connections and Protocols

The protocol uses up to five connections between the user and server

processes. The operator console uses a a full-duplex Telnet

connection. The data transfer streams for the virtual card reader,

printer, and punch each use a separate simplex connection under a

data transfer protocol defined in Appendix A. This document will use

the term "channel" for one of these simplex data transfer connections

and will designate a connection "input" or "output" with reference to

t...