Domain/PAK Software Release Document
Software Release 3.0
Part No. 008896-B00
This document describes Software Release 3.0 of the
Domain Performance Analysis Kit (Domain/PAK).
APOLLO COMPUTER INC.
330 Billerica Road
Chelmsford, Massachusetts 01824
Confidential and Proprietary. Copyright 1988 Apollo Computer Inc.,
Chelmsford, Massachusetts. Unpublished -- rights reserved under the
Copyright Laws of the United States. All rights reserved.
Printed in U.S.A. First printing: June 1986. Latest printing: June 1988.
This document was formatted using the FMT tool distributed with the Domain
computer system.
Apollo and Domain are registered trademarks of Apollo Computer Inc.
UNIX is a registered trademark of AT&T in the USA and other countries.
Ada is a registered trademark of U.S. Government (Ada Joint Program
Office).
3DGMR, Aegis, D3M, DGR, Domain/Access, Domain/Ada, Domain/Bridge, Domain/C,
Domain/ComController, Domain/CommonLISP, Domain/CORE, Domain/Debug,
Domain/DFL, Domain/Dialogue, Domain/DQC, Domain/IX, Domain/Laser-26,
Domain/LISP, Domain/PAK, Domain/PCC, Domain/PCI, Domain/SNA, Domain X.25,
DPSS, DPSS/Mail, DSEE, FPX, GMR, GPR, GSR, NLS, Network Computing Kernel,
Network Computing System, Network License Server, Open Dialogue, Open
Network Toolkit, Open System Toolkit, Personal Supercomputer, Personal Super
Workstation, Personal Workstation, Series 3000, Series 4000, Series 10000,
and VCD-8 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 PROGRAMS 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.
ii
Reader_Notice
This document resides online 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
CHAPTER 1 OVERVIEW OF DOMAIN/PAK SOFTWARE RELEASE 3.0 1-1
SECTION 1.1 SOFTWARE DESCRIPTION 1-1
SECTION 1.2 CHANGES SINCE LAST RELEASE 1-1
CHAPTER 2 SOFTWARE INSTALLATION PROCEDURES 2-1
CHAPTER 3 DOCUMENTATION 3-1
CHAPTER 4 BUGS AND BUG FIXES 4-1
SECTION 4.1 BUGS FROM LAST RELEASE NOW FIXED 4-1
SECTION 4.2 KNOWN BUGS IN THIS RELEASE 4-1
iv
CHAPTER 1
OVERVIEW OF DOMAIN/PAK SOFTWARE RELEASE 3.0
1.1 Software Description
Domain/PAK, the Domain Performance Analysis Kit, consists of three tools that
help you analyze the performance of your applications. Each of the tools
examines performance at a different degree of detail:
o DSPST (Display Process Status) looks at the relative use of CPU time
by several processes at the system level. DSPST also shows you
network and disk activity for the node.
o DPAT (Domain Performance Analysis Tool) is an interactive tool that
looks at the performance of programs, including I/O, paging, and
system calls at the procedure level.
o HPC (Histogram Program Counter) looks at the performance of
compute-bound procedures at the statement level.
1.2 Changes Since Last Release
Domain/PAK SR3.0 is substantially similar to Domain/PAK SR2.1. There are,
however, two changes to DPAT.
1) In SR2.1 of Domain/PAK, "next process" caused DPAT to monitor the next
process that was created on the node after you selected "go". "Existing
process" let you monitor an existing process (including a shell) and any
program invoked in that process. So, it was common to use "existing
process" to choose a shell, then execute a program in the shell for DPAT to
monitor.
Under SR10.0 of Domain/OS, however, programs are never invoked within an
existing process. Each program gets its own process. Therefore, in SR3.0
of Domain/PAK, the function of "next process" and "existing process" has
changed.
"Next process" now shows you a menu of all the processes running on the
node. You select one of the processes from the list. DPAT then monitors the
next child process that the chosen process creates after you select "go".
This_is_now_the_way__you_should_monitor_a_program_run_by_a__shell: 1) select
the "next process" option, 2) choose the shell, 3) select "go", 4) then run
a program from the shell, 5) DPAT will monitor the program.
Domain/PAK 1-1 SR3.0
One of the choices under "next process" is "any". Choosing this option
causes DPAT to monitor the next process created after you select "go", no
matter which process creates it.
"Existing process" now shows you a menu of current processes. After you
select one, DPAT monitors that very process, but not any of its child
processes. This also applies to shells and programs run from a shell; a
program run from a shell is no longer part of the shell's process.
2) It is no longer possible to request that DPAT stop monitoring a process at
a debugger breakpoint.
Domain/PAK 1-2 SR3.0
CHAPTER 2
INSTALLATION INFORMATION
You can add Domain/PAK SR3.0 to a user node (one equipped with monitor and
keyboard) or a Domain Server Processor (DSP) that is running SR10.0 or a
more recent version of the operating system. If the user node or DSP is not
running SR10.0 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.
For directions about how to install this product, see the manual Installing
Domain_Software (Order No. 008860).
NOTE: The user node or DSP must have a minimum of 600 blocks of available
disk space for a successful installation of this software.
Domain/PAK 2-1 SR3.0
CHAPTER 3
DOCUMENTATION
Analyzing Program Performance with Domain/PAK (008906-A00) documents all
features of the software as of Software Release 3.0.
In some cases though, parts of sample screens are somewhat out of date. When
an example shows an aspect of the operating system, that information may not
reflect the current version of the operating system.
For instance: The chapter about DSPST shows some sample screens where DSPST
is monitoring the processes on a node. The names of the processes follow the
naming convention of a previous release of the operating system, rather than
SR10. The information about DSPST itself is correct, but the information
about the operating system is out of date.
The same applies to examples that show the names of sections in an object
file (an executable program). The chapter about HPC shows some examples that
include the names of object file sections. The names shown (PROCEDURE$,
DATA$) are for a previous version of the operating system. Under SR10 of
Domain/OS the corresponding section names are .text and .data. In these
examples the information about HPC is correct, but the operating system used
is old.
Domain/PAK 3-1 SR3.0
CHAPTER 4
BUGS AND BUG FIXES
4.1 Bugs from Last Release Now Fixed
There are no specific bugs that were fixed between SR 2.1 and 3.0.
4.2 Known Bugs in This Release
There is one known bug.
1) There is a bug that involves DPAT, a C shell, and the "next process"
option in DPAT. This bug arises when you use the "next process" option in
DPAT, and the process you name is a C shell.
Normally, you select the "next process" option when you want to run a
program from a shell, and you want DPAT to monitor that program.
When the C shell runs a program, however, DPAT may start monitoring the child
process too quickly. DPAT may start gathering samples before the child
process has even invoked the program you are interested in. When this
happens, you can get a few samples that are meaningless, or the entire DPAT
session may be thrown off.
This problem does not occur with /com/sh or /bin/sh shells.
Domain/PAK 4-1 SR3.0