HP Support Information Digests

===============================================================================
o IT Resource Center World Wide Web Service
   ---------------------------------------------------

   If you subscribed through the IT Resource Center and would
   like to be REMOVED from this mailing list, access the
   IT Resource Center on the World Wide Web at:

     http://www.itresourcecenter.hp.com/

   Login using your IT Resource Center User ID and Password.
   Then select Support Information Digests (located under
   Maintenance and Support). You may then unsubscribe from the
   appropriate digest.

   To download a patch referenced below, access the
   IT Resource Center on the World Wide Web at:

     http://www.itresourcecenter.hp.com/

   Login using your IT Resource Center User ID and Password.
   Then select Individual Patches (under Maintenance and Support)
   to access the patch. You may also download a patch via anonymous
   ftp(1) from ftp.itrc.hp.com.
===============================================================================


Digest Name: weekly HP-UX series 800 10.X patch digest
    Created: Sun Mar 18 3:05:04 PST 2001

Table of Contents:

Document ID Title
--------------- -----------
PHSS_22883 s700_800 10.20 OV ITO6.0X NT Agent Patch A.06.03
PHKL_23481 s800 10.20 LVM cumulative patch, array controller hot-swap
PHSS_23358 s700_800 10.20 ODBCLINK/SE F.00.00 Run-Time Patch
PHSS_22881 s700_800 10.20 OV ITO6.0X HP-UX 11.x Agent Patch A.06.03
PHSS_22879 s700_800 10.20 OV ITO6.0X HP-UX 10.x Agent Patch A.06.03
PHNE_22877 s700_800 10.20 NFS Kernel General Rel & Perf Patch
PHCO_23455 s700_800 10.24 (VVOS) cumulative cron/at/crontab patch
PHNE_22522 s700_800 10.20 2.40.0[012] X.25/ACC Accessory (EISA/PCI)
PHSS_23342 s700_800 10.X OpenMail B.06.00 March 01 Periodic Patch

The documents are listed below.
-------------------------------------------------------------------------------


Document ID: PHSS_22883
Date Loaded: 20010316
      Title: s700_800 10.20 OV ITO6.0X NT Agent Patch A.06.03

Patch Name: PHSS_22883

Patch Description: s700_800 10.20 OV ITO6.0X NT Agent Patch A.06.03

Creation Date: 01/03/13

Post Date: 01/03/16

Hardware Platforms - OS Releases:
        s700: 10.20
        s800: 10.20

Products:
        OpenView IT/Operations 6.0

Filesets:
        OVOPC-CLT.OVOPC-NT-CLT,A.06.00

Automatic Reboot?: No

Status: General Release

Critical: No

Path Name: /hp-ux_patches/s700_800/10.X/PHSS_22883

Symptoms:
        PHSS_22883:
        - Automatic Actions can't start applications that display a
          user interface.
        - The Event Interceptor might get into a looping state when
          running on an NNM system and the ovtrapd is stopped.
        - Multiple issues with the agent on MS Terminal Server
          systems running on NT 4.0.
        - Perl script might show strange behavior when called
          as monitor.
        - Logfile encapsulator might report an access violation
          when reading EventLog message.
        - Agent has to run as 'HP ITO account' user.
        - Agent installation might fail with 'Error from
          InformManager' when the Management Server is a multi
          homed host.
        - Agent installation adds the agent path to the system
          environment without checking if it's already there. Agent
          deinstallation doesn't remove this path at all.
        - Japanese messages might have wrong characters.

        PHSS_22008:
        - ITO requires the setting of all IP addresses in
          opc.hosts for NT multi homed hosts.
        - The control agent aborts when the /usr/OV/tmp/OpC/bin
          directory does not exist.
        - The installation aborts with the NetGetDCName API
          failing: network path not found.
        - The event correlation agent might abort.
        - In some situations the the source IP address of an
          incoming trap has the wrong byte ordering.
        - When there are many quickly incoming traps, the Event
          Interceptor does not handle them but instead buffers
          until there are new traps arriving.
        - Event Interceptor aborts when running on an NNM system
          and an invalid trap is received.
        - After distributing of templates to NT system, sometimes
          there is a message in the errorlog about failures while
          suspending threads.
        - Several changes for firewall environments. For detailed
          information refer to the VPO Firewall Configuration
          White Paper version 3.0
        - The 'Processes' application on Windows 2000 produces a
          Dr.Watson window.
        - Event Interceptor aborts after receiving trap with
          unresolvable IP address.
        - If buffer file size limitation is enabled, the agent may
          discard low-severity messages even if there is still
          space in the buffer file.
        - The execution of monitors or applications might try to
          execute a directory.

Defect Description:
        PHSS_22883:
        - The ITO agent can now run as non 'HP ITO account' user.
          This also includes the 'SYSTEM' account.

          Installation instruction:

          Use the manual installation. Before calling the
          'opc_inst.bat' script, an additional entry can be added to
          the 'opcsetup.inf' file to specify the run user for the
          agent:

            [Agent User]
            SYSTEM

          Instead of 'SYSTEM', any other name could be specified. In
          this case the user account is created.
          If 'SYSTEM' is given, no user account is created (no
          'opc_op' either).

          NOTE: User names may not contain space characters.

          If a user name is specified in 'opcsetup.inf', the agent
          will be installed using this account name, no matter if
          there was already an agent installed using another
          account.

          If a different user is specified in 'opcsetup.inf', the
          account created by the existing agent is not removed but
          left on the system. It has to be removed manually.

          If no user name is specified in 'opcsetup.inf', the
          installation will check if there is already an agent
          installed. If it finds one, the same user will be used.

          If a user is specified or found to be used by an old
          agent, and the password specified was not correct for this
          account, the user is removed and re-created. It has the
          same name afterwards but a different internal user ID.

          Applications:
          -------------

          - All applications configured to run as 'opc_op' or
            'HP ITO account' have to be changed to specify a user
            that exists on the system.
          - All monitoring executables will be run as the specified
            account. This might restrict some of the access rights
            to monitored applications.
          - The 'SYSTEM' account does not have any network access
            capabilities.

          Remote installation:
          --------------------

          - On Domain Controllers there is the Installation Server
            service that executes the installation on remote systems
            in this domain. If this service is modified to run as
            'SYSTEM', the remote installation is not possible at all
            (the 'SYSTEM' account does not have any access rights
            for remote systems).
          - If remote execution is wanted, the Installation Server
            service can be configured to run as a domain user that
            has Domain Admin user rights.

        PHSS_22008:
        check the list of the symptoms

SR:
        R555003313 B555009712 B555009553 B555009412 B555009388
        B555009360 B555009201 B555009153 B555009099 B555008912
        B555008754 B555008729 B555008663 B555008526 B555008314
        B555008309 B555008180 B555007966 B555007883 B555007847
        B555007840 B555007752 B555007619 B555007602 B555007549
        B555007478 B555007056 B555005125 8606161695 8606140211

Patch Files:
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/opc_pkg.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/unzip.exe
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/unzip.txt
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/opc_inst.bat
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/opc_pre.bat
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/opcsetup.inf
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/monitor/itoprocs.exe.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/monitor/sms_chk.bat.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/monitor/mf_service.bat.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/cmds/mfluse.exe.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/cmds/itomserv.exe.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/cmds/itoreg.cfg.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/cmds/opcdf.bat.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/cmds/opcps.bat.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/cmds/itodiag.exe.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/cmds/itokill.exe.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/cmds/itoreg.exe.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/cmds/itosdown.exe.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/cmds/itouser.exe.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/cmds/opcprfls.exe.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/cmds/mf_app.bat.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                AgentPlatform

what(1) Output:
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/opc_pkg.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/unzip.exe:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/unzip.txt:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/opc_inst.bat:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/opc_pre.bat:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/opcsetup.inf:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/monitor/itoprocs.exe.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/monitor/sms_chk.bat.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/monitor/mf_service.bat.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/cmds/mfluse.exe.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/cmds/itomserv.exe.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/cmds/itoreg.cfg.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/cmds/opcdf.bat.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/cmds/opcps.bat.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/cmds/itodiag.exe.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/cmds/itokill.exe.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/cmds/itoreg.exe.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/cmds/itosdown.exe.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/cmds/itouser.exe.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/cmds/opcprfls.exe.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                A.06.03/RPC_DCE_TCP/cmds/mf_app.bat.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/intel/nt/
                AgentPlatform:
                None

cksum(1) Output:
        807165917 7433650 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/ms/intel/nt/A.06.03/RPC_DCE_TCP/opc_pkg.Z
        3162183940 113152 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/ms/intel/nt/A.06.03/RPC_DCE_TCP/unzip.exe
        1939298735 508 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/ms/intel/nt/A.06.03/RPC_DCE_TCP/unzip.txt
        4115030442 1664 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/ms/intel/nt/A.06.03/RPC_DCE_TCP/opc_inst.bat
        2405569119 1715 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/ms/intel/nt/A.06.03/RPC_DCE_TCP/opc_pre.bat
        388202266 133 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/ms/intel/nt/A.06.03/RPC_DCE_TCP/opcsetup.inf
        2464947784 61347 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/ms/intel/nt/A.06.03/RPC_DCE_TCP/monitor/
                itoprocs.exe.Z
        2939951577 134 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/ms/intel/nt/A.06.03/RPC_DCE_TCP/monitor/
                sms_chk.bat.Z
        3318698057 132 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/ms/intel/nt/A.06.03/RPC_DCE_TCP/monitor/
                mf_service.bat.Z
        3048156552 3925 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/ms/intel/nt/A.06.03/RPC_DCE_TCP/cmds/
                mfluse.exe.Z
        516284605 49768 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/ms/intel/nt/A.06.03/RPC_DCE_TCP/cmds/
                itomserv.exe.Z
        1586237090 188 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/ms/intel/nt/A.06.03/RPC_DCE_TCP/cmds/
                itoreg.cfg.Z
        2003580432 38 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/ms/intel/nt/A.06.03/RPC_DCE_TCP/cmds/
                opcdf.bat.Z
        849569434 41 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/ms/intel/nt/A.06.03/RPC_DCE_TCP/cmds/
                opcps.bat.Z
        1639814180 36073 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/ms/intel/nt/A.06.03/RPC_DCE_TCP/cmds/
                itodiag.exe.Z
        2950571021 6858 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/ms/intel/nt/A.06.03/RPC_DCE_TCP/cmds/
                itokill.exe.Z
        3887122869 13779 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/ms/intel/nt/A.06.03/RPC_DCE_TCP/cmds/
                itoreg.exe.Z
        2696124353 46646 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/ms/intel/nt/A.06.03/RPC_DCE_TCP/cmds/
                itosdown.exe.Z
        1048399349 51463 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/ms/intel/nt/A.06.03/RPC_DCE_TCP/cmds/
                itouser.exe.Z
        1024478161 10104 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/ms/intel/nt/A.06.03/RPC_DCE_TCP/cmds/
                opcprfls.exe.Z
        3746185156 778 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/ms/intel/nt/A.06.03/RPC_DCE_TCP/cmds/
                mf_app.bat.Z
        3507093227 6469 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/ms/intel/nt/AgentPlatform

Patch Conflicts: None

Patch Dependencies: None

Hardware Dependencies: None

Other Dependencies: None

Supersedes:
        PHSS_22008

Equivalent Patches:
        ITOSOL_00067:
        sparcSOL: 2.6 2.7 2.8

        PHSS_22884:
        s700: 11.00
        s800: 11.00

Patch Package Size: 7760 KBytes

Installation Instructions:
        Please review all instructions and the Hewlett-Packard
        SupportLine User Guide or your Hewlett-Packard support terms
        and conditions for precautions, scope of license,
        restrictions, and, limitation of liability and warranties,
        before installing this patch.
        ------------------------------------------------------------
        1. Back up your system before installing a patch.

        2. Login as root.

        3. Copy the patch to the /tmp directory.

        4. Move to the /tmp directory and unshar the patch:

                cd /tmp
                sh PHSS_22883

        5a. For a standalone system, run swinstall to install the
            patch:

                swinstall -x autoreboot=true -x match_target=true \
                        -s /tmp/PHSS_22883.depot

        By default swinstall will archive the original software in
        /var/adm/sw/patch/PHSS_22883. If you do not wish to retain a
        copy of the original software, you can create an empty file
        named /var/adm/sw/patch/PATCH_NOSAVE.

        WARNING: If this file exists when a patch is installed, the
                 patch cannot be deinstalled. Please be careful
                 when using this feature.

        It is recommended that you move the PHSS_22883.text file to
        /var/adm/sw/patch for future reference.

        To put this patch on a magnetic tape and install from the
        tape drive, use the command:

                dd if=/tmp/PHSS_22883.depot of=/dev/rmt/0m bs=2k

Special Installation Instructions:
        BEFORE LOADING THIS PATCH...

            o It provides bug fixes and enhancements for the
              VPO A.06.00 Management Server system.

            o DO NOT use this patch with older releases of ITO,
              for example versions A.05.00, A.05.11 or A.05.30
        (A) Patch Installation Instructions
            -------------------------------

        (A1) Install the patch, following the standard
              installation instructions.

              For backing up the system before installing
              a patch, you may use opc_backup(1m)

        NOTE: MAKE SURE THAT NO AGENT OF THE PLATFORM
              ADDRESSED BY THIS PATCH IS DISTRIBUTED
              (either from the VPO Administrator's GUI
              or from command line using inst.sh) WHILE
              RUNNING SWINSTALL.

              Don't be afraid of the '-x autoreboot=true'
              option above. There won't be a reboot due
              to this VPO patch.
              You can skip this option if you like.

        NOTE: This patch must be installed on the VPO Management
              Server system, NOT on an VPO Managed Node directly.
              Changes will take effect on managed nodes by means of
              VPO Software Distribution (using 'Force Update' if
              there is already an agent installed on the managed
              node). See chapter 2 of the VPO Administrator's
              Reference manual for more information.

        - The ITO agent can now run as non 'HP ITO account' user.
          This also includes the 'SYSTEM' account.

          Installation instruction:

          Use the manual installation. Before calling the
          'opc_inst.bat' script, an additional entry can be added to
          the 'opcsetup.inf' file to specify the run user for the
          agent:

            [Agent User]
            SYSTEM

          Instead of 'SYSTEM', any other name could be specified. In
          this case the user account is created.
          If 'SYSTEM' is given, no user account is created (no
          'opc_op' either).

          NOTE: User names may not contain space characters.

          If a user name is specified in 'opcsetup.inf', the agent
          will be installed using this account name, no matter if
          there was already an agent installed using another
          account.

          If a different user is specified in 'opcsetup.inf', the
          account created by the existing agent is not removed but
          left on the system. It has to be removed manually.

          If no user name is specified in 'opcsetup.inf', the
          installation will check if there is already an agent
          installed. If it finds one, the same user will be used.

          If a user is specified or found to be used by an old
          agent, and the password specified was not correct for this
          account, the user is removed and re-created. It has the
          same name afterwards but a different internal user ID.

          Applications:
          -------------

          - All applications configured to run as 'opc_op' or
            'HP ITO account' have to be changed to specify a user
            that exists on the system.
          - All monitoring executables will be run as the specified
            account. This might restrict some of the access rights
            to monitored applications.
          - The 'SYSTEM' account does not have any network access
            capabilities.

          Remote installation:
          --------------------

          - On Domain Controllers there is the Installation Server
            service that executes the installation on remote systems
            in this domain. If this service is modified to run as
            'SYSTEM', the remote installation is not possible at all
            (the 'SYSTEM' account does not have any access rights
            for remote systems).
          - If remote execution is wanted, the Installation Server
            service can be configured to run as a domain user that
            has Domain Admin user rights.

        (B) Patch Deinstallation Instructions
            ---------------------------------

        (B1) To deinstall the patch PHSS_22883 run swremove:

              NOTE: MAKE SURE THAT NO AGENT OF THE PLATFORM
                    ADDRESSED BY THIS PATCH IS DISTRIBUTED (either
                    from the ITO Administrator's GUI or from
                    command line using inst.sh) WHILE RUNNING
                    SWREMOVE.

              # swremove PHSS_22883
-----End of Document ID: PHSS_22883------------------------------------------


Document ID: PHKL_23481
Date Loaded: 20010316
      Title: s800 10.20 LVM cumulative patch, array controller hot-swap

Patch Name: PHKL_23481

Patch Description: s800 10.20 LVM cumulative patch, array controller hot-swap

Creation Date: 01/03/10

Post Date: 01/03/16

Hardware Platforms - OS Releases:
        s800: 10.20

Products: N/A

Filesets:
        LVM.LVM-KRN OS-Core.CORE-KRN

Automatic Reboot?: Yes

Status: General Release

Critical:
        Yes
        PHKL_23481: PANIC HANG CORRUPTION
        PHKL_19705: PANIC
        PHKL_20964: HANG
        PHKL_19697: PANIC
        PHKL_19210: OTHER
                This patch is essential to improve the recovery of
                FC devices in large configurations.
        PHKL_19167: HANG

Path Name: /hp-ux_patches/s800/10.X/PHKL_23481

Symptoms:
        PHKL_23481:
        (SR: 8606142976 CR: JAGad12319)
        LVM commands may hang forever in the kernel
        lv_sa_config() routine (requiring a system reboot to
        break the hang). Volume group activations may fail with
        indications that the disks do not belong to the volume
        group or some other obscure LVM error message. Although
        it has never been reported from the field, there is also
        a remote possibility of data corruption caused by LVM
        using an older copy of the mirror consistency record (MCR)
        or the volume group status (VGSA). These situations may
        most likely happen on systems where the system time has
        been advanced far into the future, then changed back to
        the correct time again. The hangs can also occur if
        a volume group is exported from one system and imported
        to another with a system time behind the first.
        Multiple volume groups on the system may be affected
        simultaneously. Volume Groups that are most
        likely to demonstrate the problem have timestamps on the
        LVM disk VGSA, VGDA or MWC data structures which exceed
        the current system time (although these timestamps are
        themselves not bad).

        (SR: 8606166039 CR: JAGad35326)
        When media defects are encountered on LVM disks, i/o's may
        panic while LVM is trying to map the defect to an alternate
        block. The problem is characterized by an i/o path panic
        "wait_for_lock_spinner: Already own this lock!", with a
        thread deadlocked on a spinlock in the kernel
        lv_defecthash() routine. This is similar to a
        problem discovered on 11.00: JAGad30462.

        (SR: 8606166971 CR: JAGad36258)
        On ServiceGuard OPS clusters, A kernel hang can occur
        in the lv_resyncpv() routine, when previously failed
        devices are recovered and are being resynced by LVM.
        This problem is characterized by a situation where a device
        goes offline then returns, but LVM never recovers the
        device and never starts using it again because LVM
        has gotten stuck in lv_resyncpv().

        (SR: 8606168136 CR: JAGad37418)
        A kernel Data Page Fault (DPF) panic is possible in the
        kernel lv_resyncpv() routine when a volume group is
        deactivated while disks are offline and LVM is actively
        trying to recover the disks. A similar DPF panic
        is possible in lv_resyncpv() when vgreduce(1M) is used
        to reduce PVs from a VG while a resync of the
        logical volumes(s) containing the PV is in progress.

        (SR: 8606173900 CR: JAGad43153)
        After a system crash, mirrored logical volumes might not
        be resynchronized correctly if the Mirror Write Cache is
        enabled (see lvchange(1M) for details). The result is that
        the data written at the time of a system crash might not
        be made consistent across the mirrors. This is a form of
        data corruption.

        (SR: 8606161601 CR: JAGad30917)
        Very poor read performance for HFS filesystems on LVM LVs
        during an lvmerge(1M) operation. VxFS file systems are not
        affected. Reads are held off for as long as 30 seconds.

        (SR: 8606124005 CR: JAGac39365)
        During heavy I/O stress system may panic in LVM
        lv_unblock() due to a spinlock held too long.

        PHKL_22529:
        ( SR:8606113703 DTS: JAGac07217 )
        If a physical volume in an LVM mirrored disk configuration
        is replaced without deactivating the volume group it belongs
        to, an application might see spurious I/O errors, mirror
        resync failures, or data corruption. (The I/O errors and
        resync failures may have been observed prior to replacing
        the disk.)

        (SR: 8606138886 CR: JAGad08152)
        A shared volume group has one or more LUNs on an active-
        passive disk array (Nike, Galaxy or Optimus), and one of
        the array's Service Processors is hot-swapped without
        deactivating the volume group. Later, a node deactivates
        the volume group (while it remains activated on other
        nodes), and that node is not able to reactivate it.

        (SR: 8606162303 CR: JAGad31619)
        Read performance on HFS filesystems on LVM logical
        volumes drops substantially when lvmerge operations
        are in progress. VxFS file systems are unaffected.
        Reads/writes from raw logical volumes are unaffected.
        The problem occurs after installing patch PHKL_20964.

        PHKL_21370:
        (SR: 8606108373 CR: JAGab78776)
        Reads from a mirrored LV can take a very long time to
        complete if one of the mirrors is unavailable.

        (SR: 8606106798 CR: JAGab76189)
        With PHKL_20964 (recalled) installed, LVM may perform a
        full resync every time a volume group is activated. While
        the resync is in progress, system performance may be
        degraded. In addition, since LVM does not have two valid
        copies of all data during the resync, the system is
        vulnerable to a disk failure until the resync completes.

        PHKL_19705:
        ( SR: 1653305987 DTS: JAGab17773 )
        If bad block relocation is enabled on a logical volume
        with parallel read support, then any requests to a
        block currently being relocated results in system panic.

        PHKL_20964:
        (SR: 8606128444 CR: JAGac81735)
        It might not be possible to activate a volume group in
        shared mode if any of its physical volumes are on an
        Optimus Prime Disk Array.

        (SR: 8606106637 CR: JAGab75913)
        An LVM deadlock (hang) can occur when LVM commands which
        operate on logical volumes are run at the same time as
        device query operations. The result is that the LVM
        commands and the query operations never complete (and
        cannot be terminated), and it is not possible to run any
        subsequent LVM commands. Furthermore, it is possible that
        subsequent device recovery will be delayed indefinitely.
        The only way to restore normal operation is to reboot the
        system. For example, the lvmerge(1M), lvsplit(1M) commands
        and glance(1) when run together could cause the commands
        to deadlock, resulting in a situation where they make no
        forward progress and cannot be interrupted or killed.
        The same result could occur running lvchange(1M) or
        lvextend(1M) and lvdisplay(1M) together.

        The defect was introduced in PHKL_19210
        which has since been recalled. This new patch supersedes
        PHKL_19697, PHKL_19210, PHKL_20057 and PHKL_20808.
        This patch contains all the fixes contained in these
        patches. Customers with any of these superseded patches
        installed should apply this new patch.

        (SR: 8606106012 CR: JAGab74797)
        It's possible for an I/O request to be accepted while a
        logical volume is being closed, causing the operating system
        to panic. Typical actions that close a logical volume are
        unmounting a filesystem and closing a database (or other)
        application which uses raw logical volumes. The panic would
        likely be a data page fault in an lvm ("lv_") routine.

        PHKL_20808:
        ( SR:8606100412 DTS: JAGab31786 )
        This is an interim patch to support the Optimus disk array.

        PHKL_20057:
        ( SR:8606100412 DTS: JAGab31786 )
        LVM incorrectly treats two volumes within an Optimus disk
        array as alternate paths to a single volume because they
        have the same LUN ID, even though they are distinct volumes
        and have different target IDs.

        PHKL_19697:
        ( SR:8606101971 DTS: JAGab66231 )
        If there is a problem with the physical volume to which the
        logical volume is mapped, LVM returns EIO error for logical
        requests, without retrying till the I/O timeout value
        set on that logical volume.

        PHKL_19210:
        ( SR:5003437970 DTS: JAGaa40887 )
        When multiple physical volumes or paths to physical volumes
        are lost, it can require minutes to recover them.
        During the time the PVs for a given volume group are
        tested, locks were held which delayed other LVM operations
        and the opens and closes of logical volumes. Prior changes
        to the device recovery code provided some benefit, assuring
        that device recovery was 1-2 minutes regardless of the
        number of paths or devices to be recovered, however this
        still was not enough. The new device recovery code
        in this patch reduces the recovery time to under 35 seconds,
        again independent of the number of paths or devices offline.

        PHKL_19167:
        ( SR: 8606100864 DTS: JAGab39559 )
        ( SR: 4701424846 DTS: JAGab14452 )
        Performance degradation when massively parallel subpage
        size (<8K) reads are performed (as with Informix).

        ( SR: 8606100864 DTS: JAGab39559 )
        ( SR: 1653289132 DTS: JAGaa67952 )
        The system hangs when lvmkd is waiting for the lock obtained
        earlier by an application that performs a vg_create
        operation. The hang does not happen unless there is a
        powerfailed disk.

        ( SR: 8606100864 DTS: JAGab39559 )
        ( SR: 4701424895 DTS: JAGab14455 )
        Optimus Disk Arrays (model number A5277A-HP) are not
        recognized as an ACTIVE/PASSIVE device and subsequently are
        not handled properly by the driver.

        PHKL_17547:
        ( SR: 1653289553 DTS: JAGaa46305 )
        LVM's autoresync after disk powerfail can leave extents
        stale.

