Welcome to the Close of Business learning unit.

In this session you will understand the

basic concepts around which T24’s COB process works.

COB1.Close Of Business - Introduction-R10.01 1

 At the end of the session you will have

Adequate knowledge to understand

1. COB and its Stages

2. The BATCH application
3. Executing COB in T24
4. Date changes in T24
5. Monitoring COB
6. Troubleshooting

COB1.Close Of Business - Introduction-R10.01 2

 1. COB stands for Close Of Business
2. COB marks the end of all financial transactions for the day and rolls forward the T24 date
to the next business day
3. 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

Steve has taken a loan from a bank at a 10% rate of interest, payable back to the bank in a
year. This amount will be paid by him in 12 monthly installments. The bank would like to
keep a daily track of the interest amount they are due to receive from Steve at the end of the
month. So, they calculate the amount payable by him everyday. This is done to keep the
Profit and Loss/Balance sheet current. Now, this is just for one customer. Imagine the bank
has given 100,000 loans with different interest rates for different periods of time to
individuals like Steve. It’s an arduous task for the bank to do the whole process manually.
So, they automate it. However the amount payable to the bank need not be calculated
during normal working hours of the bank (because they will be busy doing other day to day
activities of the bank). So they do it at the end of the day. The process of calculating the
interest payable, but not yet fallen due for payment, is called Accrual. Therefore, accrual is
one of the processes that is done during T24’s COB (Close of Business)

COB1.Close Of Business - Introduction-R10.01 3

 COB runs in five stages, A-S-R-D-O

A stands for Application stage. It involves all the individual application processes. Eg: Forex,
Funds Transfer, etc.

S stands for System Wide stage. It involves jobs that are common to T24. Eg: Interest
accrual, Interest capitalization

R stands for Reporting stage. It involves generation and printing of reports. Eg: Trial
Balance, Transaction journal etc.

D stands for Start Of Day stage. It involves all the start of day operations and date change.
Eg: Executing standing orders etc.

O stands for Online stage. It involves any non-critical reports and processes which can be
run after the system has returned to online mode. Eg: Jobs to clean up of temporary work
files, etc.

COB1.Close Of Business - Introduction-R10.01 4

 1. Each Batch stage is suffixed with a 3 digit sequence number, between 000-999, which will
tell the system the order of execution of COB e.g. A000, A100, S000, R099 etc.,
2. A Batch Stage consists of one or more processes. In T24, these COB Processes are
defined in an application called BATCH
3. 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. For E.g. In
the diagram that you see, Job 2, will never get executed before Job 1 is complete, so on
and so forth.

Why should the processes be executed in a particular order?

As a continuation of the previous scenario of accrual, it is time for Steve to make his first
installment of monthly interest. The bank has been calculating the interest everyday and
on that day they know the exact amount payable by Steve. The calculated interest
amount is now accounted as due for payment and is called Interest Capitalisation. Steve
should now arrange to pay through his bank account/cash/card/cheque etc., to the bank’s
account. Till yesterday, what the bank was doing was calculating the amount receivable
from Steve and not actually taking the money from him. Multiply the same work to be
done for hundreds of loans amount being repaid . As said earlier, it’s an arduous task to
keep track of this everyday so we automate the process and reserve it for end of the day
activities. Therefore, Interest Capitalisation is also one of the processes executed during
T24’s COB.
Now, lets try to answer this question
Q. Should I do Interest accrual first and then Interest Capitalisation, or vice versa?
A. The obvious answer would be first interest accrual and then interest capitalisation
otherwise the math would never be correct.
Therefore all the processes, or to be more specific, all jobs are executed in a specified order
during COB.

COB1.Close Of Business - Introduction-R10.01 5

Slide 5

SG5 Explain the concept of Interest accrual and Interest Capitalisation.

Once you have explained the concept of -"Why should the processes be executed in a particular order?",
ask the trainees - "Which batch stage should we do accrual and capitalisation in?" The answer is Batch
Stage "S" i.e. system wide (because accrual and capitalisation can take place for any contract and has
nothing to do with specific applications)
Sujoy Ghosh, 2008/04/24
 1. As, you just learnt, a record in the BATCH application is called a process. All processes
