T24 COB

[AAL]

Dear All:

The bank I work for will soon be going live on T24. As a DR Manager I
am looking into the scenarios that can go wrong with T24.
Unfortunately, the consultants who are implementing T24 dont have
enough experience of working on negative scenarios.

One of the problems I foresee is the with T24 COB ie I understand that
if COB crashes than data has to be restored and COB needs to be re
executed again. My question is what happens to the transactions that
have been posted while the COB was running, like ATM, Internet Banking
etc.?

[raphael olapade]

Hi,

While i appreciate your concerned on the negative scenario you are
hoping it might happened and your comment on the Consultant incharge,
there's the need for you to have confident on those your cusultant.

On the probability that COB might crash, this depend on the COB
stage(s) as you know we have four stages in COB. The MOST CRITICAL
stage that could warrant you restoring your before the COB bakup is
bothe APPLICATION and SYSTEM-WIDE stages. If it is REPORTING/START OF
DAY there might NOT be any need to restore your BCOB data backup.

And NOTE since Temenos Helpdesk is operating 24/7 just make sure when
any NEGATIVE scenarios occurs you either get in touch with Temenos by
phone, google talk and of course skpe.

Wishing you successfull LIVE and free from negative scenarios

Rgds.


Segun

2009/1/30 AAL <amir....@gmail.com>:

--
Raphael

[ADENIYI KAREEM]

Hi,

Sometime you don't need to restore your backup when COB crash , it depend on the jobs that is runnning. The batch/jobs determine if you need to restore or not.

On T24, there are critical jobs that need urgent attention especially on LIVE environment. You can quickly contact the Temenos Helpdesk immediately for solution. They will work through with you on any LIVE issues.

Moreso, it is better to always Test any patches release by temenos before applying to LIVE, because sometime , it may go wrong.

There will always be issues on COB  maybe sometime due to either wrong setting or data related issues during operational setup. So be prepare. Don't panic... contact temenos, and you will become familiar with some later on, to resolve on your own.

Goodluck.

regards,

'Niyi

--
'Niyi Kareem
IT Consultant
P.O.Box 1006
Satellite Town,
Lagos,Nigeria
+2348023382844

[Dada Oluwaseun]

HI,

COB stages determine whether u restore database or not, Application and System Wide are stages that are critical and u need to monitor it well for a start by running COB in DEBUG mode tha is manually starting the tSA on different sessions so that u can see what is been processed directly from the &COMO& ,hope the COnsultant in charge will take care of it and contact Temenos and Senior friends where necessary.

Don't panick for the first few days COB will give u stress.But good hands on Ground will help to make it better.

And Hope the infrastructure and Platform Archectiture will Perfect because it also after COB 

either single server or Multi server (ensure the Multi server COB module as been installed) 

Note: COB is hardware tasking and u need know it is multi thread so the whole system resources are in use.

Also if Non Stop is Installed make sure it is activated for all the Companys (branches).

 

 

regards and God Bless 

 

[raphael olapade]

Once again for the ATM, Internet Banking or any e-banking products
operations/transactions that will continuously be posted while you are
running COB what you shuld try and do via your consultant is that they
should make sure anytime you are about to commence COB operations; ATM
and any allied e.banking products should be directed to a stand-by
server that usually mirroring your main server so that once you start
COB operations any ATM transactions will be taking place on the
standby server which of course contains the CURRENT BALANCES of the
CUSTOMERS and immediately the COB finishes all the transactions that
takes place in ATM server will be replicated automatically on the main
server BY updating the customers balances immediately with their
transactions.

I hope this will be a guide to your consultant.

Thanks and My Best Regards


Segun

2009/1/30 AAL <amir....@gmail.com>:

--
Raphael

[mike ryder]

Hmm - interesting - the OP never stated his T24 version, OS or
database and the responders are busy sending replies without ever
caring about this. I don't see how one could make a reply without
considering this.

In a real-time scenario with R6, R7 or R8, non-stop module, online ETL
to a DW, ATM, Web and all of the other stuff the bank wants - there is
no possibility of a restore and rerun - for a global follow the sun
bank of some stature, it would be an absolute nightmare.

Fortunately, in these later versions, Temenos have made changes to the
COB process in recognition of this. In earlier releases, such as G13,
if a contract mismatch occurred, this would stop the COB and require a
restore, fix and rerun. In these later releases, the contract gets
noted in EB.EOD.ERROR and ignored. It can then be fixed intraday.

Some of this may depend on whether you are using as a database jBase,
Oracle, DB2 or a SQL product from the Redmond double glazing company.

Catastrophic breakdown of the database structure requiring a restore
will only occur with badly written code. Sufficient testing will
eliminate that risk. Competent developers on local dev will eliminate
that risk. Sticking to Temenos local dev guidelines and not trying to
re-invent some new flavour of banking software will eliminate that
risk.

However, confirmation of all of this should be obtained from Temenos.
Your account manager will be able to direct you to the correct
resource for your world area for such confirmation.

Just my 2p (from the Eastern side of the pond) and I hope it helps.
Mike

[Vlad]

A mismatch can also happen without crash. On the other hand, not every
crash needs a restore and fix (I would say, most of the crashes do not
require that). But you definitely would like to have THD phone number
in case of emergency.