T24 Close of Business (COB) - T24 Helper

1/25/2018

T24 Close of Business (COB) - T24 Helper

Tips and Tutorials on T24 Core Banking System Home

About Us

Jobs

Disclaimer

 

Privacy Po Policy







Contact us us







Search …

T24 Close of Close of Busines Businesss (COB) November 3, 2016  T24 Helper  One comment

T24 Helper

[ 4,028 views

]

Close of Business (COB) handles the T24 Batch Processing. Close of Business is used for processing pr ocessing events, calculating and posting interest, rolling the bank date forward and production of various reports. The Close of Business triggers various activities based on the scheduled date and based on specic conditions. The Close of Business consists of the following ve stages in sorted order:

Individual application processes http://www.t24helper.com/t24-close-business/

YouTube

626

Tier 1 US bank selects Temenos T24 Core Banking for global cash management backbone How to export ACCOUNT$HIS records through DW.EXPOR DW.EXPORT T How to activate EB.DUPLICATE.TYPE control How to congure Multiple T24 environments using JBoss Procedure to input single side DATA.CAPTURE How to mature a MM contract online T24 DEVELOPER: (T24, TEMENOS T24, JIRA, SCRUM) LarrainVial nally goes live with Temenos’ T24 core banking system 1/17

1/25/2018


(Forex, Funds Transfer, etc.) System wide processes (Interest and Charges, Revaluation, etc.) Main system reports (Trial Balance, General Ledgers, etc.) Change date (Standing Orders, split

Five steps, ve minutes, €5 – KBC launches new mobile app for current accounts Openbank step closer to new core banking system decision

month end events, cash ow maintenance, etc.) Any non critical reports and processes that can be run after the

T24 Helper Like Page

137 likes

system has returned to on line mode. Be the first of your friends to like this

The Close of Business runs various processes based on the order above, in order of stages and within the stage based on the sequence number. Each batch stage consists of a number of processes with the same or different sequence number, which corresponds directly to records in the BATCH le, and each process consists of a number of jobs for

T24 Helper about 2 months ago

How to activate EB.DUPLICATE.TYPE control.

which routines are dened in the PGM.FILE as type ‘B’. Each batch process denes the stage and sequence at which it has to be run, the jobs to be run and the frequency in which it has to be run. At no point, the stage and the sequence of the batch process will be violated thus ensuring data integrity and proper processing of jobs if they are dependent on an earlier job.

In order to get the most out of this manual, it is essential that you are familiar with the standard procedures regarding navigating your way around the system. This includes items such as program access

RFID Wristband

via menus, data entry and editing, mandatory and multi‐level elds, committing details, and so forth. All of these are described in detail in the Navigation manual .

T24 Close of Business processes have been designed to run as multi threaded to reduce the time taken and to maximise the usage of system resources. Multiple agents can be used to run the Close of Business and they share the job load. However, this will not affect the sequence or the verication of the Close of Business. The agents complement each other within the same stage and sequence and do not violate the agents, thus ensuring data integrity. The number of agents is dened in the TSA.WORKLOAD PROFILE record, which is in turn attached to the TSA.SERVICE record on 12,308 Pageviews

http://www.t24helper.com/t24-close-business/

2/17

1/25/2018


COB.

Dec. 18th - Jan. 18th

A Service Manager (TSM) and Service Agents (COB) control the COB process. Create TSA.WORKLOAD.PROFILE and TSA.SERVICE records for each of these as described below:

The Manager only requires one agent (above) whereas 2 to 3 agents for the COB are sufcient (below)

There is only one record – SYSTEM. This application tells the Service Manager at which levels (in seconds) to review and restart the Agents.


3/17

1/25/2018


This is the user name that will be associated with all records processed during the Close of Business.

The process to create a user is described in the System Administrator manual and is therefore not repeated here.

(Create COMMA Version to facilitate starting and stopping Agents without the need to log in as a second user)


4/17

1/25/2018


