Browse Prior Art Database

Surrogate RJS for UCLA-CCN (RFC0490) Disclosure Number: IPCOM000003632D
Original Publication Date: 1973-Mar-06
Included in the Prior Art Database: 2000-Sep-13
Document File: 5 page(s) / 9K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J.R. Pickens: AUTHOR



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

Network Working Group John R. Pickens

RFC # 490 UCSB

NIC # 15355 6 March, 1973

references RFC # 436

RFC # 477


By using UCSB's Network Standard RJS* users can now gain access to

UCLA-CCN's RJS without converting to the UCLA protocol. In addition,

the need to use and create files in an intermediate host is avoided.

For example, TIP users may operate with hot card readers and printers

through UCSB's Remote Job Server and have their jobs execute at UCLA-

CCN. The disadvantages of this scheme as compared to direct connections

to UCLA are as follows:

1. A small amount of additional JCL is required to route jobs from


2. A UCSB batch account must be opened.

3. Turnaround time includes waits in UCSB batch queues.

4. The current implementation requires separate submission and

retrieval steps.

5. The RJS terminal used for submission/retrieval at UCLA-CCN

should not be accessed online until all transfers to/from UCSB

are complete.

Hopefully, these disadvantages are outweighed by the convenient

interface to standard RJS.

Attached is the document which describes this procedure to access



*RFC #436 announces RJS at UCSB and RFC #477 describes its use.




Users of the IBM 360/75 at UCSB may now route jobs to and from

UCLA-CCN (IBM 360/91). Only the reading, printing, and punching are

handled at UCSB while the scheduling, allocation of resources, and

execution are handled at UCLA. The program described below operates by

establishing operator and data connections with UCLA's Remote Job

Service through the ARPA Network and issuing operator commands to

control the submission and retrieval of jobs. Thus it is possible for a

user to run jobs on UCLA's 360/91 almost as if he were at UCLA.



Submission and retrieval are two separate phases which the user must

initiate for each of his UCLA destined jobs. Usually, two UCSB jobs

will be required for the two phases of one UCLA job. Exceptions do

occur using the BATCH options described below and jobs with a guaranteed

fast UCLA turnaround (e.g. QUICKRUN jobs.)

Commands are issued through JCL to the local process and resultant

actions and messages are recorded in the RJS system log on the user's

listing. The user must be aware of the timing of his commands, e.g. a

request to retrie...