Google
 

Trailing-Edge - PDP-10 Archives - bb-d868e-bm_tops20_v41_2020_dist_1of2 - 4-1-documentation/tops20.bwr
There are 34 other files named tops20.bwr in the archive. Click here to see a list.


                    TOPS-20 Beware File


                         Apr-05-83


                     VERSION 4.1(5471)


                        Release 4.1










COPYRIGHT (C) 1976,1978,1979,1980,1981,1982,1983 BY  DIGITAL
EQUIPMENT   CORPORATION,   MAYNARD,   MASS.    THE  SOFTWARE
DESCRIBED IN THIS DOCUMENT 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  DOCUMENT  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.
                                                      Page 2


1.0 INTRODUCTION

1.1 Function

This document supplements the TOPS-20  manuals  by  pointing
out   hints  and  potential  problems  that  may  have  been
discovered at the last minute.

2.0 INSTALLATION INFORMATION

The installation of this release is almost identical to  the
installation  of  the Release 4.  The only difference is the
names of  two  files.   In  the  manuals,  these  files  are
referred to as n-CONFIG.CMD and n-SETSPD.EXE, where n is the
number of the release.  For Release 4.1, n is  4-1,  so  the
names    of   the   two   files   are   4-1-CONFIG.CMD   and
4-1-SETSPD.EXE.  4-1-SETSPD is supplied on the  installation
tape.   Each  site supplies its own CONFIG file, tailored to
its needs.  The easiest way to create this file is  to  copy
the   4-CONFIG.CMD   file   to  4-1-CONFIG.CMD.   Leave  the
4-CONFIG.CMD file in case you  decide  to  go  back  to  the
previous  release.  To create a new 4-1-CONFIG.CMD file, see
the TOPS-20 INSTALLATION GUIDE, Chapter 3.

On page 4-5 of the TOPS-20 Software Installation Guide there
is  an error.  In step 122 after the error "UFD -- DIRECTORY
ALREADY EXISTS" the recovery procedure is  wrong.   If  this
error  occurs  and  you are positive that you have performed
step 116 on page 4-4, then  the  front-end  file  system  is
irrepairably  damaged.  You will have to start building your
pack from scratch after you have reformatted it.  If you are
not  sure  that  you  performed  step 120, you can start the
procedure from step 113 on page 4-3.