are prefixed with the bank mnemonic

2. Processes to be executed during COB must belong to a Batch Stage.

3. Processes that do not belong to a Batch Stage will be executed as services. Please
refer “SER1.Services In T24” for more information on services.
4. It is important to understand - Why the Bank Mnemonic is part of the BATCH record ID?
This is because all processes are company specific. If we want the same process to be
executed for each company defined in the COMPANY application then we have to have
processes defined for every company separately.

For Example:
A company with mnemonic BNK might want a process to run during COB whereas
another company with mnemonic EU1 might not want the same process to run during
COB. The only way to do this in T24, is to create a process in the BATCH application
with ID prefixed with the mnemonic BNK and not EU1.
BNK/<Batch Proces ID Name>

If you want this batch process to be executed for both BNK and EU1, then you need to
do the following. Create the folloiwng records in the BATCH application
BNK/<Batch Proces ID Name>
EU1/<Batch Proces ID Name>

COB1.Close Of Business - Introduction-R10.01 6

 1. Batch Stage Contains a character to denote the Batch Stage and a 3 digit number to
denote the sequence within the stage. Sequence numbers are in the range 000 - 999.
The first Batch stage executed during COB is A000 and the last is O999.

2. Job Name Contains the name of the routine to be executed. All routines defined here
will have an entry in PGM.FILE with TYPE set to ‘B’

3. Frequency specifies the frequency at which the batch job has to be executed. It can
have values as follows.
D specifies that the job will be executed every working day.
D nn specifies that the job will be executed every nnth working day
W specifies that the job will be executed on a weekly basis, that is every Friday
M specifies that the job will be executed on the last working day of every month
M nn specifies that the job will be executed every nn day of the month or previous
working day of each month
Y specifies that the job will be executed last working day of the year
Y nn specifies that the job will be executed the last working day of the nn'th month
A specifies that the job will be executed on an adhoc basis. You should manually
specify a date on which the job has to be executed.
SW specifies that the job will be executed every start of WEEK
SM specifies that the job will be executed every start of Month
SY specifies that the job will be executed every start of Year

COB1.Close Of Business - Introduction-R10.01

 1. In the field Verification, you can enter the name of the job (routine) which needs to
have been executed successfully on that day before the current job is executed. For e.g.
The job COB.CHECK.EB.EOD.ERROR will be executed only if the job
COB.EXECUTE.API has been executed successfully.
NOTE: Only jobs already defined in the current record can be entered in the field
Verification. Jobs belonging to other Processes (Batch Records) cannot be entered in
this field.
2. Next Run Date contains the date when the current job has to run next. Populated
automatically on authorisation of the record (new jobs) or on successful execution of the
job. NO date is populated for Daily jobs, as the jobs needs to be run daily. User input is
required for Adhoc jobs.
3. Last Run Date is a No Input Field and is populated on successful execution of the job
during COB.

COB1.Close Of Business - Introduction-R10.01

 1. Process Status field holds the status of the Batch record. It can hold the following
values
0 specifies that the process is in Ready state
1 specifies that the process is in Running state
2 specifies that the process has Completed successfully
3 specifies that the process has stopped due to some Error

2. Job Status field Holds the status of the individual job (routine) . It can hold the following
values
0 specifies that the job is in Ready state
1 specifies that the job is in Running state
2 specifies that the job has Completed successfully
3 specifies that the job has stopped due to some Error

COB1.Close Of Business - Introduction-R10.01 9

 What you see here is a flowchart explaining the relationship between process status and job
status.

1.When a batch is loaded for execution, the process status of the batch record is changed
from 0 to 1, (Ready to Running)
2.The first available batch job’s status changes from 0 to 1 (Ready to Running)
3.The job is executed
4.After the job completes execution, the status of the job is changed from 1 to 2 (Running to
Completed Successfully) marking successful completion of the job.
5.Next the batch record is checked for any other available job
5.1 If there is another job available, it is processed in the same fashion as we saw
just now
5.2 If there is no job available in the batch, the process status of the batch record is
changed from 1 to 2 (Running to Completed Successfully)

