Concurrent Computer Corporation
CXUX 6.2 Release Notes

CXUX_6.2 Products are:

630_sx_6.2 emacs_6.2 hf77_6.2 streams_6.2
ada_88k_6.2 floppy_6.2 hsd_6.2 svvs_tests_6.2
axi_88k_6.2 gdb_6.2 int_network_6.2 tcp_ip_6.2
cnd_6.2 gmake_6.2 ksh_6.2 vdisk_6.2
cx_6.2 gpib_6.2 lan_sx_6.2 vsx_tests_6.2
cx_rt_6.2 gs_6.2 nfs_6.2 x25_6.2
cx_sx_6.2 hc_6.2 rje_6.2
dr11w_6.2 hed_6.2 snmp_agent_6.2

================================================================================

630/SX SECURE WINDOWS -
VERSION 6.2
RELEASE NOTES

Harris Computer Systems Division

1. Introduction

630/SX Secure Windows adds support for the 630 Multi-Tasking
Graphics (MTG) intelligent terminal. Major features
include:

o Trusted Communication with Host

o Trusted Window Management

o Multilevel Windows with Security Labels

o MAC for Cut and Paste Operations between Windows

o Terminal Object Reuse Enforced for Login and Logout

2. Documentation

The following documentation is included with this release:

_______________________________________________________
| Manual Name Pub. Number|
|________________________________________|_____________|
| CX/SX User's Guide and Reference Manual| 0890335-030|
| CX/SX Trusted Facility Manual | 0890336-030|
| 630/SX Secure Windows Release Notes | 0890354-6.2|
|________________________________________|_____________|
|________________________________________|_____________|

__________

- These release notes cover the following products:
630_sx

- 1 -

630/SX Secure Windows 6.2 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 630/SX Secure Windows Version 6.2 are as
follows: | |
| | |
| | |
3.1 Hardware | |
| | |
| o Any Series 4000 or 5000 system. | |
| | |
| o A 630 MTG terminal. | |
| | |
Refer to the CX/UX 6.2 Release Notes for information on the
minimum hardware revision levels required for installation
of this software release. | |
| | |
3.2 Software | |
| | |
| o CX/UX 6.2 | |
| | |
| o CX/SX 6.2 | |
| | |
| | |
|
4. Installation

Please refer to Appendix E of the CX/SX Trusted Facility
Manual, section E.3, for instructions on software
installation.

- 2 -

Release Notes 6.2 630/SX Secure Windows

5. Cautions

It may be necessary to increase the kernel configuration
parameter maxproc when using 630/SX secure windows. This
configuration parameter specifies the maximum number of
processes that a user may have at any given time. When
running a windowing terminal, a user may exceed the default
value of 25 processes per user. Consult the CX/UX System
Administration Manual for more details on kernel
configuration.

The 630 MTG terminal must have a minimum of 1 Megabyte of
memory installed for 630/SX to function properly.

This software does not currently support the 730 MTG or the
730X terminals.

6. New Features in this Release

None.

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.

- 3 -

630/SX Secure Windows 6.2 Release Notes

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. Direct Software Support................................... 3

- i -

_________________________________________________________________

HARRIS
COMPUTER SYSTEMS
_________________________________________________________________

630/SX SECURE WINDOWS
VERSION 6.2

RELEASE NOTES

0890354-6.2

October 1992

_________________________________________________________________

return to index
================================================================================

CX/UX HAPSEO -
VERSION 6.2
RELEASE NOTES

Harris Computer Systems Division

1. Introduction

The Harris Ada Programming Support Environment (HAPSE) is a
tool set for the development of Ada programs on Harris
computers under the CX/UX, CX/RT, and CX/SX environments.
This release has been validated under version 1.11 of the
Ada Compiler Validation Capability (ACVC) suite. HAPSE
version 6.2 (v6.2) applies to both Harris Series-4000 and
Harris Series-5000 systems. HAPSE v6.2 contains two
distinct Ada run-time environments: the Basic Ada Run-time
and the Ada Real-time Multiprocessor System (ARMS) (TM).

HAPSE v6.2 contains not only a complete release of the HAPSE
product, but also a skeleton HAPSE environment that makes it
possible for more than one version (installation) of HAPSE
to be configured on your system at a given time. Details of
this multiple HAPSE capability are outlined in Chapter 2 of
the CX/UX HAPSE Reference Manual.

In addition, HAPSE v6.2 includes CX/UX HAPSE POSIX 1003.5, 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. It 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, located under
hapse_location/bindings/posix_1003.5.

__________

- These release notes cover the following products:
ada_88k

- 1 -

CX/UX HAPSE 6.2 Release Notes

Optional Harris Ada products that are not bundled with the
HAPSE product are available as stand-alone products that
must be obtained separately. For more information about
optional Ada products and support tools, contact the Harris
Software Support Center at the number listed in the next
section.

Optional products that complement HAPSE include the
following:

o Harris AXI (an Ada X Window Systems (TM) Interface to
Xlib, Xt, and Motif (TM))

o Harris ID Tools (Ada and C cross-referencing tools)

o Harris NightTrace (TM) (a graphical real-time trace and
analysis tool)

2. Trademark Acknowledgements

ARMS is a trademark of Harris Corporation.
HAPSE is a registered trademark of Harris Corporation.
Motif is a trademark of the Open Software Foundation.
NightTrace is a trademark of Harris Corporation.
X Window System is a trademark of the Massachusetts Institute of Technology.

3. Documentation

The following documentation is included with this release:

__________________________________________________________
| Manual Name Pub. Number|
|___________________________________________|_____________|
| CX/UX HAPSE Reference Manual | 0890288-050|
| CX/UX HAPSE 6.2 Release Notes | 0890288-6.2|
| CX/UX HAPSE POSIX 1003.5 Conformance Guide| 0890404-010|
| HAPSE a.db Debugging Manual | 0890450-000|
|___________________________________________|_____________|

Additional copies 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.

- 2 -

Release Notes 6.2 CX/UX HAPSE

The CX/UX HAPSE POSIX 1003.5 Conformance Guide describes in
detail the compliance of the implementation with the
standard. Specification of the actual POSIX 1003.5 standard
is available directly from IEEE, the Institute of Electrical
and Electronic Engineers (1-800-678-IEEE).

4. Prerequisites

Prerequisites for CX/UX HAPSE Version 6.2 are as follows:

- 3 -

CX/UX HAPSE 6.2 Release Notes

4.1 Hardware

o Any Harris Series-4000 or Series-5000 system

o 32MB physical memory (minimum configuration)

o Total of 8MB physical memory per HAPSE user (minimum
configuration)

4.2 Software

o CX/UX 6.2 (CX/RT 6.2 or CX/SX 6.2 are acceptable)

5. Cautions

o The compiled form of HAPSE v5.2 and HAPSE v6.2 Ada
libraries are incompatible. Therefore, all Ada source
code contained in user HAPSE libraries must be
recompiled after the installation of HAPSE v6.2 (except
for libraries that continue to use HAPSE v5.2 as their
HAPSE version of choice). The HAPSE tool, a.cleanlib,
should be used to clean out user HAPSE libraries before
recompilation begins.

o Harris-defined defaults for all system-wide
configurable HAPSE parameters are in effect when v6.2
is installed. If non-default parameters were utilized
prior to the installation of this release, please make
the necessary adjustments to the configurable
parameters to obtain the desired limits using the HAPSE
tool a.config.

6. Installation

Installation instructions are contained solely within
Chapter 2 of the CX/UX HAPSE Reference Manual and are not
included in these release notes. Please consult the manual
for configuration options and specific installation
procedures to use with the multiple HAPSE capability.

- 4 -

Release Notes 6.2 CX/UX HAPSE

7. Fixes in this Release

o All fixes and enhancements from HAPSE v5.2 patches.

- A patched assembler has been provided which does
not corrupt object files produced from large Ada
source files.

- In the Basic Ada run-time model, the a.db tool no
longer disables breakpoints between one execution
of a program and the next in the same session.

- a.ld now correctly links programs that use the AXI
(X Window System) bindings.

- The performance of a.ld was significantly
improved.

- a.slinker now removes dead routines which were
previously considered as "live" only because they
had explicit exception handlers.

- a.slinker now removes dead routines from programs
which utilize C object that was compiled for the
88110 architecture (Series 5000).

- The code generator now correctly sizes
uninitialized package allocation bases that are
marked with pragma MEMORY_POOL (data, pkg, ...);
this corrects the bus error or segmentation fault
sometimes seen during program startup.

- The run-time startup code now migrates to the
correct CPU board before creating the physical
local memory pool as specified by the user via
pragma MEMORY_POOL (data, pkg, local, ...).

- The a.make tool now correctly compiles source
files after failed compilations of subunits when
their source files contain other, unrelated units,
and when the error is actually in a parent unit.

- The a.make tool was not prepared for the
circumstance that the same PID may be reused at
different times in extremely long compilations.
It now correctly handles this situation.

- The implementation of a.make's -All option has
been corrected to compile source files of out-of-

- 5 -

CX/UX HAPSE 6.2 Release Notes

date units in other libraries in those other
libraries.

- A new option, a.make -import, compiles all out-
of-date units into the current library or library
specified by -lib.

- The a.make tool now correctly handles the case
where large numbers of error messages occur in its
dependency-analysis phase.

- The performance of a.make was significantly
improved.

- a.monitor's permissions were corrected and
fast_interrupt_task tasks are now displayed even
in the absence of "ghost" mode.

- The a.rm tool has been extensively modified and
will no longer corrupt ada.lib files.

- The a.rm utility now accepts a new option, -U. It
permits a user to place units in the UNCOMPILED
state, instead of physically removing them. The
use of this option works correctly with the a.make
utility, whereas the physical removal of units
without the -U option can confuse it.

- The requirement for the Data_Rec_Array_Index_Limit
to be greater than 1 in order to data record or
monitor complex array components was lifted for
the tool a.rtm and the real_time_data_monitoring
package. This tool and package now are able to do
lookups on arbitrarily complex array components as
long as Data_Array_Index is 1 (or greater.)
Please note that the system utility rtutil(1) was
not modified and its requirements have not
changed.

- A bug in the internal symbol table management for
a.rtm and the real_time_data_monitoring package
was corrected such that simple name collisions are
handled correctly; two variables in different
packages that have the same simple name can now be
monitored.

- The a.target tool no longer fails when executed.

- 6 -

Release Notes 6.2 CX/UX HAPSE

- Automatic packing of arrays will not pack an array
such that the elements will be smaller than
specified by the user in a 'size representation
clause on the element type. Explicit packing with
pragma PACK, of course, can still force complete
packing.

- Packed-record assignment involving bit extraction
now works correctly.

- The -dr option no longer causes the compiler to
abort with a signal 11.

- Compilation involving nested records where the
outer record is declared private no longer cause
internal assertion errors.

- Compilations of units containing fixed-point types
with dynamic bounds used as the elements of packed
types now compile without internal errors.

- Multiple executions of the fe.88k processor no
longer deadlock.

- The fe.88k processor has been modified to store
correct source file names where there was a
previous compilation of a foreign source file
which contained generic instantiations. (A
foreign source file is a source file that exists
in a library other than the library in which it is
compiled; compiling with the -lib option allows
this.)

- The compilation speed of very large array
aggregates specified with positional notation has
been considerably improved. As an additional
consequence of this, the "TN count exceeded" error
does not occur in relation to them.

- The compilation of non-local source files
containing separate subunits of separate subunits
no longer produces linker errors.

- Bit moves involving objects overlaid with a "for x
use y.z'address" clause, where the base address of
the two objects was not identical, now works
correctly.

- 7 -

CX/UX HAPSE 6.2 Release Notes

- The front end of the compiler was corrected to
elaborate task interrupt entry addresses in the
presence of high levels of optimization.

- The abortion of tasks in select statements with
"terminate" alternatives under the ARMS model no
longer causes the task master to terminate
prematurely.

- On Series 5000 systems, the non-volatile x
registers are saved in all appropriate cases.

- Text_io.new_page raises STATUS_ERROR if the file
is null.

- The standard library contains a new package called
address_clauses. The package contains the
elaboration code for address clauses. If users
wish to modify this code, they can simply make a
copy of the file locally, change the code and add
a with clause on their copy of the address_clauses
package to one of the units in their program.

- A new package, task_synchronization, which
provides the equivalent of a counting semaphore,
was added to the arms HAPSE library. This
provides an extremely efficient real-time
mechanism for synchronizing "n" ARMS tasks.

- Ada tasking programs that use the AXI bindings no
longer experience STORAGE_ERRORS while in the
Xt.AppMainLoop routine.

o Additional Fixes in this Release:

- Generic instantiations now compile correctly in
child libraries, even when the same units exist in
parent libraries, thus eliminating link errors.

- Recompilation of units, when those same units
exist in other libraries on the ADAPATH now work
correctly.

- a.make -p recovers gracefully from failed fork()
calls and when it exhausts both pipes and file
descriptors. It continues after reducing the
degree of parallelism.

- 8 -

Release Notes 6.2 CX/UX HAPSE

- a.rm -U was corrected to remove .objects files.

8. Features in this Release

o Compliance with ACVC validation suite version 1.11.

o Full support of Ada R.M. Chapter 13.

o Compliance with IEEE-Std-1003.5-1992. The CX/UX HAPSE
POSIX 1003.5 implementation is fully compliant when the
Basic Ada Run-time 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 Run-time is selected at link time (-arms
option to the HAPSE tool a.ld). See the CX/UX HAPSE
POSIX 1003.5 Conformance Guide for more details.

o All enhancements from v5.2 patches, including:

- A new option, a.rm -U, places a unit in an
UNCOMPILED state.

- A new option, a.make -import, compiles all out-
of-date units into the current library or library
specified by -lib.

- 9 -

CX/UX HAPSE 6.2 Release Notes

o New Development in this Release:

- ARMS Enhancements:

* Pragma MEMORY_POOL. The implementation
requires less physical memory and less CPU
time during elaboration. The memory pool
configuration can be stored in a dynamic
MAP_FILE, which may be altered without
relinking the program. Use the new a.ld -mp
option for this.

