MQSeries link for R/3 CSD History ================================= A) Superseded PTFs --------------- CSD01 - PTF U464324 AIX PTF U200107 Sun Solaris PTF U200108 Windows NT B) Latest Available PTFs --------------------- CSD01 - PTF U200106 HP-UX Version 10 CSD02 - PTF U472735 AIX PTF U200145 HP-UX Version 11 PTF U200129 Sun Solaris PTF U200130 Windows NT PTFs for MQSeries link for R/3 V1.2 are only obtainable via your IBM Support Center (ISC). Your level 2 service representative will be able to get this PTF for you and send it to you. C) APAR IC32003 ------------ MQSeries link for R/3 for Windows NT V1.2 does not install on a Windows 2000 system. This APAR will add support for MQSeries link for R/3 for Windows NT V1.2 when installing on a Windows 2000 system. The APAR fix (IC32003.zip) for this problem consists of a single zip file which contains a replacement for the following file in MQSeries link for R/3 for Windows NT V1.2. SETUP.INS To apply the fix :- (1) Unzip the IC32003.zip file into a temporary directory on your hard drive. (2) Rename the existing SETUP.INS file so that you have a backup of the original file. (3) Replace the original SETUP.INS file with the one in the efix. (4) Run the installation. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ PTF HISTORY =========== A) CSD02 ----- The second PTFs for IBM MQSeries link for R/3 Version 1.2. They are distributed for the English language version only. It is delivered via PTF U472735 for APAR IY12355 on AIX. It is delivered via PTF U200145 for APAR IY12357 on HP-UX V11. It is delivered via PTF U200129 for APAR IY12379 on Sun Solaris. It is delivered via PTF U200130 for APAR IC27770 on Windows NT or Windows 2000. They contain fixes for ALL the problems listed below: IC33198 - Message SMQ4128 incorrect for HP-UX where the field appears as a space. On all platforms the message is displayed correctly and the message insert becomes: on Queue Manager . IC28350 - Message performance WindowsNT/Windows 2000. Message SMQ4117 can now be displayed correctly; could wait 1500 mS before failing on Windows. IY18764 - User Exit locking on HP-UX V11 UNRESOLVED SYMBOL: PTHREAD_LOCK_GLOBAL_NP When user called an SMQSI/SMQSO exit whilst connecting using MQSeries 5.2 or later. IY14014 - SMQ4188 mqrc=2086/Queue Manager name added to text of message Fixed SMQSO getting mqrc=2086 (unknown qmgr object) when trying to open the outbound queue. This error occurs if the outboundqueuemanager parm in the smqdestconf file is missing or misspelled. On all platforms the message is displayed correctly and the message insert becomes: on Queue Manager . 64232 - Set size of SMQERR01/02/03.LOG wrapping (size) Environment variable on Solaris/AIX/HP-UX SMQERR01/02/03.LOG wrap at 250,000 characters. This can now be set from an environment variable: export SMQERRORLOGSIZE=1000000 63851 - Control MQSeries Agent memory usage with SMQSI Blocking MQGET from Input Queue no longer waits for data of maxidocsize size (in.ini or out.ini). This prevents potential problem with multiple SMQSI waiting within an MQSeries Agent process using large amounts of memory. 55772 - Windows 2000 install (work around) Original CD-ROM will not install on Windows 2000 Although the original CD-ROM is not refreshed, an e-fix is available from IBM Service to allow an install on Windows 2000. CSD1 and CSD2 are not affected by the platform. 55649 - Solaris locking on MQSeries 5.2 UNRESOLVED SYMBOLS: sun_lock_global_np/sun_unlock_global_np When user called an SMQSI/SMQSO exit whilst connecting using MQSeries 5.2 or later. 54523 - Set size of SMQERR01/02/03.LOG wrapping (size) Environment variable on WindowsNT/2000 SMQERR01/02/03.LOG wrap at 250,000 characters. This can now be set from an environment variable: set SMQERRORLOGSIZE=1000000 48395 - Control-C hang on solaris fixed Prevents MQSeries queue manager hanging when SMQSI is ended with Control-C in rare circumstances. 45421 - IDOC left on Queue manager when closing SMQSO Prevents SMQSO loosing an IDOC if the MQSeries Server is ending whilst the SMQSO is running. 45029 - New SAP Inbound coordination Requiring a minimum of RFC 4.5B from SAP 44594 - Suppress User exit (re)loading messages Messages that the User exit has (re)loaded when an exit is called are suppressed. This reduces the amount of text written to SMQERR01/02/03 logs. B) CSD01 ----- The first PTFs for IBM MQSeries link for R/3 Version 1.2. They are distributed for the English language version only. It is delivered via PTF U464324 for APAR IX89448 on AIX. It is delivered via PTF U200106 for APAR IX89449 on HP-UX. It is delivered via PTF U200107 for APAR IX89451 on Sun Solaris. It is delivered via PTF U200108 for APAR IC23728 on Windows WinNT They contain fixes for ALL the problems listed below: IX88947 - SAP R/3 LINK LOAD BALANCING=YES CAUSES CORE DUMPS. When an attempt was made to use the load balancing option on the inbound server (loadbalance=y) with MQIntegrator, the inbound server core dumped. This was due to MQIntegrator putting a NULL at the end of the hostname option. MQSeries link for R/3 has been changed to accommodate NULL characters at the end of the hostname option. IX88949 - R/3 LINK LOGGING SLOWS PERFORMANCE A new option has been added to the inbound and outbound server initialisation files to improve performance. The option is called "logging". By default the option will be set to logging=y, but to improve performance it can be set to logging=n. This means that the MQSeries Link for R/3 status information will not be written to the log file. The information is still written to the console. IX88956 - R/3 LINK - On Solaris a 2030 can cause a core dump On Solaris, when an attempt is made to put an IDoc to a queue where the IDoc size is larger than that of the max queue depth, the error 2080 MQRC_TRUNCATED_MSG_FAILED is received. This error caused the Outbound server to core dump. This problem was fixed by improving the error handling. IY00023 - EDI_MESTYPE APPEARS TO BE IGNORED When an attempt is made to match an outbound server's IDoc with a routing destination, a value in the EDI_MSGTYP may be incorrectly interpreted as a * (wildcard) when an alternative value was provided. This problem was fixed by improving the matching of this field. 39387 - Terminating the inbound server with CTRL-C whilst the inbound server was within an RfcInbound function call caused IDocs to be duplicated in the SAP server. This SAP problem has been addressed by improving the signal handling within the product.