|
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
us-support.external.hp.com)Date: Sun Dec 16 2001 - 07:58:20 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:
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 700 10.X patch digest
Created: Sun Dec 16 3:05:32 PST 2001
Table of Contents:
Document ID Title
--------------- -----------
PHSS_25548 s700_800 10.10 CDE Runtime OCT2001 Periodic Patch
PHSS_24421 s700_800 10.X OV OB3.10 patch - MA packet
PHSS_25755 s700_800 10.20 MPower//Web December 2001 Periodic Patch
PHSS_25656 s700_800 10.20 HP JDBC DRIVER 1.15
PHSS_25647 s700_800 10.X OpenMail B.07.00 December 01 Periodic Patch
PHSS_25858 s700_800 10.20 Fortran90 patch B.10.20.40 to B.10.20.48
The documents are listed below.
-------------------------------------------------------------------------------
Document ID: PHSS_25548
Date Loaded: 20011213
Title: s700_800 10.10 CDE Runtime OCT2001 Periodic Patch
Patch Name: PHSS_25548
Patch Description: s700_800 10.10 CDE Runtime OCT2001 Periodic Patch
Creation Date: 01/10/22
Post Date: 01/12/13
Hardware Platforms - OS Releases:
s700: 10.10
s800: 10.10
Products: N/A
Filesets:
CDE.CDE-ENG-A-MAN CDE.CDE-ENG-A-MSG CDE.CDE-MIN CDE.CDE-RUN
CDE.CDE-SHLIBS CDE.CDE-HELP-RUN CDE.CDE-TT
Automatic Reboot?: No
Status: General Release
Critical: No
Path Name: /hp-ux_patches/s700_800/10.X/PHSS_25548
Symptoms:
PHSS_25548:
1. If you pass a file name containing more
than 1024 characters as an argument to
dtaction, dtaction will dump core.
PHSS_25136:
1. Buffer overflow in rpc.ttdbserverd
causes core dump.
PHSS_23355:
1. dtterm problem with -tn option.
2. Buffer overflow in rpc.cmsd.
3. Buffer overflow in help search string causes core
dump.
PHSS_16150:
1) Buffer overflow in dtmail.
2) Buffer overflow in rpc.ttdbserverd.
PHSS_14594:
1) permissions problem with dtappgather.
2) permissions problem with dtprintinfo.
PHSS_13723:
1) Re-release of 'dtappgather'
PHSS_13402:
1) buffer overrun in dtaction.
2) permissions problem with dtappgather.
3) permissions problem with dtsearchpath.
4) Memory leak in dtlogin.
5) Race condition with xdm.
6) rpc.ttdbserverd version mismatch caused by garbage
collection.
7) buffer overrun problem in dtlock.
8) dtaction core dumps when no action found.
PHSS_12137:
1) Fix condition whereby a string copy of an environment
variable can overflow the stack buffer causing various
applications to core dump.
2) CDE screen locker doesn't use DCE authentication to
unlock the screen.
3) CDE:trusted system:screen lock:display hangs after 3
unsucc.tries2unlock
4) CDE:Trusted system:root can't unlock screen lock
5) cde:trusted system:screenlock: unlock by root seen as
unsuccessful try
6) Possibility of disableing user accounts on trusted
system by screen lock
7) dtmail die when a mail message with an attachment is
dropped to dtpad
8) dtmail receipt of certain elm messages can corrupt
mailbox
9) core dump as soon as help/contents asked to xsnapadmin,
or start
10) HP CDE/VUE (newer version) adding 'newline' after
!!emphasized!! text
11) dtwm may hang at reading $HOME/.dt/types/dt.dt under
LANG=ja_JP.eucJP
12) CDE does not log bad login attempts to /var/adm/btmp.
PHSS_11172:
1) Bad patch for dthelptag files in PHSS_9802. dthelptag
dumps core in locales other than C. -verbose option to
dthelptag will print messages indicating unresolved
symbols in libc.1 from the loader.
PHSS_9802:
1) Audit trail in CDE on trusted symptoms doesn't work
correctly.
2) Duplicate symbol names in libDtSvc cause conflicts.
3) The Abbrev shows up in an xref.
4) dthelp parser checkdefault routine has logic flaws.
5) dthelptag errors in sdl file when no source errors
exist.
6) <term> doesn't allow splitting across line ending in
indented text.
7) dthelptag puts empty <entry> in index list.
8) link for xref in ex put in incorrect location..
9) Index does not redisplay topic after choosing a second
different topic.
10) dthelpview can't view a help volume index when one is
empty.
11) dthelpview -man doesn't manage the text widget
correctly if resize ViewW.
12) Dthelpprint uses obsolete option.
13) When -subTopics used, dthelpprint does not print the
sub topics.
14) Selection cancel is failing after scroll in dtterm.
15) Canceling drag operation causes selection to change in
dtterm.
16) After soft or hard reset, dtterm no longer displays
line drawing chars.
17) Dtterm sometimes stops doing full selection
(char->work->line->all)
18) Dtterm sometimes will not allow user to shrink width of
terminal window.
19) Dtterm doesn't remove utmp entry at loggin off from CDE.
20) Dtterm uses utmp id's that clash with those used by
rlogin.
21) Dtfile hangs in ja_JP.SJIS locale when attempting to
edit filenames.
PHSS_9690:
1) It is possible to bypass proper authentication
PHSS_8665:
1) dthelpprint quits with memory fault in
fr_FR.sio88591 locale.
2) dtwm aborts when using lrom under certain conditions
3) dtwm aborts when deleting action from subpanel that
is also on front panel.
4) dtmail doesn't read MPower attachments correctly.
Dragging multiple messages from one mailbox to another
doesn't work.
5) dtmail will randomly abort when performing drag and
drop.
6) Document saved w/ all mime encoding intact in dtmail
if saved as text.
7) Dtmail locks the mail file - this can hang dtmail.
8) dtmail needs transition link: /usr/lib/sendmail ->
/usr/sbin/sendmail.
9) ttsession -p can fail to print data returned from
child.
10) ttsession hangs on pmap_getport() call.
PHSS_7812:
1) 2 user licenses no longer allow unlimited network
logins as it did in Vue.
PHSS_7721:
1) Missing multiple group info in id(1) command.
2) xdmMode does not work for CDE.
3) Default 2-user license desn't count logins as it did
in Vue.
4) Dtterm may hang in Korean and other EUC locales.
5) Dtmail crashes 2nd time a calendar appointment is
opened.
6) Dtlogin in MIT-MAGICCOOKIE env. refuses connection to
local display.
7) Can't create appointments in several locales.
8) in EUC-2byte codesets, it takes 2 backpaces to erase 1
multi-byte character.
9) Dthelpview will memory fault on Vue help volumes if LANG
variable is unset.
10) CDE is vulnerable to denial of service attacks.
PHSS_7138:
1) Dtterm fails to get the certain characters
when LANG=zh_TW.big5 and zh_TW.ccdc.
2) DtHelpDialog Widget displays version mismatch warning.
3) Dtcm crashes when displaying ceratin appointment lists.
4) Dtterm displays incorrect Japanese characters.
5) CDE/VUE apps crash displaying certain bitmaps.
6) Dthelpprint process can hang in EUC locales when
printing browser page.
7) Xtim is unavailable in dticon in zh_TW.eucTW locale.
8) Dtcm crashes when no text is entered in appointment
editor.
9) Libtt returns "Unknown Tt_staus" for valid status codes.
10) User gets no feedback if dtpad can't access a dir.
11) Dtpad unable open any file out of root '/' directory.
12) When invoke a dtterm manually, can't backpsace over
multi-byte characters.
13) Dtcm eventually crashes if default calendar not
accessible.
14) Dtcm has performance & memory overrun problems.
PHSS_6571:
1) Many Dtcm localization errors.
2) Dtcm drag & drop inconsistant.
3) Dtcm dumps core.
4) Memory leaks in Dtwm, Dtfile and Dtsession
5) Dtfile dumps core.
6) Screen saver dialog incosistant in Dtstyle.
7) Front panel gets corrupted.
8) rpc.cmsd reports incorrect or inconsistant data.
9) Incorrect mneumonics on file menu in Dtcm.
10) Missing Dthelpprint app-defaults files for some locales.
11) Several memory leaks in libDtSvc.
12) libcsa leaves dangling callbacks on exit,
causing rpc.cmsd to dump core.
13) libDtHelp not parsing correctly.
Defect Description:
PHSS_25548:
1. Problem with dtaction.
Resolution:
The following are implemented to warn
the user about this -
1. Documented this limitation in the
manpages of dtaction.
2. Restricted the user from passing a
file name containing more than 255
characters as an argument to dtaction.
3. If ABSOLUTE FILE PATH exceeds 1023
characters, then we are exiting the
program after showing the error message.
PHSS_25136:
1. Problem with rpc.ttdbserverd.
Resolution:
Buffer overflow is checked in
rpc.ttdbserverd.
PHSS_23355:
1) dtterm problem.
Resolution:
Error checking has been introduced to check the
dtterm problem with the -tn option.
2) Another problem in rpc.cmsd.
Resolution:
Buffer overflow is checked in rpc.cmsd.
3) Problem in dtprintinfo.
Resolution:
Buffer overflow is prevented in libDtHelp to
avoid core dump.
PHSS_16150:
1) Buffer overflow in dtmail.
2) Buffer overflow in rpc.ttdbserverd.
PHSS_14594:
1) permissions problem with dtappgather.
2) permissions problem with dtprintinfo.
PHSS_13723:
1) Re-release of 'dtappgather'
PHSS_13402:
1) buffer overrun in dtaction.
2) permissions problem with dtappgather.
3) permissions problem with dtsearchpath.
4) Memory leak in dtlogin.
5) Race condition with xdm.
6) rpc.ttdbserverd version mismatch caused by garbage
collection.
7) buffer overrun problem in dtlock.
8) dtaction core dumps when no action found.
PHSS_12137:
1) Fix condition whereby a string copy of an environment
variable can overflow the stack buffer causing various
applications to core dump.
2) CDE screen locker doesn't use DCE authentication to
unlock the screen.
3) CDE:trusted system:screen lock:display hangs after 3
unsucc.tries2unlock
4) CDE:Trusted system:root can't unlock screen lock
5) cde:trusted system:screenlock: unlock by root seen as
unsuccessful try
6) Possibility of disableing user accounts on trusted
system by screen lock
7) dtmail die when a mail message with an attachment is
dropped to dtpad
8) dtmail receipt of certain elm messages can corrupt
mailbox
9) core dump as soon as help/contents asked to xsnapadmin,
or start
10) HP CDE/VUE (newer version) adding 'newline' after
!!emphasized!! text
11) dtwm may hang at reading $HOME/.dt/types/dt.dt under
LANG=ja_JP.eucJP
12) CDE does not log bad login attempts to /var/adm/btmp.
PHSS_11172:
1) Bad patch for dthelptag files in PHSS_9802. dthelptag
dumps core in locales other than C. -verbose option to
dthelptag will print messages indicating unresolved
symbols in libc.1 from the loader.
PHSS_9802:
1) Audit trail in CDE on trusted symptoms doesn't work
correctly.
2) Duplicate symbol names in libDtSvc cause conflicts.
3) The Abbrev shows up in an xref.
4) dthelp parser checkdefault routine has logic flaws.
5) dthelptag errors in sdl file when no source errors
exist.
6) <term> doesn't allow splitting across line ending in
indented text.
7) dthelptag puts empty <entry> in index list.
8) link for xref in ex put in incorrect location..
9) Index does not redisplay topic after choosing a second
different topic.
10) dthelpview can't view a help volume index when one is
empty.
11) dthelpview -man doesn't manage the text widget
correctly if resize ViewW.
12) Dthelpprint uses obsolete option.
13) When -subTopics used, dthelpprint does not print the
sub topics.
14) Selection cancel is failing after scroll in dtterm.
15) Canceling drag operation causes selection to change in
dtterm.
16) After soft or hard reset, dtterm no longer displays
line drawing chars.
17) Dtterm sometimes stops doing full selection
(char->work->line->all)
18) Dtterm sometimes will not allow user to shrink width of
terminal window.
19) Dtterm doesn't remove utmp entry at loggin off from CDE.
20) Dtterm uses utmp id's that clash with those used by
rlogin.
21) Dtfile hangs in ja_JP.SJIS locale when attempting to
edit filenames.
PHSS_9690:
1) It is possible to bypass proper authentication
PHSS_8665:
1) dthelpprint quits with memory fault in
fr_FR.sio88591 locale.
2) dtwm aborts when using lrom under certain conditions
3) dtwm aborts when deleting action from subpanel that
is also on front panel.
4) dtmail doesn't read MPower attachments correctly.
Dragging multiple messages from one mailbox to another
doesn't work.
5) dtmail will randomly abort when performing drag and
drop.
6) Document saved w/ all mime encoding intact in dtmail
if saved as text.
7) Dtmail locks the mail file - this can hang dtmail.
8) dtmail needs transition link: /usr/lib/sendmail ->
/usr/sbin/sendmail.
9) ttsession -p can fail to print data returned from
child.
10) ttsession hangs on pmap_getport() call.
PHSS_7812:
1) 2 user licenses no longer allow unlimited network
logins as it did in Vue.
PHSS_7721:
1) Missing multiple group info in id(1) command.
2) xdmMode does not work for CDE.
3) Default 2-user license desn't count logins as it did
in Vue.
4) Dtterm may hang in Korean and other EUC locales.
5) Dtmail crashes 2nd time a calendar appointment is
opened.
6) Dtlogin in MIT-MAGICCOOKIE env. refuses connection to
local display.
7) Can't create appointments in several locales.
8) in EUC-2byte codesets, it takes 2 backpaces to erase 1
multi-byte character.
9) Dthelpview will memory fault on Vue help volumes if LANG
variable is unset.
10) CDE is vulnerable to denial of service attacks.
PHSS_7138:
1) Dtterm fails to get the certain characters
when LANG=zh_TW.big5 and zh_TW.ccdc.
2) DtHelpDialog Widget displays version mismatch warning.
3) Dtcm crashes when displaying ceratin appointment lists.
4) Dtterm displays incorrect Japanese characters.
5) CDE/VUE apps crash displaying certain bitmaps.
6) Dthelpprint process can hang in EUC locales when
printing browser page.
7) Xtim is unavailable in dticon in zh_TW.eucTW locale.
8) Dtcm crashes when no text is entered in appointment
editor.
9) Libtt returns "Unknown Tt_staus" for valid status codes.
10) User gets no feedback if dtpad can't access a dir.
11) Dtpad unable open any file out of root '/' directory.
12) When invoke a dtterm manually, can't backpsace over
multi-byte characters.
13) Dtcm eventually crashes if default calendar not
accessible.
14) Dtcm has performance & memory overrun problems.
PHSS_6571:
1) Many Dtcm localization errors.
2) Dtcm drag & drop inconsistant.
3) Dtcm dumps core.
4) Memory leaks in Dtwm, Dtfile and Dtsession
5) Dtfile dumps core.
6) Screen saver dialog incosistant in Dtstyle.
7) Front panel gets corrupted.
8) rpc.cmsd reports incorrect or inconsistant data.
9) Incorrect mneumonics on file menu in Dtcm.
10) Missing Dthelpprint app-defaults files for some locales.
11) Several memory leaks in libDtSvc.
12) libcsa leaves dangling callbacks on exit,
causing rpc.cmsd to dump core.
13) libDtHelp not parsing correctly.
SR:
8606221993 8606215512 8606155712 8606177477 8606183236
4701398297 4701398529 4701386417 4701386425 4301386433
4701314070 4701312231 4701312330 4701312181 4701312199
4701312207 4701314047 4701312215 4701312223 4701312124
4701314195 4701312264 4701312132 4701312272 4701312280
4701314088 4701312298 4701312140 4701312306 4701312314
4701312157 4701312348 4701312603 4701312165 4701314062
4701312173 4701312371 4701319525 1653161489 5003312785
1653169334 5003314740 4701327726 1653173344 5003323287
5003307769 5003321679 5003321943 1653181099 5003334722
4701343012 5003342196 5003342246 5003352997 5003354209
5003352930 5003356279 5003356287 5003356303 5003357632
5003358358 5003362095 1653211110 4701364158 4701373860
5003394981 5003393801 4701376855 5003392720
Patch Files:
/usr/dt/share/man/man1/dtaction.1
/usr/dt/lib/nls/msg/C/dtact.cat
/usr/dt/bin/tttar
/usr/dt/bin/ttdbck
/usr/dt/bin/dtaction
/usr/dt/bin/dtappgather
/usr/dt/bin/dtcalc
/usr/dt/bin/dtchooser
/usr/dt/bin/dtcm
/usr/dt/bin/dtcm_admin
/usr/dt/bin/dtcm_delete
/usr/dt/bin/dtcm_editor
/usr/dt/bin/dtcm_insert
/usr/dt/bin/dtcm_lookup
/usr/dt/bin/dtfile
/usr/dt/bin/dtfile_copy
/usr/dt/bin/dtfplist
/usr/dt/bin/dtgreet
/usr/dt/bin/dthelpprint
/usr/dt/bin/dthelp_ctag1
/usr/dt/bin/dthelp_htag1
/usr/dt/bin/dthelp_htag2
/usr/dt/bin/dthelptag
/usr/dt/bin/dticon
/usr/dt/bin/dtlogin
/usr/dt/bin/dtmail
/usr/dt/bin/dtpad
/usr/dt/bin/dtprintinfo
/usr/dt/bin/dtsearchpath
/usr/dt/bin/dtsession
/usr/dt/bin/dtspcd
/usr/dt/bin/dtstyle
/usr/dt/bin/dtterm
/usr/dt/bin/dtwm
/usr/dt/bin/rpc.cmsd
/usr/dt/bin/rpc.ttdbserver
/usr/dt/bin/ttsession
/usr/dt/bin/Xsession
/usr/dt/config/Xsession.d/0030.dttmpdir
/usr/dt/lib/libDtHelp.1
/usr/dt/lib/libDtSvc.1
/usr/dt/lib/libcsa.1
/usr/dt/lib/libtt.1
/usr/dt/lib/libDtWidget.1
/usr/dt/lib/libDtTerm.1
/usr/dt/app-defaults/C/Dtcm
/usr/dt/app-defaults/C/Dthelpprint
/usr/dt/app-defaults/C/Dtmail
/usr/dt/appconfig/types/C/dtfile.dt
what(1) Output:
/usr/dt/share/man/man1/dtaction.1:
None
/usr/dt/lib/nls/msg/C/dtact.cat:
None
/usr/dt/lib/libDtHelp.1:
libDtHelp: $Revision: 2.12 $
X Window System, Version 11 R5+ HP-UX B.10.10.00 Feb
ruary 2001 Patch Release
(build date: Fri Mar 16 13:51:29 IST 2001)
/usr/dt/lib/libDtSvc.1:
libDtSvc: $Revision: 1.5 $
X Window System, Version 11 R5+ HP-UX B.10.10.00 Nov
1997_A Patch Release
(build date: Tue Dec 2 12:47:09 PST 1997)
/usr/dt/lib/libDtTerm.1:
DtTermPrimitiveWidget: $Revision: 1.196 $
libDtTerm: $Revision: 1.172 $
X Window System, Version 11 R5+ HP-UX B.10.10.00 Feb
ruary 2001 Patch Release
(build date: Mon Feb 19 16:41:38 IST 2001)
/usr/dt/lib/libDtWidget.1:
libDtWidget: $Revision: 1.4 $
X Window System, Version 11 R5+ HP-UX B.10.10.00 Mar
1997 Patch Release
(build date: Mon Feb 24 10:08:45 PST 1997)
/usr/dt/lib/libcsa.1:
Common Desktop Environment Version 1
(build date: Sat Dec 30 00:24:14 PST 1995)
/usr/dt/lib/libtt.1:
Common Desktop Environment Version 1
(build date: Thu Mar 28 13:29:54 PST 1996)
/usr/dt/bin/dthelp_ctag1:
X Window System, Version 11 R5+ HP-UX B.10.10.00 Mar
1997 Patch Release
(build date: Thu Feb 20 16:37:17 PST 1997)
dthelp_ctag1: $Revision: 1.1 $
/usr/dt/bin/dthelp_htag1:
X Window System, Version 11 R5+ HP-UX B.10.10.00 Mar
1997 Patch Release
(build date: Thu Feb 20 16:22:34 PST 1997)
dthelp_htag1: $Revision: 1.1 $
/usr/dt/bin/dthelp_htag2:
X Window System, Version 11 R5+ HP-UX B.10.10.00 Mar
1997 Patch Release
(build date: Thu May 29 16:42:45 PDT 1997)
dthelp_htag2: $Revision: 1.1 $
/usr/dt/bin/dthelpprint:
X Window System, Version 11 R5+ HP-UX B.10.10.00 Mar
1997 Patch Release
(build date: Fri Feb 21 09:57:55 PST 1997)
dthelpprint: $Revision: 1.2 $
/usr/dt/bin/dthelptag:
X Window System, Version 11 R5+ HP-UX B.10.10.00 Mar
1997 Patch Release
dthelptag: $Revision: 1.24 $
/usr/dt/bin/dtspcd:
X Window System, Version 11 R5+ HP-UX B.10.10.00 Mar
1997 Patch Release
(build date: Wed Feb 19 19:42:15 PST 1997)
dtspcd: $Revision: 1.2 $
/usr/dt/bin/rpc.ttdbserver:
X Window System, Version 11 R5+ HP-UX B.10.10.00 Sep
tember 2001 Patch Release
(build date: Tue Sep 4 13:39:59 IST 2001)
rpc.ttdbserver: $Revision: 1.1 $
/usr/dt/bin/Xsession:
None
/usr/dt/bin/dtaction:
X Window System, Version 11 R5+ HP-UX B.10.10.00 Oct
ober 2001 Patch Release
(build date: Thu Oct 18 18:10:06 IST 2001)
dtaction: $Revision: 1.1 $
/usr/dt/bin/dtappgather:
X Window System, Version 11 R5+ HP-UX B.10.10.00 Mar
1998_A Patch Release
(build date: Wed Apr 1 10:39:56 IST 1998)
dtappgather: $Revision: 1.1 $
/usr/dt/bin/dtcalc:
X Window System, Version 11 R5+ HP-UX B.10.10.00 Mar
1997 Patch Release
(build date: Mon Feb 24 15:41:51 PST 1997)
dtcalc: $Revision: 2.0 $
/usr/dt/bin/dtchooser:
Common Desktop Environment Version 1
(build date: Fri Jun 7 08:28:49 PDT 1996)
/usr/dt/bin/dtcm:
Common Desktop Environment Version 1
(build date: Fri Jun 7 11:20:17 PDT 1996)
dtcm: $Revision: 1.57 $
/usr/dt/bin/dtcm_admin:
Common Desktop Environment Version 1
(build date: Thu Mar 28 17:02:23 PST 1996)
dtcm_admin: $Revision: 1.2 $
/usr/dt/bin/dtcm_delete:
Common Desktop Environment Version 1
(build date: Thu Mar 28 17:01:38 PST 1996)
dtcm_delete: $Revision: 1.2 $
/usr/dt/bin/dtcm_editor:
Common Desktop Environment Version 1
(build date: Fri Jun 7 11:21:47 PDT 1996)
dtcm_editor: $Revision: 1.10 $
/usr/dt/bin/dtcm_insert:
Common Desktop Environment Version 1
(build date: Thu Mar 28 17:01:55 PST 1996)
dtcm_insert: $Revision: 1.5 $
/usr/dt/bin/dtcm_lookup:
Common Desktop Environment Version 1
(build date: Thu Mar 28 17:02:09 PST 1996)
dtcm_lookup: $Revision: 1.2 $
/usr/dt/bin/dtfile:
X Window System, Version 11 R5+ HP-UX B.10.10.00 R5
July 1997 Point Patch Release
(build date: Tue Sep 2 10:34:24 PDT 1997)
dtfile: $Revision: 2.1 $
/usr/dt/bin/dtfile_copy:
X Window System, Version 11 R5+ HP-UX B.10.10.00 Mar
1997 Patch Release
(build date: Wed Feb 19 17:38:43 PST 1997)
dtfile_copy: $Revision: 1.2 $
/usr/dt/bin/dtfplist:
X Window System, Version 11 R5+ HP-UX B.10.10.00 Mar
1997 Patch Release
(build date: Wed Feb 19 21:01:02 PST 1997)
dtfplist: $Revision: 1.1 $
/usr/dt/bin/dtgreet:
Common Desktop Environment Version 1
(build date: Fri Jun 7 08:28:18 PDT 1996)
dtgreet: $Revision: 1.5 $
/usr/dt/bin/dticon:
X Window System, Version 11 R5+ HP-UX B.10.10.00 Mar
1997 Patch Release
(build date: Mon Feb 24 15:45:39 PST 1997)
dticon: $Revision: 1.7 $
/usr/dt/bin/dtlogin:
X Window System, Version 11 R5+ HP-UX B.10.10.00 R5
July 1997 Point Patch Release
(build date: Tue Aug 19 10:42:45 PDT 1997)
dtlogin: $Revision: 1.16 $
/usr/dt/bin/dtmail:
X Window System, Version 11 R5+ HP-UX B.10.10.00 Aug
ust 1998 Point Patch Release
(build date: Wed Aug 12 12:05:25 IST 1998)
dtmail: $Revision: 1.3 $
/usr/dt/bin/dtpad:
X Window System, Version 11 R5+ HP-UX B.10.10.00 Mar
1997 Patch Release
(build date: Mon Feb 24 15:49:36 PST 1997)
dtpad: $Revision: 3.0 $
/usr/dt/bin/dtprintinfo:
X Window System, Version 11 R5+ HP-UX B.10.10.00 Mar
1998_A Patch Release
(build date: Tue Mar 31 15:44:03 IST 1998)
dtprintinfo: $Revision: 1.1 $
/usr/dt/bin/dtsearchpath:
X Window System, Version 11 R5+ HP-UX B.10.10.00 Nov
1997_A Patch Release
(build date: Tue Dec 2 12:18:40 PST 1997)
dtsearchpath: $Revision: 1.1 $
/usr/dt/bin/dtsession:
X Window System, Version 11 R5+ HP-UX B.10.10.00 Nov
1997_A Patch Release
(build date: Tue Dec 9 16:35:55 PST 1997)
dtsession: $Revision: 2.0 $
/usr/dt/bin/dtstyle:
X Window System, Version 11 R5+ HP-UX B.10.10.00 Mar
1997 Patch Release
(build date: Wed Feb 19 19:49:43 PST 1997)
dtstyle: $Revision: 1.4 $
/usr/dt/bin/dtterm:
X Window System, Version 11 R5+ HP-UX B.10.10.00 Mar
1997 Patch Release
(build date: Wed Feb 19 20:17:15 PST 1997)
dtterm: $Revision: 1.3 $
/usr/dt/bin/dtwm:
X Window System, Version 11 R5+ HP-UX B.10.10.00 Mar
1997 Patch Release
(build date: Wed Feb 19 21:00:00 PST 1997)
dtwm: $Revision: 1.11 $
/usr/dt/bin/rpc.cmsd:
X Window System, Version 11 R5+ HP-UX B.10.10.00 Feb
ruary 2001 Patch Release
(build date: Sat Mar 3 02:08:40 IST 2001)
rpc.cmsd: $Revision: 1.7 $
/usr/dt/bin/ttsession:
X Window System, Version 11 R5+ HP-UX B.10.10.00 Nov
1996 Patch Release
(build date: Sat Oct 5 14:47:33 PDT 1996)
ttsession: $Revision: 1.1 $
/usr/dt/bin/tttar:
X Window System, Version 11 R5+ HP-UX B.10.10.00 Sep
tember 2001 Patch Release
(build date: Tue Sep 4 13:40:07 IST 2001)
tttar: $Revision: 1.1 $
/usr/dt/bin/ttdbck:
X Window System, Version 11 R5+ HP-UX B.10.10.00 Sep
tember 2001 Patch Release
(build date: Tue Sep 4 13:39:26 IST 2001)
ttdbck: $Revision: 1.1 $
/usr/dt/app-defaults/C/Dtcm:
None
/usr/dt/app-defaults/C/Dthelpprint:
Common Desktop Environment 1.0
/usr/dt/app-defaults/C/Dtmail:
Dtmail 1.2 21 Oct 1994
/usr/dt/appconfig/types/C/dtfile.dt:
None
/usr/dt/config/Xsession.d/0030.dttmpdir:
Common Desktop Environment Version 1
0030.dttmpdir $Revision: 1.11 $
cksum(1) Output:
1744133972 5371 /usr/dt/share/man/man1/dtaction.1
3409963115 693 /usr/dt/lib/nls/msg/C/dtact.cat
1898383551 872448 /usr/dt/lib/libDtHelp.1
3209702174 659456 /usr/dt/lib/libDtSvc.1
3837670632 466944 /usr/dt/lib/libDtTerm.1
4225865634 360448 /usr/dt/lib/libDtWidget.1
2398232244 331776 /usr/dt/lib/libcsa.1
3630454538 1097728 /usr/dt/lib/libtt.1
491015219 352256 /usr/dt/bin/dthelp_ctag1
165806017 389120 /usr/dt/bin/dthelp_htag1
2443317200 286720 /usr/dt/bin/dthelp_htag2
2817263688 57344 /usr/dt/bin/dthelpprint
1158262163 12335 /usr/dt/bin/dthelptag
2695247990 163840 /usr/dt/bin/dtspcd
146203363 307200 /usr/dt/bin/rpc.ttdbserver
177076278 13965 /usr/dt/bin/Xsession
14818965 45056 /usr/dt/bin/dtaction
522075164 98304 /usr/dt/bin/dtappgather
646638294 241664 /usr/dt/bin/dtcalc
2490143831 94208 /usr/dt/bin/dtchooser
1494842623 737280 /usr/dt/bin/dtcm
770168528 274432 /usr/dt/bin/dtcm_admin
2006058588 274432 /usr/dt/bin/dtcm_delete
1948035221 360448 /usr/dt/bin/dtcm_editor
3271058272 286720 /usr/dt/bin/dtcm_insert
2402656636 274432 /usr/dt/bin/dtcm_lookup
2570167977 724992 /usr/dt/bin/dtfile
3760929157 77824 /usr/dt/bin/dtfile_copy
3568712050 65536 /usr/dt/bin/dtfplist
1520857556 86016 /usr/dt/bin/dtgreet
2264690634 188416 /usr/dt/bin/dticon
3803968620 167936 /usr/dt/bin/dtlogin
2604827949 995328 /usr/dt/bin/dtmail
582461619 114688 /usr/dt/bin/dtpad
301505385 475136 /usr/dt/bin/dtprintinfo
2814852970 143360 /usr/dt/bin/dtsearchpath
1133473973 167936 /usr/dt/bin/dtsession
3321248574 217088 /usr/dt/bin/dtstyle
1502344822 53248 /usr/dt/bin/dtterm
4271016744 569344 /usr/dt/bin/dtwm
1698605150 360448 /usr/dt/bin/rpc.cmsd
1036858789 253952 /usr/dt/bin/ttsession
1181251434 77824 /usr/dt/bin/tttar
2257362157 393216 /usr/dt/bin/ttdbck
1783216485 4695 /usr/dt/app-defaults/C/Dtcm
2580243029 8200 /usr/dt/app-defaults/C/Dthelpprint
524897624 6061 /usr/dt/app-defaults/C/Dtmail
1715966790 22693 /usr/dt/appconfig/types/C/dtfile.dt
4182997342 3328 /usr/dt/config/Xsession.d/0030.dttmpdir
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_6571 PHSS_7138 PHSS_7721 PHSS_7812 PHSS_8665 PHSS_9690
PHSS_9802 PHSS_11172 PHSS_12137 PHSS_13402 PHSS_13723 PHSS_14594
PHSS_16150 PHSS_23355 PHSS_25136
Equivalent Patches:
PHSS_25192:
s700: 10.20
s800: 10.20
PHSS_25194:
s700: 11.00
s800: 11.00
PHSS_25196:
s700: 11.11
s800: 11.11
PHSS_25197:
s700: 11.11
s800: 11.11
Patch Package Size: 13030 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_25548
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHSS_25548.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHSS_25548. 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_25548.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_25548.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
Please note:
The CDE environment must not be running when this
patch is installed.
If it is, you will receive warnings that text files
are busy. SD will move these aside and place the
new files in the appropriate location, but it is
recomended that CDE first be shutdown prior to patch
installation.
Also:
The memory leak in dtlogin and the race condition
with xdm will reappear in this patch as the dtlogin
component has been replaced with the one that was
in PHSS_12137 patch. This is being done due to the
problems discovered with the later versions of dtlogin.
-----End of Document ID: PHSS_25548------------------------------------------
Document ID: PHSS_24421
Date Loaded: 20011213
Title: s700_800 10.X OV OB3.10 patch - MA packet
Patch Name: PHSS_24421
Patch Description: s700_800 10.X OV OB3.10 patch - MA packet
Creation Date: 01/12/11
Post Date: 01/12/13
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.10
Filesets:
OMNIBACK-II.OMNI-ACS-P,A.03.10
OMNIBACK-II.OMNI-DAS-P,A.03.10
OMNIBACK-II.OMNI-HPUX-P,A.03.10
OMNIBACK-II.OMNI-OTHUX-P,A.03.10
Automatic Reboot?: No
Status: General Release
Critical: No
Path Name: /hp-ux_patches/s700_800/10.X/PHSS_24421
Symptoms:
PHSS_24421:
Id = JAGad15060, NSMex03524 SR: 8606145724, B554000653
Backup fails with an error:
"Cannot unload the drive "0,0,2,3"
STATUS_LOCKID_NOT_FOUND"
Id = NSMbb36866 SR: B555007360
Import of OmniBack II A.02.55 media with omnistream
objects to any later version of OmniBack II corrupts
the Monitor GUI.
Id = NSMbb40166 SR: H555005004
Multiple "STATING Media Agent" messages appear at the
end of the backup session.
Id = NSMex03031 SR: B554000160
The restore of OmniStorage objects fails with an error:
"Can not backspace block ([5] I/O error)".
Id = NSMex03572 SR: B554000701
Backup fails with an error:
"Invalid physical device type - aborting".
Id = NSMex03613 SR: B554000744
Backup to MO media fails with an error:
"Medium has no capacity.".
Id = NSMex03775 SR: B554000906
Port used to connect to has a value 0.
Id = NSMex03944 SR: H555004912
In case of a bad drive, the debug.log on Media Agent
system fills up.
Id = NSMex03967 SR: H555004450
Barcode scan of a library connected to SAN fails.
Id = NSMex04021 SR: H555005353
OmniBack II does not correctly recognize that a drive
needs cleaning.
Id = NSMex03297 SR: B554000426
SCSI-II Library does not work on Sun Solaris platform.
Id = NSMex03734 SR: H555004009
Blank tapes are causing duplicates in the Media
Management database.
Id = NSMex04530 SR: H555006362
Media import sometimes fails due to I/O errors.
PHSS_21642:
Id = HSLco12763
OmniBack II doesn't report a dirty drive on systems
other than HP-UX even if the cleanme signal on the
device is pending.
Id = NSMbb34346
All operations with a SCSI-II library fail with an
error:
"Cannot open exchanger control device
([4] Interrupted system call)"
Id = NSMex02763
SCSI Library cannot unload DLT tape cartridge after
the tape rewind.
Id = NSMex02842
Initialization of a DLT tape fails with an error:
"Unsupported device => aborting"
Id = NSMex03125
Backup aborts with Media Agent error:
"Can not write to device
([28] No space left on device)"
Id = NSMex03137
GRAU library cannot use more than 15 drives.
Id = NSMex03159
Backup to a GRAU library fails with error:
"Got unexpected close from BMA"
Id = NSMex03330
Omnimcopy copies data even if the source tape is
corrupted.
Id = NSMex03391
Backup to a DLT8000 drive fails with an error:
"Cannot open device".
Id = NSMex02816 SSPUX310_008
Device intermittently report an I/O error and the tape
gets stuck in the drive.
Id = NSMex03019 SSPUX310_008
Positioning to EOD on STK 9840 drive takes too long.
Id = NSMex03096 SSPUX310_015
Backup to MO device fails with an error:
"Can not write to device
([6] No such device or address)"
Id = NSMex03106 SSPUX310_017
QUERY command doesn't update the OmniBack
database with repository status of ACSLS Library
if there are STK 9840 media cartridges in the library.
([4] Interrupted system call)"
Id = NSMex02763
SCSI Library cannot unload DLT tape cartridge after
the tape rewind.
Id = NSMex02842
Initialization of a DLT tape fails with an error:
"Unsupported device => aborting"
Id = NSMex03125
Backup aborts with Media Agent error:
"Can not write to device
([28] No space left on device)"
Id = NSMex03137
GRAU library cannot use more than 15 drives.
Id = NSMex03159
Backup to a GRAU library fails with error:
"Got unexpected close from BMA"
Id = NSMex03330
Omnimcopy copies data even if the source tape is
corrupted.
Id = NSMex03391
Backup to a DLT8000 drive fails with an error:
"Cannot open device".
Id = NSMex02816 SSPUX310_008
Device intermittently report an I/O error and the tape
gets stuck in the drive.
Id = NSMex03019 SSPUX310_008
Positioning to EOD on STK 9840 drive takes too long.
Id = NSMex03096 SSPUX310_015
Backup to MO device fails with an error:
"Can not write to device
([6] No such device or address)"
Id = NSMex03106 SSPUX310_017
QUERY command doesn't update the OmniBack
database with repository status of ACSLS Library
if there are STK 9840 media cartridges in the library.
([4] Interrupted system call)"
Id = NSMex02763
SCSI Library cannot unload DLT tape cartridge after
the tape rewind.
Id = NSMex02842
Initialization of a DLT tape fails with an error:
"Unsupported device => aborting"
Id = NSMex03125
Backup aborts with Media Agent error:
"Can not write to device
([28] No space left on device)"
Id = NSMex03137
GRAU library cannot use more than 15 drives.
Id = NSMex03159
Backup to a GRAU library fails with error:
"Got unexpected close from BMA"
Id = NSMex03330
Omnimcopy copies data even if the source tape is
corrupted.
Id = NSMex03391
Backup to a DLT8000 drive fails with an error:
"Cannot open device".
Id = NSMex02816 SSPUX310_008
Device intermittently report an I/O error and the tape
gets stuck in the drive.
Id = NSMex03019 SSPUX310_008
Positioning to EOD on STK 9840 drive takes too long.
Id = NSMex03096 SSPUX310_015
Backup to MO device fails with an error:
"Can not write to device
([6] No such device or address)"
Id = NSMex03106 SSPUX310_017
QUERY command doesn't update the OmniBack
database with repository status of ACSLS Library
if there are STK 9840 media cartridges in the library.
([4] Interrupted system call)"
Id = NSMex02763
SCSI Library cannot unload DLT tape cartridge after
the tape rewind.
Id = NSMex02842
Initialization of a DLT tape fails with an error:
"Unsupported device => aborting"
Id = NSMex03125
Backup aborts with Media Agent error:
"Can not write to device
([28] No space left on device)"
Id = NSMex03137
GRAU library cannot use more than 15 drives.
Id = NSMex03159
Backup to a GRAU library fails with error:
"Got unexpected close from BMA"
Id = NSMex03330
Omnimcopy copies data even if the source tape is
corrupted.
Id = NSMex03391
Backup to a DLT8000 drive fails with an error:
"Cannot open device".
Id = NSMex02816 SSPUX310_008
Device intermittently report an I/O error and the tape
gets stuck in the drive.
Id = NSMex03019 SSPUX310_008
Positioning to EOD on STK 9840 drive takes too long.
Id = NSMex03096 SSPUX310_015
Backup to MO device fails with an error:
"Can not write to device
([6] No such device or address)"
Id = NSMex03106 SSPUX310_017
QUERY command doesn't update the OmniBack
database with repository status of ACSLS Library
if there are STK 9840 media cartridges in the library.
([4] Interrupted system call)"
Id = NSMex02763
SCSI Library cannot unload DLT tape cartridge after
the tape rewind.
Id = NSMex02842
Initialization of a DLT tape fails with an error:
"Unsupported device => aborting"
Id = NSMex03125
Backup aborts with Media Agent error:
"Can not write to device
([28] No space left on device)"
Id = NSMex03137
GRAU library cannot use more than 15 drives.
Id = NSMex03159
Backup to a GRAU library fails with error:
"Got unexpected close from BMA"
Id = NSMex03330
Omnimcopy copies data even if the source tape is
corrupted.
Id = NSMex03391
Backup to a DLT8000 drive fails with an error:
"Cannot open device".
Id = NSMex02816 SSPUX310_008
Device intermittently report an I/O error and the tape
gets stuck in the drive.
Id = NSMex03019 SSPUX310_008
Positioning to EOD on STK 9840 drive takes too long.
Id = NSMex03096 SSPUX310_015
Backup to MO device fails with an error:
"Can not write to device
([6] No such device or address)"
Id = NSMex03106 SSPUX310_017
QUERY command doesn't update the OmniBack
database with repository status of ACSLS Library
if there are STK 9840 media cartridges in the library.
Defect Description:
PHSS_24421:
Id = JAGad15060, NSMex03524
If any media management operation (for example, scan
or init) is started during a backup to STK Silo
Library, Media Management Agent fails and unlocks the
drive. When the backup is finished, Backup Media Agent
tries to unlock drive and fails because it is already
unlocked by Media Management Agent.
Resolution:
Media Management Agent does not unlock the drive that
it failed to lock.
Id = NSMbb36866
Incorrect conversion of object's backup type from
OmniBack II A.02.55 tape format causes the GUI to
display senseless messages in "Backup type" field.
Resolution:
Conversion of OmniBack II A.02.55 tape format improved.
Id = NSMbb40166
If Media Agent is unable to unload the drive from a
STK Library, the Utility Media Agent (UMA) improperly
finishes and is restarted for 10 times.
Resolution:
UMA properly finishes its actions in case of problems
with STK Library.
Id = NSMex03031
Incorrect positioning to a requested block position
causes restore failure.
Resolution:
Repositioning is implemented in the Restore Media
Agent.
Id = NSMex03572
Table of supported devices was limited to 50. Media
Agent was not able to check .devtab file for additional
devices because the table was too big.
Resolution:
Table of supported devices is increased.
Id = NSMex03613
OmniBack II fails to calculate MO medium capacity for
MO devices connected to a HP-UX system with "HPPB" bus.
Resolution:
Capacity calculating is improved.
Part of SSPUX310_045.
Id = NSMex03775
Port returned by getservbyname command on Novell
NetWare contains the port value in the higher order
word.
Resolution:
Shift returnes port value.
Id = NSMex03944
In case that a drive is bad, it is possible that Media
Agent runs into a loop and fills up the debug.log with
error messages.
Resolution:
A posibble loop is removed and exchanged with five
re-tries.
Id = NSMex03967
Incorrect device name is used for barcode scan
operation if a library is connected to SAN.
Resolution:
Correct device name is used for barcode scanning.
Id = NSMex04021
OmniBack II does not check TapeAlert report
correctly, so it is not able to recognize that
drive needs cleaning.
Resolution:
Media Agent is changed in order to check TapeAlert
report correctly.
Id = NSMex03297
sst driver does not work on 64-bit Sun Solaris system.
Resolution:
New sst driver sst.64 is added to package.
Id = NSMex03734
If Media Agent is unable to read Medium Header ID,
it report new Medium ID which causes duplicates to
appear in the Media Management database.
Resolution:
If Media Agent is unable to read Medium Header ID
then the buffer for ID is reset to 0.
Id = NSMex04530
Media import uses a lot of search operations in
order to achieve better performance. In case of
bad quality of drives or tapes, it sometimes fails
with an I/O error.
Resolution:
New OB2 environment variable is introduced:
OB2NOSEEKIMPORT.
If this variable is set to 1, Media Agent will read
through the complete tape and it will not use any
search operations.
This option reduces the chances of experiencing
I/O errors during media import, but its performance
is 3-4 times slower.
If OB2NOSEEKIMPORT is set and the tape contains
the "OB-crc" field, not only the tape is verified but
also the "OB-crc". Since a copied tape (omnimcopy)
will contain "OB-crc" field as well if the source tape
did contain "OB-crc" fields, importing such a tape
will also be "OB-crc" checked.
Part of SSPUX310_062.
PHSS_21642:
Id = HSLco12763
Cleanme signal handling is only implemented for HP-UX
platforms.
Resolution:
Cleanme signal handling has been applied to other UX
platforms.
Id = NSMbb34346
Media agent does not handle the option "SCSI Reserve/
Release (robotic control)" correctly.
Resolution:
Media Agent option handling has been improved.
Id = NSMex02763
SCSI Library can not unload DLT tape cartridge after
the tape rewind in case previous offline operation
failed.
Resolution:
Media Agent now checks the offline operation exit
status before unloading the medium.
Id = NSMex02842
If a Quantum DLT device is used then any OB2 operation
fails with an error: "Unsupported device => aborting".
Resolution:
Devices with Product ID "Quantum" and "QUANTUM" are now
both recognized by OmniBack.
Id = NSMex03125
Some devices report an errno=ENOSPC if a write reaches
the virtual end of medium, instead of returning 0 as
most devices do. OmniBack II then handles this as an
error.
Resolution:
To use the write error as a signal for virtual end of
medium the environment variable OB2NOVIRTUALEOM in the
.omnirc on Media Agent client must be set:
OB2NOVIRTUALEOM=1
Id = NSMex03137
The function aci_drivestatus() only allows using up to
15 drives.
Resolution:
New function aci_drivestatus2() enables using up to 255
drives in a GRAU library.
Id = NSMex03159
With the latest DAS Media Agents, new DAS API function
call is used in order to support new libraries with more
than 15 drives. As this function call is not supported
in older APIs, new Media Agent does not work with old
libraries.
Resolution:
New OB2 variable is introduced: OB2DASDRIVESTATUS2. If
this variable is set to 1, Media Agent support libraries
with >15 drives, otherwise old libraries are supported.
Id = NSMex03330
Omnimcopy command does not check whether the source
tape is corrupted or not. Because of that it copies
the source tape to the target tape even if the source
tape is corrupted.
Resolution:
When copying the tape, OmniBack II checks the CRC of
the data read from the source tape.
Id = NSMex03391
If a DLT8000 is connected to HP-UX machines with class
higher than L, then the backup to the device fails with
an error:
"Cannot open device".
Resolution:
A special environment variable for the Media Agent has
been introduced for specifying a timeout when waiting
for the device to become ready. Edit the file
/opt/omni/.omnirc on the MA host and specify the
following variable:
OB2DEVSLEEP=(seconds).
The "seconds" can set to the value between 5 and 20.
Id = NSMex02816 SSPUX310_008
If a rewind or offline operation fails after an I/O
error, the tape will get stuck in the drive.
Resolution:
With setting OB2REWINDRETRY and OB2REWINDSLEEP
variables in the .omnirc file on the Media Agent host,
the rewind/offline will retry if it fails.
Id = NSMex03019 SSPUX310_008
Seek to EOD is performed in for loop with jump for one
filemark until the EOD is reached. This can be very
time consuming.
Resolution:
Jump to EOD is now implemented using a jump over
one million filemarks.
Id = NSMex03096 SSPUX310_015
Capacity of the MO medium is incorrectly calculated.
This results in MA writing after the end of media.
Resolution:
MO capacity is now correctly calculated.
Id = NSMex03106 SSPUX310_017
If there are only STK 9840 media cartridges in the
library, QUERY command results in
"No query data found".
Resolution:
STK 9840 media are now mapped into 3840 media class.
SR:
H555005004 B555007360 H555004009 H555004450 H555005353
H555004912 B554000160 H555006362 B554000701 8606145724
B554000426 B554000653 B554000744 B554000906
Patch Files:
/opt/omni/databases/vendor/ma/ibm/rs6000/aix-42/A.03.10/
packet.Z
/opt/omni/databases/vendor/ma/sco/i386/sco_sv/A.03.10/
packet.Z
/opt/omni/databases/vendor/ma/sequent/i386/dynix/A.03.10/
packet.Z
/opt/omni/databases/vendor/ma/siemens/r400/sinix/A.03.10/
packet.Z
/opt/omni/databases/vendor/ma/sun/sparc/solaris/A.03.10/
packet.Z
/opt/omni/databases/vendor/ma/sun/sparc/solaris-26/A.03.10/
packet.Z
/opt/omni/databases/vendor/ma/hp/s800/hp-ux-10/A.03.10/
packet.Z
/opt/omni/databases/vendor/acs/hp/s800/hp-ux-10/A.03.10/
packet.Z
/opt/omni/databases/vendor/das/hp/s800/hp-ux-10/A.03.10/
packet.Z
/opt/omni/databases/vendor/das/ibm/rs6000/aix-42/A.03.10/
packet.Z
what(1) Output:
/opt/omni/databases/vendor/ma/ibm/rs6000/aix-42/A.03.10/
packet.Z:
None
/opt/omni/databases/vendor/ma/sco/i386/sco_sv/A.03.10/
packet.Z:
None
/opt/omni/databases/vendor/ma/sequent/i386/dynix/A.03.10/
packet.Z:
None
/opt/omni/databases/vendor/ma/siemens/r400/sinix/A.03.10/
packet.Z:
None
/opt/omni/databases/vendor/ma/sun/sparc/solaris/A.03.10/
packet.Z:
None
/opt/omni/databases/vendor/ma/sun/sparc/solaris-26/A.03.10/
packet.Z:
None
/opt/omni/databases/vendor/ma/hp/s800/hp-ux-10/A.03.10/
packet.Z:
None
/opt/omni/databases/vendor/acs/hp/s800/hp-ux-10/A.03.10/
packet.Z:
None
/opt/omni/databases/vendor/das/hp/s800/hp-ux-10/A.03.10/
packet.Z:
None
/opt/omni/databases/vendor/das/ibm/rs6000/aix-42/A.03.10/
packet.Z:
None
cksum(1) Output:
629310214 1484885 /opt/omni/databases/vendor/ma/ibm/rs6000/
aix-42/A.03.10/packet.Z
307953322 1317677 /opt/omni/databases/vendor/ma/sco/i386/
sco_sv/A.03.10/packet.Z
744167621 1502242 /opt/omni/databases/vendor/ma/sequent/
i386/dynix/A.03.10/packet.Z
2089943179 1790931 /opt/omni/databases/vendor/ma/siemens/
r400/sinix/A.03.10/packet.Z
130044495 1737635 /opt/omni/databases/vendor/ma/sun/sparc/
solaris/A.03.10/packet.Z
111074125 1763950 /opt/omni/databases/vendor/ma/sun/sparc/
solaris-26/A.03.10/packet.Z
3641042244 1760623 /opt/omni/databases/vendor/ma/hp/s800/
hp-ux-10/A.03.10/packet.Z
2140147840 2266454 /opt/omni/databases/vendor/acs/hp/s800/
hp-ux-10/A.03.10/packet.Z
3125218805 1836291 /opt/omni/databases/vendor/das/hp/s800/
hp-ux-10/A.03.10/packet.Z
2279984134 1699201 /opt/omni/databases/vendor/das/ibm/
rs6000/aix-42/A.03.10/packet.Z
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_21642
Equivalent Patches:
PHSS_24422:
s700: 11.00
s800: 11.00
Patch Package Size: 16830 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_24421
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHSS_24421.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHSS_24421. 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_24421.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_24421.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
PHSS_24421:
NOTE!
This Patch has to be installed on the Installation
Server host.
The OB2 Media Agent must be redistributed to the Media
Agent client system(s) after the installation of the patch
in order to get the fixes into effect.
For distribution of the Media Agent, refer to the
OmniBackII Installation guide.
Patch includes the following Site Specific Patches:
SSPUX310_008
SSPUX310_015
SSPUX310_017
SSPUX310_045
SSPUX310_062
-----End of Document ID: PHSS_24421------------------------------------------
Document ID: PHSS_25755
Date Loaded: 20011211
Title: s700_800 10.20 MPower//Web December 2001 Periodic Patch
Patch Name: PHSS_25755
Patch Description: s700_800 10.20 MPower//Web December 2001 Periodic Patch
Creation Date: 01/11/27
Post Date: 01/12/11
Hardware Platforms - OS Releases:
s700: 10.20
s800: 10.20
Products:
MPower//Web 2.0
MPower//Web 1.1
MPower//Web 1.0
Filesets:
VideoClients.WTMPEGP-RUN,B.10.20.00,B.10.20.01,B.10.20.02
VideoClients.WTMPEGP-RUN,B.10.20.03,B.10.20.04,B.10.20.05
WTSharedX.WTSHAREDX-MAN,B.10.20.00,B.10.20.01,B.10.20.02
WTSharedX.WTSHAREDX-MAN,B.10.20.03,B.10.20.04,B.10.20.05
WTSharedXDe.WTSX-GER-I-M,B.10.20.00,B.10.20.01,B.10.20.02
WTSharedXDe.WTSX-GER-I-M,B.10.20.03,B.10.20.04,B.10.20.05
WTSharedXFr.WTSX-FRE-I-M,B.10.20.00,B.10.20.01,B.10.20.02
WTSharedXFr.WTSX-FRE-I-M,B.10.20.03,B.10.20.04,B.10.20.05
WTSharedXJp.WTSX-JPN-S-M,B.10.20.00,B.10.20.01,B.10.20.02
WTSharedXJp.WTSX-JPN-S-M,B.10.20.03,B.10.20.04,B.10.20.05
WTSharedXJp.WTSX-JPN-E-M,B.10.20.00,B.10.20.01,B.10.20.02
WTSharedXJp.WTSX-JPN-E-M,B.10.20.03,B.10.20.04,B.10.20.05
WTWhiteboard.WTWHITEBOARD,B.10.20.00,B.10.20.01,B.10.20.02
WTWhiteboard.WTWHITEBOARD,B.10.20.03,B.10.20.04,B.10.20.05
WTScreenCapt.WTSCNCAP,B.10.20.00,B.10.20.01,B.10.20.02
WTScreenCapt.WTSCNCAP,B.10.20.03,B.10.20.04,B.10.20.05
AudioClients.WTAUDIO-RUN,B.10.20.00,B.10.20.01,B.10.20.02
AudioClients.WTAUDIO-RUN,B.10.20.03,B.10.20.04,B.10.20.05
WTSharedX.WTSHAREDX,B.10.20.00,B.10.20.01,B.10.20.02
WTSharedX.WTSHAREDX,B.10.20.03,B.10.20.04,B.10.20.05
Imaging.WTIMAGE-RUN,B.10.20.00,B.10.20.01,B.10.20.02
Imaging.WTIMAGE-RUN,B.10.20.03,B.10.20.04,B.10.20.05
WTScreenCapt.WTSCNCAP-MAN,B.10.20.00,B.10.20.01,B.10.20.02
WTScreenCapt.WTSCNCAP-MAN,B.10.20.03,B.10.20.04,B.10.20.05
Automatic Reboot?: No
Status: General Release
Critical: No
Path Name: /hp-ux_patches/s700_800/10.X/PHSS_25755
Symptoms:
PHSS_25755:
1. Video_Play: Save Frame doesn't work.
2. Man page missing for the new slider control
("Timeout Value") in SharedX.
PHSS_24757:
1. Problem with PHSS_24190 when /usr and /opt are on
different file systems
PHSS_24190:
1. SharedX causes Xserver to core dump if network connection
is slow or unreliable.
2. Problem with the popup and pulldown menu in SharedX.
3. SXshare destroys the names of shared windows.
4. SharedX on 11.0 issues "Cannot convert string ... to
type Pixmap".
PHSS_22756:
1. SharedX memory leak
PHSS_21665:
1. SharedX fails to refresh remote window if local window
has StructureNotify
2. Need Undo function in Whiteboard
3. Undo function in Whiteboard is not handled properly in
some cases
4. Whiteboard dumps core if a filename with colon is
dropped
5. Screen Capture should recognise the window id as one of
the command line arguments.
6. Screen Capture gives memory fault when Help button is
reactivated
7. Screencapture does not save my previous setting
8. Text across options button in Sreencapture should be in
bold letters
9. If type letter for Pause, don't give error message in
Screen Capture
10. Desensitize Append toggle for non-tiff files in Screen
Capture
11. Cannot use Append option in Screen Capture, if this is
the first image in the file
12. Imageview hangs after deleting the image file and
performing a cut/paste operation
13. Would like ability to print modified images from
imageview
14. Imageview should clear the drawing area when a non-image
file is dropped
PHSS_17977:
1. Monitoring incorrectly handled in Audio Control Panel.
2. audio_editor Save As option fails when the free disk
space is greater than 2GB .
3. Full Audio CD input enhancements for Audio III hardware.
PHSS_16228:
SharedX:
Can't share window with Japanese title.
Imageview:
Imageview cannot save TIFF uncompressed in some locales.
Capture man page:
The file /opt/wt/share/man/man1.Z/capture.1 was
compressed twice instead of once.The man command will
not format it.
PHSS_11920:
SharedX:
SharedX is slow when sharing applications that do
pixmap-to-pixmap copy.
Screencapture:
Screen capture fails if an image window is overlaid
with a transparent window.
AudioClients:
When opening the audio_editor and loading a sound file,
an error message can appear:
"Insufficient disk space to load file".
Even though free space is available.
Defect Description:
PHSS_25755:
1. Video_Play: Save Frame doesn't work.
2. Man page missing for the new slider control
("Timeout Value") in SharedX.
PHSS_24757:
1. Problem with PHSS_24190 when /usr and /opt are on
different file systems
PHSS_24190:
1. SharedX causes Xserver to core dump if network connection
is slow or unreliable.
2. Problem with the popup and pulldown menu in SharedX.
3. SXshare destroys the names of shared windows.
4. SharedX on 11.0 issues "Cannot convert string ... to
type Pixmap".
PHSS_22756:
1. SharedX memory leak
PHSS_21665:
1. SharedX fails to refresh remote window if local window
has StructureNotify
2. Need Undo function in Whiteboard
3. Undo function in Whiteboard is not handled properly in
some cases
4. Whiteboard dumps core if a filename with colon is
dropped
5. Screen Capture should recognise the window id as one of
the command line arguments.
6. Screen Capture gives memory fault when Help button is
reactivated
7. Screencapture does not save my previous setting
8. Text across options button in Sreencapture should be in
bold letters
9. If type letter for Pause, don't give error message in
Screen Capture
10. Desensitize Append toggle for non-tiff files in Screen
Capture
11. Cannot use Append option in Screen Capture, if this is
the first image in the file
12. Imageview hangs after deleting the image file and
performing a cut/paste operation
13. Would like ability to print modified images from
imageview
14. Imageview should clear the drawing area when a non-image
file is dropped
Resolution:
1. Code is modified to check the mapping state and according
to it, flag is set.
2. Undo function in Whiteboard is now incorporated.
3. Undo functionality in whiteboard is checked for all
cases.
4. Code modified to handle filename with colon.
5. Screen Capture recognises the window id as one of the
command line arguments.
6. The number of arguments passed to Helpwin is set to 3.
7. .capture file is newly created to hold the latest screen
settings.
8. Text across options button in Screencapture is now made
bold with good visibility.
9. Screencapture does not accept non-numeric values and
gives a error message if entered.
10. Append toggle button is desensitized for all non-tiff
files.
11. Append option is used even if this is a first image in
the file.
12. Imageview gives and error while trying to do cut/paste
operation after the image file.
13. Changed the print callback to print the modified image.
14. The drawing area is cleared when a non-image file is
dropped.
PHSS_17977:
1. Monitoring incorrectly handled in Audio Control Panel.
2. audio_editor Save As option fails when the free disk
space is greater than 2GB.
3. Full Audio CD input enhancements for Audio III hardware.
Resolution:
1. The Minimum and Maximum monitor gain values are now
-128db and 0db respectively.
2. The variable holding the value of free disk space
over-flowed when the disk space is > 2GB. After this fix
the variable will be able to hold values greater than
2GB.
3. The Audio III hardware has an additional input for CD .
The enhancements are meant to make AudioSubsystem aware
of that input.
PHSS_16228:
SharedX:
A call which does not support compound text encoding
was used.
Imageview:
Localized "TIFF uncompressed" text was compared with
hard coded "TIFF uncompressed".
Capture man page:
The file /opt/wt/share/man/man1.Z/capture.1 was
compressed twice instead of once.The man command will
not format it.
PHSS_11920:
SharedX:
Single-bit depth pixmap replicas on the receiver
were not being found after they were created, so
they were being re-created on each use.
Screencapture:
Overlay windows were not correctly handled in all
situations.
AudioClients:
The "Insufficient disk space" error message occurs
because signed values are used to check filesystem
free space. These overflow and become negative when
free space > 2Gb.
SR:
8606194620 8606227012 8606212249 8606167016 8606188040
8606156774 8606167370 8606138447 8606130700 5003448522
1653240689 1653259424 1653216044 4701359810
Patch Files:
/opt/wt/bin/whiteboard
/opt/wt/lib/nls/msg/C/imageview.cat
/opt/wt/bin/audio_editor
/opt/wt/bin/capture
/opt/wt/bin/SharedX
/opt/wt/bin/SXshare
/opt/wt/bin/imageview
/opt/wt/newconfig/usr/lib/X11/extensions/libSX.1010
/opt/wt/newconfig/usr/lib/X11/extensions/libSX.1020
/opt/wt/share/man/man1.Z/capture.1
/opt/wt/bin/AudioCP
/opt/wt/lib/nls/msg/C/audEditor.cat
/opt/wt/newconfig/etc/dt/app-defaults/C/Sharedx
/opt/wt/newconfig/etc/dt/app-defaults/de_DE.iso88591/Sharedx
/opt/wt/newconfig/etc/dt/app-defaults/fr_FR.iso88591/Sharedx
/opt/wt/newconfig/etc/dt/app-defaults/ja_JP.SJIS/Sharedx
/opt/wt/newconfig/etc/dt/app-defaults/ja_JP.eucJP/Sharedx
/opt/wt/bin/Video_Play
/opt/wt/share/man/man1.Z/SharedX.1
what(1) Output:
/opt/wt/bin/AudioCP:
X Window System, Version 11 R5+ HP-UX B.10.01.00 Apr
1999 Patch Release
(build date: Tue Mar 23 00:47:33 MST 1999)
/opt/wt/bin/SXshare:
X Window System, Version 11 R6+ HP-UX B.10.20.00 Jun
e 2001 Patch Release
(build date: Fri May 18 18:23:38 IST 2001)
SharedX 2.5 SXshare - HP OpenFlow User Environment
/opt/wt/bin/SharedX:
X Window System, Version 11 R6+ HP-UX B.10.20.00 Jun
e 2001 Patch Release
(build date: Mon May 21 09:50:15 IST 2001)
SharedX 2.5 Connector - Hewlett-Packard MPower//Web
1.0
/opt/wt/bin/audio_editor:
X Window System, Version 11 R5+ HP-UX B.10.01.00 Apr
1999 Patch Release
(build date: Tue Mar 23 01:42:37 MST 1999)
/opt/wt/bin/capture:
X Window System, Version 11 R6+ HP-UX B.10.20.00 Jun
e 2000 Patch Release
(build date: Thu May 25 16:06:55 IST 2000)
/opt/wt/bin/imageview:
X Window System, Version 11 R6+ HP-UX B.10.20.00 Jun
e 2000 Patch Release
(build date: Tue May 2 19:00:44 IST 2000)
/opt/wt/bin/whiteboard:
X Window System, Version 11 R6+ HP-UX B.10.20.00 Jun
e 2000 Patch Release
(build date: Tue May 2 23:30:27 IST 2000)
/opt/wt/bin/Video_Play:
Version 1.0.3, HP-UX A.09.03 VERSION= MPower 2.02
X Window System, Version 11 R5+ HP-UX B.10.01.00 Dec
ember 2001 Patch Release
(build date: Fri Nov 23 19:00:01 IST 2001)
/opt/wt/lib/nls/msg/C/audEditor.cat:
None
/opt/wt/lib/nls/msg/C/imageview.cat:
None
/opt/wt/newconfig/etc/dt/app-defaults/C/Sharedx:
SharedX 2.4 app-defaults -- 10/95
/opt/wt/newconfig/etc/dt/app-defaults/de_DE.iso88591/
Sharedx:
SharedX 2.4 app-defaults -- 10/95
/opt/wt/newconfig/etc/dt/app-defaults/fr_FR.iso88591/
Sharedx:
SharedX 2.4 app-defaults -- 10/95
/opt/wt/newconfig/etc/dt/app-defaults/ja_JP.SJIS/Sharedx:
SharedX 2.4 app-defaults -- 10/95
/opt/wt/newconfig/etc/dt/app-defaults/ja_JP.eucJP/Sharedx:
SharedX 2.4 app-defaults -- 10/95
/opt/wt/newconfig/usr/lib/X11/extensions/libSX.1010:
libSX.1: SharedX Extensions Lib.,Version 2.4, HP-UX
10.10
X Window System, Version 11 R5+ HP-UX B.10.10.00 Jul
y 1997 Patch Release
(build date: Tue Jun 24 08:20:09 PDT 1997)
/opt/wt/newconfig/usr/lib/X11/extensions/libSX.1020:
libSX.1: SharedX Extensions Lib.,Version 2.5, HP-UX
10.20
X Window System, Version 11 R6+ HP-UX B.10.20.00 Jun
e 2001 Patch Release
(build date: Fri May 18 18:19:52 IST 2001)
/opt/wt/share/man/man1.Z/capture.1:
None
/opt/wt/share/man/man1.Z/SharedX.1:
None
cksum(1) Output:
2019090864 57492 /opt/wt/bin/AudioCP
3881701747 49152 /opt/wt/bin/SXshare
3242454784 208896 /opt/wt/bin/SharedX
2518312740 312428 /opt/wt/bin/audio_editor
3466654134 94208 /opt/wt/bin/capture
1275014962 188416 /opt/wt/bin/imageview
1783433912 172032 /opt/wt/bin/whiteboard
2437016528 193092 /opt/wt/bin/Video_Play
2164466559 6385 /opt/wt/lib/nls/msg/C/audEditor.cat
3381487249 5511 /opt/wt/lib/nls/msg/C/imageview.cat
4112754319 23203 /opt/wt/newconfig/etc/dt/app-defaults/C/
Sharedx
1293483781 23587 /opt/wt/newconfig/etc/dt/app-defaults/
de_DE.iso88591/Sharedx
3155840178 24752 /opt/wt/newconfig/etc/dt/app-defaults/
fr_FR.iso88591/Sharedx
3877072839 29348 /opt/wt/newconfig/etc/dt/app-defaults/
ja_JP.SJIS/Sharedx
3452852684 29349 /opt/wt/newconfig/etc/dt/app-defaults/
ja_JP.eucJP/Sharedx
2680715542 147456 /opt/wt/newconfig/usr/lib/X11/extensions/
libSX.1010
2407211814 147456 /opt/wt/newconfig/usr/lib/X11/extensions/
libSX.1020
1572689633 1469 /opt/wt/share/man/man1.Z/capture.1
3547540353 11755 /opt/wt/share/man/man1.Z/SharedX.1
Patch Conflicts: None
Patch Dependencies:
s700: 10.20: PHSS_17971
s800: 10.20: PHSS_17971
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_11920 PHSS_16228 PHSS_17977 PHSS_21665 PHSS_22756 PHSS_24190
PHSS_24757
Equivalent Patches:
PHSS_25756:
s700: 11.00
s800: 11.00
Patch Package Size: 1780 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_25755
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHSS_25755.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHSS_25755. 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_25755.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_25755.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHSS_25755------------------------------------------
Document ID: PHSS_25656
Date Loaded: 20011211
Title: s700_800 10.20 HP JDBC DRIVER 1.15
Patch Name: PHSS_25656
Patch Description: s700_800 10.20 HP JDBC DRIVER 1.15
Creation Date: 01/11/08
Post Date: 01/12/11
Hardware Platforms - OS Releases:
s700: 10.20
s800: 10.20
Products:
HP SQL/HP-UX A.G3.14
Filesets:
ALLBASE-SQL.AB-JDBC,A.G3.14
Automatic Reboot?: No
Status: General Release
Critical: No
Path Name: /hp-ux_patches/s700_800/10.X/PHSS_25656
Symptoms:
PHSS_25656:
JDBC driver does not handle translations UNICODE<->ROMAN8
Prompt option not supported on MPE client and results
in error when used.
driver fails to load under JDK 1.2 on MPE or NT
fails to handle ESCAPE clause with LIKE expressions
Sample app broken on Java 1.2.1.
PHSS_21577:
Users may see problems with end user tools e.g. StarOffice
on Linux, or their own Java application which uses the HP
JDBC driver for Allbase. Information about the catalog will
not be returned correctly. E.g. the list of tables for the
Database may be blank.
If tracing is switched on at the server, then the servlog
will show a select with a where clause of the form
.. column like 'NULL' escape '\' ..
whereas it should be
.. column is NULL ....
Defect Description:
PHSS_25656:
SR# 8606132652
JDBC driver was not designed to support Roman8 character set
In order to support Unicode<->Roman8, some of the methods
in classes ByteArray, SolidBuffer and SolidResultSet
needs to modified.
Roman8 convertion classes are required for this enhancement
to work.
SR# 8606179196
Creating AWT or Motif window in MPE doesnt make sense
since GUI is not supported on MPE. In order to avoid this
problem the code has been modified in JdbcDriver.class not
to create an AWT or Motif window.
SR# 8606110028
Driver loads under JDK 1.2 on MPE or NT
SR# 8606154949
Driver can handle ESCAPE clause with LIKE expressions.
SR# 5003466086
Sample applications works fine on Java 1.2.1
PHSS_21577:
SR# 8606137358
The underlying problem is with methods such as getTables in
the DataBaseMetaData interface incorrectly handling 'null'.
These methods are used to retrieve information about the
structure of the Database. If a parameter to one of these
calls is set to =null, rather than ="" then an incorrect
select is passed to Allbase so the information is not
retrieved correctly.
The resolution is to change the methods so that they handle
nulls in the same way as an empty string.h DataBaseMetaData
methods and handling of 'null'
SR:
8606132652 8606179196 8606110028 8606154949 5003466086
8606137358
Patch Files:
/opt/allbase/jdbc/READ1ST
/opt/allbase/jdbc/RELNOTES
/opt/allbase/jdbc/hpjdbc.tar
what(1) Output:
/opt/allbase/jdbc/READ1ST:
None
/opt/allbase/jdbc/RELNOTES:
None
/opt/allbase/jdbc/hpjdbc.tar:
TOOLS(ByteArray.jp): Ver:1 $Revision: 1.9 $ $Date:
01/04/16 15:39:20 $
JSOLID(Factory.jp): Ver:1 $Revision: 1.3 $ $Date:
20/0./4. 7.:6.:9. $
JDBC(Jdbc.jp): $Revision: 1.14 $ $Date: 99/04/08
12:10:18 $
JDBC(JdbcCallableStatement.jp): $Revision: 1.10 $
$Date: 99/01/07 07:13:30 $
JDBC(JdbcConnection.jp): $Revision: 1.15 $ $Date:
99/03/30 07:06:52 $
JDBC(JdbcDatabaseMetaData.jp): $Revision: 1.17 $
$Date: 20/0./5. 6.:4.:3. $
JDBC(JdbcDriver.jp): $Revision: 1.15 $ $Date:
01/04/16 15:13:03 $
JDBC(JdbcPreparedStatement.jp): $Revision: 1.10 $
$Date: 99/01/07 08:16:52 $
JDBC(JdbcResultSet.jp): $Revision: 1.13 $ $Date:
99/03/30 07:08:43 $
JDBC(JdbcResultSetMetaData.jp): $Revision: 1.10 $
$Date: 99/03/30 07:09:11 $
JDBC(JdbcStatement.jp): $Revision: 1.11 $ $Date:
99/01/07 08:19:30 $
JDBC(JdbcVersion.jp): $Revision: 1.10 $ $Date:
99/03/30 13:31:44 $
TOOLS(LogonDialog.jp): Ver:1 $Revision: 1.6 $
$Date: 99/04/06 09:56:18 $
JSOLID(ParameterException.jp): Ver:1 $Revision:
1.6 $ $Date: 98/09/22 09:42:34 $
JSOLID(Solid.jp): Ver:1 $Revision: 1.37 $ $Date:
99/03/31 12:02:00 $
TOOLS(tracing.h): Ver:1 $Revision: 1.4 $ $Date:
98/09/22 06:17:30 $
JSOLID(SolidBuffer.jp): Ver:1 $Revision: 1.6 $
$Date: 01/04/16 15:33:06 $
JSOLID(SolidConnection.jp): Ver:1 $Revision: 1.22
$ $Date: 99/01/29 12:47:38 $
JSOLID(SolidDaemon.jp): Ver:1 $Revision: 1.2 $
$Date: 99/05/07 06:17:12 $
JSOLID(SolidException.jp): Ver:1 $Revision: 1.9 $
$Date: 98/11/24 12:51:40 $
JSOLID(SolidParameterSet.jp): Ver:1 $Revision: 1.5
$ $Date: 98/09/22 11:34:01 $
JSOLID(SolidReadThread.jp): Ver:1 $Revision: 1.4 $
$Date: 98/12/22 11:08:47 $
JSOLID(SolidResultSet.jp): Ver:1 $Revision: 1.14 $
$Date: 01/04/16 15:36:37 $
JSOLID(SolidResultSetMetaData.jp): Ver:1 $Revision:
1.7 $ $Date: 98/10/13 08:48:49 $
TOOLS(ThreadInfo.jp): Ver:1 $Revision: 1.1 $
$Date: 98/09/17 06:21:53 $
JSOLID(TimeoutException.jp): Ver:1 $Revision: 1.6
$ $Date: 98/09/22 13:05:45 $
TOOLS(Tracing.jp): Ver:1 $Revision: 1.10 $ $Date:
99/03/31 12:05:09 $
JSOLID(TypeConversionException.jp): Ver:1
$Revision: 1.6 $ $Date: 98/09/22 13:06:24 $
*** SOLID V5.3 HP-UX JDBC Port Monitor built Nov 8
2001 19:01:16
sldmon.c $Revision: 4.40 $ $Date: 20/0./3.
7.:5.:4. $
*** SOLID V5.3 Static Library built Nov 8 2001
18:53:31
sldcrypt.c $Revision: 4.3 $ $Date: 99/09/10
16:47:16 $
sldbuf.c $Revision: 4.2 $ $Date: 99/08/19 16:13:33
$
convapi.c $Revision: 4.13 $ $Date: 20/0./2.
7.:7.:5. $
sldlib.c $Revision: 4.9 $ $Date: 20/0./1.
2.:0.:3. $
convccb.c $Revision: 4.2 $ $Date: 98/09/30
17:13:11 $
convtcb.c $Revision: 4.2 $ $Date: 99/08/19
16:03:50 $
converr.c $Revision: 4.3 $ $Date: 99/08/19
16:02:49 $
convdm.c $Revision: 4.3 $ $Date: 20/0./4.
9.:7.:8. $
kb.c $Revision: 4.3 $ $Date: 99/08/19 16:10:25 $
sldsub.c $Revision: 4.20 $ $Date: 20/0./2.
1.:7.:3. $
slddm.c $Revision: 4.2 $ $Date: 99/08/19 16:15:18
$
slddmlib.c $Revision: 4.3 $ $Date: 20/0./2.
6.:3.:6. $
sldldm.c $Revision: 4.1 $ $Date: 98/09/30 18:00:49
$
sldssl.c $Revision: 4.16 $ $Date: 20/0./2.
4.:0.:4. $
convutil.c $Revision: 4.1 $ $Date: 98/09/30
17:19:01 $
kbstub.c $Revision: 4.1 $ $Date: 98/09/30 17:38:30
$
inspectmon.c $Revision: 1.12 $ $Date: 99/10/28
12:26:05 $
inspectutil.c $Revision: 1.9 $ $Date: 99/10/21
07:48:10 $
iascrypt.c $Revision: 4.4 $ $Date: 99/11/29
16:16:41 $
strutils.c $Revision: 4.11 $ $Date: 20/0./1.
2.:4.:4. $
sldcfg.c $Revision: 4.23 $ $Date: 20/0./3.
1.:8.:5. $
xpprocess.c $Revision: 1.6 $ $Date: 99/11/08
11:51:15 $
xplink.c $Revision: 1.5 $ $Date: 99/11/08 10:26:42
$
*** SOLID V5.3 Utilities Static Library built Nov 8
2001 18:57:53
xppipe.c $Revision: 1.2 $ $Date: 99/10/18 09:22:43
$
HP36217-02A.G3.31 SQLX/9000 ALLBASE/SQL
HP36217-02A.G3.31.00 SQL Parser/Linearizer/9000
ALLBASE/SQL 10/23/01
*** Allbase JDBC Data Manager built Nov 8 2001
18:59:28
Allbase Version A.G3.31
albodbc.sql $Revision: 4.6 $ $Date: 99/03/02
09:14:13 $
allbase.sql $Revision: 4.16 $ $Date: 99/07/23
08:13:33 $
albmeta.sql $Revision: 4.10 $ $Date: 99/04/29
17:50:38 $
*** SOLID V5.3 Data Manager Common (JDBC) built Nov
8 2001 18:57:57
dmCommon.c $Revision: 4.21 $ $Date: 20/0./1.
2.:5.:0. $
HP36217-02A.G3.31 NET AF Library ALLBASE/SQL
10/23/01
HP36217-02A.G3.31 NET Library ALLBASE/SQL 10/23/01
HP36217-02A.G3.31 NET VC Library ALLBASE/SQL
10/23/01
sldsrv.c $Revision: 4.26 $ $Date: 20/0./2.
3.:5.:0. $
sldmeta.c $Revision: 4.8 $ $Date: 99/04/29
19:19:25 $
*** SOLID V5.3 HP-UX Data Manager Library built Nov
8 2001 18:52:58
getconfig.c $Revision: 4.5 $ $Date: 20/0./2.
6.:7.:5. $
*** SOLID V5.3 Static Library built Nov 8 2001
18:53:31
sldlib.c $Revision: 4.9 $ $Date: 20/0./1.
2.:0.:3. $
kb.c $Revision: 4.3 $ $Date: 99/08/19 16:10:25 $
sldsub.c $Revision: 4.20 $ $Date: 20/0./2.
1.:7.:3. $
slddm.c $Revision: 4.2 $ $Date: 99/08/19 16:15:18
$
sldldm.c $Revision: 4.1 $ $Date: 98/09/30 18:00:49
$
sldssl.c $Revision: 4.16 $ $Date: 20/0./2.
4.:0.:4. $
kbstub.c $Revision: 4.1 $ $Date: 98/09/30 17:38:30
$
sldcrypt.c $Revision: 4.3 $ $Date: 99/09/10
16:47:16 $
slddmlib.c $Revision: 4.3 $ $Date: 20/0./2.
6.:3.:6. $
sldbuf.c $Revision: 4.2 $ $Date: 99/08/19 16:13:33
$
mbchar.c $Revision: 4.1 $ $Date: 98/10/01 14:28:38
$
myutil.c $Revision: 4.1 $ $Date: 98/10/01 14:31:55
$
*** SOLID V5.3 Allbase Parser built Nov 8 2001
18:57:40
oprlex.l $Revision: 4.2 $ $Date: 99/03/23 06:45:31
$
oprutil.c $Revision: 4.1 $ $Date: 98/10/01
14:51:15 $
oprexec.c $Revision: 4.2 $ $Date: 20/0./4.
4.:4.:9. $
oprgram.y $Revision: 4.1 $ $Date: 98/10/01
14:46:15 $
oprtrav.c $Revision: 4.1 $ $Date: 98/10/01
14:50:12 $
license.c $Revision: 4.13 $ $Date: 20/0./4.
2.:3.:5. $
strutils.c $Revision: 4.11 $ $Date: 20/0./1.
2.:4.:4. $
dumpbuff.c $Revision: 4.4 $ $Date: 99/09/10
19:01:05 $
*** SOLID V5.3 Utilities Static Library built Nov 8
2001 18:57:53
sldcfg.c $Revision: 4.23 $ $Date: 20/0./3.
1.:8.:5. $
cksum(1) Output:
2884846313 2512 /opt/allbase/jdbc/READ1ST
1556820463 1966 /opt/allbase/jdbc/RELNOTES
2244850800 2385920 /opt/allbase/jdbc/hpjdbc.tar
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_21577
Equivalent Patches:
PHSS_25657:
s700: 11.00
s800: 11.00
Patch Package Size: 2400 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_25656
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHSS_25656.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHSS_25656. 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_25656.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_25656.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
Roman8 encoding support for JDBC driver.
How to use this feature.
1. In order to use Roman8 encoding, Roman8
option needs to be passed through the URL.
For ex:
jdbc:allbase://server.roman.com/dbname?encoding=Roman8
IF the encoding option is not passed then the
default encoding is used.
2. Along with the driver classes two Roman8
conversion classes areprovided with this package.
ByteToCharRoman8.class
CharToByteRoman8.class
For JDK 1.1.7, the conversion classes are to be added
to the CLASSPATH.
For JDK 1.2.2 and above, the conversion classes are
to be added to the -Xbootclasspath
-----End of Document ID: PHSS_25656------------------------------------------
Document ID: PHSS_25647
Date Loaded: 20011211
Title: s700_800 10.X OpenMail B.07.00 December 01 Periodic Patch
Patch Name: PHSS_25647
Patch Description: s700_800 10.X OpenMail B.07.00 December 01 Periodic Patch
Creation Date: 01/12/03
Post Date: 01/12/11
Hardware Platforms - OS Releases:
s700: 10.20
s800: 10.20
Products:
OpenMail B.07.00
Filesets:
OpenMail.OM-ADM,B.07.00 OpenMail.OM-AMECAT,B.07.00
OpenMail.OM-AMEICE,B.07.00 OpenMail.OM-AMEPAW,B.07.00
OpenMail.OM-AMEPSS,B.07.00 OpenMail.OM-APPL,B.07.00
OpenMail.OM-BB,B.07.00 OpenMail.OM-CHSICE,B.07.00
OpenMail.OM-CHSPAW,B.07.00 OpenMail.OM-CORE,B.07.00
OpenMail.OM-DESK,B.07.00 OpenMail.OM-DSYNC,B.07.00
OpenMail.OM-ENGCAT,B.07.00 OpenMail.OM-ENGICE,B.07.00
OpenMail.OM-ENGPAW,B.07.00 OpenMail.OM-ENGPSS,B.07.00
OpenMail.OM-FINICE,B.07.00 OpenMail.OM-FINPAW,B.07.00
OpenMail.OM-FREICE,B.07.00 OpenMail.OM-FREPAW,B.07.00
OpenMail.OM-GERICE,B.07.00 OpenMail.OM-GERPAW,B.07.00
OpenMail.OM-IMAP4,B.07.00 OpenMail.OM-ITAICE,B.07.00
OpenMail.OM-ITAPAW,B.07.00 OpenMail.OM-KORICE,B.07.00
OpenMail.OM-KORPAW,B.07.00 OpenMail.OM-LC,B.07.00
OpenMail.OM-LDAP,B.07.00 OpenMail.OM-MAN,B.07.00
OpenMail.OM-NIPICE,B.07.00 OpenMail.OM-NIPPAW,B.07.00
OpenMail.OM-PMOVER,B.07.00 OpenMail.OM-POP3,B.07.00
OpenMail.OM-PTBICE,B.07.00 OpenMail.OM-PTBPAW,B.07.00
OpenMail.OM-RC,B.07.00 OpenMail.OM-SMS,B.07.00
OpenMail.OM-SPAICE,B.07.00 OpenMail.OM-SPAPAW,B.07.00
OpenMail.OM-SWEICE,B.07.00 OpenMail.OM-SWEPAW,B.07.00
OpenMail.OM-UNIX,B.07.00 OpenMail.OM-WEBADM,B.07.00
OpenMail.OM-X400,B.07.00
Automatic Reboot?: No
Status: General Release
Critical: No
Path Name: /hp-ux_patches/s700_800/10.X/PHSS_25647
Symptoms:
PHSS_25647:
CR: JAGad83534 SR: 8606214343
If an auto-redirect is enabled for a users inbox, then all
other auto- actions are excluded from execution for that
mailbox.
CR: JAGad83915 SR: 8606214723
If, when creating an auto-forward rule using the PAW-client
the user deletes the auto-forward covering text, local
delivery fails to forward the message.
CR: JAGad83932 SR: 8606214740
B.06 and B.07
This concerns the UAL Checklist command, when the flag is
set to search the directory on the internet-addr (167)
attribute.
When more than one match is found, the command does not
return the entries found as alternatives. This is unlike
UAL Checkname, which does.
This affects the OMGUI, for example. When entering the
duplicate internet address into a DL, the behaviour varies
depending on whether the Auto Name Checking option is on.
If on, Checkname is used, and you see the X400 attributes
of the entries. If off, you get an error when the message
is Mailed. When you click on the name in error, you get a
message that no alternatives can be displayed, or else you
get an empty box that is supposed to show the alternatives.
CR: JAGad84893 SR: 8606215716
If a message that contains an ORN with a DDVn field greater
than the maximum 128 bytes, the X400 outgoing gateway
correctly rejects this message, and will generate a
non-delivery if appropriate.
If the message is a return of contents (the normal type of
non-delivery), then all subsequent messages that are not
return of contents will be rejected by the gateway. An
error 6019 appears in the omshowlog output for each
rejected message.
After a number of the 6019 errors (200 at most), the
gateway will abort, with log output showing 'too many
transaction files open'.
CR: JAGad84922 SR: 8606215745
If no auto-reply text is provided for an auto-reply rule,
then local delivery fails to send the auto-reply message.
CR: JAGad87535 SR: 8606218386
B.07: omtidyu -B alters the last signon time of the user.
In previous releases it did not.
CR: JAGad87649 SR: 8606218500
Using the Outlook client delegate permissions cannot be set
if the delegate has the Common Name (CN) attribute set. An
error is displayed in the Outlook interface.
CR: JAGad88671 SR: 8606219531
When the X400 outgoing gateway processes a message with a
non-textual content item, and with GENERATE_FTPBP=TRUE in
the ~sys/madmd.cfg file, x400.hpx.out leaks approximately
4Kbytes of memory on the message.
The workaround is to stop and start the X400 gateway
periodically, before the process fails with insufficient
memory.
CR: JAGad88889 SR: 8606219749
IMAP: rereading messages with many attachments can result
in raw base64 encoded information being displayed.
CR: JAGad89888 SR: 8606220752
Signatures which include 8-bit text will appear corrupted
when added to the message body using the B.07.00 ICE
client.
CR: JAGad90057 SR: 8606220921
An Internet Ack which contains a NULL character will cause
unix.in to fail.
CR: JAGad90490 SR: 8606221356
Reading Non-Delivery Notifications for a non-english user
(e.g. German) using an IMAP cleint (e.g. Netscape
Navigator) gives text where the accented characters (e.g.
umlaute) are displayed incorrectly.
CR: JAGad90761 SR: 8606221627
Failure to check if enough memory is available before doing
a write results in the corruption of the shared memory used
by the notification server. The result of this is that
local delivery and UAL remote abort.
CR: JAGad91276 SR: 8606222161
omupdtis does not return an error result when interrupted.
CR: JAGad93282 SR: 8606224187
The unix.out gateway, when processing tnef routed messages,
should generate IDs for Mapi Named Properties, in the range
8000-FFFE. The gateway increments the ID each time that a
named property is processed, generating IDs like 80000003,
8001000b, 80020003....
If the gateway runs for some time, the Named Property IDs
become undefined, once FFFE has been reached.
CR: JAGad93317 SR: 8606224222
The audit log only contains entries for successful signons.
At B.06 unsuccessful signons (e.g. password wrong) were
logged to the audit file with an indication of the signon
error.
CR: JAGad94573 SR: 8606225486
When connecting to the OpenMail message store via the Web
Client 5.10 on a Virtual Vault machine with the portal
access disabled, the error message "cannot connect to the
specified host" is displayed.
CR: JAGad94888 SR: 8606225815
The OpenMail daemons omvvrelay, ompop3, omimap and omportal
(B.06.00) cannot be started or stopped manually by root in
a VirtualVault 4.5 environment, due to root not having
sufficient authorisation.
PHSS_24875:
CR: JAGad30137 SR: 8606160818
OpenMail B.06.00.00 + MayPP00
unix.in might hang and a message queued on the sendmail
queue when the message contains one part only, which is a
distribution list.
Workaround: Prior to sending the DL, add some text in the
body part of the message.
CR: JAGad31466 SR: 8606162150
One-way disrsync agreement between OpenMail and Exchange
(over OMEXCONN). Updates are done on the Exchange server.
When modifying attributes 111 and PHONE-1, then the next
dirsync results in the full loss of tis modified entry
within the OM directory. (However, the next dirsync cycle
will add the corrected entry again).
CR: JAGad49568 SR: 8606180347
Defining more than one sender name on the omtidyu
command-line makes omtidyu substitute the last defined name
as all defined names.
For example:
omtidyu -B -u "daniel wink" -R -T i -n -w "gren elliot" -n
-w "iain parker"
will return :
CRITERIA : Messages in the InTray NOT matching "iain parker
" in SENDER field AND NOT matching "iain parker " in SENDER
field.
CR: JAGad65896 SR: 8606196695
HPUX 11.x - 10.x
Openmail 6.0 Dec '00 PP
The incoming internet gateway, unix.in, loops if supplied
with a bad RCPT_TO or Arpa ORN that contains more than one
sign.
For instance,
To:
_//org/co/admd/prmd////RFC-822/ppinetia.coma.b.c
CR: JAGad67601 SR: 8606198411
Message with a large distribution list (thousands of
recipients) can take a long, long time to pass through the
X.400 gateway (from OpenMail to X.400).
CR: JAGad68810 SR: 8606199624
omshowcda -d <dir_name> displays the mask used to extract
directory entries. The format of this mask changed with GR6
PP-Mar. It used to be:
S/G/I
and now it is:
S=/G=/I=
This will also occur for other directory related commands
that display attribute masks.
CR: JAGad69036 SR: 8606199850
WC6.0 and PAW corrupts the autoreply covering text in the
languages Japenese, Korean and simplified Chinese when the
rule is listed. The covering text is not corrupted when
viewed from within the auto-replied message.
CR: JAGad69543 SR: 8606200362
Occasionally some message body parts, which require base 64
mime encoding, cause the item.browse binary to perform a
segmentation violation. This occurs when a user attempts to
read the message from the intray or folder area using an
IMAP client (Netscape communicator).
CR: JAGad70640 SR: 8606201464
Some scripts included in the OM-APPL component assume that
the 'cut' command is located in /usr/bin. In RedHat 7.1,
'cut' is located in /bin. The scripts affected are
omaddapp, omaddapppdl, omaddapppdln, omdelapp, omdelapppdl,
omdelapppdln, omshowapp, omshowapppdl and omshowapppdln.
CR: JAGad70641 SR: 8606201465
During installation of patch PHSS_23491 the script vvice
attempts to create the directory
/var/opt/openmail/temp/vv_bkp_log and fails. The directory
/var/opt/openmail/temp has the sensitivity label "SYSTEM
INSIDE" and the vvice script is executed from within the
"SYSTEM" environment and therefore does not have
sufficient privileges to perform the operation.
During installation of the patch PHSS_23491, vvsync
attempts to copy the portal.daemon and kill.portal binaries
from /opt/openmail/bin to the CHROOTED bin directory and
fails. These binaries do not form part of the OpenMail
B.07.xx.xx components and therfore are not present in the
OpenMail bin directory.
During installation of the patch PHSS_23491, user
configurable settings are not retained in the general.cfg
CR: JAGad71090 SR: 8606201916
Web Client 6.0 may, under certain cirumstances, display the
incorrect item count when listing items in the tray areas
or the folder areas.
CR: JAGad71959 SR: 8606202785
Clear/signed S/MIME message sent into OpenMail via Internet
g/w cannot be browsed by IMAP client. The multipart/signed
part of the message is empty.
The message can be successfully read by the OMGUI client.
CR: JAGad74578 SR: 8606205403
Some messages that have come from the internet contain
attachments that cannot be opened when using an IMAP client
(eg. Internet Explorer or Netscape).
Typically these are messages that only contain an
attachment and no covering text, but other types of message
structure may also suffer from this problem.
The user typically sees a copy progress bar that just
stops, the transfer of the attachment does not complete.
The format of attachment within the MIME message is not
correct - it should be base64 and in fact the data is
unencoded.
CR: JAGad74715 SR: 8606205540
This applies to B.06.00.00 and B.07.00.00
Use of ldapmodify to replace the mhsORAddress or omAddress
attributes does not work if attempting to replace existing
individual attributes, other than S, S-TX, G and G-TX.
For instance, if the entry for S=user111 has an OU1
configured, then
# ldapmodify -L UTF8-N -D "cn=clim, o=Openmail" -v
dn: cn=user111, o=OpenMail
changetype: modify
replace: mhsORAddresses
mhsORAddresses: S=user111/ou1=japan3
gives
ldap_modify: Operations error
ldap_modify: additional info: [OM 16092] An attribute has
multiple values, but is notconfigured as multi-value.
Parameter : Directory Entry Modifier
Attribute : OU1Max allowed size : 32
Required syntax : PRINTABLE-STRING
The error can also be seen on the server side, on the
omslapd debug output.
The recommended method is to use ldapmodify to modify the
individual attributes explicitly.
For instance, the input to ldapmodify would be
dn:...
changetype: modify
replace: 5
5: <new_OU1_value>
The internal names of the OU<n> attributes are used as they
are not mapped by default in the ~openmail/sys/ldap.attribs
file. Mappings could of course be added to this file, so
that more meaningful tags could be used in ldapmodify.
CR: JAGad75038 SR: 8606205863
Directory entries added using omaddent that contain
OCTET-STRING attributes have octets with certain values
stripped out. ommodent shows the same problem.
The FREEBUSY directory attributes used by Outlook FreeBusy
lookup are examples of OCTET-STRING data. A situation where
the FREEBUSY attributes may become incorrect is when
omdiropt is run on the FREEBUSY directory. This is because
omdiropt uses omaddent.
Octet 014 (14 decimal) is one value that gets stripped.
There may be some other values.
CR: JAGad75517 SR: 8606206344
The problem is seen on Linux with OM 7 only.
The problem is that issuing a valid IMAP command causes the
IMAP4 server to crash, which should not happen.
With the test mailbox, issuing the commands:
. login "username" "password"
. select inbox
. fetch 2 (BODY.PEEK[3.HEADER.FIELDS (Resent-Date)])
causes the crash.
CR: JAGad75975 SR: 8606206802
The problem is with the way that sendmail converts the
address and OpenMail subsequently parses it.
If an entry has the format ", then sendmail quotes it and
adds an extra to the " sequence.
So us"er <user.local>, goes to "us\"er" <user/local>,
Openmail then splits up the address list using commans as
the separator. If a separator is in a quote, it ignores it.
In the above example, the quote after the \ is taken to be
a closing quote. This means that things get out of sync, as
the last quote is taken to be an opening, rather than
closing, quote and the address list becomes mangled.
In addition, the mangled address list may now contain
entries in excess of 1024 characters This can cause a fatal
error.
CR: JAGad79081 SR: 8606209895
Certain printable chars may be used in the components, e.g.
Surname, of OM Personal Names, but should be represented by
special characters on input (see man page omattribs). Such
a char is that 'space' should be input as '_' to allow for
Surnames like "Van Gogh".
IMAP makes no allowance for this mapping, and so fails to
login because the username as input does not exist as an OM
user.
CR: JAGad80029 SR: 8606210842
OpenMail may fail to configure auxiliary child processes
correctly when using the omsetscv command. This results in
the child processes not terminating via the omshut command.
CR: JAGad83734 SR: 8606214543
This applies to B.07, when configured to allow duplicate
internet addresses in the directory. This is the default
for servers upgraded from an earlier version of OpenMail,
but not for new B.07 installations.
Using OMGUI to send a message, if an internet name is
entered that is in the OpenMail system directory twice and
the Dist. List is checked then a System Error 2 is
generated and the connection is lost (the UAL session is
terminated). This only occurs if individual name checking
is turned off.
This is caused by an error in the UAL Checklist command,
when attempting to return the duplicate entries as
alternatives. Note that, prior to B.07, UAL CheckList did
not actually return alternatives when searching on the
internet address field.
See also the related CR JAGad 83932, which is not planned
for fixing in the September 2001 Periodic Patch.
PHSS_23490:
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 server feature of REPEAT REMINDERS in the OMGUI and
MOB GUI do not stop sending out reminders after the Expiry
date.
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: JAGad40563 SR: 8606171299
The web clients do not work with HTTPS and the Apache web
server.
When the user tries to signon they are presented with the
following message:
Bad Request
Your browser sent a request that this server could not
understand.
Reason: You're speaking plain HTTP to an SSL-enabled server
port.
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: 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.
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: JAGad44030 SR: 8606174784
Openmail does not have a converter from unicode to IA5, but
it does have one from unicode to ISO8859_1.
When the item browser is used to display a text message
using the default format, it has no problem in displaying
the message if OM_DEF_USER_CHAR is set to ISO8859_1 in the
configuration file.
However, if OM_DEF_USER_CHAR is set to IA5, then the item
browser isn't able to do the conversion and reports an
error. As the error reported in the log file was that a
character set conversion between MIME-UTF8 and IA5 was
failing, then this is probably the case.
The second problem is the way that the item browser
displays the message in MIME format.
Adding the mapping of UTF-8 to UTF8 in the mime.cs file
means that the character set for the message is now UTF8
which is recognised by OpenMail and the message is
correctly displayed on most clients. However, for Netscape
Messenger, which uses the item browser MIME option, there
is a problem.
The steering file ~sys/brwmime.str specified that generally
character sets should be converted to ISO8859_1 unless
otherwise specified. This means that the item browser
attempts a conversion from UTF8 to ISO8859_1 and fails.
It should be noted that UNICODE is not generally supported
on OpenMail when messages are in the MIME format.
CR: JAGad45429 SR: 8606176189
When using PAW and Web Client 6.0 rule names may be
displayed incorrectly in Korean, Japanese and Simplified
Chinese versions. This may cause the browser to hang.
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: JAGad46439 SR: 8606177205
For an OpenMail server that is configured to support
Czech...
Messages being sent from X400 with 1992 standard General
Text: context-specific 0 (23 octets):
GeneralString (21 octets):
1b 28 42 0f 1b 2d 42 1b 7e 31 31 31 31 b1 ea 32 32 32
. ( B . . - B . ~ 1 1 1 1 . . 2 2 2
are not correctly converted by the X400 In Mapper. They
should be converted to files of type 1736 with character
set T61BASE, and the data of the file should be consistent
with this.
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: JAGad47713 SR: 8606178486
1) omtidyu -l, -t and -w options - wildcards may get
confused in MB.
If a multibyte string contains an *, this is assumed to be
a wildcard.
2) Username incorrectly displayed if it contains TX fields.
The TX fields are concatenated to earlier field values.
This is also a problem with other address list attributes.
3) The -l option is not displayed.
This displays a list of the requested folders and should be
displayed in the full listing.
4) The error/usage string is not displayed if not options
are specified.
omtidyu either returns nothing, or prompts for the password
for the defult user.
5) The -q option does not work.
The -q option produce similar output to a full report, and
more information than a summary report.
6) The msg type selection is not output.
When a full report is requested, the information on each
item should include the message type.
7) The -f option no longer includes WB.
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: JAGad50818 SR: 8606181602
If a message is sent from a user who has an INTERNET_ADDR
defined, to another machine, e.g. via the SMINTFC gateway,
replies to that message do not get returned via the same
route - they always get returned via the INTERNET gateway.
This occurs when the receiving server does does not have
the user's INTERNET_ADDR defined in the directory, and when
the sending server is version GR7
CR: JAGad52689 SR: 8606183476
This applies to omsmtpd in Release 7.
With heavy usage, the SMTP Relay port 25 listener
occasionally stops with a Select error - Bad File Number.
The omshowlog output contains:
ERROR SMTP Relay (SMTPD Relay
Pr) 03.02.01 13:34:27
[OM.DMON 2163] Failed in select.
Error: 'Bad file number'
Alternatively, after logging this error, omsmtpd may hang.
In this case, there will be more than one copy of omsmtpd
running, and the parent will be waiting for the child
processes, and vice versa.
Temporary Workaround:
Stop and restart the daemon.
Or, if Authorisation or Anti-spam features are not in use,
turn off the relay, and rely on sendmail & ommapsmtp to
route incoming messages correctly.
CR: JAGad55411 SR: 8606186206
When shutting down the Remote Client Interface a
segmentation violation is occuring in the Notification
Monitor occasionally because of a buffer over-run or
under-run.
CR: JAGad56484 SR: 8606187277
The OpenMail delegate implementation does not include an
equivalent for Exchange's "Delegate can see my private
items" option (disabled by default in Exchange). Hence when
forwarding Meeting Requests no distinction is made between
Private items and others.
CR: JAGad56620 SR: 8606187413
Message delivery rulesets are not working with empty
subjects.
CR: JAGad57754 SR: 8606188546
omredirtcp logs errors "getsockname: Bad file number" when
no error has occurred.
CR: JAGad58840 SR: 8606189626
MAPI addressbook download fails when trying to download a
directory whose first entry is a large entry such as a pdl
because a buffer overflow occurs.
CR: JAGad63387 SR: 8606194177
A coding defect while processing MIME data sometimes causes
a fatal error within the item.browse binary.
On the Netscape Client the user is presented with the
message:
"The current command did not succeed. The mail server
responded: Some of the requested messages no longer exist."
CR: JAGad64229 SR: 8606195023
Some of the OpenMail patch install scripts may use return
codes which are invalid in Software Distibutor (SD). In
addition, symbolic names such as $SUCCESS, $FAILURE and
$WARNING should be instead of 0, 1 and 2.
Some of the messages do not follow the conventions, with a
word such as ERROR in column 1 of the first line only, and
the text indented to column 10.
CR: JAGad64671 SR: 8606195467
When performing searches of large message stores if the
ual.remote associated with the in.imap41d terminates due to
inactivity or is deliberately killed then in.imap41d goes
into a spin. When using TOP or glance the in.imap41d
processes appear to be consuming a lot of CPU activity,
however, they will not impact on system performance
because the kernel will have assigned them a low priority.
CR: JAGad66344 SR: 8606197150
When installing OpenMail B.07.00, file
~openmail/release.sys/smtpd.cfg is updated to contain the
current domain name in place of the string %LOCALDOMAIN%.
This is also done whenever a new OpenMail instance is
created.
When a patch is installed, the patch scripts need to repeat
this edit.
This does not affect ~openmail/sys/smtpd.cfg which is
intended to be tailored by the OpenMail administrator. This
file is not changed during patch installation.
Defect Description:
PHSS_25647:
CR: JAGad83534 SR: 8606214343
This is an enhancement to the behaviour of the
auto-actions. Auto- redirect may now be controlled by two
directives from the config file; EXECUTE_AA_ON_REDIRECT and
DELETE_INTRAY_MSG_ON_REDIRECT. The values they take are 0
or 1. Before the introduction of this enhancement an
auto-redirect prevented other auto-actions from being
honoured. The first of these two directives ensures that if
any other auto-actions are enabled then they are honoured,
however the trigger message is delivered to the intray. The
second directive will delete the trigger message from the
intray.
CR: JAGad83915 SR: 8606214723
An empty auto-forward covering text string prevents the
file, held within the users g directory, which holds the
covering text from being generated. If this file is not
present the local delivery agent fails to forward the
message.
CR: JAGad83932 SR: 8606214740
The UAL checklist command did a check to see if the
specified address matched the internet address before
looking for a match on the X400 attributes.
If alternatives were found, then the list of alternatives
was compiled by researching the directory. however, the
search to create the list was only being done on the X400
attributes and no internet search was done on the internet
directory. This resulted in no matches being found and the
list being empty.
In addition, the internet search was done only on the
internet attribute. So if X400 attributes had been
specified, these were ignored when determining a match from
the internet directory.
CR: JAGad84893 SR: 8606215716
After processing a erroneous Return of Contents, the X400
outgoing gateway failed to clear a global data item. This
led to subsequent messages being incorrectly handled, and
rejected with 6019 log error numbers. Processing following
the detection of the 6019 errors failed to close the
transaction file of the message or distibution list, and
eventually the limit for the maximum number of open
transaction files was reached.
CR: JAGad84922 SR: 8606215745
An empty auto-reply covering text string prevents the file,
held within the users g directory, which holds the covering
text from being generated. If this file is not present the
local delivery agent fails to generate an auto-reply
message.
CR: JAGad87535 SR: 8606218386
In GR7 a session monitor daemon was introduced which does
some of the work of the UAL. One thing it does is to update
the user's signon information, and the functionality of
when to update the last signon time was not implemented.
Instead, the last signon time is always updated - which
does not correspond to the GR6 functionality when an admin
session or a session run by a trusted user is doing the
signon.
CR: JAGad87649 SR: 8606218500
The UAL_BBACL command that set Outlook permissions on
folders uses the ACL name checking code which (incorrectly)
will not allow the Common Name field to be specified with
other Mnemonic ORN fields. Eg. Teresa
Green/acme,sales/CN=tg will be rejected as an invalid
delegate name.
CR: JAGad88671 SR: 8606219531
The code in the X400 intrinsics, that processes non-textual
content items using the EMA BodyPart 15 rules, allocates
memory on a per message basis for a number of linked data
structures, and fails to release all of them at the end of
the message.
CR: JAGad88889 SR: 8606219749
Extra spurious content is displayed for an IMAP client when
there are more that 9 top level contents. This is due to an
incorrect comparison of the content item number.
CR: JAGad89888 SR: 8606220752
An internal format error within TCL strings caused 8-bit
strings to appear corrupted.
CR: JAGad90057 SR: 8606220921
When the message type is multipart/report, the message is
written out to a temporary file. The length of the line is
noted and if less than 1, an error is reported. If the
first character of a line is null, then the length is 0,
incorrectly causing a fatal error.
CR: JAGad90490 SR: 8606221356
Non-ascii NDN text from message catalogue is not given the
correct charset specification in the MIME header.
CR: JAGad90761 SR: 8606221627
One write to the shared memory used by the Notification
Server failed to check if enough space was available before
commencing the write.
CR: JAGad91276 SR: 8606222161
The omupdtis code traps the SIGHUP and SIGTERM to allow
processing of the omupdtis command to be interrupted but
does not set a error return when this happens.
CR: JAGad93282 SR: 8606224187
The Named Property Id is incremented each time a named
property is generated. There is no check for the actual
maximum of FFFE, or for overflow at FFFF. So once the value
FFFE was exceeded, the named property id's take undefined
values.
CR: JAGad93317 SR: 8606224222
PAM changes for B.07 cause unsuccessful signons to return
early without doing any audit logging.
CR: JAGad94573 SR: 8606225486
The tweaks DEFAULT-OMSERVER and OMSERVER where not honoured
if the portal access mechanism was disabled.
CR: JAGad94888 SR: 8606225815
At VV4.5 root does not have the required authorisation
level to execute the setlevel command.
PHSS_24875:
CR: JAGad30137 SR: 8606160818
This form of message is not a multi-part message, and the
code that reads and processes the '.' terminator in this
case omitted to include the newline character in the check.
Hence the code attempted to continue to read stdin, and
hence the hang, as unix.in is waiting for more from
sendmail
CR: JAGad31466 SR: 8606162150
Exchange Connector resyncs were removing any
entry that had a non-addressing attribute changed on the
Exchange side - this was caused by the fact that the DS
entries coming from Exchange do NOT have a LID attribute so
the normal method of getting the entry using DA_SOURCE_LID
does not work.
CR: JAGad49568 SR: 8606180347
Multiple sender names on the omtidyu command line were all
held in a single buffer resulting in the last senders name
to be registered for all the sender names.
CR: JAGad65896 SR: 8606196695
This was caused by an error in the code that scans Arpa
ORNs, when attempting to map domain names to Openmail
mailnodes using the unixmap.in configuration file.
CR: JAGad67601 SR: 8606198411
The code that is used to build the PDUs for outgoing X.400
messages is not under our control, we use XAPI libraries to
give us a higher level interface to ASN.1 structures and
independence from the underlying MTA. This code is not
particularly efficient and it uses quite large structures
in memory when a PDU is being contructed. In the case of a
message that has a Distribution List with 10,000 names it
will take a long time and use a lot of resources.
The fix for this problem is to add some general.cfg options
to replace large distribution lists with a single name
distribution list. This will not prevent the message from
reaching the intended recipients, but it will speed up the
transfer of the message through the X.400 gateway. If this
DL replacement occurs then the message cannot be
successfully replied to 'all' (as the original distribution
list has been removed).
The general.cfg options are:
X4O_MAX_DL_NAMES=n
where n is the maximum number of names allowed in a
DistList before they get replaced with a single stub DL
name. Default is the current behaviour... there is no
limit.
where the string contains the stub DistList name in
positional ORN format (each ORN field separated with a '/'
character). %s can be used in this string and will be
substituted with the number of names found in the original
DistList. For example: X4O_MAX_DL_NAMES=1000
X4O_MAX_DL_NAMES_ORN=DistList/%s-Name///Black/Hole
will produce a name that the user sees as:
TO: 1001-Name DistList /Black,Hole
when a DistList with 1001 names is send through the X.400
gateway. The default for this ORN string is:
DISTRIBUTION-LIST/%s-NAME///MAIL-SYS
CR: JAGad68810 SR: 8606199624
The fix for JAGab39939 (omfmtent produces illegal directory
entries for entries with null values) has caused omshowcda
to display the directory mask to be displayed differently.
CR: JAGad69036 SR: 8606199850
The cause of the corrupted Korean, Japanese and Simplified
Chinese strings was due to an internal formating error.
CR: JAGad69543 SR: 8606200362
A coding defect within the item.browse binary resulted in a
failure while mime encoding a message.
CR: JAGad70640 SR: 8606201464
Some scripts supplied with OM-APPL specified the full path
name for the 'cut' command. They needed to be enhanced to
support a different location on some OS versions.
CR: JAGad70641 SR: 8606201465
The scripts vvice and vvysnc where not updated for OpenMail
B.07.00 periodic patches
CR: JAGad71090 SR: 8606201916
Hidden items within the message store were included within
the item count when listing the tray or folder areas.
CR: JAGad71959 SR: 8606202785
The mime browsing library only expects to be dealing with
message components in a serialised file. There are
occasions when the components of a message are not
serialised - when this is the case the browse of that item
returns nothing.
CR: JAGad74578 SR: 8606205403
The MIME header is slightly strange inasmuch as the value
is separated from the tag by two spaces. For example:
Content-Transfer-Encoding: base64
This causes the MIME generation routines (in some
circumstances) to misinterpret the MIME header field value.
In this particular case the MIME header has come in from
outside of OpenMail and is being retained in the
inetMessageHeader object file associated with the message.
CR: JAGad74715 SR: 8606205540
A coding error resulted in the mhsORAddress and omAddress
attribute being mapped only to the the Openmail S, S-TX, G
and G-TX attributes for the modify:replace option.
Consequently, when building the OpenMail modification data,
only the former surname and givenname attributes were
deleted and 2 values were supplied for OU1 and other
modified attributes.
CR: JAGad75038 SR: 8606205863
When processing ORNs, omaddent converts to T61 and then
breaks the ORN down into a set of T61 substrings. This may
mean adding some bytes (T61 characters) at the start of
each substring. For non-T61 values, these bytes are later
removed before the value is stored in the directory. This
defect was also removing bytes whose values are the same as
the T61 characters, but which were not added by the initial
parsing.
CR: JAGad75517 SR: 8606206344
The code that constructs the command output was erroneously
attempting to dereference a pointer whose value was NULL.
CR: JAGad75975 SR: 8606206802
Sendmail modifies entries of the form
user/"test <user/test>
to
"user//"test" <user/test>.
Openmail takes this and assumes that the second " ends the
quoted text, then the third quote opens further quoted text
and the To: input can become out of sync.
Further, it becomes possible for mangled addresses to be
greater in size that that expected causing a serious error
to occur.
CR: JAGad79081 SR: 8606209895
A coding defect in the IMAP Server does not take any
account of the special chars in OM Personal Names as input
and therefore fails to map them into those they represent.
CR: JAGad80029 SR: 8606210842
The child process IDs were corrupted within the process ID
configuration file due to incorrect file locking mechanisms
CR: JAGad83734 SR: 8606214543
UAL Checklist searches on the internet address field, and
records in the DL the entries with alternatives/duplicates.
Later it reprocesses the DL, re-searching to get the
alternatives in a new file, which is then appended to the
DL. However, the re-search is on the X400 attributes, not
on the internet address, and the alternatives file is not
created. But the attempt to append continued anyway, and
tried to open a non-existent file.
PHSS_23490:
CR: JAGab39939 SR: 8606100957
The parser does not take into account the case when there
is an attribute name but no attribute value.
CR: JAGab68963 SR: 8606102906
When a Repeat Reminder is set, the message is placed in the
message list DEFER.UA by the UAL. While calculating the
next submission date-time of the message, the final
reminder date is calculated based on the current date and
the value of the current reminder.
If the next submission date of the reminder message is less
than the final reminder date, then the message is placed on
the Service router for routing. Otherwise it is deleted
from the message list, so that no more repeat reminders
will be sent. But since the final reminder date is
calculated using the current date the submission date is
ALWAYS less than the final reminder date.
CR: JAGad31664 SR: 8606162348
The Outgoing Internet Gateway is confused by addresses that
can be generated by the cc:Mail client, such as :
"S=Friendly Name .gren/OU1=mime/
DDT1=RFC-822/DDV1=Friendly Name <grennowhere.hp.com>/
INTERNET-ADDR=Friendly Name <grennowhere.hp.com>"
===========================================================
A coding defect in the ux component tries to enclose the
"Comment <userdomain>" within angle brackets <>, by only
inserting a start bracket < at the beginning, before
passing it to Sendmail, resulting in unmatched brackets,
which naturally generates a Sendmail error.
CR: JAGad35090 SR: 8606165799
The algorithm used to select the approprate user's message
store to restore selects the last message store that
matches just the name part of the user's address.
CR: JAGad40563 SR: 8606171299
The Root-URL is used initially when sending back the
Location: header on signon. The SERVER-PROTOCOL environment
variable is used to construct part of the URL. It appears
that the Apache web server sets the SERVER-PROTOCOL
variable to HTTP/1.0 regardless of whether you are talking
HTTP or HTTPS, however it identifies the fact that we are
talking HTTPS by setting the environment variable
HTTPS="on"
CR: JAGad41471 SR: 8606172211
A segmentation fault occures when parsing a blank line at
the top of the mnMapFile which is located in the
var/opt/openmail/sys directory.
CR: JAGad42968 SR: 8606173711
A design defect in the mim component restricts the search
for an internet address within an ORN to the ordinary DDA
fields of the ORN. However an 8-bit address is stored in a
teletex DDA-TX field, which is ignored by this search and
so the internet address is effectively discarded.
CR: JAGad43052 SR: 8606173797
The IMAP daemon was not converting MIME subject before
copying an item into the OpenMail message store.
CR: JAGad44030 SR: 8606174784
The item browser fails to convert UTF8 to ISO8859_1 when a
message is in MIME format, even though a converter exists.
It recognises that a converter exists, but fails to convert
the UTF8 characters to UCS2 first in the case of the MIME
format. The conversion is then incorrect. In the case of
non MIME text, this two stage conversion is completed
successfully.
UNICODE conversions for MIME formatted messages are not
generally supported in OpenMail and so the 2 step
conversion required had not been implemented.
CR: JAGad45429 SR: 8606176189
When the rule name is read from the OpenMail Auto-Actions
file, tcl expects the format of the string to be UTF-8.
OpenMail does not store the rule names in UTf-8 format,
thus if the rule name is modified in anyway then it becomes
corrupted.
CR: JAGad45449 SR: 8606176209
When a folder is listed (UAL_PRPLST/UAL_LIST) any messages
in the list that not have TextPreview data setup get it
dynamically generated. This causes the ModifiedDate in the
ctner to be updated. This updated ModifiedDate in the ctner
means that the sync. process treats this as a conflict. The
fix is to suppress the ModifiedDate update for this
behind-the-scenes modification. As far a synchronisation
goes the TextPreview is a 'computed' field, dynamically
created in an offline store and is not synchronised data-
so this change is good both architecturally and
pragmatically.
CR: JAGad45880 SR: 8606176642
The attempted encoding of a ' ' character followed by a
'n' as the 1015 and 1016 characters of a line in an html
attachment resulted in the premature abort of the
item.browser and a subsequent segmentation violation.
CR: JAGad46439 SR: 8606177205
The General Text handling code at the incoming X400
interface was written on the assumption that the
interchange charset for non-Latin-1 single byte languages
would be based on an ISO8859_n charset, as used in General
Text bodyparts.
When the Czech version of OpenMail was done, it was decided
to use T61BASE as the interchange charset. However, the
X400 incoming mapper was not changed to properly convert
and map the bodyparts.
CR: JAGad46896 SR: 8606177664
A coding defect in the ux component tries to run off the
end of the temporary file holding the Multipart/Signed part
of the Sendmail message, when this part has missing
end-boundaries of composite contents types, Multipart or
Message.
CR: JAGad47713 SR: 8606178486
) omtidyu -l, -t and -w options - wildcards may get
confused in MB.
The * character is assumed to be the wildcard character in
all cases. This may not be so for certain MB strings.
2) Username incorrectly displayed if it contains TX fields.
The display routine does not take the address group
separator 027 into consideration.
3) The -l option is not displayed.
This is an enhancement request.
4) The error/usage string is not displayed if not options
are specified.
A check to no parameters is not done.
5) The -q option does not work.
The reporting mechanism displays a full report if a SUMMARY
report is not requested, rather than if a FULL report is
requested.
6) The msg type selection is not output.
This is an enhancement request.
7) The -f option no longer includes WB.
In GR7, the -T w option is used to display the waste basket
CR: JAGad48103 SR: 8606178878
Some changes introduced to omdosur as part of the 5.20 MAPI
work, was failing to take into account the possibility of a
missing container.
CR: JAGad50818 SR: 8606181602
When the OMGUI processes a reply, it takes the Distribution
List of the original message and supplies it to UAL
Checklist, requesting Lookup of the 167 attribute in the
UnixMap directory for ORNs that have a group 5 internet
address field.
Messages received from GR7 may contain the internet address
of Openmail users as well as of internet users. If the GR7
internet addresses are not present in the directory of the
server where the reply is constructed, the 167 lookup will
fail to find a match. The code then assumes the recipient
is an internet user and adds the address of the internet
Gateway to the ORN.
CR: JAGad52689 SR: 8606183476
When the relay is heavily loaded, it creates one or more
child relay processes to share the incoming requests. The
child processes later stop when they have been idle for a
while (30 seconds by default). The select error can occur
when the parent is processing the Termination signal from
the child, if the signal is received between when the code
decides to look for input from the child (FD SET) and doing
the select.
After hitting this error, the code does not explicitly stop
the child relay processes, but does wait for them to die.
As the child processes may be waiting for instructions from
the parent, a hang can occur.
CR: JAGad55411 SR: 8606186206
The segmentation violation in the Notification Monitor is
caused by dirty data in a buffer which then causes a buffer
under-run or over-run to then occur. This dirty data
appears to be generated by a large number of
deregistrations for notifications which happens when the
RCI is shut down and timing problems cause a write to the
buffer to be killed thus generating the dirty data which is
then read. The current write is in two stages with the
possibility that the process can be terminated inbetween
these two writes.
CR: JAGad56484 SR: 8606187277
Currently the client does not set up a filter on the
Outlook delegate redirection to prevent private items being
redirected.
The best solution to this problem is to change the server
code so that by default a private Outlook meeting request
will NOT be redirected to a delegate. This behaviour can be
overridden by the LD_SENSITIVE_ITEM_DELEG_REDIR=TRUE
config option (user.cfg and general.cfg)
CR: JAGad56620 SR: 8606187413
Subject is not currently matched (via user-supplied script)
if the subject of the message is null (blank).
The fix is to change the code to allow a blank subject to
be matched. The old behaviour will be reinstated by setting
the RSL_MATCH_BLANK_SUBJECT=FALSE
general.cfg option.
CR: JAGad57754 SR: 8606188546
Porting changes for Linux have caused a problem with the
EINTR signal handling to become visible in the syslog.
EINTR signal handling corrected so that this interrupt is
silently swallowed.
CR: JAGad58840 SR: 8606189626
The failure to download the directory was caused by a
buffer overflow when reading in a large directory entry in
order to pass them to the client.
CR: JAGad63387 SR: 8606194177
The cause of this failure was due to incorrectly parsing
the Content-Disposition response header which sometimes
resulted in corrupted memory.
CR: JAGad64229 SR: 8606195023
The patch installation scripts contained hard-coded exit
codes of 0, 1 and 2, instead of the preferred $SUCCESS,
etc. Also, there were some cases where values other than 0,
1 or 2 could be returned.
CR: JAGad64671 SR: 8606195467
in.imap41d was going into a spin in the function imapsearch
because although conn->state was set to TERMINATED when the
ual socket had died this was not checked for.
CR: JAGad66344 SR: 8606197150
~openmail/release.sys/smtpd.cfg was replaced by an
unconfigured file during patch installation. It is now
edited so it contains a domain name. This is similar to the
work done during initial B.07.00 installation.
SR:
8606214343 8606214723 8606214740 8606215716 8606215745
8606218386 8606218500 8606219531 8606219749 8606220752
8606220921 8606221356 8606221627 8606222161 8606224187
8606224222 8606225486 8606225815 8606160818 8606162150
8606180347 8606196695 8606198411 8606199624 8606199850
8606200362 8606201464 8606201465 8606201916 8606202785
8606205403 8606205540 8606205863 8606206344 8606206802
8606209895 8606210842 8606214543 8606100957 8606102906
8606162348 8606165799 8606171299 8606172211 8606173711
8606173797 8606174784 8606176189 8606176209 8606176642
8606177205 8606177664 8606178486 8606178878 8606181602
8606183476 8606186206 8606187277 8606187413 8606188546
8606189626 8606194177 8606195023 8606195467 8606197150
Patch Files:
/opt/openmail/patch/filesets/OM-ADM
/opt/openmail/patch/filesets/OM-AMECAT
/opt/openmail/patch/filesets/OM-AMEICE
/opt/openmail/patch/filesets/OM-AMEPAW
/opt/openmail/patch/filesets/OM-AMEPSS
/opt/openmail/patch/filesets/OM-APPL
/opt/openmail/patch/filesets/OM-BB
/opt/openmail/patch/filesets/OM-CHSICE
/opt/openmail/patch/filesets/OM-CHSPAW
/opt/openmail/patch/filesets/OM-CORE
/opt/openmail/patch/filesets/OM-DESK
/opt/openmail/patch/filesets/OM-DSYNC
/opt/openmail/patch/filesets/OM-ENGCAT
/opt/openmail/patch/filesets/OM-ENGICE
/opt/openmail/patch/filesets/OM-ENGPAW
/opt/openmail/patch/filesets/OM-ENGPSS
/opt/openmail/patch/filesets/OM-FINICE
/opt/openmail/patch/filesets/OM-FINPAW
/opt/openmail/patch/filesets/OM-FREICE
/opt/openmail/patch/filesets/OM-FREPAW
/opt/openmail/patch/filesets/OM-GERICE
/opt/openmail/patch/filesets/OM-GERPAW
/opt/openmail/patch/filesets/OM-IMAP4
/opt/openmail/patch/filesets/OM-ITAICE
/opt/openmail/patch/filesets/OM-ITAPAW
/opt/openmail/patch/filesets/OM-KORICE
/opt/openmail/patch/filesets/OM-KORPAW
/opt/openmail/patch/filesets/OM-LC
/opt/openmail/patch/filesets/OM-LDAP
/opt/openmail/patch/filesets/OM-MAN
/opt/openmail/patch/filesets/OM-NIPICE
/opt/openmail/patch/filesets/OM-NIPPAW
/opt/openmail/patch/filesets/OM-PMOVER
/opt/openmail/patch/filesets/OM-POP3
/opt/openmail/patch/filesets/OM-PTBICE
/opt/openmail/patch/filesets/OM-PTBPAW
/opt/openmail/patch/filesets/OM-RC
/opt/openmail/patch/filesets/OM-SMS
/opt/openmail/patch/filesets/OM-SPAICE
/opt/openmail/patch/filesets/OM-SPAPAW
/opt/openmail/patch/filesets/OM-SWEICE
/opt/openmail/patch/filesets/OM-SWEPAW
/opt/openmail/patch/filesets/OM-UNIX
/opt/openmail/patch/filesets/OM-WEBADM
/opt/openmail/patch/filesets/OM-X400
/opt/openmail/patch/ompatch
/opt/openmail/patch/PHSS_25647/omunpatch
/opt/openmail/patch/PHSS_25647/ompatch.idx
what(1) Output:
/opt/openmail/patch/filesets/OM-ADM:
No what strings
/opt/openmail/patch/filesets/OM-AMECAT:
No what strings
/opt/openmail/patch/filesets/OM-AMEICE:
No what strings
/opt/openmail/patch/filesets/OM-AMEPAW:
No what strings
/opt/openmail/patch/filesets/OM-AMEPSS:
No what strings
/opt/openmail/patch/filesets/OM-APPL:
No what strings
/opt/openmail/patch/filesets/OM-BB:
No what strings
/opt/openmail/patch/filesets/OM-CHSICE:
No what strings
/opt/openmail/patch/filesets/OM-CHSPAW:
No what strings
/opt/openmail/patch/filesets/OM-CORE:
No what strings
/opt/openmail/patch/filesets/OM-DESK:
No what strings
/opt/openmail/patch/filesets/OM-DSYNC:
No what strings
/opt/openmail/patch/filesets/OM-ENGCAT:
No what strings
/opt/openmail/patch/filesets/OM-ENGICE:
No what strings
/opt/openmail/patch/filesets/OM-ENGPAW:
No what strings
/opt/openmail/patch/filesets/OM-ENGPSS:
No what strings
/opt/openmail/patch/filesets/OM-FINICE:
No what strings
/opt/openmail/patch/filesets/OM-FINPAW:
No what strings
/opt/openmail/patch/filesets/OM-FREICE:
No what strings
/opt/openmail/patch/filesets/OM-FREPAW:
No what strings
/opt/openmail/patch/filesets/OM-GERICE:
No what strings
/opt/openmail/patch/filesets/OM-GERPAW:
No what strings
/opt/openmail/patch/filesets/OM-IMAP4:
No what strings
/opt/openmail/patch/filesets/OM-ITAICE:
No what strings
/opt/openmail/patch/filesets/OM-ITAPAW:
No what strings
/opt/openmail/patch/filesets/OM-KORICE:
No what strings
/opt/openmail/patch/filesets/OM-KORPAW:
No what strings
/opt/openmail/patch/filesets/OM-LC:
No what strings
/opt/openmail/patch/filesets/OM-LDAP:
No what strings
/opt/openmail/patch/filesets/OM-MAN:
No what strings
/opt/openmail/patch/filesets/OM-NIPICE:
No what strings
/opt/openmail/patch/filesets/OM-NIPPAW:
No what strings
/opt/openmail/patch/filesets/OM-PMOVER:
No what strings
/opt/openmail/patch/filesets/OM-POP3:
No what strings
/opt/openmail/patch/filesets/OM-PTBICE:
No what strings
/opt/openmail/patch/filesets/OM-PTBPAW:
No what strings
/opt/openmail/patch/filesets/OM-RC:
No what strings
/opt/openmail/patch/filesets/OM-SMS:
No what strings
/opt/openmail/patch/filesets/OM-SPAICE:
No what strings
/opt/openmail/patch/filesets/OM-SPAPAW:
No what strings
/opt/openmail/patch/filesets/OM-SWEICE:
No what strings
/opt/openmail/patch/filesets/OM-SWEPAW:
No what strings
/opt/openmail/patch/filesets/OM-UNIX:
No what strings
/opt/openmail/patch/filesets/OM-WEBADM:
No what strings
/opt/openmail/patch/filesets/OM-X400:
No what strings
/opt/openmail/patch/ompatch:
$Header: sh_patch.gen /main/gr7_patch/2 2001/05/25 1
9:57:32 pl $
/opt/openmail/patch/PHSS_25647/omunpatch:
$Header: sh_unpat.gen,v
/opt/openmail/patch/PHSS_25647/ompatch.idx:
No what strings
cksum(1) Output:
435393179 867936 /opt/openmail/patch/filesets/OM-ADM
2038279564 217308 /opt/openmail/patch/filesets/OM-AMECAT
1637767291 17017 /opt/openmail/patch/filesets/OM-AMEICE
3613168657 13849 /opt/openmail/patch/filesets/OM-AMEPAW
604057119 22208 /opt/openmail/patch/filesets/OM-AMEPSS
1834248374 178002 /opt/openmail/patch/filesets/OM-APPL
115864625 83448 /opt/openmail/patch/filesets/OM-BB
3499613081 17079 /opt/openmail/patch/filesets/OM-CHSICE
2645433330 14134 /opt/openmail/patch/filesets/OM-CHSPAW
2705636254 11808081 /opt/openmail/patch/filesets/OM-CORE
806486974 107727 /opt/openmail/patch/filesets/OM-DESK
1643875321 174290 /opt/openmail/patch/filesets/OM-DSYNC
1644407995 217290 /opt/openmail/patch/filesets/OM-ENGCAT
2395484317 16990 /opt/openmail/patch/filesets/OM-ENGICE
3138929075 13849 /opt/openmail/patch/filesets/OM-ENGPAW
3135136928 22205 /opt/openmail/patch/filesets/OM-ENGPSS
2790918932 17099 /opt/openmail/patch/filesets/OM-FINICE
719574280 14248 /opt/openmail/patch/filesets/OM-FINPAW
834451841 17046 /opt/openmail/patch/filesets/OM-FREICE
913795811 14170 /opt/openmail/patch/filesets/OM-FREPAW
3674947646 17062 /opt/openmail/patch/filesets/OM-GERICE
913681834 14093 /opt/openmail/patch/filesets/OM-GERPAW
1908783752 82286 /opt/openmail/patch/filesets/OM-IMAP4
3438723826 17037 /opt/openmail/patch/filesets/OM-ITAICE
1803316776 14060 /opt/openmail/patch/filesets/OM-ITAPAW
819910584 17093 /opt/openmail/patch/filesets/OM-KORICE
269429595 14287 /opt/openmail/patch/filesets/OM-KORPAW
3126854903 721628 /opt/openmail/patch/filesets/OM-LC
520702548 84125 /opt/openmail/patch/filesets/OM-LDAP
1685490675 6911 /opt/openmail/patch/filesets/OM-MAN
3952612868 17124 /opt/openmail/patch/filesets/OM-NIPICE
2816438939 14320 /opt/openmail/patch/filesets/OM-NIPPAW
837200547 63344 /opt/openmail/patch/filesets/OM-PMOVER
1261700664 24603 /opt/openmail/patch/filesets/OM-POP3
3574991640 17067 /opt/openmail/patch/filesets/OM-PTBICE
2419528638 14109 /opt/openmail/patch/filesets/OM-PTBPAW
2958251843 477391 /opt/openmail/patch/filesets/OM-RC
2650689949 208075 /opt/openmail/patch/filesets/OM-SMS
562508626 17078 /opt/openmail/patch/filesets/OM-SPAICE
3839798582 14108 /opt/openmail/patch/filesets/OM-SPAPAW
673760489 17052 /opt/openmail/patch/filesets/OM-SWEICE
2457023739 14102 /opt/openmail/patch/filesets/OM-SWEPAW
3014800438 129578 /opt/openmail/patch/filesets/OM-UNIX
3725785324 714595 /opt/openmail/patch/filesets/OM-WEBADM
1781472329 1019708 /opt/openmail/patch/filesets/OM-X400
839793273 26586 /opt/openmail/patch/ompatch
4120277454 11249 /opt/openmail/patch/PHSS_25647/omunpatch
271817426 105041 /opt/openmail/patch/PHSS_25647/ompatch.idx
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_23490 PHSS_24875
Equivalent Patches:
PHSS_25648:
s700: 11.00 11.04 11.11
s800: 11.00 11.04 11.11
PFSS_17034:
sparcSUN: 5.6 5.7 5.8
PASS_17034:
AIX: 4.3
PLSS_17038:
intelLinux: RedHat7.0
Patch Package Size: 17470 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_25647
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHSS_25647.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHSS_25647. 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_25647.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_25647.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
SUBSYSTEM_SHUT
=================================================
PHSS_25647:
=================================================
CR: JAGad83534 SR: 8606214343
-------------------------------
The behaviour of the redirect rule can be controlled by the
directives EXECUTE_AA_ON_REDIRECT and
DELETE_INTRAY_MSG_ON_REDIRECT specified in the
/var/opt/openmail/omhtml/config file. The values these
directives can take are 0 or 1.
The directive EXECUTE_AA_ON_REDIRECT will force local
delivery to retain a copy of the message in the users
intray, thus allowing the auto-actions to be executed.
The directive DELETE_INTRAY_MSG_ON_REDIRECT will force
deletion of the message from the users intray after it has
been delivered and the auto actions have been executed.
=================================================
PHSS_24875:
=================================================
CR: JAGad75038 SR: 8606205863
-------------------------------
Directory entries that have been affected by the defect
should be rewritten with the correct values.
A way to force the republishing the FreeBusy info.
is for the user to do the following in Outlook:
Tools/Options/Preferences tab
- Calendar Options
- FreeBusy Options
- Set publish <n> months... to 0 and hit OK
- FreeBusy Options
- Set publish <n> months... to what is was
before (eg 2) and hit OK
This will cause the FreeBusy info to be rewritten to the
server.
NOTE: OpenMail must be shutdown before installing
this patch.
----------------------------------------------------------
This patch will need the following minimum disk
space requirements:
/opt/openmail/patch : 61 MB
NOTE: ServiceGuard Installations will need twice
this amount.
----------------------------------------------------------
-----End of Document ID: PHSS_25647------------------------------------------
Document ID: PHSS_25858
Date Loaded: 20011210
Title: s700_800 10.20 Fortran90 patch B.10.20.40 to B.10.20.48
Patch Name: PHSS_25858
Patch Description: s700_800 10.20 Fortran90 patch B.10.20.40 to B.10.20.48
Creation Date: 01/12/03
Post Date: 01/12/10
Hardware Platforms - OS Releases:
s700: 10.20
s800: 10.20
Products:
FORTRAN90 B.10.20.40
FORTRAN90 B.10.20.42
Filesets:
FORTRAN90.FORT90-PRG,B.10.20.40
FORTRAN90.FORT90-PRG,B.10.20.42
FORTRAN90.FORT90-MAN,B.10.20.40
FORTRAN90.FORT90-MAN,B.10.20.42
FORTRAN90.F90-JPN-E-MAN,B.10.20.40
FORTRAN90.F90-JPN-E-MAN,B.10.20.42
FORTRAN90.F90-JPN-S-MAN,B.10.20.40
FORTRAN90.F90-JPN-S-MAN,B.10.20.42
Automatic Reboot?: No
Status: General Release
Critical: No
Path Name: /hp-ux_patches/s700_800/10.X/PHSS_25858
Symptoms:
PHSS_25858:
01)JAGad96301: The compiler aborts in a segmentation
fault when compiling an incomplete type
at +O3.
02)JAGad96827: The compiler does not recognize the $SHORT
directive. This is needed for f77 backward
compatibility.
03)JAGad96964: The compiler aborts using +i8 when
compiling the index intrinsic.
04)JAGad96969: The compiler aborts in wide mode with the
+i8 switch when compiling OMP intrinsics.
05)JAGad97206: The compiler reports the wrong line number
in error messages when the -I include path
is used.
06)JAGad97500: The compiler aborts compiling
set_num_threads call using +autodbl in
64-bit mode.
07)JAGad97556: The compiler issues an error 300 message
when compiling a generic function.
08)JAGad97884: The compiler issues an error message for
a character array argument whose length is
different that a specific formal parameter
character array argument.
PHSS_25771:
01)JAGad96323: The compiler aborts during handling of a
CRAY pointer object.
02)JAGad96085: The compiler issues an error message when
defining a generic function using
an INTERFACE block when the function
specification contains a RESULT clause.
03)JAGad95772: The compiler asserts with -g on a program
with a hollerith constant.
04)JAGad95812: The compiler issues an error with +Oopenmp
and Sun's c$pragma directive.
05)JAGad95935: Bad compile-time evaluation of math
function calls with constant arguments.
06)JAGad93111: The compiler emits an "unable to privatize
compiler temp" warning for an OMP parallel
directive.
07)JAGad95189: The compiler emits an f95resolve.c assert
on operator in INTERFACE definition.
PHSS_25616:
01)JAGab14095: Debugger does not stop at the right line
number.
02)JAGab76571: Compiler gets an internal error with array
assignment.
03)JAGad06371: The compiler aborts with segmentation fault
after correctly reporting errors.
04)JAGad91856: Wrong answers for reentrant subroutines.
05)JAGad92916: Data size over 2**31 bytes is incorrectly
promoted to 64 bit
06)JAGad93080: Compiler issues error messages for
c$doacross, c$$, *$$ and !$$.
07)JAGad93165: The compiler aborts when a module is 'use'd
multiple times within the same source file.
08)JAGad93166: The compiler issues an error message for
c$$$.
09)JAGad93470: Line number information is incorrect when
compiling .F files or when +cpp=yes.
10)JAGad93578: The compiler generates an assertion
claiming "Missing LAB for label" on
Open MP code.
11)JAGad94515: The F90 compiler limits initialized DATA
to 42 megabytes, much smaller than F77.
PHSS_25520:
01)JAGad87638: Intermittant wrong answers using at
high optimization levels.
02)JAGad89871: Compiler error compiling a recursive
function, abnormal exit from bridge.
03)JAGad92123: Use of 300 continuation lines causes
internal compiler error.
04)JAGad92124: The label on a 'type' statement is lost.
PHSS_25413:
01)JAGad85737: The compiler does not correctly handle BOZ
constants in intrinsic function calls.
02)JAGad90122: The compiler does not accept the incremental
linking options +ild and +ildrelink.
03)JAGad90369: The compiler asserts on data statement which
uses rep and has another overlapping data
statement.
04)JAGad90394: The compiler aborts with f90: Signal 6.
05)JAGad90477: Use of the +Ofaster compile option causes
bus error.
PHSS_25175:
01)JAGab67472: A problem with strength reduction of 64
bit multiplication by unsigned consants
caused wrong answers.
02)JAGac86637: The compiler errantly reports "invalid arc
calculation" warning.
03)JAGad62170: The +U option needs to support multiple
arguments.
04)JAGad84653: The compiler does not accept 'type' as
a 'print' statement.
05)JAGad85160: Reference to omp_memcpy is unresolved.
06)JAGad85254: The compiler asserts on an OMP intrinsic.
07)JAGad85371: Customer reports need to have more than 256
continuation lines.
08)JAGad85372: Performance for guided scheduling does not
scale well beyond 2 threads.
09)JAGad86385: The compiler aborts with interanl error on
the pack intrinsic.
10)JAGad87340: Compiler aborts with TCG assertion in
in_descriptor.c.
11)JAGad87380: The compiler does not recognize the
+Onoopenmp command-line switch.
12)JAGad87416: Compiler aborts with TCG assertion.
13)JAGad87513: Using $HP$SHARED_COMMON within second
subroutine in a file Is ignored, causing
wrong answers.
14)JAGad88599: Bus error occurs when intrinsic function LOC
is called with a non-subscripted array.
15)JAGad88762: OMP directive is ignored.
16)JAGad89129: Error occurs when implicitly opening a file
with unit number greater than 99.
PHSS_24771:
01)JAGaa68246: Wrong answers with floating point
comparisons using +FPD.
02)JAGab73429: The compiler does not allow the !$ALIAS
directive.
03)JAGad03801: Compiler crashing on end do statements with
no matching do statements.
04)JAGad08183: Run time error with assigned gotos in 64bit
mode
05)JAGad15689: Failure on entry statement that returns a
quadword result.
06)JAGad62340: The +cat option at the end of the compile
line caused compile problems.
07)JAGad73062: Compiler aborts when parallelizing a loop
with an inlined routine.
08)JAGad73370: Wrong answers from libF90 cputime routine.
09)JAGad73465: Code sometimes generated wrong answers at
optimization level +O3.
10)JAGad73529: Garbled "Module not found" error messages.
11)JAGad74647: Open MP parallelization causes segmentation
fault.
12)JAGad77170: SAVE tags an automatic variable, a variable
type not eligible for SAVE causing bogus
compile-time errors.
13)JAGad77176: Compiler abort when an Open MP PRIVATE
variable is from a USEd module.
14)JAGad77883: Compiler abort on interface assignment.
15)JAGad79146: Gdb unable to show the correct f90 source
lines when stepping.
16)JAGad81039: Compiler aborts with "abnormal exit taken
from bridge" with nested routines and
modules.
17)JAGad81737: OMP variable trip count loops not always
correctly parallelized.
18)JAGad81738: Loops with induction variables of type
integer*8 were not transforming the
increment value to be an I*8 constant.
19)JAGad82866: Compiler aborts while generating code for
an array initialization in wide mode.
Defect Description:
PHSS_25858:
01)JAGad96301: The compiler was stuck in an infinite
recursive call loop when compiling an
incomplete type.
02)JAGad96827: The compiler needed to recognize and
correctly handle the $SHORT directive.
03)JAGad96964: There was a bug coding the determination
of the index intrinsic parameter.
04)JAGad96969: The +i8 switch was not compatible with
some of the OMP internal intrinsics.
05)JAGad97206: The compiler incorrectly reported the hash
line number instead of the line number.
06)JAGad97500: The compiler failed to convert some types.
07)JAGad97556: The compiler did not allow dimension as
a function result attribute.
08)JAGad97884: The compiler should issue a warning rather
than an error.
PHSS_25771:
01)JAGad96323: The CRAY target object was not being
handled properly by intrinsics.
Resolution: Recompile with the new compiler.
02)JAGad96085: The function result type attributes were
not being checked correctly.
Resolution: Recompile with the new compiler.
03)JAGad95772: The compiler recognized a hollerith
field as an unnamed variable and issued
invalid debug information.
Resolution: Recompile with the new compiler.
04)JAGad95812: C$pragma was not recognized, the compiler
has been changed to ignore it.
Resolution: Recompile with the new compiler.
05)JAGad95935: The compiler was constant folding divides
by zero.
Resolution: Recompile with the new compiler.
06)JAGad93111: The compiler created temporary variables
but failed to privatize them in the parallel
region.
Resolution: Recompile with the new compiler.
07)JAGad95189: A USE statement of a module which exported
an operator definition within a nested
scope caused an abort due to failure to
clear the pushed operator count.
Resolution: Recompile with the new compiler.
PHSS_25616:
01)JAGab14095: Fixed problem with line number handling.
Resolution: Recompile with new compiler.
02)JAGab76571: Fixed problem with type conversion on array
constants.
Resolution: Recompile with new compiler.
03)JAGad06371: Fixed problem with graceful handling of
error situation.
Resolution: Recompile with new compiler.
04)JAGad91856: Fixed problem with more than one thread
saving the result.
Resolution: Recompile with the new compiler.
05)JAGad92916: The compiler stored subspace lengths as
integers. Changed them to use unsigned
integers.
Resolution: Recompile with the new compiler.
06)JAGad93080: Changed the compiler to suppress errors for
c$doacross, c$$, *$$, and !$$.
Resolution: Recompile with the new compiler.
07)JAGad93165: Multiple use statements caused a name
collision. This has been fixed.
Resolution: Recompile with the new compiler.
08)JAGad93166: Fixed the compiler to allow C$$$ to be a
comment.
Resolution: Recompile with the new compiler.
09)JAGad93470: Fixed problem with #line directives throwing
off the line countin the original source
file.
Resolution: Recompile with the new compiler.
10)JAGad93578: Fixed problem with missing label from
replicated nodes resulting from
parallelization.
Resolution: Recompile with the new compiler.
11)JAGad94515: The data limit was too small. Increased it
to 400 megabytes.
Resolution: Recompile with the new compiler.
PHSS_25520:
01)JAGad87638: Fixed uninitialized register problem causing
intermitant wrong answers at high
optimization levels.
Resolution: Recompile with the new compiler.
02)JAGad89871: Code to determine where the character length
is stored is aborting. Fixed this problem.
Resolution: Recompile with the new compiler.
03)JAGad92123: Over-writing memory due to overflow of 16
bit field describing debugger position.
Fixed field size.
Resolution: Recompile with the new compiler.
04)JAGad92124: Fixed handling of the 'type' form of the
print statement so that the label is
recognized.
Resolution: Recompile with the new compiler.
PHSS_25413:
01)JAGad85737: The compiler did not correctly infer data
type for BOZ (typeless) constants from
context. This has been fixed.
Resolution: Recompile with the new compiler.
02)JAGad90122: Implemented the +ild and +ildrelink compile
options.
Resolution: Recompile with the new compiler.
03)JAGad90369: Fixed bug in handling of the data statement.
Resolution: Recompile with the new compiler.
04)JAGad90394: Fixed the internal compiler assertion.
Resolution: Recompile with the new compiler.
05)JAGad90477: Fixed the bug in handling the +Ofaster
compile option.
Resolution: Recompile with the new compiler.
PHSS_25175:
01)JAGab67472: Fixed a problem with strength reduction
of 64 bit multiplication by unsigned
consants.
Resolution: Recompile with the new compiler.
02)JAGac86637: Removed an unused warning message
"invalid arc calculation".
Resolution: Recompile with the new compiler.
03)JAGad62170: Added support for multiple arguments to
the +U option.
Resolution: Recompile with the new compiler.
04)JAGad84653: To be consistent with f77, updated the
compiler to accept 'type' as a synonym
for 'print' when not within a declaration.
Resolution: Recompile with the new compiler.
05)JAGad85160: Fixed the compiler to resolve the
omp_memcpy reference.
Resolution: Recompile with the new compiler.
06)JAGad85254: Fixed the OMP intrinsic assertion problem
resulting from parameter mismatch.
Resolution: Recompile with the new compiler.
07)JAGad85371: Enhanced the compiler to allow up to 300
continuation lines.
Resolution: Recompile with the new compiler.
08)JAGad85372: Error in algorithm was causing the
compiler to use workload/2 to guide
scheduling. Changed this to use
workload/numthreads.
Resolution: Recompile with the new compiler.
09)JAGad86385: Fixed the internal compiler error
generated on a pack intrinsic.
Resolution: Recompile with the new compiler.
10)JAGad87340: Fixed the internal compiler error
resulting in TCG in_descriptor.c
assertion.
Resolution: Recompile with the new compiler.
11)JAGad87380: Implemented the +Onoopenmp
command-line switch.
Resolution: Recompile with the new compiler.
12)JAGad87416: Fixed the compiler internal error.
Resolution: Recompile with the new compiler.
13)JAGad87513: Placement of $HP$SHARED_COMMON
directive contrary to documentation
was permitted in F77. Upgraded the
f90 compiler to allow the f77 placement.
Resolution: Recompile with the new compiler.
14)JAGad88599: Fixed problem with intrinsic handling
of dope vector array, resulting in bus
error.
Resolution: Recompile with the new compiler.
15)JAGad88762: Fixed problem so that OMP directives
are not lost.
Resolution: Recompile with the new compiler.
16)JAGad89129: Fixed bug in compiler for implicit
open of file with unit number greater
than 99.
Resolution: Recompile with the new compiler.
PHSS_24771:
01)JAGaa68246: The compiler had a problem with using +FPD
combined with certain optimizations. This
has been fixed.
Resolution: Recompile with the new compiler.
02)JAGab73429: The compiler did not recognize the !$ALIAS
form of the $ALIAS directive. The compiler
has been changed to recognize !$ALIAS
Resolution: Recompile with new compiler.
03)JAGad03801: Compiler expected each end do statement to
have matching do statements. This has been
fixed so that an error message is generated.
Resolution: Recompile with new compiler.
04)JAGad08183: Compiler was incorrectly calculating the
destination address. This has been fixed.
Resolution: Recompile with the new compiler.
05)JAGad15689: Problem with quadword results for entry
statements has been fixed.
Resolution: Recompile with the new compiler.
06)JAGad62340: The compiler included the concatenated
file plus all of the individual files in
the compile and link. This has been fixed.
Resolution: Recompile with the new compiler.
07)JAGad73062: The compiler asserted under some cases
when parallelizing a loop with an inlined
routine. This has been fixed.
Resolution: Recompile with the new compiler.
08)JAGad73370: The cputime routine did not return the
correct value. This has been fixed.
Resolution: Recompile with the new compiler.
09)JAGad73465: The compiler incorrectly removed some code
assuming it was unreachable when it was in
fact needed. This has been fixed.
Resolution: Recompile with the new compiler.
10)JAGad73529: The compiler was built with the wrong version
of the error message file. This has been
fixed.
Resolution: Recompile with the new compiler.
11)JAGad74647: There was a problem with the variable step
transformation. This has been fixed.
Resolution: Recompile with the new compiler.
12)JAGad77170: The compiler generated SAVE tags for an
automatic variable. This has been fixed.
Resolution: Recompile with the new compiler.
13)JAGad77176: The compiler did not clear the USEASSOCIATED
bit for use variables which were privatized.
This has been fixed.
Resolution: Recompile with the new compiler.
14)JAGad77883: An INTERFACE Assignment definition prevented
the compiler from resolving an operator. This
has been fixed.
Resolution: Recompile with the new compiler.
15)JAGad79146: The compiler was using the incorrect variable
hashlinenumber which did not always track
line number. This has been fixed.
Resolution: Recompile with the new compiler.
16)JAGad81039: When propagating type tags from uplevel
imported module to the nested routine,
the compiler was not checking to see if
the type tags had already been set. This
has been fixed.
Resolution: Recompile with the new compiler.
17)JAGad81737: The compiler inadvertantly modified loops
not directly attached to OMP DO directives.
This has been fixed.
Resolution: Recompile with the new compiler.
18)JAGad81738: The compiler was not correctly typing
I*8 induction variables. This has been
fixed.
Resolution: Recompile with the new compiler.
19)JAGad82866: The compiler was incorrectly using the
address of the repetition count instead of
the repetition count. This has been fixed.
Resolution: Recompile with the new compiler.
SR:
1653237206 8606102064 8606105391 8606129091 8606134666
8606138917 8606146346 8606192958 8606193128 8606203884
8606204193 8606204286 8606204347 8606205472 8606207992
8606207998 8606208696 8606209960 8606211851 8606212551
8606212552 8606213675 8606215466 8606215988 8606216083
8606216201 8606216202 8606216568 8606217231 8606218190
8606218230 8606218266 8606218364 8606219457 8606219622
8606219988 8606220986 8606221235 8606221260 8606221343
8606218489 8606220735 8606223019 8606223020 8606106993
8606137253 8606222745 8606223819 8606223985 8606224069
8606224070 8606224378 8606224490 8606225428 8606224016
8606226117 8606226118 8606226709 8606226750 8606226873
8606227023 8606227262 8606227239 8606227765 8606227905
8606227912 8606228148 8606228443 8606228499 8606228831
8606229185
Patch Files:
/opt/fortran90/bin/f90
/opt/fortran90/lbin/f90com32
/opt/fortran90/lbin/f90com64
/opt/fortran90/lib/libF90.a
/opt/fortran90/lib/pa2.0/libF90.a
/opt/fortran90/lib/nls/C/libF90.cat
/opt/fortran90/lib/nls/msg/C/f90.cat
/opt/fortran90/lib/nls/msg/C/f90com.cat
/opt/fortran90/share/man/man1.Z/f90.1
/opt/fortran90/share/man/ja_JP.eucJP/man1.Z/f90.1
/opt/fortran90/share/man/ja_JP.SJIS/man1.Z/f90.1
what(1) Output:
/opt/fortran90/bin/f90:
HP-UX f90 20011204 (233946) B3907DB/B3909DB PHSS_25
858 B.10.20.48
HP F90 v2.5.9
/usr/lib/libc: $Revision: 76.3 $
/opt/fortran90/lbin/f90com32:
HP F90 v2.5.9
HP-UX SLLIC/OPTIMIZER UX.11.01.96 (ROSE): 11/16/98
HP aC++ B3910B A.01.19.02 Classic Iostream Library
HP aC++ B3910B A.01.19.02 Language Support Library
Ucode Code Generator - UX11.01.04(GS IB4) (PACG - No
vember 16, 1998)
HP-UX f90com32 20011205 (110012) B3907DB/B3909DB PH
SS_25858 B.10.20.48
Copyright (c) 1993-2001 HP. All Rights Reserved.
HP Fortran-95 Version F95D4 HP:131200:080240
Ucode-2 Version 2-6
High Level Optimizer - 04-Dec-2001.22:56
/usr/lib/libc: $Revision: 76.3 $
/opt/fortran90/lbin/f90com64:
HP F90 v2.5.9
HP-UX SLLIC/OPTIMIZER UX.11.01.96 (ROSE): 11/16/98
HP aC++ B3910B A.01.19.02 Classic Iostream Library
HP aC++ B3910B A.01.19.02 Language Support Library
Ucode Code Generator - UX11.01.04(GS IB4) (PACG - No
vember 16, 1998)
HP-UX f90com64 20011205 (111638) B3907DB/B3909DB PH
SS_25858 B.10.20.48
Copyright (c) 1993-2001 HP. All Rights Reserved.
HP Fortran-95 Version F95D4 HP:131200:080240
Ucode-2 Version 2-6
High Level Optimizer - 04-Dec-2001.22:56
/usr/lib/libc: $Revision: 76.3 $
/opt/fortran90/lib/libF90.a:
None
/opt/fortran90/lib/pa2.0/libF90.a:
None
/opt/fortran90/lib/nls/C/libF90.cat:
None
/opt/fortran90/lib/nls/msg/C/f90.cat:
None
/opt/fortran90/lib/nls/msg/C/f90com.cat:
None
/opt/fortran90/share/man/man1.Z/f90.1:
None
/opt/fortran90/share/man/ja_JP.eucJP/man1.Z/f90.1:
None
/opt/fortran90/share/man/ja_JP.SJIS/man1.Z/f90.1:
None
cksum(1) Output:
2756182248 552960 /opt/fortran90/bin/f90
662820057 12189696 /opt/fortran90/lbin/f90com32
3438766918 12263424 /opt/fortran90/lbin/f90com64
2048174389 4104160 /opt/fortran90/lib/libF90.a
2393100507 4380764 /opt/fortran90/lib/pa2.0/libF90.a
1589122412 9505 /opt/fortran90/lib/nls/C/libF90.cat
3003341517 16737 /opt/fortran90/lib/nls/msg/C/f90.cat
2106671116 115447 /opt/fortran90/lib/nls/msg/C/f90com.cat
2787625229 28185 /opt/fortran90/share/man/man1.Z/f90.1
3306331455 32415 /opt/fortran90/share/man/ja_JP.eucJP/
man1.Z/f90.1
1541050148 32531 /opt/fortran90/share/man/ja_JP.SJIS/man1.Z/
f90.1
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_25771 PHSS_25616 PHSS_25520 PHSS_25413 PHSS_25175 PHSS_24771
Equivalent Patches: None
Patch Package Size: 33010 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_25858
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHSS_25858.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHSS_25858. 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_25858.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_25858.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
The baselines to which this patch applies are AR0901 or
AR1201. It will not install over patch PHSS_23952 or
earlier.
-----End of Document ID: PHSS_25858------------------------------------------
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]