* Pragma PASSIVE_TASK enhancements include the
addition of GENERAL passive tasks, which have
fewer restrictions on the form of a task
body, and IPL_SERVER passive tasks (system
Interrupt Priority Level control for use with
FAST_INTERRUPT_TASKs).

* Pragma FAST_INTERRUPT_TASK enhancements
include support for the IPL_SERVER passive
task mechanism. Also, conditional entry
calls to passive and non-passive tasks are
now allowed.

- Optimizations and Program Size:

* Enhanced instruction scheduling.

* Reduced compilation size and time for large
programs.

* More opportunities for a.analyze88
optimizations.

* General code quality improvements.

* Internal symbol name-space changes
significantly reduce the size of linked
programs.

- Tools:

* Automatic translation of raw symbol names to
Ada expanded names is output from the tools
a.analyze88 and a.report88. Use the new
option -Zraw_names, to preserve the raw form.
Other new options include -hapse, -lib, and
-V (very verbose). See the help screens or

- 10 -

Release Notes 6.2 CX/UX HAPSE

man pages for a list of all options.

* a.demangle is a new tool which filters names
into a human-readable form.

* The new a.ld -mp option creates a memory-pool
map file that describes the layout of memory
pools defined by the user via pragma
MEMORY_POOL, as well as default heap and
stack sizes. At post-link time, the user may
modify entries in this file, which affect
physical location, cache mode, and size. The
values are read at program startup and used
during program execution by the ARMS
executive. No relinking is needed.

* Enhancements were made to a.make -Z (zoom),
which ignores non-local libraries to reduce
recompilation time.

* The a.make tool was enhanced to handle this
situation: a.make is given a target in a
library that has no such object available,
yet a source file exists with the name
{object}.a or {object}.pp. Instead of
getting a fatal error, a.make finds
dependents of that source file and attempts
to compile the target again, in case {object}
is in that source file.

* Enhancements to a.monitor include
initialization-time performance improvements
and an automatic rescan if a program is not
currently running.

* Enhancements to a.rtm include the ability to
define a display format for a particular item
(e.g., base, fore, aft, exp), the ability to
define a default display format for discrete
types and real types (e.g., base, fore, aft,
exp), a fast modify mode from the command
window, and improved handling of long
expanded names in the display.

- Ada Debugger (a.db) Enhancements and Features:

* a.db displays array slices.

- 11 -

CX/UX HAPSE 6.2 Release Notes

- The following HAPSE-supplied library packages were
added or modified:

* Package: interrupt_entry, arms. File:
interrupt_entry.a. Description: New
subprogram specifications were added to allow
for blocking and unblocking of interrupts
using real-time-clock and eti IDs from the
rtc_control and eti_control packages.

* Package: task_synchronization, arms. File:
task_synchronization.a,
task_synchronization_b.a. Description: New
package added for low-overhead, real-time
synchronization of "n" tasks.

* Packages: real_time_data_monitoring, usermap,
dr_interface, harrislib. Files: rtm.a,
rtm_b.a, rtm_image.a, rtm_value.a, usermap.a,
usermap_b.a, dr_interface.a,
dr_interface_b.a. Description: Real-time
debug enhancements were added which
significantly improve the package. Changes
include support for intermixed use of
multiple programs, a generic read/write
subpackage, enhanced list and search
capabilities, and a more generalized
interface. The old interfaces are still
provided for compatibility, but will be
removed in the next release. Please see the
specification of real_time_data_monitoring in
harrislib for more information.

* Package: generic_math, harrislib. File:
generic_math.a. Description: Remove abs
function, use standard.abs instead.

* Package: interval_timer, harrislib. File:
interval_timer.a. Description: Function "+"
returns the result, not "l".

* Package: math, harrislib. File: math_b.a.
Description: Replace /lib/libM.a with the
new -alM link option.

- 12 -

Release Notes 6.2 CX/UX HAPSE

* Package: rt_interface, harrislib. Files:
rt_interface.a, rt_interface_b.a.
Description: Change slot parameter to OUT
for sched_pgm_add.

* Package: address_clauses, standard. File:
address_clauses.a. Description: New package
added with elaboration code for address
clauses.

* Package: a_strings, standard. File:
a_strings_b.a. Description: Added check for
null string to function to_c.

* Package: machine_code, standard. File:
machine_code.a. Description: Added support
for Series-5000 (MC88110) to the package.

* Package: unix_prcs, standard. File:
unix_prcs_b.a. Description: Deleted function
cx_system which interfaced to CX/UX system.

- Optional Products:

* Ada bindings to the X Window System
(including Xlib, Xt, and Motif) may be
purchased for any system running this release
of HAPSE.

* Harris ID tools may be used for performing
cross-referencing over Ada source files.

9. Changes From Previous Releases

o The dr_interface package no longer operates on FORTRAN
data.

o The dr_interface package will not be released with the
next version of HAPSE. Please use the
real_time_data_monitoring package instead.

o The structure of the internal representation of
previously compiled information (DIANA) has changed in
this release. Therefore, libraries previously compiled
with different versions of HAPSE must be cleaned and/or
removed if this version of HAPSE is to be used in such
libraries.

- 13 -

CX/UX HAPSE 6.2 Release Notes

o The run-time library names in the lib directory
changed. For example, the Basic runtime is now called
libbart.a, rather than lib88k.rts.a, and the ARMS
runtime is called libarms.a, rather than libarms.rts.a.
This should be transparent to the user.

10. Known Problems with HAPSE v6.2

Problems with HAPSE version 6.2 will be individually
resolved in patches to v6.2, or in subsequent releases.

11. Direct Software Support

To obtain copies of SAR forms, call the Software Support
Center and request form number CSD1833B.

- 14 -

CONTENTS

1. Introduction............................................ 1

2. Trademark Acknowledgements.............................. 2

3. Documentation........................................... 2

4. Prerequisites........................................... 3
4.1 Hardware........................................... 4
4.2 Software........................................... 4

5. Cautions................................................ 4

6. Installation............................................ 4

7. Fixes in this Release................................... 5

8. Features in this Release................................ 9

9. Changes From Previous Releases.......................... 13

10. Known Problems with HAPSE v6.2.......................... 14

11. Direct Software Support................................. 14

- i -

_________________________________________________________________

HARRIS
COMPUTER SYSTEMS
_________________________________________________________________

CX/UX HAPSEO
VERSION 6.2

RELEASE NOTES

0890288-6.2

December 1993

_________________________________________________________________

return to index
================================================================================

CX/UX AXI -
VERSION 6.2
RELEASE NOTES

Harris Computer Systems Division

1. Introduction

The Ada X Interface (AXI)1 is an abstract Ada binding to the
X2 Library (Xlib), the X Toolkit (Xt) and Motif3 (Xm).
Using this interface, applications written in Ada may take
full advantage of the X library, the X Toolkit, and Motif.

Installation of this software assumes that the actual C
libraries to which the AXI product "binds" is present on the
system. This product also assumes that the Harris Ada
Programming Support Environment (HAPSE)4 is installed. The
specifics of these requirements are outlined later in this
document.

The documentation contained with this product assumes that
users are familiar with X and programming with X. It also
assumes a working knowledge of the Ada language and the
HAPSE environment. The documentation provided with the AXI
product does not substitute documentation about X, Motif,
HAPSE, or the Ada language.

__________

- These release notes cover the following products:
axi_88k

1. AXI is a trademark of Advanced Technology Center.

2. X is a registered trademark of the Massachusetts
Institute of Technology.

3. Motif is a trademark of the Open Software Foundation,
Inc.

4. HAPSE is a registered trademark of Harris Computer
Systems Division.

- 1 -

CX/UX AXI 6.2 Release Notes

The AXI documentation contains the specifications that
comprise the Ada X Interface. No Ada source modules for the
package bodies that make up the AXI interface are shipped
with the AXI product; however, source for the package
specifications are available. These source files may be
useful as a point of reference in addition to the AXI
manual.

- 2 -

Release Notes 6.2 CX/UX AXI

2. Documentation

The following documentation is included with this release:

_____________________________________
| Manual Name Pub. Number|
|______________________|_____________|
| AXI Reference Manual | 0890418-000|
| AXI 6.2 Release Notes| 0890418-6.2|
|______________________|_____________|

3. Prerequisites

Prerequisites for CX/UX AXI Version 6.2 are as follows:

3.1 Hardware

o Any Harris Series-4000 or Series-5000 system

o 32MB physical memory (minimum configuration)

o Total of 8MB physical memory per AXI user

o An X Terminal

3.2 Software

o CX/UX 6.2 or CX/RT 6.2.

o HAPSE version 6.2 installed.

o X Window System Version 11, Release 5 (X11R5).

- 3 -

CX/UX AXI 6.2 Release Notes

4. Cautions

AXI version 6.2 supports only systems that are running X11R5
and HAPSE v6.2. Any system running CX/UX 6.2 or higher
should be running X11R5; however, it may be possible that a
system running CX/UX 6.2 is only running X11R4. In order to
use the AXI bindings, X11R5 must be installed.

In order to figure out which version of the X Window System
your system is running, use the xdpyinfo(1) command.

No Ada package body source files are shipped with the AXI
product; therefore, it is not possible to debug Ada programs
through X library calls at the source level. The a.db
debugger may still be used to debug Ada programs; however,
stepping into any calls within the AXI bindings may be
debugged only at the assembly level.

The 6.2 release of AXI is identical to the 3.0.1 release of
AXI, but is compiled for use with HAPSE v6.2.

5. Installation

The installation tape is in cpio format. It contains the
source for all AXI package specifications as well as the
pre-compiled versions of the package specifications and
bodies.

To install CX/UX AXI, follow these steps:

o Sign on as root, or use the "su" program to become
root.

o CX/UX AXI 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 under
"usr/hapse_88k_6.2/bindings", and because the HAPSE
product is usually read from tape at the root
directory.

o IT IS REQUIRED THAT AXI BE INSTALLED FROM THE SAME
LOCATION AS THE HAPSE PRODUCT!. If the hapse_88k6.2
product was read from some location other than the root
directory, then the AXI product must also be read in
from that same location.

- 4 -

Release Notes 6.2 CX/UX AXI

o Execute "cd /" to position yourself under the root
directory.

o Mount the CX/UX AXI 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 AXI 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_6.2/bindings.

o When the menu returns, select "Exit", and remove the
tape from the drive.

o Installation is now complete.

6. Using the AXI Bindings

Once installed, the AXI bindings may be used in Ada
applications. This section describes the steps required in
order to compile, link, execute, and debug programs that use
the AXI bindings.

- 5 -

CX/UX AXI 6.2 Release Notes

6.1 Compilation

In order to compile applications that reference any part of
the AXI bindings (e.g., Xlib, Xt, Motif), a user must first
include the appropriate library pathname(s) on the ADAPATH
search list in the HAPSE library where the application is to
be compiled.

Assuming that the HAPSE installation we are using is
installed in what we will refer to as $hapse_location, then
it is necessary to include either one or both of the
following HAPSE libraries on the ADAPATH:

$hapse_location/bindings/xlibxt
$hapse_location/bindings/motif

The first is necessary for all programs that use the Xlib
and/or Xt interfaces. If these are used exclusively, then
this is the only additional library required on a HAPSE
library's ADAPATH. If Motif is also to be used, then both
libraries shown above must be included on the library path.

The HAPSE library tool a.path recognizes the AXI library
directory names as keywords (regardless of the value of
$hapse_location); therefore, it is possible to configure a
HAPSE library to reference the Xlib and Xt interface by
typing the following command:

a.path -A xlibxt

If Motif will be used, then the additional command should
also be issued:

a.path -A motif

Note that for applications that utilize the Motif interface,
both supplied libraries must be included on the ADAPATH in
the library where compilations will be performed. The
Motif-specific library path is not sufficient for Ada Motif
applications as the Motif interface depends upon both Xlib
and Xt, making the presence of both supplied-libraries
necessary.

Aside from including the appropriate library(ies) on the
ADAPATH, nothing special needs to be done in order to
compile applications that use the AXI interface. A user can
compile source code that contains AXI calls in the same

- 6 -

Release Notes 6.2 CX/UX AXI

manner as he would any other Ada source file by invoking the
HAPSE compiler, ada. For example:

ada helloworld.a

compiles the Ada source file helloworld.a which contains a
simple Motif "helloworld" program that utilizes the AXI
bindings. The source for this program is provided in these
release notes.

6.2 Linking

Linking AXI programs does not require any special steps
other than the presence of the appropriate AXI library(ies)
on the ADAPATH of the target HAPSE library. The AXI
interface internally links in the C libraries required
(e.g., libX11.a, libXt.a, libXm.a) when applications use any
AXI-specific features that would require these C libraries
to be linked. In order to link any AXI program, a user must
only invoke the a.ld prelinker as he would any Ada program.
For example, to link the program helloworld, simply issue
the command:

a.ld helloworld

Note that the AXI interface only supports X11R5 versions of
the C libraries and that AXI programs will not link unless
the R5 versions are installed on your system. If R4
versions are installed, attempts to link AXI applications
will most likely result in errors due to undefined
externals.

6.3 Executing

Executing a program that utilizes the AXI interface only
requires that the user will be running the program on an X
terminal with an appropriate DISPLAY variable setting.

6.4 Debugging

Ada programs that use the AXI interface may be debugged
using the a.db debugger just like any other Ada program.
However, since no source is supplied for the bodies of the
packages that make up the AXI interface, debugging through
any AXI functions and procedures may be done only at the
assembly level. Because most AXI calls access C libraries,

- 7 -

CX/UX AXI 6.2 Release Notes

these would have to be debugged at the assembly level
anyway.

The a.db debugger traps most CX/UX signals by default,
stopping the program being debugged in the process. Because
X programs rely heavily on the use of SIGIO, the debugger
does not stop (by default) when the application being
debugged encounters SIGIO. This default behavior may be
modified using the a.db command handle. All other CX/UX
signals are trapped and handled by the debugger as
documented in the CX/UX HAPSE Reference Manual.

7. Programming Hints

7.1 Setting and Getting Widget Resources

The X Toolkit and Motif widget-creation convenience
functions expect users to identify widget resources in a
static array. This array is passed as an argument to the
convenience function along with an argument specifying the
number of resources in the list.

