rfc325.txt

著名的RFC文档,其中有一些文档是已经翻译成中文的的.

        his job (for output) from the beginning.  The format of the
        restart command is:

                  RESTART (device or jobname[,JOB])

        There will be a confirming message that specifies the action
        taken.

   STATUS SYSTEM - this will tell the operator what remote terminals are
        using the RJS System now.  In addition, status system includes
        the status of all jobs currently in the system that have been
        submitted from the user's terminal.  The only abbreviation
        allowed is for system (SYS).

   STATUS JOB - will tell the operator what output if any is waiting to
        be returned to his terminal.  It will also tell him if there are
        any jobs being  executed.  This command should be done each time
        the user signs onto RJS.  Abbreviation allowed: J for JOB.

THE NETRJS CONTROL CHARACTERS

   The escape character for NETRJS is the control character ^S.   This
   was specified so that remote sites (and users!) could use the program
   and still retain their sanity  and  that of telnet.  This will always



Hicks                                                           [Page 5]

RFC 325             Network Remote Job Entry Program          April 1972


   return you to the command level of NETRJS.  This is good if you think
   that you've made a mistake (eg...  when writing the program, etc...)
   and you want to abort a send.  In other words, do not do ^S and think
   that you can continue where you left off in a send or retrieval.  It
   won't work at this time.  In a later implementation, it may, with the
   provision of stopping (and then continuing, if you wish) the printer,
   punch, or reader.


