How to Manage Services in T24

Managing services in T24 isn’t just a technical task—it actually shapes how well the system runs. Services are basically collections of jobs scheduled to run in a specific order. You decide when they start, set schedules, run them automatically, and shut them down when they’re no longer needed.

Before Starting the Service

Before you kick off a service, make sure you understand how jobs inside it finish. Usually, each job updates its JOB.STATUS to 2 once it completes, and the next job takes over. When all jobs hit status 2, the PROCESS.STATUS for the whole service flips to 2 as well. It's a clear sign everything’s done. So, setting up jobs and services correctly matters a lot.

If you leave services running when they’re not needed, they’ll keep chewing up CPU and memory. This is especially true for AUTO mode services. If there’s nothing for them to do, the good ones barely use any resources—they just sit quietly, waiting. But if you forget to stop them, even idle services can start draining the system.

During COB (Close of Business), it’s critical to stop services at the right moment. You do this by setting OPERATION.MODE to STOP in TSA.SERVICES.COB. If you don’t, agents for those services keep launching and churning away until COB hits a certain stage. That means extra processing you probably don’t want—and your system slows down right when performance matters most.

So, stop services you aren’t using by updating OPERATION.MODE to STOP in TSA.SERVICES.COB, then let COB finish. You’re saving resources and avoiding the headaches that come with bloated performance.

Services in Auto Mode:

AUTO mode services are what they sound like—once you set SERVICE.CONTROL to AUTO in the TSA.SERVICE record, the system handles the rest. These services run on their own, tackling tasks as they pop up without anyone manually starting or stopping them. They’re perfect for background jobs or tasks triggered by system events.

Issues with Services in Auto Mode:

AUTO mode isn’t foolproof. If a service is designed well, it idles gracefully when there’s nothing to do, barely touching CPU or memory. If it's designed badly, though, it gets stuck in a loop—constantly checking for work, burning CPU for no reason. You’ll notice it in high CPU usage even when tasks are missing. That’s a sign you probably need to review the code or fix the wait logic.

Monitoring tools help a lot here—keep an eye out for whether the service is actually waiting or just spinning its wheels. Efficient waiting means stable CPU and memory, even when tasks are scarce.

Why is it Recommended to Restart the Auto Services after a Few Days?

Restarting AUTO services every few days isn’t just advice—it’s almost a necessity. The main reason is log size. All the logs pile up in a single COMO file if you let a service run non-stop, and these files balloon over time. That can cause disk space headaches and make logs harder to manage. Stop and restart the service now and then; each restart creates a fresh COMO file, making life easier.

Some AUTO services never stop, so you have to restart them manually to shake up the environment and keep logs clean. So, restart regularly—it helps prevent performance drops, keeps logs manageable, and makes sure AUTO services don’t trip over themselves.

Service Cleanup and TSA.SERVICES.COB Details

If things go sideways—say a service hangs, crashes, or you had to reboot a server—it’s cleanup time before restarting. Clear job lists, unlock records, check TSA status, and so on. You don’t want leftover junk causing more issues.

The TSA.SERVICES.COB table is where you set all this up for COB. It tells the system which services to start, stop, or run in AUTO mode as COB moves through its stages. Review it often. See what's running, spot what's idle or useless, and shut down those you don’t need. It keeps your COB processing lean and efficient.

Monitoring Services in Dynatrace

With our Fast-Pack services, you don’t have to worry about a thing. It keeps an eye on everything when services start, how long they've been running, job status, last contact, the latest updates, and all your COMO details. Even the COMO logs show up in Dynatrace. Plus, if there’s a sudden spike in CPU or memory, you’ll spot it right away.

We helped the banks identify and organize service management. If you would like to learn more about our T24 Fast-Pack services, feel free to contact Performetriks today. We are always happy to assist!

Happy Performance Engineering!