|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: AIX Service Mail Server (aixserv
austin.ibm.com)Date: Tue Jun 26 2001 - 02:21:30 CDT
APAR: IY18276 COMPID: 5622DJX00 REL: 211
ABSTRACT: APAR FOR PTF 9 FOR DATAJOINER V2 AIX PLATFORM V211
PROBLEM DESCRIPTION:
APAR FOR PTF 9 FOR DATAJOINER V2 AIX PLATFORM V211
------
APAR: IY18524 COMPID: 5765E6100 REL: 510
ABSTRACT: BINDER COREDUMPS WITH KAI COMPILER
PROBLEM DESCRIPTION:
Customer is facing the problem while compiling and linking.
While linking the application,binder core dumps with SEGV. The
problem only shows up when you use rtl, lapi, and
noobjreorder (but that isn't an unusual combination) with a
KCC compiled routine and one of the KCC libraries (but,
ofcourse, KAI claims that this is a binder problem and not a
problem with their stuff.) The load line needed to show the
problem is as follows: ld /lib/mcrt0.o -bnoobjreorder tttt.o
-L/usr/lpp/ppe.poe/lib -binitfini:poe_remote_main -lmpi_r
-llapi_ above line includes an "r" to finish -llapi_r and the
last line follows libKCC-eh-ts_so.a -brtl -lc I have given you
on snow a tar file with the above information, the tttt.o file,
and the libKCC-eh-ts_so.a library (which I got permission from
KAI to give to IBM for purposes of finding this problem.)
PROBLEM SUMMARY:
The binder coredumps in some cases when -brtl, -bnoobjreorder
are used
PROBLEM CONCLUSION:
Incrementing the export counter for bss symbol will resolve.
------
APAR: IY18525 COMPID: 5765E6100 REL: 510
ABSTRACT: SYSTEM CRASHED WHEN CUSTOMER IS USING THE SHARED LIBRARY NAME
PROBLEM DESCRIPTION:
System crashes due to memory leak, when a shared library name
is used as a directory, in the library path.
PROBLEM SUMMARY:
System crashes due to memory leak, when a shared library
name is a directory.
PROBLEM CONCLUSION:
System crashes due to memory leak,
when a shared library name is a directory.
------
APAR: IY18534 COMPID: 5765E6100 REL: 510
ABSTRACT: FILEMON REPORTS NEGATIVE VALUES
PROBLEM DESCRIPTION:
filemon reports the time in negative and also
the CPU utilization is some times negative and some times
a wrong value.
PROBLEM CONCLUSION:
fixed the problem by making data types consistant across
filemon code.
------
APAR: IY18535 COMPID: 5765E6100 REL: 510
ABSTRACT: AGENT'S LIBRARY DOESN'T SEND CORRECT CPU VALUES TO SNMP
PROBLEM DESCRIPTION:
The values for CPU stats supplied by libSpmi to snmp daemon
are incorrect or zero.
PROBLEM CONCLUSION:
modified the code of Agent's shared library to
retrive & calculate the CPU stats correctly
------
APAR: IY18536 COMPID: 5765E6100 REL: 510
ABSTRACT: TOPAS IS SHOWING ONLY 6 DIGITS OF PID
PROBLEM DESCRIPTION:
Customer will be able to see only 6 digits for PID even if
it has more than 6 digits.
PROBLEM CONCLUSION:
topas was getting the PID info from the description string of
the process context,now modified the code to get the pid
from the Context name which gives the full pid.
------
APAR: IY18537 COMPID: 5765E6100 REL: 510
ABSTRACT: CALCULATIONS FOR KERNCPU, USERCPU, CPUPCT ARE WRONG
PROBLEM DESCRIPTION:
kerncpu, usercpu, cpupct values exceed 100%.
PROBLEM CONCLUSION:
modified the code to implement the correct
conversion factor for calculation of the above mentioned stats
------
APAR: IY18557 COMPID: 5765E6100 REL: 510
ABSTRACT: DRIVE UNCONFIGURED ERRORS AND COSMETIC FIXES
PROBLEM DESCRIPTION:
imperfect user interface.
PROBLEM CONCLUSION:
Small code change
------
APAR: IY18558 COMPID: 5765E6100 REL: 510
ABSTRACT: MEMORY LEAK RELATED TO STATIC INITIALIZATION OF MUTEX AND CV
PROBLEM DESCRIPTION:
popserv core dumps - exceeds 2gb of heap
PROBLEM CONCLUSION:
turn off dbx allocations by default.
------
APAR: IY18559 COMPID: 5765E6100 REL: 510
ABSTRACT: CLIPPED CONCAVE POLYGONS ARE SLOW ON GXT6000
PROBLEM DESCRIPTION:
Dust particles are displayed in certain area of a model. Pixel
level holes or overpaints are displayed on irregular pixel
position for each redraw. It looks like a dust particle. It
emerges not on whole screen but on certain area of a model.
PROBLEM SUMMARY:
The following problem occurs on GXT6000P when doing clipped
polygons:
Dust particles are displayed in certain area of a model. Pixel
level holes or overpaints are displayed on irregular pixel
position for each redraw. It looks like a dust particle. It
emerges not on whole screen but on certain area of a model.
APAR IY14967 was the original fix for this problem, but a hang
was introduced in certain situations.
PROBLEM CONCLUSION:
The original fix had performance implications. This new fix
regains the original performance for rendering clipped poly-
gons. The new fix also removes the hang situations caused by
APAR IY14967. The new fix utilizes a different set of hardware
commands when rendering clipped polygons.
------
APAR: IY18561 COMPID: 5765E6100 REL: 510
ABSTRACT: FC I/O HANG AFTER SHARK WARMSTART OR CABLE PULL ERROR INJECT
PROBLEM DESCRIPTION:
FC I/O may hang on AIX host, especially when DPO with 4 or
more paths is used.
PROBLEM CONCLUSION:
Correctly preserve error recover flags on back-to-back check
conditions as well as clear ACA flags when non-ACA error
recovery occurs to insure halted queues are resumed.
------
APAR: IY18639 COMPID: 5765E6100 REL: 510
ABSTRACT: PTY CAN WASTE CPU TIME DURING SLAVE CLOSE
PROBLEM DESCRIPTION:
When a pts closes and there is output on the ptc, the thread
closing the pts will wake itself up along with the gil thread
in an endless loop. This consumes cpu time for no benifit.
PROBLEM CONCLUSION:
The solution is to remove two unneeded qenables from the
code.
------
APAR: IY18733 COMPID: 5765E6100 REL: 510
ABSTRACT: OGL STRESS CAUSES SYSTEM BUS TIMEOUT AND CHECKSTOP
PROBLEM DESCRIPTION:
A locking mechanism that would synchronize the interrupt
handler and the FIFO drain to workaround a HW bug has a hole.
Under the rare case, the interrupt mask might get turned on
while the FIFO drain was still holding the lock and caused
the bus timeout.
PROBLEM CONCLUSION:
Fixed the DD interrupt handler code to prevent the interrupt
mask to be enabled before its time.
------
APAR: IY18823 COMPID: 5765E6100 REL: 510
ABSTRACT: THE GXT2000P MAY NOT COPY THE STENCIL BUFFER.
PROBLEM DESCRIPTION:
The GXT2000P graphics adapter may not copy the stencil buffer
when windows are moved.
PROBLEM CONCLUSION:
Update the FRG_SWMASK register so the stencil mask will be
set correctly.
------
APAR: IY18824 COMPID: 5765E6100 REL: 510
ABSTRACT: PROBLEMS WITH OPENGL RENDERING USING GL_QUAD_STRIP ON SEVERAL
PROBLEM DESCRIPTION:
OpenGL rendering using GL_QUAD_STRIP vertex arrays may not
produce correct results on the GXT500, GXT500D, GXT500P,
GXT550P, GXT800P, or GXT800M. Vertex arrays include
glDrawArrays, glDrawElements, glDrawRangeElements,
glMultDrawArraysEXT, and glMultiDrawElementsEXT. This problem
should only occur when object coordinates are not required
for the computation of color, fog, and texture.
PROBLEM CONCLUSION:
Don't call transform specialist when ending a quad strip
vertex array. The buffer vertex data will get flushed by the
vertex array specialist.
------
APAR: IY18825 COMPID: 5765E6100 REL: 510
ABSTRACT: EDGE FLAG DOES NOT WORK IN PVT_BUTTERFLY
PROBLEM DESCRIPTION:
OpenGL applications running on the GXT6000P will not get
correct edge flags when rendering vertex arrays with edgeflags
specified using the glEdgeFlagPointerListIBM function call.
Using glEdgeFlagPointer or glEdgeFlagPointerEXT are ok.
PROBLEM CONCLUSION:
Reverse the setting of the slow and fast vertex arrays
rendering flags. They were backwards.
------
APAR: IY18826 COMPID: 5765E6100 REL: 510
ABSTRACT: GXT6000P HANGS WHEN RENDERING MULTI-VERTEX ARRAYS
PROBLEM DESCRIPTION:
OpenGL application on the GXT6000P may dump core or hang the
graphics display when rendering multi-vertex arrays. This
includes the OpenGL functions glMultiDrawArraysEXT,
glMultiDrawElementsEXT, glMultiModeDrawArraysIBM, and
glMultiModeDrawElementsIBM.
This problem can only occur if GL_CULL_VERTEX_IBM (see
GL_IBM_vertex_cull extension), a primitive has a 0 or less
vertex count, or a primitive "mode" is invalid.
PROBLEM CONCLUSION:
Move userqueue assurance checks to the top of the primitive
look so that check are made on the primitives rendered.
Otherwise, without adequate assurance UQ buffers may overflow.
------
APAR: IY18827 COMPID: 5765E6100 REL: 510
ABSTRACT: OPENGL DLIST CLIPPING ERRORS ON GXT4000
PROBLEM DESCRIPTION:
Incorrect clipping for display list primitives on
GXT2000P, GXT3000P, GXT4000P, GXT6000P.
PROBLEM CONCLUSION:
Change computation of global bounding box so that it
accounts for all necessary orientations.
------
APAR: IY18828 COMPID: 5765E6100 REL: 510
ABSTRACT: SUSPENDED OPENGL APPLICATIONS MAY LOCK DISPLAY
PROBLEM DESCRIPTION:
Suspending (ĒZ) a OpenGL application on the GXT4000P and
GXT6000P on AIX 510 should not have th potential of locking
up the graphics display.
PROBLEM CONCLUSION:
Correct typo that resulting in the critical section logic
not to be inserted.
------
APAR: IY18829 COMPID: 5765E6100 REL: 510
ABSTRACT: PATTERNED LINE CAN DISPLAY INCORRECTLY ON GXT6000P
PROBLEM DESCRIPTION:
A patterned line with a pattern length that exceeds 4 will
display incorrectly on GXT6000P.
PROBLEM SUMMARY:
A patterned line with a pattern length greater than 4 will
display incorrectly on GXT6000P.
PROBLEM CONCLUSION:
Change the shift count used to combine the pattern length into
the Line Style Pattern commands to the hardware from 20 to 16.
------
APAR: IY18830 COMPID: 5765E6100 REL: 510
ABSTRACT: GXT6000P/4000P FAILS TO DISPLAY CURSOR COLOR
PROBLEM DESCRIPTION:
When using multicolor cursor extension with the GXT4000P or
GXT6000P graphics adapter, the cursor may display the wrong
color.
PROBLEM CONCLUSION:
Shift the 16 bit RGB color components for the cursor to the
right by 8 bits so the upper 8 bits will be used. This will
allow the graphics adapter to use the most significant bits
to display the cursor's color.
------
APAR: IY18832 COMPID: 5765E6100 REL: 510
ABSTRACT: NIS+: PARTIAL SUCCESS WHEN CHANGING PASSWORDS
PROBLEM DESCRIPTION:
When changing password in a NIS+ environment, the user gets the
message: "Partial success changing NIS+ password.". In spite
of this error message, the password actually gets changed
correctly.
LOCAL FIX:
None, just disregard the error message.
PROBLEM SUMMARY:
When changing password in a NIS+ environment, the user gets the
message: "Partial success changing NIS+ password.". In spite
of this error message, the password actually gets changed
correctly.
PROBLEM CONCLUSION:
change the password field only. Keep gecos and shell alone.
------
APAR: IY18834 COMPID: 5765E6100 REL: 510
ABSTRACT: XNFS: NSM FAILURES FOR STATE CHANGES
PROBLEM DESCRIPTION:
nfs failed the xnfs test if you run nsm8 and nsm10
together.
PROBLEM CONCLUSION:
if it's itself then it will not send the notification to itself
twice. (only for -x option)
------
APAR: IY18836 COMPID: 5765E6100 REL: 510
ABSTRACT: MANAGING MOUNTD AUXILIARY CONNECTIONS
PROBLEM DESCRIPTION:
rpc.mountd does not use reserved port to do rpc call
so the port number vary. can't write fire wall rules
for it.
PROBLEM CONCLUSION:
rpc.mountd will first use the entries in /etc/services if
there is any. If it does not have an entries in /etc/services
then it'll use the non-reserved port.
------
APAR: IY18837 COMPID: 5765E6100 REL: 510
ABSTRACT: NFSO DOES NOT SHOW THR RIGHT INFO ON 64BIT MACHINE
PROBLEM DESCRIPTION:
some of the nfso options have the wrong number in
64 bit kernel.
PROBLEM CONCLUSION:
type cast it from ulong to uint
------
APAR: IY18842 COMPID: 5765E6100 REL: 510
ABSTRACT: PERFORMANCE ON NETIF_BACKUP
PROBLEM DESCRIPTION:
failover from link status takes too long (i.e. 12-15 sec
range)
PROBLEM CONCLUSION:
failover takes 2-3 sec range
------
APAR: IY18843 COMPID: 5765E6100 REL: 510
ABSTRACT: SYSTEM DSI CRASH IN GXENTDD
PROBLEM DESCRIPTION:
System DSI crash in gxentdd. Stack trace appears
as follows:
MST STACK TRACE:
(excpt=0000000a:0a000000:00000000:0000000a:00000106)
(intpri=3)
IAR: . gxentdd:undo_rx +f8 (051bb0a0): sthx r0,r5,r4
LR: . gxentdd:start_adapter +550 (051b8ea0)
00436bc0: . gxentdd:start_adapter +550 (051b8ea0)
00436c30: . gxentdd:reset_timeout +15c (051becb4)
00436c90: .watchdog+d4 (0008e274)
00436cf0: .sys_timer+474 (0002def4)
00436d80: .clock+134 (0002e448)
00436de0: .i_softmod+2a8 (0001c3b0)
00436e70: flih_603_patch+cc (0002863c)
------
APAR: IY18847 COMPID: 5765E6100 REL: 510
ABSTRACT: VARYON MWCC TSTAMP WRITE NOT NEEDED
PROBLEM DESCRIPTION:
In a shared disk environment where nodeA
has read/write access and nodeB has read
only access to the disk, if we do an
extendvg and then 'importvg -L' to teach
nodeB about the change, the 'importvg -L'
might fail.
Varyon will try to update the on disk mwcc
timestamp for the newly added disk. nodeB
has read only access to the disk so the write
would fail and therefore so would the varyon.
PROBLEM CONCLUSION:
Don't update the on disk mwcc timestamp
at varyon time. We do update the on disk mwcc
timestamp at other times which are more
appropriate, and doing it at varyon time is
redundant.
------
APAR: IY18849 COMPID: 5765E6100 REL: 510
ABSTRACT: SINGLE USER MODE FROM DIAGNOSTICS
PROBLEM DESCRIPTION:
cannot access single user mode when booting from
disk in service mode when booting with 64 bit kernel
PROBLEM CONCLUSION:
replace sysconfig() with sys_parm()
------
APAR: IY18850 COMPID: 5765E6100 REL: 510
ABSTRACT: BOOT PROCESS NEEDS TO SYNC DISK WRITES IN RC.BOOT
PROBLEM DESCRIPTION:
Under very rare circumstances, the Cu* ODM databases might be
empty when booting from removeable media into maintenance mode.
PROBLEM CONCLUSION:
Use the sync command to flush copied data to the hard disk.
------
APAR: IY18851 COMPID: 5765E6100 REL: 510
ABSTRACT: PPDD DOES NOT DO COPYIN OF DDS AND CAUSES DSI
PROBLEM DESCRIPTION:
On the latest levels of 4.3.3, the machine will DSI while in
pp_read_POS. This is being called from ppinit_dev which
is called from ppconfig in ppdd. The ultimate reason
for the DSI is that the driver is attempting to access the
dds up in user space directly rather than using copyin. It
apears that this use to work until the latest builds but it
is a forbidden practice.
PROBLEM SUMMARY:
On the latest levels of 4.3.3, the machine will DSI while in
pp_read_POS. This is being called from ppinit_dev which
is called from ppconfig in ppdd. The ultimate reason
for the DSI is that the driver is attempting to access the
dds up in user space directly rather than using copyin. It
apears that this use to work until the latest builds but it
is a forbidden practice.
PROBLEM CONCLUSION:
The solution is to use copyin to copy in the dds into local
storage and then access the fields.
------
APAR: IY18852 COMPID: 5765E6100 REL: 510
ABSTRACT: SUBNET MASK WITH MULTIPLE ADAPTERS
PROBLEM DESCRIPTION:
On the IA64 machine with multiple adapter cards,
it will allow you to change the subnet mask
without any problem. The icon states SUCCESS.
When you refresh the window for Token Ring,
the subnet mask has the same value as the IP address.
The work around for this problem is to stop then
restart wsm
PROBLEM CONCLUSION:
So far there was a problem with the detection of
multiple adapter cards. This code change fixes this
problem.
------
APAR: IY18853 COMPID: 5765E6100 REL: 510
ABSTRACT: SCSI HARD DRIVE ENCLOSURE LED'S DO NOT WORK
PROBLEM DESCRIPTION:
The SCSI hard drive enclosure LED's will fail to blink for the
identify, insert/remove commands.
PROBLEM CONCLUSION:
The bug exists in bos.diag.util 4.3.3.26 and later.
Use a prior level for proper operation.
The PTF associated with this APAR fixes the bug.
------
APAR: IY18854 COMPID: 5765E6100 REL: 510
ABSTRACT: UDP-BASED RPC PROGRAMS CAN GET IN A SPIN
PROBLEM DESCRIPTION:
Due to some network events (ICMP Host/Port unreachable),
UDP-based RPC programs using libnsl can get in a spin, quickly
using up available memory and sometimes even causing system
lockups.
PROBLEM CONCLUSION:
If an error is posted to a stream head in svc_dg_recv and
svc_dg_reply, it is not enough to just do a t_rcvuderr(), since
the error that is set on the socket does not get cleared. All
following operations will result in the same error being
posted. Instead, t_optmgmt will be called with the option level
with XTI_GENERIC, name with XTI_ERROR, and option req. flags
with T_NEGOCIATE, causing the error to be read and cleared off
of the socket as well.
------
APAR: IY18855 COMPID: 5765E6100 REL: 510
ABSTRACT: RPC.MOUNTD MEMORY LEAK / LOCKUP
PROBLEM DESCRIPTION:
The changes made in APAR IY10455 (bos.net.nfs.client 4.3.3.31)
had two issues, causing a slow but steady memory leak as well
as a risk of lockups of rpc.mountd, making it stop servicing
new requests.
PROBLEM CONCLUSION:
One of the struct hostent fields that are duplicated for each
mountd request never gets deallocated. This causes a slow but
steady memory leak. Also, one unlock operation was accidentally
moved under an if condition, sometimes causing a lockup since
the lock was not released before the thread exited.
------
APAR: IY18856 COMPID: 5765E6100 REL: 510
ABSTRACT: SHUTDOWN OF LOCKD VERY SLOW
PROBLEM DESCRIPTION:
When there are many NFS clients which do file locking on an
NFS server, it may take a long time for rpc.lockd to exit
after it is asked to shutdown.
PROBLEM CONCLUSION:
Can vfs_search/vn_search only once when determining if
locks exists for the cached sysid's.
------
APAR: IY18858 COMPID: 5765E6100 REL: 510
ABSTRACT: NIM DISKLESS CLIENT INSTALLATION ERROR.
PROBLEM DESCRIPTION:
When an NFS server is running a 64-bit kernel, all mknod
requests from the client will create the device with a
major number of zero.
PROBLEM CONCLUSION:
Correct device conversions on server.
------
APAR: IY18859 COMPID: 5765E6100 REL: 510
ABSTRACT: BOS INSTALL, COULD NOT CREATE THE / FILE SYSTEM
PROBLEM DESCRIPTION:
A tape system backup of a 64bit jfs2 system will fail to
reinstall.
PROBLEM CONCLUSION:
Add the jfs2 helpers to the tapefiles1 file.
------
APAR: IY18861 COMPID: 5765E6100 REL: 510
ABSTRACT: MIGRATEPV FAILING WITH MULTIPLE DESTINATION PVS
PROBLEM DESCRIPTION:
The migratepv command is returning Illegal parameter error in
certain cases with multiple destination PVs.
migratepv -l <lvname> hdisk0 hdisk1 hdisk2
0516-022 lmigratelv: Illegal parameter or structure value.
0516-812 migratepv: Warning, migratepv did not completely
succeed.
The following conditions apply, for this error to occurr: 1.
There are multiple destination PVs(hdisk1 hdisk2 ) 2. hdisk1
should have some USED PPs. 3. The USED PPs distribution on
hdisk1 and hdisk2 should
be complimentary.(corresponding pp nos which are used in
hdisk1 should be free on hdisk2).
PROBLEM SUMMARY:
migratepv fails with error , as lvm_migratelv()
returns illegal parameter or value.
when there are multiple destination PVs
PROBLEM CONCLUSION:
Ensure that when ever the newpv_id(dest PV) inside the loop
changes, the routine get_pvandpp() is called for that PVid.
Now the savepp2 (which is used to calculate the individual PP
address) will contain the starting PP address of the changed
dest PV.(Earlier it contains the starting PP adress of first
destination PV regardless of the number of destination PVs).
------
APAR: IY18862 COMPID: 5765E6100 REL: 510
ABSTRACT: NODE CRASHES AFTER CONCURRENT-CAPABLE VG IS VARIED OFF.
PROBLEM DESCRIPTION:
A concurrent-capable volume group is varied on
concurrently(varyonvg -c testvgX). When it is
varied off(varyoffvg testvgX), the machine
crashes shortly afterward. This occurs with
AIX 5.1. This is due to a pointer being freed twice.
PROBLEM CONCLUSION:
Remove duplicate code from several places and allow the
hd_vgcleanup() routine to free structures within the VG
structure when varying off a VG.
------
APAR: IY18865 COMPID: 5765E6100 REL: 510
ABSTRACT: YPPUSH DOES NOT WAIT FOR CHILDREN TO FINISH
PROBLEM DESCRIPTION:
yppush does not wait until all the children finished.
------
APAR: IY18866 COMPID: 5765E6100 REL: 510
ABSTRACT: PASSWD -R NISPLUS CORE DUMPS
PROBLEM DESCRIPTION:
it cores when changing password on IA
PROBLEM CONCLUSION:
didn't assign the return variable to NULL
------
APAR: IY18869 COMPID: 5765E6100 REL: 510
ABSTRACT: ULTRA2 SCSI PCI ADAPTER DIAGNOSTICS CAUSES AIX ERROR LOG
PROBLEM DESCRIPTION:
Running diagnostics on the Ultra 2 SCSI PCI Adapter(Channel B)
causes an error to be logged against Channel A in the error
log.
PROBLEM CONCLUSION:
Ignore the error message. It does not indicate a failure
on the adapter.
------
APAR: IY18871 COMPID: 5765E6100 REL: 510
ABSTRACT: CANNOT PREINSTALL HI_IN KEYBOARD MAP
PROBLEM DESCRIPTION:
Customer unable to bos install Hindi
PROBLEM CONCLUSION:
Changed bosinst_menu to yes in ILS.add
------
APAR: IY18877 COMPID: 5765E6100 REL: 510
ABSTRACT: DISABLING TEXTURE KILLING DOESN'T WORK
PROBLEM DESCRIPTION:
Debugging texture mapped OpenGL applications on the GXT4000P
and GXT6000P often results in the application being killed.
The _RMS_DEBUG_PROCESS environment variable was added to keep
the device driver from killing the application when being
debugged. However, dbx then doesn't work if being run from
the local display without also disabling the texture thread.
PROBLEM CONCLUSION:
Remove SIGTRAP from the list of signals masked by the texture
manager thread.
------
APAR: IY18878 COMPID: 5765E6100 REL: 510
ABSTRACT: OPENGL CAN HANG WHEN USING TEXTURE MAPPING
PROBLEM DESCRIPTION:
OpenGL applications that use texture mapping might hang
on the GXT2000P, GXT3000P, GXT4000P, or GXT6000P.
PROBLEM CONCLUSION:
Make sure the domain is locked whenever the shared textures
structures are accessed.
------
APAR: IY18879 COMPID: 5765E6100 REL: 510
ABSTRACT: GLXCOPYCONTEXT MAY DUMP CORE ON GXT4000P
PROBLEM DESCRIPTION:
Calling glXCopyContext on a GXT4000P can result in a core
in the function __glCopyContext.
PROBLEM CONCLUSION:
Don't attempt to fetch the current active texture using a
GC point that has not been initialized.
------
APAR: IY18881 COMPID: 5765E6100 REL: 510
ABSTRACT: GXT4000/6000 EXTSHM=ON HANGS ADAPTER IF GLX EXTENTION USED.
PROBLEM DESCRIPTION:
The OpenGL README recommends setting EXTSHM=ON to maximize
the available segments. However, setting on the GXT4000P and
GTX6000P causes the X server to hang during startup.
PROBLEM CONCLUSION:
Don't detach the texture shared memory region within the
X server.
------
APAR: IY18884 COMPID: 5765E6100 REL: 510
ABSTRACT: TABLET WILL KILL X AFTER RUNNING TEST CASE 3RD TIME
PROBLEM DESCRIPTION:
X process dies after changing the primary pointer to a tablet
after several iterations.
PROBLEM CONCLUSION:
Make sure device is open in the "device on" case statement.
------
APAR: IY18886 COMPID: 5765E6100 REL: 510
ABSTRACT: 64BIT KERNEL STACK OVERFLOW IN SO_PIN_MORE_STACK
PROBLEM DESCRIPTION:
crash in uipc code dealing with accessing paged out stack
space while interrupts are disabled
PROBLEM CONCLUSION:
remove the adjustment to the backward pinning of the stack
------
APAR: IY18893 COMPID: 5765E6100 REL: 510
ABSTRACT: BOSINSTLOG HAS MK_JFS2 CATALOG OPEN ERROR
PROBLEM DESCRIPTION:
During bos install JFS2 mkfs issues error messages when it
fails to open the message catalog file.
PROBLEM CONCLUSION:
Don't issue error message when JFS2 mkfs cannot open the
message catalog file.
------
APAR: IY18897 COMPID: 5765E6100 REL: 510
ABSTRACT: UPT64BK -MOE HUNG - COULD NOT LOG IN
PROBLEM DESCRIPTION:
Extending a jfs2 file system while the system is under
heavy load may leave the chfs process and other processes
deadlocked.
PROBLEM CONCLUSION:
This problem is corrected by a modification to the
serialization strategy for quiescing the file system
while the file system is being extending.
------
APAR: IY18903 COMPID: 5765E6100 REL: 510
ABSTRACT: TRCNM DOES NOT WORK ON 64BK
PROBLEM DESCRIPTION:
trcnm cammand does not work on 64 bit env.
PROBLEM CONCLUSION:
Make sure to check for magic numbers for both 32 bit and 64
bit kernels
------
APAR: IY18909 COMPID: 5765E6100 REL: 510
ABSTRACT: X SERVER CORES WHEN DESTROYING GLX RESOURCES
PROBLEM DESCRIPTION:
The X-Server may core dump when closing an application's
window.
PROBLEM CONCLUSION:
Free the clients resources in reverse order.
------
APAR: IY18911 COMPID: 5765E6100 REL: 510
ABSTRACT: SPMI CAN'T HANDLE SOME 64 BIT SIQUANT VALUES
PROBLEM DESCRIPTION:
Some of the 64 Bit Quants values are wrong due to it very
large values
PROBLEM CONCLUSION:
Changed the base unit of these values to a higher range. For
e.g. all the byte values will be displayed as Kilobytes from
now onwards.
------
APAR: IY18926 COMPID: 5765E6100 REL: 510
ABSTRACT: THE X-SEVER MAY CORE DUMP OR LEAK MEMORY.
PROBLEM DESCRIPTION:
The X-Server may core dump or leak memory.
PROBLEM CONCLUSION:
Assign pGC->ops->devPrivate.val to 0 so the pGC->ops static
structure in sonValidateGC will not be freed.
------
APAR: IY18929 COMPID: 5765E6100 REL: 510
ABSTRACT: NOINTEGRITY DOES NOT WORK FOR 64BIT KERNEL
PROBLEM DESCRIPTION:
Mounting JFS filesystem with nointegrity option returned
EFORMAT in 64-bit kernel.
PROBLEM CONCLUSION:
If VFS_NOINTEG is set in vfs_flag, don't bother to check/
obtain the logdev number.
------
APAR: IY18933 COMPID: 5765E6100 REL: 510
ABSTRACT: INUTOC COMMAND CREATES A .TOC WHEN NO BFF IMAGE IN THE DIR.
PROBLEM DESCRIPTION:
inutoc creates invalid .toc files when there are no
valid fileset images in the directory specified on
the command line.
PROBLEM CONCLUSION:
Have intoc remove the invalid .toc file.
------
APAR: IY18942 COMPID: 5765E6100 REL: 510
ABSTRACT: GXT6000P/4000P CODE CLEAN UPS
PROBLEM DESCRIPTION:
Unused texture memory.
PROBLEM CONCLUSION:
Set the texute memory bank offsets right.
------
APAR: IY18944 COMPID: 5765E6100 REL: 510
ABSTRACT: ENCRYPTION ALGORITHM NOT GREYED OUT FOR AH
PROBLEM DESCRIPTION:
While creating a manualtunnel, the user can choose AH for the
tunnel. While choosing AH, the encryption algorithm has to be
greyed out, as is not relevant in such a scenario.
PROBLEM CONCLUSION:
Code has been modified to grey out the encryption algorithm
field, when AH is selected while creating the manualtunnel.
------
APAR: IY18946 COMPID: 5765E6100 REL: 510
ABSTRACT: DATABASE CORRUPTION ON TUNNEL UPDATE
PROBLEM DESCRIPTION:
Under certain conditions, an update of a phase 1 tunnel will
not work. This typically happens when a tunnel was created
to use an RSA Signature as its validation scheme, and then
the proposal is changed to pre-shared key, and then a tunnel
which points to that proposal is updated.
PROBLEM CONCLUSION:
Allowed deletion of the pre-shared key on a tunnel update to
fail, which is a valid response in the case described above.
------
APAR: IY18950 COMPID: 5765E6100 REL: 510
ABSTRACT: SEG FAULT/CORE IN GP_UTILITIES.PRE_MALLOC
PROBLEM DESCRIPTION:
Customers graPHIGS based application triggers
a segmentation fault. The generated core files
shows the following:
(dbx) where
gP_utilities.pre_malloc(??, ??) at 0xd1eea5f8
AFMO_process_local_structures(??, ??, ??) at 0xd12056c0
AFMO_process_local_structures(??, ??, ??) at 0xd1204b04
afmotrv(??, ??) at 0xd12046a8
afmoctl(??, ??) at 0xd120f608
afmopr(??, ??) at 0xd1209ba0
afmnwcr(??) at 0xd1180924
afmnndp(??) at 0xd116cd90
PROBLEM SUMMARY:
Customers graPHIGS based application triggers
a segmentation fault. The generated core files
shows the following:
(dbx) where
gP_utilities.pre_malloc(??, ??) at 0xd1eea5f8
AFMO_process_local_structures(??, ??, ??) at 0xd12056c0
AFMO_process_local_structures(??, ??, ??) at 0xd1204b04
afmotrv(??, ??) at 0xd12046a8
afmoctl(??, ??) at 0xd120f608
afmopr(??, ??) at 0xd1209ba0
afmnwcr(??) at 0xd1180924
afmnndp(??) at 0xd116cd90
PROBLEM CONCLUSION:
Add check for null pointer returned by
malloc_solid_se_info before attempting to
use the returned pointer.
------
APAR: IY18951 COMPID: 5765E6100 REL: 510
ABSTRACT: FVTI:TPROF CORE DUMPS WHEN USED WITH -J SOMETIMES
PROBLEM DESCRIPTION:
tprof with -j segfaults intermittently
PROBLEM CONCLUSION:
Fixed the Memory Overflow problem
------
APAR: IY18953 COMPID: 5765E6100 REL: 510
ABSTRACT: QDAEMON OCCASIONALLY HANGS
PROBLEM DESCRIPTION:
qdaemon hangs occasionally while handling SIGTRAP.
When it gets into that hung state, it eventually goes
down and has to be restarted (This is usually taken care
of by the entry in /etc/inittab).
LOCAL FIX:
When qdaemon gets into that hung state, stop it
and restart it using stopsrc and startsrc.
PROBLEM SUMMARY:
qdaemon might occasionally hang.
PROBLEM CONCLUSION:
Signal handling for qdaemon has been changed to prevent this
situation.
------
APAR: IY18954 COMPID: 5765E6100 REL: 510
ABSTRACT: MKLVCOPY: COMMAND WITH -U AND -S S OPTION FAIL
PROBLEM DESCRIPTION:
mklvcopy with the -u and -s specified gives an error msg
0516-1037.
PROBLEM CONCLUSION:
changed the uVAL in mklvcopy to UVAL.
------
APAR: IY18955 COMPID: 5765E6100 REL: 510
ABSTRACT: TRUSS DOESN'T DISPLAY THE ARGS IN HEX FOR FIRST EXEC CALL
PROBLEM DESCRIPTION:
When -x flag is enabled, the first exec call displayed by
truss doesn't display all the args as hexa decimal value.
PROBLEM CONCLUSION:
Fixed truss to enable the -x option for the first exec
call processing.
------
APAR: IY18960 COMPID: 5765E6100 REL: 510
ABSTRACT: NIM CONFIGURATION FAILS WHEN PERFORMING OPERATION ON MACHINES
PROBLEM DESCRIPTION:
NIM configuration fails when performing operation on machines
PROBLEM CONCLUSION:
increase RAM fs size for certain network boot images
------
APAR: IY18962 COMPID: 5765E6100 REL: 510
ABSTRACT: M1+MPV:8-DIGIT FRU PART NUMBER.
PROBLEM DESCRIPTION:
The "lscfg -vl tokX" will only not display EC Level, Serial
Number, FRU Number, Manufacturer, Network Address, or
Displayable Message. It will only display Loadable Microcode
Level, Part Number, and Device Specific.(YL).
PROBLEM CONCLUSION:
Parts of the VPD were not written, and therefore not displayed.
I modified source code to write these fields into the VPD.
------
APAR: IY18972 COMPID: 5765E6100 REL: 510
ABSTRACT: WHEN 3LAMPS MODEL IS LOADED ONE OF THE VIEWS IS SHADED
PROBLEM DESCRIPTION:
Adapter state is not carried over from view to view.
PROBLEM CONCLUSION:
Always make sure the adapter state is set.
------
APAR: IY18997 COMPID: 5765E6100 REL: 510
ABSTRACT: ITI ON BU13B
PROBLEM DESCRIPTION:
Because of a small timing hole in add_ldata_heap, it is
possible for find_heap to fail to find the correct heap,
although it is there.
------
APAR: IY19013 COMPID: 5765E6100 REL: 510
ABSTRACT: INCORRECT RENDERING ON VERTEX COLORED POLYGONS
PROBLEM DESCRIPTION:
Vertex colored polygons may not appear as expected.
PROBLEM CONCLUSION:
Force vertex colored polygons down the original code path.
------
APAR: IY19043 COMPID: 5765E6100 REL: 510
ABSTRACT: DBX FUNCTION CORE DUMPS WHEN ATTEMPTING TO ATTACH TO CATIA
PROBLEM DESCRIPTION:
Attempts to use dbx on a 64-bit kernel to attach to certain
processes cause stdin to be corrupted and dbx gets garbage
for commands.
PROBLEM SUMMARY:
Ptrace in 64-bit kernel sometimes returns incomplete
loader info buffer.
PROBLEM CONCLUSION:
Fixed size checking on ptrace/sysldr interface.
------
APAR: IY19049 COMPID: 5765E6100 REL: 510
ABSTRACT: HELPS CURSOR IS TOO SMALL FOR PC CLIENT/APPLET MODE
PROBLEM DESCRIPTION:
Help pointer icon is too small for PC Client/applet mode.
Problem was caused by a change made because on AIX the icon
was too large.
PROBLEM CONCLUSION:
Use new icon only if running on AIX platform.
------
APAR: IY19050 COMPID: 5765E6100 REL: 510
ABSTRACT: TABLES WITH MANY ENTRIES TAKE LONG TO SORT
PROBLEM DESCRIPTION:
Multi-column tables that support sorting of their columns
take a long time to sort if there are large amount of data
to sort (up to 10 min. for approx. 6000 records).
PROBLEM CONCLUSION:
Change the sort algorithm to a more efficient sort (n*log n)
instead of (nĒ2)
------
APAR: IY19051 COMPID: 5765E6100 REL: 510
ABSTRACT: OVERVIEWS RELOADED INCORRECTLY - NULL PTR EXCPT
PROBLEM DESCRIPTION:
Null ptr exception with certain Overviews
PROBLEM CONCLUSION:
Ensure Overview plugin is loaded with correct window info.
------
APAR: IY19052 COMPID: 5765E6100 REL: 510
ABSTRACT: COMMAND LINE ENTRY FOR WEBSM_NO_REMOTE_CLASS_LOADING OVERRIDDEN
PROBLEM DESCRIPTION:
command line entry for -DWEBSM_NO_REMOTE_CLASS_LOADING
overridden in wsm script.
PROBLEM CONCLUSION:
only set value for java.security.policy in script.
------
APAR: IY19054 COMPID: 5765E6100 REL: 510
ABSTRACT: CURRENT VERSION OF WEB-BASE SYSTEM MANAGER MIGHT NOT BE
PROBLEM DESCRIPTION:
Current version of Web-base System Manager might not be
compatible with future versions of Web-base System Manager.
PROBLEM CONCLUSION:
Apply fix to pervent possible compatibility problem.
------
APAR: IY19060 COMPID: 5765E6100 REL: 510
ABSTRACT: FIX PAM IMPORTS AND HEADERS
PROBLEM DESCRIPTION:
Problems compiling or running PAM applications.
PROBLEM CONCLUSION:
Corrected PAM library and headers.
------
APAR: IY19062 COMPID: 5765E6100 REL: 510
ABSTRACT: GENCOPY NEEDS TO HAVE -X OPTION AND SHOULD RECOGNIZE
PROBLEM DESCRIPTION:
gencopy -X complains that -X is not a valid option.
gencopy does not recognize the devices.all keyword.
PROBLEM CONCLUSION:
Recognize the -X flag to expand filesystems as needed.
Recognize the devices.all keyword to copy all devices from
the media.
------
APAR: IY19063 COMPID: 5765E6100 REL: 510
ABSTRACT: BFFCREATE COPIES PKGS TO TARGET DIR BASED ON MEDIA VERSION
PROBLEM DESCRIPTION:
When a customer uses the bffcreate command to copy packages,
the packages will either be copied into the default target
directory (/usr/sys/inst.images) with the new 5.1
sub-directory path added (installp/<platform>), or a
user-specified target dir with the new 5.1 sub-dir
path added. However, if copying version 4 images, the old
directory structure of packages being copied directly
into the directory specified, should be maintained.
This is important for creating version 4 lpp_sources in NIM.
PROBLEM CONCLUSION:
Have bffcreate check whether version 4 images or version 5
images are being copied, and use the appropriate directory
structure to copy them into.
------
APAR: IY19064 COMPID: 5765E6100 REL: 510
ABSTRACT: SMIT 'BFFCREATE' CAN'T COPY SW FROM MEDIA TO DIRECTORY
PROBLEM DESCRIPTION:
Customer will not be able to use the SMIT "Copy Software to
Hard Disk for Future Installation" selection to copy media.
PROBLEM CONCLUSION:
Fix a problem in the way the sm_inst script is parsing the
selections from the F4 listing.
------
APAR: IY19065 COMPID: 5765E6100 REL: 510
ABSTRACT: GENCOPY FAILS IN COPYING DEVICES.ALL .
PROBLEM DESCRIPTION:
On IA, during a bos installation, and the EHD CD is used,
the error message, bffcreate: No such file or directory is
displayed.
PROBLEM CONCLUSION:
Fixed gencopy to handle this situation.
------
APAR: IY19066 COMPID: 5765E6100 REL: 510
ABSTRACT: MKSYSB PROGRESS MESSAGES ERRONEOUS
PROBLEM DESCRIPTION:
This is usually not seen because most backups are probably
of a large number of files most of which are not large.
The backup completes without ever showing a final total of
files or percentage it thought it backed up. The problem is
when all/most of the files are backed up are large. This
allows it to display progress almost to the individual number
of files it is backing up. As a result it may show near the
end that it has backed up more than it thought was available.
For example: 18 of 20 120%
PROBLEM SUMMARY:
Under certain circumstances mksysb/savevg can report that it
has backed up more files then it though were available. For
example, it could report 20 of 18 114%. With this apar, it
will never go beyond 100% and will not report beyond the
number of files that it is attempting to back up.
PROBLEM CONCLUSION:
This apar fix will make sure that mksysb/savevg does not
report beyond 100% backup.
TEMPORARY FIX:
It is just erroneous information, the backup functions
properly.
------
APAR: IY19070 COMPID: 5765E6100 REL: 510
ABSTRACT: DBX FAILS TO ALLOCATE OR ACCESS MEMORY IF DEBUG A 64-BIT
PROBLEM DESCRIPTION:
The customer will not be able to assign a literal string
to a debuggee character pointer variable. (i.e.
'assign t = "hello"', if t is of type 'char *', will not
work).
PROBLEM CONCLUSION:
The dbx routine that calls malloc in the debuggee's address
space and acquires the address of the new memory needs to
return a 64bit value to accomodate 64bit debuggee's heap
addresses. It currently returns an integer.
------
APAR: IY19071 COMPID: 5765E6100 REL: 510
ABSTRACT: SYSTEM CRASH
PROBLEM DESCRIPTION:
DSI in xm_gethandle
PROBLEM CONCLUSION:
Check for XMEM_GLOBAL in pre-translated buffer
------
APAR: IY19075 COMPID: 5765E6100 REL: 510
ABSTRACT: VSX4: LOCALECONV() SETS UNAVAILABLE ELEMENTS TO WRONG VALUE
PROBLEM DESCRIPTION:
Default settings for above locale members will not be correct.
PROBLEM CONCLUSION:
Modify default settings for above locale members for IA64.
------
APAR: IY19077 COMPID: 5765E6100 REL: 510
ABSTRACT: NEED LOWER HMT LOAD THRESHOLD FOR BEST SDET PERFORMANCE
PROBLEM DESCRIPTION:
Performance using hardware multithreading is degraded.
PROBLEM CONCLUSION:
Fix calculation that decides if system is lightly loaded.
------
APAR: IY19083 COMPID: 5765E6100 REL: 510
ABSTRACT: MISSING FILESETS IN NIM CLIENT
PROBLEM DESCRIPTION:
To properly install KDE desktop using NIM, X11.samples and
bos.mh are needed in the lpp_source. Without them, KDE
may not install.
PROBLEM CONCLUSION:
(s)images option for a 5.1.0 lpp_source needs bos.mh and
X11.samples added to the current list in c_sh_lib.
------
APAR: IY19088 COMPID: 5765E6100 REL: 510
ABSTRACT: FSCK SEG FAULTS AFTER BIGFILE TEST AND CRASH
PROBLEM DESCRIPTION:
logredo got Segmentation fault(coredump)
PROBLEM CONCLUSION:
the buffer for log rec is one page size. In jfs2
env., it needs more than one page size
------
APAR: IY19089 COMPID: 5765E6100 REL: 510
ABSTRACT: MKLV ON OLD-CONC VG CAN CRASH
PROBLEM DESCRIPTION:
When creating a logial volume on a concurrent (classic)
capable VG with more than one logical partition, can cause
a system crash on passive nodes.
PROBLEM CONCLUSION:
The clvmd daemon on passive nodes only sends one extend/reduce
partition structure to the driver. Change the clvmd daemon to
pass the correct number of extend/reduce partition structures.
------
APAR: IY19091 COMPID: 5765E6100 REL: 510
ABSTRACT: CAN'T NIM INSTALL 64BIT MKSYSB
PROBLEM DESCRIPTION:
Failure to reinstall system backups from JFS2 rootvg
systems.
PROBLEM CONCLUSION:
Fix problems for nim mksysb installs from 64bit/jfs2 systems.
Fix problems with mksysbs from migrated systems installed
with Enable 64bit kernel set to yes.
Add quotes to prevent ksh test errors in Make_Sys_LV.
Correct problems when cloning from 64 bit enabled systems to
32 bit systems.
------
APAR: IY19134 COMPID: 5765E6100 REL: 510
ABSTRACT: ENHANCE THREADSAFETY OF MALLOC SUBSYSTEM
PROBLEM DESCRIPTION:
Using malloc() while running another program that modifies
the sbrk value may cause malloc() to fail.
PROBLEM CONCLUSION:
Use sbrk(), instead of brk(), to modify the brk value inside
the malloc subsystem
------
APAR: IY19135 COMPID: 5765E6100 REL: 510
ABSTRACT: CACHEFSWSSIZE COMMAND GIVING ERROR
PROBLEM DESCRIPTION:
programs using libc version of xdr_stdio fail
PROBLEM CONCLUSION:
add ntohl/htonl to xdrstdio get/put routines
------
APAR: IY19136 COMPID: 5765E6100 REL: 510
ABSTRACT: DO NOT DROP LOCK BEFORE IP_FREEMOPTIONS
PROBLEM DESCRIPTION:
ip_setmoptions depends on the socket lock but
we unlock the socket before calling the
ip_freemoptions function.
PROBLEM SUMMARY:
Fixed crash resulting from use of multicast options
buffer that was freed without proper locking.
PROBLEM CONCLUSION:
Freeing of multicast options buffer now occurs with
proper locking.
------
APAR: IY19137 COMPID: 5765E6100 REL: 510
ABSTRACT: HOT : DSH HANG ON SP SYSTEM
PROBLEM DESCRIPTION:
The dsh command hangs.
PROBLEM CONCLUSION:
Fix serialization problems in the code to bind to a port.
------
APAR: IY19138 COMPID: 5765E6100 REL: 510
ABSTRACT: TRACE HOOKS FOR TCP/IP USE UNREGISTERED HOOK IDS
PROBLEM DESCRIPTION:
Trace hook 25C is used by both UDP and SNA. Trace hooks
25B - 25F are all incorrectly used by TCP/IP and may conflict
with other products. This may cause unexpected results when
tracing.
PROBLEM CONCLUSION:
Change TCP/IP to use different trace hooks that are not used
by other products. The new trace hooks will be 535-539.
------
APAR: IY19139 COMPID: 5765E6100 REL: 510
ABSTRACT: UMOUNT FAILS WHILE UNMOUNTING FILE SYSTEM CONTAINING ZERO SIZED
PROBLEM DESCRIPTION:
umount fails while unmounting a file system which has
a core file created with zero length.
PROBLEM SUMMARY:
The core file is closed before returning an error.
PROBLEM CONCLUSION:
The umount fails to unmount the filesystem which core
file still open.
------
APAR: IY19140 COMPID: 5765E6100 REL: 510
ABSTRACT: KDB: ADD J2 SUPPORTS TO KDB
PROBLEM DESCRIPTION:
Cannot debug j2 using kdb.
PROBLEM CONCLUSION:
Add commands in kdb to display j2 structure.
------
APAR: IY19141 COMPID: 5765E6100 REL: 510
ABSTRACT: RIGEL HANG LOW PAGING SPACE
PROBLEM DESCRIPTION:
The machine will hang if it is running low on
paging space and kernel is trying to kill a process
which has set its flag to not wake up, when signal
is sent.
PROBLEM CONCLUSION:
The subroutine which decides about sending the kill signal to
the process, has been modified such that it does not send kill
signal to the process which has flag setup as not to wake
when signal is sent.
------
APAR: IY19142 COMPID: 5765E6100 REL: 510
ABSTRACT: JFSERRLOGGING CODE SHOULD CORRECTLY HANDLE MULTI-SEG .INDIRECT
PROBLEM DESCRIPTION:
In some cases of file system corruption, information needed
to analyze the system crash is not included in the dump.
PROBLEM CONCLUSION:
Enable JFS Smart Dump to include extended .indirect segments.
------
APAR: IY19143 COMPID: 5765E6100 REL: 510
ABSTRACT: JFS2 CRASH ON BIGFILE TEST CASE
PROBLEM DESCRIPTION:
If a J2 filesystem is filled to 100% capacity and then a
file is truncated into a hole in the file, the system may
crash.
PROBLEM CONCLUSION:
vm_zeropage called bzero without knowing all the material
being zeroed was backed. The fix is to wrap the bzero with
a setjmpx exception handler to prevent this page fault from
crashing the system.
------
APAR: IY19144 COMPID: 5765E6100 REL: 510
ABSTRACT: SYSTEM CRASH WITH STATIC BREAK INSTRUCTION INTERRUPT
PROBLEM DESCRIPTION:
System crashes.
PROBLEM CONCLUSION:
pageProtect service has been modified.
------
APAR: IY19145 COMPID: 5765E6100 REL: 510
ABSTRACT: DEACTIVATE PAGE SPACE CAN OVERLOOK EXTENSION MEM LOCKWORDS
PROBLEM DESCRIPTION:
While deactivating a live paging space, system may crash.
PROBLEM CONCLUSION:
Correct problems with serailization and segment id / page no
calculations.
------
APAR: IY19146 COMPID: 5765E6100 REL: 510
ABSTRACT: KDB CANNOT DISPLAY PAG VALUES
PROBLEM DESCRIPTION:
Additional functionality was added to support AFS PAG
values. The values are not displayed by KDB.
PROBLEM CONCLUSION:
PAG values will be displayed after the group ID values.
------
APAR: IY19147 COMPID: 5765E6100 REL: 510
ABSTRACT: NFS AUTOFS FILESYSTEM NOT GETTING UNMOUNTED
PROBLEM DESCRIPTION:
If there is an entry in an automount map which tries to mount
a directory from a server, and that directory is not exported,
the autofs mount on the client will not be able to be umounted.
PROBLEM CONCLUSION:
nfsmount() should return the err, not 0.
------
APAR: IY19148 COMPID: 5765E6100 REL: 510
ABSTRACT: TOKEN OBJECTS NOT PROPERLY CLEANED UP ON INIT
PROBLEM DESCRIPTION:
All object references from shared memory should be removed
when the token is reinitialized.
PROBLEM CONCLUSION:
Added an object_mgr_destroy_token_objects() call to
SC_InitToken to clean up correctly on initialization.
------
APAR: IY19149 COMPID: 5765E6100 REL: 510
ABSTRACT: FIX DEADLOCK CONDITION IN OBJ_MGR.C
PROBLEM DESCRIPTION:
Application using object management functions may lock up.
PROBLEM CONCLUSION:
Several calls to unlock global_shm->mutex were added along
error paths in obj_mgr.c to avoid the possibility of deadlock.
------
APAR: IY19150 COMPID: 5765E6100 REL: 510
ABSTRACT: TOTAL_LEN CALCULATED INCORRECTLY IN SAVE_PUBLIC_TOKEN_OBJECT
PROBLEM DESCRIPTION:
Loading a previously saved public token object can fail.
PROBLEM CONCLUSION:
Corrected the calculation of total length when saving a public
token object.
------
APAR: IY19151 COMPID: 5765E6100 REL: 510
ABSTRACT: POSSIBLE CORE DUMP IF LOADING STDLL FAILS
PROBLEM DESCRIPTION:
If the STDLL doesn't load successfully, an application that
tries to use PKCS #11 functions could core dump.
PROBLEM CONCLUSION:
The function list pointer is always checked to make sure it's
valid before any PKCS #11 functions can be called.
------
APAR: IY19152 COMPID: 5765E6100 REL: 510
ABSTRACT: DES KEYS SHOULD BE GENERATED RANDOMLY AND HAVE CORRECT PARITY
PROBLEM DESCRIPTION:
DES and 3DES keys generated by C_GenerateKey using ICA are not
sufficiently random and don't have parity bits set to conform
to the NIST standard.
PROBLEM CONCLUSION:
Filled key with random data and implemented parity-fixing code.
------
APAR: IY19153 COMPID: 5765E6100 REL: 510
ABSTRACT: XETHCHAN_TRACE_LOCK IS KILLING ETHERCHANNEL PERFORMANCE
PROBLEM DESCRIPTION:
netif_backup introduces an unneeded lock into etherchannel
that significantly slows etherchannel down
PROBLEM CONCLUSION:
remove the lock from the transmit path for none netif_backup
etherchannel configurations
------
APAR: IY19154 COMPID: 5765E6100 REL: 510
ABSTRACT: WINDOW MANAGER CTWM CAUSES X WINDOWS TO CORE DUMP
PROBLEM DESCRIPTION:
The X-Server may core dump when the mouse is moved while
the display is being rendered.
PROBLEM CONCLUSION:
Change the WheelMouseID to be different than the FastCursorID.
------
APAR: IY19155 COMPID: 5765E6100 REL: 510
ABSTRACT: FSCK/LOGREDO PROBLEMS WITH INLINE LOG
PROBLEM DESCRIPTION:
logredo will hang for clean fs with an inlinelog
PROBLEM CONCLUSION:
when fs with an inlinelog is clean, don't call updateSuper,
just return
------
APAR: IY19156 COMPID: 5765E6100 REL: 510
ABSTRACT: EXTENDLV WILL PANIC PASSIVE NODE IN OLD CONC VG
PROBLEM DESCRIPTION:
extendlv with more than 5 logical partitions will cause
panic on passive node.
PROBLEM CONCLUSION:
In routine hd_concconfig_kextred routine, LVMcopyin uses
wrong size argument. It should use size and not expart_size
argument.
------
APAR: IY19157 COMPID: 5765E6100 REL: 510
ABSTRACT: GXT6000P HANGS RUNNING CATIA SHD WITH PTF U474642
PROBLEM DESCRIPTION:
With GXT6000P adapter with PTF U474642 installed, Catia
application hangs with a specific customer model in
SHD mode when being rotated. Actually graPHIGS is in
a tight loop, which makes it appear that X is hung.
PROBLEM SUMMARY:
The following problem occurs on GXT6000P when doing clipped
polygons:
Dust particles are displayed in certain area of a model. Pixel
level holes or overpaints are displayed on irregular pixel
position for each redraw. It looks like a dust particle. It
emerges not on whole screen but on certain area of a model.
The original fix for this problem ran slowly, and a hang
existed in certain situations.
PROBLEM CONCLUSION:
Utilize a different set of hardware commands when rendering
clipped polygons on a GXT6000P.
------
APAR: IY19158 COMPID: 5765E6100 REL: 510
ABSTRACT: GIGABIT ETHERNET ADAPTER COMES UP IN DEFINED STATE
PROBLEM DESCRIPTION:
During adapter config of the Gigabit Ethernet Fiber or UTP
adapter, the config method will fail with the following
error message:
Method error (/usr/lib/methods/cfggxent):
0514-050 Cannot perform the requested function
because the specified device was not
detected.
PROBLEM CONCLUSION:
Replace io_delay() system call with delay() system call
in adapter initialization routine.
------
APAR: IY19159 COMPID: 5765E6100 REL: 510
ABSTRACT: MAN TUNNELS - MODIFY PROPERTIES
PROBLEM DESCRIPTION:
When the properties in manual tunnels are modified the
changed values are not seen when properties are clicked and
the container is reloaded which takes lot of time instead
of refreshing. When new tunnel is added then also contianer
is reloaded which takes lot of time.
PROBLEM CONCLUSION:
The newly created tunnel is added to screen withou reloading.
Also the properties and container are refreshed when a tunnel
properties are modified. All the values are modified correctly
in the database. New scripts were added to get the tunnel id
of the newly created tunnel and to get all the properties of
a tunnel given a tunnel id.
------
APAR: IY19160 COMPID: 5765E6100 REL: 510
ABSTRACT: EXCEPTION WHEN ERROR OCCURS TRYING TO CREATE A MANUAL TUNNEL
PROBLEM DESCRIPTION:
When creating a manual tunnel in Websm, if the underlying
shell command fails, the user gets a null pointer exception.
PROBLEM CONCLUSION:
Change code to exit the create manual tunnel action when the
command fails.
------
APAR: IY19161 COMPID: 5765E6100 REL: 510
ABSTRACT: IKE TUNNELS - MODIFY PROPERTIES HAS CACHEING PROBLEM
PROBLEM DESCRIPTION:
When a user modifies the KM transforms or DM proposals or
transforms, the database gets updated, but, at times, the
WebSM GUI does not reflect what is saved in the database.
PROBLEM CONCLUSION:
Code has been added to solve the caching problem in the KM
and DM code.
------
APAR: IY19162 COMPID: 5765E6100 REL: 510
ABSTRACT: TRANSFORMS AND PROPOSALS DON'T TAKE DEFAULT VALUES
PROBLEM DESCRIPTION:
Change of the default values on the IKE object menu (tunnel
defaults), doesn't always modify the IKE definition for a
transform.
------
APAR: IY19163 COMPID: 5765E6100 REL: 510
ABSTRACT: GUI LABELS INCORRECT
PROBLEM DESCRIPTION:
Some of the panels had misspelled words and other
grammatical errors.
PROBLEM CONCLUSION:
Corrected the message text file.
------
APAR: IY19164 COMPID: 5765E6100 REL: 510
ABSTRACT: HEX PRESHARED KEY MISSING 0X
PROBLEM DESCRIPTION:
When the auth method is preshared key, and the user enters
the value in Hex, the display of the key is chopping off
the '0x' in front. The user can't determine if the key
is in hex or ascii.
------
APAR: IY19165 COMPID: 5765E6100 REL: 510
ABSTRACT: WIZARD-INCORRECT ID TYPE IS STORED WHEN GO BACK-FORTH
PROBLEM DESCRIPTION:
The information that gets saved in the IKE tunnel database
isn't correct if a user moves back and forth within the
6 wizard panels. The information is not what the summary
panel says will be written to the database.
PROBLEM CONCLUSION:
Added code to clear the variable cache.
------
APAR: IY19166 COMPID: 5765E6100 REL: 510
ABSTRACT: ACTIVE TUNNEL MONITOR PLUG-IN UPDATES
PROBLEM DESCRIPTION:
Active Tunnel Monitor plugin which allows a user to view the
status of the IKE Tunnels which have been activated.
PROBLEM CONCLUSION:
Fixed code to include a new WebSM 2000 plugin under the
IKE tunnel plug-in.
------
APAR: IY19167 COMPID: 5765E6100 REL: 510
ABSTRACT: MKSECLDAP -C GOT ERROR AT THE FIRST TIME
PROBLEM DESCRIPTION:
Running the client set up the first time with a -u
flag for some user produces an error.
PROBLEM CONCLUSION:
Added LDAP load module definition to the methods.cfg
file before processing any users.
------
APAR: IY19174 COMPID: 5765E6100 REL: 510
ABSTRACT: LDAP CLIENT DAEMON HANGS IF /ETC/GROUP LINE IS TOO BIG
PROBLEM DESCRIPTION:
The LDAP client daemon secldapclntd hangs when
commands like "lsuser -R LDAP <uname>" or
"lsgroup -R LDAP <groupname>" is entered and the
user <uname> belongs to a group which has a large
number of users (app 1500 users in /etc/group from
which ldap database is created). The lsgroup command
also hangs trying to get information for such a group.
If the daemon is killed, the comands give partial output.
PROBLEM SUMMARY:
The LDAP client daemon secldapclntd hangs when
/etc/group contains large number of users. All the
associated commands like "lsuser -R LDAP" and
"lsgroup -R LDAP" also hang due to this.
PROBLEM CONCLUSION:
The memory allocation required for such large
number of users is insufficient which is now
fixed.
------
APAR: IY19175 COMPID: 5765E6100 REL: 510
ABSTRACT: ZOMBIE PROCESSES ARE NOT CLEANED UP AIX510 GOLD
PROBLEM DESCRIPTION:
the system starts to have many zombies who would not die
PROBLEM CONCLUSION:
setpinit in lock manager's thread
------
APAR: IY19176 COMPID: 5765E6100 REL: 510
ABSTRACT: ASSERT IN THREAD_SETSTATE_FAST
PROBLEM DESCRIPTION:
Program termination due to an assert in thread_setstate_fast.
PROBLEM SUMMARY:
Assert in thread_setstate_fast
PROBLEM CONCLUSION:
Increase lock scope.
------
APAR: IY19177 COMPID: 5765E6100 REL: 510
ABSTRACT: LOADING KERNEL EXTENSION WITH MAXDATA PROGRAM CAUSES CRASH
PROBLEM DESCRIPTION:
If a "maxdata" program is used to load a kernel extension,
the system will crash. (Setting
LDR_CNTRL=MAXDATA=... can turn any program into a maxdata
program.)
PROBLEM CONCLUSION:
Disable code used to manipulate user segment registers when
loading kernel extensions.
------
APAR: IY19178 COMPID: 5765E6100 REL: 510
ABSTRACT: TOPAS PROBLEMS
PROBLEM DESCRIPTION:
Starting topas with topas -n3 will come up with 3 lines for
network adapters,but only two will be used,i.e.there will be
two blank lines between the network adapter section and the
disk section.
PROBLEM CONCLUSION:
Modified the code at the place where the starting line
postions of the network and disk sections were calculated.
------
APAR: IY19179 COMPID: 5765E6100 REL: 510
ABSTRACT: ASCI: C/R REGRESSION DEFECTS AND OTHER 32-BIT ISSUES
PROBLEM DESCRIPTION:
Checkpoint/restart may not work.
PROBLEM CONCLUSION:
Add enhancements to Checkpoint/restart code to support
SP-level checkpoint/restart requirements.
------
APAR: IY19180 COMPID: 5765E6100 REL: 510
ABSTRACT: AOPT FAILURE, BENCHMARK UPDATE1
PROBLEM DESCRIPTION:
aopt fails on -qfdpr apps
PROBLEM CONCLUSION:
drop current development code to be used for later
benchmarks tests
------
APAR: IY19181 COMPID: 5765E6100 REL: 510
ABSTRACT: XMDBG -S CRASHES SYSTEM
PROBLEM DESCRIPTION:
After running bosdebug with the -s option and re-bosbooting
and rebooting the machine with the 64-bit kernel, the machine
will crash almost immediately in pgfree, due to an incorrect
parameter passed to pgfree.
PROBLEM CONCLUSION:
Fix the parameter to be correct on the 64-bit kernel (already
correct on 32-bit kernel).
------
APAR: IY19182 COMPID: 5765E6100 REL: 510
ABSTRACT: MISSING ICON, WZ_ADD_NETWORK.GIF, IN NEW NETWORK WIZARD.
PROBLEM DESCRIPTION:
Wizard icon is missing from the first panel of the
add new network wizard.
PROBLEM CONCLUSION:
Add new icon wz_add_network.gif
------
APAR: IY19183 COMPID: 5765E6100 REL: 510
ABSTRACT: WEBSM NIM SHOWS NIMCLIENT DEFINED AS UP INSTEAD OF MP
PROBLEM DESCRIPTION:
WebSM NIM shows a system defined as MP, being defined as UP
in the properities field.
PROBLEM CONCLUSION:
Trim the value being passed be the property editor for the
variable from _editor.getAsText().
------
APAR: IY19184 COMPID: 5765E6100 REL: 510
ABSTRACT: PTF:SNMP MONITOR GENERATES A NULL POINTER EXCEPTION.
PROBLEM DESCRIPTION:
When the SNMP Montoring panel is opened, 3 warning panels
pop up, but the SNMP Monitoring panel doesn't get opened.
PROBLEM CONCLUSION:
Dropped code to correct this.
------
APAR: IY19185 COMPID: 5765E6100 REL: 510
ABSTRACT: VPN ICONS MUST BE USED IN WIZARD AND APPLICATION
PROBLEM DESCRIPTION:
Missing icon in VPN smartguides.
PROBLEM CONCLUSION:
Move icon to correct place.
------
APAR: IY19216 COMPID: 5765E6100 REL: 510
ABSTRACT: 64BIT APPS ARE NOT WORKING WITH ZH_CN
PROBLEM DESCRIPTION:
64bit IME can not be loaded
PROBLEM CONCLUSION:
modify chinese.h, imefun.c imefun.h, ime_abc.c and ime_abc.h
------
APAR: IY19229 COMPID: 5765E6100 REL: 510
ABSTRACT: CLASS ASSIGNMENT FAILS FOR NFS APPLICATIONS ON 64BK
PROBLEM DESCRIPTION:
in 64BK, applications get their dev_t converted to DEVNO64
for storing them in the WLM rules.
But this should not be done for remote files, which
dev_t is not a major/minor, but some 32 bit ID.
Later, during classification, the dev_t comparison fails.
PROBLEM CONCLUSION:
In 64 BK, do not convert the dev_t of remote files to DEVNO64,
but only extend them to 64 bits. For 32BK and 64bit apps.,
only convert to DEVNO32 the real DEVNO64s.
Also, for U struct, fix kdb display of WLM dev and ino fields
and remove the conversions to and from the U_dev field.
------
APAR: IY19232 COMPID: 5765E6100 REL: 510
ABSTRACT: LOGINLOG() DOES NOT LOG TO LDAP
PROBLEM DESCRIPTION:
If customer has defined user accounts with the same user name
on both local and the ldap server, and configures the
authentication to ldap, when the ldapuser logins, the login
log will be done on the local files, not the ldap.
PROBLEM CONCLUSION:
change the loginlog() call to handle different domains
------
APAR: IY19234 COMPID: 5765E6100 REL: 510
ABSTRACT: MKSECLDAP COMMAND DOES NOT SETUP SSL RIGHT
PROBLEM DESCRIPTION:
1.Even if version 4 gskit is installed, the mksecldap command
still returns an error saying that gskit is not installed
during LDAP server/client SSL setup.
2. After SSL setup of a LDAP server (LDAP version 3.2 and
above), the slapd server process can not be started.
PROBLEM CONCLUSION:
1. update the mksecldap command to handle the new version 4
gskit fileset.
2. update the mksecldap command to place the SSL key password
to the right place in slapd32.conf
------
APAR: IY19235 COMPID: 5765E6100 REL: 510
ABSTRACT: ADUMP:CUR_CPU_ID NOT DISPLAYED PROPERLY AFTER MEMORY METHODS
PROBLEM DESCRIPTION:
Extra characters at end of memory dump, invalid CPU number
PROBLEM CONCLUSION:
Correct single line in PERL script for cpu_id method
------
APAR: IY19236 COMPID: 5765E6100 REL: 510
ABSTRACT: 32-BIT PROCESS THAT FORKS MAY CRASH 64-BIT KERNEL
PROBLEM DESCRIPTION:
The application may crash the 64-bit kernel since one of the
segments used by this kernel is not attached to properly.
PROBLEM CONCLUSION:
Attach the missing segment in the 64-bit kernel.
------
APAR: IY19237 COMPID: 5765E6100 REL: 510
ABSTRACT: STARTING PTRACE DURING LOADER ACTIVITY CAN CAUSE DEADLOCK
PROBLEM DESCRIPTION:
If a threaded application is loading modules when ptrace is
invoked upon that process, a deadlock may occur when two
threads each hold a lock that the other requires.
LOCAL FIX:
Do not attempt to ptrace a process while it is dynamically
loading modules. If the module(s) being loaded reside on
an NFS filesystem, move the modules to a local filesystem.
PROBLEM SUMMARY:
Loader must ensure that multiple threads within
a process can handle different loader tasks without
interfering with one another.
PROBLEM CONCLUSION:
Modify locking scheme.
------
APAR: IY19238 COMPID: 5765E6100 REL: 510
ABSTRACT: 64-BIT KERNEL BUILD WITH -DDEBUG DOES NOT BOOT.
PROBLEM DESCRIPTION:
The 64-bit kernel will not boot when build with -DDEBUG.
PROBLEM CONCLUSION:
Check if the overflow segment is attached before cloning it
onto the child process during fork.
------
APAR: IY19255 COMPID: 5765E6100 REL: 510
ABSTRACT: NON BLOCK ALIGNED TRANSFERS TO RAW CD/DVD MAY CAUSE PANIC
PROBLEM DESCRIPTION:
Machine may panic when running io to raw cd/dvb device.
This may only happen on non block aligned transfers that are
multiples of 512.
PROBLEM CONCLUSION:
Initialization of all buf structures that are created by the
disk driver for this situation.
------
APAR: IY19257 COMPID: 5765E6100 REL: 510
ABSTRACT: RANDOM ACCESS FILE I/O PROBLEM WITH NFS
PROBLEM DESCRIPTION:
xlf tests failed. see defect
PROBLEM CONCLUSION:
ioctl for nfs files will return ENOTTY instead of EOPNOTSUPP
------
APAR: IY19261 COMPID: 5765E6100 REL: 510
ABSTRACT: POOR FILE I/O THROUGHPUT ON 64-BIT KERNEL
PROBLEM DESCRIPTION:
Throughput is low when sequential reads and writes are being
performed to large files, about 2Gb in size, on J2 filesystem
and J1 filesystem with 64-bit kernel because page replacement
begins freeing up pages before free page count reaches
MINFREE.
PROBLEM CONCLUSION:
Uninitialized variable caused unintended page replacement
behavior. Variable was initialized.
------
APAR: IY19263 COMPID: 5765E6100 REL: 510
ABSTRACT: 64BIT PRECISION SUPPORT
PROBLEM DESCRIPTION:
The eval macro of m4 command does not to support 64 bit
precision.
PROBLEM CONCLUSION:
The m4 command's code was modified to support 64 bit precision
------
APAR: IY19264 COMPID: 5765E6100 REL: 510
ABSTRACT: SHIP ICA STDLL
PROBLEM DESCRIPTION:
LeedsLite support not available.
PROBLEM CONCLUSION:
Added /usr/lib/pkcs11/stdll/PKCS11_ICA.so to bos.pkcs11.il.
------
APAR: IY19265 COMPID: 5765E6100 REL: 510
ABSTRACT: STARTING PTRACE DURING LOADER ACTIVITY CAN CAUSE DEADLOCK
PROBLEM DESCRIPTION:
If a threaded application is loading modules when ptrace is
invoked upon that process, a deadlock may occur when two
threads each hold a lock that the other requires.
LOCAL FIX:
Do not attempt to ptrace a process while it is dynamically
loading modules. If the module(s) being loaded reside on
an NFS filesystem, move the modules to a local filesystem.
PROBLEM SUMMARY:
Loader must ensure that multiple threads within
a process can handle different loader tasks without
interfering with one another.
PROBLEM CONCLUSION:
Modify locking scheme.
------
APAR: IY19308 COMPID: 5765E6100 REL: 510
ABSTRACT: DISPLAY PROBLEM OF MOTIF TEXT WIDGET IN 510
PROBLEM DESCRIPTION:
If a user presses backspace while in column 1 of a Motif 2.1
XmText widget, the cursor will move to the last column of the
previous row, but the entire row may not be visible.
PROBLEM CONCLUSION:
Motif 2.1 code fix.
------
APAR: IY19329 COMPID: 5765E6100 REL: 510
ABSTRACT: UNABLE TO REJECT UPDATES WITH SMIT OR WEBSM.
PROBLEM DESCRIPTION:
Rejecting applied updates with the SMIT or WebSM interfaces
will fail.
PROBLEM CONCLUSION:
Fix sm_inst script to properly handle the case of a list
of installp updates that are to be rejected.
------
APAR: IY19344 COMPID: 5765E6100 REL: 510
ABSTRACT: APAR17172:CATIA ENGINE PERFORMANCE DOWN 10% GXT4000/6000P HH450
PROBLEM DESCRIPTION:
Fast concave going down the slow path.
PROBLEM CONCLUSION:
Sent fast concave down fast path.
------
APAR: IY19375 COMPID: 5765E6100 REL: 510
ABSTRACT: MACHINES C20 DURING UPDATE INSTALL
PROBLEM DESCRIPTION:
System rendered unavailable.
PROBLEM CONCLUSION:
Fclear logic is bypassed temporarily.
------
APAR: IY19452 COMPID: 5765E6100 REL: 510
ABSTRACT: KDM SHUTDOWN CRASHES SYSTEM
PROBLEM DESCRIPTION:
The system will show led code of 888 upon choosing the
shutdown option of login screen(kdm) of kde.
PROBLEM CONCLUSION:
Make sure Shared Memory Transport does not free up any
segments that are marked working.
------
APAR: IY19516 COMPID: 5765E6100 REL: 510
ABSTRACT: GENINSTALL AND GENCOPY DO NOT RECOGNIZE OTHER BFF IMAGE TYPES
PROBLEM DESCRIPTION:
A customer will not be able to apply single installp updates
PROBLEM CONCLUSION:
The wrong prefix for format type is getting passed to
geninstall. Pass the update prefixes as installp format types
so the geninstall command will send the update to installp for
processing.
------
APAR: IY19531 COMPID: 5765E6100 REL: 510
ABSTRACT: UPDATE_ALL INTO A NIM SPOT FAILS
PROBLEM DESCRIPTION:
Because of the new cd layout structure, NIM calls to geninstall
were prefixed with the I: option. This caused an invalid flag
error in geninstall when "update_all" creates a list of
update images to install.
PROBLEM CONCLUSION:
Moved position of I: prefix. Now the prefix is set ONLY when
default spot options are used for the fileset listing. This
fixes the "update_all" scenario and makes calling cust with
individual package names more robust. - Now non-installp
images can be given as packages for installation into the
spot. But this means that the user must prefix individual
packages when using the "filesets" attribute for "custing".
------
APAR: IY19626 COMPID: 5765E6100 REL: 510
ABSTRACT: IDD:CHARSET IS INCORRECT (SHOULD BE SHIFT_JIS)
PROBLEM DESCRIPTION:
The charset for Ja_JP is being set as x-jis
PROBLEM CONCLUSION:
The charset should be changed to shift_jis
------
APAR: IY19627 COMPID: 5765E6100 REL: 510
ABSTRACT: IDD:SEARCH RESULTS DISPLAYING ENGLISH FOR VIEWS
PROBLEM DESCRIPTION:
An untranslated word appears in the results page.
PROBLEM CONCLUSION:
Print out the translated view label instead of the view name.
------
APAR: IY19628 COMPID: 5765E6100 REL: 510
ABSTRACT: IDD:TOP PART OF THE LIBRARY PAGE IS SHOWN IN GARBAGE.
PROBLEM DESCRIPTION:
On some PC configurations, Russian text displays incorrectly
because helvetica is not a Russian font and the browser does
not choose cyrillic instead.
PROBLEM CONCLUSION:
When displaying Russian forms, use the cyrillic font instead
of helvetica.
------
APAR: IY19629 COMPID: 5765E6100 REL: 510
ABSTRACT: IDDT9N: RU_RU DOCSEARCH RESULTS IN GARBAGE BOOK TITLE
PROBLEM DESCRIPTION:
Book titles become corrupted for certain languages when
echoed into a file by index_config.sh
PROBLEM CONCLUSION:
Reove calls to SetLocale within the script. The changing of
the LANG environment variable seems to cause the corruption.
------
APAR: IY19631 COMPID: 5765E6100 REL: 510
ABSTRACT: PKCS11 RSA OPS WITH LEEDSLITE FAILURES
PROBLEM DESCRIPTION:
PKCS11 RSA ops with leedslite device driver fail
PROBLEM CONCLUSION:
fix removed defines in ica_api.h
------
APAR: IY19958 COMPID: 5765E7200 REL: 310
ABSTRACT: PROBLEM IN REMOVING SHARE IN CIFSPASSWD FILE
PROBLEM DESCRIPTION:
delete share will corrupt the cifsPasswd file.
PROBLEM CONCLUSION:
change the RO_share old definition (started with '-') back
to ensure backward and forward compatible.
------
APAR: IY19977 COMPID: 5765E7200 REL: 310
ABSTRACT: NET USER COMMAND FAILS WITH RC = 1 WITH LARGE # OF USERS
PROBLEM DESCRIPTION:
net user cmd cannot list big list of user names.
PROBLEM CONCLUSION:
net user cmd will allocate a new bigger buffer to handle
long list of user names
------
APAR: IY19979 COMPID: 5765E7200 REL: 310
ABSTRACT: COPY FROM SERVER TO LOCAL DOESNOT INHERIT READONLY ATTRIBUTE
PROBLEM DESCRIPTION:
Copying a file from a mapped drive to
local drive does not inherit the readonly
attribute.
LOCAL FIX:
send the correct attributes.
PROBLEM CONCLUSION:
Checking attributes in the print server
------
APAR: IY19980 COMPID: 5765E7200 REL: 310
ABSTRACT: INCORRECT TIME STAMPS WITH LANMAN 2.1
PROBLEM DESCRIPTION:
copy a file from client on a mapped drive, creates a file
with incorrect time stamp
PROBLEM CONCLUSION:
set with correct time stamp.
------
APAR: IY19981 COMPID: 5765E7200 REL: 310
ABSTRACT: SUPPORT FOR 4 NEW JAPANESE CHARACTERS
PROBLEM DESCRIPTION:
Customer can not use these 4 characters for file names.
PROBLEM CONCLUSION:
New configuration parameter is added, incoming and outgoing
characters are checked for these four characters and converted
------
APAR: IY19982 COMPID: 5765E7200 REL: 310
ABSTRACT: DRIVE SELECT FROM FILE OPEN IN EXCEL FAILS
PROBLEM DESCRIPTION:
selecting a mapped drive from file open in excel returns
error
PROBLEM CONCLUSION:
server needs to send the file attributes correctly.
------
APAR: IY19983 COMPID: 5765E7200 REL: 310
ABSTRACT: PRINTING PROBLEM IN WIN95
PROBLEM DESCRIPTION:
Printing Problem in Win95
PROBLEM SUMMARY:
Printing Problem in Win95. When a file is printed to a network
printer, only first 18 characters of the filename appear in
the Document name on
PROBLEM CONCLUSION:
Job number will be sent instead of filename, which will be
helpful in differentiating different print jobs.
------
APAR: IY20097 COMPID: 5765E6100 REL: 510
ABSTRACT: J2 PROBLEMS WHEN REBOOTING
PROBLEM DESCRIPTION:
On J2 systems, reboot can cause file damage.
PROBLEM CONCLUSION:
Certain operations could cause the system to lose track of
the fact that particular inodes needed to be synced. Fixed.
------
APAR: IY20367 COMPID: 5765C3403 REL: 430
ABSTRACT: DRIVER SUPPORT FOR 64-BIT PCI FIBRE CHANNEL ADAPTER
PROBLEM DESCRIPTION:
This APAR delivers support for the 64-bit PCI Fibre Channel
adapter (feature code 6228).
This is a packaging APAR only. It will not appear in the list
of APARs on the SMIT "Update software by Fix (APAR)" panel, nor
will the 'instfix' command show this APAR as being installed
after the updates delivered by this package are installed.
PROBLEM SUMMARY:
Packaging only.
PROBLEM CONCLUSION:
Packaging only.
------
APAR: IY20399 COMPID: 5765B8100 REL: 220
ABSTRACT: ALLOWS THE VXML BROWSER TO IMPLEMENT TIMEOUT
PROBLEM DESCRIPTION:
to allow the VXML browser to implement timeout
PROBLEM SUMMARY:
T0 allow the VXML browser to implement
timeout
PROBLEM CONCLUSION:
New code added to provide the required
functionality.
------
APAR: IY20444 COMPID: 5697F6400 REL: 640
ABSTRACT: MESSAGECENTER VIAVOICE TTS
PROBLEM DESCRIPTION:
Message Center requires ViaVoice TTS feature support
PROBLEM SUMMARY:
Support required for ViaVoice TTS
PROBLEM CONCLUSION:
Support added
------
APAR: JR16017 COMPID: 5765C7100 REL: 230
ABSTRACT: THE SNAPSHOT COMMAND FOR ACCOUNTING RECORDS IS REJECTED BY NAS
PROBLEM DESCRIPTION:
A time-out is reported on the Risc/6000 Network Management
Station for a "SNAPSHOT" command issued to the 2220 Node
Administration Station to collect traffic counters/accounting
records at 2220 node level.
This problem only occurs when the "SNAPSHOT" command is received
by NAS, immediately followed by a "DISABLE ACCOUNTING" command.
LOCAL FIX:
Do not issue a nways_stop_acct command at the same time
as a nways_snapshot_acct command.
PROBLEM SUMMARY:
Nways_snapshot_acct commands are rejected by
the 2220 Node Administration Station with a "resource busy"
return code from the Accounting Management Object (code).
This is due to the previous snapshot command being stuck after
receiving a nways_stop_acct command.
Engineering defect is CMVC 42171.
A minor enhancement to the current design is being developed
to handle these two contradictory and conflicting commands
in a better way.
PROBLEM CONCLUSION:
Design change request to meet new customer's
needs for their billing application.
TEMPORARY FIX:
avoid sending nways_snapshot_acct command
at the same time as a nways_stop_acct command.
------
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]