For example, the often-used Xt function
CreateManagedWidget() accepts as its arguments, the name of
the widget to create, the class of the widget, the widget's
parent, and, as its last two arguments, the function accepts
an array of resource pairs and an integer specifying the
number of resource pairs in the array.

When using the AXI bindings, Motif and Xt resources may
easily be constructed by creating argument lists using the
SetArg procedure that is defined in the Xt package. An
argument list that is created using this technique may then
be passed onto the Ada version of the convenience function
along with the number of resources defined in the list.

The following Ada code fragments demonstrate how a user may
specify a horizontal orientation when creating a simple
Motif RowColumn widget. The user first creates an argument
list of widget resources. Then the user passes this list as
an argument to the CreateManagedWidget function found in the
Xt package. In this example, only one resource pair is
specified in the list (to specify the orientation of the
widget):

with Xt;

- 8 -

Release Notes 6.2 CX/UX AXI

with Xm;
with Xmdef;

...

arglist : Xt.arglist(1..1);
rowcol_w, toplevel : Xt.Widget;

...

Xt.SetArg (arglist(1), Xmdef.Norientation, Xt.Argval(Xm.HORIZONTAL));
rowcol_w := Xt.CreateManagedWidget("Row", Xm.RowColumnWidgetClass,
toplevel, arglist, 1);
...

A few things are important to note regarding resource lists:

o The resource list is of the AXI-defined type Xt.arglist
and is an array type. The SetArg procedure may be
called repetitively to set as many resource pairs in
the argument list array as necessary.

o The Motif resource names are defined in the Xmdef
package and parallel the names of the resources as they
appear in the C language header files with a similar
notation. (In this case Norientation appears as it
would in C without the "Xt" or "Xm" prefix that the C
language uses. For Ada, these resource names MUST BE
prefixed by "Xmdef.", UNLESS a "use" clause is given
for this package, as all resource names are defined in
the Xmdef package).

o Constants for resource values are defined within either
the Xt or Xm packages, depending upon whether the value
is an X Toolkit or Motif resource value. The names for
these constants also mimic the C language definitions
in the C header files (Xm.HORIZONTAL in this case
parallels the C value XmHORIZONTAL).

o Resource values may either be simple integer values or
must be converted to the AXI-defined type Xt.Argval as
shown in the example above. The SetArg procedure is
overloaded to accept either type as a resource value.

- 9 -

CX/UX AXI 6.2 Release Notes

7.2 Callbacks

Callback routines are an integral part of X Toolkit
programming. To register a callback routine in an Ada
program using Xt or Motif is quite similar to the C
language; however, certain programming techniques should be
used when programming Ada callbacks in order to minimize
errors.

A callback may be registered in Ada by using the AddCallback
procedure found in the Xt package. Its arguments are
similar to the C function XtAddCallback(). What users
should be most aware of when programming Ada callbacks is
that all callback routines must be defined in library-level
packages. Because the Harris C compiler and the HAPSE Ada
compiler use similar calling conventions, nothing further
needs to be done in order to register an Ada callback
routine with the Xt toolkit. The requirement that Ada
callbacks be defined at the library level eliminates
confusion introduced by uplevel references.

An example of an Ada callback routine and a code fragment
demonstrating how to register the callback are shown below:

--
-- A simple Ada callback routine in a library-level package body.
--

with text_io;
package body callback is
--
procedure call_me (w : in Xt.Widget;
client_data : in Xt.Pointer;
call_data : in Xt.Pointer) is
begin
text_io.put_line ("Callback was called");
end call_me;
--
end callback;

--
-- This callback can then be registered with the X Toolkit
-- for an AXI application where "some_widget" is defined.
--

with callback;
procedure test is
--

- 10 -

Release Notes 6.2 CX/UX AXI

...

Xt.AddCallback(some_widget, Xtdef.NactivateCallback,
callback.call_me'address, Xt.XtNULL);
...

--
end test;

Full debugging of Ada callbacks is supported when using the
a.db symbolic debugger; however, traversing the call stack
backwards from a callback routine into C code found within
the Xt library can be debugged only at the assembly level
from within the debugger.

7.3 Ada Tasking in AXI Applications

The AXI bindings support Ada tasking features that make it
easy to integrate X programming with applications that
utilize Ada tasking constructs. Normally, any Ada task (in
the Basic Ada Runtime System) that blocks to wait for input
will block all other tasks, including those which are
runable. AXI contains an internal tasking implementation
whereby all X calls that block to wait for input will block
through an internal event handler mechanism (implemented
using Ada tasking). This mechanism allows all other tasks
in the application to proceed normally without blocking when
another task is blocked in an X call.

Without this internal mechanism, all tasks in a given
application would not be able to execute, even if runable,
when any other task is blocked in an X call. The task that
makes the X call would be blocked in a CX/UX system call
(waiting for input), prohibiting all other tasks from
executing until the blocked task has exited the system call.
This kind of behavior is evident in some Ada/X binding
implementations available from other vendors. The AXI
implementation eliminates this problem for programs linked
with the Basic Ada Runtime.

In ARMS applications, Ada tasks are mapped to CX/UX
processes. This implementation does not introduce the
problems outlined above that exist in the Basic Ada Runtime.
It is important to note; however, that only one ARMS task in
a given application can operate on an open connection to the
server. That is, it is not possible to establish a
connection to the server from one ARMS task and attempt to

- 11 -

CX/UX AXI 6.2 Release Notes

make X calls on the same connection from another ARMS task.
Because ARMS tasks are implemented as CX/UX processes, only
one ARMS task in an application may perform X calls, because
within the X toolkit, only one connection to the server per
process is allowed.

7.4 Optimizations

The HAPSE compiler supports three levels of optimization.
The details of these levels of optimization are outlined in
the CX/UX HAPSE Reference Manual. Ada programs that use the
AXI interface may be fully optimized.

Additionally, link-time optimizations may be performed to
enhance execution speed and reduce program size. The a.ld
prelinker supports a selective linking capability that may
reduce the size of a linked Ada program. Other link-time
optimizations are available and may be performed to improve
the execution speed of a program (See a.ld(1)).

AXI imposes no restrictions when using any of the
optimization techniques available when compiling and linking
AXI applications using the HAPSE environment.

7.5 An Example Motif Program

The following is the source code for a simple Motif program
that uses the AXI bindings. It may be compiled and linked
using the HAPSE compiler as shown in sections 6.1 and 6.2 of
these release notes.

--
-- Make all appropriate AXI packages visible
--

with Xm;
with Xrm;
with Xt;
with Xlib;

procedure helloworld is
--
app_context : Xt.AppContext;
toplevel, label : Xt.Widget;

- 12 -

Release Notes 6.2 CX/UX AXI

argv : Xt.stringlist_ptr;
options : Xrm.optiondesclist (1 .. 0);
fallback : string (1 .. 0) := "";
args : Xt.arglist (0 .. 1);
--
begin
--
argv := Xlib.getarguments;

-- Create and initialize the application context

app_context := Xt.createapplicationcontext;
Xt.AppInitialize (app_context, "Hello", options, 0, argv,
fallback, args, 0, toplevel);

-- Create a simple label widget

label := Xm.CreateLabel (toplevel, "Hello_World", args, 0);
Xt.ManageChild (label);

-- Enter the event loop

Xt.RealizeWidget (toplevel);
Xt.AppMainLoop (app_context);
--
end helloworld;

Other sample programs that demonstrate the usage of the AXI
bindings are available from Harris. Contact your Harris
analyst to obtain a copy of the sample programs. The sample
programs that are available use the AXI bindings to exercise
features in Xlib, Xt and Motif.

7.6 Programming Pitfalls

Many Xt and Motif references discourage the use of system
calls such as fork(), exec(), and system() because error
conditions that may arise (when using these system calls)
are virtually unrecoverable from an X application's
standpoint. If error recovery is not a critical matter from
the X application's view, then the use of such system calls
may be appropriate, and often useful. For non-ARMS
programs, the use of any such system call is clearly up to
the programmer; however, for ARMS applications, use of these
types of system calls is strictly prohibited. Any ARMS
program which attempts to use any routine that uses the
fork() system call will get an error at link time. The ARMS

- 13 -

CX/UX AXI 6.2 Release Notes

"spawn" services may be used as an alternative in ARMS
applications which require the ability to spawn other
processes.

AXI calls were designed to map as closely as possible to the
C language library functions to which they "bind". Ada
typing restrictions sometimes make this task more difficult,
and several AXI-defined Ada types have been defined in order
to make this task a bit easier. Users should always consult
the AXI documentation or refer to the package specifications
in order to choose the most appropriate form of any Xlib,
Xt, or Motif function that they wish to employ. Often
several different Ada interfaces are available (as
overloaded Ada functions and procedures) for a single C
function. If chosen properly, much work can be saved by
avoiding Ada type conversions when programming with the AXI
bindings.

8. Fixes in this Release

This is not the initial release of this product, however,
there are no fixes in this release. AXI version 6.2 is
identical to AXI version 3.0.1, compiled specifically for
use with HAPSE version 6.2.

9. Features in this Release

o Full Ada support of Xlib, Xt, and Motif operations on
Harris NightHawk Series 4000 and Series 5000 systems
running HAPSE. The AXI product includes:

o Support for X11 Release 5.

o Support for Motif version 1.1.

o Access to functions in the X Extensible Library.

o Access to functions in the X Miscellaneous
Utilities Library.

o Ada support for the Motif Resource Manager
(including UIL-based applications).

- 14 -

Release Notes 6.2 CX/UX AXI

o Support for the STARS interface to the X window
system (Xlib only)

o Support for non-blocking Ada tasking using the
Basic Ada Runtime System.

o A conventional naming scheme which parallels the
original C implementation.

o AXI is integrated with the HAPSE environment to take
advantage of the latest real-time Ada optimization and
performance features including:

o The HAPSE Ada compiler's CCG (common code
generator) optimizer which performs state-of-the-
art optimizations of Ada applications. Ada X
applications may be fully optimized for maximum
performance.

o The HAPSE prelinker's selective linking capability
which is capable of removing unused routines that
would normally be linked into Ada applications.

o The flexibility of choosing between the ARMS and
Basic Ada Runtime Systems when linking AXI
applications. Each has its own advantages and
disadvantages for Ada tasking and memory pool
configuration.

o A variety of real-time features and packages
provided with the HAPSE programming environment.

o A complete set of Ada bindings to standard UNIX5
(CX/UX) utilities. (Note: The POSIX 1003.5
product must be obtained separately from HAPSE).

__________

5. UNIX is a registered trademark of UNIX System
Laboratories, Inc.

- 15 -

CX/UX AXI 6.2 Release Notes

10. Known Problems with AXI 6.2

Problems with AXI version 6.2 included in the following list
will be addressed in patches to version 6.2 or will be
corrected in later versions of AXI. Full functionality of
the STARS binding to the Xt toolkit will provided in a
future release.

o The 6.2 version of AXI does not support Motif version
1.2.

o The STARS Xt implementation is not complete. The STARS
bindings should only be used for programming at the
Xlib level.

o Ada applications that use the Motif Resource Manager
may not correctly reference .uid files created by the
uil compiler.

o The HAPSE selective linker will not remove dead code
from C language libraries. Only dead code from Ada
libraries is subject to removal from linked
executables.

11. Direct Software Support

- 16 -

Release Notes 6.2 CX/UX AXI

for follow-up and action.

To obtain copies of SAR forms, call the Software Support
Center and request form number CSD1833B.

- 17 -

CONTENTS

1. Introduction............................................ 1

2. Documentation........................................... 3

3. Prerequisites........................................... 3
3.1 Hardware........................................... 3
3.2 Software........................................... 3

4. Cautions................................................ 4

5. Installation............................................ 4

6. Using the AXI Bindings.................................. 5
6.1 Compilation........................................ 6
6.2 Linking............................................ 7
6.3 Executing.......................................... 7
6.4 Debugging.......................................... 7

7. Programming Hints....................................... 8
7.1 Setting and Getting Widget Resources............... 8
7.2 Callbacks.......................................... 10
7.3 Ada Tasking in AXI Applications.................... 11
7.4 Optimizations...................................... 12
7.5 An Example Motif Program........................... 12
7.6 Programming Pitfalls............................... 13

8. Fixes in this Release................................... 14

9. Features in this Release................................ 14

10. Known Problems with AXI 6.2............................. 16

11. Direct Software Support................................. 16

- i -

_________________________________________________________________

HARRIS
COMPUTER SYSTEMS
_________________________________________________________________

CX/UX AXI
VERSION 6.2

RELEASE NOTES

0890418-6.2

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

- 2 -

Release Notes 6.2 Condor Ethernet Driver

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
================================================================================

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:

__________

- 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

- 2 -

Release Notes 6.2 Condor Ethernet Driver

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
================================================================================

CX/UX -
VERSION 6.2
RELEASE NOTES

Harris Computer Systems Division

1. Introduction

CX/UX Version 6.2 is a complete new release of the operating
system and applicable optional products; it requires a
complete re-gen of your system. This release incorporates
major system changes and support for new products.

Please read this entire document and all applicable optional
product release notes before you proceed with installation.

The CX/UX 6.2 release package contains a minimum of two
magnetic tapes: a Boot tape and a Products tape. The Boot
tape is in dd format and contains a number of stand-alone
utilities and the files in the Mini-root file system. The
Products tape is in cpio format and contains the root, /usr,
and /var file systems and optional products when purchased.
The root files, /usr files, /var files, and optional
products may require more than one tape depending on the
number of products included.

__________

- These release notes cover the following products: cx

- 1 -

CX/UX 6.2 Release Notes

2. Documentation

The following documentation is included with this release:

__________________________________________________
| Manual Name Pub. Number|
|___________________________________|_____________|
| CX/UX System Administration Manual| 0890108-100|
| CX/UX User's Guide | 0890112-020|
| CX/UX Support Tools Guide | 0890113-050|
| CX/UX Programmer's Guide | 0890114-060|
| Introducing UNIX System V | 0890184-000|
| CX Documentation Roadmap | 0890273-060|
| (KSH) KornShell Release Notes | 0890352-6.2|
| CX/UX POSIX Conformance Guide | 0890361-040|
| Using GDB Manual | 0890393-000|
| Night Hawk Documentation Overview | 0890377-010|
| CX/UX Version 6.2 Release Notes | 0890108-6.2|
|___________________________________|_____________|

