================================================================================
PowerUX NightTrace*
Version 3.1
Release Notes
Harris Computer Systems Corporation
1. Introduction
The NightTrace product is part of NightStar tool set aimed at
developing, debugging and analyzing multiprocess and multiprocessor
real-time applications.
NightTrace is a graphical tool set for analyzing the dynamic behavior
of multiprocess and multiprocessor applications. Trace applications
can be written in C, Fortran, or Ada. The ntraceud daemon process
writes the trace-event records generated by the execution of a user
application program to user-specified files. The generated files are
input to the ntrace program. The ntrace interactive trace-event
analysis tool provides a graphical view and summary statistics about
the run-time behavior of one or more application programs and possibly
the system.
NightTrace also includes KernelTrace, a tool set for analyzing the
dynamic behavior of the PowerUX operating system. The ktrace program
is used to collect information out of the running kernel. In
addition, ktrace can produce summaries and listings of kernel
activity. The ntfilter tool can convert KernelTrace data files into
NightTrace data format so that kernel and application activity can be
simultaneously analyzed with ntrace.
__________
* These release notes cover the following products: NightTrace
Version 3.1
- 1 -
PowerUX NightTrace 3.1 Release Notes
2. Documentation
The following table lists the documentation available with NightTrace
Version 3.1.
___________________________________________
| Manual Name Pub. Number|
|____________________________|_____________|
| NightTrace Manual | 0890398-050|
| NightTrace Release Notes | 0890398-3.1|
| NightTrace Pocket Reference| 0890474-000|
|____________________________|_____________|
Copies of the Concurrent documentation can be ordered by contacting
the Concurrent Software Support Center. The toll-free number for
calls within the continental United States is 1-800-245-6453. For
calls outside the continental United States, the number is 1-954-971-
6248.
3. Prerequisites
Prerequisites for NightTrace Version 3.1 are as follows:
3.1 Software Prerequisites
o PowerUX 3.1
3.2 Hardware Prerequisites
o Any Series 6000, Power Hawk or Power MAXION system
4. Installation
You will need to install the ntrace and ktrace packages on your
system. Please refer to chapter 3 of the System Administration Volume
1 manual for instructions on software installation.
5. Cautions
o Display pages created with NightTrace version 2.1 and earlier
that use the pid string table may not work as expected with
version 3.1. See the "C Thread and Ada Task Support" section of
these release notes for more information.
- 2 -
Release Notes 3.1 PowerUX NightTrace
o NightTrace 3.1 trace files created on PowerUX systems are not
guaranteed to work with version 2.2 and earlier. However,
NightTrace 2.2 trace files can be used with version 3.1 ntrace.
o Users of ntraceud are required to have permission to read
/dev/interval_timer. In addition, by default ntraceud requires
read and write access to /dev/spl as well as P_PLOCK privilege.
See the ntraceud(1) man page for a description of the -ipldisable
and -lockdisable options to override the default behavior.
o Both ntraceud and ktrace require special privileges when running
on a secure enabled system. The privileges needed are P_FPRI and
P_PLOCK. See the intro(2) man page for more information.
o On Series 6000, Power Hawk and Power MAXION systems, do not call
clock_settime(3P4) from your application. This system call can
corrupt the system interval timer which both NightTrace and
KernelTrace use for trace-event timings.
o NightTrace and KernelTrace need enough disk space to accommodate
each trace event logged, at an average rate of 16 bytes per trace
event.
o NightTrace configuration files must define format tables before
the files reference the tables. There are no similar
restrictions for macros, qualified events, and qualified states.
o NightTrace does not possess any print mechanism. If you wish to
capture a window, follow these steps:
1. Read xwd(1), xpr(1), and lp(1).
2. If you are using a color monitor, the colors get translated
into shades of gray before printing. For greatest
readability, make sure adjacent fields have colors with very
different values (blackness).
3. For single-window printing, make sure that the window you
wish to print out is not overlapping or overlapped by some
other window.
4. From a system with a PostScriptO printer, issue the
following command, substituting an appropriate printer name
for devname.
xwd -frame | xpr -device ps -gray 3 | lp -ddevname
Your pointer shape will change to that of the sighting
pointer (crosshairs). Click your leftmost mouse button in
the window of interest. You will hear a beep and you will
- 3 -
PowerUX NightTrace 3.1 Release Notes
see your pointer shape restored. Eventually your window
image will be queued at your PostScript printer; the larger
the window, the longer this command stream takes.
o There are some anomalies that can occur while examining a
kernel-trace file with the ntrace display utility. They are:
- It is possible for the first system call (since tracing
began) of a given process to be missing. This occurs if a
process is switched in for the first time since tracing
began in the middle of a system call, and then it is
switched out before completing that system call. Once the
process has completed its first system call, the system
calls of the process will be accurately represented.
- It is possible for the trace-event times in a kernel-trace
file and a user trace file to be merged by ntrace
incorrectly. This can occur because the trace tool records
only the low 32 bits of the interval timer in kernel-trace
records. Thus, ntrace assumes that the high 32 bits of the
time stamp of the first kernel-trace record match the high
32 bits of the time stamp of the earliest user-trace record
found. If this assumption is incorrect, the trace-event
times of the kernel trace events will be incorrect.
- It is possible, though unlikely, for system calls to nest,
confusing ntrace. This can happen if during a system call a
user-level interrupt occurs and a user-level interrupt
handler is invoked, calling server_wake(). This situation
causes any StateGraphs that graph system calls on kernel
display pages to display the wrong state. It also makes the
ntfilter tool throw away data, causing you to see "can't
determine" messages for system call names.
6. Product Description
This is the third release of NightTrace on PowerUX. Some customers
may be interested in the new and changed features of this release,
particularly if they are migrating from CX/UX. The following sections
describe these features.
6.1 Lightweight Process Support
The process identifier logged with all trace events is now a 32-bit
global process identifier. This value is returned from the
_lwp_global_self() function and is unique for all lightweight
processes on the system. This change is visible in the following
- 4 -
Release Notes 3.1 PowerUX NightTrace
ways:
o The pid() functions now return the new 32-bit global process
identifier.
o New raw_pid() functions can be used to access the old 16-bit
process identifier of a trace event.
o New lwpid() functions can be used to access the lightweight
process identifier (LWPID) of a trace event.
o Syntax has been added for specifying a process via its raw PID
and LWPID. For example, 1234'2 refers to a process with a raw
PID of 1234 and a LWPID of 2. This new syntax can be used in all
places where a PID is expected.
6.2 C Thread and Ada Task Support
NightTrace now supports multithreading and multitasking. For both
threads and tasks, a 32-bit integer NightTrace thread identifier (TID)
is logged with each trace event that uniquely identifies the thread.
For C threads the TID is composed of the raw PID and the thread ID
assigned by the Threads library. For Ada tasks the TID is composed of
the raw PID and the task ID assigned by the Ada run-time executive.
To access the TID information from ntrace, the following functions
have been added to the NightTrace expression language: tid(),
start_tid(), end_tid(), and offset_tid(). These functions can be
called anywhere a NightTrace expression is permitted.
There is now a tid string table in addition to the pid string table.
In previous releases, process names and NightTrace thread names from
trace_open_thread() were both placed into the pid table. In this
release, only process names are placed into the pid table, and only
NightTrace thread names are placed into the tid table. Display pages
that relied upon NightTrace thread names being placed into the pid
table will need to change to reference the new tid table in order to
achieve the same results.
Syntax has been added for specifying a NightTrace thread via its raw
PID and C thread ID (or Ada task ID). For example, 5678'3 refers to a
NightTrace thread with a raw PID of 5678 and a C thread ID of 3. This
new syntax can be used in all places where a TID is expected,
including the new TID List configuration parameter. See Chapter 8 of
the NightTrace Manual, "Configuring Display Objects," for more
information on the TID List configuration parameter.
There are new functions to access just the 16-bit C thread ID or 16-
- 5 -
PowerUX NightTrace 3.1 Release Notes
bit Ada task ID. To access this information from ntrace, the
following functions have been added to the NightTrace expression
language: thread_id(), start_thread_id(), end_thread_id(),
offset_thread_id(), task_id(), start_task_id(), end_task_id(),
offset_task_id(). These functions can be called anywhere a NightTrace
expression is permitted.
The trace_open_thread() function can now be called on a per-thread or
per-task basis. Thus, each thread or task in a process can be
associated with a unique thread name. In addition, trace_start() can
now be called on a per-thread or per-task basis, allowing individual
tasks and threads to log their trace events to separate ntraceud
daemons.
6.3 Kernel Tracing
To build a kernel with KernelTrace enabled you must:
1. Enable the kernel trace device. This is accomplished by changing
the N to a Y in the /etc/conf/sdevice.d/trace file.
2. Enable shared memory. This is accomplished by changing the N to
a Y in the /etc/conf/sdevice.d/ipc file.
3. Optionally use idtune(1M) to configure the number of trace
buffers (TR_BUFFER_COUNT) to be allocated by the kernel.
4. Rebuild the kernel with idbuild(1M).
5. Reboot the system with the new kernel.
The old trace executable has been renamed to ktrace. In addition, its
command line options have been changed. See the ktrace -help option
for more information.
The ktrace utility now reads the system's process table before and
after tracing. This information is put into the vectors file pid
string table for use with ntrace kernel trace pages.
The device string table is no longer included in the
/usr/lib/NightTrace/tables file. Instead, ktrace builds the device
table dynamically by examining the /etc/conf/node.d files on the
system at startup time. This information is stored in the raw
KernelTrace trace-event file. The device string table is then
included in the vectors file generated by the ntfilter tool.
The formats of the ktrace kernel activity summary and verbose listing
output have changed slightly. The same information is present, but
any tools designed to parse the output may need to account for the
- 6 -
Release Notes 3.1 PowerUX NightTrace
formatting changes. See the NightTrace Manual for examples of kernel
summary text and verbose listings.
The <sys/trace.h> file has been replaced with <sys/ktrace.h>. In
addition, the kernel trace implementation has changed significantly,
so tools depending on undocumented details in this header file may no
longer work.
The CPU identifier logged with kernel trace events is now the logical
CPU number. In previous versions, the CPU identifier was the physical
CPU number.
The set of system calls with associated device information has
changed. The set now includes: open, close, read, write, poll and
ioctl.
There are no actual idle processes under PowerUX. For simplicity,
ktrace creates a fake idle process with a global process identifier of
zero. This fake idle process "switches in" whenever a CPU becomes
idle.
Processes with names that are not in the pid string table will be
displayed in the PID'LWPID format on all kernel display pages.
System calls are no longer associated with a vendor index, so the
vendor string table is no longer used.
6.4 Miscellaneous
Manually creating the /dev/spl and /dev/interval_timer devices is no
longer required.
7. Direct Software Support
Software support is available from a central source. If you need
assistance or information about your system, please contact the Harris
Software Support Center at our toll free number (1-800-245-6453). Our
customers outside the continental United States can contact us
directly at 1-305-971-6248. The Software Support Center operates
Monday through Friday from 8 a.m. to 7 p.m., Eastern Standard time.
Calling the Software Support Center gives you immediate access to a
broad range of skilled personnel and guarantees you a prompt response
from the person most qualified to assist you. If you have a question
requiring on-site assistance or consultation, the Software Support
Center staff will arrange for a field analyst to return your call and
schedule a visit.
- 7 -
PowerUX NightTrace 3.1 Release Notes
Harris provides a Software Action Request (SAR) form which our
customers can fill out and submit to their local field analyst or the
Software Support Center. This procedure ensures that your request is
entered into our SAR database for follow-up and action.
To obtain copies of SAR forms, call the Software Support Center and
request form number CSD1833B.
- 8 -
Contents
1. Introduction................................................... 1
2. Documentation.................................................. 2
3. Prerequisites.................................................. 2
3.1 Software Prerequisites.................................... 2
3.2 Hardware Prerequisites.................................... 2
4. Installation................................................... 2
5. Cautions....................................................... 2
6. Product Description............................................ 4
6.1 Lightweight Process Support............................... 4
6.2 C Thread and Ada Task Support............................. 5
6.3 Kernel Tracing............................................ 6
6.4 Miscellaneous............................................. 7
7. Direct Software Support........................................ 7
- i -
_________________________________________________________________
HARRIS
COMPUTER SYSTEMS
_________________________________________________________________
PowerUX NightTrace
Version 3.1
Release Notes
0890398-3.1
July 1996
_________________________________________________________________
Trademark Acknowledgments
Night Hawk is a registered trademark of Concurrent Computer
Corporation.
NightTrace is a trademark of Concurrent Computer Corporation.
PostScript is a registered trademark of Adobe Systems Inc.
PowerUX is a trademark of Concurrent Computer Corporation.
UNIX is a registered trademark licensed exclusively by
the X/Open Company Ltd.
return to index
================================================================================
================================================================================
PowerMAX OS NightTrace*
Version 3.2
Release Notes
Harris Computer Systems Corporation
1. Introduction
NightTrace (TM) is part of NightStar (TM) tool set aimed at
developing, debugging and analyzing multiprocess and multiprocessor
real-time applications.
NightTrace is a graphical tool set for analyzing the dynamic behavior
of multiprocess and multiprocessor applications. Trace applications
can be written in C, Fortran, or Ada. The ntraceud daemon process
writes the trace-event records generated by the execution of a user
application program to user-specified files. The generated files are
input to the ntrace program. The ntrace interactive trace-event
analysis tool provides a graphical view and summary statistics about
the run-time behavior of one or more application programs and possibly
the system.
NightTrace also includes KernelTrace, a tool set for analyzing the
dynamic behavior of the PowerMAX OS operating system. The ktrace
program collects information out of the running kernel. In addition,
ktrace can produce summaries and listings of kernel activity. The
ntfilter tool can convert KernelTrace data files into NightTrace data
format so that kernel and application activity can be analyzed
simultaneously with ntrace.
__________
* These release notes cover the following products: NightTrace
Version 3.2
- 1 -
PowerMAX OS NightTrace 3.2 Release Notes
2. Documentation
The following table lists the documentation available with NightTrace
Version 3.2.
___________________________________________
| Manual Name Pub. Number|
|____________________________|_____________|
| NightTrace Manual | 0890398-050|
| NightTrace Release Notes | 0890398-3.2|
| NightTrace Pocket Reference| 0890474-000|
|____________________________|_____________|
You can order copies of the Concurrent documentation by contacting the
Concurrent Software Support Center. The toll-free number for calls
within the continental United States is 1-800-245-6453. For calls
outside the continental United States, the number is 1-954-971-6248.
3. Prerequisites
The following describes the Software and Hardware prerequisites:
3.1 Software Prerequisites
o PowerMAX OS 4.1
3.2 Hardware Prerequisites
o Any Night Hawk (TM) Series 6000, Power Hawk (TM) or Power MAXION
(TM) system
4. Installation
You will need to install the ntrace and ktrace packages on your
system. Please refer to chapter 3 of the System Administration Volume
1 manual for instructions on software installation.
NightTrace Version 3.2 must be run with the an License Manager. Follow
the steps in the "Obtaining Licenses" section of the an License
Manager Release Notes (0891055-4.1.3); the feature alias is
NightTrace. If you are not already running the an License Manager, if
you do not have a copy of the an License Manager Release Notes, or if
you need a license key, contact Concurrent Software Distribution at
1-800-666-5405.
- 2 -
Release Notes 3.2 PowerMAX OS NightTrace
5. Cautions
o Display pages created with NightTrace version 2.1 and earlier
that use the pid string table may not work as expected with
version 3.2. See the "C Thread and Ada Task Support" section of
these release notes for more information.
o NightTrace 3.2 trace files created on PowerMAX OS systems are not
guaranteed to work with version 2.2 and earlier. However,
NightTrace 2.2 trace files can be used with version 3.2 ntrace.
o To use ntraceud, you must be able to read /dev/interval_timer.
In addition, by default, ntraceud requires read and write access
to /dev/spl as well as the P_PLOCK privilege. See the
ntraceud(1) man page for a description of the -ipldisable and
-lockdisable options to override the default behavior.
o Both ntraceud and ktrace require special privileges when running
on a secure enabled system. The privileges needed are P_FPRI and
P_PLOCK. See the intro(2) man page for more information.
o On Series 6000, Power Hawk and Power MAXION systems, do not call
clock_settime(3P4) from your application. This system call can
corrupt the system interval timer which both NightTrace and
KernelTrace use for trace-event timings.
o NightTrace and KernelTrace need enough disk space to accommodate
each trace event logged, at an average rate of 16 bytes per trace
event.
o NightTrace configuration files must define format tables before
the files reference the tables. There are no similar
restrictions for macros, qualified events, and qualified states.
o NightTrace does not possess any print mechanism. If you wish to
capture a window, follow these steps:
1. Read xwd(1), xpr(1), and lp(1).
2. If you are using a color monitor, the colors are translated
into shades of gray before printing. For greatest
readability, be sure adjacent fields are colors with very
different values (blackness).
3. For single-window printing, be sure that the window you wish
to print out is not overlapping or overlapped by some other
window.
- 3 -
PowerMAX OS NightTrace 3.2 Release Notes
4. From a system with a PostScriptO printer, issue the
following command, substituting an appropriate printer name
for devname.
xwd -frame | xpr -device ps -gray 3 | lp -ddevname
Your pointer shape will change to that of the sighting
pointer (crosshairs). Click your leftmost mouse button in
the window of interest. You will hear a beep and you will
see your pointer shape restored. Eventually your window
image will be queued at your PostScript printer; the larger
the window, the longer this command stream takes.
o There are some anomalies that can occur while examining a
kernel-trace file with the ntrace display utility. They are:
- It is possible for the first system call (since tracing
began) of a given process to be absent. This occurs if a
process (during a system call) is switched in for the first
time since tracing began, and then the process is switched
out before completing that system call. Once the process
has completed its first system call, the system calls of the
process are accurately represented.
- It is possible for the trace-event times in a kernel-trace
file and a user trace file to be merged by ntrace
incorrectly. This can occur because the trace tool records
only the low 32 bits of the interval timer in kernel-trace
records. Thus, ntrace assumes that the high 32 bits of the
time stamp of the first kernel-trace record match the high
32 bits of the time stamp of the earliest user-trace record
found. If this assumption is incorrect, the trace-event
times of the kernel trace events will be incorrect.
- It is possible, though unlikely, for system calls to nest,
confusing ntrace. This can happen if during a system call a
user-level interrupt occurs and a user-level interrupt
handler is invoked, calling server_wake(). This situation
causes any StateGraphs that graph system calls on kernel
display pages to display the wrong state. It also causes
the ntfilter tool to throw away data, generating "can't
determine" messages for system call names.
- 4 -
Release Notes 3.2 PowerMAX OS NightTrace
6. Product Description
Some customers may be interested in the new and changed features of
this release, particularly if they are migrating from CX/UX. The
following sections describe these features.
6.1 Lightweight Process Support
The process identifier logged with all trace events is now a 32-bit
global process identifier. This value is returned from the
_lwp_global_self() function and is unique for all lightweight
processes on the system. This change is visible in the following
ways:
o The pid() functions now return the new 32-bit global process
identifier.
o You can use new raw_pid() functions to access the old 16-bit
process identifier of a trace event.
o You can use new lwpid() functions to access the lightweight
process identifier (LWPID) of a trace event.
o Syntax has been added for specifying a process via its raw PID
and LWPID. For example, 1234'2 refers to a process with a raw
PID of 1234 and a LWPID of 2. This new syntax can be used at any
time a PID is expected.
6.2 C Thread and Ada Task Support
NightTrace now supports multithreading and multitasking. For both
threads and tasks, a 32-bit integer NightTrace thread identifier (TID)
is logged with each trace event that uniquely identifies the thread.
For C threads, the TID is composed of the raw PID and the thread ID
assigned by the Threads library. For Ada tasks the TID is composed of
the raw PID and the task ID assigned by the Ada run-time executive.
The following functions have been added to the NightTrace expression
language. to access the TID information from ntrace: tid(),
start_tid(), end_tid(), and offset_tid(). These functions can be
called anytime a NightTrace expression is permitted.
There is now a tid string table in addition to the pid string table.
In previous releases, process names and NightTrace thread names from
trace_open_thread() were both placed into the pid table. In this
release, only process names are placed into the pid table, and only
NightTrace thread names are placed into the tid table. Display pages
that relied upon NightTrace thread names being placed into the pid
- 5 -
PowerMAX OS NightTrace 3.2 Release Notes
table need to change to reference the new tid table to achieve the
same results.
Syntax has been added for specifying a NightTrace thread via its raw
PID and C thread ID (or Ada task ID). For example, 5678'3 refers to a
NightTrace thread with a raw PID of 5678 and a C thread ID of 3. This
new syntax can be used in all places where a TID is expected,
including the new TID List configuration parameter. See Chapter 8 of
the NightTrace Manual, "Configuring Display Objects," for more
information on the TID List configuration parameter.
There are new functions to access just the 16-bit C thread ID or 16-
bit Ada task ID. The following functions have been added to the
NightTrace expression language To access this information from ntrace:
thread_id(), start_thread_id(), end_thread_id(), offset_thread_id(),
task_id(), start_task_id(), end_task_id(), offset_task_id(). These
functions can be called anytime a NightTrace expression is permitted.
The trace_open_thread() function can now be called on a per-thread or
per-task basis. Thus, each thread or task in a process can be
associated with a unique thread name. In addition, trace_start() can
now be called on a per-thread or per-task basis, allowing individual
tasks and threads to log their trace events to separate ntraceud
daemons.
6.3 Kernel Tracing
To build a kernel with KernelTrace enabled, you must:
1. Enable the kernel trace device. To do this, change the N to a Y
in the /etc/conf/sdevice.d/trace file.
2. Enable shared memory. You can do this by changing the N to a Y in
the /etc/conf/sdevice.d/ipc file.
3. Optionally, use idtune(1M) to configure the number of trace
buffers (TR_BUFFER_COUNT) allocated by the kernel.
4. Rebuild the kernel with idbuild(1M).
5. Reboot the system with the new kernel.
The old trace executable was renamed to ktrace. In addition, its
command line options have changed. See the ktrace -help option for
more information.
The ktrace utility now reads the system's process table before and
after tracing. This information is put into the vectors file pid
string table for use with ntrace kernel trace pages.
- 6 -
Release Notes 3.2 PowerMAX OS NightTrace
The device string table is no longer included in the
/usr/lib/NightTrace/tables file. Instead, ktrace builds the device
table dynamically by examining the /etc/conf/node.d files on the
system at startup. This information is stored in the raw KernelTrace
trace-event file. The device string table is then included in the
vectors file generated by the ntfilter tool.
The formats of the ktrace kernel activity summary and verbose listing
output have changed slightly. The same information is present, but
any tools designed to parse the output may need to account for the
formatting changes. See the NightTrace Manual for examples of kernel
summary text and verbose listings.
The <sys/trace.h> file has been replaced with <sys/ktrace.h>. In
addition, the kernel trace implementation has changed significantly,
so tools depending on undocumented details in this header file may no
longer work.
The CPU identifier logged with kernel trace events is now the logical
CPU number. In previous versions, the CPU identifier was the physical
CPU number.
The set of system calls with associated device information has
changed. The set now includes: open, close, read, write, poll and
ioctl.
There are no actual idle processes under PowerMAX OS. For simplicity,
ktrace creates a fake idle process with a global process identifier of
zero. This fake idle process "switches in" whenever a CPU becomes
idle.
Processes with names that are not in the pid string table will be
displayed in the PID'LWPID format on all kernel display pages.
System calls are no longer associated with a vendor index, so the
vendor string table is no longer used.
6.4 Miscellaneous
Manually creating the /dev/spl and /dev/interval_timer devices is no
longer required.
7. Direct Software Support
Software support is available from a central source. If you need
assistance or information about your system, please contact the Harris
Software Support Center at our toll free number (1-800-245-6453). Our
customers outside the continental United States can contact us
- 7 -
PowerMAX OS NightTrace 3.2 Release Notes
directly at 1-305-971-6248. The Software Support Center operates
Monday through Friday from 8 a.m. to 7 p.m., Eastern Standard time.
Calling the Software Support Center gives you immediate access to a
broad range of skilled personnel and guarantees you a prompt response
from the person most qualified to assist you. If you have a question
requiring on-site assistance or consultation, the Software Support
Center staff will arrange for a field analyst to return your call and
schedule a visit.
Harris provides a Software Action Request (SAR) form which our
customers can fill out and submit to their local field analyst or the
Software Support Center. This procedure ensures that your request is
entered into our SAR database for follow-up and action.
To obtain copies of SAR forms, call the Software Support Center and
request form number CSD1833B.
- 8 -
Contents
1. Introduction................................................... 1
2. Documentation.................................................. 2
3. Prerequisites.................................................. 2
3.1 Software Prerequisites.................................... 2
3.2 Hardware Prerequisites.................................... 2
4. Installation................................................... 2
5. Cautions....................................................... 3
6. Product Description............................................ 5
6.1 Lightweight Process Support............................... 5
6.2 C Thread and Ada Task Support............................. 5
6.3 Kernel Tracing............................................ 6
6.4 Miscellaneous............................................. 7
7. Direct Software Support........................................ 7
- i -
_________________________________________________________________
HARRIS
COMPUTER SYSTEMS
_________________________________________________________________
PowerMAX OS NightTraceTM
Version 3.2
Release Notes
0890398-3.2
February 1997
_________________________________________________________________
Trademark Acknowledgments
Elan License Manager is a trademark of Elan Computer Group, Inc.
Night Hawk is a registered trademark of Concurrent
Computer Corporation.
NightStar is a trademark of Concurrent Computer
Corporation.
NightTrace is a trademark of Concurrent Computer
Corporation.
Power Hawk is a registered trademark of Concurrent
Computer Corporation.
PostScript is a registered trademark of Adobe Systems Inc.
PowerMAX OS is a registered trademark of Concurrent
Computer Corporation.
PowerMAXION is a registered trademark of Concurrent
Computer Corporation.
return to index
================================================================================
================================================================================
NightTune*
Version 1.1
Release Notes
Harris Computer Systems Corporation
1. Introduction
This document provides an overview of release 1.1 of the NightTune
Performance Tuner. NightTune is a real-time tuning tool that is part
of the NightStar(TM) development environment. It provides an X Window
System(TM) and OSF/Motif(TM) graphical user interface (GUI) to the
system facilities available for real-time performance tuning of a
system or application.
NightTune is a page-based graphical tool that can be used to tune an
application or to monitor various aspects of the system. NightTune
provides simple point & click and drag & drop process control
facilities, enabling the binding and scheduling parameters of any
process to be changed with minimal effort. Client/server architecture
facilitates tuning/monitoring of remote systems.
NightTune displays panels which indicate CPU utilization, context
switching levels, virtual memory paging activity, disk I/O activity,
and network traffic levels.
2. Documentation
The following table lists the documentation available with release 1.1
of NightTune.
__________
* These release notes cover the following products: NightTune
- 1 -
NightTune 1.1 Release Notes
_________________________________________
| Manual Name Pub. Number|
|__________________________|_____________|
| NightTune Quick Reference| 0890515-000|
| NightTune Release Notes | 0890515-1.1|
|__________________________|_____________|
You can order copies of the Concurrent documentation by contacting the
Concurrent Software Support Center. The toll-free number for calls
within the continental United States is 1-800-245-6453. For calls
outside the continental United States, the number is 1-954-971-6248.
3. Prerequisites
The following describes the software and hardware prerequisites for
release 1.1 of NightTune.
3.1 Software Prerequisites
o PowerMAX OS(TM) operating system release 4.1 or later.
o X Window System release 5.2 or later.
o Elan License Manager(TM).
3.2 Hardware Prerequisites
o Any Night Hawk(TM) Series 6000, Power Hawk(TM), or
PowerMAXION(TM) system.
o An X Window System display device, such as an X terminal.
4. Installation
NightTune is installed as a software package by using the Software
Packaging Tools. The package name is ntune. Refer to the chapter
"Installing Add-On Software" in PowerMAX OS System Administration,
Volume 1 (Pub. No. 0890429), the PowerMAX OS Release Notes (Pub. No.
0890454-4.1), and the pkgadd(1M) man page for instructions on software
installation.
NightTune may be installed in either the root directory or elsewhere.
When you run pkgadd(1M) to install NightTune, you are prompted to
enter the name of the directory for installation. If you want to
install in the root directory, just press the return key at the
prompt. Otherwise, enter the name of the directory where you want
- 2 -
Release Notes 1.1 NightTune
NightTune installed. If this directory does not exist, the
installation procedures attempt to create it for you.
NightTune must be run with the Elan License Manager. Follow the steps
in the "Obtaining Licenses" section of the Elan License Manager
Release Notes (Pub. No. 0891055-Rel.#); the feature alias is
NightTune. If you are not already running the Elan License Manager,
if you do not have a copy of the Elan License Manager Release Notes,
or if you need a license key, contact Concurrent Software Distribution
at 1-800-666-5405.
5. Cautions
The NightTune Quick Reference only assists you to get started with
NightTune. It does not contain detailed procedural information that a
user's guide typically provides. For additional assistance on using
NightTune, consult the on-line help and the ntune(1) man page.
When using NightTune to run an application and NightTune is run as
client/server please note:
o The pathname specified in the PROGRAM statement should be a full
pathname, since it is an application which is to be executed on a
remote system and will be started by the server.
o Messages from the application are directed to the server standard
out/error.
o Error messages which occur as a result of setting scheduling
parameters are output to the server standard error.
6. Direct Software Support
Software support is available from a central source. If you need
assistance or information about your system, please contact the Harris
Software Support Center at our toll free number (1-800-245-6453). Our
customers outside the continental United States can contact us
directly at 1-305-971-6248. The Software Support Center operates
Monday through Friday from 8 a.m. to 7 p.m., Eastern Standard time.
Calling the Software Support Center gives you immediate access to a
broad range of skilled personnel and guarantees you a prompt response
from the person most qualified to assist you. If you have a question
requiring on-site assistance or consultation, the Software Support
Center staff will arrange for a field analyst to return your call and
schedule a visit.
- 3 -
NightTune 1.1 Release Notes
Harris provides a Software Action Request (SAR) form which our
customers can fill out and submit to their local field analyst or the
Software Support Center. This procedure ensures that your request is
entered into our SAR database for follow-up and action.
To obtain copies of SAR forms, call the Software Support Center and
request form number CSD1833B.
- 4 -
Contents
1. Introduction................................................... 1
2. Documentation.................................................. 1
3. Prerequisites.................................................. 2
3.1 Software Prerequisites.................................... 2
3.2 Hardware Prerequisites.................................... 2
4. Installation................................................... 2
5. Cautions....................................................... 3
6. Direct Software Support........................................ 3
- i -
_________________________________________________________________
HARRIS
COMPUTER SYSTEMS
_________________________________________________________________
NightTuneTM
Version 1.1
Release Notes
0890515-1.1
February 1997
_________________________________________________________________
Trademark Acknowledgments
Elan License Manager is a trademark of Elan Computer Group, Inc.
Night Hawk is a registered trademark of Concurrent
Computer Corporation.
NightTune is a trademark of Concurrent Computer
Corporation.
NightStar is a trademark of Concurrent Computer
Corporation.
OSF/Motif is a registered trademark of Open Software
Foundation, Inc.
Power Hawk is a registered trademark of Concurrent
Computer Corporation.
PowerMAX OS is a registered trademark of Concurrent
Computer Corporation.
PowerMAXION is a registered trademark of Concurrent
Computer Corporation.
X Window System is a trademark of The Open Group.
return to index
================================================================================
================================================================================
X Window System*
Version 5.3
Release Notes
Harris Computer Systems Corporation
1. Introduction
This document provides an overview of release 5.3 of the X Window
System(TM) product. X is a network-transparent window system that
allows applications built with the X libraries on a Concurrent
computer to display graphics on devices such as an X terminal or a
workstation running an X server. This product is based on Version 11,
Release 5 of the X Window System (X11R5).
Bundled with this release is OSF/Motif(TM) 1.2.5. Motif is an
industry-standard graphical user interface that is licensed by the
Open Software Foundation (OSF), Inc. Motif has been developed to
provide a standard user environment across a wide range of hardware
platforms. Applications that adhere to the OSF/Motif specification
provide users with consistent screen appearance and behavior.
In addition to the standard libraries, header files, and client
programs associated with X11R5 and Motif, this release includes some
new and enhanced libraries and clients. See section 5 for details.
2. Documentation
The following table lists the documentation available with release 5.3
of the X Window System.
__________
* These release notes cover the following products: X Window System
- 1 -
X Window System 5.3 Release Notes
_____________________________________________
| Manual Name Pub. Number|
|______________________________|_____________|
| X Window System Release Notes| 0890298-5.3|
| X Window System User's Guide | 0890300-010|
|______________________________|_____________|
Copies of the Concurrent documentation can be ordered by contacting
the Concurrent Software Support Center. The toll-free number for
calls within the continental United States is 1-800-245-6453. For
calls outside the continental United States, the number is 1-954-971-
6248.
On-line manual pages are also provided for both the X Window System
and Motif. The Motif manual pages are available in printed form as the
OSF/Motif Programmer's Reference manual. This manual is not included
in the OSF/Motif documentation set, but is available from Prentice-
Hall.
A wide selection of additional documentation can be found in local
bookstores for both the X Window System and Motif. For instance,
O'Reilly & Associates, Inc. publishes a series of books on the X
Window System and Motif, including two excellent books on Motif
programming: Volume 6A: Motif Programming Manual and Volume 6B: Motif
Reference Manual.
3. Prerequisites
Prerequisites for the X Window System release 5.3 are described in
sections 3.1 and 3.2.
3.1 Software Prerequisites
o PowerUX operating system release 3.1 or later.
3.2 Hardware Prerequisites
o Any Night Hawk(TM) Series 6000, Power MAXION(TM), or
PowerHawk(TM) system.
4. Installation
The X Window System product is installed as a software package using
the Software Packaging Tools. The package name is x11. Please refer to
the chapter "Installing Add-On Software" in the PowerUX System
Administration, Volume 1 (Pub. No. 0890429), the PowerUX Release Notes
- 2 -
Release Notes 5.3 X Window System
(Pub. No. 0890454-3.1), and the pkgadd(1M) command for instructions on
software installation.
4.1 Installation Options
Normally, packages are installed interactively, and the installer is
asked a series of questions during the installation process. The first
question asks if support files for developing X Window System
applications should be installed. Answering "no" prevents the static
libraries and header files from being installed. Such an installation
allows X client programs to be run, but does not allow compilation of
X programs.
The next option determines whether to install the on-line manual
pages. This is especially relevant when development support is
installed, because manual pages for over 1100 X and Motif library
routines are supplied in the package. If development support is not
selected, then answering "yes" causes only the manual pages for the
client programs to be installed.
The final question that the installer is asked is if the X Display
Manager daemon, xdm, should be started at boot time on this system. If
the answer is "yes", then the script /etc/init.d/xdm is linked into
the directory of commands that are executed at each system boot.
See xdm(1) and X(1) for more information about using xdm.
Packages can also be installed automatically, with the above options
determined from a set of default responses provided in the
installation package. If the package is installed this way, the
complete installation including development support and all manual
pages will be installed, and xdm will be enabled.
5. Product Description
The X Window System software in this product is based on the X Window
System Version 11, Release 5 distribution from the X Consortium. In
addition, all X11R5 public patches through patch #26 have been
applied. The product contains:
o Shared and static versions of all the standard X libraries,
including the X Window System library (libX11), the X extension
library (libXext), the X toolkit library (libXt), the Athena
widget set (libXaw), the miscellaneous utilities library
(libXmu), and the PEX library (libPEX5).
o C language header files for the preceding libraries.
- 3 -
X Window System 5.3 Release Notes
o Standard X client programs (xterm, xclock, and so on) and X
program development tools (xmkmf, imake, and makedepend).
o On-line manual pages for library functions and client programs.
The Motif software corresponds to the 1.2.5 distribution from the Open
Software Foundation. Motif software in this product includes:
o Shared and static versions of the standard Motif libraries,
including the Motif widget set (libXm), the Motif resource
manager (libMrm), and the User Interface Language library
(libUil).
o C language header files for the preceding libraries.
o The Motif window manager (mwm) and the User Interface Language
compiler (uil).
o The Widget Meta Language (WML) facility. This can be found in the
directory /usr/lib/Xm/wml.
o Unsupported Motif demo programs in source form. These can be
found in the directory /usr/lib/Xm/demos.
o On-line manual pages for library functions and client programs.
This release includes several enhancements and additions to the
standard X11R5 and Motif software. These include:
o Support for color pixmaps in X Pixmap (Xpm) format. This includes
the Xpm library (libXpm), header file, sample icons
(/usr/include/X11/bitmaps/*.xpm), a pixmap viewer (sxpm), a
pixmap editor (pixmap), and a program for installing a pixmap on
the root window (xpmroot). In addition, the Motif window manager
and the xbiff mailbox monitoring client have been enhanced to
display Xpm format color icons.
o An enhanced version of the X Display Manager (xdm). This provides
a login window with a Motif Graphical User Interface (GUI) and
configurable messages and graphics.
o NightLaunch(TM), a graphical program launcher. NightLaunch allows
you to create windows with icons representing other programs, and
launch those programs by activating the icons.
o NEdit, a text editor with a Motif GUI. NEdit provides full-
featured text editing, yet is simple to learn and use.
- 4 -
Release Notes 5.3 X Window System
o An enhanced terminal emulator (nterm). Nterm supports all the
features of the standard terminal emulator, xterm, with the
addition of a Motif GUI and other small enhancements such as a
configurable scrollbar and blinking cursor.
o Xdiary, a simple calendar and datebook program.
o Xmessage, a program for displaying messages or asking questions
in a window.
6. New Features in this Release and Changes from Previous Releases
The following list describes the changes between this release and
release 5.2.1 of the X Window System product.
o A response file, allowing the package to be installed without
stopping and asking the user questions about the installation,
has been added to the software packaging files
o The platform imake configuration file found in
/usr/lib/X11/config has been renamed from powerunix.cf to
powerux.cf.
o The X Pixmap (Xpm) library has been updated to the latest version
(3.4h). None of the externally-visible interfaces have changed,
so the shared library version number was left at 4.5, the same as
in the previous release.
o Two new clients were added: xpmroot for installing pixmaps on the
root window, and xmessage for displaying messages in a window.
o The nedit text editor has been updated to version 4.0.1. This
version also includes a program called nc that allows additional
files to be opened in a running NEdit session. See nedit(1),
nc(1), and the nedit online help for more details.
o nterm and xterm have been fixed so that they inherit privileges
from their parent process. In the previous release, new terminal
windows always came up with all privileges denied.
o A serious bug in nterm that was causing it to use large amounts
of CPU time has been fixed. Now nterm and xterm have comparable
CPU utilization.
o The X Display Manager, xdm, has been fixed to properly set
privileges before executing the Xsession file. If the user
logging in is the superuser, all privileges are granted;
otherwise, all privileges are denied.
- 5 -
X Window System 5.3 Release Notes
o A bug in the Motif library that was causing xdm to crash under
certain circumstances has been fixed. The symptom of this problem
was the xdm login window not reappearing after logging out.
o The Night Hawk image displayed in the xdm window has been changed
to the Concurrent logo. The old Night Hawk image can be restored
by editing the file /usr/lib/X11/xdm/Xresources and changing
``xlogin*pixmap: BUILTIN'' to ``xlogin*pixmap: NIGHTHAWK''.
7. Use
The libraries and header files included with this product can be used
to compile C programs written for X11 or Motif. Most publicly-
distributed programs come with an Imakefile, from which a regular
Makefile can be generated. To do this, you can enter the command xmkmf
which will build a Makefile based on the Imakefile and the provided
X11 and/or Motif configuration files. The resulting Makefile will
have all the settings necessary to build your X program on PowerUX.
If you do not have an Imakefile or do not wish to use this facility,
you must set up the linking command manually. In addition to whichever
X or Motif libraries you need, all X programs need the following
libraries: -lsocket -lnsl -lgen -lresolv. Note: Under CX/UX, it was
necessary to add the library -lPW when linking Motif programs. This is
not necessary under PowerUX.
This release of the X Window System product contains version 1.2.5 of
the Motif library. Motif 1.2.5 contains new functionality and
enhancements to converge OSF/Motif 1.2.4 with the Common Desktop
Environment (CDE) 1.0 version of Motif. These changes are not covered
in the available Motif 1.2 documentation. The following sections,
taken from the Motif 1.2.5 documentation supplied by OSF, briefly
describe the new features of Motif 1.2.5.
7.1 Overview of Motif 1.2.5
The changes in Motif 1.2.5 fall into three categories: features to
support running applications in a CDE environment, usability changes
to allow for better interoperability with other graphical user
interfaces, and visual enhancements to provide better usability. All
of the changes can be enabled or disabled through the use of
resources. The default behavior is to use the functionality of Motif
1.2.4 and earlier, so none of these will take effect unless
specifically enabled.
Motif 1.2.5 maintains full backwards binary compatibility with Motif
1.2.4, so applications linked with the shared library in the previous
release of this product do not have to be re-linked. Furthermore,
- 6 -
Release Notes 5.3 X Window System
applications that make use of the new library will automatically have
access to the new features.
7.2 ColorObject
PURPOSE
The ColorObject allows applications run in a CDE environment to share
colors and change colors dynamically.
DESCRIPTION
The ColorObject is used exclusively by the CDE dtstyle client. Its
function is to manage four sets of colors used in the toolkit:
XmNprimaryColorSetId, XmNsecondaryColorSetId, XmNactiveColorSetId, and
XmNinactiveColorSetId. There is only one resource that is of interest
to the general user: useColorObject.
___________________________________________
| Name Default Access|
| Class Type |
|__________________________________________|
| useColorObject False CSG |
| UseColorObject Boolean |
|__________________________________________|
useColorObject
This Boolean resource enables and disables use of the
ColorObject. By default it is False meaning that the ColorObject
is not used.
7.3 Integrating Selection and Transfer on Button1
PURPOSE
The second button on a three button mouse is used for the Adjust
function in the OPEN LOOK graphical user interface. In Motif, this
button is bound to PrimaryTransfer. The usability issue arises because
PrimaryTransfer is a destructive action.
DESCRIPTION
Enabling Button2 as the Adjust function is done through the Display
resource enableBtn1Transfer. The default value for this resource is
False.
________________________________________________
| Name Default Access|
| Class Type |
|_______________________________________________|
| enableBtn1Transfer False C |
|_______________________________________________|
- 7 -
X Window System 5.3 Release Notes
| EnableBtn1Transfer Boolean |
|_______________________________________________|
7.4 Tab Between Buttons
PURPOSE
Most graphical user interfaces allow the Tab key to move between the
buttons in a window. In Motif, the buttons are typically one group so
that when the user tabs to the group, access to the other buttons is
through the arrow keys. This change allows the Tab key to be used to
move through a group of PushButtons widgets and gadgets, ArrowButton
widget and gadgets, and DrawnButton widgets.
DESCRIPTION
This feature modifies the Primitive widget actions and the Gadget
actions for KNextField and KPrevField to move as an arrow key until
the boundary of the list is reached. When at the boundary of the list,
these actions act as KNextField and KPrevField do now. The change
takes effect only if the enableButtonTab Boolean resource is set to
True. The default value for enableButtonTab is False.
____________________________________________
| Name Default Access|
| Class Type |
|___________________________________________|
| enableButtonTab False C |
| EnableButtonTab Boolean |
|___________________________________________|
7.5 Menu Button and Key in CascadeButton
PURPOSE
Under previous versions of Motif, the CascadeButtons in either a menu
bar or a menu do not post the associated menu when the Menu button or
key is pressed. The purpose of this usability change is to enable
interoperability with other graphical user interfaces.
DESCRIPTION
The translations of the CascadeButton is changed to duplicate the
action of the Select button and key for the Menu button and key. This
functionality is controlled by the enableMenuInCascade resource. This
is a Boolean resource that defaults to False.
________________________________________________
| Name Default Access|
| Class Type |
|_______________________________________________|
|_______________________________________________|
- 8 -
Release Notes 5.3 X Window System
| enableMenuInCascade False C |
| EnableMenuInCascade Boolean |
|_______________________________________________|
7.6 XmFileSelectionBox
PURPOSE
The Motif 1.2.5 XmFileSelectionBox widget provides an alternate layout
for better usability. The API for the XmFileSelectionBox has the same
API as the Motif standard with the addition of three new resources.
The new layout features:
o An additional text entry area for use in selecting the directory.
o Removal of path information from the default text that is loaded
into the filter text entry area.
o Removal of path information from the Directory List and File List
contents.
o Removal of path information from the Selection text area.
o Scroll bars of the Directory List and File List are now enabled
on an ``as needed'' basis, instead of being constantly visible.
o Geometry layout is modified to support these changes.
DESCRIPTION
While the new XmFileSelectionBox has some new features, it remains
completely binary compatible with the old XmFileSelectionBox. The API
for the XmFileSelectionBox is unchanged with the following additional
resources. Applications should be designed so as not to depend on the
presence of these resources; all are silently ignored if the
application is linked to the older implementation of the File
Selection Box. Note that there are no XmN_______ style defines
provided for these resources; this is to avoid creating a source
compatibility dependency on the CDE Xm header files. Application code
should use string immediate values for the resource name and class.
Specifying values for resources with enumerated types (such as
PathMode below) present a special case. When specifying values for the
resource in application code, a numeric value must be used because
constants are not defined in the header files. When specifying values
in a resource file, the string identifiers must be used. In these
cases, the string value is listed in parentheses next to the numeric
value.
- 9 -
X Window System 5.3 Release Notes
_______________________________________________________
| Name Default Access|
| Class Type |
|______________________________________________________|
| pathMode 0 (PATH_MODE_FULL) C |
| PathMode PathMode |
|______________________________________________________|
| fileFilterStyle 0 (FILTER_NONE) C |
| FileFilterStyle FileFilterStyle |
|______________________________________________________|
| dirTextLabelString NULL C |
| DirTextLabelString XmString |
|______________________________________________________|
pathMode
Specifies if the alternate layout and functionality should be
used. The following values are available:
o 0 (PATH_MODE_FULL)
o 1 (PATH_MODE_RELATIVE)
The default is 0 (PATH_MODE_FULL) so that the look and feel is
identical to the Motif 1.2.4 widget. When this resource is 1
(PATH_MODE_RELATIVE), the XmFileSelectionBox uses the CDE style
layout.
fileFilterStyle
This resource takes effect when pathMode is 1
(PATH_MODE_RELATIVE). It is ignored when pathMode is 0
(PATH_MODE_FULL). The following values are supported:
o 0 (FILTER_NONE)
o 1 (FILTER_HIDDEN_FILES)
When this resource is 0 (FILTER_NONE), all files including the
``dot'' files are listed in the file and directory scrolling
lists. Setting this resource to 1 (FILTER_HIDDEN_FILES), removes
all of the ``dot'' files from the file and directory scrolling
lists. The one exception is that the ``..'' directory in the
directory list is always displayed.
dirTextLabelString
The XmString specified in this resource is used as the label
above the Directory TextField. If the pathMode resource is 0
(PATH_MODE_FULL), this resource is ignored.
- 10 -
Release Notes 5.3 X Window System
7.7 Multiple Key Bindings
PURPOSE
The CDE designers identified that some of the actions in the Motif
widgets needed to have the MS Windows equivalent key bindings. There
is also a need to support the special keys on the Sun keyboard
directly in the widgets. The purpose of this usability change is to
enable interoperability with other graphical user interfaces.
DESCRIPTION
The current implementation of the Intrinsics and Motif toolkits does
not allow more than one key binding per action in the translation
table. The XtNbaseTranslations of the widgets is changed to add the
translations specified by the user model team. These translations are
merged into the resource database so that they do not override an
application's specification of XtNbaseTranslations. This
functionality is controlled by enableMultiKeyBindings. This is a
Boolean resource that defaults to False.
___________________________________________________
| Name Default Access|
| Class Type |
|__________________________________________________|
| enableMultiKeyBindings False C |
| EnableMultiKeyBindings Boolean |
|__________________________________________________|
7.8 Visual Enhancements
PURPOSE
Motif 1.2.5 provides the following visual enhancements:
o Add a check glyph to the ToggleButton to show state more clearly
o Add a circular ToggleButton for MS Windows similarity
o Change the ToggleButton fill color to show state more clearly
o Change the CascadeButton to have an etched out border when active
for consistency
o Reduce the size of default PushButtons by putting the location
cursor in the ``trough''
o Remove the thumb from the read-only Scale to distinguish it from
the Scale
DESCRIPTION
Each of the visual enhancements is enabled using a resource. These
- 11 -
X Window System 5.3 Release Notes
resources all default to False so that the look is unchanged from
Motif 1.2.4. Most of the enabling resources are resources on the
XmDisplay object. They do not have the typical XmN prefix.
________________________________________________________________
| Name Default Access|
| Class Type |
|_______________________________________________________________|
| enableToggleColor False C |
| EnableToggleColor Boolean |
|_______________________________________________________________|
| enableToggleVisual False C |
| EnableToggleVisual Boolean |
|_______________________________________________________________|
| enableEtchedInMenu False C |
| EnableEtchedInMenu Boolean |
|_______________________________________________________________|
| defaultButtonEmphasis 0 (EXTERNAL_HIGHLIGHT) C |
| DefaultButtonEmphasis DefaultButtonEmphasis |
|_______________________________________________________________|
enableToggleColor
Creating an application with enableToggleColor True changes the
fill color of the ToggleButton widget and gadget to use the
highlight color. In CDE the highlight color is calculated and set
by the ColorObject. When this resource is False, the fill color
of the ToggleButton widget and gadget remains the same.
enableToggleVisual
Creating an application with enableToggleVisual set to True
allows the check mark glyph and circular style of the
ToggleButton widget and gadget. When this resource is False, the
look of the ToggleButton widget and gadget is unchanged.
enableEtchedInMenu
Creating an application with enableEtchedInMenu set to True
changes the shadowing of the CascadeButton widget and gadget to
be depressed when the control is activated. When this resource is
False, the CascadeButton widget and gadget have the normal etched
out appearance.
defaultButtonEmphasis
Specifies the look of the PushButton widget and gadget when the
control is the default. The following values are available:
o 0 (EXTERNAL_HIGHLIGHT)
o 1 (INTERNAL_HIGHLIGHT)
- 12 -
Release Notes 5.3 X Window System
Default buttons are drawn as an etched out button which is then
enclosed with another etched in border. When this resource is 0
(EXTERNAL_HIGHLIGHT), the location cursor appears outside of the
second border. When this resource is 1 (INTERNAL_HIGHLIGHT), the
location cursor appears in between the two etched borders to
minimize the space needed.
The changes to the XmScale widget are intended to give users an
indication of when the scale is read-only and when they can manipulate
the value. The new gauge visual is similar to the current XmScale's
look. The gauge removes the thumb from the XmScale and uses colors to
indicate the value. The following resource on the XmScale widget
controls this appearance.
________________________________________
| Name Default Access|
| Class Type |
|_______________________________________|
| enableGauge False C |
| EnableGauge Boolean |
|_______________________________________|
enableGauge
Creating an XmScale widget with enableGauge True changes the look
of the XmScale. The XmScale does not have a thumb control, so the
user has a clear indication that the XmScale is a read-only
control. The value of the XmScale is indicated by the colors
that fill the XmScale. When enableGauge is False, the XmScale has
a thumb control.
8. Direct Software Support
Software support is available from a central source. If you need
assistance or information about your system, please contact the Harris
Software Support Center at our toll free number (1-800-245-6453). Our
customers outside the continental United States can contact us
directly at 1-305-971-6248. The Software Support Center operates
Monday through Friday from 8 a.m. to 7 p.m., Eastern Standard time.
Calling the Software Support Center gives you immediate access to a
broad range of skilled personnel and guarantees you a prompt response
from the person most qualified to assist you. If you have a question
requiring on-site assistance or consultation, the Software Support
Center staff will arrange for a field analyst to return your call and
schedule a visit.
Harris provides a Software Action Request (SAR) form which our
customers can fill out and submit to their local field analyst or the
- 13 -
X Window System 5.3 Release Notes
Software Support Center. This procedure ensures that your request is
entered into our SAR database for follow-up and action.
To obtain copies of SAR forms, call the Software Support Center and
request form number CSD1833B.
- 14 -
Contents
1. Introduction.................................................. 1
2. Documentation................................................. 1
3. Prerequisites................................................. 2
3.1 Software Prerequisites................................... 2
3.2 Hardware Prerequisites................................... 2
4. Installation.................................................. 2
4.1 Installation Options..................................... 3
5. Product Description........................................... 3
6. New Features in this Release and Changes from Previous
Releases...................................................... 5
7. Use........................................................... 6
7.1 Overview of Motif 1.2.5.................................. 6
7.2 ColorObject.............................................. 7
7.3 Integrating Selection and Transfer on Button1............ 7
7.4 Tab Between Buttons...................................... 8
7.5 Menu Button and Key in CascadeButton..................... 8
7.6 XmFileSelectionBox....................................... 9
7.7 Multiple Key Bindings.................................... 11
7.8 Visual Enhancements...................................... 11
8. Direct Software Support....................................... 13
- i -
_________________________________________________________________
HARRIS
COMPUTER SYSTEMS
_________________________________________________________________
X Window System
Version 5.3
Release Notes
0890298-5.3
July 1996
_________________________________________________________________
Trademark Acknowledgments
Night Hawk is a registered trademark of Concurrent Computer
Corporation.
NightLaunch is a trademark of Concurrent Computer Corporation.
OSF/Motif is a trademark of Open Software Foundation, Inc.
PowerHawk is a registered trademark of Concurrent Computer
Corporation.
Power MAXION is a registered trademark of Concurrent Computer
Corporation.
X Window System is a trademark of X Consortium, Inc.
return to index
================================================================================