Chapter 32. Conversion Process

Converting a data processing installation from VSE/ESA to OS/390 is a complex process that affects all areas of an installation. Personnel must learn different procedures; operations work changes in many ways and applications that run under VSE require conversion before they run under OS/390. Even managing the migration project, which includes planning, allocating people and resources and tracking the migration process, is a complex job.

Migration includes the entire process of moving your installation from VSE to MVS. Conversion deals with the changes that an application running under VSE requires to enable it to run under MVS.

This chapter:

∙

∙

∙

provides high level information about the conversion process directs the reader to resources for additional high level information summarizes the information of the preceding chapters

Major migration tasks and where task information resides in this book:

1Planning and installing the MVS system.

∙Refer to Chapter 25, ªPrepare the Migration Environmentº on page 401.

2Training personnel to work on the OS/390 system.

∙

∙

∙

∙

∙

Refer to 2.6, ªEducational Requirementsº on page 31.

Refer to Chapter 27, ªOrienting ICCF Users to TSO/ISPFº on page 437. Refer to Chapter 28, ªOrientation to OS/390 Console Operationº on page 443.

Refer to Chapter 29, ªOrientation for Utilitiesº on page 455. Refer to Appendix A, ªEducation Informationº on page535.

Each chapter contains information on personnel, training or OS/390 system use.

3Analyzing migration requirements and developing a migration plan that is specific for this site.

∙

∙

∙

Refer to 2.7, ªScope of Work and Challengesº on page 32. Refer to Chapter 3, ªDeveloping the Planº on page 41.

Refer to Chapter 3, ªDeveloping the Planº on page 41 and Appendix A of the MVS Migration System - Planning Guide, SB11-8077.

4Analyzing the VSE workload and developing a complete list of the applications to be converted.

∙

∙

Refer to 2.7, ªScope of Work and Challengesº on page 32. Refer to 32.4, ªPreparation Phasesº on page 493.

5Developing standards for application conversion that reflect your standards for the new OS/390 system.

∙

∙

∙

∙

Refer to 3.3.7, ªStandardized Conversion Deliverables and Automationº on page 51.

Refer to 5.2, ªData Set Naming Considerationsº on page 99.

Refer to 25.4, ªSet Up Standards, Procedures, and Documentationº on page 407.

Refer to Appendix C, ªDFSMS Naming Conventionsº on page 543.

© Copyright IBM Corp. 1998

481

Page 504 Page 506
Page 505
Image 505
IBM OS/390 manual Conversion Process, 481
Page 504 Page 506

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