rfc740.txt

RFC 相关的技术文档

      Under CCN's job management system, the default destination for
      output is the input source.  Thus, a job submitted under a given
      VRBT 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 user opens his print or punch output channel, RJS immediately
      starts sending job output from the Active Queue, and continues
      until this queue is empty.  Job output in the Deferred Queue, on
      the other hand, must be called for by job name, (via a RESET
      command from the remote operator)  before RJS will send it.  The
      Active/Deferred choice for output from a job is determined by the





Braden                                                         [page 13]

RFC 740                                              RTB 42423 22 Nov 77
NETRJS Protocol



      deferral status of the VRBT when the job is entered; the deferral
      status, which is set to the Active option when the user signs on,
      may be changed by the SET command.

      SET           Allows the remote user to change certain properties
                    of his VRBT for the duration of the current session;
      
                    (a)  May change the default output destination to be
                    another (real or virtual) RJS terminal or the
                    central facility.
      
                    (b)  May change the deferral status of the VRBT.

      DEFER         Moves the print and punch output for a specified job
                    or set of jobs from the Active Queue to the Deferred
                    Queue. If the job's output is in the process of
                    being transmitted over a channel, RJS aborts the
                    channel and saves the current output location before
                    moving the job to the Deferred Queue.  A subsequent
                    RESET command will return it to the Active Queue
                    with an implied Backspace (BSP).

      RESET         Moves specified job(s) from Deferred to Active Queue
                    so they may be sent to user.  A specific list of job
                    names or all jobs can be moved with one RESET
                    command.

      ROUTE         Re-routes output of specified jobs (or all jobs)
                    waiting in the Active and Deferred Queues for the
                    VRBT.  The new destination may be any other RJS
                    terminal or the central facility.

      ABORT         Cancels a job which was successfully submitted and
                    awaiting execution or is currently executing.

   Output Stream Control Commands

      BSP (BACKSPACE)  "Backspaces" output stream within current sysout
                    data set.  Actual amount backspaced depends upon
                    sysout blocking but is roughly equivalent to a page
                    on the line printer.

      CAN (CANCEL)  (a)  On an output channel, CAN causes the rest of
                    the output in the sysout data set currently being
                    transmitted to be omitted. Alternatively, may omit
                    the rest of the sysout data sets for the job
                    currently being transmitted; however, the remaining





Braden                                                         [page 14]

RFC 740                                              RTB 42423 22 Nov 77
NETRJS Protocol



                    system and accounting messages will be sent.
      
                    (b)  On an input channel, CAN causes RJS to ignore
                    the job currently being read.  However, the channel
                    is not aborted as a result, and RJS will continue
                    reading in jobs on the channel.
      
                    (c)  CAN can delete all sysout data sets for
                    specified job(s) waiting in Active or Deferred
                    Queue.

      RST (RESTART) (a)  Restarts a specified output stream at the
                    beginning of the current sysout data set or,
                    optionally, at the beginning of the job.
      
                    (b)  Marks as restarted specified job(s) whose
                    transmission was earlier interrupted by system
                    failure or user action (e.g., DEFER command or
                    aborting the channel).  When RJS transmits these
                    jobs again it will start at the beginning of the
                    partially transmitted sysout data set or,
                    optionally, at the beginning of the job. This
                    function may be applied to jobs in either the Active
                    or the Deferred Queue; however, if the job was in
                    the Deferred Queue then RST also moves it to the
                    Active Queue.  If the job was never transmitted, RST
                    has no effect other than this queue movement.

      REPEAT        Sends additional copies of the output of specified
                    jobs.

      EAM           Echoes the card reader stream back in the printer
                    and/or punch stream.



















Braden                                                         [page 15]

RFC 740                                              RTB 42423 22 Nov 77
NETRJS Protocol



                               APPENDIX E

                        NETRJS TERMINAL OPTIONS

   When a new NETRJS virtual terminal is defined, certain options are
   available; these options are listed below.

      1. Truncated/Compressed Data Format

         A VRBT may use either the truncated data format (default) or
         the compressed format for printer and punch output.  See
         Reference 9 for discussion of the virtues of compression.

      2. Automatic Coldstart Job Resubmission

         If "R" (Restart) is specified in the accounting field on the
         JOB card and if this option is chosen, RJS will automatically
         resubmit the job from the beginning if the server operating
         system should be "coldstarted" before all output from the job
         is returned.  Otherwise, the job will be lost and must be
         resubmitted from the remote terminal in case of a coldstart.

      3. Automatic Output RESTART

         With this option, transmission of printer output which is
         interrupted by a broken connection always starts over at the
         beginning.  Without this option, the output is backspaced
         approximately one page when restarted, unless the user forces
         the output to start over from the beginning with a RESTART
         command when the printer channel is re-opened and before
         printing begins.

      4. Password Protection

         This option allows a password to be supplied when a terminal is
         signed on, preventing unauthorized use of the terminal ID.

      5. Suppression of Punch Separator and Large Letters.

         This option suppresses both separator cards which RJS normally
         puts in front of each punched output deck, and separator pages
         on printed output containing the job name in large block
         letters.  These separators are an operational aid when the
         ouptut is directed to a real printer or punch, but generally
         undesirable for an ARPA user who is saving the output in a file
         for on-line examination.