Likewise the other batch records are processed.

COB1.Close Of Business - Introduction-R10.01 10

 The next few slides are going to take you through – “How to Run COB”

COB1.Close Of Business - Introduction-R10.01 11

 1. The entire COB process is controlled by tSM. There can be only 1 manager running in an
application server.

1.1 tSM stands for T24 Service Manager

1.2 As the name implies, it acts as a manager and controls all worker processes
that perform COB
1.2.1 Launches worker processes
1.2.2 Checks if worker processes are running as scheduled
1.2.3 If any of the worker processes are dead, launches substitute worker
processes

2. The actual COB process is executed by tSAs, Multiple tSA’s can be started in the
application server
2.1 tSA stands for T24 Service Agent (Worker processes)
2.2 Execute the jobs (routines) defined in BATCH record(s)

3. The tSM and tSA are started on T24 Application Servers. First the manager should be
started followed by the agents

COB1.Close Of Business - Introduction-R10.01 12

 1. A bank having multiple applications servers running T24, might want to use both the
servers to run COB. This would help them in completing COB faster. In order to run
COB in Multiple app servers, a module named MS (Multi Server) needs to be installed
separately and configured.

2. In a multi application server scenario

2.1 Each T24 application server will have one tSM running. The job of this tSM is to
monitor the tSAs running on that server only
2.2 Each of the T24 application servers can have any number of tSAs running to
run COB. However, the number of tSAs depend on the capacity of the server
(number of processors). The Default Thumb rule is No.Of.tSA =
No.of.Processors * 2

COB1.Close Of Business - Introduction-R10.01 13

 1. TSA.SERVICE, As the name signifies, it is an application in T24 where the services are
defined

1.1 In the application TSA.SERVICE, TSM is defined as a service

1.2 COB is also another service defined in TSA.SERVICE

1.3 Both services namely TSM and COB are pre-configured in the TSA.SERVICE
application. You will see quite a few records in the TSA.SERVICE application other
than TSM and COB. They are online services (Covered as part of the session
‘Services in T24’)

COB1.Close Of Business - Introduction-R10.01 14

 What you see here is the TSM record in TSA.SERVICE application.

Description field holds the text that describes the TSA.SERVICE record

Server Name field holds the IP address or the host name of the server where this service
TSM needs to be executed.

There can be only one tSM per T24 application server. When MS (Multi Server)
product is installed, this field can be multi valued to include the ip of all the servers
involved in running COB

Work Profile field holds the ID of the TSA.WORKLOAD.PROFILE application which in turn
contains the number of agents required to run this service. For the record TSM, the number
of agents should always be 1. This field forms a multivalue set along with Description and
Server Name fields

User field holds a valid T24 user name. It has no significance for this record TSM. Has
significance for the record COB.

Service Control : It is the field that controls the starting and stopping of this service. If set to
START, T24 will allow us to start TSM by issuing the command START.TSM. To stop the
TSM, set this field to STOP.

COB1.Close Of Business - Introduction-R10.01

 What you see here is the COB record in TSA.SERVICE application.

User field holds the valid T24 user ID. During COB, number of records could get
created/updated in T24. This user’s profile will be used to update the audit fields of such
records. Make sure that the USER specified here has super user privileges in T24.

Service Control : Setting this field to START denotes that COB can be started. TSM will
start the number of agents specified for this service only if this field is set to START. Once
COB is complete, this field will be automatically set to STOP. Before commencing the next
COB, this field needs to be set to START.

COB1.Close Of Business - Introduction-R10.01

 This is the application used to specify the number of agents. The number of agents in
TSA.WORKLOAD.PROFILE can be set based on time. Agents can be increased/decreased
based on time (T24 application server time)

Assume a scenario where in you know that the server will be busy at 11PM as that is when
transactions from an interface will be coming in. You may choose to reduce the number of
agents running COB during that period so that the server be used for the interface as well.
Define this in the TSA.WORKLOAD.PROFILE application.

COB1.Close Of Business - Introduction-R10.01 17

 1.1.1 The T24 Service Manager (TSM), reads every record in TSA.SERVICE with the field
SERVICE.CONTROL set to value ‘START’ or ‘AUTO’.

1.1.2 Once it (TSM) does this, it checks the appropriate TSA.WORKLOAD.PROFILE

record, to find out how many agents are required to run a service.
Lets assume that a service COB requires 3 agents for running, however only 2
agents for COB are currently running then it (TSM) will prompt the user to start the
remaining agent required to run this service. In this case 1 more agent needs to be
started.
Therefore, TSM checks if the appropriate number of agents have been started for a service,
if not, it prompts the user to start the agent. (This will happen only if TSM is launched in
DEBUG mode)

Once TSM is done with all its work, it waits for a while before starting the same cycle all over
again. This time for which the TSM waits is specified in a field REVIEW.TIME.

For eg: if the field REVIEW.TIME specified in TSA.SERVICE record TSM is 60 (the value is
always in sec); then every 60 sec the TSM will do the above mentioned steps.
So, lets assume the first check started at 12:10pm and took 10 sec to complete; the next
cycle of check(s) would take place at 12:11:10 pm

COB1.Close Of Business - Introduction-R10.01 18

 1. Every agent (tSA) is required to tell the tSM (update the manager) that it is performing
the task assigned to it

2. The tSM is designed to wait for a stipulated amount of time for each agent to report that
it is alive and working

3. The tSM will term the agent as dead, if it doesn’t get a reply within the stipulated time.

4. It will stop the tSA process at the operating system level (kill the process) and start a
substitute process

5. 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)

COB1.Close Of Business - Introduction-R10.01 19

 Parameter file
Has only one record – ID is SYSTEM

Review Time Is used if the REVIEW.TIME field in the TSA.SERVICE record in not
specified. Default value is 60.

Death Watch Is used if the TIME.OUT field in the TSA.SERVICE record is not specified.
Default value is 300.

Highest Agent No input field. Updated by T24 with the number of agents running on all T24
application servers put together

COB1.Close Of Business - Introduction-R10.01 20

 The entire process of COB can be run in phantom mode, meaning in the background. There
are various monitoring tools available that will help you identify what is taking place with
respect to COB at any given point, this is discussed later in the session.

1. Step 1 : Check EB.EOD.ERROR for details. This is like a file that contains all the errors
that took place during the previous COB. Any errors reported in this file, should be
corrected before starting COB. You will learn about this in detail later.

2. Step 2: Set the field SERVICE.CONTROL to “START” in the records TSM and COB in
the TSA.SERVICE application. Commit and authorise both the records. You just learnt
how to do this step in the previous slides

3. Step 3: Login to jshell prompt i.e. the backend.

4. Type the command START.TSM at this prompt. This will start the TSM in phantom
mode. tSM not only starts agents for COB but also for various other online services in
T24. You will learn more about online services in the learning unit ‘Services in T24’.

COB1.Close Of Business - Introduction-R10.01 21

 COB can be run in the interactive mode too i.e. in the foreground mode. Once the tSM is
started, it finds out the number of agents that are required to be started for COB. Since, tSM
is run in interactive mode, it prompts you to start the require number of agents. If tSM was
run in a phantom mode, then it would have started the agents automatically.

1. The first two steps are like before.

2. Step 3: Login to jshell prompt i.e. the backend. Type START.TSM –DEBUG to start the
TSM in interactive/ debug mode. You will be prompted to manually launch agents.

3. Step 4: Login to another session. Start agents (tSAs) that the tSM wants you to start
from the jsh prompt using the command tSA followed by the agent number.

For eg: You can see the TSM has prompted you start three agents for running COB. You will
have to open another session, login to jsh and type the keyword tSA 2 to start the T24
service agent. You will have to repeat this for starting agents 2 and 3. As you can see, you
will be able to see what the tSA is executing in the foreground as opposed to the previous
case.

Until COB is stabilized in a bank, it always advisable to run it in –DEBUG MODE

COB1.Close Of Business - Introduction-R10.01 22

 Now that you have seen how to run COB you are now going to see what happens when you
run COB, and how DATE CHANGE takes place during COB

COB1.Close Of Business - Introduction-R10.01 23

 1. When you initiate COB, either in debug mode or interactive mode
2. The System Mode is changed from Online mode to Batch mode. This is reflected in the
DATES application. This is to indicate that COB is currently running on the system
3. The Execution of COB jobs take place in A, S, R, D order
4. The System is changed to Online mode at the start of “O” stage of COB. This is also
reflected in the DATES application
5. Finally all the jobs in the online stage are completed.

COB1.Close Of Business - Introduction-R10.01 24

 T24 maintains it own date per company in an application called DATES. This is date that is
referred to for all financial transactions.

When do you think T24 decides it’s the next day?

This is done during COB, as it marks the end of all financial transactions for that day and
makes the system ready for the next day.

COB1.Close Of Business - Introduction-R10.01 25

 1. Before COB is first run on a T24 environment, there will be only 1 record per company
in the DATES application.
2. As soon as we start COB, in the batch stage A001, a job called EB.CYCLE.DATES is
executed. What does EB.CYCLE.DATES do? It creates a record in the DATES
application with @ID as <Company.Code>-COB. It also advances
TODAY/LAST.WORKING.DAY by 1 day and changes the field NEXT WORKING DAY.
This is done for the existing DATES record for a COMPANY with @ID
<Company.Code>. Eg: Imagine we are running COB during the end of day of 10 JAN
2008, the following takes place - EU0010001 is the default DATES record for the Euro
Company. Notice that the field TODAY has been advanced to 11 JAN 2008 from 10
JAN 2008, field LAST WORKING DAY has been advanced from 09 JAN 2008 to 10
JAN 2008, field NEXT WORKING DAY has been changed to 14 JAN 2008 (because
12/13 JAN 2008 are weekend days corresponding to Sat and Sun) A record with @ID
EU0010001-COB has been created with details that was held by DATES record -
EU0010001, before COB was started.

When COB is run, ALL company specific cob jobs will reference DATES
record <Company.Code>-COB and not the default DATES record for a
company with @ID <Company.Code>

3. When COB reaches batch stage D000, a job called B.DATE.CHANGE is executed. This
job changes fields TODAY, LAST WORKING DAY and NEXT WORKING DAY for the
record <Company.Code>-COB in the DATES application

4. During the beginning of the online stage, the job BATCH.DATE.RESET is executed. The
NEXT RUN DATE is updated for all jobs executed today (excluding jobs with
FREQUENCY D and A). Also, all the PROCESS.STATUS and JOB.STATUS fields in
the BATCH records are reset to zero. This is all part of the COB framework.

COB1.Close Of Business - Introduction-R10.01 26

 1. The record in the DATES application that gets created during COB <Company.Code> –
COB, does not get deleted after COB

2. The record will exist and will be overwritten during the next COB

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

4. 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??

COB1.Close Of Business - Introduction-R10.01 27

 COB supports 24 hour non stop processing
1.1 For this a product named NS (Non Stop) needs to be installed

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

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

1.4 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

COB1.Close Of Business - Introduction-R10.01 28

 The first agent (tSA) to be started is called the tSM (T24 Service Manager). tSM monitors
one or more agent processes called tSA (T24 Service Agent). Every time an agent is
started, it will first check if it is the tSM. If not, then it will continue to work as an agent
because it knows that an agent has already been assigned as the tSM.

tSA calls a routine called S.JOB.RUN, that inturn invokes a routine EB.SORT.BATCH only
ONCE. The work of EB.SORT.BATCH is to sort the COB jobs in ‘A’, ‘S’, ‘R’, ‘D’, ‘O’ order
and give it to the tSA’s.

COB1.Close Of Business - Introduction-R10.01 29

Slide 29

SG4 Concentrate on explaining How the jobs are sorted. Make the trainees write it on a piece of paper first
and then check with the slide. The slide is animated, so the result of sorting is on a mouse click, wait for
the trainees to complete before showing the animation
Make sure that they understand that within a BATCH stage the jobs CANNOT be swapped or sorted, for
eg: JOB2 cannot be executed before JOB1
Sujoy Ghosh, 2008/05/08
 You are now going to see how to Monitor COB

COB1.Close Of Business - Introduction-R10.01 30

 You know tSM launches and controls the tSAs. How does an end user know what is
happening with the tSAs? Use the enquiry AGENT.STATUS

Agent ID is the Agent Number

T24.SESSION.NO is updated with a unique number that identifies every session in T24. A
number between 1 -99999 is allocated when a session is started in a port to uniquely identify
that particular session in T24(both for online and COB).
Note: This random number is generated using a routine called
EB.ALLOCATE.SESSION.NUMBER and is stored in a common variable called
C$T24.SESSION.NO. This helps in improving the monitoring capabilities of T24.
A live file called T24.SESSION gets updated with record key being the T24.SESSION.NO
and contains information regarding the agent to which this session number was assigned. A
record in this application gets deleted, when the corresponding process terminates(session
expires).

Server Name is the name of the server where the agent is running. Note that details of tSAs
and tSMs across application servers will be updated here

COB1.Close Of Business - Introduction-R10.01 31

Slide 31

s2 The AGENT.STATUS enquiry output has been split into three screen shots as it elapses the screen. Some
of the fields are explained in this slide and the remaining are explained in the next slide.
salamelu, 2010/02/23
 Agent Status is the status of the agent. It can hold either of the three values.

RUNNING – Agent performing the job

STOPPED – Agent has stopped properly.

DEAD – Agent did not report within the time given and hence the tSM has marked the
agent as DEAD

Process Id is the Operating system level process ID for the agent process that is running

Current Service is the service the agent is performing at the moment. Note agent 1 is
performing the service TSM and the others are performing the service COB

Next Service is the service the agent is supposed to perform next. While COB is running, if
you wish to stop COB, set the field SERVICE.CONTROL to STOP for the record COB in the
TSA.SERVICE file. Then, check the NEXT.SERVICE value for the agents running COB, it
will be set to STOP denoting that the agents needs to stop once they complete the current
transaction

COB1.Close Of Business - Introduction-R10.01 32

Slide 32

s3 This slide is hidden in the slide show, it is present only for the notes page information
salamelu, 2010/02/23
 Job Progress is the status of the jobs

Opens, Reads, Writes, Inputs, Executes, Deletes, Clearfiles, Memory provides details
about the number of file opens, number of I/O’s, memory usage etc., by each agent. These
details available in the enquiry improves the monitoring capabilities of T24. It provides an
understanding on the processing done by the agent. Updated both for service and online
agents.

COB1.Close Of Business - Introduction-R10.01 33

 Last Message is the message displayed by the agents as they are performing the jobs. The
agent running tSM will not display any message as it is just monitoring agents.

Como Name is the name of the log record ID that holds the log information of the agent.
These log records are stored in a directory called &COMO&. The contents of these records
cannot be viewed from browser. You will have to open these records at the jBASE prompt

COB1.Close Of Business - Introduction-R10.01

 The enquiry picks up data from the TSA.STATUS file.

COB1.Close Of Business - Introduction-R10.01 35

 This is one utility available for monitoring COB in the T24 Classic interface.

COB1.Close Of Business - Introduction-R10.01 36

Slide 36

s1 The 'Total' column in the COB.MONITOR display indicates the total number of records(pcocesses) in the
BATCH application that belongs to that particular COB stage, irrespective of whether jobs in that process
are intended to run as part of TODAY's COB or not. This is the reason why some times, in this display it
may appear as though S stage(say for example) has begun even though A stage has not been 100%
complete.
salamelu, 2010/02/21
 1.318 OUT OF 4123 JOBS HAVE BEEN PROCESSED
2.Progress Bar displaying % completion
3.While executing the enquiry, you can set the Auto Refresh Option, this way the enquiry will
keep refreshing and showing you the % of jobs completed.

