Rick Welykochy wrote:
Jake Anderson wrote:
The bank may well be pretty sure that nothing will go wrong but given
the cost/benefit ratio its prudent not to take the chance that there is
one line of code somewhere or another in the many tens of millions they
have that will freak out when the clock goes backwards.
What about ATMs? Will they be down for the count?
If not, and the main systems are down, they must queue up
transactions. The timestamps on those transactions will
have to be handled correctly when the queue is processed.
Including transactions during the hour the leaps back.
Just spoke to somebody "in the know"
netbank is shut down, all other services are unaffected (well common
services anyway).
Her explanation is this.
All other transactions are processed in a batch at night, IF you
withdraw money at an ATM your account balance is immediately debited but
the transaction itself is just recorded.
This is presumably also when all the interests are calculated and so on.
Only on business nights are those transactions actually processed to
create a statement.
Netbank transactions however are processed "instantly".
As such it can cause issues when the time roles back.
It probably also has something to do with the age of netbank, its very
very new as far as bank software goes.
Listening to the errors they have with processing and the like, its
enough to make me want to keep my money under the bed.
The same can be said about bank-to-bank and bank-to-international
transactions.
It seems like a problem they must already have to deal with.
Transactions world wide into and out of Australia do not stop
for an hour at 2:00 AM Easter Sunday, do they?
Anyone working in the banking sector out there?
cheers
rickw
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
