has requested a copy or has subscribed to the document named "New_AIXV4_Fixes".
If you would like to be removed from this mailing list, send e-mail to
aixservaustin.ibm.com with a subject of "unsubscribe New_AIXV4_Fixes", or
send a note to owner-aixservaustin.ibm.com with your request.

APAR: IC34490 COMPID: 5724B5900 REL: 200
ABSTRACT: ENHANCEMENT VIAVOICE.DIRTALK.RTE

PROBLEM DESCRIPTION:
Enhancement to support new function

PROBLEM SUMMARY:
Enhancement required

------

APAR: IC34530 COMPID: 5724B5900 REL: 200
ABSTRACT: ENHANCEMENTS VIAVOICE.DIRTALK_SAMPLE.CLIENT.EN_GB

PROBLEM DESCRIPTION:
Enhancements for viavoice.dirtalk_sample.client.en_GB

PROBLEM SUMMARY:
enhancements for viavoice.dirtalk_sample.client
.en_GB

------

APAR: IC34531 COMPID: 5724B5900 REL: 200
ABSTRACT: ENHANCEMENTS FOR VIAVOICE.DIRTALK_SAMPLE.CLIENT.EN_US

PROBLEM DESCRIPTION:
Enhancements for viavoice.dirTalk_sample.client.en_US

PROBLEM SUMMARY:
Enhancements for viavoice.dirTalk_sample.client
.en_US

------

APAR: IC34532 COMPID: 5724B5900 REL: 200
ABSTRACT: ENHANCEMENTS FOR VIAVOICE.DIRTALK_SAMPLE.SERVER.EN_GB

PROBLEM DESCRIPTION:
Enhancements for viavoice.dirTalk_sample.server.en_GB

PROBLEM SUMMARY:
Enhancements for viavoice.dirTalk_sample.server
.en_GB

------

APAR: IC34534 COMPID: 5724B5900 REL: 200
ABSTRACT: ENHANCEMENTS FOR VIAVOICE.DIRTALK_SAMPLE.SERVER.EN_US

PROBLEM DESCRIPTION:
Enhancements for viavoice.dirTalk_sample.server.en_US

PROBLEM SUMMARY:
Enhancements for viavoice.dirTalk_sample.server
.en_US

------

APAR: IC34535 COMPID: 5724B5900 REL: 200
ABSTRACT: ENHANCEMENTS FOR VIAVOICE.DIRTALK.DOCS.EN_US

PROBLEM DESCRIPTION:
Enhancements for viavoice.dirTalk.docs.en_US

------

APAR: IC34536 COMPID: 5724B5900 REL: 200
ABSTRACT: ENHANCEMENTS FOR VIAVOICE.DIRTALK.TTS.RTE

PROBLEM DESCRIPTION:
Enhancements for viavoice.dirTalk.tts.rte

------

APAR: IC34537 COMPID: 5724B5900 REL: 200
ABSTRACT: VV_RECO_END NOT WORKING CORRECTLY

PROBLEM DESCRIPTION:
reco_flag cannot be unset

PROBLEM CONCLUSION:
new version of ViaVoice custom server

------

APAR: IC34538 COMPID: 5724B5900 REL: 200
ABSTRACT: ENHANCEMENTS FOR VIAVOICE.CLIENT.RTE

PROBLEM DESCRIPTION:
Enhancements for viavoice.client.rte

------

APAR: IC34539 COMPID: 5724B5900 REL: 200
ABSTRACT: ENHANCEMENTS FOR VIAVOICE.TCL.RTE

PROBLEM DESCRIPTION:
Enhancements for viavoice.tcl.rte

------

APAR: IC34541 COMPID: 5724B5900 REL: 200
ABSTRACT: ENHANCEMENTS FOR VIAVOICE.ASR.RTE

PROBLEM DESCRIPTION:
Enhancements for viavoice.asr.rte

------

APAR: IC34542 COMPID: 5724B5900 REL: 200
ABSTRACT: ENHANCEMENTS FOR VIAVOICE.SAMPLE.RTE

PROBLEM DESCRIPTION:
Enhancements for viavoice.sample.rte

