iSeries System Rationalisation - System Consolidation Merging two systems to run under the same instance of OS/400 is a very complex task. However, with the IBM charges that now govern interactive and batch workloads it can make good financial sense to do so. For example, a company has two systems an S20 #2161 (113 CPW) and a 720 #2061 (240 CPW) with an #1501 interactive feature. The 720 system is used almost exclusively for interactive work, leaving 70% (170 CPW) of available processor resource unused. Through merging the two workloads on to the 720 system, management effort is reduced as are operating costs. The service starts with a fact finding project to identify all duplications, such as libraries, profiles, etc and application conflicts. All issues are discussed and resolved with your application vendor or development team before detailed planning takes place. The consolidation process takes place in four stages; Planning, Initial load, Testing and Go Live. All tasks are planned in detailed and listed in order. Following the plan, the initial load stage is executed, loading the target system with data and applications from all source systems. Testing now begins. All aspects of the system, communications and applications are tested. Go Live only occurs after satisfactory test results. ATS can supply an interim system for the purpose of research and testing. If an interim system is used a system migration will be built into the project. 20 days support is also provided after Go Live. Deliverables: • Project management Benefits: • Reduced operating costs System Rationalisation - LPAR Services - Design and Planning System Rationalisation - LPAR Services - Configuration and Set-up |