Defect Description:
        PHKL_23481:
        (SR: 8606142976 CR: JAGad12319)
        The cause of the LVM command hang reported in the CR was
        that the LVM in-memory timestamp had overflowed so that
        a new timestamp had a value older (less) than the prior
        one applied to the VGSA. The potential for data
        corruption also exists due to the remote possibility
        that latest LVM on-disk metadata may be stamped with
        an old timestamp causing LVM not to use the latest
        metadata upon a subsequent activation.

        Resolution:
        The fix in this patch is a redesign of the timestamp
        algorithm to far reduce the possiblity of a timestamp
        overflow by modifying how timestamps are generated.
        The new timestamp algorithm generates timestamps
        independent of the system time, and generates
        independent timestamps for each volume group.
        The new timestamp algorithm also corrects errors
        in the code which could cause the timestamp to
        advance faster than it should, and situations where
        the timestamp could be truncated. The patch also
        includes code to correct (roll-back) the
        LVM VG timestamp in a safe way should the
        timestamp on a VG pass a danger threshold
        approaching the overflow point.

        (SR: 8606166039 CR: JAGad35326)
        The panic and potential i/o hang mentioned in the
        CR was caused by a kernel spinlock deadlock in
        lv_defecthash(). lv_defecthash() incorrectly
        acquired a spinlock already held.

        Resolution:
        lv_defecthash() was corrected so it would not
        acquire the unnecessary spinlock.
        This problem was fixed in 11.0. Migrated the fix for
        SR: 8606161146 CR: JAGad30462 to 10.20.

        (SR: 8606166971 CR: JAGad36258)
        The LVM resync hang is most definitively identified by
        a deadlock between a resync process running on the VG
        server node deadlocked with the processing of a resync
        request from a client node. The server resync process
        is holding the vg_lock waiting for the
        slvm_resync_lock, and the client resync request process
        is holding the slvm_resync_lock waiting for the
        vg_lock. The deadlock was due to the order of
        acquisition of locks in lv_resyncpv(). Another problem
        within lv_resyncpv() was that a routine called during
        the resync dropped locks held which kept the PV from
        being removed or the VG from being deactivated.
        So the physical volume or logical volume data structures
        could be deallocated while they were still being used by
        lv_resyncpv(), resulting in a Data Page Fault.

        Resolution:
        lv_resyncpv() was redesigned for 11.11 to modify how the
        different locks were acquired and to avoid the deadlock
        and DPF problems. The re-written routine was included
        in this 10.20 patch.

        (SR: 8606168136 CR: JAGad37418)
        The description for this defect is similar to the one
        for SR: 8606166971 CR: JAGad36258.
        The kernel LVM lv_resyncpv() routine called during device
        resync dropped locks held which kept the PV from
        being removed or the VG from being deactivated.
        So the physical volume or logical volume data structures
        could be deallocated while they were still being used by
        lv_resyncpv(), resulting in a Data Page Fault.

        Resolution:
        The resolution for this defect is similar to the one
        for SR: 8606166971 CR: JAGad36258.
        lv_resyncpv() was re-written for 11.11 to modify how the
        different locks were acquired and to avoid the deadlock
        and DPF problems. The re-written routine was included
        in this 10.20 patch.

        (SR: 8606173900 CR: JAGad43153)
        There are two problems in the routine which synchronizes
        extents from the MWC cache entries (lv_recover_ltg()):
        One problem is an off-by-one bug which causes the last
        mirror copy to not be considered when looking for a fresh
        available copy of a given extent. To make matters worse,
        if for a given extent there is no fresh data available
        to read from to perform the MWC resync, the extent is
        skipped, leaving the fresh mirror copies still fresh
        even when their data is possibly inconsistent.

        Resolution:
        The fix for the off-by-one error from PHKL_23127 for
        11.00 JAGad43153 was included in this patch to fix the
        first problem. Additional code from 11.00 MR was
        included in this 10.20 patch to assure that a failed
        attempt to resynchronize an extent leaves only
        synchronized copies of the extent fresh.

        (SR: 8606161601 CR: JAGad30917)
        The problem was that every HFS read makes a call to an
        LVM lv_readahead_info() routine to determine the optimum
        readahead (presumably to optimize readahead for striped
        volumes). The LVM routine grabs the necessary locks
        to assure consistency of the data structures it accesses,
        competing for them with the LVM merge operation. Thus,
        adversely affecting read performance.

        Resolution:
        This patch eliminates the locking in lv_readahead_info().
        This works because LVM lv_readahead_info() routine cannot
        be called with a closed logical volume and the stripe
        factor cannot be changed once a logical volume is created.

        (SR: 8606124005 CR: JAGac39365)
        When an i/o completes, all the requests in the LVM work
        queue containing the request are analyzed to see if any
        requests can be unblocked, whether or not the request
        could necessarily be unblocked by the completed i/o.
        The LV spinlock must be held while traversing the queue,
        and it is held a very long time. The algorithm is time
        consuming because it requires traversing the queue up to
        each request, for each request on the list.
        The algorithm is wasteful because the only requests
        which can be unblocked by the completed request are
        those directed to the same LTG as the completed
        request, and on the work queue after it.

        Resolution:
        The fix was migrated from 11.00 patch PHKL_22233.
        Instead of traversing the list of all prior requests once
        for each request in the list to determine whether any of
        the requests can be unblocked, the new unblock algorithm
        scans the list only once to attempt to unblock only the
        requests that can be unblocked by completion of the i/o
        request. Thus, reducing the length of time the lock
        protecting the queue is held.

        PHKL_22529:
        ( SR:8606113703 DTS: JAGac07217 )
        When a physical volume is replaced without deactivating the
        volume group it belongs to, the operating system does not
        read the bad block directory from the disk, but continues
        using the old one. This can cause spurious I/O errors or
        mirror resync failures if bad block relocation is disabled,
        or data corruption if bad block relocation is enabled.

        Resolution:
        Whenever a physical volume is replaced, the bad block
        directory from the new physical volume is read.

        (SR: 8606138886 CR: JAGad08152)
        If a shared volume group has one or more LUNs on an
        active-passive disk array (Nike, Galaxy or Optimus), and
        if one of the array's Service Processors is hot-swapped
        without deactivating the volume group, then there is no
        guarantee that all the nodes in the cluster will be using
        the same IDs to refer to those LUNs or to refer to
        particular paths (i.e., PVLinks) to the LUNs. This is
        because each Service Process has a unique "controller
        signature" which is used to construct these IDs.

        The LUN and path IDs are passed between nodes in PVLinks-
        related messages. If the IDs do not match, the messages
        will fail. This can lead to various symptoms, but the most
        obvious is that if a node deactivates the volume group
        (while it remains activated on other nodes), that node
        will not be able to reactivate it.

        Resolution:
        The solution is to detect situations where the IDs might be
        out of sync and reconstruct them, by reading the controller
        signatures again. If necessary, messages are reprocessed (if
        the receiver was using an old ID) or resent (if the sender
        was using an old ID).

        (SR: 8606162303 CR: JAGad31619)
        Reads directed to HFS file systems on LVM logical volumes
        can take substantially longer to complete during an lvmerge
        operation. The cause is that the LVM lv_readahead_info()
        interface called by HFS during each read is substantially
        slower than it was prior to patch PHKL_20964 (in which
        significant LVM locking improvements were made).

        Resolution:
        LVM lv_readahead_info() performance has been improved by
        not being quite so strict with the locks acquired during
        the lv_readahead_info() operation.

        PHKL_21370:
        (SR: 8606108373 CR: JAGab78776)
        When reading from a mirrored logical volume, LVM might try
        a disk that is known to be off line before it tries another
        disk which is still available. The read is delayed while the
        first I/O times out.

        Resolution:
        In selecting the best mirror to read from, give preference
        to disks that are still available over disks that are known
        to be off line.

        (SR: 8606106798 CR: JAGab76189)
        When a volume group is activated, LVM validates a data
        structure on each physical volume called the Mirror
        Consistency Record (MCR). If the MCR is not valid, LVM
        performs a full resync of the physical volume and should
        rewrite the MCR. But with PHKL_20964 installed, LVM does
        not rewrite the MCR. Instead, if the MCR is invalid, LVM
        performs a full resync every time the volume group is
        activated, rather than just the first time. While the
        resync is in progress, system performance may be degraded.
        In addition, since LVM does not have two valid copies of
        all data during the resync, the system is vulnerable to a
        disk failure until the resync completes. (This problem
        does not affect performance or availability of mirrored
        logical volumes after the resync has completed.)

        With PHKL_20964 installed, LVM might also display the
        wrong physical volume (PV) number in certain diagnostic
        messages. PHKL_21370 corrects this, as well.

        Resolution:
        If the MCR is not valid, rewrite it after performing a
        full resync.

        PHKL_19705:
        ( SR: 1653305987 DTS: JAGab17773 )
        Currently, LVM does not allow bad block relocation with
        parallel read operation for consistency in bad block
        relocation. So when a bad block relocation is going on
        and a new request comes on to the same block then
        we panic.

        As an enhancment, we enable bad block relocation with
        parallel read operation if we notice that the block we
        are accessing is being relocated, depending on the
        state either initiate bad block relocation or wait till
        the bad block relocation is completed. If REL_DESIRED
        meaning a read noticed a bad block is set on a block
        then we initiate the relocation for this block.
        If REL_PENDING or REL_DEVICE meaning relocation is going
        on, then we wait till the relocation is completed and
        then we will do the I/O from the new location.

        Resolution :
        Modified lv_hwreloc() and lv_validblk() for taking
        action appropriately for the above mentioned states.

        PHKL_20964:
        (SR: 8606128444 CR: JAGac81735)
        It might not be possible to activate a volume group in
        shared mode if any of its physical volumes are on an
        Optimus Prime Disk Array, because the serial numbers for
        these device are truncated when they're passed between
        nodes in a ServiceGuard cluster.

        Resolution:
        Don't truncate Optimus Prime serial numbers.

        [Although this defect was resolved in PHKL_20964, the
        original documentation did not mention it.]

        (SR: 8606106637 CR: JAGab75913)
        The LVM deadlock (hang) occurs due to a defect introduced
        in PHKL_19210 (recalled). In the bad
        patch, the problem was that an easily encountered
        deadlock condition was introduced while attempting
        to correct another relatively rare deadlock.
        The problem can be easily reproduced by running LVM
        commands which operate on existing logical volumes
        such as lvextend(1M), lvsplit(1M) or lvmerge(1M)
        along with commands that query logical volumes, such as
        glance(1). The deadlock occurs roughly 10% of the time,
        but when it does happen there are severe consequences.
        The deadlock makes it impossible to complete the operations
        or to run any other LVM commands, without rebooting the
        system.

        Resolution:
        The LVM kernel code was modified. The volume group lock and
        other LVM locks were reordered and a new volume group data
        lock was added to allow device recovery operations to occur
        simultaneously with command operations. Thus correcting the
        old and newly introduced deadlock defects.

        This patch supersedes the interim PHKL_20808 patch.
        It reintroduces the device recovery changes from PHKL_19210
        and the bug fixes from PHKL_19697 which were purposely
        excluded from PHKL_20808.

        (SR: 8606106012 CR: JAGab74797)
        Because of a race condition in LVM, it is possible for an
        I/O request to be accepted when the logical volume is being
        closed. Eventually, a data structure that has already been
        freed (as a result of closing the logical volume) is
        referenced, causing the operating system to panic.

        Resolution:
        Eliminate the race condition so that I/O cannot proceed
        after a logical volume has been closed.

        [Although this defect was resolved in PHKL_20964, the
        original documentation did not mention it.]

        PHKL_20808:
        ( SR:8606100412 DTS: JAGab31786 )
        This is an interim patch to support the Optimus disk array.

        PHKL_20057:
        ( SR:8606100412 DTS: JAGab31786 )
        For some disk arrays, LVM treats all occurrences of the
        same LUN ID as alternate paths to a single volume. This
        assumption is not correct for the Optimus disk array: two
        distinct volumes may have the same LUN ID, but different
        target IDs.

        Resolution:
        To identify a unique volume in an Optimus array, LVM now
        uses both its LUN ID and target ID.

        PHKL_19697:
        ( SR:8606101971 DTS: JAGab66231 )
        If the physical volume to which the logical volume is
        mapped has problems, instead of retrying till the
        lv_iotimeout value set on the logical volume, LVM
        returns EIO for logical requests before lv_iotimeout.

        This is because we are initializing the start time on the
        request during scheduling of the request. If the PV to
        which the request is to be scheduled is down then we
        append the request to powerfail wait queue without
        scheduling. When the PV comes back, we start resending
        the buffers in the powerfail wait queue and at that
        time we check the elapsed time (current time - initial
        time set) of the request, since we had not initialized
        the time on the request as we did not do the scheduling,
        it will be set to zero resulting in a value higher
        than the lv_iotimeout. Hence we bail out the request
        without processing it, although the time elapsed will
        be much less than the lv_iotimeout value.

        Resolution :
        Initializing logical buf start time in lv_strategy(),
        at the time of processing the request instead of
        setting it during scheduling in lv_schedule().

        PHKL_19210:
        ( SR:5003437970 DTS: JAGaa40887 )
        The problem was that some of the LVM device recovery was
        still a serial process.

        Resolution:
        The LVM device recovery code was modified to cause all tests
        of devices and paths to be conducted in parallel. Devices
        which are available are immediately brought online again,
        irrespective of other failed devices or paths. The changes
        in this patch assure that devices recover within the time it
        takes to test the device/path and to update its data
        structures. The volume group data structures and LVM
        operations that require them --LVM commands and opens and
        closes of logical volumes should be held off no more than 35
        seconds.

        PHKL_19167:
        ( SR: 8606100864 DTS: JAGab39559 )
        ( SR: 4701424846 DTS: JAGab14452 )
        Informix issues massive amounts of 1K reads in parallel.
        With an 8K page size and I/Os serialized within the page,
        performance suffers.

        Resolution:
        Logic was added to allow reads from the same 8K page to
        proceed in parallel when bad block relocation is completely
        disabled (lvchange -r N).

        ( SR: 8606100864 DTS: JAGab39559 )
        ( SR: 1653289132 DTS: JAGaa67952 )
        If the holder of the vg_lock is waiting for I/O to finish,
        and if the I/O can't finish until we switch to another link,
        then we get into a deadlock.

        Resolution:
        To resolve the deadlock, the code now obtains the lock
        temporarily, in order to switch to the alternate link, then
        returns the lock to the original holder to finish the I/O.

        ( SR: 8606100864 DTS: JAGab39559 )
        ( SR: 4701424895 DTS: JAGab14455 )
        We need to recognize Optimus Array as an ACTIVE/PASSIVE
        device.

        Resolution:
        Added code to recognize the Optimus Array as an
        ACTIVE/PASSIVE device.

        PHKL_17547:
        ( SR: 1653289553 DTS: JAGaa46305 )
        lv_syncx() may return with stale extents without actually
        syncing all the extents.

        Resolution:
        Added additional check to see if all the extents are synced;
        otherwise return error. lv_syncx() will return SUCCESS only
        when the syncing is completed. Made changes in
        lv_resyncpv() to preserve error value.

SR:
        1653289132 1653289553 1653305987 4701424846 4701424895
        5003437970 8606100412 8606100864 8606101971 8606106637
        8606106798 8606108373 8606113703 8606138886 8606142976
        8606166039 8606166971 8606168136 8606173900 8606161601
        8606124005 8606162303

Patch Files:
        /usr/conf/lib/libhp-ux.a(lv_lvm.o)
        /usr/conf/lib/libhp-ux.a(rw_lock.o)
        /usr/conf/lib/liblvm.a(lv_block.o)
        /usr/conf/lib/liblvm.a(lv_cluster_lock.o)
        /usr/conf/lib/liblvm.a(lv_defect.o)
        /usr/conf/lib/liblvm.a(lv_hp.o)
        /usr/conf/lib/liblvm.a(lv_ioctls.o)
        /usr/conf/lib/liblvm.a(lv_lvsubr.o)
        /usr/conf/lib/liblvm.a(lv_mircons.o)
        /usr/conf/lib/liblvm.a(lv_phys.o)
        /usr/conf/lib/liblvm.a(lv_schedule.o)
        /usr/conf/lib/liblvm.a(lv_spare.o)
        /usr/conf/lib/liblvm.a(lv_strategy.o)
        /usr/conf/lib/liblvm.a(lv_subr.o)
        /usr/conf/lib/liblvm.a(lv_syscalls.o)
        /usr/conf/lib/liblvm.a(lv_vgda.o)
        /usr/conf/lib/liblvm.a(lv_vgsa.o)
        /usr/conf/lib/liblvm.a(sh_vgsa.o)
        /usr/conf/lib/liblvm.a(slvm_comm.o)

what(1) Output:
        /usr/conf/lib/libhp-ux.a(lv_lvm.o):
                lv_lvm.c $Date: 2000/04/27 14:02:14 $ $Revision: 1.3
                        .98.5 $ PATCH_10.20 (PHKL_21370)
        /usr/conf/lib/libhp-ux.a(rw_lock.o):
                rw_lock.c $Date: 2000/10/20 15:32:10 $ $Revision: 1.
                        8.98.7 $ PATCH_10.20 (PHKL_22529)
        /usr/conf/lib/liblvm.a(lv_block.o):
                lv_block.c $Date: 2001/03/10 14:56:42 $ $Revision: 1
                        .13.98.9 $ PATCH_10.20 (PHKL_23481)
        /usr/conf/lib/liblvm.a(lv_cluster_lock.o):
                lv_cluster_lock.c $Date: 2000/04/27 13:40:16 $ $Revi
                        sion: 1.10.98.9 $ PATCH_10.20 (PHKL_21370)
        /usr/conf/lib/liblvm.a(lv_defect.o):
                lv_defect.c $Date: 2001/03/10 14:56:40 $ $Revision:
                        1.16.98.9 $ PATCH_10.20 (PHKL_23481)
        /usr/conf/lib/liblvm.a(lv_hp.o):
                lv_hp.c $Date: 2001/03/10 14:55:21 $ $Revision: 1.18
                        .98.40 $ PATCH_10.20 (PHKL_23481)
        /usr/conf/lib/liblvm.a(lv_ioctls.o):
                lv_ioctls.c $Date: 2001/03/10 14:55:52 $ $Revision:
                        1.18.98.28 $ PATCH_10.20 (PHKL_23481)
        /usr/conf/lib/liblvm.a(lv_lvsubr.o):
                lv_lvsubr.c $Date: 2001/03/10 14:56:29 $ $Revision:
                        1.15.98.27 $ PATCH_10.20 (PHKL_23481)
        /usr/conf/lib/liblvm.a(lv_mircons.o):
                lv_mircons.c $Date: 2001/03/10 14:56:04 $ $Revision:
                         1.14.98.10 $ PATCH_10.20 (PHKL_23481)
        /usr/conf/lib/liblvm.a(lv_phys.o):
                lv_phys.c $Date: 2000/04/27 13:59:37 $ $Revision: 1.
                        14.98.21 $ PATCH_10.20 (PHKL_21370)
        /usr/conf/lib/liblvm.a(lv_schedule.o):
                lv_schedule.c $Date: 2000/04/27 13:59:39 $ $Revision
                        : 1.18.98.16 $ PATCH_10.20 (PHKL_21370)
        /usr/conf/lib/liblvm.a(lv_spare.o):
                lv_spare.c $Date: 2000/04/27 13:59:58 $ $Revision: 1
                        .3.98.12 $ PATCH_10.20 (PHKL_21370)
        /usr/conf/lib/liblvm.a(lv_strategy.o):
                lv_strategy.c $Date: 2000/04/27 14:00:04 $ $Revision
                        : 1.14.98.18 $ PATCH_10.20 (PHKL_21370)
        /usr/conf/lib/liblvm.a(lv_subr.o):
                lv_subr.c $Date: 2001/03/10 14:56:09 $ $Revision: 1.
                        18.98.12 $ PATCH_10.20 (PHKL_23481)
        /usr/conf/lib/liblvm.a(lv_syscalls.o):
                lv_syscalls.c $Date: 2000/04/27 14:00:07 $ $Revision
                        : 1.14.98.13 $ PATCH_10.20 (PHKL_21370)
        /usr/conf/lib/liblvm.a(lv_vgda.o):
                lv_vgda.c $Date: 2001/03/10 14:56:12 $ $Revision: 1.
                        18.98.9 $ PATCH_10.20 (PHKL_23481)
        /usr/conf/lib/liblvm.a(lv_vgsa.o):
                lv_vgsa.c $Date: 2001/03/10 14:56:27 $ $Revision: 1.
                        14.98.9 $ PATCH_10.20 (PHKL_23481)
        /usr/conf/lib/liblvm.a(sh_vgsa.o):
                sh_vgsa.c $Date: 2001/03/10 14:56:21 $ $Revision: 1
                        .3.98.12 $ PATCH_10.20 (PHKL_23481)
        /usr/conf/lib/liblvm.a(slvm_comm.o):
                slvm_comm.c $Date: 2001/03/10 14:56:44 $ $Revision:
                        1.3.98.6 $ PATCH_10.20 (PHKL_23481)

cksum(1) Output:
        3682845836 156624 /usr/conf/lib/libhp-ux.a(lv_lvm.o)
        3753784657 7132 /usr/conf/lib/libhp-ux.a(rw_lock.o)
        1887245431 2620 /usr/conf/lib/liblvm.a(lv_block.o)
        2776493385 10592 /usr/conf/lib/liblvm.a(lv_cluster_lock.o)
        3198851558 12788 /usr/conf/lib/liblvm.a(lv_defect.o)
        2891246741 91892 /usr/conf/lib/liblvm.a(lv_hp.o)
        992211100 35120 /usr/conf/lib/liblvm.a(lv_ioctls.o)
        2163901249 39192 /usr/conf/lib/liblvm.a(lv_lvsubr.o)
        1231446672 18624 /usr/conf/lib/liblvm.a(lv_mircons.o)
        3498976193 8424 /usr/conf/lib/liblvm.a(lv_phys.o)
        2206454939 26332 /usr/conf/lib/liblvm.a(lv_schedule.o)
        723445810 38920 /usr/conf/lib/liblvm.a(lv_spare.o)
        907693295 7476 /usr/conf/lib/liblvm.a(lv_strategy.o)
        3626544382 16120 /usr/conf/lib/liblvm.a(lv_subr.o)
        271633937 14176 /usr/conf/lib/liblvm.a(lv_syscalls.o)
        2559876353 9624 /usr/conf/lib/liblvm.a(lv_vgda.o)
        2080382172 12696 /usr/conf/lib/liblvm.a(lv_vgsa.o)
        1750144930 42624 /usr/conf/lib/liblvm.a(sh_vgsa.o)
        45683920 27104 /usr/conf/lib/liblvm.a(slvm_comm.o)

Patch Conflicts: None

Patch Dependencies:
        s800: 10.20: PHKL_16751

Hardware Dependencies: None

Other Dependencies:
        PHKL_21085 should also be installed on systems using Nike,
        Galaxy, or Optimus disk arrays in a Shared LVM configuration
        to improve the recovery after the hot-swapping of array
        Service Processors.

Supersedes:
        PHKL_17547 PHKL_19167 PHKL_19210 PHKL_19697 PHKL_19705 PHKL_20057
        PHKL_20808 PHKL_20964 PHKL_21370 PHKL_22529

Equivalent Patches:
        PHKL_23480:
        s700: 10.20

Patch Package Size: 650 KBytes

Installation Instructions:
        Please review all instructions and the Hewlett-Packard
        SupportLine User Guide or your Hewlett-Packard support terms
        and conditions for precautions, scope of license,
        restrictions, and, limitation of liability and warranties,
        before installing this patch.
        ------------------------------------------------------------
        1. Back up your system before installing a patch.

        2. Login as root.

        3. Copy the patch to the /tmp directory.

        4. Move to the /tmp directory and unshar the patch:

                cd /tmp
                sh PHKL_23481

        5a. For a standalone system, run swinstall to install the
            patch:

                swinstall -x autoreboot=true -x match_target=true \
                        -s /tmp/PHKL_23481.depot

        By default swinstall will archive the original software in
        /var/adm/sw/patch/PHKL_23481. If you do not wish to retain a
        copy of the original software, you can create an empty file
        named /var/adm/sw/patch/PATCH_NOSAVE.

        WARNING: If this file exists when a patch is installed, the
                 patch cannot be deinstalled. Please be careful
                 when using this feature.

        It is recommended that you move the PHKL_23481.text file to
        /var/adm/sw/patch for future reference.

        To put this patch on a magnetic tape and install from the
        tape drive, use the command:

                dd if=/tmp/PHKL_23481.depot of=/dev/rmt/0m bs=2k

Special Installation Instructions:
        New tests run for the first time on this patch revealed a
        preexisting problem with some LVM commands which will be
        fixed in a separate commands patch. Commands that are run
        independently work fine, but when a logical volume command
        (lvchange, lvcreate, lvextend, lvreduce, lvremove, lvrmboot)
        is run at the same time as a volume group command (vgchgid,
        vgexport, vgreduce, vgremove, vgscan), it is possible that
        the 'lvlnboot -R' and vgcfgbackup portions of the logical
        volume command may fail. The best way to avoid the problem
        is not to run the indicated LVM commands simultaneously.

        If the 'lvlnboot -R' or vgcfgbackup operation fails, the
        workaround is simply to repeat these manually. Similarly,
        vgdisplay and lvdisplay might fail if they are run while
        the LVM configuration is changing. If this happens, simply
        repeat the vgdisplay or lvdisplay command.

        There are no inconsistencies introduced into the LVM
        configuration file or the on-disk LVM data structures by
        this defect. However, it is important to run the failed
        'lvlnboot -R' command when boot logical volumes are changed
        and to perform configuration backups whenever the volume
        group configuration is changed.

        This patch depends on base patch PHKL_16751.
        For successful installation, please ensure that PHKL_16751
        is in the same depot with this patch, or PHKL_16751 is
        already installed.

        Due to the number of objects in this patch, the
        customization phase of the update may take more than 10
        minutes. During that time the system will not appear to
        make forward progress, but it will actually be installing
        the objects.
