Remote Job Service at UCSB
RFC 477

Document Type RFC - Unknown (May 1973; No errata)
Last updated 2013-03-02
Stream Legacy
Formats plain text pdf html bibtex
Stream Legacy state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 477 (Unknown)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                     M. Krilanovich
Request for Comments: 477                                           UCSB
NIC: 14922                                                   23 May 1973
References: RFCs 354, 407,
            NIC 16306

                       Remote Job Service at UCSB


   This RFC is the follow-on document to RFC #436, which briefly
   described UCSB'S RJS.  This document restates the essence of the
   official RJE protocol (RFC #407), and documents in detail UCSB's
   implementation of it.

   The program described here is available under socket 5 at UCSB, and
   supports a subset of the official protocol.  Specifically, no checks
   are made for RJE control cards in the input file, jobs may not be
   batched in the input file, only output file dispositions of discard
   and transmit-and-discard are implemented, no restart markers are sent
   on output in FTP blocked mode, and several of the commands are not
   implemented.  There are also other ways in which RJS is known to be
   less than ideal.  For example, whenever any error is detected while
   processing a job, such as the output's destination host being dead,
   the job is abandoned, and any further output deleted.  A re-write of
   RJS is scheduled for the near future (in about six months), and many
   of these deficiencies will be corrected at that time.   (Any
   suggestions for further improvements are more than welcome, and may
   be made through the Journal to MCK, by mail to the author at the UCSB
   Computer Center, or by telephone at (8O5) 961-3454.)

   In addition to the deviations from the protocol stated above, several
   modifications have been made to increase user convience.
   Specifically, the INACCT, OUTACCT, and ACCT commands have been added
   to accommodate users of TENEX and other systems requiring an account
   number, OUTPATH has been added as a synonym for OUT and INUSER for
   INID, and the BYE command does not cause an ABORT.  Also, in
   recognition of the fact that the official protocol is biased heavily
   toward use by programs, and is therefore rather cumbersome for human
   users, an alternate, optional, command syntax has been provided.  An
   attempt was made to make this alternate syntax, called 'local
   syntax', as 'natural' as possible to a human user.  It also provides
   some features not available with the standard syntax.

Krilanovich                                                     [Page 1]
RFC 477                Remote Job Service at UCSB            23 May 1973

Service Provided

   The UCSB Computer Center operates an IBM 360/75 and runs OS MVT
   release 21.0 and HASP.  All batch jobs at UCSB enter the system
   through HASP, and therefore RJS acts as an interface between the user
   and HASP.  RJS's function is to provide the user with a HASP virtual
   RJE terminal, consisting of card reader, card punch, line printer and
   operator's console, and to manage the first three of these for the
   user in response to commands issued by him.  By virtue of the fact
   that RJS maintains the correspondence between a particular user and
   the HASP RJE terminal owned by him, the user may issue commands to
   alter the status of those jobs submitted by him through his RJE
   terminal.  This may be done even if the user has logged out of RJS
   and back in again, possibly from another site.

   The sequence of events involved in using RJS are as follows.  First,
   the user logs in, specifying a user name, password, and account
   number.  In addition to indicating how subsequent use of RJS is to be
   billed, this accounting information identifies the owner of a
   particular RJE terminal.  That is, the association between user name
   and HASP virtual RJE terminal is unique, and only one individual is
   allowed logged in under a given user name at a time.

   At present, billing within RJS is not implemented, and therefore the
   login account number is completely arbitrary, and user name and
   password are relatively so.  The first time a given user name is
   used, any password may be chosen; thereafter, as long as the user
   name is known to RJS, the same password must be used.  A user name
   remains known to RJS while he is logged in, and when he is not, as
   long as he owns at least one job known to PJS.  Otherwise, the user
   name is discarded.

   After a user is logged in, he specifies input and output file
   information and requests input retrieval be initiated.  He may then
   log out or not as he wishes; specifically he is not required to
   remain logged in during source file retrieval.  A job can completed
   abnormally at any stage of processing, or normally, after storage of
   the last of its output.  In any case, the circumstances of the final
   disposition of the job are displayed to the user immediately if he is
   logged in, saved for a period after its completion, and are available
   to him on request the next time he logs in.  This status information
Show full document text