Scheduling test activities

IPL the new release in a production environment after you have tested the new release with a simulated production workload that includes all applications and all non-IBM products, and that ensures that service level agreements can be met.

IPL in a shared resource environment after you have installed any coexistence PTFs.

If your production workload will require greater than 2 GB of real storage, be sure to use greater than 2 GB on your test image. In fact, the more storage you use above the 2 GB line on your test image, the greater the chance that pages will be backed up there, and the greater the odds of exposing problems during test rather than during production.

Perform function and stress test. Testing by IBM® does not replace the need for this testing in your own environment. Testing might include:

Initializing the system
Initializing JES2 or JES3
Logging on to TSO/E
Running the IVPs
Submitting a job
Checking the job's output
Starting customization of z/OS®
If CICS® or IMS™ is installed, initializing a region and signing on to a terminal
Bringing your ISV products into the test environment
Running critical production jobs
Supporting a representative interactive workload
Communicating with all networks
Testing critical functions in applications
Checking some of the paths not often taken
Checking for completeness of accounting records
Testing all non-IBM product functions
Bringing your applications into the test environment
Ensuring that performance goals stated in service level agreements can be met.

Do not complicate your testing by exploiting the new function that z/OS provides. Save that task until after you are successfully running in production.

You should have a fallback (backout) plan in case problems occur during testing and you have to fall back to your previous level.