-----End of Document ID: PHKL_23481------------------------------------------


Document ID: PHSS_23358
Date Loaded: 20010315
      Title: s700_800 10.20 ODBCLINK/SE F.00.00 Run-Time Patch

Patch Name: PHSS_23358

Patch Description: s700_800 10.20 ODBCLINK/SE F.00.00 Run-Time Patch

Creation Date: 01/02/26

Post Date: 01/03/15

Hardware Platforms - OS Releases:
        s700: 10.20
        s800: 10.20

Products:
        HP SQL/HP-UX A.G3.17 A.G3.14

Filesets:
        ALLBASE-SQL.AB-ODBCSE,E.58.03

Automatic Reboot?: No

Status: General Release

Critical: No

Path Name: /hp-ux_patches/s700_800/10.X/PHSS_23358

Symptoms:
        PHSS_23358:

        SR# 8606157045
        dberr 2103 when doing a lock table on odbclink/se 58.03

        SR# 8606133019
        Using Visual Basic RDO query returns max of 200 rows on a
        second select

        SR# 8606168718
        ODBCLink/SE SQLAllocStmt fails: Can't change timeout on
        active statement

Defect Description:
        PHSS_23358:

        SR# 8606157045
        dberr 2103 when doing a lock table on odbclink/se 58.03

        SR# 8606133019
        Using Visual Basic RDO query returns max of 200 rows on a
        second select

        SR# 8606168718
        ODBCLink/SE SQLAllocStmt fails: Can't change timeout on
        active statement

SR:
        8606157045 8606133019 8606168718

Patch Files:
        /opt/allbase/bin/odbcse/HPREADME
        /opt/allbase/bin/odbcse/odbccl32
        /opt/allbase/bin/odbcse/odbclnse
        /opt/allbase/bin/odbcse/odbcutse

what(1) Output:
        /opt/allbase/bin/odbcse/HPREADME:
                None
        /opt/allbase/bin/odbcse/odbccl32:
                None
        /opt/allbase/bin/odbcse/odbclnse:
                HP92453-02A.11.00 HP-UX SYMBOLIC DEBUGGER (END.O
                ILP32) $Revision: 75.02 $
                $header: ODBCHOST.C 1.61 TUE, OCT 3, 2000, 4:41 PM
                JOHNM.ODBCLINK $
                $revision: 1.61 $
                $header: ODBCCONS.C 1.13 THU, JUN 29, 2000, 11:35
                AM JOHNM.ODBCLINK $
                $revision: 1.13 $
                $header: ODBCSERV.C 1.103 WED, OCT 4, 2000, 3:02 PM
                JOHNM.ODBCLINK $
                $revision: 1.103 $
                $header: ODBCCOMH.C 1.31 TUE, JAN 25, 2000, 11:02
                AM MGR.ODBCLINK $
                $revision: 1.31 $
                $header: ODBCFMT.C 1.79 WED, JUN 7, 2000, 4:22 PM
                MGR.ODBCLINK $
                $revision: 1.79 $
                $header: VERSJR.C 1.2 MON, MAR 15, 1999, 2:08 PM
                MGR.ODBCLINK $
                $revision: 1.2 $
                $header: PARSE.C 1.101 WED, SEP 20, 2000, 2:15 PM
                JOHNM.ODBCLINK $
                $revision: 1.101 $
                $header: OPEN.C 1.141 THU, OCT 5, 2000, 11:07 AM
                JOHNM.ODBCLINK $
                $revision: 1.141 $
                $header: ERROR.C 1.15 FRI, APR 28, 2000, 2:11 PM
                JOHNM.ODBCLINK $
                $revision: 1.15 $
                $header: DATACONV.C 1.76 MON, JUL 17, 2000, 2:32 PM
                JOHNM.ODBCLINK $
                $revision: 1.76 $
                $header: FETCH.C 1.84 TUE, SEP 19, 2000, 1:47 PM
                YEOUNWHA.ODBCLINK $
                $revision: 1.84 $
                $header: NONSQL.C 1.29 TUE, JAN 25, 2000, 10:18 AM
                MGR.ODBCLINK $
                $revision: 1.29 $
                $header: QUERY.C 1.64 TUE, SEP 26, 2000, 2:20 PM
                JOHNM.ODBCLINK $
                $revision: 1.64 $
                $header: SECURE.C 1.10 THU, FEB 17, 2000, 9:35 AM
                MGR.ODBCLINK $
                $revision: 1.10 $
                $header: SQL.C 1.4 THU, JUN 15, 2000, 12:16 PM
                JOHNM.ODBCLINK $
                $revision: 1.4 $
                $header: STUBS.C 1.20 WED, MAY 31, 2000, 9:57 AM
                MGR.ODBCLINK $
                $revision: 1.20 $
                $header: ALLBASER.C 1.60 THU, AUG 17, 2000, 11:39
                AM JOHNM.ODBCLINK $
                $revision: 1.60 $
                $header: ALLBASEX.PC 1.18 WED, MAY 10, 2000, 6:45
                PM MATTHEW.ODBCLINK $
                $revision: 1.18 $
                $header: ORASTUBS.C 1.2 FRI, FEB 26, 1999, 2:47 PM
                MGR.ODBCLINK $
                $revision: 1.2 $
                HP36217-02A.G3.04 SQLX/9000 ALLBASE/SQL
                HP36217-02A.G3.04.00 SQL Parser/Linearizer/9000
                ALLBASE/SQL 02/03/99
                HP36217-02A.G3.04 NET AF Library ALLBASE/SQL
                02/02/99
                HP36217-02A.G3.04 NET Library ALLBASE/SQL 02/02/99
                HP36217-02A.G3.04 NET VC Library ALLBASE/SQL
                02/02/99
                PATCH-PHCO_17381 for 10.20; for 10.30, 11.x
                compatibility libc.a_ID/main/r10dav/libc_dav/15
                /ux/core/libs/libc/archive_pa1/libc.a_ID
                Mar 9 1999 13:52:37
        /opt/allbase/bin/odbcse/odbcutse:
                HP92453-02A.11.00 HP-UX SYMBOLIC DEBUGGER (END.O
                ILP32) $Revision: 75.02 $
                $header: ODBCUTIL.C 1.69 THU, JUL 13, 2000, 11:36
                AM MATTHEW.ODBCLINK $
                $revision: 1.69 $
                $header: VERSJR.C 1.2 MON, MAR 15, 1999, 2:08 PM
                MGR.ODBCLINK $
                $revision: 1.2 $
                $header: PARSE.C 1.101 WED, SEP 20, 2000, 2:15 PM
                JOHNM.ODBCLINK $
                $revision: 1.101 $
                $header: OPEN.C 1.141 THU, OCT 5, 2000, 11:07 AM
                JOHNM.ODBCLINK $
                $revision: 1.141 $
                $header: ERROR.C 1.15 FRI, APR 28, 2000, 2:11 PM
                JOHNM.ODBCLINK $
                $revision: 1.15 $
                $header: DATACONV.C 1.76 MON, JUL 17, 2000, 2:32 PM
                JOHNM.ODBCLINK $
                $revision: 1.76 $
                $header: FETCH.C 1.84 TUE, SEP 19, 2000, 1:47 PM
                YEOUNWHA.ODBCLINK $
                $revision: 1.84 $
                $header: NONSQL.C 1.29 TUE, JAN 25, 2000, 10:18 AM
                MGR.ODBCLINK $
                $revision: 1.29 $
                $header: QUERY.C 1.64 TUE, SEP 26, 2000, 2:20 PM
                JOHNM.ODBCLINK $
                $revision: 1.64 $
                $header: SECURE.C 1.10 THU, FEB 17, 2000, 9:35 AM
                MGR.ODBCLINK $
                $revision: 1.10 $
                $header: SQL.C 1.4 THU, JUN 15, 2000, 12:16 PM
                JOHNM.ODBCLINK $
                $revision: 1.4 $
                $header: STUBS.C 1.20 WED, MAY 31, 2000, 9:57 AM
                MGR.ODBCLINK $
                $revision: 1.20 $
                $header: ALLBASER.C 1.60 THU, AUG 17, 2000, 11:39
                AM JOHNM.ODBCLINK $
                $revision: 1.60 $
                $header: ALLBASEX.PC 1.18 WED, MAY 10, 2000, 6:45
                PM MATTHEW.ODBCLINK $
                $revision: 1.18 $
                $header: ORASTUBS.C 1.2 FRI, FEB 26, 1999, 2:47 PM
                MGR.ODBCLINK $
                $revision: 1.2 $
                HP36217-02A.G3.04 SQLX/9000 ALLBASE/SQL
                HP36217-02A.G3.04.00 SQL Parser/Linearizer/9000
                ALLBASE/SQL 02/03/99
                HP36217-02A.G3.04 NET AF Library ALLBASE/SQL
                02/02/99
                HP36217-02A.G3.04 NET Library ALLBASE/SQL 02/02/99
                HP36217-02A.G3.04 NET VC Library ALLBASE/SQL
                02/02/99
                PATCH-PHCO_17381 for 10.20; for 10.30, 11.x
                compatibility libc.a_ID/main/r10dav/libc_dav/15
                /ux/core/libs/libc/archive_pa1/libc.a_ID
                Mar 9 1999 13:52:37

cksum(1) Output:
        3027944210 6383 /opt/allbase/bin/odbcse/HPREADME
        1102762546 6505769 /opt/allbase/bin/odbcse/odbccl32
        38812643 3582192 /opt/allbase/bin/odbcse/odbclnse
        912678471 3403144 /opt/allbase/bin/odbcse/odbcutse

Patch Conflicts: None

Patch Dependencies: None

Hardware Dependencies: None

Other Dependencies: None

Supersedes: None

Equivalent Patches:
        PHSS_23359:
        s700: 11.00
        s800: 11.00

Patch Package Size: 13240 KBytes

Installation Instructions:
        Please review all instructions and the Hewlett-Packard
        SupportLine User Guide or your Hewlett-Packard support terms
        and conditions for precautions, scope of license,
        restrictions, and, limitation of liability and warranties,
        before installing this patch.
        ------------------------------------------------------------
        1. Back up your system before installing a patch.

        2. Login as root.

        3. Copy the patch to the /tmp directory.

        4. Move to the /tmp directory and unshar the patch:

                cd /tmp
                sh PHSS_23358

        5a. For a standalone system, run swinstall to install the
            patch:

                swinstall -x autoreboot=true -x match_target=true \
                        -s /tmp/PHSS_23358.depot

        By default swinstall will archive the original software in
        /var/adm/sw/patch/PHSS_23358. If you do not wish to retain a
        copy of the original software, you can create an empty file
        named /var/adm/sw/patch/PATCH_NOSAVE.

        WARNING: If this file exists when a patch is installed, the
                 patch cannot be deinstalled. Please be careful
                 when using this feature.

        It is recommended that you move the PHSS_23358.text file to
        /var/adm/sw/patch for future reference.

        To put this patch on a magnetic tape and install from the
        tape drive, use the command:

                dd if=/tmp/PHSS_23358.depot of=/dev/rmt/0m bs=2k

Special Installation Instructions:
        From this version onward client support for 16-bit
        is not provided. The client file ODBCCL32 is now a
        "ZIP" file rather than a self extracting executable.
        You may need WINZIP to extract the files.
-----End of Document ID: PHSS_23358------------------------------------------


Document ID: PHSS_22881
Date Loaded: 20010315
      Title: s700_800 10.20 OV ITO6.0X HP-UX 11.x Agent Patch A.06.03

Patch Name: PHSS_22881

Patch Description: s700_800 10.20 OV ITO6.0X HP-UX 11.x Agent Patch A.06.03

Creation Date: 01/03/13

Post Date: 01/03/15

Hardware Platforms - OS Releases:
        s700: 10.20
        s800: 10.20

Products:
        OpenView IT/Operations 6.0

Filesets:
        OVOPC-CLT.OVOPC-UX11-CLT,A.06.00

Automatic Reboot?: No

Status: General Release

Critical: No

Path Name: /hp-ux_patches/s700_800/10.X/PHSS_22881

Symptoms:
        PHSS_22881:
        - Changes were required for the security add-on product
          VantagePoint Advanced Security.
        - agent installation configure script fails to convert
          ITO 4 queue files: awk syntax error in swagent.log file

        PHSS_22012:
        - disk_mon.sh returns invalid values if the bdf command
          returns more than one line output for a filesystem
          (e.g. if the filesystem name exceeds its column width)
        - Several changes for firewall environments. For detailed
          information refer to the VPO Firewall Configuration
          White Paper version 3.0
        - When executing large numbers of autoactions, some of them
          were staying in 'running' state.
        - opctrapi aborts after getting traps with unresolvable IP
          address.
        - The handling of '\' was different in the pattern
          definition and the "matching pattern".
        - if buffer file size limitation is enabled the agent may
          discard low-severity messages even if there is still
          space in the buffer file

Defect Description:
        PHSS_22881:
        check the list of the symptoms

        PHSS_22012:
        check the list of the symptoms

SR:
        B555009152 B555008613 B555008314 B555007752 B555007709
        B555007602 B555007426 B555006890 B555006267 8606137088

Patch Files:
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/opc_pkg.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/install/opcrclchk
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/install/opcrdschk
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/install/opcrndchk
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/install/opcroschk
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/install/opcrverchk
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/install/opcrinst
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/monitor/ana_disk.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/monitor/cpu_mon.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/monitor/disk_mon.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/monitor/last_logs.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/monitor/mailq_l.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/monitor/proc_mon.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/monitor/sh_procs.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/monitor/swap_mon.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/monitor/vp_chk.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/monitor/dist_mon.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/monitor/mondbfile.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/monitor/ssp_chk.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/monitor/opcfwtmp.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/monitor/opcnprcs.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/monitor/
                opc_get_ems_resource.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/actions/mailq_pr.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/actions/st_inetd.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/actions/st_syslogd.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/actions/st_mail.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/actions/dist_del.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/cmds/opcdf.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/cmds/opclpst.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/cmds/opcps.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/cmds/E10000Log.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/cmds/ssp_config.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/cmds/opc_sec_v.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/AgentPlatform

what(1) Output:
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/opc_pkg.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/install/opcrclchk:
                HP OpenView VantagePoint A.06.03 (02/13/01)
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/install/opcrdschk:
                HP OpenView VantagePoint A.06.03 (02/13/01)
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/install/opcrndchk:
                HP OpenView VantagePoint A.06.03 (02/13/01)
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/install/opcroschk:
                HP OpenView VantagePoint A.06.03 (02/13/01)
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/install/opcrverchk:
                HP OpenView VantagePoint A.06.03 (02/13/01)
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/install/opcrinst:
                HP OpenView VantagePoint A.06.03 (02/13/01)
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/monitor/ana_disk.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/monitor/cpu_mon.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/monitor/disk_mon.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/monitor/last_logs.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/monitor/mailq_l.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/monitor/proc_mon.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/monitor/sh_procs.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/monitor/swap_mon.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/monitor/vp_chk.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/monitor/dist_mon.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/monitor/mondbfile.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/monitor/ssp_chk.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/monitor/opcfwtmp.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/monitor/opcnprcs.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/monitor/
                opc_get_ems_resource.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/actions/mailq_pr.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/actions/st_inetd.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/actions/st_syslogd.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/actions/st_mail.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/actions/dist_del.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/cmds/opcdf.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/cmds/opclpst.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/cmds/opcps.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/cmds/E10000Log.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/cmds/ssp_config.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/A.06.03/RPC_DCE_TCP/cmds/opc_sec_v.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/pa-risc/
                hp-ux11/AgentPlatform:
                None

cksum(1) Output:
        1271432915 7534093 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/pa-risc/hp-ux11/A.06.03/RPC_DCE_TCP/
                opc_pkg.Z
        1701946874 6708 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/pa-risc/hp-ux11/A.06.03/RPC_DCE_TCP/
                install/opcrclchk
        1413231539 28659 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/pa-risc/hp-ux11/A.06.03/RPC_DCE_TCP/
                install/opcrdschk
        2712646702 6720 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/pa-risc/hp-ux11/A.06.03/RPC_DCE_TCP/
                install/opcrndchk
        1865863824 6287 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/pa-risc/hp-ux11/A.06.03/RPC_DCE_TCP/
                install/opcroschk
        1071737952 31788 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/pa-risc/hp-ux11/A.06.03/RPC_DCE_TCP/
                install/opcrverchk
        4155948290 105219 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/pa-risc/hp-ux11/A.06.03/RPC_DCE_TCP/
                install/opcrinst
        643522410 2731 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/pa-risc/hp-ux11/A.06.03/RPC_DCE_TCP/
                monitor/ana_disk.sh.Z
        1886211588 5977 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/pa-risc/hp-ux11/A.06.03/RPC_DCE_TCP/
                monitor/cpu_mon.sh.Z
        2371254160 6040 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/pa-risc/hp-ux11/A.06.03/RPC_DCE_TCP/
                monitor/disk_mon.sh.Z
        2767097449 5847 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/pa-risc/hp-ux11/A.06.03/RPC_DCE_TCP/
                monitor/last_logs.sh.Z
        3677040148 5842 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/pa-risc/hp-ux11/A.06.03/RPC_DCE_TCP/
                monitor/mailq_l.sh.Z
        2910083782 6008 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/pa-risc/hp-ux11/A.06.03/RPC_DCE_TCP/
                monitor/proc_mon.sh.Z
        359637373 5439 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/pa-risc/hp-ux11/A.06.03/RPC_DCE_TCP/
                monitor/sh_procs.sh.Z
        2312257539 5884 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/pa-risc/hp-ux11/A.06.03/RPC_DCE_TCP/
                monitor/swap_mon.sh.Z
        243195849 5743 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/pa-risc/hp-ux11/A.06.03/RPC_DCE_TCP/
                monitor/vp_chk.sh.Z
        3563612125 6125 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/pa-risc/hp-ux11/A.06.03/RPC_DCE_TCP/
                monitor/dist_mon.sh.Z
        3988654549 14386 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/pa-risc/hp-ux11/A.06.03/RPC_DCE_TCP/
                monitor/mondbfile.sh.Z
        288486600 5985 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/pa-risc/hp-ux11/A.06.03/RPC_DCE_TCP/
                monitor/ssp_chk.sh.Z
        352276620 13459 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/pa-risc/hp-ux11/A.06.03/RPC_DCE_TCP/
                monitor/opcfwtmp.Z
        1152145441 10212 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/pa-risc/hp-ux11/A.06.03/RPC_DCE_TCP/
                monitor/opcnprcs.Z
        2374480424 18894 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/pa-risc/hp-ux11/A.06.03/RPC_DCE_TCP/
                monitor/opc_get_ems_resource.Z
        2384349740 2537 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/pa-risc/hp-ux11/A.06.03/RPC_DCE_TCP/
                actions/mailq_pr.sh.Z
        4097820511 2581 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/pa-risc/hp-ux11/A.06.03/RPC_DCE_TCP/
                actions/st_inetd.sh.Z
        328357893 2590 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/pa-risc/hp-ux11/A.06.03/RPC_DCE_TCP/
                actions/st_syslogd.sh.Z
        356548349 2582 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/pa-risc/hp-ux11/A.06.03/RPC_DCE_TCP/
                actions/st_mail.sh.Z
        1641796185 6099 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/pa-risc/hp-ux11/A.06.03/RPC_DCE_TCP/
                actions/dist_del.sh.Z
        3387604035 324 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/pa-risc/hp-ux11/A.06.03/RPC_DCE_TCP/cmds/
                opcdf.Z
        4104454961 386 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/pa-risc/hp-ux11/A.06.03/RPC_DCE_TCP/cmds/
                opclpst.Z
        1746062549 401 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/pa-risc/hp-ux11/A.06.03/RPC_DCE_TCP/cmds/
                opcps.Z
        3371519425 3322 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/pa-risc/hp-ux11/A.06.03/RPC_DCE_TCP/cmds/
                E10000Log.sh.Z
        445974867 3106 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/pa-risc/hp-ux11/A.06.03/RPC_DCE_TCP/cmds/
                ssp_config.sh.Z
        3051914556 13151 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/pa-risc/hp-ux11/A.06.03/RPC_DCE_TCP/cmds/
                opc_sec_v.sh.Z
        483349596 6324 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/pa-risc/hp-ux11/AgentPlatform

Patch Conflicts: None

Patch Dependencies: None

Hardware Dependencies: None

Other Dependencies: None

Supersedes:
        PHSS_22012

Equivalent Patches:
        ITOSOL_00066:
        sparcSOL: 2.6 2.7 2.8

        PHSS_22882:
        s700: 11.00
        s800: 11.00

Patch Package Size: 7820 KBytes

Installation Instructions:
        Please review all instructions and the Hewlett-Packard
        SupportLine User Guide or your Hewlett-Packard support terms
        and conditions for precautions, scope of license,
        restrictions, and, limitation of liability and warranties,
        before installing this patch.
        ------------------------------------------------------------
        1. Back up your system before installing a patch.

        2. Login as root.

        3. Copy the patch to the /tmp directory.

        4. Move to the /tmp directory and unshar the patch:

                cd /tmp
                sh PHSS_22881

        5a. For a standalone system, run swinstall to install the
            patch:

                swinstall -x autoreboot=true -x match_target=true \
                        -s /tmp/PHSS_22881.depot

        By default swinstall will archive the original software in
        /var/adm/sw/patch/PHSS_22881. If you do not wish to retain a
        copy of the original software, you can create an empty file
        named /var/adm/sw/patch/PATCH_NOSAVE.

        WARNING: If this file exists when a patch is installed, the
                 patch cannot be deinstalled. Please be careful
                 when using this feature.

        It is recommended that you move the PHSS_22881.text file to
        /var/adm/sw/patch for future reference.

        To put this patch on a magnetic tape and install from the
        tape drive, use the command:

                dd if=/tmp/PHSS_22881.depot of=/dev/rmt/0m bs=2k

Special Installation Instructions:
        BEFORE LOADING THIS PATCH...

            o It provides bug fixes and enhancements for the
              VPO A.06.00 Management Server system.

            o DO NOT use this patch with older releases of ITO,
              for example versions A.05.00, A.05.11 or A.05.30
        (A) Patch Installation Instructions
            -------------------------------

        (A1) Install the patch, following the standard
              installation instructions.

              For backing up the system before installing
              a patch, you may use opc_backup(1m)

        NOTE: MAKE SURE THAT NO AGENT OF THE PLATFORM
              ADDRESSED BY THIS PATCH IS DISTRIBUTED
              (either from the VPO Administrator's GUI
              or from command line using inst.sh) WHILE
              RUNNING SWINSTALL.

              Don't be afraid of the '-x autoreboot=true'
              option above. There won't be a reboot due
              to this VPO patch.
              You can skip this option if you like.

        NOTE: This patch must be installed on the VPO Management
              Server system, NOT on an VPO Managed Node directly.
              Changes will take effect on managed nodes by means of
              VPO Software Distribution (using 'Force Update' if
              there is already an agent installed on the managed
              node). See chapter 2 of the VPO Administrator's
              Reference manual for more information.

        (B) Patch Deinstallation Instructions
            ---------------------------------

        (B1) To deinstall the patch PHSS_22881 run swremove:

              NOTE: MAKE SURE THAT NO AGENT OF THE PLATFORM
                    ADDRESSED BY THIS PATCH IS DISTRIBUTED (either
                    from the ITO Administrator's GUI or from
                    command line using inst.sh) WHILE RUNNING
                    SWREMOVE.

              # swremove PHSS_22881
-----End of Document ID: PHSS_22881------------------------------------------


Document ID: PHSS_22879
Date Loaded: 20010315
      Title: s700_800 10.20 OV ITO6.0X HP-UX 10.x Agent Patch A.06.03

Patch Name: PHSS_22879

Patch Description: s700_800 10.20 OV ITO6.0X HP-UX 10.x Agent Patch A.06.03

Creation Date: 01/03/13

Post Date: 01/03/15

Hardware Platforms - OS Releases:
        s700: 10.20
        s800: 10.20

Products:
        OpenView IT/Operations 6.0

Filesets:
        OVOPC-CLT.OVOPC-UX10-CLT,A.06.00

Automatic Reboot?: No

Status: General Release

Critical: No

Path Name: /hp-ux_patches/s700_800/10.X/PHSS_22879

Symptoms:
        PHSS_22879:
        - Changes were required for the security add-on product
          VantagePoint Advanced Security.
        - agent installation configure script fails to convert
          ITO 4 queue files: awk syntax error in swagent.log file

        PHSS_22010:
        - disk_mon.sh returns invalid values if the bdf command
          returns more than one line output for a filesystem
          (e.g. if the filesystem name exceeds its column width)
        - Several changes for firewall environments. For detailed
          information refer to the VPO Firewall Configuration
          White Paper version 3.0
        - When executing large numbers of autoactions, some of them
          were staying in 'running' state.
        - opctrapi aborts after getting traps with unresolvable IP
          address.
        - The handling of '\' was different in the pattern
          definition and the "matching pattern".
        - if buffer file size limitation is enabled the agent may
          discard low-severity messages even if there is still
          space in the buffer file