COB1.Close Of Business - Introduction-R10.01 37

 You are now going to see some useful tips that will help you to trouble shoot COB

COB1.Close Of Business - Introduction-R10.01 38

 1. Is there a file where all the errors encountered during COB can be viewed?
1.1 Yes. The name of the file is EB.EOD.ERROR
2. The id to a record in EB.EOD.ERROR is <company.code>.<date>
1.1 Eg: GB0010001.20100120
3. 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
4. The id to record in EB.EOD.ERROR.DETAIL application is present in the record of
EB.EOD.ERROR

COB1.Close Of Business - Introduction-R10.01 39

 Once you list the records present in the application EB.EOD.ERROR you will be able to see
records that are date and company specific. All errors encountered as a result of running
COB on a single day are stored in 1 record. If multiple errors are recorded during the same
day, they are stored in the same EB.EOD.ERROR record but multivalued.

Each error has a Detail Key populated against it which is nothing but the ID to the
application EB.EOD.ERROR

COB1.Close Of Business - Introduction-R10.01 40

 For every error encountered during COB (for that day) there will be a equivalent record in
the application EB.EOD.ERROR.DETAIL.

The application EB.EOD.ERROR.DETAIL will contain the name of the Process, the name of
the job and the routine from which the error was generated

The ID to a record in this application is held in the EB.EOD.ERROR file. The main use of
this application is to track down the cause of the problem encountered during COB. This
helps the consultant in fixing the problem before starting COB the next time.

COB1.Close Of Business - Introduction-R10.01 41

 COB cannot run the next day without resolving errors encountered during the previous run.

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

A. Open the corresponding record in EB.EOD.ERROR in EDIT mode and set the field Date
Resolved to the date when the error was fixed. Commit and authorise the record. This has to
be done before COB is started the next day

COB1.Close Of Business - Introduction-R10.01 42

 1. While running COB the agents suddenly stops. What to do?
1.1 Check the AGENT.STATUS enquiry output to see if there are any errors
1.2 Check the EB.EOD.ERROR file to see if any errors have been logged
1.3 If you are running COB in interactive mode, then the TSM that is running will prompt
you to manually launch the agent.
1.4 If you are running COB in phantom mode, TSM will automatically start the agent
during the next REVIEW.TIME

2. 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?
2.1 This error is a Critical Error. It means that COB cannot be started without setting the
error right.
2.2 In order to find out the error. Run the enquiry AGENT.STATUS. It will show the last
message processed by that agent. You can also find out the COMO ID using the
AGENT.STATUS enquiry and search for this record in &COMO& to find out the details
of the error.

COB1.Close Of Business - Introduction-R10.01 43

 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.

COB1.Close Of Business - Introduction-R10.01 44

 tSM stands for T24 Service Manager
• this tSM is to monitor the tSAs running

2. tSA stands for T24 Service Agent

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

3. Always start the Manager first

• START.TSM

4. TSA.SERVICE is the application that is used to define the various

services and is also used to control the services (Start and Stop them)

TSA.PARAMETER is the main parameter application and contains default values for death
watch, review time etc

COB1.Close Of Business - Introduction-R10.01 45

 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

COB1.Close Of Business - Introduction-R10.01 46

 How to Start COB? (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)

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

Step 10: Repeat step 9 for the other two agents (tSA 3 and tSA 4)

COB1.Close Of Business - Introduction-R10.01

 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 r09 ~ -->START.TSM

The TSM will take care of starting all the agents automatically

COB1.Close Of Business - Introduction-R10.01

 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

COB1.Close Of Business - Introduction-R10.01

 1. False
2. True
3. True
4. True
5. True

COB1.Close Of Business - Introduction-R10.01 50

 In this learning unit, you learnt about an Introduction to the COB system

You will now be able to understand

1. COB and its Stages

2. The BATCH application
3. Executing COB in T24
4. Date changes in T24
5. Monitoring COB
6. Troubleshooting

COB1.Close Of Business - Introduction-R10.01 51

DEV1.T24 Template Programming-R10.01 52