------

APAR: IC34543 COMPID: 5724B5900 REL: 200
ABSTRACT: ENHANCEMENTS FOR VIAVOICE.SERVER.COM

PROBLEM DESCRIPTION:
Enhancements for viavoice.server.com

------

APAR: IC34544 COMPID: 5724B5900 REL: 200
ABSTRACT: ENHANCEMENTS FOR VIAVOICE.ASR.EN_US

PROBLEM DESCRIPTION:
Enhancements for viavoice.asr.en_US

------

APAR: IC34545 COMPID: 5724B5900 REL: 200
ABSTRACT: ENHANCEMENTS FOR VIAVOICE.ASR_SERVER.RTE

PROBLEM DESCRIPTION:
Enhancements for viavoice.asr_server.rte

------

APAR: IC34546 COMPID: 5724B5900 REL: 200
ABSTRACT: ENHANCEMENTS FOR VIAVOICE.CORE.RTE

PROBLEM DESCRIPTION:
Enhancements for viavoice.core.rte

------

APAR: IC34547 COMPID: 5724B5900 REL: 200
ABSTRACT: ENHANCEMENTS FOR VIAVOICE.TOOLKIT.ADT

PROBLEM DESCRIPTION:
Enhancements for viavoice.toolkit.adt

------

APAR: IC34548 COMPID: 5724B5900 REL: 200
ABSTRACT: ENHANCEMENTS FOR VIAVOICE.TTS_SERVER.RTE

PROBLEM DESCRIPTION:
Enhancements for viavoice.tts_server.rte

------

APAR: IW00565 COMPID: 5765E4300 REL: 210
ABSTRACT: MEMORY CORRUPTION IN DUMP CAUSES DEADLOCK, PREVENTING GATEWAY

PROBLEM DESCRIPTION:
Concurrent transactions resulting in dumps could potentially
cause the shared memory region which tracks the pointers to the
data in the dump to become corrupt.
This would cause a dump to get caught in a near-infinite loop,
locking the resources necessary for other transactions to write
dumps. Other transactions would deadlock, and the Gateway would
stop processing transactions completely.

LOCAL FIX:
This code patch allows the dump code to more gracefully handle
shared memory corruption condition. To get this eFix, queue
your PMR to ECOMWW,109.

PROBLEM SUMMARY:
Gateway has a memory corruption which will cause
the SET trace manager's to loop forever.
This will cause a deadlock on the PGDecryptor thread.

PROBLEM CONCLUSION:
We have added code that will break out of the loop after
an appropriate # of times.

------

APAR: IW00598 COMPID: 5765E4301 REL: 210
ABSTRACT: MEMORY CORRUPTION IN DUMP CAUSES DEADLOCK, PREVENTING GATEWAY

PROBLEM DESCRIPTION:
Concurrent transactions resulting in dumps could potentially
cause the shared memory region which tracks the pointers to the
data in the dump to become corrupt.
This would cause a dump to get caught in a near-infinite loop,
locking the resources necessary for other transactions to write
dumps. Other transactions would deadlock, and the Gateway would
stop processing transactions completely.

LOCAL FIX:
This code patch allows the dump code to more gracefully handle
shared memory corruption condition. To get this eFix, queue
your PMR to ECOMWW,109.

PROBLEM SUMMARY:
Gateway has a memory corruption which will cause
the SET trace manager's to loop forever.
This will cause a deadlock on the PGDecryptor thread.

PROBLEM CONCLUSION:
We have added code that will break out of the loop after
an appropriate # of times.

------

APAR: IY26152 COMPID: 5765D4900 REL: 210
ABSTRACT: CRASH IN MPC DRIVER STARTING MULTIPLE LINK STATIONS

PROBLEM DESCRIPTION:
Crash in the MPC driver when starting two MPC groups on two
ESCON adapters. The trace back shows mpcdd:mpcaccec3 and
mpcdd:mpcaccec as the executing modules.

PROBLEM SUMMARY:
The MPC device driver crashed when starting
two links over two ESCON adapters at the same time.