Defect Description:
        PHSS_22879:
        check the list of the symptoms

        PHSS_22010:
        check the list of the symptoms

SR:
        B555009152 B555008613 B555008314 B555007752 B555007709
        B555007602 B555007426 B555006890 B555006267 8606137088

Patch Files:
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/opc_pkg.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/install/opcrclchk
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/install/opcrdschk
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/install/opcrndchk
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/install/opcroschk
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/install/opcrverchk
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/install/opcrinst
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/monitor/ana_disk.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/monitor/cpu_mon.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/monitor/disk_mon.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/monitor/last_logs.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/monitor/mailq_l.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/monitor/proc_mon.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/monitor/swap_mon.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/monitor/sh_procs.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/monitor/vp_chk.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/monitor/dist_mon.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/monitor/mondbfile.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/monitor/ssp_chk.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/monitor/opcfwtmp.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/monitor/opcnprcs.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/monitor/
                opc_get_ems_resource.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/actions/mailq_pr.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/actions/st_inetd.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/actions/st_syslogd.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/actions/st_mail.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/actions/dist_del.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/cmds/opcdf.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/cmds/opclpst.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/cmds/opcps.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/cmds/E10000Log.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/cmds/ssp_config.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/cmds/opc_sec_v.sh.Z
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/AgentPlatform
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s800/
                hp-ux10/AgentPlatform

what(1) Output:
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/opc_pkg.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/install/opcrclchk:
                HP OpenView VantagePoint A.06.03 (02/14/01)
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/install/opcrdschk:
                HP OpenView VantagePoint A.06.03 (02/14/01)
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/install/opcrndchk:
                HP OpenView VantagePoint A.06.03 (02/14/01)
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/install/opcroschk:
                HP OpenView VantagePoint A.06.03 (02/14/01)
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/install/opcrverchk:
                HP OpenView VantagePoint A.06.03 (02/14/01)
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/install/opcrinst:
                HP OpenView VantagePoint A.06.03 (02/14/01)
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/monitor/ana_disk.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/monitor/cpu_mon.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/monitor/disk_mon.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/monitor/last_logs.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/monitor/mailq_l.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/monitor/proc_mon.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/monitor/swap_mon.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/monitor/sh_procs.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/monitor/vp_chk.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/monitor/dist_mon.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/monitor/mondbfile.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/monitor/ssp_chk.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/monitor/opcfwtmp.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/monitor/opcnprcs.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/monitor/
                opc_get_ems_resource.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/actions/mailq_pr.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/actions/st_inetd.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/actions/st_syslogd.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/actions/st_mail.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/actions/dist_del.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/cmds/opcdf.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/cmds/opclpst.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/cmds/opcps.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/cmds/E10000Log.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/cmds/ssp_config.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/A.06.03/RPC_DCE_TCP/cmds/opc_sec_v.sh.Z:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s700/
                hp-ux10/AgentPlatform:
                None
        /var/opt/OV/share/databases/OpC/mgd_node/vendor/hp/s800/
                hp-ux10/AgentPlatform:
                None

cksum(1) Output:
        1426758660 7509526 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s700/hp-ux10/A.06.03/RPC_DCE_TCP/opc_pkg.Z
        549947403 6898 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s700/hp-ux10/A.06.03/RPC_DCE_TCP/install/
                opcrclchk
        2873125364 28659 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s700/hp-ux10/A.06.03/RPC_DCE_TCP/install/
                opcrdschk
        1045260605 6734 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s700/hp-ux10/A.06.03/RPC_DCE_TCP/install/
                opcrndchk
        2798385959 6287 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s700/hp-ux10/A.06.03/RPC_DCE_TCP/install/
                opcroschk
        1107600480 32236 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s700/hp-ux10/A.06.03/RPC_DCE_TCP/install/
                opcrverchk
        1315316847 105784 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s700/hp-ux10/A.06.03/RPC_DCE_TCP/install/
                opcrinst
        1507632593 2731 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s700/hp-ux10/A.06.03/RPC_DCE_TCP/monitor/
                ana_disk.sh.Z
        1153108917 5977 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s700/hp-ux10/A.06.03/RPC_DCE_TCP/monitor/
                cpu_mon.sh.Z
        3431123336 6113 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s700/hp-ux10/A.06.03/RPC_DCE_TCP/monitor/
                disk_mon.sh.Z
        1264682947 5847 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s700/hp-ux10/A.06.03/RPC_DCE_TCP/monitor/
                last_logs.sh.Z
        3842413466 5842 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s700/hp-ux10/A.06.03/RPC_DCE_TCP/monitor/
                mailq_l.sh.Z
        125526017 6008 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s700/hp-ux10/A.06.03/RPC_DCE_TCP/monitor/
                proc_mon.sh.Z
        2254766819 5884 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s700/hp-ux10/A.06.03/RPC_DCE_TCP/monitor/
                swap_mon.sh.Z
        3337310400 5439 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s700/hp-ux10/A.06.03/RPC_DCE_TCP/monitor/
                sh_procs.sh.Z
        44923687 5741 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s700/hp-ux10/A.06.03/RPC_DCE_TCP/monitor/
                vp_chk.sh.Z
        1648535914 6125 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s700/hp-ux10/A.06.03/RPC_DCE_TCP/monitor/
                dist_mon.sh.Z
        538649249 14386 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s700/hp-ux10/A.06.03/RPC_DCE_TCP/monitor/
                mondbfile.sh.Z
        316974996 5985 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s700/hp-ux10/A.06.03/RPC_DCE_TCP/monitor/
                ssp_chk.sh.Z
        3308619561 12402 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s700/hp-ux10/A.06.03/RPC_DCE_TCP/monitor/
                opcfwtmp.Z
        1498118547 9458 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s700/hp-ux10/A.06.03/RPC_DCE_TCP/monitor/
                opcnprcs.Z
        3288429598 17925 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s700/hp-ux10/A.06.03/RPC_DCE_TCP/monitor/
                opc_get_ems_resource.Z
        1931806786 2537 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s700/hp-ux10/A.06.03/RPC_DCE_TCP/actions/
                mailq_pr.sh.Z
        892609819 2581 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s700/hp-ux10/A.06.03/RPC_DCE_TCP/actions/
                st_inetd.sh.Z
        691529804 2590 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s700/hp-ux10/A.06.03/RPC_DCE_TCP/actions/
                st_syslogd.sh.Z
        1206499283 2582 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s700/hp-ux10/A.06.03/RPC_DCE_TCP/actions/
                st_mail.sh.Z
        4060767072 6099 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s700/hp-ux10/A.06.03/RPC_DCE_TCP/actions/
                dist_del.sh.Z
        3943412997 324 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s700/hp-ux10/A.06.03/RPC_DCE_TCP/cmds/
                opcdf.Z
        3986935362 386 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s700/hp-ux10/A.06.03/RPC_DCE_TCP/cmds/
                opclpst.Z
        768832386 401 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s700/hp-ux10/A.06.03/RPC_DCE_TCP/cmds/
                opcps.Z
        2823941480 3322 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s700/hp-ux10/A.06.03/RPC_DCE_TCP/cmds/
                E10000Log.sh.Z
        3619885336 3106 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s700/hp-ux10/A.06.03/RPC_DCE_TCP/cmds/
                ssp_config.sh.Z
        1276834919 13151 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s700/hp-ux10/A.06.03/RPC_DCE_TCP/cmds/
                opc_sec_v.sh.Z
        3885164851 6319 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s700/hp-ux10/AgentPlatform
        1491926144 6317 /var/opt/OV/share/databases/OpC/mgd_node/
                vendor/hp/s800/hp-ux10/AgentPlatform

Patch Conflicts: None

Patch Dependencies: None

Hardware Dependencies: None

Other Dependencies: None

Supersedes:
        PHSS_22010

Equivalent Patches:
        ITOSOL_00065:
        sparcSOL: 2.6 2.7 2.8

        PHSS_22880:
        s700: 11.00
        s800: 11.00

Patch Package Size: 7810 KBytes

Installation Instructions:
        Please review all instructions and the Hewlett-Packard
        SupportLine User Guide or your Hewlett-Packard support terms
        and conditions for precautions, scope of license,
        restrictions, and, limitation of liability and warranties,
        before installing this patch.
        ------------------------------------------------------------
        1. Back up your system before installing a patch.

        2. Login as root.

        3. Copy the patch to the /tmp directory.

        4. Move to the /tmp directory and unshar the patch:

                cd /tmp
                sh PHSS_22879

        5a. For a standalone system, run swinstall to install the
            patch:

                swinstall -x autoreboot=true -x match_target=true \
                        -s /tmp/PHSS_22879.depot

        By default swinstall will archive the original software in
        /var/adm/sw/patch/PHSS_22879. If you do not wish to retain a
        copy of the original software, you can create an empty file
        named /var/adm/sw/patch/PATCH_NOSAVE.

        WARNING: If this file exists when a patch is installed, the
                 patch cannot be deinstalled. Please be careful
                 when using this feature.

        It is recommended that you move the PHSS_22879.text file to
        /var/adm/sw/patch for future reference.

        To put this patch on a magnetic tape and install from the
        tape drive, use the command:

                dd if=/tmp/PHSS_22879.depot of=/dev/rmt/0m bs=2k

Special Installation Instructions:
        BEFORE LOADING THIS PATCH...

            o It provides bug fixes and enhancements for the
              VPO A.06.00 Management Server system.

            o DO NOT use this patch with older releases of ITO,
              for example versions A.05.00, A.05.11 or A.05.30
        (A) Patch Installation Instructions
            -------------------------------

        (A1) Install the patch, following the standard
              installation instructions.

              For backing up the system before installing
              a patch, you may use opc_backup(1m)

        NOTE: MAKE SURE THAT NO AGENT OF THE PLATFORM
              ADDRESSED BY THIS PATCH IS DISTRIBUTED
              (either from the VPO Administrator's GUI
              or from command line using inst.sh) WHILE
              RUNNING SWINSTALL.

              Don't be afraid of the '-x autoreboot=true'
              option above. There won't be a reboot due
              to this VPO patch.
              You can skip this option if you like.

        NOTE: This patch must be installed on the VPO Management
              Server system, NOT on an VPO Managed Node directly.
              Changes will take effect on managed nodes by means of
              VPO Software Distribution (using 'Force Update' if
              there is already an agent installed on the managed
              node). See chapter 2 of the VPO Administrator's
              Reference manual for more information.

        (B) Patch Deinstallation Instructions
            ---------------------------------

        (B1) To deinstall the patch PHSS_22879 run swremove:

              NOTE: MAKE SURE THAT NO AGENT OF THE PLATFORM
                    ADDRESSED BY THIS PATCH IS DISTRIBUTED (either
                    from the ITO Administrator's GUI or from
                    command line using inst.sh) WHILE RUNNING
                    SWREMOVE.

              # swremove PHSS_22879
-----End of Document ID: PHSS_22879------------------------------------------


Document ID: PHNE_22877
Date Loaded: 20010315
      Title: s700_800 10.20 NFS Kernel General Rel & Perf Patch

Patch Name: PHNE_22877

Patch Description: s700_800 10.20 NFS Kernel General Rel & Perf Patch

Creation Date: 01/03/14

Post Date: 01/03/15

Hardware Platforms - OS Releases:
        s700: 10.20
        s800: 10.20

Products: N/A

Filesets:
        OS-Core.CORE-KRN

Automatic Reboot?: Yes

Status: General Release

Critical:
        Yes
        PHNE_22877: PANIC HANG
                Panic due to race condition between mount and
                umount with ufs filesytems.
                Hang encountered because of rfs_readdirplus3()
                memory leak in NFS PV3.
        PHNE_20021: PANIC
                panic in internal test - cachefs with autofs.
        PHNE_16924: PANIC CORRUPTION
                Panic due to buffer cache corruption
        PHNE_16925: PANIC CORRUPTION
                Panic due to buffer cache corruption
        PHNE_15863: PANIC HANG CORRUPTION
                Hang encountered in nfs_fsync()
                Panic with m_free(), sbdrop(), and
                clntkudp_callit()
                Panic with truncated file
                Panic with nfs_purge_caches(), binvalfree(),
                bwrite(), nfs_strategy(), do_bio(), and
                nfswrite() recursion
                Hang encountered with autofs (this applies
                only to systems that have the ACE 2 software
                bundle installed)
                Hang encountered because of rfs_readdirplus3()
                memory leak (this applies only to systems that
                have the ACE 2 software bundle installed)
                Hang encountered with cachefs (this applies
                only to systems that have the ACE 2 software
                bundle installed)
                Panic with rfs3_readlink_free() (this applies
                only to systems that have the ACE 2 software
                bundle installed)
                Corruption encountered with reads (this applies
                only to systems that have the ACE 2 software
                bundle installed)
        PHNE_15864: PANIC HANG CORRUPTION
                Hang encountered in nfs_fsync()
                Panic with m_free(), sbdrop(), and
                clntkudp_callit()
                Panic with truncated file
                Panic with nfs_purge_caches(), binvalfree(),
                bwrite(), nfs_strategy(), do_bio(), and
                nfswrite() recursion
                Hang encountered with autofs (this applies
                only to systems that have the ACE 2 software
                bundle installed)
                Hang encountered because of rfs_readdirplus3()
                memory leak (this applies only to systems that
                have the ACE 2 software bundle installed)
                Hang encountered with cachefs (this applies
                only to systems that have the ACE 2 software
                bundle installed)
                Panic with rfs3_readlink_free() (this applies
                only to systems that have the ACE 2 software
                bundle installed)
                Corruption encountered with reads (this applies
                only to systems that have the ACE 2 software
                bundle installed)
        PHNE_15041: PANIC
                Panic encountered with autofs (this applies
                only to systems that have the ACE 2 software
                bundle installed)
        PHNE_15042: PANIC
                Panic encountered with autofs (this applies
                only to systems that have the ACE 2 software
                bundle installed)
        PHNE_14071: PANIC HANG
                Panic encountered in ku_sendto_mbuf()
                Panic encountered in ckuwakeup()
                Panic encountered in vn_rele()
                Hang encountered in nfs_fsync()
        PHNE_14072: PANIC HANG
                Panic encountered in ku_sendto_mbuf()
                Panic encountered in ckuwakeup()
                Panic encountered in vn_rele()
                Hang encountered in nfs_fsync()
        PHNE_13823: HANG PANIC
                Hang encountered in nfs_fsync()
                Panic encountered in clnt_kudpinit()
        PHNE_13824: HANG PANIC
                Hang encountered in nfs_fsync()
                Panic encountered in clnt_kudpinit()
        PHNE_13668: HANG
                Hang encountered in Instant Ignition
        PHNE_13669: HANG
                Hang encountered in instant ignition
        PHNE_13235: PANIC CORRUPTION
                Panic encountered in nfs_prealloc()
                Corruption encountered with retransmissions
        PHNE_13236: PANIC CORRUPTION
                Panic encountered in nfs_prealloc()
                Corruption encountered with retransmissions
        PHNE_12427: HANG
                Hang encountered with exportfs command
        PHNE_12428: HANG
                Hang encountered with exportfs command
        PHNE_11386: HANG
                Hang encountered in NFS IO
        PHNE_11387: HANG
                Hang encountered in NFS IO
        PHNE_11008: CORRUPTION PANIC
                Overwritten rnode error in do_bio()
                Rename of jfs file system from PCNFS causes panic
                Data page fault in ckuwakeup()
        PHNE_11009: CORRUPTION PANIC
                Overwritten rnode error in do_bio()
                Rename of jfs file system from PCNFS causes panic
                Data page fault in ckuwakeup()
        PHKL_8544: HANG
        PHKL_8545: HANG

Path Name: /hp-ux_patches/s700_800/10.X/PHNE_22877

Symptoms:
        PHNE_22877:
        libnfs.a
           SR:8606138879
           DTS:JAGad08145
           The NFS client was extremely slow during the back-up
           so that the ATM time daemon did not get run and causes
           the ATM switch reset.
        libnfs.a
           SR:1653275800
           DTS:JAGaa24099
           System hang caused by memory leak.
        libnfs.a
           SR:8606135856
           DTS:JAGad04988
           Panic occurs when trying to umount a ufs filesystem
           which is still in the process of mounting.
        libnfs.a
           SR:8606159736
           DTS:JAGad29062
           Unexpected delay in unmounting of Autofs mounts.
        libnfs.a
           SR:8606144704
           DTS:JAGad14044
           NFSv3 does not remove the hardlink of a file if the
           file is busy.

        PHNE_22893:
        {Site Specific Patch}

        PHNE_22117:
        libnfs.a
           SR:8606140818
           DTS:JAGad10180
           Nulls appearing at end of 10.20 NFS V2 client
           files w/ PHNE_21108 patch.

        PHNE_21704:
        1. File System may eventually get full due to
           several debug messages in dmesg and syslog
           when Cachefs is used after installing
           PHNE_21108, PHNE_20957 or PHNE_20313.
           The debug messages are like:
           vmunix: cachefs_getattr: backvp:
           vmunix: cachefs_getattr: vap->va_nodeid:
           JAGad08894 SR:8606139585

        PHNE_21108:
        1. AutoFS incorrectly handles certain indirect
           hierarchical maps
        2. Improved read-ahead algorithm to enhance
           READ performance.
        3. Data corruption occurs in the form of embedded NULL
           characters in files written to simultaneously by
           more than one process.
        4. nfsstat(1M) output does not accurately report
           retransmissions.
        5. ls -s reports incorrect number of blocks for files on
           NFS PV3 server.
        6. The link(1M) command does not return an error on NFS
           PV3 mounted directory when trying to create a new
           linked file and an existing linked file is already
           present.
        7. A system panic occurs when a process writes to a file
           and then immediately tries to perform another file
           operation, such as truncating the file.

        PHNE_20957:
        1. Glance tool fails to start after installing
            PHNE_20313.

        PHNE_20313:
        1. Automounter hangs when trying to mount cachefs
            filesystem.
        2. The timeo option in the mount command does not
            have any effect when set.
        3. Untar-ing a large quantity of files over NFS
            can be slow.
        4. NFS version 3 client is very slow when performing a
            write operation to a Celerra server.
        5. 'maxcnodes' is a constant but should be made a
            configurable variable to improve cachefs performance.
        6. fuser does not work over Cachefs mountpoint.
        7. diff(1) failed on AIX client with HP 10.20 server due
            to name of a regular file passed to pathconf(2) call.
        8. MP_SPINLOCK was not taken in nfs3_do_bio()which could
            have caused a credential related panic.
        9. NFS3ERR_TOOSMALL reported as a last packet when it
            should not be. SUNs solstice PC-NFS-client and
            DEC-clients cannot handle this error message and fail
            while accessing the directory.
        10. mount command fails with kernel data page fault panic
            instead of failing with ETIMEDOUT.
        11. Enhanced NFS version 3 to support the full 32k
            read/write block size.

        PHNE_20021:
        1. Panic found during internal testing in cachefs with
           autofs.

        PHNE_19426:
        1. Client process can hang forever over NFS. This can
           occur when an NFS client generates a high amount of
           write requests, and the NFS server is very busy.
           Once the process is hung it cannot be killed.
        2. Client might see many networking timeouts using NFS
           version 3.
        3. NFS file creation fails with EACCESS when open() is
           called with O_TRUNC|O_EXCL.
        4. mknod of /dev/rroot (c 255 0xffffff) fails over NFS
           mount.
        5. 10.20: implicit UDP bind results in using
           inp_lport==0 in ku_fastsend.
        6. NFS client panic when mounting using smaller than
           1k block size.
        7. Loading executable file or running memory map
           applications over NFS will fail when NFS read/write
           block size is not set to 4k increment.
        8. Autofs not always triggering a re-mount with
           concurrent mounts and umounts, incorrectly gets
           error ENOENT - "No such file or directory"
        9. Autofs hangs even with PHNE_17200 when running
           scripts triggering concurrent mount/umount
        10. Autofs - cp(1) to inactive direct mount fails
            with error EOPNOTSUPP - "Operation not supported"
        11. Autofs - mv command fails in direct mnt with
            error ENOSYS - "Function is not available"

        PHNE_18961:
        1. Some Sun's clients using Automount might fail to mount
           when HPUX's server setting MOUNTD_VER to 2 in
           /etc/rc.config.d/nfsconf
        2. Memory leak in the NFS client system when using NFS
           file locking.

        PHNE_18962:
        1. Some Sun's clients using Automount might fail to mount
           when HPUX's server setting MOUNTD_VER to 2 in
           /etc/rc.config.d/nfsconf
        2. Memory leak in the NFS client system when using NFS
           file locking.

        PHNE_17619:
        NOTE:
        This ONC+/NFS patch has been reconstructed to deliver
        the ONC+/NFS Networking ACE products (NFS PV3, AutoFS,
        and CacheFS). In addition, the older NFS Automounter
        will be delivered, along with configuration scripts
        (in /etc/rc.config.d/nfsconf) necessary to select AutoFS,
        or the Automounter, or neither. Please read the NOTE
        in Special Installation Instructions for more details.

        1. With a umask of 027, a write followed by a sleep
           followed by another write (all over an NFS mount)
           fails with a "Permission denied" error.
        2. Autofs hangs when manual unmounts are used
        3. NFS PV3 only supports up to 8k read/write transfer
           size
        4. NFS PV3 performs poorly when writing small records
           in synchronous mode.
        5. Cannot copy NFS PV3 Large files greater than 2GB from the
           NFS mounted file system to the local file system.
        6. NFS3ERR_JUKEBOX is not handled in 10.20 ACE PV3
        7. System hang/sleep at clntkudp_callit() at outbuf and not
           waking up
        8. NFS file can be removed even when the file is still
           being referenced.
        9. The system may panic with a kernel stack
            overflow.
        10. Root trying to write to an NFS mounted file that
            is not writable by root can reset the file size
            to zero on 10.20 PV3.
        11. 10.20 Client writes NULL characters into file
            even though client application did not generate them.
        12. System panic while doing reading or writing over
            cachefs mount point for a long period of time.

        PHNE_17620:
        NOTE:
        This ONC+/NFS patch has been reconstructed to deliver
        the ONC+/NFS Networking ACE products (NFS PV3, AutoFS,
        and CacheFS). In addition, the older NFS Automounter
        will be delivered, along with configuration scripts
        (in /etc/rc.config.d/nfsconf) necessary to select AutoFS,
        or the Automounter, or neither. Please read the NOTE
        in Special Installation Instructions for more details.

        1. With a umask of 027, a write followed by a sleep
           followed by another write (all over an NFS mount)
           fails with a "Permission denied" error.
        2. Autofs hangs when manual unmounts are used
        3. NFS PV3 only supports up to 8k read/write transfer
           size
        4. NFS PV3 performs poorly when writing small records
           in synchronous mode.
        5. Cannot copy NFS PV3 Large files greater than 2GB from the
           NFS mounted file system to the local file system.
        6. NFS3ERR_JUKEBOX is not handled in 10.20 ACE PV3
        7. System hang/sleep at clntkudp_callit() at outbuf and not
           waking up
        8. NFS file can be removed even when the file is still
           being referenced.
        9. The system may panic with a kernel stack
            overflow.
        10. Root trying to write to an NFS mounted file that
            is not writable by root can reset the file size
            to zero on 10.20 PV3.
        11. 10.20 Client writes NULL characters into file
            even though client application did not generate them.
        12. System panic while doing reading or writing over
            cachefs mount point for a long period of time.

        PHNE_16924:
        The system may panic with a data page fault.

        NOTE: Patch PHNE_16924 installs a patch for the networking
              ACE 2 software bundle (PHNE_13833) only if that bundle
              has been installed on the system. Otherwise, patch
              PHNE_16924 installs a patch for the standard release
              and its patches (represented by PHNE_13823).

        PHNE_16925:
        The system may panic with a data page fault.

        NOTE: Patch PHNE_16925 installs a patch for the networking
              ACE 2 software bundle (PHNE_13834) only if that bundle
              has been installed on the system. Otherwise, patch
              PHNE_16925 installs a patch for the standard release
              and its patches (represented by PHNE_13824).

        PHNE_15863:
        1. Processes may hang when trying to access files
        across NFS.

        2. The system may panic with a data page fault
        when an NFS operation is interrupted on a
        uniprocessor system.

        3. The system may panic with a data page fault
        when reading a file that has been truncated.

        4. The system may panic with a kernel stack
        overflow.

        5. Syslog shows the message:

              vxfs: mesg 016: vx_ilisterr

        6. Quotas are not honored on a diskless client in
        the same way that they are honored on its server
        under certain circumstances.

        7. The setting of NFS file/directory modification and
        access time stamps is inconsistent.

        8. An HP NFS server does not permit NFS file/directory
        time stamps to be set from a non-HP NFS client.

        9. Autofs hangs when remounting hierarchical autofs
        mount points (this applies only to systems that
        have the ACE 2 software bundle installed).

        10. Autofs hangs when running Netscape (this applies
        only to systems that have the ACE 2 software bundle
        installed).

        11. System hangs when using NFS PV3 as a server (this
        applies only to systems that have the ACE 2 software
        bundle installed).

        12. Cachefs hangs (this applies only to systems that
        have the ACE 2 software bundle installed).

        13. When an archive library is in an NFS PV3 mounted
        directory, nm gives the "bad magic" error string after
        listing all symbols (the symbols list is fine). This
        problem does not occur with NFS PV2 (this applies
        only to systems that have the ACE 2 software bundle
        installed).

        14. The system may panic with a data page fault on an
        NFS PV3 server and shows rfs3_readlink_free() in the
        panic stack trace (this applies only to systems that
        have the ACE 2 software bundle installed).

        15. A read() after an lseek() past EOF is successful
        (this applies only to systems that have the ACE 2
        software bundle installed).

        16. A cp over an NFS PV3 mount encounters an error:

               Value too large to be stored in data type

        NFS PV2 does not encounter the error (this applies
        only to systems that have the ACE 2 software bundle
        installed).

        NOTE: Patch PHNE_15863 installs a patch for the networking
              ACE 2 software bundle (PHNE_13833) only if that bundle
              has been installed on the system. Otherwise, patch
              PHNE_15863 installs a patch for the standard release
              and its patches (represented by PHNE_13823).

        PHNE_15864:
        1. Processes may hang when trying to access files
        across NFS.

        2. The system may panic with a data page fault
        when an NFS operation is interrupted on a
        uniprocessor system.

        3. The system may panic with a data page fault
        when reading a file that has been truncated.

        4. The system may panic with a kernel stack
        overflow.

        5. Syslog shows the message:

              vxfs: mesg 016: vx_ilisterr

        6. Quotas are not honored on a diskless client in
        the same way that they are honored on its server
        under certain circumstances.

        7. The setting of NFS file/directory modification and
        access time stamps is inconsistent.

        8. An HP NFS server does not permit NFS file/directory

        9. Autofs hangs when remounting hierarchical autofs
        mount points (this applies only to systems that
        have the ACE 2 software bundle installed).

        10. Autofs hangs when running Netscape (this applies
        only to systems that have the ACE 2 software bundle
        installed).

        11. System hangs when using NFS PV3 as a server (this
        applies only to systems that have the ACE 2 software
        bundle installed).

        12. Cachefs hangs (this applies only to systems that
        have the ACE 2 software bundle installed).

        13. When an archive library is in an NFS PV3 mounted
        directory, nm gives the "bad magic" error string after
        listing all symbols (the symbols list is fine). This
        problem does not occur with NFS PV2 (this applies
        only to systems that have the ACE 2 software bundle
        installed).

        14. The system may panic with a data page fault on an
        NFS PV3 server and shows rfs3_readlink_free() in the
        panic stack trace (this applies only to systems that
        have the ACE 2 software bundle installed).

        15. A read() after an lseek() past EOF is successful
        (this applies only to systems that have the ACE 2
        software bundle installed).

        16. A cp over an NFS PV3 mount encounters an error:

               Value too large to be stored in data type

        NFS PV2 does not encounter the error (this applies
        only to systems that have the ACE 2 software bundle
        installed).

        NOTE: Patch PHNE_15864 installs a patch for the networking
              ACE 2 software bundle (PHNE_13834) only if that bundle
              has been installed on the system. Otherwise, patch
              PHNE_15864 installs a patch for the standard release
              and its patches (represented by PHNE_13824).

        PHNE_15041:
        1. Poor NFS performance over 100BT.

        2. System panics with data page fault (this applies only
        to systems that have the ACE 2 software bundle installed).

        3. Application fails (this applies only to systems that
        have the ACE 2 software bundle installed).

        4. Application fails (this applies only to systems that
        have the ACE 2 software bundle installed).

        NOTE: Patch PHNE_15041 installs a patch for the networking
              ACE 2 software bundle (PHNE_13833) only if that bundle
              has been installed on the system. Otherwise, patch
              PHNE_15041 installs a patch for the standard release
              and its patches (represented by PHNE_13823).

        PHNE_15042:
        1. Poor NFS performance over 100BT.

        2. System panics with data page fault (this applies only
        to systems that have the ACE 2 software bundle installed).

        3. Application fails (this applies only to systems that
        have the ACE 2 software bundle installed).

        4. Application fails (this applies only to systems that
        have the ACE 2 software bundle installed).

        NOTE: Patch PHNE_15042 installs a patch for the networking
              ACE 2 software bundle (PHNE_13834) only if that bundle
              has been installed on the system. Otherwise, patch
              PHNE_15042 installs a patch for the standard release
              and its patches (represented by PHNE_13824).

        PHNE_14071:
        1. The system may panic with a data memory protection fault.

        2. Processes may hang when trying to access files
        across NFS.

        3. The system may panic with a data page fault.

        4. The system may panic with a vn_rele.

        NOTE: Patch PHNE_14071 installs a patch for the networking
              ACE 2 software bundle (PHNE_13833) only if that bundle
              has been installed on the system. Otherwise, patch
              PHNE_14071 installs a patch for the standard release
              and its patches (represented by PHNE_13823).

        PHNE_14072:
        1. The system may panic with a data memory protection fault.

        2. Processes may hang when trying to access files
        across NFS.

        3. The system may panic with a data page fault.

        4. The system may panic with a vn_rele.

        NOTE: Patch PHNE_14072 installs a patch for the networking
              ACE 2 software bundle (PHNE_13834) only if that bundle
              has been installed on the system. Otherwise, patch
              PHNE_14072 installs a patch for the standard release
              and its patches (represented by PHNE_13824).

        PHNE_13833:
        This patch is part of the 10.20 ACE 2 bundle which adds
        networking enhancements to 10.20. New networking features
        supported in ACE 2 include NFS Version 3.0, AutoFS, and
        CacheFS.

        PHNE_13834:
        This patch is part of the 10.20 ACE 2 bundle which adds
        networking enhancements to 10.20. New networking features
        supported in ACE 2 include NFS Version 3.0, AutoFS, and
        CacheFS.

        PHNE_13823:
        1. Processes may hang when trying to access files
        across NFS.

        2. The system may panic with a spinlock deadlock.

        PHNE_13824:
        1. Processes may hang when trying to access files
        across NFS.

        2. The system may panic with a spinlock deadlock.

        PHNE_13668:
        Client IO from root is denied across an NFS mount point,
        causing hang in instant ignition and NFS clients.

        PHNE_13669:
        Client IO from root is denied across an NFS mount point
        causing hang in instant ignition and NFS clients.

        PHNE_13235:
        1. JFS Servers with NFS clients may see poor performance
        when doing large file transfers across NFS

        2. When using swap across an NFS mount, and the mounted
        disk becomes full, the system may panic.

        3. Data corruption may occur when a transmission errors
        on a crowded network force retransmissions.

        PHNE_13236:
        1. JFS Servers with NFS clients may see poor performance
        when doing large file transfers across NFS

        2. When using swap across an NFS mount, and the mounted
        disk becomes full, the system may panic.

        3. Data corruption may occur when a transmission errors
        on a crowded network force retransmissions.

        PHNE_12427:
        The exportfs -u command hangs.

        PHNE_12428:
        The exportfs -u command hangs.

        PHNE_11386:
        Hang when doing IO across an NFS mount

        PHNE_11387:
        Hang when doing IO across an NFS mount

        PHNE_11008:
        1. Some instances of NFS writes (such as cp from
        an NFS client) may complete successfully even when
        errors occur.

        2. Renaming a VxFS file to another VxFS from a PCNFS
        client causes a panic.

        3. Disabling anonymous access is not recognized
        by PCNFS clients, allowing them to run as a
        priviledged user.

        4. Data page faults caused in the client

        5. Directories in an NFS mounted file system are created
        with 000 permissions value.

        PHNE_11009:
        1. Some instances of NFS writes (such as cp from
        an NFS client) may complete successfully even when
        errors occur.

        2. Renaming a VxFS file to another VxFS from a PCNFS
        client causes a panic.

        3. Disabling anonymous access is not recognized
        by PCNFS clients, allowing them to run as a
        priviledged user.

        4. Data page faults caused in the client

        PHNE_9864:
        Directories in an NFS mounted file system are created
        with 000 permissions value.

        PHKL_9155:
        1. Add write-gathering support for NFS servers.

        2. The length of a timeout for an NFS request may become
        extremely long (on the order of minutes).

        PHKL_9156:
        1. Add write-gathering support for NFS servers.

        2. The length of a timeout for an NFS request may become
        extremely long (on the order of minutes).

        PHKL_8544:
        1. Data page fault in an MP environment due to
        synchronization problems with the client's biod's.

        2. A panic within kernel RPC (in svc_getreqset) in an MP
        environment is generated due to another synchronization
        problem.

        3. System hangs caused in large systems.

        PHKL_8545:
        1. Data page fault in an MP environment due to
        synchronization problems with the client's biod's.

        2. A panic within kernel RPC (in svc_getreqset) in an MP
        environment is generated due to another synchronization
        problem.

        3. System hangs caused in large systems.

