The patch note contains the following sections:
This patch contains the following revisions since the last maintenance
release:
|
Available as of
Version |
CR Number / APAR
Number |
Description |
|
5.3.1 |
24812 / JR18847 |
During polling, if the FTP server goes down and comes up at a later stage, the connector ignores remote polling and just continues with the local polling. This defect has been resolved . For eg .. FTPPollTerminateIfServerDown=false FTPKeepConnectionOpen=false PollFrequency=10000 FTPPollFrequency=10 In the above scenario, even if the ftp server goes down, connector will continue polling the ftp local event directory. Now when the ftp server comes up, remote poll will occur once the poll cycle equals the FTPPollFrequency and the poll cycle count will start again from 1. |
|
5.3.2 |
BGTRK00027337/JR19163; CR 23365/ 23370 |
JText connector produces infinite loop with an invalid/damaged file. Customer sees an infinite loop when using JText 5.3.1 adapter. It seems that the connector goes into an endless loop when picking up an invalid file from the ftp local directory. The endless loop that the connector falls into takes up significant processor time, and it actually becomes nearly impossible to connect to the ICS when the failure is happening. The CR23365 is for handling the zero byte files. The CR23370 is for handling output filenames being appending at each service call. |
|
5.3.3 |
BGTRK00023370 |
When the property FTPKeepConnectionOpen=true, the output filenames on MVS are being appended at each service call. |
|
5.3.4 |
BGTRK00016411 BGTRK00031747/JR18847 |
The list of problems that have been corrected : 1. Archival ( Timestamp/Renaming ) of files on MVS 2. Re-establishment of connection during FTP server being down / after a timeout condition ( On all platforms) during both FTP polling and FTP service calls. Note: During service calls, the first call after the timeout is being discarded from processing. |
|
5.3.5 |
BGTRK00035017 |
When JText connector was used for event processing with FTP service, it was hanging after running for several hours. The problem was detected in the FTP network read operation where the JText connector sometimes wait for data indefinitely. The problem was corrected by timing out the FTP network read operations, (if it blocks for a specified interval of time) and retrying it. If the read operation still fails after a specified number of retries, the FTP connection was broken and re-established internally. |
To perform an upgrade to this version of the connector add, replace, or
remove the following files and directories as indicated:
|
For Connector Version |
Platform [WIN;UNIX] |
Add / Replace / Remove |
File (Starting from %CROSSWORLDS%/$CROSSWORLDS) |
|
5.3.1 |
Win; Unix |
Replace |
connectors\JText\CWJText.jar |
|
5.3.2 |
Win; Unix |
Replace |
connectors\JText\CWJText.jar |
|
5.3.3 |
Win; Unix |
Replace |
connectors\JText\CWJText.jar |
|
5.3.4 |
Win; Unix |
Replace |
connectors\JText\CWJText.jar |
|
5.3.5 |
Win; Unix |
Replace |
connectors\JText\CWJText.jar connectors\JText\dependencies\NetComponents.jar |
April 27, 2004, 4:30 PM
© 2003 IBM Corporation. Proprietary and Confidential. All Rights Reserved.