Google
 

Trailing-Edge - PDP-10 Archives - BB-X140B-BB_1986 - 10,7/703mon/703.bwr
There are 2 other files named 703.bwr in the archive. Click here to see a list.


          BEWARE FILE FOR TOPS-10 VERSION 7.03 DISTRIBUTION





                             Revision:  7

                         Date:  15 April 1986

























COPYRIGHT  (c)  DIGITAL  EQUIPMENT  CORPORATION  1986.    ALL   RIGHTS
RESERVED.


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 TOPS-10 VERSION 7.03 DISTRIBUTION               Page 2


                          TABLE OF CONTENTS


     This file  contains  the  following  information  concerning  the
     TOPS-10 Version 7.03 monitor release:


     1.0  Introduction


     2.0  List of files included in the 7.03 release


     3.0  Installation instructions for 7.03


     4.0  Warnings of known deficiences in 7.03


     5.0  Important differences between 7.02 and 7.03


     6.0  Dependencies


     7.0  Unbundled software
BEWARE FILE FOR TOPS-10 VERSION 7.03 DISTRIBUTION               Page 3


1.0  INTRODUCTION

The major reason for release 7.03 of the TOPS-10 operating  system  is
to  support  the CI20/HSC50 disk subsystem, to implement the corporate
networking protocol DECnet-10 Phase IV for Ethernet communication, and
to  implement  a  number  of security enhancements, including password
encryption.   Additionally,  7.03  implements  support  for  user-mode
extended  addressing,  alternate  contexts  (PUSH/POP),  LAT  terminal
concentrators,  CTERM  (the   corporate   network   virtual   terminal
protocol),  and  a number of minor enhancements.  Installation of 7.03
is very similar to the installation of 7.02.  Also, the  7.03  package
contains  GALAXY  5.1.   The  installation  of  these new products and
ramifications with respect to dropping back to 7.02 are  discussed  in
the section on operator differences below.
BEWARE FILE FOR TOPS-10 VERSION 7.03 DISTRIBUTION               Page 4


2.0  LIST OF FILES INCLUDED IN 7.03

The 7.03 release consists of the following media:

     1.  The distribution tape with 2 save sets:

         A.  Monitor files

         B.  ANF10 network files

     2.  MPE - (CPNSER) - an unbundled product

     3.  DECnet-10 - an unbundled product

     4.  The appropriate bootable tape, floppies, or DECtapes for your
         configuration

     5.  The full DEC-supported CUSP distribution (2 tapes)

     6.  The customer-supported tape with 2 save sets

         A.  Customer-supported utilities

         B.  Customer-supported monitor files


     7.  Tools tape
BEWARE FILE FOR TOPS-10 VERSION 7.03 DISTRIBUTION               Page 5


2.1  The Following New Utilities Are Required With 7.03:


     BOOT         V3   - Replaces MONBTS, contains various microcodes.

     DAEMON       V22  - Supports error reporting for the CI and NI.  

     DDT          V44  - Required for multi-section monitor patching.

     FILDAE       V4   - Required to support PUSH/POP messages.

     KNILDR       V1   - Required to load the NIA20 microprocessor  on
                         a KL10.

     LINK         V6   - Required to build the multi-section monitor.

     MACRO        V53B - Required  to   assemble   the   multi-section
                         monitor.

     MONGEN       V57  - Required to create configuration files.

     SPEAR BASIC  V2   - Required for  hardware  and  software  report
                         generation.

     UUOSYM       V17  - Updated with 7.03 monitor symbols.



2.2  Documentation Files Found On The Monitor Save Set


       STOPCD.MEM    Stopcodes

       MONTAB.MEM    Monitor Tables



2.3  This Documentation File Can Be Found On The ANF10 Save Set:


       DN8TSK.MEM    DN87 Specification
BEWARE FILE FOR TOPS-10 VERSION 7.03 DISTRIBUTION               Page 6


3.0  INSTALLATION INSTRUCTIONS

