Documentos de Académico
Documentos de Profesional
Documentos de Cultura
Introduction
T24 Batch Processing is handled by the Close Of Business (COB). Close Of Business is used
for processing events, calculating and posting interest, rolling the bank date forward and
productions of various reports. The Close Of Business triggers various activities based on the
scheduled date and based on any specific condition.
The Close Of Business consists of the following five stages in sorted order.
Initialisation
T24 COB is run as a T24 Service.
To invoke a COB, a record needs to be created by the TSM service with the key as COB. This
service has to be defined with the appropriate profile and the server it has to run and the
OPERATOR who will be running the Close Of Business. Other details such as the
REVIEW.TIME and DEATH.WATCH have to be entered otherwise the details will be
defaulted from the TSA.PARAMETER record.
Once the COB record is created, the service status can be set to START thus making the
service ready for running.
Temenos Service Manager runs the COB service as a background service by invoking the
appropriate agents as defined in the profile of COB service.
If there are any unresolved errors on the EB.EOD.ERROR file (which were produced as a
result of a previous Close Of Business) and if the errors are critical, then the Close of
Business will stop for the errors to be resolved first.
Start COB with Users Signed On
Non Stop Processing and Close Of Business compliment each other. Close Of Business
disallow input and processing of records in all applications other than one supported by NonStop service.
The applications that are available in NS stop service will be available without any
restrictions and will be using the next working date for processing thus ensuring the
concurrent transactions are not picked up processing by the Close Of Business which is
running in parallel.
To support this, Close Of Business distinguishes the dates by two different records per
company in the DATES application. Close Of Business at the beginning cycles the dates
record and restores the old dates record with the key as the CO.CODE-COB thus ensuring
that all COB processing happens based on the COB record in DATES and online processing
happens with the cycled record in DATES application.
Initiate the COB Service
To initiate the COB service, the record in TSA.SERVICE application called COB has to be
marked for Starting. If the TSM service is not started, then it needs to be started before the
COB is initiated.
T24 COB processes have been designed to run in multi thread way to reduce the time taken
and to maximise the usage of system resources. Multiple agents can be used to run the COB
and load on the jobs will be shared by them.
However, this will not affect the sequence or the verification of the COB. The agents will
compliment each other within the same stage and sequence and will not violate the agents
thus ensuring data integrity.
The number of agents can be defined in the TSA.WORKLOAD.PROFILE record, which can
be attached to the TSA.SERVICE record COB.
There is a facility in Close Of Business to run it specifically for one or a set of companies.
This ensures that Global Processing feature of T24 is maintained. The companies could be
grouped together and COB shall be run only for them. While the COB is running for a
company, the other companies will be in online mode and will perform on a different date.
Close Of Business can be run in interactive mode for testing purposes. The agents then have
to be manually started for every session. This requires the Temenos Service Manager to run
in debug mode and thus the subsequent agents have to be manually started. It is advised that
this method is used for testing purposes only. After starting the TSM, the individual agents
allotted to COB should be manually started.
Every job during the Close Of Business uses a LIST file for storing and sharing the records
for processing between different agents. The LIST file is dynamically determined based on
the session number doing the SELECT processing of a multi-threaded job. The other agents
use the allotted list for sharing their load of the job. The list file is empty at the end of the job
thus making it available for a different job.
Como
Since the introduction of multi threaded architecture, the Como will be written with the
session no to distinguish processing between different threads. The Como will be written
with the key as tSA_<agent no>_datetime.
Monitoring COB
Three enquiries are available that help in monitoring the progress of COB and the records
processed with the time taken. They can be accessed via the Temenos Enterprise Console
(tEC).
COB.PROGRESS A listing of active companies and an indication (progress bar) of their time
to completion
JOB.PROGRESS This enquiry lists all active and completed jobs by descending start times (i.e.
current on top).It shows the start time, end time, elapsed time, contracts
processed, total contracts to process, throughput (contracts/minute) and individual
server rate. The latter is the number of contracts processed in one minute by a
server process this will be compared historically to see if thee job is slowing
down as time passes.
JOB.HISTORY Drilling down from JOB.PROGRESS, the user can see a graph of the elapsed time
of the last ten runs of the job and the individual server rate. If the latter figure rises
over time, this indicates a problem which could be badly sized files.
Batch Output
All reports, COMOs etc. produced by the batch system are output using the T24 report
control system. This enables the operator to determine the destination printer, user addressing,
number of copies etc. The following applications are used in this process:
Any application related crashes will write into EB.EOD.ERROR with the information on the
job name, the record and the text of the crash. The underlying record from the .LIST file will
be removed and the updates done till then for the particular transaction will be rolled back.