HP-UX Support Plus 11.00
Quality Pack Bundle README File
March 2002

Contents of this Document

• Bundle Notes
• Bundle Contents
  • Patch List
  • Changes from Previous Release
• Patches with Dependencies in this Bundle
  • Patch Dependencies
  • Other Dependencies
• Patches with Special Installation Instructions
  • Patch List
  • Special Instructions to Install the Patches
• Legal Notices

Bundle Notes

Please read the following entries, which describe problems or important notes for individual patches from previous releases and/or the current release. If the description applies to your system, then perform the recommended action.

PHKL_22312: VxFS I/O throttling for slow devices


PHKL_22312 introduced behavior that can cause commands that utilize
the sync(2) system call to temporarily hang while the system is
copying VxFS file system information to disk.

The behavior can affect commands such as sync(1M), bdf(1M), and
login(1).  The most noticeable symptom reported thus far has been
exceedingly long delays, up to several minutes, during user logins.

This behavior occurs when there is heavy activity on the disk.
PHKL_22312 introduced a "throttling mechanism" to improve performance
to slower devices.  Unfortunately, under heavy I/O this mechanism
causes sync(2) to intermittently wait for the disk to process I/O
requests, resulting in extended delays.

To avoid this behavior, HP recommends PHKL_22312 be removed from all
systems with VxFS file systems experiencing extended delays during the
login process, or when commands such as sync(1M) or bdf(1M) are
executed.

PHKL_22312 is found in these bundles:

  June 2001
    XSWGR1100 (B.11.00.53.2)

This note was first posted in March 2002.

PHCO_22712: ksh(1) cumulative patch


PHCO_22712 introduced behavior that may cause shell scripts utilizing
the shell special built-in command 'eval' to abort prematurely.
Depending on the shell script, this may cause unexpected results.

The expected behavior is that the shell may abort if the special
built-in command 'eval' returns a syntax error, but not if another
type of error is returned.  PHCO_22712 causes the shell to abort if
the 'eval' special built-in command returns any type of error.

If you utilize scripts that depend on the special built-in command
'eval' and this behavior is not acceptable, HP recommends removing
PHCO_22712 from all systems on which these scripts are executed.  The
patch should also be removed from software depots used to install
patches on these systems.

The previous patch, PHCO_22020, does not exhibit this same behavior.
If you choose to remove PHCO_22712, to ensure as many known issues as
possible are addressed HP recommends that PHCO_22020 be installed
after these patches are removed.

If PHCO_22020 was installed prior to PHCO_22712, it will automatically
be restored when these patches are removed and it will not need to be
reinstalled.

PHCO_22712 is found in these bundles:

  December 2001
    QPK11000 (B.11.00.54.7)

  September 2001
    QPK11000 (B.11.00.54.7)

This note was first posted in March 2002.

PHCO_23873: sh-posix(1) cumulative patch 
PHCO_22537: sh-posix(1) cumulative patch 


PHCO_22537 introduced behavior that may cause shell scripts utilizing
the shell special built-in command 'eval' to abort prematurely.
Depending on the shell script, this may cause unexpected results.

The expected behavior is that the shell may abort if the special
built-in command 'eval' returns a syntax error, but not if another
type of error is returned.  PHCO_22537 causes the shell to abort if
the 'eval' special built-in command returns any type of error.

The same behavior is exhibited with superseding patch PHCO_23873.

If you utilize scripts that depend on the special built-in command
'eval' and this behavior is not acceptable, HP recommends removing
PHCO_22537 and PHCO_23873 from all systems on which these scripts are
executed.  The patches should also be removed from software depots
used to install patches on these systems.

The previous patch, PHCO_20816, does not exhibit this same behavior.
If you choose to remove PHCO_22537 and PHCO_23873, to ensure as many
known issues as possible are addressed HP recommends that PHCO_20816
be installed after these patches are removed.  If PHCO_20816 was
installed prior to PHCO_22537 and PHCO_23873, it will automatically be
restored when these patches are removed and it will not need to be
reinstalled.  PHCO_23873 is included in the following Support Plus

PHCO_23873 is found in these bundles:

  December 2001
    QPK11000 (B.11.00.54.7)

  September 2001
    QPK11000 (B.11.00.54.7)

PHCO_22537 is found in these bundles:

  June 2001
    XSWGR1100 (B.11.00.53.2)

This note was first posted in March 2002.

PHKL_24201: VxFS quota access failure;vx_maxlink tunable
PHKL_21210: VxFS quota access failure;vx_maxlink tunable


PHKL_21210 introduced a new kernel tunable for VxFS 3.1, vx_maxlink,
which can be used to increase the limit on the number of
sub-directories per directory on a VxFS file system.  However, if this
kernel tunable parameter is set to a value exceeding 65535 and a
number of sub-directories exceeding 65535 are created in a given
directory, it can cause problems for the stat(2) system call.
Commands and applications that call stat(2), such as the ls(1) and
find(1) commands and backup utilities, may fail or report incorrectly
when accessing the sub-directories.

The same behavior is exhibited by the superseding patch PHKL_24201.

To avoid this behavior, HP recommends ensuring that the vx_maxlink
kernel tunable is set to a value less than or equal to 65535.  This
kernel tunable is normally configured in the /stand/system file.  If
the vx_maxlink kernel tunable is currently set to a value exceeding
65535, HP recommends reducing the value, rebuilding the kernel, and
rebooting the system using the newly built kernel.

Please note that the vx_maxlink kernel tunable is not automatically
configured when the patches are installed.  The value must be manually
added to the /stand/system file for this change to become effective.
Thus, it is not necessary to remove PHKL_21210 nor PHKL_24201 from
systems on which they are installed.  It is only necessary to ensure
the value, if set, does not exceed 65535.

PHKL_24201 is found in these bundles:

  March 2002
    QPK1100 (B.11.00.56.5)
  December 2001
    QPK1100 (B.11.00.54.7)
  September 2001
    QPK1100 (B.11.00.54.7)

PHKL_21210 is found in these bundles:

  June 2001
    XSWGR1100 (B.11.00.53.2)
  March 2001
    XSWGR1100 (B.11.00.52.2)
  December 2000
    XSWGR1100 (B.11.00.51.2)
  September 2000
    XSWGR1100 (B.11.00.50.5)

This note was first posted in March 2002.

PHSS_24105: B1000/B2000/C3X00/J5X00/J6000/J7000 5.0 FW


CAUTION:  PHSS_24105 will not update firmware if installed from a
golden image PHSS_24105 (11.00 B1000/B2000/C3X00/J5X00/J6000/J7000 5.0
FW patch) will not install properly and will not update the firware
properly if it is placed in a Golden Image and ignited on systems.  If
this patch is placed in a Golden Image and subsequently ignited, the
following error messages will be seen in
/var/opt/ignite/local/install.log:

  Executing: /var/adm/sw/products/PHSS_24105/pfiles/iux_postload
  ERROR: Cannot find the utility: lifcp
  ERROR: The script: /var/adm/sw/products/PHSS_24105/pfiles/iux_postload
         failed, exit code was 1
  NOTE: tlinstall is searching filesystem - please be patient
  NOTE: Successfully completed

PHSS_24105 will be listed as installed on the system, however the
firmware will not be updated.

To avoid this problem:  you can successfully install PHSS_24105 by
using Software Distributor to install one of the depots this patch
appears in, or to install just this patch.  Instructions on how to use
Software Distributor (via the swinstall command) for installation can
be found in the Support Plus User's Guide.

If you have encountered this problem:  if you placed PHSS_24105 in a
Golden Image and have already encountered the above error message, you
will need to swremove PHSS_24105, and then reinstall it using
swinstall in order to truly update the firmware.

PHSS_24105 is found in these bundles:

  March 2002
    HWE1100 (B.11.00.0203.5)
    QPK1100 (B.11.00.56.5)

  December 2001
    HWE1100 (B.11.00.0112.6)
    QPK1100 (B.11.00.54.7)

  September 2001
    XSWHWCR1100 (B.11.00.54.6)
    QPK1100 (B.11.00.54.7)

This note was first posted in December 2001.

PHKL_22940: pthread fixes, thread hang, nfs/tcp panic
PHKL_23955: pm cumulative,spinlock,IDS,q3p,prntf,lwp_SS
PHKL_23002: pthread, thread hang, nfs/tcp panic, chanq
PHKL_24752: pthrd,hang,nfs panic,chanq,prio inv,kwakeup
PHKL_24753: sig,thd,spinlock,sched,IDS,q3p,prntf,FSS,slp
PHKL_24734: sig,thd,spinlock,sched,IDS,q3p,prntf,FSS,slp
PHKL_24943: pm cumulative,spinlock,IDS,q3p,prntf,lwp_SS


PHKL_22940 introduced behavior that can result in a system
panic.  Under rare conditions, the thread sleep queue could
be corrupted.  This could lead to a system panic when the
system attempts to wake up a sleeping thread that is not
found on the sleep queue.

The sleep queue corruption, and thus the system panic, will
only occur if several specific conditions exist.  The
conditions are that a thread going to sleep must receive a
wakeup before it is completely asleep.  It must then go back
to sleep at a later time and be placed on the same sleep
queue.  If this thread is not the only thread on the sleep
queue, or is not the last thread on the sleep queue, the
panic could occur when the system attempts to wake up another
thread on the same sleep queue.

Under normal configuration and operation, this behavior
should not be experienced.  As of this date, this behavior
has only been reported by one customer.  The system that
experienced the panic was configured with an inadequate
number of sleep queues based on the configuration of the
maximum number threads.  This lead to contention on the
sleep queues, which exposed the problem.

The number of configured sleep queues is based on the kernel
parameter 'nproc', while the maximum number of kernel threads
is defined by the kernel parameter 'nkthread'.  By default,
the value of nkthread is calculated from value of nproc using
the formula nkthread=(((nproc*7)/4)+16).  The resulting
default calculation of the value of nkthread is slightly
smaller than double the value of nproc.  For example, in an
unmodified kernel nproc is set to 276 and the calculated
value of nkthread is 499.  A system using the default
calculation for nkthread or configured with an approximate
2-to-1 ratio of nkthread to nproc should not experience the
behavior.  The system that experienced the panic was
configured with nproc set to 500 and nkthread set to 15000.

This behavior exists in PHKL_22940 and superseding patches
PHKL_23002, PHKL_23955, PHKL_24752, PHKL_24753, PHKL_24734, and
PHKL_24943.

PHKL_23955 is found in these bundles:

  December 2001
    QPK1100 (B.11.00.54.7)

  September 2001
    QPK1100 (B.11.00.54.7)

PHKL_23002 is found in these bundles:

  September 2001
    XSWHWCR1100 (B.11.00.54.6)
 
  June 2001
    XSWGR1100 (B.11.00.53.2)
    XSWHWCR1100 (B.11.00.53.8)

This note was first posted in December 2001.

PHKL_23127: LVM cumulative patch, performance upgrades 


PHKL_20333 introduced behavior that can result in the LVM kernel
daemon (lvmkd) experiencing a hang when the disk load is high.  If
this occurs on a system configured as an MC/ServiceGuard or SG OPS
cluster member during the reformation of the cluster (e.g.  a node
joins or leaves the cluster), the reconfiguration of the
MC/ServiceGuard LVM daemon (cmlvmd) fails.  If this occurs, all the
nodes of a multi-node cluster fail with a TOC and single-node clusters
are not able to start or stop packages.  On clusters running
MC/ServiceGuard or SG OPS A.11.09 with PHSS_24033, or A.11.12 with
PHSS_24305 or any later version, not all nodes will fail with a TOC,
but only the one experiencing the hang of the LVM kernel daemon.

This behavior is also exhibited with superseding patches PHKL_20419,
PHKL_22267, PHKL_22266 and PHKL_23127.  To avoid this behavior, HP
recommends removing PHKL_20333, PHKL_20419, PHKL_22267, PHKL_22266 and
PHKL_23127 from all MC/ServiceGuard and SG OPS cluster nodes.  The
patches should also be removed from software depots that may be used
to install patches on these systems.

The behavior is corrected in PHKL_24268, which is released.  HP
recommends that PHKL_24268 be installed after PHKL_20333, PHKL_20419,
PHKL_22267, PHKL_22266 and PHKL_23127 are removed.  To prevent
reverting back to these patches if PHKL_24268 is removed in the
future, HP recommends that the patches be removed before PHKL_24268 is
installed.  If you choose not to remove the patches before installing
PHKL_24268, the system will still function properly after PHKL_24268
is installed.

PHKL_23127 is found in the following bundles:

   December 2001
     QPK1100 (B.11.00.54.7)

   September 2001
     QPK1100 (B.11.00.54.7)
 
   June 2001
     XSWGR1100 (B.11.00.53.2)
     XSWHWCR1100 (B.11.00.53.8)

This note was first posted in December 2001.

PHNE_18546: sendmail(1m) 8.9.3 patch 


PHNE_18546 introduced a design change to identd(1M), an identification
mechanism used by sendmail, that exposes behavior which can result in
severe performance problems on any system or a TOC on an
MC/ServiceGuard cluster node.  This behavior may be experienced on
systems that have identd(1M) enabled and also have a large number of
concurrent TCP connections.

This behavior has been exhibited on systems that have more than than
3000 concurrent TCP connections.  To determine the number of TCP
connections on a system, the following command string can be used:

  /usr/bin/netstat -a | grep -ic tcp

The identd(1M) server implements an advisory identification mechanism
that can be used by sendmail and is enabled by default.  The
identd(1M) provided in PHNE_18546 makes use of the ndd(1M) command
which results in the undesirable behavior.

To avoid this behavior, HP recommends disabling identd(1M) on all
systems that have PHNE_18546 installed.  Disabling identd(1M) will not
negatively impact the delivery of mail.  To disable identd(1M),
perform the following steps as root:

  1. Edit the /etc/inetd.conf file and comment out the
     ident line by placing a '#' in the first column:
       #ident  stream tcp wait  bin  /usr/lbin/identd  identd

  2. Force inetd(1M) to re-read the inetd.conf file by
     executing:
       /usr/sbin/inetd -c

In addition, to avoid generating ident requests, HP recommends
disabling ident lookups in the sendmail configuration file on all
systems that have PHNE_18546 installed.  To disable this feature,
perform the following steps as root:

  1. Edit the /etc/mail/sendmail.cf file as root and change
     the line:
       #O Timeout.ident=30s
     to:
       O Timeout.ident=0s

  2. Stop sendmail by executing:
       /usr/sbin/killsm

  3. Restart sendmail by executing:
       /sbin/init.d/sendmail start

Please note that leaving the line commented out does not disable ident
lookups.  The line must be uncommented and the timeout value
explicitly set to "Os" in order to stop sendmail from making ident
connections to the remote client.  Since the undesirable behavior is
easily avoided by disabling the identd(1M) functionality, HP
recommends that the feature be disabled instead of removing PHNE_18546
from the systems on which it is installed.

A new patch will be released as soon as possible to resolve this
issue.

PHNE_18546 is found in these bundles:

  June 2001:
    XSWGR1100 (B.11.00.53.2)

  March 2001:
    XSWGR1100 (B.11.00.52.2)

  December 2000:
    XSWGR1100 (B.11.00.51.2)

  September 2000:
    XSWGR1100 (B.11.00.50.5)

PHSS_21959: X/Motif 32bit Runtime AUG2000 Periodic Patch
PHSS_22946: X/Motif 32bit Runtime JAN2001 Periodic Patch


PHSS_21959 and superseding patch PHSS_22946 introduced changes that may
cause problems with the Oracle Forms application.  The forms builder (f60desm)
fails to start and displays the following message:
 
  ASSERTION FAILED: STATUS == CLIPBOARDSUCCESS, FILE UICL.C,
      LINE 985

