Chapter 26. Test Environments
This chapter describes the different needs for test systems during and after the
migration to OS/390. There are many valid test configurations which vary
according to your installation′s testing and maintenance philosophies, as well as
your environment.
Here are some of the discussion points:
•
VM, LPAR, or stand-alone test systems
•
Number and availability of test systems
•
Inter-connectivity and isolation of test systems
•
Shared DASD or cloned data between production and test systems
References for additional information: See the
OS/390 Software Management
Cookbook
, SG24-4775 for some more detailed advice on how to manage software
levels.
26.1 Introduction
Just as you need a test VSE system to test out maintenance and new releases,
you will need a test OS/390 system when you go to OS/390. As part of this
conversion, you will also need test OS/390 systems for systems programmer
tailoring and testing (a ″sand-box″), application conversion and testing, and
fallback or rescue situations.
26.1.1 Differences in Testing ″Philosophy″
As your production system′s availability requirements get more demanding, so
will your need for a separate test system.
You also will want to apply maintenance and upgrade your system more
frequently with OS/390 than you did with VSE.
26.1.2 Terminology
The term ″Test System″ means different things to different people. Any system
that is not a ″Production System″ required for supporting the primary business of
the company is a ″Test System.″
There are different test system requirements and many ways to set them up.
Here is a sample set of three different test OS/390 systems during the life of the
conversion project. They will also be the basis after you go into production on
OS/390.
Backup System A system that is usually not running, but available to IPL
should one of your systems become inoperable. (Also
called the Rescue or Fall-Back system.)
This system should have a minimum number of volumes,
and can be saved to tape and restored by stand-alone
DSS.
Copyright IBM Corp. 1998 419