Refer to Chapter 3, ªDeveloping the Planº on page 41 for information on project staffing, assignments and responsibilities.

Refer to Appendix C, ªDFSMS Naming Conventionsº on page543 for information on data set naming conventions.

Refer to Appendix A of the MVS-MS Planning Guide for help developing the Migration Plan.

Refer to Appendix B of the MVS-MS Planning Guide for help developing the Conversion Plan.

Implement System Managed Storage (DFSMS)

It is strongly recommended that DFSMS be planned for and implemented from day one of the migration. The key benefit of implementing DFSMS is how it helps the installation be positioned for future growth. Implementing DFSMS also helps the conversion by providing structure for standards and naming conventions. Other benefits of installing DFSMS from the outset are:

1.No future conversion of the configuration is required.

2.Positioning for new software function and hardware support where most new functions in OS/390 have SMS as a prerequisite. Examples include data compression and extended data sets.

3.Provides DASD management.

4.Supports cataloging all your data sets from the beginning.

5.Less complicated JCL from a VSE user perspective through the use of data classes.

32.4.1 Phase 0: Project Management and Technical Leadership

A Project Manager/Technical Leader is assigned the responsibility for administration and technical direction of the conversion efforts. Project management activities consist of:

Developing detailed work plans and schedules

Evaluating the progress made against work plans and schedules

Conducting weekly progress review meetings

Conducting monthly project status reports

Providing liaison and coordination between all personnel involved

32.4.1.1 Project Planning and Orientation

The objective of this task is to develop detailed project plans and orient the conversion team and all personnel involved to the conversion approach and to the project plans. The project plans include:

Overall project plan

Online application test plan

Batch application test plan

Switchover plan

It is recommended to use a project management software tool to develop and update the project plans. An example of a project plan is provided in Chapter 3, ªDeveloping the Planº on page 41.

The project education sessions are scheduled:

494VSE to OS/390 Migration Workbook

Page 518
Image 518
IBM OS/390 manual Phase 0 Project Management and Technical Leadership, Project Planning and Orientation

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.