Google
 

Trailing-Edge - PDP-10 Archives - de-10-omona-v-mc9 - beware.63a
There is 1 other file named beware.63a in the archive. Click here to see a list.


                  BEWARE FILE FOR 6.03A DISTRIBUTION





                             Revision:  1

                          Date: 20 Dec 1978

























COPYRIGHT (C) 1977,1978 BY
DIGITAL EQUIPMENT CORPORATION, MAYNARD, MASS.


THIS SOFTWARE IS FURNISHED UNDER A LICENSE AND MAY BE USED AND  COPIED
ONLY  IN  ACCORDANCE  WITH  THE  TERMS  OF  SUCH  LICENSE AND WITH THE
INCLUSION OF THE ABOVE COPYRIGHT NOTICE.  THIS SOFTWARE OR  ANY  OTHER
COPIES  THEREOF MAY NOT BE PROVIDED OR OTHERWISE MADE AVAILABLE TO ANY
OTHER PERSON.  NO TITLE TO AND OWNERSHIP OF  THE  SOFTWARE  IS  HEREBY
TRANSFERRED.

THE INFORMATION IN THIS SOFTWARE IS SUBJECT TO CHANGE  WITHOUT  NOTICE
AND  SHOULD  NOT  BE  CONSTRUED  AS  A COMMITMENT BY DIGITAL EQUIPMENT
CORPORATION.

DIGITAL ASSUMES NO RESPONSIBILITY FOR THE USE OR  RELIABILITY  OF  ITS
SOFTWARE ON EQUIPMENT WHICH IS NOT SUPPLIED BY DIGITAL.
BEWARE FILE FOR 603A DISTRIBUTION                               Page 2
Table of Contents


                           TABLE OF CONTENTS


     This file contains the following information concerning the  603A
monitor release:


     1.0  List of files included in 603A release


     2.0  Installation instructions for 603A


     3.0  Warnings of known deficiencies in 603A


     4.0  Observable differences between 603 and 603A


     5.0  Dependencies


     6.0  Results of running 603A on our in-house systems
          and at Field Test sites


     7.0  Unbundled Software


          1)   Virtual Memory
          2)   DC44 Support
          3)   DAS78 Support
          4)   XTCSER Support
          5)   TSK to TSK Communications Support
          6)   Networks
BEWARE FILE FOR 603A DISTRIBUTION                               Page 3
Purpose/Scope


0.0  PURPOSE/SCOPE OF 603A

603A is a maintenance release with many bug fixes, and has three LIR's
incorporated:   the  KLINIK  LIR, the SCHEDULER LIR, and the 1091 LIR.
These changes are documented in 603A.MCO.

The  SCHEDULER  LIR  provides  a  new  class  scheduler  and  includes
performance  improvements  to  the  round  robin scheduler in the 6.03
release of the monitor.   The  new  class  scheduler  is  a  pie-slice
scheduler  with two levels of allocation, in contrast to the scheduler
in 6.03 that was an exponential-decay scheduler with only one level of
allocation.   The changes to the round robin scheduler reduce overhead
and enhance scheduler performance, especially on small to medium sized
systems.

Also included in the LIR is a performance  evaluation  package  and  a
load  simulation package.  The performance evaluation package consists
of a data collection program and several data  reduction  and  display
programs.   The  load  simulation package consists of several programs
that can be used to load  the  system  for  scheduler  testing  and  a
controller  that  starts  and stops the load simulation programs.  The
documentation files LODTST.MEM and PERFOR.MEM are included  with  this
release.   The  remainder  of the performance installation package and
the load simulation package will be included  in  a  forthcoming  CUSP
tape.

Use of the performance evaluation and  load  simulation  packages  can
help the system administrator tune the scheduler for his or her site's
configuration and load.  (See the SCHED section of  Software  Notebook
11.)


The KLINIK LIR provides support for the remote diagnostic line.   This
line  can be used in one of two modes:  remote-console and user.  When
remote-console mode is selected, the local console  terminal  and  the
KLINIK  line  are logically ORed so that all characters that are typed
on either line print on both terminals.  In this mode the KLINIK  line
can  be  used  for  any  function  that  can  be done with the console
terminal, including running front-end diagnostic systems  and  booting
of  monitors.   When  user mode is selected, the KLINIK line becomes a
normal data-set terminal connected through  the  DECsystem-10  in  the
normal manner.

Because the KLINIK line allows privileged access to a system, it  must
be enabled by explicit action on the part of the operator.  To enhance
security, the operator selects a password which must be typed  by  the
KLINIK  user  before  he  can  gain access to the system.  Security is
further enhanced when the remote-console mode is selected by the  fact
that  all characters that are transmitted in either direction are also
printed on the CTY.  This allows any undesired access to be detected.
BEWARE FILE FOR 603A DISTRIBUTION                               Page 4
List of Files


1.0  COMPONENTS OF 603A RELEASE

     603A consists of the following items:

     1)  603A monitor tape with the monitor and new utility releases.

     2)  RSX20F DECtapes for KL10A,B,D sites.

     3)  RSX20F Floppies for KL10E sites.

     4)  Unbundled options appropriate to each site.



1.1  List of Files Included in 603A

     The following files constitute the complete 603A release:

     1)        *.MAC       New monitor source files  (complete  except
                           for unbundled files).

     2)        603A.MCO    Description of the  monitor  changes  which
                           make up 603A.

     3)        603A.DDT    DDT patch file which can be  applied  using
                           the $Y feature of FILDDT to fix problems in
                           603A (see section 4.0).

     4)        *.RAM       LP20 translation RAM files.

     5)        NORMAL.VFU  Default  VFU  for  LP20   or   LP100   line
                           printers.

     6)        *.COR       SOUP correction files for changes to  CUSPS
                           (see section 3).

     7)        TOPA10.REL  The  combined  .REL  files  for  loading  a
                           regular KA10 monitor.

     8)        TOPG10.REL  The KA10 "LUG" monitor combined .REL files.

     9)        TOPI10.REL  The  combined  .REL  files  for  loading  a
                           regular KI10 monitor.

    10)        TOPH10.REL  The KI10 "LUG" monitor combined .REL files.

    11)        TOPW10.REL  The  combined  .REL  files  for  loading  a
                           regular KL10 monitor.

    12)        MONGEN.EXE  Version 50A(136) of MONGEN.

    13)        FGEN.HLP    Version  1076  of  FGEN.HLP  for   use   in
                           conjunction with MONGEN.