Braden                                                         [page 16]

RFC 740                                              RTB 42423 22 Nov 77
NETRJS Protocol



                               APPENDIX F

                  Character Translation by CCN Server

   A VRBT declares its character set for job input and output by the
   initial connection socket it chooses. A VRBT can have the ASCII-68,
   the ASCII-63, or the EBCDIC character set.  The ASCII-63 character
   mapping was added to NETRJS at the request of users whose terminals
   are equipped with keyboards like those found on the model 33
   Teletype.

   Since CCN operates an EBCDIC machine, its NETRJS server translates
   ASCII input to EBCDIC and translates printer output back to ASCII.
   The details of this translation are described in the following.

   For ASCII-68, the following rules are used:

      1.  There is one-to-one mapping between the three ASCII characters
          broken vertical bar, tilde, and back slash, which are not in
          EBCDIC, and the three EBCDIC characters vertical bar, not
          sign, and cent sign (respectively), which are not in ASCII.

      2.  The other six ASCII graphics not in EBCDIC are translated on
          input to unused EBCDIC codes, shown in the table below.

      3.  The ASCII control DC4 is mapped to and from the EBCDIC control
          TM.

      4.  The other EBCDIC characters not in ASCII are mapped in the
          printer stream into the ASCII question mark.

   For ASCII-63, the same rules are used except that the ASCII-63 codes
   X'60' and X'7B' - X'7E' are mapped as in the following table.

      EBCDIC              | ASCII-68 VRBT       | ASCII-63 VRBT
      ---------------------------------------------------------------
      vertical bar  X'4F' | vertical bar  X'7C' | open bracket  X'5B'
      not sign      X'5F' | tilde         X'7E' | close bracket X'5D'
      cent sign     X'4A' | back slash    X'5C' | back slash    X'5C'
      underscore    X'6D' | underscore    X'5F' | left arrow    X'5F'
      .             X'71' | up arrow      X'5E' | up arrow      X'5E'
      open bracket  X'AD' | open bracket  X'5B' | .             X'7C'
      close bracket X'BD' | close bracket X'5D' | .             X'7E'
      .             X'8B' | open brace    X'7B' | .             X'7B'
      .             X'9B' | close brace   X'7D' | .             X'7D'
      .             X'79' | accent        X'60' | .             X'60'






Braden                                                         [page 17]

RFC 740                                              RTB 42423 22 Nov 77
NETRJS Protocol



                               APPENDIX G

                               REFERENCES

   1. "Interim NETRJS Specifications", R. T. Braden.  RFC #189:  NIC
   #7133, July 15, 1971.

      This was the basic system programmer's definition document.  The
      proposed changes mentioned on the first page of RFC #189 were
      never implemented, since the DTP then in vogue became obsolete.

   2. "NETRJS Remote Operator Commands", R. T. Braden.  NIC #7182,
   August 9, 1971

      This document together with References 3 and 8 define the remote
      operator (i.e. user) command language for NETRJS, and form the
      basic user documentation for NETRJS at CCN.

   3. "Implementation of a Remote Job Service", V. Martin and T. W.
   Springer.  NIC #7183, July, 1971.

   4. "Remote Job Entry to CCN via UCLA Sigma 7; A scenario", UCLA/CCN.
   NIC #7748, November 15, 1971.

      This document described the first NETRJS user implementation
      available on a server host.  This program is no longer of general
      interest.

   5. "Using Network Remote Job Entry", E. F. Harslem.  RFC #307:  NIC
   #9258, February 24, 1972.

      This document is out of date, but describes generally the Tenex
      NETRJS user process "RJS".

   6. "EBCDIC/ASCII Mapping for Network RJS", R. T. Braden.  RFC #338:
   NIC #9931, May 17, 1972.

      The ASCII-63 mapping described here is no longer correct, but
      CCN's standard ASCII-68/EBCDIC mapping is described correctly.
      This information is accurately described in Appendix F of the
      current document.











Braden                                                         [page 18]

RFC 740                                              RTB 42423 22 Nov 77
NETRJS Protocol



   7. "NETRJT--Remote Job Service Protocol for TIP's", R. T. Braden. RFC
   #283: NIC 38165, December 20, 1971.

      This was an attempt to define an rje protocol to handle TIPs.
      Although NETRJT was never implemented, many of its features are
      incorporated in the current Network standard RJE protocol.

   8. "CCN NETRJS Server Messages to Remote User", R. T. Braden.  NIC
   #20268, November 26, 1973.

   9. "FTP Data Compression", R. T. Braden.  RFC #468:  NIC #14742,
   March 8, 1973.

   10. "Update on NETRJS", R. T. Braden.  RFC #599: NIC #20854, December
   13, 1973.

      This updated reference 1, the current document combines the two.

   11. "Network Remote Job Entry -- NETRJS", G. Hicks.  RFC #325: NIC
   9632, April 6, 1972.

   12. "CCNRJS: Remote Job Entry between Tenex and UCLA-CCN", D.
   Crocker.  NUTS Note 22, [ISI]<DOCUMENTATION>CCNRJS.DOC, March 5,
   1975.

   13. "Remote Job Service at UCSB", M. Krilanovich.  RFC #477: NIC
   #14992, May 23, 1973.

























Braden                                                         [page 19]