If you don't know how to format a disk pack you should  have
your  DIGITAL  Field  Service Representative format the pack
for you.  If you are updating an  existing  pack  (which  is
probably  the  case  if  you received the "DIRECTORY ALREADY
EXISTS" error) you should be sure to save any files from the
disk  that  you  don't  want to lose before you reformat the
pack.  You can boot and  run  the  system  from  the  floppy
drives  until  you  format  the  pack.   Once  the  pack  is
reformatted you can restart the installation by returning to
step 3 on page 2-2 of the INSTALLATION GUIDE

3.0 EXEC

3.1 Exec

The EXEC that is included in this release is  based  on  the
Release  5  EXEC.  The version of the EXEC is 5.1(1354).  It
contains a few more edits than the Release 5 EXEC to make it
transportable  between  a  4.1 system and a 5.0 system.  Any
new features to the Release 5 EXEC falls under one of  three
categories  under  Release  4.1.   The  new feature is fully
                                                      Page 3


functional under Release 4.1;  it is meaningless  under  4.1
(i.e.  DECNET ACCESS in a directory);  it is not implemented
under  4.1  (i.e.   extended  address   switches   to   EXEC
commands).    The  TOPS-20  USER'S  GUIDE  and  the  TOPS-20
COMMANDS REFERENCE MANUAL  have  been  updated  to  indicate
which category the new features fall under.

3.2 Directory

Directory commands now have more  descriptive  guide  words.
Users  must change any DIRECTORY command guide words used in
control  (.CTL)  files.   Otherwise,  the  command  will  be
rejected by the EXEC with the error "?Invalid Guide Word".

3.3 Compile/Load

The version 5 EXEC also includes a change in  the  operation
of  the COMPILE/LOAD commands which is intended to correct a
deficiency  but   which   may   possibly   affect   existing
procedures.

This situation arises on load-class commands if there  is  a
search list for the object (REL) files.  For example,

@COMPILE PROG

where DSK:  has a logical name definition including a search
list of two or more directories, or

@COMPILE AA:PROG BB:PROG

where the object file specification includes such a  logical
name.

This situation usually exists where a  user  has  a  private
directory  containing  sources  files  he  has modified, and
builds a program using RELs from a common library  directory
as well.  E.g.,

@DEFINE DSK:  DSK:,PS:<LIBRARY>

The usual operation of COMPILE/LOAD is to compile  a  source
if  there is no REL or if the existing REL is older than the
source (determined by date of last write).  This is  correct
when  all sources and RELs are in the same directory, but it
can prevent the sources in the private directory from  being
compiled,  taking the library REL instead, thus building the
program without the user's version of the source.

To correct this, the Version 5 EXEC makes a  further  check:
the  source  file  is  found  according  to  the  given file
specification.  If it is found in the  connected  directory,
then  the  lookup  for  the  REL file will be limited to the
first item on the search list (if any) for the  object  file
specification.   Thus,  in  the example above, if the source
                                                      Page 4


file is found in the connected directory, only the connected
directory  will  be  checked for the REL.  If the REL is not
found there, the source will be compiled and the REL put  in
the connected directory.  Any source found in <LIBRARY>, not
being the connected directory, will  allow  the  REL  to  be
taken  from  the  connected directory or <LIBRARY>.  As with
usual search list rules, the search will stop at  the  first
directory in which the REL file is found.

3.4 LOGIN.CMD and COMAND.CMD

V4.1 now  reads  LOGIN.CMD  before  COMAND.CMD.   Also,  the
CSAVE,   DEPOSIT,   EXAMINE,  SAVE,  SET-ADDRESS-BREAK,  SET
ENTRY-VECTOR, and START commands take  symbolic  expressions
in   addition   to  octal  numbers.   See  TOPS-20  Commands
Reference Manual.

3.5 Compiling Cobol Programs

The default compiler names for COBOL have  changed  in  this
EXEC.  The EXEC will look for CBL74.EXE when it is compiling
a file with type C74 or the /74-COBOL switch.  It will  look
for CBL68.EXE for file types of C68 or the /68-COBOL switch.
Finally, it will look for COBOL.EXE for types of CBL or  the
/COBOL switch.

4.0 SOFTWARE

4.1 Dumper

The version of DUMPER that is on the  distribution  tape  is
from  Version  4.  Due to some changes in the MACSYM macros,
this field-image version of DUMPER cannot be assembled  with
the  new version of MACSYM that is on this tape.  Therefore,
in order for DUMPER  version  4  to  be  re-built,  the  old
version  of  MACSYM  must be used.  Sites without this older
version  should  see  their  DEC  Software  Specialist   for
details.

4.2 Utilities

The Utilities included in this release are the same as those
included  in  Release  5  except  for  BOOT and CHECKD.  The
versions of these two programs are the same  as  Release  4,
including  bug fixes that have been discovered since Release
4 has been in the field.

4.3 TV

TV has three new commands that will fail under  4.1.   These
are WDELETE$, WFETCH$ and WSTORE$.  If desired, these may be
removed from TV by setting MAXSEC to 0 and recompiling TV.
                                                      Page 5


4.4 RUNOFF

The Tops-10 style RUNOFF that used to  be  supplied  on  the
installation  tape is not included in this release.  Instead
a Tops-20 style RUNOFF  is  included  on  this  tape.   This
RUNOFF  is  based on the DSR that was previously included on
the Tools tape.  This new RUNOFF has replaced both  DSR  and
the old RUNOFF.

4.5 LINK

The LINK that is on this tape is Version  5.1.   This  is  a
maintenance  version  of the 5.0 LINK that was sent out with
Release 5.0 of TOPS-20.  Note that the RMS on this tape  was
built  with  a  different LINK.  If you need to rebuild RMS,
you will have to use a previous version of LINK.

There are two new switches to LINK that will not work  under
this  release  because  they  deal  with extended addressing
features.  The two switches are:

                  /PVDATA      /PVBLOCK

5.0 EDIT NUMBERS

5.1 Exec and Monitor

Be aware that all patches that have  been  applied  to  this
Monitor  and  EXEC  have  been assigned decimal edit numbers
which  have  appeared  with  the  patches  that  have   been
published.  This is true even though the EXEC's INFO VERSION
command  outputs  edit  numbers  in  octal.   In  order   to
determine  if  a particular edit is included in this version
of the software, it is necessary to convert the edit  number
to  octal  and  compare it to the edit number printed out by
the EXEC.  If the edit number is less than or equal  to  the
edit  from  INFO  VERSION,  then the patch of interest is in
this version of the software.

6.0 FLOPPIES

6.1 Updating RSX20F from V14-45 to V14-45G

For those customers who have  a  KL  Model  A,  release  4.1
includes  V14-45G  of  RSX20F contained on floppies A and B.
Floppy C has not been included in  the  release  4.1  update
because  the  RSX20F.MAP  file that is on the floppy has not
changed  from  RSX20F  V14-45.   Version  V14-45G   is   the
maintenance  release RSX20F V14-45 with edits C, D, E, F and
G installed as patches (edits A and B were  not  applied  as
edit  A  does  not  currently apply to TOPS20 and edit B was
superseded by edit D).  The floppies also contain a  patched
PARSER.TSK that has edit A installed.

The  file  RSX20F.PCO  lists  the  edits  that   have   been
                                                      Page 6


installed, the following is a brief description of each:

Edit C fixes a problem  of  spurious  modem  interrupts  for
local  lines.   These  interrupts  have  been  the  cause of
severly degraded performance.  This will also prevent  error
logs  for  local lines reporting "Lost Interrupt" for DM11's
in SPEAR after front-end reloads.

Edit D fixes a hung line problem where  all  terminal  input
gets responded to with a <BELL>.

Edit E makes RSX20F more forgiving when  connecting  modems.
This  edit  removes  the  necessity  of  installing  the two
unsupported patches that have  been  widely  distributed  to
make modems work with V14-45.  In particular RSX20F will now
accept interrupts with secondary  receive  high  and  RSX20F
will check for carrier when a ring interrupt occurs.

Edit F fixes a problem of the CTY hanging  when  the  KLINIK
line  is  accessed  in  USER  mode  while enabled for REMOTE
access.

Edit G fixes a problem of RSX20F appearing to  lose  an  XON
from a terminal when running programs loaded with PA1050.

PARSER edit A fixes  the  EXAMINE  PI  command  so  that  it
returns valid data for PI GEN and PI HOLD.

If you are updating from a release prior to release  4,  you
MUST   follow   the  instructions  for  building  a  working
front-end file system as described in  Notebook  14  in  the
TOPS-20  Software  Installation  Guide,  Chapter 4, Creating
Front End File System.

To update your release 4 front end you can save  some  steps
and  install  V14-45G  by  doing  the  following with TOPS20
shutdown (via PAR>SHUT):

Put the V14-45G floppies A and B in the floppy drives 0  and
1 respectively.
Put 3 (switches 0 and 1) in the console  switches  and  push
ENABLE SWITCH.

        RSX-20F VB14-45G 14:48 23-Nov-82

        [SY0: redirected to DX0:]
        [DX0: mounted]
        [DX1: mounted]

        Type a "^\" (control backslash).

        PAR%mcr mou
        MOU>db0:
        MOU -- MOUNT COMPLETE
        MOU>^z
                                                      Page 7


        ^\
        PAR%mcr red
        RED>db0:=sy0:
        <will not return>
        ^\
        PAR%mcr pip
        PIP>DB0:RSX20F.SYS;*/DE
        PIP>DB0:RSX20F.SYS;1445=DX1:RSX20F.SYS
        PIP>DB0:PARSER.TSK;*/DE
        PIP>DB0:PARSER.TSK;2=DX1:PARSER.TSK
        PIP>^z
        ^\
        PAR%mcr sav
        SAV>sy0:/wb

        [DB0: dismounted]
        [DX0: dismounted]
        [DX1: dismounted]

        RSX-20F VB14-45G 14:48 23-Nov-82

        [SY0: redirected to DB0:]
        [DB0: mounted]


 7.0 RSX20F DEPOSIT COMMAND

 The RSX20F DEPOSIT command has changed its delimiter.   The
 old  delimiter was a ":".  The new delimiter is a "=".  The
 format of the DEPOSIT command is now as follows:

 DEPOSIT ADDR=DATA