BEWARE FILE FOR 603A DISTRIBUTION                               Page 5
List of Files


    14)        CON???.CMD  COMPILE  command   files   for   assembling
                           monitors.

    15)        CMB???.CCL  PIP indirect files for making TOP?10.REL.

    16)        BEWARE.63A  This file.


     In addition to the  above  files  that  constitute  the  standard
     (bundled)  603A  monitor release, each customer site will receive
     the files associated with those unbundled portions of 603A  which
     the  installation  is  licensed  to use.  See Section 2.1 of this
     document for further details.


1.2  New Utility Releases

     1)  BOOTM  - V4(17) to handle TM03 controller.

     2)  BOOTS  - V22(105) to avoid RH20 hang on data error,  or  hang
                  after KL10 just powered up.

     3)  DAEMON - V16(612) fixes bugs plus on-line error logging.

     4)  DTELDR - V2(26) reload and restart  CFE  properly  for  power
                  fail recovery.

     5)  SCDSET - V3(10) version required by SCHEDULER  LIR  which  is
                  now in 603A.

     6)  SYSERR - V12A(1013)  supports  on-line  error  reporting  and
                  /BRIEF switch.

     7)  TWICE  - V4A(25) since 603A  refresher  changed  to  be  more
                  cautious.

     8)  LOGIN  - V60A(634) which is 60(631) plus edits 632, 633,  and
                  634 for Scheduler Class, Auto Locate, and Background
                  Batch.

     9)  OMOUNT - V26B(110) which is 26A(107) plus edit  to  recognize
                  RP06's.

    10)  MAKVFU - V1(17) See VFU1.DOC for information about MAKVFU.

    11)  DDT    - V40A(250) which is V40(220) with a few bug fixes.
BEWARE FILE FOR 603A DISTRIBUTION                               Page 6
Installation Instructions


2.0  INSTALLATION INSTRUCTIONS FOR 603A

First, read BEWARE.63A.  Then if you have a KL based system  read  the
Operator's  Guide in Notebook 13 (revised Jan 1978) for information on
KLINIK.

The installation of 603A should  be  straightforward.   All  necessary
files  are  on  this  month's distribution tape.  Customer sites using
standard supported monitors may use the library files directly to load
their  monitors,  for example TOPI10.REL or TOPH10.REL for KI systems.
Those sites using a non-standard set of  feature  test  settings  will
need  to  run MONGEN and then reassemble the monitor using the correct
CONK?.CMD file.  All of these are standard procedures as documented in
the Monitor Installation Guide.

The patches given in the next section should be installed in your 603A
monitor.    For  your  convenience,  a  machine  readable  patch  file
(603A.DDT) is included.  To use this patch file proceed as follows:

     .GET YURMON  (or whatever you called the monitor you built)
     .DDT
     $"/603A/$Y ($=altmode or ESC)
     (the patches will now be typed out automatically as they are
     made)
     ^C
     .NSAV NEWMON  (or whatever name you wish to call your monitor)

However, if your installation lacks adequate core to .GET your monitor
.EXE file, it is possible instead to use FILDDT as follows:

     .AS TTY LPT  (otherwise $Y to FILDDT outputs to the LPT)
     .R FILDDT
     FILE: YURMON/P
     $"/603A/$Y
     (the patches are now typed out as above)
     ^Z


     1)  The 603A MONGEN differences are:

         The 603A  MONGEN  dialog  has  changed  slightly  to  include
         support  for  the  1091.   Non-1091 KL sites and all KI sites
         will only see this change as an additional question in TTYGEN
         and some changes in terminology in HDWGEN as follows:

         In HDWGEN:

         The question

              LPTs (1,0-3):

         has been replaced by:

              I/O Bus LPTs(1,0-3):
BEWARE FILE FOR 603A DISTRIBUTION                               Page 7
Installation Instructions


         The question

              CDRs(1,0-2):

         has been replaced by:

              I/O Bus CDRs(1,0-2):

         In TTYGEN:

         The following question has been added:

              DECsystem10(1040,1050,1055,1070,1077,1080,1088,1091):

         This question should be answered with the  same  response  as
         the identical question in HDWGEN.

         In addition to the above changes, 1091 sites  will  be  asked
         the following questions:

         In HDWGEN:

              # Line printers on the master front end on CPU0(0,0-2):

              LPTn Lower case(Y,N):

         These should be answered with the  number  of  line  printers
         driven  by RSX20F on the front end on CPU0 and whether or not
         they are lower case.

              # card readers on the master front end on CPU0(0,0-1):

         This should be answered  with  the  number  of  card  readers
         driven by RSX20F on the front end on CPU0.

         In TTYGEN:

              # terminals on the master front end on CPU0(1,1-132):

         This should be answered with the number of timesharing  lines
         connected  through  DH11s  to  the  master front end.  Do not
         include the CTY or KLINIK lines.


     2)  KLINIK Installation

         It is recommended that you install the new version of  RSX20F
         onto  a  spare disk pack so that it will be easy to fall back
         to an existing version of RSX20F should serious  problems  be
         encountered.    The  procedure  for  creating  a  new  RSX20F
         front-end on  a  fresh  pack  is  described  in  the  Monitor
         Installation Guide.

         If you want to install the new software on a disk  pack  with
BEWARE FILE FOR 603A DISTRIBUTION                               Page 8
Installation Instructions


         an  existing  front-end  area, the following procedure can be
         used.  Should you encounter problems, it will be possible  to
         run  RSX20F  from your old DECtapes until you can rebuild the
         front-end area on a disk pack.  This procedure should be done
         during  stand-alone  time  and  requires  an  hour  or  so to
         perform.

         1.  Place the front-end DECtape number 1 on DECtape  unit  0,
             and  front-end  DECtape number 2 on DECtape unit 1.  Both
             tapes must be write-enabled.

         2.  Set the console data switches to binary 000 000  000  000
             000 011.

         3.  Load the new version of RSX20F from the supplied  DECtape
             by  depressing  the  ENABLE  and  then  the  LOAD  SW/REG
             switches on the KL10 front panel.

         4.  Then type:

             ^\ (type control-backslash here)

                 Each time that you are supposed to type ^\, you  will
                 be  loading  the  RSX20F  parser  from DECtape.  This
                 takes about a minute or so because the  DECtape  will
                 have  to  be repositioned each time before the parser
                 code can be read in.  While you are waiting you  must
                 not  type ahead, since RSX20F cannot handle character
                 typein while it is positioning the DECtape.  When the
                 parser is loaded, it should prompt:

                      PAR%

                 If the prompt is  "PAR>",  then  the  KL10  is  still
                 running and should be halted by typing:

                      PAR>SET CONSOLE MAINTENANCE
                          --- ------- -----------
                       Console mode maintenance
                      PAR>HALT
                          ----
                      PAR%SET CONSOLE OPERATOR
                          --- ------- --------
                       Console mode operator

                 If the prompt is "PAR#", then the KL10  microcode  is
                 not running and it should be started by typing:

                      PAR#SET CONSOLE MAINTENANCE
                          --- ------- -----------
                      PAR#START MICROCODE
                          ----- ---------
                      PAR%SET CONSOLE OPERATOR
                          --- ------- --------
