IBM OS/390 User Manual

Page of 673
Application personnel should be made responsible for providing test data,
and for evaluating, and approving application test results. (Obtaining test
data can be a problem - early plans should be made to define and obtain
test data.).
Involvement of applications to some degree in the test process can prove
beneficial at OS/390 switchover and initial OS/390 production.
Operations personnel should do the operating during testing. This is a vital
part of their training. Operations personnel should be pointing out
ease-of-use changes that can be made thereby improving OS/390 production
jobstreams; that is, their feedback is important. They should also be
preparing application 
Run Books
″ 
during this time.
Systems programmer personnel should only monitor system activity (for
example, performance) and assist in problem resolution during tests; that is,
they should not be running the tests.
Online applications should be stress and performance tested prior to
production.
This type of testing involves bringing in (if on a weekend) as many users as
possible to 
bang away
″ 
at the terminals with as many different transaction
types as possible. CPU-intensive batch, dump/restores, and other jobs that
heavily load the system should be running during these tests, thereby better
insuring good performance of online systems during peak system usage.
MVS Tools Testing
The tools selected for MVS operations (for example, tape manager, job
scheduler, job preparation and report manager) should be used for the batch
functional and parallel production tests in order to validate their installation and
setup. If a job scheduler will be used in OS/390 production then use the same
job scheduler during parallel testing.
DASD Requirements
Data migration during the testing phase creates a need for extra DASD. It is a
far better scenario to overestimate your needs than struggle with insufficient
DASD. Securing ample DASD can also be very helpful in reducing the time
required for migration of databases. If the installation is growing in size it will
generally not take long to make use of this capacity anyway.
Subsystem Storage Protect
It is recommended the implementation of SSP be delayed until after testing. The
problem that can occur is that once implemented it can be difficult to identify the
source of some problems and attribute them to testing old applications, to the
SSP install or to a conversion issue.
32.5.4.3 Test Plan
Before any testing begins for any phase of testing the test group/team need to
assemble and a test plan developed. Determinations need to be made about
what actions will take place in each of the phases. Typical test plans turn out to
be checklists that will be worked against. One team member will have the
responsibility to sign off on each checklist item and signify whether the task was
successfully completed or not. For those tasks that were not successfully
completed this person would have the responsibility for the remedial plan. Each
508
VSE to OS/390 Migration Workbook