NEOHAPSIS - Peace of Mind Through Integrity and Insight

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com

Neohapsis > Archives > IBM AIX Digests> 2002-q2

From: AIX Service Mail Server (aixservaustin.ibm.com)
Date: Fri Apr 26 2002 - 01:32:21 CDT

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 4//EN">
<HTML><HEAD>
<TITLE>Release Notes</TITLE>









<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META HTTP-EQUIV="updated" CONTENT="Fri, 08 Mar 2002 08:10:59">
<META HTTP-EQUIV="review" CONTENT="Sat, 08 Mar 2003 08:10:59">
<META HTTP-EQUIV="expires" CONTENT="Mon, 08 Mar 2004 08:10:59">
</HEAD><BODY>

<A NAME="Top_Of_Page"></A>
<H1>Release Notes</H1>
AIX Version 4.3.3<BR>
Release Notes<BR>
<P>Document Number GI10-0697-09
<BR><TABLE BORDER WIDTH="100%"><TR><TH ALIGN="LEFT">Note</TH><TR><TD>
<P>Before using this information and the product it supports, read the
information in <A HREF="#HDRNOTICES">Appendix A, Notices</A>.</TD></TR></TABLE>
<P><B>Tenth Edition (April 2002)</B>
<P><B>(C) Copyright International Business Machines Corporation 2001. All rights reserved.</B> <BR>U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
<HR><H1><A NAME="MTOC">Contents</A></H1>
<P><B><A NAME="MTOC_1" HREF="#MTOC">Contents</A></B><BR>
<P><B><A NAME="MTOC_2" HREF="#Header_2">AIX Version 4.3.3 Release Notes</A></B><BR>
<MENU>
<LI><A NAME="MTOC_3" HREF="#Header_3">Introduction</A>
<MENU>
<LI><A NAME="MTOC_4" HREF="#Header_4">AIX Version 4.3.3 Installation Documentation</A>
<LI><A NAME="MTOC_5" HREF="#Header_5">Hardware Documentation</A>
<LI><A NAME="MTOC_6" HREF="#Header_6">README Files</A>
<LI><A NAME="MTOC_7" HREF="#Header_7">Other Sources of Information</A>
<LI><A NAME="MTOC_10" HREF="#Header_10">How to Get Help and Report Problems</A>
</MENU>
<LI><A NAME="MTOC_11" HREF="#Header_11">Listing and Previewing Installation Software</A>
<MENU>
<LI><A NAME="MTOC_12" HREF="#Header_12">Listing and previewing software from the command line:</A>
<LI><A NAME="MTOC_13" HREF="#Header_13">Listing and previewing software from the ASCII SMIT interface:</A>
<LI><A NAME="MTOC_14" HREF="#Header_14">Listing and previewing software from the Web-based System Manager interface:</A>
</MENU>
<LI><A NAME="MTOC_15" HREF="#Header_15">Installation</A>
<MENU>
<LI><A NAME="MTOC_16" HREF="#Header_16">Installing AIX Version 4.3.3</A>
<LI><A NAME="MTOC_17" HREF="#Header_17">Installing AIX Version 4.3.3 on an Existing AIX Version 4.3 System</A>
<LI><A NAME="MTOC_22" HREF="#Header_22">Memory Requirements</A>
<LI><A NAME="MTOC_23" HREF="#Header_23">Initial Paging Space Requirements</A>
<LI><A NAME="MTOC_24" HREF="#Header_24">Disk Space Requirements</A>
<LI><A NAME="MTOC_25" HREF="#Header_25">Multiple Volume CD-ROMs</A>
<LI><A NAME="MTOC_26" HREF="#Header_26">Network Installation Management (NIM) Enhancements - AIX 4.3.3</A>
<LI><A NAME="MTOC_27" HREF="#Header_27">Other Installation Information</A>
<LI><A NAME="MTOC_40" HREF="#Header_40">Migration</A>
</MENU>
<LI><A NAME="MTOC_51" HREF="#Header_51">Base Operating System (BOS)</A>
<MENU>
<LI><A NAME="MTOC_52" HREF="#Header_52">AutoFS Compatibility</A>
<LI><A NAME="MTOC_53" HREF="#Header_53">Logical Volume Manager (LVM) Enhancements</A>
<LI><A NAME="MTOC_54" HREF="#Header_54">wlmcntrl Command Correction</A>
<LI><A NAME="MTOC_55" HREF="#Header_55">Print Subsystem Changes</A>
<LI><A NAME="MTOC_56" HREF="#Header_56">Parallel Printer Cable Selection</A>
<LI><A NAME="MTOC_57" HREF="#Header_57">man Command</A>
<LI><A NAME="MTOC_58" HREF="#Header_58">New Flag for the sar Command</A>
<LI><A NAME="MTOC_59" HREF="#Header_59">shutdown Command</A>
<LI><A NAME="MTOC_60" HREF="#Header_60">lsps Command</A>
<LI><A NAME="MTOC_61" HREF="#Header_61">chnlspath Command</A>
<LI><A NAME="MTOC_65" HREF="#Header_65">lsnlspath Command</A>
</MENU>
<LI><A NAME="MTOC_69" HREF="#Header_69">Communications, Networking and I/O</A>
<MENU>
<LI><A NAME="MTOC_70" HREF="#Header_70">gated Compatibility</A>
<LI><A NAME="MTOC_71" HREF="#Header_71">7135 RAIDiant Array for AIX requirements (when upgrading to AIX 4.3)</A>
<LI><A NAME="MTOC_72" HREF="#Header_72">Interface Specific Network Options (ISNO)</A>
<LI><A NAME="MTOC_73" HREF="#Header_73">inetd.conf Migration</A>
<LI><A NAME="MTOC_74" HREF="#Header_74">Network Terminal Accelerator</A>
<LI><A NAME="MTOC_75" HREF="#Header_75">System Networking, Analysis and Performance Pilot (SNAPP)</A>
<LI><A NAME="MTOC_76" HREF="#Header_76">TCP Selective Acknowledgement (SACK)</A>
<LI><A NAME="MTOC_77" HREF="#Header_77">DVD-RAM Drive Support</A>
</MENU>
<LI><A NAME="MTOC_78" HREF="#Header_78">Graphics</A>
<MENU>
<LI><A NAME="MTOC_79" HREF="#Header_79">X11R5/X11R6.3 Compatibility Issues On AIX Version 4.3</A>
<LI><A NAME="MTOC_80" HREF="#Header_80">graPHIGS for AIX 4.3</A>
<LI><A NAME="MTOC_81" HREF="#Header_81">Ultimedia Services for AIX</A>
</MENU>
<LI><A NAME="MTOC_82" HREF="#Header_82">Documentation</A>
<MENU>
<LI><A NAME="MTOC_83" HREF="#Header_83">Installation and Configuration</A>
<LI><A NAME="MTOC_92" HREF="#Header_92">InfoExplorer</A>
</MENU>
<LI><A NAME="MTOC_93" HREF="#Header_93">WLM Commands</A>
<MENU>
<LI><A NAME="MTOC_94" HREF="#Header_94">wlmassign Command</A>
<LI><A NAME="MTOC_98" HREF="#Header_98">wlmset Command</A>
</MENU>
<LI><A NAME="MTOC_103" HREF="#HDROPTIONAL_JLP">Optional Software</A>
<MENU>
<LI><A NAME="MTOC_104" HREF="#Header_104">Viewing Information about Optional Software</A>
<LI><A NAME="MTOC_105" HREF="#Header_105">Installing NetWare</A>
<LI><A NAME="MTOC_106" HREF="#Header_106">SecureWay Directory V3.1.1 Lightweight Directory Access Protocol (LDAP)</A>
<LI><A NAME="MTOC_110" HREF="#Header_110">Communications Server</A>
<LI><A NAME="MTOC_111" HREF="#Header_111">X.25 Migration and Configuration</A>
<LI><A NAME="MTOC_114" HREF="#Header_114">DCE/DFS Migration to AIX Version 4.3</A>
<LI><A NAME="MTOC_115" HREF="#Header_115">Tivoli Management Agent (TMA), Version 3.2</A>
<LI><A NAME="MTOC_118" HREF="#Header_118">Soft5080</A>
<LI><A NAME="MTOC_119" HREF="#Header_119">Perl</A>
</MENU>
<LI><A NAME="MTOC_120" HREF="#Header_120">Service</A>
<MENU>
<LI><A NAME="MTOC_121" HREF="#Header_121">Electronic Fix Distribution for AIX</A>
<LI><A NAME="MTOC_123" HREF="#Header_123">Problem Solving Databases for AIX</A>
</MENU></MENU>
<P><B><A NAME="MTOC_124" HREF="#HDRNOTICES">Appendix A. Notices</A></B><BR>
<MENU>
<LI><A NAME="MTOC_125" HREF="#Header_125">Trademarks</A>
</MENU><P>
<HR><H1><A NAME="Header_2" HREF="#MTOC_2">AIX Version 4.3.3 Release Notes</A></H1>
<HR><H2><A NAME="Header_3" HREF="#MTOC_3">Introduction</A></H2>
<P>AIX 4.3.3 Release Notes contains information that will aid
you in the installation and migration to AIX 4.3.3. For
information about new function for AIX 4.3.3, visit the RS/6000
software web page at:
<PRE>http://www.rs6000.ibm.com/software
</PRE>
<P>For information on new, changed, or removed function that was not available
at the time of publication of the AIX documentation, and for additional
information not documented in other publications, refer to the AIX
4.3.3 README at <B>/usr/lpp/bos/README</B> or view the
README in an HTML format at <B>/usr/lpp/bos/README.htm</B>.
<P>Some of the installation instructions in this document assume knowledge
of:
<UL>
<LI>AIX system administration commands
</LI><LI>System Management Interface Tool (SMIT)
</LI><LI>Software installation operations, such as <I>apply</I> and
<I>commit</I>
</LI></UL>
<P><H3><A NAME="Header_4" HREF="#MTOC_4">AIX Version 4.3.3 Installation Documentation</A></H3>
<P>Documentation is available only online except for <I>Installation
Guide</I>, which is available both online and in hardcopy.
<P>See the following web site for AIX Version 4.3.3
documentation:
<PRE>http://www.rs6000.ibm.com/cgi-bin/ds_form
</PRE>
<P>To order the <I>Installation Guide</I> book, contact your point of
sale, or, in the U.S., call IBM Customer Publication Support at
1-800-879-2755. Specify order number SC23-4112.
<P>The following publications describe AIX Version 4.3.3
installation:
<UL>
<LI><I>Installation Guide</I>, order number SC23-4112
</LI><LI><I>Network Installation Management Guide and Reference</I>, available
only online
</LI></UL>
<P><H3><A NAME="Header_5" HREF="#MTOC_5">Hardware Documentation</A></H3>
<P>Hardware documentation is available on the Web or can be ordered in printed
hardcopy.
<P>To access the hardware documentation on the Web, go to:
<PRE>http://www.ibm.com/servers/eserver/pseries/library/hardware_docs
</PRE>
<P>Installation, use, and service documentation is available from this Web
site. To order printed versions of the books that are available in
hardcopy, go to:
<PRE>http://www.ibm.com/shop/publications/order
</PRE>
<P><H3><A NAME="Header_6" HREF="#MTOC_6">README Files</A></H3>
<P>For information on how to view the README files for base operating system
(BOS) software and optional software products, refer to the <I>Installation
Guide</I>, SC23-4112.
<P>Some README files are shipped in separate directories that are not
accessible if you follow the procedure described in the <I>Installation
Guide</I>. To find the README files installed on your machine, use
the following command:
<PRE>find /usr -name "*README*" -print
</PRE>
<P>These notes should be used in conjunction with the AIX Version 4.3
Installation documentation.
<P><H3><A NAME="Header_7" HREF="#MTOC_7">Other Sources of Information</A></H3>
<P><H4><A NAME="Header_8">Installation Hints and Tips</A></H4>
<P>The latest AIX 4.3.3 installation hints and tips can be
obtained from:
<UL>
<LI><B>The IBM FAX Information Server </B>
<P>Call 800-IBM-4FAX in the U.S. from any touch-tone telephone,
or 415-855-4329 worldwide from your FAX machine, and request document number
8175.
</LI><LI><B>The AIX Service Mail Server </B>
<P>Send electronic mail with a subject of <B>43_Install_Tips</B> to
<I>aixservaustin.ibm.com</I>.
</LI></UL>
<P><H4><A NAME="Header_9">Optional Software Information</A></H4>
<P>Licensed programs include AIX 4.3.3 and optionally purchased
products. Each program can have one or more separately installable
filesets. The <I>Package Installation Database for Current
Media</I> is an HTML database which contains information about the contents
of these separately installable filesets. See <A HREF="#HDROPTIONAL_JLP">Optional Software</A> for instructions on viewing this online database.
<P><H3><A NAME="Header_10" HREF="#MTOC_10">How to Get Help and Report Problems</A></H3>
<P>To report code-related problems, contact the Program Services
representative for your area.
<HR><H2><A NAME="Header_11" HREF="#MTOC_11">Listing and Previewing Installation Software</A></H2>
<P>You can list the available software products, packages, and filesets on AIX
media. This media can be a CD-ROM, tape, diskette, or directory.
The output lists the available packages and filesets on the media. The
descriptions are provided at the fileset level.
<P>You can choose to do a preview installation before performing the acutal
installation. A preview installation provides the preinstallation
information that will occur during a regular installation, however no software
will actually be installed.
<P>When you select a package or fileset to be installed with the preview
installation process, you will see a list that contains all the requisite
packages and filesets needed by the selected package or fileset to be
successfully installed.
<P>The other information generated during the preinstallation process concerns
file system size checking. The file systems are checked to make sure
there is enough free space available to install the selected package or
fileset.
<P>You can run the list software and previewing software functions from the
command line, the SMIT interface, or the Web-based System Manager
interface.
<P><H3><A NAME="Header_12" HREF="#MTOC_12">Listing and previewing software from the command line:</A></H3>
<OL TYPE=1>
<LI>Log in as the root user.
</LI><LI>List the available software on the media using <B>installp
-ld</B><B><I>device</I></B>. For example, to list the software on the
first CD of the base media, insert the Volume 1 CD in the first CD
drive. Then enter:
<PRE>installp -ld /dev/cd0 | pg
</PRE>This will display output in the following form:
<PRE> Fileset Name Level
  ==========================================
  IMNSearch.bld.DBCS 2.3.1.0
# NetQuestion DBCS Buildtime Modules

    IMNSearch.bld.SBCS 2.3.1.0
# NetQuestion SBCS Buildtime Modules