BEWARE FILE FOR 603A DISTRIBUTION                               Page 9
Installation Instructions


                 (With the parser and the KL10 in the  correct  state,
                 now  run  the  MOU  (MOUNT)  program  so that you can
                 access  DT1:   and  DB0:.   You  should   enter   all
                 underlined text.

             PAR%MCR MOU
                 --- ---

             MOU>DT1:  (Change this if not on unit 1)
                 ----

             MOU -- MOUNT COMPLETE (typed by RSX20F)

             MOU>DB0:  (Change this if not on unit 0)
                 ----

             MOU -- MOUNT COMPLETE (typed by RSX20F)

             MOU>^Z
                 --

             ^\ (Back to PARSER)
             --

             PAR%MCR PIP
                 --- ---

             PIP>DB0:[5,5]/NV=DT0:*.*;0,DT1:*.*;0
                 --------------------------------

             PIP>^Z
                 --

             ^\
             --

             PAR%MCR RED
                 --- ---

             RED>DB0:=SY:
                 --------

             ^\
             --

             PAR%MCR SAV
                 --- ---

             SAV>SY:/WB (This command saves the bootable front-end  on
             disk)
                 ------

             ^\ [Procedure complete]
             --
BEWARE FILE FOR 603A DISTRIBUTION                              Page 10
Installation Instructions


     3)  SCHEDULER Installation

         If you use the scheduler in round robin mode, you can  simply
         install  it  and the system should continue to run in more or
         less the same way that it runs currently.  On  systems  where
         running  jobs  are  being  swapped  frequently, response will
         probably seem more uniform and you should notice an  increase
         in overall system throughput.  The new scheduler controls the
         balance between I/O bound and CPU bound jobs quite well.  You
         can  adjust  the relative response between these two types of
         jobs by adjusting the in-core protect time parameters (PROTM,
         PROT0,  and  PROT)  and  the quantum runtime for PQ1 and PQ2.
         (See chapter 6 of SCHED in Software Notebook Number 11).

         If you are using scheduler classes, you will have  to  modify
         your  commands to SCDSET to allocate primary percentages that
         add to exactly 100 percent, and define secondary  allocations
         for  each  class (as desired).  It is not necessary to change
         the accounting files when switching between the SCHEDULER  in
         603A and the SCHEDULER in the 6.03 release of TOPS10.


2.1  Unbundled Components of the 603A Release

The following components of the 603A monitor are unbundled, and  hence
are shipped only to properly licensed customers:


     Virtual Memory VMSER.MAC,TOPV10.REL,TOPW10.REL
     DAS78          D78INT.MAC
     DA28           XTCSER.MAC
     DC44           TYPSER.MAC
     TSK to TSK     TSKSER.MAC,TSKSER.DDT
     Networks       S.P11,DN*.P11,CHK11.P11,DDT11.*,MACROS.P11,NETLDR.*
                    DDT.P11,NETTST.MAC,DN92.*,DC72*.PAL,TULIP.*,TULLIB.
     *


If unbundled options or options other than virtual memory are included
in  your  monitor,  restore  the  unbundled  monitor  modules from the
distribution tape, assemble them, and  load  your  monitor  using  the
following LINK command string:

/NOINITIAL /HASH:6000 YURMON/SAVE, YURMON/MAP = /LOCALS /MAXCOR:60K
COMMON,COMDEV,COMNET,COMMOD,UNB1,...,UNBN,TOPW10/SEARCH/GO

where UNB1 is the first unbundled module, UNB2 is the second unbundled
module,  etc.   For  example,  if  a  KL10 site required the unbundled
modules D78INT and TSKSER, the following procedure would be followed:

.R BACKUP
/INTERCHANGE ;files are written on the tape in interchange mode
/TAPE MTxn   ;tape drive where tape containing D78INT is mounted
/RESTORE D78INT.MAC
BEWARE FILE FOR 603A DISTRIBUTION                              Page 11
Installation Instructions


!

"Done
/TAPE MTxm   ;tape drive where tape containing TSKSER is mounted
/RESTORE TSKSER.MAC
!

"Done
/^C
.COMPILE F,S,D78INT,TSKSER
MACRO:  F
MACRO:  S
MACRO:  D78INT
MACRO:  TSKSER
.R LINK
*/NOINITIAL /HASH:6000 YURMON/SAVE, YURMON/MAP = /LOCALS /MAXCOR:60K
COMMON,COMDEV,COMNET,COMMOD,D78INT,TSKSER,TOPW10/SEARCH/GO
BEWARE FILE FOR 603A DISTRIBUTION                              Page 12
Warnings of Known Deficiencies


3.0  WARNINGS OF KNOWN DEFICIENCIES IN 603A


    ***********************************************************
    *                                                         *
    *              WARNING -- REQUIRED PATCHES                *
    *                                                         *
    ***********************************************************


3.1  Required Patches To The Monitor

In 603A.DDT:


"" MCO 8294 - PREVENT STOPCD PLP ON USETO WHICH DOUBLY EXTENDS A RIB"
FILIO$:
USETO4-1/JRST USETO3

""MCO 8290 - RETURN CORRECT ERROR CODE ON RENAME FAILURE"
FILUUO$:
RENAM5 22/POP P,T2
ANDCAM T2,PPBNLG(P1)


3.2  Required Patches To CUSPS

None.  Any CUSPs with 603A dependent changes  are  being  released  on
this tape with 603A.


3.3  Recommended Patches

The latest  distributed  MACRO,  that  is  MACRO  53(1020),  will  not
correctly  assemble the POINTR MACRO as used in LOGIN 60A.  A complete
cure will be available  in  the  next  maintenance  release  of  MACRO
scheduled to occur with 701.  Until then either assemble LOGIN and any
other programs using the POINTR MACRO with  the  previous  version  of
MACRO or install edit 1026 (SPR 10-25962) as published in the 1 August
1978 Software Bulletin.


