[prev in list] [next in list] [prev in thread] [next in thread] 

List:       aix4fixes
Subject:    Re: New_AIXV4_Fixes
From:       AIX Service Mail Server <aixserv () austin ! ibm ! com>
Date:       2001-10-23 7:23:31
[Download RAW message or body]

APAR: IY06869  COMPID: 5765E2820  REL: 430
ABSTRACT: CICS / UNIX 4.3 THE CEMT INQ PROG NEW COMMAND WILL FAIL WITH

PROBLEM DESCRIPTION:
 When we run the command
 CEMT I PROG(JT*)
 and append the parm NEW
 ie
 Pro(JTIME   ) Cob Ena NEW                  Invalid Change
 gets returned.
 This same operation will run fine on CICS 4.2
 One difference that we see on CICS 4.2 is that a call to
 the function RegPR_SpecialSetOptHndlr is made.
Transarc Defect 202569

LOCAL FIX:
Use CEMT SET PROG instead of INQ

PROBLEM SUMMARY:
USERS AFFECTED: CICS users, Release 430
When the CEMT I PROG(prog_name) command was executed with the
NEW parameter to force a new copy of a program into the run
time, an error stating Invalid Change was returned. This
command had worked in version 4.2

PROBLEM CONCLUSION:
The problem occurred because a previously applied fix had
changed a copy command so that it did not copy enough
characters of the program name and padded the name with an
invalid character. The code has been corrected, and problem
does not occur.
KEYWORDS: PTF5 CICS 4.3.0.5, defect # 202569

------

APAR: IY09760  COMPID: 5765D1400  REL: 220
ABSTRACT: SEC_LOGIN_NEWGROUPS RETURNS A BOGUS LOGIN CONTECT

PROBLEM DESCRIPTION:
sec_login_newgroups returns an incorrect login context

PROBLEM SUMMARY:
Customer's program using sec_login_newgroups() fails.
klist output from a sec_login_newgroups born context
looks like :-
Global Principal: <NIL>/<NIL>
Cell:      00000000-0000-0000-000000000000 <NIL>
Principal: 00000000-0000-0000-000000000000 <NIL>
Group:     00000000-0000-0000-000000000000 <NIL>

PROBLEM CONCLUSION:
In sec_login_pvt_create_restricted_context(), we now
initialize the generation_id,v1_v_info,and in particular we
initialize v1_v_info.epac_chain of the new login context.

------

APAR: IY11841  COMPID: 5639I0920  REL: 430
ABSTRACT: ABEND APCT RECEIVED WHEN RUNNING PROGRAMS COMPILED WITH MICRO

PROBLEM DESCRIPTION:
When running CICS programs compiled with Micro Focus COBOL
Workbench against TXSeries 4.3 for Windows NT, APCT abends are
received.

PROBLEM SUMMARY:
USERS AFFECTED: CICS users, Release 430
Customers attempting to use the Micro Focus COBOL Workbench
with TXSeries 4.3 received an APCT abend because the Workbench
was not supported in TXSeries 4.3.

PROBLEM CONCLUSION:
This APAR adds support for the Micro Focus COBOL Workbench to
TXSeries 4.3. The abends no longer occur.

------

APAR: IY13475  COMPID: 5765E2820  REL: 430
ABSTRACT: THE SMITTY PANEL WILL NOT COLD START A PPC GATEWAY. MESSAGE

PROBLEM DESCRIPTION:
The command generated by SMITTY when cold-starting the ppc
gateway is:

LOCAL FIX:
Start via command line:
cicsppcgwy /.:/cics/ppc/gateway/rs020gwy StartType=cold

PROBLEM SUMMARY:
USERS AFFECTED: CICS users, Release 430
(AIX only) When the System Management Interface Tool (SMIT)
utility was used to start a Peer-to-Peer Communications (PPC)
Gateway server, the operation failed with the message Invalid
Format. The error occurred because the command was generated
with parameters in the wrong order.

PROBLEM CONCLUSION:
The parameter string has been placed in the correct order for
the generated command, and the PPC Gateway server now starts.

------

APAR: IY15168  COMPID: 5765D1400  REL: 220
ABSTRACT: FOREIGN MEMBERS OF GROUP_OBJ NOT GIVEN CORRECT PERMS ON DFS FILE

PROBLEM DESCRIPTION:
If a foreign user is a member of group_obj he
does not get the correct access.  If he is
in a group explicitly put on an acl, he
gets the correct access.

PROBLEM SUMMARY:
When a foreign user is added to a local group.
The foreign user is not getting the permissions
of that local group.

PROBLEM CONCLUSION:
we have modified the code in such a way that the
foreign user will get the permissions of that
local group.

------

APAR: IY15347  COMPID: 5765D1700  REL: 220
ABSTRACT: FL/REP/FT/BAKSERVER CORES CAN OVERWRITE EACH OTHER

PROBLEM DESCRIPTION:
fl/bak/rep/ftservers all drop core in /var/dce/dfs/adm
if more than one of these processes drop core at the
same time, the cores overwrite each other and bos
can misname the corefile

PROBLEM SUMMARY:
If more than one process drop cores at the same time then
bosserver gets confused in renaming the files and the core
file gets corrupted.

PROBLEM CONCLUSION:
The server process is now been modified to start from
/var/dce/dfs/adm/<server process name> directory instead
of /var/dce/dfs/adm directory. Hence they all drop core in
their respective directories.

------

APAR: IY15660  COMPID: 5765D1700  REL: 220
ABSTRACT: DFSBIND SPINS AND CONSUMES EXCESSIVE CPU TIME

PROBLEM DESCRIPTION:
dfsbind appears to be hung, spinning in a loop which
consumes excessive CPU time.
If one attaches via dbx to the dfsbind process, the
stack should look similar to:
(dbx) th current 6;t
krb5_fcc_open_file(??, ??) at 0xd04c6cbc
krb5_fcc_next_cred_aux(??, ??, ??, ??) at 0xd05c09e8
krb5_fcc_store(??, ??) at 0xd05c31c4
krb5_get_credentials_dce(??, ??, ??, ??) at 0xd05a3a84
sec_krb_get_cred(??, ??, ??, ??, ??, ??, ??, ??) at 0xd05a1da8
cred_from_cred_rep(??, ??, ??, ??) at 0x100060b4
handle_sec_krb_get_cred(??, ??, ??) at 0x10004700
do_auth_request(??, ??, ??, ??) at 0x10002e1c
ProcessRequest(??) at 0x100021f4
service_thread(??) at 0x10001b58
pthread._pthread_body(??) at 0xd012c358

LOCAL FIX:
Stop and restart dfsbind.

PROBLEM SUMMARY:
nd appears to be hung, spinning in a loop which
consumes excessive CPU time

PROBLEM CONCLUSION:
code has been modified to check for ENOENT error
status from within loop in krb5_fcc_store and break
out of loop if we get that error

TEMPORARY FIX:
recycle dfsdind.

------

APAR: IY15860  COMPID: 5765D1700  REL: 220
ABSTRACT: RMXCRED CORE DUMPS IN SEC_LOGIN_PVT_FREE_LOGIN_CONTEXT

PROBLEM DESCRIPTION:
rmxcred core dumps with the following stack trace:
Segmentation fault in dce_free at 0xd042b2c0 ($t1)
0xd042b2c0 (dce_free+0x34) 8003ffd8          l   r0,-40(r3)
(dbx) where
dce_free(??) at 0xd042b2c0
libdcelibc_r.free(??) at 0xd07a9488
sec_login_pvt_free_login_context(??) at 0xd04c88e0
sec_login_pvt_allocate_login_context() at 0xd04ce428
sec_login_pvt_get_default_context(??) at 0xd04cec88
sec_login_get_current_context(??, ??) at 0xd04bde80
seek_and_destroy(??) at 0x10001288
main(??, ??) at 0x10002120

PROBLEM SUMMARY:
rmxcred coredumps in dce_free with segmentation fault

------

APAR: IY16130  COMPID: 5765D1400  REL: 220
ABSTRACT: 'DCED' DAEMON IS UNABLE TO REFRESH THE MACHINE CREDENTIALS.

PROBLEM DESCRIPTION:
'dced' daemon is unable to refresh the machine credentials and
is failing with the error status '0x14129098' i.e.
KRB5_REALM_UNKNOWN. This error code denotes "Cannot find KDC
for requested realm". This suggests that the security servers
are not reachable. But, surprisingly, customer is getting this
error code even though the security servers are actually
reachable.
The reason for this problematic behaviour is, rca_rebind() is
failing due to an incorrect manipulation of the binding
handles' count. The problem is seen when the customer has more
than 12 entries in pe_site file. i.e.  six security servers,
and none of the sec servers are reachable at any point of
time.

LOCAL FIX:
In the rca_rebind() function, the way the binding handle count
is manipulated is corrected.

PROBLEM SUMMARY:
dced fails to refresh the machine self credentials saying
that the security servers are not reachable. Consequently,
the machine will lose its credentials.

PROBLEM CONCLUSION:
This problem has been fixed by changing the way the binding
handle count is manipulated.

TEMPORARY FIX:
Re-start DCE.

------

APAR: IY16360  COMPID: 5765D1700  REL: 220
ABSTRACT: OLD AUDIT DIRECTORY PREVENTS SECD FROM STARTING

PROBLEM DESCRIPTION:
secd (or possibly any other dce daemon using audit) does not
start with the following message found in the fatal.log:
2001-02-01-14:46:30.256-06:00I----- secd FATAL sec rs_mainthr
rs_main.c 1526 0x3 005b290 msgID=0x10323078 Cannot make
directory
This situation arises when a previously running dce daemon
(using audit) apparently does not shutdown gracefully, allowing
for proper cleanup of its /var/dce/audit/client/<pid>
directory.  When using audit, subdirectories are created in the
afore-mentioned directory using the pid as the directory name.
If a new dce daemon is starting with a pid equal to an
already-existing audit subdirectory, then it will fail to
start.

LOCAL FIX:
Simply trying to restart the dce daemon again will likely be
successful since the odds of obtaining the exact pid as before
are extremely low.  Or to be absolutely certain, one could get
a "ps" listing of the currently running dce daemons and
determine which <pid> subdirectory in /var/dce/audit/client is
no longer in use and remove that directory and its contents.

PROBLEM SUMMARY:
DCE daemon (in this case secd) fails to start
with a "Cannot make  directory" error message
in the fatal.log

PROBLEM CONCLUSION:
If the /var/dce/audit/client/<pid> directory
already exits then simply remove the
update_binding_file in that directory and
continue as normal.

TEMPORARY FIX:
Simply restart daemon

------

