T24 Core Banking System Implementation

for
SABA African Bank
T24 Training
T24 Operation - Close of Business
Agenda

01 Learning Objectives
02 Introduction to COB
03 Stages in COB
04 The BATCH application
05 Executing the COB Service
06 The DATES application
07 Monitoring COB process
08 Trouble shooting errors in COB
Learning Objectives
Overview of COB

Different stages in COB

Understanding the BATCH application

Executing COB Service

Understanding the DATES application

Monitoring COB and Troubleshooting

Agenda

01 Learning Objectives
02 Introduction to COB
03 Stages in COB
04 The BATCH application
05 Executing the COB Service
06 The DATES application
07 Monitoring COB process
08 Trouble shooting errors in COB
COB - Overview

• COB stands for Close Of Business

• Marks the end of all financial transactions for the day and rolls forward the T24 date to the
next business day

• COB can be run on every working day of the bank

Let’s understand one of the processes done during COB with a simple example
COB – Example
I Need a LOAN TERMS
Loan
Name : Steve
Amount : $50,000
Interest : 10%
Payment : EMI 12 Months
Steve

COB Process Started on Steve

every working day LOAN A/c
EMI
debited
End of
. Daily Month
Interest
Accrual
Steve
Other Savings A/c
Processes
Agenda

01 Learning Objectives
02 Introduction to COB
03 Stages in COB
04 The BATCH application
05 Executing the COB Service
06 The DATES application
07 Monitoring COB process
08 Trouble shooting errors in COB
 Stages of COB
Non-critical reports and
processes . Eg: Jobs to
clean up of temporary Individual application
work files, etc. processes. Eg: Forex,
1-Application
Funds Transfer

Jobs that are common

5-Online
2-System to T24. Eg: Interest
Wide accrual, Interest
capitalization

Generation and
printing of reports. Eg:
4-Start of Day 3-Reporting
Start of day Trial Balance,
operations and date Transaction journal
change. Eg:
Executing standing
orders
 COB – High Level Overview

COB
D000 Completed
Execution of
jobs in
O(nline) O(nline)
A0001 mode in stage
Execution DATES
of jobs in Application
B(atch)
A-S-R-D
mode in
order
DATES
Application
Initiate COB
 Batch Stage

 Stages tell the system the order of execution of COB

A
What?
 Each Batch stage is suffixed with a 3 digit sequence O Batch S
number, between 000-999 . Ex : A000, A100, S000, R099 , Stages
D017 D R
• Each batch record, i.e , a Process, needs to be
Why? executed in a particular order, for COB

• Each Process consists of one or more Jobs that perform

a specific task

• All jobs within a process are executed in the order they

are defined and NEVER simultaneously
 Batch Stage - Illustration

BATCH STAGE

A000 A100 S000 R099

PROCESS 1 PROCESS 2 PROCESS 3 PROCESS 4 PROCESS 5

Job 1 Job 2 Job 3 Job 4 Job 5 Job 6 Job 7

Agenda

01 Learning Objectives
02 Introduction to COB
03 Stages in COB
04 The BATCH application
05 Executing the COB Service
06 The DATES application
07 Monitoring COB process
08 Trouble shooting errors in COB
BATCH Records
• List the processes in your T24 area – BATCH L

Process linked to a Batch stage,

is a part of COB.

Process without a stage, is a service

BATCH – For a COB Process
BATCH – For a COB Process
 BATCH Record – Process Status and Job
Status
Status Codes
0 - Ready
1 - Running
2 - Completed
3 - Error
Process Status And Job Status - Relationship
Update BATCH – Mark Process
Status as Running(0 to 1)
Next batch
record
Job Update BATCH – Mark Job Status
1 as Running(0 to 1)

Job Job Execute Job

Process
4 2
Update BATCH – Mark Job Status
Job as Completed( 1 to 2)
3
Is it last job in the BATCH?

No Yes

Update BATCH – Mark Process

Status as Completed(1 to 2)
Agenda

01 Learning Objectives
02 Introduction to COB
03 Stages in COB
04 The BATCH application
05 Executing the COB Service
06 The DATES application
07 Monitoring COB process
08 Trouble shooting errors in COB
 Execution Of COB – Recap – tSM & tSA

• The entire COB process is controlled by tSM

• tSM acts as a manager and controls all worker processes that
perform COB
• Launches worker processes
• Checks if worker processes are running as scheduled
• If any of the worker processes are dead, launches substitute worker
processes

• The actual COB process is executed by tSAs

• tSA stands for T24 Service Agent (Worker processes)
• Execute the jobs (routines) defined in BATCH record(s)

• tSM and tSA’s are started on the T24 application servers

TSA.SERVICE – For COB

• TSM is a service

• COB is a service

• TSM and COB are pre-configured in TSA.SERVICE application

Steps – Running COB (Phantom Mode)

• Check EB.EOD.ERROR

• Set the field SERVICE.CONTROL to “START” in the records TSM and

COB in the TSA.SERVICE application. Commit and authorise both the
records

• Login to jsh ->

• Type tRun TART.TSM

 Steps – Running COB (Interactive Mode)
• Login to jsh -> and type tRun START.TSM –DEBUG
• Open another session and type “ tRun tSA” followed by the agent
number
Agenda