3.4  Known Problems - SCHEDULER

     1)  Class Scheduler Secondary Quota Allocations - If your  system
         does  not  have  a  large  amount  of core, the assignment of
         secondary quotas and  the  value  of  the  response  fairness
         factor should be made with considerable care.  Because of the
         manner in which the swapper chooses to swap jobs in and  out,
         the  system may temporarily stop running jobs if core becomes
         filled with jobs whose secondary allocation is small.   These
         jobs  tend  to  stay in core for long periods of time because
         their in-core protect time  is  not  decremented  when  their
         class  is  not  being scanned to run.  This can prevent other
BEWARE FILE FOR 603A DISTRIBUTION                              Page 13
Warnings of Known Deficiencies


         jobs from being swapped in and run.

     2)  Load Simulation Package - The load  simulation  package  will
         hang  if  the programs have not been installed in the correct
         disk area.  The load simulation package  controller,  LODTST,
         expects  to  find  the  programs  that  it runs on the ERSATZ
         device TST:  ([5,23]).  If the programs are  not  found,  the
         simulation jobs will hang.

     3)  Using Job Classes to Run Spoolers  and  Similar  Jobs  -  The
         standard  6.03 class Scheduler used an exponentially decaying
         average of accumulated runtime to assign  priorities  to  the
         various  classes.   As  a  result,  if  all  of the jobs in a
         particular class used very little  runtime,  when  they  were
         able  to  run  they would have a very high priority.  The new
         class scheduler works by  granting  each  class  the  highest
         priority  to  run  in  the same percentage as assigned to the
         class by the system administrator.  This means that jobs that
         turn  down  a chance to run on a particular cycle will not be
         given a higher priority  later  on  when  they  again  become
         runnable.   As a result, using a special scheduler class will
         not substitute as a high priority queue for  I/O  bound  jobs
         such  as  spoolers and system jobs such as DAEMON.  Such jobs
         should be placed in a high priority queue if running them  in
         a  normal  timesharing  queue  does  not  result  in adequate
         throughput at your installation.


3.5  Known Problems - KLINIK

     1)  Double Typing of System Startup Message - If the KLINIK  line
         is  in  remote  console  mode,  the  initial message from the
         system after startup is double typed.  This  is  because  the
         message  is  being  transmitted  both for the CTY and for the
         KLINIK timesharing line.

     2)  Unexpected Pauses in KLINIK Output - The output  occasionally
         will  pause  for a little over one second.  This happens when
         the front-end fails to acknowledge a message  and  output  is
         suspended until the -10 times out.

     3)  Numerics in PSWD.

     4)  Hangs up and won't answer data set if you mistype the PSWD  3
         times.
BEWARE FILE FOR 603A DISTRIBUTION                              Page 14
Observable Differences between 6.03 and 603A


4.0  OBSERVABLE DIFFERENCES BETWEEN 6.03 AND 603A


4.1  General Warnings

On KL10  based  systems,  it  may,  under  certain  circumstances,  be
desirable  to  run  the  monitor  with KLDCP and/or RSX10F rather than
RSX20F.  Since the monitor expects to be running with  RSX20F  as  the
front end software, it starts up the so called "primary communications
protocol" which KLDCP  does  not  understand.   To  disable  this  the
following patch should be installed in the monitor:

     PPCPAT/   PUSHJ P,STMPPC   JFCL

Note that if the monitor is patched in this  fashion,  it  will  still
work  with  RSX20F but RSX will not automatically attempt to cause the
monitor to reload  itself  whenever  it  detects  that  the  KL10  has
stopped.  Also, none of the front end devices will be available.

Sites who do not wish to use the class scheduler, may turn it  off  by
defining  the  symbol M.CLSS,0 in the "DEFINE SYMBOL,VALUE" portion of
the MONGEN dialogue.

To support up to 8 RH20's, the EPT was moved to page  1.   This  broke
SNOOPY  and  possibly  other  programs.   The  location  of the EPT is
GETTABable and any program which needs to know the address of the  EPT
should use the GETTAB to determine it.

DAEMON must be run without DSKFUL PAUSE set.

In 602A and 6.03 there was a bug whereby if IO was attempted on a tape
drive  on  a  TM10  controller  a  "problem on device" message was not
given, but instead the tape timed out with  a  "hung  device"  message
after  1  minute.   This  has  been  fixed in 603A, and runs correctly
in-house and at most field-test  sites.   At  some  field-test  sites,
however, this code does not execute correctly, and we have been unable
to determine what the hardware difference  is.   We  are  distributing
603A  with  the  new TMXKON which fixes the original problem.  If your
site  experiences  spurious  "problem  on  device"  or  "hung  device"
messages on mag tapes, make the following change in TMXKON:

     TMXSEL+12/ HRROI T2,RB.FYB JFCL


The KA TINY configuration has not been assembled or tested.


4.2  Differences Important to the System Programmer

603A incorporates many bug fixes and three LIR's:  the KLINIK LIR, the
SCHEDULER LIR, and the 1091 LIR.  General information on each of these
LIR's is included here for reference.

     1)  SCHEDULER Differences from 6.03
BEWARE FILE FOR 603A DISTRIBUTION                              Page 15
Observable Differences between 6.03 and 603A


         603A contains a new version of SCDSET  that  will  allow  the
         system administrator to adjust all of the parameters that can
         be set in the new scheduler.  It contains functions  to  read
         and   set   primary  and  secondary  allocation  percentages,
         scheduler fairness parameters and job classes.  In  addition,
         SCDSET  can  now  be  directed  to read commands from a file.
         This makes running SCDSET at  system  startup  somewhat  more
         convenient.

         603A contains a class scheduler that is very  different  from
         the  existing  6.03  class  scheduler.   With  the 6.03 class
         Scheduler, the sum of the class  allocation  percentages  may
         add  up  to  any  value,  and  no direct control of secondary
         allocation is offered.  With 603A, the  sum  of  the  primary
         allocation percentages must be 100, secondary allocations may
         be provided by the system administrator.

     2)  Using the KLINIK Line

         The KLINIK line is normally  disabled  so  that  unauthorized
         access  is prevented.  To enable the KLINIK line for use, the
         operator must issue the SET  KLINIK  command  to  the  RSX20F
         parser.  The parser will then prompt for a mode which must be
         one of either:

         1.  User -- which enables the KLINIK line  as  a  timesharing
             terminal.

         2.  Remote -- which logically OR's the KLINIK line  with  the
             console terminal.

         After the mode has been accepted, the parser will then prompt
         the  operator  for  the access window parameters which define
         the  period  of  time  the  KLINIK  line  will  actually   be
         available.  RSX20F will ask four questions:

         1.  Access window open date:  Give the date on  which  access
             will begin.

         2.  Access window open time:   Give  the  time  of  day  when
             access will begin.

         3.  Access window close date:  Give the date on which  access
             will terminate.

         4.  Access window close time:  Give the time of day at  which
             access will terminate.

         If the open date or time is answered with a carriage  return,
         the  day  will default to today, and the time will default to
         the current time of day.   If  the  close  date  or  time  is
         answered with a carriage return, the date will default to one
         day after the open date and the time will default to the open
         time.