APAR: IY16379  COMPID: 5765D6600  REL: 201
ABSTRACT: EXECUTION GROUP TERMINATES ON STARTUP WITH BIP2123

PROBLEM DESCRIPTION:
The two lock files:
(a) MQSeriesIntegrator2BrokerResourceTableLockSempahore
(b) MQSeriesIntegrator2RetainedPubsTableLockSemaphore
in /var/mqsi/locks contain a semaphore id each that is used to
control access to particular resources. It would appear that
these two files may not always get cleaned up/deleted when all
broker processes on the box have been stopped.  If you reboot
the machine then obviously the semaphores no longer exist on
startup, yet if the lock files still exist, they now reference
semaphore ids that are no longer present.
If lock file (a) exists yet the semaphore it references does not
exist, then the Execution Group terminates on startup with
BIP2123.
If lock file (b) exists yet the semaphore it references does not
exist, then the Admin agent (bipbroker) process terminates on
startup with BIP2088.

PROBLEM SUMMARY:
When the system is rebooted the IPC list is cleared out but
the disk files are not. This means that the semaphors retained
in the lock files are reused causing failure when the broker
is restarted.

PROBLEM CONCLUSION:
This memory overwrite has been removed.

------

APAR: IY16679  COMPID: 5765D6600  REL: 201
ABSTRACT: INADEQUATE ERROR MESSAGE PRODUCED FOR EXECUTION GROUP FAILURE

PROBLEM DESCRIPTION:
The execution group fails after a full deploy when trying to
handle x '0', generating message BIP4120E:
Configuration message contained an invalid SQL expression;
however the precise problem is not covered by an error message
BIP0055E Cannot find message 0.
The message number does not exist in the message catalog file
MQSIv201.
Turn on Control Center tracing to capture details of the error
Retry the operation and contact your IBM support center.

PROBLEM SUMMARY:
Missing BIP error message.

PROBLEM CONCLUSION:
BIP2925 has been added to address this issue.

------

APAR: IY16830  COMPID: 5765E2820  REL: 430
ABSTRACT: ERZ057032E : BUFFER OVERFLOW WHILE PROCESSING INTERNAL TEXT -

PROBLEM DESCRIPTION:
When running with the LANG environemnt variable set to Ja_JP
and "CEMT I" is issued, ERZ0570032E Buffer OVERFLOW while
processing internal text - supplied size length:70, required
size: 87 is returned.
Defect 203419.

PROBLEM SUMMARY:
USERS AFFECTED: CICS users, Release 430
Customers running CICS with a Japanese locale sometimes
received the message ERZ057032E Buffer OVERFLOW. This message
is generated when a message being translated overflows the
internal message buffer.

PROBLEM CONCLUSION:
The size of the internal buffer has been increased to better
handle the translation of messages into languages that use
double-byte character sets. This has corrected the problem.

------

APAR: IY17186  COMPID: 5639I0920  REL: 430
ABSTRACT: CICSLU PROCESS MEMORY GROWTH

PROBLEM DESCRIPTION:
Over a short period of time growth the cicslu process to 100mb a
nd more and crashes the system.

PROBLEM SUMMARY:
USERS AFFECTED: CICS users, Release 430
For short-lived threads, such as those found in FEPI (SNA LU0
Listener), the linked list of stash pointers was not cleaned up
properly, resulting in a memory leak.

PROBLEM CONCLUSION:
The problem was with the checking of the use count for this
activity.  Now when the use count is zero, the stash buffers
are freed. This has resolved the memory leak.

------

APAR: IY17192  COMPID: 5765E2820  REL: 430
ABSTRACT: CICSTRAN COMPILE HAS PROBLEMS WITH SQL STATEMENTS

PROBLEM DESCRIPTION:
The cicstran command is modifying the EXEC SQL EXECUTE IMMEDIATE
statement when it is coded over several lines if the database
precompiler has not been run first.

LOCAL FIX:
If the EXEC SQL includes EXECUTE IMMEDIATE code the statement on
one continuous line.

PROBLEM SUMMARY:
USERS AFFECTED: CICS users, Release 430
The cicstran command stripped parameters from SQL statements if
the statement was coded over a number of lines. If the
statement was coded on one line, the problem did not occur.

PROBLEM CONCLUSION:
The problem occurred because the parameters between the EXEC
and END EXEC delimiters were being stripped when the statement
was coded on multiple lines. The parser in cicstran has been
changed to handle SQL statements across multiple lines, and the
problem has been corrected.

------

APAR: IY17486  COMPID: 5765D6600  REL: 201
ABSTRACT: COBOL STRUCTURES, CONTAINING SIGNED DECIMAL NUMBERS (PIC S9),

PROBLEM DESCRIPTION:
When the MRM-parser within MQSI v2.01 detects cobol structures,
containing fields, defined as signed decimals (PIC S9),
it rejects them.
The CWF definitions for those fields are extended decimal,
signed, length 4 .
Following is the explanation, given by the customer:
The Cobol structure contains PIC S9(n) defined fields.
MRM rejects to parse records for declaration of signed decimal
numbers :
-- PIC S9(n) with n > 1 for example PIC S9(4) :
-- if the fields content is 0 but flagged as positive
   (x-Representation F0 F0 F0 C0) .
-- As far as I remember this is valid on OS/390.
   MRM accepts the content if we zap the C0 to F0.

LOCAL FIX:
Use the NEON-parser to parse/handle those messages.

PROBLEM SUMMARY:
We accept only F in the sign position.  We do not accept C or D.

------

APAR: IY17512  COMPID: 5765D2800  REL: 430
ABSTRACT: HACMP: FAST CONNECT STARTS WITH IMPROPER LC_ALL VALUE

PROBLEM DESCRIPTION:
The HACMP script which starts Fast Connect does not restore
the LC_ALL settings.  Fast Connect is run with LC_ALL=C.

LOCAL FIX:
Modify get_fast_connect_rs to export LC_ALL="".

PROBLEM SUMMARY:
The HACMP script which starts Fast Connect does not restore
the LC_ALL settings. Fast Connect is run with LC_ALL=C.

PROBLEM CONCLUSION:
Set LC_ALL back to null before starting Fast Connect.

------

APAR: IY17808  COMPID: 5765D6600  REL: 201
ABSTRACT: XML PARSER ADD TRUE TO THE END OF XML DECLARATION.

PROBLEM DESCRIPTION:
XML Parser add True to the end of XML Declaration.

PROBLEM SUMMARY:
On AIX whitespace between XML tags becomes corrupted in some
circumstances, ie CrLfs, resulting in the XML parser inserting
spurious TRUE's.

------

APAR: IY17814  COMPID: 5765E2820  REL: 430
ABSTRACT: SPORADIC QIDERR WHEN INQUIRING ON EXISTING TS QUEUES WITH NAMES

PROBLEM DESCRIPTION:
Sporadically if the TS queue name is less than 8 characters on
an INQUIRE TSQUEUE the queue name is being passed to
RegTS_GetRun padded with invalid characters.  This is returning
an EIB RESP of 44, a QIDERR.
Defect 203457.

PROBLEM SUMMARY:
USERS AFFECTED: CICS users, Release 430
When a customer used the EXEC CICS INQUIRE TSQ(tsq_name)
command and the name of the TSQ contained fewer than eight
characters, a QIDERR(eibresp44) queue not found error was
received even though the queue existed.

PROBLEM CONCLUSION:
The queue was not found because the code that padded the field
used invalid characters. The code has been changed to pad with
spaces, and the problem has been corrected.

------

APAR: IY18477  COMPID: 5765E2820  REL: 430
ABSTRACT: TXSERIES FOR AIX LINE COMMAND CICSTFMT RECEIVES ERZ086002E

PROBLEM DESCRIPTION:
At the TXSeries CICS for AIX PTF4 level issuing line command
cicstfmt receives message ERZ086002E/0061: No formatting has
been performed. Errors were detected during translation of the
template file '/usr/lpp/cics/etc/cicstrcfmt'.

PROBLEM SUMMARY:
USERS AFFECTED: CICS users, Release 430
After PTF 4 was applied, the cicstfmt command used to format
traces did not work.

PROBLEM CONCLUSION:
The code for the trace-formatting logic has been corrected, and
the cicstfmt command works properly.
KEYWORDS: PTF5 CICS 4.3.0.5, defect # 203461

------

APAR: IY18563  COMPID: 5765D1400  REL: 220
ABSTRACT: CDS PERFORMANCE PROBLEM WHEN THE MASTER CLH IS DOWN

PROBLEM DESCRIPTION:
A significant performance degradation in CDS
lookups when the master cds server is down.

LOCAL FIX:
Changes were made to  CACleSetOk() function in
src/directory/cds/cache/cacle.c and in
src/directory/cds/library/cds_check_ch.c for GDA.

------

APAR: IY18565  COMPID: 5765D1400  REL: 220
ABSTRACT: DCECRED_XXXXXXXX.DATA.DB FILE CURRUPTED, DFSBIND DUMPS CORE

PROBLEM DESCRIPTION:
IBM Rochester is seeing a problem where dfsbind core
dumps due to a corrupted dcecred_XXXXXXXX.data.db file.

LOCAL FIX:
To open and lock the .data.db file, we call dce_db_open_file(),
passing in the database filename and flags indicating how the
file should be locked. dce_db_open_file() calls dbopen() to
open the database and then dce__db_lock_file() to lock it. That
looks fine on first glance. But looking more closely at
dbopen(), we see that not only does it open the file, it also
reads data out of the file. This is a Bad Thing. The file
should be locked immediately after the open(), and before any
reads or writes.
So, the fix is to move the lock from dce_db_open_file() down
into the lower level open routines (__bt_open(), __hash_open()
and __rec_open()), immediately after they do the open(). To do
this, dbopen() and __{bt,rec,hash}_open() had to be modified to
pass in the flags argument that had the lock flags. And a
slightly different interface to dce__db_lock_file() had to be
written that takes the file descriptor instead of the database
handle as an argument (the database handle is not constructed
until after the call to dbopen()).

PROBLEM SUMMARY:
One of the credential files (dcecred_NNNNNNNN.data.db)
associated with a users login context can become corrupted.
This can cause any DCE process that tries to access that
file to dump core. These may include klist, kinit,
cdsclerk, dfsbind and others.

PROBLEM CONCLUSION:
Fixed the file locking logic so that the file is always
locked immediately after it is opened, and before it is
read.

------

APAR: IY18586  COMPID: 5765E2820  REL: 430
ABSTRACT: CEDF ON CICS V4303 HANGS UP ON JAPANESE REGION