...
</PRE>
</LI><LI>To do a preview installation from the command line, use the <B>-p</B>
flag with the <B>installp</B> command. For example, to preview the
installation of the <B>IMNSearch.bld.DBCS</B> fileset,
type:
<PRE>installp -aXgq -p -d/dev/cd0 IMNSearch.bld.DBCS
</PRE>The preview option shows the filesets selected to be installed, the
filesets that will be pulled in by requisites, and the system resources that
will be used by this <B>installp</B> operation.
</LI></OL>
<P><H3><A NAME="Header_13" HREF="#MTOC_13">Listing and previewing software from the ASCII SMIT interface:</A></H3>
<OL TYPE=1>
<LI>Log in as the root user.
</LI><LI>List available software on media using <B>smitty
install_update</B>.
</LI><LI>Select <B>Install Software</B>.
</LI><LI>Press the F4 key to list the available input devices and select the
appropriate one; or type the input device name in the blank field.
Press Enter to continue.
</LI><LI>To list all available software on the selected media, press the F4 key on
the <B>SOFTWARE to Install</B> field.
</LI><LI>Scroll through the list of software by using the arrow keys or the Page Up
or Page Down keys.
<DL><DT><B>Note:</B></DT><DD>The software shown in this listing are the available packages and filesets
for that software product. For example, in the following output
example, the software product is IMNSearch.
<PRE>IMNSearch.bld
  + 2.3.1.0 NetQuestion DBCS Buildtime Modules
  + 2.3.1.0 NetQuestion SBCS Buildtime Modules

IMNSearch.rte.httpdlite
2.0.0.2 Lite NetQuestion Local Web Server
</PRE>The two packages are IMNSearch.bld and
IMNSearch.rte.httpdlite. The filesets in the
IMNSearch.bld package are the NetQuestion DBCS Buildtime Modules
fileset and the NetQuestion SBCS Buildtime Modules fileset. Both
filesets are at the 2.3.1.0 level. Notice that the
descriptions for the software product are described at the fileset
level.
<P>If the fileset is preceded by a + (plus sign), then it is available to be
installed. If the fileset is preceded by an (at sign), then the
fileset is already installed at the level shown or later.
</DD></DL>
</LI><LI>Select the package or fileset you wish to install by scrolling to that
package or fileset, and pressing the F7 key to make the selection.
Press enter to continue.
</LI><LI>To do a preview installation of the package or fileset that you selected,
press the Tab key to select <B>yes</B> in the <B>PREVIEW only?</B>
field. Press Enter.
<DL><DT><B>Note:</B></DT><DD>To obtain detailed information about the installation, select <B>yes</B>
in the <B>DETAILED output?</B> field. The filesets being installed
are displayed in parentheses.
</DD></DL>
</LI></OL>
<P><H3><A NAME="Header_14" HREF="#MTOC_14">Listing and previewing software from the Web-based System Manager interface:</A></H3>
<OL TYPE=1>
<LI>Log in as the root user.
</LI><LI>To initialize the environment, run <B>wsm &</B> at the command
prompt.
</LI><LI>After the <B>Launch Pad</B> is running, double click on the
<B>Software</B> icon
</LI><LI>At the top of the <B>Software</B> window in the menu bar, select
<B>Software</B> to display the <B>Software</B> menu.
</LI><LI>Select <B>New Software</B> (<B>Install/Update</B>).
</LI><LI>Select <B>Install Additional Software</B>.
</LI><LI>Specify or select a software source.
</LI><LI>To list available software, click the <B>Browse</B> button To display
a tree view of all the software on the media. The tree can be expanded
by clicking the + (plus sign) to the left of the icon.
<DL><DT><B>Note:</B></DT><DD>If the software is already installed, you will see a small checkmark to the
left of the fileset description.
</DD></DL>
</LI><LI>Select the package or fileset you want to install by highlighting the
package or fileset.
<DL><DT><B>Note:</B></DT><DD>You can select multiple packages or filesets by holding down the left mouse
button while on one selection and dragging the mouse pointer up or
down.
<P>You can also use the Ctrl key or the Shift key to select multiple
items. Hold the Ctrl key while making your selections with the left
mouse button to choose nonconsecutive selections.Hold the Shift key
while making your selections with the left mouse button to choose consecutive
selections.
</DD></DL>
</LI><LI>To do a preview installation of the selected package or fileset, press the
<B>Preview</B> button.
</LI></OL>
<P>Additional information about AIX-supported products is available from the
following Web site:
<PRE>http://www.ibm.com/servers/aix/products/ibmsw
</PRE>
<HR><H2><A NAME="Header_15" HREF="#MTOC_15">Installation</A></H2>
<P>This section contains information about installing AIX Version
4.3.3 that supplements the information contained in the AIX
Version 4.3 Installation documentation. Refer to the
publications listed in "AIX Version 4.3.3 Installation
Documentation" for complete installation instructions.
<P><H3><A NAME="Header_16" HREF="#MTOC_16">Installing AIX Version 4.3.3</A></H3>
<DL><DT><B>Note:</B></DT><DD>If your system is at AIX 4.3.0 or later, proceed to the next
section.
</DD></DL>
<P>There are three ways to install AIX Version 4.3.3:
<UL>
<LI>Complete overwrite installation
</LI><LI>Preservation installation
</LI><LI>Migration installation
</LI></UL>
<P>Boot from the product media and follow instructions in the <I>AIX Version
4.3 Installation Guide</I>, SC23-4112. It is recommended that
you do a migration installation, if you are upgrading from a previous release
of AIX. If you use preservation installation, some configuration
information will not be saved. See the Migration section for more
information about migration installations.
<P>The AIX Version 4.3.3 product media cannot be used to boot a
system with more than 64 GB of memory. Before upgrading your hardware
configuration to have more than 64 GB of memory, you must install the updates
on the 10/2000 (or later) AIX Update CD. You should make a system
backup with the <B>mksysb</B> command of the system after installing the
updates for system recovery, if necessary.
<P><H3><A NAME="Header_17" HREF="#MTOC_17">Installing AIX Version 4.3.3 on an Existing AIX Version 4.3 System</A></H3>
<OL TYPE=1>
<LI>Update all additional currently installed software to the latest
levels. Type the following on the command line and accept the default
menu values:
<PRE>smit update_all
</PRE>
</LI><LI>If you updated from a Version 4.3.0 system,
<B>reboot</B> immediately.
<P>If you updated from a Version 4.3.1 or 4.3.2
system, <B>reboot</B> as soon as possible.
<PRE>shutdown -rF
</PRE>
</LI></OL>
<P><H4><A NAME="Header_18">Recovery From Failed Upgrades with CD-ROM Media</A></H4>
<P>If you upgraded using a CD-ROM device, the Pre-installation Failure/Warning
Summary may have the following text:
<PRE>Not found on the installation media
</PRE>
<P>If so, unmount the CD, and repeat the <B>update_all</B> step.
<P>Use the following steps:
<OL TYPE=1>
<LI>Run the mount command to determine the mount point for the CD-ROM.
For example:
<PRE># mount
  node mounted mounted over vfs date options
-------- --------------- --------------- ------ ------------ ---------------
          /dev/hd4 / jfs Mar 23 13:04 rw,log=/dev/hd8
          /dev/hd2 /usr jfs Mar 23 13:04 rw,log=/dev/hd8
          /dev/hd9var /var jfs Mar 23 13:04 rw,log=/dev/hd8
          /dev/hd3 /tmp jfs Mar 23 13:04 rw,log=/dev/hd8
          /dev/hd1 /home jfs Mar 23 13:05 rw,log=/d ev/hd8
          /dev/cd0 /.cd_fRlNMc cdrfs Mar 24 09:15 ro
