Browse Prior Art Database

Update on NETRJS (RFC0599) Disclosure Number: IPCOM000003672D
Original Publication Date: 1973-Dec-01
Included in the Prior Art Database: 2019-Feb-12
Document File: 9 page(s) / 11K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R.T. Braden: AUTHOR

Related Documents

10.17487/RFC0599: DOI

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 23% of the total text.

13 Dec 73 NIC 20854, RFC 599: Update on NETRJS

Network Working Group Robert T. Braden NIC #20854 UCLA/CCN RFC #599 December 13, 1973



In July 1971, CCN published RFC #189 defining NETRJS, a private protocol for remote job entry. NETRJS provides a Network interface to CCN’s rje program called RJS (Remote Job Service).(3) As noted in an earlier RFC,(6) "RJS" is the proper name of a software package existing ony at CCN, not a generic term for rje.

For over two years now, CCN has provided rje service to the Network using NETRJS. We know of the following distinct implementations of NETRJS user porgrams:

RAND OS/MVT on 370/158 (originally on 360/65)

UCLA-NMC SEX on Sigma 7

Illinois ANTS on PDP-11

Utah Tenex on PDP-10


Harvard DEC system on PDP-10

UCSB OS/MVT on 360/75

ISI,BBN,NIC,I4 Tenex on PDP-10

We apologize to anyone slighted by omission from this list. Writing a new user process for NETRJS has proved to be a modest and straightforward task.

During the month of October, 1973, CCN processed 1373 batch jobs via NETRJS. The complete statistics are:

1,373 Jobs submitted

1,105 Jobs "printed"

0 Jobs "punched"

Braden [page 1]

13 Dec 73 NIC 20854, RFC 599: Update on NETRJS

49,400 Cards "read"

822,900 Lines "printed"

18,907 Pages "printed"

393.6 Connect hours

The average job submitted was 360 lines ("cards"), and returned 745 lines on 17.1 pages. These figures are fairly typical.


At the request of the Socket Czar, Jon Postel, (see RFC #433) we intend to move the NETRJS ICP sockets from 11, 13, and 15 to 71, 73, and 75, respectively. At present, NETRJS is available from either socket subspace, so system programmers responsible for maintaining NETRJS user processes can switch over at their leisure. We plan to "decommit" sockets 11, 13, and 15 on July 1, 1974.

Those hosts which access NETRJS via socket 1 are unaffected.


Last Fall, CCN installed a new implementation of its NETRJS server. An internal NETRJS rewrite was necessitated by other system changes and was timed to coincide with installation on September 5 of the "last release" of OS/360, Release 21.7. The new version of NETRJS contains a number of internal improvements over the original version written two years ago. There are also a few external differences, as follows:

1. No More Squish

The long-standing "squish" problem in NETRJS has been fixed. This problem arose because of the "squishiness" of Network data transfer, i.e. the variable delay between originator and receiver processes due to NCP buffering. The result was that a short print output file could be "transmitted" by RJS, dequeued, and discarded at CCN before the first message had actually reached the remote host. If the remote host crashed or the user tried to cancel (and save) the output stream, it was too late; the output was lost in the "squish". We were careless about this in the first version. Now NETRJS awaits the RFNM from the end-of-data mark be...