Additional copies of documentation may be ordered by
contacting the Harris Software Support Center. Customers
are encouraged to use the CX Documentation Roadmap Manual
and the Night Hawk Documentation Overview Pamphlet.

In general, release notes are provided with software
products. The release notes you receive will be at the
software revision level at which the associated product last
changed. Please note that manual pages (manpages) are also
provided on-line in addition to printed or hard copy.

Certain operating system features that are common to both
the CX/UX and the CX/RT kernels are designed to increase the
determinism and predictability of the operating system and
improve the process dispatch latency for high-priority
tasks. These features are described in the 6.2 version of
the CX/RT Reference Manual (0890285-060). They may be of
interest to real-time users who do not purchase the CX/RT
product. Such users may order a copy of the CX/RT Reference
Manual separately.

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.

- 2 -

Release Notes 6.2 CX/UX

3. Prerequisites

Prerequisites for CX/UX Version 6.2 are as follows:

3.1 Hardware

o Any Series 4000 or Series 5000 system. (Note that
references in text where Series numbers are grouped,
e.g., "Series 4000-5000," implies Series 4000 through
Series 5000 hardware systems or platforms.)

3.2 Software

None.

4. Installation

4.1 General

The installation procedure for CX/UX Version 6.2 replaces
the current contents of your root, /usr, and /var
partitions. You should save and restore any files which you
have modified locally, files which are not distributed by
Harris, and any files which belong to products which are not
a part of the CX/UX Version 6.2 release. The distribution
tape is accompanied by a list of products contained on the
distribution tape.

Harris recommends that you back up your /, /usr, and /var
file systems using fdump(1M). You may alternatively prefer
to use cpio(1) or tar(1) to perform the backup. Following
the CX/UX 6.2 installation procedure, you should selectively
restore certain of the saved files.

You should merge any files which contain local
modifications. You should NOT use your locally modified
CX/UX 6.1 or earlier version of any file without merging in
the changes from CX/UX 6.2.

You should restore any files which are not distributed by
Harris. You should also restore any files belonging to
products which are not a part of the CX/UX 6.2 release.

The setup(1M) program generates a log of products installed
on the system. The log file is located in
/usr/src/PRODUCTS/loaded. It contains the product name, the
revision level of the product, the date it was installed,
and the directory it was installed under if not /. Whenever

- 3 -

CX/UX 6.2 Release Notes

optional or updated products are installed at a later date,
they are appended to the log, providing a quick reference
for what software at what revision level is on the system
and when it was installed.

Please refer to the CX/UX System Administration Manual,
Chapter 3, for specific software installation instructions.

4.2 Disk Partition Sizes

Each release of CX/UX includes new software in the root,
/usr, and /var partitions. Partition sizes that were
appropriate in earlier releases may not be sufficient for a
new release. Before attempting to load new software
products, the administrator should check the disk
requirements to verify that existing partition sizes are
adequate for the products that are to be installed.

Some file systems, particularly the /var file system, grow
during daily usage. The system administrator must determine
the amount of space needed for expansion of each file
system, and add that to the specified requirements.
Furthermore, the administrator should assume that the disk
space requirements will increase in future releases.

4.3 Installation Cautions

The setup(1M) command of CX/UX Version 6.2 can be directed
to put the /var directory tree in any of three places:

- physically within the /usr file system. Using this
option, /var is created as a symbolic link to /usr/var.
This option is most useful when re-installing CX/UX
onto an already existing master pack.

- on a third partition (which must have been created
previously using format(1M)). When this option is
used, /var is mounted automatically during each boot.
This option is recommended when installing CX/UX onto a
new master pack.

- on the root partition. Although the most
straightforward of the three choices, this option is
not recommended due to the root partition often being
small.

- 4 -

Release Notes 6.2 CX/UX

System administrators will need to decide where to put /var
when formatting the master disk or, at the latest, before
running setup(1M). See the CX/UX System Administration
Manual, Chapter 3, for details. Whichever file system holds
the /var directory structure will have to provide sufficient
free disk space for accounting files, log files, spool
files, and temporary files.

Although a product's release level may not have changed,
customers are strongly encouraged to use the latest version
of the product's object, which is shipped on the products
tape(s). The latest object of a given product should be
used for the following reasons:

1. It has the latest bug fixes incorporated in it.

2. It was compiled with the latest versions of the
compilers.

3. It was linked with the latest versions of the system
library routines that are used by that product.

4. It takes advantage of the latest system services
available in the most recent kernel.

5. Cautions

The file system structure provides only a small number of
commands in the root partition. Consequently, very little
can be done before the /usr and /var file systems are
mounted. The /sbin directory contains only those commands
that are helpful in mounting these file systems.

6. New Features in this Release

6.1 Integrated Graphics

The new GPX Integrated Graphics Processor is a tightly-
coupled component of the Night Hawk architecture, an
expansion of the Integrated SCSI-Ethernet daughter board.
The GPX 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 product 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

- 5 -

CX/UX 6.2 Release Notes

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.

The GPX/8 has 4 megabytes of video display memory,
sufficient for double buffering. This frame buffer may be
mapped into the application's address space for display
control without any kernel interactions. Up to four
independent display stations can be configured on a single
Night Hawk system (one per processor board).

GPX devices can be used as user terminals, the boot console
and system console, or as graphics output devices. They may
be used also as X Window System terminals with the optional
X11 product that provides an X11R5 server with PEX
extensions and is fully compatible with X11 and OSF/Motif
applications.

Configuration information for the GPX devices can be found
in gpx(7) and console(7). Additional programming
information can be found in display(7), keyboard(7), and
termio(7).

6.2 IEEE POSIX 1003.4

CX/UX release 6.2 supports all of the interfaces included in
IEEE Draft Standard P1003.4/D12. This is a draft, not the
final version of the standard. The interfaces in CX/UX will
be revised to reflect any changes made by future drafts of
the standard.

Warning: Future releases will be source compatible when the
interfaces in POSIX.4 are unchanged, but programs may need
to be recompiled when upgrading to new releases.

The POSIX.4 interfaces are documented in the CX/RT Reference
Manual, CX/UX Programmer's Guide, and man pages. Following
is a list of all of the POSIX.4 functional areas and the
name of the chapter and manual in which the corresponding
CX/UX interfaces are documented:

Counting semaphores "Interprocess Synchronization"
CX/UX Programmer's Guide
Process memory locking "Memory Management"

- 6 -

Release Notes 6.2 CX/UX

CX/UX Programmer's Guide
Memory mapped files and shared memory "Memory Management"
CX/UX Programmer's Guide
Priority scheduling "Process Scheduling and Management"
CX/RT Reference Manual
Real-time signal extension "Signal Management"
CX/UX Programmer's Guide
Clocks and timers "Timing Facilities"
CX/UX Programmer's Guide
"Improving Response Time"
CX/RT Reference Manual
Interprocess message passing "Interprocess Communication"
CX/UX Programmer's Guide
Synchronized input and output fdatasync(2), open(2)
CX/UX Programmer's Reference Manual
Asynchronous input and output "Real-Time I/O"
CX/UX Programmer's Guide
Real-time files "Real-Time Files"
CX/UX Programmer's Guide

Some of the interfaces included in Draft 12 were added in
previous releases. The Draft 12 interfaces that are being
added to CX/UX 6.2 are described in the sections that
follow.

6.2.1 Interprocess_message_passing

The interprocess message-passing interfaces provide a means
of passing arbitrary amounts of data between cooperating
processes. These interfaces are defined to provide
efficient and deterministic data passing. They allow
processes to communicate through message queues, which are
accessed through names that are not a part of the file
system. Messages can be assigned priorities ranging from
zero to 31.

For more information about the POSIX.4 message-passing
interfaces, refer to the following man pages:

mq_close(3P4) mq_destroy(3P4)
mq_getattr(3P4) mq_notify(3P4)
mq_open(3P4) mq_receive(3P4)
mq_send(3P4)

- 7 -

CX/UX 6.2 Release Notes

6.2.2 Counting_Semaphores

The counting semaphore mechanism provides a means of fast
process synchronization. It allows multiple processes to
synchronize their access to the same resource. A counting
semaphore is created by specifying a non-negative value for
the semaphore. If the value is positive, a resource is
available, and the calling process is allowed to continue.
If the value is zero or less, the calling process is blocked
until some other process holding a resource unlocks the
semaphore.

For more information about the POSIX.4 counting semaphore
interfaces, refer to the following man pages:

sem_destroy(3P4) sem_init(3P4)
sem_lock(3P4) sem_trylock(3P4)
sem_unlink(3P4) sem_unlock(3P4)

6.2.3 Synchronized_I/O

The synchronized I/O facility provides the assurance that
the data being read or written is an accurate image of the
data present on disk. POSIX.4 synchronized I/O is supported
only for the local disk file system. A synchronized output
operation guarantees that the data written is actually
present on the disk. A synchronized input operation
guarantees that the data read is a current copy of the data
on disk; any pending write operations affecting the data are
completed before returning to the application.

For more information about the POSIX.4 synchronized I/O
interfaces, refer to the following man pages:

fdatasync(2) open(2)

6.2.4 Memory_Mapped_Files_and_Shared_Memory

POSIX.4 defines interfaces for memory mapped files and
shared memory. Although CX/UX does not currently support
the memory mapped files option, it does provide an
implementation of the shared memory objects option. The
CX/UX implementation does not adhere to all of the POSIX.4
specifications in this area because the interfaces that it
provides do not have all of the functionality of the POSIX.4
interfaces. The CX/UX implementation of the POSIX.4 mmap
routine, for example, gives processes a means to share data
by allowing them to map a portion of their address space to
a memory object, but it does not allow them to map the

- 8 -

Release Notes 6.2 CX/UX

contents of a file or the registers of a hardware device.
Although the CX/UX implementation of the interfaces is
restricted in this and other ways that are noted in the
explanations of the routines, an application that uses the
CX/UX interfaces in the restricted manner will be compliant
with POSIX.4; it will be source-code compatible with a
subsequent CX/UX release that supports all of the mmap
capabilities as they are defined in POSIX.4.

For more information about the POSIX.4 memory mapped files
and shared memory interfaces, refer to the following man
pages:

shm_open(3P4) shm_unlink(3P4)
mmap(3P4) munmap(3P4)

6.2.5 Real-Time_Files

The real-time files interfaces allow the transfer of
advisory information between an application and the
underlying file system. The intent is that an application
can vary its behavior as a result of the capabilities of the
system. Conversely, a system may be able to perform some
level of optimization based on the intentions of an
application.

The file system performance features affected by the POSIX.4
interfaces are as follows:

1. Files optimized for sequential access

2. Pre-allocation of the data space for a file - possibly
contiguously

3. Direct I/O

4. Hints to the buffer cache on the anticipated usage of a
given file

An application can optimize its I/O throughput by obtaining
the following information:

1. Buffer alignment requirements for direct, buffered, and
atomic I/O transfers

2. Transfer size information for direct, buffered, and
atomic I/O transfers (includes supported and optimal
transfer size range)

- 9 -

CX/UX 6.2 Release Notes

For more information about the POSIX.4 real-time files
interfaces, refer to the following man pages:

rf_create(3P4) rf_setattr(3P4)
rf_getattr(3P4) rf_getalloccap(3P4)
rf_getcachecap(3P4) rf_getbiocap(3P4)
rf_getaiocap(3P4) rf_getdiocap(3P4)
rf_getbuf(3P4) rf_freebuf(3P4)
rf_getincr(3P4)

6.2.6 Asynchronous_I/O

The asynchronous I/O mechanism provides the ability to
overlap application processing and I/O operations initiated
by the application. The asynchronous I/O mechanism allows a
single process to perform I/O simultaneously to a single
file multiple times or to multiple files multiple times.

The POSIX.4 asynchronous I/O interfaces are offered in
addition to the current CX/UX asynchronous I/O facilities.
They support list-directed I/O, which is new to CX/UX. The
lio_listio() interface allows the caller to submit multiple
asynchronous I/O requests with a single system call.

For more information about the POSIX.4 asynchronous I/O
interfaces, refer to the following man pages:

aio_cancel(3P4) aio_error(3P4)
aio_fsync(3P4) aio_read(3P4)
aio_return(3P4) aio_suspend(3P4)
aio_write(3P4) lio_listio(3P4)

6.3 Disk Enhancements

The generic disk drivers were modified to support removable
media, such as on optical disks. The system can be
initialized without media in the drive, and the media will
be checked and the geometry block read upon the first access
after the media has been loaded. If the media is removed
during system usage, error codes are returned to the calling
program until new media has been loaded. Once loaded new
geometry is read from the media to determine locations of
disk partitions. The HSA and ISE disk drivers have also
been updated to allow disk drives to have physical sector
sizes of 1024 bytes, in addition to the current 512 value.

- 10 -

Release Notes 6.2 CX/UX

On drives which support variable sector size, the format
utility can be used to specify the sector size when the
media is formatted.

6.4 HN5800 Support

The HN5800 is based on the second generation of RISC based
microprocessors from Motorola, the MC88110, which follows
the MC88100/200 RISC processor used in the Harris
HN4400/4800. In keeping with the Pre-Planned Product
Improvement (P3I) strategy, the HN5800 will be a direct
upgrade to the current product line: the boards will be
plug-compatible with the current backplane; the operating
system will be CX/UX; the instruction set will be
compatible; and all of the I/O controllers in the current
product line will work with the HN5800. Another important
feature will be user-level object compatibility with
HN4400/HN4800 user code which does not utilize
architecture-dependent features (code which bypasses the
operating system and directly manipulates the hardware).

The HN5800 will be a RISC-based super microcomputer system
using the Motorola MC88110 as its core processor. The
HN5800 will have various system configurations depending on
the number of processor boards, global memory boards, and
the possible inclusion of an I/O expansion board, all of
which are typically installed in a 21-slot HVME64 backplane.
The Integral SCSI/Ethernet (daughter card) and local memory
daughter cards also will be available on this system. In
fact, a minimum system will consist of one processor board
(containing one CPU), an Integral SCSI/Ethernet, and a 16 MB
local memory daughter card. Furthermore, smaller HN5800
configurations will fit in HN4400/HN4800 pedestal packages.

