Browse Prior Art Database

Network Specifications for Remote Job Entry and Remote Job Output Retrieval at UCSB (RFC0105) Disclosure Number: IPCOM000001856D
Original Publication Date: 1971-Mar-01
Included in the Prior Art Database: 2019-Feb-10
Document File: 9 page(s) / 13K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J.E. White: AUTHOR

Related Documents

10.17487/RFC0105: DOI

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

Network Working Group James E. White Request for Comments: 105 Computer Research Lab. Category: Informational University of California Santa Barbara, California March 1971

Network Specifications for Remote Job Entry and Remote Job Output Retrieval at UCSB

In the discussions that follow, ’byte’ means 8 bits, with those eight bits numbered 0-7 from left to right.

I - Remote Job Entry (RJE)

UCSB will accept input of pseudo card files for batch processing at socket number x’200’, site 3. Network users should obtain an account number from the UCSB Computer Center; account #1025, programmer names ’UCLA’, ’SRI’, ’UTAH’, etc. may be used during checkout. The 360/75 runs under OS MVT and HASP. Users submit jobs to HASP for scheduling and subsequent execution by OS through an intermediary process hereafter called RJE which is addressed as socket number x’200’ and can be invoked through the Logger. This section is intended to provide programmers with the information necessary to communicate with RJE; the is assumed familiar with the batch services offered by the Computer Center, and with its job control language (JCL) requirements.

RJE conducts all Network transactions through the NCP, which operates under the Host-Host protocol of 3 August 1970. It expects the first message it receives to be Type 0, discards the first eight bits (the message type) assuming them to be zeros, and thereafter for the life of the connection takes no notice of IMP-message boundaries.

I.A - Logging into RJE

To submit one or more jobs for batch processing, the Network user must establish a simplex connection with RJE. RJE is core resident only while such a simplex connection is established (i.e., while a user is transmitting a file). At all other times, it resides on direct-access storage and must be invoked through the Logger. A login sequence can always be initiated by requesting connection to socket x’200’. RJE does not serve multiple users simultaneously. This if a connection request is made to that socket while RJE is in use, the NCP will queue the request. When the current file transmission is

White [Page 1]

RFC 105 RJE at UCSB March 1971

complete, RJE will listen for and accept the next request (if any) in its queue; if no requests are queued for it, it will terminate execution, releasing the main storage it occupied. At times when RJE is not in core, the Logger listens on socket x’200’, and will reject the first call it receives, read RJE into core, and dispatch it. RJE will then list on that socket. Thus to initiate a login sequence, the user requests connection to socket x’200’. If accepted, he is in contact with RJE. If rejected, he should reissue the connection request; when accepted, he will be connected to RJE. A second rejection would indicate that the NCP’s resources were exhausted. Once the connection has been established, RJE will consider the user logged in.

To prevent RJE from being monopolized by a single user, provision is made within the software for ter...