Defect Description:
        PHNE_22877:
        libnfs.a
        JAGad08145
           From gprof data collected, it showed that the
           dnlc_purge() was not properly used to purge the
           entire dnlc cache. Also the rnode hash table size
           and algorithm was inefficent so that more than
           1000 entries hashed in the same hash bucket.
        Resolution:
           Used the appropriate dnlc_purge_vp per file and
           dnlc_purge_vfs per file system to purge only cache
           entries needed instead of entire cache table.
           Also increased the rnode hash table size and
           algorithm to provide a better distributed hash
           table and algorithm.
        libnfs.a
        JAGaa24099
           Memory leak in rfs_readdirplus3() in NFS PV3.
        Resolution:
           Now the size to be malloc'ed is checked. No memory is
           allocated when the number of entries not already read
           in the directory is 0.
        libnfs.a
        JAGad04988
           Race condition between mount and umount with ufs
           filesystems.
        Resolution:
           Check VFS_MOUNTING flag in make_unmount_list and
           get_hierarchical_mounts.
        libnfs.a
        JAGad29062
           When an unmount request comes in to the automountd,
           it stats each file system to find the entry with
           the matching file system id. The stat command updates
           the reference times of the autonodes, preventing them
           from unmounting when they should.
        Resolution:
           AutoFS now uses an existing macro to make sure that
           the calling process is not automountd before updating
           the reference times of autonodes.
        libnfs.a
        JAGad14044
           Cannot remove a file or a hardlink to that file,
           depending on which is removed first; the first one
           to be removed will succeed and will be renamed, the
           second one to be removed will get an error.
        Resolution:
           Busy file and its hardlink will be removed without an
           error.

        PHNE_22893:
        {Site Specific Patch}

        PHNE_22117:
        libnfs.a
        JAGad10180
           When a file is truncated on the server the
           client never sees the new smaller size. Hence
           the client displays null characters at the end
           of the file.
        Resolution:
           The logic to update the atttribute
           cash is fixed to update the size in all cases
           (if the size on the server is larger or smaller
           than the size on the client).

        PHNE_21704:
        1. Code had some printf messages which filled the
           syslog and dmesg when CacheFs is used.
           JAGad08894 SR:8606139585
        Resolution:
           The printf messages which were causing this have
           been deleted.

        PHNE_21108:
        1. When hierarchical indirect maps are used on 10.20
           these maps fail with a mkdir error from automountd.
           The same maps work on 11.0 systems.
        Resolution:
           Allow indirect maps lookups initiated by the
           daemon to always succeed.
           Affected module: auto_vnops.c
        2. The new read ahead algorithm calculates the number
           of blocks to read ahead, instead of doing two blocks
           read ahead everytime. The max number of blocks to
           read ahead is 4. If the calculated read ahead blocks
           is larger than the nfs read head max, the max is
           applied.
        Resolution:
           Enhancement. The new read ahead algorithm calculates
           the number of blocks to read ahead, instead of doing
           two blocks read ahead everytime. The max number of
           blocks to read ahead is 4. If the calculated read
           ahead blocks is larger than the nfs read head max,
           the max is applied.
           The rw3vp() routine in nfs3/hpnfs_vnops.c and
           rwvp() routine in nfs/nfs_vnops.c have been changed.
        3. When two processes write to the same file, Null
           characters are written to the file. This problem
           does not occur when -noac (no attribute caching)
           is specified at mount time. NFS write code has a
           race condition where the second process zeroes out
           the buffer the first process has written
           to, if the write size is less than nfs block size
           of 8K.
        Resolution:
           A partial fix was put in to check if r_size has increased
           while the process waits for an empty buffer and not zero
           out the buffer is r_size has increased.
           The condition was coded in error to zero out the buffer
           is r_size has increased. Fix the if condition to not zero
           out if r_size is larger than previous value.
           rw3vp() routine in nfs3/hpnfs_vnops.c and rwvp() routine
           in nfs/nfs_vnops.c have been changed.
           The second race condition is in getattr code, where
           r_size is updated with size received from the server,
           when r_size is larger and more accurate. r_size should be
           updated only if r_size is smaller than the server file
           size and client has dirty buffers to flush.
           nfsgetattr3() routine in nfs3/nfs_vnops3.c and
           nfsgetaatr() routine in nfs/nfs_vnops.c have been
           changed.
        4. A NFS client was experiencing many retransmissions of NFS
           packets (viewable in a nettle trace) but nfsstat is not
           incrementing the retrans counter. This was because the
           retrans counter was only being incremented if a packet we
           tried to send on the wire failed due to resource problem.
           But the retrans counter should be incremented regardless
           of why the call failed, if the call failed.
        Resolution:
           Code change. In clntkdup_callit() in rpc/clnt_kudp.c the
           retrans incrementation check was moved out of the
           RPC_SYSTEMERROR if statement.
        5. For each directory argument,the ls command lists the
           contents of the directory. The -s options gives size in
           blocks for each entry. If the ls -s command was run
           on the same directory on the client and the server,
           different block sizes was reported for the files.
           The problem was due to the fact that the MAXBSIZE used
           for the calculation of va_blksize in fattr_to_vattr3()
           in nfs3/nfs_subr3.c was 64K, unlike 11.0 code or Sun code
           where it is 8K.
        Resolution:
           The solution was to include onc+sys/param.h in
           nfs_subr3.c where MAXBSIZE = 8K. Previously only
           h/param.h was included where MAXBSIZE=64K.
        6. The link(2)(1M) does not return an EEXIST on NFS PV3
           mounted directory though there is a linking file. This
           was due to the fact that that in most error cases we were
           branching to out: where the error conditon was reset to
           NFS3_OK. This erased the previous error condition.
        Resolution:
           Code change in rfs_link3(). Setting the status to
           NFS3_OK has been moved out of out:.
        7. Holding a spinlock and calling binvalfree() causes the
           panic.
        Resolution:
           Code change. Release spinlock before calling binvalfree()
           in nfs_setattr3().

        PHNE_20957:
        1. A kernel variable has been changed to support NFS
           32k read/write block size. Glance made reference
           to this variable and it fails to start when it
           can't find this variable even though Glance doesn't
           use this variable for NFS statistics.
        Resolution:
           Reintroduce this variable back to NFS kernel to allow
           glance to start correctly.

        PHNE_20313:
        1. With PHNE_19426, autofs controlling cachefs indirect
           map will hang on mount
        Resolution:
           Improve detection logic to allow automountd
           detection logic to detect mount calling mount
           or unmount calling unmount.
           Change applied to AUTOFS_PROCESS_IS AUTOMOUNTED
           macro in kernel.
        2. The timeo option in the mount command does not have
           any effect when set.
        Resolution:
           A change in the NFS kernel to make use of this
           option passed down by the NFS mount command.
        3. Untar-ing a large quantity of files over NFS can be
           slow. NFS sometimes needs to invalidate it's client
           cache to ensure that it's cache is not stale
           (binvalfree). It is in this path that NFS makes
           some unnecessary calls to binvalfree, which slows
           down the Untar operation.
        Resolution:
           A performance enhancement has been made to the NFS
           kernel to avoid some calls to binvalfree.
        4. NFS version 3 client is very slow when performing
           a write operation to a Celerra server.
           The Celerra server doesn't implement post attribute
           return on error which is part of the NFS version 3
           protocol, but is not a required feature. What is
           required is that a client must handle this scenario
           correctly and this is what out NFS client has failed
           to do.
        Resolution:
           A change in the NFS path has been made to handle the
           scenario where a server does't return post
           attribute on error.
        5. The 'maxcnodes' s a constant(= MAXCNODES ) the value
           of which is 500. Sometimes this is too low a value
           when a dedicated file system is used for Cahefs.
        Resolution:
           The value of 'maxcnodes' variable will now be a
           computed value which defaults to 50% of ninode. One
           can cahnge the value with adb. There is a feature,
           that if the user does not like the changed value,
           you can set maxcnodes=0x7fffffff and on the next
           Cachefs mount the value will be set to 50% of ninode
           again.
        6. The command fuser does not work over a Cachefs mount
           point though fuser -c does. As a result the
           ServiceGuard scripts fail to work because fuser -k
           cannot kill the processes keeping the mount points
           busy. The root cause is that the v_nodeid field in
           the cnode is not set.
        Resolution:
           Set the v_nodeid field in the cnode with the fid
           returned in the attributes. Also one has to set
           the kernel parameter "pi_newmnttype". One can use
           adb to turn on the pi_newmnttype, or this can be
           done by the command onccompat -n.
        7. diff(1) failed due to invalid name length returned by
           NFS pathconf(2) from HP Server on regular files.
           HP's local file system does not support pathconf(2)
           on regular files and when AIX generates pathconf(2)
           call on regular files, server replies with name length
           of zero.
        Resolution:
           When a file argument is passed in to nfs server code:
           rfs_pathconf(),it is now converted to the parent
           directory before calling and passing the value to the
           underlying filesystem pathconf() call.
        8. MP_Spinlock was omitted in nfs3_do_bio() in
           hpnfs_vnops.c. This could have caused a panic when cred
           was decremented.
        Resolution:
           MP_Spinlock was added to nfs3_do_bio().
        9. 10.20 NFS-servers always do send an NFS3ERR_TOOSMALL
           reply as a last packet during an readdirplus-call.
           SUNs solstice PC-NFS-client and DEC-clients cannot
           handle this error message and fail while accessing the
           directory.
        Resolution:
           Code change. Remove nents==0 code from rfs_readdirplus3.
        10. nfs_mount() routine frees mount info pointer and
            then calls nfs_inactive() which references one of
            the fields in mount info structure causing a kernel
            data page fault panic.
        Resolution:
            The order of freeing the pointers looks obvisously
            wrong. The reason kernel does not crash every time
            mount timesout is the following:
            The answer is in kmem_free(), FREE() and how they
            work. After kmem_free() returns the memory we just
            freed ends up on a free list. So referencing it
            does not cause a page fault everytime we go through
            through nfs_inactive3(), after freeing mi.We page fault
            if that memory gets allocated to some other process
            and the data is no longer valid.
        11. Enhanced NFS version 3 to support the full 32k
            read/write block size.
        Resolution:
            Enhanced NFS version 3 to support the full 32k
            read/write block size.

        PHNE_20021:
        1. Internal testing with cachefs controlled by autofs
           will get a 'data page fault' panic in <30min.
        Resolution:
           In autofs, added a concurrency check on node before
           using (vnode_t*)vp->v_vfsmountedhere.

        PHNE_19426:
        1. This turned out to be a server problem where the NFS
           server dropped the client request. This caused the
           client to retry in a infinite loop, which is normal.
           The reason this occurred is because the server
           corrupted the cache data entry.
        Resolution:
           A fix has been made in the NFS server code to prevent
           duplicate cache table corruption.
        2. The timeout table for NFS version 3 wasn't correct.
           This leads to client timing out too quickly.
        Resolution:
           The timeout's table has been fixed in the NFS kernel
           to match Sun's timeout implementation of NFS.
        3. Specifying both O_EXCL and O_TRUNC at file creation
           time caused NFS client to pass 0 file size to the
           server who treats the file as an existing file and
           tries to verify the credential which failed.
        Resolution:
           A fix has been implemented to not allow 0 file size to
           pass to the server so it will not verify the credential
           of a newly created file.
        4. mknod of a character device with -1 minor number will
           cause the NFS client to create a FIFO file.
        Resolution:
           A new error message "Operation not supported" will be
           returned when the user attempts to create a file with
           the properties described above.
        5. Connectivity problem can occur when all dynamic port
           numbers are in use.
        Resolution:
           Return error when no port can be allocated.
        6. The NFS kernel doesn't support block size of less
           than 1k even though the mount commands allows it.
        Resolution:
           The kernel mount routine has been changed to allow
           the use of less than 1k block size.
        7. Loading executable file or running memory map
           applications over NFS will fail when NFS read/write
           block size is not set to 4k increment.
        Resolution:
           A check in the NFS mount code to ensure that the
           buffer page is allocated at 4k increment.
        8. AutoFS is not triggering re-mount === Running
           AutoFS with very short node timeout (e.g.
           "automount -t0") can cause failures to access files
           which are present.
        Resolution:
           Adjust the logic used to detect special requests
           from the "automountd" daemon. Include tests to
           avoid race conditions between autofs_proc and file
           lookups. Set a minimum hold time for autonodes so
           that they are not recycled immediately after being
           created.
        9. AutoFS hangs even with PHNE_17200 ===
           AutoFS with a short node timeout with a script
           using manual umounts in a tight loop can hang autofs
           after 10-15 minutes.
        Resolution:
           Adjust the logic used to detect special requests
           from the "automountd" daemon. Include tests to
           avoid race conditions between autofs_proc and file
           lookups. Set a minimum hold time for autonodes so
           that they are not recycled immediately after being
           created.
        10. cp(1) fails to inactive direct mount ===
            When a command is given to copy a file to the
            top of an unmounted direct mount point, 'cp' fails
            with "Operation not supported".
        Resolution:
           Add a pathconf() handler for direct mounts.
        11. mv command fails in AutoFS direct mnt ==
            When the 'mv' command is used to rename a file
            from the current directory and it is a direct mount
            point, it will fail if the direct mount is not
            already active (mounted), with error ENOSYS.
        Resolution:
            Add direct mount handler to auto_access() and
            auto_rename(). With changes, 'cd' triggers mount.

        PHNE_18961:
        1. Setting MOUNTD_VER to 2 will force HPUX server to
           start rpc.mountd servicing only version 2 of NFS.
           This is a special feature introduced in 10.20 for
           backward compatibility reason. According to NFS
           specification, a client should contact rpc.mountd
           on the server to see which is the highest version
           it supports before attempting to use that version.
           This wasn't the case for some Sun's clients. Sun's
           clients attempt to contact nfsd instead of rpc.mountd
           for service. This is a problem. Since HP's nfsd
           always servicing both versions and rpc.mountd only
           servicing version 2, some Sun's client get confuse.
           HP's client doesn't have this problem because it
           is smart enough to fall back to version 2 if 3 is
           not available.
        Resolution:
           Setting MOUNTD_VER to 2 will now force HPUX server
           to start both rpc.mountd and nfsd servicing only
           version 2 of NFS. This solved the confusion for
           some Sun's clients.
        2. When using NFS file locking/unlocking heavily, the
           kernel RPC on the client system leaks memory in
           chunks of 32 byte.
        Resolution:
           The memory leak is due to not deallocating a spinlock
           structure associated with the RPC client handle when
           the client handle is freed. This has been fixed

        PHNE_18962:
        1. Setting MOUNTD_VER to 2 will force HPUX server to
           start rpc.mountd servicing only version 2 of NFS.
           This is a special feature introduced in 10.20 for
           backward compatibility reason. According to NFS
           specification, a client should contact rpc.mountd
           on the server to see which is the highest version
           it supports before attempting to use that version.
           This wasn't the case for some Sun's clients. Sun's
           clients attempt to contact nfsd instead of rpc.mountd
           for service. This is a problem. Since HP's nfsd
           always servicing both versions and rpc.mountd only
           servicing version 2, some Sun's client get confuse.
           HP's client doesn't have this problem because it
           is smart enough to fall back to version 2 if 3 is
           not available.
        Resolution:
           Setting MOUNTD_VER to 2 will now force HPUX server
           to start both rpc.mountd and nfsd servicing only
           version 2 of NFS. This solved the confusion for
           some Sun's clients.
        2. When using NFS file locking/unlocking heavily, the
           kernel RPC on the client system leaks memory in
           chunks of 32 byte.
        Resolution:
           The memory leak is due to not deallocating a spinlock
           structure associated with the RPC client handle when
           the client handle is freed. This has been fixed

        PHNE_17619:
        1. The problem is that there are conditions in which
           read credentials are not set. That means that any
           reads performed as part of a write operation will
           fail because there are no read credentials available
           for them to pass and all work done on the server is
           as root.
        2. Remount logic causes hangs
        3. Enhanced NFS version 3 to support up to 24k read/
           write block size.
        4. Tunned the code to perform better in small block
           synchronous write.
        5. A NFS PV3 client is unable to copy large files
           greater than 2GB from a NFS mounted file system
           to the local file system.
        6. NFS3ERR_JUKEBOX is not handled in 10.20 ACE PV3 code
        7. Fixed system hang/sleep in clntkudp_callit() at
           outbuf and not waking up. Also added statistcial
           data collection for sleep and wakeup calls.
        8. The code in nfs_remove checks if a file is busy
           and if it has been renamed. If the test is true
           then the file will be removed. This can cause a busy
           file that has not been renamed removed. The 2
           conditions should be checked separately, i.e. first
           check if a file is busy, if it is, then check if it's
           been renamed? Do nothing if it is; otherwise, rename
           it. Only when a file is not busy then it will be
           removed.
        9. the code path to purge the buffer caches of a stale
            file handle who has large amount of delayed write
            data could be too long and causes kernel stack
            overflow.
        10. When a root user can not write to the file, the
            file attributes are changed including the file
            size. The code closing the file does not check
            if the user closing the file has write permission
            before it sets the file attribute using the new
            one thus causing the file size gets reset to zero.
        11. The problem occurs due to avoiding the read of the
            block when multiple processes are appending data
            to the same file block when nfs_no_read_before_write
            is turned on. Due to NFS client avoiding the read
            of the file block and initializing the buffer to
            NULLs,NULLs are written out.
        12. The cachefs read and write path is not releasing
            credential correctly.

        PHNE_17620:
        1. The problem is that there are conditions in which
           read credentials are not set. That means that any
           reads performed as part of a write operation will
           fail because there are no read credentials available
           for them to pass and all work done on the server is
           as root.
        2. Remount logic causes hangs
        3. Enhanced NFS version 3 to support up to 24k read/
           write block size.
        4. Tunned the code to perform better in small block
           synchronous write.
        5. A NFS PV3 client is unable to copy large files
           greater than 2GB from a NFS mounted file system
           to the local file system.
        6. NFS3ERR_JUKEBOX is not handled in 10.20 ACE PV3 code
        7. Fixed system hang/sleep in clntkudp_callit() at
           outbuf and not waking up. Also added statistcial
           data collection for sleep and wakeup calls.
        8. The code in nfs_remove checks if a file is busy
           and if it has been renamed. If the test is true
           then the file will be removed. This can cause a busy
           file that has not been renamed removed. The 2
           conditions should be checked separately, i.e. first
           check if a file is busy, if it is, then check if it's
           been renamed? Do nothing if it is; otherwise, rename
           it. Only when a file is not busy then it will be
           removed.
        9. the code path to purge the buffer caches of a stale
            file handle who has large amount of delayed write
            data could be too long and causes kernel stack
            overflow.
        10. When a root user can not write to the file, the
            file attributes are changed including the file
            size. The code closing the file does not check
            if the user closing the file has write permission
            before it sets the file attribute using the new
            one thus causing the file size gets reset to zero.
        11. The problem occurs due to avoiding the read of the
            block when multiple processes are appending data
            to the same file block when nfs_no_read_before_write
            is turned on. Due to NFS client avoiding the read
            of the file block and initializing the buffer to
            NULLs,NULLs are written out.
        12. The cachefs read and write path is not releasing
            credential correctly.

        PHNE_16924:
        A buffer cache entry is being released more than once
        causing corruption in the buffer cache hash lists.

        NOTE: Patch PHNE_16924 installs a patch for the networking
              ACE 2 software bundle (PHNE_13833) only if that bundle
              has been installed on the system. Otherwise, patch
              PHNE_16924 installs a patch for the standard release
              and its patches (represented by PHNE_13823).

        PHNE_16925:
        A buffer cache entry is being released more than once
        causing corruption in the buffer cache hash lists.

        NOTE: Patch PHNE_16925 installs a patch for the networking
              ACE 2 software bundle (PHNE_13834) only if that bundle
              has been installed on the system. Otherwise, patch
              PHNE_16925 installs a patch for the standard release
              and its patches (represented by PHNE_13824).

        PHNE_15863:
        1. An access of a kernel variable on an NFS client
        was not protected by a spinlock and thus conflicted
        with other accesses of the same variable causing
        the integrity of that variable to be compromised and
        leading to a case where a sleep could not be woken up.

        2. An interrupt performing an operation on a socket
        on which NFS is attempting a socket buffer data
        drop (sbdrop) causes the socket operation to access
        a bad socket buffer address.

        3. A read of a file that was truncated during the
        read operation causes an access of non-existent
        data.

        4. With no biods running, a write of a stale file
        in which the writes are less than 8K bytes in length
        causes a recursive call stack that can get very
        large.

        5. Before reading the entries of a directory, no
        check is performed to determine if the entity being
        read is a directory, which leads to the given syslog
        message.

        6. The file open credentials are used by NFS and
        not the thread credentials. This can lead to a
        quota problem when the user that opened a file
        is not the user accessing the file.

        7. When a utime() operation with a NULL timestamp is
        performed on an NFS file/directory, the NFS client uses
        the system time of the client to set file/directory
        modification and access times with SETATTR operations.
        However, WRITE operations use the system time of the
        server to set file/directory modification and access
        times. This causes inconsistencies when the client and
        server systems are in different time zones.

        8. A SUN NFS client attempting to perform a utime()
        operation with a NULL timestamp on an HP NFS server
        file/directory is rejected due to a permissions error
        even though the process has write permissions but is
        not the file/directory owner.

        9. When hierarchical maps are used, a umount of the
        mount points causes the autofs daemon to hang (this
        applies only to systems that have the ACE 2
        software bundle installed).

        10. Running Netscape from automounter paths causes
        hangs (this applies only to systems that have the
        ACE 2 software bundle installed).

        11. A slow memory leak in rfs_readdirplus3() eventually
        starves the server of free memory (this applies only to
        systems that have the ACE 2 software bundle installed).

        12. The calls from cachefs to do attribute lookups hang
        when trying to make a cachefs node (this applies only to
        systems that have the ACE 2 software bundle installed).

        13. The nm tool is given incorrect file length data and
        reports a standard HPPA error (this applies only to
        systems that have the ACE 2 software bundle installed).

        14. The system panics with data page fault on the NFS PV3
        server when trying to remove a symbolic link (this applies
        only to systems that have the ACE 2 software bundle
        installed).

        15. An application can lseek to EOF and then read past
        EOF without having an error status returned (this applies
        only to systems that have the ACE 2 software bundle
        installed).

        16. The maximum file size field in the NFS PV3 protocol
        has been initialized incorrectly (this applies only to
        systems that have the ACE 2 software bundle installed).

        NOTE: Patch PHNE_15863 installs a patch for the networking
              ACE 2 software bundle (PHNE_13833) only if that bundle
              has been installed on the system. Otherwise, patch
              PHNE_15863 installs a patch for the standard release
              and its patches (represented by PHNE_13823).

        PHNE_15864:
        1. An access of a kernel variable on an NFS client
        was not protected by a spinlock and thus conflicted
        with other accesses of the same variable causing
        the integrity of that variable to be compromised and
        leading to a case where a sleep could not be woken up.

        2. An interrupt performing an operation on a socket
        on which NFS is attempting a socket buffer data
        drop (sbdrop) causes the socket operation to access
        a bad socket buffer address.

        3. A read of a file that was truncated during the
        read operation causes an access of non-existent
        data.

        4. With no biods running, a write of a stale file
        in which the writes are less than 8K bytes in length
        causes a recursive call stack that can get very
        large.

        5. Before reading the entries of a directory, no
        check is performed to determine if the entity being
        read is a directory, which leads to the given syslog
        message.

        6. The file open credentials are used by NFS and
        not the thread credentials. This can lead to a
        quota problem when the user that opened a file
        is not the user accessing the file.

        7. When a utime() operation with a NULL timestamp is
        performed on an NFS file/directory, the NFS client uses
        the system time of the client to set file/directory
        modification and access times with SETATTR operations.
        However, WRITE operations use the system time of the
        server to set file/directory modification and access
        times. This causes inconsistencies when the client and
        server systems are in different time zones.

        8. A SUN NFS client attempting to perform a utime()
        operation with a NULL timestamp on an HP NFS server
        file/directory is rejected due to a permissions error
        even though the process has write permissions but is
        not the file/directory owner.

        9. When hierarchical maps are used, a umount of the
        mount points causes the autofs daemon to hang (this
        applies only to systems that have the ACE 2
        software bundle installed).

        10. Running Netscape from automounter paths causes
        hangs (this applies only to systems that have the
        ACE 2 software bundle installed).

        11. A slow memory leak in rfs_readdirplus3() eventually
        starves the server of free memory (this applies only to
        systems that have the ACE 2 software bundle installed).

        12. The calls from cachefs to do attribute lookups hang
        when trying to make a cachefs node (this applies only to
        systems that have the ACE 2 software bundle installed).

        13. The nm tool is given incorrect file length data and
        reports a standard HPPA error (this applies only to
        systems that have the ACE 2 software bundle installed).

        14. The system panics with data page fault on the NFS PV3
        server when trying to remove a symbolic link (this applies
        only to systems that have the ACE 2 software bundle
        installed).

        15. An application can lseek to EOF and then read past
        EOF without having an error status returned (this applies
        only to systems that have the ACE 2 software bundle
        installed).

        16. The maximum file size field in the NFS PV3 protocol
        has been initialized incorrectly (this applies only to
        systems that have the ACE 2 software bundle installed).

        NOTE: Patch PHNE_15864 installs a patch for the networking
              ACE 2 software bundle (PHNE_13834) only if that bundle
              has been installed on the system. Otherwise, patch
              PHNE_15864 installs a patch for the standard release
              and its patches (represented by PHNE_13824).

        PHNE_15041:
        1. NFS performance over 100BT is poor.

        2. Autofs panics system with data page fault (this
        applies only to systems that have the ACE 2 software
        bundle installed).

        3. Autofs fails to work with 9.X archived directory
        path libraries (this applies only to systems that
        have the ACE 2 software bundle installed).

        4. Autofs causes swlist to fail (this applies only to
        systems that have the ACE 2 software bundle installed).

        NOTE: Patch PHNE_15041 installs a patch for the networking
              ACE 2 software bundle (PHNE_13833) only if that bundle
              has been installed on the system. Otherwise, patch
              PHNE_15041 installs a patch for the standard release
              and its patches (represented by PHNE_13823).

        PHNE_15042:
        1. NFS performance over 100BT is poor.

        2. Autofs panics system with data page fault (this
        applies only to systems that have the ACE 2 software
        bundle installed).

        3. Autofs fails to work with 9.X archived directory
        path libraries (this applies only to systems that
        have the ACE 2 software bundle installed).

        4. Autofs causes swlist to fail (this applies only to
        systems that have the ACE 2 software bundle installed).

        NOTE: Patch PHNE_15042 installs a patch for the networking
              ACE 2 software bundle (PHNE_13834) only if that bundle
              has been installed on the system. Otherwise, patch
              PHNE_15042 installs a patch for the standard release
              and its patches (represented by PHNE_13824).

        PHNE_14071:
        1. An uninitialized kernel variable on an NFS server
        causes an address to be decremented by one and
        thus leaves it not pointing to a word-aligned
        area.

        2. An access of a kernel variable on an NFS client
        was not protected by a spinlock and thus conflicted
        with other accesses of the same variable causing
        the integrity of that variable to be compromised and
        leading to a case where a loop cannot be terminated.

        3. A lack of synchronization within the RPC kernel
        layer causes an access of a kernel variable after
        its memory has already been freed.

        4. The NFS server allows access of a previously
        released vnode when a file lock is unblocked.

        NOTE: Patch PHNE_14071 installs a patch for the networking
              ACE 2 software bundle (PHNE_13833) only if that bundle
              has been installed on the system. Otherwise, patch
              PHNE_14071 installs a patch for the standard release
              and its patches (represented by PHNE_13823).

        PHNE_14072:
        1. An uninitialized kernel variable on an NFS server
        causes an address to be decremented by one and
        thus leaves it not pointing to a word-aligned
        area.

        2. An access of a kernel variable on an NFS client
        was not protected by a spinlock and thus conflicted
        with other accesses of the same variable causing
        the integrity of that variable to be compromised and
        leading to a case where a loop cannot be terminated.

        3. A lack of synchronization within the RPC kernel
        layer causes an access of a kernel variable after
        its memory has already been freed.

        4. The NFS server allows access of a previously
        released vnode when a file lock is unblocked.

        NOTE: Patch PHNE_14072 installs a patch for the networking
              ACE 2 software bundle (PHNE_13834) only if that bundle
              has been installed on the system. Otherwise, patch
              PHNE_14072 installs a patch for the standard release
              and its patches (represented by PHNE_13824).

        PHNE_13833:
        New functionality to support networking features in
        10.20.

        PHNE_13834:
        New functionality to support networking features in
        10.20.

        PHNE_13823:
        1. Processes within the RPC kernel layer are not
        releasing a lock which is needed by other NFS client
        processes to synchronize IO requests (which requires
        a flush of all outstanding client to server IO).

        2. A spinlock is held by a kernel RPC process when
        it tries to acquire a beta semaphore.

        PHNE_13824:
        1. Processes within the RPC kernel layer are not
        releasing a lock which is needed by other NFS client
        processes to synchronize IO requests (which requires
        a flush of all outstanding client to server IO).

        2. A spinlock is held by a kernel RPC process when
        it tries to acquire a beta semaphore.

        PHNE_13668:
        The NFS client prevents root from opening a file on the
        server. It will allow file creation, but not IO to an
        existing file.

        PHNE_13669:
        The NFS client prevents root from opening a file on the
        server. It will allow file creation, but not IO to an
        existing file.

        PHNE_13235:
        1. NFS Clients may send serial IO requests out of order,
        causing performance problems for JFS on the Server.

        2. NFS writes to a full disk used as a swap device will
        return an error which results in a call to panic() from
        nfs_prealloc().

        3. When retransmitting, the XID may not be properly
        reinitialized, allowing data corruption in the form of
        null-valued blocks of 8192 bytes (or less).

        PHNE_13236:
        1. NFS Clients may send serial IO requests out of order,
        causing performance problems for JFS on the Server.

        2. NFS writes to a full disk used as a swap device will
        return an error which results in a call to panic() from
        nfs_prealloc().

        3. When retransmitting, the XID may not be properly
        reinitialized, allowing data corruption in the form of
        null-valued blocks of 8192 bytes (or less).

        PHNE_12427:
        The reference count of the exported entry is not managed
        correctly, and may remain greater than 0 when unused.

        PHNE_12428:
        The reference count of the exported entry is not managed
        correctly, and may remain greater than 0 when unused.

        PHNE_11386:
        Hang in clnt_kudp.o

        PHNE_11387:
        Hang in clnt_kudp.o

        PHNE_11008:
        1. Error codes kept in the rnode for an NFS client's file
        may get overwritten, and therefore not reported back to the
        caller when the file is closed.

        2. The NFS server renaming procedures do not check for
        differing VxFS file systems when asking for a rename,
        which will cause a panic down in VxFS.

        3. The server authorization program does not properly
        check for anonymous access when user IDs of -2 are used.

        4. The netisr callout function did not protect against a
        race condition.
        null-valued blocks of 8192 bytes (or less).

        5. The system does not initialize the vnode attributes when
        it sees a file size which is too large for the 10.20 file
        system, and returns an error. The server is making the
        directory anyway, with uninitialized (000) attributes.

        PHNE_11009:
        1. Error codes kept in the rnode for an NFS client's file
        may get overwritten, and therefore not reported back to the
        caller when the file is closed.

        2. The NFS server renaming procedures do not check for
        differing VxFS file systems when asking for a rename,
        which will cause a panic down in VxFS.

        3. The server authorization program does not properly
        check for anonymous access when user IDs of -2 are used.

        4. The netisr callout function did not protect against a
        race condition.

        PHNE_9864:
        The system does not initialize the vnode attributes when
        it sees a file size which is too large for the 10.20 file
        system, and returns an error. The server is making the
        directory anyway, with uninitialized (000) attributes.

        PHKL_9155:
        1. NFS write performance can be improved by doing gather
        writes at the server. This patch implements the NFS
        portion of gather writes.

        2. The maximum timeout values defined in RPC were very
        long, and neither RPC nor NFS values matched that of SUN.

        PHKL_9156:
        1. NFS write performance can be improved by doing gather
        writes at the server. This patch implements the NFS
        portion of gather writes.

        2. The maximum timeout values defined in RPC were very
        long, and neither RPC nor NFS values matched that of SUN.

        PHKL_8544:
        1. The kernel's biod support code did not sufficently
        protect against MP race conditions.

        2. The RPC processor affinity implementation used by nfsd's
        was not sufficently protected against MP race conditions.

        3. Incorrect usage of the dnlc purge functions.

        PHKL_8545:
        1. The kernel's biod support code did not sufficently
        protect against MP race conditions.

        2. The RPC processor affinity implementation used by nfsd's
        was not sufficently protected against MP race conditions.

        3. Incorrect usage of the dnlc purge functions.