For larger HN5800 configurations (i.e., those consisting of
multiple boards in the HVME backplane), the HN4800
frontplane concept will be utilized with some adaptations.
The HN5800 frontplane will provide both a high-speed access
to system expansion boards and an independent path for a
secondary I/O (bus) capability. A maximum system
configuration will be four processor boards (eight CPUs
total), one global memory board, one I/O expansion board,
and a six-slot frontplane. If enhanced I/O throughput is
not required, the I/O expansion board may be replaced with a
second global memory board.

Even though most user-level object code is upwardly
compatible from the NH4800 systems, HN5800 systems require
different kernels, standalone utilities, and diagnostics.

- 11 -

CX/UX 6.2 Release Notes

See the Series 5000 Compatibility section for more
information on HN5800 compatibility.

6.5 Series 5000 Compatibility

In general, it is possible to be object and source
compatible between Series 4000 and Series 5000 systems.
However some pre-6.2 sources and executables will not
operate on Series 5000 systems. These include:

o Kernel device drivers, user device drivers, and any
program which directly accesses an I/O device may need
to be modified. The MC88110 executes loads and stores
out of order and may re-execute loads many times. If
this is a problem, the driver must be modified to use
the "volatile" type for pointers to the device and
compile with the "-Qsync_volatile" option.

o Executables using binary semaphores (lockbinsem(3C) and
unlockbinsem(3C)) linked prior to 6.2 will not operate
correctly. They use an instruction that is changed on
the MC88110.

o Executables and sources that access the 64-bit system-
wide interval timer will not operate correctly. The
format of the interval timer on the Series 5000 is
different from the Series 4000. The Series 5000 timer
matches the POSIX 1003.4 format. It is 64 bits wide,
the upper word incrementing in seconds and the lower in
nanoseconds. The entire counter may be accessed in one
atomic 64 bit read. It is recommended that the POSIX
1003.4 interfaces available in 6.1 be used to isolate
applications from the format of the interval timer.
The release 6.2 interfaces will support both systems
with no recompilation required (current 6.1 libraries
do not support the Series 5000, however the source
interface is the same).

o Because of the interval timer changes, ADA ARMS
programs and all programs using the interval_timer
package will need to be recompiled or relinked.

o On Series 5000 systems, all semaphore operations must
occur in cached memory. The xmem instruction, which is
used to construct test-and-set operations is not atomic
except in cached memory. See bsemget(2),
Test_and_set(3c), spin_trylock(2), and server_block(2)
for examples of routines which use this instruction.

- 12 -

Release Notes 6.2 CX/UX

The Series 4000 does not have this restriction.

o Programs directly accessing the RTCs will need
recompiling and possibly source changes. The command
register offset has been changed, and the method of
reprogramming the RTC in direct mode is different. It
is strongly suggested that the kernel driver be used to
access the RTCs. This interface is compatible on all
architectures.

o The FPSR register is not updated with the cause of a
floating point exception in a signal handler. The
cause of the exception is available in the exception
blocks in the same manner as on a Series 4000. See
signal(5) for more information. When a signal handler
is not invoked, the FPSR is updated.

o Instructions which use odd register pairs are emulated
by trapping into the operating system on a Series 5000.
This results in much slower performance in these cases.
An example of this would be: ld.d r13,r4,0. Released
compilers do not generate this condition.

o Certain assembly instructions have different behavior,
they should no longer be used in assembly source. This
should not be a problem unless assembly source was
written. The instructions that have changed are: lda
immediate, lda unscaled, triadic lda.b, and the
immediate form of xmem.

It is possible to target applications to work only on the
Series 5000 (uses 88110 features), only on the Series 4000
(uses 88100 features), or will operate on both (uses only
compatible features). See the Language Processors section
for more information.

6.6 Intelligent Networking

Intelligent Networking allows the Internet Protocol software
to exist on the networking controller. Specifically, the
TCP, UDP, IP, and ICMP protocol software will execute on
both the Interphase 4207 Eagle (Ethernet) controller and the
Interphase 4211 Peregrine (FDDI) controller. This allows
offloading the host CPU for protocol processing functions.

Both of the above controllers will be supported in both
intelligent and non-intelligent (host-based protocols) in
6.2. For the 4211, the same board is used in both cases,

- 13 -

CX/UX 6.2 Release Notes

the only difference being software configuration. For the
4207 (Ethernet), a different board with different firmware
is required.

The intelligent networking controllers are STREAMS drivers
and, hence, use STREAMS to access the boards. Therefore,
there are many changes in the system and utilities to access
the STREAMS controllers. Specifically, a kernel sockets
library is included in 6.2 which translates socket calls to
appropriate STREAMS calls. This code was ported from the
M88K SVR4 and is needed to ensure BCS compatibility with the
STREAMS-based networking. Other utility changes are
required, such as in ifconfig, ping, arp, inetd, etc. These
utilities have been modified to operate on either or both
kinds of networking.

Any number (up to six) of intelligent networking controllers
can be active on a given host at the same time. This is
(optionally) in addition to the host-based networking.
However, default Internet activity must be directed to a
single interface. Thus processes may access any specific
controller through appropriate TLI calls; however, Internet
utility traffic (such as ftp, telnet, rlogin) will be
limited to a single intelligent controller or the host-based
protocols. Routing between an intelligent controller and
any other interface is not permitted.

6.7 Miscellaneous Enhancements

6.8 New Utilities

The following commands are new in CX/UX release 6.2:

asa(1) interpret ASA carriage control
characters

6.9 New C Library Functions

New fpgettcfp and fpsettcfp functions are available for use
on Series 5000 systems. They provide user control and
access of the time-critical floating point modes.

- 14 -

Release Notes 6.2 CX/UX

7. Changes from Previous Releases

7.1 Operating System

7.1.1 Configuration_file

The system configuration file has an option
(PTRACE_BCS_CONFORMANCE) that enables 88open ptrace
conformance. This option disables the ptrace() attach
functions (PT_TRACE_PROC, PT_RELEASE_PROC, PT_TRACE_CHILD).

Note that the format for configuring the Integral SCSI
Adaptor and the Integral Ethernet adaptor has changed in the
system configuration file. The vector parameter is no
longer valid.

7.1.2 Changes_to_POSIX.4_Interfaces

The POSIX.4 interfaces that are being released are based on
IEEE Draft Standard P1003.4/D12. This is an unapproved
draft, subject to change. The interfaces provided by CX/UX
will evolve to support the latest drafts of this standard as
they become available. Any incompatibilities introduced by
a new operating system release will be documented in this
section of the release notes for all future operating system
releases.

The following POSIX.4 interfaces that were introduced in
release 6.1 have changed: (1) binary semaphores and (2)
clocks and timers. The changes are described in the
sections that follow.

7.1.2.1 Binary Semaphores

The binary semaphore interfaces are not a part of
P1003.4/D12. Synchronization between processes is now
supported via the counting semaphore mechanism. The syntax
of the counting semaphore interfaces is significantly
different from the syntax of the binary semaphore
interfaces. Counting semaphores can be used to obtain the
same functionality as a binary semaphore by initializing the
counting semaphore value to one.

7.1.2.2 Clocks and Timers

The name of the header file that must be included by a
program that uses any of the POSIX.4 clocks and timers
interfaces has changed. In release 6.1, the name of the
header file was . In release 6.2, the name of the

- 15 -

CX/UX 6.2 Release Notes

header file is .

7.2 Language Processors

7.2.1 Development_and_Execution_Environments

Ada and the C compiler will support the "sync_volatile"
options and all libraries/runtimes will support the new
interval timer format. See the Series 5000 Compatibility
sections for more information.

To support the HN5800 changes were made to the development
environments. There are now three modes for an object file
(including executables):

o 88100: Relies on features unique to the 88100.

o 88110: Relies on features unique to the 88110.

o 88110-compatible: Does not rely on features unique to
either chip.

Corresponding C compiler, assembler, dis, and adb options:

o -Qtarget=m88100

o -Qtarget=m88110

o -Qtarget=m88110compat

Analyze88 options:

o -Z88100

o -Z88110

Without options, the compilers, assembler, analyze88, dis,
and adb use the machine type to establish the mode.

The linker verifies the compatibility of modes and
identifies any restrictive mode (88100 or 88110) in the
executable's vendor section file. It also defines global
variables, accordingly, so that run-time C library routines
can determine in which mode to execute.

- 16 -

Release Notes 6.2 CX/UX

No additional compilers or libraries are needed for CX/UX
6.2. A single set will be shared among Series 4000 and
Series 5000 systems.

Object files and link edited programs are identified as to
whether they require architectural features unique to Series
4000 and/or Series 5000 systems. New assembler options
(see below) provide this identification in the vendor
sections ($0001300) of object files. The link editor then
examines the identifiers of all object files which make up
the program. Any "mixing" of features produces a warning,
for the program may not execute successfully on one of the
platforms. The link editor also identifies the program as
to which platform, if any, provides unique features needed
by the program. During program initialization, the *crt0.o
routines initialize global variables ____mc88100 and
____mc88110. ____mc88100 is set to one if the program
requires features unique to Series 4000 systems; otherwise,
it is set to zero. Similarly, ____mc88110 is set to one if
the program requires features unique to Series 5000 systems;
otherwise, it is set to zero.

7.2.2 Assembler

New -Q options are added to identify object files with
respect to their dependence on architectural features of
Series 4000 and Series 5000 systems (see above). -
Qtarget=m88100 indicates that the assembly source and
resulting object file depend upon the Motorola MC88100
microprocessor, provided in Series 4000 systems. -
Qtarget=m88110 indicates that the assembly source and
resulting object file depend upon the Motorola MC88110
microprocessor, provided in Series 5000 systems. Warnings
are issued if features unique to the other platform are used
in the assembly source. -Qtarget=m88110compat indicates
that the assembly source and resulting object file should be
regarded as compatible with any other code from either
Series 4000 or Series 5000 systems.

7.2.3 Disassembly

Both dis and adb accept new -Q options for disassembling
instructions. -QMC88100 interprets opcodes and operands as
MC88100 instructions, and -QMC88110 interprets them as
MC88110 instructions. If neither option is supplied,
interpretation is done according to the platform (either
Series 4000 or Series 5000) on which the utility is run.

- 17 -

CX/UX 6.2 Release Notes

7.2.4 Debuggers

adb will fully support the HN5800 in release 6.2. gdb will
support the NH5800 at release 6.2 and a new version will be
released when full compiler support for the NH5800 is
complete. dbx will be frozen at the current version (no
changes are planned to support the new features of the
NH5800).

7.3 Utilities

shutdown(1M), halt(1M) and reboot(1M)

In previous releases, only super-user could invoke the
shutdown(1M), halt(1M) and reboot(1M) utilities. In this
release, a non super-user with reboot (ACC_REBOOT) and
signal generation (ACC_KILL) access may also invoke these
utilities. Refer to acc_vector(4) for more description on
access vectors.

tar(1)

A new CX/UX 'U' command modifier has been added to tar.
This modifier will permit archives created with this release
of tar to be read by versions of tar released by the
University of California at Berkeley (UCB) on other systems.
The UCB version of tar appends a "/" by default after every
directory name archived. This release of tar does not
perform this action by default, because it is not permitted
by the POSIX 1003.1 or X/Open extended tar formats. Usage
of this modifier will permit the UCB default action to take
place when creating an archive. Utilizing this option, will
permit archives created by this release of tar to be read by
CX/UX versions of UCB tar released prior to CX/UX 5.3.
Refer to tar(1) for more information.

tarmail(1)

A new CX/UX '-u' option has been added to tarmail permitting
it to create tar archives in the UCB format described by the
tar(1) section above. Refer to tarmail(1) for more
information.

- 18 -

Release Notes 6.2 CX/UX

8. Direct Software Support

To obtain copies of SAR forms, call the Software Support
Center and request form number CSD1833B.

- 19 -

CONTENTS

1. Introduction............................................. 1

2. Documentation............................................ 2

3. Prerequisites............................................ 3
3.1 Hardware............................................ 3
3.2 Software............................................ 3

4. Installation............................................. 3
4.1 General............................................. 3
4.2 Disk Partition Sizes................................ 4
4.3 Installation Cautions............................... 4

5. Cautions................................................. 5

6. New Features in this Release............................. 5
6.1 Integrated Graphics................................. 5
6.2 IEEE POSIX 1003.4................................... 6
6.2.1 Interprocess message passing................. 7
6.2.2 Counting Semaphores.......................... 8
6.2.3 Synchronized I/O............................. 8
6.2.4 Memory Mapped Files and Shared Memory........ 8
6.2.5 Real-Time Files.............................. 9
6.2.6 Asynchronous I/O............................. 10
6.3 Disk Enhancements................................... 10
6.4 HN5800 Support...................................... 11
6.5 Series 5000 Compatibility........................... 12
6.6 Intelligent Networking.............................. 13
6.7 Miscellaneous Enhancements.......................... 14
6.8 New Utilities....................................... 14
6.9 New C Library Functions............................. 14

7. Changes from Previous Releases........................... 15
7.1 Operating System.................................... 15
7.1.1 Configuration file........................... 15
7.1.2 Changes to POSIX.4 Interfaces................ 15
7.1.2.1 Binary Semaphores................... 15
7.1.2.2 Clocks and Timers................... 15
7.2 Language Processors................................. 16
7.2.1 Development and Execution Environments....... 16
7.2.2 Assembler.................................... 17
7.2.3 Disassembly.................................. 17
7.2.4 Debuggers.................................... 18
7.3 Utilities........................................... 18

8. Direct Software Support.................................. 19

- i -

_________________________________________________________________

HARRIS
COMPUTER SYSTEMS
_________________________________________________________________

CX/UX
VERSION 6.2

RELEASE NOTES

0890108-6.2

October 1992

_________________________________________________________________

Trademark Acknowledgments

Ethernet is a registered trademark of Xerox Corporation

return to index
================================================================================

CX/RT -
VERSION 6.2
RELEASE NOTES

Harris Computer Systems Division

1. Introduction