</PRE>
</LI><LI>Unmount the CD-ROM. For example:
<PRE># umount /.cd_fRlNMc
</PRE>
</LI><LI>Reinvoke the <B>update_all</B> with the CD-ROM as the INPUT
device. For example:
<PRE>smit update_all
</PRE>
</LI></OL>
<P><H4><A NAME="Header_19">Updating from the AIX Update CD</A></H4>
<P>An Update CD is included with the AIX Version 4.3.3 product
media, which contains updates that are required for some configurations and is
recommended for all configurations. After completing the installation
from the AIX Version 4.3.3 product media (including any
additional program products), update from the Update CD by entering the
following command:
<PRE>smit update_all
</PRE>
<P><H4><A NAME="Header_20">IBM AIX Developer Kit, Java Technology Edition, Version 1.1.8</A></H4>
<P>IBM AIX Developer Kit, Java Technology Edition, Version 1.1.8
(Java 1.1.8) is released in Java * filesets. The code on
the Install CD is the GA code that was made available in September
1999. The code on the Update CD is the Java
1.1.8.8 code (PTF8).
<DL><DT><B>Note:</B></DT><DD>Java 1.1.8 PTF 12 images are located on the Update CD in the
<B>/java118_ptf12</B> directory.
</DD></DL>
<P>For more information (including a download of updates), go to the following
Web site:
<PRE>http://www.ibm.com/java/jdk/index.html
</PRE>
<P><H4><A NAME="Header_21">Installing the Parallel System Support Programs (PSSP) APARs</A></H4>
<P>Before installing AIX 4.3.3 on RS/6000 SP systems, the
following PSSP APARs must be installed so that the SP switch functions
correctly:
<UL>
<LI>IY03104 PSSP 3.1.1
</LI><LI>IY03103 PSSP 2.4.0
</LI><LI>IY03102 PSSP 2.3.0
</LI></UL>
<P><H3><A NAME="Header_22" HREF="#MTOC_22">Memory Requirements</A></H3>
<P>AIX 4.3.3 requires a minimum of 32 megabytes of physical
memory.
<P><H3><A NAME="Header_23" HREF="#MTOC_23">Initial Paging Space Requirements</A></H3>
<P>AIX 4.3.3 requires the initial paging space
(<B>/dev/hd6</B>) to be a minimum of 64 megabytes in size.
<P><H3><A NAME="Header_24" HREF="#MTOC_24">Disk Space Requirements</A></H3>
<P>AIX 4.3.3 requires additional disk space for the same set of
installed filesets due to the increased library sizes and additional
function. If you are migrating from previous releases of AIX, refer to
the following tables for disk space requirements.
<DL><DT><B>Note:</B></DT><DD>These measurements are not meant to be exact, but are meant to help you
understand that additional disk space may be required on your system when you
install or migrate to AIX 4.3.3.
</DD></DL>
<BR>
<TABLE WIDTH="100%" BORDER>
<TR>
<TD ALIGN="LEFT" VALIGN="TOP" COLSPAN="4" WIDTH="100%">Base AIX Install (graphical system with CDE)
</TD></TR><TR>
<TH ALIGN="LEFT" VALIGN="BOTTOM" ID="COL1" WIDTH="25%">
<BR></TH><TH ALIGN="LEFT" VALIGN="BOTTOM" ID="COL2" WIDTH="25%">AIX 4.1.5 Allocated (Used)
</TH><TH ALIGN="LEFT" VALIGN="BOTTOM" ID="COL3" WIDTH="25%">AIX 4.2.1 Allocated (Used)
</TH><TH ALIGN="LEFT" VALIGN="BOTTOM" ID="COL4" WIDTH="25%">AIX 4.3.3 Allocated (Used)
</TH></TR><TR>
<TD ALIGN="CENTER" VALIGN="TOP" HEADERS="COL1" WIDTH="25%">/
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="25%">4MB (1.8MB)
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL3" WIDTH="25%">16MB (2.9MB)
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL4" WIDTH="25%">4MB (2.5MB)
</TD></TR><TR>
<TD ALIGN="CENTER" VALIGN="TOP" HEADERS="COL1" WIDTH="25%">/usr
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="25%">140MB (134.3MB)
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL3" WIDTH="25%">156MB (143.5MB)
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL4" WIDTH="25%">294MB (279MB)
</TD></TR><TR>
<TD ALIGN="CENTER" VALIGN="TOP" HEADERS="COL1" WIDTH="25%">/var
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="25%">4MB (0.4MB)
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL3" WIDTH="25%">16MB (0.9MB)
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL4" WIDTH="25%">4MB (1.3MB)
</TD></TR><TR>
<TD ALIGN="CENTER" VALIGN="TOP" HEADERS="COL1" WIDTH="25%">/tmp
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="25%">8MB (0.3MB)
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL3" WIDTH="25%">16MB (0.5MB)
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL4" WIDTH="25%">16MB (0.6MB)
</TD></TR></TABLE>
<BR>
<TABLE WIDTH="100%" BORDER>
<TR>
<TD ALIGN="LEFT" VALIGN="TOP" COLSPAN="4" WIDTH="100%">Base AIX Install with Network Support, X11, CDE, and client bundle
installed
</TD></TR><TR>
<TH ALIGN="LEFT" VALIGN="BOTTOM" ID="COL1" WIDTH="25%">
<BR></TH><TH ALIGN="LEFT" VALIGN="BOTTOM" ID="COL2" WIDTH="25%">AIX 4.1.5 Allocated (Used)
</TH><TH ALIGN="LEFT" VALIGN="BOTTOM" ID="COL3" WIDTH="25%">AIX 4.2.1 Allocated (Used)
</TH><TH ALIGN="LEFT" VALIGN="BOTTOM" ID="COL4" WIDTH="25%">AIX 4.3.3 Allocated (Used)
</TH></TR><TR>
<TD ALIGN="CENTER" VALIGN="TOP" HEADERS="COL1" WIDTH="25%">/
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="25%">4MB (2MB)
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL3" WIDTH="25%">16MB (3.2MB)
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL4" WIDTH="25%">8MB (4MB)
</TD></TR><TR>
<TD ALIGN="CENTER" VALIGN="TOP" HEADERS="COL1" WIDTH="25%">/usr
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="25%">172MB (161.6MB)
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL3" WIDTH="25%">192MB (170.2MB)
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL4" WIDTH="25%">328MB (320MB)
</TD></TR><TR>
<TD ALIGN="CENTER" VALIGN="TOP" HEADERS="COL1" WIDTH="25%">/var
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="25%">4MB (0.5MB)
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL3" WIDTH="25%">16MB (0.9MB)
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL4" WIDTH="25%">4MB (1.4MB)
</TD></TR><TR>
<TD ALIGN="CENTER" VALIGN="TOP" HEADERS="COL1" WIDTH="25%">/tmp
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="25%">12MB (0.5MB)
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL3" WIDTH="25%">16MB (0.7MB)
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL4" WIDTH="25%">16MB (0.8MB)
</TD></TR></TABLE>
<BR>
<TABLE WIDTH="100%" BORDER>
<TR>
<TD ALIGN="LEFT" VALIGN="TOP" COLSPAN="3" WIDTH="100%">AIX 4.3.3 with Network Support, X11, CDE after migration
</TD></TR><TR>
<TH ALIGN="LEFT" VALIGN="BOTTOM" ID="COL1" WIDTH="33%">
<BR></TH><TH ALIGN="LEFT" VALIGN="BOTTOM" ID="COL2" WIDTH="33%">AIX 4.1.5 Allocated (Used)
</TH><TH ALIGN="LEFT" VALIGN="BOTTOM" ID="COL3" WIDTH="33%">AIX 4.2.1 Allocated (Used)
</TH></TR><TR>
<TD ALIGN="CENTER" VALIGN="TOP" HEADERS="COL1" WIDTH="33%">/
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="33%">4MB (3MB)
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL3" WIDTH="33%">8MB (3.4MB)
</TD></TR><TR>
<TD ALIGN="CENTER" VALIGN="TOP" HEADERS="COL1" WIDTH="33%">/usr
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="33%">320MB (284MB)
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL3" WIDTH="33%">328MB (310MB)
</TD></TR><TR>
<TD ALIGN="CENTER" VALIGN="TOP" HEADERS="COL1" WIDTH="33%">/var
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="33%">4MB (1.3MB)
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL3" WIDTH="33%">4MB (1.3MB)
</TD></TR><TR>
<TD ALIGN="CENTER" VALIGN="TOP" HEADERS="COL1" WIDTH="33%">/tmp
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="33%">16MB (0.7MB)
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL3" WIDTH="33%">16MB (1.0MB)
</TD></TR></TABLE>
<BR>
<TABLE WIDTH="100%" BORDER>
<TR>
<TD ALIGN="LEFT" VALIGN="TOP" COLSPAN="2" WIDTH="100%">AIX 4.3.3 with Network Support, X11, CDE, after update
from AIX 4.3.2
</TD></TR><TR>
<TH ALIGN="LEFT" VALIGN="BOTTOM" ID="COL1" WIDTH="50%">
<BR></TH><TH ALIGN="LEFT" VALIGN="BOTTOM" ID="COL2" WIDTH="50%">Product Media Allocated (Used)
</TH></TR><TR>
<TD ALIGN="CENTER" VALIGN="TOP" HEADERS="COL1" WIDTH="50%">/
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="50%">8MB (4MB)
</TD></TR><TR>
<TD ALIGN="CENTER" VALIGN="TOP" HEADERS="COL1" WIDTH="50%">/usr
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="50%">390MB (313MB)
</TD></TR><TR>
<TD ALIGN="CENTER" VALIGN="TOP" HEADERS="COL1" WIDTH="50%">/var
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="50%">12MB (2MB)
</TD></TR><TR>
<TD ALIGN="CENTER" VALIGN="TOP" HEADERS="COL1" WIDTH="50%">/tmp
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="50%">16MB (0.6MB)
</TD></TR></TABLE>
<DL><DT><B>Note:</B></DT><DD>The filesets that are automatically installed have changed since AIX Version
4.1. That is, <B>bos.sysmgt.sysbr</B> (the
<B>mksysb</B> fileset),
<B>bos.sysmgt.nim.client</B>, and
<B>bos.net.nfs.client</B> were not automatically
installed in AIX 4.1, but are automatically installed in AIX
4.3.3. Some new filesets (such as Java, Web-based System
Manager, and NetQuestion Web Server) are also automatically installed in AIX
4.3.3.
</DD></DL>
<P><H3><A NAME="Header_25" HREF="#MTOC_25">Multiple Volume CD-ROMs</A></H3>
<P>AIX 4.3 has added multiple volume CD-ROMs. If you ask to
install a fileset or a bundle of filesets, you may be prompted to insert
another CD-ROM volume to complete the installation. If you do not want
to be prompted, or do not have the other volumes available, set the
<B>Process multiple volumes?</B> field in SMIT or the Web-based System
Manager to <B>no</B> (it is set to <B>yes</B> by default). If
you are using the command line to call <B>installp</B>, specify the
<B>-S</B> flag to not process multiple volumes. If the CD volume is
already mounted as a file system at the time of the installation, multiple
volume processing is disabled.
<DL><DT><B>Note:</B></DT><DD>You will <I>not</I> be asked to switch CD-ROMs during a Base (BOS)
Installation of AIX. Multiple volume CD-ROMs are only enabled after the
operating system has rebooted.
</DD></DL>
<P><H3><A NAME="Header_26" HREF="#MTOC_26">Network Installation Management (NIM) Enhancements - AIX 4.3.3</A></H3>
<P>Network Installation Management (NIM) has been enhanced to suppport
Kerberos 4 (K4) authentication.
<P>To use K4 authentication in an SP environment using PSSP 3.1, you
must install APAR IX88526. If this APAR is not installed, a failure is
returned when a NIM master with K4 issues commands to a node without
K4.
<P><H3><A NAME="Header_27" HREF="#MTOC_27">Other Installation Information</A></H3>
<P><H4><A NAME="Header_28">BOS Installation Support for Fibre Channel Boot</A></H4>
<P>BOS installation supports installation to fibre channel-attached
disks. Bootable AIX 4.3.3 installation media is required
or NIM resources prepared from such media. The fibre channel-attached
disks must be attached to a fibre channel host adapter that supports boot
capability.
<P>A fibre channel-attached disk can be identified by a World Wide Port Name
and Logical Unit ID. To see the format of the World Wide Port Name and
Logical Unit ID, type:
<PRE>lsattr -E -O -l DiskName
</PRE>
<UL>
<LI>In a non-prompted BOS installation, you can specify a fibre
channel-attached disk in the target_disk_data stanza of the
<B>bosinst.data</B> file by:
<PRE>SAN_DISKID = (World Wide Port Name)//(Logical Unit ID)
</PRE>Where the (World Wide Port Name) and (Logical Unit ID) are each in the
format returned by <B>lsattr</B>, that is, "0x" followed by 1-16
hexadecimal digits.
</LI><LI>In a prompted BOS Installation, the BOS Menus display the list of
available disks and associated information. You can select the desired
disk(s).
</LI></UL>
<P><H4><A NAME="Header_29">AIX Network Installation Management (NIM) README</A></H4>
<P>The AIX Network Installation Management (NIM) includes a <B>README</B>
file that is installed with the NIM Master
<B>bos.sysmgt.nim.master</B> fileset. The path
name of the file is <B>/usr/lpp/bos.sysmgt/nim/README</B>.
The <B>README</B> file contains additional information about the AIX
Version 4.3 NIM product.
<P><H4><A NAME="Header_30">Dedicated System Dump Device</A></H4>
<P>The default system dump device is paging space. This may not be
adequate for system configurations that have large memory sizes or when system
availability is a concern. For these configurations, it is recommended
that you allocate a dedicated system-dump logical volume.
<P>The dump is now copied to tape in pax format because pax supports large
(greater than 2 GB) files. You must install APAR IY12510 and
IY13015.
<P><H4><A NAME="Header_31">License Use Management Runtime</A></H4>
<P>Some of the products included in this release have been modified to use
license management software. These products require a license password
in order for you to use them. License Use Management Runtime for AIX is
the new license management product. It is an enhancement to iFOR/LS
included in AIX Version 4.1 and 4.2 and contains new license
management functions, but still uses the same techniques and is completely
compatible with iFOR/LS. For further information on License Use
Management Runtime, see <I>Using License Use Management Runtime for
AIX</I>.
<P><H4><A NAME="Header_32">Installing AIX 4.3 over AIX 4.1 or 4.2 with License Use Runtime Version 4 Installed</A></H4>
<P>If you are using License Use Runtime Version 4 on AIX 4.1 or
4.2 and you upgrade to AIX 4.3, select <B>Migration
Install</B> from the AIX installation menu. Do not select
<B>Overwrite Install or Preservation Install</B>. This will
maintain your license database and your configuration information.
<P><H4><A NAME="Header_33">Upgrading to a new Modification Level of AIX 4.3</A></H4>
<P>If you are using License Use Runtime Version 4 on AIX 4.3, and you
upgrade to a new modification level of AIX (for example, from AIX
4.3.1 to 4.3.3), use <B>smit</B> to
upgrade. Choose <B>Install and Update Software</B>, and then the
<B>Install/Update From All Available Software</B> option. This will
maintain your license database and your configuration information.
<P><H4><A NAME="Header_34">What Software Must You Install?</A></H4>
<P>The following section specifies which License Use Management Runtime
filesets and other software you must install on the system.
<P><H5><A NAME="Header_35">Installing the License Use Runtime GUI on AIX 4.3.3</A></H5>
<P>If you have AIX 4.3.3 and you want to use the License Use
Runtime graphical user interface, install the following:
<OL TYPE=1>
<LI>IPF/X Runtime Support. This is required if you install the backward
compatibility GUI. IPF/X Runtime Support is in the
<B>ipfx.rte</B> package that is shipped with the AIX installation
media.
</LI><LI>License Use Runtime Filesets:
<B>ifor_ls.compat.cli.</B> and
<B>ifor_ls.compat.gui</B> (optional)
</LI></OL>
<DL><DT><B>Note:</B></DT><DD>If you installed the backward compatibility package on AIX
4.3.0, 4.3.1, or 4.3.2, and then you
migrated to AIX 4.3.3, the backward compatibility package is
automatically upgraded to the 4.3.3 level. You do not
need to do any additional installation.
</DD></DL>
<P>For more information about License Use Runtime, see the
<B>/usr/opt/ifor/ls/os/aix/doc/readme.ark</B> file.
<P><H5><A NAME="Header_36">Some Licenses not Registered</A></H5>
<P>Some applications, such as DB2 V5, register their product license using the
License Use Management (LUM) Nodelock Administration Tool
<B>/var/ifor/i4nat</B>. This tool is included in the LUM
Compatibility fileset <B>ifor_ls.compat</B> that was shipped with
AIX 4.3.2 as an option, but is <I>not</I> part of the base
installation. Install this fileset before installing DB2 V5 on AIX
4.3.2 or later, or attempting to upgrade a DB2 V5 demonstration
license to a product license.
<P><H4><A NAME="Header_37">bos.content_list Fileset and the which_fileset Command</A></H4>
<P>AIX 4.3.2 and later include a new, optionally installable
fileset, <B>bos.content_list</B>, that lists all installable files
and the filesets/packages that contain them. The fileset includes one
file, <B>/usr/lpp/bos/AIX_file_list</B>.
<P>The <B>bos.rte.install</B> fileset now also ships the
<B>/usr/sbin/which_fileset</B> command, which allows you to search the
<B>/usr/lpp/bos/AIX_file_list</B> file after
<B>bos.content_list</B> is installed.
<P><H4><A NAME="Header_38">ARTIC960 Adapter</A></H4>
<P>When running SNA Version 5.0 with the ARTIC960 adapter, you may
experience system hangs or crashes. APARs IX82178 and IX82256 are
available to fix these problems.
<P><H4><A NAME="Header_39">Welcome Center</A></H4>
<P>The Welcome Center application as shipped on RS/6000 systems, contains a
Java Search applet that searches the Welcome Center files only when the
Welcome Center is launched during the system reboot. Note the following
information about this function:
<UL>
<LI>When running the Welcome Center on a GXT150 class graphics adapter, the
Java Search applet colors show blue on black, which could be difficult to
read.
</LI><LI>After you <B>login</B> to the Common Desktop Environment, you can run
the Welcome Center by the icon in the Application Manager. In this
environment, the Documentation Library search function will be launched
instead of the Java Search applet.
</LI><LI>The search function is not provided in the ja_JP locale.
</LI></UL>
<P><H3><A NAME="Header_40" HREF="#MTOC_40">Migration</A></H3>
<P><H4><A NAME="Header_41">Migrating to AIX Version 4.3</A></H4>
<P>When migrating to AIX Version 4.3 from an earlier level of AIX, you
must update filesets from all CD-ROM volumes. The initial migration
installation updates only the filesets from volume 1. After the system
is booted in normal mode, enter the following command:
<PRE>smit update_all
</PRE>
<P>This command updates the filesets from the additional CD-ROM
volumes. SMIT prompts for the additional volumes as necessary.
<P><H4><A NAME="Header_42">sendmail update in AIX Version 4.3.3</A></H4>
<P>AIX 4.3.3 runs sendmail Version 8.9.3 which
contains fixes, new configuration options, and Anti-Spam features. For
more information about sendmail, see the <B>/usr/lpp/bos/README</B>
file.
<P><H4><A NAME="Header_43">sendmail on AIX Version 3.2.5/4.1.5 and sendmail on AIX Version 4.3.3</A></H4>
<P>sendmail Version 5.64 (supported on AIX version 3.2.5
and 4.1.5) and sendmail Version 8.9.3 (supported
on AIX 4.3.3) are not compatible. sendmail
8.9.3 does not work with the Version 5.64
<B>/etc/sendmail.cf</B> file. There is no script available
to assist in migration of the Version 5.64
<B>/etc/sendmail.cf</B> file to the Version 8.9.3
<B>/etc/sendmail.cf</B> file.
<P>During migration installation of AIX Version 4.3.3, the
Version 5.64 sendmail files are saved in the following locations:
<P>
<PRE>/usr/lpp/save.config/usr/sbin/sendmail
/usr/lpp/save.config/etc/sendmail.cf
/lpp/save.config/etc/sendmail.nl
</PRE>
<P>The <B>/etc/aliases</B> file is not modified during the
installation.
<P><H4><A NAME="Header_44">sendmail on AIX 4.2.0/4.2.1/4.3.0/4.3.2 and sendmail on AIX 4.3.3</A></H4>
<P>sendmail Version 8.7 (supported on AIX 4.2.0, AIX
4.2.1, and AIX 4.3.0) and sendmail Version
8.8.8 (supported on AIX 4.3.2) and sendmail
Version 8.9.3 are somewhat compatible. The Version
8.7 <B>/etc/sendmail.cf</B> file works with the Version
8.8.8 and Version 8.9.3 sendmail binaries.
The Version 8.8.8 <B>/etc/sendmail.cf</B> file works
with the Version 8.9.3 sendmail binary. However, each new
version of <B>/etc/sendmail.cf </B>contains new rewrite rules,
macros, and options that are particular to the updated sendmail binary.
Therefore, if you choose to run the Version 8.7
<B>/etc/sendmail.cf</B> file with the Version 8.9.3
sendmail binary, you could lose some new features and function particular to
Version 8.9.3. You may want to merge the new options,
macros, and rewrite rules. The new <B>sendmail.cf</B> file
should have been saved in
<B>/usr/lpp/save.config/etc/sendmail.cf.new</B>.
You must merge this manually, because no migration script exists.
<P><H4><A NAME="Header_45">Migrating to the AIX Common Desktop Environment 1.0</A></H4>
<P>This section provides information on moving to the AIX Common Desktop
Environment (CDE) 1.0 from any version of AIX 3.2 or AIX
4.
<P><B>Notes: </B><OL>
<P><LI>AIX Common Desktop Environment (AIX CDE) is the default desktop shipped
with AIX 4.1.3 or later.
<P><LI>AIXwindows Desktop is the default desktop shipped with AIX
3.2.x, 4.1.0, 4.1.1, and
4.1.2.
</OL>
<P>If, after migrating to AIX CDE 1.0 from AIXwindows desktop on AIX
4.1.1 or 4.1.2, you have problems with the desktop
(for example, icons on the front panel do not execute properly, icons are
missing, or actions cannot be found), check that the following has been
done:
<OL TYPE=1>
<LI>The <B>X11.Dt.compat</B> fileset has been
installed.
</LI><LI>Action, data type, and front panel definitions in personal directories
have been migrated to a valid format for AIX CDE 1.0.
</LI></OL>
<P>An online help volume is provided to assist you in migrating to AIX CDE
1.0 from the AIXwindows Desktop. View this online help by
selecting <B>Welcome to AIX CDE 1.0</B> from the Help Manager
subpanel.
<P><H4><A NAME="Header_46">OpenGL, UMS or graPHIGS Migration</A></H4>
<P>After migrating the OpenGL filesets some filesets may remain at the same
VRMF level. For example, if you migrate from AIX 4.1.5 to
AIX 4.3.2 and have all of the OpenGL filesets installed, the
following filesets will not be migrated and their VRMF will not change:
<PRE>Fileset name VRMF
------------------------------------- -------
OpenGL.OpenGL_X.adt.doc 4.1.0.0
OpenGL.OpenGL_X.dev.pci.14104000.PPC 4.1.5.0
OpenGL.OpenGL_X.tools.glperf 4.1.0.0
</PRE>
<P>This is an expected result and is not an indication that the migration was
not successful or did not finish.
<P><H4><A NAME="Header_47">UMS Deinstalled on AIX 4.3 Migration Installations</A></H4>
<P>When performing a migration installation from any version of AIX 4.1
or AIX 4.2 toAIX 4.3, an existing UMS will be
deinstalled. This is to prevent problems due to incompatibilities
between the UMS X11R5 XVideo Extension and the AIX X11R6 Xserver contained in
AIX 4.3. After the migration installation, the user must
reinstall UMS, including the <B>UMS.video_ext</B> package
containing the X11R6 version of the UMS XVideo Extension, from the AIX
4.3 Bonus Pack CDs.
<P><H4><A NAME="Header_48">AIX Version 3.2 to 4.3 Migration Problems</A></H4>
<P>On some AIX Version 3.2 systems, the default installation method is
set as preservation (instead of migration). Check the default settings
and select your desired method of installation from the <B>Change/Show
Installation Settings and Install</B> panel. See "Step 5.
Verifying or Changing the Installation Settings" in the <I>Installation
Guide</I>, SC23-4112-00, for additional information.
<P><H4><A NAME="Header_49">4.3.3.0 Installation Media</A></H4>
<P>Updates for some IBM products are included on the AIX
4.3.3.0 Installation media. They are included
because these products will not function correctly after updating to
4.3.3 without them. The products themselves are not
included on the AIX media, and must be obtained/purchased separately.
<P>If you try to install these updates and you do not have the product
installed, an error similar to the following displays:
<PRE>Sample failure:
.........
Requisite Failures
------------------
SELECTED FILESETS: The following is a list of filesets that you asked to
install. They cannot be installed until all of their requisite filesets
are also installed. See subsequent lists for details of requisites.