01 Learning Objectives
02 Introduction to COB
03 Stages in COB
04 The BATCH application
05 Executing the COB Service
06 The DATES application
07 Monitoring COB process
08 Trouble shooting errors in COB
Date Change

• There will be one record per company in the DATES application

• ID of the record will be the company code

 Date Change During COB
1
Initiate COB
2
BATCH Record ID :
UNAUTH.PROCESSING
Batch Stage : A001
Job Name : EB.CYCLE.DATES

3
BATCH Record ID : DATE.CHANGE
Batch Stage : D000
Job Name : B.DATE.CHANGE
4
After the Online Stage is complete, the
NEXT RUN DATE is updated for all jobs
executed today (excluding jobs with
FREQUENCY D and A)
Date Change
• The record in the DATES application that gets created during COB
<Company.Code> – COB, does not get deleted after COB

• The record will exist and will be overwritten during the next COB

• COB doesn’t use the DATES record with @ID <Company.Code> for
processing

• The record <Company.Code> is created and is used by the T24 system

for new transactions coming into the system while COB is running
(Possible only if NS module is installed)
What is the NS module??
Non Stop (NS) Module
• COB supports 24 hours non stop processing
• For this a product named NS (Non Stop) needs to be installed

• When NS is installed, the T24 system will be available for input when COB is
in progress

• It uses the DATES record with @ID - <Company.Code>

• Therefore, all transactions when input during COB, will have the value day as
next working day.
Eg: If we input a FT when COB is running on 22 MAR 2013, the value date for
the transaction will be taken as 26 MAR 2013
Agenda

01 Learning Objectives
02 Introduction to COB
03 Stages in COB
04 The BATCH application
05 Executing the COB Service
06 The DATES application
07 Monitoring COB process
08 Trouble shooting errors in COB
Monitoring COB

• Type COB.MONITOR at the awaiting application prompt from the

classic user interface of T24. Output is auto refreshed
Monitoring COB
Agenda

01 Learning Objectives
02 Introduction to COB
03 Stages in COB
04 The BATCH application
05 Executing the COB Service
06 The DATES application
07 Monitoring COB process
08 Trouble shooting errors in COB
Troubleshooting Errors
• Is there a file where all the errors encountered during COB can be
viewed?
Yes. The name of the file is EB.EOD.ERROR

• The id to a record in EB.EOD.ERROR is <company.code>.<date>

• Eg: GB0010001.20130121

• EB.EOD.ERROR contains one record per company per day running

COB. The details of the individual errors can be found in a file called
EB.EOD.ERROR.DETAIL

• The id to record in EB.EOD.ERROR.DETAIL application is present in

the record of EB.EOD.ERROR
Troubleshooting Errors
Troubleshooting Errors
Troubleshooting Errors

How do we tell T24 that an error has been resolved?

Recap

• COB stands for Close Of Business

• Stages In COB
• Application Wide
• System Wide
• Reporting
• Start of Day
• Online

• BATCH is the application where all the COB jobs are defined.
Recap

• tSM stands for T24 Service Manager

 this tSM is to monitor the tSAs running

• tSA stands for T24 Service Agent

 tSA’s execute the jobs (programs) defined in the BATCH application

• TSA.SERVICE
Recap: How to Start COB?

Step 1: Modify the TSM record (TSA.SERVICE I TSM)

 Set the following field SERVICE CONTROL : START

Step 2 : Authorise the record TSM

Step 3: Modify the COB record (TSA.SERVICE I COB)

 Set the following field SERVICE CONTROL : START

Step 4: Authorise the record COB

Step 5: EB.EOD.ERROR L (Check for any errors)

Step 6: Logout of T24

Recap: How to Start COB? Interactive/Debug
Mode(Cont.)
Step 7: Login to the server where you are going to run COB by typing
TELNET <ip address of the server> at run prompt
 ACCOUNT NAME: <O/S user name>
 PASSWORD: <password set for the above user>

Step 8: Start the Service Manager (TSM)

 tRun START.TSM –DEBUG
manually launch tSA 2 for COB
manually launch tSA 3 for COB
manually launch tSA 4 for COB

Step 9: Start the agent COB. Open another telnet session to the server (like step 7)
 tRun tSA 2

Step 10: Repeat step 9 for the other two agents (tSA 3 and tSA 4)
Recap: How to Start COB? Phantom Mode
(Cont.)

Step 7: Login to the server where you are going to run COB by typing
TELNET <ip address of the server> at run prompt
 ACCOUNT NAME: <O/S user name>
 PASSWORD: <password set for the above user>

Step 8: Start the Service Manager (TSM)

 tRun START.TSM

The TSM will take care of starting all the agents automatically
Recap: How to monitor COB?

• Using the enquiry AGENT.STATUS

• ENQ AGENT.STATUS
• TSA.STATUS L

• Using the tool COB.MONITOR (can run only from T24 classic mode
of navigation)

• Using the enquiry COB.PROGRESS

• ENQ COB.PROGRESS
What Did We Learn?

COB and its different stages

How to execute COB and understand the BATCH application

The changes in the DATES application and its implications

How to monitor and trouble shoot the errors during COB

Thank You

Slide 43