Browse Prior Art Database

Network Remote Job Entry program - NETRJS (RFC0325)

IP.com Disclosure Number: IPCOM000004887D
Original Publication Date: 1972-Apr-06
Included in the Prior Art Database: 2001-Jul-11
Document File: 10 page(s) / 18K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

G. Hicks: AUTHOR

Abstract

Since October 1971 we, at the University of Utah, have had very large compute bound jobs running continuously. These jobs did reduce response time on our PDP-10 for the other Tenex users.

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

Network Working Group G. HICKS Request for Comments: 325 UTAH N.I.C. 9632 APRIL 6, 1972

Network Remote Job Entry Program NETRJS

Since October 1971 we, at the University of Utah, have had very large compute bound jobs running continuously. These jobs did reduce response time on our PDP-10 for the other Tenex users.

Since February we have been submitting jobs to the UCLA 360/91. Our normal mode of operation is diagrammed below.

UTAH NETWORK UCLA

NETRJS : |: RJS FILE SYSTEM

USER To use NETRJS the user creates a job file under the Tenex system. He then requests NETRJS to send that file to the UCLA RJS (Remote Job Service System). Using NETRJS, the user is able to monitor the progress of his job. When RJS notifies the user that his job output is ready to be picked up, the user can request NETRJS to retrieve his output ("printed" or "punched") to a local file.

WHERE TO GET THE SOURCE PROGRAM

A copy of the source program is available by contacting:

Gregory P. Hicks Computer Science Department Merrill Engineering Building 3160 University of Utah Salt Lake City, Utah 84112 (801) 531-8224

Hicks [Page 1]

RFC 325 Network Remote Job Entry Program April 1972

UCLA REMOTE JOB SERVICE

To use the UCLA 360/91 via RJS it is necessary to:

1) Have a valid account at UCLA 2) Have an assigned RJS terminal id.

These can both be obtained from:

Bob Braden UCLA Math Sciences Building 3531 Boelter Hall Los Angeles, Calif. 90024 (213) 825-7518

The remainder of this paper describes the program in greater detail and the steps necessary to run a users program at UCLA.

DESCRIPTION OF THE PROBLEM

There are some jobs that are compute bound for such a long time that they seriously affect response time for interactive users. These are jobs that run from ten hours upward. Another computer was needed to handle these jobs. The UCLA-CCN 360/91 was suggested. The 360/91 is primarily a batch processing type of system where, as a matter of course, it is tuned to jobs that typically run for hours. UCLA does have software to allow jobs to be submitted via remote terminals, either through direct communication lines or through the ARPANET.

HOW AND WHY THE PROGRAM WAS WRITTEN

UCLA's software allowed the remote terminals to have unlimited connect time (i.e. The time the terminal was actually connected to the 360/91) at no charge to the user. The software at UCLA required that each terminal be allotted 2k (2048 S/360 bytes) core for each connection that is open at any one time. Now, since each terminal could have a virtual card reader, virtual line printer and a virtual card punch, this means that one terminal could occupy 10k of core at UCLA. This according to the UCLA systems people would put a heavy load on the system if all the ports were occupied at once. So to alleviate this situation as a matter of design decision it was decide...