sysback.rte 4.1.3.1 # AIX System Backup & Recovery
sysback.sbom 4.1.3.0 # Sysback Offline Mirror Backu..

MISSING REQUISITES: The following filesets are required by one or more
of the selected filesets listed above. They are not currently installed
and could not be found on the installation media.

sysback.rte 4.1.0.0 # Base Level Fileset
sysback.sbom 4.1.0.0 # Base Level Fileset

.........
</PRE>
<P>This error indicates that the updates cannot be applied without the base
level product.
<P><H4><A NAME="Header_50">Firmware</A></H4>
<P>The firmware in many of the PCI bus-based RS/6000 machines is limited
regarding the region of the hard disk from which it can read a boot
image. This problem will not be encountered under most
circumstances. The symptom of the problem is a failure to boot from
hard disk, and a message from firmware similar to <TT>unrecognized Client
Program format</TT>.
<P>The affected machines can be identified most easily as the machines that
provide access to the firmware System Management Services by means of pressing
the F1 keys on the system attached keyboard, or the 1 key on a tty
keyboard.
<P>The problem is that the firmware on the affected machines cannot read the
boot image from the hard disk if any part of the boot image resides past the 4
gigabyte boundary on the hard disk. This is not a problem for most
customers because the AIX installation process creates the boot logical volume
at the beginning of the disk. This is achieved by using the
<B>-a</B> flag with the <B>mklv</B> command and specifying
<B>e</B> (which corresponds to <B>edge</B>) as the argument for the
<B>-a</B> flag. Using the <B>mklv</B> command with this
parameter results in the boot logical volume being created at the edge of the
hard disk, and the resulting address that the firmware uses to read the boot
image will be within a safe range. The AIX installation process has
always created the boot logical volume near the edge of the hard disk because
that region of the hard has the slowest access time, and this allows other
regions of the hard disk to be used by filesystems that can benefit from the
better performance.
<P>The only way that a customer can encounter this problem is by creating and
initializing a new boot logical volume that extends past the 4 gigabyte
boundary of the hard disk, either in part or in entirety.
<P>In almost all cases, there is no need for a customer to create a new boot
logical volume, but if they do, they should use the <B>lsvg</B> and
<B>lslv</B> commands to verify that the newly created boot logical volume
does not reside above the 4 gigabyte address on the hard disk.
<P>An example of this calculation follows:
<OL TYPE=1>
<LI>Run <B>lsvg rootvg</B> to determine PP SIZE.
<DL><DT><B>Note:</B></DT><DD>On a 4.5 gigabyte hard disk,the default PP SIZE is 8 megabytes.
</DD></DL>
</LI><LI>Run <B>lslv -m bootlv00</B>
<P>Replace bootlv00 with the name of the newly created boot logical
volume. The numbers in the second, fourth, and sixth columns of the
output indicate the physical partitions which have been assigned to the boot
logical volume. If the PP SIZE is 8 megabytes, the boot logical volume
must not use any physical partition above 511. (512 * 8 = 4096, which
is 4 gigabytes). Similarly, if the PP SIZE is 16 megabytes, the boot
image must not use any partition above 255, and if the PP SIZE is 4 megabytes,
then the boot image must not use any partition above 1023.
</LI></OL>
<P>As a reminder, this problem will not happen unless the customer has created
and initialized a boot image that resides above the 4 gigabyte
boundary.
<HR><H2><A NAME="Header_51" HREF="#MTOC_51">Base Operating System (BOS)</A></H2>
<P>This section contains information about the base operating system
(BOS).
<P><H3><A NAME="Header_52" HREF="#MTOC_52">AutoFS Compatibility</A></H3>
<P>In the event that an administrator wants to use the <B>automount</B>
command rather than the <B>AutoFS</B> command, they must set an
environment variable before invoking the <B>automount</B> command.
They should also ensure that any map parameters previously used by the
<B>automount</B> command are passed to the <B>automount</B> command
with the <B>COMPAT_AUTOMOUNT</B> environment variable set and
exported.
<P>The <B>/usr/bin/automount</B> script looks for a
<B>COMPAT_AUTOMOUNT</B> environment variable. If
<B>COMPAT_AUTOMOUNT</B> is set to any value, the old version of
<B>automount</B> is used and it now runs as
<B>/usr/sbin/compat_automount</B>.
<P><H3><A NAME="Header_53" HREF="#MTOC_53">Logical Volume Manager (LVM) Enhancements</A></H3>
<P>The LVM enhancements allow commands <B>mklv</B>, <B>rmlv</B>,
<B>splitlvcopy</B>, and <B>chlv</B> (except name change) to function
in concurrent mode and the new options for <B>syncvg</B> (<B>-H</B>
<B>-P</B>) that allow a faster concurrent <B>syncvg</B> require that
all machines in the cluster be at AIX Version 4.3. These new
functions should not be attempted in mixed release level environments.
If your environment is a mixture of AIX 4.1 or AIX 4.2 and AIX
4.3, do not try these new functions until you obtain the following
APARs:
<UL>
<LI>IX70098 - V41 - clvmd should not vary off volume group for all NAK
cases.
</LI><LI>IX70099 - V42 - clvmd should not vary off volume group for all NAK
cases.
</LI></UL>
<P>Otherwise, the passive cluster nodes will vary off the volume group when
the new functions are attempted.
<P>If you wish to do <B>rootvg</B> mirroring, use <B>mirrorvg</B> to
setup the mirroring and <B>unmirrovg</B> to remove the mirroring.
With these two commands, the limitations on rootvg mirroring have been
removed. The white paper "Mirroring the rootvg Volume Group for AIX 4"
is therefore no longer valid with AIX 4.3 and should not be
followed.
<P>A new partition allocation policy (Super Strict) is supported. This
policy prohibits partitions from one mirror from sharing a disk with a second
or third mirror.
<DL><DT><B>Note:</B></DT><DD>Super Strict policies and mirroring and striping are not supported on AIX
releases prior to AIX Version 4.3.3. You cannot import
volume groups to AIX Version 4.3.2 and earlier if the volume
groups include Super Strict policies or mirroring and striping
functions.
</DD></DL>
<P><H3><A NAME="Header_54" HREF="#MTOC_54">wlmcntrl Command Correction</A></H3>
<P>The description of the <B>-u</B> flag for the <B>wlmcntrl</B>
command is incorrect in the AIX 4.3.3 documentation.
<P>Use the following information for the <B>-u</B> flag:
<DL>
<P><DT><B><B>-u</B>
</B></DT><DD>Update: request to change the limits and/or shares of the active
classes. Classes cannot be added or removed this way.
</DD></DL>
<P><H3><A NAME="Header_55" HREF="#MTOC_55">Print Subsystem Changes</A></H3>
<P>The location of the device file for HP JetDirect attached printers changed
between AIX Version 3 and Version 4. In AIX Version 3, the device file
resided in the <B>/var/spool/lpd/pio/dev</B> directory. In AIX
Version 4, this device file has moved to the
<B>/var/spool/lpd/pio/local/dev</B> directory.
<P>Having the device file reside in a different directory will cause problems
for existing HP JetDirect queues after an upgrade from AIX Version 3 to
Version 4. Because the <B>/etc/qconfig</B> file is
user-configurable, it is not modified during an AIX upgrade.
<P>To allow the HP JetDirect queues to work after an upgrade, the
<B>/etc/qconfig</B> file must be edited to indicate the new pathname for a
device file. Any existing HP JetDirect queue must have the
<B>local</B> directory inserted between the <B>pio</B> and
<B>dev</B> directories for the <B>file</B> entry of the queue, as
shown in the following example.
<P>This is an HP JetDirect queue on an AIX Version 3 system:
<PRE>netps:
device = hpserver
hpserver:
file =
/var/spool/lpd/pio/dev/hpserver
header = never
trailer = never
access = both
backend = /usr/lib/lpd/pio/etc/piojetd server
</PRE>
<P>To allow this queue to work after an upgrade to AIX Version 4, change the
line containing <B>file</B> = for the queue to the following:
<PRE>file = /var/spool/lpd/pio/local/dev/hpserver
</PRE>
<P><H3><A NAME="Header_56" HREF="#MTOC_56">Parallel Printer Cable Selection</A></H3>
<P>The parallel printer cable must be changed to a cable that is IEEE1284
compliant if all of the following are true:
<UL>
<LI>Your system was manufactured since 1998.
</LI><LI>The printer is "parallel attached."
</LI><LI>The attached printer is <I>not</I> a dot-matrix printer.
</LI><LI>The output of the <B>lsdev -C -l ppa0</B> command contains the word
<TT>IEEE1284</TT>.
</LI></UL>
<P>If the output of the <B>lsdev</B> command above contains the word
<TT>Standard</TT>, or the printer is a dot-matrix printer, an IEEE1284
compliant cable is <I>not</I> required.
<P>Cables that are not IEEE1284 compliant may not properly transmit data to
high speed printers and loss of printer data may occur, because the cables may
not be capable of transmitting data at rates that are possible with newer ECP
parallel ports.
<P><H3><A NAME="Header_57" HREF="#MTOC_57">man Command</A></H3>
<P>To access manual pages with the <B>man</B> command on a remote system,
you have to specify the <B>-r</B> flag.
<P>The syntax is:
<PRE>man [[[ -c ] [ -t ] [ Section ]] | [ -k | -f ]] [ -M MPath ] [ -r ] Title ...
</PRE>
<DL><DT><B>Note:</B></DT><DD>If the <B>-r</B> flag is specified with the <B>man</B> command for
accessing remote manual pages, set the <B>DOCUMENT_SERVER_MACHINE_NAME</B>
environmental variable to the name of the documentation search server machine
you want to use.
</DD></DL>
<P><H3><A NAME="Header_58" HREF="#MTOC_58">New Flag for the sar Command</A></H3>
<P>In order to enable the <B>sar</B> command to read binary files
generated by an older version of the <B>sadc</B> command, a new
<B>-X</B> option was introduced. The <B>-X</B> file extracts
the records from the file parameter, which is generated by the older version
of the <B>sadc</B> command. The new <B>-X</B> option has to be
specified if the binary file is generated by the older version of the
<B>sadc</B> command.
<P>The new option "-X" has to be specified if the binary file is generated by
the older version of the sadc.
<P>The modification to the 4.3.3 <B>sar</B> command is
below:
<P>Current syntax:
<PRE>/usr/sbin/sar { -A | [-a][-b][-c][-d][-k][-m][-q][-r][-u]
[-v][-w][-y] } [-s hh[:mm[:ss]]] [-e hh[:mm[:ss]]]
[-P processor_id[,...] | ALL]
[-f file] [-i seconds] [-o file] [interval [number]] [-V]
</PRE>
<P>New syntax:
<PRE>/usr/sbin/sar { -A | [-a][-b][-c][-d][-k][-m][-q][-r][-u]
[-v][-w][-y] } [-s hh[:mm[:ss]]] [-e hh[:mm[:ss]]]
[-P processor_id[,...] | ALL]
[-f file] [-X file][-i seconds] [-o file] [interval [number]] [-V]

