top of page

Real-Time T24 COB Monitoring With Fast-Pack

Writer: Josef Mayrhofer
Josef Mayrhofer
Nov 14
2 min read

Manual T24 Close of Business (COB) monitoring is challenging. It requires switching between multiple applications, keeping countless tabs open, and constantly checking what is happening.


Our T24 Fast-Pack service gives you a single COB reporting dashboard for all your monitoring activities. In this blog, we will learn how to identify if COB is having an issue.


The dashboard brings every possible issue together in one place. In the example below, it has flagged a COB issue, which can come from one of three main sources.



  1. EB.EOD.ERROR:


Most common COB issues are logged in EB.EOD.ERRORS. Rather than digging through EB.EOD.ERROR mid-run, COB operators get a clear view of both historical and current errors in one place, allowing for easy problem identification.


In our example, an error occurred in the latest COB. The

dashboard captured it immediately and changed the COB status to “COB ISSUE.”




  1. Failed JOB in the COB

In the T24 COB, jobs run sequentially. We get the details of currently running jobs, and also, in case there is an error in the job, we will display the JOB with:


  • Error

  • Batch details

  • COMO details

  • Last message

  • Last contact

  • The agent causing the issue

  • A link to view the COMO file in Dynatrace



We can also check which stage of the COB the JOB is stuck in; we can clearly monitor the stages as well.



  1. Stalled Jobs


In this, we check jobs that have been hung or stuck for more than 30 mins, fetch complete details (JOB name, BATCH name, COMO details), and trigger an alert that the job has had no progress for more than 30 mins. You can also change the time to 10 mins so we can monitor job progress in a single dashboard.


A JOB might get stuck because of a CPU or memory issue, or simply because of an issue with the JOB itself. With every detail shown on the dashboard, operators can quickly pinpoint what caused the COB to stop.



The workload profile details are being displayed. Running the COB with more agents than usual increases CPU usage and slows performance across all agents, so monitoring this is important.



To check total T24 health while COB is running, we have a dedicated dashboard that shows all the details, problems, and errors. Memory and CPU spikes.



To determine the COB status, the dashboard combines all of these checks: EB.EOD.ERROR entries, failed jobs, stalled jobs, and system health. If any one of them detects a problem, the status changes to “COB ISSUE.” The operator can then see exactly which check was triggered, what the issue is, and resolve it right away.


The T24 Fast-Pack dashboard replaces multiple applications and tabs with a single view that flags COB issues and shows exactly what caused them.


Ready to simplify your COB monitoring? If you would like to learn more about our Fast-Pack dashboard, contact Performetriks today, and our experts will be glad to help.

Happy Performance Engineering! #T24 #FastPack #CoreBanking

Comments


bottom of page