BEWARE FILE FOR 603A DISTRIBUTION                              Page 16
Observable Differences between 6.03 and 603A


         The date should be entered as one of

              DD-MMM-YY

              DD-MMM-19YY

              DD MM YY

              DD MM 19YY

         where DD is the day of  the  month,  MMM  is  a  3  character
         abreviation  for  the  month and YY is the last two digits of
         the year.

         The time should be entered in one of the forms

              HHMM

              HH:MM

         where HH is the hour using a 24-hour  clock  and  MM  is  the
         minutes.

         If the KLINIK mode  specified  above  was  user,  the  dialog
         terminates  at this point.  If the KLINIK mode is remote then
         the parser will prompt for a password.  The  operator  should
         type  from  1  to  6  alphanumeric  characters  to define the
         password that will be required  from  the  KLINIK  line  user
         before the line will be connected.

         Finally, the RSX20F parser will ask:

              Highest console mode:

         to which the operator must type one of MAINTENANCE (highest),
         OPERATOR  or  PROGRAMMER  (lowest).  While the KLINIK line is
         active, RSX20F will not allow the mode of the console  to  be
         set  above  the  level  specified  at this time.  There is no
         default answer to this question.


         The operator can terminate the KLINIK line  at  any  time  by
         entering the command:

              CLEAR KLINIK

         This command causes RSX20F to ignore all data passing to  and
         from  the  KLINIK  line, but does not hang up the phone.  The
         phone can be hung up using the command:

              DISCONNECT
BEWARE FILE FOR 603A DISTRIBUTION                              Page 17
Observable Differences between 6.03 and 603A


     3)  Differences Between 6.03 and 603A/1091

         Line Printer

         There are two new functions to the DEVOP. UUO for loading the
         VFU  and  the  translation  RAM  on  LP20 line printers.  The
         LPTSPL distributed with the 603A  1091  LIR  knows  and  uses
         these  DEVOP.'s.  Externally, the VFU handling is the same as
         with the standard release 2 VFU handling for LP100's,  except
         that  the  LP20  does  not  have  a  very good default VFU in
         hardware.  Just follow the standard documentation for LPTSPL.

         The translation RAM makes a much more noticeable  difference.
         LPTSPL  will  automatically  load  the  RAM  when  it  starts
         printing.  LPTSPL will not currently change the  contents  of
         the RAM once it has started.

         There are two RAM files that get placed onto  SYS:.   One  is
         for  upper  case only printers, and the other is for printers
         with both upper and lower case.  LPTSPL decides which to  use
         by checking whether the printer was declared to be lower case
         in MONGEN.

         Card Reader

         The format of the data returned from  an  INPUT  UUO  when  a
         Console  Front  End card reader is inited in Super Image mode
         is different  from  an  I/O  bus  card  reader.   The  SPRINT
         included  with  603A  for  1091's has been taught to use this
         format.

         Terminals

         For Console Front End  terminals,  only  dial-up  lines  will
         auto-baud.   And,  dial-up  lines  will always auto-baud, but
         only after the phone is first answered.  Noise on  the  line,
         or pressing break on the terminal or any other technique that
         used to work to cause  auto-baud  detect  will  not  work  on
         Console Front End lines.

         Therefore, line speeds must be set up  in  TTY.INI  (assuming
         that  INITIA  is  run  on  all Console Front End lines).  The
         following mapping can be used to determine which  TTY  number
         to use for which Console Front End line number:

             TTY      Front End Line

             TTY0     KLINIK line
             TTY1     First Comm FE Console
             TTY2     Second Comm FE Console
             TTY3     Third Comm FE Console
             TTY4     Port 0 on DC20   0
             TTY5     Port 1 on DC20   0
             .  .  .
BEWARE FILE FOR 603A DISTRIBUTION                              Page 18
Observable Differences between 6.03 and 603A


             TTY23    Port 17 (octal) on DC20  0
             TTY24    Port 0 on DC20   1
             .   .   .


4.3  Differences Observable to the User

None.


4.4  Differences Observable to the Operator

Refresh questions

REFRESH now preserves the front-end  file  system  (FE.SYS[1,4]).   If
there  is  an  FE.SYS  on  a  pack when a REFRESH command is given the
monitor will put an entry in the UFD and mark the blocks of FE.SYS  as
in use.

A new message, "ERROR TRYING TO REREAD HOME BLOCKS" is given if a data
error occurs while reading home blocks.

On-line  error  reporting  has  been  added  to  SYSERR   V12A.    See
SYSERR.DOC.
BEWARE FILE FOR 603A DISTRIBUTION                              Page 19
Observable Differences between 6.03 and 603A


5.0  DEPENDENCIES

     1)  Requires SYSERR V10(543)  or  later.   SYSERR  V12A(1012)  is
         included in this release.

     2)  Model B processors require version 212 of KL10 microcode.
         Model A processors require version 157 of KL10 microcode.

     3)  Requires version 12(0), or later, of DX10 microcode.

     4)  Requires RSX20F, version YA10-14.


5.1  Dependencies for 603A 1091 LIR only

     1)  LPTSPL V 102(2263)-1.

     2)  SPRINT V 102(2024)-1.

     3)  RSX20F VB12-40.
BEWARE FILE FOR 603A DISTRIBUTION                              Page 20
Results of Running 603A  on our In-house Systems


6.0  RESULTS OF RUNNING 603A ON OUR IN-HOUSE SYSTEMS AND AT
     FIELD TEST SITES


We have run the final 603A on our in-house  software  development  and
marketing  systems,  including KI10, and KL10 configurations, for more
than two weeks with no unresolved crashes.   Our  in-house  experience
with preliminary versions of 603A covers more than six months of heavy
usage with steadily increasing reliability.

