IBM OS/390 User Manual
The large number of inactive and non-critical or obsolete tape files is not
migrated. They are either eliminated, or the VSE volumes are set aside together
with a last copy of the VSE tape file catalog at switchover time.
migrated. They are either eliminated, or the VSE volumes are set aside together
with a last copy of the VSE tape file catalog at switchover time.
Any automated operations product, which will be used for actual production after
switchover, must be installed, loaded with data used in production mode during
regression testing, not for sample unit testing, but starting with full-size
application functional testing and definitely throughout simulated production
testing (see regression testing below).
switchover, must be installed, loaded with data used in production mode during
regression testing, not for sample unit testing, but starting with full-size
application functional testing and definitely throughout simulated production
testing (see regression testing below).
Designing implementation standards for an OS/390 job scheduler or report
manager, and loading them with job scheduling or report management
instructions, is best performed with the on-site assistance of a specialist acting
as a mentor and a tutor. Such a specialist may either be provided by the vendor
(part of the product licensing agreement) or hired outside for a couple of months.
The basic education included in the license agreement brings some
understanding of the product features and limited hands-on practice, but it
doesn
manager, and loading them with job scheduling or report management
instructions, is best performed with the on-site assistance of a specialist acting
as a mentor and a tutor. Such a specialist may either be provided by the vendor
(part of the product licensing agreement) or hired outside for a couple of months.
The basic education included in the license agreement brings some
understanding of the product features and limited hands-on practice, but it
doesn
′
t replace the experience of a true specialist when it comes to full size
implementation as experienced in a mass conversion from VSE to OS/390.
32.5.5 Initialization Testing
Initialization tests are performed to verify that online applications (tables,
transaction programs, screens, and files) have been properly defined to CICS.
Transactions are started to verify that the screens come up as expected.
Initialization test scripts identify the minimum input required to get from a screen
to the next one. At this level of testing, results and file updates are not verified.
transaction programs, screens, and files) have been properly defined to CICS.
Transactions are started to verify that the screens come up as expected.
Initialization test scripts identify the minimum input required to get from a screen
to the next one. At this level of testing, results and file updates are not verified.
This is a time to ensure the basics work. Many problems can surface here
including mistakes in setting up the CICS environment. Frequently terminal
definitions or file definitions need to be changed. During this process you are
testing both your applications and CICS itself.
including mistakes in setting up the CICS environment. Frequently terminal
definitions or file definitions need to be changed. During this process you are
testing both your applications and CICS itself.
32.5.6 Unit Testing
Unit testing is the first phase of testing. Early unit testing is done using a
sampling of jobs and applications. These should be a representative sample, a
good mix of your jobs and applications used to expose problems. The idea
behind the approach is that you will discover some problems. These early
problems will be global problems that affect all your jobs and applications. You
will go in and fix these problems and not rediscover these as you test other
areas. If you tested everything at once, you would discover and rediscover the
same errors over and over again.
sampling of jobs and applications. These should be a representative sample, a
good mix of your jobs and applications used to expose problems. The idea
behind the approach is that you will discover some problems. These early
problems will be global problems that affect all your jobs and applications. You
will go in and fix these problems and not rediscover these as you test other
areas. If you tested everything at once, you would discover and rediscover the
same errors over and over again.
An approach for testing that works in most migrations is to separate the test
environments into two distinct areas. These two areas are online CICS and batch
applications. Typically the online portion is tested first. The online testing is
easiest because there is limited JCL conversion involved. Online testing is also
unique because it is converted once and you are through with it.
environments into two distinct areas. These two areas are online CICS and batch
applications. Typically the online portion is tested first. The online testing is
easiest because there is limited JCL conversion involved. Online testing is also
unique because it is converted once and you are through with it.
Chapter 32. Conversion Process
511