For normal installation, refer to the  TOPS-10  Software  Installation
Guide.

For sites that have ANF10 networks, read and follow the TOPS-10  ANF10
Networks Software Installation Guide.

For sites that have DECnet-10 networks, read and  follow  the  TOPS-10
DECnet and PSI Installation Guide.
BEWARE FILE FOR TOPS-10 VERSION 7.03 DISTRIBUTION               Page 7


4.0  WARNINGS OF KNOWN DEFICIENCIES IN 7.03

As a convenience to customers, there is a third saveset on the monitor
distribution  tape which contains .COR files for PCO(s) to the monitor
which represent fixes to problem(s) discovered after the final package
was  complete.   This  saveset is called "7.03 Monitor .COR files" and
the SFD will be DSKB:[10,7,COR].   The  files  in  this  area  can  be
restored  to the [10,7,703mon] area or wherever normal monitor sources
are kept.  Also in this area on the tape  is  an  unsupported  utility
called  UPDATE.EXE  which  takes  the  .COR files, applies them to the
sources which have been restored from this monitor  distribution  tape
and  produces  a  newly  updated  source  file with which to build the
monitor.  This file can be restored to the build area and/or SYS:.

To run UPDATE:

*****The current path should be in the build or source  area  at  this
time.*****

.r update
*DSK:.MAC = device name:filename.mac[ppn],device name:filename.cor[ppn]

This produces a new filename.mac in the current  area.   Device  names
and  ppn are only necessary for the .COR file if the .COR file is kept
in a separate area.  Pathalogical names can also be used if desired.
BEWARE FILE FOR TOPS-10 VERSION 7.03 DISTRIBUTION               Page 8


5.0  IMPORTANT DIFFERENCES BETWEEN 7.02 AND 7.03

5.1  Differences Important To System Programmers

5.1.1  Required Software/Firmware - Version  2.0(411)  of   the   KL10
microcode  must  be  used  with  7.03.   Version  2.0(130) of the KS10
microcode is required.  The CI20 microcode version  number  is  1(711)
and  the  NIA20  microcode  version  number is 1(167).  Version 250 or
later of CRONIC (the HSC50 microcode) is also required.

LINK version 6 MUST be used to link this monitor;  (E)DDT  Version  44
MUST  be  used with this monitor.  A KL monitor with DECnet configured
now requires a minimum of 768K of physical memory.  Please  note  that
the  load  order of monitor modules is very important.  DECnet modules
MUST be loaded  immediately  following  the  COMMON  modules  (COMMON,
COMDEV, COMNET, and COMMOD) and if the system contains the MPE option,
CPNSER must be loaded immediately following DECnet.


5.1.2 PSECTed Monitor  -  The  7.03  monitor  sources  use  PSECTs  to
increase  the  amount  of  virtual  address  space  available  in  the
monitor's section 0/1 addressing space.   All  DECnet  code  has  been
moved  to  section 2 in the "sky high" segment (PSECT).  SAB rings and
swapping SATs which occupied this space in 7.02  have  been  moved  to
section 7.

Because of PSECT usage in the monitor, some local edits in the  common
modules (COMMON, COMDEV, COMNET, and COMMOD) may not compile correctly
due to forward referencing a  symbol  in  one  PSECT  which  is  later
defined  in  another  PSECT.   The  following example illustrates this
problem:

             $HIGH
     CPOPJ:: POPJ    P,
             . . .
             PUSHJ   P,PPDTIC
             . . .
             $ABS
     IFE M.SCA,<
     XP      PPDTIC,CPOPJ
     >

The PUSHJ to PPDTIC is an  illegal  forward  reference  in  a  PSECTed
program.   MACRO  V53B will flag such references with either an "E" or
"U" error and the message "<symbol>  NOT  FULLY  DEFINED  IN  PASS  1,
DEFINED  AS  IF  EXTERNAL".  The solution is to move the definition of
PPDTIC into the same PSECT as the reference.
BEWARE FILE FOR TOPS-10 VERSION 7.03 DISTRIBUTION               Page 9