Twenty field-test sites including  KA's,  KI's,  and  KL's  have  been
running  several  early  versions of 603A for several months.  We have
assembled and loaded many options of 603A including LUG  monitors  and
non-virtual KI10's, but the only options to receive heavy testing were
KA10's, and KI10's and KL10's with virtual  memory.   All  field  test
sites  report 603A to be more reliable than 603.  All field test sites
report 603A to be more reliable than 6.03.
BEWARE FILE FOR 603A DISTRIBUTION                              Page 21
Unbundled Portions of the Monitor


7.0  UNBUNDLED SOFTWARE


7.1  SUPPORT FOR UNBUNDLED OPTION - VM


7.1.1  LIST OF FILES INCLUDED IN THE 603A VM SUPPORT PACKAGE

The following  files  constitute  the  complete  603A  virtual  memory
support package:


     1)   VMSER.MAC      603A monitor  source  file  which  implements
                         virtual memory.

     2)   TOPV10.REL     The  combined  .REL  file  for  KI10  virtual
                         memory monitors analogous to TOPI10.REL.

     3)   TOPW10.REL     The  combined  .REL  file  for  KL10  virtual
                         memory monitors.

     4)   CONVI.CMD      Command files for assembling KI10 virtual
          CMBVI.CCL      memory monitors and  creating  combined  .REL
                         files.

     5)   CONVL.CMD      Command files for assembling KL10 virtual
          CMBVL.CCL      memory monitors and  creating  combined  .REL
                         files.

     6)   MAKPFH.MAC     Page fault handler.
          MAKPFH.EXE
          PFH.VMX

     7)   DDT.VMX        VMDDT.

     8)   GET.*          User mode program to .GET virtual memory
          GET3.DOC       executable programs.


7.1.2  INSTALLATION INSTRUCTIONS

Installation of virtual memory monitors is  very  straightforward  and
similar  to  non-VM monitors.  The differences are mainly obvious file
substitutions such as TOPV10.REL or TOPW10.REL in place of TOPI10.REL.
BEWARE FILE FOR 603A DISTRIBUTION                              Page 22
Unbundled Portions of the Monitor


7.2  SUPPORT FOR UNBUNDLED OPTION - DC44


7.2.1  LIST OF FILES INCLUDED IN THE 603A DC44 SUPPORT PACKAGE

The following file constitutes the complete 603A DC44 support package:

     1)   TYPSER.MAC     603A monitor source file for DC44 interface.


7.2.2  INSTALLATION INSTRUCTIONS

The particular instructions  that  apply  in  order  to  include  DC44
support are:

Assemble TYPSER.MAC by typing the following command string:

          COMPILE F,S,TYPSER

Then LINK your monitor following the procedure  described  in  section
2.1.
BEWARE FILE FOR 603A DISTRIBUTION                              Page 23
Unbundled Portions of the Monitor


7.3  SUPPORT FOR UNBUNDLED OPTION - DAS78


7.3.1  LIST OF FILES INCLUDED IN THE 603A DAS78 SUPPORT PACKAGE

The  following  files  constitute  the  complete  603A  DAS78  support
package:


     A.   MONITOR CODE

     1)   D78INT.MAC     603A monitor source file for DAS78 interface.


     B.   DAS78 PDP-11 CODE

     1)   DAS78.CTL      Control file to assemble the PDP-11 code.

     2)   DAS78.P11      Sources for DAS78 PDP-11 code.

     3)   DAS78.BIN      Executable DAS78 PDP-11 code.

     4)   DAS78.EXE      DDT11 file for the PDP-11 code.


     C.   DAS78 SPOOLER - USED TO SHIP FILES TO/FROM THE DAS78

     1)   D78SPL.CTL     Control file to assemble D78SPL.

     2)   D78SPL.MAC     Source code for D78SPL.

     3)   D78SPL.EXE     Executable code.


     D.   DAS78 QUEUE AND QMANGR - FOR USE WITH D78SPL

     1)   QUE.CTL        Control file to assemble QMANGR and QUEUE.

     2)   QUEUE.D78      Source code for DAS78 modified QUEUE.

     3)   QUEUE.EXE      Executable code.

     4)   QMANGR.D78     Source code for DAS78 modified QMANGR.

     5)   QMANGR.EXE     Executable code.
BEWARE FILE FOR 603A DISTRIBUTION                              Page 24
Unbundled Portions of the Monitor


     E.   SPOOL - DAS78 MODIFIED LPTSPL

          This program is for use when using a 2780 as a Remote  Batch
          Station  to the DECsystem-10.  This modified LPTSPL also can
          be used to print on the local printer.

     1)   SPOOL.CTL      Control file for assembling a DAS78 LPTSPL.

     2)   SPOOL.D78      Source code for DAS78 modified SPOOL.

     3)   LPTSPL.EXE     Executable code.


     F.   SPRINT - DAS78 MODIFIED SPRINT

          This program is for use when using a 2780 as a Remote  Batch
          Station to the DECsystem-10.  This modified SPRINT will also
          be used to read cards from the local card reader.

     1)   SPRINT.CTL     Control file for assembling a DAS78 SPRINT.

     2)   SPRINT.D78     Source code for DAS78 modified SPRINT.

     3)   SPRINT.EXE     Executable code.


     G.   PDP-11 DEBUGGING PROGRAM

     1)   DDT11.MAC      Source for DDT11.

     2)   DDT11.EXE      Executable code.

     3)   DDT11.DOC      DDT11 document.


     H.   MODEM DIAGNOSTIC

     1)   DQMODM.HLP     Short document on how to use DQMODM.

     2)   DQMODM.BIN     Executable code.


     I.   DOCUMENTS

     1)   DAS78.MEM      The DAS78 "Cookbook" - WARNING:   Preliminary
                         version.

     2)   D78MNT.MEM     Installation   hints   and    other    useful
                         information.

     3)   DAS78.DOC      Changes from 6.03 to 603A.
BEWARE FILE FOR 603A DISTRIBUTION                              Page 25
Unbundled Portions of the Monitor


     J.   MISCELLANEOUS PROGRAMS

     1)   C.MAC          Needed for assembling QUEUE.

     2)   SCNMAC.MAC     Needed for assembling QUEUE.

     3)   HELPER.REL     Needed for LPTSPL, SPRINT, and QUEUE.

     4)   QUEUER.REL     Needed for LPTSPL, SPRINT, and QUEUE.

     5)   SCAN.REL       Needed for QUEUE (V4).

     6)   WILD.REL       Needed for QUEUE (V5).


     Note:  The MACDLX assembler is required  to  assemble  DAS78.P11,