</PRE>
<P><H3><A NAME="Header_59" HREF="#MTOC_59">shutdown Command</A></H3>
<P>This section of the Release Notes is included to document the <B>-u</B>
flag in the <B>shutdown</B> command. This flag was not documented
in any 4.3 releases. The <B>-u</B> flag is used by
diagnostics to update the flash memory and reboot.
<P>Use the following syntax to implement the <B>-u</B> flag in the
<B>shutdown</B> command:
<PRE>shutdown [-d] [-F] [-h] [-i] [-k] [-m] [-p] [-r] [-t mmddHHMM[yy]] [-u] [-v] [+Time[Message]]

</PRE>
<P><H3><A NAME="Header_60" HREF="#MTOC_60">lsps Command</A></H3>
<P>The current man page for the <B>-c</B> flag of the <B>lsps</B>
command reads:
<PRE>-c Specifies that the output should be in colon format. The colon format gives the paging space
     size in physical partitions.

</PRE>
<P>The documentation should say:
<PRE>-c Specifies that the output should be in colon format. The colon format gives the paging space
     size in <I>logical</I> partitions.

</PRE>
<P><H3><A NAME="Header_61" HREF="#MTOC_61">chnlspath Command</A></H3>
<P><H4><A NAME="Header_62">Purpose</A></H4>
<P>Modifies the value of the secure NLSPATH system configuration
variable.
<P><H4><A NAME="Header_63">Syntax</A></H4>
<PRE>chnlspath nlspath-value
</PRE>
<P><H4><A NAME="Header_64">Description</A></H4>
<P>The <B>chnlspath</B> command is used to modify the secure NLSPATH
system configuration variable.
<P><H3><A NAME="Header_65" HREF="#MTOC_65">lsnlspath Command</A></H3>
<P><H4><A NAME="Header_66">Purpose</A></H4>
<P>Views the value of the secure NLSPATH.
<P><H4><A NAME="Header_67">Syntax</A></H4>
<PRE>lsnlspath
</PRE>
<P><H4><A NAME="Header_68">Description</A></H4>
<P>The <B>lsnlspath</B> command outputs the current value of the secure
NLSPATH variable from the system.
<HR><H2><A NAME="Header_69" HREF="#MTOC_69">Communications, Networking and I/O</A></H2>
<P>This section contains information about communications, networking, and
I/O-related topics.
<P><H3><A NAME="Header_70" HREF="#MTOC_70">gated Compatibility</A></H3>
<P>The new <B>gated</B>, in <B>/usr/sbin</B>, uses a different syntax
from the old version. Therefore, the <B>gated</B> configuration
file in <B>/etc/gated.conf</B> should not be used. There is
a sample <B>gated.conf</B> file in <B>/usr/tcpip/samples</B>
that contains the correct syntax for the new version, and should be used as a
guide for configuring <B>gated</B> in this release.
<P>In AIX 4.3.3, the <B>udp_pmtu_discover</B> and
<B>tcp_pmtu_discover</B> network options have a default value of 1.
This enables path MTU discovery. Path MTU may cause problems for users
running <B>gated</B> in environments where dynamic routing changes are
expected to become effective quickly throughout the network.
<P>If you experience problems when running <B>gated</B>, you can disable
path MTU discovery by using the following commands:
<PRE>no -o udp_pmtu_discover=0
no -o tcp_pmtu_discover=0
</PRE>
<P>To make this change permanent, add the commands to your
<B>/etc/rc.net</B> file.
<P><H3><A NAME="Header_71" HREF="#MTOC_71">7135 RAIDiant Array for AIX requirements (when upgrading to AIX 4.3)</A></H3>
<P>Customers upgrading systems with attached 7135-110 or 7135-210 RAIDiant
Array subsystems to AIX 4.3 must also obtain and install the latest
version of controller and drive microcode. This microcode update can be
obtained using hardware service channels (800-IBM-SERV in the
U.S.) by requesting ECA 010. A new publication for the
7135, containing information on microcode and device driver installation,
should also be ordered. This publication is titled <I>7135 RAIDiant
Array for AIX: Installation Guide and Reference</I>, SC23-1742.
<P><H3><A NAME="Header_72" HREF="#MTOC_72">Interface Specific Network Options (ISNO)</A></H3>
<P>Prior to AIX 4.3.3, several key network options had a single
global default value, making it very difficult to tune a system that has
widely differing network adapters. Some applications are capable of
setting their own options (overriding the defaults), but most of these
applications only allow a single setting and this does not work well with
different network adapters.
<P>AIX 4.3.3 provides a feature called Interface Specific
Network Options (ISNO). This feature can be enabled (the default) or
disabled by setting the <B>no</B> option (<B>use_isno</B>) to 1 or
0.
<P>For each network interface, five new parameters have been added;
<B>rfc1323</B>, <B>tcp_nodelay</B>, <B>tcp_sendspace</B>,
<B>tcp_recvspace</B>, and <B>tcp_mssdflt</B>. These correspond
to the same values in the <B>no</B> options.
<P>If these values are set for a specific interface, then they will override
the system <B>no</B> default value. This allows different network
adapters to be tuned for the best performance.
<P>Use the <B>lsattr -E -l</B> <I>interface</I> command to display the
values. They can be changed via the <B>chdev -l</B>
<I>interface</I> <B>-a</B> <I>attribute</I>=<I>value</I>
command. For example, <TT>chdev -l en0 -a tcp_recvspace=65536 -a
tcp_sendspace=65536</TT> sets the <B>tcp_recvspace</B> and
<B>tcp_sendspace</B> to 64K for <B>en0</B> interface. Using the
<B>chdev</B> command will change the value in the ODM database so it will
be saved between system reboots. If you want to set a value for testing
or temporarily, use the <B>ifconfig</B> command. For example,
<TT>ifconfig en0 hostname tcp_recvspace 65536 tcp_sendspace 65536 tcp_nodelay
1</TT> sets the <B>tcp_recvspace</B> and <B>tcp_sendspace</B> to 64K
and enables <B>tcp_nodelay</B>.
<P>You can also use the <B>ifconfig</B> <I>interface</I> command to
display these values.
<P><H3><A NAME="Header_73" HREF="#MTOC_73">inetd.conf Migration</A></H3>
<P>When you complete your migration, the <B>tftp</B>, <B>ftp</B>,
<B>telnet</B>, <B>shell</B>, <B>login</B>, and <B>exec</B>
services defined in /<B>etc/inetd.conf</B> may be enabled to run,
even if they were disabled in the previous release.
<P><H3><A NAME="Header_74" HREF="#MTOC_74">Network Terminal Accelerator</A></H3>
<P>Network Terminal Accelerator is not supported on AIX Version
4.3.
<P><H3><A NAME="Header_75" HREF="#MTOC_75">System Networking, Analysis and Performance Pilot (SNAPP)</A></H3>
<P>The 4330-05 Recommended Maintenance Package contains the SNAPP
product. SNAPP is used for performing limited system administration and
basic RS/6000 network configuration from a handheld Personal Digital Assistant
(PDA) through a serial line connection. The handheld PDA must be
compatible with Palm OS.
<P>The SNAPP product's primary purpose is to allow IP address
configuration on a newly preinstalled AIX system that does not have a monitor
or ASCII terminal and keyboard attached. It is assumed that once the
AIX machine is on a network, access can be given to it through
<B>telnet</B>, the <B>rlogin</B> command, or some other TCP/IP remote
login command. However, the SNAPP product is not designed to replace a
monitor or ASCII terminal.
<P>The SNAPP product consists of a SNAPP client, the
<B>Snapp.prc</B> program, which resides on a handheld PDA, and a
SNAPP server, <B>/usr/sbin/snappd</B>, which resides in AIX. The
client and server communicate over the serial connection using simple XML
statements. The SNAPP server performs system administration tasks
through perl scripts.
<P>The serial connection is made as the handheld PDA's serial cable is
plugged into the serial port of an AIX box.
<P>The SNAPP product is contained in the
<B>bos.net.snapp</B> fileset. When this fileset is
installed, all the necessary files for the SNAPP server are installed on the
local machine. The SNAPP client binary is installed in
<B>/usr/samples/snapp/Snapp.prc</B>. It can also be
downloaded from the AlphaWorks site at the following URL:
<PRE>http://www.alphaWorks.ibm.com/tech/snapp
</PRE>
<P>The SNAPP client requires a handheld PDA that is compatible with Palm OS
and has a Palm OS software level of V3.5.0 or above. To
copy the SNAPP client binary onto your handheld PDA, copy the
<B>Snapp.prc</B> file to a PC and install the SNAPP application as
you would install any other handheld PDA application. The SNAPP icon
displays as a light bulb with the label <B>SNAPP</B> beneath it.
<P>Additional information on SNAPP is available in
<B>/usr/samples/snapp</B> and from the AlphaWorks web site.
<P><H3><A NAME="Header_76" HREF="#MTOC_76">TCP Selective Acknowledgement (SACK)</A></H3>
<P>TCP SACK is available in AIX 4.3.3 and later. It is
described in detail in RFC 2018, TCP <I>Selective Acknowledgement
Options</I>. SACK allows TCP to recover from multiple losses within
the window in lossy networks and internetworks.
<P>By default, SACK is disabled. To enable it, enter the following
command:
<PRE>/usr/sbin/no -o sack=1
</PRE>
<P><H3><A NAME="Header_77" HREF="#MTOC_77">DVD-RAM Drive Support</A></H3>
<P>Functionality was added in AIX 4.3 to support backing up to
DVD-RAM. System backups (such as the <B>mksysb</B> and
<B>savevg</B> commands) have a limitation that they expect the media to be
4.7 GB or larger per side. They will not process the next volume
until they write over 4 GB on the current volume, thus the use of smaller
media would result in corruption when going beyond the media's
capacity. The other commands (such as <B>tar</B>, <B>cpio</B>,
<B>backup</B>) do not have this size constraint.
<P>For more information on creating CD and DVD backups, refer to the
<B>/usr/lpp/bos.sysmgt/mkcd.README.txt</B>
file.
<HR><H2><A NAME="Header_78" HREF="#MTOC_78">Graphics</A></H2>
<P>This section contains information about graphics software.
<P><H3><A NAME="Header_79" HREF="#MTOC_79">X11R5/X11R6.3 Compatibility Issues On AIX Version 4.3</A></H3>
<P>The AIX 4.3.0, AIX 4.3.1, and AIX
4.3.2 X server is upgraded to the X Consortium release 6 version
of X (commonly known as X11R6.3). The libraries are upgraded to
X11R6.3 as well. These libraries are backward-compatible, in
that the broad majority of applications work as on previous releases of
AIX. For maximum customer flexibility, compatibility options for X11R3,
X11R4, and X11R5 libraries are also shipped.
<P>Applications that use the loadable extension facility provided by the X
server may need to change. The X server allows the addition of new
functionality through its extension mechanism. For each extension, part
of the extension is loaded into the X server before it can be executed.
X11R6.3 has modified how this mechanism works in the course of
improvements to X, and it is this part of the extension that must be made
compatible with X11R6.3 to execute properly. All of the
extensions that are supplied are compatible and execute properly. In
some circumstances, including the following, a customer may have an extension
that will not work with X11R6.3:
<UL>
<LI>A customer has a sample extension downloaded from the X Consortium FTP
site.
</LI><LI>A customer develops his own extension.
</LI><LI>A customer uses a third-party extension.
</LI></UL>
<P>In these cases, the extension must be made compatible with X11R6.3
before it executes properly. Customer-developed extensions and sample X
consortium extensions must be recompiled with the X11R6.3
environment. For third-party extensions, the customer should contact
the vendor for a X11R6.3 compatible update.
<P>Customers using non-IBM display adapters may also be using vendor-supplied
software specific to those devices, which uses X11R6.3 Server
capabilities. If so, this software must be made compatible with
X11R6.3 to operate properly. The customer should contact the
particular vendor of the display adapter for this software.
<P>An AIX Version 4.3 porting guide and the information on <I>The
Developers Connection</I> CD provides assistance to customers and vendors
developing adapters or extensions for AIX.
<P><H3><A NAME="Header_80" HREF="#MTOC_80">graPHIGS for AIX 4.3</A></H3>
<P>graPHIGS applications that run Distributed Application Processes (DAPs) may
need to change. By default on AIX 4.3, DAPs run with the new
X11R6 libraries. If a DAP requires X11R5 libraries for any reason, the
user may use a new flag, <B>-r5</B>, with the <B>gPinit</B> command as
follows:
<PRE>gPinit -a -r5
</PRE>
<P>The <B>-a</B> flag allows for DAP execution and has not changed.
<P>If the <B>-r5</B> flag is used, then all DAPs run as X11R5
clients. By default, DAPs and the graPHIGS remote nucleus run as X11R6
clients in AIX Version 4.3.
<P>The <B>-r5</B> flag is useful for DAPs that depend on X11R5
functionality that no longer exists in X11R6 (for example,
<B>XAsyncInput()</B>).
<P>If the following message is observed while running a X11R5 DAP, then
restart the graPHIGS remote nucleus with the <B>-r5</B> flag in addition
to the <B>-a</B> flag.
<PRE>WARNING: The XAsyncInput API is no longer implemented in X11R6.
</PRE>
<P><H3><A NAME="Header_81" HREF="#MTOC_81">Ultimedia Services for AIX</A></H3>
<P>Customers upgrading to AIX 4.3.3 on systems with either the
GXT2000P or GXT3000P graphics adapter must run the <B>smit update_all</B>
command using the AIX 4.3.3 Bonus Pack CD to upgrade
<B>UMS.objects</B> to version 2.2.1.5 or
later. See the <I>AIX Version 4.3.3 Bonus Pack Release
Notes</I> for detailed instructions.
<HR><H2><A NAME="Header_82" HREF="#MTOC_82">Documentation</A></H2>
<P>This section contains information about documentation changes.
<P><H3><A NAME="Header_83" HREF="#MTOC_83">Installation and Configuration</A></H3>
<P>If you have a system that supports a GUI (Graphical User Interface) and are
running in the X-Windows System, you can use the Configuration Assistant to
install and configure the library service, or you can use the manual
method. It is highly recommend that you use Configuration Assistant
because it automatically performs some steps for you and is easier to
use. Configuration Assistant starts automatically at reboot after the
system installation. After you close Configuration Assistant, you can
reopen it from the command line by entering configassist
<P><H4><A NAME="Header_84">AIX Documentation Libraries</A></H4>
<P>The AIX Version 4.3 documentation is contained on two compact
discs:
<UL>
<LI>AIX Version 4.3 Base Documentation CD, contains the following types
of documentation:
<UL>
<LI>User guides
</LI><LI>System management guides
</LI><LI>Application programmer guides
</LI><LI>Commands reference volumes
</LI><LI>Files reference information
</LI><LI>Technical reference volumes used by application programmers
</LI></UL>
</LI><LI>AIX Version 4.3 Extended Documentation CD, contains the following
types of documentation:
<UL>
<LI>Adapter guide and reference books
</LI><LI>Technical specifications describing industry-standard functions
</LI><LI>Technical reference volumes used by system programmers
</LI></UL>
</LI></UL>
<P>These CDs contain AIX and related products documentation designed for use
with an HTML 3.2 Web browser, such as the Netscape browser that is
shipped with the AIX Version 4.3 Bonus Pack. The discs require a
CD-ROM drive. A few documents in these libraries are in PDF format and
must be viewed using the Adobe Acrobat Reader, Version 3.0.
<P>Beginning with AIX Version 4.3.3, the Documentation Library
Service allows users to navigate, read, and search registered HTML documents
using their Web browser and the library application. The library
application presents documents in an expandable-tree format that can be
navigated by clicking on button controls in the tree. This action opens
those documents for reading and also allows users to search keywords using a
search form in the application. The Documentation Library Service
searches for those words and then presents a list of results that are linked
to information contained in the online documentation files.
<P>The Documentation Library Service provides three types of Graphical User
Interfaces (GUIs) to the user, as follows:
<UL>
<LI>The Global Documentation Library Service GUI. This GUI shows all
documentation on the documentation server that has been registered with the
Global GUI. This GUI can be accessed by the icons in the Help sub-panel
in the CDE desktop.
</LI><LI>The AIX Documentation Library GUI. This GUI contains the AIX
operating system manuals. This GUI can be accessed by the icons in the
Help sub-panel in the CDE desktop.
</LI><LI>The application GUI. Applications can use the library to create
GUIs that just show the manuals for that application. This type of GUI
is typically launched from within the application. An example of this
type of GUI is the extended help GUI that is launched from within the AIX
Web-Based System Manager application.
</LI></UL>
<P>Users can access the global library application by typing
<TT>docsearch</TT> on the command line or by clicking the <B>Documentation
Library</B> icon in the Help subpanel under the CDE Desktop front
panel.
<DL><DT><B>Note:</B></DT><DD>IBM continues to ship <B>topnav.htm</B>. If you have a
bookmark to <B>topnav.htm</B>, the links out of that navigation
model will continue to work; however, the header and footer links will
take you into the Documentation Library Service, and you may not be able to
get back to <B>topnav.htm</B>. If you try to open the AIX
Version 4.3.3 Documentation Library using the AIX Library
Documentation icon and you do not have AIX 4.3.3 documentation
installed for the language you are using, you will be sent to a previous level
4.3 (for example, 4.3.2) documentation navigation
page. This page allows you to navigate to any previous level of AIX
manuals that may be installed.
</DD></DL>
<P>The documentation information is made accessible by loading it onto the
hard disk or by mounting the documentation CD in the CD-ROM drive.
While mounting the CD saves on the amount of hard disk space used, it requires
the CD be kept in the CD-ROM drive at all times. Also, searching the
documentation from the CD-ROM drive can be significantly slower (in some cases
up to ten times slower) than searching the information if it is installed on a
hard disk.
<P>You can install all of the AIX documentation from the AIX Version
4.3 Base Documentation CD and the AIX Version 4.3 Extended
Documentation CD or you can selectively install pieces of the
documentation. Some documentation may have previously been installed
with the operating system or other licensed products. Run the
<B>lslpp</B> command to determine which packages and filesets are already
installed on your system.
<P>See <I>Installation Guide</I>, SC23-4112, for information about
mounting the documentation CD-ROMs, installing documentation from these
CD-ROMs, and configuring a documentation server.
<P><H4><A NAME="Header_85">Testing the Documentation Library Service</A></H4>
<P>If you are not sure if the search service is installed and configured,
enter the following command:
<PRE>docsearch
</PRE>
<P>You will see one of the following results or messages:
<UL>
<LI>The library application appears, with no error messages and the search
form appears at the top of the page. This search form contains one or
more fields where you can enter words you want to search for. There are
documents visible in at least one of the views. Try opening a document
to read it and then searching keywords to test the search function.
<P>If everything is working correctly and you need to install some of the
operating system manuals, see "Installing the Online Documentation" section of
Installation Guide.
<P>If the search fails, go to "Problem Determination" in Chapter 19 of
<I>System Management Concepts: Operating System and
Devices</I>.
</LI><LI>There are no documents installed for this view. The library service
may be installed, but the service cannot find any installed documents that are
registered for the current view you are looking at. Try clicking on the
other views to see if they contain documents. Once you find a view with
documents, try reading and searching the documents.
<P>The library may be installed and configured correctly, but you cannot fully
test the service until documentation is installed and registered. To
install the operating system manuals go to "Installing the Online
Documentation" in <I>Installation Guide</I>. You may also install
and register any other documents that register themselves with the library
service. After you have done this, return to this section and retest
the library functions.
</LI><LI>Search is not enabled. The service is not fully installed and
configured. See "Installing the Documentation Library Service" in
Chapter 7 of the <I>Installation Guide</I>.
</LI><LI>Search is not supported in this language. The search engine cannot
perform searches in a language installed on the system. This is not an
error. This message will always be visible when you are using this
language.
</LI><LI>Cannot find or execute ds_form. The wording of this message
varies. The search service is not installed and configured
correctly. See "Manually Installing the Documentation Library Service"
in Chapter 7 of the <I>Installation Guide</I>.
</LI><LI>No browser appears. The search service is not installed and
configured correctly. See "Manually Installing the Documentation
Library Service" in Chapter 7 of the <I>Installation Guide</I>.
</LI></UL>
<P>For more information about the Documentation Library Service, see the
<B>/usr/docsearch/README</B> file. This README file ships as part
of the Documentation Library Service package on the first AIX CD.
<P><H4><A NAME="Header_86">Using the man Command</A></H4>
<P>If you are interested in viewing reference information (on topics such as
commands, subroutines, and files) by using the <B>man</B> command, you
must first install the AIX documentation. See the "Installation and
Configuration" subsection under the "Documentation" section of this
publication for more information.
<P><H4><A NAME="Header_87">Configuring the Language of the AIX Documentation</A></H4>
<P>By default, documentation that is viewed by using the <B>docsearch</B>
command or the CDE Desktop icons for the AIX Documentation or the
Documentation Library appears in the same language as the current locale of
the user's client computer.
<P>However, you may want to see the documentation in a language other than the
language of the system's or user's current default locale.
Starting in AIX 4.3.2, the documentation language can be changed
for all users on a system, or it can be changed for a single user. The
<B>chdoclang</B> utility program is available for configuring the language
of the AIX Documentation.
<P><H4><A NAME="Header_88">Locale Requisite for Documentation</A></H4>
<P>Starting with AIX Version 4.3.3, the documentation requires
its locale to be installed. The only exception is the English
documentation, which does not require the en_US locale to be installed.
<P>This prerequisite allows the unified library CGIs to collate and parse text
when the library is being searched.
<P><H4><A NAME="Header_89">Changing the Documentation Language for All Users</A></H4>
<P>To change the default documentation language for all users, the system
administrator, logged in as the root user, runs the following command:
<PRE>/usr/bin/chdoclang <I>locale</I>
</PRE>
<P>Where <I>locale</I> is the locale specification of the desired
documentation language. Running the command as the root user adds the
following line to the system's <B>/etc/environment</B> file:
<PRE>DOC_LANG=locale
</PRE>
<P>where locale is the <I>locale</I> that is the new default documentation
viewing and searching language. See the "Available Languages for AIX
Documentation Library" section for the appropriate locale name to be used with
the <B>chdoclang</B> command when configuring the language to be viewed
when selecting the Documentation Library icon.
<DL><DT><B>Note:</B></DT><DD>If the users are using a remote documentation server, the DOC_LANG variable
should be set on the user's client computer, not the remote
server. Also, the language change does not take effect until the next
time a user logs out and back into the computer.
</DD></DL>
<P>For example, when a computer's default locale is English, a user sees
English documentation when using the docsearch command or selecting the
Documentation Library icon.
<P>If the system administrator now wants all the users to see Japanese
documentation instead of English, the administrator would enter the following
command:
<PRE>/usr/bin/chdoclang Ja_JP
</PRE>
<P>Which adds the following line to the system's
<B>/etc/environment</B> file:
<PRE>DOC_LANG=Ja_JP
</PRE>
<P>A user logging out and then logging back in will now see Japanese
documentation when using the <B>docsearch</B> command or selecting the
Documentation Library icon.
<DL><DT><B>Note:</B></DT><DD>Before a computer can serve documents in a language, the AIX locale (language
environment) for that language and the translated versions of the documents
must also be installed on the documentation server.
</DD></DL>
<P><H4><A NAME="Header_90">Changing the Documentation Language for a Single User</A></H4>
<P>A user may override their system's default documentation language by
running the following command:
<PRE>/usr/bin/chdoclang locale
</PRE>
<P>Where <I>locale</I> is the locale specification of the desired
documentation language. Running the command as described above will add
the following line to the user's <B>$HOME/.profile</B> file
(when the Korn shell is the default shell of the user):
<PRE>DOC_LANG=locale; export DOC_LANG
</PRE>
<P>Where <I>locale</I> is the locale that will be the new default
documentation viewing and searching language. See the "Available
Languages for AIX Documentation Library" section for the appropriate locale
name to be used with the <B>chdoclang</B> command when configuring the
language to be viewed when selecting the Documentation Library icon.
<P>For example, when a user's default locale is Japanese, the user will
see Japanese documentation when they use the <B>docsearch</B> command or
select the Documentation Library icon.
<P>However, suppose that the Japanese documentation is not installed but the
English documentation is installed. To view the English documentation
when the default locale is set to Japanese, the user would execute the
following command:
<PRE>/usr/bin/chdoclang en_US
</PRE>
<P>Which adds the following line to the user's
<B>$HOME/.profile</B> file (when the Korn shell is the default
shell of the user):
<PRE>DOC_LANG=en_US; export DOC_LANG
</PRE>
<P>A user logging out and then logging back in will now see English
documentation when using the <B>docsearch</B> command or selecting the
Documentation Library icon.
<DL><DT><B>Note:</B></DT><DD>Defining the DOC_LANG environment variable in a user's
<B>$HOME/.profile</B> (or <B>$HOME/.cshrc</B> for C
shell users) will take precedence over any global DOC_LANG setting in their
system's <B>/etc/environment</B> file.
</DD></DL>
<P>Also, CDE users must uncomment the "DTSOURCEPROFILE=true" line in the
<B>$HOME/.dtprofile</B> file, which will cause the
<B>$HOME/.profile</B> (or <B>$HOME/.cshrc</B> for C
shell users) to be read during CDE login.
<P><H4><A NAME="Header_91">Available Languages for AIX Documentation Library</A></H4>
<P>The AIX Base Documentation is currently available in a number of different
languages. When configuring the documentation language using the
<B>chdoclang</B> command, use the following locale specifiers:
<BR>
<TABLE WIDTH="100%" BORDER>
<TR>
<TH ALIGN="LEFT" VALIGN="BOTTOM" ID="COL1" WIDTH="50%">Documentation Language
</TH><TH ALIGN="LEFT" VALIGN="BOTTOM" ID="COL2" WIDTH="50%">Locale specifier for the chdoclang command
</TH></TR><TR>
<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL1" WIDTH="50%">Brazilian-Portuguese
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="50%">pt_BR
</TD></TR><TR>
<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL1" WIDTH="50%">Catalan
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="50%">ca_ES
</TD></TR><TR>
<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL1" WIDTH="50%">Czech
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="50%">cs_CZ
</TD></TR><TR>
<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL1" WIDTH="50%">English
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="50%">en_US
</TD></TR><TR>
<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL1" WIDTH="50%">German
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="50%">de_DE
</TD></TR><TR>
<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL1" WIDTH="50%">Hungarian
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="50%">hu_HU
</TD></TR><TR>
<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL1" WIDTH="50%">Japanese
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="50%">Ja_JP
</TD></TR><TR>
<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL1" WIDTH="50%">Korean
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="50%">ko_KR
</TD></TR><TR>
<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL1" WIDTH="50%">Polish
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="50%">pl_PL
</TD></TR><TR>
<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL1" WIDTH="50%">Russian
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="50%">ru_RU
</TD></TR><TR>
<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL1" WIDTH="50%">Spanish
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="50%">es_ES
</TD></TR><TR>
<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL1" WIDTH="50%">Traditional Chinese
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="50%">Zh_TW
</TD></TR></TABLE>
<P><H3><A NAME="Header_92" HREF="#MTOC_92">InfoExplorer</A></H3>
<P>InfoExplorer is no longer a part of the AIX Base Operating System.
In AIX Version 4.3, InfoExplorer is sold as a separate AIX
feature. If you have applications or personal documentation that
requires the InfoExplorer browser, contact your point of sale to order the
InfoExplorer feature.
<P>Migration installation to AIX 4.3 preserves non-AIX InfoExplorer
documentation. Prior to installation of the InfoExplorer feature for
4.3, the <B>lppchk -v</B> utility will report that the required
software to access the InfoExplorer documentation is missing.
<HR><H2><A NAME="Header_93" HREF="#MTOC_93">WLM Commands</A></H2>
<P><H3><A NAME="Header_94" HREF="#MTOC_94">wlmassign Command</A></H3>
<P><H4><A NAME="Header_95">Purpose</A></H4>
<P>Manually assign a process to a class.
<P><H4><A NAME="Header_96">Syntax</A></H4>
<P>wlmassign <I>ClassName PID</I>
<P><H4><A NAME="Header_97">Description</A></H4>
<P>The <B>wlmassign</B> command assigns the process designated by by its
process ID, <I>PID</I> to the class named <I>ClassName</I>.
This overrides the automatic assignment.
<P>The <B>wlmassign</B> command is restricted to the root user.
<P>The <I>ClassName</I> parameter specifies the class that the process is
to. The <I>PID</I> parameter specifies the process ID of the
process to be assigned to the new class.
<P>In addition to manual assignment, AIX 4.3.3 now supports a
new class attribute called <B>inheritance</B>. This attribute, with
a <B>yes</B> or <B>no</B> value, can be added to the classes file in
the same way the <B>tier</B> attribute is, for example. The default
value is <B>no</B>, indicating that new processes will be automatically
classified upon calling "exec". If the <B>inheritance</B> attribute
is set to <B>yes</B>, a new process created by a process in the class will
remain in the class regardless of which application it executes. The
syntax in the classes file is similar to the syntax for the other
attributes. Example of the description in the classes file of a class
named "student":
<PRE>student:
   tier = 1
   inheritance = yes