HP recommends that you do not install PHSS_21959 or PHSS_22946 on
systems that run the Oracle Forms application.  Installing PHSS_21493 or
one of its predecessors on these systems does not exhibit this problem.
 
PHSS_21959 is found in these bundles:

  June  2001
    QPK1100 (B.11.00.51.01)

  March 2001
    XSWGR1100 (B.11.00.52.2)
    XSWHWCR1100 (B.11.00.52.3)
    QPK1100 (B.11.00.51.01)
 
  December 2000
    XSWGR1100 (B.11.00.51.2)
    XSWHWCR1100 (B.11.00.51.2)
    QPK1100 (B.11.00.51.01)

This note was first posted in June 2001.

PHCO_18676: make(1) patch 


PHCO_18676 introduces in which the system examines the wrong timestamp
when deciding if a target needs rebuilding:  if the target is a
symbolic link and the link target does not exist, the system uses the
timestamp of the symbolic link rather than that of the link target
itself.

HP recommends that you remove PHCO_18676 from systems and depots that
could experience this problem.

PHCO_18676 is found in these bundles:

  June 2001
    XSWGR1100 (B.11.00.53.2)
    QPK1100 (B.11.00.51.01)

  March 2001
    XSWGR1100 (B.11.00.52.2)
    QPK1100 (B.11.00.51.01)

  December 2000
    XSWGR1100 (B.11.00.51.2)
    QPK1100 (B.11.00.51.01)

  September 2000
    XSWGR1100 (B.11.00.50.5)
    QPK1100 (B.11.00.49.01)

  June 2000
    XSWGR1100 (B.11.00.49.3)
    QPK1100 (B.11.00.49.01)

  March 2000
    XSWGR1100 (B.11.00.48)

This note was first posted in June 2001.

PHCO_19292: login(1) cumulative patch


PHCO_19292 can result in login(1) failing to preserve the value of the
TERM environment variable during log-ins from remote systems.  The
behavior only occurs when a user logs in from a remote system using
telnet(1) and the user's password has expired. After the user provides a
new password and logs in, the TERM variable will not be set correctly

You can work around the problem by avoiding remote log-ins immediately
after a new password is set.  This problem is considered very limited
and non-destructive.

If you want to avoid this problem you will need to remove PHCO_19292
from all systems that use password aging and are accessed using
telnet(1).  The previous patch, PHCO_18572, does not exhibit this same
problem.  PHCO_18572 should be installed after you remove PHCO_19292.
If PHCO_18572 was installed prior to PHCO_19292, the system will
automatically restore it when PHCO_19292 is removed.

PHCO_19292 is found in these bundles:

  June 2001
    XSWGR1100 (B.11.00.53.2)
    QPK1100 (B.11.00.51.01)

  March 2001
    XSWGR1100 (B.11.00.52.2)
    QPK1100 (B.11.00.51.01)

  December 2000
    XSWGR1100 (B.11.00.51.2)
    QPK1100 (B.11.00.51.01)

  September 2000
    XSWGR1100 (B.11.00.50.5)
    QPK1100 (B.11.00.49.01)

  June 2000
    XSWGR1100 (B.11.00.49.3)
    QPK1100 (B.11.00.49.01)

  March 2000
    XSWGR1100 (B.11.00.48)

PHCO_18572 is not found in any Support Plus bundles.  It can be obtained
from http://itrc.hp.com or ftp://ftp.itrc.hp.com.

This note was first posted in June 2001.

PHCO_20443: memory windows cumulative patch
PHCO_16795: memory windows cumulative patch


PHCO_16795 and PHCO_20443 can remove a customized memory
windows configuration upon installation.  Both patches
deliver a default copy of /etc/services.window, which may
have been previously customized to associate applications
with memory window ids.  Such applications could experience
problems due to the default configuration being utilized
after the patches are installed.

The problem will only occur on systems that are actively
using memory windows and have customized the
/etc/services.window file.  Systems that are not using memory
windows or have not modified the /etc/services.window file
will not experience any problems.

Since it is a configuration problem that the patches
introduce, it is not necessary to remove them from systems on
which they are installed.  It may be necessary, however, to
restore the pre-existing configuration file after one of the
patches is installed.  This can be accomplished by copying
the files saved during the patch installation process:
  cp -p /var/adm/sw/save/PHCO_16795/CMDS-AUX/etc/\
    services.window /etc/services.window
  - OR -
  cp -p /var/adm/sw/save/PHCO_20443/CMDS-AUX/etc/\
    services.window /etc/services.window

If the patches were installed such that the pre-existing
files were not saved, then the /etc/services.window file will
have to be recovered from backup media or modified manually.

PHCO_20443 is found in these bundles:

  June 2001
    XSWGR1100 (B.11.00.53.2)
    XSWHWCR1100 (B.11.00.53.8)
    QPK1100 (B.11.00.51.01)

  March 2001
    XSWGR1100 (B.11.00.52.2)
    XSWHWCR1100 (B.11.00.52.3)
    QPK1100 (B.11.00.51.01)

  December 2000
    XSWGR1100 (B.11.00.51.2)
    XSWHWCR1100 (B.11.00.51.2)
    QPK1100 (B.11.00.51.01)

  September 2000
    XSWGR1100 (B.11.00.50.5)
    XSWHWCR1100 (B.11.00.50.5)
    QPK1100 (B.11.00.49.01)

  June 2000
    XSWGR1100 (B.11.00.49.3)
    XSWHWCR1100 (B.11.00.49.3)
    QPK1100 (B.11.00.49.01)

  March 2000
    XSWGR1100 (B.11.00.48)
    XSWHWCR1100 (B.11.00.48)

PHCO_16795 is found in these bundles:

  December 1999
    XSWGR1100 (B.11.00.46)
    XSWHWCR1100 (B.1100.47)

  September 1999
    XSWGR1100 (B.11.00.45)
    XSWHWCR1100 (B.11.00.46)

This note was first posted in March 2001.

PHKL_22759: SCSI IO Subsystem Cumulative Patch
PHKL_21989: SCSI IO Subsystem Cumulative Patch


PHKL_21607 can introduce symptoms that include longer boot times and
longer ioscan times.  These symptoms have only been seen on V-Class
systems with a large number (900+) LUNs on EMC disk arrays attached
via Fibre Channel.

With the patch installed, a typical boot time increases from 30 to 60
minutes; and ioscan(1M) takes up to 20 minutes (with or without the
'-k' option).

These symptoms have also been experienced with superseding patches
PHKL_22460, PHKL_22759, and PHKL_22941.

If unexpected lengthy boot or ioscan(1M) times are experienced with
any of the above patches installed, HP recommends removing those
patches and reverting to PHKL_21504.

PHKL_22759 is found in these bundles:

  June 2001
    XSWGR1100 (B.11.00.53.2) 
    XSWHWCR1100 (B.11.00.53.8) 
    
  March 2001
    XSWGR1100 (B.11.00.52.2) 
    XSWHWCR1100 (B.11.00.52.3) 

PHKL_21989 is found in these bundles:

  June 2001
    QPK100 (B.11.00.51.01) 

  March 2001
    QPK100 (B.11.00.51.01) 

  December 2000
    XSWGR1100 (B.11.00.51.2) 
    XSWHWCR1100 (B.11.00.51.2) 
    QPK100 (B.11.00.51.01) 

This note was first posted in March 2001.

PHKL_18543: PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch


PHKL_18543 was last reposted on November 06, 2000 to document a new
patch dependency on PHKL_22589.

HP recommends that you install all missing dependencies on systems
which have PHKL_18543 installed.  You do not need to reinstall
PHKL_18543.

The most current dependencies for PHKL_18543 are:

  PHCO_23876: cumulative SAM/ObAM patch
  PHCO_22453: fsck_vxfs(1M) cumulative patch
  PHKL_20016: 2nd CPU not recognized in G70/H70/I70
  PHKL_24027: VxFS 3.1 icache cumulative patch
  PHKL_22589: LOFS, select(), IDS/9000 and umount race fix
  PHKL_25210: VM, async, hyperfabric, ttrace, buffer cache

Dependencies can be satisfied with any superseding patch of the
original dependency.

PHKL_18543, with all of its dependencies, are found these bundles.

  March  2002
    HWE1100 (B.11.00.0203.5)
    QPK1100 (B.11.00.56.5)

  December  2001
    HWE1100 (B.11.00.55.5)
    QPK1100 (B.11.00.54.7)

  September 2001
    XSWHWCR1100 (B.11.00.54.6)
    QPK1100 (B.11.00.54.7)

  June 2001
    XSWGR1100 (B.11.00.53.2)
    XSWHWCR1100 (B.11.00.53.8)
    QPK1100 (B.11.00.51.01)

  March 2001
    XSWGR1100 (B.11.00.52.2)
    XSWHWCR1100 (B.11.00.52.3)

This note was first posted in March 2001.

PHNE_21376:  ONC/NFS General Release/Performance Patch


PHNE_20371 may disable access to the /etc/services file for nonroot
users.  The access rights change according to the umask(1) value set
when /sbin/init.d/nfs.core executes at system boot time.  By default,
a umask(1) of 000 is used. However, this value may be altered in any
of the /etc/rc.config.d configuration files.

You may not notice this problem if NIS services are configured.

Services such as telnet(1) and ftp(1) may fail and issue error
messages such as:

	telnet:  tcp/telnet:  unknown service ftp:
	ftp/tcp:  unknown service

Other applications may also fail if they require nonroot access to the
/etc/services file and do not provide a default udp or tcp port value.

You can fix the problem by restoring the proper access rights. For
example:

	chmod 444 /etc/services

The problem is corrected in PHNE_22125, which is released.

PHNE_21376 is found in these bundles:

  June 2001
    QPK1100 (B.11.00.51.01)

  March 2001
    QPK1100 (B.11.00.51.01)

  December 2000
    XSWGR1100 (B.11.00.51.2)
    XSWHWCR1100 (B.11.00.51.2)
    QPK1100 (B.11.00.51.01)

PHNE_22125 is found in these bundles:

  June 2001
    XSWGR1100 (B.11.00.53.2)

  March 2001
    XSWGR1100 (B.11.00.52.2)
    XSWHWCR1100 (B.11.00.52.3)

This note was first posted in December 2000.

PHKL_20419:  LVM Cumulative patch
PHKL_22267:  LVM Cumulative patch


PHKL_20333 causes the dynamic pstat(2) values for the number of open
logical volumes (psd_openlv) and number of volume groups (psd_openvg)
to always show a count of zero.  (You can see this as the GBL_NUM_VG
metric in GlancePlus remaining at zero.)

The problem also exists in superseding patches PHKL_20419 and
PHKL_22267.

PHKL_20333 is found in these bundles:

  March 2000
    XSWGR1100 (B.11.00.48)
    XSWHWCR1100 (B.11.00.48)

PHKL_20419 is found in these bundles:

  June 2001
    QPK1100 (B.11.00.51.01)

  March 2001
    QPK1100 (B.11.00.51.01)

  December 2000
    XSWGR1100 (B.11.00.51.2)
    QPK1100 (B.11.00.51.01)

  September 2000
    XSWGR1100 (B.11.00.50.5)
    XSWHWCR1100 (B.11.00.50.5)
    QPK1100 (B.11.00.49.01)

  June 2000
    XSWGR1100 (B.11.00.49.3)
    XSWHWCR1100 (B.11.00.49.3)
    QPK1100 (B.11.00.49.01)

PHKL_22267 is found in these bundles:

  March 2001
    XSWGR1100 (B.11.00.52.2)
    XSWHWCR1100 (B.11.00.52.3)

  December 2000
    XSWHWCR1100 (B.11.00.51.2)

This note was first posted in December 2000.

PHCO_19047: Cumulative SAM/ObAM Patch
PHCO_21187: Cumulative SAM/ObAM Patch


When PHCO_19047 or its superseding patch PHCO_21187, is installed on a
system which contains a PCI 100BT LAN interface card, PHNE_21220 (PCI
100BT/F cumulative patch) must be installed.  If the system contains
an A5506 card, then PHNE_20423 (4 port PCI 100BASE-T cumulative patch)
must also be installed.

After PHNE_21220 is installed, its new configuration
file(/usr/newconfig/etc/rc.config.d/hpsppci100conf) must be merged
with the existing configuration file(/etc/rc.config.d/hpsppci100conf).

After PHNE_20423 is installed, its new configuration
file(/usr/newconfig/etc/rc.config.d/hpbtlanconf) must be merged with
the existing configuration file(/etc/rc.config.d/hpbtlanconf).

Without PHNE_21220, PHNE_20423, and the manual copy steps, the "Network
Interface Cards" area of SAM may produce the message "invalid duplex
value for interface" or display odd combinations of the Autoneg, Speed,
and Duplex Mode selections when PHCO_19047 is installed, and, when
PHCO_21187 is installed, may produce a message instructing the user to
copy the latest configuration file from /usr/newconfig/rc.config.d.

PHNE_20423 is found in these bundles:

  December 2000
    XSWHWCR1100 (B.10.20.51.2)

  September 2000
    XSWHWCR1100 (B.10.20.50.5)

PHNE_21220 is found in these bundles:

  June 2001
    QPK1100 (B.11.00.51.01)

  March 2001
    QPK1100 (B.11.00.51.01)

  December 2000
    QPK1100 (B.11.00.51.01)

  September 2000
    XSWHWCR1100 (B.10.20.50.5)

PHCO_19047 is found in these bundles:

  September 2000
    QPK1100 (B.11.00.49.01)

  June 2000
    XSWGR1100 (B.10.20.49.3)
    XSWHWCR1100 (B.10.20.49.3)
    QPK1100 (B.11.00.49.01)

PHCO_21187 is found in these bundles:

  June 2001
    QPK1100 (B.11.00.51.01)

  March 2001
    XSWGR1100 (B.11.00.52.2)
    QPK1100 (B.11.00.51.01)

  December 2000
    XSWGR1100 (B.11.00.51.2)
    XSWHWCR1100 (B.11.00.51.2)
    QPK1100 (B.11.00.51.01)

  September 2000
    XSWGR1100 (B.10.20.50.5)
    XSWHWCR1100 (B.10.20.50.5)

This note was first posted in June 2000.

PHCO_19047:cumulative SAM/ObAM patch
PHCO_20765:libc cumulative patch


PHCO_19047 interacts with PHCO_20765 to cause a core dump when you
manually enter a baud rate in the terminal configuration dialog for
the SAM utility.

To reach the terminal configuration dialog:

  1) Enter SAM.

  2) Enter the "Peripheral Devices" area.

  3) Enter "Terminals and Modems" area.

  4) Select the "Actions" menu.

  5) Select "Add Terminal". This opens the terminal configuration
     dialog box.

SAM will core dump if you manually move the cursor to the "Speed (Baud
Rate) ..."  text entry field, type a value, then press the "Enter" key
or click "OK".

The problem is corrected in PHCO_21187, which is released.

PHCO_19047 is found in these bundles:

  September 2000
    QPK1100 (B.11.00.49.01)

  June 2000
    XSWGR1100 (B.11.00.49.3)
    XSWHWCR1100 (B.11.00.49.3)
    QPK1100 (B.11.00.49.01)

PHCO_20765 is found in these bundles:

  June 2001:
    QPK1100 (B.11.00.51.01)

  March 2001:
    QPK1100 (B.11.00.51.01)

  December 2000
    XSWGR1100 (B.11.00.51.2)
    QPK1100 (B.11.00.51.01)

  September 2000
    XSWGR1100 (B.11.00.50.5)
    XSWHWCR1100 (B.11.00.50.5)
    QPK1100 (B.11.00.49.01)

  June 2000
    XSWGR1100 (B.11.00.49.3)
    XSWHWCR1100 (B.11.00.49.3)
    QPK1100 (B.11.00.49.01)

