References you can consult for additional information about the conversion specification phases include:

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

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

Refer to Chapter 3 of the MVS-MS Planning Guide named ²Developing the Conversion Plan².

Refer to specific product, program or utility migration guides. Examples include COBOL or DB2 migration guides.

Refer to MVS-MS Production Standards document for information on JCL standards. It does not provide guidance on programs. It does provide a model of how to structure your jobs, job names, job step names and data set names.

Recommendations for the specifications phase include taking a training class on the installation of System Managed Storage (SMS).

The major elements of the Specification phase are:

1.Analyze the VSE source material

2.Design the MVS target output

3.Determine the method to get from source to target

32.4.4.1 Analyze the VSE Source Material

This task is a process of looking at the source material and referring to the checklist of specification considerations. Your specification document can be based on the checklist in the MVS MS Planning Guide - Appendix A . From this comparison you can identify the problems or exceptions needing to be resolved by the conversion team. You may find you are lacking a key utility, or have not identified a plan to deal with a unique operation or that you have odd JCL.

The analysis of the VSE material is both qualitative and quantitative. Qualitative analysis consists of listing the types of syntax that are being used in VSE, and defining the types of replacement syntax that will be used in OS/390. Quantitative analysis consists of determining the number of times that each type of syntax occurs within the VSE material.

Quantitative analysis is performed with scan utilities. It is essential in determining the conversion approach to be used. While conversion issues that occur numerous times are addressed with automated solutions (if technically possible), low occurrence conversion issues may be addressed with manual positioning of the VSE material (when possible) or even manual modification of the OS/390 version.

The resolution can come during meetings with the services provider and/or site team where explanations can be presented of why certain things are done the way they are or why things are where they are.

500VSE to OS/390 Migration Workbook

Page 524
Image 524
IBM OS/390 manual Analyze the VSE Source Material

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.