5.1.2  Packaging Changes - The contents of  the  RP20  tape  (formally
unbundled)  has  been  moved  to  the  BOOT SFD on the CUSP tape.  The
monitor tape, the DECnet tape, the CUSP tape, and the tools  tape  are
now in non-interchange format.



5.1.3  DAEMON - The DAEMON on the 7.03 distribution tape will only run
with 7.03, that is it will not function correctly with 7.02 or earlier
monitors.  The 7.02 version of DAEMON should be renamed to  DAE702.EXE
on  SYS  as  part  of the 7.03 installation.  When the 7.03 version of
DAEMON is started, it determines whether the monitor is 7.03  and,  if
not, causes DAE702 to be started.



5.1.4  MONBTS - The functions of  the  MONBTS  module  have  now  been
implemented  in  BOOT.   BOOT can now be configured to contain various
microcodes and sites will probably want to configure  BOOT  with  only
those  microcodes  necessary  for the devices that they have.  Because
BOOT does contain microcodes, the loading procedure  executed  by  KLI
takes  significantly  longer  with 7.03 than with 7.02.  Although BOOT
may  be  configured  to  include  the  NIA20  microcode,  the  monitor
currently  does  not  have  the capability of loading the NIA20.  This
functionality is handled by the KNILDR  program.   There  is  still  a
module  called  MONBTS.   It contains code that interfaces between the
monitor and the bootstrap.



5.1.5  MONGEN Dialogue - There is no longer a TTYGEN  portion  in  the
MONGEN  dialog  (or  a  TTYCNF.MAC file).  The only relevant questions
remaining (OPR terminal, and dataset lines) have been moved to HDWGEN.



5.1.6  MONGEN For Unsupported Configurations - MONGEN     has     been
modified   to   allow  the  system  administrator  to  select  various
unsupported (customer supported) options.  See the MONGEN help  output
or   consult   the   MONGEN  documentation  in  the  TOPS-10  Software
Installation Guide.



5.1.7  File Daemon - Two new monitor messages to the File Daemon  have
been  added.   They  are  the  Suspend  (or  PUSH) and Resume (or POP)
messages.  FILDAE edit 44 or later (or a local FILDAE  with  similarly
updated dispatching code) is required under 7.03 monitors.
BEWARE FILE FOR TOPS-10 VERSION 7.03 DISTRIBUTION              Page 10


5.1.8  Monitor Free Core - To make it easier to increase the amount of
monitor  free  core,  a  MONGENable  symbol "EXTRAW" has been added to
define the amount of extra words of general-purpose section 0  monitor
free core to allocate (used by facilities such as ANF network service,
ENQ/DEQ, IPCF, PSI, etc.).

Multiple processor KL-10 configurations may not be able  to  configure
enough  4-word core to run the full complement of configured jobs.  If
your site is running low on 4-word core, and you have already  defined
the  MONGEN  parameter  "EXTRAW", the adjustments to the origin of the
monitor's  high  segment  described  herein  may  help  alleviate  the
problem.   Numbers  are  in  octal  unless otherwise specified.  It is
assumed you have a working knowledge of FILDDT.

Before any adjustments can be made you must first determine the amount
of  free space following the end of the monitor's high segment and the
data structures created by AUTCON.  Make sure all disk and tape drives
which  may  be  accessible to the system are powered on so the monitor
has configured them via AUTCON at system start-up.  If  you  find  any
device  which was not powered on you must reload the monitor after the
device is powered on, so AUTCON will build  data  structures  for  all
devices  in  your configuration.  Do not use the AUTOCONFIGURE command
of OPR as this will build the data structures in the wrong section  of
memory.