SR:
        5003445601 1653280412 5003433078 5003429753 5003428292
        5003427963 5003425116 5003423590 5003423368 5003423111
        5003419325 5003418962 5003417329 5003417071 5003406660
        5003404616 5003402743 5003402677 5003398826 5003394056
        5003368050 5003352534 5003344226 5003343277 5003340042
        5003330894 5003327338 5003326090 5003324657 5003322370
        5003321513 5003319665 5003319145 5003279927 5003279091
        4701408047 4701400903 4701378117 4701351577 4701341669
        4701314302 4701306837 4701306829 1653275800 1653272385
        1653266577 1653249268 1653197632 1653192294 1653150599
        1653146886 1653146308 1653134924 1653101337 1653281691
        5003456574 1653275974 1653299602 5003456897 1653308254
        5003467373 1653298828 5003458299 1653299826 5003462911
        8606139585 8606140818 8606138879 1653275800 8606135856
        8606159736 8606144704

Patch Files:
        /usr/conf/lib/libnfs.a
        /usr/conf/lib/libhp-ux.a(cachefs.o)
        /usr/conf/lib/libhp-ux.a(nfs.o)
        /usr/conf/lib/libhp-ux.a(nfs_iface.o)
        /usr/conf/lib/onc_debug.o
        /usr/conf/master.d/nfs

what(1) Output:
        /usr/conf/lib/libnfs.a:
                svc_kudp.c $Date: 99/12/07 17:43:14 $ $Revision: 1.7
                        .112.5 $ PATCH_10.20 PHNE_20313 700/800
                svc.c $Date: 98/11/13 13:37:28 $ $Revision: 1.8.112
                        .16 $ PATCH_10.20 PHNE_16924
                kudp_fsend.c $Date: 99/08/13 15:42:23 $ $Revision:
                        1.4.112.3 $ PATCH_10.20 PHNE_19426 700/800
                clnt_kudp.c $Date: 00/02/10 15:30:16 $ $Revision: 1
                        .9.112.30 $ PATCH_10.20 PHNE_20313 700/800
                hpautofs.c $Date: 99/11/18 15:08:46 $ $Revision: 1.
                        1.112.4 $ PATCH_10.20 PHNE_20313 700/800
                auto_subr.c $Date: 00/12/20 15:17:29 $ $Revision: 1
                        .1.112.9 $ PATCH_10.20 PHNE_22877 700/800
                auto_vfsops.c $Date: 00/12/15 15:41:06 $ $Revision:
                         1.1.112.3 $ PATCH_10.20 PHNE_22877 700/800
                auto_vnops.c $Date: 00/12/15 16:15:08 $ $Revision:
                        1.1.112.9 $ PATCH_10.20 PHNE_22877 700/800
                cachefs_vnops.c $Date: 00/06/07 16:10:58 $ $Revisio
                        n: 1.1.112.9 $ PATCH_10.20 PHNE_21704 700/8
                        00
                cachefs_vfsops.c $Date: 99/12/06 13:52:33 $ $Revisi
                        on: 1.1.112.4 $ PATCH_10.20 PHNE _20313 700/
                        800
                cachefs_module.c $Date: 99/12/06 13:49:30 $ $Revisi
                        on: 1.1.112.4 $ PATCH_10.20 PHNE _20313 700/
                        800
                cachefs_cnode.c $Date: 99/12/06 13:44:21 $ $Revisio
                        n: 1.1.112.5 $ PATCH_10.20 PHNE_20313 700/80
                        0
                hpnfs_vnops.c $Date: 00/03/16 19:35:42 $ $Revision:
                         1.1.112.30 $ PATCH_10.20 PHNE_21108 700/800
                nfs_vfsops3.c $Date: 00/01/07 16:41:29 $ $Revision:
                         1.1.112.11 $ PATCH_10.20 PHNE_20313 700/800
                nfs_vnops3.c $Date: 01/02/16 14:02:20 $ $Revision:
                        1.1.112.29 $ PATCH_10.20 PHNE_22877 700/800
                nfs_subr3.c $Date: 01/01/03 12:00:45 $ $Revision: 1
                        .1.112.15 $ PATCH_10.20 PHNE_22877 700/800
                nfs_server3.c $Date: 00/12/20 16:11:00 $ $Revision:
                         1.1.112.11 $ PATCH_10.20 PHNE_22877 700/800
                nfs_export3.c $Date: 00/01/04 13:58:42 $ $Revision:
                         1.1.112.2 $ PATCH_10.20 PHNE_20313 700/800
                klm_lckmgr.c $Revision: 1.5.112.3 $
                klm_kprot.c $Revision: 1.1.112.2 $
                nfs_vfsops.c $Date: 00/01/07 16:45:56 $ $Revision:
                        1.1.112.9 $ PATCH_10.2 0 PHNE_20313 700/800
                nfs_vnops.c $Date: 01/02/16 13:59:27 $ $Revision: 1
                        .3.112.68 $ PATCH_10.20 PHNE_22877 700/800
                nfs_subr.c $Date: 00/12/20 16:02:24 $ $Revision: 1.
                        1.112.33 $ PATCH_10.20 PHNE_22877
                nfs_server.c $Date: 99/08/13 15:41:02 $ $Revision:
                        1.3.112.33 $ PATCH_10.20 PHNE_19426 700/800
                nfs_fcntl.c $Revision: 1.1.112.18 $
        /usr/conf/lib/libhp-ux.a(cachefs.o):
                None
        /usr/conf/lib/libhp-ux.a(nfs.o):
                None
        /usr/conf/lib/onc_debug.o:
                None
        /usr/conf/lib/libhp-ux.a(nfs_iface.o):
                None
        /usr/conf/master.d/nfs:
                $Revision: 1.2.113.3 $

cksum(1) Output:
        3668783361 647654 /usr/conf/lib/libnfs.a
        566132716 191044 /usr/conf/lib/libhp-ux.a(cachefs.o)
        3631930508 166548 /usr/conf/lib/libhp-ux.a(nfs.o)
        3472542863 2012 /usr/conf/lib/libhp-ux.a(nfs_iface.o)
        566132716 191044 /usr/conf/lib/onc_debug.o
        1421096347 4241 /usr/conf/master.d/nfs

Patch Conflicts: None

Patch Dependencies:
        s700: 10.20: PHKL_16750 PHNE_19937 PHNE_22288
        s800: 10.20: PHKL_16751 PHNE_19936 PHNE_22288

Hardware Dependencies: None

Other Dependencies: None

Supersedes:
        PHKL_8545 PHKL_8544 PHKL_9156 PHKL_9155 PHNE_9864 PHNE_11009
        PHNE_11008 PHNE_11387 PHNE_11386 PHNE_12428 PHNE_12427 PHNE_13236
        PHNE_13235 PHNE_13669 PHNE_13668 PHNE_13824 PHNE_13823 PHNE_13834
        PHNE_13833 PHNE_14072 PHNE_14071 PHNE_15042 PHNE_15041 PHNE_15864
        PHNE_15863 PHNE_16925 PHNE_16924 PHNE_17620 PHNE_17619 PHNE_18962
        PHNE_18961 PHNE_19426 PHNE_20021 PHNE_20313 PHNE_20957 PHNE_21108
        PHNE_21704 PHNE_22117 PHNE_22893

Equivalent Patches: None

Patch Package Size: 1250 KBytes

Installation Instructions:
        Please review all instructions and the Hewlett-Packard
        SupportLine User Guide or your Hewlett-Packard support terms
        and conditions for precautions, scope of license,
        restrictions, and, limitation of liability and warranties,
        before installing this patch.
        ------------------------------------------------------------
        1. Back up your system before installing a patch.

        2. Login as root.

        3. Copy the patch to the /tmp directory.

        4. Move to the /tmp directory and unshar the patch:

                cd /tmp
                sh PHNE_22877

        5a. For a standalone system, run swinstall to install the
            patch:

                swinstall -x autoreboot=true -x match_target=true \
                        -s /tmp/PHNE_22877.depot

        By default swinstall will archive the original software in
        /var/adm/sw/patch/PHNE_22877. If you do not wish to retain a
        copy of the original software, you can create an empty file
        named /var/adm/sw/patch/PATCH_NOSAVE.

        WARNING: If this file exists when a patch is installed, the
                 patch cannot be deinstalled. Please be careful
                 when using this feature.

        It is recommended that you move the PHNE_22877.text file to
        /var/adm/sw/patch for future reference.

        To put this patch on a magnetic tape and install from the
        tape drive, use the command:

                dd if=/tmp/PHNE_22877.depot of=/dev/rmt/0m bs=2k