CX/RT Version 6.2 includes two products, cx_rt and
cx_rt_develop, to be used in conjunction with CX/UX 6.2. The
cx_rt product consists of the CX/RT kernel, which is a low-
overhead real-time kernel compatible with the CX/UX 6.2
kernel. It is a multiprocessing multithreaded, preemptive
kernel.

2. Documentation

The following documentation is included with this release:

_______________________________________________
| Manual Name Pub. Number|
|________________________________|_____________|
| CX/RT Reference Manual | 0890285-060|
| CX/RT Version 6.2 Release Notes| 0890285-6.2|
|________________________________|_____________|

__________

- These release notes cover the following products: cx_rt
and cx_rt_develop

- 1 -

CX/RT 6.2 Release Notes

3. Prerequisites

Prerequisites for CX/RT Version 6.2 are as follows:

3.1 Hardware

o Any Series 4000 or 5000 system.

3.2 Software

o CX/UX 6.2

4. Installation

Please refer to the CX/UX System Administration Manual,
Chapter 3, for instructions on software installation.

Refer to the CX/RT Reference Manual for configuration
instructions specific to cx_rt_develop.

5. Cautions

The real-time data recording program, rt_datarec, requires
that the CX/RT kernel be configured with the frequency-based
scheduler facility, the shared memory mechanism, and the
AT&T System V semaphore mechanism.

Due to its vendor-specific nature, the real-time library for
FORTRAN, /usr/lib/libF77rt.a, a part of the cx_rt_develop
product, is not OCSTM (Object Compatibility Standard)
compliant.* FORTRAN object modules compiled in OCS-
compliant mode will not be able to link with this library.

__________

* OCS is a trademark of the 88open Consortium Ltd.

- 2 -

Release Notes 6.2 CX/RT

6. New Features in the cx_rt Product

6.1 Additional Interfaces Based on POSIX 1003.4

The 6.2 releases of CX/UX and CX/RT support all of the
interfaces included in IEEE Draft Standard P1003.4/D12.
Some of the interfaces included in Draft 12 were added in
previous releases. The interface areas that have been added
in release 6.2 are as follows: interprocess message
passing, counting semaphores, synchronized I/O, memory
mapped files and shared memory, real-time files, and
asynchronous I/O. For a description of these interfaces,
refer to the CX/UX Version 6.2 Release Notes. For detailed
information on the procedures for using these interfaces,
refer to the CX/UX Programmer's Guide.

7. Changes from Previous Releases

7.1 Changes to POSIX.4 Interfaces

IEEE Draft Standared P1003.4/D12 is an unapproved draft,
subject to change. The interfaces provided by CX/UX and
CX/RT will change to reflect any changes made by future
drafts of the standard.

The POSIX.4 interfaces related to binary semaphores and
clocks and timers, which were introduced in release 6.1,
have changed. For a description of the changes, refer to
this section in the CX/UX Version 6.2 Release Notes.

7.2 Changes to Include (Header) Files

Some changes were made to the sys/rtcmacros.h header file.
Unless the RTC devices are accessed directly (not through
the device driver), these changes will have no effect.
Directly accessing the RTC devices is not recommended.

7.3 Change Regarding Man Pages

In previous releases, the system manual pages related to the
cx_rt product have been included in an appendix in the CX/RT
Reference Manual. These man pages have always also been
included in the appropriate man page manuals-that is, the
CX/UX User's Reference Manual, CX/UX Programmer's Reference
Manual, and the CX/UX Administrator's Reference Manual.

- 3 -

CX/RT 6.2 Release Notes

Beginning with release 6.2, these man pages are included
only in the appropriate man page manuals.

8. Direct Software Support

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 the cx_rt Product......................... 3
6.1 Additional Interfaces Based on POSIX 1003.4.......... 3

7. Changes from Previous Releases............................ 3
7.1 Changes to POSIX.4 Interfaces........................ 3
7.2 Changes to Include (Header) Files.................... 3
7.3 Change Regarding Man Pages........................... 3

8. Direct Software Support................................... 4

- i -

_________________________________________________________________

HARRIS
COMPUTER SYSTEMS
_________________________________________________________________

CX/RT
VERSION 6.2

RELEASE NOTES

0890285-6.2

October 1992

_________________________________________________________________

return to index
================================================================================

CX/SX -
VERSION 6.2
RELEASE NOTES

Harris Computer Systems Division

1. Introduction

CX/SX is the Harris Secure operating system. It includes
the following features:

o Configuration to either C2 or B1 level security

o Mandatory Access Control (MAC)

o Enhanced Discretionary Access Control (DAC)

o Trusted Path

o Object Reuse

o System Audit Trail (SAT)

o System Assurance Tools

o Management of User and Device Clearances

It is essential that you read this entire document and the
CX/SX Trusted Facility Manual before you attempt to install
CX/SX 6.2 on your system. Many decisions must be made
before installation which may affect proper operation of
CX/SX. Reading of the documentation will enable you to make
proper decisions about the configuration of your secure
installation.

__________

- These release notes cover the following products: cx_sx

- 1 -

CX/SX 6.2 Release Notes

2. Documentation

The following documentation is included with this release:

_______________________________________________________
| Manual Name Pub. Number|
|________________________________________|_____________|
| CX/SX Trusted Facility Manual | 0890336-040|
| CX/SX User's Guide and Reference Manual| 0890335-040|
| CX/SX Version 6.2 Release Notes | 0890336-6.2|
|________________________________________|_____________|

3. Prerequisites

Prerequisites for CX/SX Version 6.2 are as follows:

3.1 Hardware

o Any Series 4000 or 5000 system.

3.2 Software

o CX/UX 6.2

4. Installation

Installation of CX/SX is done with the setup(1M) and
sysadm(1M) programs. Please refer to the CX/UX System
Administration Manual, Chapter 3, for instructions on
software installation and Chapter 8 of the CX/SX Trusted
Facility Manual for CX/SX installation.

- 2 -

Release Notes 6.2 CX/SX

5. Configuration of Security Features

CX/SX Version 6.2 is a target B1 level secure system as
defined in the Trusted Computer System Evaluation Criteria
(TCSEC or Orange Book) published by the Department of
Defense. CX/SX may be configured to enforce only C2 level
security features, which are a subset of the B1 level
features. Please refer to chapter 8 of the CX/SX Trusted
Facility Manual for further information on configuring
security features.

Sites planning to configure their system to enforce only C2
level security may wish to consider a special B1 level
configuration instead. If a B1 system is defined with only
two security levels, system level and user level, extra
protection is provided to system software without enforcing
multilevel security among users. The site administrator
should read the CX/SX Trusted Facility Manual thoroughly to
determine whether this special configuration would be
appropriate.

6. Installing Optional Products

The recommended way to install optional products on CX/SX is
to install them as part of the CX/UX installation, prior to
installing CX/SX as described in the CX/SX Trusted Facility
Manual.

Part of the CX/SX installation procedure includes the
automatic removal of any commands that might compromise
security. These commands are listed in the file
/usr/admin/menu/securemgmt/Savelist. If any optional
products are brought onto the system after the CX/SX
installation is complete, the administrator must ensure that
none of the items listed in Savelist have been re-installed
on the system. Furthermore, the Trusted Computing Base
(TCB) should be verified before new application software is
installed. New assurance tapes should be created after the
new application software is installed, but before bringing
the system into multi-user mode. Procedures for creating
the assurance tapes and verifying the TCB are contained in
Appendix B of the CX/SX Trusted Facility Manual.

- 3 -

CX/SX 6.2 Release Notes

7. New Features

None.

8. Security Cautions

There is more to system security than just software. Proper
education of the user community and administrative personnel
is required to assure secure operation. It is highly
recommended that each person involved with the
administration of the system read the CX/SX Trusted Facility
Manual before installing and using CX/SX. There are several
decisions which can be made that will affect the overall
security of the system. Administrative duties should be
divided up among operators, system administrators, and
security administrators. Note that physical security of the
system console is imperative.

For specific cautions and warnings regarding interaction of
CX/SX with some optional products, see Appendix G of the
CX/SX Trusted Facility Manual.

9. Direct Software Support

- 4 -

Release Notes 6.2 CX/SX

To obtain copies of SAR forms, call the Software Support
Center and request form number CSD1833B.

- 5 -

CONTENTS

1. Introduction.............................................. 1

2. Documentation............................................. 2

3. Prerequisites............................................. 2
3.1 Hardware............................................. 2
3.2 Software............................................. 2

4. Installation.............................................. 2

5. Configuration of Security Features........................ 3

6. Installing Optional Products.............................. 3

7. New Features.............................................. 4

8. Security Cautions......................................... 4

9. Direct Software Support................................... 4

- i -

_________________________________________________________________

HARRIS
COMPUTER SYSTEMS
_________________________________________________________________

CX/SX
VERSION 6.2

RELEASE NOTES

0890336-6.2

October 1992

_________________________________________________________________

return to index
================================================================================

DR11W -
VERSION 6.2
RELEASE NOTES

Harris Computer Systems Division

1. Introduction

The DR11W emulator is a high-speed, 16-bit parallel DMA
interface between the CX systems and most DR11W-compatible
devices, including other DR11W emulators. Furthermore, the
DR11W emulator provides several real-time features, such as
I/O directly to/from a process's address space, asynchronous
I/O support, three attention interrupt notification
mechanisms, and a 32 megabyte DMA transfer capability.

A set of library routines can be obtained to access the
DR11W device directly from user space. The source code to
this user level driver is provided so that the driver can be
modified to perfectly fit the needs of a given application.
Performing I/O through the user-level driver can provide a
tremendous improvement in reducing the overhead of issuing
an I/O request.

Refer to the CX/UX Programmer's Guide for complete
information.

2. Documentation

The following documentation is included with this release:

___________________________________
| Manual Name Pub. Number|
|____________________|_____________|
|____________________|_____________|

__________

- These release notes cover the following products: dr11w

- 1 -

DR11W 6.2 Release Notes

| DR11W Release Notes| 0890303-6.2|
|____________________|_____________|

3. Prerequisites

Prerequisites for DR11W Version 6.2 are as follows:

3.1 Hardware

o Any Series 4000 or 5000 system.

o DR11W emulator

3.2 Software

o CX/UX 6.2

4. Installation

Please refer to the CX/UX System Administration Manual,
Chapter 3, for instructions on software installation.

5. Cautions

None.

6. New Features in this Release

None.

- 2 -

Release Notes 6.2 DR11W

7. Changes from Previous Releases

None.

8. Direct Software Support

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. New Features in this Release.............................. 2

7. Changes from Previous Releases............................ 3

8. Direct Software Support................................... 3

- i -

_________________________________________________________________

HARRIS
COMPUTER SYSTEMS
_________________________________________________________________

DR11W
VERSION 6.2

RELEASE NOTES

0890303-6.2

October 1992

_________________________________________________________________

return to index
================================================================================

EMACS -
VERSION 6.2
RELEASE NOTES

Harris Computer Systems Division

1. Introduction

This release of Emacs is version 18.55 of the Free Software
Foundation's GNU Emacs with minor enhancements in use at
Harris Computer Systems Division. Emacs is provided free to
every customer in source and object form. It is Class B
software and, therefore, is not supported by Harris.

This release also includes Leif (a language based editing
system). Leif is provided under the same terms as emacs as a
Class B product and with the source code included.

2. Copyright

GNU Emacs is copyrighted by Richard M. Stallman. Conditions
for redistribution and warranty information may be found in
the GNU Emacs General Public License, which is included as
part of this distribution.

3. Documentation

The following documentation is included with this release:

____________________________________
| Manual Name Pub. Number|
|_____________________|_____________|
| GNU Emacs Manual | 0891016-100|
| Emacs Release Notes | 0891016-6.2|
|_____________________|_____________|

__________

- These release notes cover the following products: emacs

- 1 -

Emacs 6.2 Release Notes

| User Manual for Leif| 0890387-000|
|_____________________|_____________|

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 of the continental United States, the number
is 1-305-971-6248.

4. Prerequisites

Prerequisites for Emacs Version 6.2 are as follows:

4.1 Hardware

o Any Series 4000 or 5000 system.

4.2 Software

o CX/UX 6.2

5. Installation

Please refer to the CX/UX System Administration Manual,
Chapter 3, for instructions on software installation.

The source for GNU Emacs may be found in /usr/src/cmd/emacs;
the executable itself in /usr/bin, and its libraries and
auxiliary programs and data files in /usr/lib/emacs.

6. Cautions

GNU Emacs requires approximately 12 megabytes of disk space
to install. After site-dependent build, it may require an
additional 4 megabytes to keep the individual object
modules.

- 2 -

Release Notes 6.2 Emacs

7. Changes from Previous Releases

None.

8. Direct Software Support

To obtain copies of SAR forms, call the Software Support
Center and request form number CSD1833B.

- 3 -

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.................................................. 2

7. Changes from Previous Releases............................ 3

8. Direct Software Support................................... 3

- i -

_________________________________________________________________

HARRIS
COMPUTER SYSTEMS
_________________________________________________________________

EMACS
VERSION 6.2

RELEASE NOTES

0891016-6.2

October 1992

_________________________________________________________________

return to index
================================================================================

CX/UX FLOPPY DISK DRIVER AND UTILITIES -
VERSION 6.2
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.

2. Documentation

The following documentation is included with this release:

________________________________________________________________
| Manual Name Pub. Number|
|_________________________________________________|_____________|
| CX/UX Floppy Disk Driver/Utilities Release Notes| 0890386-6.2|
|_________________________________________________|_____________|

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 6.2lities Release Notes

3. Prerequisites

Prerequisites for CX/UX Floppy Disk Driver and Utilities
Version 6.2 are as follows:

3.1 Hardware

o Any Series 4000 or 5000 system.

o An HVME SCSI Adapter (HSA) or an Integral SCSI/Ethernet
(ISE) daughtercard.

3.2 Software

o CX/UX 6.2.

4. Installation

Please refer to the CX/UX System Administration Manual,
Chapter 3, for instructions on software installation.

5. Cautions

None.

6. 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
(ISE). With these drives, the generic floppy disk driver
supports the following IBM-PC compatible media:

- 2 -

Release Notes CX/UX Floppy Disk Driver and Utilities

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