PROBLEM DESCRIPTION:
After application of PTF3, message ERZ019009E is issued if an
attempt is made to use CEDF when the terminal to be debugged
is in Ja_JP.
In cics system trace,
TerBM_Just() returns 2 as
 I<  TerBM_Just                     return(0, RSN_2)
and TerBM_CreateField() return non-zero as
 E<  TerBM_CreateField              return(17, RSN_5)
then ERZ019009E was detected,
    E>  DamTD_ErrorSafeWrite          (CSMT, ERZ019009E/0020

LOCAL FIX:
use En_US region instead of Ja_JP

PROBLEM SUMMARY:
USERS AFFECTED: CICS users, Release 430
After PTF 3 was applied, the CEDF debugger did not work if the
terminal being debugged was associated with the locale ja_J
(Japanese). The error ERZ019009E Display could not be created
resulted.

PROBLEM CONCLUSION:
The problem was caused by insufficient allocation of space for
the message conversions, which prevented the conversion of SOSI
characters. The message conversion for the Japanese locale has
been changed to provide for the proper function of SOSI
characters.

------

APAR: IY18812  COMPID: 5765D6600  REL: 201
ABSTRACT: CUMULATIVE MAINT #03 FOR MQSERIES INTEGRATOR FOR AIX V201

PROBLEM DESCRIPTION:
CUMULATIVE MAINT #03 FOR MQSERIES INTEGRATOR FOR AIX V201

PROBLEM SUMMARY:
Cumulative Maintenance #3

PROBLEM CONCLUSION:
This is the third PTF for IBM MQSeries Integrator Version 2.0.1
for AIX.  It is delivered via PTF U476289 for APAR IY18812.
It contains fixes for ALL the problems listed below:
Name      Abstract
IY18812 - CUMULATIVE MAINT #03 FOR MQSERIES INTEGRATOR FOR AIX V
IC28463 - LENGTH FUNCTION NOT WORKING IF THE ELEMENT ARRIVE WITH
IC29210 - MQSIMRMCOPYMSGSET CHANGES TWO ATTRIBUTES OF THE COPY I
IC29235 - SPURIOUS ESQL SYNTAX ERROR IN COMPUTE NODE WHEN SETTIN
IC29416 - COMPUTE NODE ADD MAPPING TO MRM LAYOUT GENERATES BAD E
IC29489 - DBCS MESSAGES WERE NOT CONVERT CORRECTLY FROM PC CODEP
IC29632 - MQSI - INCORRECT STRUCLENGTH AND NAMEVALUELENGTH IN RF
IC29775 - MQSI BROKER DO NOT PASS THE MQMD CONTEXT INFORMATION W
IC29801 - MQSI V2 FAILS TO RECONNECT AFTER ORACLE HAS BEEN BOUNC
IC29992 - IF DEFAULTHEX IN THE DB TABLE HAS 1000 BYTES OR MORE T
IC30011 - INCORRECT MESSAGES, WHICH ARE SENT TO THE FAILURE-TERM
IC30171 - REORDER OF ELEMENTS FOR A MESSAGE SET, WITHIN A COMPOU
IC30173 - MQINPUT CATCH TERMINAL DOES NOT COMMIT DATABASE LOCKS.
IC30195 - EG ABEND WHEN USING TWO MESSAGES OF THE SAME STRUCTURE
IC30424 - AFTER APPLIED CSD2, THE MESSAGE BROKER INTERNAL PROBLE
IC30497 - ERRORS OCCURRING DURING MQSI GUI CONNECTION TO ORACLE
IC30502 - OUTPUT TREE AFTER PARSING XML MESSAGE IS NOT CORRECT
IC30653 - WHEN YOU UNSET A PROMOTED PROPERTY, DEFAULT IS LOST
IC30673 - SQL SYNTAX CHECKER REPORTS ERROR ON VALID SYNTAX WHICH
IY14970 - DOCUMENTATION INCORRECT/NEEDS CHANGE ON COMPILERS SUPP
IY16379 - EXECUTION GROUP TERMINATES ON STARTUP WITH BIP2123
IY16679 - INADEQUATE ERROR MESSAGE PRODUCED FOR EXECUTION GROUP
IY16970 - DFE STOPS PROCESSING MESSAGES FOR A FLOW. INCOMING MES
IY17486 - COBOL STRUCTURES, CONTAINING SIGNED DECIMAL NUMBERS (P
IY17561 - RULES NODE NOT PROCESSING A MQS EXPIRY NO PROPAGATE FI
IY17772 - AFTER UPGRADE MQSI VERSION F/V1.1 T/V2.0.1, MQSI BROKE
IY17780 - DFE NOT STARTING PROCESSING OF MESSAGES ON THE INPUT Q
IY17806 - WHEN BROKER HAS LONG CONNECTION TO DATABASE, SOMETIMES
IY17808 - XML PARSER ADD TRUE TO THE END OF XML DECLARATION.
IY18104 - CAST FUNCTION INTERMITTENTLY FAILING
IY18146 - IF THE BROKERDB IS ORACLE, ADDITIONAL NLSPATH IS REQUI
IY18245 - PERFORMANCE FIX TO ADDRESS INEFFICENCY IN BIT STREAM F
IY18458 - ERROR PUT TO DLQ BY THROW NODE IS UNREADABLE - 4048 ER
IY19242 - LOCAL_TIMEZONE ESQL IS RETURN 239/241 INSTEAD OF 240 A
IY19382 - DATAFLOWENGINE LOOP
IY21179 - DFE COSUMING HIGH CPU AND HANGING WITH NO ERRORS
IY22261 - BROKER IN AIX SMP ENVIRONMENT MEMORY MANAGEMENT VULNER
14500   - Over optimization in MTI refresh bitstream method
15071   - Can't put more than 999 bytes of data into an Oracle c
15130   - SIGBUS on SQLExtendedFetch within Compute node
15634   - MQInput catch terminal does not commit database locks
15937   - Error msg from date/time columns in Oracle on Solaris
16516   - PMR: AdminAgent Recovery is compromised
16520   - Cannot insert more than 4000 bytes into Oracle CLOB
16675   - getControlType() missing logNamedExitData
16843   - Whitespace between XML tags is corrupted on AIX
17052   - STRESS: Subscriptions expire immediately during BST
17169   - XML parser: insets TRUE string in parsed block
17763   - CCI_SQL_TRANSACTION_COMMIT ignored
17764   - ImbDecimal needs to support ".xyz" numbers
17994   - XML Parser does not correctly process empty elements
18496   - DFE process seems to be dying after
20216   - Exception thrown creating EG on a migration broker

------

APAR: IY18984  COMPID: 5765E6400  REL: 220
ABSTRACT: HAGEO: NETWORK_DOWN RESULTS IN CLSTOP OF ONLY NODE UP IN CLUSTER

PROBLEM DESCRIPTION:
Customer experienced two situation in which the non-dominant
site went down due to network_down event with HAGEO running
on HAES.  If bringing up the non-dominant site first and when
issuing halt -q on primary site node, a network_down event
following the node_up or node_down takeover, the
geo_network_down brought the node down through geo_node_down.

PROBLEM SUMMARY:
Customer experienced two situation in which the non-dominant
site went down due to network_down event with HAGEO running
on HAES. If bringing up the non-dominant site first and when
issuing halt -q on primary site node, a network_down event
following the node_up or node_down takeover, the
geo_network_down brought the node down through geo_node_down.
These network events were for non-geo networks and should not
have resulted in an actions by hageo.

PROBLEM CONCLUSION:
Add a test in the network_ scripts to check for a geo network.

------

APAR: IY19242  COMPID: 5765D6600  REL: 201
ABSTRACT: LOCAL_TIMEZONE ESQL IS RETURN 239/241 INSTEAD OF 240 ABOUT 50% O

PROBLEM DESCRIPTION:
When ESQL is used to get the Local Timezone, similar to the
following:
SET OutputRoot.XML.timezonediff = CAST(LOCAL_TIMEZONE AS
CHARACTER);
The value returned by LOCAL_TIMEZONE is incorrect.  In this
case the value to be returned is 240 and the value being
returned is 239/241.

PROBLEM SUMMARY:
The timezoneDisplacement (difference between localtime and GMT)
was occasionally 1 minute out because of rounding errors in the
calculation of seconds since 01/01/1970 00:00.

PROBLEM CONCLUSION:
ImbTimeStamp::timezoneDisplacement has been changed to do the
calculation as an integer division.

------

APAR: IY19304  COMPID: 5765E2920  REL: 430
ABSTRACT: MSGERZ004052E USING CICS PRE-COMPILER ON COBOL PROGRAM ON SUN

PROBLEM DESCRIPTION:
   Compiling a Cobol program on Sun Solaris 2.8, using CICS
V4.3, we get ERZ004052E / 2601 "xxxxx Command or DHF macro too
long". The particular commands generating this error are a MOVE
DFHRESP(DUPKEY) TO WP-CICS-ERROR-HANDLE(2). Yet the same command
on other lines within the program do not generate this error.
Further, the same program successfully compiles under AIX and
NT.
   Change Team reproduced the error and determined that this was
a different problem from internal defect 202774, which reports
an error from the NL_TEXTMAX limit of 2084 on Solaris, related
to ExecCommandBuffer. This problem is also from the NL_TEXTMAX
limit, but related to MacroBuffer. Defect 203472 has been raised
for this problem.

PROBLEM SUMMARY:
USERS AFFECTED: CICS users, Release 430
When the cicstran command was used on a Solaris system to
translate a very large COBOL program, the error
ERZ004052E/2601:  42006 Command or DFH macro too long was
received. If the size of the program was reduced, the error did
not occur.

PROBLEM CONCLUSION:
The code was changed to reset the MacroBufIndex counter, and
the problem has been resolved.

------

APAR: IY19382  COMPID: 5765D6600  REL: 201
ABSTRACT: DATAFLOWENGINE LOOP

PROBLEM DESCRIPTION:
DataFlowEngine loop.

PROBLEM SUMMARY:
Problem when performing a complete deploy, processing some MRM
messages and then redeploying.  On AIX the the DFE consumes 100%
of the cpu, on NT the DFE crashes with memory violation errors.

PROBLEM CONCLUSION:
There is an error in the CMGarbageCollect function which cleans
up the hashtables.  This problem has now been resolved.

------

APAR: IY19498  COMPID: 5765E2820  REL: 430
ABSTRACT: ABENDA28D

PROBLEM DESCRIPTION:
ERZ028015E/0814 with abend A28D when upgrade to client 3.1.2
if message length is greater than 5120.
Problem is due to a difference in the limitation of the
MaxTIOALength between TXSeries CICS and CICS Universal Client.
Defect 203456.

LOCAL FIX:
Do not send message greater than 5120 bytes.

PROBLEM SUMMARY:
USERS AFFECTED: CICS users, Release 430
After upgrading the CICS Universal Client to the 3.1.2 level, a
customer received the error message ERZ0280215E Incorrectly
formatted.

PROBLEM CONCLUSION:
The problem occurred because the new version of the client has
a larger buffer size for the terminal input/output area (TIOA)
than the earlier version had. The internal buffer area for the
TIOA has been increased from 5120 to 12288, and the problem has
been corrected.

------

APAR: IY19598  COMPID: 5765D1400  REL: 220
ABSTRACT: CAN'T FTS LSFLDB ON DETACHED AGGREGATES

PROBLEM DESCRIPTION:
The User can't list the filesets on a
Detached Aggregate by using the fts
lsfldb command.

PROBLEM SUMMARY:
The user can't list the filesets that are there on
a detached aggregate.

PROBLEM CONCLUSION:
we have modified the code, so that the user can
list the filesets that are there on a detached aggregate
by using aggrgate id only.

------

APAR: IY20203  COMPID: 5765E2820  REL: 430
ABSTRACT: MISSING PERIOD FROM CICSTRAN OUTPUT AT EMPTY SPECIAL-NAMES.

PROBLEM DESCRIPTION:
Period was missing when CICS COBOL has empty  SPECIAL-NAMES.
For example, if following CICS COBOL code is used for cicstran
input file,
     IDENTIFICATION DIVISION.
     PROGRAM-ID. JACKM.
     ENVIRONMENT DIVISION.
     SPECIAL-NAMES.
     PROCEDURE DIVISION.
cicstran will generate COBOL code like this.
        IDENTIFICATION DIVISION.
        PROGRAM-ID. JACKM.
        ENVIRONMENT DIVISION.
        SPECIAL-NAMES.
          call-convention 8 is litlink
        DATA DIVISION.
In here, period was missing after litlink.
cicstran was expecting actual SPECIAL-NAMES paragraph, but if it
was omitted then, it just went to the next token(DATA DIVISION).
To compare with normal case, if the source code was written like
        IDENTIFICATION DIVISION.
        PROGRAM-ID. JACKM.
        ENVIRONMENT DIVISION.
        SPECIAL-NAMES.
          CALL-CONVENTION 77 is BORLAND.
        PROCEDURE DIVISION.
Then, generated COBOL file from cicstran would be
        IDENTIFICATION DIVISION.
        PROGRAM-ID. JACKM.
        ENVIRONMENT DIVISION.
        SPECIAL-NAMES.
          call-convention 8 is litlink
One major problem in fix cicstran code was, cicstran is simple
string substitutor, and that process cannot do any back tracking
.  Which means, at the time of hitting DATA DIVISION, and even
if it recognized that actual SPECIAL-NAMES is omitted,it can
not get back to the previous step.

PROBLEM SUMMARY:
USERS AFFECTED: CICS users, Release 430
When the special names paragraph of a COBOL program did not
contain a user-coded statement, the cicstran command did not
generate a period (.) on the statement it adds. The statement
added without a period, call-convention 8 is litlink, then
caused an errorin the compiler.

PROBLEM CONCLUSION:
The cicstran command has been changed to recognize an empty
Special Names paragraph, and it now generates a period on the
statement added. This prevents the compiler error.

------

APAR: IY20211  COMPID: 5765D1700  REL: 220
ABSTRACT: DFSBIND MEMORY LEAK PROBLEM

PROBLEM DESCRIPTION:
dfsbind leaks memory and core dumps when it hits
the process limits.

PROBLEM SUMMARY:
dfsbind leaks memory and could result in
core dumps when process ulimits are hit.

PROBLEM CONCLUSION:
code is modified to free the appropriate cred
structures after the use.

------

APAR: IY20225  COMPID: 5765D1500  REL: 220
ABSTRACT: START.DFS MISTAKENLY REPORTS SERVER NOT STARTING

PROBLEM DESCRIPTION:
start.dfs incorrectly reports dfs server not starting
this is caused by dfsbind misinterpreting a message
printed by dfsbind when RPC_RESTRICTED_PORTS is set

PROBLEM SUMMARY:
If RPC_RESTRICTED_PORTS environment variable defined
then start.dfs script states that "Unable to start DFS
File server"

PROBLEM CONCLUSION:
Changed the way tcl scripts are interpreting the
KRPC_RESTRICTED_PORTS Message as it is not at all
harmfull message.

------

APAR: IY20226  COMPID: 5765D1500  REL: 220
ABSTRACT: CFGDMEPI FAILS TO LOAD DMLFS.EXT

PROBLEM DESCRIPTION:
cfgdmepi fails to load dmlfs.ext

PROBLEM SUMMARY:
Attempts to load dmlfs kernel extension using cfgdmepi
binary used to fail. This problem was caused by an
uninitialized variable(cload.libpath) being passed
to SYSCONFIG function.

PROBLEM CONCLUSION:
Added code to initialize the cload.libpath varible.

------

APAR: IY20228  COMPID: 5765D1500  REL: 220
ABSTRACT: MACHINE PANICS WHEN DCE_LOGIN_NOEXEC FOLLOWED BY KDESTROY

PROBLEM DESCRIPTION:
Machine panics when dce_login_noexec followed by kdestroy
command is issued

LOCAL FIX:
dce_login_noexec should be avoided when DFS is running
(as specified in the DCE documentation)

PROBLEM SUMMARY:
When running dce_login_noexec followed by kdestroy,
machine will panic due to DFS trying to release a
mutex of which it is not a owner.

PROBLEM CONCLUSION:
In order to avoid calls to recursive mutex,
osi_MakePreemptionRight() and osi_UnmakePreemptionRight()
function calls have been inserted before and after calling
the function checkPagCredFile(inpag).

------

APAR: IY20291  COMPID: 5765D1700  REL: 220
ABSTRACT: UUID HASH ERRORS IN ERROR.LOG WHEN USING AUDIT

PROBLEM DESCRIPTION:
When using audit, the following may appear in the error.log:
2001-01-02-12:40:43.100-05:00I----- cdsd(6808) ERROR aud esl
esl_in_core.c 896 0x00001112 msgID=0x10323064 Cannot get the
hash value of the subject uuid: uuid_to_string_failed ;
status:  -Aš (B, -A  (BH0K{

PROBLEM SUMMARY:
The following will occur in the error.log:
2000-12-18-11:26:16.186-05:00I----- cdsd(19030) ERROR aud
esl esl_in_core.c 896 0x00000f10 msgID=0x10323064 Cannot
get the hash value of the subject uuid:
uuid_to_string_failed ; status:

PROBLEM CONCLUSION:
In dce_aud_start, make sure the empty_pac has been
completely initialized (0'ed out), to ensure no garbage
exists in the uuid fields.
Also in aud_esl_entry_lookup, make sure the error_string
has been set before printing out error messages.

------

APAR: IY20991  COMPID: 5765E2920  REL: 430
ABSTRACT: CSTD TERMINAL STATISTICS ABEND ASRA WITH GREATER THAN 4000 TERMI

PROBLEM DESCRIPTION:
TXSeries 4.3.0.4 for Solaris - Software lab electronic APAR for
defect 203510
See Problem Description / Problem Solution for a complete
description when this APAR is closed.

PROBLEM SUMMARY:
USERS AFFECTED: CICS users, Release 430
After PTF 4 was applied on Solaris and Windows NT systems,
running the CSTD transaction and selecting option 7 caused an
ASRA abend.  The problem resulted from a defect that was added
for AIX at PTF 4, which inadvertently changed the internal
table processing for Windows NT and Solaris systems.

PROBLEM CONCLUSION:
The internal table processing has been corrected, and the ASRA
abend no longer occurs.

------

APAR: IY21179  COMPID: 5765D6600  REL: 201
ABSTRACT: DFE CONSUMING HIGH CPU AND HANGING WITH NO ERRORS

PROBLEM DESCRIPTION:
Customer is using flows provided by MQSFSE V1.0 and is having
problem with the reply message appears getting stuck in a
flow called HUBOUT. DFE appears to cosume high CPU, no errors
generated. Message did enter the HUBOUT flow, and appears stuck
in there, as no output message was generated even after waiting
for one hour. HUBOUT flow contains a lot of subflows and also
includes a number of iterations of the message flows.
Change team were able to recreate the problem and got a coredump

PROBLEM SUMMARY:
A message flow that processed a message successfully on NT
failed to complete on AIX.  This was due to a stack overflow
problem on AIX.  On Unix platforms, MQSI overrides the default
thread stack size and allocates a stack size of 1MB to each
thread.  On NT, MQSI does not override the default thread stack
which is sufficiently high at 2MB.

PROBLEM CONCLUSION:
This problem has been fixed by allowing the default thread
stack size of 1MB on Unix platforms to be overridden by use of a
new environment variable:- MQSI_THREAD_STACK_SIZE
The stack size should be specified in bytes, so to set the
thread stack size to 2MB for example, set the following in the
environment from which the Broker will be started:
    MQSI_THREAD_STACK_SIZE=2000000
    export MQSI_THREAD_STACK_SIZE
This environment variable is only applicable on the Unix
platforms.

------

APAR: IY21697  COMPID: 5765E2920  REL: 430
ABSTRACT: CICS FOR SOLARIS : CICS REGION HANG WITH LONG RUNNING CCIN AND

PROBLEM DESCRIPTION:
ERZ034114E and ERZ042043I are received for the CD entry when
a client is terminated while running a long running
conversational XA transaction.  Because the transaction is long
running the terminal and client can not be cleaned up.  If
another client attempts to use the same termid/netname it too
attempts cleanup of the same client.
Defect 203533.

PROBLEM SUMMARY:
USERS AFFECTED: CICS users, Release 430
When a client was terminated after a long conversational XA
transaction and the user tried to start the client again with
the same netname (terminal ID), a number of errors resulted.
The message ERZ03411E Unsuccessful uninstall, entry marked as
in use was displayed in the console. The messages ERZ042043I
Waiting for task to finish, ERZ042009E Unable to install
terminal, and ERZ042016E Terminal is already installed were
received in the CSMT. If the user kept attempting to use the
same netname (terminal ID), all of the cicsas processes became
suspended while attempting to clean up the same client.  The
problem was found in the code used to check the system ID of
the terminal from the CTIN transaction. In response to a ping
function, another CCIN uninstall request was issued. This
blocked another application server process because one CCIN was
already running for the terminal ID. The spiral continued until
all application server processes were blocked.

PROBLEM CONCLUSION:
The code has been changed to recognize the same terminalID
(netname) and does not do the ping under these circumstances.
Because the ping is not issued, the application server process
is not blocked, and the problem does not occur.

------

APAR: IY22081  COMPID: 5765E6110  REL: 220
ABSTRACT: TOPOLOGY SERVICES DAEMON ATTEMPTING TO USE ALL CPU CYCLES

PROBLEM DESCRIPTION:
Topology Services daemon attempting to use all CPU cycles
available.  topsvcs dies on node after starting.

PROBLEM SUMMARY:
The RSCT Topology Services daemon may exit under
some circumstances, due to excessive CPU use.
In some scenarios, the select() system call invoked
by one of the threads fails, and this causes the
thread to retry the operation immediately. Since
the system call fails repeatedly, the daemon
starts using too much CPU. A "watchdog" thread
in the daemon will detect the excessive CPU
use and will terminate the process to prevent other
processes in the system from being starved.

PROBLEM CONCLUSION:
The problem was fixed by introducing a time
delay every time the select() system call
fails.
With the fix, the daemon should no longer
exit due to excessive CPU consumption when the
select() system call fails.

------

APAR: IY22136  COMPID: 5765E6110  REL: 220
ABSTRACT: LIBNETMON:SIOCADDRT IOCTL() TO ADD ROUTES FAILS

PROBLEM DESCRIPTION:
libnetmon:siocaddrt ioctl() to add routes fails

PROBLEM SUMMARY:
A change in AIX has resulted in modifications to the
way network routing is implemented. With the change,
a host route table entry is created for each local
adapter interface. The entry has the adapter's address as
destination and the "loopback" address (127.0.0.1)
as gateway. When running command
   netstat -rn
lines like the following will appear in the command's
output:
9.114.149.65     127.0.0.1         UGH       0    29266  lo0
These route entries create a problem for RSCT
Topology Services when in the HACMP/ES environment,
since this component needs to add and remove routes
dynamically. Such route manipulations are needed
when sending an "echo" message from a (say) standby
adapter to a service adapter located in the same
HACMP network, which is used to determine the adapter's
liveness. The route added by AIX creates a conflict
with the route to be added by Topology Services,
resulting in the latter not being accepted by AIX.
The following may be seen in the "netmon" log files,
located at
/var/ha/run/topsvcs.<cluster name>/nmDiagFile.<interface>
(RSCT prior to version 1.2.1)
or at
/var/ha/log/nmDiag.nim.topsvcs.<interface>.<cluster name>
(remaining releases):
nmRouteAddHost:SIOCADDRT ioctl() failed, errno is 17.
This may result in HACMP/ES falsely reporting adapters as
dead, which will cause unnecessary (and possibly repeated)
"adapter swap" events.

PROBLEM CONCLUSION:
The fix in Topology Services accounts for the
possibility that the loopback routes are present.
If an error is encountered while adding the
temporary route, Topology Services will first
retrieve information about the current route,
remove it, then add the temporary route. After
the packet is sent to the destination adapter, the
temporary route is removed and the original route
is restored.
With the fix, no false adapter downs or spurious
adapter swap events should occur in HACMP.

------

APAR: IY22261  COMPID: 5765D6600  REL: 201
ABSTRACT: BROKER IN AIX SMP ENVIRONMENT MEMORY MANAGEMENT VULNERABLE TO FR

PROBLEM DESCRIPTION:
On AIX, the 'multiheap' heap manager used in SMP environments is
vulnerable to fragmentation with large numbers of small
allocations of varying size.  MQSI does large numbers of
allocations by using of the underlying String Class from
the C++ Standard Template Library.
In some cases, the combination of allocations and frees could
result in fragmentation of heap.

PROBLEM SUMMARY:
On AIX the 'multiheap' heap manager used in SMP environments is
vulnerable to fragmentation with large numbers of small
allocations of varying size.  MQSI does large numbers of
allocations by using the underlying String Class from the C++
Standard Template Library.  This combination of allocations and
frees has resulted in fragmentation of the heap.

PROBLEM CONCLUSION:
This problem has been resolved by using the AIX multiheap
management model with a number of buckets reserved for these
small allocations.

------

APAR: IY22280  COMPID: 5765D2800  REL: 430
ABSTRACT: HAES HARC.NET: .HWUNDO SET INCORRECTLY

PROBLEM DESCRIPTION:
.hwundo file is created in the HACMP/ES directory
/usr/es/sbin/cluster.
However, .hwundo in /usr/es/sbin/cluster/etc/harc.net
is hardcoded: /usr/sbin/cluster/.hwundo

LOCAL FIX:
Change path to .hwundo in harc.net.

PROBLEM CONCLUSION:
Change path based on installed product.

------

APAR: IY22281  COMPID: 5765D2800  REL: 430
ABSTRACT: CL_UNSWAP_HW_ADDRESS ACCEPTS ADAPTER NAMES WITH 1 DIGIT ONLY

PROBLEM DESCRIPTION:
When an interface name has more than one digit, i.e. en10,
the swap of MAC address does not work. This APAR is a
follow up to IY05421 and IY12409.

LOCAL FIX:
efix available

PROBLEM CONCLUSION:
Correct regular expression.

------

APAR: IY22382  COMPID: 5765E2820  REL: 430
ABSTRACT: CUC DISCONNECT/RECONNECT AFTER PING.

PROBLEM DESCRIPTION:
The symptom exhibited in the problem is the Universal Client
disconnects and then reconnects after another terminal tries to
connect to the region with the same netname.
The  ReceiveThread for connection @P4C (thread 26) when it goes
back in ComIP_SocketReadMsg at 16:15:23.  It DOES NOT call
ComSU_XPGetBuf.  This means that InternalFailure (one of the
flags) must already be set to TRUE from a previous pass through
the loop.  After this point, the result is a foregone conclusion
:  CICS waits until the client sends a CDI and immediately fires
back an FMH7. It appears that our processing of a connection
level ping response is faulty. This means that we wind up trying
to send the echo over to a cicsas.  In this case, this attempt
fails (because we haven't set any options when we make a call to
ComSU_XPSend) and that causes us to set InternalFailure to TRUE.
What we should do is add an 'else if (ConnPingReply)' clause to
the end of the larger if statement that deals with the various
ping cases and basically just 'continue' to go back round the
loop waiting for more client input.  There may be some resetting
of state required as well.

PROBLEM SUMMARY:
USERS AFFECTED: CICS users, Release 430
The CICS Universal Client disconnected and reconnected after
another terminal tried to connect to the region with the same
netname.

PROBLEM CONCLUSION:
The problem was caused by an incorrect setting of an internal
error flag during the ping process. This incorrect setting
caused an internal error response to the client, which caused
the client to disconnect. The flag is now set correctly, and
the client no longer disconnects.

------

APAR: IY22408  COMPID: 5765E2820  REL: 430
ABSTRACT: MSGERZ057002 ABENDA57A ON AN EXEC CICS RECEIVE MAP

PROBLEM DESCRIPTION:
On an EXEC CICS RECEIVE MAP an ABENDA57A and the following
message were received:
msgERZ057002E / 0012 CICS internal error: Unsuccessful condition
'DataLength < TERBM_BUFFER_LENGTH' for function  'TerBM_Just' on
line 277 in file '/cics/PTF3/src/ter/bm/src/terbm_just.c' of
+module 62
Addition search Words:
ERZ057002E/0012 msgERZ057002E/0012 abenduA57A

PROBLEM SUMMARY:
USERS AFFECTED: CICS users, Release 430
An abend 57A occurred when a CICS RECEIVE MAP command was
executed. The abend was accompanied by the message
ERZ05002e/0012 cics internal error (assert) data length is less
than TerBM_Buffer length.

PROBLEM CONCLUSION:
It was determined that the internal setting for the buffer
length was too small to handle a large buffer. The buffer is
now set to the largest known screen image, which is 27 lines by
132 characters, with allowances for double-byte character
languages.

------

APAR: IY22428  COMPID: 5765E6400  REL: 220
ABSTRACT: GEO_PRESTART_GMDS DOES NOT USE CORRECT CLINFO SRC WITH HAES

PROBLEM DESCRIPTION:
When running HAES clinfo is known as "clinfoES"
to the srcmstr, however Geo_prestart_gmds attempts
to start or refresh "clinfo".

PROBLEM CONCLUSION:
Start clinfo or clinfoES based on HACMP product.

------

APAR: IY22483  COMPID: 5765D2800  REL: 431
ABSTRACT: CLDARE RETURNS FAILURE TO MIGRATE RESOURCE GROUP BUT RESOURCE

PROBLEM DESCRIPTION:
The customer issued the command through the smit panels to
move a cascading resource group from one node to the other.
The resource move function within smit indicated failure
with the clfindres showing ??? for the State of the resource
group, but later issuance of the clfindres command and log
files all indicated the resource move was successful.

PROBLEM SUMMARY:
The customer issued the command through the smit panels to
move a cascading resource group from one node to the other.
The resource move function within smit indicated failure
with the clfindres showing ica tmp for the State of the
resource group, but later issuance of the clfindres command
and log files all indicated the resource move was successful.

PROBLEM CONCLUSION:
Since not all nodes finish the cldare processing at the same
time, node taking resources will generally take longer, the
clfindres command was adding into the waiting loop with a
check for good return code from the command before
considering the command complete.  In this way, the final
clfindres should be successful unless there truly is an
error not detected by the local node.

------

APAR: IY22532  COMPID: 5765D2800  REL: 430
ABSTRACT: CLLOGSPACE FAILS IF LANGUAGE ENVIRONMENT IF DIFFERENT THAN C

PROBLEM DESCRIPTION:
When LANG is set to a different language than C,
cllogspace reports "-1 K disk space left on filesystem"
for all the associated filesystems.

PROBLEM CONCLUSION:
set LANG=C in cllogspace script.

------

APAR: IY22710  COMPID: 5765E2820  REL: 430
ABSTRACT: ERZ046002E - WHEN CREATING A CICS REGION

PROBLEM DESCRIPTION:
TXSeries 4.2 - CICS
When creating a new CICS region with the command:
  CICSEXPORT -r'BPMSTAR' -o'tempreg'
msg ERZ046002E - unable to access region '.GNT
is received.
It only works if the command is as follow:
  CICSEXPORT -r'BPMSTAR' -o'tempreg' -1'bin'
The transarc defect is 201730.

PROBLEM SUMMARY:
USERS AFFECTED: CICS users, Release 430
When the cicsexport command was run against a region with a
symbolic link that was not resolved, the system displayed the
message ERZ046002E Unable to access region. This message was
misleading because the problem was with the link, not the
region.

PROBLEM CONCLUSION:
The error message has been changed to say that a link points to
a file that does not exist in the region. When the error
occurs, the user can now resolve the link and rerun the export
command.

------

APAR: IY22879  COMPID: 5765D2800  REL: 431
ABSTRACT: ATTEMPT TO START CLUSTER HANGS IN CLSTART - HAES

PROBLEM DESCRIPTION:
When attempting to start the cluster in HAES 4.4, the startup
hung in clstart.  It was hanging on a grep for clstop and
a tail -1.

PROBLEM SUMMARY:
When attempting to start the cluster in HAES 4.4, the startup
hung in clstart. It was hanging on a grep for clstop and
a tail -1.

PROBLEM CONCLUSION:
The problem was in code which attempts to find a timestamp
of the last stop of the cluster.  Two problems existed:
1. If the cluster.log entry in /etc/syslog.conf was missing
it still continued with trying to grep a null filename
causing the hang. 2. It was grepping for clstop in the
cluster.log file, which does not exist.  Code was changed
to check to be sure a file location was returned before
attempting the grep and the grep was changed to look for
"EVENT COMPLETED: node_down_complete".

------

APAR: IY23100  COMPID: 5765D2800  REL: 430
ABSTRACT: SYNCHRONIZING CLUSTER TOPOLOGY SHOULD NOT MAKE THE HANDLE

PROBLEM DESCRIPTION:
When upgrade from HAS 4.2.2 to HAS 4.3.1 each node will have a
unique handle but if you synchronize topology they will all be
equal.

PROBLEM SUMMARY:
Migration to HAES will not complete and topology services will
loop with the following error message,
errorCb: Sredrive already scheduled, return

PROBLEM CONCLUSION:
Make the HACMPcluster ODM handle value unique when cluster
topology is synchronized.

------

APAR: IY23187  COMPID: 5765D2800  REL: 431
ABSTRACT: ONLY ONE SWAP_ADAPTER WHEN TWO SERVICE ADAPTERS FAIL - HAES

PROBLEM DESCRIPTION:
The customer was using 4-port ethernet adapters and was testing
what would happen if one of these adapter cards failed
completely.  With 2 service adapters, one for each of two
different networks, configured on the same 4-port adapter, the
customer pulled both service cables and only one swap_adapter
event occurred followed by its fail_standby event.  No event
occurred for the second network.

PROBLEM SUMMARY:
The customer was using 4-port ethernet adapters and was testing
what would happen if one of these adapter cards failed
completely. With 2 service adapters, one for each of two
different networks, configured on the same 4-port adapter, the
customer pulled both service cables and only one swap_adapter
event occurred followed by its fail_standby event. No event
occurred for the second network.

PROBLEM CONCLUSION:
The problem was that the second swap_adapter event on the
queue was being found to be the same one that had just
completed, because there was no test for the network being
the same.  This was corrected in the evque.C routine.

------

APAR: IY23233  COMPID: 5765D2800  REL: 430
ABSTRACT: AUTO ERROR NOTIFICATION FAILS W/ C-10 SCSI0 ADAPTER

PROBLEM DESCRIPTION:
Automoatic Error Notification fails with a
C-10 scsi0 adapter (unknown parent).

PROBLEM CONCLUSION:
Added adapter type 8fba in AdapterConfig.c

------

APAR: IY23234  COMPID: 5765D2800  REL: 430
ABSTRACT: VERIFYING CLUSTER SECURITY WILL FAIL IF NODE NAME IS NOT EQUAL

PROBLEM DESCRIPTION:
When cluster has enhanced security clverify will fail in the
Verifying Cluster Security section if the node name is not
equal to an interface name.

PROBLEM SUMMARY:
The error below is received when doing Cluster Verification.
Verifying Cluster Security
host: name Node_b2 NOT FOUND
ERROR: Could not open file /tmp/caaqfmQMc

PROBLEM CONCLUSION:
Use address returned by get_addrs instead of cluster node name.

------

APAR: IY23235  COMPID: 5765D2800  REL: 430
ABSTRACT: AUTO ERROR NOTIFY METHODS NOT CREATED FOR SINGLE POINTS OF FAIL

PROBLEM DESCRIPTION:
No errnotify entries created for scsi adapters  that connect
to the Shark and have no virtual device as parent.

PROBLEM CONCLUSION:
current implementation assumes the existence of a virtual
device *scsi. In fct GetDPOAdapters add logic that accounts
for scsi adapters that do not have a virtual device as parent.

------

APAR: IY23236  COMPID: 5765D2800  REL: 430
ABSTRACT: IMPROPER MESSAGE LOGGED TO CLUSTER.LOG

PROBLEM DESCRIPTION:
The message "syslog PID : Failed operation(1) return status 9."
may be logged to cluster.log, even though no failures have
occurred.  This message should not be logged under normal
circumstances.

PROBLEM SUMMARY:
The message "syslog PID : Failed operation(1) return status 9."
may be logged to cluster.log, even though no failures have
occurred. This message should not be logged under normal
circumstances.

PROBLEM CONCLUSION:
The error will no longer be logged during normal operations.

------

APAR: IY23237  COMPID: 5765D2800  REL: 430
ABSTRACT: HAES: USER IS NOT NOTIFIED WHEN RG_MOVE FAILS

PROBLEM DESCRIPTION:
HAES 4.4.1 added funcitonality to recover from resource group
allocation failure (RGAF). When RGAF occurs, the cluster will
launch an rg_move event to move the RG to another node. If
there is no other node available for the RG, the RG will be
moved into the error state. The user receives no notification
of this error.

PROBLEM CONCLUSION:
rg_move_complete will be modified to exit with the value 3 if
a resource group is homeless after an rg_move event.  clevcall
will be modified to run the user's config_too_long notify
method if rg_move_complete exits with the value 3.

------

APAR: IY23240  COMPID: 5765D2800  REL: 430
ABSTRACT: CANNOT CHANGE LOCK MANAGER RESOURCE ALLOCATION PARAMETERS

PROBLEM DESCRIPTION:
Change/Show Cluster Lock Manager Resource Allocation returns
the following error message,
The cllockd Subsystem must exist to complete this command.

PROBLEM CONCLUSION:
Replace cllockd subsystem with cllockdES in clacdCLM script.

------

APAR: IY23291  COMPID: 5765E6400  REL: 220
ABSTRACT: SMIT CFG DBFS MANGLES USER INPUT, REPORTS NO ERROR

PROBLEM DESCRIPTION:
When smit is used to configure DBFS, the entries are mangled if
an apostrophe is entered. However, no warning is given that
the entry could not be properly read.

PROBLEM CONCLUSION:
Unfortunately it is diffucult to find a method of inputting an
apostrophe as this gets confused with a delimeter and as such
the input gets split.  The only real solution is to add an
entry into the release_notes file such that the user is made
aware of this problem and the possible solutions.

------

APAR: IY23365  COMPID: 5765E6400  REL: 220
ABSTRACT: UPDATE TO HAGEO2.2.README FILE

PROBLEM DESCRIPTION:
The HAGEO documentation is not entirely clear as to how
a filesystem should be set up on GEOmirror devices and
how an existing filesystem can be converted to a
GEOmirror'd filesysem.

PROBLEM CONCLUSION:
The HAGEO2.2.README needs to be updated with the correct
information.

------

APAR: IY23461  COMPID: 5765E2820  REL: 430
ABSTRACT: WEBSPHERE 4.3 CICS ON AIX 4.2.1 AND AIX 4.3.1 PTF5 REFERENCE

PROBLEM DESCRIPTION:
Websphere 4.3 CICS on AIX 4.2.1 and AIX 4.3.1 PTF5 reference
apar.
This apar should be used when ordering the latest Websphere
CICS maintenance on the AIX 4.2.1 and AIX 4.3.1 operating
systems.
The PTF associated with the reference apar contains fixes for
the following list of apars which were opened against
component id 5765E2820:
IY22710 IY06869 IY13475 IY11841 IY15663 IY17192 IY16830 IY19498
IY17814 IY18477 IY18586 IY19304 IY20203 IY17186 IY20991 IY21697
IY22382 IY22408

LOCAL FIX:
PTF 5 reference apar used for ordering.

PROBLEM SUMMARY:
USERS AFFECTED: CICS users, Release 430
PTF5 CICS 4.3.0.5 for AIX

PROBLEM CONCLUSION:
IY22710 IY06869 IY13475 IY11841 IY17192 IY16830 IY19498 IY17814
IY18477 IY18586 IY19304 IY20203 IY17186 IY20991 IY21697 IY22382
IY22408

------

APAR: IY23579  COMPID: 5765C3407  REL: 210
ABSTRACT: V2R1 PTF-13

PROBLEM SUMMARY:
Added filesets for AIX V2R1 NSM PTF 13

------

APAR: IY23588  COMPID: 5765B8100  REL: 220
ABSTRACT: RUNNING OUT OF BUFFERS FOR THE ISDN SIGNALING PROCESS.

PROBLEM DESCRIPTION:
Running out of buffers for the isdn signaling process.
Have to kill and restart the process

PROBLEM SUMMARY:
Running out of buffers for the isdn signaling
process. Have to kill and restart the process

PROBLEM CONCLUSION:
Fixed RLT protocol functions for dms100 and
dms250 a buffer leak was causing a system abend after approx
2 weeks. The buffer leak was tracked down to ISDNDL4 call
control, caused when caller hangs up before the transfer
completes. The buffer that was being held incorrectly
was freed.

------

APAR: IY23769  COMPID: 5765E6110  REL: 220
ABSTRACT: HAES: TOPSVCSD ASSARTED IN HB_NCT.C WHILE PROCESSING CORRUPTED

PROBLEM DESCRIPTION:
This problem had been found on HACMP/ES V4.2.2.
HAES had a mechanizum that filtered a corrupting packets from
other node. But in rare case, The corrupted packet was not disca
rded but passed to other functions. So there was a possibilty
that the function assarted while processing the packet.
 In our case, topsvcsd.log had following error message at that
time.
Assertion failed: amg_adapter_offset == adapter_offset,
file ../../../ ../../../../src/ssp/availability/pts/pam
/nct/Hb_nct.C, line 1248

PROBLEM SUMMARY:
It is possible for a hats packet to be corrupted in such a
way that it is not detected by the checksum.  In this case
the corrupted packet ended up causing an assert in hats,
which causes hats to die.

PROBLEM CONCLUSION:
A special check has been added to the code to detect this
specific corruption pattern, and act accordingly.

------

APAR: IY23770  COMPID: 5765E6110  REL: 220
ABSTRACT: PHOENIX.SNAP ENHANCEMENTS

PROBLEM DESCRIPTION:
phoenix.snap enhancements

PROBLEM SUMMARY:
phoenix.snap should be able to run in a non-SP environment
(HACMP/ES)

PROBLEM CONCLUSION:
phoenix.snap will now collect rsct data specifc to HAMP/ES
regardless of whether it is on an SP.

------

APAR: IY23771  COMPID: 5765E6110  REL: 220
ABSTRACT: KEEP 2-3 LOG FILES WITH HIGH PRIORITY

PROBLEM DESCRIPTION:
keep 2-3 log files with high priority

PROBLEM SUMMARY:
The problem is due to that the original method to assign
priorities to the log and core files was  designed
for keeping only one (highest priority) log file
in case there is no enough space.

PROBLEM CONCLUSION:
After we change the method to assign the priorities
it should keep at least 3 log files with highest
priorities and one recent core file together with the
corresponding log files.

------

APAR: IY23774  COMPID: 5765E6110  REL: 220
ABSTRACT: MISSING SUBSCRIPTION GROUP - ML0MEMBERSHIP

PROBLEM DESCRIPTION:
Missing subscription group - ml0Membership

PROBLEM SUMMARY:
The group ml0Membership group is missing
from the sample_test program. Thus the
users are having the difficult to test
the ml0Membership using the sample_test.

PROBLEM CONCLUSION:
This adds the ml0Membership group to the sample_test
so that the users can easily test the subscription
to the ml0Membership.

------

APAR: IY23775  COMPID: 5765E6110  REL: 220
ABSTRACT: TOO SHORT OF LOCALNAME FOR HA_GS_JOIN

PROBLEM DESCRIPTION:
too short of localname for ha_gs_join

PROBLEM SUMMARY:
An application uses ha_gs_join() to form a Group
Services group. Among the parameters, a field
gs_provider_local_name is limited to 16 bytes
unlike the other group names (limited to 32 bytes).
This max length is checked at ha_gs_join() and
returns an error code if it exceeds. This
different max values (and short length of local_name)
cause the confusion to the applications.
Furthermore, the gs_provider_local_name is used
only for the internal tracking.

PROBLEM CONCLUSION:
This fix will truncate the gs_provider_local_name
with 32bytes and prevent an error msg.

------

APAR: IY23776  COMPID: 5765E6110  REL: 220
ABSTRACT: YP BLOCKING NETMONADAPTERHEALTH

PROBLEM DESCRIPTION:
netmonAdapterHealth hungs causing a false down of an adapter
which leads to multiple failovers in an hacmpes environment
that using YP.

PROBLEM SUMMARY:
When running Network Information Service (NIS),
it has been noticed that calls to getprotobyname()
could block for 30 seconds or more. Since such
calls are issued by the netmonAdapterHealth
program -- which is used by RSCT Topology Services
to determine the status of the local adapters --
the result was the program being blocked. In an
HACMP/ES environment, the blockage may cause the
local adapters to be flagged as down incorrectly,
provoking spurious "swap_adapter" events.

PROBLEM CONCLUSION:
To work around the problem of getprotobyname() blocking
in the presence of Network Information Service (NIS),
the code in RSCT Topology Services is being changed
to remove such call. With the fix, the
netmonAdapterHealth program should no longer
block when NIS is running, and therefore false
adapter down indications or "swap_adapter" events
in HACMP/ES should not occur.

------

APAR: IY23778  COMPID: 5765E6110  REL: 220
ABSTRACT: FALSE FAIL_STANDBY EVENT IN HAES441

PROBLEM DESCRIPTION:
false fail_standby event in haes441

PROBLEM SUMMARY:
A problem in RSCT Topology Services results in
"false" fail_standby events in HACMP/ES, and
possibly other forms of "false" failed adapter
indications. The problem occurs due to an
incorrect interaction (a race condition)
between the Topology Services NIM process and
the netmon (adapter status determination) library.
The following sequence may be observed in the
Topology Services NIM process log -- located at
/var/ha/log/nim.topsvcs.<interface>.<cluster_name> .00X  --
up to a few minutes after the false adapter
indication:
10:04:17: Received an OPEN command      <= (3)
10:04:17: Minimum packet size:    76
 ...
10:04:17: Local address: 192.114.129.195
 ...
10:04:17: Adapter has broadcast capability. Address
192.114.129.255.
10:04:17: Broadcast address is 192.114.129.255.
10:04:17: Bind to broadcast address succeeded.
10:04:17: Response successfully sent.
10:04:17: Sleep for 5.0 sec.
10:04:17: netmon_thread_main: got a netmon request. <= (2)
10:04:17: Netmon thread: file descriptors closed. <= (1)
The occurrence of the "file descriptors closed" (1)
entry right after the "got a netmon request" (2)
entry, a few lines AFTER the
"Received an OPEN command" (3) entry gives an indication
that the problem is being seen.

PROBLEM CONCLUSION:
With the fix, the false fail_standby event
in HACMP/ES should no longer occur.
When examining the Topology Services NIM
process log -- located at
/var/ha/log/nim.topsvcs.<interface>.<cluster_name> .00X  --
the "file descriptors closed" entry should NOT occur
right after the "got a netmon request" entry (when the
latter occurs a few lines after the "Received an OPEN
command"
entry)
See example below:
10:51:41: Received an OPEN command
10:51:41: Minimum packet size:    76
 ...
10:51:41: Adapter has broadcast capability. Address
9.114.61.255.
10:51:41: Broadcast address is 9.114.61.255.
10:51:41: Bind to broadcast address succeeded.
10:51:41: Response successfully sent.
10:51:41: Sleep for 5.0 sec.
10:51:41: netmon_thread_main: got a netmon request.
10:51:42: Receive thread (re-)enabled.
10:51:42: netmon response: 2
10:51:42: netmon response: Adapter is up

------

APAR: IY23782  COMPID: 5765E6110  REL: 220
ABSTRACT: DCE CWS HANG

PROBLEM DESCRIPTION:
dce cws hang

PROBLEM SUMMARY:
Reset haemd priority to 60.

PROBLEM CONCLUSION:
Reset haemd priority to 60.

------

APAR: IY23783  COMPID: 5765E6110  REL: 220
ABSTRACT: MISSING MESSAGE TEMPLATES

PROBLEM DESCRIPTION:
RSCT 1.2.1 is missing some error templates and many messages
show up in errpt with LABEL: NONE and missing detail data.

PROBLEM SUMMARY:
In rsct.basic.rte 1.2.1 the error template errid's have
changed.  When this release is migrated to, the new error
templates are missing and any of the rsct errpt entries
will not have detailed data.

PROBLEM CONCLUSION:
Modified the packaging files so that the updated
error templates for rsct.basic.rte will be applied
as part of the service stream.

------

APAR: IY23877  COMPID: 5765B8100  REL: 220
ABSTRACT: ISDN CALL TRANSFER CUSTOM SERVER CORE DUMPS WHEN NO SPARE CHPS

PROBLEM DESCRIPTION:
The ISDN Call Transfer Custom Server core dumps when the
system runs out of CHPs.

PROBLEM SUMMARY:
The ISDN Call Transfer Custom Server core dumps
 when the system runs out of CHPs.

PROBLEM CONCLUSION:
By correcting the call to the error function
 to remove the core dump.

------

APAR: IY24020  COMPID: 5765E6110  REL: 220
ABSTRACT: FIXES REQUIRED FOR UNIX MPM AUTHENTICATION SUPPORT

PROBLEM DESCRIPTION:
fixes required for unix mpm unauthentication support

PROBLEM SUMMARY:
The CSM Technology Preview was unable to remotely
authenticate between the managed node and the
management  server.  In particular, the CSM
install of the managed node failed because the
mgmtsvr command that runs on the managed
node could not perform its function since it could
not remotely connect to the management server.
The symptom would be an "INSTALL FAILED"
message output to the screen when installing the
CSM Technology Preview product, and there
would be a more detailed error from the mgmtsrv
command in the installnode.log in /var/log/csm.

PROBLEM CONCLUSION:
The RMCAPI now recognizes the code from the security library
that indicates the user should be treated as an
unauthenticated user.

------

APAR: IY24043  COMPID: 5648C9802  REL: 430
ABSTRACT: SDK 1.3.0 PTF 8 : CA130-20010925  WITH COMM API CHANGE

PROBLEM DESCRIPTION:
Fixes since PTF 7a  (ca130-20010615a) :
(Note: The descriptions here have been truncated.)
+--------+------+-------+------------------------------------+
|20010720|29377 |       |Javacore fix #2 - native stack backt|
+--------+------+-------+------------------------------------+
|20010720|32242 |       |activeCount is not accurate         |
+--------+------+-------+------------------------------------+
|20010720|32772 |       |AIX lockup in GC                    |
+--------+------+-------+------------------------------------+
|20010720|32919 |       |Step over System.gc() in jdb causes |
+--------+------+-------+------------------------------------+
|20010720|33071 |       |Incorrect Apperance of AWT Checkboxe|
+--------+------+-------+------------------------------------+
|20010720|33115 |       |Sunbug 4413973 fixes                |
+--------+------+-------+------------------------------------+
|20010720|33132 |       |UpFolder Button on JFileChooser init|
+--------+------+-------+------------------------------------+
|20010720|33154 |       |Popup menus displayed off screen.   |
+--------+------+-------+------------------------------------+
|20010720|33470 |       |Missing error message on invalid dev|
+--------+------+-------+------------------------------------+
|20010720|33642 |       |unable to display chinese characters|
+--------+------+-------+------------------------------------+
|20010720|33667 |       |HTMLEditorKit: Backspace deletes but|
+--------+------+-------+------------------------------------+
|20010720|33674 |       |JViewport painting problem with back|
+--------+------+-------+------------------------------------+
|20010720|33706 |       |Java hang during build (gc parallel |
+--------+------+-------+------------------------------------+
|20010720|33763 |       |LINUX 390-SVT: JGrinder Hang under e|
+--------+------+-------+------------------------------------+
|20010720|33790 |       |Tree editing is invisible           |
+--------+------+-------+------------------------------------+
|20010720|33793 |       |Disabled JTextField bkgd color not g|
+--------+------+-------+------------------------------------+
|20010720|33894 |       |java.security - security.provider li|
+--------+------+-------+------------------------------------+
|20010720|33938 |       |Deserialization of file URLs fails  |
+--------+------+-------+------------------------------------+
|20010720|33985 |       |GIF's in HTMLEditorKit Incorrectly s|
+--------+------+-------+------------------------------------+
|20010720|34049 |       |JRE doesn't use default Win32 keyboa|
+--------+------+-------+------------------------------------+
|20010720|34054 |       |scrolling prob on JTextField /w a bo|
+--------+------+-------+------------------------------------+
|20010720|34057 |       |JFileChooser inmproper display in Br|
+--------+------+-------+------------------------------------+
|20010720|34070 |       |GZIPOutputStream leaks native heap  |
+--------+------+-------+------------------------------------+
|20010720|34318 |       |Korean and Chinese fonts do not work|
+--------+------+-------+------------------------------------+
|20010722|34393 |       |AIX - Corrupted objects after a MMI2|
+--------+------+-------+------------------------------------+
|20010724|34162 |       |JNI Local Refs set to 2 when JIT ena|
+--------+------+-------+------------------------------------+
|20010724|34427 |       |AIX - Mapping up to 3 JIT frame valu|
+--------+------+-------+------------------------------------+
|20010725|33782 |       |Wrong path names in src.jar         |
+--------+------+-------+------------------------------------+
|20010725|34338 |       |Exception with threads command      |
+--------+------+-------+------------------------------------+
|20010726|33683 |       |pt_BR months and days in incorrect c|
+--------+------+-------+------------------------------------+
|20010726|34488 |       |java.sql.Date and Time classes too s|
+--------+------+-------+------------------------------------+
|20010727|33624 |       |java.specification.version system pr|
+--------+------+-------+------------------------------------+
|20010727|33742 |       |Not able to Keyin Turkish characters|
+--------+------+-------+------------------------------------+
|20010731|33912 |       |JFileChooser error selecting directo|
+--------+------+-------+------------------------------------+
|20010801|27769 |       |jawt_GetAWT routine missing         |
+--------+------+-------+------------------------------------+
|20010801|33005 |       |Japanese Character Translation      |
+--------+------+-------+------------------------------------+
|20010801|33993 |       |bug in JComponent.getTopLevelAncesto|
+--------+------+-------+------------------------------------+
|20010804|34656 |       |Addition to README.HTML about not su|
+--------+------+-------+------------------------------------+
|20010807|34538 |       |CTRL accelerator key is NOT translat|
+--------+------+-------+------------------------------------+
|20010808|34536 |       |Java Thread dump shows owned monitor|
+--------+------+-------+------------------------------------+
|20010809|34331 |       |Visibility problem with JTabbedPane |
+--------+------+-------+------------------------------------+
|20010809|34714 |       |Null Pointer Exception in first page|
+--------+------+-------+------------------------------------+
|20010809|34885 |       |Hang withWebSphere installation     |
+--------+------+-------+------------------------------------+
|20010810|34879 |       |SmtpClient.to() strips angled bracke|
+--------+------+-------+------------------------------------+
|20010813|34628 |       |KeyPad Enter key is not Functioning |
+--------+------+-------+------------------------------------+
|20010813|34845 |       |JTextField scroll problem           |
+--------+------+-------+------------------------------------+
|20010813|34870 |       |Dimension.setSize(double, double) fa|
+--------+------+-------+------------------------------------+
|20010815|32451 |       |Accessibility problem with SplitPane|
+--------+------+-------+------------------------------------+
|20010815|34941 |       |Index8GrayToRBG565 not in libawt.a e|
+--------+------+-------+------------------------------------+
|20010817|34620 |       |JDK locks up after Ctrl-Break       |
+--------+------+-------+------------------------------------+
|20010818|35129 |       |Proxy class refer java/lang/Char ins|
+--------+------+-------+------------------------------------+
|20010821|34774 |       |Multiple threads loop or segfault oc|
+--------+------+-------+------------------------------------+
|20010824|35325 |       |ECONNABORTED should be ignored      |
+--------+------+-------+------------------------------------+
|20010810|34879 |       |SmtpClient.to() strips angled bracke|
+--------+------+-------+------------------------------------+
|20010813|34628 |       |KeyPad Enter key is not Functioning |
+--------+------+-------+------------------------------------+
|20010813|34845 |       |JTextField scroll problem           |
+--------+------+-------+------------------------------------+
|20010813|34870 |       |Dimension.setSize(double, double) fa|
+--------+------+-------+------------------------------------+
|20010904|34768 |       |RAS:Add "Check on Exception" process|
+--------+------+-------+------------------------------------+
|20010904|35130 |       |Locale.getDisplayName wrong for Simp|
+--------+------+-------+------------------------------------+
|20010904|35584 |       |Modify jni header files/compatibilit|
+--------+------+-------+------------------------------------+
|20010905|34781 |       |Font for Install Panels are hard to |
+--------+------+-------+------------------------------------+
|20010913|35651 |       |GC can collect live objects in threa|
+--------+------+-------+------------------------------------+
|20010921|35886 |       |Mem. leak on registerKeyboardAction |
+--------+------+-------+------------------------------------+
|20010921|36114 |       |Backing out changes from 33993      |
+--------+------+-------+------------------------------------+
|20010925|25813 |       |Port defect 25789 into 1.3.0 line (T|
+--------+------+-------+------------------------------------+
|20010925|35150 |       |Code not getting compile            |
+--------+------+-------+------------------------------------+
|20010925|35316 |       |Disabled JTextField background color|
+--------+------+-------+------------------------------------+
|20010925|35396 |       |Java crash using PS web console with|
+--------+------+-------+------------------------------------+
|20010925|35503 |       |JVM core-dump with Object.clone() in|
+--------+------+-------+------------------------------------+
|20010925|35843 |       |Japanese Character Translation      |
+--------+------+-------+------------------------------------+
|20010925|35900 |       |Attach to a running VM hits NullPoin|
+--------+------+-------+------------------------------------+
|20010925|35960 |       |IM status window remains, even after|
+--------+------+-------+------------------------------------+
|20010925|35967 |       |Call to Naming.lookup never returns |
+--------+------+-------+------------------------------------+
|20010925|36000 |       |TimeZone calculates DST wrong for AE|
+--------+------+-------+------------------------------------+
|20010925|36007 |       |JComboBox.isFocusTraversable() alway|
+--------+------+-------+------------------------------------+
|20010925|36217 |       |reshape() causes paint() to be repea|
+--------+------+-------+------------------------------------+
|20010925|349546|CommAPI|Timeout not working for read on seri|
+--------+------+-------+------------------------------------+

------

APAR: IY24200  COMPID: 5765D5100  REL: 311
ABSTRACT: LATEST PSSP 3.1.1 FIXES AS OF OCTOBER 2001

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

PROBLEM SUMMARY:
This is a packaging apar for PSSP 3.1.1 fixes
as of October 2001.

PROBLEM CONCLUSION:
This is a packaging apar for PSSP 3.1.1
fixes as of October 2001.

------

APAR: IY24204  COMPID: 5765C3403  REL: 433
ABSTRACT: PUT_LID FAILED FOR EMPTY DATABASE

PROBLEM DESCRIPTION:
Customer can not add phase 1 tunnels to the IKE database
if there are no phase 1 tunnels already in the database.

PROBLEM CONCLUSION:
Fixed LSP to return proper error code for "no records found"

------

APAR: IY24229  COMPID: 5765D1700  REL: 220
ABSTRACT: AIXDCE22 MAINTENANCE PACKAGE FOR PTF SET 10

PROBLEM DESCRIPTION:
THIS APAR CREATED FOR MAINTENANCE PACKAGE OF PTF SET 10
aixdce22 Maintenance Package for PTF SET 10

PROBLEM SUMMARY:
AIXDCE22 MAINTENANCE PACKAGE FOR PTF SET 10

------

APAR: IY24285  COMPID: 5765B8100  REL: 220
ABSTRACT: 3270 DISABLE_SESSION CANNOT BE RE-ENABLED

PROBLEM DESCRIPTION:
If the 3270 script statemant "DISABLE_SESSION" is executed then
the session cannot be re-enabled without shutting down and
restarting SNA.

PROBLEM SUMMARY:
If the 3270 script statemant "DISABLE_SESSION"
is executed then the session cannot be re-enabled without
shutting down and restarting SNA.

PROBLEM CONCLUSION:
Make DISABLE_SESSION work as though the
session had been disabled by the GUI
by the GUI

------

APAR: IY24302  COMPID: 5765E2600  REL: 502
ABSTRACT: BROKEN LINKS TO IOC RTE AFTER AIX51 INSTALL

PROBLEM DESCRIPTION:
There are links that point to AIX43 libraries even after
migration to AIX51

PROBLEM CONCLUSION:
VisualAge C++ for AIX 5.0.2.2 PTFs

------

APAR: IY24313  COMPID: 5697E3000  REL: 220
ABSTRACT: EPSON GT-8700 SCANNER SUPPORT

PROBLEM DESCRIPTION:
JKIT modification up

LOCAL FIX:
change for modification up

------

APAR: IY24346  COMPID: 5765B8100  REL: 220
ABSTRACT: RUNNING OUT OF BUFFERS FOR THE ISDN SIGNALING PROCESS ISDN.ATT

PROBLEM DESCRIPTION:
Running out of buffers for the isdn signaling process.
Have to kill and restart the process

PROBLEM SUMMARY:
Running out of buffers for the isdn signaling
process. Have to kill and restart the process

PROBLEM CONCLUSION:
Fixed RLT protocol functions for dms100 and
dms250 a buffer leak was causing a system abend after approx
2 weeks. The buffer leak was tracked down to ISDNDL4 call
control, caused when caller hangs up before the transfer
completes. The buffer that was being held incorrectly
was freed.

------

APAR: IY24349  COMPID: 5765B8100  REL: 220
ABSTRACT: RUNNING OUT OF BUFFERS FOR THE ISDN SIGNALING PROCESS ISDN.DMS

PROBLEM DESCRIPTION:
Running out of buffers for the isdn signaling process.
Have to kill and restart the process

PROBLEM SUMMARY:
Running out of buffers for the isdn signaling
process. Have to kill and restart the process

PROBLEM CONCLUSION:
Fixed RLT protocol functions for dms100 and
dms250 a buffer leak was causing a system abend after approx
2 weeks. The buffer leak was tracked down to ISDNDL4 call
control, caused when caller hangs up before the transfer
completes. The buffer that was being held incorrectly
was freed.

------

APAR: IY24352  COMPID: 5765B8100  REL: 220
ABSTRACT: RUNNING OUT OF BUFFERS FOR THE ISDN SIGNALING PROCESS ISDN.EURO

PROBLEM DESCRIPTION:
Running out of buffers for the isdn signaling process.
Have to kill and restart the process

PROBLEM SUMMARY:
Running out of buffers for the isdn signaling
process. Have to kill and restart the process

PROBLEM CONCLUSION:
Fixed RLT protocol functions for dms100 and
dms250 a buffer leak was causing a system abend after approx
2 weeks. The buffer leak was tracked down to ISDNDL4 call
control, caused when caller hangs up before the transfer
completes. The buffer that was being held incorrectly
was freed.

------



[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic