TSA services debugging in T24 Core Banking

Many times, we encounter issues during the execution of our services in T24. Most of the time, these issues can be easily identified as configuration errors or spotted in our code. However, in other cases, it becomes more difficult to pinpoint the root cause of the problem. That’s why it’s important to know how to debug our services in the environments where we can replicate the error.

This post provides a simple explanation of how to debug our TSA services in T24 using Transact's native commands.

Using a console in the Transact environment, you need to run the main TSM service in debug mode with the command tRun START.TSM -DEBUG (remember not to close this console windows, otherwise the debug mode will end.). This will display all the services that are ready to be executed in the environment.

Take note of the agent number assigned to the service you want to debug. Then, in another console window of the environment, run the command tRun tSA [agentNumber].

This will display in the console all real-time information about the service execution. It is recommended to add printstatements or leave the DEBUG instruction in your code to get more insights into what the service is processing during the debug session.

And with just these steps, you can debug your services from your available Transact environment.

If you want to learn more about how to investigate issues in your T24 core banking system, identify performance problems in your services, and how to resolve them, don’t hesitate to hire our services. At Performetriks, we’ll be happy to help you.

Keep up the great work! Happy Performance Engineering!

#T24 #Temenos #CoreBanking