CLOSE OF BUSINESS

Close Of Business
1

CLOSE OF BUSINESS

Introduction to COB
Stages in COB
EOD and COB
Features in COB
Configuring COB

Close Of Business
2

INTRODUCTION
In T24, Batch Processing is handled by the
Close Of Business (COB).
Marks the end of all financial transactions for a
day.

Close Of Business
3

COB STAGES

Application wide - Individual application process

System wide
- System wide process
Reporting
- Main system reports
Start Of Day
- Change Date
Online
- Any non critical reports and
processes which can be run after the system
has returned to online mode
Based on this order the close of business runs
various processes.

Close Of Business
4

COB HIGH LEVEL OVERVIEW

INITIATE COB
System mode changed to
Batch
Execution of jobs in
A-S-R-D order
System mode changed back to
Online
Execution of jobs in Online stage

Close Of Business
5

EOD and COB

During EOD, no user is allowed to input any
transaction.But in Close of Business(COB) ,it is
facilitated through a module called Non-Stop
module.
In case of an error during EOD the whole process
stops. But in COB, the error will be entered in
EB.EOD.ERROR and the process would continue.

Close Of Business
6

Date Changes
There are a number of tasks that get executed
as a part of the COB process. The date change
is the most crucial one.
Company Code

Today

Next Working
Day

Last Working
Day

US0010001

14th July 2004

15th July 2004

13th July 2004

US0010001-COB

13th July 2004

14th July 2004

12th July 2004

Close Of Business
7

Dates Record during COB process

Job Name
Batch Stage

:EB.CYCLE.DATES
: A000

This is the first job to get executed as a part

of the COB process. It will cycle the dates for the
online user.

Close Of Business
8

Dates Record during COB process

Job Name
Batch Stage

:DATE.CHANGE
:D000

This will cycle the date for the COB process

only, since the dates have already been cycled
for the non-COB sessions.

Close Of Business
9

Dates Record during COB process

Job Name
Batch Stage

:BATCH.DATE.RESET
: O999

This job changes the next run date.

Close Of Business
10

FEATURES OF COB
COB can be run with the users signed
on.
Background/Foreground modes
All jobs are Multi threaded
Como is created for each service agent
List file is for selected records to be
processed.
Close Of Business
11

CONFIGURING COB

TSA.SERVICE
TSA.WORKLOAD.PROFILE
TSA.PARAMETER
TSA.STATUS

Close Of Business
12

TSA.WORKLOAD.PROFILE
TSA.WORKLOAD.PROFILE, defines the
number of agents, which should be launched to
support the service.
ID
- Anything
AGENTS.REQUIRED
- Number of tSAs to
dedicate 0-N

Close Of Business
13

TSA.WORKLOAD.PROFILE
The maximum number of agents that will be supported is mentioned in the SPF

Close Of Business
14

TSA.WORKLOAD.PROFILE
The number of tSA to be dedicated would be
specified in AGENTS.REQUIRED field

Close Of Business
15

TSA.PARAMETER
This file enables the tSM to monitor the tSAs at fixed
intervals of time
This is done by two important fields
REVIEW.TIME
Specifies the number of seconds the tSM will sleep
before reviewing the tSA.SERVICEs,
DEATH.WATCH
Specifies the maximum number of seconds allowed
for an agent to report to the tSM.

Close Of Business
16

TSA.PARAMETER

Close Of Business
17

TSA.SERVICE
To initiate a COB, record TSM in TSA.SERVICE
needs to be started

Close Of Business
18

TSA.SERVICE
To initiate the COB service, the record COB in TSA.SERVICE has to
be marked for Starting.

Close Of Business
19

TSA.SERVICE
After marking service control as START
for TSM and TSA , open necessary
sessions.
One session for TSM and required no of
sessions for TSAs depending on agents
specified in TSA.WORKLOAD.PROFILE.

Close Of Business
20

TSA.SERVICE
From the jsh prompt initiate TSM using
jsh ---- > START.TSM DEBUG
This will prompt you to manually launch
tSAs with agent number.

Close Of Business
21

TSA.SERVICE
From the jsh prompt initiate TSM using
jsh ---- > tSA 2 -DEBUG
This will start tSAs and COB as well.

Close Of Business
22

TSA.STATUS
This file shows the status of the agents
AGENT............. 1
-----------------------------------2 AGENT.STATUS...... STOPPED
3 LAST.CONTACT...... 23:05:54
7 LAST.MESSAGE...... 0
8 COMO.NAME......... tSA_1_1352482673
9 JOB.PROGRESS...... 0

Close Of Business
23

LIST FILES
Every job during the Close Of Business uses a
LIST file for storing and sharing the records for
processing between different agents.
Name of the List file have format like this
F<company mnmonic>.JOB.LIST.<agent no>
Example:
FBNK.JOB.LIST.1

Close Of Business
24

COMO
The Como will be written with the session no to
distinguish processing
The Como will be written with the key as
tSA_<agent no>_datetime

Close Of Business
25

MONITORING COB
Enquiry JOB.PROGRESS helps in monitoring
the progress of COB
It gives the details for each job (Start time, End
time, Records processed and Records selected
and time taken for processing each record)

Close Of Business
26

ERROR HANDLING
If an error occurs, it displays the error message
with the process name and job name.
In case of less severe errors, updates the record
for the current batch run and the current
company on the EB.EOD.ERROR file and
continues.

Close Of Business
27

ERROR HANDLING
The details of these errors can be found be
examining the records of
EB.EOD.ERROR
EB.EOD.ERROR.DETAIL

Close Of Business
28

SUMMARY
COB can be initiated with users signed on.
It is controlled by TSM and TSAs.
TSA.SERVICE is the application used for setting
START for services.
After Configuring Service profiles , COB can be
initiated from jsh prompt.

Close Of Business
29