PHCO_21187 is found in these bundles:

  June 2001:
    QPK1100 (B.11.00.51.01)

  March 2001
    XSWGR1100 (B.11.00.52.2)
    QPK1100 (B.11.00.51.01)

  December 2000
    XSWGR1100 (B.11.00.51.2)
    XSWHWCR1100 (B.11.00.51.2)
    QPK1100 (B.11.00.51.01)

  September 2000
    XSWGR1100 (B.11.00.50.5)
    XSWHWCR1100 (B.11.00.50.5)

This note was first posted in June 2000.

PHSS_21621: B1K/B2K/C3X00/J5X00/J6K/J7K 4.0 FW update


PHKL_21621 will add support for J6000, fix a cache self-test failure,
fix LPMC handler so it doesn't touch any RDR registers during
processing, enables support for B5506A ethernet card, fix PCI memory
allocator to support J3525A, J2526A X.24 cards, fix a RS232 hang
during early chassis codes for 3 wire RS232 connections, and read
status command twice to fix a Mitsumi CD ROM problem on B2K.

PHSS_21621 changes the system firmware revision to 4.0, unless it is
already at revision 4.0 or greater.  This patch will execute a
download tool only on the new workstation models:  B1000, B2000,
C3X00, J5X00, J6000, and J7000.  The download tool is automatically
executed at the scheduled reboot time after installing selected
patches.  Please allow the firmware update to complete and boot the
system with the new 4.0 firmware.  The tool initially changes boot
information on your root disk to execute the reflash program, then it
restores the boot information.  Any interruption to the firmware
update may leave your workstation in an unusable state.

PHSS_21621 is found in these bundles:
   
  June 2001
    QPK1100 (B.11.00.51.01)

  March 2001
    QPK1100 (B.11.00.51.01)

  December 2000
    XSWGR1100 (B.11.00.51.2)
    XSWHWCR1100 (B.11.00.51.2)
    QPK1100 (B.11.00.51.01)

  September 2000
    XSWGR1100 (B.11.00.50.5)
    XSWHWCR1100 (B.11.00.50.5)

This note was first posted in September 2000.

Bundle Contents

This section contains a list of all patches in this bundle, the changes in the bundle since it was last released.

Click on the patch name to view the patch text file.

Patch List

Changes from Previous Release

Click on the patch name to view the patch text file.

This bundle was last refreshed for the March 2002 release.

NEW PATCHES
No new patches were added.

---

Patches with Dependencies in this Bundle

Patch Dependencies

The following table lists patch dependencies for patches in this bundle.

Click on the patch name to view the patch text file.

SUPERSEDED PATCHES
No patches were superseded.

Patch ID	Dependencies	Description
PHCO_16527		eucset(1) patch
	PHNE_25385	Streams Pty cumulative patch
PHCO_16748		mt(1) new reserve, release, status options
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHCO_18276		cumulative date(1) patch
	PHCO_24148	libc cumulative patch
PHCO_19640		SCSI passthru device man page
	PHKL_24004	SCSI IO Subsystem Cumulative Patch
PHCO_19656		mkboot(1M) cumulative patch
	PHCO_24148	libc cumulative patch
PHCO_20029		cumulative cp(1) patch
	PHCO_24148	libc cumulative patch
	PHKL_22677	fix of getdirentries, MVFS, rcp, mmap & IDS
PHCO_20030		Enhance ln(1) to work with JFS ACLs
	PHCO_24148	libc cumulative patch
	PHKL_22677	fix of getdirentries, MVFS, rcp, mmap & IDS
PHCO_20031		Enhance ls(1) to work with JFS ACLs
	PHCO_24148	libc cumulative patch
	PHKL_22677	fix of getdirentries, MVFS, rcp, mmap & IDS
PHCO_20032		Enhance mv(1) to work with JFS ACLs
	PHCO_24148	libc cumulative patch
	PHKL_22677	fix of getdirentries, MVFS, rcp, mmap & IDS
PHCO_20033		Enhance rm(1) to work with JFS ACLs
	PHCO_24148	libc cumulative patch
	PHKL_22677	fix of getdirentries, MVFS, rcp, mmap & IDS
PHCO_20034		Enhance shar(1) to work with JFS ACLs
	PHCO_24148	libc cumulative patch
	PHKL_22677	fix of getdirentries, MVFS, rcp, mmap & IDS
PHCO_20035		Enhance compact(1) to work with JFS ACLs
	PHCO_24148	libc cumulative patch
	PHKL_22677	fix of getdirentries, MVFS, rcp, mmap & IDS
PHCO_20036		Enhance compress(1) to work with JFS ACLs
	PHCO_24148	libc cumulative patch
	PHKL_22677	fix of getdirentries, MVFS, rcp, mmap & IDS
PHCO_20038		cumulative pack(1) patch
	PHCO_24148	libc cumulative patch
	PHKL_22677	fix of getdirentries, MVFS, rcp, mmap & IDS
PHCO_20039		Enhance unpack(1) to work with JFS ACLs
	PHCO_24148	libc cumulative patch
	PHKL_22677	fix of getdirentries, MVFS, rcp, mmap & IDS
PHCO_20575		Cumulative find(1) patch
	PHCO_24148	libc cumulative patch
	PHKL_22677	fix of getdirentries, MVFS, rcp, mmap & IDS
PHCO_21040		kmadmin is modified due to defect in modadm
	PHKL_23329	panic, fails for coredump, drivers
PHCO_21596		mksf(1M) cumulative patch
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
	PHNE_24762	telnet kernel and telnetd(1M) patch
PHCO_21854		HPDPS cumulative patch
	PHCO_25110	lpspool subsystem cumulative patch
PHCO_21901		fuser(1M) cumulative patch
	PHKL_22986	cumulative pstat patch
PHCO_22592		pipcs(1) and pipcrm(1) patch
	PHKL_22986	cumulative pstat patch
PHCO_22676		swapinfo(1M) patch
	PHKL_22771	fix device and file system swap problems
PHCO_22899		DLKM configuration tools cumulative patch
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHCO_23118		df(1M) cumulative patch
	PHCO_24148	libc cumulative patch
PHCO_23325		libc cumulative man page patch
	PHCO_24448	cumulative patch for syslogd(1M)
PHCO_23651		fsck_vxfs(1M) cumulative patch
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHCO_23652		/etc/default/tz patch
	PHCO_24148	libc cumulative patch
PHCO_23705		memory windows cumulative patch
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHCO_23792		libpthreads cumulative patch
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHCO_23854		cumulative fbackup(1M)/frecover(1M) patch
	PHCO_24148	libc cumulative patch
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
	PHKL_22677	fix of getdirentries, MVFS, rcp, mmap & IDS
	PHKL_24221	SCSI Tape (stape) cumulative
PHCO_24148		libc cumulative patch
	PHCO_23963	libc cumulative header file patch
	PHKL_23226	syscall, msem_lock, umask cumulative patch
PHCO_24168		cumulative cpio(1) patch
	PHCO_24148	libc cumulative patch
	PHKL_22677	fix of getdirentries, MVFS, rcp, mmap & IDS
PHCO_24437		LVM commands cumulative patch
	PHKL_24268	LVM Kernel Cumulative Patch
PHCO_24633		Cumulative tar(1) patch
	PHCO_24148	libc cumulative patch
	PHKL_22677	fix of getdirentries, MVFS, rcp, mmap & IDS
PHCO_24963		pthread(3t) cumulative man page patch
	PHCO_23325	libc cumulative man page patch
PHCO_25418		pax(1) cumulative patch
	PHKL_22677	fix of getdirentries, MVFS, rcp, mmap & IDS
PHCO_25527		libpam and libpam_unix cumulative patch
	PHCO_24189	cumulative passwd(1) patch
	PHNE_24909	ONC/NFS General Release/Performance Patch
PHKL_17019		ttrace(2) man page update
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_18543		PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
	PHCO_23651	fsck_vxfs(1M) cumulative patch
	PHCO_23876	cumulative SAM/ObAM patch
	PHKL_20016	2nd CPU not recognized in G70/H70/I70
	PHKL_24027	VxFS 3.1 cumulative patch
	PHKL_25475	PM cumulative patch
	PHKL_25525	Probe,IDDS,PM,VM,PA-8700,asyncio,T600,FS
PHKL_19246		vm_superpage patch
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_19286		Enable boot-time hooks for 3rd party driver
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_19734		diag1 add PCI subvendor info,FC card support
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_20016		2nd CPU not recognized in G70/H70/I70
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_20165		New workstation WSIO support
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_20170		Dino (GSCtoPCI) spinlock fixes
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_20228		Large Data Space (7 of 8)
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_20400		inherited attrs cause panic in file creation
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_20473		I/O forwarding patch
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_20873		patch for kernel stack unwinding
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_20900		Add missing crash dump debug information
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_20915		trap-related panics/hangs
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_20937		Fix for TOC vector overwriting
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_20966		Add dump debug information for IDE driver
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_20989		Cumulative dump device, dump size patch
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_21039		semget;large data space;msgmnb;SEMMSL
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_21120		patch for kernel stack unwinding
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_21161		patch for inaccurate isr.ior printout
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_21180		Improved largepage performance for data
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_21280		Corrects A180 port access card chassis code
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_21352		rtsched(1) enhancement, IDS/9000 support
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_21359		Enable IDS/9000 support
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_21364		dynamic spinlock inlining missing opcodes
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_21420		specify diag2 as MP-safe
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_21549		Cumulative gang scheduling patch
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_21678		Disk sort algorithm fix for slow io response
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_21680		Fix panic on deadlock: NULL thread ptr
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_22208		Fix VxFS DMAPI DPFs and Memory Leak
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_22264		AIO panic fix and performance improvement
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_22330		callout list corruption/panic fix
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_22377		PC floppy cumulative patch
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_22635		fix ufs inode hangs & race of mkdir, umount
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_22677		fix of getdirentries, MVFS, rcp, mmap & IDS
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_22684		fix unexpected interrupt msg
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_22785		HPMC, FC reset & conn, chassis log, I20 RAID
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_22792		Fix VM page read-ahead panics
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_22840		IDS/9000; syscalls related to file/socket
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_22926		Incomplete Selective Dump, TOC/Panic Failure
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_22975		VM 32bit I/O requests kept in I/O space
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_22976		FXE perf, server patch, cumulative graphics
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
	PHKL_22975	VM 32bit I/O requests kept in I/O space
PHKL_22986		cumulative pstat patch
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_23193		VxFS cumulative patch
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_23226		syscall, msem_lock, umask cumulative patch
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_23329		panic, fails for coredump, drivers
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_23409		NFS, Large Data Space, kernel memory leak
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_23853		debug shared lib; bsema waitlist corruption
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_23901		remove stopped threads from load averages
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_23902		pthread_detach race condition thread leak
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_23939		Fibre Channel Mass Storage Driver Patch
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_23956		Profile, virtual timers and disabling fix
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_24004		SCSI IO Subsystem Cumulative Patch
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
	PHKL_24187	ioscan performance gain for SCSI Subsystem
PHKL_24005		fixes erroneous EFAULT (Bad address) return
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_24011		JFS 3.1 mount,fsck,corruption patch
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_24021		Fix for kthread b_sema wait queue corruption
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_24027		VxFS 3.1 cumulative patch
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_24055		pages deallocated in pdt_read on L-class
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_24074		PCI cumulative patch
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
	PHKL_24279	Directed range,PIOP,PAT and high temp Alerts
PHKL_24201		JFS;stickybit;quota access;vx_maxlink tunabl
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_24221		SCSI Tape (stape) cumulative
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_24251		copy is unsafe to or near I/O space
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_24266		DNLC panic and Enable IDS/9000 support
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_24268		LVM Kernel Cumulative Patch
	PHCO_24437	LVM commands cumulative patch
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
	PHKL_25525	Probe,IDDS,PM,VM,PA-8700,asyncio,T600,FS
PHKL_24279		Directed range,PIOP,PAT and high temp Alerts
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
	PHKL_24074	PCI cumulative patch
PHKL_24487		LP64 maxdsiz; max msgmnb; major no; maxfiles
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_24729		IO pdir, SBA, async IO deadlock, PA-8700
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_24905		VxFS mount/unmount problems
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_25010		Cumulative USB Driver patch
	PHKL_20165	New workstation WSIO support
	PHKL_22976	FXE perf, server patch, cumulative graphics
PHKL_25352		dump, PSW, PA-8700, printf cumulative fix
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_25475		PM cumulative patch
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_25525		Probe,IDDS,PM,VM,PA-8700,asyncio,T600,FS
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_25725		Cumulative vfork(2) patch
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHKL_25813		Cumulative mmap fixes
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHNE_15537		Fibre Channel cumulative patch
	PHNE_21767	cumulative ARPA Transport patch
PHNE_17104		gated(1M) patch
	PHNE_21767	cumulative ARPA Transport patch
	PHNE_25116	Cumulative STREAMS Patch
PHNE_20536		HP-PB Token Ring Cumulative Patch
	PHNE_24413	LAN product cumulative patch
PHNE_20874		PCI FDDI B.11.00.[01-03,05,08,11-13] patch
	PHNE_24413	LAN product cumulative patch
PHNE_21390		HSC FDDI B.11.00.0[0-7] cumulative patch
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHNE_21767		cumulative ARPA Transport patch
	PHNE_25116	Cumulative STREAMS Patch
PHNE_21835		inetd(1M) cumulative patch
	PHNE_21767	cumulative ARPA Transport patch
PHNE_22033		ATM PCI, HSC and HP-PB cumulative patch
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHNE_22034		ATM PCI, HSC and HP-PB cumulative patch
	PHKL_18543	PM/VM/UFS/async/scsi/io/DMAPI/JFS/perf patch
PHNE_22244		Built-in PCI 100BASE-T patch
	PHNE_24413	LAN product cumulative patch
	PHNE_25116	Cumulative STREAMS Patch
PHNE_22461		HSC 100BT lan cumulative patch
	PHNE_24413	LAN product cumulative patch
	PHNE_25116	Cumulative STREAMS Patch
PHNE_23982		HP-PB 100Base-T cumulative patch
	PHNE_24413	LAN product cumulative patch
PHNE_24007		4 port PCI 100BASE-T cumulative patch
	PHNE_24413	LAN product cumulative patch
	PHNE_25116	Cumulative STREAMS Patch
PHNE_24307		1000Base-SX/T B.11.00.[02-11] cumul. patch
	PHKL_24729	IO pdir, SBA, async IO deadlock, PA-8700
	PHNE_24413	LAN product cumulative patch
	PHSS_24105	B1000/B2000/C3X00/J5X00/J6000/J7000 5.0 FW
PHNE_24308		APA cumulative patch
	PHNE_24413	LAN product cumulative patch
PHNE_24392		PCI 100B(Tx/Fx) cumulative patch
	PHNE_24413	LAN product cumulative patch
	PHNE_25116	Cumulative STREAMS Patch
PHNE_24413		LAN product cumulative patch
	PHNE_25116	Cumulative STREAMS Patch
PHNE_24725		EISA 100BT patch
	PHNE_24413	LAN product cumulative patch
PHNE_24762		telnet kernel and telnetd(1M) patch
	PHCO_21596	mksf(1M) cumulative patch
	PHCO_24542	libsec cumulative patch
PHNE_24909		ONC/NFS General Release/Performance Patch
	PHCO_23117	bdf(1M) cumulative patch
	PHCO_24148	libc cumulative patch
	PHKL_25475	PM cumulative patch
	PHNE_25116	Cumulative STREAMS Patch
PHNE_25116		Cumulative STREAMS Patch
	PHNE_21767	cumulative ARPA Transport patch
PHNE_25580		PCI 100BT lan cumulative patch
	PHNE_24413	LAN product cumulative patch
	PHNE_25116	Cumulative STREAMS Patch
PHSS_19069		Asian Printer cumulative patch
	PHCO_21854	HPDPS cumulative patch
	PHSS_20192	Asian Utility NOV 1999 cumulative patch
PHSS_20445		HP DCE/9000 1.7 Integrated Login cum. patch
	PHSS_20444	HP DCE/9000 1.7 Runtime cumulative patch
PHSS_20446		HP DCE/9000 1.7 Server/DevTools cum. patch
	PHCO_23792	libpthreads cumulative patch
	PHSS_20444	HP DCE/9000 1.7 Runtime cumulative patch
PHSS_22750		TechPrintServ Dec 2000 Periodic Patch
	PHSS_25194	CDE Runtime OCT2001 Periodic Patch
	PHSS_25447	X/Motif 32bit Runtime OCT2001 Periodic Patch
PHSS_22758		AudioKernelThread Dec 2000 Periodic Patch
	PHSS_20444	HP DCE/9000 1.7 Runtime cumulative patch
	PHSS_20446	HP DCE/9000 1.7 Server/DevTools cum. patch
	PHSS_24608	AudioSubsystem July 2001 Periodic Patch
PHSS_24381		LIBCL patch
	PHSS_24832	MILLI/ASM cumulative patch
PHSS_24931		Japanese TrueType fonts patch
	PHSS_25091	X Font Server SEP2001 Periodic Patch
PHSS_24933		Korean TrueType font patch
	PHSS_25091	X Font Server SEP2001 Periodic Patch
PHSS_24935		Chinese-S TrueType font patch for 11.00
	PHSS_25091	X Font Server SEP2001 Periodic Patch
PHSS_25194		CDE Runtime OCT2001 Periodic Patch
	PHCO_25527	libpam and libpam_unix cumulative patch
	PHNE_25385	Streams Pty cumulative patch
	PHSS_25199	CDE Msg Cat OCT2001 Periodic Patch
	PHSS_25447	X/Motif 32bit Runtime OCT2001 Periodic Patch
PHSS_25254		PEX 5.1/Starbase/Hardcopy Run (PA2.0 only)
	PHSS_25253	3D Common Run (PA2.0 only)
PHSS_25255		DDA Run (PA2.0 only)
	PHSS_25253	3D Common Run (PA2.0 only)
	PHSS_25254	PEX 5.1/Starbase/Hardcopy Run (PA2.0 only)
PHSS_25256		PEX 5.1 Run (PA2.0 only)
	PHSS_25253	3D Common Run (PA2.0 only)
	PHSS_25254	PEX 5.1/Starbase/Hardcopy Run (PA2.0 only)
PHSS_25257		PEX 5.1 Dev (PA2.0 only)
	PHSS_25253	3D Common Run (PA2.0 only)
	PHSS_25254	PEX 5.1/Starbase/Hardcopy Run (PA2.0 only)
	PHSS_25255	DDA Run (PA2.0 only)
	PHSS_25256	PEX 5.1 Run (PA2.0 only)
PHSS_25258		Starbase/Hardcopy Dev (PA2.0 only)
	PHSS_25253	3D Common Run (PA2.0 only)
	PHSS_25254	PEX 5.1/Starbase/Hardcopy Run (PA2.0 only)
	PHSS_25255	DDA Run (PA2.0 only)
	PHSS_25256	PEX 5.1 Run (PA2.0 only)
PHSS_25259		PHIGS Run (PA2.0 only)
	PHSS_25253	3D Common Run (PA2.0 only)
	PHSS_25254	PEX 5.1/Starbase/Hardcopy Run (PA2.0 only)
	PHSS_25255	DDA Run (PA2.0 only)
	PHSS_25256	PEX 5.1 Run (PA2.0 only)
PHSS_25260		PHIGS Dev (PA2.0 only)
	PHSS_25253	3D Common Run (PA2.0 only)
	PHSS_25254	PEX 5.1/Starbase/Hardcopy Run (PA2.0 only)
	PHSS_25255	DDA Run (PA2.0 only)
	PHSS_25256	PEX 5.1 Run (PA2.0 only)
	PHSS_25259	PHIGS Run (PA2.0 only)
PHSS_25261		OpenGL 1.1 Run (PA2.0 only)
	PHSS_23566	Xserver cumulative patch
	PHSS_25253	3D Common Run (PA2.0 only)

Other Dependencies

The following patches have non-patch dependencies, such as dependencies on other software products or hardware, or are conditional on other patches. If you are loading these patches, please read the instructions carefully.

PHCO_22592 pipcs(1) and pipcrm(1) patch

	s700: 11.00: PHKL_21588 PHKL_21778 PHKL_21684
	s800: 11.00: PHKL_21588 PHKL_21778 PHKL_21684
	PHKL_22588 and PHCO_22592 together provide an
	enhancement so that the customer is able to use
	commands to display the information about POSIX
	message queues and named semaphores as well as
	remove them.
	PHKL_21684, PHKL_21518, PHKL_21778 together provide
	an enhancement to increase the SysV IPC MSGMNB
	message queue capacity.  To enable the enhancement,
	both PHKL_21684 and PHKL_21518 must be installed,
	and PHKL_21778 is required if SAM support is desired
	to modify system tunables.  Each may be installed
	independently of the others.

	This patch provides the utilities for the HP Fibre
	Array/60. To use the utilities an HP Fibre Array/60
	array must be connected and configured to the system.

	This patch provides the utilities for the HP
	Array with AutoRAID. It requires the
	OS-Core.C2400-UTIL fileset to be installed for
	the array status to monitored properly.
	To use the utilities an HP AutoRAID array
	must be connected and configured to the system.

	To enable the TLS feature, the following patches should
	also be installed:
	PHCO_24148 libc cumulative patch
	PHSS_23440 linker cumulative patch
	PHSS_23785 linker startup patch
	PHSS_23953 Fortran90 B.11.01 patch

	PHCO_24148: JAGab20870
	The tzset()  behaviour  have been changed to take default TZ
	values  from  the file /etc/default/tz.  A  sample  file  is
	released as patch PHCO_23652.  The /etc/default/tz  included
	in  the  patch  contains  the  earlier  default  value  ie.,
	EST5EDT.  So unless the user  explicitly  changes  the value
	contained in the file the tzset changes are  transparent  to
	the user.  The file  /etc/default/tz  contains  the timezone
	value set by tzset() when the environment variable TZ is not
	set.  The format  for the file is same as TZ format  without
	the prefix  "TZ=".  Please check  environ(5)  for TZ format.
	The order of TZ setting is as follows.
	1) if the environment variable TZ is present, it takes the
	precedence.
	2) if TZ is not present, then the value contained in
	/etc/default/tz is used for default.
	3) if /etc/default/tz is not set, then the default value is
	equivalent to EST5EDT (Eastern Standard Time) of US.

	- If HyperFabric B.11.00.00 or HyperFabric B.11.00.01 is
	installed, PHNE_16199 must also be installed.
	- If OnLine JFS is installed and applications utilizing
	DMAPI, such as OmniStorage, are being used PHKL_22208
	should also be installed.

	s700: 11.00: PHKL_21684 PHKL_21778
	s800: 11.00: PHKL_21684 PHKL_21778
	PHKL_21684, PHKL_21518, PHKL_21778 together provide
	an enhancement to increase the SysV IPC MSGMNB
	message queue capacity.  To enable the enhancement,
	both PHKL_21684 and PHKL_21518 must be installed,
	and PHKL_21778 is required if SAM support is desired
	to modify system tunables.  Each may be installed
	independently of the others.

	
	A.20.00), PHSS_21427 is also required to completely fix the
	problem of mpc_bindlwp messages being logged to
	/var/adm/syslog/syslog.log.  For Support Tool Manager
	versions B.11.00.13.* (STM A.21.00) and higher, only
	PHKL_21420 is required to fix the problem.

	The commands patch PHCO_22676 fixes the swapinfo(1M)
	utility to correctly display file system swap over
	1.5GB.

	The patch PHKL_22976 should be installed, along with this
	one, on server systems that use graphics cards.  If only
	this patch is installed, but not PHKL_22976 or a successor,
	then the panic is still possible, although a warning
	message will be place in the system message buffer.

	s700: 11.00: PHKL_21518 PHKL_21778
	s800: 11.00: PHKL_21518 PHKL_21778
	PHKL_21684, PHKL_21518, PHKL_21778 together provide
	an enhancement to increase the SysV IPC MSGMNB
	message queue capacity.  To enable the enhancement,
	both PHKL_21684 and PHKL_21518 must be installed,
	and PHKL_21778 is required if SAM support is desired
	to modify system tunables.  Each may be installed
	independently of the others.
	s700: 11.00: PHCO_22592
	s800: 11.00: PHCO_22592
	PHKL_22588 and PHCO_22592 together provide an
	enhancement so the customer is able to use commands
	to display the information about POSIX message
	queues and named semaphores as well as remove them.

	PHKL_23409:
	If NFS is installed on the system, all five patches
	(PHNE_23249, PHKL_23406, PHKL_23407, PHKL_23408, PHKL_23409)
	are required to resolve the process hang/deadlock due to
	unkillable processes executed over NFS.  However, if NFS is
	not in use, none of these patches are required.

	s700: 11.00: PHKL_21518 PHKL_21684
	s800: 11.00: PHKL_21518 PHKL_21684
	PHKL_21684, PHKL_21518, PHKL_21778 together provide
	an enhancement to increase the SysV IPC MSGMNB
	message queue capacity.  To enable the enhancement,
	both PHKL_21684 and PHKL_21518 must be installed,
	and PHKL_21778 is required if SAM support is desired
	to modify system tunables.  Each may be installed
	independently of the others.

	PHKL_23814:
	Two other patches work in conjuction with this patch
	to enable PA-8700 support. These other two patches are
	PHKL_23813 and PHKL_23815.

	PHKL_23815:  Two other patches work in conjuction with this
	patch to enable PA-8700 support.  These other two patches
	are PHKL_23813 and PHKL_23814.

	PHKL_23617:  PHKL_23842:  Six patches work together to
	implement this change:  PHKL_23617, PHKL_23842, PHKL_20943,
	PHKL_20944, PHKL_20945, and PHKL_21024 to reduce dispatch
	latency for higher priority runnable threads.  These patches
	may be installed in any order or combination, or not at all
	(if the reduced dispatch latency feature is not desired).
	PHKL_23406:  PHKL_23407:  If NFS is installed on the system,
	all five patches (PHNE_23249, PHKL_23406, PHKL_23407,
	PHKL_23408, PHKL_23409) are required to resolve the process
	hang/deadlock due to unkillable processes executed over NFS.
	However, if NFS is not in use, none of these patches are
	required.  All five of these patches may be installed
	independently.  If fewer than four out of the four PHKL
	patches are installed the P_NOSTOP feature will not be
	enabled.

	PHKL_21549 is required when using the gang scheduler.
	Without PHKL_21549, the gang scheduler exhibits unacceptable
	performance after this patch is installed.
	PHKL_23406:  If NFS is installed on the system, all five
	patches (PHNE_23249, PHKL_23406, PHKL_23407, PHKL_23408,
	PHKL_23409) are required to resolve the process
	hang/deadlock due to unkillable processes executed over NFS.
	However, if NFS is not in use, none of these patches are
	required.
	PHKL_23813:  Two other patches work in conjuction with this
	patch to enable PA-8700 support.  These other two patches
	are PHKL_23814 and PHKL_23815.

	PHNE_23981

	The libsis.sl patch PHSS_23710 should be installed
	for the fix of JAGad92559 to work properly.

	Fix for JAGad91730 depends on Filesystems patch
	PHKL_25525.
	On systems with PCI interfaces PHKL_20170
	should also be installed.
	Fix for JAGab70789/JAGad28779 depends on
	PM patches PHKL_23406, PHKL_23407,
	PHKL_23408, and PHKL_23409.

	This patch can resolve a race condition and a panic in the
	Terminal I/O subsystem. However, on multiprocessor systems
	it can introduce performance degradation. The performance
	degradation can be slight to severe, depending on the use
	of the system. We recommend that you install the Terminal
	I/O patch PHNE_19616 or a superseding patch together with
	this patch. The performance degradation results from binding
	child processes of "rlogin" and "remsh" to a single CPU.

	Every development site (on A.03.25 through A.03.27) that
	installs this patch MUST also install the header file patch
	PHSS_22868.  All aC++ applications built with the -AA option
	on versions A.03.25 through A.03.27 must then be recompiled
	and relinked.  If this is not done, link time or run time
	incompatibilities may result.  See CR JAGad36658 above.

	1) The fix for the defect JAGad16185 (Result of dtcm_lookup
	"-v" week" is not correct for some locales), does not
	work for S_Chinese locale with the patch PHCO_20765
	(which is present in Dec2000 QPK) or with PHCO_23770.
	However, 11.00 LR (patch PHCO_16629) doesnot exhibit
	this problem. If you have either PHCO_20765 or
	PHCO_23770 installed on your system, then install
	the latest patch PHCO_24148.
	2) For getting the gb18030 codeset support,
	please install the following patches:
	PHSS_25199 and
	PHSS_25200

	For gb18030 character set support, please install
	both these patches on your system:
	1) PHSS_25194
	2) PHSS_25200

	For gb18030 character set support, please install
	both these patches on your system:
	1) PHSS_25194
	2) PHSS_25199

Patches with Special Installation Instructions

The following list shows patches that have special installation instructions. If you are loading these patches, please read the information following the table.

Click on the patch name to jump to the actual instructions in the following section.

Patch List