Run your monitor-specific FILDDT  and  examine  the  running  monitor.
Examine  the  contents  of the location "MONVFF".  MONVFF contains the
first free address following the monitor's high segment  and  AUTCON's
data  structures.   This  value  must  be  subtracted  from 1000000 to
determine the maximum number of free  words  which  may  be  used  for
4-word  core.   For  example,  if MONVFF contained 712000, subtracting
712000 from 1000000 gives 66000 words available.  To be extra safe and
allow  for  the  addition of future hardware, subtract 4000 words from
the result of the  above  computation.   In  our  example,  the  final
adjustment amount would be 62000 words.

Now you must edit S.MAC to change the definition of two symbols  which
define  the origin of the monitor's high segment and the origin of the
per-process space ("funny space").  Within an IFN  FTXMON  conditional
you will see the definition:

     FYSORG==324000

Change this definition to:

     FYSORG==324000+adjfct

where "adjfct" is the adjustment factor you have determined.   In  our
example, this would be:

     FYSORG==324000+62000

Similarly,  within  an  IFN  FTXMON  conditional  you  will  see   the
definition:
BEWARE FILE FOR TOPS-10 VERSION 7.03 DISTRIBUTION              Page 11


     HIORG==364000

Change this definition to:

     HIORG==364000+adjfct

where "adjfct" is the adjustment factor you have  determined.   Again,
in our example this would be:

     HIORG==364000+62000

After editing S.MAC you MUST re-compile EVERY monitor module  to  make
sure  the  new  high segment origin will be used.  After re-compiling,
re-link your monitor and test.  You should notice MONVFF  much  closer
to 1000000, indicating your adjustment.



5.1.9  Six Character STOPCD Names, STOPCD Macro - 
There are four major changes:
1) The code generated by the STOPCD macro is now
               XCT [
   name::                     PUSHJ P,DIE
                              SIXBIT /name/
                              XWD bits,cont addr
                              EXP typeout address
                   ]

2) DIE handles the above format. DIE also now has an entry point PERISH
   which handles the above format with a XPCW .CPSPC instead of PUSHJ DIE.
   This entry point could be used in cases where the stack pointer is
   suspect.

3) %SYSPC (prev. name,,pc) now contains a fullword PC. %SYSCD (new entry in
   .GTSYS) contains the full stopcode name.

4) Location CRSWHY is now a fullword stopcode name, and the date/time/name
   checksum has moved to the right half of CRSCHK in location 26.



5.1.10  User-defined STOPCDs - A continuation address of ".+1" in  the
STOPCD  macro is no longer special-cased in 7.03.  Therefore, if users
have added any STOPCDs with a ".+1" continuation address in a literal,
execution won't continue at the "expected" address in 7.03.



5.1.11  Monitor Debugging - If the monitor is loaded with EDDT  and  a
STOPCD  occurs, EDDT will be entered via an XCT .CPDDT (normally a JSR
$0BPT##), which means that you can now say $P  to  continue  from  the
STOPCD.
BEWARE FILE FOR TOPS-10 VERSION 7.03 DISTRIBUTION              Page 12


5.1.12  Command Abbreviations - The uniqueness  bits  in  the  command
definition  tables (UNIQ.1, UNIQ.2, etc.) now specify the exact length
of command uniqueness and not its length and all those  greater.   For
example,  this  allows  CO to be a unique abbreviation for the CONTEXT
command while CON is a unique abbreviation for the  CONTINUE  command.
The  system  programmer  should keep this change in mind when defining
site specific commands with MONGEN.



5.1.13  DN8X Sources - The DNCDDH and DNDM11 modules are now  defunct,
and are superseded by (and included within) the DNDH11 module.  Anyone
using DH11-based datasets or DDCMP links should change  their  control
files  accordingly  (i.e., remove the DNDM11 and DNCDDH modules).  The
DNCDDH  and  DNDM11  modules  are  still  physically  extant,  and  if
assembled  will  PRINTX  that they shouldn't be assembled anymore (but
will not error/abort the batch job).



5.1.14  DN8X Assembly Options - The  asynchronous  line  configuration
instructions are as follows:

DH11-based systems use  the  DHCNFG  and  DHUSE  macros  as  currently
documented,  with  the exception that the arguments to the DHUSE macro
are ***NOT*** to be enclosed in parentheses as shown in the examples.

DZ11-based systems no longer use  the  DHCNFG  and  DHUSE  macros  but
instead  use the DZCNFG and DZUSE macros, which are invoked exactly as
the DHCNFG macro.

DN20 systems now assume DZ11s and TTY support  as  the  default  case.
(This is easy to change back, but the majority of DN20s are configured
with TTYs.)

While  it  was  recommended  that  the  TTYN  parameter  be   supplied
explicitly  in  the DN8X control file, that parameter is now correctly
defined by the DHUSE/DZUSE macros.

*ALL* arguments to the DHUSE/DZUSE macros must be  supplied  correctly
(and in particular - for emphasis - NO PARENTHESES!!!).

To suppress TTYs, set FTDH11=0 or FTDZ11=0, depending on the class  of
-11  (DN8?   or  DN2?   respectively).   To force TTY support, set the
corresponding symbol non-zero and invoke the  appropriate  D?CNFG  and
D?USE macros.

The DZSPD macro has been added to correspond to the DHSPD  macro,  for
DZ11-based systems.

Two new assembly macros are added - DHSET and  DZSET,  to  be  invoked
within  the DHCNFG or DZCNFG macros respectively.  DHSET/DZSET must be
invoked before the DHUSE/DZUSE macros.   Each  takes  four  arguments:
physical  line number, line class ("TTY", "RDA", etc.), receive speed,
and transmit speed.  These macros look like DHSPD but use the physical
BEWARE FILE FOR TOPS-10 VERSION 7.03 DISTRIBUTION              Page 13


line  rather  than logical line within a specified class of lines, and
set the class of the line.

The FT.RDE assembly parameter has been removed.  Use only  FT.RDM  for
multi-point  DDCMP  RDX  device  support, or FT.RDP for point-to-point
DDCMP RDX device support.  FT.RDA continues to be used for ASCII RDA.



5.1.15  GALAXY 5.1 And 7.02 - There are two PCOs which must be applied
to  7.02  in  order  to run GALAXY version 5.1 and the 7.03 accounting
system under 7.02.  PCO 10-702-197 corrects problems  in  IPCSER  with
the  QUEUE.  UUO.   PCO  10-702-200  causes  the  monitor's LPT device
drivers to correctly set the printer class.



5.1.16  Private File Structures - GALAXY will no longer allow  a  user
to  MOUNT  a  private file structure, unless that user has a quota (it
may be zero) on that structure or  the  user  is  the  owner  of  that
structure.



5.1.17  Patching 7.03 Under 7.02 - FILDDT must be used to patch a 7.03
monitor   under   7.02.    A  7.02  monitor  will  be  unable  to  GET
multi-section .EXE files, hence EDDT cannot be used for patching under
7.02.



5.2  Differences Important To The User

5.2.1  TTY IGNORE - Occasionally users type "TTY I" when  they  really
meant  to type "I TTY".  Because the result of "TTY I" is to zero baud
the user's line, making the terminal useless  to  the  user,  the  TTY
IGNORE  command  may no longer be abbreviated.  To achieve the desired
affect, the entire command must be typed.



5.2.2  Terminal "APC" Code - In earlier monitors, the  terminal  "APC"
code  for  local  (RSX-20F,  KS10/DZ11)  dataset terminals always said
"hardwired" (.TOHWD) rather than  "dataset"  (.TODSD)  terminal.   The
correct value is returned in 7.03.



5.2.3  ENQC. Status - We have changed the behavior of the ENQC. status
function  in response to an SPR on 7.02.  The left half of word .ENQCI
(symbol EQ.CIQ) was documented as returning  the  number  of  requests
queued.   The  actual  value being returned was always zero, no matter
how many requests were queued for the resource.  Also, this definition
of EQ.CIQ was inconsistent with the TOPS-20 ENQC% JSYS.
BEWARE FILE FOR TOPS-10 VERSION 7.03 DISTRIBUTION              Page 14