Special Installation Instructions:
        PHNE_17619:
        PHNE_17620:
        After installation of this patch, the NFS configuration
        file will have been modified to control the behavior of
        the system, and, as an ascii file, can be altered by the
        system administrator.

        The environment variable names and values defined by this
        patch (and the resulting system behavior based on those
        values) are as follows:

        For systems not previously running NFS Version 3 either
        via patch installation or by installation of the ACE/HWE
        Networking Bundles (B6378AA or B6379AA), the NFS
        configuration file will now contain

        AUTOFS=0
        MOUNT_VER=2
        MOUNTD_VER=2

        This indicates that only the Automounter may be used (as
        previously set by the AUTOMOUNT variable in this file) and
        that the AutoFS product will not be used. In addition,
        the default client protocol requested at mount time
        will be PV2 (MOUNT_VER=2), and only PV2 will be supported
        by the server (MOUNTD_VER=2).

        For systems currently running NFS Version 3 either via
        patch installation or by installation of the ACE/HWE
        Networking Bundles (B6378AA or B6379AA), the NFS
        configuration file will contain

        AUTOFS=1
        MOUNT_VER=3
        MOUNTD_VER=3

        This indicates that AutoFS will be used, if the previously
        defined AUTOMOUNT variable is set to 1. In addition, the
        default client protocol requested at mount time will be PV3,
        and the default protocol supported for exported file systems
        will be PV3. PV2 will be supported as well in both
        instances.

        NOTE: When using AutoFS (AUTOFS=1) please verify that
        execute ("x") file access is turned OFF for all existing
        map files ("auto_master", "auto.home", etc.). Any map file
        which has execute access set will be interpreted by AutoFS
        as an executable map and not as a regular map file. Execute
        access to the "/etc/auto.home" file can, for example, be
        removed with the chmod command:

         chmod a-x /etc/auto.home

        The system administrator may modify the NFS variables as is
        deemed appropriate, but selecting PV3 or AutoFS should not
        be attempted unless all patches included in the Networking
        Bundle have been installed. These patches have been
        listed in the April 15th DataComm Newsletter, and are also
        listed below (using the latest superceding patches):

        In the s700 ACE Networking Bundle:
        hp-ux_patches/s700_800/10.X/PHCO_16591
        hp-ux_patches/s700_800/10.X/PHCO_18018
        hp-ux_patches/s700_800/10.X/PHCO_14645
        hp-ux_patches/s700_800/10.X/PHCO_15336
        hp-ux_patches/s700_800/10.X/PHCO_18135
        hp-ux_patches/s700_800/10.X/PHCO_15262
        hp-ux_patches/s700_800/10.X/PHCO_15263
        hp-ux_patches/s700_800/10.X/PHCO_15337
        hp-ux_patches/s700_800/10.X/PHCO_16809
        hp-ux_patches/s700_800/10.X/PHCO_15339
        hp-ux_patches/s700_800/10.X/PHCO_15340
        hp-ux_patches/s700_800/10.X/PHCO_15341
        hp-ux_patches/s700_800/10.X/PHCO_16874
        hp-ux_patches/s700_800/10.X/PHCO_15343
        hp-ux_patches/s700_800/10.X/PHCO_15344
        hp-ux_patches/s700_800/10.X/PHCO_17389
        hp-ux_patches/s700_800/10.X/PHCO_10947
        hp-ux_patches/s700_800/10.X/PHCO_17699
        hp-ux_patches/s700/10.X/PHCO_13851
        hp-ux_patches/s700/10.X/PHKL_17573
        hp-ux_patches/s700/10.X/PHKL_8693
        hp-ux_patches/s700/10.X/PHKL_18197
        hp-ux_patches/s700/10.X/PHKL_16750
        hp-ux_patches/s700/10.X/PHKL_15240
        hp-ux_patches/s700/10.X/PHKL_16959
        hp-ux_patches/s700/10.X/PHKL_18439
        hp-ux_patches/s700/10.X/PHKL_17253
        hp-ux_patches/s700/10.X/PHNE_17731
        hp-ux_patches/s700/10.X/PHNE_16924
        hp-ux_patches/s700/10.X/PHNE_16999
        hp-ux_patches/s700_800/10.X/PHNE_17098
        hp-ux_patches/s700_800/10.X/PHNE_15159
        hp-ux_patches/s700_800/10.X/PHNE_16692

        In the s800 HWE Networking Bundle:
        hp-ux_patches/s700_800/10.X/PHCO_16591
        hp-ux_patches/s700_800/10.X/PHCO_17389
        hp-ux_patches/s700_800/10.X/PHCO_18018
        hp-ux_patches/s700_800/10.X/PHCO_14645
        hp-ux_patches/s700_800/10.X/PHCO_15336
        hp-ux_patches/s700_800/10.X/PHCO_18135
        hp-ux_patches/s700_800/10.X/PHCO_15262
        hp-ux_patches/s700_800/10.X/PHCO_15263
        hp-ux_patches/s700_800/10.X/PHCO_15337
        hp-ux_patches/s700_800/10.X/PHCO_15344
        hp-ux_patches/s700_800/10.X/PHCO_16809
        hp-ux_patches/s700_800/10.X/PHCO_15339
        hp-ux_patches/s700_800/10.X/PHCO_15340
        hp-ux_patches/s700_800/10.X/PHCO_15341
        hp-ux_patches/s700_800/10.X/PHCO_16874
        hp-ux_patches/s700_800/10.X/PHCO_15343
        hp-ux_patches/s700_800/10.X/PHCO_17699
        hp-ux_patches/s700_800/10.X/PHCO_10947
        hp-ux_patches/s800/10.X/PHCO_14016
        hp-ux_patches/s800/10.X/PHKL_17574
        hp-ux_patches/s800/10.X/PHKL_8694
        hp-ux_patches/s800/10.X/PHKL_16751
        hp-ux_patches/s800/10.X/PHKL_18198
        hp-ux_patches/s800/10.X/PHKL_15247
        hp-ux_patches/s800/10.X/PHKL_18440
        hp-ux_patches/s800/10.X/PHKL_16957
        hp-ux_patches/s800/10.X/PHKL_17254
        hp-ux_patches/s800/10.X/PHNE_17730
        hp-ux_patches/s800/10.X/PHNE_16925
        hp-ux_patches/s700_800/10.X/PHNE_17098
        hp-ux_patches/s700_800/10.X/PHNE_15159
        hp-ux_patches/s700_800/10.X/PHNE_16692
        hp-ux_patches/s800/10.X/PHNE_18174
                           -------------------

        A performance enhancement which was originally introduced
        in PHNE_15863/4 addressed a problem where an
        NFS client sent READ calls over the wire prior to
        sending WRITESs even in cases where the READ was not
        necessary. Part of the fix for this problem was to
        introduce a new kernel variable called
        "nfs_no_read_before_write"

        By default, the no_read_before_write behavior, which avoids
        redundant read request to an NFS Server when appending
        to a file, is on. To turn it off, the system manager must
        do the following using adb:
        echo "nfs_no_read_before_write/W 0" | \
        adb -k -w /stand/vmunix /dev/mem

        One good reason to turn this flag off is when there
        are multiple processes on a single client writing to the
        same file over an nfs mount point without holding a lock.

        --------------------------------------------------------
        The following is a useful process for applying more than one
        patch while only requiring a single reboot after the final
        patch installation:

         1) Get the individual depots over into /tmp.

         2) Make a new directory to contain the set of patches:
             mkdir /tmp/DEPOT # For example

         3) For each patch "PHKL_xxxx":

            swcopy -s /tmp/PHKL_xxxx.depot \* /tmp/DEPOT

         4) swinstall -x match_target=true -x autoreboot=true \
            -s /tmp/DEPOT
-----End of Document ID: PHNE_22877------------------------------------------


Document ID: PHCO_23455
Date Loaded: 20010315
      Title: s700_800 10.24 (VVOS) cumulative cron/at/crontab patch

Patch Name: PHCO_23455

Patch Description: s700_800 10.24 (VVOS) cumulative cron/at/crontab patch

Creation Date: 01/03/05

Post Date: 01/03/15

Hardware Platforms - OS Releases:
        s700: 10.24
        s800: 10.24

Products: N/A

Filesets:
        OS-Core.CMDS-MIN OS-Core.CMIN-ENG-A-MAN

Automatic Reboot?: No

Status: General Release

Critical: No

Path Name: /hp-ux_patches/s700_800/10.X/PHCO_23455

Symptoms:
        PHCO_23455:
        Port HP-UX patch PHCO_22768 to VVOS.

        Based on HP-UX patch PHCO_22768:
        1.crontab(1) incorrect functionality.

        2.When DST shift is due before the scheduled time, at(1)
          does not schedule the jobs correctly.

        3.at(1) incorrect argument parsing.

        4.cron(1M) does not schedule jobs during daylight saving
          shift.

        5.In trusted mode, crontab(1) does not create correct
          audit record.

        6.at(1) reports "bad date specification" when specifying
          four digits time .

        Based on HP-UX patch PHCO_19985:
        1. at now + [n] months ignores leap year.
        2. crontab(1) -e creates crontab job files
           with incorrect permissions.
        3. at(1) manpage needs to be modified.
        4. Patches for cron(1M) should stop cron and
           start the new cron.
        5. PHCO_17552 does not have libc dependencies specified.
        6. at(1) assumes the given time to be AM if the am_pm
           string in the specified locale is NULL.

        PHCO_17966:
        Ported HP-UX patch PHCO_17552 for VVOS.

        Based on HP-UX patch PHCO_17552:
           at(1) does not accept input of "00" or "0" for year for
           all locales.

        PHCO_17489:
        Ported a portion of HP-UX patch PHCO_16864 for VVOS.

        Based on HP-UX patch PHCO_16864:
        1. On trusted systems, cron(1) has slower performance due
           to calling getspwent() when getspwnam() should have
           been used.
        2. Cron from patch PHCO_15679 does not run at(1) and
           batch(1) jobs.
        3. at(1) schedules jobs incorrectly relative to
           28 Feb of non-leap years.
        4. at(1) does not recognize year 00 (2000). When year
           is input as 00, at(1) exits with the error message -
           "bad date specification"

        Based on HP-UX patch PHCO_15679:
        On trusted systems, /etc/passwd is inherited as stdin
        by processes spawned by cron.

        PHCO_15813:
        Ported HP-UX patch PHCO_15234 for VVOS.

        Based on HP-UX patch PHCO_15234:
        Year diplayed in two digits.

        PHCO_15092:
        Ported HP-UX patch PHCO_14179 for VVOS.

        Based on HP-UX patch PHCO_14179:
        1. at non able to schedule job for Feb 29 2000 correctly.
        2. at creates an invalid file in /var/spool/cron when
        given a non-existant job file with the -f option.'

        Based on HP-UX patch PHCO_10737:
        Cron used to dump core and die when jobs submitted
        with at -m were killed.

        Based on HP-UX patch PHCO_10123:
        The following symotoms correspond to the descriptions
        in the defect descriptions field for PHCO_10123:
        1. option -t now deal with year 2000 input correctly.
        2. year limit has been increased from 2030 to 2037.

        Based on HP-UX patch PHCO_9348:
        1. Cron does not mail stdout and stderr to user on a
        trusted system.
        2. '.' not present in the default PATH
        3. Cron has a hard-coded limit of MAXRUN (40) child
        processes which can be running simultaneously. Now
        the limit has been increased to 100.

        Based on HP-UX patch PHCO_8277:
        at(1) records incorrect audit id on trusted systems

        Based on HP-UX patch PHCO_7836:
        at(1) cannot schedule job using weekdays in the last
        week of the month.

        PHCO_12325:
          at(1) patch does not install cleanly.

        PHCO_11690:
        1)Option -t does not deal with year 2000 input correctly.
        2)The year limit is not set to 2037.

Defect Description:
        PHCO_23455:
        Ported HP-UX patch PHCO_22768 to VVOS.

        Based on HP-UX patch PHCO_22768:
        1. crontab(1) incorrect functionality.
        Resolution:
           Code has been modified to take care of this issue.

        2. When DST shift is due, there will be a non-existing
           time in a day. When jobs are scheduled for such
           non-existing times through commands like -
           at now + <offset> minutes, at fails with message
           "too late".
        Resolution:
           Now the code has been modified to take care of
           jobs scheduled for non-existing times.

        3. at(1) incorrect argument parsing.
        Resolution:
           The code has been modified to take care of this.

        4.cron(1M) executes the job 2 days later than the
          scheduled date, if a shift in daylight happens between
          the current date and the scheduled date.
        Resolution:
           Now the code has been modified to take care of
           jobs scheduled for non-existing times.

        5. In trusted mode, crontab(1) does not create audit
           records because required data is not generated by
           the underlying library call .
        Resolution:
           Appropriate calls to get audit ids are used to
           resolve the problem.

        6.at(1) shows bad date specification when specifying
          four digits time.
        Resolution:
           Now the code has been modified to accept the
           four digits time.

        Based on HP-UX patch PHCO_19985:
        1. Setting the system date such that the day is any day
           after 28th and executing the at(1) command to schedule
           the job for the month of February in a leap year,
           schedules the jobs incorrectly. The following
           shows the incorrect behaviour of at(1).

        $ date 1229084495
        date: do you really want to run time backwards?[yes/no]yes
        Fri Dec 29 08:44:00 EST 1995
        $ at now + 2 month
        warning: commands will be executed using /usr/bin/sh
        job 825687848.a at Fri Mar 1 08:44:08 1996

        at(1) should have scheduled the job for Feb 29.
        Instead it is scheduling the job for Mar 1.

        2. crontab when used with -e creates the job files
           with read permission for all.

        3. The manpage of at(1) needs to be more clear
           regarding the ambiguity of dates.

        4. The cron(1M) patches do not stop the old cron daemon
           and start the new cron daemon. The starting and
           stopping of the daemon does not correctly work in the
           swinstall scripts since the signal mask of the cron
           daemon gets modified through SD scripts.

        5. The cron/at patches should have the libc
           dependencies specified. Without the libc patch
           PHCO_8108 installed, the at(1) command will fail
           with an unresolved symbol error for 'snprintf'.

        6. For certain locales like fr_FR.iso88591, where am_pm
           string is defined as null ("";""), at(1) treats the
           specified time to be AM. The following illustrates
           the problem.

        $ export LANG=fr_FR.iso88591
        $ echo date | at 07:00 demain # OK
        job 879487201.a at Vendredi 14 november 1997 07:00:00
        $ echo date | at 20:00 # OK
        job 879447600.a at Jeudi 13 november 1997 20:00:00
        $ echo date | at 20:00 demain # BUG
        Hours Field Is Invalid

        Resolution:
        1. Checking for the leap year before scheduling the
           job, solves the problem.
        2. The crontab command was relying on a macro for
           permissions on the job file. This macro was incorrect.
           This has been set right now. Now, crontab(1) creates
           job files with read permission only for the owner.
        3. Necessary changes are made to the at(1) manpage to
           solve this problem.
        4. Resetting the signal handlers in cron to their
           respective defaults solves the problem.
        5. Specifying the libc patch, PHCO_8108, in the patch
           dependencies field solves the problem.
        6. Checking for the value of am_pm string for the locale
           solves the problem.

        PHCO_17966:
        Ported HP-UX patch PHCO_17552 to VVOS.

        Based on HP-UX patch PHCO_17552:
           at(1) treats year input of 00 or 0 as incorrect when
           locale is set to one which defines D_T_FMT (date-time)
           string to have year in fields other than the third.
           For eg. japanese locale defines the date string to
           be of format yy/mm/dd. With locale set to japanese,
           an attempt to schedule a job using at(1) for a date
           00/12/20 or 0/12/20 fails.

        Resolution:
           at(1) assumed that the year field can be only in the
           third field of the date string. This assumption has been
           removed. Also, the function which returned error if the
           date string had 0 or 00 in the first or second fields
           has been changed not to check and return error for such
           a condition. Now, at(1) accepts input of 0 or 00 for year
           in any field of the date string, as specified by D_T_FMT
           string for the locale.

        PHCO_17489:
        Ported a portion of HP-UX patch PHCO_16864 for VVOS.

        Based on HP-UX patch PHCO_16864:
        1. On trusted systems, cron(1) called getspwent() which
           performs a linear search in the passwd database, instead
           of getspwnam() which performs a keyed search.

        2. After installing PHCO_15679, jobs submitted from
           at(1) are never actually run, although they are
           removed from the /var/spool/cron/atjobs queue.

        3. Jobs scheduled after 28 Feb are scheduled
           erratically by at(1). The following shows the
           incorrect behaviour of at(1).

           # date 0227112099
           Sat Feb 27 11:20:00 GMT 1999
           # at now + 2 day
           warning: commands will be executed using /usr/bin/sh
           job 920287223.a at Mon Mar 1 11:20:23 1999
           # at now + 3 day
           warning: commands will be executed using /usr/bin/sh
           job 920287243.a at Mon Mar 1 11:20:43 1999

           In the above example, job is scheduled for March 1st
           for both the inputs "now + 2 day" and "now + 3 day".
           For the input "now + 3 day", at(1) should have
           scheduled the job for March 2nd 1999.

           The source code has been changed to fix the defect.

           After the fix, at(1) correctly schedules jobs
           relative to Feb, 28th. In the above example, for
           input "now + 3 day", at(1) schedules the job for
           March 2nd.

        4. at(1) treats year input of 00 as incorrect. Following
           shows how at(1) behaves with 00 as input year.

           # at 12:00 1 Jan 00
           bad date specification

           The command has been changed to accept 00 as year
           2000.

           After the fix, at(1) treats year input of 00 as
           year 2000 and does not show any error messages.

        Based on HP-UX patch PHCO_15679:
        On trusted systems, /etc/passwd is inherited as stdin
        by processes spawned by cron.

        PHCO_15813:
        Ported a portion of HP-UX patch PHCO_15234 for VVOS.

        Based on HP-UX patch PHCO_15234:
        Year displayed in two digits.

        PHCO_15092:
        Ported HP-UX patch PHCO_14179 for VVOS.

        Based on HP-UX patch PHCO_14179:
        1. Job submitted for Feb 29, 2000 was actually scheduled
        for Mar 1, 2000.
        2. At fails to clean up the file created under
        /var/spool/cron when invoked with -f option and

        Based on HP-UX patch PHCO_10737:
        Cron used to dump core and die when jobs submitted
        with at -m were killed.

        Based on HP-UX patch PHCO_10123:
        The following symptoms correspond to the descriptions
        in the defect descriptions field for PHCO_10123:
        1. option -t now deal with year 2000 input correctly.
        2. year limit has been increased from 2030 to 2037.

        Based on HP-UX patch PHCO_9348:
        1. Cron does not mail stdout and stderr to user on a
        trusted system.
        2. '.' not present in the default PATH
        3. Cron has a hard-coded limit of MAXRUN (40) child
        processes which can be running simultaneously. Now
        the limit has been increased to 100.

        Based on HP-UX patch PHCO_8277:
        at(1) records incorrect audit id on trusted systems

        Based on HP-UX patch PHCO_7836:
        at(1) cannot schedule job using weekdays in the last
        week of the month.
        non-existent job file.

        PHCO_12325:
          at(1) patch does not install cleanly. It has incorrect
          group and gid.

        PHCO_11690:
        1)Option -t does not deal with year 2000 input correctly.
        2)The year limit is currently set to 2030. It should be
          set to 2037.

SR:
        8606165710 8606125591 8606157697 8606158467 8606140830
        4701411173 8606106557 1653312975 5003459313 1653293407
        5003451278 5003457150 1653238113 4701416891 1653274167
        5003425777 5003426254 1653269746 1653266239 1653241117
        4701383794 1653215038 4701347153 4701334763 4701328179
        4701393728 4701360701 4701365635 5003409763 1653297424

Patch Files:
        /usr/lib/nls/msg/C/at.cat
        /usr/lib/nls/msg/C/cron.cat
        /usr/lib/nls/msg/C/crontab.cat
        /usr/sbin/cron
        /usr/bin/at
        /usr/bin/crontab
        /usr/share/man/man1.Z/at.1
        /usr/share/man/man1.Z/batch.1

what(1) Output:
        /usr/lib/nls/msg/C/at.cat:
                None
        /usr/lib/nls/msg/C/cron.cat:
                None
        /usr/lib/nls/msg/C/crontab.cat:
                None
        /usr/sbin/cron:
                $Revision: Hewlett-Packard ISSL Level vvos_davis40 $
                         $Header: Hewlett-Packard ISSL Release vvos_
                        davis $ $Date: Mon Mar 12 20:21:32 EST 2001
                        $
                PATCH_10_20 PHCO_10737 $Revision: 78.2.1.35 $
                $Source: cmd/cron/cron.c, hpuxcmdcntl, vvos_davis, d
                        avis178 $ $Date: 01/02/27 08:56:42 $ $Revisi
                        on: 1.17.1.3 PATCH_10.24 (PHCO_23455) $
        /usr/bin/at:
                $Revision: Hewlett-Packard ISSL Level vvos_davis40 $
                         $Header: Hewlett-Packard ISSL Release vvos_
                        davis $ $Date: Mon Mar 12 20:21:32 EST 2001
                        $
                PATCH_10_20 PHCO_10737 $Revision: 78.2.1.35 $
                $Source: cmd/cron/at.c, hpuxcmdcntl, vvos_davis, dav
                        is178 $ $Date: 01/02/27 08:56:35 $ $Revision
                        : 1.19.1.7 PATCH_10.24 (PHCO_23455) $
                $Revision: 76.2.1.11 $
                $Source: cmd/cron/pdate.c, hpuxcmdcntl, vvos_davis,
                        davis178 $ $Date: 01/02/27 08:56:53 $ $Revis
                        ion: 1.9 PATCH_10.24 (PHCO_23455) $
                $Revision: 76.2.1.1.1.7 $
        /usr/bin/crontab:
                $Revision: Hewlett-Packard ISSL Level vvos_davis40 $
                         $Header: Hewlett-Packard ISSL Release vvos_
                        davis $ $Date: Mon Mar 12 20:21:32 EST 2001
                        $
                PATCH_10_20 PHCO_10737 $Revision: 78.2.1.35 $
                $Source: cmd/cron/crontab.c, hpuxcmdcntl, vvos_davis
                        , davis178 $ $Date: 01/03/12 18:08:46 $ $Rev
                        ision: 1.11.1.5 PATCH_10.24 (PHCO_23455) $
        /usr/share/man/man1.Z/at.1:
                None
        /usr/share/man/man1.Z/batch.1:
                None

cksum(1) Output:
        1412985818 3235 /usr/lib/nls/msg/C/at.cat
        1745700039 3275 /usr/lib/nls/msg/C/cron.cat
        3208849937 1095 /usr/lib/nls/msg/C/crontab.cat
        2341860499 53248 /usr/sbin/cron
        950262477 45056 /usr/bin/at
        2075879670 28672 /usr/bin/crontab
        1187665327 11361 /usr/share/man/man1.Z/at.1
        1187665327 11361 /usr/share/man/man1.Z/batch.1

Patch Conflicts: None

Patch Dependencies:
        s700: 10.24: PHCO_18432
        s800: 10.24: PHCO_18432

Hardware Dependencies: None

Other Dependencies: None

Supersedes:
        PHCO_11690 PHCO_12325 PHCO_15092 PHCO_15813 PHCO_17489 PHCO_17966

Equivalent Patches:
        PHCO_23429:
        s700: 11.04
        s800: 11.04

        PHCO_22767:
        s700: 11.00
        s800: 11.00

        PHCO_22768:
        s700: 10.20
        s800: 10.20

Patch Package Size: 210 KBytes

Installation Instructions:
        Please review all instructions and the Hewlett-Packard
        SupportLine User Guide or your Hewlett-Packard support terms
        and conditions for precautions, scope of license,
        restrictions, and, limitation of liability and warranties,
        before installing this patch.
        ------------------------------------------------------------
        1. Back up your system before installing a patch.

        2. Login as root.

        3. Copy the patch to the /tmp directory.

        4. Move to the /tmp directory and unshar the patch:

                cd /tmp
                sh PHCO_23455

        5a. For a standalone system, run swinstall to install the
            patch:

                swinstall -x autoreboot=true -x match_target=true \
                        -s /tmp/PHCO_23455.depot

        By default swinstall will archive the original software in
        /var/adm/sw/patch/PHCO_23455. If you do not wish to retain a
        copy of the original software, you can create an empty file
        named /var/adm/sw/patch/PATCH_NOSAVE.

        WARNING: If this file exists when a patch is installed, the
                 patch cannot be deinstalled. Please be careful
                 when using this feature.

        It is recommended that you move the PHCO_23455.text file to
        /var/adm/sw/patch for future reference.

        To put this patch on a magnetic tape and install from the
        tape drive, use the command:

                dd if=/tmp/PHCO_23455.depot of=/dev/rmt/0m bs=2k

Special Installation Instructions:
        This patch cannot automatically start cron(1M) during
        its installation. Therefore, to get the functionality
        of the new cron(1M) one of the following *MUST* occur:

          - the system must be rebooted during or after the
            installation of the patch

          - cron must be stopped and started manually using
            the commands:

               /sbin/init.d/cron stop
               /sbin/init.d/cron start
-----End of Document ID: PHCO_23455------------------------------------------


Document ID: PHNE_22522
Date Loaded: 20010314
      Title: s700_800 10.20 2.40.0[012] X.25/ACC Accessory (EISA/PCI)

Patch Name: PHNE_22522

Patch Description: s700_800 10.20 2.40.0[012] X.25/ACC Accessory (EISA/PCI)

Creation Date: 01/01/10

Post Date: 01/03/14

Hardware Platforms - OS Releases:
        s700: 10.20
        s800: 10.20

Products:
        Z7436AA_APZ B.02.40.00; Z7436AA_APZ B.02.40.01;
        Z7436AA_APZ B.02.40.02; Z7401A_APZ B.02.40.00;
        Z7401A_APZ B.02.40.01; Z7401A_APZ B.02.40.02

Filesets:
        ACC-X25ST.ACC-X25ST-KRN,B.02.40.00,B.02.40.01,B.02.40.02
        ACC-X25ST.ACC-X25ST-RUN,B.02.40.00,B.02.40.01,B.02.40.02
        X25PAD.X25PAD-RUN,B.10.20.00 X25BSD.X25BSD-KRN,B.10.20.00
        X25CORE.X25CORE-KRN,B.10.20.00 X25IP.X25IP-KRN,B.10.20.00

Automatic Reboot?: Yes

Status: General Release

Critical:
        Yes
        PHNE_22522: PANIC
        PHNE_18719: PANIC

Path Name: /hp-ux_patches/s700_800/10.X/PHNE_22522

