DefinePK

Abstract

The disaster could happen at any point of time and due to which there could be financial loss in addition to operational loss, considering 24/7 banking environment and having its branches in different parts of world. The risk involved in financial loss may be very high and could result in unbearable loss. In such cases where organizations have zero downtime and having high availability of data, the disaster recovery mechanism and data replication scope has to be well defined and should be strictly followed. Assuming that the network, storage and hardware is available at DR site and the replication of critical data is also verified but still there are several objects left behind which were not covered under replication scope. These objects were created by programs themselves while executing (not in replication scope). In such case the successful switch might not be called as successful because those objects will not be available at DR site and may lead to business interruption or financial loss. This problem arises when developers have access on production servers and they create new libraries/objects for their program execution without informing the implementers through proper change management process. In this paper we will provide the guidelines and framework for deployment of programs on production servers also the guide for smooth switching (change of role) of entire core banking environment running on IBM System-i to DR site.