PROBLEM CONCLUSION:
MPC device driver modified to contain
additional locking to avoid the race condition that caused
the crash with two links using two ESCON adapters.

------

APAR: IY27411 COMPID: 5765D4900 REL: 210
ABSTRACT: CRASH ON ESCON IOCTL IF BAD ARGUMENTS GIVEN

PROBLEM DESCRIPTION:
Machine crashed when a user space program did an
ioctl(ESCA_GET_SUBS), which is one of the ioctls for the
ESCON device driver API. The user program had supplied an
incorrect argument which the driver did not check before it
used the argument. This lead to a crash on a bad memory
access. The top of the stack traceback is:
        IAR: . escadd:nscaioctl +2ae8 (015b6490): lwz
 r19,0x10dc(r7)
        LR: . escadd:nscaioctl +13c (015b3ae4)

LOCAL FIX:
Ensure that the parameters passed to the ESCON ioctls are
correct if writing a program to the ESCON API.

PROBLEM SUMMARY:
Machine might crash if bad data is passed
in as the argument for some of the ESCON ioctls.

PROBLEM CONCLUSION:
Changed driver to check arguments, thus
avoiding crash.

TEMPORARY FIX:
Ensure arguments are valid before calling the
ioctl.

------

APAR: IY27416 COMPID: 5765D4900 REL: 210
ABSTRACT: CRASH IF USER APPLICATION WRITES ZERO-LENGTH DATA TO ESCON

PROBLEM DESCRIPTION:
Customer is writing and application using the PCI ESCON driver
API. The application was able to crash the machine by writing
data with a length of zero bytes. The traceback for the crash
was:

LOCAL FIX:
Ensure that the application never attempts to write zero bytes.

PROBLEM SUMMARY:
The AIX system might crash if you call
the ESCON write routine passing in a length of zero bytes.

PROBLEM CONCLUSION:
Changed driver to return EINVAL if the
length of the requested write is zero.

TEMPORARY FIX:
Never call the ESCON driver write routine with
a lenght of zero bytes.

------

APAR: IY27443 COMPID: 5765D4900 REL: 210
ABSTRACT: COMMUNICATIONS TRAFFIC HANGS WHILE RUNNING PDM OVER ESCON

PROBLEM DESCRIPTION:
Customer was running PDM over ESCON, using it along with
DB2 Autoloader. At times the communications between the
AIX and os/390 boxes would just hang.

LOCAL FIX:
remove and recreate the ESCON driver (rmdev/mkdev) and then
restart communications

PROBLEM SUMMARY:
All communications over the ESCON adapter
appeared to hang while running PDM (Parallel Data Mover, aka
Infospeed).

PROBLEM CONCLUSION:
The driver was changed to avoid the hang.
The driver was turning off all interrupts from the adapter
and not turning them back on, leading to the hang condition.

TEMPORARY FIX:
If the adapter hangs, stop the applications
and execute rmdev -l escon0 and mkdev -l escon0 and restart.

------

APAR: IY29250 COMPID: 5765E8200 REL: 230
ABSTRACT: BAD MSG'S IN SMIT SYNC GMD PANEL (GEORM 2.3)

PROBLEM DESCRIPTION:
The smit panel for sync'ing GMD's in
HAGEO 2.3 has invalid prompts due to
corruption of gmd_cmd_opt and gmd_smit.msg.
The problem was introduced by IY22526.

PROBLEM SUMMARY:
I reopened this apar to include other
changes to the geoRM smit panels. They
include corrections to a problem with
help functions on the main geoRM menu,
and an incorrect option on the geoRM
topology menu.

PROBLEM CONCLUSION:
I reopened this apar to include other
changes to the geoRM smit panels. They
include corrections to a problem with
help functions on the main geoRM menu,
and an incorrect option on the geoRM
topology menu.

------

APAR: IY29705 COMPID: 5765D4900 REL: 210
ABSTRACT: ESCON ADAPTER CAN'T BE DEFINED ON P690

