CXUX_Tools Products are:
NightProbe_2.1 fetch_1.0 tex_1.0
NightSim_1.1 floppy_5.3 trustedwm_1.0
NightView_4.4 id_tools_1.0 vcomx25_1.1
WebTrack_1.2b night_trace_1.3 vmic_1.1
blacker_1.1 posix_1003.5_88k_2.0 xig_5.0
cnd_6.2 sbs_7.0 xwindow-v11_5.1.1
elanlm_2.3.3 sclib_2.2
================================================================================
NIGHTPROBE -
VERSION 2.1
RELEASE NOTES
Harris Computer Systems Division
1. Introduction
NightProbeTM is a real-time tool that is part of the NightStarTM
development environment. It provides a graphical user interface
that permits real-time recording, viewing, and modification of
program data within one or more executing programs. It can be
used during development and operation of applications, including
simulations, data acquisition, and system control.
The features and capabilities of NightProbe include:
o An X Window SystemTM and OSF/MotifTM graphical user interface
provides data sampling control and a spreadsheet interface
for data recording, monitoring, and modification.
o Several timing sources, including the system clock and the
frequency-based scheduler, are provided for controlling the
sampling rate. The user may explicitly start, suspend, and
stop sampling using the graphical user interface.
o Any static memory location of any C or Fortran process on any
processor may be sampled by NightProbe. The symbol table
browsing facilities support all scalar data types in those
programming languages.
__________
- These release notes cover the following products: NightProbe
NightProbe, NightTrace, and NightStar are trademarks of Harris
Computer Systems Corporation.
X Window System is a trademark of X Consortium, Inc.
OSF/Motif is a trademark of the Open Software Foundation, Inc.
- 1 -
CX/UX NightProbe 2.1 Release Notes
o Sampled data can be monitored interactively or written to a
file or shared memory area in real time. It can also be
passed to the NightTraceTM daemon for later analysis.
o NightProbe can be run on a different processor from the
target program, which minimizes NightProbe's impact on the
target program's performance.
o NightProbe allows data locations to be specified using
logical addresses or the symbolic names that appear in the
program source code. The data addresses and data types are
then located by searching the symbol table in the executable
program file. NightProbe can present lists of the static
variables in programs, and the user may select the variables
of interest using the graphical user interface.
o Configuration files can be created, edited, and saved to
retain target selections and display layout, allowing for
fast start-up.
o No modifications to source code or recompilations are
required for use with NightProbe.
NOTE: NightProbe is supported on Series 4000 and Series 5000
systems running CX/UX and on Series 6000 systems running
Power UNIX. This version of the release notes is for CX/UX.
2. Documentation
The following table lists the documentation available with this
release:
___________________________________________
| Manual Name Pub. Number |
|___________________________|______________|
| NightProbe Quick Reference| 0890465-010 |
| NightProbe Release Notes | 0890465-2.1C|
|___________________________|______________|
Additional copies may be ordered by contacting the Harris Software
Support Center. The toll-free number for calls outside of Florida
is 1-800-245-6453. For calls within Florida or outside the
continental United States the number is 1-305-971-6248.
- 2 -
Release Notes 2.1 CX/UX NightProbe
3. Prerequisites
Prerequisites for CX/UX NightProbe Version 2.1 are as follows:
3.1 Software Prerequisites
o The CX/UX or CX/RT operating system, Release 7.1 or later.
Note that the CX/RT development product is required to build
a CX/UX kernel with the data recording and frequency-based
scheduler facilities configured.
o The X Window System, Version 11, Release 4.0 or later.
o The Elan License ManagerTM.
3.2 Hardware Prerequisites
o Any Series 4000 or 5000 system.
o An X Window System display device (e.g., X terminal).
4. Installation
The NightProbe installation tape is a standard cpio format product
tape that should be installed using the setup command. The tape
contains the executable programs, support files, and the man and
catman pages. Please refer to the CX/UX System Administration
Manual, Chapter 3, for instructions on software installation.
4.1 File List
The installation tape for the NightProbe product includes these
files:
/usr/bin/nprobe
the application program
__________
Elan License Manager is a trademark of Elan Computer Group,
Inc.
- 3 -
CX/UX NightProbe 2.1 Release Notes
/usr/lib/NightProbe/np-fbs
the frequency-based scheduler timing program
/usr/lib/NightProbe/Install
product installation script
/usr/lib/NightProbe/NightProbe_symlinks
internal database of symbolic link requirements
/usr/lib/NightProbe/mklinks
command to update symbolic links
/usr/lib/X11/app-defaults/Nprobe
basic application default resources file
/usr/lib/X11/app-defaults/Nprobe-color
application default resources file for color displays
/usr/lib/X11/app-defaults/Nprobe-mono
application default resources file for monochrome
displays
/usr/lib/locale/C/LC_MESSAGES/NightProbe-help
English language help message texts
/usr/lib/locale/C/LC_MESSAGES/NightProbe-text
English language message texts
/usr/catman/u_man/man1/nprobe.1.z
compressed pre-formatted manual page
/usr/man/u_man/man1/nprobe.1
nroff source for manual page
The installation script will create the necessary symbolic links
for the files that are referenced by absolute path name-for the
case where the product is installed from some directory other than
the root directory.
4.2 Installation Procedure Summary
Here is a summary of the installation steps you will need to take
with super-user privileges to install the NightProbe product from
an installation tape.
1. Change the current working directory to the directory that
will be the product load point. Normally this is the root
directory, /, but may be another directory if you wish:
- 4 -
Release Notes 2.1 CX/UX NightProbe
cd directory
2. If this is a directory other than / and there is no usr
subdirectory, then create a usr subdirectory:
mkdir usr
3. Follow standard software product installation procedures to
load the NightProbe product using the setup command.
4. Run the NightProbe installation script using these commands:
cd usr/lib/NightProbe
./Install
The Install script makes the symbolic links, if necessary, and
updates the ``whatis'' database. The script has a -H option to
get a usage help message that explains some options that are
available.
The nprobe executable of the NightProbe product must be run with
the Elan License Manager. Follow the steps in the Obtaining
Licenses section of the Elan License Manager Release Notes
(0891055); the feature alias for NightProbe is NightProbe. 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 Harris Software Distribution at 1-
800-666-5405.
5. Cautions
Target programs must be compiled and linked with debugging
information (the -g compiler and linker option) in order to obtain
the full functionality of NightProbe, specifically identification
of memory locations by name and browsing the symbol table.
Only static variables can be sampled (i.e., variables that are not
on the stack or in registers).
Currently NightProbe does not handle indirection, literal
enumeration values, Fortran character types, or Fortran datapools.
It does handle enumeration position numbers.
The kernel must be configured for data recording and, if the FBS
is a timing source, the frequency-based scheduler.
Users of NightProbe must be granted the ACC_USERMAP access
permission.
- 5 -
CX/UX NightProbe 2.1 Release Notes
Input and output file formats are not compatible between rtutil
and rtdatarec and NightProbe.
Additional information about NightProbe can be obtained from the
nprobe(1) system manual page and the NightProbe Quick Reference.
6. Release Description
Release 2.1 of NightProbe introduces several new features:
o C structures and unions are aggregates. Aggregates are
displayed both in the symbols list and in the scopes list.
As an item in the symbols list, an aggregate can be selected
for monitoring as one large data item. As an item in the
scopes list, you may go down into an aggregate and select
individual elements for monitoring.
o Elements and element ranges (slices) of arrays can be
selected simply by specifying the array index(es) after the
symbol name.
o Function scopes, packages, aggregates, and source files can
be filtered individually in the symbol table browser.
o The process list displayed for program selection shows user
names and can filter the display based on user name, program
name, and process ID.
In addition to these new features, several deficiencies of the
user interface were corrected.
7. Direct Software Support
Software support is available from a central source. When you
need assistance or information about your system, please contact
the Harris Software Support Center at our toll free number (800-
245-6453). Our customers outside the continental United States
can contact us directly at 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
- 6 -
Release Notes 2.1 CX/UX NightProbe
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.
- 7 -
CONTENTS
1. Introduction.............................................. 1
2. Documentation............................................. 2
3. Prerequisites............................................. 3
3.1 Software Prerequisites............................... 3
3.2 Hardware Prerequisites............................... 3
4. Installation.............................................. 3
4.1 File List............................................ 3
4.2 Installation Procedure Summary....................... 4
5. Cautions.................................................. 5
6. Release Description....................................... 6
7. Direct Software Support................................... 6
- i -
_________________________________________________________________
HARRIS
COMPUTER SYSTEMS
_________________________________________________________________
NIGHTPROBE
VERSION 2.1
RELEASE NOTES
0890465-2.1C
September 1995
_________________________________________________________________
return to index
================================================================================
NIGHTSIM(TM) -
VERSION 1.1
RELEASE NOTES
Harris Computer Systems Division
1. Introduction
NightSim is a real-time tool that is part of the NightStar
development environment. It provides a Graphical User
Interface (GUI) to the frequency-based scheduler (FBS) and
performance monitor real-time facilities.
This is the first general release of the NightSim product.
2. Documentation
The following documentation is included with this release:
________________________________________
| Manual Name Pub. Number|
|_________________________|_____________|
| NightSim Quick Reference| 0890458-000|
| NightSim Release Notes | 0890458-1.1|
|_________________________|_____________|
Additional copies may be ordered by contacting the Harris
Software Support Center. The toll-free number for calls
outside of Florida is 1-800-245-6453. For calls within
Florida or outside the continental United States the number
is 1-305-971-6248.
__________
- These release notes cover the following products:
NightSim
NightSim is a trademark of Harris Corporation Computer
Systems Division.
- 1 -
NightSim 1.1 Release Notes
3. Prerequisites
Prerequisites for NightSim Version 1.1 are as follows:
3.1 Hardware
o Any Series 4000 or Series 5000 system
o A bitmap display device, such as an X terminal.
3.2 Software
o CX/UX 6.1 or later
o X Window System(TM), Version 11, Release 4.0 or later
o Elan License Manager(TM)
o The system must be configured with the FBS kernel
option. To use the performance monitor features of
NightSim, the HIGHRESTIMING option must also be
enabled.
For more information about configuring your system to
support NightSim, see the NightSim Quick Reference.
4. Installation
The NightSim installation tape is in cpio format. It
contains the NightSim executables, support files, and man
and catman pages. Please refer to the CX/UX System
Administration Manual, Chapter 3, for general instructions
on software installation.
This product must logically reside in the /usr partition. If
you do not have enough disk space to physically install
__________
X Window System is a trademark of X Consortium, Inc.
Elan License Manager is a trademark of Elan Computer
Group, Inc.
- 2 -
Release Notes 1.1 NightSim
NightSim on /usr, then you can install it somewhere else.
The installation script will automatically make symbolic
links from /usr to where NightSim is installed.
The files (or symbolic links) must be installed as:
o /usr/bin/nsim
o /usr/lib/NightSim/Install
o /usr/lib/NightSim/NightSim_symlinks
o /usr/lib/NightSim/mklinks
o /usr/lib/NightSim/nsim-errors
o /usr/lib/NightSim/nsim-help
o /usr/lib/NightSim/XKeysymDB-R5
o /usr/lib/X11/app-defaults/Nsim
o /usr/lib/X11/app-defaults/Nsim-color
o /usr/man/u_man/man1/nsim.1
o /usr/catman/u_man/man1/nsim.1.z
o /usr/src/PRODUCTS/NightSim_1.1_lpr
o /usr/src/PRODUCTS/NightSim_1.1_rel
o /usr/src/PRODUCTS/NightSim_1.1_si
To install NightSim, follow these steps:
o Sign on as root, or use the su command to become root.
o If you want to physically install NightSim under /usr,
then execute cd / to position yourself under the root
directory.
If you want to physically install NightSim under the
partition named /partition, then execute the following
commands (in the order specified):
mkdir -p /partition/NightSim_1.1/usr
- 3 -
NightSim 1.1 Release Notes
cd /partition/NightSim_1.1
o Issue the command cpio -iBcvdum < /dev/rmt/0mn to read
in the first two files setup and tape_list with no
rewind. (NOTE: the installation tape is assumed to be
loaded on drive 0.)
o Issue the command ./setup -d /dev/rmt/0mn to run a
menu-driven program that installs the NightSim product.
o The setup program displays a prompt similar to: Enter
the name of the running kernel or if /unix. Press
the carriage return key. The following message is
displayed: Non-generic boot. Assuming System
Generation not to be done.
o The next message displayed is: The first product tape
should be loaded on /dev/rmt/0mn. Is this the case? (y
| n). Type y.
o Expect a pause, then a menu will prompt: Enter the
numbers of the actions you would like to perform. Enter
the number corresponding to Load NightSim object files.
o As files come onto the system under the directories
usr/bin, usr/lib, usr/man, and usr/catman, there will
be a message similar to the following: Loading NightSim
object files.
o When the menu returns, select the Exit option, then
remove the tape from the drive.
o Execute cd ./usr/lib/NightSim to position yourself in
the NightSim support directory. If you want to see what
the installation script will do, you can execute it
with the -n option, which prints what it would do
without doing anything: ./Install -n. When you are
satisfied, execute the installation script without the
-n option: ./Install.
o Installation of NightSim version 1.1 is now complete.
The nsim executable of the NightSim product must be run with
the Elan License Manager. Follow the steps in the "Obtaining
Licenses" section of the Elan License Manager Release Notes
(0891055-Rel.#); the feature alias is NightSim. 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 Harris Software Distribution
- 4 -
Release Notes 1.1 NightSim
at 1-800-666-5405.
5. Cautions
The purpose of the NightSim Quick Reference is only to
assist you in getting started with the use of NightSim. It
does not contain the detailed procedural information that a
user's guide typically provides. For additional assistance
with using NightSim, consult the on-line help and the
nsim(1) man page.
6. Features in this Release
6.1 Frequency-Based Scheduler Functions
NightSim provides an intuitive GUI that allows you to
perform the full range of functions associated with the FBS.
Functions include configuring a scheduler, selecting a
timing source, scheduling programs, saving and restoring
scheduler configurations, running a simulation, and viewing
scheduling data.
6.2 Performance Monitor Functions
NightSim also provides a comprehensive GUI for the
performance monitor. Functions include selecting a
scheduler, enabling and disabling monitoring for each
process, clearing performance values, setting the timing
mode, and sending performance data either to the screen or
to a text file. Data that is to be sent to the screen can
be filtered and sorted in a variety of ways.
7. Direct Software Support
Software support is available from a central source. When
you need assistance or information about your system, please
contact the Harris Software Support Center at our toll free
number (800-245-6453). Our customers outside the
continental United States can contact us directly at 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
- 5 -
NightSim 1.1 Release Notes
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.
- 6 -
CONTENTS
1. Introduction.............................................. 1
2. Documentation............................................. 1
3. Prerequisites............................................. 2
3.1 Hardware............................................. 2
3.2 Software............................................. 2
4. Installation.............................................. 2
5. Cautions.................................................. 5
6. Features in this Release.................................. 5
6.1 Frequency-Based Scheduler Functions.................. 5
6.2 Performance Monitor Functions........................ 5
7. Direct Software Support................................... 5
- i -
_________________________________________________________________
HARRIS
COMPUTER SYSTEMS
_________________________________________________________________
NIGHTSIM(TM)
VERSION 1.1
RELEASE NOTES
0890458-1.1
August 1994
_________________________________________________________________
return to index
================================================================================
CX/UX(TM) NIGHTVIEW(TM) -
VERSION 4.4
RELEASE NOTES
Harris Computer Systems Division
1. Introduction
NightView is a general-purpose, source-level debugger for
Ada, C, and Fortran. NightView can be used to debug
multiple processes on the local system or on different
hosts.
NOTE: NightView is supported on Series 4000 and Series 5000
systems running CX/UX and on systems based on the
PowerPC(TM) running PowerMAX OS(TM). This version of the
release notes is for CX/UX.
NightView 4.4 features include:
o Remote debugging. NightView can be used to debug
processes on a remote system.
o Repeated debugging. 4.4 has features that make it easy
to debug the same programs many times with little user
interaction.
__________
- These release notes cover the following products:
NightView
CX/UX is a trademark of Concurrent Computer Corporation.
NightView is a trademark of Concurrent Computer
Corporation.
PowerPC is a trademark of IBM Corp.
PowerMAX OS is a trademark of Concurrent Computer
Corporation.
- 1 -
CX/UX NightView 4.4 Release Notes
NOTE: Installation procedures for this product are slightly
different from those for other Concurrent products. Please
read the Installation section of these release notes before
attempting to install this product, and carefully follow the
installation instructions.
NOTE: In these release notes, chapter and section
references are to the NightView User's Guide, unless stated
otherwise.
2. Documentation
The following documentation is included with this release:
___________________________________________
| Manual Name Pub. Number |
|___________________________|______________|
| NightView User's Guide | 0890395-150 |
| NightView Pocket Reference| 0890475-010 |
| NightView Release Notes | 0890395-4.4C|
|___________________________|______________|
Additional copies may be ordered by contacting the
Concurrent Software Support Center. The toll-free number
for calls outside of Florida is 1-800-245-6453. For calls
within Florida or outside the continental United States the
number is 1-954-971-6248.
3. Prerequisites
Prerequisites for NightView Version 4.4 are as follows:
3.1 Hardware
o Any Series 4000 or Series 5000 system.
o A bitmapped display device, such as an X terminal, if
you are using NightView's graphical user interface.
- 2 -
Release Notes 4.4 CX/UX NightView
3.2 Software
o CX/UX 6.1 or later.
o Kernel patch cx7.1-016, if you are running CX/UX 7.1
and you are on a Series 5000 system. The patch is
necessary for any release of NightView, not just
release 4.4.
o The system must not be configured with the
PTRACE_BCS_CONFORMANCE kernel option. This option
interferes with the way NightView controls programs.
If this option is set, NightView hangs during
initialization.
o An X server is required if you are using NightView's
graphical user interface. (The X server may be built
into the bitmapped display device.)
o The X Window System(TM), Version 11 is recommended if
you are using NightView's graphical user interface.
o A Fortran compiler of at least release level 7.2, if
you are using Fortran and building ELF executables.
CX/UX 7.1 is required for ELF.
o An Ada compiler of at least release level 7.1.1, if you
are debugging Ada. This requires CX/UX 7.1 or later.
Patch ada7.1.1-001 is recommended. That patch fixes
problems with the debugging information for multi-
dimensioned arrays with dynamic bounds, for the
predefined type duration and for a complex form of
referencing unconstrained arrays.
o Linker patch cx7.1-040 if you are debugging programs
with shared objects that have debugging information,
such as dynamically linked Ada programs.
o Elan License Manager(TM). See the Installation section
of these release notes for details.
__________
X Window System is a trademark of The Open Group.
Elan License Manager is a trademark of Elan Computer
Group, Inc.
- 3 -
CX/UX NightView 4.4 Release Notes
For more information about configuring your system to
support NightView, see appendix B, System Resource
Requirements, in the NightView User's Guide.
4. Installation
The NightView installation tape is in cpio format. It
contains the NightView executables, online documentation,
man and catman pages. Please refer to the CX/UX System
Administration Manual, Chapter 3, for general instructions
on software installation.
This product must logically reside in the /usr partition.
If you do not have enough disk space to physically install
NightView on /usr, then you can install it somewhere else.
The installation script automatically makes symbolic links
from /usr to where NightView is installed.
If you have NightView previously installed on your system,
then you should do the following:
o Sign on as root, or use the su program to become root.
o Execute cd /usr/lib/NightView to position yourself in
the old NightView support directory.
o If a file named NightView_symlinks_installed exists in
this directory, or if a file named
NightView_symlinks_installed.hostname exists in this
directory and hostname is the name of the machine upon
which you wish to install NightView, then execute to
remove any symbolic links that were created on behalf
of this prior version of NightView.
You should back up any old versions of the NightView files
and remove them.
The new files (or symbolic links) must be installed as:
o /usr/bin/nview
o /usr/bin/xnview
o /usr/lib/NightView-4.4/NightView.p
o /usr/lib/NightView-4.4/ReadyToDebug
o /usr/lib/NightView-4.4/endian.h
o /usr/lib/NightView-4.4/run_NightView.p
o /usr/lib/NightView-4.4/ticks
o /usr/lib/NightView-4.4/xnview
- 4 -
Release Notes 4.4 CX/UX NightView
o /usr/lib/NightView/DemoText
o /usr/lib/NightView/Demos/tut-c-1/Demo.mk
o /usr/lib/NightView/Demos/tut-c-1/Script
o /usr/lib/NightView/Demos/tut-c-2/Demo.mk
o /usr/lib/NightView/Demos/tut-c-2/Script
o /usr/lib/NightView/Install
o /usr/lib/NightView/NightView_symlinks
o /usr/lib/NightView/Tutorial/child.a
o /usr/lib/NightView/Tutorial/child.c
o /usr/lib/NightView/Tutorial/child.f
o /usr/lib/NightView/Tutorial/main.a
o /usr/lib/NightView/Tutorial/main.c
o /usr/lib/NightView/Tutorial/main.f
o /usr/lib/NightView/Tutorial/msg.h
o /usr/lib/NightView/Tutorial/msg.i
o /usr/lib/NightView/Tutorial/parent.a
o /usr/lib/NightView/Tutorial/parent.c
o /usr/lib/NightView/Tutorial/parent.f
o /usr/lib/NightView/Tutorial/signals.a
o /usr/lib/NightView/XKeysymDB-R5
o /usr/lib/NightView/app-defaults/Nview
o /usr/lib/NightView/app-defaults/Nview-color
o /usr/lib/NightView/app-defaults/Nview-mono
o /usr/lib/NightView/emacs/info/NightView-info*
(There are several NightView-info files)
o /usr/lib/NightView/emacs/info/sinfo-info
o /usr/lib/NightView/fact.c
o /usr/lib/NightView/mklinks
o /usr/lib/NightView/nview-demo
o /usr/lib/NightView/nv.xwd.Z
o /usr/lib/X11/app-defaults/Nview
o /usr/lib/X11/app-defaults/Nview-color
o /usr/lib/X11/app-defaults/Nview-mono
o /usr/lib/emacs/info/NightView-info*
(There are several NightView-info files)
o /usr/lib/emacs/info/sinfo-info
(The files in /usr/lib/emacs/info are soft links into
/usr/lib/NightView/emacs/info.)
o /usr/man/u_man/man1/nview.1
o /usr/catman/u_man/man1/nview.1.z
o /usr/catman/u_man/man1/NightView.1.z
(The last two are linked to each other.)
To install NightView, follow these steps:
o Sign on as root, or use the su program to become root.
- 5 -
CX/UX NightView 4.4 Release Notes
o If you want to physically install NightView under /usr,
then execute cd / to position yourself under the root
directory.
If you want to physically install NightView under the
partition named /partition, then execute the following
commands (in the order specified):
mkdir -p /partition/NightView_4.4/usr
cd /partition/NightView_4.4
o Issue the command cpio -iBcvdum < /dev/rmt/0mn to read
in the first two files, setup and tape_list, with no
rewind. (NOTE: the installation tape is assumed to be
loaded on drive 0.)
o Issue the command to run a menu-driven program that
installs the new NightView product.
o The setup program displays a prompt similar to: Enter
the name of the running kernel or if /unix(R).
Press the RETURN key. The following message is
displayed: Non-generic boot. Assuming System
Generation not to be done.
o The next message displayed is: The first product tape
should be loaded on device /dev/rmt/0mn. Is this the
case? (y|n). Type y.
o Expect a pause, then a menu prompts: Enter the numbers
of the actions you would like to perform. Select Load
NightView object files.
o The next message displayed is: You are requesting that
NightStar(TM) optional products be loaded. They will
be loaded in subdirectories of ./usr/opt. Do you wish
to load instead in ./usr? (y | n). Type y.
__________
UNIX is a registered trademark licensed exclusively by
the X/Open Company Ltd.
NightStar is a trademark of Concurrent Computer
Corporation
- 6 -
Release Notes 4.4 CX/UX NightView
o There will be a message similar to: Loading NightView
object files as files come onto the system under the
directories usr/bin, usr/lib, usr/man, and usr/catman.
o When the menu returns, select Exit, and remove the tape
from the drive.
o Execute cd ./usr/lib/NightView to position yourself in
the NightView support directory. If you want to see
what the installation script will do, you can execute
it with the -n option, which prints what it would do
without doing anything: When you are satisfied,
execute without the -n option:
o Installation of NightView version 4.4 is now complete.
NightView must be run with the Elan License Manager. Follow
the steps in the Obtaining Licenses section of the Elan
License Manager Release Notes (0891055); the feature alias
is NightView. If you are debugging Ada, then you need an
additional license. The Elan feature alias to debug Ada is
NightView_Ada. 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
5.1 Ada Support
Many Ada features are supported, but some are not. See
section 3.10.1.1, Ada Expressions.
5.2 CX/UX Ptrace BCS Conformance Option
NightView is not supported on systems configured with the
PTRACE_BCS_CONFORMANCE kernel option.
- 7 -
CX/UX NightView 4.4 Release Notes
5.3 NightView on CX/SX
Only root can use NightView on a CX/SX system.
5.4 Breakpoint Command Streams
The current implementation of breakpoint command streams
does not include protection against concurrent access of
data structures internal to the debugger. Avoid referencing
other processes within breakpoint command streams. In
practice, this is rarely a problem.
5.5 Fortran 77 Arrays
There is currently a problem with Fortran 77 arrays passed
as formal arguments. The compiler generates a temporary
variable to optimize references to the array. This
temporary variable is then used in place of the original
array argument. If the original array argument is not used
later in the routine, then the lifetime of the argument is
very short and its value is discarded. If you try to use
the debugger to reference the argument later in the routine,
the results are undefined. You can do two things to avoid
running into this problem:
o Use the array later in the routine. For example, pass
the array as an argument to another routine. This
extends the lifetime of the original argument.
o Use the debugger to look at the array at the first
executable line of the routine. The value of the
original argument probably still exists at this point.
5.6 Scroll Bars
Some users have had a problem using the scroll bars in the
graphical user interface. When the up-arrow button on a
scroll bar is clicked, the window scrolls the length of the
entire window contents, rather than just one line. This
problem is caused by an inappropriate X resource, which has
apparently been copied from one user to another in much the
same way as $HOME/.profile files are often copied:
*XmScrollBar*translations: : Select()
- 8 -
Release Notes 4.4 CX/UX NightView
You should remove this resource from your $HOME/.Xdefaults
or whatever other means you use for setting X resources.
This resource affects any Motif(TM) application, not just
NightView.
5.7 Accessing Variables While in Prologue of Ada Subprogram
Because the Ada compiler generates line-number information
for code that comprises the prologue of a subprogram, you
may inadvertently set an eventpoint or stop your program at
such a location. The prologue is the code that the compiler
generates to set up the execution environment for a
subprogram; until that code completes execution, the
environment is incomplete. Attempts to access variables
while in the context of the prologue may result in errors
from NightView or may result in erroneous values.
If you suspect such a problem, you can determine whether you
are in the prologue by doing the following:
o Stop the program at the point where the referencing
problem occurs.
o Enter the command info frame.
o If the output from this command says something like
Could not obtain frame description information, then
you are probably stopped in the prologue.
To try and avoid this problem, do not set an eventpoint on
the lines containing a subprogram heading. If you want to
set the eventpoint at the beginning of the subprogram, use
the unit_name form of location specifier, rather than a
file_name and line_number. See section 7.1.2, Location
Specifiers.
__________
Motif is a trademark of Open Software Foundation, Inc.
- 9 -
CX/UX NightView 4.4 Release Notes
5.8 Shared Objects
For CX/UX 7.1 core files, NightView cannot always find
correct stack description information (tdesc) for shared
objects. This problem occurs when the shared objects are
built without position-independent code. This problem can
cause NightView to display the wrong results for any routine
other than the most recently called routine. For example, a
backtrace command may print the wrong information, or an up
command may fail. This is true for any release of
NightView, not just 4.4. This is not a problem for running
processes, only for core files.
We recommend that you build shared objects with position-
independent code if you plan to debug programs that use
them. For C and Fortran, use the -Zpic option. See cc(1)
or f77(1). For Ada, use -sm shared or -sm both. See Shared
Libraries and Shared-Objects on page 3-6 of the HAPSE
Reference Manual (Pub. No. 0890288-060).
5.9 Next and Fork
NightView has a minor problem doing a next over a fork
system call. You may sometimes see the child process stop
with an unexpected SIGTRAP signal. This is harmless.
Resume the process with either
resume 0
or
signal 0
to clear the signal. This problem can occur not only when
doing a next over a fork system call, but also when doing a
next over a routine that contains a nested fork call.
5.10 Attach and server_block
NightView cannot attach to a process waiting in
server_block. Also, the Stop button in the Debug Window and
the stop command do not work correctly for a process waiting
in server_block-the debugger indicates that the process is
stopped, but the process is not stopped. This is due to a
kernel problem, so it affects any release of NightView.
- 10 -
Release Notes 4.4 CX/UX NightView
6. New Features in This Release
6.1 Remote Debugging
NightView allows you to debug processes on a remote system.
You can use remote debugging to control processes on
multiple systems from a single invocation of NightView. You
can also use remote debugging to debug on a system that does
not have sufficient resources to run all of NightView with
your application.
Using either the Start Remote Dialogue... item in the
NightView menu, or the login command, you can establish a
dialogue on the remote system. The part of NightView that
implements the dialogue uses only a small part of the system
resources because it does not need to read debug information
or control a user interface.
Some systems require precise allocation of resources.
NightView lets you adjust the priority, CPU bias and memory
allocation of the dialogue to minimize the impact of
debugging on your application.
See section 3.4.3, Remote Dialogues.
It is likely that you will need to translate object
filenames used on the remote system so that the local system
can find them. See section 7.4.2.4, translate-object-file.
6.2 Repeated Debugging
Some debugging situations do not require as much interactive
control of the application. NightView 4.4 provides
mechanisms to reduce the amount of user interaction with
each process when that is desired. For information about
not stopping for new processes, see section 7.4.4.15, set-
children. For information about not stopping when a process
exits, see section 7.4.4.16, set-exit. For information
about not stopping when a process executes a new program,
see section 3.6.3, Restarting a Program.
- 11 -
CX/UX NightView 4.4 Release Notes
7. Changes from Previous Releases
7.1 NightView Menu
The Create Debug Window... menu item now has the mnemonic
D. A new menu item is added: Start Remote Dialogue....
See section 9.3.1.1, Debug NightView Menu.
7.2 Default Qualifier and Prompt
The initial default qualifier has changed from local to all,
which is a better default for remote debugging. The initial
prompt has changed from (%q) to (%a) . %a is a new prompt
specifier that prints the list of dialogues if the default
qualifier is all, and otherwise prints the qualifier (like
%q). This causes the normal prompt to appear the same as in
previous releases: (local) . See section 7.4.5.3, set-
qualifier and section 7.4.5.6, set-prompt.
7.3 Debugger Environment Variable
The environment variable NIGHTVIEW_ENV is set to 1 within a
dialogue shell. For remote debugging, it is set to the name
of the connecting system while the shell initializes (e.g.,
runs .profile). See section 3.4, Dialogues and section
7.4.2.1, login.
7.4 apply on dialogue
If there is a local dialogue, the debugger automatically
performs (local) apply on dialogue after all initialization
files have been read. See section 7.4.2.7, apply on
dialogue.
7.5 Unimplemented Features
Some unimplemented features and unwritten appendices have
been removed from the NightView User's Guide.
- 12 -
Release Notes 4.4 CX/UX NightView
7.6 select-context
NightView now performs auto-frame-mode processing as part of
the select-context command. See section 7.4.5.12,
set-auto-frame, and section 7.10.4, select-context.
8. Direct Software Support
Software support is available from a central source. When
you need assistance or information about your system, please
contact the Harris Software Support Center at our toll free
number (800-245-6453). Our customers outside the
continental United States can contact us directly at 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.
- 13 -
CONTENTS
1. Introduction............................................. 1
2. Documentation............................................ 2
3. Prerequisites............................................ 2
3.1 Hardware........................................... 2
3.2 Software........................................... 3
4. Installation............................................. 4
5. Cautions................................................. 7
5.1 Ada Support........................................ 7
5.2 CX/UX Ptrace BCS Conformance Option................ 7
5.3 NightView on CX/SX................................. 8
5.4 Breakpoint Command Streams......................... 8
5.5 Fortran 77 Arrays.................................. 8
5.6 Scroll Bars........................................ 8
5.7 Accessing Variables While in Prologue of Ada
Subprogram......................................... 9
5.8 Shared Objects..................................... 10
5.9 Next and Fork...................................... 10
5.10 Attach and server_block............................ 10
6. New Features in This Release............................. 11
6.1 Remote Debugging................................... 11
6.2 Repeated Debugging................................. 11
7. Changes from Previous Releases........................... 12
7.1 NightView Menu..................................... 12
7.2 Default Qualifier and Prompt....................... 12
7.3 Debugger Environment Variable...................... 12
7.4 apply on dialogue.................................. 12
7.5 Unimplemented Features............................. 12
7.6 select-context..................................... 13
8. Direct Software Support.................................. 13
- i -
_________________________________________________________________
HARRIS
COMPUTER SYSTEMS
_________________________________________________________________
CX/UX(TM) NIGHTVIEW(TM)
VERSION 4.4
RELEASE NOTES
0890395-4.4C
November 1997
_________________________________________________________________
return to index
================================================================================
WebTrackTM -
VERSION 1.2b
RELEASE NOTES
Harris Computer Systems Division
WebTrack is a specialized proxy server for controlling and
logging Internet access. It controls and logs access to HTTP
(WWW), FTP, NNTP (Usenet), WAIS, and GopherTM resources.
WebTrack works with the CyberGuardTM Firewall to allow only
outbound requests of these types through the WebTrack proxy.
It does this by requiring users to configure their Web
browsers to be proxy-aware and to connect to the WebTrack
proxy (webt) port (default 8000) through the internal
interface of the firewall. This directs the browser to first
connect to the WebTrack proxy and then lets the proxy
connect to the target machine specified by the user.
WebTrack is mainly used for logging and blocking access to
specified Internet resources. Log files can be displayed
with a browser as hypertext links to the Uniform Resource
Locators (URLs) that users tried to visit. Active blocking
can be applied to one or more of 16 categories, which can be
selected during or after installation. Refer to the
WebTrack Configuration and Operations Guide for UNIX for a
complete product description.
Contact your CyberGuard Corporation sales representative or
call the CyberGuard Corporation Customer Assistance Center
at one of the numbers in "Direct Software Support" for the
following information:
o WebTrack license-authorization key
o Monthly login and password for the WebTrack ftp site
o Additional copies of WebTrack documentation
Note: WebTrack is supported by CyberGuard Firewall versions
3.x on the SCO UnixWare 2.1 operating system and by
CyberGuard Firewall versions 2.1.2 and 2.2.x on Concurrent
Computer Corporation's CX/SXTM 6.2 operating system. This
__________
- These release notes cover the following products:
WebTrack
- 1 -
WebTrackTM 1.2b Release Notes
version of the release notes is for CyberGuard Firewall
2.2.x.
Note: WebTrack 1.2b is a rerelease of WebTrack 1.2 with
added support for 1997 temporary authorization codes. It
includes the last WebTrack control (wtcontrol) file for
February, 1997.
- 2 -
Release Notes 1.2b WebTrackTM
1. Documentation
The following documentation is included with this release:
_____________________________________________________________________
| Manual Name Pub. Number |
|_____________________________________________________|______________|
| WebTrack Configuration and Operations Guide for UNIX| 0840059-020 |
| WebTrack Release Notes | 0840058-1.2b|
|_____________________________________________________|______________|
2. Installation
Before beginning the installation procedure, the WebTrack
administrator should read the WebTrack Configuration and
Operations Guide for UNIX. The installation process
consists of four steps:
1. Installing WebTrack onto the firewall.
2. Answering all questions on the supplied WebTrack
Configuration Worksheet.
3. Configuring the WebTrack proxy.
4. Concluding the installation.
All four steps of the installation process must be followed.
2.1 WebTrack Installation
The following steps must be executed to install WebTrack.
1. Become the root user.
2. Bring the CyberGuard system into single-user mode by
first entering the following (system prompt given as
"#"):
# /etc/sync
# /etc/sync
# /etc/shutdown now
3. Enter your root password when prompted with "Enter root
password:".
4. Enter "S" if prompted with "Enter RUN LEVEL:".
(Otherwise continue with the next step.)
- 3 -
WebTrackTM 1.2b Release Notes
5. At the system prompt, mount all partitions:
# /sbin/mount -a
6. Insert the product tape into the system tape drive.
7. Change directory to root:
# cd /
8. Load the contents of the product tape:
# cpio -icBdumv < /dev/rmt/0m
9. Run the CyberGuard Corporation product installation
script called setup. Answer the questions prompted by
the script exactly as shown below. Note: stands
for the Enter key.
# ./setup
Enter the name of the running kernel or if /unix:
Tape 1 of the product tape(s) must be loaded on device /dev/rmt/0mn.
Is this the case? (y|n) y
Searching for an operational system tape device.
Using /dev/rmt/0mn (gt0).
Is this correct (y|n)? y
Enter the numbers of the actions you would like to perform:
1 All
2 Exit
3 Load WebTrack object files.
4 Update 'whatis' man page database.
5 Reprint menu (no other actions)
setup: 1
(Selecting 1 performs actions 3 through 5 automatically. Some messages may be displayed.)
Updating whatis man page database
(Upon completion of the product installation, the
actions menu will be redisplayed.)
Enter the numbers of the actions you would like to perform:
1 All
2 Exit
3 Load WebTrack object files.
4 Update 'whatis' man page database.
5 Reprint menu (no other actions)
setup: 2
- 4 -
Release Notes 1.2b WebTrackTM
(Selecting 2 will exit from the setup script and return
you to the '#' system prompt.)
10. Activate the software with a key. Customers who have
purchased WebTrack receive a permanent authorization
key. Others who are interested in purchasing or
evaluating the product may contact CyberGuard
Corporation's Customer Assistance Center at one of the
numbers listed in "Direct Software Support".
11. The WebTrack software product is now installed on your
system. Unload the product tape from the system drive
and proceed to the next section.
- 5 -
WebTrackTM 1.2b Release Notes
2.2 WebTrack Configuration Worksheet
Complete this worksheet before continuing the WebTrack
installation, and use it instead of any similar standalone
worksheet supplied by Webster Network Strategies, Inc. Refer
to the WebTrack Configuration and Operations Guide for UNIX
for assistance.
What is your WebTrack Authorization key? (Provided by your
sales representative)
__________________________________________________
What is the domain name of your WebTrack proxy? (Note: Use
the FULL domain name, for example, WebTrack.company.com)
__________________________________________________
How should your company or organization name appear in
online messages and hyperlinks? (Note: No embedded blanks
are allowed. Use the underscore character instead.)
__________________________________________________
Will you allow access to some site categories after business
hours? If so, then what are the starting and ending times
for business hour restrictions to apply? (Note: In 24-hour
time, specify the hour only, for example, 8 and 17.)
__________________________________________________
Do you want to configure WebTrack to allow access to sites
that you have explicitly exempted? (Note: This causes a
major change in WebTrack behavior and may result in
significant administrative burden; consider this carefully
before choosing this option. The recommended option is N.)
__________________________________________________
Will you allow users to request URLs by specifying dotted-
decimal addresses?
Answer Y to allow access to dotted-decimal addresses.
Answer N to prevent access to dotted-decimal addresses.
Answer R to allow access to dotted-decimal addresses after
attempting to resolve the address.
__________________________________________________
Will you allow users to access uncategorized personal pages?
- 6 -
Release Notes 1.2b WebTrackTM
(Note: uncategorized personal pages are those URL's
containing /~username.)
__________________________________________________
- 7 -
WebTrackTM 1.2b Release Notes
Will you allow users access to News Back Door Sites? (Note:
The N (no) option requires edit file processing.)
__________________________________________________
Will you use the WebTrack edit file processing?
__________________________________________________
Will you use the WebTrack custom file processing?
__________________________________________________
What is the domain name of the NNTP (news) server? (Note:
Omitting this will disable Usenet support entirely.)
__________________________________________________
If you have enabled Usenet support, will you allow access
only to exempted news groups?
__________________________________________________
What is the mail ID of the administrator? (Example:
WebTrackadmin@company.com)
__________________________________________________
If you use the SOCKS server, what is its domain name?
__________________________________________________
Will you use disk caching, and if so, how much? (Range: 5-
60Mb)
__________________________________________________
Do you want to add an uncontrolled client?
__________________________________________________
Which of the following categories are to be restricted
during business hours (or all the time if no business hours
are specified)?
Alternative Journals, Criminal Skills, Drugs, Entertainment,
Extreme, Gambling, Games, Hate Speech, Humor, Jobs,
Lifestyle, Online Sales/Merchandising, Personal, Sex,
Sports, Worthless
- 8 -
Release Notes 1.2b WebTrackTM
__________________________________________________
- 9 -
WebTrackTM 1.2b Release Notes
Which of the following categories are to be restricted after
business hours? (No hourly restrictions exist if business
hours are omitted.)
Alternative Journals, Criminal Skills, Drugs, Entertainment,
Extreme, Gambling, Games, Hate Speech, Humor, Jobs,
Lifestyle, Online Sales/Merchandising, Personal, Sex,
Sports, Worthless
__________________________________________________
What is the Administrator ID for WebTrack Control List
updates and Log Access? (Note: The WebTrack Administrator ID
is unique to WebTrack. It is distinct from any UNIX
operating system IDs.)
__________________________________________________
What is the Administrator ID's password? (Note: As with the
Administrator ID above, the password is unique to WebTrack;
the two together control online access to administrative
functions.)
__________________________________________________
2.3 WebTrack Configuration
The following steps should be performed to configure
WebTrack on your system.
1. Become the root user.
2. Change directory as follows:
cd /var/third-party/WebTrack
3. Enter the following:
./WT-Install
4. Answer the configuration questions as prompted. (Refer
to the WebTrack Configuration and Operations Guide for
UNIX for assistance.)
5. (Optional) Correct any mistakes by editing the
/var/third-party/WebTrack/control/webtrack.conf file.
- 10 -
Release Notes 1.2b WebTrackTM
2.4 Post Installation
The following steps should be executed to complete the
installation when WebTrack is used in conjunction with
CyberGuard Firewall Release 2.2.x.
1. Become the root user.
2. Verify that the following lines exist in the
/etc/services file:
webt 8000/tcp
webt 8000/udp
3. For CyberGuard Firewall 2.1.2 ONLY, use an editor such
as /usr/bin/vi to edit the /etc/rc file by uncommenting
the following lines:
- 11 -
WebTrackTM 1.2b Release Notes
## Webster Network Strategies Inc. WebTrack proxy
if [ -x /var/third-party/WebTrack/sbin/httpp ]; then
/mls/bin/NETWORKexec /var/third-party/WebTrack/sbin/httpp \
-r /var/third-party/WebTrack/control/webtrack.conf \
> /dev/null 2>&1
echo ' WebTrack\c'
fi
4. For CyberGuard Firewall 2.2.x, to enable WebTrack, the
value assigned to the USE_WEBTRACK_PROXY variable,
located at the beginning of the /etc/rc script file
should be yes. If it does not have this value, then
use an editor such as /usr/bin/vi to change the
variable to this character string. The /etc/rc file
statements that are executed are as follows:
if [ "$USE_WEBTRACK_PROXY" = "yes" \
-a -x /var/third-party/WebTrack/sbin/httpp ]; then
/mls/bin/NETWORKexec /var/third-party/WebTrack/sbin/httpp \
-r /var/third-party/WebTrack/control/webtrack.conf \
> /dev/null 2>&1
echo ' WebTrack\c'
fi
5. Define packet-filtering rules in the
/mls/net/netguard.conf file similar to the following
example. These rules allow all internal hosts to
connect to the firewall using the WebTrack proxy and
then the firewall to connect to the outside using the
specified service. Force users through the WebTrack
proxy by denying access to the regular services from
internal systems.
# permit internal users to use WebTrack and then
# permit WebTrack to use regular services
permit webt/tcp ALL_INTERNAL LOCAL_HOST
permit webt/udp ALL_INTERNAL LOCAL_HOSTENABLE_REPLY
permit http/tcp LOCAL_HOST ALL_EXTERNAL
permit http/udp LOCAL_HOST ALL_EXTERNALENABLE_REPLY
permit ftp/tcp LOCAL_HOST ALL_EXTERNAL
permit nntp/tcp LOCAL_HOST ALL_EXTERNAL
permit gopher/tcp LOCAL_HOST ALL_EXTERNAL
permit gopher/udp LOCAL_HOST ALL_EXTERNALENABLE_REPLY
# Deny use of service without WebTrack
deny http/tcp ALL_INTERNAL LOCAL_HOST
deny http/tcp ALL_INTERNAL ALL_EXTERNAL
deny http/udp ALL_INTERNAL LOCAL_HOST
deny http/udp ALL_INTERNAL ALL_EXTERNAL
deny ftp/tcp ALL_INTERNAL LOCAL_HOST
- 12 -
Release Notes 1.2b WebTrackTM
deny ftp/tcp ALL_INTERNAL ALL_EXTERNAL
deny nntp/tcp ALL_INTERNAL LOCAL_HOST
deny nntp/tcp ALL_INTERNAL ALL_EXTERNAL
deny gopher/tcp ALL_INTERNAL LOCAL_HOST
deny gopher/tcp ALL_INTERNAL ALL_EXTERNAL
deny gopher/udp ALL_INTERNAL LOCAL_HOST
deny gopher/udp ALL_INTERNAL ALL_EXTERNAL
6. Flush all file modifications to disk:
# /etc/sync
7. Flush all file modifications to disk again:
# /etc/sync
8. Reboot your CyberGuard Firewall to multi-user mode:
# /etc/reboot
WebTrack will now run as a daemon and listen on the
interface specified during configuration at port 8000.
3. Starting WebTrack
The two methods for starting WebTrack for CyberGuard
Firewall Release 2.2.x are as follows.
3.1 Manual Startup
This section is pertinent if:
o This is the first startup of WebTrack after its
installation and configuration
or
o You want to manually start the WebTrack proxy now
Become the root user, and execute the following script:
/var/third-party/WebTrack/sbin/startproxy
3.2 Automatic Startup
This section is pertinent if you want to automatically start
the WebTrack proxy at the next system reboot.
Assign the value "yes" to the USE_WEBTRACK_PROXY variable in
the script file called /etc/rc.
WEBT_PROXY=true
- 13 -
WebTrackTM 1.2b Release Notes
4. WebTrack Control File (wtcontrol)
The Webster-supplied control file, wtcontrol, contains the
list of URLs for thousands of sites that have been
associated with one or more of the categories to which you
can prohibit access. This file is compiled for your
particular operating system and is not user-readable. The
CyberGuard Firewall is shipped with a copy of this file so
that you can immediately set up and use WebTrack. WebTrack
reads the file into memory.
The wtcontrol file is updated weekly. Issue the following
commands to save the wtcontrol file and obtain the latest
version from the Webster Networking Solutions, Inc. ftp
site:
- 14 -
Release Notes 1.2b WebTrackTM
cd /var/third-party/WebTrack/control
mv wtcontrol wtcontrol.old
ftp webtrack.webster.com
login
password
cd pub/ver1.2/CYBERGUARD
binary
get wtcontrol
bye
To use the new wtcontrol file, do one of the following:
o Run /var/third-party/WebTrack/sbin/reloadcontrol
o Wait until midnight (when WebTrack automatically reads
the file)
For one year, WebTrack purchasers can obtain new versions of
the file at no charge.
5. Instructions to Enable User Authentication
The following instructions show how to enable user
authentication in WebTrack. It works only with Netscape
Navigator. Each user must be added using a script or a
browser. (There is no interface to existing authentication.)
This is done after WebTrack is installed.
To add user authentication to WebTrack Version 1.2b:
1. Become the root user.
2. Issue the following commands:
cd /var/third-party/WebTrack
chgrp bin wtadduser
chmod 544 wtadduser
3. Add at least one user with the wtadduser script.
(If your browser needs a proxy when you restart
WebTrack after enabling authentication, you will need
an ID to use the browser. Use the one you added in
wtadduser.)
4. Edit the control/webtrack.conf file:
- 15 -
WebTrackTM 1.2b Release Notes
a. Find the lines that look like:
Protection PROTECT {
Userid SOMETHING
Groupid SOMETHING
AuthType Basic
ServerId WebTrack
PasswordFile /var/third-party/WebTrack/admin/passwd
GetMask ALL
}
- 16 -
Release Notes 1.2b WebTrackTM
b. Add the PostMask line so it looks like:
Protection PROTECT {
Userid SOMETHING
Groupid SOMETHING
AuthType Basic
ServerId WebTrack
PasswordFile /var/third-party/WebTrack/admin/passwd
GetMask ALL
PostMask ALL
}
c. Near the top of the file add these lines:
# User Authentication enabled
webtrackuserauthenticate enable
d. Save the file
5. If you have not yet started WebTrack, execute the
following command:
sbin/startproxy
6. If you have already started WebTrack, execute the
following command:
sbin/restartproxy
7. Additional users may be added using the
http://WebTrack's_full_domain_name:8000/admin/adduser.htm
admin screen from a browser.
6. Direct Software Support
Software support is available from a central source. When
you need assistance or information about your system, please
contact the Harris Software Support Center at our toll free
number (800-245-6453). Our customers outside the
continental United States can contact us directly at 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.
- 17 -
WebTrackTM 1.2b 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.
- 18 -
CONTENTS
1. Documentation............................................ 3
2. Installation............................................. 3
2.1 WebTrack Installation............................... 3
2.2 WebTrack Configuration Worksheet.................... 6
2.3 WebTrack Configuration.............................. 10
2.4 Post Installation................................... 11
3. Starting WebTrack........................................ 13
3.1 Manual Startup...................................... 13
3.2 Automatic Startup................................... 13
4. WebTrack Control File (wtcontrol)........................ 14
5. Instructions to Enable User Authentication............... 15
6. Direct Software Support.................................. 17
- i -
_________________________________________________________________
HARRIS
COMPUTER SYSTEMS
_________________________________________________________________
WebTrackTM
VERSION 1.2b
RELEASE NOTES
0840058-1.2b
February 1997
_________________________________________________________________
Copyright and Trademark Attribution
All trademarks not explicitly listed below are the property of their respective owners.
CyberGuard is a trademark of CyberGuard Corporation.
Gopher is a trademark of the University of Minnesota.
Netscape Navigator is a trademark of Netscape Communications Corporation.
UNIX is a registered trademark in the USA and other countries, licensed exclusively through
X/Open Company Limited.
WebTrack is a trademark of Webster Network Strategies, Inc.
return to index
================================================================================
CX/SX BLACKER INTERFACE -
VERSION 1.1
RELEASE NOTES
Harris Computer Systems Division
1. Introduction
The BLACKER interface software package provides access to a
Blacker Front End (BFE). The Blacker interface uses the
CX/UX VCOM X.25 software package and the VCOM X.25
controller to provide the physical interface to the BFE.
This release contains the software utilities that allow a
CX/SX system to communicate with another BLACKER compliant
system across a BLACKER network. The package provides an
interface which allows TCP/IP utility programs to operate
over the BLACKER link.
This product provides BLACKER addressing and complete
"Emergency Mode" functionality. This release conforms to
the "BLACKER Interface Control Document (ICD)".
2. Documentation
The following documentation is included with this release:
_____________________________________________________
| Manual Name Pub. Number|
|______________________________________|_____________|
| CX/UX Networking Reference Manual | 0890118-050|
| CX/UX VCOM X.25 User's Guide | 0890417-000|
| CX/SX BLACKER Interface Release Notes| 0890420-1.1|
|______________________________________|_____________|
__________
- These release notes cover the following products:
BLACKER
- 1 -
CX/SX BLACKER Interface 1.1 Release Notes
|______________________________________|_____________|
Additional copies may be ordered by contacting the Harris
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-305-971-6248.
3. Prerequisites
Prerequisites for CX/SX BLACKER Interface Version 1.1 are as
follows:
3.1 Hardware
o Any Series 4000 or Series 5000 system.
o VCOM-24/34 X.25 controller.
3.2 Software
o CX/UX 6.2 Patch level 51 or higher.
o CX/SX LAN SX
o CX/UX STREAMS.
o CX/UX TCP/IP.
o CX/UX VCOM X.25.
4. Installation
Please refer to the CX/UX System Administration Manual,
Chapter 3, for instructions on software installation.
- 2 -
Release Notes 1.1 CX/SX BLACKER Interface
5. Cautions
BLACKER is supported only over the VCOM X.25 controllers.
If it is necessary to disable the BLACKER product once
installed the BLACKER en try in the config file must be
commented out and the following line in the /usr/
src/uts/machine/cf/files file modified.
OLD: vipx/blacker_stub.c lib_black optional vcomddn blacker
NEW: vipx/blacker_stub.c lib_black optional blacker
The BLACKER interface is supported only on VCOM boards 0 and
1 (vc0 and vc1).
6. New Features in this Release
This is the initial release of the BLACKER Interface
package.
7. Changes from Previous Releases
This is the initial release of the BLACKER Interface
package.
8. Direct Software Support
Software support is available from a central source. When
you need assistance or information about your system, please
contact the Harris Software Support Center at our toll free
number (800-245-6453). Our customers outside the
continental United States can contact us directly at 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 -
CX/SX BLACKER Interface 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 Hardware............................................. 2
3.2 Software............................................. 2
4. Installation.............................................. 2
5. Cautions.................................................. 3
6. New Features in this Release.............................. 3
7. Changes from Previous Releases............................ 3
8. Direct Software Support................................... 3
- i -
_________________________________________________________________
HARRIS
COMPUTER SYSTEMS
_________________________________________________________________
CX/SX BLACKER INTERFACE
VERSION 1.1
RELEASE NOTES
0890420-1.1
December 1993
_________________________________________________________________
return to index
================================================================================
CONDOR ETHERNET DRIVER -
VERSION 6.2
RELEASE NOTES
Harris Computer Systems Division
1. Introduction
The Condor EthernetO* driver provides support for multiple
ports of the Interphase Condor 4221 Ethernet controller.
2. Documentation
The following documentation is included with this release:
____________________________________________________
| Manual Name Pub. Number|
|_____________________________________|_____________|
| Condor Ethernet Driver Release Notes| 0890477-6.2|
|_____________________________________|_____________|
Additional copies may be ordered by contacting the Harris
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-305-971-6248.
__________
- These release notes cover the following products: cnd
* Ethernet is a registered trademark of Xerox Corporation.
- 1 -
Condor Ethernet Driver 6.2 Release Notes
3. Prerequisites
Prerequisites for the Condor Ethernet Driver Version 6.2 are
as follows:
3.1 Hardware
o Any Series 4000 or 5000 system.
o One or more Interphase Condor Ethernet VME controller
boards.
3.2 Software
o CX/UX 6.2 or later releases
o TCP/IP 6.2 or later releases
o Ethernet 6.2 or ISE 7.1
4. Installation
Please refer to the CX/UX System Administration Manual,
Chapter 3, for instructions on software installation.
5. Direct Software Support
Software support is available from a central source. When
you need assistance or information about your system, please
contact the Harris Software Support Center at our toll free
number (800-245-6453). Our customers outside the
continental United States can contact us directly at 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.
- 2 -
Release Notes 6.2 Condor Ethernet Driver
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.
- 3 -
CONTENTS
1. Introduction.............................................. 1
2. Documentation............................................. 1
3. Prerequisites............................................. 2
3.1 Hardware............................................. 2
3.2 Software............................................. 2
4. Installation.............................................. 2
5. Direct Software Support................................... 2
- i -
_________________________________________________________________
HARRIS
COMPUTER SYSTEMS
_________________________________________________________________
CONDOR ETHERNET DRIVER
VERSION 6.2
RELEASE NOTES
0890477-6.2
June 1995
_________________________________________________________________
return to index
================================================================================
ELAN LICENSE MANAGER(TM) -
VERSION 2.3.3
RELEASE NOTES
Harris Computer Systems Division
1. Introduction
Elan License Manager1 is a software package that controls
single or multi-user access to software applications in a
single user or networked multi-user environment. The
principal functions of Elan License Manager include:
o User Based Licensing - To allow per-user floating
licensing which controls the number of concurrent users
for an application. Licenses are not provided to
machines, but to users.
o Component Licensing - The ability to license features
or components of an application individually.
o Timed Software - The ability to establish an expiration
date on software for creating evaluation or trial
copies.
o Copy Protection - A form of copy protection ensures
that licensed software applications will only operate
on an authorized CPU or network. Unlike MS-DOS copy
protection, this copy protection scheme still permits
backup copies, changing disks, reinstallation, etc.
__________
- These release notes cover the following products:
elanlm
1. Elan License Manager is a trademark of Elan Computer
Group, Inc. Much of the text of this paper comes from
the Elan License Manager Technical Overview and the Elan
License Manager Programmer's Guide by the Elan Computer
Group, Inc. and is used with their permission.
- 1 -
Elan License Manager(TM) 2.3.3 Release Notes
Certain Harris applications are now released as licensed
products using Elan License Manager. The elanlm product is
required to manage the licenses required by those products.
Elan License Manager is based on the client/server model
with a license manager, running on one or more servers, and
the application running on one or more clients. The server
and client may be the same machine or they may be different
machines.
The license manager maintains a central database of licenses
and activity. The license manager verifies valid clients,
grants licenses to valid client applications, and collects
the licenses when the application terminates. The license
manager runs as a daemon invoked at system start-up.
The application may run on the server or on one or more
clients on a network. Applications communicate with the
license manager via sockets using datagram connections to
request and return licenses.
Licenses are available to anyone on the network or CPU - the
applications need not be tied to any particular nodes
(although they can be). This scheme of flexible licensing
has been coined dynamic licensing or floating licensing. It
is far more convenient than the older ``one copy on one
CPU'' license scheme, and it increases the availability of
the application within the site at no increase in cost.
Elan License Manager licenses objects called features.
Features can be considered components or major functions of
an application. Applications can have one feature (i.e. the
ability to invoke the application) or many. Each feature
may have its own license count and expiration date.
Obtaining and administering licenses for application
features is described later in this document.
2. Documentation
The following documentation is included with this release:
____________________________________________________
| Manual Name Pub. Number |
|___________________________________|_______________|
|___________________________________|_______________|
- 2 -
Release Notes 2.3.3 Elan License Manager(TM)
| Elan License Manager Release Notes| 0891055-2.3.3|
|___________________________________|_______________|
Additional copies may be ordered by contacting the Harris
Software Support Center. The toll-free number for calls
outside of Florida is 1-800-245-6453. For calls within
Florida or outside the continental United States the number
is 1-305-971-6248.
3. Prerequisites
Prerequisites for Elan License Manager(TM) Version 2.3.3 are
as follows:
3.1 Hardware
o Any Series 4000 or Series 5000 Night Hawk system.
3.2 Software
o CX/UX operating system release 6.1 or later.
4. Installation
Please refer to the CX/UX System Administration Manual,
Chapter 3, for instructions on software installation.
After loading the elanlm product, run the installation
script
./usr/lib/harris_licenses/bin/install
relative to the directory in which the product was
installed. The installation script will see that the
following directories exist:
/usr/lib/harris_licenses key directory
/usr/lib/harris_licenses/bin administrative
commands directory
- 3 -
Elan License Manager(TM) 2.3.3 Release Notes
/usr/catman/elanlm_man pre-processed manual
pages
/usr/man/elanlm_man manual page source
files
If the product was installed in an alternate directory, the
directories listed above will be created as symbolic links
to the corresponding directories in the alternate directory.
User commands in ./usr/bin will not be moved to /usr/bin by
the installation script.
After installation, the command
/usr/lib/harris_licenses/bin/elmd -e /usr/lib/harris_licenses \
-l /var/tmp/harris_elm.log
will initiate the license manager. You may also want to use
the -m option to automatically trim the log file, the -s
option to control the delay period when waiting for client
reconnections in a network environment, and the -r option to
specify a resource file. See elmd(1) and elm_resource(5).
5. Cautions
Depending on your operating system release level, your
/etc/rc script may have instructions to initiate the license
manager at boot time if the program
/usr/lib/harris_licenses/bin/elmd exists.
If you do not wish to run the license manager on any system
on which you have installed this product, you may need to
modify the /etc/rc script.
If your /etc/rc script does not include instructions to
start the license manager, you should add those instructions
either to /etc/rc or to /etc/rc.local. Add the command
/usr/lib/harris_licenses/bin/elmd -e /usr/lib/harris_licenses \
-l /var/tmp/harris_elm.log
All Harris applications use numeric license keys. This
means that license keys (provided by Harris) and server
codes (generated by the elmadmin program) all look similar
to credit card numbers, for example:
- 4 -
Release Notes 2.3.3 Elan License Manager(TM)
0145 3482 6579 1462
If you use elmadmin to generate a server code and it does
not look vaguely like a credit card number, then you
probably did not use the -n option flag. Re-run the command
with the -n option.
6. New Features in this Release
This section describes the administration of feature
licenses using Elan License Manager.
6.1 Obtaining Licenses
Licenses are granted by obtaining a key from Harris that is
generated specifically for your CPU or network and encodes
the number of licenses and their expiration date. You must
obtain the appropriate keys before you can run licensed
products. Each Harris product that requires a license will
describe in its documentation what components of the product
are licensed.
The steps for obtaining and installing licenses are:
1. Read the release notes for the product for which you
wish to obtain licenses and find the feature alias
(usually a derivative of the name of the product).
2. Determine the number of license managers you wish to
run at your site and the machines on which they will
run (see below).
3. On one of the machines on which you will run a license
manager, run the program elmadmin:
$ elmadmin -c -n -e /usr/lib/harris_licenses name
where name is the feature alias provided in the
documentation for the product for which you are
obtaining a license. You will be asked for the number
of managers (servers) you wish to run and, if more than
one, the host names for each. When you have answered
all questions, elmadmin will display a server code for
each server on which you will run a license manager.
The program will then prompt you for a key which you
must now obtain from Harris.2
- 5 -
Elan License Manager(TM) 2.3.3 Release Notes
4. Contact Harris Software Distribution at 1-800-666-5405
to obtain your key. You will need to provide the
feature alias and each server code generated by
elmadmin.
5. Enter your key for elmadmin. The licenses are now
initialized and you should be able to run the protected
application.
Here is a sample dialogue with elmadmin.
$ elmadmin -c -n -e /usr/lib/harris_licenses NightView
On how many hosts will you run the license server? (default=1):
Code for server elan is: 0245 8672 9914 7243
Please enter your key: 0589 7713 2354 6209
The system administrator may need to interact with the
license manager using the feature name, which is a five-
digit number with which the feature alias is associated.
The feature name will be provided in the application's
documentation. When placing entries in the resource file
(see below), be sure to use the feature name and not the
feature alias.
6.2 License Allocation
Elan License Manager implements two principal schemes of
licensing: floating and non-floating licenses. As a
refinement, the features of reserving and holding licenses
are also available. These concepts will be discussed in the
following sections. See elm_resource(5) for additional
information.
__________
2. If you cannot contact Harris immediately, it is safe to
interrupt the elmadmin program at any point. Rerunning
it later after contacting Harris and entering the same
responses will generate the same server codes.
- 6 -
Release Notes 2.3.3 Elan License Manager(TM)
6.2.1 Floating_Licenses
Licenses are generally available to anyone on a network who
can reach the server running the license manager daemon. As
such, these licenses are known as floating licenses - the
licenses float on the network and anyone on the network can
use them. When 100 licenses, for example, are encoded in
the license key for a product, then any 100 users on the
network can use the product concurrently.
When the concurrent usage reaches the licensed number, 100
in this example, a subsequent request to use the product
will be denied because all licenses are currently in use.
6.2.2 Node-Locked_Licenses
It is occasionally desired that licenses not float on a
network. In these cases, the site can request that their
licenses be node-locked on a per-CPU basis. The licenses
will only be available on the CPU that the license manager
daemon is running on.
Node-locked licenses must be specified when contacting
Harris for the license key.
If at a later time floating licenses are desired, the non-
floating key can be converted to a floating license key
simply by requesting a new key from Harris.
6.2.3 Reserved_Licenses
Whether licenses float on a network or not, sometimes you
would like to reserve licenses for particular people,
groups, or even machines.
For example, let's say a company of 400 employees purchases
100 floating licenses for a product. However, the company
would like their simulation department of 20 to always have
access to the application. In the resource file, these 20
people can be named and 20 licenses reserved for them.
Similarly, a company may buy many floating licenses for a
diagnostic package, but they would like the lab machines to
always have access to the package. The resource file may
list these machines, and reserve some licenses for these
particular machines. The remainder of the licenses will
float.
- 7 -
Elan License Manager(TM) 2.3.3 Release Notes
The resource file looks very much like the /etc/group file.
Here's an example portion of a resource file:
11000:development:jim,tom,bill,cindy,brad:10:0
11000:simulation:barbara,vince,todd:2:0
11000:proj-lead:eddy:1:0
11000:demo-room:@showoff.mycorp.com:1:0
In the example above, 10 licenses for NightView (the feature
name for NightView is ``11000'') have been reserved for the
development department, 2 licenses for a group of 3 in the
simulation department, 1 license for the boss, eddy, and 1
license has been reserved for the demonstration room machine
named showoff.mycorp.com. The remaining licenses, if any,
will float as usual.
Notice that one may reserve fewer licenses than there are
group members. We have done this in our example above with
the simulation group. In such a case, any member of this
group will acquire a license from the reserved pool first,
thus affording a high probability to this group of obtaining
a license. If the reserved pool is already fully allocated,
however, licenses are taken from the remaining non-reserved
pool.
The resource file may be used for floating or non-floating
licenses alike. The distinction is simply that the non-
floating licenses stay with a particular machine. Licenses
may still be reserved for individuals. It makes little
sense, of course, to reserve to a machine name in the
resource file if the licenses are already non-floating.
Please refer to elm_resource(5) and elmd(1) for more details
on the resource file.
6.2.4 Excluded_Users
Users and/or hosts may be excluded from using specified
features by listing them in the resource file with the word
EXCLUDE in the license count field. For example:
11000:mother-in-law:harriet,@wanda:EXCLUDE:0
would disallow harriet or anyone logged onto machine wanda
from checking out licenses for NightView. EXCLUDE-ed users
must be listed before any reserved licenses.
- 8 -
Release Notes 2.3.3 Elan License Manager(TM)
6.2.5 Domain_Licensing
It may be desirable to limit clients that may check out
licenses by network domain. For example, a system
administrator may wish to limit certain licenses only to the
network domain servicing the department that purchased the
license.
For example, if a company owned a Class-A network but was
also on the InterNet, the administrator might wish to limit
license server requests from only those on the Class-A
network.
License requests may be limited to a domain of clients via
the resource file. The token %IPACCEPT followed by a mask,
specified in the resource file, limits client accesses to
mask.
The mask appears in the resource file as a line of the form:
%IPACCEPT mask
where mask is a 4-tuple of expressions ``e'' separated by
periods: ``e.e.e.e''. Each e may be any one of the
following, or a comma separated list of any of the
following:
N A decimal integer between 0 and 255.
N-M An integer range. N and M should be decimal
integers between 0 and 255, and N should be less
than M.
* An asterisk matches all integers.
THIS The word ``THIS'' (or ``this'') means the server's
IP octet value in the designated position. For
example, if the server address were 192.100.42.16,
then ``THIS.*.*.*'' would be the same as
``192.*.*.*'' and ``THIS.THIS.THIS.*'' would be
the same as ``192.100.42.*''.
For example, a mask of:
THIS.*.*.*
would limit requests from only those on the same Class-A
network as the license server. Also,
- 9 -
Elan License Manager(TM) 2.3.3 Release Notes
THIS.100,200-224,226.*.*
would limit requests from only those on the same Class-A
network and from Class-B subnetworks 100, 200 through 224,
and 226.
6.2.6 Held_Licenses
Held licenses are those licenses that are held or retained
as checked out by the license server after an application
exits. These licenses are each marked with the original
owner's user and host name, and are held for a specific
duration, the hold period, for this person's reuse. If
prior to the expiration of the hold period, the same person
(the same user@host) requests a license that is held, the
held license will be transferred to him. When the hold
period passes, however, such licenses are freed to the free
license pool for anyone's use.
Held licenses are useful for several quite different
purposes.
1. A minimum license usage period may be established for
short-lived applications. For example, a compiler
often runs for a brief period. As such, a standard
floating license per se may not be an effective form of
licensing since, by probabilities, it will usually be
checked in and, therefore, usually be granted to anyone
who asks for it. However, if the application has a
minimum usage period of, say, 10 minutes, a more
equitable per-license usage will be realized. The held
license feature may be used to implement such a scheme.
2. When a series of applications are used together,
perhaps in a series from a shell script, holding a
common feature license for as little as a minute will
guarantee that each application in series will still be
able to obtain a license and the user will not be
stalled in the midst of a job.
3. A user or, more often, system administrator, may wish
to allow users to exit and shortly thereafter re-enter
an application and not have their license lost to
another. In this case, a license may be held for, say,
5 minutes after the application exits, allowing a user
to re-enter without there being a chance of the license
not being available.
- 10 -
Release Notes 2.3.3 Elan License Manager(TM)
A minimum hold period may be defined by the application. A
hold period greater than the minimum hold period (if one)
may be designated by the user or system administrator via
the resource file.
The final entry in each resource file line is the hold
period for this group in seconds. For example,
11000:proj-lead:eddy:1:900
11000:demo-room:@showoff.mycorp.com:0:600
11000:others::0:60
In this example, when eddy uses NightView, the license will
be held for him for 15 minutes (900 seconds) after exiting
the application.
In the second example, if anyone uses NightView on the
machine showoff.mycorp.com, their license will be held for
10 minutes.
In the third example, everyone else (indicated by an empty
member list) will have their license for NightView held for
1 minute after exiting the application.
If the value in the held field is less than the minimum hold
period defined by the application, the minimum is used.
6.3 Redundant License Servers
Many customers will install applications on a single system,
usually a file server, and run a single license server on
the same system. Of course, if this file server goes down
they will no longer have access to the application - or any
other files on the server, for that matter.
In some cases, however, it is desirable to maintain one or
more backup systems, such that if the main file server
crashes work can be continued on a backup file system. The
application and all support files must be installed on the
backup file server, and the license manager must also be
installed on these systems to afford license control from
these backup servers.
Elan license manager supports redundant license servers with
a technique similar to other fault-tolerant systems such as
the space shuttle. The license server, elmd, may be run on
multiple servers with a special key called a redundant
license key. The redundant key is distinct from a standard
- 11 -
Elan License Manager(TM) 2.3.3 Release Notes
key in that it encodes the system IDs for all systems that
are authorized to run the license server. This key is
shared among all redundant servers. A redundant key is
generated by supplying server codes for each of the systems
on which the license manager is to run.
The set of systems on which the license manager runs can be
changed at any time by requesting a new key from Harris with
server codes for the new machines (or possibly the one
single machine) on which the license manager is to be run.
When the redundant model is used, all license servers on a
network will communicate with each other and maintain status
information on each other. When a cluster of elmds are
started on a network, one automatically receives the status
of master, and the remaining elmds receive the status of
shadow. Client communication is automatically routed to the
current master for license acquisition and authentication.
For security, the license manager requires that a majority
of license servers remain running. The reason for this
requirement is that if a network were broken in two, then
each section would have to decide who can continue to issue
licenses. If both continued, each would be authorizing
licenses - twice as many licenses as are valid. However,
since only one side can mathematically have a majority of
the original number of servers, the remaining majority only
wins and takes over license distribution. The minority side
(or sides) will become inactive.
In order for a majority side to exist, the original number
of servers must be an odd number.
When using elmadmin to generate server codes and install a
license key, a key file will be created on the machine on
which elmadmin is run. The key file must be made accessible
to the other servers by one of the following methods:
1. placing the key file in a file system shared by all
machines, or
2. by copying it to a location on each machine.
For convenience it is preferable to place the key in the
same directory path on each system. If this is not
practical, use the -e option of elmd on each system to
specify the key location.
- 12 -
Release Notes 2.3.3 Elan License Manager(TM)
The host name of each of the redundant servers should be
mentioned in the resource file. This may be done by placing
lines of the form:
%SERVER hostname
into the resource file, where hostname is the name of one of
the hosts. There should be one line for each of the
redundant servers.
6.4 Running License Managed Applications
When running an application whose usage is managed by the
Elan license manager, be prepared for the application to
exit immediately upon invocation if there are not enough
licenses or if the license manager is down (or if the
application cannot connect to the master server). The
documentation for each application will indicate what
happens when a license is unavailable when you try to run
it, or if the license is lost during execution of the
application.
Usually an application must send a broadcast request on the
network to locate the master license server. If you know
the hostname on which the license server is running, you may
set the environment variable ``HARRIS_ELMHOST'' to the
hostname and avoid the network broadcast.
By default, the Harris implementation of the Elan license
manager uses socket port 6461. If this port number
conflicts with an application at your site, you may change
it by modifying the /etc/services file by adding a line of
the form:
harris_elmd 1234/udp harris-license-server
where the ``1234'' here is an otherwise unused port number
of your own choosing.
6.4.1 Error_Messages
The following messages can be produced during failed
attempts to start an application that must connect to the
license manager.
License server initializing; please wait
or...
- 13 -
Elan License Manager(TM) 2.3.3 Release Notes
License server coming up in n seconds; please wait
or...
License server coming up in n minutes; please wait
The license server has just started and the application
must wait for the server to complete its
initialization, which includes waiting for a
synchronization period specified with the -s option to
elmd.
License server is down
No operational license server could be found running on
the network. Check the value of the HARRIS_ELMHOST
environment variable if set.
Insufficient servers running
The client is running with redundant servers but there
are not enough servers active. For license validation
purposes, a majority of servers must remain active in
the redundant mode.
License server host unknown
The hostname is not valid. Check that the
HARRIS_ELMHOST environment variable, if set, is set to
the name of the proper host for the license manager
daemon and that that hostname appears in the /etc/hosts
file.
No licenses are currently available
There are no licenses available for the designated
feature.
License authorization failure
Authorization failure. Client or daemon fraud or an
attempt to acquire a non-floating license from another
host.
License has expired
The feature license has expired or there was a date
validation error.
Communications socket failure
A socket(2) connection failed, probable network
failure.
Network error: unable to send message to license server
A sendto(2) system call failed when trying to send a
message to the license daemon, probable network
failure.
- 14 -
Release Notes 2.3.3 Elan License Manager(TM)
License lost
A reconnect after a server crash failed to reestablish
all the client's prior licenses. That is, one or more
licenses was denied for some reason during a reconnect.
No license file found for feature
or...
No such feature
There is no license key file installed for the
specified feature.
6.5 Administrative Commands
The Elan license manager product includes these
administrative commands:
elmd The license server which controls all
licensing checkouts and reclaims. This
daemon program runs on the server and issues
and collects license requests. It is usually
initiated from the /etc/rc script.
elmadmin Creates license keys, performs daemon control
functions, and lists current license
activity.
elmalert Provides an end-user or system administrator
information regarding when licenses are near
expiration or when a license for a particular
feature becomes available. Notification may
be done via screen message or by email.
elmrpt Provides a summary report on daily license
activity, indicating the number of license
requests, the number issued, and the number
denied. It optionally gives a day to day
breakdown or total breakdown. When using
this command, it is necessary to specify the
log file name as a command line parameter,
usually ``/var/tmp/harris_elm.log''.
elmusage Produces a snapshot report of current license
activity, updating every 10 seconds.
elmdecode A diagnostic tool which may be used to
extract some information from licenser server
codes and license keys.
- 15 -
Elan License Manager(TM) 2.3.3 Release Notes
elmd and elmdecode are usually installed in the
/usr/lib/harris_licenses/bin directory. Other commands are
installed in the ./usr/bin directory relative to where the
product is loaded.
In addition to manual pages for these administrative
commands, the elm_resource(5) describes the format of the
resource file.
7. Changes from Previous Releases
None.
8. Direct Software Support
Software support is available from a central source. When
you need assistance or information about your system, please
contact the Harris Software Support Center at our toll free
number (800-245-6453). Our customers outside the
continental United States can contact us directly at 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.
- 16 -
CONTENTS
1. Introduction............................................. 1
2. Documentation............................................ 2
3. Prerequisites............................................ 3
3.1 Hardware............................................ 3
3.2 Software............................................ 3
4. Installation............................................. 3
5. Cautions................................................. 4
6. New Features in this Release............................. 5
6.1 Obtaining Licenses.................................. 5
6.2 License Allocation.................................. 6
6.2.1 Floating Licenses............................ 7
6.2.2 Node-Locked Licenses......................... 7
6.2.3 Reserved Licenses............................ 7
6.2.4 Excluded Users............................... 8
6.2.5 Domain Licensing............................. 9
6.2.6 Held Licenses................................ 10
6.3 Redundant License Servers........................... 11
6.4 Running License Managed Applications................ 13
6.4.1 Error Messages............................... 13
6.5 Administrative Commands............................. 15
7. Changes from Previous Releases........................... 16
8. Direct Software Support.................................. 16
- i -
_________________________________________________________________
HARRIS
COMPUTER SYSTEMS
_________________________________________________________________
ELAN LICENSE MANAGER(TM)
VERSION 2.3.3
RELEASE NOTES
0891055-2.3.3
FEBRUARY 1994
_________________________________________________________________
return to index
================================================================================
FETCH -
VERSION 1.0
RELEASE NOTES
Harris Computer Systems Division
1. Introduction
This release contains utilities which allow CX/UX systems to
read tapes that are from the VOS operating system and are
written in keep/fetch format.
2. Documentation
The following documentation is included with this release:
___________________________________
| Manual Name Pub. Number|
|____________________|_____________|
| Fetch Release Notes| 0891051-1.0|
|____________________|_____________|
Additional copies may be ordered by contacting the Harris
Software Support Center. The toll-free number for calls
outside of Florida is 1-800-245-6453. For calls within
Florida or outside the continental United States the number
is 1-305-971-6248.
__________
- These release notes cover the following products: Fetch
- 1 -
Fetch 1.0 Release Notes
3. Prerequisites
Prerequisites for Fetch Version 1.0 are as follows:
3.1 Hardware
o Any Series 1000, 3000 or 4000 system.
3.2 Software
o CX/UX 6.1
4. Installation
Please refer to the CX/UX System Administration Manual,
Chapter 3, for instructions on software installation.
5. Cautions
This software works only with reel-to-reel tapes at 1600bpi
and 6250bpi. For more information, refer to the fetch(1)
and verify(1) manual pages.
6. Direct Software Support
Software support is available from a central source. When
you need assistance or information about your system, please
contact the Harris Software Support Center at our toll free
number (800-245-6453). Our customers outside the
continental United States can contact us directly at 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.
- 2 -
Release Notes 1.0 Fetch
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.
- 3 -
CONTENTS
1. Introduction.............................................. 1
2. Documentation............................................. 1
3. Prerequisites............................................. 2
3.1 Hardware............................................. 2
3.2 Software............................................. 2
4. Installation.............................................. 2
5. Cautions.................................................. 2
6. Direct Software Support................................... 2
- i -
_________________________________________________________________
HARRIS
COMPUTER SYSTEMS
_________________________________________________________________
FETCH
VERSION 1.0
RELEASE NOTES
0891051-1.0
December 1992
_________________________________________________________________
return to index
================================================================================
CX/UX FLOPPY DISK DRIVER AND UTILITIES -
VERSION 5.3
RELEASE NOTES
Harris Computer Systems Division
1. Introduction
The CX/UX Floppy Disk Driver and Utilities product provides
support for IBM-PC compatible floppy disk drives on Harris
Series 4000 real-time computers.
2. Documentation
The following documentation is included with this release:
________________________________________________________________
| Manual Name Pub. Number|
|_________________________________________________|_____________|
| CX/UX Floppy Disk Driver/Utilities Release Notes| 0890386-5.3|
|_________________________________________________|_____________|
Additional copies may be ordered by contacting the Harris
Software Support Center. The toll-free number for calls
outside of Florida is 1-800-245-6453. For calls within
Florida or outside the continental United States the number
is 1-305-971-6248.
__________
- These release notes cover the following products:
floppy
- 1 -
CX/UX Floppy Disk Driver and 5.3lities Release Notes
3. Prerequisites
Prerequisites for CX/UX Floppy Disk Driver and Utilities
Version 5.3 are as follows:
3.1 Hardware
o Any Series 4000 system
o An HVME SCSI Adapter (HSA) or an Integral SCSI/Ethernet
(ISE) daughtercard
3.2 Software
o CX/UX 5.3 or later
o All CX/UX 5.3 patches up to and including cx5.3-042
4. Installation
Please refer to the CX/UX System Administration Manual,
Chapter 3, for instructions on software installation.
5. Cautions
Proper use of the floppy software requires proper
configuration and software setup. Refer to the gf(7) manual
page for assistance.
6. New Features in this Release
This product consists of two major components: the generic
floppy disk driver and the MS-DOS compatible utility set.
The generic floppy disk driver supports several models of
SCSI interfaced floppy disk drives, including the TEAC FD-
235JS-501 3.5" micro floppy drive and the TEAC FD-55GS-751
5.25" mini floppy drive. Both drives are equipped with
integral SCSI interfaces, which means the drives can be
connected to a Series 4000 system either via the HVME SCSI
Adapter (HSA) or via the Integral SCSI/Ethernet daughtercard
- 2 -
Release Notes CX/UX Floppy Disk Driver and Utilities
(ISE). With these drives, the generic floppy disk driver
supports the following IBM-PC compatible media:
Media Capacity
______________________
31/2" DS/DD 720 Kb
31/2" DS/HD 1.44 Mb
31/2" DS/ED 2.88 Mb*
51/4" DS/DD 360 Kb
51/4" DS/HD 1.2 Mb
* Not fully tested
This floppy disk driver will comply with Level 1 of the
88open Compatibility Standards PC Floppy Emulation
Supplements. The exact functionality that this compliance
provides is documented in the gf(7) manual page of the CX/UX
Administrator's Reference Manual. Note that the floppy disk
driver is not yet fully compliant with the 88open standard
in this release of the product.
The generic floppy disk driver supports UNIX character
device read(2) and write(2) semantics. This means the
floppy drive can be used by any program that reads and
writes files, such as tar(1), cpio(1), cat(1), and dd(1).
However, there is no support for creating a CX/UX filesystem
on a floppy disk.
The other part of this product is the MS-DOS compatible
utility set. This utility set consists of the necessary
commands to create and access MS-DOS formatted floppy disks.
In this product release, the following utilities are
provided:
dosformat performs both a low level MS-DOS format
and a high level MS-DOS format of the
floppy disk
dosclear performs only a high level MS-DOS format
of the floppy disk
dosmkdir creates a new directory on the floppy
disk
dosdir lists the contents of a MS-DOS directory
on the floppy disk
dosget reads a MS-DOS file on the floppy disk
and writes its contents to stdout
- 3 -
CX/UX Floppy Disk Driver and 5.3lities Release Notes
dosput writes a MS-DOS file on the floppy disk
with the data read from stdin
dosdel deletes a MS-DOS file from a directory
on the floppy disk
dosinit initializes various shell environment
variables required by the other
utilities
More information about these utilities is available in the
corresponding manual pages in Section 1 of the CX/UX User's
Reference Manual.
7. Changes from Previous Releases
None.
8. Direct Software Support
Software support is available from a central source. When
you need assistance or information about your system, please
contact the Harris Software Support Center at our toll free
number (800-245-6453). Our customers outside the
continental United States can contact us directly at 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.
- 4 -
Release Notes CX/UX Floppy Disk Driver and Utilities
- 5 -
CONTENTS
1. Introduction.............................................. 1
2. Documentation............................................. 1
3. Prerequisites............................................. 2
3.1 Hardware............................................. 2
3.2 Software............................................. 2
4. Installation.............................................. 2
5. Cautions.................................................. 2
6. New Features in this Release.............................. 2
7. Changes from Previous Releases............................ 4
8. Direct Software Support................................... 4
- i -
_________________________________________________________________
HARRIS
COMPUTER SYSTEMS
_________________________________________________________________
CX/UX FLOPPY DISK DRIVER AND UTILITIES
VERSION 5.3
RELEASE NOTES
0890386-5.3
September 1992
_________________________________________________________________
return to index
================================================================================
CX/UX ID TOOLS -
VERSION 1.0
RELEASE NOTES
Harris Computer Systems Division
1. Introduction
The CX/UX ID Tools provide a simple, yet powerful database
for cross referencing identifiers and the source files they
appear in. The ID Tools support C and Ada source as well as
plain text files. FORTRAN is not supported by this toolset.
The ID Tools provide a source scanner which builds an ID
database and a series of programs with which to query the
database.
2. Documentation
The following documentation is included with this release in
addition to online man pages:
________________________________________________
| Manual Name Pub. Number|
|_________________________________|_____________|
| CX/UX ID Tools 1.0 Release Notes| 0890408-1.0|
|_________________________________|_____________|
Additional copies may be ordered by contacting the Harris
Software Support Center. The toll-free number for calls
outside of Florida is 1-800-245-6453. For calls within
Florida or outside the continental United States the number
is 1-305-971-6248.
__________
- These release notes cover the following products:
id_tools
- 1 -
CX/UX ID Tools 1.0 Release Notes
3. Prerequisites
Prerequisites for CX/UX ID Tools Version 1.0 are as follows:
3.1 Hardware
o Any Harris Series 4000 or 5000 system
3.2 Software
o CX/UX 6.1 or higher
4. Installation
Please refer to the CX/UX System Administration Manual,
Chapter 3, for instructions on software installation.
5. Cautions
If your system has run the public-domain ID tools in the
past, the system administrator should verify that old copies
of the ID tool programs are removed from the system prior to
installation of the CX/UX ID Tools.
Any existing ID databases created by the public-domain ID
tools are incompatible with the CX/UX ID tools. Users
should remove existing ID databases and rebuild them from
scratch after the CX/UX ID Tools are installed.
6. New Features in this Release
This is the initial release of the CX/UX ID Tools.
The ID Tools provide a source scanner which builds an ID
database, and a series of programs with which to query the
database.
An ID database is simply a file containing a list of file
names, a list of identifiers, and a binary relation (stored
as a bit matrix) indicating which of the identifiers appear
- 2 -
Release Notes 1.0 CX/UX ID Tools
in each file. With this database and some tools to
manipulate the data, a host of tasks become simpler and
faster. It is possible to `grep' through hundreds of files
for a name, skipping the files that don't contain the name.
Another use might be to search for all the memos containing
references to a project. Another tool provides the ability
to edit every file that calls a particular function, for
example, to add a new required argument. The ID Tools are
beneficial to anyone maintaining a large software project or
even a large set of text files.
There are several programs in the ID family:
o mkid scans the files, finds the identifiers and builds
the ID database.
o lid is used to generate a list of files which contain
an identifier.
o aid is much like lid, but searches for identifiers
containing a particular substring.
o eid will invoke an editor on each of the files
containing an identifier.
o gid will `grep' (search) for an identifier in the
subset of files known to contain it.
o pid is used to query the path names of the files in the
database rather than the contents.
o fid prints a list of all the identifiers that occur in
a given file. If two filenames are given, fid will
print the identifiers that appear in both files.
o iid is an interactive program supporting complex
queries to intersect and join sets of file names.
Please see the online man page for each tool for more
detailed information.
7. Changes from Previous Releases
This is the initial release of the CX/UX ID Tools.
- 3 -
CX/UX ID Tools 1.0 Release Notes
8. Direct Software Support
Software support is available from a central source. When
you need assistance or information about your system, please
contact the Harris Software Support Center at our toll free
number (800-245-6453). Our customers outside the
continental United States can contact us directly at 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.
- 4 -
CONTENTS
1. Introduction.............................................. 1
2. Documentation............................................. 1
3. Prerequisites............................................. 2
3.1 Hardware............................................. 2
3.2 Software............................................. 2
4. Installation.............................................. 2
5. Cautions.................................................. 2
6. New Features in this Release.............................. 2
7. Changes from Previous Releases............................ 3
8. Direct Software Support................................... 4
- i -
_________________________________________________________________
HARRIS
COMPUTER SYSTEMS
_________________________________________________________________
CX/UX ID TOOLS
VERSION 1.0
RELEASE NOTES
0890408-1.0
NOVEMBER 1992
_________________________________________________________________
return to index
================================================================================
NIGHTTRACE -
VERSION 1.3
RELEASE NOTES
Harris Computer Systems Division
1. Introduction
The NightTrace product is part of Harris' new NightStar
series of tools 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.
ntraceud is a daemon process responsible for writing 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. ntrace is the
interactive trace-event analysis tool. It provides a
graphical view and summary statistics about the run-time
behavior of one or more application programs and possibly
the system.
2. Documentation
The following documentation is included with this release:
__________
- These release notes cover the following products:
NightTrace
- 1 -
NightTrace 1.3 Release Notes
______________________________________________
| Manual Name Pub. Number|
|_______________________________|_____________|
| CX/UX NightTrace Manual | 0890398-030|
| CX/UX NightTrace Release Notes| 0890398-1.3|
|_______________________________|_____________|
Additional copies may be ordered by contacting the Harris
Software Support Center. The toll-free number for calls
outside of Florida is 1-800-245-6453. For calls within
Florida or outside the continental United States the number
is 1-305-971-6248.
3. Prerequisites
Prerequisites for NightTrace Version 1.3 are as follows:
3.1 Hardware
o An installed X Window System(TM) 1 (X) server
o Approximately two megabytes of free X-server memory
o A Series 4000 or Series 5000 system
o Enough disk space to accommodate each trace event you
log, at an average rate of 16 bytes per trace event
o Shared memory
o Read access to the system's interval timer
o Optionally, read and write access to the system's
interrupt priority level (IPL) register
o Optionally, page lock access (ACC_PLOCK)
__________
1. The X Window System is a trademark of the Massachusetts
Institute of Technology.
- 2 -
Release Notes 1.3 NightTrace
3.2 Software
o CX/UX or CX/RT Release 6.2 or later
o Patch trace6.2-001 is required for kernel tracing
o The trace optional product is required for kernel
tracing NightTrace
o Elan License Manager(TM) 2
4. Installation
The NightTrace installation tape is in cpio format. It
contains the NightTrace executables, libraries, and online
documentation. Please refer to the CX/UX System
Administration Manual, Chapter 3, for general instructions
on software installation.
The ntrace executable of the NightTrace product must be run
with the Elan License Manager. Follow the steps in the
"Obtaining Licenses" section of the Elan License Manager
Release Notes (0891055); the feature alias is NightTrace.
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 Harris Software
Distribution at 1-800-666-5405.
This product must logically reside in the /usr partition. If
you do not have enough disk space to physically install
NightTrace on /usr, then you can install it somewhere else.
The installation script will automatically make symbolic
links from /usr to where NightTrace is installed.
If you have an earlier version of NightTrace previously
installed on your system, then you should do the following:
1. Sign on as root, or use the "su" program to become
root.
__________
2. Elan License Manager is a trademark of Elan Computer
Group, Inc.
- 3 -
NightTrace 1.3 Release Notes
2. Remove the /usr/lib/NightTrace directory.
3. Execute "cd {destination}/usr/lib/NightTrace", where
{destination} is the directory where you loaded
NightTrace. This will position you in the NightTrace
support directory.
4. Execute "./Install -f" to force the removal of other
old NightTrace files and directories so that new ones
can be made.
You should back up any old versions of the NightTrace files
and remove them.
The files (or symbolic links) must be installed as:
o /usr/bin/ntrace
o /usr/bin/ntraceud
o /usr/include/ntrace.h
o /usr/lib/libntrace.a
o /usr/lib/NightTrace/eventmap
o /usr/lib/NightTrace/examples/entry_exit.c
o /usr/lib/NightTrace/examples/entry_exit_map
o /usr/lib/NightTrace/examples/entry_exit_page
o /usr/lib/NightTrace/Install
o /usr/lib/NightTrace/kernel2
o /usr/lib/NightTrace/kernel4
o /usr/lib/NightTrace/kernel6
o /usr/lib/NightTrace/kernel8
o /usr/lib/NightTrace/NightTrace_symlinks
o /usr/lib/NightTrace/tables
o /usr/man/u_man/man1/ntraceud.1
- 4 -
Release Notes 1.3 NightTrace
o /usr/man/u_man/man1/ntrace.1
o /usr/man/p_man/man3/ntrace.3x
o /usr/man/p_man/man4/ntrace.4
o /usr/catman/u_man/man1/ntraceud.1.z
o /usr/catman/u_man/man1/ntrace.1.z
o /usr/catman/p_man/man3/ntrace.3x.z
o /usr/catman/p_man/man4/ntrace.4.z
To install NightTrace, follow these steps:
1. Sign on as root, or use the "su" program to become
root.
2. If you want to physically install NightTrace under
/usr, then execute "cd /" to position yourself under
the root directory.
If you want to physically install NightTrace under the
partition named "/partition", then execute the
following commands (in the order specified):
mkdir -p /partition/NightTrace_1.3/usr
cd /partition/NightTrace_1.3
3. Issue the command "cpio -iBcvdum < /dev/rmt/0mn" to
read in the first two files setup and tape_list with no
rewind. (NOTE: the installation tape is assumed to be
loaded on drive 0.)
4. Issue the command "./setup" to run a menu-driven
program that installs the new NightTrace product.
5. The setup program displays a prompt similar to: "Enter
the name of the running kernel or if /unix".
Press the carriage return key. The following message
is displayed: "Non-generic boot. Assuming System
Generation not to be done."
6. The next message displayed is: "The first product tape
should be loaded on device /dev/rmt/0mn. Is this the
case? (y|n)". Type "y".
- 5 -
NightTrace 1.3 Release Notes
7. Expect a pause, then a menu will prompt: "Enter the
numbers of the actions you would like to perform."
Select "Load NightTrace object files".
8. There will be a message similar to: "Loading NightTrace
object files" as files come onto the system under the
directories usr/bin, usr/lib, usr/man, and usr/catman.
9. When the menu returns, select "Exit", and remove the
tape from the drive.
10. Execute "cd ./usr/lib/NightTrace" to position yourself
in the NightTrace support directory. If you want to
see what the installation script will do, you can
execute it with the -n option, which prints what it
would do without doing anything: "./Install -n". When
you are satisfied, execute without the -n option:
"./Install".
11. Installation of NightTrace version 1.3 is now complete.
5. Cautions
o By default, NightTrace expects its users to have read
and write permission to the system's interrupt priority
level (IPL) register, read permission to the system's
interval timer, and page lock access (ACC_PLOCK). For
information on overriding these defaults, see the CX/UX
NightTrace Manual. For information on the IPL register
and interval timer, see the CX/UX Programmer's Guide.
o On Series 5000 systems, do not call clock_settime(3P4)
from your application. This system call can corrupt
the system interval timer which NightTrace uses for
trace-event timings.
o NightTrace needs 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 yet.
If you wish to capture a window, follow these steps:
- 6 -
Release Notes 1.3 NightTrace
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 3 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 problems 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
__________
3. PostScript is a registered trademark of Adobe Systems
Inc.
- 7 -
NightTrace 1.3 Release Notes
merged by ntrace incorrectly. This can occur
because the trace tool only records the low 32
bits of the interval timer in kernel-trace
records. 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. This
should happen very rarely, since the interval
timer high 32 bits only change once every 28.6
minutes on Series 4000 systems and once every 18.3
minutes on Series 5000 system.
- It is possible, though unlikely, for system calls
to nest, confusing NightTrace. 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. New Features in this Release
o Running NightTrace now requires installation of the
Elan License Manager. See the "Installation" section
of these release notes for details.
o The bits() function is no longer documented. Use
shifting and masking instead.
o There is now full support of all C-language operators,
including: &, |, ^, ?:, %, <<, and >>. See the "Using
Expressions" chapter of the CX/UX NightTrace Manual.
o It is now possible to name trace events with associated
configuration information. These trace events are
called qualified events. See the "Using Expressions"
chapter of the manual.
o The support for trace-event summaries is greatly
improved. See the "Using the Built-In Tools" chapter
of the manual.
- 8 -
Release Notes 1.3 NightTrace
o Several chapters and an appendix in the manual now
contain exercises that illustrate NightTrace concepts.
o The following X resources are new. See the "GUI
Customization" appendix of the manual for details.
- Ntrace*QualifiedEventDialog
- Ntrace*SummarizeForm*SaveTextAsPopup
7. Changes from Previous Releases
o All ntrace options can be typed in as mnemonic words or
letters. You can no longer group options after a
single hyphen. You can abbreviate all options to their
shortest unambiguous length. Options are case-
insensitive. Wherever possible, the meaning of old
option letters has been preserved. Exceptions include
the following:
- The old -L (listing) option is now -filestats.
- The old -h (hardclock) option is now -nohardclock.
- The -version, -start, and -end options are new.
Use the -start and -end options to reduce the
number of trace events loaded when ntrace starts
up.
For a full list of options, see ntrace(1).
o All ntraceud options can be typed in as mnemonic words
or letters. You can no longer group options after a
single hyphen. You can abbreviate all options to their
shortest unambiguous length. Options are case-
insensitive. Wherever possible, the meaning of old
option letters has been preserved. Exceptions include
the following:
- The old -S (do not set IPL) option is now
-ipldisable.
- The old -w option is now -bufferwrap.
- The old -o option is gone. The new default
behavior has ntraceud overwriting a trace-event
log file that is not currently in use by another
daemon. No new option causes the old non-
- 9 -
NightTrace 1.3 Release Notes
overwrite behavior.
- The old -p (present summary information) option is
now -stats.
- The old -h (high-water mark) option is now
-cutoff.
- The old -b (buffer size) option is now -memsize.
- The -version option is new.
For a full list of options, see ntraceud(1).
o The Main Window is now called the Global Window for
compatibility with the NightView debugger.
o Each of the NightTrace windows has a unique icon image
that relates to the window's function. The Global
Window icon displays the identifying NightTrace image,
and each icon for the other windows includes this image
as part of its icon. If you are displaying the icon
images, you can quickly see which iconified windows
belong to the NightTrace application.
o The "X Resources" appendix is now called "GUI
Customization" for compatibility with the NightView
documentation.
o The following X resources have been replaced. For more
information about X resources, see the "GUI
Customization" appendix of the manual.
Old Name New Name
___________________________ _________________________
Ntrace*MainWindow Ntrace*GlobalWindow
Ntrace*OpenDialog Ntrace*OpenPopup
Ntrace*ReadDialog Ntrace*ReadPopup
Ntrace*SaveAsDialog Ntrace*SaveAsPopup
Ntrace*IntegerVariableDefinitionForm Ntrace*MacroDialog
Ntrace*StateDefinitionForm Ntrace*QualifiedStateDialog
Ntrace*Color*GraphColumn Ntrace*Color*Column
Ntrace*Mono*GraphColumn Ntrace*Mono*Column
o The GraphColumn display object is now called Column.
o Trace-event codes are now called trace-event IDs.
- 10 -
Release Notes 1.3 NightTrace
o Trace-event names in event-name files are now called
trace-event tags in event-map files. See the "Viewing
Trace-Event Logs with Ntrace" chapter of the manual.
o The file /usr/lib/NightTrace/eventnames is now
/usr/lib/NightTrace/eventmap.
o A menu entry on the Global Window changed from "Read
Event-Name File" to "Read Event-Map File...."
o The /usr/lib/NightTrace/tables file contains four new
pre-defined format tables: state_summary,
event_summary, event_arg_summary and
event_arg_dbl_summary. See the "Using Expressions"
chapter of the manual.
o State variables are now called qualified states. See
the "Using Expressions" chapter of the manual.
o Integer variables are now called macros. Macro
references may be nested. Like integer variables,
macro references are preceded by a $. See the "Using
Expressions" chapter of the manual.
o Pre-defined variables have been replaced by functions.
The functions have different names than the variables
they replace. There are more functions. Functions
that return times always return seconds in type double.
Many new functions take a qualified event or qualified
state as an argument. Unlike pre-defined variables,
function names are not preceded by a $. See the "Using
Expressions" chapter of the manual.
o Pre-defined variables will not be supported after this
release. Use the new $count macro or sum() function
for counting or summation instead of the $$ predefined
variable.
8. Direct Software Support
Software support is available from a central source. When
you need assistance or information about your system, please
contact the Harris Software Support Center at our toll free
number (800-245-6453). Our customers outside the
continental United States can contact us directly at 305-
971-6248. The Software Support Center operates Monday
through Friday from 8 a.m. to 7 p.m., Eastern Standard time.
- 11 -
NightTrace 1.3 Release Notes
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.
- 12 -
CONTENTS
1. Introduction............................................. 1
2. Documentation............................................ 1
3. Prerequisites............................................ 2
3.1 Hardware............................................ 2
3.2 Software............................................ 3
4. Installation............................................. 3
5. Cautions................................................. 6
6. New Features in this Release............................. 8
7. Changes from Previous Releases........................... 9
8. Direct Software Support.................................. 11
- i -
_________________________________________________________________
HARRIS
COMPUTER SYSTEMS
_________________________________________________________________
NIGHTTRACE
VERSION 1.3
RELEASE NOTES
0890398-1.3
March 1994
_________________________________________________________________
return to index
================================================================================
CX/UX HAPSE POSIX 1003.5 -
VERSION 2.0
RELEASE NOTES
Harris Computer Systems Division
1. Introduction
CX/UX HAPSE POSIX= 1003.5 is a complete implementation of
the Institute of Electrical and Electronic Engineers (IEEE)
standard IEEE-Std-1003.5-1992. POSIX 1003.5 is an abstract
Ada binding to items covered by POSIX 1003.1. This
implementation is fully compliant with the standard and
allows users to create fully compliant applications. This
product includes source code for the specification of all
POSIX 1003.5 packages as well as the pre-compiled form of
the source for the specifications and bodies of those
packages. This product was built with the validated Harris
Ada compiler and requires the complete HAPSE product
(Product Model Numbers XL1491 or XL1492) for use.
2. Documentation
The following documentation is included with this release:
__________________________________________________________
| Manual Name Pub. Number|
|___________________________________________|_____________|
| CX/UX HAPSE POSIX 1003.5 Conformance Guide| 0890404-010|
| CX/UX HAPSE POSIX 1003.5 Release Notes | 0890404-2.0|
|___________________________________________|_____________|
Specification of the actual POSIX 1003.5 standard is
available directly from IEEE, the Institute of Electrical
__________
- These release notes cover the following products: 88K
HAPSE POSIX 1003.5
- 1 -
CX/UX HAPSE POSIX 1003.5 2.0 Release Notes
and Electronic Engineers (1-800-678-IEEE).
Additional copies of the Harris documentation may be ordered
by contacting the Harris Software Support Center. The
toll-free number is 1-800-245-6453. For calls outside the
continental United States the number is 1-305-971-6248.
3. Prerequisites
Prerequisites for CX/UX HAPSE POSIX 1003.5 Version 2.0 are
as follows:
3.1 88K Hardware
o Any Harris Series 4000 or 5000 system
3.2 Software
o CX/UX 6.2 or higher (CX/RT and CX/SX version 6.2 are
also acceptable)
o HAPSE v5.2 or higher
4. Cautions
None.
5. Installation
The installation tape is in cpio format. It contains the
source for all POSIX 1003.5 package specifications as well
as the pre-compiled versions of the package specifications
and bodies.
To install CX/UX HAPSE POSIX 1003.5, follow these steps:
o Sign on as root, or use the "su" program to become
root.
o CX/UX HAPSE POSIX 1003.5 should be installed after the
HAPSE product has been installed. It is intended that
this product be installed under the root partition,
since its default placement is "usr/hapse_88k_5.2-
000/bindings/posix_1003.5". This is not a requirement.
- 2 -
Release Notes 2.0 CX/UX HAPSE POSIX 1003.5
o Execute "cd /" to position yourself under the root
directory.
o Mount the CX/UX HAPSE POSIX 1003.5 installation tape.
o Issue the command "cpio -iBcvdum < /dev/rmt/0mn" to
read in the first two files setup and tape_list (Note:
the installation tape is assumed to be loaded on drive
0.)
o Issue the command "./setup" to run a menu-driven
program that installs the new CX/UX HAPSE POSIX 1003.5
product.
o The setup program displays a prompt similar to: "Enter
the name of the running kernel or if /unix".
Press the carriage return key. The following message
is displayed: "Non-generic boot. Assuming System
Generation not to be done."
o The next message displayed is: "Reel 1 of the product
tape(s) must be loaded on device /dev/rmt/0mn. Is this
the case? (y|n)". Type "y".
o Expect a pause, then a menu will prompt: "Enter the
numbers of the actions you would like to perform."
Select the number corresponding to "All".
o You will see a message similar to: "Loading object
files" as files come onto the system under the
directories usr/hapse_88k_5.2-000, usr/hapse_88k_5.2-
000/bindings5.2, and usr/hapse_88k_5.2-
000/bindings/posix_1003.5.
o When the menu returns, select "Exit", and remove the
tape from the drive.
o Installation is now complete.
To test the installation, execute the following steps:
1. Log off from root and log on as a regular user.
2. Add /usr/hapse/bin to your PATH variable to make HAPSE
tools visible.
- 3 -
CX/UX HAPSE POSIX 1003.5 2.0 Release Notes
PATH=${PATH}:/usr/hapse/bin; export PATH # for /bin/sh
or /bin/ksh users
setenv PATH $PATH:/usr/hapse/bin # for /bin/csh users
3. Create a new HAPSE library in an empty directory.
mkdir a_new_directory
cd a_new_directory
a.mklib .
4. Add the CX/UX HAPSE POSIX 1003.5 library to your list
of visible HAPSE libraries. By default, this path is
/usr/hapse/88k_5.2/bindings/posix_1003.5; however, it
may be in an alternate location if you installed the
product tape into a directory other than "/".
a.path -I /usr/hapse/88k_5.2/bindings/posix_1003.5
5. Create and edit a source file named
"posix_Ada_version.a", in the current working
directory, to contain the following lines:
with posix ;
with text_io ;
procedure posix_Ada_version is
begin
text_io.put_line ("POSIX_Ada_Version =" &
integer'image(posix.POSIX_Ada_Version)) ;
end posix_Ada_version ;
6. Compile and link the program. The following command
will place the executable program file in
"./posix_Ada_version".
ada -o posix_Ada_version -M posix_Ada_version.a
7. Invoke the program. It will print the following
message to standard output:
- 4 -
Release Notes 2.0 CX/UX HAPSE POSIX 1003.5
POSIX_Ada_Version = 199206
6. Compliance
The CX/UX HAPSE POSIX 1003.5 Conformance Guide describes in
detail the compliance of the implementation with the
standard. The CX/UX HAPSE POSIX 1003.5 implementation is
fully compliant when the basic Ada runtime system is
selected by the user at link time. (This is the default.)
The CX/UX HAPSE POSIX 1003.5 implementation is not fully
compliant when the ARMS executive is selected at link time
(-arms option to the HAPSE tool a.ld). See the conformance
guide for more details.
7. Direct Software Support
Software support is available from a central source. When
you need assistance or information about your system, please
contact the Harris Software Support Center at our toll free
number (800-245-6453). Our customers outside the
continental United States can contact us directly at 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.
- 5 -
CONTENTS
1. Introduction.............................................. 1
2. Documentation............................................. 1
3. Prerequisites............................................. 2
3.1 88K Hardware......................................... 2
3.2 Software............................................. 2
4. Cautions.................................................. 2
5. Installation.............................................. 2
6. Compliance................................................ 5
7. Direct Software Support................................... 5
- i -
_________________________________________________________________
HARRIS
COMPUTER SYSTEMS
_________________________________________________________________
CX/UX HAPSE POSIX 1003.5
VERSION 2.0
RELEASE NOTES
0890404-2.0
March 1993
_________________________________________________________________
return to index
================================================================================
MIL-STD-1553 DEVICE DRIVER -
VERSION 7.0
RELEASE NOTES
Harris Computer Systems Division
1. Introduction
The MIL-STD-1553 product consists of the SBS Engineering
MIL-STD-1553 VMEbus interface card and appropriate software.
The MIL-STD-1553 card supports standard 1553 bus
connections, multiple data protocols, bus controller
operation and remote terminal simulation. The VMEbus
interface card is accessed via 64K bytes of memory
accessible on the VMEbus through the CX/UX shared memory
interface.
This release contains the kernel drivers and user-level
software to access a MIL-STD-1553 interface. This product
includes a vendor-provided user library, demonstration
programs, and test programs.
2. Documentation
The following documentation is applicable to this release:
___________________________________________________________________
| Manual Name Pub. Number |
|__________________________________________________|_______________|
| MIL-STD-1553 Device Driver Release Notes | 0890402-7.0 |
| MIL-STD-1553 Documentation Set (2 Vendor Manuals)| |
|__________________________________________________|_______________|
SBS Engineering provides the MIL-STD-1553 Documentation Set
consisting of two manuals. The first is the hardware
__________
- These release notes cover the following products: sbs
- 1 -
MIL-STD-1553 Device Driver 7.0 Release Notes
reference manual, "MIL-STD-1553 Advanced Bus Interface (ABI)
Reference Manual." The other document is the software
library manual entitled "MIL-STD-1553 Interface Library
Reference Manual."
Additional copies may be ordered by contacting the Harris
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-305-971-6248.
3. Prerequisites
Prerequisites for MIL-STD-1553 Device Driver Version 7.0 are
as follows:
3.1 Hardware
o Any Series 4000 system
o SBS MIL-STD-1553 VMEbus interface card
3.2 Software
o CX/UX 7.0 or greater
4. Installation
Please refer to the CX/UX System Administration Manual,
Chapter 3, for instructions on software installation.
After installing the software product, the following steps
should be performed:
1. Edit the lines in the file
/usr/src/SBS/utilities/memconfig to match the
configuration of the MIL-STD-1553 boards in your system
configuration. Append this file to your /etc/rc.local
file.
2. Append the file
/usr/src/uts/machine/cf/sbs.config.insert to the end of
your system configuration file in
- 2 -
Release Notes 7.0 MIL-STD-1553 Device Driver
/usr/src/uts/machine/cf. Uncomment the appropriate
line(s) denoting the actual interfaces in use.
3. Copy the modified system configuration file to
/etc/master.
4. Configure and 'make' a new kernel using the modified
configuration file.
5. In the /dev directory, perform a MAKEDEV on the
appropriate devices (ami0, ami1, ami2).
6. Shutdown the system and reboot it with the newly
constructed kernel.
7. Verify board operation by executing the test programs
supplied in the /usr/src/SBS/abi directory.
5. Cautions
None.
6. New Features in this Release
None.
7. Changes from Previous Releases
This release allows the MIL-STD-1553 VMEbus interface card
to be used on Series 4000 systems running CX/UX 7.0 or
greater. This release cannot be used on machines running
versions of CX/UX prior to 7.0.
8. Direct Software Support
Software support is available from a central source. When
you need assistance or information about your system, please
contact the Harris Software Support Center at our toll free
number (800-245-6453). Our customers outside the
continental United States can contact us directly at 305-
971-6248. The Software Support Center operates Monday
through Friday from 8 a.m. to 7 p.m., Eastern Standard time.
- 3 -
MIL-STD-1553 Device Driver 7.0 Release Notes
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.
- 4 -
CONTENTS
1. Introduction.............................................. 1
2. Documentation............................................. 1
3. Prerequisites............................................. 2
3.1 Hardware............................................. 2
3.2 Software............................................. 2
4. Installation.............................................. 2
5. Cautions.................................................. 3
6. New Features in this Release.............................. 3
7. Changes from Previous Releases............................ 3
8. Direct Software Support................................... 3
- i -
_________________________________________________________________
HARRIS
COMPUTER SYSTEMS
_________________________________________________________________
MIL-STD-1553 DEVICE DRIVER
VERSION 7.0
RELEASE NOTES
0890402-7.0
March 1993
_________________________________________________________________
return to index
================================================================================
CSPI SUPERCARD LIBRARY -
VERSION 2.2
RELEASE NOTES
Harris Computer Systems Division
1. Introduction
This release contains all the user software for the
SuperCard1 Array Processor (AP). This product includes the
SuperCard user libraries, the download file, the emulation
library and the diagnostic program.
2. Documentation
The following Harris and vendor documentation is included
with this release:
________________________________________________________
| Manual Name Pub. Number |
|_______________________________________|_______________|
| CSPI SuperCard-1 Library Release Notes| 0890368-2.2 |
| CSPI SuperCard Programming Guides | 0890385 |
|_______________________________________|_______________|
CSPI provides a documentation set, titled "SuperCard
Programming Guides", which is delivered with the hardware.
The CSPI documentation set, consisting of seven manuals,
details the features and use of the SuperCard. Within this
documentation set is the CSPI SuperCard Installation Manual
and the CSPI SuperCard User Manual which provide details
__________
- These release notes cover the following products:
SuperCard
1. SuperCard, SuperCard-1 and SuperCard-2 are trademarks of
CSPI
- 1 -
CSPI SuperCard Library 2.2 Release Notes
about the installation of the SuperCard software. This
information about software installation is not applicable to
the Harris computer systems. Please refer to section 4 in
this document instead for instructions on software
installation.
Additional copies may be ordered by contacting the Harris
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-305-971-6248.
3. Prerequisites
Prerequisites for CSPI SuperCard Library Version 2.2 are as
follows:
3.1 Hardware
o Any Series 4000 system
o CSPI SuperCard-1 or SuperCard-2 Array Processor
3.2 Software
o CX/UX 7.0 or greater
4. Installation
Please refer to the CX/UX System Administration Manual,
Chapter 3, for instructions on software installation.
After installing the library software, a new SuperCard
device driver must be installed. To install the new
SuperCard device driver, change your current directory to
/usr/src/supercard-1/install and execute the
install_csdriver command. Once the device driver is
installed a new kernel must be built.
To build a new kernel the installer must configure the
appropriate SuperCard devices in the system configuration
file. To do this, the installer should uncomment the lines
in the system configuration file that represent a SuperCard
- 2 -
Release Notes 2.2 CSPI SuperCard Library
installed on the system. An example of the lines in the
configuration file follow:
# CSPI SuperCard Array Processor
# Uncomment only those lines which represent a SuperCard-1 device which
# actually exists on your system.
#
#device cs0 at vba0 csr 0x3fff7000 flags 0xea00 vector cs_intr
#device cs1 at vba0 csr 0x3fff7080 flags 0xee00 vector cs_intr
When a SuperCard is installed in a Secondary VME bucket the
following lines should be used:
device cs0 at vba1 csr 0x3fff7000 flags 0xaa00 vector cs_intr
device cs1 at vba1 csr 0x3fff7080 flags 0xae00 vector cs_intr
For further reference, the device driver needs to be
configured into the kernel with the following line:
driver cs cdev 83 vector cs_intr
This line should already exist in your system configuration
file by default.
The installer can then reconfigure and build a new kernel
with the CSPI SuperCard device driver. Consult the CX/UX
System Administration Manual, Chapter 4, for further
instructions.
Before installing the hardware on the system the SuperCard
must be configured to be either device 0 or device 1. The
installer should consult the CSPI SuperCard Installation
Manual for instructions on how to set the switches
accordingly. For Harris installations it should be noted
that devices destined for the secondary VME bus need to be
configured differently as illustrated by the following
table.
Logical SuperCard Physical SuperCard
cs0 (primary) Unit 0
cs1 (primary) Unit 1
cs0 (secondary) Unit 2
cs1 (secondary) Unit 3
In the table above, logical SuperCard refers to the name the
operating system associates with the device. Physical
SuperCard is the device unit number with which the SuperCard
is configured as determined by the switch settings described
- 3 -
CSPI SuperCard Library 2.2 Release Notes
in the CSPI SuperCard Installation Manual.
After rebooting with a new kernel, the installer should
change to the /dev directory and run MAKEDEV to create the
desired device nodes.
To create two devices, the installer would execute:
MAKEDEV cs0 cs1
In order for MAKEDEV to function properly, the device driver
must be configured in the system's /etc/master configuration
file, or the configuration file used to build the kernel
including the SuperCard device driver should be provided on
the MAKEDEV command line as an argument to the -f option
(See makedev(1m)).
The maximum number of devices a system can have is two.
Next, the necessary shared memory regions for the SuperCard
libraries must be configured. Use the following commands as
appropriate to configure the shared memory regions required
for the installed SuperCard devices:
/usr/etc/csconfig cs0
/usr/etc/csconfig cs1
These commands may be added to the system's /etc/rc.local
file or uncommented from the system's /etc/rc file.
NOTE: The csconfig command requires that the system imposed
limit for maximum shared memory region size be large enough
to contain the memory space of the SuperCard. If the
csconfig command were to fail to get the shmid of the
SuperCard shared memory region, it is probably caused by
this system imposed limit. In order to get around this
problem, some systems will need to increase the maximum
shared memory segment size by changing the SHMMAX value in
/usr/src/uts/machine/cf/ipcconfig.h to ( n * 1048576 )
before building a new kernel. In this example, n equals the
memory size (in megabytes) of the largest SuperCard
installed on the system.
Finally, type in the command /usr/bin/CSPI/cstst to run the
hardware diagnostic program. This program will execute the
SuperCard functions and verify their results. All tests
should run without failures. If this program does not run
correctly, there was probably an error in installing the
SuperCard software. In the event of the diagnostic program
- 4 -
Release Notes 2.2 CSPI SuperCard Library
failing, you should verify that you followed all the steps
in installing the software and hardware correctly.
5. Cautions
When compiling programs that use the SuperCard libraries,
the user must have the SDE_TARGET environment variable set
to COFF. Only COFF object format libraries are shipped with
this release, but ELF libraries can be built. See the
SuperCard manual for further information on rebuilding the
SuperCard libraries, and see the CX/UX 7.0 release notes for
further information on building ELF libraries. When using
ELF libraries the user must set the SDE_TARGET environment
variable to ELF.
6. Features in this Release
6.1 The SuperCard Interface Libraries
This product includes the user interface libraries to the
SuperCard. There are several libraries provided with the
product. These are:
o SuperCard Library (libhsl.a)
o SuperCard Library (libtsl.a)
o SuperCard Library (libldr.a)
o Combined SuperCard Library (libcs.a)
o Emulation Library (libcsemu.a)
o SuperCard Download File (xlssl.lo)
o SuperCard Download Library (libssl.a)
The SuperCard Libraries contain the software functions to
access and operate the CSPI SuperCard Array Processor. The
Emulation Library contains the same functions as the
SuperCard Libraries, but the functions are performed by the
host CPU instead of the Array Processor.
- 5 -
CSPI SuperCard Library 2.2 Release Notes
6.2 The SuperCard Device Driver
The SuperCard device driver is required by the SuperCard
libraries to provide special support for handling device
interrupts and supplying special information about the
device.
6.3 DMA on Harris Platforms
The SuperCard has the capabilities of being a (H)VME Bus
Master allowing the Intel i860 processor to take control of
the System I/O Bus to perform DMA transfers. In order to
perform DMA transfers, users should perform the following
steps:
o In the system configuration file, reserve a contiguous
block of physical memory with the cache-coherence flags
indicating that we want the caches to be coherent on
DMA reads and writes. The cache-coherence flag is
needed because the CSPI libraries do not perform any
cache control (i.e. they do not flush any caches as
needed). Choose addresses in the high end of the
physical memory installed on your system. An example
line in the configuration file would look like:
reserve 0xf00000 length 0x20000 cache-coherence DMA_RDWR
o Configure a shared memory region, and bind it to the
reserved memory section. An example command for this
purpose is:
shmconfig -p 0xf00000 -s 0x20000 shmkey
The shared memory key, shmkey, can be any unique shared
memory key that user programs know about.
o Attach data space in a user's program to the shared
memory region via the shmget(2) and shmat(2) system
calls. See the man pages for the shmget(2) and
shmat(2) system calls for more information.
o Transfer data between the CSPI SuperCard and this
memory region using only the SuperCard xdmah function
call. See the CSPI SuperCard User's Manual for more
information.
CAUTION - There is very little operating system protection
- 6 -
Release Notes 2.2 CSPI SuperCard Library
to prevent the user from using the DMA privileges of the
SuperCard from reading or writing the entire memory map and
I/O registers of the system. Therefore, great care should
be taken when granting use of the SuperCard to system users.
The only way to deny access to the DMA is to deny access to
the SuperCard by setting the ownership of /dev/cs*
appropriately.
6.4 Development Environment
Provided with the CSPI SuperCard software is the capability
to download compiled code for the Array Processor.
Currently the development environment is not supported on
the Harris systems, but the necessary files needed to
compile code for the SuperCard are provided under the
directory /usr/src/supercard-1/ssl. The use of these files
is described in CSPI's documentation for the SuperCard
development environment supported on the Sun-32 and Sun-43
workstations.
7. Changes from Previous Releases
This release allows the SuperCard to be used with CX/UX
version 7.0. This release cannot be used with any versions
of CX/UX prior to 7.0. For further references to new
features included with this release refer to the README file
installed under /usr/src/supercard-1/README.
8. Direct Software Support
Software support is available from a central source. When
you need assistance or information about your system, please
contact the Harris Software Support Center at our toll free
number (800-245-6453). Our customers outside the
continental United States can contact us directly at 305-
__________
2. Sun-3 is a registered trademark of Sun Microsystems,
Inc.
3. Sun-4 is a registered trademark of Sun Microsystems,
Inc.
- 7 -
CSPI SuperCard Library 2.2 Release Notes
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............................................. 1
3. Prerequisites............................................. 2
3.1 Hardware............................................. 2
3.2 Software............................................. 2
4. Installation.............................................. 2
5. Cautions.................................................. 5
6. Features in this Release.................................. 5
6.1 The SuperCard Interface Libraries.................... 5
6.2 The SuperCard Device Driver.......................... 6
6.3 DMA on Harris Platforms.............................. 6
6.4 Development Environment.............................. 7
7. Changes from Previous Releases............................ 7
8. Direct Software Support................................... 7
- i -
_________________________________________________________________
HARRIS
COMPUTER SYSTEMS
_________________________________________________________________
CSPI SUPERCARD LIBRARY
VERSION 2.2
RELEASE NOTES
0890368-2.2
August 1993
_________________________________________________________________
return to index
================================================================================
TEX -
VERSION 1.0
RELEASE NOTES
Harris Computer Systems Division
1. Introduction
TeXTM is a computer typesetting language developed and
implemented by Donald Knuth, Professor of Computer Science
at Stanford University. This release of TeX is version 3.14
from the University of Washington Computer Science
Department. It is Class B software and, therefore, is not
supported by Harris.
2. Copyright
TeX is a trademark of the American Mathematical Society
(AMS). The source code copyright belongs to Donald Knuth.
To keep TeX as standard and portable as possible, permission
to use the TeX source code is granted only if absolutely no
changes are made to it.
3. Documentation
The following documentation is included with this release:
_________________________________
| Manual Name Pub. Number|
|__________________|_____________|
| TEX Release Notes| 0890415-1.0|
|__________________|_____________|
Additional copies may be ordered by contacting the Harris
Software Support Center. The toll-free number for calls
__________
- These release notes cover the following products: TeX
- 1 -
TeX 1.0 Release Notes
outside of Florida is 1-800-245-6453. For calls within
Florida or outside the continental United States the number
is 1-305-971-6248.
Documentation for the TeX language may be found in The
TeXbook, by Donald Knuth, published by Addison Wesley (ISBN
0-201-13448-9). You may also wish to consider getting LaTeX
by Leslie Lamport, published by Addison Wesley (ISBN 0-201-
15790-X). Both of these books were typeset with the system
they describe. The older manual, TeX and Metafont, New
Directions in Typesetting, published by Digital Press and
the AMS, is obsolete.
The source to The TeXbook is available in the
/usr/lib/TeX/TeX3.14/TeXdoc directory as texman.tex. This
material is copyrighted, 1983, by the American Mathematical
Society and is intended to be used only to help you test
your TeX port and to provide examples of how to use TeX.
LaTeX documentation is available in the
/usr/lib/TeX/TeX3.14/LaTeX/LaTeXdoc directory and Metafont
documentation is located in the /usr/lib/TeX/TeX3.14/MFdoc
directory. Other documentation is located throughout the
/usr/lib/TeX subdirectories.
4. Prerequisites
Prerequisites for TeX Version 1.0 are as follows:
4.1 Hardware
o Any Series 4000 computer system.
4.2 Software
o CX/UX release 6.2 or later.
5. Installation
Installation of TeX is done with the setup(1M) program.
Please refer to the CX/UX System Administration Manual,
Chapter 3, for instructions on software installation.
The TeX product must logically reside in the /usr partition
- 2 -
Release Notes 1.0 TeX
and consumes apporoximately 30-50MB of disk space. If there
is not enough space in the /usr partition or if it is
desired to physically install the TeX product in some other
disk partition, then the installer should follow this
procedure:
o cd to the directory chosen for the TeX product to
physically reside.
o Execute the command: mkdir TeX.
o Make a symbolic link to the directory /usr/lib/TeX
by executing the following command: ln -s `pwd`/TeX
/usr/lib/TeX.
o cd to the root(/) directory and install the TeX
product with the setup(1M) program as described
above.
- 3 -
TeX 1.0 Release Notes
Files included with TeX will be loaded into the /usr/lib/TeX
directory. To properly set PATHs in your environment, issue
the command ". /usr/lib/TeX/texinit". texinit is a Bourne
shell script that will set the paths to search for binaries
and fonts; this file can be changed to reflect your system's
configuration.
This software is distributed by Harris in executable format.
However, if for some reason the executables need to be
rebuilt, and you have the source installed on your system,
the instructions for building TeX can be found in the
/usr/lib/TeX/README file.
6. Cautions
None.
7. New Features in this Release
This is the first release of TeX.
8. Changes from Previous Releases
None.
9. Direct Software Support
Software support is available from a central source. When
you need assistance or information about your system, please
contact the Harris Software Support Center at our toll free
number (800-245-6453). Our customers outside the
continental United States can contact us directly at 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
- 4 -
Release Notes 1.0 TeX
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.
- 5 -
CONTENTS
1. Introduction.............................................. 1
2. Copyright................................................. 1
3. Documentation............................................. 1
4. Prerequisites............................................. 2
4.1 Hardware............................................. 2
4.2 Software............................................. 2
5. Installation.............................................. 2
6. Cautions.................................................. 4
7. New Features in this Release.............................. 4
8. Changes from Previous Releases............................ 4
9. Direct Software Support................................... 4
- i -
_________________________________________________________________
HARRIS
COMPUTER SYSTEMS
_________________________________________________________________
TEX
VERSION 1.0
RELEASE NOTES
0890415-1.0
MARCH 1993
_________________________________________________________________
return to index
================================================================================
CX/SX TRUSTED WINDOW MANAGER RELEASE NOTES -
VERSION 1.0
RELEASE NOTES
Harris Computer Systems Division
1. Introduction
The Trusted Window Manager provides a trusted environment
for X Window System applications under CX/SX. Using a
trusted X Window terminal and the Trusted Motif product,
users can enjoy the convenience of the Motif/X Window
environment while retaining all the security functionality
of CX/SX. The features of the trusted window manager
include:
o Motif Graphical User Interface (GUI)
o Designed to a B1 level of trust and compatible with the
B1-evaluated version of CX/SX and LAN/SX
o Mandatory Access Control (MAC) imposed on all window
operations
o Non-removable system-configurable color security label
on each window
o Graphical trusted path mechanism
o Copy and paste between windows is subject to MAC
o Security bar indicates the label and color of the
currently selected window
o User-reducible session clearance
__________
- These release notes cover the following products:
Trusted Window Manager
- 1 -
CX/SX Trusted Window Manager1.0 Release Notes
o Graphic-oriented interface to labeled file operations
2. Documentation
The following documentation is included with this release:
_________________________________________________________
| Manual Name Pub. Number|
|__________________________________________|_____________|
| CX/SX Trusted Window Manager User's Guide| 0890456-000|
| CX/SX Trusted Facility Manual | 0890336-060|
|__________________________________________|_____________|
Additional copies may be ordered by contacting the Harris
Software Support Center. The toll-free number for calls
outside of Florida is 1-800-245-6453. For calls within
Florida or outside the continental United States the number
is 1-305-971-6248.
3. Prerequisites
Prerequisites for CX/SX Trusted Window Manager Version 1.0
are as follows:
3.1 Hardware
o Nighthawk 4000 Series or Nighthawk 5000 Series
o Tektronix 350 series (Harris model VG8246 or VG8248),
including keyboard and at least 8 MB of memory.
3.2 Software
o CX/SX 6.1 (or later) with LAN/SX. CX/SX 6.1 patch
levels required: CX/SX patch cx_sx6.1-014, LAN/SX patch
lan_sx6.1-011, CX/UX patch cx6.1-60. CX/SX 6.2 patches
as appropriate.
o X11R5 with Motif Model Number XG2611 (X Window Release
5.0.1).
- 2 -
Release Notes 1.0 CX/SX Trusted Window Manager
o Tektronix X terminal boot software version 6.3 (or
later)
o Boot monitor software revision 3.12.3 (or later). This
revision number is displayed during the X terminal's
boot process.
4. Installation
Installation of the Trusted Window Manager is done with the
setup(1M) program. Please refer to the CX/UX System
Administration Manual, Chapter 3, for instructions on
software installation using setup(1M).
Installation procedures are outlined in Appendix I of the
CX/SX Trusted Facility Manual (0890336-060).
5. Direct Software Support
Software support is available from a central source. When
you need assistance or information about your system, please
contact the Harris Software Support Center at our toll free
number (800-245-6453). Our customers outside the
continental United States can contact us directly at 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.
- 3 -
CX/SX Trusted Window Manager1.0 Release Notes
- 4 -
CONTENTS
1. Introduction.............................................. 1
2. Documentation............................................. 2
3. Prerequisites............................................. 2
3.1 Hardware............................................. 2
3.2 Software............................................. 2
4. Installation.............................................. 3
5. Direct Software Support................................... 3
- i -
_________________________________________________________________
HARRIS
COMPUTER SYSTEMS
_________________________________________________________________
CX/SX TRUSTED WINDOW MANAGER RELEASE NOTES
VERSION 1.0
RELEASE NOTES
0890456-1.0
JUNE 1994
_________________________________________________________________
return to index
================================================================================
CX/UX VCOM X.25/DDN -
VERSION 1.1
RELEASE NOTES
Harris Computer Systems Division
1. Introduction
The VCOM X.25 software package provides access to the VCOM
X.25 controller having the X.25/LAPB/WAN software resident
on the controller itself.
This release contains the software utilities that allow a CX
system to communicate with another system with X.25 either
directly or through a Public Data Network. The package
provides an interface which allows TCP/IP utility programs
to operate over the X.25 link.
The VCOM X.25 STREAMS driver will provide an interface to
the NLI, LAP-B, and WAN layers via the SBE VCOM-24/34
multi-channel high-speed synchronous communications
controller. A programatic interface for SX/UX is not being
provided.
The driver/controller will support the following standards
and physical interfaces:
o CCITT X.25(80), X.25(84), and X.25(88)
o ISO 8208 support for DTE-DTE operation
o X.25 Level III '80, '84, and '88 Basic and extended
packet sequence numbering.
o X.25 Level II LAPB '80, '84, and '88. Basic and
extended frame sequencing not supported in '80 version.
__________
- These release notes cover the following products: VCOM
X.25 and DDN
- 1 -
CX/UX VCOM X.25/DDN 1.1 Release Notes
o DTE and DCE operation.
o EIA-232-C
o EIA-449
o V.35
2. Documentation
The following documentation is included with this release:
_________________________________________________
| Manual Name Pub. Number|
|__________________________________|_____________|
| CX/UX Networking Reference Manual| 0890118-050|
| CX/UX VCOM X.25 User's Guide | 0890417-000|
| CX/UX VCOM X.25 Release Notes | 0890417-1.1|
|__________________________________|_____________|
Additional copies may be ordered by contacting the Harris
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-305-971-6248.
3. Prerequisites
Prerequisites for CX/UX VCOM X.25/DDN Version 1.1 are as
follows:
3.1 Hardware
o Any Series 4000 or Series 5000 system.
o VCOM X.25 controller and interface specific ports.
- 2 -
Release Notes 1.1 CX/UX VCOM X.25/DDN
3.2 Software
o CX/UX 6.2 Patch level 51 or higher.
o CX/UX STREAMS.
o CX/UX TCP/IP.
4. Installation
Please refer to the CX/UX System Administration Manual,
Chapter 3, for instructions on software installation.
5. Cautions
DDN cannot be run concurrently over two different types of
communications controllers.
The DDN interface is supported only on VCOM boards 0 and 1
(vc0 and vc1).
6. New Features in this Release
This is the initial release of the VCOM X.25 package.
7. Changes from Previous Releases
This is the initial release of the VCOM X.25 package.
8. Direct Software Support
Software support is available from a central source. When
you need assistance or information about your system, please
contact the Harris Software Support Center at our toll free
number (800-245-6453). Our customers outside the
continental United States can contact us directly at 305-
971-6248. The Software Support Center operates Monday
through Friday from 8 a.m. to 7 p.m., Eastern Standard time.
- 3 -
CX/UX VCOM X.25/DDN 1.1 Release Notes
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.
- 4 -
CONTENTS
1. Introduction.............................................. 1
2. Documentation............................................. 2
3. Prerequisites............................................. 2
3.1 Hardware............................................. 2
3.2 Software............................................. 3
4. Installation.............................................. 3
5. Cautions.................................................. 3
6. New Features in this Release.............................. 3
7. Changes from Previous Releases............................ 3
8. Direct Software Support................................... 3
- i -
_________________________________________________________________
HARRIS
COMPUTER SYSTEMS
_________________________________________________________________
CX/UX VCOM X.25/DDN
VERSION 1.1
RELEASE NOTES
0890417-1.1
December 1993
_________________________________________________________________
return to index
================================================================================
VMIC IIOC HOST SOFTWARE SUPPORT PACKAGE -
VERSION 1.1
RELEASE NOTES
Harris Computer Systems Division
1. Introduction
The VMIC IIOC Host Software Support Package consists of the
utilities and libraries necessary to operate the VME
Microsystems International VMIVME-9066 or VMIVME-9064
Intelligent I/O Controllers (IIOC) on Harris Night Hawk
systems. The package is based on the Host Software Support
Package provided by VMIC, modified as necessary to operate
under the CX/UX Operating System.
The 9064 and 9066 IIOC are 68030-microprocessor-based
controllers used to control the various VMIC Analog and
Digital Data Acquisition cards. These cards are VMEbus
based and provide multiple lines for Analog, Digital and
Syncro input and output. Without the IIOC, the host
software would be required to control and monitor the
various VMEbus addresses and control registers associated
with each card. The IIOC offloads this individual card
processing from the host, allowing the user application to
merely read or write a series of data points.
The 9066 IIOC is an embedded controller which resides in the
Night Hawk VMEbus, along with the Analog and Digital cards
it controls. The 9064 on the other hand resides in its own
VMEbus rack independent of the Night Hawk system. It is
connected to the host via the VMIC 5550 Reflective Memory.
The 9064 configuration offloads the Night Hawk VMEbus
backplane and allows for a greater number of Analog and
Digital cards. Both the 9064 and 9066 are addressed through
shared-memory mapping and hence are software compatible.
__________
- These release notes cover the following products:
vmic9066,vmic9064
- 1 -
VMIC IIOC Host Sftw Supt Pkg1.1 Release Notes
This software release contains the utilities described in
the VMIC IIOC documentation along with include files and
libraries needed to access the controller on-line under
CX/UX.
2. Documentation
The following documentation is applicable to this release:
________________________________________________________________
| Manual Name Pub. Number|
|_________________________________________________|_____________|
| IIOC Host Software Support Package Release Notes| 0891049-1.1|
| IIOC Documentation Set (Vendor Manuals) | |
|_________________________________________________|_____________|
The VMIC Documentation Set consists of a variety of vendor-
provided manuals which vary depending upon the hardware
configuration being used. Included in this set should be
the following:
o "VMIVME-9066 Intelligent I/O Controller, Product
Manual". This manual provides an overview of the 9066
hardware installation and configuration.
o "VMIVME-9064 Intelligent I/O Controller, Product
Manual". This manual provides an overview of the 9064
hardware installation and configuration.
o "VMIC IIOC Family Instruction Manual". This document
provides a more detailed explanation of the
communications required with the complete line of VMIC
Intelligent I/O Controllers, including the 9064 and
9066. In addition to detailed operating instructions,
the manual describes the self-test and offline test
procedures available.
o "VMIVME-SW-IIOC1 IIOC Host Software Support Package,
User's Guide". This document describes the software
utilities provided in this package along with calling
sequences for the library routines. This manual should
be consulted regarding the contents of the VMIC
software package provided by Harris. Specific
exceptions and helpful hints are described later in
these Release Notes.
- 2 -
Release Notes 1.1 VMIC IIOC Host Sftw Supt Pkg
o "VMIVME-xxxx, yyyyyyyy Board, Instruction Manual". One
of these manuals is provided for each type of Digital,
Analog or Syncro board provided in the customer
configuration. The 'xxxx' value is the VMIC Model
Number of the board, and 'yyyyyyyy' is the name or
functional description. This manual describes hardware
setup and installation of the board, along with the
electrical and programming characteristics required for
use.
Additional copies of these Release Notes may be ordered by
contacting the Harris 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-305-971-6248. To obtain addition
copies of the VMIC documents, the VME Microsystems toll-free
number is 1-800-322-3616.
3. Prerequisites
Prerequisites for Version 1.1 are as follows:
3.1 Hardware
o Any Series 1000, Series 3000, or Series 4000 system
o VMIVME 9064 or 9066 IIOC (Intelligent I/O Controller)
o VMIVME 5550 Reflective Memory (if using a 9064 system)
o VMIC I/O Cards as required by configuration.
3.2 Software
o CX/UX 6.1.
4. Installation
Please refer to the CX/UX System Administration Manual,
Chapter 3, for instructions on software installation.
After installing the software product, the following steps
should be performed:
- 3 -
VMIC IIOC Host Sftw Supt Pkg1.1 Release Notes
1. Append the lines from the appropriate file in
/usr/src/VMIC/utilities to the end of your
/etc/rc.local file. There are two files in this
directory, one which is used when the VMIC 9066 IIOC or
5550 Reflective Memory is configured on the primary
VMEbus, and a second for use when the VMIC link is
configured on a secondary VMEbus (The secondary VMEbus
is optional hardware available on the Series 3000 and
Model 4800 systems).
2. Shutdown the system and reboot it to utilize the new
rc.local file.
3. Verify board operation by executing some of the VMIC
IIOC utilities such as 'vreset', 'viosiz', and
'vtestd'. These are loaded into the /usr/bin
directory.
5. Cautions
None.
6. New Features in this Release
This is the initial release of the VMIC IIOC Software
Support Package. The VMIC document, "VMIVME-SW-IIOC1 IIOC
Host Software Support Package, User's Guide" provides the
majority of the information required to utilize this
package. Specific items are noted below.
6.1 Board Configuration for 9066 Installations
In 9066 Embedded IIOC configurations, the VMIC I/O cards
exist in the same VMEbus as other Night Hawk controllers.
These cards must be configured in the 'short I/O' address
space of the VME bus. This is also known as 'A16' address
space. The IIOC will scan this VMEbus memory range and
automatically configure the I/O cards it finds.
In order to avoid addressing conflicts with other Night Hawk
controllers, a certain address range has been dedicated for
use by the VMIC cards. This address space corresponds to
Chassis 10, 11, and 12 of the VMIC I/O space.
The VMIC address map is supplied with the IIOC Family
Instruction Manual. Refer to this document for exact VMEbus
- 4 -
Release Notes 1.1 VMIC IIOC Host Sftw Supt Pkg
addresses to be used for each board type. On the Night Hawk
systems, it is necessary to utilize only Chassis 10, 11, and
12 configurations. Note that the VMIC IIOC does not require
consecutive addresses, and therefore it is legal to start at
Chassis 10.
6.2 Using the Library
The 'C'-callable library routines are provided in
/usr/lib/libvmic.a. Thus the '-lvmic' option must appear
when loading a routine which utilizes this library.
Each 'C' program must include the VMIC header files in order
to properly load. This can be accomplished with the single
include statement:
#include
6.3 Using the VMIC utilities
The standard VMIC utility and test programs are provided in
binary (and source -- see below) with the release. The
product installation process will load them into the
/usr/bin directory. In order to use them, be sure that
this directory is in your default PATH. Consult the
appropriate manual described above for usage instructions.
6.4 Rebuilding VMIC modules
Complete source for the VMIC utilities and libraries is
provided with the release. The /usr/src/VMIC/c directory
contains this source and a 'Makefile'. The 'Makefile' can
be used to rebuild the object if necessary. It should then
be moved to the appropriate object directory as described
above.
7. Changes from Previous Releases
None.
- 5 -
VMIC IIOC Host Sftw Supt Pkg1.1 Release Notes
8. Direct Software Support
Software support is available from a central source. When
you need assistance or information about your system, please
contact the Harris Software Support Center at our toll free
number (800-245-6453). Our customers outside the
continental United States can contact us directly at 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.
- 6 -
CONTENTS
1. Introduction.............................................. 1
2. Documentation............................................. 2
3. Prerequisites............................................. 3
3.1 Hardware............................................. 3
3.2 Software............................................. 3
4. Installation.............................................. 3
5. Cautions.................................................. 4
6. New Features in this Release.............................. 4
6.1 Board Configuration for 9066 Installations........... 4
6.2 Using the Library.................................... 5
6.3 Using the VMIC utilities............................. 5
6.4 Rebuilding VMIC modules.............................. 5
7. Changes from Previous Releases............................ 5
8. Direct Software Support................................... 6
- i -
_________________________________________________________________
HARRIS
COMPUTER SYSTEMS
_________________________________________________________________
VMIC IIOC HOST SOFTWARE SUPPORT PACKAGE
VERSION 1.1
RELEASE NOTES
0891049-1.1
September 1992
_________________________________________________________________
return to index
================================================================================
GPX X WINDOW SYSTEM(TM) SERVER -
VERSION 5.0
RELEASE NOTES
Harris Computer Systems Division
1. Introduction
The GPX X Window System(TM) server supports X11 client
applications using the Night Hawk Integrated Graphics
display station. The Integrated Graphics processor (GPX),
video controller and frame buffer comprise a tightly-coupled
component of the Night Hawk architecture, an expansion of
the Integrated SCSI-Ethernet daughter board. The Integrated
Graphics subsystem supports a color graphics display,
keyboard, and mouse. The integrated design ensures higher
throughput than networked graphics display devices can
provide.
The GPX/8 graphics system is an 8-bit pseudo-color device
capable of supporting monitors with up to 1280x1024 pixels
at 72Hz. It is based on the Fujitsu MB86990 Graphics System
Processor, which provides rapid bitblt, line drawing,
polygon filling, and text drawing functions plus clipping,
zooming, plane masking, transparencies, boolean and
arithmetic pixel combinations, hidden pixel removal, and
Gouraud shading - all with only minimal host system
interaction. It provides 4 megabytes of video display
memory and up to four independent display stations on a
single Night Hawk system (one per processor board).
The X11 server, Xgpx, is based on the X11R5 server
implementation from the Massachusetts Institute of
Technology and optimized for use with the Integrated
Graphics hardware. This server provides a full range of X11
features, including the PEX extension, and it is fully
compatible with X11 and OSF/Motif applications.
__________
- These release notes cover the following products: xig
- 1 -
GPX X Window System(TM) Serve5.0 Release Notes
This product includes the X server program, prototype
configuration files, fonts, and online manual entries.
2. X Window System Copyright
Copyright O 1991 by the Massachusetts Institute of
Technology.
Copyright O 1990, 1991, 1992 by Metro Link Inc.
X Window System is a trademark of MIT. See X(1) for a full
statement of rights and permissions.
3. Documentation
The following documentation is included with this release:
________________________________________________________
| Manual Name Pub. Number|
|_________________________________________|_____________|
| GPX X Window System Server Release Notes| 0890407-5.0|
|_________________________________________|_____________|
Additional copies may be ordered by contacting the Harris
Software Support Center. The toll-free number for calls
outside of Florida is 1-800-245-6453. For calls within
Florida or outside the continental United States the number
is 1-305-971-6248.
4. Prerequisites
Prerequisites for GPX X Window System(TM) Server Version 5.0
are as follows:
4.1 Hardware
o Any Series 4000 or Series 5000 Night Hawk system
o Integrated SCSI/Ethernet/Graphics daughtercard
o Monitor, keyboard, mouse, and cables
- 2 -
Release Notes 5.GPX X Window System(TM) Server
4.2 Software
o CX/UX 6.2
o Patch cx6.2-005 is required if the mouse will be
connected on a HPS serial controller
o X Window System Version 11 Release 4 or Release 5
5. Installation
Please refer to the CX/UX System Administration Manual,
Chapter 3, for instructions on software installation.
The following steps may be taken to verify that the Night
Hawk Integrated Graphics hardware is installed correctly.
o Each ISEG daughtercard should be attached to one of the
processor boards.
o The RGB cable from each monitor should be plugged in to
connectors on the system chassis, which in turn are
cabled to the corresponding ISEG daughtercard.
o The RS-232 cable from the keyboard should be attached
to one of the UARTs on the same processor board as the
ISEG daughtercard and monitor cable. The DIP switch on
the ISEG daughtercard must identify which of the two
UARTs on that board is being used for the keyboard:
the position labeled ON indicates that the remote or
higher-numbered port is being used, the other position
indicates that the console or lower-numbered port is
being used.
o The mouse can be connected to any serial port on the
system.
The operating system kernel must also be prepared to
interact with the graphics hardware. Take these steps to
configure a kernel with graphics support.
o Edit the kernel configuration file /etc/master and
specify that the integrated graphics processor devices,
gpxn, are present in your system. Simply uncomment
each line that corresponds to an Integrated Graphics
product installed in your system.
- 3 -
GPX X Window System(TM) Serve5.0 Release Notes
o Rebuild the kernel as described in the CX/UX System
Administration manual.
Additional information is available in the ise(7), gpx(7),
display(7), and keyboard(7) manual entries.
6. Configuring the Server
The following steps should be taken to configure the server
for operation with each of the Night Hawk Integrated
Graphics display stations.
o Edit the configuration files in /usr/lib/X11/gpx to
specify the device files used for the keyboard and
mouse for each display station. A prototype file,
Xconfig, is distributed in that directory but the
actual configuration files must have the display number
appended to the file name, e.g., Xconfig:0. See
Xgpx(1).
o If you wish to use xdm(1) to start X11 sessions, edit
/usr/lib/X11/xdm/Xservers to include the following line
for each display station, where n is the display number
(the same as the processor board number).
:n Local local /usr/bin/X11/Xgpx
o If you wish xdm to be started automatically in multi-
user mode, add the following line to the /etc/inittab
file.
xs:2:once:/usr/bin/X11/xdm
o If the display station is attached on the console port
and you are starting xdm from the /etc/inittab file,
you will need to alter the console entry in the
/etc/inittab file so that it runs the getty(1M) program
only in single user mode, by placing 1 in the second
field (see inittab(4)):
co:1:respawn:/usr/sbin/getty console console
o Be sure that the /etc/inittab file does not have
entries that initiate the getty program on other
Integrated Graphics keyboard ports or mouse ports.
- 4 -
Release Notes 5.GPX X Window System(TM) Server
Additional information is available in the Xgpx(1), xdm(1),
xinit(1), init(1M), and inittab(4) manual entries.
7. Cautions
If an Integrated Graphics display is attached to processor
board 0, you will be unable to use the remote enable
feature.
A common error is trying to start the X server while some
other application (typically getty or a shell) is already
reading from the keyboard port. Be sure to terminate all
other programs running at the keyboard port before starting
the server.
This release does not support backing store. It must be
disabled using the NoBackingStore command in the Xconfig
configuration file.
8. New Features in this Release
None.
9. Changes from Previous Releases
None.
10. Direct Software Support
Software support is available from a central source. When
you need assistance or information about your system, please
contact the Harris Software Support Center at our toll free
number (800-245-6453). Our customers outside the
continental United States can contact us directly at 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
- 5 -
GPX X Window System(TM) Serve5.0 Release Notes
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.
- 6 -
CONTENTS
1. Introduction............................................. 1
2. X Window System Copyright................................ 2
3. Documentation............................................ 2
4. Prerequisites............................................ 2
4.1 Hardware............................................ 2
4.2 Software............................................ 3
5. Installation............................................. 3
6. Configuring the Server................................... 4
7. Cautions................................................. 5
8. New Features in this Release............................. 5
9. Changes from Previous Releases........................... 5
10. Direct Software Support.................................. 5
- i -
_________________________________________________________________
HARRIS
COMPUTER SYSTEMS
_________________________________________________________________
GPX X WINDOW SYSTEM(TM) SERVER
VERSION 5.0
RELEASE NOTES
0890407-5.0
DECEMBER 1992
_________________________________________________________________
return to index
================================================================================
X WINDOW SYSTEM(TM), VERSION 11 -
Release 5.1.1
RELEASE NOTES
Harris Computer Systems Division
1. Introduction
This is Release 5.1.1 of the X Window System, Version 11
(X11). X11 is a network-transparent window system that
allows applications built with the X11 libraries on a Harris
computer to display graphics to devices such as the Harris
GPX/8 8-bit color integrated graphics device, a workstation
running an X11 server, or an X terminal. This product is
based on the X Consortium's X Window System, Version 11
Release 5 core distribution and includes the Xlib library,
the Xt toolkit library, the Athena widget set, the
miscellaneous utilities library, and all core clients and
header files. (The X Window System server software for the
GPX/8 8-bit color integrated graphics device exists as a
separate product.)
Bundled with this release of X11, Harris provides
OSF/Motif(TM), Release 1.2.2. Motif is an industry-standard
graphical user interface that is licensed by the Open
Software Foundation (OSF(TM)), 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. This product consists of libraries,
header files, and several programs including the Motif
window manager (mwm) and uil, which invokes the User
Interface Language (UIL) compiler.
__________
- These release notes cover the following products: X
Window System, Version 11 (X11)
- 1 -
X Window System, Version 115.1.1 Release Notes
2. X Window System Copyright
Copyright O 1991 by the Massachusetts Institute of
Technology.
X Window System is a trademark of MIT. Portions of this
product are copyrighted by the Massachusetts Institute of
Technology; AT&T; UNIX System Laboratories, Inc.; Adam de
Boor; Adobe Systems, Inc.; Apollo Computer, Inc.; Apple
Computer, Inc.; Ardent Computer; Bigelow & Holmes;
Bitstream, Inc.; Cognition Corp.; Daewoo Electronics Co.;
Dale Schumacher; Digital Equipment Corporation; Don Bennett;
Evans & Sutherland Computer Corporation; Franz Inc.; Fuji
Xerox Co., Ltd.; Fujitsu Limited; Hewlett Packard Company;
IBM Corporation; Joseph Friedman; Larry Wall; MIPS Computer
Systems; Marvin Solomon; Matra Datavision, Inc.; Megatek
Corporation; NTT Software Corporation; National Computer
Graphics Association; Network Computing Devices, Inc.; Nihon
Sun Microsystems K.K.; Nippon Telegraph and Telephone
Corporation; O'Reilly and Associates, Inc.; OMRON
Corporation; Oki Technosystems Laboratory, Inc.; Prentice-
Hall; SORD Computer Corp.; SRI; Snitily Graphics Consulting
Services; Solbourne Computer, Inc.; Sony Corporation; Sun
Microsystems, Inc.; Tektronix, Inc.; Texas Instruments
Incorporated; The Open Software Foundation; The Regents of
the University of California; Thomas Roell; Toshiba
Corporation; University of Michigan; University of
Wisconsin; William Kucharski; and Wyse Technology.
3. Documentation
The following documentation is included with this product:
__________________________________________________________
| Manual Name Pub. Number |
|_________________________________________|_______________|
| X Window System Version 11 Release Notes| 0890298-5.1.1|
| X Programming Conventions | 0890299-020 |
| X Window System User's Guide | 0890300-010 |
| OSF/Motif Documentation Set | 0890380-010 |
|_________________________________________|_______________|
Additional copies may be ordered by contacting the Harris
Software Support Center. The toll-free number to call is 1-
800-245-6453. For calls outside the continental United
States the number is 1-305-971-6248.
- 2 -
Release Notes 5.1.1 X Window System, Version 11
On-line manual pages are also provided for both the X Window
System and Motif. The Motif manual pages comprise the
OSF/Motif Programmer's Reference manual. This manual is not
included in the OSF/Motif manual 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. publish a series
of books on the X Window System and Motif, including an
excellent book on Motif programming (Volume 6: Motif
Programming Manual). Official OSF/Motif documentation is
published by Prentice-Hall.
4. Prerequisites
Prerequisites for X11, Release 5.1.1 are as follows:
4.1 Hardware
o Any Series 4000 or Series 5000 system
4.2 Software
o CX/UX 7.1
5. Installation
The X11 installation tape is in cpio format. It contains the
X11 libraries, header files, executables, online
documentation, and man and catman pages. Please refer to
the CX/UX System Administration Manual, Chapter 3, for
general instructions on software installation.
This product must logically reside in the /usr partition.
Because the default partition sizes for CX/UX 7.1 do not
leave enough disk space to physically install X11 on /usr,
you will probably want to install it somewhere else. The
installation script will automatically make symbolic links
from /usr to where X11 is installed.
- 3 -
X Window System, Version 115.1.1 Release Notes
To install X11, follow these steps:
o Sign on as root, or use the "su" program to become
root.
o If you want to physically install X11 under /usr, then
execute "cd /" to position yourself in the root
directory.
If you want to physically install X11 under the
partition named /partition in a directory named X11R5,
then execute the following commands (in the order
specified):
mkdir -p /partition/X11R5/usr
cd /partition/X11R5
o Issue the command "cpio -iBcvdum < /dev/rmt/0mn" to
read in the first two files setup and tape_list with no
rewind. (NOTE: the installation tape is assumed to be
loaded on drive 0.)
o Issue the command "./setup" to run a menu-driven
program that installs the new X11 product.
o The setup program displays a prompt similar to: "Enter
the name of the running kernel or if /unix".
Press the carriage return key. The following message is
displayed: "Non-generic boot. Assuming System
Generation not to be done."
o The next message displayed is: "The first product tape
should be loaded on device /dev/rmt/0mn. Is this the
case? (y|n)". Type "y".
o Expect a pause, then a menu will prompt: "Enter the
numbers of the actions you would like to perform."
Select "Load X11 object files".
o There will be a message similar to: "Loading X11 object
files" as files come onto the system under the
directories usr/bin, usr/include, usr/lib, usr/sde,
usr/man, and usr/catman.
o When the menu returns, select "Exit", and remove the
tape from the drive.
- 4 -
Release Notes 5.1.1 X Window System, Version 11
o Execute "cd ./usr/lib/X11" to position yourself in the
X11 support directory. If you want to see what the
installation script will do, you can execute it with
the -n option, which prints what it would do without
doing anything: "./Install -n". When you are
satisfied, execute without the -n option: "./Install".
o Installation of X11 version 5.1.1 is now complete.
Other installation notes:
The xterm client uses pseudo terminals (ptys) for terminal
emulation. The kernel must be configured for ptys and the
pty devices must be installed in /dev with MAKEDEV. See the
CX/UX System Administration Manual for details.
Refer to the X Window System User's Guide for information
about using the X Window System and the OSF/Motif
Documentation Set for information regarding Motif.
6. Cautions
If a previous version of the X Window System is installed on
the system, then all of the clients, libraries, include
files, and man pages should be removed before installing
this release.
- 5 -
X Window System, Version 115.1.1 Release Notes
7. New Features in this Release and Changes from Previous
Releases
These notes describe the differences between this release
and Release 5 of the Harris X11 product. If you are
upgrading from Release 4 of X11, you may want to refer to
the Release 5 release notes (Pub. Number 890298-5.0) for a
description of the changes made in that release.
This release of X11 supports the ELF binary format and the
dynamic linking (shared library) capabilities of CX/UX 7.1.
This product includes shared ELF versions of the major X11
and Motif libraries, as well as standard (static linking)
ELF and COFF libraries.
The standard X11 and Motif clients are supplied as shared
ELF executables. Consequently, this release requires
considerably less disk space than previous releases.
Other changes:
o The X Window System clients and libraries have been
upgraded with all MIT public patches through patch #25.
The Motif clients and libraries have been patched to
version 1.2.2. These patches fix numerous bugs in the
X11 and Motif distributions.
o The logging function of the xterm client has been
removed. A vulnerability in the logging function
existed which could allow local users to gain root
access. Removing this function closes this security
hole. The vulnerability was reported by the Computer
Emergency Response Team in CERT Advisory CA-93:17
issued November 11, 1993.
o For programs that build using an Imakefile, the default
is now to compile in ANSI-C mode. See the section on
Use below for more detail.
o X11 and Motif man and catman pages are now in
directories separate from the rest of the system man
pages: /usr/man/X11_man and /usr/catman/X11_man. The
xman client recognizes this separation and gives them
their own sections on the Sections menu.
o The xdm client now puts its authorization files in
their own directory: /usr/lib/X11/xdm/auth. This makes
it easier to clean these files up, as they sometimes
- 6 -
Release Notes 5.1.1 X Window System, Version 11
get left around.
o The resize command now prints the window size to
standard output, as it did in Release 4.
o The xbiff client now uses slightly different rules to
determine when it should put the flag up and down. The
new rules should make its behavior more logical.
8. Use
The libraries and include files that comprise 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 appropriate X11 and/or Motif
configuration files.
Makefiles generated in this manner use the ANSI-C compiler
("-Xa" is added to the compilation line). If you do not
want to compile in ANSI-C mode, add the following line to
your Imakefile:
CCOPTIONS =
If you do not have an Imakefile or do not wish to use this
facility, you can set up the linking command manually. To
link X11 applications which use the Athena widget set,
include -lXaw -lXt -lX11 on the compile/link command line.
To link Motif applications, include -lXm -lXt -lX11 -lPW on
the compile/link command line.
This release also contains some unsupported Motif demos in
source form. These can be found under /usr/src/X11/motif-
demos. These applications can be built by entering xmkmf,
then make in the appropriate directory. They can be
installed by entering make install as superuser.
If you are writing X11 programs, do not use the name index
as a variable, struct member, or union member. This can
cause problems, as it is used as a macro in one of the X11
header files.
Refer to the distributed documentation for additional
information on the use of the X Window System and Motif.
- 7 -
X Window System, Version 115.1.1 Release Notes
9. Direct Software Support
Software support is available from a central source. When
you need assistance or information about your system, please
contact the Harris Software Support Center at our toll free
number (800-245-6453). Our customers outside the
continental United States can contact us directly at 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 -
Release Notes 5.1.1 X Window System, Version 11
Trademark Acknowledgements
o OSF, the Open Software Foundation, OSF/Motif and Motif
are trademarks of the Open Software Foundation, Inc.
o X Window System is a trademark of the Massachusetts
Institute of Technology.
- 9 -
CONTENTS
1. Introduction.............................................. 1
2. X Window System Copyright................................. 2
3. Documentation............................................. 2
4. Prerequisites............................................. 3
4.1 Hardware............................................. 3
4.2 Software............................................. 3
5. Installation.............................................. 3
6. Cautions.................................................. 5
7. New Features in this Release and Changes from Previous
Releases.................................................. 6
8. Use....................................................... 7
9. Direct Software Support................................... 8
- i -
_________________________________________________________________
HARRIS
COMPUTER SYSTEMS
_________________________________________________________________
X WINDOW SYSTEM(TM), VERSION 11
RELEASE 5.1.1
RELEASE NOTES
0890298-5.1.1
December 1993
_________________________________________________________________
return to index
================================================================================