dosput writes a MS-DOS file on the floppy disk
with the data read from stdin

- 3 -

CX/UX Floppy Disk Driver and 6.2lities Release Notes

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. New Features in this Release

None.

8. Changes from Previous Releases

None.

9. Direct Software Support

- 4 -

Release Notes CX/UX Floppy Disk Driver and Utilities

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 Hardware............................................. 2
3.2 Software............................................. 2

4. Installation.............................................. 2

5. Cautions.................................................. 2

6. Features in this Release.................................. 2

7. New Features in this Release.............................. 4

8. Changes from Previous Releases............................ 4

9. Direct Software Support................................... 4

- i -

_________________________________________________________________

HARRIS
COMPUTER SYSTEMS
_________________________________________________________________

CX/UX FLOPPY DISK DRIVER AND UTILITIES
VERSION 6.2

RELEASE NOTES

0890386-6.2

October 1992

_________________________________________________________________

return to index
================================================================================

GDB -
VERSION 6.2
RELEASE NOTES

Harris Computer Systems Division

1. Introduction

Version 4.2 of the Free Software Foundation's GNU Source-
Level Debugger is provided with minor enhancements in use at
Harris Computer Systems Division.

GDB is provided free with CX/UX and is a fully supported
product.

2. Source

Source for either version of GDB is available on request
from Harris. However, only official distributions of GDB
will be supported by Harris. Harris will not support
customer-made changes to GDB.

3. Copyright

GDB is copyrighted by the Free Software Foundation, Inc.
Conditions for redistribution and warranty information may
be found in the GDB General Public License included as part
of this distribution.

4. Documentation

The following documentation is included with this release:

__________

- These release notes cover the following products: gdb

- 1 -

GDB 6.2 Release Notes

_________________________________
| Manual Name Pub. Number|
|__________________|_____________|
| Using GDB | 0890393-000|
| GDB Release Notes| 0890393-6.2|
|__________________|_____________|

5. Prerequisites

Prerequisites for GDB Version 6.2 are as follows:

5.1 Hardware

o Any Series 4000 or 5000 system.

5.2 Software

o CX/UX 6.2

6. Installation

Please refer to the CX/UX System Administration Manual,
Chapter 3, for instructions on software installation.

The source for GDB may be found in /usr/src/cmd/gdb. The
executable is in /usr/bin.

7. Cautions

None.

- 2 -

Release Notes 6.2 GDB

8. New Features for 4.2 Release

This release of GDB incorporates all of the changes made by
the Free Software Foundation between versions 2.8 and 4.2.

9. Changes from Previous Releases

9.1 Renamed Commands

The following commands were renamed in GDB 4.2 in order to
make the command set as a whole more consistent and easier
to use and remember:

- 3 -

GDB 6.2 Release Notes

10. Direct Software Support

To obtain copies of SAR forms, call the Software Support
Center and request form number CSD1833B.

- 4 -

CONTENTS

1. Introduction............................................. 1

2. Source................................................... 1

3. Copyright................................................ 1

4. Documentation............................................ 1

5. Prerequisites............................................ 2
5.1 Hardware............................................ 2
5.2 Software............................................ 2

6. Installation............................................. 2

7. Cautions................................................. 2

8. New Features for 4.2 Release............................. 3

9. Changes from Previous Releases........................... 3
9.1 Renamed Commands.................................... 3

10. Direct Software Support.................................. 4

- i -

_________________________________________________________________

HARRIS
COMPUTER SYSTEMS
_________________________________________________________________

GDB
VERSION 6.2

RELEASE NOTES

0890393-6.2

October 1992

_________________________________________________________________

return to index
================================================================================

GNU MAKE -
VERSION 6.2
RELEASE NOTES

Harris Computer Systems Division

1. Introduction

This is version 3.60 of the Free Software Foundation's GNU
Make tool with minor enhancements. GNU Make is provided
free of charge, in source and object form, to every
customer. It is Class B software and, therefore, is not
supported by Harris.

2. Copyright

GNU Make is copyrighted by the Free Software Foundation.
Conditions for redistribution and warranty information may
be found in the GNU General Public License, which is
included in the documentation provided.

3. Documentation

The following documentation is included with this release:

______________________________________
| Manual Name Pub. Number|
|_______________________|_____________|
| GNU Make Manual | 0890381-000|
| GNU Make Release Notes| 0890381-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

__________

- These release notes cover the following products: gmake

- 1 -

GNU Make 6.2 Release Notes

calls outside of the continental United States, the number
is 1-305-971-6248.

4. Prerequisites

Prerequisites for GNU Make Version 6.2 are as follows:

4.1 Hardware

o Any Series 4000 or 5000 system.

4.2 Software

o CX/UX 6.2

5. Installation

Please refer to the CX/UX System Administration Manual,
Chapter 3, for instructions on software installation.

6. Direct Software Support

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

- 2 -

Release Notes 6.2 GNU Make

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. Copyright................................................. 1

3. Documentation............................................. 1

4. Prerequisites............................................. 2
4.1 Hardware............................................. 2
4.2 Software............................................. 2

5. Installation.............................................. 2

6. Direct Software Support................................... 2

- i -

_________________________________________________________________

HARRIS
COMPUTER SYSTEMS
_________________________________________________________________

GNU MAKE
VERSION 6.2

RELEASE NOTES

0890381-6.2

October 1992

_________________________________________________________________

return to index
================================================================================

GNU MAKE -
VERSION 6.2
RELEASE NOTES

Harris Computer Systems Division

1. Introduction

2. Copyright

3. Documentation

The following documentation is included with this release:

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

__________

- These release notes cover the following products: gmake

- 1 -

GNU Make 6.2 Release Notes

calls outside of the continental United States, the number
is 1-305-971-6248.

4. Prerequisites

Prerequisites for GNU Make Version 6.2 are as follows:

4.1 Hardware

o Any Series 4000 or 5000 system.

4.2 Software

o CX/UX 6.2

5. Installation

Please refer to the CX/UX System Administration Manual,
Chapter 3, for instructions on software installation.

6. Direct Software Support

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

- 2 -

Release Notes 6.2 GNU Make

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. Copyright................................................. 1

3. Documentation............................................. 1

4. Prerequisites............................................. 2
4.1 Hardware............................................. 2
4.2 Software............................................. 2

5. Installation.............................................. 2

6. Direct Software Support................................... 2

- i -

_________________________________________________________________

HARRIS
COMPUTER SYSTEMS
_________________________________________________________________

GNU MAKE
VERSION 6.2

RELEASE NOTES

0890381-6.2

October 1992

_________________________________________________________________

return to index
================================================================================

IEEE 488 -
VERSION 6.2
RELEASE NOTES

Harris Computer Systems Division

1. Introduction

These release notes describe the release of the General
Purpose Interface Bus (GPIB) software. It is based on the
Motorola MVME300 GPIB interface board. The GPIB is a
parallel interface bus that allows up to 31 devices to be
attached to each controller. Devices may talk to each other
or to the controller. Currently, the driver only supports
the MVME300 in controller mode and cannot be used as a
device in slave mode. Features that are supported include:

o Direct DMA to and from memory.

o Talker/Listener functionality in system controller mode
only.

o Serial and parallel polling.

o Local/remote/local lockout modes.

o Service requests.

Refer to the gpib(7) man page for additional information.

2. Documentation

The following documentation is included with this release:

______________________________________
Manual Name Pub. Number

__________

- These release notes cover the following products: gpib

- 1 -

IEEE 488 6.2 Release Notes

|_______________________|_____________|
| IEEE 488 Release Notes| 0890372-6.2|
|_______________________|_____________|

3. Prerequisites

Prerequisites for IEEE 488 Version 6.2 are as follows:

3.1 Hardware

o Any Series 4000 or 5000 system.

3.2 Software

o CX/UX 6.2

4. Installation

4.1 Software

This section documents the setup and installation of GPIB
software. Harris recommends that the procedures described
below be performed by system administrator level personnel.
Consult the CX/UX System Administration manual for
additional information.

4.1.1 Updating_the_Configuration_File

The configuration file contains lines of ASCII text of
possible system and product configurations. To include
product information for the GPIB product, search for the
lines below in your configuration file, and if they do not
exist, add them:

####################################
#
# Motorola MVME 300 driver for GPIB
#

- 2 -

Release Notes 6.2 IEEE 488

####################################
#
#device gpib0 at vba? csr 0xff8600 vector gpibintr
#device gpib1 at vba? csr 0xff8640 vector gpibintr
#device gpib2 at vba? csr 0xff8680 vector gpibintr
#device gpib3 at vba? csr 0xff86c0 vector gpibintr
#device gpib4 at vba? csr 0xff8700 vector gpibintr
#device gpib5 at vba? csr 0xff8740 vector gpibintr
#device gpib6 at vba? csr 0xff8780 vector gpibintr
#device gpib7 at vba? csr 0xff87c0 vector gpibintr

Uncomment only those lines which designate a GPIB board
installed in your system. (The # character denotes the line
as being a comment; deleting the character changes it to an
executable line.)

Next, you will need to reconfigure and relink your kernel.
Consult the CX/UX System Adminstration manual, Chapter 4,
for further instructions.

Note: During the boot process a message displays which GPIB
controllers were found on your system. If the newly
installed controllers are not found, you will need to check
on the hardware installation and jumper settings before
proceeding.

4.1.2 Running_MAKEDEV

The MAKEDEV script-utility uses mknod calls to create
special files that specify major and minor numbers used by
the system to identify GPIB devices. The controllers are
numbered 0 to 7. The devices on each controller are
numbered 0 to 30. MAKEDEV must be run for each controller
configured on your system.

Because each special file is tied to a specific physical
connection, a single device-file will be necessary for each
link. The special files will be named /dev/gpib/xxx, where
xxx is the logical unit number.

To create the GPIB special files the installer must change
(cd) to the /dev directory and type:

MAKEDEV gpibn

where n is the controller number of the GPIB. Following the
successful execution of the above utility, special files
will exist in the /dev/gpib directory. Note: Special files

- 3 -

IEEE 488 6.2 Release Notes

need only be created for controllers that are currently
installed.

Devices are referenced as in the example table below.

/dev/gpib/0d0 ; controller 0 device 0
/dev/gpib/0d1 ; controller 0 device 1
/dev/gpib/0d13 ; controller 0 device 13
/dev/gpib/1d1 ; controller 1 device 1
/dev/gpib/3d20 ; controller 3 device 20

4.2 Hardware

Before installing the MVME 300 board, set it up following
the tables below.

_________________________
| Jumper Settings |
|___|____________________|
| J1| 3-4, 5-6, 7-8 |
|___|____________________|
| J2| 1-2 |
|___|____________________|
| J3| 1-2 |
|___|____________________|
| J4| 1-2 |
|___|____________________|
| J6| 1-2, 3-4, 5-6, 7-8|
|___|____________________|
| J7| 2-3 |
|___|____________________|
| J8| 1-2 |
|___|____________________|
| J9| 2-3 |
|___|____________________|

The controller board address is selected by installing
jumpers on J5, as shown in the following table.

- 4 -

Release Notes 6.2 IEEE 488

_________________________________________________________
| Jumper J5 Address Settings |
|______|______|______|______|____________________________|
| GPIB0| 1-2,| 3-4,| 5-6,| 11-12, 13-14, 15-16, 17-18|
|______|______|______|______|____________________________|
| GPIB1| | 3-4,| 5-6,| 11-12, 13-14, 15-16, 17-18|
|______|______|______|______|____________________________|
| GPIB2| 1-2,| | 5-6,| 11-12, 13-14, 15-16, 17-18|
|______|______|______|______|____________________________|
| GPIB3| | | 5-6,| 11-12, 13-14, 15-16, 17-18|
|______|______|______|______|____________________________|
| GPIB4| 1-2,| 3-4,| | 11-12, 13-14, 15-16, 17-18|
|______|______|______|______|____________________________|
| GPIB5| | 3-4,| | 11-12, 13-14, 15-16, 17-18|
|______|______|______|______|____________________________|
| GPIB6| 1-2,| | | 11-12, 13-14, 15-16, 17-18|
|______|______|______|______|____________________________|
| GPIB7| | | | 11-12, 13-14, 15-16, 17-18|
|______|______|______|______|____________________________|

Set all 8 dip switches to ON.

5. Interface Definitions

5.1 open/close

Devices must be opened before they may be accessed. Each
device can be opened by only one process at a time. When a
process has finished with a device it should be closed, in
order to free the device for another process.

5.2 read/write

Once a device has been opened it can be read from or written
to with the standard read and write calls.

5.3 ioctl()

See the gpib(7) man page for a complete listing of ioctl
commands.

- 5 -

IEEE 488 6.2 Release Notes

6. Cautions

Device reads and writes are restricted to 2048 bytes unless
the application enlarges the buffer size by calling ioctl()
with GPIB_SIZE. Reads or writes larger than the device's
current buffer allocation will be truncated to the current
buffer size. Closing a device resets the buffer size to the
default value.

Non-system controller mode is not supported. The GPIB board
must be the controller at all times. Some non-system
controller functions are included in the driver; their
results are unpredictable.

7. New Features in this Release

None.

8. Changes from Previous Release

None.

9. Appendix A - Sample Code Fragment

/***************************************************
*
* Test read and write functions on an Iotech 488 analyzer
* Iotech should be in device simulator mode.
* Displays test loops completed on Iotech.
* Test runs until killed.
* map 6/1/90
*
****************************************************/

#include
#include
#include
#include
#include

int fd;
int ctlr = -1, device = -1;
int stat, i, ret, mm, count;
char str[88];
char *out = "D/ 0/\r";

- 6 -

Release Notes 6.2 IEEE 488

char arg;
char *test[32];
char term = '\r';

