IBM OS/390 User Manual
the third job in the sequence is missing due to being treated as a temporary
data set.
data set.
The management of transition files is very different between VSE and OS/390. In
OS/390 there are only a couple of possibilities. In VSE it depends on the type of
organization, the products used and the traditions followed.
OS/390 there are only a couple of possibilities. In VSE it depends on the type of
organization, the products used and the traditions followed.
These problems don
′
t show up until the applications are tested together. This is
the right time for these to surface. If these all occurred during parallel testing it
would take a very long time to complete.
would take a very long time to complete.
32.5.7.1 Data Migration in System Testing
The system test phase may or may not require that more data is available but
frequently requires that more accurate data is needed. An example is working
with databases that are two or three months old. In some cases these
applications will not run because they have been written to work only on recent
data. Recent data may be required. Another hurdle can be that these
applications have dependencies on batch data feeds to them.
frequently requires that more accurate data is needed. An example is working
with databases that are two or three months old. In some cases these
applications will not run because they have been written to work only on recent
data. Recent data may be required. Another hurdle can be that these
applications have dependencies on batch data feeds to them.
32.5.8 Parallel/Production Simulation Testing
Parallel testing is more representative of what the system will be like in OS/390.
In parallel testing you start with a day, typically a Sunday, and then do one day
at a time. The data from each day is scrutinized. Here the end user community
will get involved in testing. Output reports are reviewed and verified that they
are what they should be. This depth of review and comparison also requires that
in parallel testing you start to synchronize the data between systems.
In parallel testing you start with a day, typically a Sunday, and then do one day
at a time. The data from each day is scrutinized. Here the end user community
will get involved in testing. Output reports are reviewed and verified that they
are what they should be. This depth of review and comparison also requires that
in parallel testing you start to synchronize the data between systems.
At this point your network should provide access to this environment from any
terminal. This is an important consideration in allowing quantities of end users
on the system who should not be restricted to a small number of terminals with
access to MVS.
terminal. This is an important consideration in allowing quantities of end users
on the system who should not be restricted to a small number of terminals with
access to MVS.
Parallel (batch) production tests will include all jobs executed for a period-end
day. Duplicating VSE execution will not always be possible, due to the integration
between online and batch applications and some side effects of job execution
date.
day. Duplicating VSE execution will not always be possible, due to the integration
between online and batch applications and some side effects of job execution
date.
The final phase of parallel testing is ensuring the output is the same from both
systems, where actual production is compared to the test output. In this phase
there are two systems running in parallel. Monday is run on the OS/390 system
and compared to Monday
systems, where actual production is compared to the test output. In this phase
there are two systems running in parallel. Monday is run on the OS/390 system
and compared to Monday
′
s output and reports from the VSE production system.
For week ending, month ending and year ending scenarios that actual date
change becomes the test.
change becomes the test.
32.5.8.1 Data Migration in Parallel Testing
In parallel testing the data in the systems needs to be synchronized as you will
be comparing production runs under VSE with test runs under OS/390. Typically
by this time you have done switchover rehearsals a couple times. Now just
before parallel testing begins you will synchronize the data for a particular day,
for example, Monday or Tuesday.
be comparing production runs under VSE with test runs under OS/390. Typically
by this time you have done switchover rehearsals a couple times. Now just
before parallel testing begins you will synchronize the data for a particular day,
for example, Monday or Tuesday.
514
VSE to OS/390 Migration Workbook