Fix Readme
Abstract
This document contains the Fix List information for Financial Transaction Manager (FTM) Check for Red Hat OpenShift 4.0.6.
Content
The following table shows the list of available packages for FTM Check for Red Hat OpenShift 4.0.6.
Note: Unless stated otherwise, interim fixes are cumulative and include prior interim fixes.
| V.R.M.F fix list | Download | Build date | Prerequisites |
| 4.0.6.0 | Available through Passport Advantage | 20240323-1631 | None |
| 4.0.6.0-iFix1 | Available through Passport Advantage | 20240521-1526 | None |
| 4.0.6.0-iFix2 | Available through Passport Advantage | 20240808-1946 | None |
| 4.0.6.0-iFix3 | Available through Passport Advantage | 20240808-1946 (same as iFix2) | None |
| 4.0.6.0-iFix4 | Available through Passport Advantage | 20241030-1545 | None |
| 4.0.6.0-iFix5 | Available through Passport Advantage |
20250321-1542 |
None |
| 4.0.6.0-iFix6 | Available through Passport Advantage |
20250805-1331 |
None |
For more information about the issues and changes, see Release Information for Financial Transaction Manager for Check for Red Hat OpenShift 4.0.6.
| Back to contents | 4.0.6.0 interim fix 6 (iFix6) |
|
Fix number
|
Description |
| 15759 |
Document how to connect an RMI client from outside the cluster
FTM Docs has been updated with information on how to connect to the Transaction Server over RMI from outside the OpenShift cluster.
|
| 15897 |
Pre-Allocation Task Failure due to Daylight Savings Time
Scheduled tasks in the scheduler.xml were not running at the specified time after the switch to/from DaylightSavingsTime
|
| 17553 |
Distribution - clean up auto-release file after build exception
Resolves an issue where rebuild of an outbound file results in an error indicating the outbound file already exists
|
| 17871 |
Incoming file failing at the gateway with error 300
Trim error code values before being used as a lookup key against the Business Rules error code map.
|
| 18377 |
Dup detect purge run frequency
The duplicate detect purge task will now run using the correct configured interval.
|
| 18445 |
Dup detect purge rescheduling
The duplicate detect purge task will now properly reschedule after restarting the duplicate detect engine pod.
|
| 18497 |
Exception updating presentment group totals
When updating a presentment group without a currency code attached, an exception can occur, preventing the update of the totals. An OTW can be provided at request by contacting support.
|
| 18503 |
Exception during RMI processing
Resolved a benign exception during RMI processing when comparing classes without a canonical name.
|
| 18882 |
Cancel of Admin Returns items
Cancelling of rejected admin return items is now allowed.
|
| 19226 |
Reviewing duplicate items would stop after the 5th item
Items that were marked as duplicates or not duplicates were not being locked when reviewed by the user. This would cause the query pulling the items to pull the same items again when the user reached the end of the buffer.
|
| 19328 |
Cross-Site Scripting Issue
Removed Transmission ID from Warning Message to eliminate the possibility of Cross-Site Scripting
|
| 19392 |
FTM Liberty core dumps
Liberty core dumps for FTM components are available on the PV shared path. Locations: /<PV Shared path>/debug-data/dumps/<POD_NAME>
|
| 19676 |
Presentment group state race condition
Presentment group-level ITS stanzas utilizing the presentment states will now only fire once.
|
| 19707 |
Unhandled Warning Scenario
Added a Warning Message for situations where no Items are written during the Extract
|
| 19746 |
Event handler messages are not sent because group.condition doesn't match
|
| 21580 |
Image fingerprint mismatch after rotating an image
Resolves an issue where rotating and saving an image could cause fingerprinting issues in distribution.
|
| 21595 |
Use correct ecp type values in TransmittalGenerator
Corrects an issue where the TransmittalGenerator would use an ecp type of "ICL - Forward" and "ICL - Return" instead of its intended "icl" and "iclr"
|
| 21596 |
Remediation Lock Management unlocking
Unlocking dispositioned work from the Remediation Lock Management screen should now ensure the reviewed state is set properly.
|
| 21719 |
Settlement MQ exception handling
When an exception is thrown, such as when work is locked, the message will now be successfully requeued for processing.
|
| 21965 |
ITS image retrieve request failure
Fixed the SQL ambiguity error to retrieve the column from the correct table
|
| 23100 |
SFTP server doc is missing required information
FTM Docs has been updated with additional information on how to connect to the FTM SFTP server from an SFTP client
|
| 23101 |
Distribution - check file build problems
Prevent builds of files that are already released. Resolves the issue where the IZLCH151S message is incorrectly reported. Fixed the issue where empty segments are appearing in a file
|
| Back to contents | 4.0.6.0 interim fix 5 (iFix5) |
|
Fix number
|
Description |
| 13110 |
Add support for configurable termination grace period seconds
|
| 8422 |
CPCS Reset Entry numbers upon restart flag
There a reset upon restart flag introduced ifix4. Per customer feedback changed the default from true to false.
|
| 16019 | Can be combined with 16017 as together they are the complete fix. |
| 16017 |
IIA Suspect Rate increased in 4.0.x, especially for field 3 and 7 matching.
With 4.0.5, a new smart matching algorithm was introduced, which adversely affected the match rate and escape rate. This has been fixed in this release and has a new operating point. Most customers will need to run production-like work to establish the impact to them and tune their systems to this new operating point. The former default values of 70% may need to be tuned higher or lower to have the system reduce false positives and reduce the number of IIA Suspects escaping detection. Be sure to use the updated SaveAnalysisResults.java user exit, which reports details of the matching and scoring.
|
| 16232 |
The SaveAnalysisResults.java code dropped records from the results file.
The sample user exit for writing reports now supports maxFileThreads on the Gateway of more than 1, as well as iqaThreads of more than 1 (although setting this to 1 gives results in a consistent order). It also now demonstrates some simple codeline manipulations that can be used to reduce the number of false positive suspects dramatically.
|
| 16018 |
The Gateway native code experienced a buffer overrun that could cause the Gateway POD to go down, crash, or otherwise behave irradically.
The buffer overrun was corrected, and the Gateway is more stable. This occurred when items with more than 1 pad bit per scan line (so anything not on a multiple of 8 bits) were processed. It also caused codeline recognition to fail and impacted the ability to perform IIA.
|
| 12982 |
The entire ca.crt certificate chain is not being imported into the FTM truststore.
If the FTM CA certificate contains a certificate chain, then every certificate in that chain will be imported into the FTM trust store.
|
| 13433 |
The default user id of the SFTP pod might get changed if the pod restarts.
In order to prevent the default user ID from changing in the SFTP pod, the user should set the default user ID in an SCC and associate that SCC with the FTM service account.
|
| 16344 |
The ACE JDBC Provider configuration has a syntax error when TLS is disabled to the database.
The syntax error in the ACE JDBC Provider configuration that occurs when TLS is disabled has been fixed.
|
| 15759 |
FTM documentation does not explain how to connect an RMI client to the transaction server from outside the OCP cluster.
Documentation was added to address this scenario.
|
| 12083 |
Restarting FTM pods can impact transactions in progress and require manual intervention.
This issue has been mitigated in that customers can set a longer termination grace policy for the FTM pods to give them time to finish processing active transactions before they are terminated.
|
| 14341 |
FTM documentation does not explain how to install the prereq cloudpak operators in an airgapped environment.
Users who install the prereq cloudpak operators in an airgapped environment must follow the documentation of those operators when doing so.
|
| 15349 |
An error message is shown on the inbound gateway pod saying duplicate port 2005 in use.
This error has been fixed. The pod does not use duplicate container ports anymore.
|
| 16424 |
TCR Default Amount Usage Configured by Adjustments Type
If the adjustment type has a default amount configuration based on the adjustment code, it should use such an amount instead of the out-of-balance amount.
|
| 17333 |
TCR Duplicate Adjustments
A race condition existed that could apply adjustments twice with two or more TCR engine pods configured.
|
| 17334 |
Large batch cancellation
Improved performance when cancelling a file with a large number of payments in a single batch
|
| 17515 |
TCR Adjustment entry auditing
If multiple users touch a newly inserted item, ensure the adjustment entry only credits the final user.
|
| 15761 |
Entry allocation race condition
Resolved a validation race condition that could occur with multiple entry allocations running at the same time.
|
| 15729 |
Duplicate Detect database data loading
Will now prevent work from going into the dup detect database if the presentments have already been marked as duplicate detected.
|
| 16654 |
Hide image review properties descriptions
You can now hide the descriptions of the image review properties.
|
| 17633 |
Validation results version copying
Custom code applying payment updates can now specify that all error codes are copied to the newly created version.
|
| 15166 |
Error Categories to Error Codes hyperlink
The error codes hyperlink on the error categories screen now properly filter the error codes screen.
|
| 17337 |
Duplicate detect database unloading with migration server
Respond to a request in 3.0.X that we have successfully unloaded work from the duplicate detect database.
|
| 16369 |
Dynamic duplicate detect ordering properties
Dynamic duplicate detect ordering and sorting properties will now be displayed without issue on the properties page.
|
| 15749 |
Image review work unable to progress
Image review work will now be able to progress through the system without having to be loaded in payment repair.
|
| 16356 |
Transaction server RMI Connection release
Ensure that transaction server database connections are released, even if experiencing specific connection issues.
|
| 15470 |
Email alerts missing columns
Ensure the subject and distribution list columns are visible on the Email alerts page.
|
| 16047 |
Payment Repair '.' hotkey not working
Ensure that the '.' hotkey can be used to fill the focus field.
|
| 13534 |
Settlement cutoff date description column
The description column will now display its full name.
|
| 16209 |
Payment Repair and Image Compliance logging
Reduced the log level of a few logs to tracing instead of info.
|
| 14501 |
Transmission message type correction
For ICL files, the transmission message type will now be icl instead of image.
|
| 12933 |
CPCS Imported filter on Batch screens
The CPCS Imported filter now has valid filter options on both batch screens.
|
| 15472 |
Improve component cleanup
Improved cleanup of component data when servers are not given sufficient shutdown time
|
| 18179 |
Image retrieval from a 3.0.5.4 iFix5 system
|
| 15398 |
Critical/high CVEs in catalog and operator image
Resolved critical and high-severity CVEs affecting the catalog and operator image
|
| 15149 |
Unable to locate Images when running VP Task
Files will now be moved to correct locations
|
| 15213 |
Difficult for user to correlate Work ID with Presentment
Added Presentment info to Task Comments
|
| 17467 |
Image Files not found for VP Task
Files will now be moved to correctlocations
|
| 17471 |
Filter not working for Dup Detected column
The
Column Filter was updated so that it will now filter correctly
|
| 17871 |
File ingestion failing
Trim error code values before being used as a lookup key against the Business Rules error code map.
|
| 15421 |
Unable to connect to Transaction Server via RMI from client application.
Allow a client application to utilize SSL for RMI communications to all JSE servers.
|
| 15443 |
Connecting Transaction Server using RMI from outside of OpenShift
Allow a client application to communicate Transaction Server using the RMI protocol from outside of the OpenShift cluster
|
| 15333 |
Timestamp always uses the UTC in the physical transmission's error section.
The timestamp must be converted to the user's time zone as other timestamps are already. This eliminates inconsistency of the timestamp value while Gateway File Status is being processed.
|
| Back to contents | 4.0.6.0 interim fix 4 (iFix4) |
|
Fix number
|
Description |
| 8422 |
The user cannot select whether to regenerate the entry number upon restart
When restart (different from manually run) "CPCS Extract task", the task regenerates the entry number. There is no configurable parameter to determine whether to regenerate the entry number.
|
| 12872 |
Improved query during distribution
Added filtering on an index to a query used during distribution for improved performance.
|
| 12873 |
Incorrect zooming applied to images after clicking on Finalize All
An update was made that allows the users to see the correct image after clicking on the Finalize All button
|
| 12874 |
Fixed Dup Detect for Images on older ITS Servers
Fixed an issue where 4.x Dup Detect used a different datatype than 3.x ITS Servers when evaluating Item information.
|
| 12875 |
Updated Payment Repair to show correct information when re-editing a pending repair
If the user cancels finalizing the last item, the MICR data for the final item will no longer reset to its original values.
|
| 12876 |
Updated ibmClientType for Business Rules
Customer will see 'TCR Reconciliation' as their ibmClientType within their downstream code and workflows.
|
| Back to contents | 4.0.6.0 interim fix 3 (iFix3) |
| Back to contents | 4.0.6.0 interim fix 2 (iFix2) |
|
Fix number
|
Description |
|
C-152006 |
Outbound Gateway adds the '.dat' extension when archiving a file when using a custom extension |
|
C-151989 |
Inbound Physical Transmission detail screen becomes unavailable |
|
C-151882 |
Inbound Transmission Hierarchy screen fails to render batch |
|
C-151803 |
Gateway lock files not being removed |
|
C-151755 |
File contains no cash letters and cannot be expedited |
|
C-152339 |
Gateway Server was not loading the any .xlsl or .xslt files from PV to classpath for outbound email transmission: |
|
C-152338 |
BdayActivationTask does not support an interval of 0 |
|
C-152335 |
Orphaned GW_SORTER_LIST records |
|
C-152307 |
Component table not properly cleaned up |
|
C-152262 |
Suspect_reviewed_ID not filled in with the Image Review operator |
|
C-152260 |
NullPointerException processing return files |
|
C-152159 |
Transaction Balancing Insert dialog not displaying full image |
|
C-152093 |
Inbound Physical Transmission stuck in Arrived
During a DB2 failure, incoming files may get stuck in the Arrived state and not will be corrected with the resync process. |
|
C-151763 |
SQLCODE=-530 Error On Insert to OUTBOUND_TRANCHE table in Distribution |
|
C-9722 |
Service engine pod can't access DUPDETECT_DB_PASSWORD. When a check solution is deployed, the service engine pod is unable to access DUPDETECT_DB_PASSWORD. |
|
C-9937 |
Image Review creates an extra entry in the ICRE extract. Image review incorrectly updated the version of payment when tracking updates to MICR fields. Since the image does not update those fields, the extra item in the ICRE extract was incorrect. Image review has been fixed so that the extra versioning is not happening. |
|
151767 |
Batch rejected after doing DB2 failover with no reason given. |
|
151811 |
Issue when overriding a file (or batch) using "Accept" with revalidation After file (or batch) ingestion, if an error occurs (example: duplicate file/batch); if you try to override the file/batch using "Accept" with revalidation, then items in this file are marked incorrectly with the validation error flag. |
|
5151585/6022 |
A Db2 Pod restart (failover) during ingestion, may cause some ingested files to be flagged as duplicaes |
|
152023 |
Metering Service fails to upload usage details
The following metering service alert can be caused by an issue with the NetworkPolicy configurations. FTMMT013S: Unknown exception while trying to upload usage details to the license server metric upload service. Please check the log for details.
If the metering pod logs show "javax.ws.rs.ProcessingException: java.net.SocketTimeoutException: SocketTimeoutException" in the ibm_stackTrace field, then the issue is likely caused by the FTM NetworkPolicies preventing communication with the ibm-common-services namespace.
|
|
151995 |
Issue with Cognos Reports where Database view GET_OPERATIONAL_TZ_TIME_NOW_V is improperly created by the FTM operator
Db2 produces the following error when view FTMPUB.GET_OPERATIONAL_TZ_TIME_NOW_V is accessed by Cognos Analytics reports for a database built by the FTM operator: SQL Error [42724]: Java stored procedure or user-defined function "FTMPUB.J_GET_OPERATION", specific name "GET_OPERATIONAL_TZ_TIM" could not load Java class "com/ibm/fxh/base/util/ud", reason code "".. SQLCODE=-4304, SQLSTATE=42724, DRIVER=4.26.14
|
|
152304 |
Setting the environment variable TZ in the FTM operator yaml file is not working for j2se pods |
|
8083 |
FTM operator is ignoring the spec.scheduling configuration User is not able to set spec.scheduling to configure the OpenShift scheduling for FTM pods. |
|
8100 |
“oc explain” command not working for FTM CRD The user is unable to run the “oc explain” command to get a description of the fields in the FTM CRD. |
|
9131 |
The user is not able to mount custom volumes in FTM pods. A user cannot mount custom volumes, such as config maps, secrets, PVCs, or other types of volumes, into any of the FTM pods. |
|
9597 |
The FTM operator ignores the exclude clause once the FTM instance is deployed. Once FTM is deployed, the FTM operator ignores the init container exclude clause. If a user adds a pod to the exclude clause, the FTM operator will not remove the init container from that pod. |
|
9603 |
Users cannot scale down individual pods after deployment. Users cannot scale down individual pods after deployment. If they try, errors show up in the FTM operator log. |
|
9712 |
Unable to customize FTM pod security context. Users are not able to customize the security context for FTM pods. For example, it is not possible to specify the uid or gid that the FTM pods run as. |
|
9721 |
FTM documentation erroneously includes quotes around the values in the sample vars.env file. The values in the vars.env file must not be enclosed in quotes. The FTM documentation erroneously includes quotes around the sample vars.env file. |
|
9778 |
FTM instance status stays as Ready when the user makes updates to the instance. When FTM is deployed and the operator has finished reconciling the custom resource, the CR's status changes to "Ready." If the customer updates the CR again, the status stays as Ready. Once the instance is reconciled, the status should change to NotReady and then back to Ready. |
|
10057 |
FTM web-server is not getting TLS secret from the external vault. If the user is getting the TLS certificates from an external vault, then the artifacts web server needs to configure TLS with those certs. Currently, it only configures TLS with certificates from OpenShift. |
|
152304
|
Setting the environment variable TZ in the FTM operator yaml file is not working for j2se pods
|
|
152095 |
Updated AdjustmentRuleUtility.getAdjustmentRule(long,long,short). There is a line of code where we retrieve the user default value for the insert amount, but we weren't passing the configured default amount to the method, so it wasn't recognizing the need to use the configured default amount instead of the current amount. |
| Back to contents | 4.0.6.0 interim fix 1 (iFix1) |
| Fix number | Description |
| 151092 |
Backup and Restore process using restore scripts have a known issue while executing.
While executing the script 'ftm-backup-restore-config-map.sh' during the Backup and Restore process, the following error appears: configmap "ftm-inst-licensing-upload-config" deleted Warning: resource configmaps/ftm-inst-licensing-upload-config is missing the kubectl.kubernetes.io/last-applied-configuration annotation which is required by oc apply. oc apply should only be used on resources created declaratively by either oc create --save-config or oc apply. The missing annotation will be patched automatically. Error from server (Conflict): error when applying patch: {} Resource: "/v1, Resource=configmaps", GroupVersionKind: "/v1, Kind=ConfigMap" Name: "ftm-inst-licensing-upload-config", Namespace: "hadr-setup1" for: "/tmp/temp-configmap-restore/ftm-inst-licensing-upload-config.yaml": Operation cannot be fulfilled on configmaps "ftm-inst-licensing-upload-config": the object has been modified; please apply your changes to the latest version and try again NAME DATA AGE ftm-inst-licensing-upload-config 2 5s |
| 150882 |
Fixed the following Gateway server crash situation with TIFF image
The gateway server crashes when TIFF Corrections are disabled and an item is presented with an invalid tag type on the StripByteCounts tag. |
| 151423 |
Unable to load different jar files to the gateway-server and Business Rules Servers (BRS) containers, which are deployed on the same POD using a secure vault. When the secure vault is integrated with FTM, the jar files in the BRS container should get loaded from /shared/lib/brs and not from /shared/lib directory.
|
| 151122 |
4060 iFix1 has replaced "cloudctl" with "ibm-pak" which means the AirGap warning message seen in the 4.0.6.0 GA release no longer appears.
|
| 151666 | Distribution Replica Bundle Build Error A null pointer exception is reported when building replica outbound bundles |
Was this topic helpful?
Document Information
Modified date:
18 August 2025
UID
ibm17129570