main(argc,argv)
int argc;
char **argv;
{

if ( argc < 3 ) usage();
ctlr = atoi(argv[1]);
device = atoi(argv[2]);
if ( ctlr < 0 || ctlr > 7 || device < 0 || device > 30 ) usage();

/** initialize arrays **/

for ( i = 0; i < 32; i++ ) test[i] = (char *)malloc(80);

printf("IoTech Test on controller %d, device %d.0,ctlr,device);

sprintf(str,"/dev/gpib/%dd%d",ctlr,device);

if ((fd=open(str,O_RDWR)) < 0) {
perror("open") ;
printf("open error on %s.\n",str);
exit(0);
}

if ((stat = ioctl(fd, GPIBSETEOS, &term)) < 0) {
perror( "GPIBSETEOS");
exit(1);
}

/** double buffer size to 4K for the fun of it **/

*term = 4096;

if ((stat = ioctl(fd, GPIB_SIZE, &term)) < 0) {
perror( "GPIB_SIZE");
exit(1);
}

/** tell device what we want to read **/

ret = write(fd,"W0X",3);
if ( ret == 3 ) ret = write(fd,"G0X",3);
if ( ret == 3 ) ret = write(fd,"I44X",4);
if ( ret == 4 ) ret = write(fd,"H4X",3);
if ( ret != 3 ) {

- 7 -

IEEE 488 6.2 Release Notes

printf("Write failed.\n");
exit(1);
}

/** read in test patterns **/

mm = 0;
do {
ret = read(fd,test[mm], 27);
test[mm][27] = 0;
mm++;
} while ( ret == 27 && mm < 32 );

if ( ret != 27 ) {
printf("Read failed.\n");
exit(1);
}

/** now continue looping forever **/

count = 1;
do {

ret = write(fd,"W0X",3);
if ( ret == 3 ) ret = write(fd,"G0X",3);
if ( ret == 3 ) ret = write(fd,"I44X",4);
if ( ret == 4 ) ret = write(fd,"H4X",3);
if ( ret != 3 ) {
printf("Write failed.\n");
exit(1);
}

mm = 0;
do {
ret = read(fd,str,27);
str[27] = 0;
if ( strcmp(test[mm],str) || ret != 27 ) {
printf("Read %ld Failed !\n",count);
printf("Test value [%s]\n",test[mm]);
printf("Read value [%s]\n",str);
exit(1);
}
mm++;
} while ( mm < 32 );

/** increment display **/

inc_count(21);
ret = write(fd,out,24);

- 8 -

Release Notes 6.2 IEEE 488

if ( ret != 24 ) {
printf("Write failed.\n");
exit(1);
}

} while ( 1 );

close(fd);
}

inc_count(i)
int i;
{

if ( i < 2 ) return; /* overflow */

if ( out[i] == ' ' ) out[i] = '0'; /* added a digit */

if ( out[i] != '9' ) {
out[i]++;
return;
}
else {
out[i] = '0';
inc_count(i-1);
}

}

usage()
{
printf("usage: tech controller device\n");
printf("controller 0..7, device 0..30\n");
exit(1);
}

10. Direct Software Support

- 9 -

IEEE 488 6.2 Release Notes

To obtain copies of SAR forms, call the Software Support
Center and request form number CSD1833B.

- 10 -

CONTENTS

1. Introduction............................................. 1

2. Documentation............................................ 1

3. Prerequisites............................................ 2
3.1 Hardware............................................ 2
3.2 Software............................................ 2

4. Installation............................................. 2
4.1 Software............................................ 2
4.1.1 Updating the Configuration File.............. 2
4.1.2 Running MAKEDEV.............................. 3
4.2 Hardware............................................ 4

5. Interface Definitions.................................... 5
5.1 open/close.......................................... 5
5.2 read/write.......................................... 5
5.3 ioctl()............................................. 5

6. Cautions................................................. 6

7. New Features in this Release............................. 6

8. Changes from Previous Release............................ 6

9. Appendix A - Sample Code Fragment........................ 6

10. Direct Software Support.................................. 9

- i -

_________________________________________________________________

HARRIS
COMPUTER SYSTEMS
_________________________________________________________________

IEEE 488
VERSION 6.2

RELEASE NOTES

0890372-6.2

October 1992

_________________________________________________________________

return to index
================================================================================

NIGHT HAWK GS-1 GRAPHICS SUBSYSTEM -
VERSION 6.2
RELEASE NOTES

Harris Computer Systems Division

1. Introduction

The Night Hawk GS-1 Graphics Subsystem is a complete package
of software, hardware, and documentation that provides
everything necessary for a user to create and run graphics-
based applications.

These release notes cover release 6.2 of the Night Hawk GS-1
Graphics Subsystem which is supported on CX systems running
version CX/UX 6.2.

2. Documentation

The following documentation is included with this release:

________________________________________________________________
| Manual Name Pub. Number|
|_________________________________________________|_____________|
| Night Hawk GS-1 Graphics Subsystem Release Notes| 0890358-6.2|
| Night Hawk GS-1 Graphics Subsystem Notes | 0890358-000|
| The Lib Shell VG-Series-1 Supplemental Manual | 0890359-000|
| The Lib Shell Command Reference Manual | 0890359-000|
| The Lib Shell Programmer's Manual | 0890359-000|
|_________________________________________________|_____________|

__________

- These release notes cover the following products: gs

- 1 -

Nighthawk GS-1 Graphics Subsy6.2m 1 Release Notes

1-305-971-6248.

3. Prerequisites

Prerequisites for Nighthawk GS-1 Graphics Subsystem 1
Version 6.2 are as follows:

3.1 Hardware

o Any Series 4000 system.

3.2 Software

o CX/UX, CX/RT, CX/SX 6.2 or later

4. Installation

Please refer to the Night Hawk GS-1 Graphics Subsystem
Notes, Chapter 2, for instructions on software installation.
See the appropriate System Installation Manual for your CPU
for detailed hardware instructions and also the Shippable
Drawings Package No. 1120041-903 distributed with the
product.

5. Cautions

None.

6. New Features in this Release

None.

7. Changes from Previous Releases

None.

- 2 -

Release Notes Nighthawk GS-1 Graphics Subsystem 1

8. Direct Software Support

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. New Features in this Release.............................. 2

7. Changes from Previous Releases............................ 2

8. Direct Software Support................................... 3

- i -

_________________________________________________________________

HARRIS
COMPUTER SYSTEMS
_________________________________________________________________

NIGHT HAWK GS-1 GRAPHICS SUBSYSTEM
VERSION 6.2

RELEASE NOTES

0890358-6.2

October 1992

_________________________________________________________________

return to index
================================================================================

CX/UX HC C -
VERSION 6.2
RELEASE NOTES

Harris Computer Systems Division

1. Introduction

CX/UX hc C 6.2 is the Harris ANSI C compiler for Series 4000
and Series 5000 systems. The hc compiler accepts the C
language as defined by Kernighan and Ritchie, nearly all of
the traditional UNIX extensions to this definition, and all
of the features of the ANSI C standard. On Series 4000 and
Series 5000 systems, the hc compiler is also known as cc.

2. Documentation

The following documentation is included with this release:

_______________________________________________
| Manual Name Pub. Number|
|________________________________|_____________|
| CX/UX Harris C Reference Manual| 0891019-040|
| CX/UX hc C Release Notes | 0891019-6.2|
| C A Reference Manual | 0890378-000|
|________________________________|_____________|

Additional copies may be ordered by contacting the Harris
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.

__________

- These release notes cover the following products: hc

- 1 -

CX/UX hc C 6.2 Release Notes

3. Prerequisites

Prerequisites for CX/UX hc C Version 6.2 are as follows:

3.1 Hardware

o Any Harris Night Hawk Series 4000 or Series 5000 system

3.2 Software

o CX/UX 6.2

4. Installation

Please refer to the CX/UX System Administration Manual,
Chapter 3, for instructions on software installation.

5. Cautions

o The hc 6.2 C compiler will generate code that runs on
both the Series 4000 and the Series 5000 Harris Night
Hawk computers. The 88110 processor used in the Series
5000 can reorder loads and stores of different memory
locations; use the -Qsync_volatile compiler option
should be used when compiling applications for the
Series 5000 which might depend on the ordering of loads
from and stores to memory. One example of such an
application is a device driver for which a load will
change the state of the device.

o The extent to which the hc compiler accepts the C
language as defined by the ANSI C standard as well as
defined by the first edition of Kernighan and Ritchie
is controlled by command line options. See the
discussion of compilation modes in this document and in
hc(1) for an explanation of how hc will treat specific
C language features.

o Certain incorrect C constructs (as defined by Kernighan
and Ritchie), which are accepted by pcc-based
compilers, may not be accepted by hc. Correctly-
written programs will compile without problems.

- 2 -

Release Notes 6.2 CX/UX hc C

o Users are encouraged to retain the source for their
applications. Major releases may provide new object
file formats, which require the recompilation of
programs.

6. Changes from Previous Releases

The following changes from past releases of hc should be
noted.

6.1 Preprocessor Changes

In past releases, the hc compiler used an internal
preprocessor rather than invoking a separate preprocessing
pass with cpp(1). The current release of hc always makes
use of a separate preprocessing pass either with cpp(1) or
with the new ANSI C preprocessor. This introduces the
following incompatibilities with preprocessing extensions
supported by the Harris hc compiler bundled with CX/UX 5.3:

o The sizeof() operator may no longer be used in
conditional compilation expressions (#if expressions).
This practice was never considered to be portable C.

o The #savetable, #loadtable, #pragma push, #pragma pop,
and #pragma optimization directives are no longer
supported.

o The #array_expand Harris-specific directive is no
longer supported.

o The compiler now treats the arguments to #pragma as a
sequence of C tokens. In the past these were treated as
a character string and divided into tokens according to
rules that were unique to each #pragma directive. This
change should make the behavior of pragmas more
consistent. For example, all pragmas that accept
numeric arguments will now accept C hex and octal
constants as well as decimal constants.

o #pragma must be used with all Harris-specific
directives when the compiler is run in ANSI C
conforming mode (-Xc option)

Note that the Harris #error directive (used to control
the printing of some error messages) has a name

- 3 -

CX/UX hc C 6.2 Release Notes

conflict with the ANSI C #error directive (causes the
compilation to terminate while printing the user-
specified diagnostic message), so #pragma error should
always be used when the Harris version is desired.

The use of the external preprocessors has fixed the
following problems with the past release of hc.

o Macros are now correctly expanded in #include
directives.

o Certain cases of token-splicing macros that failed with
the internal preprocessor now work in Old mode (though
typically not in the ANSI C compilation modes).

6.2 Listing Option Changes

The format of hc compiler-generated listings (-QP option)
has changed. Page headers have a different layout than in
past releases. The use of the external preprocessors forces
some changes in the presentation of macro (-QPX) and include
(-QPa) file expansions (minor variations will be noticed
depending on the compilation mode). The following #pragma
listing control directives are no longer supported:
expandinclude, expandmacro, ident, linelength, list, page,
search, title.

6.3 Problems Fixed With This Release

The following errors in previous releases of hc have been
corrected:

o The use of incomplete types in struct and union fields
is now diagnosed.

o The -Qocs option would cause linking to fail if the -X
option was used without any -L options.

o The -P option would cancel out the -g option. Now the
combination of -P and -g produces a preprocessed file
with line-number information included.

o If a single compilation included too many distinct
include files, the compiler would abort with a core
dump.

- 4 -

Release Notes 6.2 CX/UX hc C

7. Future Considerations

The 6.3 C compiler release will follow within three months
of the first customer shipment of Night Hawk Series 5000
computers. The 6.3 compilers will take advantage of the
88110's extended floating-point register set, do instruction
scheduling optimized for the 88110, and take advantage of
some new string operations in an enhanced C library. The
6.3 compiler will have three target options:

-Qtarget=M88100, -Qtarget=M88110, and -Qtarget=M88110compat.

A preprocessor macro is defined according to the compilation
target. M88100 is the default target for compilation on a
Series 4000. M88110 is the default target for compilation
on a Series 5000.

___________________________________________________________________________
| Target | Macro | Compile for| Schedule for| String library|
|_____________|______________|_____________|______________|________________|
| M88100 | M88100 | 88100 | 88100 | 88100 |
| M88110 | M88110 | 88110 | 88110 | 88110 |
| M88110compat| M88110COMPAT| 88100 | 88110 | 88100 |
|_____________|______________|_____________|______________|________________|

To provide for conditional compilation based on the target
platform, the 6.2 C compiler accepts these target options
and defines the corresponding macros, but does not make the
compilation or string library changes.

As part of Harris' commitment to standards, it can be
expected that in a future release of hc the default
compilation mode will change from Old (traditional) mode to
ANSI C mode. A final decision has not been made as to when
this might occur, but customers should plan for the
conversion of their source for ANSI-C compatibility.

8. Direct Software Support

- 5 -

CX/UX hc C 6.2 Release Notes

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.................................................. 2

6. Changes from Previous Releases............................ 3
6.1 Preprocessor Changes................................. 3
6.2 Listing Option Changes............................... 4
6.3 Problems Fixed With This Release..................... 4

7. Future Considerations..................................... 5

8. Direct Software Support................................... 5

- i -

_________________________________________________________________

HARRIS
COMPUTER SYSTEMS
_________________________________________________________________

CX/UX HC C
VERSION 6.2

RELEASE NOTES

0891019-6.2

October 1992

_________________________________________________________________

return to index
================================================================================

HARRIS EDITOR (HED) -
VERSION 6.2
RELEASE NOTES

Harris Computer Systems Division

1. Introduction

The Harris Editor (HED) is a full screen editor with
features that include:

o Easy text editing

o Multiple file editing

o Scrolling, and

o Support for various terminals via terminfo(4).

2. Documentation

The following documentation is included with this release:

______________________________________________
| Manual Name Pub. Number |
|___________________________|_________________|
| Harris Editor User's Guide| 0891000-101 |
| Hed Keyboard Aid | 866-6650010-001|
| Hed Release Notes | 0891000-6.2 |
|___________________________|_________________|

__________

- These release notes cover the following products: hed

- 1 -

Harris Editor (HED) 6.2 Release Notes

1-305-971-6248.

3. Prerequisites

Prerequisites for Harris Editor (HED) Version 6.2 are as
follows:

3.1 Hardware

o Any Series 4000 or 5000 system.

3.2 Software

o CX/UX 6.2

4. Installation

Please refer to the CX/UX System Administration Manual,
Chapter 3, for instructions on software installation.

5. Cautions

None

6. New Features in this Release

None

7. Changes from Previous Releases

None

- 2 -

Release Notes 6.2 Harris Editor (HED)