Things to be considered when you parametrize T24 Core Banking for high volume Clients
The good old saying that we unlock our greatness by working on the hard things is true for our personal development and T24 core banking systems. Of course, like in any complex system, we have thousands of tuning options. But, the science, or some call it art, in our business is really to find the optimal balance that brings out the best system performance and throughput of your Core Banking engines.
What are the technical and functional aspects in T24 where we can implement some changes to improve performance?
Let's start by sharing some functional changes to speed up the performance of your core banking system. Mainly we are talking about the parameter tables.
PGM.FILE
Its main intention is to control the processing times. For instance, we have ADDITIONAL.INFO, which defines batch program behaviors and is crucial for excellent response time and thought. In addition, the BULK.NO parameter specifies the number of records a Job can select in bulk.
AC.STMT.PARAMETER
For many of our customers is, the duration of their COB processing the most important T24 KPI. They do everything to keep this time short. One option is the set INTEREST.SCALE and TAX.ADVICE to NO. The advantage of this adjustment is that INT.STMT.AND.ADV report is much faster and reduces COB processing times dramatically.
DESKTOP.PARAMETER
Your internal and external users don't like slow-loading T24 queries. One option to improve the response times of your enqueries is to set the DESKTOP. PARAMETER ATTRIBUTES field to null. This configuration reduces the IO activities dramatically and enhances user experiences because screens load faster.
ACCOUNT
Your high-volume accounts need special attention. First, make sure that they are configured with sub-accounts but, at the same time, set the field MAX.SUB.ACCOUNT to 99 for best performance.
AC.ENTRY.PARAM
Record locking can slow down your entire Core Banking system. Some transactions and fields are incredibly vulnerable to spending too much time in locking. Therefore, ensure that fields CONTRA.CCY and CONTRA.ACCT is set to null because this avoids locking of internal account records. In addition, set the field ACCOUNTING.MODE to SAO so that overrides raised on accounting entries will not stop the processing OFS messages.
USER
Logging can help identify some problems, but keep in mind that a production environment can slow down your system. Stop the logging of events to PROTOCOL by changing the following
USER.ID........... OFSUSER
25 SIGN.ON.OFF.LOG... NO
26 SECURITY.MGMT.L... NO
27 APPLICATION.LOG... NO
28 FUNCTION.ID.LOG... NO
There are several more parameters a performance engineer should adjust when he is tuning T24 Core Banking systems. We will offer a workshop about this topic soon to explain all T24 tuning tricks to our customers.
Most relevant are the following parameter:
1. PGM.FILE
2. ACCOUNT.PARAMETER
3. AC.CONSOLIDATE.COND
4. CONSOLIDATE.COND
5. SPF
6. OFS.SOURCE
7. AUTO.ID.START
8. PM.AC.PARAM
9. PM.POSN.CLASS
10. AC.STMT.PARAMETER
11. EB.EXTRACT.PARAMETER
12. DESKTOP.PARAMETER
13. FT.TXN.TYPE.CONDITION
14. ACCOUNT.STATEMENT
15. ACCT.GROUP.CONDITION
16. ACCOUNT
17. AC.ENTRY.PARAM
18. USER
19. ACCOUNT.ACCRUAL
20. PM.PARAMETER
Don't hope that the best infrastructure will automatically bring the best Core Banking performance. Unfortunately, we know many customers who were running into this trap. After sharing the following simple steps, their T24 performance problems started to disappear:
Observability first
Make performance everyone's job
Implement functional and technical tunings
Performance validation of every change
We are specialized in Core Banking performance optimization and serve customers worldwide. Please contact us to learn how we can make your performance dreams come true.
Happy Performance Engineering! Keep up the great work!