PROBLEM DESCRIPTION:
Customer is not able to get 'escon0' device available on a
REGATTA system. 'lsdev -C' shows:
riciop0 Available 3V-08 IBM ARTIC 960 PCI Adapter
ddriciop0 Defined 3V-08-00 IBM ARTIC 960 PCI Device Driver
Problem is that ddriciop0 stays in defined state.
PTFs (U480865 and U480867) for REGATTA support are installed.
Filesets are at following levels.
devices.artic960.rte 1.4.4.0
devices.pci.esconCU.rte 2.1.3.0.
Another side effect for this problem is, that slot position
3V-08 can't be selected in the escon slot definition smitty
panels.

LOCAL FIX:
Get an e-fix from ESCON support group or install ESCON PTFs
in following order:
devices.artic960.rte 1.4.4.0
devices.pci.esconCU.rte 2.1.3.0

PROBLEM SUMMARY:
PCI ESCON installation image modified
to ensure that the PCI ESCON and ARTIC images are installed
in the correct order to maintain the correct contents of
the PdAt database.

PROBLEM CONCLUSION:
devices.pci.esconCU.rte updated.

TEMPORARY FIX:
Reinstall devices.pci.esconCU.rte and then reboot

------

APAR: IY31950 COMPID: 5765B9501 REL: 330
ABSTRACT: NEGATIVE IN_DOUBT VALUES ARE NOT DOCUMENTED VERY WELL

PROBLEM DESCRIPTION:
the output of mmcheckquota might represent to the user
negative values for the in_doubt column.
The Documentation doesnt specify neg. values at all,
so its occurence is quite confusing for customers, and
should be documented.

PROBLEM SUMMARY:
negative in-doubt values for GPFS quotas were not
documented

PROBLEM CONCLUSION:
In the Administration and Programming Reference in the
chapter "Performing GPFS Administration tasks" under the
heading "Checking quotas" and in the chapter
"GPFS commands" under the description section of the
mmcheckquota command, add the paragraph:
When issuing the mmcheckquota command on a mounted file
system, negative in-doubt values may be reported if the
quota server processes a combination of up-to-date and
back-level information. This is a transient situation
and may be ignored.
In the Administration and Programming Reference in the
chapter "Performing GPFS Administration tasks" under the
heading "Listing quotas" and in the chapter
"GPFS commands" under the description section of the
mmlsquota command, add the paragraph:
When issuing the mmlsquota command on a mounted file
system,negative in-doubt values may be reported if the
quota server processes a combination of up-to-date and
back-level information. This is a transient situation
and may be ignored.
In the Administration and Programming Reference in the
chapter "Performing GPFS Administration tasks" under the
heading "Creating file system quota reports" and in the
chapter "GPFS commands" under the description section of
the mmrepquota command, add the paragraph:
When issuing the mmrepquota command on a mounted file
system,negative in-doubt values may be reported if the
quota server processes a combination of up-to-date and
back-level information. This is a transient situation
and may be ignored.
V3 The man pages for mmcheckquota, mmlsquota and
mmrepquota were updated with this information.

------

APAR: IY31955 COMPID: 5765E8200 REL: 230
ABSTRACT: GEO NODE DOWN SCRIPT INCORRECT

PROBLEM DESCRIPTION:
hacmp shutdown with local takeover, all async gmd in remote
site changed from available to defined.

LOCAL FIX:
modify the script Geo_node_down_complete
the line 71 should be
      FAIL_SITE=`$HAGEO_UTILS/geo_info node -s $FAILING_NODE`

PROBLEM SUMMARY:
When Geo_node_down_complete determines at which site a
failure has occurred, it invokes geo_info without the node
parameter. As a result, the check to determine if the
failure was local will always fail and the script
Geo_remote_peer_down_complete will always be called. This
script should not be called if the failure was local.

PROBLEM CONCLUSION:
Geo_node_down_complete has been updated to invoke geo_info
with the node parameter when determining the site where
the failure occurred. As a result,
Geo_remote_peer_down_complete will only be called when the
failure is at a remote site.

------

APAR: IY32052 COMPID: 5724C3505 REL: 310
ABSTRACT: ENABLE WEBSPHERE VOICE RESPONSE 3.1 ENHANCEMENTS

