Close Of Business –
Introduction
TEMENOS EDUCATION CENTRE
NOTICE
These training materials are the copyrighted work of Temenos Headquarters SA and other companies in the TEMENOS group of companies
(The Copyright Owner). The training materials contain protected logos, graphics and images. Use of the training materials is restricted solely for
use by licensed end users, partners and employees. Any un-licensed reproduction by any means, redistribution, editing, transformation,
publishing, distribution, or public demonstration of the training materials whether for commercial or personal gain is expressly prohibited by law,
and may result in severe civil and criminal penalties. Violators will be prosecuted to the maximum extent possible. Such training materials shall
not be represented, extracted into or included in part, or in whole, as part of any other training documentation without the express permission of
the Copyright Owner, which must given in writing by an authorised agent of the Copyright Owner to be valid. Where such permission is given a
clear and prominent notice must be displayed on any and all documentation accrediting the Copyright Owner with having copyright over the
materials. End-user licenses will in no event contain permissions extending the use of these training materials to third parties for commercial
training purposes.
Without limiting the foregoing, copying or reproduction of the training materials in part or in whole to any other sever or location for further
reproduction or redistribution is expressly prohibited, unless such reproduction is expressly licensed by the Copyright Owner.
Copyright © 2010 Temenos Headquarters SA
Objectives
At the end of the session you will have
Adequate knowledge to understand
COB and its Stages
The BATCH application
Executing COB in T24
Date changes in T24
Monitoring
Troubleshooting
Slide 2
COB - Close Of Business
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
Slide 3
Stages of COB
1. Application (A) 2.System Wide (S)
Batch 3.Reporting (R)
5. Online (O) Stages
4. Start of Day (D)
Slide 4
What is a Batch Stage?
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
Why should the processes be executed in a particular order?
Slide 5
BATCH Records
Why is the Bank
Mnemonic a part
of the BATCH
record ID?
Slide 6
BATCH Record
Frequency
-D
- D nn
-W
-M
- M nn
-Y
- Y nn
-A
-SW
-SM
-SY
Slide 7
BATCH Record
Slide 8
BATCH Record
Slide 9
Process Status And Job Status - Relationship
Update BATCH – Mark Process Status as 1
Next batch Running(0 to 1)
record
Update BATCH – Mark Job Status as
2
Running(0 to 1)
Execute Job 3
Update BATCH – Mark Job Status as
4
Completed( 1 to 2)
No
Is it last job in the BATCH? 5
5.1
Yes
Update BATCH – Mark Process Status as
Completed(1 to 2)
5.2
Slide 10
Running COB
Running COB
Slide 11
Execution Of COB
The entire COB process is controlled by tSM
tSM stands for T24 Service Manager
As the name implies, it 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
Slide 12
tSM And tSA - MS
A module called MS(Multi Server) needs to be installed separately if
COB is to be run on Multiple Application Servers
Default thumb rule : No. of tSAs = No. of processors * 2
T24 Application Server 1 T24 Application Server 2
tSM tSM
tSA tSA tSA tSA tSA
Slide 13
TSA.SERVICE - Overview
TSA.SERVICE
TSM is a service
COB is a service
Both services namely TSM and COB are pre-configured in TSA.SERVICE
application
Slide 14
TSA.SERVICE - TSM
Slide 15
TSA.SERVICE - COB
Slide 16
TSA.WORKLOAD.PROFILE – Additional Feature
Slide 17
Review Time In TSA.SERVICE
Review Time
The job of the tSM is to
Read the TSA.SERVICE records with SERVICE.CONTROL field set to
START (COB in our case)
Read the relevant TSA.WORKLOAD.PROFILE records
Check if the required number of agents are actually running
If yes, check to see if they are performing their job
If no, instruct the user to start the required number of agents
Sleep
The sleep time is defined using the field REVIEW.TIME.
Specify the value in the TSM record
Slide 18
Time Out In TSA.SERVICE
Every agent (tSA) is required to tell the tSM (update the manager) that
it is performing the task assigned to it
The tSM is designed to wait for a stipulated amount of time for each
agent to report that it is alive and working
The tSM will term the agent as dead, if it doesn’t get a reply within the
stipulated time.
It will stop the tSA process at the operating system level (kill the
process) and start a substitute process
The time given for every agent to report to the tSM that it is alive and
working is set in the field TIME.OUT (Specify the value in the COB
record)
Slide 19
TSA.PARAMETER
Parameter file
Has only one record – ID is SYSTEM
Slide 20
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 START.TSM
Slide 21
Steps – Running COB (Interactive Mode)
Login to jsh -> and type START.TSM –DEBUG
Open another session and type “tSA” followed by the agent number
Slide 22
Internal Working
Behind the Scenes
Slide 23
COB – High Level Overview
Initiate COB
System mode changed to B(atch) Reflected in the DATES application
Execution of jobs in A-S-R-D order
System mode changed back to O(nline) Reflected in the DATES application
Execution of jobs in O(nline) stage
Slide 24
Date Change
There will be one record per company in the DATES application
ID of the record will be the company code
Slide 25
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)
Slide 26
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??
Slide 27
Non Stop (NS) Module
COB supports 24 hour 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 10 JAN 2010, the value date
for the transaction will be taken as 11 JAN 2010
Slide 28
Sorting of Jobs
tSA 1(TSM)
tSA 2 tSA 3
Am I TSM? Am I TSM?
NO NO
Sort BATCH records Sort BATCH records
Job5, Job7, Job8, Job1, Job2, Job3 Job5, Job7, Job8, Job1, Job2, Job3
Batch Record ID Batch Stage Job Name Frequency Next Run Date
(Process) (Routine)
TODAY
04-Jan-
BNK/ACCRUAL.EOD S001 Job1 D 2010
Job2 D
BNK/STANDING.ORDER.EOD D010 Job3 D
Job4 M 07-Jan-2010
BNK/PL.CLOSE.EOD A005 Job5 D
Job6 A 10-Jan-2010
BNK/FT.EOD A100 Job7 D
Job8 D
Slide 29
Monitoring COB
Monitoring COB
Slide 30
Understanding AGENT.STATUS Output
Enquiry AGENT.STATUS shows the activity of every agent
Slide 31
Understanding AGENT.STATUS Output
…. continuation from the previous screen
Slide 33
Understanding AGENT.STATUS Output
…. continuation from the previous screen
Slide 34
Where Does AGENT.STATUS Enquiry Pick Up Data From?
TSA.STATUS
Only updated by tSM and tSA(s)
Holds the status of all agents
Type TSA.STATUS L to view details in the TSA.STATUS file
Slide 35
Other Ways To Monitor COB
Type COB.MONITOR at the awaiting application prompt from the
classic user interface of T24. Output is auto refreshed
Slide 36
Enquiry - COB.PROGRESS
1 2
Slide 37
Troubleshooting
Troubleshooting
Slide 38
EB.EOD.ERROR
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.20100120
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
Slide 39
EB.EOD.ERROR
Slide 40
EB.EOD.ERROR.DETAIL
Slide 41
EB.EOD.ERROR
How do we tell T24 that an error has been resolved?
Slide 42
Questions
While running COB the agents suddenly stops. What to do?
COB stopped while running, there is no error logged in
EB.EOD.ERROR. On restarting COB, it stops at the same place. What
to do?
Slide 43
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.
Slide 44
Recap (Cont.)
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
TSA.PARAMETER
Slide 45
Recap (Cont.)
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
Slide 46
Recap (Cont.)
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)
jsh r10 ~ -->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)
jsh r10 ~ -->tSA 2
Step 10: Repeat step 9 for the other two agents (tSA 3 and tSA 4)
Slide 47
Recap (Cont.)
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)
jsh r10 ~ -->START.TSM
The TSM will take care of starting all the agents automatically
Slide 48
Recap (Cont.)
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
Slide 49
Quiz
1. The order in which the batch stages in COB runs is A,S,D,R,O – True /False
False
2. SM is a valid frequency that can be attached to a Batch Job in T24 – True /
False
True
3. When there is only ONE Company record defined in T24 the BATCH records for
that company don’t have a Company Mnemonic prefix attached to their IDs –
True / False
True
4. For a Batch job with Daily frequency the NEXT.RUN.DATE field can be left blank
– True / False
True
5. To run COB in interactive MODE use the START.TSM –DEBUG command from
the jshell prompt – True / False
True
Slide 50
Summary
In this learning unit, you learnt about an Introduction to the COB system
You will now be able to understand
COB and its Stages
The BATCH application
Executing COB in T24
Date changes in T24
Monitoring COB
Troubleshooting
Slide 51
Thank You
TEMENOS EDUCATION CENTRE
NOTICE
These training materials are the copyrighted work of Temenos Headquarters SA and other companies in the TEMENOS group of companies
(The Copyright Owner). The training materials contain protected logos, graphics and images. Use of the training materials is restricted solely for
use by licensed end users, partners and employees. Any un-licensed reproduction by any means, redistribution, editing, transformation,
publishing, distribution, or public demonstration of the training materials whether for commercial or personal gain is expressly prohibited by law,
and may result in severe civil and criminal penalties. Violators will be prosecuted to the maximum extent possible. Such training materials shall
not be represented, extracted into or included in part, or in whole, as part of any other training documentation without the express permission of
the Copyright Owner, which must given in writing by an authorised agent of the Copyright Owner to be valid. Where such permission is given a
clear and prominent notice must be displayed on any and all documentation accrediting the Copyright Owner with having copyright over the
materials. End-user licenses will in no event contain permissions extending the use of these training materials to third parties for commercial
training purposes.
Without limiting the foregoing, copying or reproduction of the training materials in part or in whole to any other sever or location for further
reproduction or redistribution is expressly prohibited, unless such reproduction is expressly licensed by the Copyright Owner.
Copyright © 2010 Temenos Headquarters SA