Special Instructions to Install the Patches

	Before installing patch,
	pfs_umount all PFS-mounted CD-ROMS, and kill
	pfs_mountd
	pfsd

	This patch introduces a new locale. CDE must be restarted to
	recognize this new locale during dtlogin.
	After installing this patch, please restart CDE.

	This patch introduces a new locale. CDE must be restarted to
	recognize this new locale during dtlogin.
	After installing this patch, please restart CDE.

	This patch introduces a new locale. CDE must be restarted to
	recognize this new locale during dtlogin.
	After installing this patch, please restart CDE.

	This patch introduces a new locale. CDE must be restarted to
	recognize this new locale during dtlogin.
	After installing this patch, please restart CDE.

	This patch introduces a new locale. CDE must be restarted to
	recognize this new locale during dtlogin.
	After installing this patch, please restart CDE.

	This patch introduces a new locale. CDE must be restarted to
	recognize this new locale during dtlogin.
	After installing this patch, please restart CDE.

	This patch should be installed only on
	s800 series and not on s700 as envd(1M)
	is supported only on s800 systems.

	This patch introduces new locales. CDE must be restarted to
	recognize these new locales during dtlogin.
	After installing this patch, please restart CDE.

	This patch introduces a new locale. CDE must be restarted to
	recognize this new locale during dtlogin.
	After installing this patch, please restart CDE.

	This patch should be installed only on
	s800 series and not on s700 as envd(1M)
	is supported only on s800 systems.

	Applying this patch will cause the system to reboot.  When
	the system reboots for the first time, it will determine if
	the device files /dev/tty0p0 and /dev/tty1p0 need to be
	reassigned.  If so, it will perform the reassignment and
	reboot the system again.
	If the system reassigns the device files for the serial
	ports /dev/tty0p0 and /dev/tty1p0, any manual configuration
	that depends on those device file names may need to be
	updated to be consistent with the new assignments.

	This patch introduces a new locale. CDE must be restarted to
	recognize this new locale during dtlogin.
	After installing this patch, please restart CDE.

	This patch introduces a new locale. CDE must be restarted to
	recognize this new locale during dtlogin.
	After installing this patch, please restart CDE.

	This patch introduces a new locale. CDE must be restarted to
	recognize this new locale during dtlogin.
	After installing this patch, please restart CDE.

	This patch introduces a new locale. CDE must be restarted to
	recognize this new locale during dtlogin.
	After installing this patch, please restart CDE.

	This patch introduces a new locale. CDE must be restarted to
	recognize this new locale during dtlogin.
	After installing this patch, please restart CDE.

	After installation, you should
	run ". /usr/contrib/Q4/bin/set_env"
	to set the q4 execution environment.

	- PHCO_20525
	-- /opt/pd/bin/lp should be executed in order to allow
	access to logical DPS printer with authorize-jobs true.
	User either explicitly calls /opt/pd/bin/lp or places
	/opt/pd/bin ahead of /usr/bin in PATH variable.
	-- DPS uses a user-configurable file, /etc/rc.config.d/pd,
	in its startup operation.  A new version of this file is
	delivered with this patch.  It can be found at
	/opt/pd/newconfig/etc/rc.config.d/pd .  Users should
	modify *a copy* of this file to reflect their
	configuration values, and place the result in
	/etc/rc.config.d/pd .  Do *not* modify the delivered file
	directly, as this will cause a swverify of future DPS
	patches to fail.
	- Must have 11.00 DistributedPrint product installed
	before this patch is installed.
	- PHCO_15616 is an LP patch needed for LP interface.

	If libnss_files patches are installed without rebooting,
	applications currently running which are linked shared
	against libnss_files will still continue using the
	former version of libnss_files. If this presents a
	problem to any applications, you should reboot.

	PHCO_23652: JAGab20870
	The /etc/default/tz included in the patch contains the
	earlier default value ie., EST5EDT. So unless the user
	explicitly changes the value contained in the file
	the tzset changes are transparent to the user.
	The file /etc/default/tz contains the timezone value set by
	tzset() when the environment variable TZ is not set. The
	format for the file is same as TZ format without the prefix
	"TZ=".  Please check environ(5) for TZ format.
	The order of TZ setting is as follows.
	1) if the environment variable TZ is present, it takes the
	precedence.
	2) if TZ is not present, then the value contained in
	/etc/default/tz is used for default.
	3) if /etc/default/tz is not set, then the default value is
	equivalent to EST5EDT (Eastern Standard Time) of US.

	This patch supersedes PHCO_20443. If you have PHCO_20443
	installed on your system, please DO NOT uninstall/remove it
	before installing this patch. If for some reason you can't
	avoid removing PHCO_20443, please make a backup of the file
	'/etc/services.window' before the uninstall and restore it
	prior to installing this patch.

	If libc patches are installed without rebooting,
	applications currently running which are linked shared
	against libc will still continue using the former version of
	libc.  If this presents a problem to any applications, you
	should reboot.

	This patch must be installed before installing any patches
	following the initial 11.0 Extension Media bundle.
	If this patch is placed in the same depot as the core 11.0
	software, and an update from a 10.x system is done using
	this depot as a source, the -x reinstall=true option must be
	specified on the SD command line for the update. Otherwise,
	the patch may not be installed.
	The above problem can be avoided if the extension media
	patches are loaded in a separate swinstall session following
	the update using the patch_match_target option.
	SD push and job capabilities, supporting distributed
	software management, are available in this patch.
	This patch can be rolled back. Rolling back this patch
	may revert to old 11.00 capabilities which does not
	include SD push and job support.

	If libc patches are installed without rebooting,
	applications currently running which are linked shared
	against libc will still continue using the former version of
	libc.  If this presents a problem to any applications, you
	should reboot.

	How to get UPS firmware revision:
	PowerTrust II LR
	To check the UPS firmware:
	1. Edit the file "/etc/uucp/Devices"
	2. Add "Direct ttyxxx - 1200 direct"
	xxx = RS-232 tty port used by UPS
	3. At unix prompt, issue "cu -l ttyxxx
	4. Enter "V"

	After installing the patch, the command "catman -w"
	should be run to get the updated /usr/share/lib/whatis
	data base [Please refer to the manpage of catman(1M)].
	This command may take upto one hour to complete.

	Run /usr/sbin/lpshut before the installation of this
	patch and run /usr/sbin/lpsched after installing the
	patch.

	Terminate dtlogin(1) before installing this patch, and
	restart it again after the installation has completed.
	Note that this will terminate all active CDE sessions.
	If this is not done, the installation could intermittently
	fail if the /usr/lib/libpam.1 library is in use by the
	dtlogin(1) program at the time this patch is installed.
	For example:
	# /usr/sbin/fuser /usr/lib/libpam.1
	/usr/lib/libpam.1:     8541m
	# ps -p8541
	PID TTY       TIME COMMAND
	8541 pts/0     0:00 dtlogin
	# /sbin/init.d/dtlogin.rc stop
	
	# /sbin/init.d/dtlogin.rc start

	If PHKL_18543 is installed on a system that does not have
	Advanced VxFS, then the Advanced VxFS driver 'vxadv' will be
	commented out of the /usr/conf/master.d/vxfs file as follows:
	* Disabling AdvJournalFS: vxadv  vxadvc     10      100  ...
	The following note will be logged in the swagent.log file:
	NOTE:    "AdvJournalFS" product is now disabled.  Any vxadv driver in
	the system file will be ignored.  If you install the 11.00
	version of "AdvJournalFS", you must again install this patch,
	PHKL_18543.
	(The reinstall* options must be set to false - the default.)
	If the Advanced VxFS product is subsequently installed, PHKL_18543
	must be reinstalled as specified in the note above, otherwise the
	following warning will occur when creating a kernel and the Advanced
	VxFS features will not be available:
	WARNING: No such device, tunable, or cdio vxadv.
	Ignoring the following line.
	vxadv
	Please apply this patch along with command patch PHCO_13411.
	Failure to do so, ie. applying one without the other, will
	result in fsck failure, or even fsck corrupting the
	filesystem.
	The new features in PHKL_13552 are only supported for
	V-Class 64-bit systems.  Non-V-Class systems can install
	this patch with no impact to those systems.  The following
	patches rely on PHKL_13552 to enable certain features:
	PHCO_13606: SAM recognition of new tunables
	PHCO_13571: insf, mksf, lssf recognize new devices
	PHCO_13494: fbackup/frecover recognize new devices
	To enable large record support on V-Class systems, you will
	need to set the following tunables:
	scsi_maxphys 16777215
	st_large_recs 1
	To enable failed data overruns where stape reads are shorter
	than the actual record size, use:
	st_fail_overruns 1
	Installing PHKL_17040 on PCI based systems will add diag1 to
	the /stand/system file and create the /dev/diag/diag1 device
	file.  Removing PHKL_17040 will delete diag1 from
	/stand/system file and remove the /dev/diag/diag1 device
	file from the system.  Installing/Removing any patch
	superseding PHKL_17040 will leave the system in the state
	it was prior to installing the patch.
	It may be necessary to boot on a backup kernel to recover
	from the boot hang before installing this fix.

	This patch depends on base patch PHKL_18543.
	This patch contains part of the enhancement to enable the
	3 Gb private address space feature. It is one of 8 patches.
	The other 7 patches necessary to enable this feature are
	PHKL_20222, PHKL_20223, PHKL_20224, PHKL_20225, PHKL_20226,
	PHKL_20227 and PHKL_20229. Each patch may be installed
	independently of the others - if enabling the 3 Gb private
	address space feature is not desired. If fewer than all
	8 patches are installed, the 3 Gb private address space
	feature will not be enabled. The code in this patch that
	is part of this feature will not have any impact on the
	system until all 8 patches are installed.
	In order to be able to use this feature you will need to
	reconfigure the kernel with a larger value for the kernel
	configurable variable "maxdsiz". In order to do this with
	SAM, you will also need to install patch PHKL_20174. Without
	PHKL_20174 installed SAM will not allow maxdsiz to exceed
	~1.9 Gb. Note that if PHKL_20174 is not installed it is
	still possible to manually configure a kernel with a larger
	value of maxdsiz (up to 3 Gb) using config(1M).

	Max number of semas per ID
	--------------------------
	For the PHKL_21039 patch, SAM is used to change the
	maximum number of semas per ID (previously SEMMSL) by
	adjusting the new 'semmsl_override' tunable.  The SEMMNS
	(max number of semas in the system) tunable value MUST be
	greater than or equal to 'semmsl_override' otherwise
	applications will be limited to the smaller of the two
	values.
	SEMMNS   MAX # of semas in the system [must be >= SEMMSL]
	SEMMSL   MAX # of semas per ID [presently 64 IDs MAX]
	To make the semas-per-ID (previously SEMMSL) adjustable,
	the 'semmsl_override' kernel tunable has been added.  The
	value can be set and adjusted up from (the minimum and
	default value of 2048) to an arbitrary maximum of 10240
	(0x2800).  This global 'semmsl_override', is the only way
	to adjust the maximum number of semas per ID and the
	changes take effect only after re-boot.
	Because a new tunable is being added, it is highly
	reccommended that you install patch PHCO_19047, which has
	the necessary SAM upgrades.  Without the upgrades, SAM
	will still be aware of the new tunable but will not be
	aware of the new range limitations for that tunable.
	Therefore, SAM will show a warning message to this effect
	when attempting to access the tunable.  With PHCO_19047
	installed, SAM will automatically update the range values.
	The tunable can still be set by SAM using values within
	the range limits specified in the
	/usr/conf/master.d/sysvipc-tune file but it is not the
	reccommended procedure as SAM will not perform the
	necessary checks and SAM will not guarantee a successful
	kernel creation if the tunable is modified.
	SysV IPC MSGMNB message queue capacity
	--------------------------------------
	o The PHKL_21518 (sysV_msg.o) (or superseding) patch
	and the pstat.o patch (PHKL_21684 or superseding patch)
	MUST BOTH be installed on the system together to enable
	the MSGMNB enhancement.
	o It is also highly recommended that patches PHKL_21778
	(core-hpux) PHCO_21187 (with the necessary SAM
	enhancements) also be installed.
	o Installing only the PHKL_21778 (core-hpux) patch
	will allow the admin to set MSGMNB >64k but the change
	will have no effect as the kernel will hard-limit the
	value to 64k.
	o Applications compiled with __BIGMSGQUEUE_ENABLED will
	not run on systems which do not have the appropriate
	patches installed.
	o Not having either the PHKL_21518 (sysV_msg.o) patch or
	the PHKL_21684 (pstat.o) patch installed means that
	applications compiled with the #define
	__BIGMSGQUEUE_ENABLED may not run or may not run
	correctly.
	o Not installing PHKL_21778 (core-hpux) and PHCO_21187
	(SAM) patches will make it more difficult to adjust the
	kernel message tunables.
	o If an application attempts to use message queues larger
	than 64K (by defining __BIGMSGQUEUE_ENABLED) and the
	PHKL_21684 (pstat.o) companion patch is missing, an
	EINVAL error code will be returned (from msgget(2))
	and a message will be placed into the system log (but
	only on the first occurrence).
	Kernel Tunables:
	----------------
	o Follow the procedures below for setting the kernel
	tunables and tunable ranges using SAM.
	o Follow these guidelines for setting new message queue
	kernel tunables:
	o MSGMNB [max number of bytes per queue]
	Set >= the largest queue required.  If single large
	messages are expected, also set >= the largest single
	message expected.
	o MSGMAX [max message size in bytes]
	Set <= MSGMNB dependent on the need to use single
	large messages which may fill the queue.
	o MSGTQL [max number of message headers]
	Set >= the largest number of messages expected.
	o MSGSSZ [number of bytes in one "segment"]
	MSGSEG [number of segments]
	MSGSSZ*MSGSEG [total message storage space]
	o Set MSGSSZ*MSGSEG >= at least to the maximum a
	single large message queue can hold.
	o If multiple large queues are expected, that
	will need to be factored in.
	o MSGSSZ is the "granularity" for message storage.
	If MSGSSZ=256 then a 257-byte message will
	consume two segments.
	o Note that MSGSEG must be < 32768 so that if 32M
	were allocated, the segment size MSGSSZ would
	need to be set to 1K bytes.
	Updating MSGMNB/MSGMAX Tunable Ranges:
	--------------------------------------
	Presently, the "range" values in master/core-hpux will
	prevent users of SAM from configuring MSGMNB and MSGMAX to
	>64K.  In order to allow larger queues, the admin should
	install PHCO_21187 (SAM) patch as a companion to
	PHKL_21778 (core-hpux) which will automatically update
	SAM's range values.  If that is not desired, the admin can
	follow the following special procedure outlined below:
	SAM, as installed on customer systems, may prevent the
	administrator from selecting queue (and message) sizes in
	excess of 64Kbytes.  This is due to the range values in
	/usr/conf/master.d/core-hpux or SAM's "params.tx" file
	(significant in older versions of SAM).
	We are providing the PHKL_21778 (core-hpux) patch for the
	"core-hpux" files (for both 32bit and 64bit kernels).
	However, due to SAM version differences, the customer has
	several procedural options, as described below.
	o If installation of the PHKL_21778 (core-hpux) patch to
	/usr/conf/master.d/core-hpux is desired, follow
	these steps:
	make a backup copy of /usr/conf/master.d/core-hpux
	install the patch
	inspect changes to /usr/conf/master.d/core-hpux
	o Note that installation of this patch will overwrite
	any local changes, these should be merged back in.
	o This particular patch will make the following changes:
	Old:
	*range msgmax<=64*1024
	*range msgmnb<=64*1024
	New:
	*range msgmax<=64*1024*1024
	*range msgmnb<=64*1024*1024
	o Any other changes are due to: having not been
	previously up-to-date with superseded patches to
	this file; superseding patches to this file; or
	prior local changes to this file.
	o Once statisfied with /usr/conf/master.d/core-hpux,
	perform one of the following procedures.
	a) If the PHCO_21187 (SAM) patch is installed, the
	procedure is:
	- make backup copy of /var/sam/boot.config
	- execute /usr/sam/lbin/getkinfo -b
	- inspect changes made to /var/sam/boot.config
	o The "KC_PARAM_MAX" values for "msgmax" and
	"msgmnb" should have change from 65536 (64Kbytes)
	to 67108863 (64Mbytes).  If there are any other
	changes to this file, they represent additional
	core-hpux changes from superseding patches,
	or changes which from superseded patches,
	but not rolled into SAM.
	o Start SAM, change MSGMAX/MSGMNB kernel parameters
	to desired values.  These values will depend upon
	the application's needs.  You may also need to
	adjust the MSGSEG/MSGSSZ parameters to allocate
	more memory for total message storage (the upper
	limits for these do not change).  Then regenerate
	and reboot the kernel in the usual manner.
	or:
	b) If the PHCO_21187 (SAM) patch is not installed,
	install it then follow procedure for "a".
	or:
	c) If installing the PHCO_21187 (SAM) patch is not
	desired, first:
	o Edit the /usr/sam/lib/kc/params.tx file to change
	the upper limits:
	Old:
	msgmax:65536:0:Message:8192:Message Max Size...
	msgmnb:0x10000:0:Message:16384:Max Number ...
	New:
	msgmax:67108863:0:Message:8192:Message Max Size...
	msgmnb:67108863:0:Message:16384:Max Number...
	o Do not change any other message queue parameters.
	o After editing, follow the procedure under "a", as
	if the patch was installed.
	o If installation of the PHKL_21778 (core-hpux) patch is
	not desired (despite the recommendation that it be
	installed), then the administrator will need to edit
	/usr/conf/master.d/core-hpux directly to change the
	upper limits:
	Old:
	*range msgmax<=64*1024
	*range msgmnb<=64*1024
	New:
	*range msgmax<=64*1024*1024
	*range msgmnb<=64*1024*1024
	o Once this is done, follow one of the above
	procedures, "a", "b", or "c", as appropriate.
	o If SAM is not the means for kernel configuration at
	the site, the PHKL_21778 (core-hpux) patch (or editing
	core-hpux may not be needed.  In this case the
	tunables for MSGMNB, MSGMAX, MSGSEG, and MSGSSZ should
	be modified, and the kernel regenerated and rebooted,
	in the usual manner for the site.  (For example: edit
	the /stand/system file then build a new kernel via
	'mk_kernel -s /stand/system'). The maximum for MSGMNB
	and MSGMAX is now 67108863 rather than 65536.
	3GB Private Address Space
	-------------------------
	This patch contains part of the enhancement to enable the
	3 Gb private address space feature.  It is one of 8
	patches.  The other 7 patches necessary to enable this
	feature are PHKL_20222, PHKL_20223, PHKL_20224,
	PHKL_20225, PHKL_20226, PHKL_20227 and PHKL_20228.  Each
	patch may be installed independently of the others - if
	enabling the 3 Gb private address space feature is not
	desired.  If fewer than all 8 patches are installed, the 3
	Gb private address space feature will not be enabled.  The
	code in this patch that is part of this feature will not
	have any impact on the system until all 8 patches are
	installed.
	In order to be able to use this feature you will need to
	reconfigure the kernel with a larger value for the kernel
	configurable variable "maxdsiz".  In order to do this with
	SAM, you will also need to install patch PHKL_20174.
	Without PHKL_20174 installed SAM will not allow maxdsiz to
	exceed ~1.9 Gb.  Note that if PHKL_20174 is not installed
	it is still possible to manually configure a kernel with a
	larger value of maxdsiz (up to 3 Gb) using config(1M).
	This patch depends on base patch PHKL_18543.

	In order for the SuperIO Floppy driver to function, the
	core SuperIO patch (PHKL_20152 or its superseding patch)
	must also be installed on the system.  The SuperIO Floppy
	driver is only required on the B1000, C3000, and J5000
	workstations, as well as future HP-UX 11.00 workstations
	which support the SuperIO interface.

	Special Installation Instructions:
	In order for the SuperIO Parallel driver to function, the
	core SuperIO patch (PHKL_20152 or its superseding patch)
	must also be installed on the system.  The SuperIO Parallel
	driver is only required on the B1000, C3000, and J5000
	workstations, as well as future HP-UX 11.00 workstations
	which support the SuperIO interface.

	In order for the SuperIO IDE/ATAPI driver to function, the
	core SuperIO patch (PHKL_20152 or its superseding patch)
	must also be installed on the system.  The SuperIO IDE
	driver is only required on the B1000, C3000, and J5000
	workstations, as well as future HP-UX 11.00 workstations
	which support the SuperIO interface.

	This patch depends on base patch PHKL_18543.
	For successful installation please insure that PHKL_18543
	is already installed, or that PHKL_18543 is included
	in the same depot with this patch and PHKL_18543
	is selected for installation.

	PHKL_22976:
	This patch depends on a second patch, PHKL_22975, to fix a
	panic on L3000 systems.  This defect only affects a specific
	set of customers (L3000), and other customers need not
	install patch PHKL_22975.  Both patches may be installed in
	any order, or together, if desired.
	This patch depends on base patch PHKL_18543.

	If you wish to display the information about POSIX message
	queues and named semaphores as well as to remove POSIX
	message queues and named semaphores, you must install the
	commands patch, PHCO_22592, in addition to this patch.
	If you wish to enable the increased SysV IPC MSGMNB message
	queue capacity feature delivered in patches PHKL_21518,
	PHKL_21778, and PHKL_21684, it is highly recommended that
	all of the Special Installation Instructions for the
	PHKL_21518 (sysV_msg.o) patch be read prior to installing
	this patch.
	This patch depends on base patch PHKL_18543.

	This patch depends on base patch PHKL_18543.
	PHKL_20225:
	This patch contains part of the enhancement to enable the
	3 Gb private address space feature. It is one of 8 patches.
	The other 7 patches necessary to enable this feature are
	PHKL_20222, PHKL_20223, PHKL_20224, PHKL_20226, PHKL_20227,
	PHKL_20228 and PHKL_20229. Each patch may be installed
	independently of the others - if enabling the 3 Gb private
	address space feature is not desired. If fewer than all
	8 patches are installed, the 3 Gb private address space
	feature will not be enabled. The code in this patch that
	is part of this feature will not have any impact on the
	system until all 8 patches are installed.
	In order to be able to use this feature you will need to
	reconfigure the kernel with a larger value for the kernel
	configurable variable "maxdsiz". In order to do this with
	SAM, you will also need to install patch PHKL_20174. Without
	PHKL_20174 installed SAM will not allow maxdsiz to exceed
	~1.9 Gb. Note that if PHKL_20174 is not installed it is
	still possible to manually configure a kernel with a larger
	value of maxdsiz (up to 3 Gb) using config(1M).
	PHKL_23409:
	If NFS is installed on the system, all five patches
	(PHNE_23249, PHKL_23406, PHKL_23407, PHKL_23408, PHKL_23409)
	are required to resolve the process hang/deadlock due to
	unkillable processes executed over NFS.  However, if NFS is
	not in use, none of these patches are required.  All five of
	these patches may be installed independently.  If fewer than
	four out of the four PHKL patches are installed, the
	P_NOSTOP feature will not be enabled.

	This patch depends on base patch PHKL_18543.
	For successful installation please insure that PHKL_18543
	is already installed, or that PHKL_18543 is included
	in the same depot with this patch and PHKL_18543
	is selected for installation.

	This patch depends on base patch PHKL_18543.
	For successful installation please insure that PHKL_18543
	is already installed, or that PHKL_18543 is included
	in the same depot with this patch and PHKL_18543
	is selected for installation.

	This patch depends on base patch PHKL_18543.
	For successful installation please insure that PHKL_18543
	is already installed, or that PHKL_18543 is included
	in the same depot with this patch and PHKL_18543
	is selected for installation.

	ALERT messages:
	One of the major changes made to the Fibre Channel driver in
	PHSS_17199 and carried forward in PHSS_18136 is that the HBA
	is reset when the system is booted. This reset causes link
	errors which result in the ALERT messages seen at boot
	time. Therefore ALERT messages at boot time should not be
	considered a problem. ALERT messages seen after the boot
	process should be considered a possible problem and need to
	be investigated.

	This patch depends on base patch PHKL_18543.
	For successful installation please insure that PHKL_18543
	is already installed, or that PHKL_18543 is included
	in the same depot with this patch and PHKL_18543
	is selected for installation.

	This patch depends on base patch PHKL_18543.
	For successful installation please insure that PHKL_18543
	is already installed, or that PHKL_18543 is included
	in the same depot with this patch and PHKL_18543
	is selected for installation.

	This patch depends on base patch PHKL_18543.
	For successful installation please insure that PHKL_18543
	is already installed, or that PHKL_18543 is included
	in the same depot with this patch and PHKL_18543
	is selected for installation.

	This patch depends on base patch PHKL_18543.
	For successful installation please insure that PHKL_18543
	is already installed, or that PHKL_18543 is included
	in the same depot with this patch and PHKL_18543
	is selected for installation.

	This patch depends on base patch PHKL_18543.
	For successful installation please insure that PHKL_18543
	is already installed, or that PHKL_18543 is included
	in the same depot with this patch and PHKL_18543
	is selected for installation.

	This patch depends on base patch PHKL_18543.
	For successful installation please insure that PHKL_18543
	is already installed, or that PHKL_18543 is included
	in the same depot with this patch and PHKL_18543
	is selected for installation.

	This patch depends on base patch PHKL_18543.
	For successful installation please insure that PHKL_18543
	is already installed, or that PHKL_18543 is included
	in the same depot with this patch and PHKL_18543
	is selected for installation.

	The A5566A Fibre Channel Mass Storage (FCMS) card must be in
	a PCI slot number greater than all non-A5566A FCMS cards on
	the same bus.  Multiple A5566A FCMS cards on a PCI bus can
	be used.
	This patch depends on base patch PHKL_18543.

	After patch is installed the vx_maxlink tunable can be
	set in /stand/system. At that time the system needs to
	be rebuilt and rebooted.
	is selected for installation.

	This patch depends on base patch PHKL_18543.
	For successful installation please insure that PHKL_18543
	is already installed, or that PHKL_18543 is included
	in the same depot with this patch and PHKL_18543
	is selected for installation.

	This patch depends on base patch PHKL_18543.
	For successful installation please insure that PHKL_18543
	is already installed, or that PHKL_18543 is included
	in the same depot with this patch and PHKL_18543
	is selected for installation.

	This patch depends on base patch PHKL_18543.
	For successful installation please insure that PHKL_18543
	is already installed, or that PHKL_18543 is included
	in the same depot with this patch and PHKL_18543
	is selected for installation.

	This patch depends upon PHKL_21775.  The dependency is a
	result of a process management defect which this patch
	exposes.  If this patch is installed on a system without
	PHKL_21775, and the user then creates mirrored logical
	volumes on a shared volume group, over time the system
	proc table will be exhausted, thus causing the system to
	become unusable.  If you are not using mirrored logical
	volumes on shared volume groups, there is no dependency
	on PHKL_21775.
	This patch depends on base patch PHKL_18543.

	This patch depends on base patch PHKL_18543.
	For successful installation please insure that PHKL_18543
	is already installed, or that PHKL_18543 is included
	in the same depot with this patch and PHKL_18543
	is selected for installation.

	This patch should not be installed if the customer has
	manually modified the /usr/conf/master.d/core-hpux file.
	This file will be overwritten by the patch.
	If you wish to enable the increased SysV IPC MSGMNB message
	queue capacity feature delivered in patches PHKL_21518,
	PHKL_21778, and PHKL_21684, it is highly recommended that
	all of the Special Installation Instructions for the
	PHKL_21518 (sysV_msg.o) patch be read prior to installing
	this patch.
	This patch depends on base patch PHKL_18543.

	PHKL_23814:
	This patch, PHKL_23814, is one of the three 11.00 PA-8700
	enablement patches. The other 11.00 PA-8700 enablement
	patches are PHKL_23813 & PHKL_23815. Installation of
	each patch individually will have not effect on the
	system.
	This patch depends on base patch PHKL_18543.

	This patch depends on base patch PHKL_18543.
	For successful installation please insure that PHKL_18543
	is already installed, or that PHKL_18543 is included
	in the same depot with this patch and PHKL_18543
	is selected for installation.

	This patch, PHKL_23815, is one of the three 11.00 PA-8700
	enablement patches. The other 11.00 PA-8700 enablement
	patches are PHKL_23813 & PHKL_23814. Installation of
	each patch individually will have not effect on the
	system.
	This patch depends on base patch PHKL_18543.

	This patch depends on base patch PHKL_18543.
	For successful installation please insure that PHKL_18543
	is already installed, or that PHKL_18543 is included
	in the same depot with this patch and PHKL_18543
	is selected for installation.

	To enable the asyncio enhancement that defers memory
	locking to improve application startup times, create the
	async device file with minor number 256 using the
	following commands. The user must have super-user rights
	to execute these commands.
	Delete the old device file.
	# rmsf -v /dev/async
	Create the new device file
	# mknod /dev/async c 101 256
	Note: This minor number should only be used on systems that
	have enough physical memory so that paging is avoided.
	Paging can cause serious performance degradation with this
	new enhancement.  On systems where paging is an issue, this
	minor number should not be used.
	PHKL_23813:
	This patch, PHKL_23813, is one of the three 11.00 PA-8700
	enablement patches. The other 11.00 PA-8700 enablement
	patches are PHKL_23814 & PHKL_23815. Installation of
	each patch individually will have no  effect on the system.
	PHKL_23406:
	If NFS is installed on the system, all five patches
	(PHNE_23249, PHKL_23406, PHKL_23407, PHKL_23408, PHKL_23409)
	are required to resolve the process hang/deadlock due to
	unkillable processes executed over NFS.  However, if NFS is
	not in use, none of these patches are required.  All five of
	these patches may be installed independently.  If fewer than
	four out of the four PHKL patches are installed, the
	P_NOSTOP feature will not be enabled.
	PHKL_20222, PHKL_20223, PHKL_20224, PHKL_20226, PHKL_20227:
	This patch contains part of the enhancement to enable the 3
	Gb private address space feature.  It is one of 8 patches.
	The 8 patches necessary to enable this feature are
	PHKL_20222, PHKL_20223, PHKL_20224, PHKL_20225, PHKL_20226,
	PHKL_20227, PHKL_20228 and PHKL_20229.  Each patch may be
	installed independently of the others - if enabling the 3 Gb
	private address space feature is not desired.  If fewer than
	all 8 patches are installed, the 3 Gb private address space
	feature will not be enabled.  The code in this patch that is
	part of this feature will not have any impact on the system
	until all 8 patches are installed.
	In order to be able to use this feature you will need to
	reconfigure the kernel with a larger value for the kernel
	configurable variable "maxdsiz". In order to do this with
	SAM, you will also need to install patch PHKL_20174. Without
	PHKL_20174 installed SAM will not allow maxdsiz to exceed
	~1.9 Gb. Note that if PHKL_20174 is not installed it is
	still possible to manually configure a kernel with a larger
	value of maxdsiz (up to 3 Gb) using config(1M).
	PHKL_21535:
	To enable shared memory dumping to application core files,
	you must first install this patch. After the new vmunix
	has been built by the patch process you need to set some
	kernel variables in the new vmunix using adb.
	To do this, first invoke adb with write capabilities
	on the vmunix file (typically /stand/vmunix):
	adb -w /stand/vmunix
	You may get some error output "Not an Elf file: No Elf
	header". ignore those errors.
	Setting core_addshmem_read to 1 enables dumping of
	read-protected shared memory segments.
	To set core_addshmem_read to 1, the command in adb is:
	core_addshmem_read?W1
	adb should output:
	core_addshmem_read:	0 	 =  1
	Setting core_addshmem_write to 1 enables dumping of
	write-protected shared memory segments.
	To set core_addshmem_write to 1, the command in adb is:
	core_addshmem_write?W1
	adb should output:
	core_addshmem_write:	0  	 =  1
	exit adb by typing
	$q
	Now the vmunix file should be enabled for shared memory
	dumping.  You must reboot in order for the change to take
	effect.  Note:  if a new vmunix is generated in the future,
	such as after installing another kernel patch, you will need
	to repeat this procedure.  This mechanism is typically used
	in troubleshooting applications.
	The effective user ID of the process calling async driver,
	typically called by a process for database applications such
	as Oracle and Sybase, must be a superuser or the user must
	be a member of a group that has the MLOCK privilege.
	To check the privilege capabilities for a group, issue the
	command:
	/usr/bin/getprivgrp 
	If the output of getprivgrp(1) does not indicate that the
	group has the MLOCK privilege, it can be set by issuing the
	following command as root:
	/usr/bin/setprivgrp  MLOCK
	This patch depends on base patch PHKL_18543.

	This patch depends on base patch PHKL_18543.
	For successful installation please insure that PHKL_18543
	is already installed, or that PHKL_18543 is included
	in the same depot with this patch and PHKL_18543
	is selected for installation.

	This patch depends on base patch PHKL_18543.
	For successful installation please insure that PHKL_18543
	is already installed, or that PHKL_18543 is included
	in the same depot with this patch and PHKL_18543
	is selected for installation.

	Note on Service Guard:
	When the package IP address is added, gated changes
	the routing table entry for all the routes from the primary
	address to alias address, because of which, all the routes
	learned through the primary address are lost.
	To solve the above problem add the following statement to
	gated.conf in the interface options statement:
	interfaces {
	options aliases-nh keepall;
	};

	PHNE_17434: Note that some netstat options may return
	inconsistent output when used on core dumps
	created from kernels with the patch
	PHNE_17017, the 11.00 cumulative ARPA
	Transport patch.  netstat will run consistently
	on live kernels with any patch level.
	An example of inconsistent output occurs when
	"netstat -rn" is run on a core file created
	from a kernel with PHNE_17017.  The output is
	similar to the expected output, except that the
	"Interface" fields will all be "*" instead of
	the correct interface name (i.e. lan0, etc.).

	A new field can now be added to /etc/dhcptab to improve
	the performance of the DHCP server.  Using this new feature
	will delay the writing of the database by a few seconds,
	and can be used if clients are timing out after 2 or 4
	seconds although the DHCP server does eventually respond.
	This is very popular with large numbers of Win95 clients.
	The new tag is:  dhcpdb-write-perf=N:
	where N is an integer between 0 and 600.
	We recommend setting N=5.  This is a system-wide feature,
	so the top of your /etc/dhcptab might look like this:
	DHCP_SERVER_SETTINGS:dhcpdb-write-perf=5:

	If lan common patch PHNE_19081 (or a superseding patch) is
	not installed on a system with PCI FDDI, then installing
	patch PHNE_19542 or a superseding patch (including this
	patch) will :
	- Not fix defect symptom #1 and #3 for PHNE_19542
	- Symptom #2 for PHNE_19542 can never occur as
	long as PHNE_19081 (or a superseding patch)
	is not applied.
	If lan common patch PHNE_19081 (or any superseding patch)
	is installed on a system with PCI FDDI, then installing
	patch PHNE_19542 or a superseding patch( including this
	patch) will fix all 3 defects described in patch
	PHNE_19542. Note that installing PHNE_19081 (or a
	superseding patch) will expose defect #2 for PHNE_19542,
	mentioned in the 'Symptoms' and 'Defect Description'
	fields, which is fixed by patch PHNE_19542 and
	superseding patches, including this patch.
	A note about the fix for item #3 listed in the  'Symptoms'
	field for patch PHNE_20874:
	Starting with the application  release of June 2000 (and
	later   releases),   the   product  has  a   per-interface
	configuration           file           located          at
	/usr/newconfig/etc/rc.config.d/hpfddi4conf.    When    the
	product is installed from the application  release of June
	2000   or  a   later   application   release,   the   file
	(hpfddi4conf)     is     automatically     copied     into
	/etc/rc.config.d/hpfddi4conf, if the file does not already
	exist   in  the   destination   directory.  If  the   file
	hpfddi4conf   already   exists   under    /etc/rc.config.d
	directory it may not be overwritten by the newly delivered
	file under /usr/newconfig/etc/rc.config.d/ directory as it
	may contain  changes  made by the user.  The user can then
	merge   the   changes,   if  any  into   the  file   under
	/etc/rc.config.d  directory.
	When  patch  PHNE_20874  (or  a  superseding  patch)  is
	installed, the file  hpfddi4conf is always delivered under
	the /usr/newconfig/etc/rc.config.d  directory and the user
	is  required to  merge/copy  changes, if any into the file
	under /etc/rc.config.d directory.
	The hpfddi4conf file allows per-interface  configuration
	information  to  be  stored  across  boots  and  automatic
	initialization of of interfaces using these  per-interface
	parameters  during  system  boot by the  product  start-up
	script  (/sbin/init.d/hppcifddi).  The following variables
	are  now   configurable  in  the  hpfddi4conf  file  on  a
	per-interface basis:
	HP_PCIFDDI_INTERFACE_NAME:  Name  of  interface   (lan0,
	lan1  ...,  lan10,  ...)  i.e.  any  lanX,  where X is the
	instance number of the interface being configured.
	HP_PCIFDDI_STATION_ADDRESS:    The    desired    unicast
	hardware address (station address) of the interface.  This
	value must be '0x' followed by 12 hexadecimal digits (i.e.
	0x080009xxxxxx).
	HP_PCIFDDI_MTU:  Maximum  transmission  unit (in  bytes)
	for the  interface.  A  value  in the  range  257-4352  is
	valid.
	HP_PCIFDDI_TREQ:  The  FDDI  station's  T_Req  value  in
	milli-seconds.  A value in the range 4-165 is valid.
	HP_PCIFDDI_TNOTIFY:  The FDDI station's  T_Notify  value
	in seconds.  A value in the range 2-30 seconds is valid.

	1) If  the EISA FDDI product (versions B.11.00 and above) is
	also   installed    on   the  system, then  PHNE_16503  or a
	superseding patch should also be installed  for  the  common
	utilities fddiif, fddilink  and   fddidump to work over both
	links.
	2)      The      HSC      FDDI      configuration      file,
	/etc/rc.config.d/hphscfddiconf has been provided in    patch
	version PHNE_21390 or product  version  B.11.00.07    of the
	driver, to  allow  setting of the transmit threshold  values
	on   the    card. If     this functionality  is     desired,
	copy the /usr/newconfig/etc/rc.config.d/hphscfddiconf   file
	to   /etc/rc.config.d/hphscfddiconf  and   set   appropriate
	transmit threshold   values.

	o 'remshd' and 'rexecd' binaries that are shipped as
	part of this patch hereafter will be using PAM for
	authenticating users. For more details regarding
	the PAMized versions of 'remshd' and 'rexecd'
	refer the readme in
	/usr/share/doc/pamized_rcom_readme.txt
	o For rlogind to work properly in 64-bit machines the
	transport patch PHNE_20094 should be installed.
	o After removing this patch, please remove the "-s" option
	from remshd/rlogind entry in the file "/etc/inetd.conf"
	if present. remshd/rlogind may fail with "-s" option if
	this patch is removed.

	If PHNE_21835 is installed with any of the following ARPA
	Transport Patches:
	PHNE_20041 PHNE_20436 PHNE_20633 PHNE_20735 PHNE_21038
	PHNE_21318 PHNE_21606 PHNE_21767 PHNE_21890 PHNE_22067
	PHNE_22318 PHNE_22397
	the defect fix provided for Service Request 5003426312 will
	no longer work.
	Service Request 5003426312 describes a specific case where a
	user supplied service is configured in /etc/inetd.conf(4)
	and is started in the swait state. In this case under
	certain circumstances inetd(1M) will loop trying to start
	the service.
	Note this is not the case with any of the Hewlett-Packard
	supplied Internet Services, such as telnetd, rlogind, ftpd,
	etc.
	This problem will be corrected when ARPA Transport patch
	PHNE_22397 is superseded.

	This patch installs only on release I.11.00.10 or earlier.
	You must remove PHNE_19506 to be able to install this
	patch.
	***************************************************
	***         ***         ***         ***         ***
	*** WARNING *** WARNING *** WARNING *** WARNING ***
	***         ***         ***         ***         ***
	***************************************************
	Several kernel patches are MANDATORY for HSC ATM
	cards. (PHKL_14532 AND PHKL_14606). If these patches
	or their successors are not already installed on the
	system, YOU WILL NOT BE ABLE TO BUILD CORRECTLY THE
	KERNEL.
	As this patch works for PCI, HSC and HP-PB ATM products,
	you may see some normal warnings about some files missing
	at installation, ignore them.

	This patch carries a new ATM stack introduced with ATM
	release I.11.00.40 to provide new functionalities such
	as MPOA, LLC, LANE v2. This patch can only be installed
	on ATM release I.11.00.40 or later. If you have an ATM
	release previous to I.11.00.40 installed, do not upgrade
	to I.11.00.40 or a later release to be able to install
	this patch unless you need one of the new functionalities.
	***************************************************
	***         ***         ***         ***         ***
	*** WARNING *** WARNING *** WARNING *** WARNING ***
	***         ***         ***         ***         ***
	***************************************************
	Several kernel patches are MANDATORY for HSC ATM
	cards. (PHKL_14532 AND PHKL_14606). If these patches
	or their successors are not already installed on the
	system, YOU WILL NOT BE ABLE TO BUILD CORRECTLY THE
	KERNEL.
	As this patch works for PCI, HSC and HP-PB ATM products,
	you may see some normal warnings about some files missing
	at installation, ignore them.

	A new version of file /etc/rc.config.d/hpbase100conf
	is delivered as part of this patch,
	as /usr/newconfig/etc/rc.config.d/hpbase100conf file.
	If you have edited /etc/rc.config.d/hpbase100conf file,
	you may want to merge these files.
	To set speed and duplex via SAM, users need to install SAM
	patch: PHCO_17792.
	ifconfig down/up is needed while changing MTU using
	lanamdin -[M|R] options.

	A new version of file /etc/rc.config.d/hpgsc100conf
	is delivered as part of this patch,
	as /usr/newconfig/etc/rc.config.d/hpgsc100conf file.
	If you have edited /etc/rc.config.d/hpgsc100conf file,
	you may want to merge these files.
	To set speed and duplex via SAM, users need to install SAM
	patch: PHCO_17792. You also need to merge
	/usr/newconfig/etc/rc.config.d/hpgsc100conf file with
	/etc/rc.config.d/hpgsc100conf.
	ifconfig down/up is needed while changing MTU using
	lanadmin -[M|R] options.

	Further information on this new version of BIND can be found
	in "/usr/share/doc/bind496.txt", including pointers to other
	sources of information regarding this patch.

	Be sure to look at /etc/ntp.conf.example for suggested
	configurations and hints.

	If the EISA 100bt product is  also installed on the  system,
	then  PHNE_23981  or  a  superseding  patch  should  also be
	installed for the EISA FDDI Intermittent card hang problem.
	If the HSC FDDI product is also  installed   on the  system,
	then   PHNE_16504  or a superseding  patch  should  also  be
	installed  for  the  common  utilities fddiif, fddilink  and
	fddidump  to  work over both links.

	Existing installations do not have to modify their ftp
	configuration  unless they want to use the new features.
	There is one exception; there is a difference in the ftp
	daemon options between legacy ftp and the new June 1998
	version of ftp. In the older version of ftp, the -A option
	enables Kerberos authentication. In the new version of
	ftp, the -K option enables Kerberos authentication, and
	the  -A option is used to disable the ftpaccess file. So
	if you are using Kerberos authentication, you will need
	to edit /etc/inetd.conf to change the existing -A option
	to -K.
	This version of FTP has some new configuration files that
	can be used to take advantage of new functionality. Sample
	of the new configuration files are provided in
	/usr/newconfig/etc/ftpd. You can edit these files as per
	your need and copy them to the location /etc/ftpd.
	You can get information on the new features introduced by
	this new version of ftpd from the file:
	/usr/share/doc/RelNotes_newftp.txt
	NOTE:
	1. WU-ftpd does not support sublogins on anonymous ftp.
	2. Two new options, "suppresshostname" and "suppressversion"
	have been added to the ftpaccess file (ftpd configuration
	file). More details on these can be found in the
	ftpaccess(4) manpage.

	1. A new copy of the hpbasetconf file is provided
	under the directory /usr/newconfig/etc/rc.config.d.
	It is recommended that the local modifications
	to the /etc/rc.config.d/hpbasetconf file be
	incorporated into the new copy and be placed
	under the directory /etc/rc.config.d. This new
	hpbasetconf is modified to support new
	speed/duplex setting options.
	2. The speed and duplex setting using SAM will work only
	if the SAM patch PHCO_17792 is installed. This patch
	is scheduled to be released by mid of July 1999.

	A new version of file /etc/rc.config.d/hpbtlanconf
	is delivered as part of this patch,
	as /usr/newconfig/etc/rc.config.d/hpbtlanconf file.
	If you have edited /etc/rc.config.d/hpbtlanconf file,
	you may want to merge these files.
	To set speed and duplex via SAM, users need to install SAM
	patch: PHCO_17792
	ifconfig down/up is needed while changing MTU using
	lanadmin -[M|R] options.

	PHNE_24307:
	1. All special instructions required for PHNE_22930 (see
	below) are applicable to PHNE_24307.
	PHNE_22930:
	1. All special instructions required for PHNE_18504 (see
	below) are applicable to PHNE_22930. Furthermore a
	new /usr/newconfig/etc/rc.config.d/hpgelanconf file has
	been delivered which contains additional configurable
	parameters. if you wish to use the new file, merge the
	contents of the existing /etc/rc.config.d/hpgelanconf
	with the new file.
	2. To configure the gigabit ethernet interface parameters
	via SAM, users need to install SAM patch: PHCO_21187.
	PHNE_18504:
	1. If PHNE_15385 is installed on the B.11.00 revision
	of the HP PCI Gigabit Ethernet Driver product,
	remove PHNE_15385 and follow step 2.
	2. If the B.11.00 revision or the B.11.00.01 revision of
	the HP PCI Gigabit Ethernet Driver product is already
	installed:
	(a) Remove the B.11.00 revision or the B.11.00.01
	revision of the PCI Gigabit Ethernet Driver product.
	(b) Install the B.11.00.05 revision of the HP
	PCI/HSC Gigabit Ethernet Driver product.
	Refer to the Release Notes for patch dependencies.
	(c) Install PHNE_18504.
	3. A test file which should have been removed from this
	patch (PHNE_18504) was not removed. Please remove
	/sbin/rc2.d/S550PHNE_18504 . Failure to do so may
	result in errors on bootup.

	PHNE_24308
	A new parameter,HP_APA_DEFAULT_PORT_MODE is added to the
	file, /etc/rc.config.d/hp_apaconf and is delivered as part
	of this patch.This new version is delivered as
	/usr/newconfig/etc/rc.config.d/hp_apaconf file.
	If you have edited /etc/rc.config.d/hp_apaconf file,
	you need to merge these files.
	A new version of file /etc/rc.config.d/hp_apaportconf is
	delivered as part of this patch,as
	/usr/newconfig/etc/rc.config.d/hp_apaportconf file.
	If you have edited /etc/rc.config.d/hp_apaportconf file,
	you may want to merge these files.

	I. When modifying the MTU value of an interface, please
	follow the following steps:
	1. Bring the interface down with 'ifconfig'
	2. Modify the MTU value
	3. Bring the interface up with 'ifconfig'
	II. Install SAM patch PHCO_17792 before using SAM to modify
	the speed and the duplex modes.
	A new version of file /etc/rc.config.d/hpsppci100conf
	is delivered as part of this patch,
	as /usr/newconfig/etc/rc.config.d/hpsppci100conf file.
	If you have edited /etc/rc.config.d/hpsppci100conf file,
	you may want to merge these files.

	1. A new copy of the hpeisabtconf file is provided
	under the directory /usr/newconfig/etc/rc.config.d.
	This new hpeisabtconf is modified to support new
	speed/duplex setting options for startup script.
	Copy this configuration file and incorporate any
	previous modifications to the
	/etc/rc.config.d/hpeisabtconf file to this new
	copy and replace the working configuration file
	/etc/rc.config.d/hpeisabtconf with it.
	2. The speed and duplex setting using SAM will work only
	if the SAM patch PHCO_17792 or any patch superseding
	it and, the lan common patch PHNE_17113 or any patch
	superseding it is installed.

	The  'insf'  patch   PHCO_17090 (or its superseding
	patch if any)   MUST  be installed   prior  to  the
	installation of this telnetd patch, for this patch
	to work.
	Please note, after installation of PHNE_14957 the
	naming convention for /dev/pts/t* changes from
	/dev/pts/tnumber to /dev/pts/tcharacter to allow
	creation of more than 1000 telnet device files.
	Consequently the first telnetd device file is
	renamed from /dev/pts/t0 to /dev/pts/ta.
	NOTE:
	For getting more user  logins, the kernel  configuration
	parameter 'nstrtel'  needs to be modified to the  desired
	number and rebuild the kernel. Ensure  that the extra
	telnet pseudo ttys are created by doing 'insf -d tels'.
	On trusted systems, the telnetd patch  has a dependency
	on the libsec patch PHCO_17622( or later) also  apart from
	the insf patch PHCO_17090 (or later).
	Thus, on trusted systems before installing the telnetd
	patch, please ensure that the libsec patch PHCO_17622
	(or later) and the insf patch PHCO_17090 (or later)
	are installed to generate device file names similar to
	telnetd.
	Please note that the  dependency on PHCO_17622 ( or later )
	is applicable only for trusted systems.
	PHNE_24762:
	1. Telnetd will timeout and exit if it does not receive
	either a positive or negative reply to any of the
	initial option negotiations.
	The -n option notifies telnetd the timeout value in
	seconds. Default is 120 seconds.
	To alter the timeout value, perform the following steps
	after installing this patch:
	1. Edit the /etc/inetd.conf file as:
	telnet   stream tcp nowait root /usr/lbin/telnetd telnetd -n
	Where  is the new timeout value in seconds.
	2. Make inetd re-read the /etc/inetd.conf configuration
	file by running the following command on the command
	line:
	$ inetd -c

	To resolve the deadlock due to filesystem locks being
	held (JAGad91730), PHKL_25525 must also be installed
	along with this patch.  If PHKL_25525 is not installed,
	the fix will not be enabled.
	The fix for JAGad15675 is disabled by default. In order to
	enable the fix, the kernel parameter 'nfs_new_lock_code'
	must be changed from the default value of 0 to 1. This can
	be done by either patching the vmunix file and rebooting,
	or patching the kernel image in memory. To patch the vmunix
	file (survives a reboot), use the following command:
	echo 'nfs_new_lock_code?W 0d1' |
	adb -w -k /stand/vmunix /dev/kmem
	To patch the in-memory kernel (does not survive a reboot),
	use the following command:
	echo 'nfs_new_lock_code/W 0d1' |
	adb -w -k /stand/vmunix /dev/kmem
	A kernel regeneration will require these steps be done
	again to enable the fix.
	The fix for JAGad70794 is not enabled unless the ypinit
	script is copied from /usr/newconfig/usr/sbin to
	/usr/sbin/. To backup the current ypinit script and
	enable the new ypinit script, do the following steps:
	mv /usr/sbin/ypinit /usr/sbin/ypinit.bak
	cp -p /usr/newconfig/usr/sbin/ypinit /usr/sbin/ypinit
	When disabling the fix for JAGad70794 and migrating
	back to the previous ypinit script, the file
	/var/yp/binding//ypservers will need
	to be deleted:
	mv /usr/sbin/ypinit.bak /usr/sbin/ypinit
	rm /var/yp/binding//ypservers
	The fix for JAGad72416 is disabled by default. In order to
	enable the fix, the kernel parameter
	'async_read_avoidance_enabled' must be changed from the
	default value of 0 to 1. This can be done by either
	patching the vmunix file and rebooting, or patching the
	kernel image in memory. To patch the vmunix file (survives
	a reboot), use the following command:
	echo 'async_read_avoidance_enabled?W 0d1' |
	adb -w -k /stand/vmunix /dev/kmem
	To patch the in-memory kernel (does not survive a reboot),
	use the following commands:
	echo 'async_read_avoidance_enabled/W 0d1' |
	adb -w -k /stand/vmunix /dev/kmem
	A kernel regeneration will require these steps to be done
	again to enable the fix.
	To resolve the process hang/deadlock due to
	unkillable processes defect (JAGab70789/JAGad28779),
	PHKL_23406, PHKL_23407, PHKL_23408, and PHKL_23409
	must also be installed along with this patch. All
	five of these patches may be installed independently.
	If all five patches are not installed, the fix will
	not be enabled.
	If NFS/TCP is configured, it is recommended to have
	the HP-UX 11.00 Extension Pack 9905 from May 1999,
	or later, installed. Any revision of the XSWGR1100
	patch bundle equal to, or greater than, B.11.00.45
	will satisfy this recommendation.
	For NFS/TCP, these minimum values are recommended
	for the kernel parameters in /stand/system:
	nkthread=2048
	max_thread_proc=256
	ncallout=2064
	Note that the default value of ncallout is
	nkthread + 16.

	A new version of file /etc/rc.config.d/hppci100conf
	was delivered as a part of this patch, which is
	/usr/newconfig/etc/rc.config.d/hppci100conf. If you
	edit /etc/rc.config.d/hppci100conf you may want to
	merge the files.
	To set speed and duplex via SAM, users need to install SAM
	patch: PHCO_17792
	ifconfig down/up is needed while changing MTU using
	lanamdin -[M|R] options.

	Please note:
	The CDE environment must not be running when this
	patch is installed.
	If it is, you will receive warnings that text files
	are busy.  SD will move these aside and place the
	new files in the appropriate location, but it is
	recomended that CDE first be shutdown prior to patch
	instalation.

	For this patch to take effect Stop and Start all
	DCE daemons and application processes OR reboot
	the machine after the patch is installed.

	For this patch to take effect Stop and Start all
	DCE daemons and application processes OR reboot
	the machine after the patch is installed.

	For this patch to take effect Stop and Start all
	DCE daemons and application processes OR reboot
	the machine after the patch is installed.
	*****IMPORTANT NOTE*****  -- Oracle 7.3.3 and above will
	need to be relinked. This patch contains changes to  the
	libcma library.  Applications such  as Oracle  that  use
	this  library  and  are   built  static  will need to be
	relinked. For  information  and  help  for  the  rebuild
	please contact your Oracle support personnel.
	*****IMPORTANT NOTE*****
	This patch contains
	1.64bit libdcekt library and header files
	2.kernel threaded libdcecp and related libraries.
	***NOTE*** -- A new  version of dce_com_utils is present
	in this  patch which  will be installed in the directory
	/opt/dce/newconfig/etc/opt/dce/. For the  new version to
	take  effect  please copy it to /etc/opt/dce/ directory.
	Please save the customized /etc/opt/dce/dce_com_utils,
	if necessary.

	1. This patch supplies new versions of document, job and
	printer in the /usr/newconfig/etc/X11/C/print/attributes
	directory.  These files have to be merged with those
	present in /etc/X11/C/print/attributes directory.
	2. To use this patch, the user should modify the dtlogin
	config file in /etc/dt/config/Xconfig.
	If /etc/dt/config/Xconfig is not present, please copy
	from /usr/dt/config/Xconfig to /etc/dt/config/Xconfig.
	Set the resource "Dtlogin*authorize:  False". Then
	restart the dtlogin daemon process or reboot the system.
	3. There is another problem not fixed with this
	patch.  "dtpdm" may fail to start from "dtpdmd"
	in some circumstances.  When CDE is used with
	"Xauthorization" true (which is the default
	behaviour),"dtpdm" may not be authorized by the
	X Display server, hence it failed with X
	authorization error. This is due to the design of
	"dtpdmd", therefore HP is considering to fix in
	the future release.
	There are several ways to get workaround this
	error such as
	-  Use "xhost" command to allow Xclient to
	connect to X display
	Ex:  $ xhost + name-of-localhost
	-  Modify /etc/X0.hosts
	-  Uncomment  "Dtlogin*authorize: False" in
	/etc/dt/config/Xconfig
	When /etc/dt/config/Xconfig is not present, copy
	it from /usr/dt/config/Xconfig and do the
	modification. After modifying Xconfig file, restart
	the dtlogin daemon process,or restart the system.
	The reason for this customization is that the
	"dtpdm" which is invoked by "dtpdmd" is NOT the
	process of the user who has currently logged in CDE,
	hence it doesn't have the proper authorization to
	access  the Xdisplay.
	Please consider carefully which of these workarounds
	will be suitable for your enviornment.  Please refer
	to xauth(1), xhost(1) and other materials about
	"X Authorization".
	Warning: Setting Dtlogin*authorize=False greatly
	reduces control over the system and is
	_not_ recommended.

	During installation of the patch the following message can
	be ignored
	NOTE: tlinstall is searching filesystem- please be patient
	NOTE: The following are messages for core transition links
	WARNING: Can't create core transition links since
	files/directories exist:
	/usr/bin/kdestroy -> /opt/dce/bin/kdestroy
	/usr/bin/kinit -> /opt/dce/bin/kinit
	/usr/bin/klist -> /opt/dce/bin/klist
	NOTE:    Complete with message(s) displayed above
	WARNING: The command "/usr/lbin/sw/install_clean" had
	warnings.  The installation will continue.Check the above
	output for details about the warnings.

	This patch will only update the firmware on these systems:
	9000/785/B1000
	9000/785/B2000
	9000/785/C3000
	9000/785/C3600
	9000/785/J5000
	9000/785/J5600
	9000/785/J6000
	9000/785/J7000
	If the installed system firmware is more recent than the
	firmware provided in the patch, the system firmware will
	not be modified when the patch is installed.
	If the patch is installed on a system other than those
	listed above, it will not modify the system firmware so no
	harm will occur.

	Note: The audio client libraries and the Aserver provided
	in this patch will not operate with earlier versions.
	This patch must be installed on all hp-ux systems
	that need to run either audio clients or the Aserver.
	If the patch cannot be installed on all systems that
	need to interoperate for audio services, the patch
	must not be installed on any of the systems.
	The Aserver in the Envizex-II and other X-terminals is
	not compatible with this patch.

	NOTE TO USERS OF THE NEWLY INTRODUCED ANSI C++ STANDARD
	LIBRARY VERSION 2.0 (libstd_v2):
	If you have used aC++ versions A.03.25 through A.03.27 with
	the -AA option then you must install this patch.
	If as an ISV you have shipped a library built WITH the -AA
	option, please contact HP for further information.  If as an
	end user you have received and installed third party
	libraries or applications built or compiled WITH the -AA
	option, please contact HP for further information.
	To determine whether your library/application uses -AA, run
	the command
	chatr  | grep libstd_v2
	If the output of this command is NOT empty, your
	library/application uses -AA.
	This libstd_v2 roll is necessary to establish compatibility
	with the definition of mbstate_t (multibyte support) in the
	HPUX 11.11 runtime (libc).
	If you install this patch you MUST recompile and relink any
	applications built with the -AA option (and be sure your
	software vendors have done so for their products).
	Every development site (on A.03.25 through A.03.27) that
	installs this patch MUST also install the header file patch
	PHSS_22868.  All aC++ applications built with the -AA option
	on versions A.03.25 through A.03.27 must then be recompiled
	and relinked.  If this is not done, link time or run time
	incompatibilities may result.  See CR JAGad36658 above.

	This patch delivers a new version of the file
	/usr/newconfig/etc/X11/fs/config. The contents
	of this file have been merged (by adding code
	to the postinstall script) with
	/etc/X11/fs/config.
	The changes done in this file are:
	- including a new font path
	( /usr/lib/X11/fonts/iso_8859.15/75dpi ) in
	the catalogue field.
	- including new font paths
	( /usr/lib/X11/fonts/TrueType/japanese.st,
	/usr/lib/X11/fonts/TrueType/korean.st,
	/usr/lib/X11/fonts/TrueType/chinese_s.st &
	/usr/lib/X11/fonts/TrueType/chinese_t.st ) in
	the catalogue field.

	1) The CDE environment must not be running when this
	patch is installed.
	If it is, you will receive warnings that text files
	are busy.  SD will move these aside and place the
	new files in the appropriate location, but it is
	recommended that CDE first be shutdown prior to patch
	installation.
	The CDE environment may be shut down by running the
	following commands as root:
	- /usr/dt/bin/dtconfig -d
	- /usr/dt/bin/dtconfig -kill
	Note that these commands will terminate all CDE sessions
	for all CDE users.
	Once the patch has been installed, you may start CDE
	back up by doing:
	- /usr/dt/bin/dtconfig -e
	- /sbin/init.d/dtlogin.rc start
	2. Multiscreen problem which was reported against Motif
	product ( CVLpt03018,5003413898) involved fixes in
	CDE components also and are included in this patch.
	The motif fixes went into PHSS_16169 and this patch
	depends on PHSS_16169.
	3. The customers who use Tech Print Server and
	applications which work with "dtpdm" (Print
	Dialog Manager) need to apply this patch.
	Before applying this patch, the customers should
	understand the effect of this patch described
	below.
	4. This patch fixed the problem of SR (#1653277293).
	"dtpdmd" invoked from /etc/rc unexpectedly
	terminated, this is due to the defect that "dtpdmd"
	doesn't handle the signals properly.  The fix was
	to add the signal routines for "dtpdmd".
	5. There is another problem not fixed with this
	patch.  "dtpdm" may fail to start from "dtpdmd"
	in some circumstances.  When CDE is used with
	"Xauthorization" true (which is the default
	behaviour),"dtpdm" may not be authorized by the
	X Display server, hence it failed with X
	authorization error. This is due to the design of
	"dtpdmd", therefore HP is considering to fix in
	the future release.
	There are several ways to get workaround this
	error such as
	-  Use "xhost" command to allow Xclient to
	connect to X display
	Ex:  $ xhost + name-of-localhost
	-  Modify /etc/X0.hosts
	-  Uncomment  "Dtlogin*authorize: False" in
	/etc/dt/config/Xconfig
	When /etc/dt/config/Xconfig is not present, copy
	it from /usr/dt/config/Xconfig and do the
	modification. After modifying Xconfig file, restart
	the dtlogin daemon process,or restart the system.
	The reason for this customization is that the
	"dtpdm" which is invoked by "dtpdmd" is NOT the
	process of the user who has currently logged in CDE,
	hence it doesn't have the proper authorization to
	access  the Xdisplay.
	Please consider carefully which of these workarounds
	will be suitable for your environment.  Please refer
	to xauth(1), xhost(1) and other materials about
	"X Authorization".
	Warning: Setting Dtlogin*authorize=False greatly
	reduces control over the system and is
	_not_ recommended.
	6.  In future, HP will take Xauthority feature into
	the product.
	7.  For the defect JAGaa40062, changes were done in
	PHSS_16903 also.  Install the patch PHSS_16903
	for the complete solution of this defect.

	Please note:
	The CDE environment must not be running when this
	patch is installed.
	If it is, you will receive warnings that text files
	are busy.  SD will move these aside and place the
	new files in the appropriate location, but it is
	recommended that CDE first be shutdown prior to patch
	installation.
	The CDE environment may be shut down by running the
	following commands as root:
	- /usr/dt/bin/dtconfig -d
	- /usr/dt/bin/dtconfig -kill
	Note that these commands will terminate all CDE sessions
	for all CDE users.
	Once the patch has been installed, you may start CDE
	back up by doing:
	- /usr/dt/bin/dtconfig -e
	- /sbin/init.d/dtlogin.rc start

	PHSS_25254 and all superseding
	patches can only be installed on systems
	that can execute PA-RISC version 2.0
	(PA2.0) object code.

	PHSS_25255 and all superseding
	patches can only be installed on systems
	that can execute PA-RISC version 2.0
	(PA2.0) object code.

	PHSS_25256 and all superseding
	patches can only be installed on systems
	that can execute PA-RISC version 2.0
	(PA2.0) object code.

	PHSS_25257 and all superseding
	patches can only be installed on systems
	that can execute PA-RISC version 2.0
	(PA2.0) object code.

	PHSS_25258 and all superseding
	patches can only be installed on systems
	that can execute PA-RISC version 2.0
	(PA2.0) object code.

	PHSS_25259 and all superseding
	patches can only be installed on systems
	that can execute PA-RISC version 2.0
	(PA2.0) object code.

	PHSS_25260 and all superseding
	patches can only be installed on systems
	that can execute PA-RISC version 2.0
	(PA2.0) object code.

	PHSS_25261 and all superseding
	patches can only be installed on systems
	that can execute PA-RISC version 2.0
	(PA2.0) object code.

	PHSS_25262 and all superseding
	patches can only be installed on systems
	that can execute PA-RISC version 2.0
	(PA2.0) object code.

Legal Notices

The information contained in this document is subject to change without notice.

Hewlett-Packard makes no warranty of any kind with regard to this document, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material.

A copy of the specific warranty terms applicable to your Hewlett-Packard product and replacement parts can be obtained from your local Sales and Service Office.

(C)Copyright 1996-2001 Hewlett-Packard Company
(C)Copyright 1980, 1984 AT&&T, Inc.
(C)Copyright 1979, 1980, 1983 The Regents of the University of California

This document contains information which is protected by copyright. All rights are reserved. Reproduction, adaptation, or translation without prior written permission is prohibited, except as allowed under the copyright laws.