3.2 Plan Components

3.2.1 Approach

For the purposes of providing more specific guidance for conversion projects, an approach to the migration had to be determined. This is also true for the migration effort itself, an approach must be adopted. In these discussions, we will describe the environment associated with using the Mass Conversion methods and tools.

3.2.2 Team

Before the actual project plan is developed, thought needs to be given to the project/migration team and the functions, responsibilities and composition of this team. There are many different ways to organize a migration team, the group of people responsible for planning and executing the migration project. A recommended organization for the migration team (see Figure 5) consists of the following people:

A project manager, who is responsible for the migration procedure as a whole - general specifications, planning, coordination, and follow-up.

Two systems or applications programmers, or one from each area, who draw up detailed migration specifications, install and customize any mass migration/conversion tools.

Two operations people to take charge of conversion testing.

A librarian to help control and track the migration activity.

 

 

￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿

 

 

 

￿

Project Manager

￿

 

 

 

￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿

 

 

 

 

￿

 

 

 

￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿

 

￿

 

 

￿

 

￿

 

￿

 

 

￿

 

￿

 

￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿

￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿

￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿

￿ Systems/Apps

￿

￿

 

￿

￿

￿

￿ programmers

￿

￿

Operations

￿

￿ Librarian

￿

￿ (2 people)

￿

￿

(2 people)

￿

￿

￿

￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿

￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿

￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿￿

Figure 5. Migration Team

The migration team should include people with the following knowledge or skills:

Some knowledge of the concepts and facilities of the OS/390 system

Knowledge of the current VSE environment and the applications to be converted

Development or systems skills to analyze special situations encountered during the early phases of the migration

Operations skills to test converted applications under OS/390 and to assess the impact of converted operational procedures on the OS/390 productions operations environment

Chapter 3. Developing the Plan

45

Page 69
Image 69
IBM OS/390 manual Plan Components Approach, Team

OS/390 specifications

IBM OS/390, a versatile operating system, was a cornerstone in enterprise environments and played a pivotal role in mainframe computing. Released in the mid-1990s, OS/390 combined the strengths of IBM's MVS (Multiple Virtual Storage) with new features and enhancements, targeting scalability, reliability, and performance in demanding business applications.

One of the key features of OS/390 was its robust support for multiple users and processes. The system allowed thousands of concurrent users to access applications and data, ensuring high availability and minimizing downtime—a critical requirement for many large organizations. This scalability was supported through various enhancements in memory management and processor scheduling, enabling optimal resource allocation across diverse workloads.

OS/390 was known for its superior workload management capabilities. The Workload Manager (WLM) component allowed administrators to define service policies, specifying how system resources would be allocated according to the priority of tasks. This ensured that critical business processes received the necessary resources while less critical tasks were managed more flexibly.

Another significant characteristic of OS/390 was its commitment to security. The operating system provided comprehensive security features, including user authentication, data encryption, and auditing capabilities. This focus on security was vital for organizations handling sensitive data, ensuring compliance with regulations and safeguarding against unauthorized access.

OS/390 also supported advanced technologies that facilitated integration and development. The system included features like the IBM CICS (Customer Information Control System) for transaction processing and IMS (Information Management System) for database management. These technologies allowed organizations to build robust, high-performance applications tailored to specific business needs.

The ease of network integration was another strength of OS/390. With the advent of the Internet and global connectivity, OS/390 systems could easily interface with various network protocols, enabling businesses to operate in a connected world. This inclusion paved the way for many organizations to expand their capabilities and offer new services, driving digital transformation.

In conclusion, IBM OS/390 represented a significant advancement in mainframe technology, combining scalability, security, and robust workload management. Its rich feature set and support for critical enterprise applications solidified its role as a vital component of many organizations' IT infrastructures, ensuring they could meet their operational challenges head-on while supporting future growth. As technology continues to evolve, the legacy of OS/390 remains influential in the realm of computing.