Symptoms:
        PHNE_22522:
        SR 8606125245 / CR JAGac40636:
        System panic with spinlock deadlock when extreme
        inbound interrupt traffic occurs.

        SR 8606126154 / CR JAGac56719:
        System panic in sohasoutofbandevent() under heavy
        inbound out-of-band data packets.

        SR 8606127758 / CR JAGac78559:
        Running "x25stat -f" does not report the correct L2
        statistics.

        SR 8606171991 / CR JAGad41254:
        System panic due to spinlock deadlock.

        SR None / CR JAGab73855:
        System panic in asm_spinlock/XSY_F_plp_callback on x25init.

        PHNE_18719:
        X25 init fails with ENOSPC error when x25stop/x25init is
        issued followed by x25stop on a large number of x25 Links
        that have not been initialised.

        JAGab66255:
        X25init fails with with errno=28 when multiple PVC are
        defined for IP usage.

        SR 1653301580 / DTS TPO0h02760
        While padem is run with aprof command, core dump occurs.

        SR 4701427237 / DTS TPO0h02760
        x29printd - Failed to work

        DTS TPO0h02824
        system panics , stack trace shows the sleep was issued on
        ICS

        DTS TPO0h02787
        X25 driver panics on inbound VC RESET or Interrupt data

        DTS TPO0h02802
        When configuring an X.25 link with more VCs than the
        ACC card can support, the error message logged in
        nettl.LOG00 does not indicate clearly what the problem
        is.

        DTS TPO0h02819
        An error message references the location of a file
        for HP-UX 9.0

        DTS TPO0h02808
        IP traffic over PVC does not work sometimes.

        DTS TPO0h02671
        Add nettl L3 tracing for X.25 to the B.02.39/B.02.40
        releases.

        DTS TPO0h02610
        Add Q4 support for the 10.X release.

        DTS TPO0h02243
        The X.25 link is shutdown after the LAP-B SABM
        collision

        DTS TPO0h02244:
        "No available idle ZLUs" error occurred when running
        test on a K220 system.

        DTS TPO0h02248:
        The ISDN L2 and L3 terms were not disabled after the
        link is disconnected.

        DTS TPO0h02448
        x25check fails on some links after x25stop and x25init
        if all the previous cards and their ports are not
        initialised.

        PHNE_15363:
        DTS TPO0h02089
        Write completion length mismatch messages in ZCOM log
        file. The could be other random symptoms being
        generated by the ACC physical driver.

        PHNE_13996:
        SR 1653234476 / DTS TPO0h01652
        Enhancement request for ITU/T 1988 Throughput class support

Defect Description:
        PHNE_22522:
        SR: 8606125245 CR: JAGac40636
        A system panic can occur when there is extreme inbound
        OOB packets arriving. This can occur because the
        inbound axin driver function for handling the inbound
        interrupt packets holds spl5 too long. The inbound
        events are arriving so rapidly that the function always
        has another event to process after it finishes the one
        it is currently working on and this does not allow the
        function to return to netisr.

        Resolution: The fix is to temporarily restore the spl
        level after processing each event and to immediately
        re-aquire spl5. This allows other threads to execute
        and thereby corrects the problem.

        SR: 8606126154 CR: JAGac56719
        A system panic can occur when there is heavy inbound
        OOB packets arriving and the socket is closed. The
        problem was determined to be a race condition between
        the socket close code and the OOB data queuing code.

        Resolution: A check for the socket about to be closed
        has been added to the OOB queuing code which corrects
        the race condition.

        SR: 8606127758 CR: JAGac78559
        There was a change in the format of the control write
        request processing in the firmware for retrieving the
        L2 statistics that is causing the axin driver's request
        to fail. Specifically, the firmware now expects a
        length of four instead of a length of three. This
        resulted in the firmware not sending up the statistics
        value which means there were no values for the axin
        driver to give to x25stat. Please note that ACC cards
        do not maintain the number of transmitted or received
        level 2 RR packets or frames receieved that were too
        long. These three counter values will always be zero.

        Resolution: The axin driver has been updated to use a
        length of four in the control write which corrects the
        problem.

        SR: 8606171991 CR: JAGad41254
        splx() calls were not handled correctly. SPL for the
        processor was not lowered.

        Resolution: splx() calls that were not done properly
        in the code are now done. Without these changes, the
        system could panic with spinlock deadlock message.

        SR: None CR: JAGab73855
        The problem was caused by walking off the end of the
        zx25_pda_infotbl and axin_zlu_tables when the VC ZLU is
        greater than the size of these tables. This corrupted
        random areas of system memory leading to the above
        panic. The drivers walked off the end of the tables
        due to incorrect or missing array bounds checks.

        Resolution: Array bounds checks have been added or
        corrected wherever neccessary and an appropriate error
        message added to instruct the user to increase the size
        of these tables through the documented kernel tunable
        parameter.

        PHNE_18719:
        X25init fails with ENOSPC error.When the X25 (axin) driver
        is opened for an operation that is not for "x25init" the
        l2pda->axin_init field is not initilised correctly and
        thereby fails an assertion in the close path. Due to this
        failure the driver entry in IFPTR table is not freed.
        Eventually this leads to no more free entries and returns
        ENOSPC on x25init/x25close.

        JAGab66255:
        X25init fails with with errno=28 when multiple PVC are
        defined for IP usage.
        This happens due to a bug in x25init that tries to update
        the driver with X25_WR_IPMAPTABLE command for each
        interface on every x25init. Instead it should do
        "X25_WR_IPMAPTABLE" only for the interface that is being
        initialised.

        SR 1653301580 / DTS TPO0h02760
        Old version of this product was shipped

        SR 4701427237 / DTS TPO0h02760
        Old version of this product was shipped

        DTS TPO0h02824
        When Axin driver runs out of free pool of buffers it tries
        to allocate new buffers and waits (sleeps) until they are
        allocated. This is OK if the routine is called in process
        context but when called on ICS it panics.

        DTS TPO0h02787
        The OOB queue is not handled correctly and this lead to
        causing data corruption and Panic.

        DTS TPO0h02802
        The driver has been modified to log an appropriate message
        that clearly states that too many virtual circuits were
        requested.
        DTS TPO0h02819
        An error message logged by the AXIN driver was not updated
        when the product was released for the HP-UX 10.X operating
        system release. This message has been corrected.

        DTS TPO0h02808
        IP traffic over PVC fails with Network down problem
        even when the Link is UP and PVCs are UP.

        DTS TPO0h02671
        There is a commitment to provide X.25 nettl level 3 tracing
        in the ACC B.02.39 and B.02.40 releases.

        DTS TPO0h02610
        There is a commitment to provide Q4 support for the
        ACC B.02.39 and B.02.40 releases.

        DTS TPO0h02243
        This problem was caused by the axin driver did not
        check the link state when the LAP-B SABM collision
        occurred.
        The axin driver was modified to check the link state.
        If the state is not UP, then the axin driver will not
        notify the isdnconfd to shutdown the link.

        DTS TPO0h02244
        This problem was caused by the "RESTART IND" event
        came in before the "VC_ENABLE_REQED" event. The fix
        of this problem is to reorder the processing in
        Axin_Enable_ZLUs to enable the VC ZLUs before the
        link terminal. This would ensure the "VC_ENABLE_REQED"
        event occur before the link is restarted.

        DTS TPO0h02248
        This problem was caused by some of the VCs were not
        properly enabled before the link is shutdown. The
        fix of this problem is to wait for all VCs are
        enabled then disconnecting the link.

        DTS TPO0h02448
        At the x25stop and "zmasterd stop" , when the links
        are marked down, the interface name field in the
        ifptr->x25ifconfig is not reset to NULL.
        This results in getting a wrong ifptr for a given link
        and leads to the above problem.

        PHNE_15363:
        DTS TPO0h02089
        Under extremely high loads, the ACC DAM can sometimes be
        reentered while it is currently executing on the ICS.
        The ACC DAM is not designed to be reentrant (it is MP
        SAFE). The AXIN driver was lowering the interrupt level
        when it should not have been allowing the ACC DAM to be
        reentered. The AXIN driver was modified to maintain a
        high SPL level when executing on the ICS.

        PHNE_13996:
        SR 1653234476 / DTS TPO0h01652
        Configure 64K Throughput Class doesn't get accepted

SR:
        8606125245 8606126154 8606127758 8606171991 1653234476
        1653301580 4701427237

Patch Files:
        /usr/conf/lib/libx25ip.a
        /usr/conf/lib/libx25ipsyms.o
        /usr/conf/lib/libx25pa.a
        /usr/conf/lib/libx25pasyms.o
        /usr/conf/lib/libx25.a
        /usr/conf/lib/libx25syms.o
        /usr/conf/master.d/x25
        /usr/sbin/padem
        /usr/sbin/x29printd
        /usr/conf/lib/libaxinsyms.o
        /usr/conf/master.d/axin
        /usr/conf/lib/libaxin.a
        /opt/acc/bin/zx25init
        /usr/conf/acc/axin.msgs

what(1) Output:
        /usr/conf/lib/libaxin.a:
                ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22522 lib
                        axin.a
        /usr/conf/lib/libaxinsyms.o:
                ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22522 lib
                        axinsyms.o
        /usr/conf/lib/libx25.a:
                ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22522 lib
                        x25.a
        /usr/conf/lib/libx25syms.o:
                ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22522 lib
                        x25syms_pci.o
        /usr/conf/lib/libx25pa.a:
                ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22522 lib
                        x25pa.a
        /usr/conf/lib/libx25pasyms.o:
                ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22522 lib
                        x25pasyms_pci.o
        /usr/conf/lib/libx25ip.a:
                ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22522 lib
                        x25ip.a
        /usr/conf/lib/libx25ipsyms.o:
                ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22522 lib
                        x25ipsyms_pci.o
        /usr/conf/master.d/x25:
                None
        /usr/sbin/padem:
                X.25 PAD Services $Revision: 10.32 $ 28_Jan_99_18:23
        /usr/sbin/x29printd:
                X.25 PAD Services $Revision: 10.32 $ 28_Jan_99_18:23
        /usr/conf/master.d/axin:
                None
        /opt/acc/bin/zx25init:
                ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_18719 zx2
                        5init
        /usr/conf/acc/axin.msgs:
                None

cksum(1) Output:
        2685402132 6003 /usr/conf/master.d/x25
        843732451 118784 /usr/sbin/padem
        2536207429 151552 /usr/sbin/x29printd
        337405979 3379 /usr/conf/master.d/axin
        1116460882 86281 /opt/acc/bin/zx25init
        4078698317 139872 /usr/conf/lib/libaxin.a
        1836188886 264832 /usr/conf/lib/libaxinsyms.o
        799488034 15943 /usr/conf/acc/axin.msgs
        3587118662 182030 /usr/conf/lib/libx25.a
        3115834007 210044 /usr/conf/lib/libx25syms.o
        4022602782 63496 /usr/conf/lib/libx25pa.a
        1010078653 117236 /usr/conf/lib/libx25pasyms.o
        759289468 29096 /usr/conf/lib/libx25ip.a
        1918720563 107572 /usr/conf/lib/libx25ipsyms.o

Patch Conflicts: None

Patch Dependencies:
        s700: 10.20: PHNE_23034
        s800: 10.20: PHNE_23034

Hardware Dependencies: None

Other Dependencies: None

Supersedes:
        PHNE_13996 PHNE_15363 PHNE_18719

Equivalent Patches: None

Patch Package Size: 1540 KBytes

Installation Instructions:
        Please review all instructions and the Hewlett-Packard
        SupportLine User Guide or your Hewlett-Packard support terms
        and conditions for precautions, scope of license,
        restrictions, and, limitation of liability and warranties,
        before installing this patch.
        ------------------------------------------------------------
        1. Back up your system before installing a patch.

        2. Login as root.

        3. Copy the patch to the /tmp directory.

        4. Move to the /tmp directory and unshar the patch:

                cd /tmp
                sh PHNE_22522

        5a. For a standalone system, run swinstall to install the
            patch:

                swinstall -x autoreboot=true -x match_target=true \
                        -s /tmp/PHNE_22522.depot

        By default swinstall will archive the original software in
        /var/adm/sw/patch/PHNE_22522. If you do not wish to retain a
        copy of the original software, you can create an empty file
        named /var/adm/sw/patch/PATCH_NOSAVE.

        WARNING: If this file exists when a patch is installed, the
                 patch cannot be deinstalled. Please be careful
                 when using this feature.

        It is recommended that you move the PHNE_22522.text file to
        /var/adm/sw/patch for future reference.

        To put this patch on a magnetic tape and install from the
        tape drive, use the command:

                dd if=/tmp/PHNE_22522.depot of=/dev/rmt/0m bs=2k

Special Installation Instructions:
        None.
-----End of Document ID: PHNE_22522------------------------------------------


Document ID: PHSS_23342
Date Loaded: 20010312
      Title: s700_800 10.X OpenMail B.06.00 March 01 Periodic Patch

Patch Name: PHSS_23342

Patch Description: s700_800 10.X OpenMail B.06.00 March 01 Periodic Patch

Creation Date: 01/02/24

Post Date: 01/03/12

Hardware Platforms - OS Releases:
        s700: 10.20 10.24 10.30
        s800: 10.20 10.24 10.30

Products:
        OpenMail B.06.00

Filesets:
        OpenMail.OM-ADM,B.06.00 OpenMail.OM-AMECAT,B.06.00
        OpenMail.OM-AMEICE,B.06.00 OpenMail.OM-APPL,B.06.00
        OpenMail.OM-BB,B.06.00 OpenMail.OM-CCMOB,B.06.00
        OpenMail.OM-CHSCAT,B.06.00 OpenMail.OM-CHSICE,B.06.00
        OpenMail.OM-CHSPSS,B.06.00 OpenMail.OM-CORE,B.06.00
        OpenMail.OM-DESK,B.06.00 OpenMail.OM-DSYNC,B.06.00
        OpenMail.OM-ENGCAT,B.06.00 OpenMail.OM-ENGICE,B.06.00
        OpenMail.OM-FINCAT,B.06.00 OpenMail.OM-FINICE,B.06.00
        OpenMail.OM-FRECAT,B.06.00 OpenMail.OM-FREICE,B.06.00
        OpenMail.OM-GERCAT,B.06.00 OpenMail.OM-GERICE,B.06.00
        OpenMail.OM-IMAP4,B.06.00 OpenMail.OM-ITACAT,B.06.00
        OpenMail.OM-ITAICE,B.06.00 OpenMail.OM-KORCAT,B.06.00
        OpenMail.OM-KORICE,B.06.00 OpenMail.OM-KORPSS,B.06.00
        OpenMail.OM-LC,B.06.00 OpenMail.OM-LDAP,B.06.00
        OpenMail.OM-MAN,B.06.00 OpenMail.OM-NIPCAT,B.06.00
        OpenMail.OM-NIPICE,B.06.00 OpenMail.OM-NIPPSS,B.06.00
        OpenMail.OM-NIPWEB,B.06.00 OpenMail.OM-NOTES,B.06.00
        OpenMail.OM-PMOVER,B.06.00 OpenMail.OM-POP3,B.06.00
        OpenMail.OM-PTBCAT,B.06.00 OpenMail.OM-PTBICE,B.06.00
        OpenMail.OM-RC,B.06.00 OpenMail.OM-SMS,B.06.00
        OpenMail.OM-SPACAT,B.06.00 OpenMail.OM-SPAICE,B.06.00
        OpenMail.OM-SWECAT,B.06.00 OpenMail.OM-SWEICE,B.06.00
        OpenMail.OM-UNIX,B.06.00 OpenMail.OM-X400,B.06.00

Automatic Reboot?: No

Status: General Release

Critical: No

Path Name: /hp-ux_patches/s700_800/10.X/PHSS_23342

Symptoms:
        PHSS_23342:
        CR: JAGab33574 SR: 1653231704
        OpenMail for Solaris's service router will abort if a
        distribution list contains a blank name in it.

        The following error is logged and can be seen using
        omshowlog :

        SERIOUS ERROR Service Router(Service Router)
        09.04.97 [OM 10250] Process about to terminate due to
        error. Signal (Segmentation Violation) trapped by process
        4613; code = 0. Procedure trace follows:
          < - da_GetAttribDefn
          -> nm_GetFieldMemPtr
          < - nm_GetFieldMemPtr
          -> da_GetAttribDefn
          -> da_GetMemAttribDefn
          < - da_GetAttribDefn
          -> nm_GetFieldMemPtr
          < - nm_GetFieldMemPtr
          -> da_GetAttribDefn

        CR: JAGab39939 SR: 8606100957
        Omfmtent -u creates output that is corrupted. This occures
        when an attribute name is specified and the attribute value
        is not. The format of the output is incorrect because it
        lists the attribute name but assigns no value to it making
        the output unusable in scripts.

        ie:

        Input to omfmtent :
        s=kessler/i=c/g=richard/q=/ou1=hdqt

        Output of omfmtent :
        1=kessler/3=c/2=richard/4/5=hdqt

        As you can see by the above example, the output from the
        omfmtent command is missing an "=" after the 4.

        CR: JAGab68963 SR: 8606102906
        The new feature of REPEAT REMINDERS in the B.06.00 version
        does not stop sending out reminders after the Expiry date.

        CR: JAGad24268 SR: 8606154951
        omupdtis and associated commands sometimes report illegal
        message store container references e.g.
        ~/sys/1000035/0000001:3

        CR: JAGad31664 SR: 8606162348
        Can't reply in OMGUI and ccMail to messages from internet
        whose address has comments.

        CR: JAGad35090 SR: 8606165799
        If 2 OpenMail users have the same name (but different
        mailnodes) Single User Restore sometimes selects the wrong
        message store to be restored.

        CR: JAGad41463 SR: 8606172203
        The Application Link Layer component does not pass all the
        basic acceptance tests on Solaris.

        CR: JAGad41471 SR: 8606172211
        The UAL sometimes aborts on Redhat 7.0 systems when using
        the directory relay service, with the following in the
        OpenMail log:

        SERIOUS ERROR Remote Client (U/I Access) 11.30.00 07:47:57
        [OM 10250] Process about to terminate due to error.
        Signal (Segmentation Violation) trapped by process 28277;
        code = 0. Procedure trace follows:
          -> pc_recv_logical_block
          <- pc_recv_logical_block
          <- pc_recvmessage
          -> ual_SendMessage
          <- ual_SendMessage
          -> ual_RecvReply
          -> ual_GetFreeBusyTime
          -> ual_ConvORNCheck
          -> ual_ConvertORN
          -> ual_GetUserCharSet
          <- ual_GetUserCharSet
          <- ual_ConvertORN
          <- ual_ConvORNCheck
          -> ual_GetUsersHost
          -> nm_ParseORN
          <- nm_ParseORN
        User Name: UAL TestUser2 / Test, UAL
        Pid of logging process: 28277

        CR: JAGad41637 SR: 8606172377
        Wrong user config file being used when accessing a delegate
        mailbox.

        CR: JAGad42631 SR: 8606173373
        Openmail GR6 experiencing OM 1209 whenever omscan is run.
        omscan logs errors in the log file which are nothing to
        worry about and are normal behaviour. These errors should
        be correctly trapped to avoid worrying administrators that
        they may be a problem

        CR: JAGad43052 SR: 8606173797
        When a message with accented characters in the subject is
        copied across message stores using Netscape messenger, the
        subject of the message has the MIME character set specifier
        in it when viewed using omcontain, OMGUI, Outlook. The
        subject appears OK when using Netscape Messenger.

        CR: JAGad43053 SR: 8606173798
        When a message is copied from one message store to another
        using Netscape Message, and an accented character exists in
        it's content, then the message content file is corrupted.
        However, the content of the message remains OK in the IMAP
        index file. This means that the content can be viewed using
        Netscape Message, but not when using OMGUI or Outlook.

        CR: JAGad44810 SR: 8606175570
        If a user has an address attribute with a backslash in,
        then when the user's address is validated (checked) the
        address attributes are displayed within the freeform field
        (to:). If a backslash is present it prevents the message
        being sent and displays the message "the user name is not
        routable"

        CR: JAGad45449 SR: 8606176209
        Outlook OFS: Item created offline and synced, and then
        modified offline but synced online causes a duplicate to be
        created.

        CR: JAGad45880 SR: 8606176642
        The IMAP/item.browse aborts with a segmentation violation
        on LINUX, when trying to encode an html attachment into
        "Quoted-Printable" format.

        CR: JAGad46896 SR: 8606177664
        The OpenMail Internet gateway rejects multipart/signed
        messages if one of its composite, multipart or message,
        part's boundary-end markers is missing.

        CR: JAGad48103 SR: 8606178878
        If omprepsur is not able to salvage certain files, omdosur
        is supposed to substitute some dummy containers instead and
        then continue to create a valid omcpoutu archive. Infact,
        omdosur was aborting straight after processing the missing
        container and so was creating a corrupt omcpoutu archive.

        CR: JAGad49581 SR: 8606180360
        The original fix for JAGac29290 was missing two files:
        i4target_ux10 and i4target_ux11. They should be included.
        JAGac29290 added the ability to run OpenMail on systems
        where the LSSERV component was not installed.

        PHSS_23081:
        CR: JAGad41842 SR: 8606172582
        Outlook OFS: The UAL_GETSYNC extracts T.61 text content
        files without performing any character set conversion on
        them.

        This affects Czech text that is synchronized and will also
        affect Japanese, Korean and Chinese text.

        CR: JAGad42033 SR: 8606172773
        Itemed moved from Inbox whilst offline gets sync'ed twice:
        Once when the MOVE is synced, and then again when the
        folder is next synced.

        CR: JAGad42115 SR: 8606172855
        When 2 Outlook clients are connected to the same user
        mailbox (eg. delegate and principal) there are occasions
        when Calendar data is changed offline and the appointment
        date emboldening is not updated for the online user after a
        sync.

        CR: JAGad42645 SR: 8606173387
        They are occasions when the synchronization a folder
        (typically the Inbox) will not pick up all of the newly
        added messages.

        This is most likely to occur on Inboxes with more than 32
        items that have had items added and deleted since the last
        synchronization. The items not sync'ed to the local Inbox
        will be in a block starting with one delivered immediately
        after the last sync.

        CR: JAGad42878 SR: 8606173621
        Message that is deleted completely on the server and
        modified offline causes a sync. error when the folder is
        next synced.

        CR: JAGad44420 SR: 8606175176
        Using Outlook OFS can cause spurious WARNINGs to be
        reported in the OpenMail error log. Happens most frequently
        when mailing messages that get saved to the Drafts folder
        during message construction.

        The warnings of the following type:

        WARNING Remote Client (U/I Access )
        01.04.01 11:11:35 [OM.UI 578] The Direct Reference supplied
        is invalid User Name: JONATHAN GEORGE / HP-Pinewood, om1
        -> ual_MatchSyncLogEntry
        <- ual_MatchSyncLogEntry
        -> ct_ofs_read
        <- ct_ofs_read
        -> ual_MatchSyncLogEntry
        <- ual_MatchSyncLogEntry
        -> ual_MatchSyncLogEntry
        <- ual_MatchSyncLogEntry
        -> ual_ListChangeLogAdd
        -> ual_ResolveDirectRef
        -> ct_FindDITEntryByRef
        -> ct_DecodeDirectRef
        <- ct_DecodeDirectRef
        -> ct_FindDITEntry
        <- ct_FindDITEntry
        <- ct_FindDITEntryByRef

        PHSS_22929:
        CR: JAGad38822 SR: 8606169547
        The Content Disposition and Content ID fields of a message
        become corrupt when replying/forwarding using the Ccmail 6
        client.

        PHSS_22995:
        CR: JAGad29260 SR: 8606159934
        If a message coming in through the unix gateway, destined
        for a Notes user, contains an empty From address in the
        header section (HFrom: <>), omrouter non-delivers this
        message and the following error messages are logged:

        08/29/2000 12:39:11 PM OMRTR-GW1210: Failed to add entry
        to text list.Entry : *NumCCRecips*Bad*
        08/29/2000 12:39:11 PM OMRTR-GW2190: Sending Non-Delivery
        Notification to ...
        08/29/2000 12:39:11 PM OMRTR-GW2191: Successfully sent
        Non-Delivery

        PHSS_22990:
        CR: JAGad42968 SR: 8606173711
        It is possible using Outlook with a MAPI connection to
        OpenMail to send a message with an internet address
        containing 8-bit characters in the domain name.

        The outgoing Internet Gateway discards these domain names,
        causing an attempt to be made to deliver the message to a
        recipient with the same address but no domain name.

        This is not correct: if an address is invalid, message
        delivery should not be attempted to a partial address in
        this manner, as there are potential privacy issues.

        PHSS_22699:
        CR: JAGad21983 SR: 8606152653
        The UXO_CHECK_TYPES_OF_DDA general.cfg configuration option
        can be used to specify synonyms for the RFC-822 domain
        defined attrubute type (DDT1).
        However, for addresses which are NOT routed through the
        internet gateway, those using DDT1=RFC-822 are treated
        differently to those which use DDT1=<synonym for RFC-822>

        For instance, assuming :
        There is a route for "unix" through the internet gateway.
        There is a route for "if" through the SendMail interface.
        general.cfg contains these settings :
        UXI_NAME_MAPPING=TRUE
        UXO_NAME_MAPPING=TRUE
        BRW_NAME_MAPPING=TRUE
        UXO_CHECK_TYPES_OF_DDA=a,RFC-822,HPMEXT1,HPMEXT2,HPMEXT3,HP
        EXT4

        Then, the addresses are :