Release notes for IBM Financial Transaction Manager for Corporate Payment Services 3.2.11 Multiplatforms

Content

• Before installation
• Product documentation
• Support
• 3.2.11 Fix pack 1
  • Feature changes
  • Known issues
• 3.2.11 Release
  • Feature changes
  • Known issues
   

  ---

  Before installation

  System requirements

  Check the IBM Financial Transaction Manager system requirements to ensure that your installation platform is supported for the product edition that you plan to install. For more information about the system requirements for all of the different versions of the product, see the IBM Financial Transaction Manager system requirements website.
   

  Downloading the product

  For information about how to download IBM Financial Transaction Manager for Corporate Payment Services for Multiplatforms see the download document for IBM Financial Transaction Manager for Corporate Payment Services for Multiplatforms 3.2.11.

  Back to contents

  ---

  Product documentation

  • Release information (this document)
  • Financial Transaction Manager online product documentation in IBM Documentation
  • Fix list (key defects fixes in this release)
  • Entitled documentation fix pack (download from Fix Central)
  • Resources (for previous releases of this offering)

    

  Data Setup Utility
  The following documentation describes the changes for the data setup utility (DSU) and the import and export workbooks:

  • DSUmigration_v3.2.11.pdf
  • DSUMigrationBR_v3.2.11.pdf

  These documents are provided in the entitled documentation fix pack.

  Database migration
  For database migration instructions, refer to the migration instructions in {Install location}\shared\vnnn\pfs\Database\db2\{os}\doc

  
  Transaction Server Scheduler XML
  The following documentation describes the changes to the scheduler XML for the Transaction Server component:

  • TransactionServerSchedulerChanges_v3.2.11.pdf

  These documents are provided in the entitled documentation fix pack.

  Back to contents

  ---

  Support

  Defects:

  These release notes might contain references to defect numbers. These numbers refer to internal IBM problem numbers that you might find helpful when you are discussing problems with your IBM Support representative.
   

  Technotes:

  For more information about available fixes, see the IBM Support web page.
  To find the information, go to Download - Fixes, updates, and drivers, and then enter the product's name. This web page links the latest maintenance for the in-service IBM Financial Transaction Manager family of products.
   

  Back to contents

   

  ---

   

  Back to top

  3.2.11 Fix pack 1

   

  New features and updates

  Fragmentation

  Fragmentation is when the Gateway Server splits large transmissions into smaller pieces or fragments, that can be processed by the number of threads that are defined in the maxFileThreads property. 

  Fragmentation is controlled by two Gateway Server properties, fragmentStartSize and fragmentSize:
  1. fragmentStartSize (default 10000) is the minimum number of records that must be in a transmission for the transmission to be fragmented. If this property is set to 0, fragmentation does not occur.
  2. fragmentSize    (default 5000) is the number of records that are included in a fragment. If this property is set to 0, fragmentation does not occur.

  An instance of Gateway Server that is processing a transmission that is fragmented cannot process any other transmissions at the same time. It is dedicated to processing that one fragmented transmission. This should be considered as it may impact the time to process other workloads/files through Gateway at the same time as a fragmented transmission.

  The concurrent processing of transmission fragments by all file threads in a Gateway may also result in increased CPU consumption, so consideration should be given to ensure that there is enough CPU available to support all processes/threads on the system.

  
  Fragmentation supports faster processing of large transmissions. For maximum performance, the fragment size should be set to ensure that all Gateway File Threads are utilized. E.g. If maxFileThreads = 10 and a large file has 50000 records, then a fragmentSize of 5000 would result in 10 fragments, one per file thread, ensuring all file threads are utilized.

  Back to contents

  ---

  Known issues

   None

  ---

  Back to top

  3.2.11

   

  New features and updates

   None

  Back to contents

  Known issues

  This section outlines the known issues and their workarounds (if any).
   

  • EDI X12 Processing is not supported in this 3.2.11 release.

  Back to contents

  ---