</PRE>
<P>Inheritance can be used together with manual assignment to assign an
application to a class when the application starts and make sure that all the
processes spawned by the application remain in the class to which the
application was manually assigned. Inheritance can be used
independently of manual assignment.
<P>The <B>wlmassign</B> command and inheritance attribute are provided in
AIX 4.3.3 to give 4.3.3 users early access to some
of the features available in Workload Manager with AIX 5L. AIX 5L
supports both manual assignment and the inheritance attribute. The AIX
5L <B>wlmassign</B> command is a superset of the 4.3.3
command and shell scripts using the 4.3.3 <B>wlmassign</B>
command syntax will still work when users upgrade to AIX 5L. This
situation is also true for class description files (classes) using
inheritance.
<P>When trying to manually reassign to a different class several cooperating
processes sharing memory, there is a risk of seeing shared memory segments go
to the shared class because between the individual manual assignments,
processes already assigned to the new class and processes net yet assigned to
the new class access the shared memory. It is therefore better to
reassign an application before it has spawned processes and start sharing
memory, using inheritance to make sure the children remain in the new
class. If this is not possible, reassign the different processes when
the application is not actively executing.
<DL><DT><B>Note:</B></DT><DD>The AIX 5L version of WLM does not have this constraint since the AIX 5L
wlmassign command takes as a parameter a list of PIDs and WLM makes the
reassignment of all the processes as a single operation, thus preventing
"false sharing."
</DD></DL>
<P>The <B>wlmassign</B> command comes with a 4.3.3 service
update and as such does not support localization, that is, the error messages
are in English only. The possible errors are as follows:
<UL>
<LI><B>wlmassign</B> is invoked by a non-root user.
</LI><LI>Syntax errors. The command issues the "usage" string as it appears
in the Syntax paragraph above.
</LI><LI>WLM is not started.
</LI><LI>The class <I>ClassName</I> does not exist
</LI><LI>The process <I>PID</I> does not exist.
</LI></UL>
<P><H3><A NAME="Header_98" HREF="#MTOC_98">wlmset Command</A></H3>
<P><H4><A NAME="Header_99">Purpose</A></H4>
<P>Set global options for Workload Manager.
<P><H4><A NAME="Header_100">Syntax</A></H4>
<PRE>wlmset [-a hardcpumax={yes|no} ] [-a shared={yes|no} ]
</PRE>
<P><H4><A NAME="Header_101">Description</A></H4>
<P>The <B>wlmset</B> command is used to customize WLM by setting global
option flags altering the standard behavior of WLM:
<UL>
<LI>The <B>hardcpumax</B> flag determines whether the CPU maximum limits
should be treated as "soft" limits; that is, they can be exceeded if
there is no contention for the CPU resource, or as "hard" (absolute) limit
should never be exceeded, even if no other class requests any CPU
cycles.
</LI><LI>The <B>shared</B> flag determines whether shared memory segments must
be "charged" to the Shared class when they are accessed by processes in
different classes, or remain into the class they were initially assign on the
first page fault (the class of the process which first accessed the
segment).
</LI></UL>
<P>The "standard" behavior when no options are set (when the <B>wlmset</B>
command has not been used) is:
<UL>
<LI>CPU maximum limits are treated as soft limits.
</LI><LI>A segment is classified to the Shared class the first time that a process
belonging to a class different from that of the segment faults on one page of
the segment.
</LI></UL>
<P>The fact that these options are global WLM flags means that they apply to
all the classes when set. The <B>wlmset</B> command can be used
whether or not WLM is active. For consistent results, it is recommended
that the <B>wlmset</B> command be used to customize Workload Manager prior
to starting it. Otherwise, in the case of the shared memory for
instance, shared memory segments accessed by processes in different classes
will go into the Shared class (and remain there) prior to the shared flag
being set and the shared memory segments accessed by processes in different
classes after the flag has been set will remain in their class of
origin.
<P>The customization of WLM is done by setting global flags in memory, and
thus has to be done every time a system is rebooted. The best method,
when using the same set of flags for each reboot, is to run the
<B>wlmset</B> command from the <B>inittab</B> prior to starting
WLM.
<P>The <B>wlmset</B> command is restricted to the root user.
<P><H4><A NAME="Header_102">Flags</A></H4>
<P>The <B>-a</B> flag precedes a keyword indicating which option is to be
set or reset. The valid keywords are:
<DL>
<P><DT><B>hardcpumax
</B></DT><DD>Possible values are "yes" or "no". Yes indicates that the CPU
maximum limits should be treated as absolute limits and should never be
exceeded. No indicates that the CPU maximum limits should be treated as
"soft" limits and can be exceeded if there is no contention for the CPU
resource. No is the default when <B>wlmset</B> is not used or is
used without specifying the <B>hardcpumax</B> keyword.
</DD><P><DT><B>shared
</B></DT><DD>Possible values are "yes" or "no". Yes indicates that shared memory
segments should "migrate" to the Shared class when accessed (page fault) by a
process belonging to a different class as that of the segment. This is
the default when <B>wlmset</B> is not used or is used without specifying
the shared keyword. No indicates that the segment should remain in the
class it was first classified into, regardless of the class of the processes
accessing it.
</DD></DL>
<P>This command is provided in AIX 4.3.3 to give AIX
4.3.3 users early access to some of the features available in
Workload Manager with AIX 5L.
<P>AIX 5L supports both "hard" and "soft" maximum limits which can be set
independently for all resource types managed by WLM, including CPU. AIX
5L also provide a per-class attribute (localshm) to prevent shared memory
segments to go into the Shared class on a per-class basis. It is
expected that users of <B>wlmset</B> will modify their WLM configuration
files to take full advantage of the corresponding AIX 5L features when they
upgrade from AIX 4.3.3 to AIX 5L, and <B>wlmset</B> is not
supported by AIX 5L.
<P>This command comes with an AIX 4.3.3 service update and as
such does not support localization. The error messages are in English
only. The possible errors are as follows:
<UL>
<LI>The <B>wlmset</B> command is invoked by a non-root user.
</LI><LI>Syntax errors, and in this case the command issues the "usage" string as
it appears in the "Syntax" paragraph above.
</LI><LI>Trying to run the command with a version of the AIX operating system that
does not support the WLM global flags described above. This should not
happen except in cases where AIX updates have been incorrectly
installed.
</LI></UL>
<HR><H2><A NAME="HDROPTIONAL_JLP" HREF="#MTOC_103">Optional Software</A></H2>
<P>This section contains information about optional software.
<P><H3><A NAME="Header_104" HREF="#MTOC_104">Viewing Information about Optional Software</A></H3>
<P>Licensed programs include AIX 4.3 and optionally purchased
products. Each program can have one or more separately installable
filesets. Information about individual software products is available
in HTML format. To view the software products information:
<OL TYPE=1>
<LI>You must have installed an HTML Version 3.2 web browser, such as
the one available on the AIX Version 4.3 Bonus Pack.
</LI><LI>Install the Package Installation Database for Current Media software
package (pkg_gd). The home page for the Package Installation Database
for Current Media is located at:
<PRE>/usr/share/man/info/en_US/a_doc_lib/aixins/inslppkg/toc.htm
</PRE>
</LI><LI>When viewing the Package Installation Database for Current Media, check to
see if there is migration information for the databases you want to
install.
</LI></OL>
<P><H3><A NAME="Header_105" HREF="#MTOC_105">Installing NetWare</A></H3>
<P>When installing NetWare for AIX on your system using a language other than
English, do the following:
<OL TYPE=1>
<LI>Type <TT>locale</TT> at the system prompt.
</LI><LI>Note the value of the <B>LC_ALL</B> variable.
</LI><LI>Set the <B>LC_ALL</B> variable to <B>en_US</B> by using the
following command:
<PRE>export LC_ALL=en_US
</PRE>
</LI><LI>Install NetWare.
</LI><LI>After installing NetWare, reset the <B>LC_ALL</B> variable to the
original value noted in step 2.
</LI></OL>
<P><H3><A NAME="Header_106" HREF="#MTOC_106">SecureWay Directory V3.1.1 Lightweight Directory Access Protocol (LDAP)</A></H3>
<P>SecureWay Directory LDAP is shipped with AIX 4.3.3 and runs
on AIX Version 4.3.1 and later. The following information
applies to this product.
<P><H4><A NAME="Header_107">SecureWay Directory LDAP Installation Considerations</A></H4>
<P>Before installing the directory server, install only the
<B>ldap.html</B>.<I>Lang</I> package and carefully
follow the installation instructions found in the Install/Configuration Guide
(see the note below about accessing this guide). Install the
<B>ldap.html</B>.<I>Lang</I> by using SMIT or by running
the following:
<PRE>installp -acgXd /dev/cd0 ldap.html.en_US
</PRE>
<DL><DT><B>Note:</B></DT><DD>When the Installation/Configuration Guide has been installed, use your local
Web browser to view
<B>file:/usr/share/man/info/<LanguageTag>/ldap/config/aparent.htm</B>.
</DD></DL>
<P><H4><A NAME="Header_108">Special Installation Instructions for LDAP If DB2 Is Already Installed</A></H4>
<P>If you already have a version of DB2 installed, do not use the <B>Update
Installed Software to Latest Level (Update All)</B> option with the LDAP and
DB2 images packaged with AIX. This option might cause installation of a
newer version of some of your existing DB2 file sets, but the resulting DB2
image might not be usable as a DB2 server. Instead, update your DB2
installation with the latest Fixpak that is available through the normal DB2
service channels prior to installing the LDAP server. DB2 FixPaks are
available at:
<PRE>http://www.software.ibm.com/data/db2/db2tech/version5.html
</PRE>
<DL><DT><B>Note:</B></DT><DD>A full installation of DB2 Version 6.1 requires up to 255 MB of disk
space if installed with all options and all manuals for any one
language.
</DD></DL>
<P><H4><A NAME="Header_109">SecureWay Directory LDAP Enhancements</A></H4>
<P>SecureWay Directory is enhanced for AIX 4.3.3. See the
following Web site for the latest information about this product:
<PRE>http://www.software.ibm.com/network/directory
</PRE>
<P>SecureWay Directory V3.1.1 Lightweight Directory Access
Protocol (LDAP) is delivered through the following packages and
filesets:
<BR>
<TABLE WIDTH="100%" BORDER>
<TR>
<TH ALIGN="LEFT" VALIGN="BOTTOM" ID="COL1" WIDTH="33%">Package
</TH><TH ALIGN="LEFT" VALIGN="BOTTOM" ID="COL2" WIDTH="33%">Fileset
</TH><TH ALIGN="LEFT" VALIGN="BOTTOM" ID="WQ11" WIDTH="33%">Description
</TH></TR><TR>
<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL1" WIDTH="33%"><B>ldap.server</B>
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="33%">
<BR></TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ11" WIDTH="33%">SecureWay Directory Server
</TD></TR><TR>
<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL1" WIDTH="33%">
<BR></TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="33%"><B>ldap.server.rte</B>
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ11" WIDTH="33%">SecureWay Directory Server Runtime
</TD></TR><TR>
<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL1" WIDTH="33%">
<BR></TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="33%"><B>ldap.server.com</B>
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ11" WIDTH="33%">SecureWay Directory Server Framework
</TD></TR><TR>
<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL1" WIDTH="33%">
<BR></TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="33%"><B>ldap.server.admin</B>
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ11" WIDTH="33%">SecureWay Directory Server Administrative Interface
</TD></TR><TR>
<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL1" WIDTH="33%"><B>ldap.client </B>
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="33%">
<BR></TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ11" WIDTH="33%">SecureWay Directory Client
</TD></TR><TR>
<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL1" WIDTH="33%">
<BR></TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="33%"><B>ldap.client.rte </B>
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ11" WIDTH="33%">SecureWay Directory Client Runtime
</TD></TR><TR>
<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL1" WIDTH="33%">
<BR></TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="33%"><B>ldap.client.adt</B>
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ11" WIDTH="33%">SecureWay Directory Client SDK
</TD></TR><TR>
<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL1" WIDTH="33%"><B>ldap.html.</B><<I>Langd</I>> See Note
1.
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="33%">
<BR></TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ11" WIDTH="33%">SecureWay Directory Documentation
</TD></TR><TR>
<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL1" WIDTH="33%">
<BR></TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="33%"><B>ldap.html.</B><<I>Langd</I>><B>.config</B>
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ11" WIDTH="33%">SecureWay Directory Install/Config Gd - Langd
</TD></TR><TR>
<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL1" WIDTH="33%">
<BR></TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="33%"><B>ldap.html.</B><<I>Langd</I>><B>.man</B>
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ11" WIDTH="33%">SecureWay Directory Man Pages - Langd
</TD></TR><TR>
<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL1" WIDTH="33%"><B>ldap.msg.</B><<I>Langd</I>> See Note
2.
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="33%">
<BR></TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ11" WIDTH="33%">SecureWay Directory Messages
</TD></TR><TR>
<TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL1" WIDTH="33%">
<BR></TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="COL2" WIDTH="33%"><B>ldap.msg.</B><<I>Langd</I>>
</TD><TD ALIGN="LEFT" VALIGN="TOP" HEADERS="WQ11" WIDTH="33%">SecureWay Directory Messages - Langd
</TD></TR></TABLE>
<P><B>Notes: </B><OL>
<P><LI><<I>Langd</I>> stands for the following locales having
documentation; however, some portions of the documentation may not be
translated. Zh_CN, ca_ES, cs_CZ, de_DE, en_US, es_ES, fr_FR, hu_HU,
it_IT, ko_KR, pl_PL, pt_BR, ru_RU, sk_SK, and zh_TW.
<P><LI><<I>Langd</I>> stands for the following locales having message
filesets. Ca_ES, De_DE, Es_ES, Fr_FR, It_IT, Ja_JP, Zh_CN, Zh_TW,
ca_ES, cs_CZ, de_DE, en_US, es_ES, fr_FR, hu_HU, it_IT, ja_JP, ko_KR, pl_PL,
pt_BR, ru_RU, sk_SK, zh_CN, and zh_TW.
</OL>
<P><H3><A NAME="Header_110" HREF="#MTOC_110">Communications Server</A></H3>
<P>If you are using Communications Server for Systems Network Architecture
(SNA) support, you must use the following levels:
<UL>
<LI>Communications Server for AIX, Version 5:
5.0.4.3
</LI><LI>Communications Server for AIX, Version 6:
6.0.0.1
</LI></UL>
<P><H3><A NAME="Header_111" HREF="#MTOC_111">X.25 Migration and Configuration</A></H3>
<P>The following information contains procedures for migrating the
AIXLink/X.25 LPP to version 1.1.5.
<DL><DT><B>Note:</B></DT><DD>The AIXLink/X.25 LPP version 1.1.5 is supported on AIX
versions 4.1.5, 4.2.1, and 4.3.1 and
later.
</DD></DL>
<P><H4><A NAME="Header_112">Minimum Requirements for X.25 Migration</A></H4>
<P>To perform a successful migration, you must meet the following
requirements:
<UL>
<LI>AIX Version 4.1.5, 4.2.1, or
4.3.1 or later with required updates installed on the system or
be migrating to AIX Version 4.1.5, 4.2.1, or
4.3.1 or later.
</LI><LI>AIXLink/X.25 licensed product already installed on your
system.
</LI><LI>All software and hardware requirements listed in the
<I>AIXLink/X.25 LPP Guide and Reference, X.25 Installation and
Configuration</I>.
</LI></UL>
<P><H4><A NAME="Header_113">Migration Procedures</A></H4>
<P>The X.25 licensed program is delivered as an installable
image. When migrating to AIXLink/X.25 Version
1.1.5, perform the following steps to save your X.25
configuration:
<OL TYPE=1>
<LI>Use the <B>backupx25</B> command to save your system's
X.25 configuration.
<DL><DT><B>Note:</B></DT><DD>If you are migrating AIX at this time, you must back up your X.25
configuration to a file system that will be kept during in the AIX migration
process. Then <B>tar</B> this file to a disk or other removable
media.
</DD></DL>
</LI><LI>Use the <B>removex25</B> command to remove the system's
X.25 configuration.
</LI><LI>Use the <B>installp</B> command or SMIT to install AIXLink/X.25
Version 1.1.5
</LI><LI>Use the <B>restorex25</B> command to redefine your system's
X.25 configuration.
</LI></OL>
<P><H3><A NAME="Header_114" HREF="#MTOC_114">DCE/DFS Migration to AIX Version 4.3</A></H3>
<P><B>Minimum Required Levels of DCE 2.1 on AIX
4.3:</B> Some optional DCE 2.1 filesets must be
installed at or later certain levels in order for DCE to be functional on AIX
4.3. The filesets and minimum levels are as follows:
<PRE>dce.client.dfs.rte 2.1.0.24
dce.dfs_server.rte 2.1.0.21
dce.dfsnfs.rte 2.1.0.11
dce.edfs.rte 2.1.0.19
</PRE>
<P>These upgrades are necessary for the DCE Distributed File System to work on
an AIX 4.3.2 or higher system. If DFS is started on an
AIX 4.3.2 machine without these upgrades, the machine will
experience network problems and may eventually crash.
<P>For customers using the DCE Distributed File System (DFS) for AIX,
migrating an existing AIX system to AIX 4.3 will automatically upgrade
the following filesets if they exist on the system:
<PRE>DCE Client Services dce.client.core.rte 2.1.0.26
DCE Security Services dce.security.rte 2.1.0.24
DCE DFS Client Services dce.client.dfs.rte 2.1.0.24
DCE DFS Base Server dce.dfs_server.rte 2.1.0.21
DCE Enhanced DFS dce.edfs.rte 2.1.0.19
DCE NFS to DFS Authenticating Gateway dce.dfsnfs.rte
</PRE>
<P>If the automatic upgrades are not successful during the AIX 4.3
migration installation, the AIX 4.3 system installation procedure will
detect that the DCE filesets are not at the minimum required level for running
on AIX 4.3. The installation procedure will move the existing
<B>/etc/dce/rc.dce</B> file to
<B>/etc/dce/rc.dce.downlevel</B> to prevent DCE/DFS from
starting on the system.
<P>If this occurs, apply the DCE PTFs from the AIX installation media, then
reboot the system. The
<B>/etc/dce/rc.dce.downlevel</B> file can then safely be
moved back to <B>/etc/dce/rc.dce</B> and DCE/DFS started on the
system.
<P>If you install DCE filesets after installing AIX 4.3, be sure to
install the required minimum levels prior to configuring DCE on the
machine.
<P>The DCE/DFS images on the AIX CD 1 media are not LPP images; they are
DCE/DFS updates that will be applied on machines where DCE/DFS is currently
installed and the customer is migrating to AIX 4.3. The AIX
installation utilities may show them as possible installation images but you
cannot install DCE/DFS from these images. You must install DCE from the
media that DCE ships on and not the AIX CD 1 media.
<P><B>Minimum Required Levels of DCE 2.2 on AIX
4.3:</B> Some optional DCE 2.2 filesets must be
installed at or above certain levels in order for DCE to be functional on AIX
4.3.2. or higher. The filesets and minimum levels
are:
<PRE>dce.client.dfs.rte 2.2.0.2
dce.dfs_server.rte 2.2.0.2
dce.dfsnfs.rte 2.2.0.2
dce.edfs.rte 2.2.0.2
</PRE>
<P>These upgrades are necessary for the DCE Distributed File System to work on
an AIX 4.3 system. If DFS is started on an AIX 4.3
machine without these upgrades, the machine may eventually crash.
<P>For customers using the DCE Distributed File System (DFS) for AIX,
migrating an existing AIX system to AIX 4.3 will automatically upgrade
the following filesets if they exist on the system:
<PRE>DCE Client Services dce.client.core.rte 2.2.0.2
DCE Security Services dce.security.rte 2.2.0.2
DCE DFS Client Services dce.client.dfs.rte 2.2.0.2
DCE DFS Base Server dce.dfs_server.rte 2.2.0.2
DCE Enhanced DFS dce.edfs.rte 2.2.0.2
DCE NFS to DFS Authenticating Gateway dce.dfsnfs.rte 2.2.0.2
</PRE>
<P>Also, beginning with AIX Version 4.2.1, the DCE Distributed
File System (DFS) for AIX no longer supports the use of the DFS fileset backup
and restore utilities with JFS filesystems exported to DFS
<P>The DFS backup and restore utilities are as follows:
<UL>
<LI>The <B>fts</B> commands (<B>fts dump</B>, <B>fts restore</B>)
</LI><LI>The DFS Backup System (the <B>bak dump</B>, <B>bak
restoredisk</B>, <B>bak restoreft</B>, and <B>bak
restoreftfamily</B> commands)
</LI></UL>
<P>If you export JFS data to DFS from an AIX 4.2.1 or later
system, the DFS commands to dump and restore this data will display the
following message:
<PRE>Error in <dump|restore>: The system call does not exist on this system
</PRE>
<P>This occurs even if you are running the DFS commands on earlier versions of
AIX. The critical point is the level of the AIX system on the DFS File
Server where the data is being exported to DFS.
<P>Use standard AIX backup and restore utilities to back up JFS data that is
exported to DFS.
<P><H3><A NAME="Header_115" HREF="#MTOC_115">Tivoli Management Agent (TMA), Version 3.2</A></H3>
<P>The Tivoli Management Agent can be installed on your system now, or in the
future, if it is to be a managed node within the Tivoli Enterprise Software
suite.
<P>The foundation for the Tivoli Enterprise Software product suite and
third-party management products is the Tivoli Management Framework.
This framework provides the graphical desktop, object-oriented databases, and
base services used by other management products. TMA is a "lightweight"
version of the Tivoli Management Framework for installation on client
systems.
<P>For more information about Tivoli Systems products and services, including
how to become a Tivoli customer:
<OL TYPE=1>
<LI>Call: 1-800-2TIVOLI (to be connected to your local sales office)
</LI><LI>Visit the Tivoli Home page at: http://
www.tivoli.com
</LI></OL>
<P><H4><A NAME="Header_116">Installation</A></H4>
<P>Install the Tivoli_Management_Agent.client fileset (400K).
<P><H4><A NAME="Header_117">Configuration</A></H4>
<P>The installation process only copies files to the disk. See the
<B>/usr/lpp/Tivoli_Management_Agent.client/Readme.txt</B>
file for configuration instructions.
<P><H3><A NAME="Header_118" HREF="#MTOC_118">Soft5080</A></H3>
<P>Customers who want to use Soft5080 with AIX 4.3.3 or
4.2.1 to perform 5080 emulation must apply APAR IX82499.
<P><H3><A NAME="Header_119" HREF="#MTOC_119">Perl</A></H3>
<P>The following Perl filesets are shipped with AIX pursuant to the terms of
the Artistic License:
<UL>
<LI><B>perl.rte 5.6.0</B> (version 5.6)
</LI><LI><B>perl.man.en_US</B>
</LI></UL>
<P>For more information, run the <B>perl -v</B> command or to view the
Artistic License, see:
<PRE>http://www.perl.com/language/misc/Artistic.html
</PRE>
<DL><DT><B>Note:</B></DT><DD>The <B>perl.rte</B> fileset will be installed
automatically.
</DD></DL>
<P>IBM will continue to update Perl to the next stable release as new versions
of AIX are shipped. However, IBM will not support Perl.
<P>For more information about Perl, see the following Web site:
<PRE>http://www.perl.org
</PRE>
<HR><H2><A NAME="Header_120" HREF="#MTOC_120">Service</A></H2>
<P><H3><A NAME="Header_121" HREF="#MTOC_121">Electronic Fix Distribution for AIX</A></H3>
<P><H4><A NAME="Header_122">Fixes on the Internet</A></H4>
<P>You can download AIX fixes from the IBM Server Support Web site:
<PRE>http://www.ibm.com/server/support
</PRE>
<P>Registration is required to download fixes. Registration is free,
and no service agreement is necessary.
<P><H3><A NAME="Header_123" HREF="#MTOC_123">Problem Solving Databases for AIX</A></H3>
<P>Besides electronic fix distribution, IBM also provides searchable technical
databases through the World Wide Web. Much of the technical information
is available to customers with support contracts but, IBM also provides a
large assortment of technical information to any web user.
<P>You can search AIX-related bug reports and technical tips at the following
Web address:
<PRE>http://www.ibm.com/servers/support/
</PRE>
<HR><H1><A NAME="HDRNOTICES" HREF="#MTOC_124">Appendix A. Notices</A></H1>
<P>This information was developed for products and services offered in the
U.S.A.
<P>IBM may not offer the products, services, or features discussed in this
document in other countries. Consult your local IBM representative for
information on the products and services currently available in your
area. Any reference to an IBM product, program, or service is not
intended to state or imply that only that IBM product, program, or service may
be used. Any functionally equivalent product, program, or service that
does not infringe any IBM intellectual property right may be used
instead. However, it is the user's responsibility to evaluate and
verify the operation of any non-IBM product, program, or service.
<P>IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not
give you any license to these patents. You can send license inquiries,
in writing, to:
<BR>
IBM Director of Licensing <BR>
IBM Corporation <BR>
North Castle Drive <BR>
Armonk, NY 10504-1785 <BR>
U.S.A.<BR>
<P><B>The following paragraph does not apply to the United Kingdom or any
other country where such provisions are inconsistent with local
law:</B> INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Some states do not allow disclaimer of express or implied warranties in
certain transactions, therefore, this statement may not apply to you.
<P>This information could include technical inaccuracies or typographical
errors. Changes are periodically made to the information herein;
these changes will be incorporated in new editions of the publication.
IBM may make improvements and/or changes in the product(s) and/or the
program(s) described in this publication at any time without notice.
<P>Licensees of this program who wish to have information about it for the
purpose of enabling: (i) the exchange of information between
independently created programs and other programs (including this one) and
(ii) the mutual use of the information which has been exchanged, should
contact:
<BR>
IBM Corporation <BR>
Dept. LRAS/Bldg. 003 <BR>
11400 Burnet Road <BR>
Austin, TX 78758-3498<BR>
U.S.A. <BR>
<P>Such information may be available, subject to appropriate terms and
conditions, including in some cases, payment of a fee.
<P>The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer
Agreement, IBM International Program License Agreement or any equivalent
agreement between us.
<P>For license inquiries regarding double-byte (DBCS) information, contact the
IBM Intellectual Property Department in your country or send inquiries, in
writing, to:
<BR>
IBM World Trade Asia Corporation <BR>
Licensing <BR>
2-31 Roppongi 3-chome, Minato-ku <BR>
Tokyo 106, Japan<BR>
<P>IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
<P>Information concerning non-IBM products was obtained from the suppliers of
those products, their published announcements or other publicly available
sources. IBM has not tested those products and cannot confirm the
accuracy of performance, compatibility or any other claims related to non-IBM
products. Questions on the capabilities of non-IBM products should be
addressed to the suppliers of those products.
<P>Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials
for this IBM product and use of those Web sites is at your own risk.
<P>This information contains examples of data and reports used in daily
business operations. To illustrate them as completely as possible, the
examples include the names of individuals, companies, brands, and
products. All of these names are fictitious and any similarity to the
names and addresses used by an actual business enterprise is entirely
coincidental.
<P>COPYRIGHT LICENSE:
<P>This information contains sample application programs in source language,
which illustrates programming techniques on various operating
platforms. You may copy, modify, and distribute these sample programs
in any form without payment to IBM, for the purposes of developing, using,
marketing or distributing application programs conforming to the application
programming interface for the operating platform for which the sample programs
are written. These examples have not been thoroughly tested under all
conditions. IBM, therefore, cannot guarantee or imply reliability,
serviceability, or function of these programs. You may copy, modify,
and distribute these sample programs in any form without payment to IBM for
the purposes of developing, using, marketing, or distributing application
programs conforming to IBM's application programming interfaces.
<HR><H2><A NAME="Header_125" HREF="#MTOC_125">Trademarks</A></H2>
<P>The following terms are trademarks of International Business Machines
Corporation in the United States, other countries, or both:
<DL>
<DD><P>AIX
<DD><P>AIXwindows
<DD><P>AlphaWorks
<DD><P>Current
<DD><P>DB2
<DD><P>IBM
<DD><P>RS/6000
<DD><P>SecureWay
<DD><P>SP
<DD><P>Tivoli
<DD><P>Tivoli Enterprise
</DL>
<P>
<P>Java and all Java-based trademarks and logos are trademarks of Sun
Microsystems, Inc. in the United States, other countries, or
both.
<P>Other company, product, or service names may be the trademarks or service
marks of others.
<A NAME="Bot_Of_Page"></A>
</BODY></HTML>

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]