The ENQC. status function .EQNCS  now  returns  in  field  EQ.CIQ  the
number  of  users  sharing the resource.  We believe this change to be
minor, as no DIGITAL-written or  DIGITAL-supported  program  uses  the
ENQC.  status function, and no run-time library, including LIBOL, uses
the ENQC. status function.

However, if your site does  have  locally-written  MACRO  programs  or
subroutines  that  use  the ENQC. status function, you should check to
make sure that those programs or subroutines do not  depend  on  field
EQ.CIQ  containing the number of requests queued for the resource.  If
you find such a program or subroutine, please change it, since  EQ.CIQ
never returned a valid number in the first place.



5.2.4  Limits/guidelines - If  a  non-zero  value   for   a   physical
limit/guideline  is  supplied which is less than 4P, the monitor makes
the limit/guideline 4P since  this  is  the  minimum  amount  of  core
required to GET/RUN a program.



5.2.5  Monitor Symbol Table - Any  customer  programs  that  read  the
monitor .EXE file to extract information from the symbol table must be
changed to handle the new extended symbol table format.  The format of
the  extended  symbol table is described in UUOSYM.MAC (see the symbol
.SYCNT).  Any customer programs that use the SNUP package will need to
be  re-linked  with  the  new  SNUP.REL which understands standard and
extended symbol tables.



5.2.6  Monitor AC Definitions - The  AC   assignments   have   changed
somewhat.   Although  there are no changes in the AC names themselves,
the assignments are different (e.g.  T1  is  now  AC  2,  etc.).   Any
program  using  the SNUP library should be re-compiled and linked with
the new SNUP.REL.



5.3  Differences Important To The Operator

5.3.1  Dropping Back To 7.02 - The   major   operational    difference
between  7.02  and  7.03  on  a  KL10  processor is the fact that 7.03
requires a new microcode and bootstrap (BOOT).   7.02  will  run  with
7.03  KL  microcode,  bootstrap, and V15-50 RSX-20F provided Autopatch
tape #9 has been applied to 7.02.

If Autopatch tape #9 hasn't been installed, you may use the  following
dropback procedures.  To facilitate dropping back, KLI will record the
names of the default files that the  microcode  and  BOOT  are  to  be
loaded  from,  in its configuration file.  Rename the 7.02 BOOT.EXB to
be OBOOT.EXB;2.  Install the 7.03 microcode  as  KLX.MCB;411  and  the
7.03 BOOT as BOOT.EXB;3.  The RSX20F file system will now contain:
BEWARE FILE FOR TOPS-10 VERSION 7.03 DISTRIBUTION              Page 15


               KLX.MCB;411    for use with 7.03 and 7.02,
               BOOT.EXB;3     and

               UB.MCB;400     for use with 7.02 only
               OBOOT.EXB;2

To run 7.03, RSX20F should be rebooted;  the operator  should  respond
'YES'  to  the  KLI  enter  dialog  question.   When  KLI  asks if the
microcode  should  be  reloaded,  the  operator   should   type   'YES
KLX.MCB;411'.   When  KLI  asks  load  bootstrap,  the operator should
respond 'BOOT.EXB;3'.  This procedure will cause  the  7.03  microcode
and  bootstrap  to be loaded.  If the configuration file is written, a
<CR> or 'NO' response to the KLI enter dialog question will  load  the
microcode   and   bootstrap  specified  in  the  most  recent  dialog.
Likewise, to run 7.02, the  operator  should  go  through  the  dialog
specifying the 7.02 microcode and bootstrap.

This monitor should be assembled by MACRO V53B and loaded by  LINK  V6
with DDT V44, which are supplied on the CUSP tape.



6.0  UNBUNDLED SOFTWARE

     MPE (CPNSER) - Multi-CPU interface.

     DECnet-10 - Support software for DECnet-10 Version 4.


[End of 703.BWR]