: The server name is not a mandatory eld. The tSM obtains the server name it should run, by executing the hostname command. It then tries to match that with the value entered in the eld SERVER.NAME in TSA.SERVICE of the agent. If it does not match then it could not start the agents. If there is no value in the eld SERVER.NAME, the tSM uses the value captured by it (through the ‘hostname’ command). So there is no need for the SERVER.NAME eld in TSA.SERVICE. This applies both to local host as well as server.

: The server name is not a mandatory eld. The tSM obtains the server name it should run, by executing the hostname command. It then tries to match that with the value entered in the eld SERVER.NAME in TSA.SERVICE of the agent. If it does not match then it could not start the agents. If there is no value in the eld SERVER.NAME, the tSM uses the value captured by it (through the ‘hostname’ command). So there is no need for the SERVER.NAME eld in TSA.SERVICE. This applies both to local host as well as server.

As Agents may become stuck, we recommend that you rst STOP all Agents, and then clear the table F.TSA.STATUS at the j prompt as follows: –> CLEAR.FILE F.TSA.STATUS


5/17

1/25/2018


Also clear the EB.EOD.ERROR le once the errors occurred during the Close of Business have been xed, by entering F.EB.EOD.ERROR at the j-prompts as follows: –> CLEAR.FILE F.EB.EOD.ERROR

Start TSA.SERVICE for both TSM and COB records


6/17

1/25/2018


You have now started the Service Manager. The Manager continues to advise to manually start the Agents:

Open a new Reection session and enter tSA 2 –DEBUG and the command prompt:

Agent 2 has been started and the COB is underway, now start Agent 3: http://www.t24helper.com/t24-close-business/

7/17

1/25/2018


Example of processing screens (with COMO as Agen ts were started with –DEBUG statement)

When the COB is completed, the Service Manager automatically stops the Agents – this is the display:


8/17

1/25/2018


Return to the TSA.SERVICE, application and STOP the TSM record. You will note that the status of COB is already set to STOP.

Non Stop Processing and Close of Business complement each other. Close of Business disallow input and processing of records in all applications, other than those supported by Non Stop service. The applications that are available in Non Stop (NS) 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 for 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 CO.CODE-COB record in DATES and on line processing happens with the cycled record in the DATES application.


9/17

1/25/2018


Even though there is no need for typical T24forMCB sites to make use of the Non Stop service, the information above is relevant as TT, FT and DC transactions may be captured while the Close of Business is being processed. There is also no longer the need to close tills and for users to be logged out of the system prior to invoking the Close of Business. Any transactions not permitted during the Close of Business provide a message to the user stating that it is invalid during Close of Business.

Every job during the Close of Business uses a LIST le for storing and sharing records for processing between different agents. The LIST le 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 le is empty at the end of the job thus making it available for a different job.

Since the introduction of multi threaded architecture, the COMO is written with the session number to distinguish processing between different threads. The COMO is written with the key as TSA__datetime. It is recommended that all COB COMOs be retained securely for at least six weeks. If there is an occasion to restore and rerun, then the COMOs should be printed or copied to a secure medium before the restore takes place. Example of the COMO with an error:


10/17

1/25/2018


Three enquiries are available that assist the monitoring the progress of Close of Business and the records processed with the time taken. They can be accessed via the Temenos Enterprise Console. COB.PROGRESS – A listing of active companies and an indication (progress bar) of their time to completion. JOB.PROGRESS – This enquiry list all active and completed j obs by descending start times (i.e. current on top). It shows the start time, end time, elapsed time, contracts processed, total con tracts 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 the job is slowing down as time passes. JOB.HISTORY – Drilling down from the 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 gure rises over time; it indicates a problem, which could be badly sized les.

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 th is process:

Prints or reprints all output for a specic batch run. Species that no printing should take place until all processes have completed. Stores detail of all output produced by the batch run. Species the printers available to the system. Dening the reports and individual should receive. In order to access the reports generated during the Close of Business, follow these steps:


11/17

1/25/2018


Enter ENQ REPORT.LIST in the Command Line.

1. Enter ENQ LIST in the Command Line. 2. Enter the search criteria and click on the

butto

