|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: IT Resource Center (support_feedback_at_us-support2-mail.external.hp.com)
Date: Sun Nov 10 2002 - 11:52:35 CST
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:
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:
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 700 10.X patch digest
Created: Sun Nov 10 6:05:18 EST 2002
Table of Contents:
Document ID Title
--------------- -----------
PHSS_27591 s700_800 10.X OV OB3.50 patch - SSEA packet
PHSS_27966 s700_800 10.20 OV WBSSPIa.02.00.00 Multi-problem
PHSS_27468 s700_800 10.20 LIBCL cumulative patch
PHCO_27803 s700_800 10.20 ksh(1) cumulative patch
The documents are listed below.
-------------------------------------------------------------------------------
Document ID: PHSS_27591
Date Loaded: 20021108
Title: s700_800 10.X OV OB3.50 patch - SSEA packet
Patch Name: PHSS_27591
Patch Description: s700_800 10.X OV OB3.50 patch - SSEA packet
Creation Date: 02/11/07
Post Date: 02/11/08
Hardware Platforms - OS Releases:
s700: 10.00 10.01 10.10 10.20
s800: 10.00 10.01 10.10 10.20
Products:
OmniBackII A.03.50
Filesets:
OMNIBACK-II.OMNI-SSEA-P,A.03.50
Automatic Reboot?: No
Status: General Release
Critical: No
Path Name: /hp-ux_patches/s700_800/10.X/PHSS_27591
Symptoms:
PHSS_27591:
Id = HSLco32398 SR:H555007043
When there is a firewall between the application and
the backup host, the split mirror backup fails.
Id = HSLco32470 SR:H555007071
Resolving performance is poor.
Id = HSLco33214 SR:H555007361
SSEA backup fails with:
"[Major] From: SSEA
<hostname> "" Time: <time>
[224:106] Resolving of object <object_path> has
failed. (Search for backup logical volume failed.)"
Id = HSLco35074 SR:H555008259
SSEA backup fails with:
"[Critical] From: SSEA<hostname> "" Time:<time>
Failed to get pair for LDEV <ldev#> in RAID <seq#>.
(Details unknown.)"
Id = HSLco36105 SR:H555008599
SSEA backup fails with:
"[Critical] From: SSEA<host> <mailto:SSEA<host>
"" Time:<time>
Command "/usr/bin/pairdisplay -g" failed with exit
code 242."
Id = HSLco36476 SR:H555008656
SSEA backup fails with:
"[Major] From: SSEA<hostname> "" Time:<time>
[224:106] Resolving of object <object_name> has
failed. (Search for backup logical volume failed.)"
Id = HSLco36975 SR:H555008750
The SSEA SMB session on the backup host abnormally ends
when trying to activate backup volume group after the
paired LDEVs have been split.
PHSS_26215:
Id = HSLco32218 SR: H555006986
Horc instance number is not configurable.
Id = HSLco32253 SR: H555006993
SSEA agent reports disks in SIMPLEX state although
they are in PAIR state in HORCM.
Id = HSLco32264 SR: H555006994
OmniBack II SSEA Integration does not work with
logical devices with XP LUN number greater than 128.
Id = HSLco32274 SR: H555006996
Performance of SSEA integration drastically decreases
after the installation of PHSS_25817/PHSS_25818.
PHSS_25817:
Id = JAGad48627 SR:8606179403
If preexec script fails OmniBack II by default just
aborts the agent and exits. It does not run post-exec
script or clean up.
Id = NSMex04226
Restore fails with:
"[Major] From: SYMA<hostname> "" Time: <time>
[223:325] Could not activate volume group
/dev/sg_sap.
[Major] From: SYMA<hostname> "" Time: <time>
[223:363] Could not prepare mirror disks of object
/sg_sap for backup.
(Activation of volume group failed.)".
Id = HSLco30300 SR:H555006603
Split mirror backup fails with:
"[Critical] From: SSEA<host> "" Time: <time>
Command "/etc/horcmgr" failed with exit code 3.
For details please check log directories:
Log file directory in operation:
/var/opt/omni/log/yyyy-mm-dd-xx/curlogxx
Log file directory for automatic storing:
/var/opt/omni/log/yyyy-mm-dd-xx/tmpxx".
Id = HSLco31032 SR:H555006753
Split mirror backup session fails with:
"[Critical] From: SSEA<host> "" Time: <time>
Failed to find T-VOL/R-Vol of LDEVs.
[SseMapLdevToRdsk] Unable to found /dev/rdsks
file for LDEV = <number>".
Id = HSLco31434 SR:H555006835
Unexpected close reading message from the agent on the
Backup System (SSEA abnormally ends on R2).
Id = HSLco30701 SR:H555006685
Resolving fails on the Application host. The spt inq
structure returns corrupted results.
Id = HSLco31490 SR:H555006844
SSEA integration backup fails with:
"[Critical] From: SSEA<host_name> "" Time: <time>
Command "/etc/horcmgr" failed with exit code 3.
[Critical] From: SSEA<host_name> "" Time: <time>
Failed to start RAID Manager instance.
(Command /etc/horcmgr failed.)".
PHSS_24425:
Id = NSMex04086
Session status is "Completed/Failures" although there
is no any indication of errors.
Id = NSMex04209
SSEA Integration backup fails with an error:
"[Critical] From: SSEA<hostname> "" Time: <time>
Failed to find <volume/volume No.> of LDEVs.".
Id = NSMex04216
SSEA Integration backup reports the following warning:
"[Warning] Cascading structure of BC pairs found
(THIS IS UNSUPPORTED).".
Id = NSMex04392
SSEA Integration backup fails with an error:
"Filesystem <path> could not be mounted.".
Id = NSMex04267
SSEA Integration backup fails with an error:
"[61:1005] Got unexpected close from Split Mirror
Agent.".
Id = HSLco23886
LVM Mirror (XP Campus Cluster) is not supported
within OmniBack II SSEA Integration.
PHSS_22436:
Id = NSMex03360
SSEA Integration split does not appear to mount some
filesystems.
Id = NSMex03700
Disk resolving failed on Backup Host.
Id = NSMex03717
a) SSEA integration backup fails with an error:
"[Major] From: SSEA<hostname> "" Time: <time>
[224:106] Resolving of object "filename" has failed.
(Cannot find block device path name of a logical
volume)"
b) SSEA Integration backup fails with an error:
"[Major] From: SSEA<hostname> "" Time: <time>
File system <filesystem> could
not be mounted to . (Invalid filesystem type.)"
Id = NSMex03482
Disk synchronization messages are incorrect.
Id = HSLco22201
OmniBack II SSEA integration is not supported on Sun
Solaris operating system.
Id = NSMex03651
Disk synchronization fails with:
"[Critical] From: SSEA<hostname> "" Time: <time>
[225:110] Mapping from LDEV to character device
file or disk failed for LDEV <dev> on
array <array>. (Unable to find character device
file for SureStoreE XP256 disk (LDEV))."
Id = NSMex03673
Backup fails with the following message:
"[Critical] From: SSEA<hostname> "" Time: <time>
Command "/usr/bin/pairdisplay -g" failed with
exit code 242.".
Id = NSMbb39679
OmniBack II aborts Business Copy split mirror
backup because one of the disks in a pair is in
status COPY.
Id = NSMex03547
SSEA Agent intermittently fails to resolve objects.
Id = NSMex03739
Pre- and post-exec scripts return invalid exit status.
Id = NSMex03913
SSEA backup fails with the following message:
"[Critical] From: SSEA<hostname> "" Time: <time>
Command "/usr/bin/pairdisplay -g" failed with
exit code 221.".
Id = NSMex03960
SSEA backup fails with the following error:
"Failed to start RAID Manager instance.
(Unable to find SureStoreE XP256 COMMAND device
file.)".
Id = NSMex03850
Sometimes volumes cannot be mounted on JFS 3.3
filesystem.
Id = NSMex03749
Mount function does not restore mount options.
Id = NSMex03563
Mounting of a filesystem fails.
Id = NSMex03931
OmniBack II SSEA Integration does not work on XP 512
for LDEVs with XP LUN addresses above 128.
Defect Description:
PHSS_27591:
Id = HSLco32398
OmniBack II selects by random the port to use and than
checks if it is free. When there is a firewall between
the application and the backup host, not all the ports
can be used, but just those in a specified range.
Resolution:
Two environment variables are added to set the port
range in .omnirc file that can be used by OmniBack II:
SSEA_RM_PORT_LOW
SSEA_RM_PORT_HIGH
Id = HSLco32470
In the resolving phase SSEA executes two ioscan
commands in the SseXIoScanRdsk and ScsiIquiry
functions. Since these two functions are called
several times the resolving performance decreases,
especially in big environments.
Resolution:
SSEA executes just one ioscan command in the
SseXIoScanRdsk and ScsiIquiry functions. The ioscan
output is cached into a buffer and parsed for
information twice.
Id = HSLco33214
In case of non-XP rdsk, SSEA can not find the volume
group belonging to this rdsk and resolving can not
be done.
Resolution:
SSEA finds and checks all the rdsks belonging to an LDEV
on the R2 side. Than it uses only those rdsks which are
included in a volume group, in this way skips the non-XP
rdsks.
Id = HSLco35074
When there are more than one smb sessions running
simultaneously, horcm instances could be attached to
the same command device.
Resolution:
SSEA retries the getldev() call for 10 times. The
timeout before calling the getldev() API again is
randomly set. From now on SSEA tries to attach up
to 5 command devices if necessary.
Id = HSLco36105
A time out occurs on remote communication, and HORC
manager fails to re-execute.
Resolution:
A new environment variable SSEA_RM_TIMEOUT is
introduced. Its default value is 6000 milliseconds.
Id = HSLco36476
When mapping the LDEVs to the appropriate rdsks,
rdsks statuses are not correctly updated.
Resolution:
Mapping is done correctly.
Part of SSPUX350_083.
Id = HSLco36975
When the LDEVs belonging to a volume group are in PAIR
status and the SSEA smb session is started on some of
these LDEVs, the vgchange command on this volume group
takes a long time. After splitting the disks on on the
R2 side, the LDEVs included in the SMB session are in
PSUS state, the rest of the LDEVs are still in PAIR
state and vgchange command can not proceed, which
causes the session to ends abnormally.
Resolution:
If the SMB_SPLIT_ENTIRE_VG environment variable is set
to 1 in the .omnirc file on both hosts, then all the
LDEV pairs included in the backup volume group are
synchronized and split.
Part of SSPUX350_084.
PHSS_26215:
Id = HSLco32218
Horc instance number is not configurable.
Resolution:
Horc instance number can be configured using new
environment variables, SSEA_RMINST_LOW and
SSEA_RMINST_HIGH. When set in ${OMNI_HOME}/.omnirc
file, these variables set instance number range. Default
values for SSEA_RMINST_LOW and SSEA_RMINST_HIGH
are 50 and 80, respectively.
Part of SSPUX350_070.
Id = HSLco32253
Incorrect comparison of the strings causes incorrect
state of the disks reported.
Resolution:
SSEA agent properly reports disk state.
Id = HSLco32264
SSEA agent creates invalid configuration files for
logical devices exported to LUN's above 128.
Resolution:
New environment variable is introduced: SSEA_XP_PORTS.
Setting the variable to the value "FC" in
${OMNI_HOME}/.omnirc file enables OmniBack II SSEA
Integration to work properly with logical devices
exported to XP LUN's greater than 128.
Id = HSLco32274
Multiple ioscan calls when extracting needed data
cause bad performance.
Resolution:
Scripts for obtaining data needed by OmniBack II SSEA
Integration are improved.
PHSS_25817:
Id = JAGad48627
If pre-exec script fails, cleanup does not start
post-exec script.
Resolution:
New environment variable is introduced. When
SSEA_ALWAYS_POST_SCRIPT in .omnirc file on
application host is set to 1, post-exec script
is always executed.
Id = NSMex04226
Backup is made in SSEA/split mirror backup environment
with the Application host in the cluster. When
restoring object on the Backup host (R2), which is not
in the cluster the cluster tag (-c y) from the
Application host is also restored, so the volume group
can not be activated properly.
Resolution:
By default the cluster tag on the Backup host (R2) is
disabled with the "vgchange -q n -c n" command. To
enable the cluster tag on Backup host, set the new
environment variable SMB_CLUS_DEACT=1 in the
/opt/omni/.omnirc file.
Id = HSLco30300
The command /etc/horcmgr fails if the command
device is used by another split mirror session.
Resolution:
New environment variables are introduced
SSEA_RM_RETRY and SSEA_RM_SLEEP.
SSEA_RM_RETRY defines the number of retries.
SSEA_RM_SLEE defines sleeping time in seconds,
before new retry is started.
Id = HSLco31032
The resolving from LDEVs to rdsks on the backup host
fails due to incorrect reporting of LDEVs to rdsks.
Resolution:
The resolving from LDEVs to rdsks is corrected.
Id = HSLco31434
SSEA agent on R2 does not read the number of rdsk
from the R1. Bug is produced while fixing the
NSMex04787 case on NT platform, but affected the
SSEA agent on the HP-UX platform.
Resolution:
The correct number of strings is read from the SSEA
agent on the R2 side.
Id = HSLco30701
The SCTL_InquiryDisk function returns empty or
corrupted inq structure.
Resolution:
The ioctl system function writes its output directly
to the inq structure. The "mapping from rdsks to LDEVs"
and the ScsiInquiry are enhanced.
Part of SSPUX350_057.
Id = HSLco31490
SSEA can not start the selected HORCMINST instance
number. It is already started by another RaidManager
process.
Resolution:
SSEA tries to start the instance with different
instance number up to five times.
PHSS_24425:
Id = NSMex04086
Message level of a resolving failure in XP environment
is set to "Normal" instead of "Major".
Resolution:
Message level is corrected.
Id = NSMex04209
If backup devices are exported to more than one port
and original devices have more than two mirrors, when
session is started and two of these ports are used for
that session, SSEA Integration detects more mirrors
than it is allowed.
Resolution:
Parsing of raidscan() output is improved.
Id = NSMex04216
If there are two or three mirror disks to source
disk, OmniBack II reports that cascading structure is
found although cascading structure is present only
when there are mirror disks to targer disk.
Resolution:
Searching for cascading structure is excluded as
this feature is not supported with OmniBack II
A.03.50 version.
Id = NSMex04392
Incorrect filesystem options are sent to R2 side.
For HFS filesystems the entries in the mnttab file
are not updated promptly.
Resolution:
Correct filesystem options are sent to R2 side.
/etc/mnttab is promptly updated for HFS filesystem.
Id = NSMex04267
SSEA API fails after 60 seconds during the change of
volume groups. SMB_TIMEOUT is hardcoded to 60 seconds.
Resolution:
SMB_TIMEOUT can be configured in .omnirc file for
situations where the changing of volume groups takes
more than one minute.
Part of SSPUX350_037.
Id = HSLco23886
LVM Mirror (XP Campus Cluster) is not supported within
OmniBack II SSEA Integration.
Resolution:
LVM Mirror (XP Campus Cluster) is supported within
OmniBack II SSEA Integration.
PHSS_22436:
Id = NSMex03360
XP256 Raid Manager's pairdisplay command returns
invalid status which causes some raw disks to fail
during resolving.
Resolution:
Status checking changed to ignore invalid status from
pairdisplay command.
Id = NSMex03700
If there is a lot of backup objects (usually case with
SAP databases) and these objects are placed in volume
group with a lot of stripped disks, then the size of
the internal message sent from SSEA-R1 to SSEA-R2 can
overflow hardcoded 100k limit.
Resolution:
New message format reduces message size significantly.
Part of the SSPUX350_007.
Id = NSMex03717
a) OmniBack II does not handle soft links correctly.
b) SSEA integration backup does not work properly in
case that a single session contains both filesystem
and rawdisk objects.
Resolution:
Fixes are implemented in ssea.
Part of the SSPUX350_007.
Id = NSMex03482
Disk synchronization failure reported as "Normal".
Resolution:
Message statuses are properly reported.
Id = HSLco22201
OmniBack II SSEA integration is not supported on Sun
Solaris operating system.
Resolution:
OmniBack II SSEA integration is supported on Sun
Solaris 7 and 8 operating systems.
Please find the integration manual in the
/usr/omni/bin/utilns directory after the patch is
installed.
Id = NSMex03651
IPC buffer for communication between SSEA Agents on
backup and application host is too small.
Resolution:
IPC buffer increased.
Id = NSMex03673
Pairdisplay command fails in ServiceGuard environment.
Resolution:
Hostname resolving is improved.
Id = NSMbb39679
OmniBack II does not treat status COPY as a valid
status.
Resolution:
OmniBack II waits (for configurable timeout) for the
second disk to change the status to PAIR.
Environment variables are:
SSEA_SYNC_SLEEP_TIME = <time in seconds>
SSEA_SYNC_RETRY = <number of retries>
Default values are 5 for SSEA_SYNC_SLEEP_TIME and
10 for SSEA_SYNC_RETRY.
Id = NSMex03547
Resolving of objects fails if stat() function reports
error for any entry in /etc/mnttab.
Resolution:
Irrelevant errors are skipped during the resolving.
Id = NSMex03739
Pre- and post-exec scripts return invalid exit status
because of timing problem.
Resolution:
Environment variable OB2EXECTIMEOUT is introduced.
Variable represents timeout (in seconds) after the end
of pre- and post-exec script. Default value is 0.
Recommended value is between 5 and 10 seconds.
Id = NSMex03913
Pairdisplay command fails if two sessions are started
at the same time.
Resolution:
SSEA Agent correctly detects service port numbers
availability.
Id = NSMex03960
SSEA Agent uses only those disks for which ioscan
reports state CLAIMED. Backup fails due to a fact that
some of the disks needed for session are in state SCAN.
Resolution:
Disks in state SCAN are reported as well as those in
state CLAIMED.
Id = NSMex03850
Changes made for JFS 3.3 support cause mount problems
on HP-UX 10.20 platform.
Resolution:
Code now properly works also for the HP-UX 10.20
platform.
Part of SSPUX350_016.
Id = NSMex03749
Filesystem is not mounted with the options that were
used before split mirror backup was performed.
Resolution:
Command line mount command is used instead of mount
function for vxfs filesystem.
Id = NSMex03563
Mount operation does not work properly on systems
with Online JFS 3.3 installed.
Resolution:
Mount API uses proper arguments.
Id = NSMex03931
Invalid configuration files are created for LDEVs
exported to LUN addresses above 128.
Resolution:
New environment variable SSEA_XP_PORTS is introduced.
Its value has to be set to "FC" when using Fibre channel
and LUN addresses greater than 128.
Part of SSPUX350_032.
SR:
H555008656 B554000692 H555007043 H555008599 H555007071
B554000869 B554000879 H555007361 H555008750 H555008259
H555006993 H555006994 H555006986 H555006996 H555006685
H555006753 8606179403 H555006844 H555006835 H555006603
H555005488 H555005717 H555005689 H555005681 H555004065
H555005289 H555003697 B554000781 B554000676 B554000847
B554000829 H555004533 H555004741 H555003490 H555003716
B554000521 B554000612 H555003817 H555004474 B554000803
B554000491 H555004919
Patch Files:
/opt/omni/databases/vendor/ssea/hp/s800/hp-ux-1020/A.03.50/
packet.Z
/opt/omni/databases/vendor/ssea/hp/s800/hp-ux-11/A.03.50/
packet.Z
/opt/omni/databases/vendor/ssea/sun/sparc/solaris-26/
A.03.50/packet.Z
/opt/omni/databases/vendor/ssea/sun/sparc/solaris-26/
A.03.50/require.dat
what(1) Output:
/opt/omni/databases/vendor/ssea/hp/s800/hp-ux-1020/A.03.50/
packet.Z:
None
/opt/omni/databases/vendor/ssea/hp/s800/hp-ux-11/A.03.50/
packet.Z:
None
/opt/omni/databases/vendor/ssea/sun/sparc/solaris-26/
A.03.50/packet.Z:
None
/opt/omni/databases/vendor/ssea/sun/sparc/solaris-26/
A.03.50/require.dat:
None
cksum(1) Output:
520178197 2040639 /opt/omni/databases/vendor/ssea/hp/s800/
hp-ux-1020/A.03.50/packet.Z
4215953217 2078307 /opt/omni/databases/vendor/ssea/hp/s800/
hp-ux-11/A.03.50/packet.Z
4065919303 1551193 /opt/omni/databases/vendor/ssea/sun/
sparc/solaris-26/A.03.50/packet.Z
1830950196 19 /opt/omni/databases/vendor/ssea/sun/sparc/
solaris-26/A.03.50/require.dat
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_22436 PHSS_24425 PHSS_25817 PHSS_26215
Equivalent Patches:
PHSS_27592:
s700: 11.00 11.11 11.20
s800: 11.00 11.11 11.20
Patch Package Size: 5600 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_27591
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHSS_27591.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHSS_27591. 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_27591.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_27591.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
PHSS_27591:
NOTE!
This patch has to be installed on the Installation
Server host.
The OB2 SSEA agent must be redistributed to the SSEA
client system(s) after the installation of the patch
in order to get the fixes into effect.
For distribution of the SSEA agent, refer to
the OmniBackII Installation guide.
Patch includes the following Site Specific Patches:
SSPUX350_007
SSPUX350_016
SSPUX350_032
SSPUX350_037
SSPUX350_057
SSPUX350_070
SSPUX350_083
SSPUX350_084
-----End of Document ID: PHSS_27591------------------------------------------
Document ID: PHSS_27966
Date Loaded: 20021107
Title: s700_800 10.20 OV WBSSPIa.02.00.00 Multi-problem
Patch Name: PHSS_27966
Patch Description: s700_800 10.20 OV WBSSPIa.02.00.00 Multi-problem
Creation Date: 02/11/05
Post Date: 02/11/07
Hardware Platforms - OS Releases:
s700: 10.20
s800: 10.20
Products:
HP OpenView Smart Plug-In for WebSphere a.02.00.00
Filesets:
WBSSPI.WBSSPI-HPUX,A.02.00.00 WBSSPI.WBSSPI-SOL,A.02.00.00
WBSSPI.WBSSPI-AIX,A.02.00.00 WBSSPI.WBSSPI-NT,A.02.00.00
Automatic Reboot?: No
Status: General Release
Critical: No
Path Name: /hp-ux_patches/s700_800/10.X/PHSS_27966
Symptoms:
PHSS_27966:
- R555018544 - All SPI scripts fail on OVO 6 Solaris agents
- R555017595 - Reporter data for a down app server is
missing
- R555018602 - Monitoring fails when WebSphere security
is on
- R555018984 - Several calculated metrics are returning
no data.
Defect Description:
PHSS_27966:
Resolution:
R555018544 - All SPI scripts fail on OVO 6 Solaris agents
PROBLEM:
The SPI fails to run on OVO 6 on Solaris with the
message:
ld.so.1: /opt/OV/contrib/perl/bin/perl: fatal:
libopcperl.so: open failed: No such file or directory
Killed
CAUSE:
The file libopcperl.so is missing from the SPI's perl
installation.
FIX:
Install the missing file
R555017595 - Reporter data for a down app server is missing
PROBLEM:
When an app server is down, the SPI should report metric
value "0" to the Reporter log file. Instead, no data is
written. This doesn't effect the uptime calculation
which is the primary purpose for the Reporter reports,
but it lumps app server downtime under No Data in the
report tables.
CAUSE:
The Reporter data logging was not properly sequenced in
the case when a server was down and metric 2 was
requested.
FIX:
The collector source was corrected. The internal metric
definitions and the OVO templates needed to be adjusted
to be in sync.
R555018602 - Monitoring fails when WebSphere security is on
PROBLEM:
When WebSphere security is turned on, the monitor will
not be able to contact the server for any metric
information.
CAUSE:
WebSphere security presents a login challenge for
access to the PMI client. The collector software
did not incorporate login/password capability.
FIX:
Collector software was modified to handle a login
and password.
R555018984
PROBLEM:
Several metrics are returning no data in WBSSPI A.02.00.
Affected metrics: WBSSPI_0014, WBSSPI_0022, WBSSPI_0222,
WBSSPI_0024, WBSSPI_0224, WBSSPI_0042, WBSSPI_0045,
WBSSPI_0245, WBSSPI_0047, WBSSPI_0247, WBSSPI_0065,
WBSSPI_0265, WBSSPI_0066, WBSSPI_0266, WBSSPI_0074,
WBSSPI_0075, WBSSPI_0076, WBSSPI_0078
CAUSE:
Metrics that have an interval in their formula where the
parameter to the interval is used previously in the
formula will fail and return no value.
FIX:
Fixed the coding problem in the collector program
that caused the error.
SR:
R555018602 R555017595 R555018984 R555018544
Patch Files:
/var/opt/OV/share/databases/OpC/mgd_node/customer/hp/
pa-risc/hp-ux11/cmds/wasspi_wbs_verify.Z
/var/opt/OV/share/databases/OpC/mgd_node/customer/hp/
pa-risc/hp-ux11/monitor/wasspi_wbs_config.pl.Z
/var/opt/OV/share/databases/OpC/mgd_node/customer/hp/
pa-risc/hp-ux11/monitor/wasspi_wbs_ca.Z
/var/opt/OV/share/databases/OpC/mgd_node/customer/sun/sparc/
solaris/monitor/wasspi_wbs_config.Z
/var/opt/OV/share/databases/OpC/mgd_node/customer/sun/sparc/
solaris/monitor/wasspi_wbs_config.pl.Z
/var/opt/OV/share/databases/OpC/mgd_node/customer/sun/sparc/
solaris/monitor/wasspi_wbs_ca.Z
/var/opt/OV/share/databases/OpC/mgd_node/customer/sun/sparc/
solaris/cmds/wasspi_wbs_verify.Z
/var/opt/OV/share/databases/OpC/mgd_node/customer/ibm/
rs6000/aix/monitor/wasspi_wbs_config.pl.Z
/var/opt/OV/share/databases/OpC/mgd_node/customer/ibm/
rs6000/aix/monitor/wasspi_wbs_ca.Z
/var/opt/OV/share/databases/OpC/mgd_node/customer/ibm/
rs6000/aix/cmds/wasspi_wbs_verify.Z
/var/opt/OV/share/databases/OpC/mgd_node/customer/ms/intel/
nt/cmds/wasspi_wbs_verify.exe
/var/opt/OV/share/databases/OpC/mgd_node/customer/ms/intel/
nt/monitor/wasspi_wbs_config.exe
/var/opt/OV/share/databases/OpC/mgd_node/customer/ms/intel/
nt/monitor/wasspi_wbs_ca.exe
what(1) Output:
/var/opt/OV/share/databases/OpC/mgd_node/customer/hp/
pa-risc/hp-ux11/cmds/wasspi_wbs_verify.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/customer/hp/
pa-risc/hp-ux11/monitor/wasspi_wbs_config.pl.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/customer/hp/
pa-risc/hp-ux11/monitor/wasspi_wbs_ca.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/customer/sun/sparc/
solaris/monitor/wasspi_wbs_config.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/customer/sun/sparc/
solaris/monitor/wasspi_wbs_config.pl.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/customer/sun/sparc/
solaris/monitor/wasspi_wbs_ca.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/customer/sun/sparc/
solaris/cmds/wasspi_wbs_verify.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/customer/ibm/
rs6000/aix/monitor/wasspi_wbs_config.pl.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/customer/ibm/
rs6000/aix/monitor/wasspi_wbs_ca.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/customer/ibm/
rs6000/aix/cmds/wasspi_wbs_verify.Z:
None
/var/opt/OV/share/databases/OpC/mgd_node/customer/ms/intel/
nt/cmds/wasspi_wbs_verify.exe:
yaccpar 1.8 (Berkeley) 01/20/91
/var/opt/OV/share/databases/OpC/mgd_node/customer/ms/intel/
nt/monitor/wasspi_wbs_config.exe:
yaccpar 1.8 (Berkeley) 01/20/91
/var/opt/OV/share/databases/OpC/mgd_node/customer/ms/intel/
nt/monitor/wasspi_wbs_ca.exe:
yaccpar 1.8 (Berkeley) 01/20/91
cksum(1) Output:
3634951765 5561 /var/opt/OV/share/databases/OpC/mgd_node/
customer/hp/pa-risc/hp-ux11/cmds/wasspi_wbs_verify.Z
712818344 2793863 /var/opt/OV/share/databases/OpC/mgd_node/
customer/hp/pa-risc/hp-ux11/monitor/
wasspi_wbs_config.pl.Z
1417493501 4816 /var/opt/OV/share/databases/OpC/mgd_node/
customer/hp/pa-risc/hp-ux11/monitor/wasspi_wbs_ca.Z
899281137 1302018 /var/opt/OV/share/databases/OpC/mgd_node/
customer/sun/sparc/solaris/monitor/
wasspi_wbs_config.Z
3830254488 2793513 /var/opt/OV/share/databases/OpC/mgd_node/
customer/sun/sparc/solaris/monitor/
wasspi_wbs_config.pl.Z
2168987027 4841 /var/opt/OV/share/databases/OpC/mgd_node/
customer/sun/sparc/solaris/monitor/wasspi_wbs_ca.Z
3959220488 5611 /var/opt/OV/share/databases/OpC/mgd_node/
customer/sun/sparc/solaris/cmds/wasspi_wbs_verify.Z
1729296685 2793559 /var/opt/OV/share/databases/OpC/mgd_node/
customer/ibm/rs6000/aix/monitor/
wasspi_wbs_config.pl.Z
3946618349 4838 /var/opt/OV/share/databases/OpC/mgd_node/
customer/ibm/rs6000/aix/monitor/wasspi_wbs_ca.Z
1237827337 5592 /var/opt/OV/share/databases/OpC/mgd_node/
customer/ibm/rs6000/aix/cmds/wasspi_wbs_verify.Z
2334770365 1630208 /var/opt/OV/share/databases/OpC/mgd_node/
customer/ms/intel/nt/cmds/wasspi_wbs_verify.exe
2870582530 6021120 /var/opt/OV/share/databases/OpC/mgd_node/
customer/ms/intel/nt/monitor/wasspi_wbs_config.exe
1138452802 1548288 /var/opt/OV/share/databases/OpC/mgd_node/
customer/ms/intel/nt/monitor/wasspi_wbs_ca.exe
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches:
PHSS_27967:
s700: 11.00 11.11
s800: 11.00 11.11
ITOSOL_00176:
sparcSOL: 2.3 2.4 2.5 2.6 2.7 2.8
Patch Package Size: 18550 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_27966
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHSS_27966.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHSS_27966. 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_27966.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_27966.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
PHSS_27966:
After installing the patch, use OVO to deploy
Actions, Monitors, and Commands to the managed
nodes where the WebLogic is running. Then run
the application "Config WLSSPI" on those managed
nodes.
-----End of Document ID: PHSS_27966------------------------------------------
Document ID: PHSS_27468
Date Loaded: 20021107
Title: s700_800 10.20 LIBCL cumulative patch
Patch Name: PHSS_27468
Patch Description: s700_800 10.20 LIBCL cumulative patch
Creation Date: 02/10/29
Post Date: 02/11/07
Hardware Platforms - OS Releases:
s700: 10.20
s800: 10.20
Products: N/A
Filesets:
OS-Core.CORE-SHLIBS,B.10.20 ProgSupport.LANG-MIN,B.10.20
Automatic Reboot?: No
Status: General Release
Critical:
No (superseded patches were critical)
PHSS_14000: OTHER
Some simulation tools requires this patch
for locating their code (stored in $DATA$ space).
Path Name: /hp-ux_patches/s700_800/10.X/PHSS_27468
Symptoms:
PHSS_27468:
JAGae40085: PROBER in unwind lib causes stack to grow
JAGad70835: support for N edit descriptor.
JAGad69726: support for M edit descriptor.
PHSS_27105:
JAGad89129: Implicit write cannot open unit # > 99
JAGad92163: Bad Octal representation of numbers > 4294967295
JAGae05973: Wrong conversion of hex read of 0x80000000
PHSS_25717:
JAGad75314: writing to unit ID 26843546 causes crash.
JAGad54112: Intrinsic function NINT produces incorrect
results.
JAGad93863: cosd(90) should be 0.0, not 0.6123233996D-16
JAGad50860: I/O problem (-0.0000 instead of 0.0000)
PHSS_22652:
1. JAGaa93357: Calls to __F90_F_EXIT always had and exit
code of 0, even when not appropriate.
2. JAGad00306: large real constants not assigned properly
3. JAGad27408: Problem with numbers starting list
directed I/O streams.
PHSS_21951:
1. JAGab21216: U_STACK_TRACE only unwinds the frames
up to the sigreturn call, and does not display the
frame of the routine that was running when the signal
was caught.
2. JAGab71918: A throw or escape out of a signal handler
in aC++ will likely cause an abort when used in the catch
clause.
3. JAGab77879: Performance problems or hangs for F90
dynamic strings/arrays and Pascal's escapecode.
PHSS_17689:
1. Fortran treats letters T, F, t, f as valid input for
numeric items, instead of catching them as an error.
PHSS_16690:
1. Unwinding through an invalid stack frame may not
discontinue the unwinding process. The routine
which finds unwind entries in the unwind table,
"U_get_unwind_entry" has an "off by one" logic
error in its search algorithm and could return a
pointer to the address beyond the end of the unwind
table indicating that it found an unwind entry
instead of indicating that no entry was found.
2. The error message reported to the user when an alloca
frame is encountered by U_get_previous_frame() is
incorrect. "5613 Procedure entry sequence is too
long for Unwind. Contact HP Service." is displayed
rather than "5612 Old version data structures won't
restore r3 and r4 for Alloca Unwind." Reminder:
U_get_previous_frame_x() is the new 10.20 interface
which permits unwinding alloca() stack frames.
PHSS_15549:
1. PHSS_11658 causes FORTRAN to ignore format spec $
(newline suppression).
2. Fortran complex arithmetic is much slower with the
post-Fortran90 libcl.
3. For value 0.0, ES12.3 format displays 0.000E-01,
it should be 0.000E+0
4. FORTRAN I/O ERROR 979: VARIABLE NOT IN NAMELIST GROUP
for variables with embedded "$"
5. FORTRAN I/O ERROR 979: VARIABLE NOT IN NAMELIST GROUP
for f90 namelist IO which defines multiple array items
after a single array element is specified.
PHSS_15255:
1. Fortran formatted real output has a generic accuracy
problem caused by sometimes rounding a formatted value
twice. This can result in a formatted value that is
too large.
PHSS_14423:
1. If when handling an exception, the unwinder is
called to unwind a stack which contains alloca frames,
the stack unwind will often fail when crossing the
alloca() frame. (This affects Ansi C++ exception
handling which uses alloca() to allocate space for
temporary variables.)
2. The unwinder may dump core when unwinding through HP_UX
exception frames in shared libraries. The dumping of
core is likely to happen if the user has not followed
the procedure calling conventions in generating object
code (examples: A 3rd party compiler, assembly
functions which don't follow the HP procedure calling
conventions, simulator generated code.) The unwinder
dumps core rather than detecting the corrupt stack and
returning a "can't unwind" return value from
U_get_previous_frame().
PHSS_14000:
1. Applications which call stack unwind routines including
U_get_previous_frame() may receive different
description of stack frame upon reaching an invalid
frame in the stack. The behavior changed with
the introduction of patch PHSS_10766.
2. When using Ansi C++ exception handling support,
U_STACK_TRACE fails when called from signal
handler. The failure mode occures only if the
handler is responding to a signal which has
interrupted an HP_UX system call
3. Fortran 77 program is not terminated on the
first use of "kill -1."
PHSS_11658:
1. SR 16533218321 : In a Fortran program, sequential
unformatted write operations with empty I/O lists
results in a file that cannot be read back in.
2. In Fortran programs, the performance of formatted
floating point output is, in some instances, much
slower than with a 9.X release of Fortran 77.
PHSS_10766:
1. Unwind library fails to cross shared library
boundaries and signal frames.
PHSS_10743:
1. SR 5003363085, 1653198705 : In a Fortran program an
unformatted read of an unquoted character string may stop
before reaching the end of the string. This happens when
the string contains a quote or ':' character.
2. SR 5003360081 : A Fortran 77 program that tries to trap
INTEGER*4 overflow using "ON INTEGER*4 OVERFLOW ..." will
not in fact trap the overflow.
PHSS_9483:
1. SR 5003324855: Unwind library doesn't work if an
alloca call has been made.
PHSS_8967:
1. Fails to allow access to files larger than
2 Gigabytes in size.
PHSS_8966:
1. SR 5003340596 : There is a memory leak when closing
files that can cause a program to run out of memory
if it opens and closes files many times.
2. SR 1653187393 : A file auto-opened with a sequential
read or write statement will create a file whose
maximum record length is 256 bytes.
PHSS_8397:
1. Use of +Oparallel and shared libraries on HPUX 10.20
results in undefined externals __FTN_SET_AR and
__FTN_300CHARS.
2. Systems cannot compile Fortran 90 programs or run
Fortran 90 programs that were linked with a shared
libcl.
3. SR 5003330738 : Reading and writing may be much slower
under HP-UX 10.20 than on earlier releases.
PHSS_6986:
1. SR 5003298067 : Reading a record from an ISAM file may
cause the program to crash or exhibit other symptoms of
writing off the end of a dynamically allocated memory
block. Whether this problem will be observed depends on
exactly what other IO commands are executed both before
and after the ISAM file read.
2. SR 5003298075 : Programs may crash when using a REWRITE
statement to alter an existing ISAM record. The REWRITE
statement is used only with ISAM files. The occurrence of
this problem is highly sensitive to the pattern of
allocation and deallocation of memory blocks at run-time.
However, if the problem occurs it will almost certainly
result in a program crash while attempting to execute the
REWRITE statement; delayed symptoms or silent incorrect
behavior are very unlikely.
3. SR 5003290122 : If a program backspaces over an initial
64 byte record, the file pointer will be left in the
wrong position and the next access to the file will read
or write the wrong location in the file. This problem
only occurs with the initial record, and that record must
be exactly 64 bytes long.
4. SR 5003280859 : Arrays of 4-byte integers do not work
correctly with namelists if the +autodblpad compiler
switch is used. Only the first element of the array will
be correctly accessed via the namelist.
PHSS_5691:
1. SR 4701296160 : "Ada/unwind fails on 10.0" Users of Alsys
Ada will experience problems with exception handling on
HP-UX 10.0 without this patch. Exceptions may not be
caught by the program's handlers, or may cause core
dumps. This patch is essential for all Alsys Ada users.
2. SR 4701295998 : "C++ program compiled on 9.0 dumps core
on 10.0" Only affects C++ programs using exception
handling. Note that this fix is also included in HP-UX
release 10.01. It is mentioned here so that users of
HP-UX 10.00 may obtain the patch without updating their
whole system, should they so wish.
Defect Description:
PHSS_27468:
JAGae40085: PROBER in unwind lib causes stack to grow
PHSS_27105:
JAGad89129: Implicit write cannot open unit # > 99
JAGad92163: Bad Octal representation of numbers > 4294967295
JAGae05973: Wrong conversion of hex read of 0x80000000
PHSS_25717:
JAGad75314: Only works on large filesystems. Added a
clearer message to libIO77 when it fails at
exactly 2 GiG mark
JAGad54112: Increased precision of internal datatypes.
JAGad93863: added new intrinsic routines for cosd(90)
sin(0), and tand(180). Default behavior is
old imprecise values. Use f90 flag
+trigdacc (trig degree accurate) to get new
alternate intrinsics. No other Source change
needed.
JAGad50860: I/O problem (-0.0000 instead of 0.0000)
PHSS_22652:
1. JAGaa93357: Calls to __F90_F_EXIT always had and exit
code of 0, even when not appropriate.
2. JAGad00306: treat large real constants like F77.
3. JAGad27408: Problem with numbers starting list
directed I/O streams.
PHSS_21951:
1. JAGab21216: Error in U_STACK_TRACE unwinding past
64 bit _sigreturn
2. JAGab71918: If a throw or escape is done out of a
signal handler that interrupted a system call the values
of the callee save registers (at least R3 and R4) may be
invalid
3. JAGab77879: Performance problems or hangs for F90
dynamic strings/arrays and Pascal's escapecode.
PHSS_17689:
1. T, F, t, f are logicals and were incorrectly accepted
as integers.
PHSS_16690:
1. The off by one error in U_get_unwind_entry()
returns a bogus unwind descriptor for a pc
offset (the first argument) which is higher
than the highest executable pc offset in the
load module.
2. The message catalog for Unwind was missing
an entry. To reproduce this problem (and thus to
determin whether you need the patch on your system,)
use the following program. Note that this program
uses short cuts which are archive library specific.
It will not link shared. Just for reference, the
program also demonstrates use of the new
U_get_previous_frame_x interface for correct un-
winding through alloca frames.
#include <alloca.h>
#include <stdio.h>
typedef unsigned int address;
typedef unsigned int space;
main()
{
struct {
int curr_frame_size;
address curr_sp;
unsigned long curr_pcspace;
address curr_pcoffset;
address curr_dp;
address curr_rp;
address curr_mrp;
space curr_sr0, curr_sr4;
int r3;
address cur_r19; /* for PIC code */
int r4;
int reserved;
} cfi;
struct {
int prev_frame_size;
address prev_sp;
space prev_pcspace;
address prev_pcoffset;
int prev_dp;
unsigned int uw_descr[2];
address ustart;
address uend;
int uw_index;
address prev_r19; /* for PIC code */
int r3;
int r4;
} pfi;
#ifdef NEW_INTERFACE
#define UNWIND_STEP(cfi,pfi) \
U_get_previous_frame_x(&cfi,&pfi,sizeof(pfi));
#else
#define UNWIND_STEP(cfi,pfi) \
U_get_previous_frame(&cfi,&pfi);
#endif
void *mptr;
mptr = alloca(1000);
U_get_frame_info(&cfi);
UNWIND_STEP(cfi,pfi);
copy_frame_info(&cfi,&pfi);
UNWIND_STEP(cfi,pfi);
}
/* END */
Compile Line: cc -Ae test_alloca.c -Wl,-aarchive -lcl
$a.out will display, "Procedure entry sequence is too
long for Unwind. Contact HP Service." if patch
PHSS_16690 has not been installed on your system. It will
display "Old version data structures won't restore r3 and
r4 for Alloca Unwind." if the patch has been installed.
PHSS_15549:
1. SR1653242602: PHSS_11658, while fixing non-advancing
IO to conform to f90 standards, makes format spec $
stop working.
2. SR1653258798: Post-f90 libcl's complex arithmetic
routines were compiled without optimization.
3. SR5003407429: ES format descriptor incorrectly
handled 0.0, by decreasing the printed exponent
by one when it shouldn't.
4. SR5003390112: dollar signs ($) were not allowed in
namelist variable names, because of an earlier change
to make $end work correctly. Supporting $end is not
mutually exclusive with allowing $'s in variable
names as long as the $ is not the first character,
and the f77 and f90 compilers do not allow names to
begin with $.
5. SR5003421701: f90 uses namelist IO handling distinct
from f77, in order to handle new f90 features such as
array sections. The f90 implementation did not allow
more than one namelist value to follow a single
specified array element, which is sometimes used as
a starting position for a list of values.
PHSS_15255:
1. The Fortran IO library rounded the value to w+1 digits
during its initial conversion from floating point to
ascii, where w is the width requested in the format
string. It then proceeded to round the ascii result a
second time, to p digits, where p is the precision
requested in the format string. Rounding should have
been performed only once, to p digits, and never to
w+1 digits.
PHSS_14423:
1. The unwinder was not always obtaining the values of
gr3 and gr4 from the appropriate locations during
unwinding through exceptions which interrupted
HP_UX system calls. When encountering a stack frame
for an exception which interrupted the OS, the
values for r3 and r4 should be obtained from the user's
stack (which the unwind library tracks in it's
"state_vector" data structure.) The unwind library
was instead, getting these values from the signal
context saved when the interrupt occurred.
2. The unwinder dumps core when unwinding exception
frames in shared libraries upon getting a return
pointer in protected memory. Routines which
extract a return pointer from exception handler
code was not checking addresses for readability
prior to accessing the address triggering bus
errors.
PHSS_14000:
1. Applications calling U_get_previous_frame() on an
invalid stack frame received different results
because U_get_previous_frame() has been modified
to unwind inport and export stubs on the stack which
have been optimized by the linker (e.g. do not appear
in the stub unwind region tables in the SOM). After
U_get_previous_frame attempted to unwind a region of
the stack which was not listed in unwind tables or
stub unwind tables, the data structure which describes
the top frame of the stack has been filled with either
1) the description of the next stack frame on the stack
if the stack contained a "linker optimized" stub at its
top, or otherwise, 2) garbage values if the top of the
stack was an invalid frame. The original behaviour
of U_get_previous_frame was to not destroy the
information in the frame data structure in condition
(2).
2. The Ansi C++ exception handling support was failing
because the Stack Unwind routines (U_get_previous_frame)
were obtaining the gr3 and gr4 register values from
the signal context record, when instead it should have
picked them up from the "callee saves" register storage
area on the stack. The Unwind functions were not
correctly handling the difference between the state
saved by signals which interrupted user code from
signals which interrupted HP_UX system code.
3. Use the following f77 program to verify the "kill -1"
patch needs to be installed.
PROGRAM toto
X=0
DO WHILE (X .NE. 1000000)
WRITE (*,*) 'X = ',X
X = X + 1
END DO
END
Compile and execute the program. Issue
a "kill -1 <process id>" If a second "kill -1"
command is necessary, the patch is needed.
PHSS_11658:
1. In a Fortran program, sequential unformatted writes
with empty IO lists wrote nonsense records into
the file making the file unreadable. SR 1653218321
2. The slow performance of Fortran formatted floating point
output was due to the unnecessary use of quad precision
computation when double precision would have sufficed.
PHSS_10766:
1. The unwind library routine, "U_get_previous_frame()"
and it's associated routines such as "U_STACK_TRACE()"
fail to cross shared library boundaries and signal
stack frames.
PHSS_10743:
1. SR 5003363085, 1653198705 : The Fortran runtime library
did not handle correctly certain delimiter characters
when they occurred in an unquoted character string. The
read should terminate only when a blank, comma, slash, or
end of record is encountered.
2. SR 5003360081 : A defect in the Fortran runtime library
caused INTEGER*4 traps to be interpreted as INTEGER*8
traps. Note that INTEGER*8 is supported by F90 but not by
F77.
PHSS_9483:
1. Calls to the unwind library routine,
"U_get_previous_frame()" or it's associated
routines such as "U_STACK_TRACE()" do not unwind
through stacks which contain a frame in which
alloca() has been used to dynamically allocate
memory.
PHSS_8967:
1. libcl fails to allow access to files larger than
2 Gigabytes in size.
PHSS_8966:
1. Some memory was not freed when a file was closed.
2. The maximum record length was incorrectly being set
when a sequential file was auto-opened.
PHSS_8397:
1. The symbols __FTN_SET_AR and __FTN_300CHARS were not
exported from the shared version of libcl.
2. The complete set of Fortran 90 functionality was not
shipped with the 10.20 or earlier releases of HP-UX.
3. Changes were made to speed up the runtime IO system.
It may still not be as fast as in HP-UX 10.01 or 10.10
due to changes for Fortran 90 but it is faster then
the HP-UX 10.20 version.
PHSS_6986:
1. SR 5003298067 : The problem is caused by the runtime IO
library inappropriately reallocating a buffer to a
smaller size.
2. SR 5003298075 : The problem was caused by an
uninitialized variable in a dynamically allocated block.
3. SR 5003290122 : The defect was caused by incorrect
control logic in a Fortran run-time library routine.
4. SR 5003280859 : The +autodblpad option causes integer
arrays to be "padded" out to a length of 8 bytes for each
array element. But the runtime library routines that
implement access through a namelist treat the array as if
it had not been padded. This causes accesses to all
elements of the array, except to the first, to be
incorrect. Either the wrong element is accessed, or some
of the padding bytes are accessed.
PHSS_5691:
1. SR4701296160
(a) Ada compiler incorrectly used the "sr4export" bit of
unwind descriptors.
(b) Unwind library for HP-UX 10.0 incorrectly handled Ada
variable-sized frames and separate package bodies.
2. SR4701295998
An internal interface was changed at the 10.0 release
which led to incompatibilities with some C++ programs
that had been compiled on HP-UX 9.0. The problem was
solved by reverting to the original interface.
SR:
5003422808 1653281634 5003438473 4701380345 1653232181
5003324855 5003340596 5003330738 5003409466 1653253690
1653242602 1653258798 5003407429 5003421701 5003390112
5003415836 5003415752 8606104417 8606129759 8606145506
8606107614 8606131152 8606158078 8606200550 8606201661
8606206139 8606184910 8606224775 8606219352 8606221758
8606219988 8606223059 8606236924 8606276008 8606201661
8606200550 8606181644
Patch Files:
/usr/lib/libcl.1
/usr/lib/libcl.a
/usr/lib/pa1.1/libcl.1
/usr/lib/pa1.1/libcl.a
/usr/lib/nls/msg/C/libcl.cat
what(1) Output:
/usr/lib/pa1.1/libcl.a:
libcl.a version B.10.29.17 - Oct 28, 2002
fs_amod.s $Revision: 1.9.1.1 $
libIO77 HP HPUX [ Release B.10.20.13 PA 32bit ]
(hp700:hp/ux) Sep 30 2002
Copyright (c) 2001 Hewlett Packard.
Unwind Library version UX.10.20.16 - 02/09/02
Trap Library version UX.10.20.15 - 99/12/13
/usr/lib/pa1.1/libcl.1:
Trap Library version UX.10.20.15 - 99/12/13
Unwind Library version UX.10.20.16 - 02/09/02
libIO77 HP HPUX [ Release B.10.20.13 PA 32bit ]
(hp700:hp/ux) Sep 30 2002
Copyright (c) 2001 Hewlett Packard.
fs_amod.s $Revision: 1.9.1.1 $
libcl.sl version B.10.29.17 - Oct 28, 2002
/usr/lib/nls/msg/C/libcl.cat:
None
/usr/lib/libcl.1:
Unwind Library version UX.10.20.16 - 02/09/02
Trap Library version UX.10.20.15 - 99/12/13
libIO77 HP HPUX [ Release B.10.20.13 PA 32bit ]
(hp700:hp/ux) Sep 30 2002
Copyright (c) 2001 Hewlett Packard.
libcl.sl version B.10.29.17 - Oct 28, 2002
/usr/lib/libcl.a:
libcl.a version B.10.29.17 - Oct 28, 2002
libIO77 HP HPUX [ Release B.10.20.13 PA 32bit ]
(hp700:hp/ux) Sep 30 2002
Copyright (c) 2001 Hewlett Packard.
Unwind Library version UX.10.20.16 - 02/09/02
Trap Library version UX.10.20.15 - 99/12/13
cksum(1) Output:
383011825 2039862 /usr/lib/pa1.1/libcl.a
1587227203 1456160 /usr/lib/pa1.1/libcl.1
1905308540 28439 /usr/lib/nls/msg/C/libcl.cat
4127621153 1431584 /usr/lib/libcl.1
49847425 1991294 /usr/lib/libcl.a
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_27105 PHSS_25717 PHSS_22652 PHSS_21951 PHSS_5691 PHSS_6986
PHSS_8397 PHSS_8966 PHSS_8967 PHSS_9483 PHSS_10743 PHSS_10766
PHSS_11658 PHSS_14000 PHSS_14423 PHSS_15255 PHSS_15549 PHSS_16690
PHSS_17689
Equivalent Patches:
PHSS_27469:
s700: 11.00 11.10
s800: 11.00 11.10
PHSS_27470:
s700: 11.11
s800: 11.11
Patch Package Size: 6850 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_27468
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHSS_27468.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHSS_27468. 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_27468.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_27468.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHSS_27468------------------------------------------
Document ID: PHCO_27803
Date Loaded: 20021107
Title: s700_800 10.20 ksh(1) cumulative patch
Patch Name: PHCO_27803
Patch Description: s700_800 10.20 ksh(1) cumulative patch
Creation Date: 02/10/25
Post Date: 02/11/07
Hardware Platforms - OS Releases:
s700: 10.20
s800: 10.20
Products: N/A
Filesets:
OS-Core.UX-CORE OS-Core.CORE-ENG-A-MAN
Automatic Reboot?: No
Status: General Release
Critical: No
Path Name: /hp-ux_patches/s700_800/10.X/PHCO_27803
Symptoms:
PHCO_27803:
ksh(1) makes improper use of the file system.
PHCO_20018:
1. ksh(1) manpage does not have information about history
file trimming.
2. ksh(1) getopts OPTARG is trashed.
3. ksh(1) fails to login when the history file is >4k and
older than 10 min.
4. ksh(1) coredump with history in heterogenous environment.
5. ksh: read not interrupted by a SIGINT. Works fine with
MR ksh.
6. After trapping SIGHUP, ksh exits.
7. ksh does not trap SIGHUP if received within a function.
PHCO_17691:
ksh(1) coredumps with script using many
heredocs.
PHCO_16363:
1. A return statement in a do-while loop
inside a function exits only the do-while
loop, not the function.
PHCO_16065:
1. ksh does not handle command
substitution of variables of length 2047,
3071, etc. correctly. When a variable is
assigned a string of length equal to
2047/3071/..., the result of command
substitution using this variable retains
only the last 1023 bytes of the variable.
PHCO_15648:
10.20 ksh subshell exits prematurely on a
uniprocessor. When ksh is executed from a
script on a uniprocessor, the shell exits by
itself, without the user typing an explicit
<exit>.
PHCO_13698:
1) ksh dies after sourcing . ./script using while loop
and command redirect. Scripts like the following, when
sourced cause the shell to exit.
echo test |
while read r
do
a=$(date)
done
2) POSIX and Korn shell do not wait(2) for zombies
while in vi input mode
PHCO_13655:
Problem with set -e in ksh:
When set -e is on, ksh does not exit on encountering
error while expanding the word list in a for statement.
This happens even in a case statement and a pipe list.
PHCO_11347:
1) Korn shell does not source a script if stderr is closed.
$cat prog
. sprog
$cat sprog
echo hello
$prog 2>&- <--- does not source 'sprog'
$
2) trap DEBUG does not behave consistently with command
substitution.
3) Shell builtin ':' (: > file) does not truncate
file when called second time from a function.
4) Korh shell dumps core due to memory fault when
function is defined in a loop.
5) Korn shell adds character when parsing input for
trap action name
$cat prog
#!/usr/bin/ksh
trap $1 EXIT
echo t (d )
$./prog ate
prog[2]: syntax error at line 3 : `(' unexpected
Fri Jun 13 18:01:14 IST 1997 <-- 'd' from line 3 is added
to action name 'ate'
PHCO_11010:
1) Korn shell dumps core during command substitution if
standard input is closed.
2) Korn shell does not remove the temporary files when
it exits due to receipt of a signal.
PHCO_10719:
1) When ksh sees history file (using old internal magic
cookies) of pre-10.10 release, it simply unlinks
(discards) that history file.
2) When any shell-builtin command returns NULL in command
substitution and the execution trace flag -x is on, then
the output of the next shell-builtin in command
substitution is affected.
PHCO_9484:
1) While using in-line command editing, characters
would sometimes appear that had not been typed
by the user, most commonly ^B. Also, in editing
long history lines, especially near the end of
the lines, garbage characters would appear and
the line couldn't be edited properly.
2) ksh was leaving fd 10 [used for history file]
always open. File descriptor 10 was being
reserved for use by the shell, but the file
descriptor was opened in a way that it would
remain open across an exec(2) system call.
3) ksh returns incorrect exit-status when it executes
'exit' command on trap.
For Example, When you run the following script
"trap.sh"
#! /usr/bin/ksh
trap "_Exit" 0 1 2 3 15
_Exit(){
exit
}
rm FOOOOOOOO
ls FOOOOOOOO
$trap.sh
$echo $?
0
The exit-value of the above script should be of last
command executed that is 2 (exit value of ls FOOOOOOOO),
rather it will return 0.
PHCO_9088:
1) Trap on EXIT set outside a function is not executed.
For example,
trap 'echo exiting shell' EXIT
f()
{
exit
}
f
should output "exiting shell" but instead produces no
output.
2) cd -P and pwd -P can fail when current directory path
includes symbolic links where the link starts with ../
For example:
cd /tmp
mkdir test
cd test
ln -s ../../usr lnk
cd lnk
pwd -P
will produce the error "pwd: permission denied".
3) ksh hangs when processing "cat bigfile | while read ..."
The right side of the pipe can be any shell command
(while, if, for, etc.)
Defect Description:
PHCO_27803:
ksh makes improper use of the file system.
Resolution:
The file system usage corrected.
PHCO_20018:
1. ksh manpage does not say anything about the history
file trimming.
Resolution:
The necessary information regarding the trimming of
history file is added in the manpage.
2. When getopts is executed it reads the option argument
from the command line and stores it in the static memory.
If we execute some other command before using the value
of OPTARG, the memory will be overwritten and the
argument is lost.
Resolution:
To avoid this the argument that is read from the command
line is stored in the heap so that it will not be
corrupted.
3. When the history file size is more than 4K and the file
is older than 10 minutes, there is some unwanted
recursion between the function which opens the history
file and the function which trims the history file.
Resolution:
The resolution involves avoiding this unwanted recursion
by using a global flag.
4. The problem was due to a corrupt .sh_history file which
was causing the shell to core dump. The problem was due
to an array buffer overflow.
Resolution:
Now this array allocation has been changed to dynamic
allocation & this fixes the problem.
5. When a script was executing a read command and a signal
was sent to it, the signal was not delivered until after
the completion of read.
Resolution:
Now checking of trap has been introduced so as to catch
signals even during input processing.
6. If SIGHUP is trapped and a SIGHUP signal received,
ksh(1) exits after executing the trap. It should
continue to run instead.
Resolution:
ksh(1) was deliberately exiting after executing the
trap for SIGHUP. This part of the code has now been
eliminated, so that it continues to execute.
7. The trap set for signal SIGHUP is not executed
by ksh(1), if it is received while a function
is being executed.
Resolution:
When executing a function, ksh(1) resets all traps to
their default action. If SIGHUP was received while
executing a function, ksh(1) used to exit without
executing the trap set.
This specific check for SIGHUP has been now removed
so that ksh(1) does not exit immediately, but instead
executes the trap set and then exits.
PHCO_17691:
ksh(1) dumps core while executing scripts
having large number of heredocs.
Resolution:
ksh(1) had limited the number of open files at
any time to 20, which was not sufficient in the
case of the script which used a large number of
heredocs. ksh(1) didn't handle the case when
this limit was exceeded, and hence it coredumped.
ksh(1) now allows as many number of open files as
the system allows, i.e. it retrieves the system
configured value for the number of open files per
process and allocates sufficient memory to the
various data structures. Now, ksh(1) does not have
internal restriction on the number of open files
and handles the situation correctly by displaying
appropriate error messages, when the number of
open files is exceeded.
PHCO_16363:
A return statement within a do-while loop
that is in a function, does not return from
the function, but exits only the do-while
loop. Running the following script demonstrates
this fact.
#!/usr/bin/ksh
fxn()
{
cat /etc/passwd | while read line
do
echo $line
return
done
echo after fxn return, still in fxn
}
fxn
echo after fxn
We see the message "after fxn return, still
in fxn" even after the return statement is
executed.
PHCO_16065:
1) ksh does not handle command
substitution of variables of length 2047,
3071, etc. correctly. In the following command,
where variable "stuff" is assigned a string of
length 2047, the contents of resulting string
"str" will be the last 1023 bytes of "stuff".
str=`echo $stuff`
PHCO_15648:
10.20 Ksh subshell exits prematurely on a
uniprocessor. On uniprocessor machines running
one of 10.20, 10.10, 10.01 and 10.0 HP-UX'es,
the subshell run through a script exits by itself
without entering the exit routine.
PHCO_13698:
1) Scripts like the following when sourced, cause
the shell to exit.
echo test | while read r
do
a=$(date)
done
2) POSIX and Korn shell do not wait(2) for zombies
while in vi input mode. Jobs which are started in
the background and exit show up as zombies (defunct)
until the user presses the return key in the xterm
where the job was started.
PHCO_13655:
If set -e is ON, ksh should exit on encountering errors
during processing the word list in a for statement, and
case statement. When the last command in a pipe list
fails also, it should exit if set -e is on. Currently
it is not happening. Scripts like the following should
exit on error.
set -e
for i in `sort a_non_existent_file`
do
echo Hello $i
done
echo "return code is " $? " -> Should not display this."
PHCO_11347:
1) Since file descriptor ERRIO (2) is used in parser, it
resets the i/o stream established with fd=2 when stderr
is closed. This indirectly leads to syntax error while
parsing and hence aborts.
2) trap DEBUG does not behave consistently with command
substitution.
3) Shell builtin ':' (: > file) does not truncate
file when called second time from a function.
4) Korh shell dumps core due to memory fault when
function is defined in a loop.
5) Unread (undo read) character in lexical analyser is
stored in shell data structure and this is added to input
for trap action name is read.
PHCO_11010:
1) When standard input is closed, the i/o channel
established using the file descriptor 0 for the command
substitution is not closed. This further leads ksh to
bus error and hence make ksh dump core when it refers
invalid location in the memory.
2) Korn shell does not clean up temporary files created when
it exits due to receipt of a signal.
PHCO_10719:
1) Since the internal magic cookies (H_UNDO & H_CMDNO) used
in history file were valid multibyte characters, the
cookies were changed to and hence avoid ambiguity when a
history file is read in multibyte locales, the old
history files were simply discarded.
2) When any shell-builtin command returns NULL in command
substitution and the execution trace flag -x is on, then
it takes incorrect output from the I/O stream for next
shell-builtin command substitution.
set -x
FOO=$(whence non_existing_file)
FOO=$(whence ls)
echo $FOO
PHCO_9484:
1) While using in-line command editing, untyped
characters would sometimes appear, most often
^B. These occurred most typically when very
long command lines had been created. Also,
in editing long history lines, especially
near the end of the lines, garbage characters
would appear and the line couldn't be edited
properly.
2) File descriptor 10 was being reserved for use by
the shell, but the file descriptor was opened in a
way that it would remain open across an exec(2)
system call.
3) ksh returns incorrect exit-status when it executes
'exit' command on trap.
PHCO_9088:
1) A trap on EXIT set outside of a function is not
executed if an exit is called from within a
function.
2) cd -P and pwd -P generate nonexistent path names
when the logical path uses symbolic links containing
..
3) ksh hangs when processing "cat bigfile | while read ..."
The right side of the pipe can be any shell command
(while, if, for, etc.)
SR:
8606179356 8606104865 1653298927 8606101547 8606103328
1653299891 5003442533 5003455519 1653302570 1653298422
4701413922 5003428490 5003424754 5003417931 1653239947
1653236851 1653240390 1653240408 4701339309 1653164350
1653174615 5003295741 5003340166 5003359547 1653210948
5003366856 1653205088 4701357939 1653152892 1653216481
Patch Files:
/usr/bin/ksh
/usr/bin/rksh
/usr/share/man/man1.Z/ksh.1
what(1) Output:
/usr/bin/ksh:
$Revision: 78.5.1.70 $
Version 11/16/88
PATCH_10_20: arith.o blok.o ctype.o defs.o edit.o ec
ho.o expand.o fault.o io.o string.o stak.o w
ord.o emacs.o vi.o hpux_rel.o args.o builtin
.o cmd.o main.o msg.o print.o xec.o name.o m
acro.o error.o service.o test.o jobs.o histo
ry.o 02/10/25
/usr/bin/rksh:
$Revision: 78.5.1.70 $
Version 11/16/88
PATCH_10_20: arith.o blok.o ctype.o defs.o edit.o ec
ho.o expand.o fault.o io.o string.o stak.o w
ord.o emacs.o vi.o hpux_rel.o args.o builtin
.o cmd.o main.o msg.o print.o xec.o name.o m
acro.o error.o service.o test.o jobs.o histo
ry.o 02/10/25
/usr/share/man/man1.Z/ksh.1:
None
cksum(1) Output:
3144805926 159744 /usr/bin/ksh
3144805926 159744 /usr/bin/rksh
3561129141 40993 /usr/share/man/man1.Z/ksh.1
Patch Conflicts: None
Patch Dependencies:
s700: 10.20: PHCO_10718
s800: 10.20: PHCO_10718
Hardware Dependencies: None
Other Dependencies:
Since the POSIX sh(1) and the ksh(1) by default share the
same history file it is advised to install the
corresponding patches on all systems that access these.
This is of particular interest in environments that mount
home directories from a central NFS server.
s700: 9.0X: PHCO_12193
s700: 10.00: PHCO_10730 PHCO_10731
s700: 10.01: PHCO_10728 PHCO_10729
s700: 10.10: PHCO_10720 PHCO_10721
s800: 9.0X: PHCO_12193
s800: 10.00: PHCO_10730 PHCO_10731
s800: 10.01: PHCO_10728 PHCO_10729
s800: 10.10: PHCO_10720 PHCO_10721
Supersedes:
PHCO_9088 PHCO_9484 PHCO_10719 PHCO_11010 PHCO_11347 PHCO_13655
PHCO_13698 PHCO_15648 PHCO_16065 PHCO_16363 PHCO_17691 PHCO_20018
Equivalent Patches: None
Patch Package Size: 260 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_27803
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHCO_27803.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHCO_27803. 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_27803.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_27803.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHCO_27803------------------------------------------
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]