PROBLEM DESCRIPTION:
WebSphere Voice Response Pre-Maintenance Level V3.1.1
enhancements.

------

APAR: IY32107 COMPID: 5765E8200 REL: 230
ABSTRACT: JFS ERRORS DURING SITE ISOLATION OF REMOTE SITE.

PROBLEM DESCRIPTION:
On a hageo system, a potential for JFS errors exist during Site
Isolation where the remote site recovers before HACMP event
processing can halt the remote site.
When the geo-network drops long enough to start site isolation
but recovers before the isolation is complete the the gmd on
the local site may return write errors to avoid data corruption.
These write errors are logged by JFS as JFS_LOG_WRITE_ERR,
JFS_FSCK_REQUIRED, JFS_META_WRITE_ERR.

PROBLEM SUMMARY:
When a geo-mirroring network problem causes site isolation,
the HA event processing halts the nodes at one site, in
order to prevent data divergence which occurs when both
sites update the data without mirroring to each other.
If the network heals before this event processing completes,
a write request may go across the network after the gmddown
gets issued on the remote node but before any nodes are
halted. When this happens, the remote node returns an error
to the local node, and the local node fails the application
write, because it knows something is wrong. The problem is
that if the GeoMirror devices are being used to mirror a
JFS filesystem, and the application write happens to be
a write to the jfslog device, the write error to the jfslog
device sets off a chain reaction of JFS errors, which requires
the user to recover the filesystem. If the user panics and
reboots the local node, this causes the filesystem to
become corrupted, as JFS data that was stored in RAM and
needed to recover the filesystem gets lost after a reboot.
Note that this assumes the nodes at the remote site are
halted, and the nodes at the local site survive after the
site isolation processing completes.

PROBLEM CONCLUSION:
The solution is for the local node to avoid failing the
application write request by continuing to resend the
remote write request to the other site, even though it will
probably fail over and over again. This will cause the
application write to hang until the site isolation event
processing gets around to issuing a gmddown command on the
local node. The gmddown will break the write processing
out of the resend loop, and the filesystem and applications
running above it will continue running without any problems.

------

APAR: IY32232 COMPID: 5765E6400 REL: 220
ABSTRACT: GEO_REMOTE_JOIN HAS ERRANT PIECE OF SCRIPT WITH APAR IY21244

PROBLEM DESCRIPTION:
When HAGEO 2.2 APAR IY21244 is applied, the
provided /usr/sbin/gmd/scripts/
Geo_remote_join has an errant piece of
scripting that references $HA_GMDS.
The HAGEO 2.2 script 'Geo_remote_join'
never sets or gets passed the value of
$HA_GMDS, and then the script block which
uses it never gets executed.
It appears that the errant script block
which uses $HA_GMDS was meant for a
completely different HAGEO 2.2 script,
and accidently found its way into
'Geo_remote_join'. Currently, the errant
script block does not harm, other than
outputting an error that "HA_GMDS: variable
not set" or "HA_GMDS: parameter not set".

LOCAL FIX:
Edit the /usr/sbin/gmd/scripts/
Geo_remote_join script, and remove
the script block that references and
uses the $HA_GMDS variable. This must
be done with all HAGEO 2.2 nodes in the
cluster.

PROBLEM SUMMARY:
When HAGEO 2.2 APAR IY21244 is applied, the
provided /usr/sbin/gmd/scripts/
Geo_remote_join has an errant piece of
scripting that references $HA_GMDS.
The HAGEO 2.2 script 'Geo_remote_join'
never sets or gets passed the value of
$HA_GMDS, and then the script block which
uses it never gets executed.
It appears that the errant script block
which uses $HA_GMDS was meant for a
completely different HAGEO 2.2 script,
and accidently found its way into
'Geo_remote_join'. Currently, the errant
script block does not harm, other than
outputting an error that "HA_GMDS: variable
not set" or "HA_GMDS: parameter not set".

PROBLEM CONCLUSION:
Create another variable other than "$HA_GMDS", and
initialize it with the GMD names being used in the cluster.
This will allow the code to function properly.

