Domain/Ada(tm) Software Release Document
August, 1987
Software Release 1.0
Part No. 008916
Revision 00
This document describes Domain/Ada.
The Domain/Ada Development System is
a toolset for developing Ada(r)
programs.
APOLLO COMPUTER INC.
330 Billerica Road
Chelmsford, Massachusetts 01824
Copyright c 1987 Apollo Computer Inc.
All rights reserved. Printed in U.S.A.
First Printing: June, 1987
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, DGR, Domain/Ada, Domain/BRIDGE, Domain/DFL-100, Domain/DQC-100,
Domain/Dialogue, Domain/IX, Domain/Laser-26, Domain/PCI, Domain/SNA, D3M,
DPSS, DSEE, GMR, and GPR 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.
Domain/Ada is derived from the VERDIX(tm) Ada Development System (VADS(tm)),
supplied by VERDIX Corporation.
VERDIX, VADS, and GVAS are trademarks of VERDIX Corporation. Ada(r) is a
registered trademark of the U.S. Government (Ada Joint Program Office).
Reader_Notice
iii
This document resides on line in the /doc directory. 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 OVERVIEW OF DOMAIN/ADA RELEASE 1.0
1.1 Validation Information . . . . . . . . . . . . . . . . . 1-1
1.2 Hardware/Software Requirements . . . . . . . . . . . . . 1-1
1.3 Using Domain/Ada with the Domain/DSEE Product . . . . . 1-2
1.4 In Case of Problems . . . . . . . . . . . . . . . . . . 1-3
CHAPTER 2 SOFTWARE INSTALLATION PROCEDURES. . . . . . . . . . . . . . 2-1
CHAPTER 3 DOCUMENTATION
3.1 Compiler . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.2 Libraries. . . . . . . . . . . . . . . . . . . . . . . . 3-2
CHAPTER 4 BUGS AND LIMITATIONS
4.1 Bugs . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.2 Limitations . . . . . . . . . . . . . . . . . . . . . . 4-2
Contents iv
CHAPTER 1
OVERVIEW OF Domain/ADA RELEASE 1.0
This chapter describes the Domain/Ada (tm) System software. Domain/Ada is
derived from the VERDIX (tm) Ada Development System (VADS(tm)), Version
5.41.
Domain/Ada is centered on a high-performance Ada(R) compiler that is fully
compliant with ANSI/MIL-STD-1815A. The system includes the software for
compilation and program generation, library management, source control,
debugging, along with utilities and libraries.
1.1 Validation Information
Domain/Ada was validated on June 22, 1987, under Version 1.8 of the ACVC
tests. We intend to keep Domain/Ada validated, in accordance with U.S.
Government (AVO) policy.
1.2 Hardware/Software Requirements
This release of Domain/Ada requires the following MINIMUM revision levels of
base software:
o Software Release 9.5 (SR9.5) of the Aegis operating system, or a
later version.
o Domain/IX BSD4.2, SR9.5 version
Be sure that the node on which you are installing Domsin/Ada contains these
revision levels, or later revision levels. Domain/Ada runs on nodes that
have a 68020-based processor, that is, all Domain nodes EXCEPT:
DN100
Release 1.0 1-1 Domain/Ada
DN400, DN420, DN460, DN660, DN600, DSP160
DN300, DN320
DSP80(A)
DN550
DSP9000
The 68020 requirement allows the Ada compiler to generate code that performs
floating point arithmetic using inline MC68881 floating point instructions,
rather than using floating point calls. This greatly improves the
performance of the generated code (see the next section for more performance
information).
1.3 Using Domain/Ada with the DSEE Product
You can use the optional DSEE product's history management features to
provide source code control for your Ada source files. You can also use the
DSEE task and monitor facilities to organize work on your Ada source files.
However, you cannot use the DSEE configuration management features to build
systems that contain Ada source files.
This section describes how to use the DSEE history management facilities with
the Domain/Ada library management facilities. We assume that you understand
the DSEE history management and Ada library management commands; if not,
consult your DSEE reference manual and the Ada manuals shipped with this
release.
Using DSEE history management facilities with Ada library management
facilities requires two libraries: a DSEE library to archive the source code
and an Ada library from which you can build the program. You use links in
the Ada library to point to the actual files, stored in the DSEE library.
First create a DSEE library and store your Ada source files in this library.
They should have their usual ".a" suffixes. Then create a separate directory
and use the Ada a.mklib command to make this library into an Ada library.
To create links in your Ada library to the source files stored in your DSEE
library, you can create a shell script. If you have DSEE Version 3.0, you
can use output from a DSEE command to make this script. If you are using an
earlier DSEE release, you can create the shell script manually.
To create the shell script using DSEE Version 3.0, generate a list of the
elements that you will use to build the Ada program. Use the DSEE show
elements command with the -format option to generate this list. Arguments to
the -format option provide the shell commands necessary to create the links.
In the following example, ada_lib is the name of the Ada library and
dsee_lib is the name of your DSEE library. The results of the DSEE command
are redirected to a file called link_script in the current working
directory.
DSEE> show elements ?*.a -format "crl ada_lib/%ele dsee_lib//%ele" >link_script
Domain/Ada 1-2 Release 1.0
After you issue this DSEE command, link_script contains a set of link
commands with the names of the links to be created. For example:
crl ada_lib/five.a dsee_lib/five.a
crl ada_lib/four.a dsee_lib/four.a
crl ada_lib/one.a dsee_lib/one.a
crl ada_lib/three.a dsee_lib/three.a
crl ada_lib/two.a dsee_lib/two.a
When you run link_script, it creates a set of links, in your Ada library.
The Ada compiler can now compile the files to which these links point.
Note that when issuing the DSEE command, you may wish to use absolute
pathnames for your libraries, to prevent incorrect resolution of relative
pathnames.
1.4 In Case of Problems
This section describes solutions to two problems you could encounter. Both
problems result from improperly installed software.
If you are building a program using a.ld or a.make, and you get an error
message stating that tb_$get_frame is undefined, you have the wrong version
of /com/bind. Reinstall Domain/Ada, as described in Chapter Two.
If you are running a.db and get a message stating that no /dev/*typ* is
installed, you do not have the node's pseudo terminals (ptys) set up
properly. This can happen if you did not install Domain/IX correctly to run
on a diskless node.
If this error occurs, use the following workaround to fix the problem. In a
Domain/IX BSD4.2 C shell, use the following commands to reconfigure the ptys:
rm /dev/ptyp*; rm /dev/ttyp*; /etc/crpty 4
Release 1.0 1-3 Domain/Ada
CHAPTER 2
INSTALLATION PROCEDURE
This chapter describes how to install Domain/Ada Release 1.0. You can add
this software to a user node (one equipped with monitor and keyboard) or a
Domain server processor (DSP) that is running SR9.5 or a more recent version
of the AEGIS and DOMAIN/IX operating systems. If the user node or DSP is not
running SR9.5 or a more recent version, follow the appropriate software
update procedures as described in Installing__Domain__Software (Order No.
008860) or in the appropriate release notes.
Note that when you plan to run Domain/Ada on a diskless node, you must take
care to properly configure the node to run DOMAIN/IX. Chapter 2 of the
DOMAIN/IX release notes describe the correct configuration procedures for
diskless nodes running DOMAIN/IX. In particular, the user or system
administator must use /etc/crpty to create psuedo terminals, as described in
the release notes. The Ada debugger, a.db, needs these to run.
NOTE: The user node or DSP must have a minimum of 10440 blocks of
available disk space for a successful installation of this
software.
2.1 Conventions and Terminology
Before you start, make sure you understand these terms and conventions:
Work Node The user node at which you perform the installation
procedure.
Target The directory into which you're installing software. The
target can be a node entry directory (for example, //TARGET)
or any subdirectory (for example, //TARGET/PRODUCT). If the
target is on a user node, then the work node and the user
node can be the same node.
NOTE: When you are installing software to update a
Release 1.0 2-1 Domain/Ada
diskless node, the target is the node entry
directory of the partner node.
Secure network A network that uses a registry of user accounts and access
control lists (ACLs) to control log-in privileges and access
to files and directories. Note that an open network does not
use a registry or ACLs.
Source area An on-line master area of Domain software. An administrator
installs software from the distribution media into the source
area and users install software from the source area over the
network. The source area can be a node's entry directory or
any subdirectory.
Source media The media (floppy disks, magnetic tape, cartridge tape, or
another node in the network) that contains the software.
< > Angle brackets ( < > ) enclose the name of a key on the
keyboard.
2.2 Planning the Installation
There are two type of installation procedures for Domain/Ada: a procedure for
a link install and a procedure for a software installation. We describe both
in this section.
2.2.1 Link Installation
A link installation enables you create a link to a node that has Domain/Ada
software. Unlike the software procedure (described below), a link
installation does not require a specific mode. However, installation
procedures for the link install are described under both the Administrative
and the User mode of the software installation procedures.
2.2.2 Software Installation
You can use the software procedure in one of three modes: ADMINISTRATIVE
mode, USER mode, or SPECIAL-CASE mode.
ADMINISTRATIVE mode creates a source area by copying the INSTALL program and
the new software from the distribution media to the target. You use the
administrative mode when no source area for this release exists in the
network. See Section 2.3 for more information about administrative-mode
installations.
USER mode involves copying your new software from a source area onto another
node in the network; it's the simplest and most commonly used mode. You can
Domain/Ada 2-2 Release 1.0
install in user mode only AFTER an administrative-mode installation has
initialized the source area with the INIT_SOURCE program.
Two default conditions apply to a user-mode installation. The defaults are:
o The INSTALL program automatically copies the new software over the
network from the initialized source area, instead of asking you to
specify the source area.
o The INSTALL program uses the SID "user.sys_admin" during the
installation, rather than your own login SID.
To install in user mode, get the source area's pathname from your system
administrator, then go on to Section 2.4.2.
SPECIAL-CASE mode involves special cases in which you need to override the
user-mode defaults. The special cases are:
o You want to install software from an initialized source area on the
network, but your own login SID gives you more rights to a target's
protected directories than the default SID "user.sys_admin"
o You want to install software from a source other than an initialized
source area (for example, source media)
o You want to install additional software in a source area that was
initialized during a previous administrative-mode installation
The installation procedure enters special-case mode when you invoke the
INSTALL program with its -my_sid option. Specifying this option overrides
the user-mode defaults, which means that the INSTALL program (1) uses your
own login SID instead of "user.sys_admin" and (2) prompts for source media
rather than automatically copying the software over the network from an
initialized source area. In all other respects, special-case mode behaves
like one of the other two modes of installation (your choice of source
determines which one).
If you want to install software from an initialized source area on the
network while using your own login SID, follow the directions for user-mode
installations in Section 2.4.2. These directions include provisions for
installing software in special-case mode.
If you want to install software from a source other than an initialized
source area, or you want to install additional software in a previously
initialized source area, follow the directions for an administrative-mode
installation in Section 2.4.1. These directions also include provisions for
installing software in special-case mode.
Release 1.0 2-3 Domain/Ada
2.3 Additional Information About Administrative-mode Installations
The target of an administrative-mode installation generally serves as the
source for subsequent user-mode installations (the administrative-mode target
pathname is therefore the same as the user-mode source pathname). User-mode
installations use both the INSTALL program and the software stored in the
source area.
ADMINISTRATIVE MODE USER MODE
SOURCE --------------------> TARGET (user node or DSP)
______
(media) SOURCE -------------------> TARGET
Your choice of target for an administrative-mode installation depends on
whether you want the target node to RUN the software as well as act as a
SOURCE for the software. If you also want the node to run the software, make
the target the node's entry directory (for example, //node). If you just
want the node to contain the software, you should make the target a
subdirectory (for example, //node/product/source_area). In either case,
users should then use the target of your administrative-mode installation as
their source area.
You can install different optional software products into the same source
area or into separate source areas. Whichever route you take, you can then
selectively install optional products on user nodes or DSPs from the source
area(s).
If you have a secure network, you must have system administrator rights to
install in administrative mode. Also, during the procedure you must
initialize the source area by running the INIT_SOURCE program. This program
marks the installation program in the source area with special privileges for
subsequent user-mode installations, such as use of the SID "user.sys_admin"
during installation. The INSTALL program can then install software in
protected system directories, even though the user running the program does
not have rights to modify these directories. In open networks, you create a
source area but you don't run INIT_SOURCE, since all users have rights to
modify their system directories.
2.4 Installation Procedure
The following sections describe the administrative mode and the user mode of
installation. To install software in special-case mode, consult Section 2.2
to determine which set of instructions you should follow.
NOTE: Steps 8b and 10b describe the differences in the procedures if you use
Domain/Ada 2-4 Release 1.0
the LINK installation.
2.4.1 Administrative Mode
NOTE: You can enter "q" or "quit" at any prompt in the INSTALL program to
abort the installation and return to the Shell.
1. If you intend to create a source area for future installations, log
on to a work node using a system administrator account (for example,
my_name.sys_admin.%.%). Otherwise, log on using your own account
(for example, my_name.%.%.%).
2. Set your working directory to the installation target. This target
will become the source area for user installations (refer to note in
section 2.2). It can be a node entry directory (like //node) or it
can be any subdirectory created prior to the installation (like
//node/product/source_area). For example:
$ wd //node or wd //node/subdirectory
in which a the user creates a directory WITHOUT a previous install
on it.
3. Insert the source 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. If you are using a floppy disk, use the F0 (Fzero)
option.
NOTE: If you are using multiple floppy disks, insert the floppy
disk with the numeral 1 at the end of its label (for
example, "FLP8_product_n.n_1").
All of the RBAK commands shown below create an INSTALL directory on
the target and write the installation software to the directory.
When entering the RBAK command, use lower-case characters to ensure
visibility of the install directory in case-sensitive environments.
Note that you can leave the source media in the drive for use in a
later step; if you remove the source media after executing the RBAK
command, the INSTALL program will later prompt you to re-insert the
media.
$ RBAK -DEV CT -F 1 install -AS install -L -MS -FORCE -SACL -DU
$ RBAK -DEV M0 -F 1 install -AS install -L -MS -FORCE -SACL -DU
$ RBAK -DEV F0 -F 1 install -AS install -L -MS -FORCE -SACL -DU
Release 1.0 2-5 Domain/Ada
4. Set your working directory to the INSTALL directory on the target.
For example:
$ wd //node/install
5. Execute the INSTALL program and follow the prompts. If you are
installing software in special-case mode, use the -my_sid option.
For ADMINISTRATIVE MODE, type:
$ install
For SPECIAL-CASE MODE, type:
$ install -mysid
6. The program may prompt you to enter an installation type, based on
what products already exist in the source area. If it does, answer
OPT and proceed. For example:
****************************************
* SOFTWARE INSTALLATION -- Version n.n *
****************************************
Software installation TYPES are:
STD -- Install standard software
RESTART -- Restart the software installation
ACL -- Set ACLs for existing software
CLEANUP -- Run the Cleanup Procedure for ADD MODE installations
OPT -- Install optional software (e.g., Pascal, FORTRAN)
Please enter installation TYPE: OPT
Domain/Ada 2-6 Release 1.0
7. When the program displays the names of one or more optional
products, enter the name of the optional product that you want to
install. For example, to install Domain/Ada software you would type
"ada", as shown in the sample menu below.
Name Description Disk Blocks Needed
(Adding New Software)
ADA Domain/Ada 10440
OTHER If the optional product that you would like to install
is not listed above, choose OTHER.
*Note: When you choose OTHER, you are asked a few questions
then shown a display of Apollo's optional products. Check
with your system administrator to determine which products
your site has purchased and in which directory these
products have been installed.
Enter the name of a single product you would like to install: ada
Now enter the type of installation procedure you want to use. Type LINK
for a link install, or type SOFTWARE for a software install.
Do you want to install Domain/Ada Software or do you want to
create a link to a node which has Domain/Ada Software ?
Enter LINK or SOFTWARE : software [or link]
If you chose the SOFTWARE install:
8a. When prompted for the name of the target, enter the appropriate
pathname (that is, the node entry directory or subdirectory that you
specified in Step 2). For example:
The TARGET is the node or subdirectory on which you are installing
software. (e.g., '//my_node' or '//my_node/subdirectory')
Enter Target: //node
Release 1.0 2-7 Domain/Ada
If you chose the LINK install:
8b. When prompted for the name of the node in which to link, enter the
appropriate pathname (that is, the node entry directory or
subdirectory that you specified in Step 2). For example:
Please enter the name of the node you want to link to
for Domain/Ada Software. Use the format: //node_name .
Enter node name : //link_to_node
9. The INSTALL program prompts for the source media. Enter your
choice.
Source MEDIA is one of:
CTAPE -- Cartridge Tape
MTAPE -- Magnetic Tape
FLOPPY -- 8" or 5 1/4" Floppies
NET -- An area on the network with valid Software
Enter Source Media:
10. The install asks you whether to install the on-line man pages.
The following man page files are available to accompany
installation of the Ada software :
man1/a.cleanlib.1
man1/a.db.1
man1/a.du.1
man1/a.error.1
man1/a.info.1
man1/a.ld.1
man1/a.list.1
man1/a.ls.1
man1/a.make.1
man1/a.mklib.1
man1/a.path.1
man1/a.pr.1
man1/a.rm.1
man1/a.rmlib.1
man1/a.tags.1
man1/a.vadsrc.1
man1/a.view.1
man1/a.which.1
man1/ada.1
man3/examples.3
man3/libraries.3
man3/math.3
Domain/Ada 2-8 Release 1.0
man3/publiclib.3
man3/standard.3
man3/verdixlib.3
Do you wish to install the on-line Manual pages ?
Enter YES or Y or NO or N : y
If you are running the SOFTWARE install:
11a.The INSTALL program may ask you to insert the media into the drive.
Insert the media and press <RETURN>.
If you are running the LINK install:
11b.The following type of link message appears to verify the
link:
LINK created from //node/subdirectory to //link_to_node/subdirectory.
12. The INSTALL program installs the software, listing each file it
copies from the source media. If the software resides on multiple
floppy disks, the program prompts you to mount (that is, insert) the
next disk and to press <RETURN> to continue.
The final message reads:
**************************************************************************
* In order to cause the c-shell to find Ada commands, we suggest that *
* you add "/usr/vads5/bin" to your path variable by setting "path" in *
* your personal ".cshrc" file as follows: *
* *
* set path = ( . /usr/ucb /bin /usr/bin /usr/vads5/bin ) *
* *
* Note, UNIX is case sensitive, so the above command must be in lower *
* case. Regarding .cshrc, during the creation of a bsd4.2 c-shell, UNIX *
* looks for a .cshrc file in the user's home directory. If one is found,*
* it is opened and the lines within are executed as the first command *
* input for that shell. *
* *
* Also, someone with the necessary privileges (your system administrator)*
* should run /usr/lib/makewhatis in order to update the data base for *
* 'apropos'. *
* *
**************************************************************************
When the INSTALL program finishes installing the software, it
displays the following menu:
Options:
Release 1.0 2-9 Domain/Ada
RERUN -- There were errors in the transcript
pad and you wish to rerun the installation.
FINISH -- The installation ran to completion error free.
There is no additional optional software you
wish to install.
CONTINUE -- Install additional optional software.
If you encountered any errors during the installation, correct the
problem(s) and select RERUN. To locate error messages issued during
installation, search backwards for the characters @? (an at sign
followed by a question mark) in the installation's transcript pad.
If there were no errors, choose CONTINUE or FINISH. Selecting
CONTINUE brings you back to the beginning of the INSTALL program;
selecting FINISH terminates the program. If you were installing
software from magnetic tape, cartridge tape, or floppy disks, you
can now remove the media from the drive.
13. If you have a secure network and you want the target of your
installation to be used as a source area for future installations,
run the INIT_SOURCE program (also run the program if you are adding
software to a previously initialized source area). You must be
logged in as a system administrator to perform this step.
Invoke INIT_SOURCE at the Shell prompt. When prompted, enter the
pathname of the new source area (which is currently the target of
your administrative-mode installation). Here is an example:
$ initsource
Please enter the name of the SOURCE AREA
for your network (e.g., '//NODE/SOURCE_AREA'):
//node
The source area for your network
has been set to: //node
This is the end of the administrative-mode installation procedure.
2.4.2 User Mode
NOTE: You can enter "q" or "quit" at any prompt in the INSTALL program to
abort the installation and return to the Shell.
Domain/Ada 2-10 Release 1.0
1. Log on to a work node using your own account (for example,
my_name.%.%.%).
2. Set your working directory to the INSTALL directory in the source
area (if necessary, ask your system administrator for the pathname).
For example:
$ wd //node/install
3. Execute the INSTALL program and follow the prompts. If you are
installing software in special-case mode, use the -my_sid option.
For USER MODE, type:
$ install
For SPECIAL-CASE MODE, type:
$ install -mysid
4. The program may prompt you to enter an installation type, based on
what products already exist in the source area. If it does, answer
OPT and proceed. For example:
****************************************
* SOFTWARE INSTALLATION -- Version n.n *
****************************************
Software installation TYPES are:
STD -- Install standard software
RESTART -- Restart the software installation
ACL -- Set ACLs for existing software
CLEANUP -- Run the Cleanup Procedure for ADD MODE installations
OPT -- Install optional software (e.g., Pascal, FORTRAN)
Please enter installation TYPE: OPT
Release 1.0 2-11 Domain/Ada
5. When the program displays the names of one or more optional
products, enter the name of the optional product that you want to
install. For example, to install Domain/Ada software you would type
"ada", as shown in the sample menu below.
Name Description Disk Blocks Needed
(Adding New Software)
Ada Domain/Ada 10440
OTHER If the optional product that you would like to install
is not listed above, choose OTHER.
*Note: When you choose OTHER, you are asked a few questions
then shown a display of Apollo's optional products. Check
with your system administrator to determine which products
your site has purchased and in which directory these
products have been installed.
Enter the name of a single product you would like to install: ada
6. When prompted for the name of the target, enter the appropriate
pathname (that is, a node entry directory or subdirectory). For
example:
The TARGET is the node or subdirectory on which you are installing
software. (e.g., '//my_node' or '//my_node/subdirectory')
Enter Target: //node
7. The INSTALL program may prompt for the source media. If so, enter
NET.
Source MEDIA is one of:
CTAPE -- Cartridge Tape
MTAPE -- Magnetic Tape
FLOPPY -- 8" or 5 1/4" Floppies
NET -- An area on the network with valid Software
Enter Source Media: net
8. The installation program asks you whether to install the on-line man
pages.
Domain/Ada 2-12 Release 1.0
The following man page files are available to accompany
installation of the Ada software :
man1/a.cleanlib.1
man1/a.db.1
man1/a.du.1
man1/a.error.1
man1/a.info.1
man1/a.ld.1
man1/a.list.1
man1/a.ls.1
man1/a.make.1
man1/a.mklib.1
man1/a.path.1
man1/a.pr.1
man1/a.rm.1
man1/a.rmlib.1
man1/a.tags.1
man1/a.vadsrc.1
man1/a.view.1
man1/a.which.1
man1/ada.1
man3/examples.3
man3/libraries.3
man3/math.3
man3/publiclib.3
man3/standard.3
man3/verdixlib.3
Do you wish to install the on-line Manual pages ?
Enter YES or Y or NO or N : y
8. The INSTALL program may prompt for the source area. If so, enter
the pathname (if you don't know it, ask your system administrator).
For example:
The SOURCE AREA is the node or subdirectory from which you are
copying software. (e.g., '//node' or '//node/subdirectory')
Enter Source Area: //node
Release 1.0 2-13 Domain/Ada
9. The INSTALL program installs the software, listing the name of each
file it copies from the source area. The final message reads:
**************************************************************************
* In order to cause the c-shell to find Ada commands, we suggest that *
* you add "/usr/vads5/bin" to your path variable by setting "path" in *
* your personal ".cshrc" file as follows: *
* *
* set path = ( . /usr/ucb /bin /usr/bin /usr/vads5/bin ) *
* *
* Note, UNIX is case sensitive, so the above command must be in lower *
* case. Regarding .cshrc, during the creation of a bsd4.2 c-shell, UNIX *
* looks for a .cshrc file in the user's home directory. If one is found,*
* it is opened and the lines within are executed as the first command *
* input for that shell. *
* *
* Also, someone with the necessary privileges (your system administrator)*
* should run /usr/lib/makewhatis in order to update the data base for *
* 'apropos'. *
* *
**************************************************************************
Upon completion, the INSTALL program displays the following menu:
Options:
RERUN -- There were errors in the transcript
pad and you wish to rerun the installation.
FINISH -- The installation ran to completion error free.
There is no additional optional software you
wish to install.
CONTINUE -- Install additional optional software.
If you encountered any errors during the installation, correct the
problem(s) and select RERUN (if necessary, consult your system
administrator for assistance). To locate error messages issued
during installation, search backwards for the characters @? (an at
sign followed by a question mark) in the installation's transcript
pad.
If there were no errors, choose CONTINUE or FINISH. Selecting
CONTINUE brings you back to the beginning of the INSTALL program;
selecting FINISH terminates the program.
This is the end of the user-mode installation procedure.
Domain/Ada 2-14 Release 1.0
CHAPTER 3
DOCUMENTATION
The Domain/Ada__Development__System__Reference manual (Order Number 008917)
fully describes the Domain/Ada Compiler and tools, except where noted below.
3.1 Compiler
These are the exceptions for the Domain/Ada compiler:
o The Domain/Ada compiler supports PRAGMA INLINE and address clauses
in subprograms.
o The compiler supports additional Chapter 13 capability with unsigned
types and bit operations. Unsigned types are declared using a length
clause as illustrated below.
type unsigned_short is range 0 .. 2 ** 16 - 1;
for unsigned_short'size use 16;
Without the length clause, UNSIGNED_SHORT is stored as a 32-bit
integer. With the length clause, it is stored as a 16-bit integer,
although operations on it are done as a 32-bit integer internally.
Unsigned types are supported. Currently only 16- and 8-bit unsigned
types are supported.
o Bit sized quantities are obtained by using pragma PACK, a length
clause, or a record representation specification. When a length
clause is provided for an array or record, if it does not fit when
not packed, packing is applied to try to make it fit. If it still
does not fit, an error message is given.
Discrete (integer and enumeration) types are the only elements or
fields that are packed. Of course, a four-bit record or array would
be packed into four bits as a field of a packed record or element of
a packed array, but it must already have been sized at four bits.
When packing occurs, whether due to a pragma or a length clause,
elements and fields are packed into a power of two bits.
Release 1.0 3-1 Domain/Ada
3.2 Libraries
In standard, the function STANDARD_ERROR has been added to TEXT_IO to allow
writing to the Domain/IX standard error stream.
Domain/Ada 3-2 Release 1.0
CHAPTER 4
BUGS AND LIMITATIONS
This chapter describes the known bugs and limitations at this release.
4.1 Bugs
The following paragraphs describe bugs that are known to exist in the 1.0
version of the Domain/Ada product.
An internal assertion error (compiler error) occurs when compiling a
qualified equals operator. For example:
package TEST_PACKAGE is
type A_TYPE is record I : INTEGER := 1; end record;
end;
with TEST_PACKAGE;
procedure TEST is
A1,A2: TEST_PACKAGE.A_TYPE;
begin
if TEST_PACKAGE."="(A1, A2) then null; end if; -- Assertion failure!
end;
To work around this, use a "USE" clause, or assign the result of the
qualified equal to a boolean variable and then test the boolean explicitly.
An internal assertion error (compiler error) occurs when declaring a PRIVATE
RECORD with an initialization clause for fields of the record.
An internal assertion error (compiler error) occurs when you do fixed-point
multiplication or division. To work around this, coerce fixed-point values
to floating-point values before doing the operation.
A warning about the wrong number of characters occurs when compiling an IF
statement that compares an array-slice against a constant-string. You can
ignore this warning.
When you declare an instance of an unconstrained array type in Domain/Ada,
Release 1.0 4-1 Domain/Ada
all instantiations share a single (STATIC) copy of the bounds of the array.
Due to a compiler bug, if you declare such an instance inside a procedure
body, and recursively call the procedure, the constant for the array bounds
doesn't get changed back to its original value.
4.2 Known Limitations at Release 1.0
The following limitations exist at this release:
4.2.1 a.make
When building a system that contains source files and binaries that are
stored in libraries that are not on the same node, a.make might not always
build the latest version. Because of clock differences that may exist from
node to node, if the binary's date-time-modified (dtm) attribute is later
than the source file, the source file is not recompiled. However, the binary
could actually be older than the source file, if the nodes' clocks are out of
synch. To work around this problem, synchronize the clocks on nodes that
contain Ada files used in building the same system. (Use the Domain calender
utility to adjust the clock on a node.)
4.2.2 a.db Debugger
The a.db debugger operates only on Ada programs. In addition, it only runs
in VT100 emulation mode; you cannot use the Domain Display Manager editing
functions.
4.2.3 Unavailable Tools/Software
Profiling of Ada programs is not available for this release because the
current version of Domain/IX does not include the profiling tools prof and
gprof.
4.2.4 Installation Limitations
The following limitations exist:
o The source area for Domain/Ada may be anywhere the system
adminstrator finds convenient, but each user must install Domain/Ada
so that it resides, as a link or as source, in /bsd4.2/usr/vads5.
o Domain/Ada runs only on a 68020-based machine. It does NOT run on
the following Domain models: DN100, DN400, DN420, DN460, DN600,
DN660, DSP160, DN300, DN320, DSP80(A), DSP9000, DN550.
Domain/Ada 4-2 Release 1.0
4.2.5 Other Limitations
When copying Ada source that has been compiled using the Domain/Ada
compiler, you must use the '-pdt' option to preserve the modified
date/time. Otherwise, a.make will not function properly.
Release 1.0 4-3 Domain/Ada