EVERYTHING UNDERLINED SHOULD BE TYPED IN BY USER

   SAMPLE SESSION USING NETRJS

   UTAH TENEX 1.28.03, JANUARY 31, 1972 EXPC 1.33.3
   [1] (USER) HICKS
              -----
   (PASSWORD)
              -----
   (ACCOUNT #) 500
               ---
    JOB 6 ON TTY21 1-APR-72 10:12
    RUN NETRJS
    ----------

   <<UCLA91 IS UP.>>
   NRJ8761 NETWORK REMOTE JOB SERVICE READY
   RJS7501 TERMINAL NETUTAH1 HAS SIGNED ONTO RJS
   RJS6601 NO ALERTS OUTSTANDING
   (^S)
   ----
   <<?
     -
   RETRIEVE.OUTPUT.FROM
   SEND.FILE.NAMED
   DISCONNECT

   QUIT
   RESTART
   TIME.NOW.IS
   LOGOUT
   DDT
   UCLA91
   SYSTAT
     SEND.FILE.NAMED TEST.F4;1
     ---             ---------
   ?
   -
   5 RECORDS TRANSFERRED.



Hicks                                                           [Page 6]

RFC 325             Network Remote Job Entry Program          April 1972


   FILE TEST.F4;1 HAS BEEN SENT.
   12 RECORDS TRANSFERRED.
   MORE FILES TO BE SENT? (Y OR N) Y
                                   -
   INPUT FILE: TEST.DAT;1
   ?
   -
   40 RECORDS TRANSFERRED.

   FILE TEST.DAT;1 HAS BEEN SENT.
   100 RECORDS TRANSFERRED.
   MORE FILES TO BE SENT? (Y OR N) N
                                   -
   << >>
     -
   RJS534I JOB NETUTAH1 ACCEPTED BY RJS - 0000112 CARDS READ
   <<SYSTAT >>
     --
   RJS802I TERMINAL NETUTAH1 HAS 1 SPL JOB(S)
   RJS800I TERMINAL GSM ACTIVE AN LINE1
   RJS909I PUNCH REROUTE = ENGR
   RJS800I TERMINAL NETILL ACTIVE ON LINE8
   RJS800I TERMINAL NETUTAH1 ACTIVE ON LINE11

   STATUS JOB
   ----------
   RJS810I TERMINAL NETUTAH1 HAS THE FOLLOWING JOBS ON RJS
   RJS812I NETUTAH1 SPL(A) 001
   RJS481I PRINT OUTPUT FOR JOB NETUTAH1 NOW AVAILABLE, PRTY=030, IMMED
   RJS481I PUNCH OUTPUT FOR JOB NETUTAH1 NOW AVAILABLE, PRTY=060, IMMED

   <<RETRIEVE.OUTPUT.FROM PRINTER
     ---                  -------
   GOING TO FILE NAMED TEST.PRT [NEW FILE]
                       --------           -
   RJS783I TERMINAL STATUS CHANGED
   ?
   -
   99 RECORDS TRANSFERRED.
   STATUS JOB
   ------ ---
   RJS809I TERMINAL NETUTAH1 HAS THE FOLLOWING JOBS IN RJS
   RJS800I NETUTAH1 PRT(A)   060
   ?
   -
   169 RECORDS TRANSFERRED.

   YOUR OUTPUT IS HERE.



Hicks                                                           [Page 7]

RFC 325             Network Remote Job Entry Program          April 1972


   217 RECORDS AND 16119 BYTES TRANSFERRED.>>

   <<RETRIEVE.OUTPUT.FROM PUNCH
     ---                  -----
   WILL THIS BE AN OBJECT DECK (O)
   OR AN ASCII FILE (A)?? ASCII
                          -
   GOING TO FILE NAMED TEST.PUJ [NEW FILE]
                       --------           -
   RJS783I TERMINAL STATUS CHANGED


   YOUR OUTPUT IS HERE.
   17 RECORDS AND 1222 BYTES TRANSFERRED.>>
   SIGNOFF
   -------
   RJS751I TERMINAL NETUTAH1 HAS REQUESTED SIGNOFF FROM RJS
   NRJ898I SIGNOFF ACCEPTED
   @


WHEN THE OPERATOR'S CONSOLE IS ACTIVE

   The NETRJS prompt character is the  "<<".  This indicates  that  the
   program is  ready to accept commands.  When the ">>" is printed the
   console is in the remote  mode.  Anything that is typed at this point
   goes directly to RJS.  When sending or retrieving files the operator
   may communicate with RJS if he wishes even though the ">>" has not
   yet been output.  The operator's console is in the remote mode at all
   times except when NETRJS is at the command level.

EDITING ON THE NETWORK

   There are two control characters that allow you to make mistakes and
   then to correct them.  One is control-x.  This has the action of
   notifying RJS to ignore your last line.  This is echoed by "___".
   The other is control-h.  This will cause UCLA to ignore the character
   immediately preceding it.  This is echoed by "_" and there will be no
   echo of the deleted character.

TABS AND OTHER NEAT GOODIES

   Most people writing programs under TENEX like to use the tab stops
   provided on the teletype.  So we needed a nice number to set them to.
   When running NETRJS the user should be aware that the tab stops are
   set every 8 columns.  In other words, a line that starts with a tab
   will find the first character in (card) column 8.  The program
   accepts almost any type of <eol> indicator eg: TENEX eol and cr lf.



Hicks                                                           [Page 8]

RFC 325             Network Remote Job Entry Program          April 1972


   (This last in any order, by the way.)  It also deletes blank lines
   and since the user may wish to use a program written in a language
   such as Fortran to generate data, the program also ignores null (00)
   characters.  When retrieving a file of data, for an <eol> the program
   uses <cr> and <lf>.  This is to keep the output compatible with
   text-editors such as QED, DED, SOS and etc.

FILE FORMAT

   When sending a file to UCLA there is a line limit of 80 characters.
   This is a design restriction in that jobs going to the OS/360 be no
   longer than 80 characters/line.  (Remember, IBM is still card
   oriented...) The operator will get a nasty (well...  semi-nasty
   anyway) message if NETRJS finds a line that is longer than that.  For
   an output file, there is no limit to the length of a line other than
   that imposed by the programming language used up to 255 characters.
   When the user retrieves a punch file he may find that there are a few
   extra lines thrown in...  This is done by UCLA to allow the user to
   identify his deck when it is punched on the card punch.


         [ This RFC was put into machine readable form for entry ]
             [ into the online RFC archives by Elias Lofgren ]




























Hicks                                                           [Page 9]