and  the  BOOT11  bootstrap is required to load code from the -10 into
the -11 memory.  Both  these  programs  will  be  found  on  the  main
(bundled) 603A monitor distribution tape.


7.3.2  INSTALLATION INSTRUCTIONS

The particular instructions that  apply  in  order  to  include  DAS78
support are:

Assemble D78INT.MAC by typing the following command string:

          COMPILE F,S,D78INT

Then LINK your monitor following the procedure  described  in  section
2.1.

Carefully read D78MNT.MEM, DAS78.MEM, and DAS78.DOC  for  installation
instructions  concerning  the  -11  portion  of  the  DAS78 as well as
installation instructions for the D78SPL spooler.  Note  that  command
formats are somewhat different from 6.02.
BEWARE FILE FOR 603A DISTRIBUTION                              Page 26
Unbundled Portions of the Monitor


7.4  SUPPORT FOR UNBUNDLED OPTION - XTCSER


7.4.1  LIST OF FILES INCLUDED IN THE 603A XTCSER SUPPORT PACKAGE

The following  file  constitutes  the  complete  603A  XTCSER  support
package:

     1)   XTCSER.MAC     603A monitor source file for DA28 driver.


7.4.2  INSTALLATION INSTRUCTIONS

The particular instructions that apply  in  order  to  include  XTCSER
support are:

Assemble XTCSER.MAC by typing the following command string:

          COMPILE F,S,XTCSER

Then LINK your monitor following the procedure  described  in  section
2.1.
BEWARE FILE FOR 603A DISTRIBUTION                              Page 27
Unbundled Portions of the Monitor


7.5  SUPPORT FOR UNBUNDLED OPTION - TSK TO TSK COMMUNICATIONS SUPPORT


7.5.1  LIST OF FILES INCLUDED IN THE 603A TSKSER SUPPORT PACKAGE

The  following  files  constitute  the  complete  603A  TSK   to   TSK
communications support package:

     1)   TSKSER.MAC     603A monitor  source  file  for  TSK  to  TSK
                         communications.  


7.5.2  INSTALLATION INSTRUCTIONS

The particular instructions that apply  in  order  to  include  TSKSER
support are:

Assemble TSKSER.MAC by typing the following command string:

          COMPILE F,S,TSKSER

Then LINK your monitor following the procedure  described  in  section
2.1.


7.5.3  WARNING OF KNOWN DEFICIENCIES IN TSKSER

Please keep in mind that DC75's were designed only to communicate with
DC72's.   Unless  FT.ANF  is non-zero, DC75's will not be able to copy
binary TSKSER data over the DL10.
BEWARE FILE FOR 603A DISTRIBUTION                              Page 28
Unbundled Portions of the Monitor


7.6  SUPPORT FOR UNBUNDLED OPTION - NETWORK


7.6.1  LIST OF FILES INCLUDED IN THE 603A NETWORK SUPPORT PACKAGE

The following is a list of all required files on the  NETWORK  support
tape.

     CHK11.P11      PDP-11 sources.
     DDT.P11
     DN2741.P11
     DNCDDH.P11
     DNCDDP.P11
     DNCDDQ.P11
     DNCDDS.P11
     DNCDMC.P11
     DNCDUP.P11
     DNCNFG.P11
     DNCOMM.P11
     DNCRD.P11
     DNCTAB.P11
     DNDBG.P11
     DNDCMP.P11
     DNDEV.P11
     DNDH11.P11
     DNDL10.P11
     DNDM11.P11
     DNDN11.P11
     DNDTE.P11
     DNDZ11.P11
     DNLBLK.P11
     DNLPT.P11
     DNNCL.P11
     DNNSP.P11
     DNNSP3.P11
     DNPLT.P11
     DNPTP.P11
     DNPTR.P11
     DNRDA.P11
     DNRDE.P11
     DNTRCE.P11
     DNTSK.P11
     DNTTY.P11
     MACROS.P11
     S.P11
     TSKTST.P11
BEWARE FILE FOR 603A DISTRIBUTION                              Page 29
Unbundled Portions of the Monitor


     NETLDR.CTL     NETLDR down line load utility files.
     NETLDR.EXE
     NETLDR.HLP
     NETLDR.MAC

     MACLIB.MAC     Network test program (See note).
     NETTST.EXE
     NETTST.MAC
     NETTST.MEM
     NETLIB.MAC
     TULIP.MEM
     TULIP.MAC
     TULLIB.MAC

     DDT11.DOC      A DECsystem-10 program for examining nodes
     DDT11.EXE      or dumps.
     DDT11.MAC

     72BLDA.CTL     Sample control files for building network
     BIGLST.CTL     nodes.
     DC7515.CTL
     DN2065.CTL
     DN8222.CTL
     DN8244.CTL
     DN8266.CTL
     DN8267.CTL
     DN8702.CTL
     DN8716.CTL
     DN8727.CTL
     DN8731.CTL
     DN8732.CTL
     DN9273.CTL
     NETBLD.CTL

     8CARDS.MAC     PDP-8 sources.
     BOOT.PAL
     BT71.PAL
     CLDR.PAL
     DUMP.PAL
     DC72NP.PAL
     DN92.PAL

     DN92.DOC       Documentation on the DN92.
     DN92.SIG
     DN9210.DOC

Note:  The files TULIP.*, TULLIB.*, and  DDT.P11  are  in  the  public
domain.  DIGITAL assumes no responsibility for their use, correctness,
or content.  DDT11 and  NETTST  are  unsupported,  and  as  such,  are
included  only as useful tools developed by DIGITAL for support of the
in-house network.
BEWARE FILE FOR 603A DISTRIBUTION                              Page 30
Unbundled Portions of the Monitor


7.6.2  REQUIRED PROGRAMS

The following are required for installation of various  parts  of  the
network software.

     MACDLX         Version 27 or later
     PAL10          Edit 143 or later
     NETLDR         Edit 126 or later
     BOOT11         Edit 44 or later
     DTELDR         Edit 26 or later


7.6.3  INSTALLATION INSTRUCTIONS

Refer to the NETWORKS SOFTWARE INSTALLATION  GUIDE  (AA-5156-TB,  June
1978)  for  instructions  on building network nodes for the DC75, DN8x
and the DN20.


