Using network Remote Job Entry
RFC 307

Document Type RFC - Unknown (February 1972; No errata)
Last updated 2013-03-02
Stream Legacy
Formats plain text pdf htmlized bibtex
Stream Legacy state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 307 (Unknown)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         E. Harslem
Request for Comment: 307                                            Rand
NIC: 9258                                              February 24, 1972
References: 113, 189



   As has been mentioned in previous RFCs and at previous Network
   meetings various groups at Rand have been doing RJE to remote Network
   sites (UCBS and UCLA) for over a year.  Until recently all this work
   has been done from our IBM 360/65 which is only a Network using host
   (not a server).  Recently our PDP-10 has come onto the Network as
   both a user and server host.  We now have, as well, a program on the
   PDP-10 allowing access to the Remote Job Service (RJS) at UCLA.  Our
   normal mode of operation is diagramed below.

                    RAND                                     UCLA
               ________________                        ________________
              |    PDP-10      |                      |     360/91     |
    ______    |                |                      |                |
   |      |   |   __________   |                      |   __________   |
   |File  |   |  | RJS      |  |                      |  |          |  |
   |System|___|__| Access   |__|___/\/\ Network /\____|__|    RJS   |  |
   |      |   |  | Program  |  |       \/     \/      |  |          |  |
   |______|   |  |__________|  |                      |  |__________|  |
              |       |        |                      |                |
              |       |        |                      |                |
              |_______|________|                      |________________|

   To use RJS the user creates a job source "deck" in the Rand File
   system.  He then instructs the RJS Access Program (RJSAP) to send
   that file (job) to RJS.  (Sample session below.)  He can then monitor
   the status of his job via RJSAP (and hence RJS) and ask that RJSAP
   retrieve his print output to a local file, (or directly to his
   console, the line printer or whatever).

   Recently, several people at other Network sites have expressed an
   interest in using RJS.  However, they are located at a minimal Host
   or at a host not providing RJS access.  Since the Rand PDP-10 is a
   Network server, these people can solve their access problem by
   logging onto the Rand PDP-10, using Telnet, and running the RJSAP
   themselves.  The remainder of this RFC describe the steps necessary

Harslem                                                         [Page 1]
RFC 307              Using Network Remote Job Entry        February 1972

   to run that program.

The Rand PDP-10

   The Rand PDP-10 operates under the Tenex operating system.  Thus,
   some understanding of the Tenex Executive is required.  The necessary
   documents can be obtained from the developers of Tenex:

                    Bolt, Beranek and Newman, Inc.
                    50 Moulton Street
                    Cambridge, Massachusetts 02138
                    (617) 491-1850

   Secondly, it is necessary to establish an account on the Rand PDP-10.
   This can be done through:

                    Rod Fredrickson
                    The Rand Corporation
                    1700 Main Street
                    Santa Monica, California 90406
                    (213) 393-0411

UCLA Remote Job Service

   To use the UCLA IBM 360/91 via RJS it is necessary to:

      1) have an account at UCLA
      2) have an assigned RJS terminal ID.

   These can both be obtained from

                    Bob Braden
                    Math Sciences Building
                    3531 Boelter Hall
                    Los Angeles, Calif.  90024
                    (213) 825-7518

The RJS Access Program (RJSAP)

   A sample session using RJSAP is attached below.  The RJSAP is started
   by typing "RJS<return>" to the Tenex executive.  The program will
   then initialize and check (via your login information) to see if you
   are a user recorded in its tables.  This is done to assure you have a
   valid RJS terminal ID.  If your ID is not found, the program will
   terminate with appropriate message.

Harslem                                                         [Page 2]
RFC 307              Using Network Remote Job Entry        February 1972

   If your ID is found, RJSAP will attempt to connect to RJS.  If UCLA
   is down, a message to that effect will appear and the program will
   terminate.  If UCLA is up, RJSAP will connect you to RJS and sign-on
   your terminal ID (see RFC 189).  RJSAP will respond "YOU ARE

   At this point RJS will acknowledge your signon and print out messages
   regarding system status.

   The programs (RJSAP and RJS) are now ready to perform RJE functions.
   All commands are initially interpreted by RJSAP.  They are listed and
Show full document text