∙

∙

A conversion team is normally chosen that will be dedicated to the project until its end. Included with this team will be (perhaps) two application programmers. Naturally, the number varies with the size and complexity of the project. The team is responsible for converting all VSE applications. (As previously mentioned a program conversion aid is normally used with this approach.) Application programmers, not part of the project team, are not disrupted during conversion work. They can continue to perform VSE application development and maintenance activities.

The migration project has a visible end.

Because the project is an important one (obviously it wouldn′t have been undertaken otherwise), and since no applications are cutover until all applications are ready, the conversion effort will not lose steam. Priorities will remain very high to complete application conversions, and to implement OS/390 as the production system. Typically, the duration of realizing total OS/390 production with this type of approach, is significantly less, (even up to 50 percent less in duration), then with the kernel approach.

Staff is better prepared, trained, and experienced with OS/390 prior to production operations.

OS/390 skills are developed during all conversion activities; that is, conversion activities are performed on the OS/390 system. All learning and hands-on activities are accomplished on a non-production OS/390 system, thereby lessening future production exposures. Since there is no dual operations of both VSE and OS/390, operators don′t get confused as to which system they′re operating on.

2.5.3 VM/ESA Guest Support in Your VSE to OS/390 Migration

VM/ESA′s Guest Support has long been an important part of many VSE and MVS(OS/390) customers operating environments. As you approach migrating VSE to OS/390 you should consider the important roll VM/ESA plays in making the job easier and more cost effective current and long term.

If you already have VM/ESA and you use VM/ESA′s Guest Support for running your VSE system(s) then you already know the value VM/ESA delivers in this environment. In migrating VSE to OS/390, VM/ESA continues to play an important roll delivering as much or more value to your new OS/390 environment. If you are not familiar with VM/ESA a more complete description of how to implement multiple VSE and OS/390 images can be found in chapter 26 of this publication. Chapter 26 also discusses the benefits and consequences of using VM/ESA and LPAR to support multiple images both during and after the migration. For more information on VM/ESA obtain a copy of VM/ESA V2R2.0 General Information, GC24-5745 and VM/ESA V2R1.0 Running Guest Operations, SC24-5755.

2.5.4Staffing Strategies

2.5.4.1In-House Staff

There are two main strategies involved when deciding how to staff the migration project. These typically are using existing in-house staff or hiring outside consultants. Some considerations when using in-house staff are:

Chapter 2. Sizing the Effort

29

Page 52 Page 54
Page 53
Image 53
IBM manual 3 VM/ESA Guest Support in Your VSE to OS/390 Migration, Staffing Strategies, In-House Staff
Page 52 Page 54

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.
Top Page Image Contents