Harvard's network RJE
RFC 499

Document Type RFC - Unknown (April 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 499 (Unknown)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         B. Reussow
Request for Comments: 499    Center for Research in Computing Technology
NIC: 15716                                            Harvard University
                                                            April 1 1973

                         HARVARD'S NETWORK RJE

Section I

   RJE was designed to provide network users with the facility of
   submitting jobs to remote servers via the ARPA net and retrieving
   results using Harvard's PDP-10.

   In order to be an expert in the use of the RJE program from a remote
   host, the user must be familiar with the FTP commands and usage.  At
   present RJE is only implemented for UCLA.  Accordingly, all examples
   will deal with the UCLA installation.  Arrangements for a password
   and a job ID must be made at UCLA before usage is to begin.  If you
   are interested, we will see to it that an account is made up for you.
   People at other sites should deal directly with UCLA to get an
   account.

Section II

                         HOW TO USE RJE AT HARVARD

   Start the program by taping R RJE<CR> at monitor level.  RJE will
   respond with a "!".

   Then type "RJE UCL<CR> to make the TELNET connection.  The TELNET
   connection is used for transfer of commands to UCLA and error
   messages from UCLA to the user of RJE.  It is important to realize
   that, in using RJE, one is talking to two systems; the local system
   (HARV-10) and the remote host where the job will actually be run.
   Therefore, there are two command processors, one local and one
   foreign.

                  COMMANDS TO THE LOCAL (HARVARD) PROCESS

   All commands to the local process begin with a *.

   *READ LDEV:FILENAME.EXTENSION<CR>

   Reads the specified file, which contains all job cards, JCL, program
   and data, formats it for RJS at UCLA and ships it over a data
   connection.  When using the data connection, ASCII files are
   translated into EBCDIC, the UCLA end of the connection.  After
   transfer is completed the file is immediately spooled for processing.

B. Reussow                                                      [Page 1]
RFC 499                  HARVARD'S NETWORK RJE              April 1 1973

   *PRINT LDEV:FILENAME.EXTENSION<CR>

   Gets the next print file from UCLA's 91 and reformats the print file
   for a PDP-10 line printer.  Write the file to the user's specified
   logical device with the specified FILENAME.EXTENSION.  FILENAME is up
   to 6 characters in length and EXTENSION is up to 3 characters in
   length.

   *QUIT<CR>

   Tear down all connections used by RJE and return to monitor level.

                      COMMANDS TO THE REMOTE PROCESS
                            (UCLA RJS COMMANDS)

   Commands to the remote process have no special character preceding a
   command.  For a explanation of the command arguments, ask Terry Sack
   for the document named, RJS OPERATOR COMMANDS FOR REMOTE TERMINALS.

   Terminal Control and Information Command
   -------- ------- --- ----------- -------

   SIGNON              First command of a session identifies VRBT
                       (virtual remote batch terminal) by giving its
                       terminal ID.  For UCLA, Harvard's terminal ID is
                       NETHARV.

   SIGNOFF             Last command of a session; RJS waits for any data
                       transfer in progress to complete and then closes
                       all connections.

   STATUS              Outputs on the local user's terminal a complete
                       list, or a summary, of all jobs in the system for
                       this VRBT, with an indication of their
                       progressing status in the Model 91.

   ALERT               Outputs on the user's terminal any special
                       "Alert" message from the CCN computer operator.
                       The Alert message is also automatically sent when
                       the user does a SIGNON, or whenever the message
                       changes.

   MSG                 Sends a message to CCN computer operator or to
                       any other RJS terminal (real or virtual).  A
                       message from the computer operator or another RJS
                       terminal will automatically appear on the user's
                       terminal.

B. Reussow                                                      [Page 2]
RFC 499                  HARVARD'S NETWORK RJE              April 1 1973

   Job Control and Routing Commands
   --- ------- --- ------- --------

   Under CCN's job management system, the default destination for output
   is the input source.  Thus, a job submitted under a given VRET will
   be returned to that VRBT (i.e., the same terminal ID), unless the
   user's JCL overrides the default destination.

   RJS places print and punch output destined for a particular remote
   terminal into either an Active Queue or a Deferred Queue.  When the
Show full document text