Take Advantage Of Conversion Tools and Automation

3.1.2.2 Take Advantage Of Conversion Tools and Automation

Executing a migration with a mass conversion tool and automated processes can reduce both the time and people required to migrate from VSE to OS/390. Where it is not a large task to convert three programs and two strings of JCL, it is a large and difficult task to increase the scope by one thousand and perform the same conversion.

The automation provided by the use of a mass conversion tool is unique. After an extensive period of analysis, which includes running both pilot conversions and dummy conversions, you can, in a final mass conversion, convert all of your VSE applications to MVS in a single automated process.

3.1.2.3 Migration Plan - Guide and Outline

Creating a migration plan involves analyzing what a migration requires and developing a plan to customize the general process to your particular installation. Developing a comprehensive and detailed migration plan is important to the success of a migration.

The type of conversion method directly affects the content of your plan. For this guide we have chosen to follow a mass conversion method using the Cortex MS processes. Chapter 3, Developing the Conversion Plan, of the MVS-MS Planning Guide provides information on how to develop a migration plan where a mass conversion method is used. Use it as a guide to develop a plan that is specific to your site.

Appendix A of the MVS MS Planning Guide provides the outline of a sample conversion workbook that you can use to write your conversion plan. The model workbook contains a checklist and some questions to help you generate ideas on what to include in your conversion plan.

3.4, ªPlan Examplesº on page 53 also provides a sample conversion project plan.

3.1.2.4 Two Phase Approach

The migration project can be broken into a few logical pieces that may help its execution. One method that has been successful is to begin with a mini project, phase 1, to identify and resolve your inventory. Proceeding with a known inventory will allow more precise pricing. The pricing for a conversion effort is based on inventory. It also provides information about the effort that may be required to recreate source materials. There are tools and service providers that perform these services. The second phase is the actual implementation.

The Phase 1 output is also a standalone deliverable that can be very useful for Year 2000 preparation.

3.1.2.5 Conversion Method

There are two basic approaches to the migration. One approach, referred to as the kernel approach, converts a single application or subsystem at a time. The other, called mass migration, converts all applications, the entire system, at the same time. The method or approach used will dictate the elements of the project plan. This chapter will explore the major considerations of using mass migration as a conversion method and as a conversion tool.

Two tools support or implement the mass migration approach. One of these tools, the IBM MVS-Migration System (MVS-MS), was previously licensed from

42VSE to OS/390 Migration Workbook

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.

IBM OS/390 Take Advantage Of Conversion Tools and Automation, Migration Plan Guide and Outline

Models: OS/390