IBM corporation Readme file for WebSphere Partner Gateway 6.2 FixPack 2. Platforms: AIX, HP-UX, Linux, PowerLinux, Solaris, Windows Maintenance Delivery Vehicle type: 6.2.0-WS-WPG-Advanced_FP2.pak 6.2.0-WS-WPG-Enterprise_FP2.pak These installables can be used across all WebSphere Partner Gateway supported platforms. © Copyright International Business Machines Corporation 2009. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. ================================================== WebSphere Partner Gateway 6.2.0.2 Readme Readme documentation for version 6.2 FixPack 2 IBM® WebSphere Partner Gateway, including installation-related instructions, prerequisites, and known issues. These notes describe the changes made in FixPack 6.2.0.2 of IBM WebSphere Partner Gateway, Enterprise and Advanced Editions. IMPORTANT: 6.2 FixPack 2 can be installed and uninstalled ONLY by using IBM® Update Installer for WebSphere® software. Refer to IBM®WebSphere® Partner Gateway Update Installer available at: http://www-01.ibm.com/support/docview.wss?uid=swg27015150 ================================================== Prerequisites 1. When using WebSphere Partner Gateway 6.2 FixPack 2 with WebSphere Application Server Network Deployment 6.1 Fixpack 23 and 25 (WAS ND FP23 and 25), following Null Pointer exceptions are seen in WebSphere Partner Gateway (WebSphere Partner Gateway)logs. The Null pointer exception seen is followed by an "DSRA9110E: Connection is closed" exception trace. The following exceptions are seen in the WebSphere Partner Gatewayserver logs: E UOW=null source=com.ibm.ws.scheduler.SchedulerDaemonImpl org=IBM prod=WebSphere component=Application Server thread=[java.lang.ThreadGroup[name=ArchiverWorkManager: WM Service Group,maxpri=10]] SCHD0104E: The Scheduler poll daemon ArchiverScheduler (scheduler/ArchiverScheduler) failed to load tasks from the database due to an exception: java.lang.NullPointerException at java.util.Hashtable.getEntry(Hashtable.java:468) at java.util.Hashtable.containsKey(Hashtable.java:354) at com.ibm.db2.jcc.a.lg.setCursorName(lg.java:695) ...... ...... E UOW=null source=com.ibm.ejs.j2c.MCWrapper org=IBM prod=WebSphere component=Application Server thread=[java.lang.ThreadGroup[name=ArchiverWorkManager: WM Service Group,maxpri=10]] J2CA0081E: Method cleanup failed while trying to execute method cleanup on ManagedConnection WSRdbManagedConnectionImpl@4e904e90 from resource datasources/bcgArchiverDS. Caught exception: com.ibm.ws.exception.WsException: DSRA9110E: Connection is closed. at com.ibm.ws.rsadapter.exceptions.DataStoreAdapterException.(DataStoreAdapterException.java:241) at com.ibm.ws.rsadapter.exceptions.DataStoreAdapterException.(DataStoreAdapterException.java:190) at com.ibm.ws.rsadapter.AdapterUtil.createDataStoreAdapterException(AdapterUtil.java:389) at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.dissociate(WSJdbcConnection.java:1383) This problem is identified to occur due to incorrect handling of closed database pooled connections in WebSphere Application Server. The recommended link to download and apply the fix for WAS ND 6.1 FP23 and WAS ND FP 25 - http://www.ibm.com/eserver/support/fixes/fixcentral/swgquickorder?fixes=6.1.0.23-WS-WAS-IFPK86552&productid=WebSphereApplication Server&brandid=5 The WebSphere Application Server APAR PK86552 description is available at http://www-01.ibm.com/support/docview.wss?rs=180&context=SSEQTP&dc=DB550&uid=swg1PK86552&loc=en_US&cs=UTF-. 2. Make sure that value for -Wupdate.RunSQLFiles is set to "Yes" in the Update Installer response parameter file. 3. For applying 6.2 FixPack 2 when WebSphere Partner Gateway is installed on an existing cell, see the technote http://www-01.ibm.com/support/docview.wss?uid=swg21402404. You do not have to apply this FixPack on bcgapps location. ================================================== Operating System, Server and Database support The Advanced Edition of WebSphere Partner Gateway Version 6.2.0.0 FixPack 2 extends support for the following Operating System, Server and Database, other than those available in the base release. 1. WebSphere Application Server Network Deployment V6.1.0.27 2. IBM DB2 UDB V9.5 FixPack4a 3. AIX 6.1 TL1, TL2, TL3 and TL4. The WebSphere Partner Gateway(WPG) 6.2 base installer does not launch on AIX 6.1 TL2, TL3 and TL4. Please visit http://www.ibm.com/support/docview.wss?uid=swg21414899 for details regarding the work-around for details of installation. For more details, refer to system requirements: http://www-01.ibm.com/support/docview.wss?uid=swg27013981 ================================================== Known problems and workarounds The following problems exist in this FixPack: 1. The Partner Migration export on DB2 does not Import on Oracle for EDI maps. This issue is found while importing a map using the console on Oracle and then importing some exported data from a DB2 system that has the same map ID. This corrupts the existing map on oracle and does not allow the same map to get imported in WebSphere Partner Gateway (using Import Utility and console). 2. Errors are observed in bcgmigration logs during the import of Certificate sets, which are associated to an already deleted partner. For the certificate set, deleted partner can be associated either as a “from” or “to” partner. 3. Client Authentication for FTPS mode may not work when an invalid primary and a valid secondary certificates are uploaded. When using client authentication for FTPS mode in case of an expired primary certificate and a properly configured valid secondary certificate, the document processing fails. The transition of secondary to primary certificate happens in WebSphere Partner Gateway configuration. The workaround solution is to perform a restart of WebSphere Partner Gateway Document Manager server. 4. When Secondary to primary transition of a certificate happens, events “BCG240027- Certificate Is Expired” and “BCG108011-Secondary Certificate changed to Primary Certificate” may not get logged. 5. When SSL client authentication is configured for FTP scripting destination with FTPS mode enabled, and a revoked CA certificate is uploaded at the hub operator profile, the events "BCG240024 -CertPath validation failed" and "BCG240033 -No valid SSL client certificate found" may not get logged. 6. When you attempt to install WebSphere Partner Gateway v6.2 GA DBLoader directly on Oracle 11.1.0.7, then the "ORA-22996: NEXT extent size is smaller than LOB chunksize" error gets generated during the creation of the following WebSphere Partner Gateway tables: - BP_RNSTATEDTL - BP_RNSTATEDTL_HIST - CF_BUSINESSLOGO - CF_CRL - CF_GUIDELINEMAP - CF_TRANSFORMMAP - PR_CERT - EDICSTX Symptom Oracle Error "ORA-22996: NEXT extent size is smaller than LOB chunksize" This error is seen to be occuring during the execution of WebSphere Partner Gateway v6.2 GA DBLoader installation. Resolving the problem This problem has been resolved with WebSphere Partner Gateway 6.2 FixPack 2. Users intending to use Oracle 11.1.0.7 with WebSphere Partner Gateway 6.2 GA installation, would need to ignore the above error message, and apply WebSphere Partner Gateway 6.2 FixPack 2 immediately after installation of WebSphere Partner Gateway 6.2 GA, so as to get these tables created. Only users who intend to have WebSphere Partner Gateway 6.2 GA installed on Oracle 11.1.0.7 are affected by this error. WebSphere Partner Gateway v6.2 GA is supported on Oracle 11.1.0.6. From WebSphere Partner Gateway v6.2 FixPack 2 onwards, support is also provided for Oracle version 11.1.0.7. 7. When you upgrade to 6.2 FixPack 2, “Error 404: Cannot load application resources bundle console” error might occur. This problem is observed intermittently on HP-UX platform. Workaround for this problem: - Run the Update Installer and uninstall the WebSphere Partner Gateway 6.2 FixPack 2. - Do NOT restore the DB. - Run the Update Installer and Install WebSphere Partner Gateway 6.2 FixPack 2 again. ==================================================== Installing WebSphere Partner Gateway 6.2 FixPack 2 IBM WebSphere Partner Gateway Version 6.2 FixPack 2 can be installed, ONLY by using IBM® Update Installer for WebSphere Software (7.0.0.1 and above). Installing the FixPack is a three step operation: Step A - Setup the IBM Update Installer environment. Step B - Take the backup of WebSphere Partner Gateway application Database. Step C - Install the FixPack. Step A - Setup the IBM Update Installer environment 1. Download the IBM® Update Installer for WebSphere Software from http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg24020212 2. Follow the instructions at: http://www-01.ibm.com/support/docview.wss?uid=swg27015150, to download and apply the WebSphere Partner Gateway specific Update Installer changes. Ensure that the necessary updates to the responsefile bcgupdate_.txt present under /responsefiles/, /responsefiles/ are performed. Now, IBM Update Installer is ready to install WebSphere Partner Gateway fixes and FixPacks on your environment. Step B - Taking the backup of existing database Take the backup of the existing WebSphere Partner Gateway Application database. This is a mandatory step, and the database backup taken at this point is to be retained and used, as necessary, during uninstallation of WebSphere Partner Gateway 6.2 FixPack 2. The backup step is required as uninstallation of the FixPack using IBM Update Installer does not restore the database to its previous version of WebSphere Partner Gateway. The database restoration step is to be performed manually, and it is mandatory whenever WebSphere Partner Gateway 6.2 FixPack 2 is uninstalled. For more information on data back up and restore, see "Migrating the database" of WebSphere Partner Gateway Installation Guide. Step C - Applying the FixPack 1. In case of applying the FixPack on WebSphere Partner Gateway distributed mode installations (Simple distributed and Fully Distributed); the 6.2 FixPack 2 pak file needs to be applied using update installer on all machines that host the following WebSphere Partner Gateway components in the specified order: a. WebSphere Partner Gateway Deployment Manager, b. WebSphere Partner Gateway Hub, 2. In case of applying the FixPack on WebSphere Partner Gateway simple mode installation, provide the product location corresponding to the WebSphere Partner Gateway Hub location to apply the 6.2 FixPack 2 file using update installer. 3. Following are the prerequisites for 6.2 FixPack 2 installation. a) While applying the FixPack on simple mode deployment, make sure that the server is up and running. b) Make sure that the Deployment Manager (DMGR) and all node agents are up and running for simple distributed and fully distributed deployments. c) Stop all WebSphere Partner Gateway clusters in case of simple distributed and fully distributed deployment before applying FixPack. 4. Execute the script update.bat for Windows and update.sh for non-Windows to launch Update Installer. 5. In the Product Selection window, enter the DMGR installed location as the value for Directory Path. 6. In the Maintenance Operation Selection window, select Install maintenance package. 7. In the Maintenance Package Directory Selection window, provide the location of the 6.2 FixPack 2 pak file. 8. In the Available Maintenance Package to Install window, ensure that the check box for FixPack pak file is selected. Note that when using the IBM Update Installer for WebSphere Partner Gateway, select only one pak file for installation. Else it may give unexpected results. Installation Summary window will list the details about the pak file to be installed on selected location. Installation will start and after it completes, an appropriate message, that is, Success or Failed will be displayed. Verify the logs present under /logs/update/<6.2 FP2 pak name>.install for more information on the FixPack installation. 9. Perform these steps on all machines where Receiver hub, Console hub, and DocMgr hub (WebSphere Partner Gateway components) are installed. Note: For applying 6.2 FixPack 2 when WebSphere Partner Gateway is installed on an existing cell, see the technote http://www-01.ibm.com/support/docview.wss?uid=swg21402404. You do not have to apply this FixPack on bcgapps location. ===================================================== Uninstalling WebSphere Partner Gateway 6.2 FixPack 2 IBM WebSphere Partner Gateway Version 6.2 FixPack 2 can be uninstalled using IBM® Update Installer for WebSphere Software (7.0.0.1 and above). Note: Uninstallation of the FixPack using Update Installer does not restore the database to its previous version of WebSphere Partner Gateway. The database restoration step is to be performed manually, and is mandatory whenever WebSphere Partner Gateway 6.2 FixPack 2 is uninstalled. Uninstalling the FixPack is a two step operation. Step A - Uninstall the FixPack using IBM Update Installer. Step B - Restore the WebSphere Partner Gateway application Database. Step A - Uninstalling the FixPack Note: In case of uninstalling the FixPack on WebSphere Partner Gateway distributed mode installations (Simple distributed and Fully Distributed), the FixPack .pak file needs to be uninstalled using IBM Update Installer on all machines that host the following WebSphere Partner Gateway components in the specified order: a. WebSphere Partner Gateway Hub b. WebSphere Partner Gateway Deployment Manager In case of uninstalling the FixPack on WebSphere Partner Gateway simple mode installation, the FixPack .pak file needs to be uninstalled using IBM Update Installer providing the product location as corresponding to the location of WebSphere Partner Gateway Hub. Following are the prerequisites for 6.2 FixPack 2 uninstallation: 1. Stop the WebSphere Partner Gateway servers. 2. Go to the IBM® Update Installer installed location and launch the same by executing the script update.bat for Windows and update.sh for non-Windows. 3. Provide the Directory Path in the Product Selection window as the DMGR installed location. 4.In the Maintenance Operation Selection window select Uninstall maintenance package. 5.Select the maintenance package to uninstall, here the 6.2 FixPack 2 pak file. Note that when using the IBM Update Installer for WebSphere Partner Gateway, only one pak file should be selected for uninstallation. Else it may give unexpected results. 6.Uninstallation Summary window will list the details about the pak file to be uninstalled on which location. 7.After this the uninstallation will start and once it is complete the appropriate message i.e., Success or Failed will be displayed. Please verify the logs <.updateconfig.log> present under /logs/update/<6.2 FixPack 2 pak name>.uninstall for more information on the FixPack uninstallation. Note: These steps should be performed in all machines where WebSphere Partner Gateway components are installed. Step B - Restoring the Application Database Once the uninstallation is successfully complete, restore the database using the backup taken before applying the FixPack. ===================================================== List of Fixes in WebSphere Partner Gateway 6.2 FixPack 2 ===================================================== Component: Archiver APAR: JR34164 Description: Some times restored documents were not visible in the console, under “Search Restored Documents” page. On clicking raw restored document, a message ‘Message not found’ was being displayed. This error was seen because DB data was being restored properly but the file data was not getting restored. This is corrected. APAR: JR34258 Description: Any user other than hubadmin user was not able to view archiver report. With this fixpack onwards any user can be provided view permissions on archiver report by providing read/write permissions of “Archiver Report” module to the group of this user. Archiver report page has been moved under Tools tab of console. Component: AS Viewer/AS APAR: JR33953 Description: When using AS Data compression, the filename within the mime part is set to smime.p7 and is different than that of the original file name. With this fix, when AS Data compression is performed, the file name in mime part is preserved as the original file name. APAR: JR35170 Description: When using the below steps to create an alert, Alert creation page was throwing error -"An Alert with this name already exists. Alerts must be unique." 1. Create an alert. 2. Save this alert without going to “Notify” page. 3. Click on Notify page. Subscribe any contact and save this page. This issue has been fixed. APAR: JR33102 Description: When WPG help server was being accessed using SSL, console help links were not working. This is corrected. Now Users who are using SSL for accessing help server need to follow the steps below - 1.In WPG Console go to system administration/Console administration/General. 2.Prefix https:// before hostname given in bcg.console.help.host 3.Provide console port in bcg.console.help.port. (default value is 58443) 4.Logout and login on console. Now all the help links on console can be viewed. APAR: JR33555 Description: If a gateway having autoqueue attribute set to yes goes offline, then its connection timeout value is reset to zero. This has been corrected so that the existing connection timeout value will be retained as is. APAR: JR33259 Description: Alert contacts were not being created having the email defined with address having 4 letter domain and it was throwing the error - "The address must end in a three-letter domain, or two letter country." APAR: JR33533 Description: When using WPG Console to manage the FTP server, the start and stop buttons did not used to work and the following error was issued: "FTP Console server not reachable. Please verify the host name and port number." Component: Console/LDAP APAR: JR34265 Description: When using the LDAP mode of authentication, for WPG Console, it was observed that the WPG Console did not allow to create FTP users with passwords. This made it impossible to create new FTP users to connect to the Intergrated FTP server. This is fixed. Component: Console/Document Viewer APAR: JR33382 Description: When routing multiple documents that were associated to a parent document it was seen that the document viewer displayed the parent document redundantly. This is fixed. Component: Console/EBMS viewer APAR: JR35181 Description: The EBMS Viewer in WPG console did not display the re-tried documents under a conversation. This has been corrected. Component: Console/EDI- Reports APAR: JR35161 Description: Selecting the Functional Acknowledgment overdue reports from WPG console for multiple From and To partners, greater than 20 in number, resulted in SQL Exception. This has been corrected and now it should be possible to retrieve reports for large number of partners at once. Component: Console/SFTP Receiver APAR: JR33957 Description: If a web server existed on the Websphere Application Server, where WPG is deployed, it was seen that the creation of SFTP Receiver using WPG console failed. WPG has been corrected to handle this case. Component: Database/RNIF APAR: JR34161 Description: During routing of large volumes of Rosettanet documents, deadlock errors such as SQL0911 errors were seen. This has been fixed. Component: Destination/File Directory APAR: JR35180 Description: When using a File Directory Gateway configured to a physical location on a unix platform, it was seen that the file permissions on the files transferred using this gateway was not consistent. Some of the files had rw-r-r permission and few others had rw-rw-rw permission. This behavior has been corrected so that all the files have the intended permission of rw-rw-rw. Component: Document Manager APAR: JR33867 Description: When external trading partner repeatedly sends the same AS2 document with same message-id in HTTP header, WPG was not rejecting it as a duplicate message and instead processes the document successfully. This is fixed. APAR: JR33127 Description: In the event of failures for large volumes of documents in WPG, it was seen that the memory in use steadily increased leading to OutOfMemory failures. This has been fixed. APAR: JR33272 Description: There was spamming of event BCG210022 "Process transaction rolled back" in WPG. These events have been restricted to maximum of four, after which the document causing generation of these events will be failed. APAR: JR34252 Description: If none of the certificates were being used, deletion of any partner was causing the below error in logs - "Failed to get WPGSecurityManagerCache config data due to null java.lang.NullPointerException at com.ibm.bcg.util.WBICSecurityManager.getHubOwnerPartnerId(WBICSecurityManager.java:694)” Component: Document Manager/FTP APAR: JR35169 Description: While delivering an EDI interchange having multiple transactions over ftp scripting gateway with the unique file name option de-selected, all the de-enveloped transaction were being shown as in process in the console. This is corrected. Component: Document manager/AS APAR: JR35178 Description: When WPG receives a syncronous response with just a "LF" and not a "CRLF", appended to the header, WPG fails to parse the content-type field, causing failure of the document. This is fixed. APAR: JR33516 Description: When WPG receives 0KB payload, during “pass through” operations, the 0KB content is delivered to the backend application. WPG now restricts sending these 0KB payload documents to the backend application. Component: Document manager/BPE APAR: JR35119 Description: Some documents were infinitely in the in-process state and issued lots of BCG210022 "Process transaction rolled back" events. This was happening for re-sent documents. This is fixed. APAR: JR34720 Description: In a deployment topology which has a network firewall in front of the database, it was seen that some of the WPG poll engines had long running transactions that were severed when the firewall timeout occurred. This resulted in a lot of StaleConnection exceptions and as a result the connections from the pool was exhausted which eventually led to ConnectionWaitTimeout exceptions. The poll engine logic is corrected to use UserTransactions instead of shareable connections under LTC boundary. Component: Document Manager/EBMS APAR: JR35159 Description: While transacting ebms documents with backend database as Oracle, in some cases it was seen that the WPG used to log the SQLException “ORA-01000: maximum open cursors exceeded error”. Some of the ebms related classes have been corrected to explicitly close the ResultsSet objects used so as to mitigate the occurrence of the ORA-01000 problem. APAR: JR35157 Description: ConversationConstraints element in the CPA is optional. However, WPG console was preventing the upload of a CPA that did not have the ConversationConstraints element. This is fixed. APAR: JR33827 Description: EBMS performance has been improved. APAR: JR35172 Description: When JMS destination is configured on WAS SIBUS other than where WPG is hosted and the corresponding messaging engine is not available, WPG issues retires on JMS destination. However, events for the retry attempts are not seen from event viewer. With this fix, for this specific scenario, the retry events are logged and viewable from WPG event viewer. APAR: JR35184 Description: The acknowledgment and “Message error” for ebms document were under the conversation constraint check for the ebms conversation. This is fixed. APAR: JR35185 Description: During EBMS logging it was seen that some errors in activity logging prevented the ebms state logging to complete. This left some of the transactions in the “in process” state even though they had reached their end state. This has been fixed. APAR: JR35186 Description: There were a lot of duplicate key exceptions seen in the logs while transacting ebms documents. These exceptions used to occur while logging the re-tried documents. This has been fixed. Component: Document manager/EDI APAR: JR35158 Description: Precision problem in double arithmetic was resulting in an unexpected result when the NumFormat function was used in the transformation map. WPG has been corrected to handle this precision problem. APAR: JR33071 Description: WPG failed while handling input ROD which has a field of the data type Binary. The failure was due to BufferOverFlow. This is fixed. APAR: JR34085 Description: The Control number in the GS control Segment in EDI X12 should have a minimum length of 1 and maximum length of 9. Prior to this fix WPG was padding zeroes to bring the length of the GS segment control number to 9, which is not according to the specification. This padding has been removed now. Component: Document manager/RNIF APAR: JR33103 Description: When processing an EDI document to de-envelope and re-envelope, the segment count value for the output document was incorrectly set to 2. This is fixed. APAR: JR33243 Description: For Rosettanet translation of an inbound RN document, if the service content had a non-UTF character, then WPG provides an option of overriding the encoding specified in the service content xml prolog by using the “Generic Pre process handler” on the receiver. This was not working as intended. This has been fixed. APAR: JR33615 Description: The XMLEvent document generated for Rosettanet transactions does not display the “Document ID” and “Document Timestamp" in the console. This has been fixed. Component: Document Manager/SFTP APAR: JR33985 Description: SFTP Destination doesn't overwrite the file at the destination folder if a file with the same name already exists. This is now supported but only on the SFTP Servers which have the Over-write function enabled. Component: EDI APAR: JR35174 Description: Duplicate documents were getting generated by WPG due to problem in locking mechanism used by Enveloper. This was happening in multiple router set-up. This is fixed. APAR: JR35162 Description: Null pointer exception accompanied with "Unexpected Exception Occurred" events (BCGEDICM0001) during inbound 997 processing. This is fixed. APAR: JR35182 Description: In multiple router set-up Enveloper was processing documents without acquiring locks and this was leading to duplicate Envelopes being generated. This is fixed. APAR: JR35165 Description: Failed inbound message when viewed using document viewer, the inbound document does not show the associated 997 when there is a syntactical error prior to EDI transformation. This is fixed. Component: Event engine APAR: JR32826 Description: Certificates expiry related events and alerts were not getting triggered . From this fix pack onwards such events and alerts will be triggered. Users who want to use this fix need to follow the additional steps provided in the below link after applying FP2 http://www.ibm.com/support/docview.wss?uid=swg21414906. Component: Event Processing APAR: JR35179 Description: During WPG document processing on Oracle, the logs show statements for unique constraint violated, when logging WPG generated events, which was misleading as the events were logged properly. With this fix, the unique constraint violated errors are suppressed. Component: Installer APAR: JR35167 Description: The Fixpack Installer fails to install successfully if any user other than bcguser is provided. This has been corrected. Component: Partner Migration APAR: JR33594 Description: Partner migration tool failed to export/import WPG post process exits of destination. This is fixed. APAR: JR33791 Description: In WPG we cannot have two connection having same source credentials. Partner migration was importing data having a connection with same source credentials as already existing and enabled connection in WPG. Instead of enabling/disabling it based on over-write option, it was causing both the connections having same credentials on source side to be enabled. This is fixed. APAR: JR34216 Description: Partner Migration tool failed to export/import the event alerts configured with Partner defined as "Any Partner". APAR: JR34684 Description: Severity level for partner migration logging while importing group permission has been changed from ERROR to WARNING. APAR: JR34798 Description: Partner Migration tool now accepts additional command line input from User to set initial and maximum JVM heap size. Component: Receiver APAR: JR34324 Description: When one 'deletes' a file receiver, without 'disabling' it first, the receiver continues receiving files. Additionally, when one 'disables' a file receiver and when the directory is empty, the receiver removes the directory recursively. This is fixed. Component: Receiver/FTP Directory Receiver APAR: JR33281 Description: FTP Receiver failed when routing EDI documents between external and non-default internal partners. The check on the package and content business ids failed. This is corrected now and FTP Receiver should be able to receive non-Binary documents which are intended for internal partners that are not default to the system. Component: Receiver/FTP Scripting Receiver APAR: JR33432 Description: FTP Scripting Receiver set to poll using a calendar schedule was not working as expected. This is fixed. ===================================================== Notices and trademarks: http://www.ibm.com/legal/copytrade.shtml Terms of use: http://www.ibm.com/legal/us/en/