Standard Software Release Notes
Software Release 9.0.020
Part No. 007759
Revision 01
This document describes the standard
version SR9.0.020 software. It gives
an overview of the software
enhancements and restrictions, the
procedures for installing the
software, and the latest changes to
documentation.
APOLLO COMPUTER INC.
330 Billerica Road
Chelmsford, Massachusetts 01824
c 1985 Apollo Computer Inc.
All rights reserved.
Printed in U.S.A.
First printing: July, 1985
Latest printing: August, 1985
This document was formatted using the FMT tool distributed with the DOMAIN
computer system.
APOLLO and DOMAIN are registered trademarks of Apollo Computer Inc.
AEGIS, DOMAIN/IX, DOMAIN/Dialogue, D3M, DPSS, DGR, GMR, GPR, and DSEE are
trademarks of Apollo Computer Inc.
Apollo Computer Inc. reserves the right to make changes in specifications and
other information contained in this publication without prior notice, and the
reader should, in all cases, consult Apollo Computer Inc. to determine
whether any such changes have been made.
THE TERMS AND CONDITIONS GOVERNING THE SALE OF APOLLO COMPUTER INC. HARDWARE
PRODUCTS AND THE LICENSING OF APOLLO COMPUTER INC. SOFTWARE CONSIST SOLELY OF
THOSE SET FORTH IN THE WRITTEN CONTRACTS BETWEEN APOLLO COMPUTER INC. AND ITS
CUSTOMERS. NO REPRESENTATION OR OTHER AFFIRMATION OF FACT CONTAINED IN THIS
PUBLICATION, INCLUDING BUT NOT LIMITED TO STATEMENTS REGARDING CAPACITY,
RESPONSE-TIME PERFORMANCE, SUITABILITY FOR USE OR PERFORMANCE OF PRODUCTS
DESCRIBED HEREIN SHALL BE DEEMED TO BE A WARRANTY BY APOLLO COMPUTER INC. FOR
ANY PURPOSE, OR GIVE RISE TO ANY LIABILITY BY APOLLO COMPUTER INC.
WHATSOEVER.
IN NO EVENT SHALL APOLLO COMPUTER INC. BE LIABLE FOR ANY INCIDENTAL,
INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING BUT NOT
LIMITED TO LOST PROFITS) ARISING OUT OF OR RELATING TO THIS PUBLICATION OR
THE INFORMATION CONTAINED IN IT, EVEN IF APOLLO COMPUTER INC. HAS BEEN
ADVISED, KNEW OR SHOULD HAVE KNOWN OF THE POSSIBILITY OF SUCH DAMAGES.
THE SOFTWARE PROGRAMS DESCRIBED IN THIS DOCUMENT ARE CONFIDENTIAL INFORMATION
AND PROPRIETARY PRODUCTS OF APOLLO COMPUTER INC. OR ITS LICENSORS.
Reader_Notice
The User hereby acknowledges and holds Apollo harmless from any loss or
damage which may result from certain incompatibilities which may arise when
floating-point applications are compiled with older versions of the C,
Fortran, or Pascal Compilers released prior to: (i) C-Rev 4.00 dated
7/8/85; (ii) Fortran-Rev. 8.28 dated 7/10/85; or (iii) Pascal-Rev 6.541
dated 7/03/85, and which are run on the DN330, DN560, or DSP90 or when the
older versions of these Compilers are run on other non-MC68020/MC68881 based
Apollo Systems using data files generated on the DN330, DN560, or DSP90 as
input.
Chapters 1 through 3 of this document reside online in the /doc directory.
Chapter 4 is only available in hard copy.
To print a copy of this document, use the PRF command with the -npag and -pr
options.
PRF <file_pathname> -PR <printer_name> -NPAG
iii
Contents
Section Page
CHAPTER 1 SOFTWARE RELEASE 9.0.020 OVERVIEW
1.1 HARDWARE PRODUCTS OVERVIEW. . . . . . . . . . . . 1-1
1.1.1 THE DN330 System . . . . . . . . . . . . . 1-1
1.1.2 The DN560 System . . . . . . . . . . . . . 1-1
1.1.3 The DSP90 System . . . . . . . . . . . . . 1-1
1.2 SR9.0.020 SOFTWARE OVERVIEW . . . . . . . . . . . 1-2
CHAPTER 2 INSTALLATION PROCEDURES
2.1 WHICH INSTALL PROCEDURE TO USE . . . . . . . . . 2-1
2.1.1 When to Use the Procedures for
Sytem Administrators . . . . . . . . . . . 2-1
2.1.2 When to Use the Procedures for Users . . . 2-2
2.2 CONVENTIONS AND TERMINOLOGY . . . . . . . . . . . 2-2
2.3 INSTALLATION PROCEDURES FOR SYSTEM ADMINISTRATORS 2-3
2.4 INSTALLATION PROCEDURES FOR USERS . . . . . . . . 2-6
CHAPTER 3 CHANGES TO DOCUMENTATION
3.1 CHANGES TO HARDWARE DOCUMENTATION DUE TO SR9.0.020 3-1
3.2 CHANGES TO SOFTWARE DOCUMENTATION DUE TO SR9.0.020 3-1
3.2.1 Changes to DOMAIN_System_Call_Reference
manual . . . . . . . . . . . . . . . . . . 3-2
3.2.2 Changes to Optional Software Products
Documentation . . . . . . . . . . . . . . 3-2
CHAPTER 4 BUGS AND BUG FIXES
Contents iv
Chapter 1
SR9.0.020 SOFTWARE RELEASE OVERVIEW
Software Release 9.0.020 contains the software to support the DN330, DN560,
and DSP90.
1.1 HARDWARE PRODUCTS OVERVIEW
The following sections offer a brief overview of the DN330, DN560, and the
DSP90 hardware products.
1.1.1 The DN330 System
The DN330 system consists of three major units: the CPU/monitor, the
keyboard, and the disk storage option. The CPU/monitor unit contains: the
display monitor (a 17 in. monochromatic display), the CPU power module (power
tray, cooling fans, keyboard plug board and power supply), the PCB cardcage,
and the network transceiver. The DN330 system uses the MC68020 CPU with the
MC68881 floating-point coprocessor on the CPU/Memory board. The keyboard is
low-profile with an optional mouse or touchpad pointing device. The disk
storage option contains either a 34 Mb or 70 Mb rigid disk unit; an optional
1.2 Mb floppy disk drive is also available.
1.1.2 The DN560 System
The DN560 consists of three major units. These are the cell, the monitor,
and the keyboard. The cell houses the processor cardcage, the optional mass
storage module, and the optional MULTIBUS module. The CPU board of the
processor module is based on the MC68020 and incorporates the MC68881
floating-point coprocessor. The DN560 uses a 19-inch high-resolution 1024 x
800 bit mapped color monitor. The keyboard is low-profile with an optional
mouse or touchpad pointing device.
1-1 SR9.0.020 Standard Release
1.1.3 The DSP90 System
The DSP90 system controls peripherals, such as storage module and fixed
storage disks, communication gateways, magnetic tape devices, line printers
and plotters, and low-speed serial devices. Unlike user nodes, such as the
DN330, and the DN560, the DSP90 does not have a display or keyboard.
Instead, you start processes and programs from a node with a keyboard and
display in the network.
The DSP90 package contains the central processing unit (CPU) based on the
MC68020 processor and MC68881 floating-point coprocessor, memory, and
hardware to support peripherals compatible with MULTIBUS standards.
1.2 SR9.0.020 SOFTWARE OVERVIEW
The SR9.0.020 software product is designed to accomodate the functions of the
MC68020 processor and MC68881 floating-point coprocessor. Since the
coprocessor is designed around the IEEE P754 (Draft 10.0) standard, it
introduces some issues of data compatibility with earlier equipment. In
general, the coprocessor is compatible with current Apollo floating-point
processing. However, incompatibilies do exist in certain ranges of value.
You must recompile all floating-point applications software that will run on
MC68020/MC68881 machines or on machines in networks with MC68020/MC68881
machines.
The IEEE P754 standard defines values for infinity and NAN (Not A Number) to
have the largest exponent. Earlier machines may generate and recognize these
values as legitimate floating-point numbers and not treat them in the manner
required by the standard.
Numbers with the smallest exponent present a problem. The IEEE P754 standard
provides for denormalized numbers and negative zero. These numbers are
generated by the MC68881 and are not handled properly by the current
compilers. Testing for zero and comparisons of numbers in these ranges may
fail. This problem may be observed both in sharing data between new and
earlier machines and, more commonly, in running floating-point programs that
were generated using earlier compilers.
New compilers have been built to do the comparisons which take into account
the new numbers that can be generated by the MC68881 coprocessor. You must
recompile all floating-point applications software that will run on
MC68020/MC68881 machines or on machines in networks with MC68020/MC68881
machines. The compilers are backward compatible. Code generated by the
compilers can run on earlier machines. We are also providing a user-callable
procedure to check floating-point values when data files must be stored on
removable media (refer to Section 3.2.1). If you are unable to recompile
because of a lack of source files, you are able avoid problems by first
executing the command "inlib /lib/syslib" in the process; this procedure
SR9.0.020 Standard Release 1-2
will, however, cause a decrease in performance compared to utilizing the
MC68881 coprocessor.
Assembly language programs that use SYSLIB calls to do comparisons will not
be affected. A SYSLIB.881 is provided and will automatically be loaded on
machines when the MC68881 coprocessor is present.
DOMAIN Pascal, C, and FORTRAN each support four new arguments to the -CPU
compiler option. These new arguments instruct the compiler to generate code
that will take full advantage of the new DSP90, DN330, and DN560 nodes.
1-3 SR9.0.020 Standard Release
CHAPTER 2
INSTALLATION PROCEDURES
This chapter explains how to install the SR9.0.020 software on nodes and
DOMAIN Server Processors that contain the 020 hardware. In order to install
this software, a node or DOMAIN server processor must be running the SR9.0
version of the operating system. Installation procedures for SR9.0 are
described in Chapter 2 of the Standard Software Release Document (Order No.
005809 Rev. 03).
Perform the 020 hardware installation before you install this software. The
hardware installation procedures are described in the following manuals:
Unpacking__and__Installing__the_DN3xx, Unpacking_and_Installing_the_DN5xx, and
Unpacking_and_Installing_the_DSP90.
2.1 WHICH INSTALL PROCEDURE TO USE
There are two installation procedures for the SR9.0.020 software, one for
system administrators and the other for users. Determine which one to use
before going any further.
2.1.1 When to Use the Procedures for System Administrators
o Use this procedure if you are a system administrator creating a
source area and designating the source area's installation program
as a protected subsystem. For more information about protected
subsystems, see Administering__Your__DOMAIN__System. You can use
cartridge tape, magnetic tape, a floppy disk, or an existing source
area.
o Use this procedure if you are a user who has the rights to delete and
change your system directories and you want to maintain those rights.
System directories include /SYS, /COM, /DOC, /DOMAIN_EXAMPLES,
/BSCOM, and /LIB. Use the ACL command to learn your rights; ACL is
documented in the DOMAIN_System_Command_Reference.
o Note that if you are a system administrator creating a protected
subsystem, you can install the software from a source area or into a
target area that is not at the entry directory (/) level. (Of
course, if you do not install the software at the entry directory
level, the node will not boot off of the new software; it will boot
from the software at the entry directory level.) You can install
various optional software products into a source area and then use
this source area to selectively install optional products on the
2-1 SR9.0.020 Release Notes
nodes in the network.
For example, first create a directory //node/sr9.0.020_source_area.
Then, when installing from tape or floppy into this area, use
//node/sr9.0.020_source_area as the target volume name. To load from
this area onto other nodes, use //node/sr9.0.020_source_area as the
source name.
2.1.2 When to Use the Procedures for Users
o Use this procedure if you are a user who does not have the rights to
delete and change your system directories. System directories
include /SYS, /COM, /DOC, /DOMAIN_EXAMPLES, /BSCOM, and /LIB. Use
the ACL command to learn your rights; ACL is documented in the
DOMAIN_System_Command_Reference.
o You can only use this procedure if your system administrator
establishes a source area and designates the installation program in
the source area as a protected subsystem. You can copy the optional
software from any release media, but you must use the INSTALL program
from the source area designated by your system administrator.
2.2 CONVENTIONS AND TERMINOLOGY
The terms and conventions used in these procedures are as follows:
o "Work node" is the node with a keyboard and display that you are
using to enter the commands to do the software installation.
o "Target volume" is the Winchester disk or mass storage disk on which
you are installing new software. You do not have to install the new
software into the target volume's entry directory (e.g., you are
creating a source area in a subdirectory on the target volume).
NOTE: When you are installing software to update a diskless node,
the target volume is the partner node's disk.
o "Target node" is the node or DOMAIN Server Processor (DSP) on which
you are installing or updating (i.e., the node that contains the
target volume). If the target node has a keyboard and a display
(i.e., it is not a DSP), the work node and the target node can be the
same.
SR9.0.020 Release Notes 2-2
o "Source" You must choose the source for your new software. If you
are installing the software using the procedure in the system
administrator phase, the source for the new software can be floppy
disks, magnetic tape, cartridge tape, or another node in the
network. If you are installing the software using the procedure in
the user phase, the source for the INSTALL program is the INSTALL
program marked as a protected subsystem by your system administrator.
You can get the rest of the SR9.0.020 software from the distribution
media.
The "source volume" is a Winchester disk or mass storage disk that
has already been updated with the new software. A "source node" is a
node in the network that has already been updated with the new
software (i.e., the node that contains the source volume).
NOTE: Ensure that the source volume contains the appropriate
optional software for the target node.
o A "secure network" is a network with a registry of user accounts and
access control of system software; an "open network" does not contain
user accounts and access control of system software.
o Angle brackets ( < > ) enclose the name of a key on the keyboard.
2.3 INSTALLATION PROCEDURES FOR SYSTEM ADMINISTRATORS
The software takes 1600 blocks. Before you begin the installation, use the
LVOLFS command to insure that you have enough disk space.
Use these procedures if you are a user who has rights to modify your system
directories, or if you are a system administrator establishing a protected
subsystem. If you establish the protected subsystem, then users can install
this software on their nodes without logging in as a system
administrator.
If you are a system administrator establishing a protected subsystem, then
create a directory which will contain the INSTALL directory and the software
before you begin to install software. In the install procedures, you must
give this directory's pathname when you are asked for the target_volume. You
must also give the same pathname when you are asked to name a source area for
the protected subsystem.
1) Log in to a work node either as a SYS_ADMIN or (if you have rights to
modify your system directories) as a user. Start a Shell on the work
node. (This can be the target node.)
2) If you are installing the optional software over the network, then
skip step 2. If you are using a tape cartridge, a magnetic tape, or a
2-3 SR9.0.020 Release Notes
floppy disk to install the optional software, then perform step 2.
a. Set your working directory to //target_volume.
$ WD //target_volume <RETURN>
b. Insert the media into the drive and enter the RBAK command
shown below. If you are using a tape cartridge, use the CT
option shown in the example. If you are using a magnetic
tape, use the M0 (Mzero) option instead of CT. If you are
using a floppy, use the F0 (Fzero) option instead of CT.
$ RBAK -DEV CT -F 1 INSTALL -AS INSTALL -L -MS -FORCE -SACL
<RETURN>
$ RBAK -DEV M0 -F 1 INSTALL -AS INSTALL -L -MS -FORCE -SACL
<RETURN>
$ RBAK -DEV F0 -F 1 INSTALL -AS INSTALL -L -MS -FORCE -SACL
<RETURN>
c. Set your working directory to //target_volume/INSTALL:
$ WD //target_volume/INSTALL <RETURN>
3) If you are installing the software from a cartridge tape, a magnetic
tape or a floppy, then skip this step. If you are installing the
software over the network, then perform this step. Set your working
directory to //source/INSTALL.
$ WD //source/INSTALL <RETURN>
4) Skip this step if you are logged in as a user. Perform this step if
you are a system administrator creating a protected subsystem. Type
INIT_SOURCE. You are then prompted to give the pathname of the
source area.
$ INIT_SOURCE
5) Execute the INSTALL Shell script and follow the prompts:
$ INSTALL <RETURN>
6) The program prompts you to enter an installation type. Please enter
SR9.0.020 and press <RETURN>.
SR9.0.020 Release Notes 2-4
Software Installation Types are:
STD -- Install SR9 standard software
RESTART -- Restart the software installation.
OPT -- Install optional software (i.e. Pascal, Fortran)
ACL -- Set ACLs for existing software
CLEANUP -- Run the Cleanup Procedure for ADD MODE installations
DOMAIN_IX -- Install the DOMAIN/IX software
SR9.0.020 -- Install SR9.0.020 support software
Please Enter Installation Type:
7) The procedure then asks if you have adequate rights to modify system
directories. You must answer yes to this question.
You must have sufficient rights to modify system directories
on the target node for the installation procedure to
work properly.
You are logged in as:
person.project.organization.node_number node_name
Do you have adequate rights ?
Please enter response. (yes or no):
8) You are then prompted for the name of the target volume. Enter the
name of the target volume. (If you are a system administrator, you
must enter the pathname of the protected subsystem that you just
established and press <RETURN>.)
** SR9.0.020 Software Installation **
Please enter the name of the TARGET volume that the SR9.0.020
Software will be installed on. (e.g. '//UPDATE_ME'):
Enter TARGET Volume:
9) The procedure prompts you for the name of the source media. Enter it
and press <RETURN>.
Source MEDIA is one of:
CTAPE -- SR9.0.020 Release Cartridge Tape
FLOPPY -- SR9.0.020 Release Floppy Disk
MTAPE -- SR9.0.020 Release Magnetic Tape
NET -- A volume on the network with SR9.0.020 software
QUIT -- Exit from the installation
2-5 SR9.0.020 Release Notes
Enter Source Media:
10) If you specified NET, the procedure prompts you for the source
volume. Enter the source volume and press <RETURN>.
Enter the name of the source volume from which to copy the
SR9 Optional Software (e.g., '//GTI):
Enter Source Volume or type 'quit':
11) The procedure installs the software. When it is finished, check the
transcript pad to verify that all the files were copied.
INSTALLING SR9.0.020 SOFTWARE on target_volume
If you are installing with floppy disks, the following message
appears:
Depending on your node's configuration, you
may not need to insert every floppy. Therefore,
you will only be prompted to insert floppies
which your node needs.
12) The procedure instructs you to shut down the target node and reset
it. Use the Display Manager SHUT command to shut down the target
node.
<cmd> shut
13) After the SUCCESSFUL SHUTDOWN message and the ">" prompt appears,
reboot the node by typing the following at the prompt: RE <RETURN>
<RETURN> EX AEGIS <RETURN>.
> RE <RETURN>
> <RETURN>
MD REV xx/xx/xx
> EX AEGIS <RETURN>
You are finished with the installation.
2.4 INSTALLATION PROCEDURES FOR USERS
The software takes 1600 blocks. Before you begin the installation, use the
LVOLFS command to insure that you have enough disk space.
Use these procedures if you are a user installing optional software. Ask
your system administrator for the name of the source area for the software.
SR9.0.020 Release Notes 2-6
1) Log in to a work node as yourself. Start a Shell on the work node.
(This can be the target node.)
2) Set your working directory to //source/INSTALL.
$ WD //source/INSTALL <RETURN>
3) Execute the INSTALL Shell script and follow the prompts. Enter:
$ INSTALL <RETURN>
4) The program prompts you to enter an installation type. Enter
SR9.0.020 and press <RETURN>.
Software Installation Types are:
STD -- Install SR9 standard software
RESTART -- Restart the software installation.
OPT -- Install optional software (i.e. Pascal, Fortran)
ACL -- Set ACLs for existing software
CLEANUP -- Run the Cleanup Procedure for ADD MODE installations
DOMAIN_IX -- Install the DOMAIN/IX software
SR9.0.020 -- Install SR9.0.020 support software
Please Enter Installation Type:
5) The procedure then asks if you have adequate rights to modify system
directories. You must answer no to this question.)
You must have sufficient rights to modify system directories
on the target node for the installation procedure to
work properly.
You are logged in as:
person.project.organization.node_number node_name
Do you have adequate rights ?
Please enter response. (yes or no):
6) You are then prompted for the name of the target volume. Enter it
and press <RETURN>.
** SR9.0.020 Software Installation **
Please enter the name of the TARGET volume that the SR9.0.020 Optional
2-7 SR9.0.020 Release Notes
Software will be installed on. (e.g. '//UPDATE_ME'):
Enter TARGET Volume:
7) The procedure prompts you for the name of the source media. Enter it
and press <RETURN>.
Source MEDIA is one of:
CTAPE -- SR9.0.020 Release Cartridge Tape
FLOPPY -- SR9.0.020 Release Floppy Disk
MTAPE -- SR9.0.020 Release Magnetic Tape
NET -- A volume on the network with SR9.0.020 software
QUIT -- Exit from the installation
Enter Source Media:
8) The procedure installs the software. When it is finished, check the
transcript pad to verify that all the files were copied.
INSTALLING SR9.0.020 SOFTWARE on target_volume
If you are installing with floppy disks, the following message
appears:
Depending on your node's configuration, you
may not need to insert every floppy. Therefore,
you will only be prompted to insert floppies
which your node needs.
9) The procedure instructs you to shut down the target node and reboot
it. Use the Display Manager SHUT command to shut down the target
node.
<cmd> shut
10) After the SUCCESSFUL SHUTDOWN message and the ">" prompt appears,
reboot the node by typing the following at the prompt: RE <RETURN>
<RETURN> EX AEGIS <RETURN>.
> RE <RETURN>
> <RETURN>
MD REV xx/xx/xx
> EX AEGIS <RETURN>
You are finished with the installation.
SR9.0.020 Release Notes 2-8
CHAPTER 3
CHANGES TO DOCUMENTATION
3.1 CHANGES TO HARDWARE DOCUMENTATION DUE TO SR9.0.020
The following is a list of the documents which have been changed
or created to support the introduction of the DN330, DN560, and
DSP90.
o Unpacking_and_Installing_the_DN3xx
o Operating_the_DN3xx
o Servicing_the_DN3xx
o Unpacking_and_Installing_the_DN5xx
o Operating_the_DN5xx/RM550
o Servicing_the_DN5xx/RM550
o Unpacking_and_Installing_the_DSP80A/DSP90
o Operating_the_DSP80A/DSP90
o Servicing_the_DSP80A/DSP90
3.2 CHANGES TO SOFTWARE DOCUMENTATION DUE TO SR9.0.020
The following sections describe the changes to software
documentation due to the release of SR9.0.020. Please note that
you must recompile all floating-point applications.
3-1 SR9.0.020 Standard Release
3.2.1 Changes to DOMAIN_System_Call_Reference manual.
This section describes the syntax of two FPP calls that should
be added to the DOMAIN_System_Call_Reference manual.
FPP_$CLASS_SP -- to return a floating-point value.
Takes a 4-byte real as an argument.
FPP_$CLASS_DP -- to return a floating-point value.
Takes an 8-byte real (double precision) as an argument.
Both procedures return a 2-byte integer which will be one of the following:
FPP_$SIG_NAN - It's a signalling NAN
FPP_$NAN - It's a quiet (non-signalling) NAN
FPP_$NEG_INFINITY - It's a negative infinity
FPP_$NEG_NORM_NONZERO - It's a negative normalized number (but not zero)
FPP_$NEG_DENORM - It's a negative denormalized number
FPP_$NEG_ZERO - It's a negative zero
FPP_$POS_ZERO - It's a positive zero
FPP_$POS_DENORM - It's a positive denormalized number
FPP_$POS NORM_NONZERO - It's a positive normalized number (but not zero)
FPP_$POS_INFINITY - It's a positive infinity
The above are defined in the following include files:
/sys/ins/fpp1.ins.c
/sys/ins/fpp1.ins.ftn
/sys/ins/fpp1.ins pas
3.2.2 Changes to Optional Software Products Documentation
The following list contains the names of documents which must be
updated to reflect the changes required for the optional SR9.0.020
software products. Refer to the Optional Software Release package
for the specific changes needed.
o DOMAIN_Pascal_Language_Reference
o DOMAIN_C_Language_Reference
o DOMAIN_FORTRAN_User's_Guide
SR9.0.020 Standard Release 3-2
CHAPTER 4
BUGS AND BUG FIXES
4.1 Commands Not Supported
The following commands are not supported by the MC68020 or MC68881
instruction sets.
o The Debugger DB command -- not a valid command.
o The Shell command PST -- returns an invalid program
counter value if the PST command is given while the
MC68881 coprocessor is executing an instruction.
4-1 SR9.0.020 Standard Release