------

APAR: IY32233 COMPID: 5765E6400 REL: 220
ABSTRACT: HAGEO: LOGREDO NOT BEING RUN ON GMD-BASED FILESYSTEMS

PROBLEM DESCRIPTION:
Logredo is not run on gmd_based JFS filesystems after upgrading
HACMP.

PROBLEM CONCLUSION:
Change Geo_mount_fs to run logredo once for each gmd-based
jfslog that is detected.

------

APAR: IY32874 COMPID: 5765E5400 REL: 450
ABSTRACT: BASE FIXES FOR HACMP 4.5.0

PROBLEM DESCRIPTION:
Base Fixes for HACMP 4.5.0:
- CLM_NOLOCKMGR after starting cluster services (HAES)
- Selective Fallover VG fails to remove errnotify stanzas (HAES)
- Stale LV copies not synchronized on lazy update
- cm.log shows garbage characters when swap_adapter runs (HAS)
- CSPOC (Add a Journaled FS> lists concurrent VG in picklist
- hacmp/es APPLY snapshot misbehaves if sites are defined
- clgetesdbginfo enhancements
- New IP Label list in SMIT Change/Show Interface is empty
- clstat -r does not react correctly
- clstat display incomplete information (HAES)
- Add an Adapter prints debug msg <Attempting to add interface>
- DARE unexpectedly brings resource groups online.
- Quorum setting not maintained on VG discovery
- Misleading message "Network already has Subnet"
- Discovering IP Connectivity gives error byt SMIT shows success
- Unable to add non-aliased network via DARE (HAES)
- Node persists in RG although node removed from topology
- HAS: clver error with max RG name concatenates RG and policy
- RG_MOVE-Node list is ignored, ONLINE SECONDARY acquires rg
- HAS: Lock Manager fails after node failure
- Change/show/remove IP network returns 1800-106 error occurred
- CPSOC start of cluster hangs on 1st node w/ rotating IP label
- Quorum settings no in effect for first vary-on after lazy upd
- SMIT cl_updatevg should list only inactive VGs - cllsvg
- HAS: Pager Notify with retry=0 failes with unfriendly msg
- CLLSNODE segfaults when a node contains many adapters
- HAS: w/fastconn clvery flags all HACMP event in error
- HAES: nodeXnode leaves HACMPpager with HAS path to sample.txt
- HAES: post nodeXnode leaves small xclstat display
- HAES: Parallel RG processing - rg_move works for 1 RG only
- clfindres utility error message is untranslated
- HAS,HAES: applying snapshot fails with libodm error on CuAt
- HAS,HAES: Extremely long gallover times due to IMFS commands
- HAES: DARE in a new conc RG gives <param not set> w/ RESGRP
- All messages in clavan.log must be English only
- Context help is missing in Save Event Summaries SMIT panel
- Pick list in Add initial interfaces panel is untranslated
- HAS: DARE a change to HACMP pager refreshed clstrmgr;leaves SC
- Auto Error Notification with FAStT500 disk array
- Ordering field is set incorrectly if HAGEO is installed
- HAES: Concurrent VG not varied on
- Add support for FAStT500
- Erroneous clverify test on /.rhosts
- Allow latest ESS models in RAID concurrent mode
- HAES: Error information not logged to shutdown_rsct.out file
- Syntax error in get_disk_vg_fs
- Cannot create GPFS Filesystem with mmcrfs - Need fence utils
- HAES: resource group state not displayed in clstat
- HAES: rg_move tries acquisition twice on same node
- After NxN Migration no /etc/services,inetd.conf clver entries
- HAES: clstat.cgi has a hard coded refresh interval
- HAVIEW: A SMIT window should appear when admin is selected
- Handle Missing disks
- clverify interprets some warning as errors
- Warnings at verify about .rhosts permissions during IP Discov
- Do no modify /etc/rc.shutdown if ofiicial callout is present
- HACMP 4.5 Documentation Updates
- Unacceptable performance of HACMP/ES cmds due to ping
- HACMP fails to acquire a cascading switch Resource Group
- HAES: Selective fallover does not occur
- Application Availability Analysis (AAA) Tool times out
- Persistent not allowed on same subnet as Service Alias Label
- HAS/HAES: cl+lsvg and cl_lsfs errors : Cannot locate VG/FS
- Multiple Service Labels in 1 Resource Group do not fallover
- cl_configure_persistent_address error if alias in /etc/hosts
- Add NAME_SERVER stanza to HACMPnode

PROBLEM SUMMARY:
Base Fixes for HACMP 4.5.0:
-CLM_NOLOCKMGR after starting cluster services (HAES)
-Selective Fallover VG fails to remove errnotify stanzas HAES
-Stale LV copies not synchronized on lazy update
-cm.log shows garbage characters when swap_adapter runs (HAS)
-CSPOC <Add a Journaled FS> lists concurrent VG in picklist
-cluster snapshot:Site definitions not saved

------

APAR: IY33418 COMPID: 5765D4900 REL: 210
ABSTRACT: CUMULATIVE SERVICE APAR FOR AIX PCI ESCON DRIVER

PROBLEM DESCRIPTION:
This is a cumulative service APAR for the AIX PCI ESCON driver.
The PTF for this APAR will include all current fixes for the
fileset devices.pci.esconCU.rte.

PROBLEM SUMMARY:
Cumulative service APAR for AIX PCI ESCON
driver

------

APAR: IY33419 COMPID: 5765D4900 REL: 210
ABSTRACT: CUMULATIVE SERVICE APAR FOR AIX ESCON MPC DRIVER

PROBLEM DESCRIPTION:
This is a cumulative service APAR for the AIX ESCON MPC device
driver. The PTF for this APAR will include all current fixes
for the fileset devices.common.IBM.esconCU.mpc.rte.

PROBLEM SUMMARY:
Cumulative Service APAR for AIX ESCON MPC

------

APAR: IY33753 COMPID: 5765E8200 REL: 230
ABSTRACT: HAGEO 2.3 CHANGES NEEDED TO SUPPORT HACMP 4.5

PROBLEM DESCRIPTION:
HAGEO 2.3 requires changes in order to support HACMP 4.5.
There are two problems that must be fixed.
1. The geo_migrate_hacmp command fails when trying to read
    cluster topology data from HACMP 4.5.
2. The existing Geo_Primary and Geo_Secondary network
    definitons do not work with HACMP/ES 4.5, because the
    pathnames of the NIM modules are incorrect.

PROBLEM CONCLUSION:
The required changes have been made to support HACMP 4.5.
1. The geo_migrate_hacmp command has been updated to work
    properly on HACMP 4.5, as well as all other supported
    HACMP releases.
2. The correct Geo_Primary and Geo_Secondary network
    definitions will be defined for the HACMP release that
    is being used. HACMP migration processing will make
    sure these network definitions remain correct when your
    cluster eventually migrates to a later HACMP release.

------

APAR: IY33857 COMPID: 5765B9500 REL: 140
ABSTRACT: MMSDRFS 0 LENGTH AFTER PANIC

PROBLEM DESCRIPTION:
mmsdrfs 0 length after panic

PROBLEM SUMMARY:
after node crash the mmsdrfs file was made
zero length

PROBLEM CONCLUSION:
need to do sync after updating key files

------

APAR: IY34168 COMPID: 5765E6900 REL: 310
ABSTRACT: LOADLEVELER FIXES

PROBLEM DESCRIPTION:
support for the 64-bit aix kernel

PROBLEM SUMMARY:
Loadleveler Fixes

------

APAR: IY34221 COMPID: 5765E8200 REL: 230
ABSTRACT: SYNC COMMAND HANGS

PROBLEM DESCRIPTION:
Application writes to GeoMirror devices may hang on
a node which leaves the HACMP cluster by way of
forced node down.

PROBLEM SUMMARY:
Application writes to GeoMirror devices may hang on
a node which leaves the HACMP cluster by way of
forced node down.
SYMPTOM STRING

PROBLEM CONCLUSION:
The forced node down event processing has been changed so
that the remote peer nodes can correctly determine the
GeoMirror device status on the node which has left the
HACMP cluster by way of forced node down.

------

APAR: IY34244 COMPID: 5765F7000 REL: 810
ABSTRACT: INTERNAL APAR FOR XLF 8.1.0.1 COMPILER PTF

PROBLEM DESCRIPTION:
INTERNAL APAR FOR THE XLF 8.1.0.1 COMPILER PTF

PROBLEM CONCLUSION:
INTERNAL APAR FOR XLF 8.1.0.1 PTF

------

APAR: IY34246 COMPID: 5765F7100 REL: 810
ABSTRACT: INTERNAL APAR FOR XLF 8.1.0.1 RUNTIME PTF

PROBLEM DESCRIPTION:
INTERNAL APAR FOR XLF 8.1.0.1 RUNTIME PTF

------

APAR: IY34284 COMPID: 5724C3505 REL: 310
ABSTRACT: CACHEM OPERATION WITH INVALID SEGMENT DOES NOT RETURN EDGE

PROBLEM DESCRIPTION:
Playing a Prompt with an invalid Voice Segment does not return
an EDGE to the State Table. Instead it eventually plays the
technical difficulties message and the Satte table exits.

PROBLEM SUMMARY:
Playing a Prompt with an invalid voice segment
does not return an EDGE to state table. Instead it eventually
plays the technical difficulties message and the state table
exits.

------

APAR: IY34295 COMPID: 5724C3505 REL: 310
ABSTRACT: PROVIDE DTBE SUPPORT FOR WEBSPHERE VOICE SERVER 3.1

PROBLEM DESCRIPTION:
Enhancements to provide DTBE support for Websphere Voice Server
version 3.1

PROBLEM SUMMARY:
Enhancements to DTBE to provide support
for Websphere Voice Server 3.1

------

APAR: IY34456 COMPID: 5765F7101 REL: 131
ABSTRACT: INTERNAL APAR FOR XLOPT 1.3.1 PTF

PROBLEM DESCRIPTION:
INTERNAL APAR FOR XLOPT 1.3.1 PTF

LOCAL FIX:
NO LOCAL FIX

PROBLEM CONCLUSION:
internal apar for XLOPT 1.3.1 PTF

------

APAR: IY34697 COMPID: 5697E3000 REL: 220
ABSTRACT: TWO FIXES IN WNN6 DICTIONARY

PROBLEM DESCRIPTION:
Two worng words in Wnn6 system dictionary.

LOCAL FIX:
Change for jkit.Wnn6.base.

PROBLEM SUMMARY:
This apar includes fixes of some problems.

PROBLEM CONCLUSION:
All problems we found were fixed.

------

APAR: IY34700 COMPID: 5765C6401 REL: 443
ABSTRACT: MEMDBG 4.4.3.0 BASE IMAGES

PROBLEM DESCRIPTION:
Adding support for AIX 5.2

------

APAR: IY34701 COMPID: 5765F7101 REL: 131
ABSTRACT: XLOPT 1.3.1.0 BASE IMAGES

PROBLEM DESCRIPTION:
Adding Support for AIX 5.2

PROBLEM SUMMARY:
same as submitter's text

PROBLEM CONCLUSION:
Adding support for AIX 5.2

------

APAR: IY34703 COMPID: 5765F7102 REL: 136
ABSTRACT: XLSMP 1.3.6.0 BASE IMAGES

PROBLEM DESCRIPTION:
Adding support for AIX 5.2

PROBLEM CONCLUSION:
Adding Support for AIX 5.2

------

APAR: IY35041 COMPID: 5765D5100 REL: 340
ABSTRACT: LATEST PSSP 3.4.0 FIXES AS OF AUGUST 2002

PROBLEM DESCRIPTION:
This is the lastest PSSP ptf as of August 2002
Order this apar to get all of the ptfs as of August 2002.

PROBLEM SUMMARY:
This is a packaging apar for PSSP 3.4.0 fixes
as of August 2002.
August 2002

PROBLEM CONCLUSION:
This is a packaging apar for PSSP 3.4.0 fixes
as of August 2002

------

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]