3. View the resulting enquiry on screen and manipulate as described in the Navigation manual . 4. Close the report.

A screen like the one shown below displays, allowing you to lter the records for on screen enquiry or report.

Selection criteria may include part of a report name, or not entering any selection criteria, the system displays all reports generated and held as per the number of days dened in the SPF record. When the enquiry displays, it will appear like the screen shown below.

Select the report by clicking on the View Report ID against the record displayed in the report list.


12/17

1/25/2018


As described in the introduction, a process can consist of any number of jobs, which in turn can execute a number of programs or operating system commands. If an error occurs, the system may return immediately to the monitor screen and display the process and the job in error or in the case of less sever errors, update the record for the current batch run and the current company on the EB.EOD.ERROR le and continues.

The details of these errors can be found in examining the records on the EB.EOD.ERROR le and on the EB.EOD.ERROR.DETAIL le. The Close of Business processes are wrapped around jBASE transaction management. Hence, in case of any crashes during Close of Business, the concerned transaction is rolled back and the Close of Business continues. This ensures that Close of Business can continue after an error and partial updates are rolled back to keep the database in sync. Jobs can abort for a variety of reasons, both system and application related. Identify the aborted job. Any system related crashes are sensed by the Temenos Service Manager (TSM) and the dead agent is started again. The TSM, if there is no activity in an agent for a period of time as dened in the DEATH.WATCH eld of TSA.SERVICE, it restarts the agent thus ensuring that the Close of Business crashes are monitored and restarted by the TSM. Any application related crashes write into EB.EOD.ERROR the information on the job name, the record and the text of the crash. The underlying record from the .LIST le is removed and the updates done until the particular transaction is rolled back.


13/17

1/25/2018


To continue the batch, use the up arrow key at the j-prompt for the last command (e.g. tSA 2 –DEBUG) and depress the return key. There will be some critical jobs that may crash and abort the Close of Business due to business reasons, as further continuance of the Close of Business is not advocated. These jobs are dened as .CRITICAL in the ADDITIONAL.INFO eld of PGM.FILE .

You cannot return to on line mode until all batch processes have been completed successfully. COB has already been set. Invalid frequency code specied in process. The jobs in the process have been specied in an execution order that is illegal i.e. job 1 depends on the successful completion of job 2 Job failed during initialization – no need to restore the database to re run. Unknown command at current action level. Job terminated with an error – see process output. Row selection number does not have an associated process. Job not dened in PGM.FILE .

Option from menu cannot be executed until the Close of Business has been initiated. You cannot start this process when another has failed. Rerun the job in error rst. Process name entered is not on the BATCH le. Cannot select process to be http://www.t24helper.com/t24-close-business/

14/17

1/25/2018


restarted when the current status is not HOLD or ERROR. Cannot select a process to be halted when the current status is not RUNNING. Unknown process name entered from action line. Fatal error during process execution – see process output for more details. Database needs to be restored to re run this job Job not dened in PGM.FILE .

End of Year Procedure

End of Year Procedure

T24 R12 and above

T24 R10 and R11

How to calculate the

How to set a customer to

interest for utilized

receive SMS and/or email

amount

alerts?

Data Capture


15/17

1/25/2018


 About the Author

 Latest Posts

This website is purely for the Temenos T24 Core Banking System Software users. You will nd all the T24 related Technical and Functional Tips and Tutorials in here. And thanks for dropping by. Don't forget to Like, Subscribe and Comment. Visit My Website



















 T24 Technical, T24 Tips & Tutorials, T24 User Guides « Why ASSET PROVISIONING Needed?

T24 TSA Service »

One comment

November 16, 2016 at 9:18 pm

Very useful article for the all the T24 Operation guys. Reply

Leave a Reply Your email address will not be published. Required elds are marked *


16/17

1/25/2018


I'm not a robot reCAPTCHA Privacy - Terms

Home

About Us

Jobs


Disclaimer

Privacy Policy

Contact us

Powered by WordPress and Courage.

17/17

T24 Close of Business (COB) - T24 Helper

Recommend Documents