IBM OS/390 User Manual

Page of 673
Chapter 2. Sizing the Effort
This chapter discusses the following topics:
2.1, Introduction to Sizing
2.2, OS/390 Components/Products/Subsystems
2.3, What Changes Between VSE and OS/390?
2.4, Who is Affected by This Migration?
2.5, Approaches to Migration
2.6, Educational Requirements
2.7, Scope of Work and Challenges
2.8, Cost Considerations
2.1 Introduction to Sizing
When undertaking a project such as migrating from VSE to OS/390 attention
always turns to how much effort is really involved. The sizing effort attempts to
get a fairly reasonable handle on the amount of effort and resources needed for
such a project. It is desired to be able to estimate with some degree of
confidence the human, system and financial resource requirements. This chapter
will discuss some of the key migration activities and issues, highlighting the
considerations that will affect the scope and size of this project. We will first
define two terms that are often used throughout this publication, migration and
conversion.
Migration is the process which takes the data processing workload, and
operations from the VSE environment to the OS/390 environment. This includes a
planning phase, a preparation phase, a conversion phase and a production
implementation phase.
Conversion is the process within the migration where programs, data, and JCL
are converted, tested, and cut over to production in the OS/390 environment.
2.1.1 Defining the Migration Project Objectives
Typical migration project objectives for an OS/390 migration project include a
combination of operational needs and cost/benefit requirements.
End-user transparency
Minimal disruption of operations and applications support
No overlap of dual VSE and OS/390 operations
Standardized and automated OS/390 applications fit for automated OS/390
operations
 Copyright IBM Corp. 1998 
13