Specifications changes for OLS, RJE/RJOR, and SMFS
A UCSB notice revising specifications for OLS, remote job services, and a file system.
White, J.E., "Specifications changes for OLS, RJE/RJOR, and SMFS", RFC 217, DOI 10.17487/RFC0217, September 1971, <https://www.rfc-editor.org/info/rfc217>.
@misc{rfc217,
series = {Request for Comments},
number = 217,
howpublished = {RFC 217},
publisher = {RFC Editor},
doi = {10.17487/RFC0217},
url = {https://www.rfc-editor.org/info/rfc217},
author = {J.E. White},
title = {{Specifications changes for OLS, RJE/RJOR, and SMFS}},
pagetotal = 2,
year = 1971,
month = sep,
} RFC text
RFC 217 8 September 71 NIC 7547 James E. White Categories: G.3 Computer Research Lab. Updates: RFC 105, RFC 122 Univ. of California Obsoletes: RFC 74 Santa Barbara Specification Changes for OLS, RJE/RJOR, and SMFS The following documents are hereby revised: (1) 'Specifications for Network Use of the UCSB On-Line System [16 October 70, RFC 74, NIC 5417], (2) 'Network Specifications for Remote Job Entry and Remote Job Output Retrieval at UCSB' [22 March 71, RFC 105, NIC 5775], and (3) 'Network Specifications for UCSB's Simple- Minded File System' [26 April 71, RFC 122, NIC 5834]. Revisions are as follows: (1) As far as can be determined, no Network site has written code to interface to the UCSB software documented in RFC 74 last October. Accordingly, UCSB has terminated support for that software, and hence RFC 74 is obsolete. (2) In accordance with subsequent Host-Host protocol changes, the notion of 'message type' has been dropped from the specifications for RJE and RJOR, RFC 105. RJE/RJOR no longer send, nor expect to receive 8 bits of zeros as the first byte trans- mitted over a connection. (3) In accordance with Document 2, RJE and RJOR now employ a standard ICP to create a full duplex connection to the user. Accordingly, RJE and RJOR listen on sockets x'201' and x'301', respectively (rather than on x'200' and x'300' as before). As documented in RFC 105, RJE required only a simplex connection to the user. A full duplex connection is now supported, but no data is transmitted to the user over the NIC 7547 added simplex connection. RJOR now also supports a full duplex connection. However, if RJOR is required to call the user back when a requested job's output is ready, it still does so employing a simplex connection to the user's receive socket. (4) RJE/RJOR and SMFS specify a byte size of eight for their connection to the user's receive socket. The user may choose the byte size for the other simplex connection to suit himself; any valid byte size is acceptable to UCSB. [ This RFC was put into machine readable form for entry ] [ into the online RFC archives by BBN Corp. under the ] [ direction of Alex McKenzie. 12/96 ]
ISO Plain Language
On this page
§1The Three UCSB Specifications
RFC 217 revises specifications for the UCSB On-Line System (OLS), Remote Job Entry (RJE) and Remote Job Output Retrieval (RJOR), and the Simple-Minded File System (SMFS). The memo says that no network site was known to have written code to interface with the OLS software described in RFC 74, so UCSB ended support for it and declared RFC 74 obsolete.
The changes to RJE and RJOR apply to the specifications in RFC 105. The byte-size change also applies to SMFS, described in RFC 122.
The note updates three UCSB service specifications. It says the OLS software had no known network interface implementation, so its earlier specification was obsolete.
§2Changes to RJE and RJOR Connections
Following changes to the Host-Host protocol, RJE and RJOR no longer send or expect 8 bits of zeros as the first byte on a connection. The message-type concept is removed from their specifications.
RJE and RJOR now use a standard Initial Connection Protocol to create a full-duplex connection to the user. They listen on sockets x'201' and x'301', respectively, instead of x'200' and x'300'. RJOR still uses a simplex connection to the user's receive socket when it calls the user back because a requested job's output is ready.
RJE and RJOR stop sending an initial zero byte and use new socket numbers. They use the standard connection procedure, while RJOR still sends its callback output over a one-way connection.
§4Byte Sizes for Service Connections
RJE/RJOR and SMFS specify a byte size of 8 for the connection to the user's receive socket. The user may choose the byte size for the other simplex connection, and UCSB accepts any valid byte size there.
The connection to the user's receive socket uses 8-bit bytes. For the other one-way connection, the user can choose any valid byte size.