7.6.4  DIFFERENCES FROM 6.03 NETWORK SUPPORT

     1)  DMC-11, DUP-11, DZ-11 Drivers

         These three drivers have been added for support of  the  DN20
         front end / DN200 remote station.

     2)  Multiple Types of Synchronous Lines

         It is now possible to build a front end / remote station that
         has  more  than  one  type  of  synchronous  line.  There are
         symbols (DS11N, DQ11N, etc.) for each type of line.  If  none
         of  these are defined, the value of NLINES will be used.  For
         example, if the node is a DN20, NLINES=4, and DMC11N=1,  then
         DUP11N  will  be  set to 3.  This is because the default line
         type for a DN20 is  a  DUP11.   If  NLINES=1,  DMC11N=1,  and
         DUP11N=2, NLINES will be reset to 3.

     3)  DZ11 Support

         As noted above, a DZ11 driver has been  added.   Please  note
         that DZ11's do NOT support split speeds as does the DH11.  If
         you attempt to define a split speed  for  a  DZ11,  an  error
         message  will  print  during assembly.  Also please note that
         the DZ11 supports different speeds than a DH11.  If the  user
         attempts  to  set the DZ11 (or the DH11) to an illegal speed,
         the command (or TRMOP.) will be ignored, but no error message
         (or return) will be given.

     4)  The DHUSE Macro

         There are two new arguments to the DHUSE macro.   Please  see
         the NETWORKS INSTALLATION GUIDE for more information.
BEWARE FILE FOR 603A DISTRIBUTION                              Page 31
Unbundled Portions of the Monitor


     5)  Phase II DECNET

         This release includes a Phase II compatible port.  This is in
         addition  to  the  Phase  I compatible port.  Both may not be
         used in a node at the same time, but with two different nodes
         in  the  same network, one could have the Phase I port, while
         the other has the Phase  II  port.   The  Phase  II  port  is
         selected  by setting FT.DCP=3 (NSP version 3).  The NSP entry
         in the NSPLST macro is replaced by an NSP3 entry.   The  NSP3
         macro has 2 or optionally 3 arguments.  The first is the line
         number, the second is the  device  list  (same  as  the  last
         argument  of the NSP macro), and the third is the node number
         to use if the DECnet node does not supply one.

     6)  Autobaud Detect

         The autobaud code has been rewritten, and will  now  autobaud
         at  110,  134,  150,  300,  and 1200 baud on ",", "<CR>", and
         "^C".

     7)  Dataset Control

         Dataset control has been rewritten,  and  all  of  the  known
         problems with 603 dataset control have been fixed.

     8)  DDT11

         There is a totally new  version  of  DDT11  on  this  NETWORK
         support  tape.  There is a DOC file which outlines all of the
         new features.  Please read it for more  information.   Please
         note that DDT11 is not supported.

     9)  TSKTST.P11

         There is a new module (TSKTST) which is meant to be used as a
         test package for the network task code (DNTSK.P11).  This has
         nothing to do with Task to Task between -10's.

    10)  NETTST, NETLIB, TULIP, TULLIB

         These four modules are used to build a DECsystem-10  program,
         NETTST,  which  may  be useful in debugging network problems.
         Documentation on this program  is  provided  on  the  NETWORK
         support  tape.   Please  note:  like  DDT11,  this program is
         unsupported.  Also,  TULIP  and  TULLIB  are  in  the  public
         domain.
BEWARE FILE FOR 603A DISTRIBUTION                              Page 32
Unbundled Portions of the Monitor


7.6.5  WARNINGS AND KNOWN DEFICIENCIES

     1)  Transfering Binary Data Through A DC75

         Please keep in mind that the DC75 was  designed  to  transfer
         ASCII  data.   If  you wish to transfer binary data, you must
         turn on the feature test FT.ANF by setting it  non-zero.   If
         you   do  not,  the  DC75  will  trap  when  binary  data  is
         transferred (The assumption is made  that  the  invalid  data
         type indicates that the protocol is broken).

     2)  Proper Modem Strapping

         The new version of the data set code, will, by  default,  set
         REQUEST  TO  SEND.   This is in conformance with EIA RS232-C.
         This may cause two types of problems.  First,  if  the  modem
         options  selected include "strap RTS to busy", the modem will
         not work correctly.  Second, there is a jumper on  the  modem
         cable  from the DH11 distribution panel which can do the same
         thing, and installation of this cable should include  cutting
         this  jumper.   The  jumper  is labeled "BUSY".  Please note,
         that this feature is required by terminals such  as  the  IBM
         2741 and the LA36/ASR.

         This feature might also effect some users of  BPO  Datel  200
         services, as they use the signal for other things.

     3)  DEBUG, DGUTS, and Long SEND ALL's

         It has been noted that many sites are  running  with  DEBUG=1
         and  DGUTS=0.   We  suggest  that production environments run
         with DGUTS=1, and DEBUG=0.  This will prevent the case  of  a
         DN87  (not  DN87S) with 96 or so TTY's from crashing when the
         -10 (which has ALL the TTYs attached) does a long SEND ALL.

     4)  TTYRNN Features (Saving Core)

         We suggest that sites with core problems (in the -10 as  well
         as  the  -11)  make  use  of  the FT.RNN feature.  Using this
         feature, and setting TTYRNN=OURNNM  will  prevent  TTYs  from
         connecting  to  the -10 until they are used (typed on).  This
         will cause SEND ALLs to go to fewer TTYs, and allow sites  to
         allocate fewer LDBs for TTYs in the -10 at MONGEN time.  This
         will save core in the -10.  If an application requires a  TTY
         to  be  connected,  the symbol TxxxRNN=nn can be defined, and
         the -10 will connect to that TTY.  In this  example,  xxx  is
         the  number of the TTY in the node, and nn is the node number
         of the -10.
BEWARE FILE FOR 603A DISTRIBUTION                              Page 33
Unbundled Portions of the Monitor


     5)  Autobaud

         Some users, in the past, have believed that it  was  required
         to  define a line as a dataset line to get autobaud.  This is
         not the case.  Autobaud is  the  default  case  for  a  line.
         Autobaud  is  cleared  by defining a speed for the line.  For
         more information, see the NETWORKS INSTALLATION  GUIDE,  page
         3-6  and  page  3-7.   This  guide was distributed as part of
         update notice #70 of the Software Notebooks in May 1978.


7.6.6  REQUIRED PATCHES

There are no known patches for  the  NETWORK  support  code  for  this
release of the TOPS-10 monitor.



[End of BEWARE.63A]