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: Cookbook, SG24-4775 for some more levels.

See the OS/390 Software Management detailed advice on how to manage software

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-Backsystem.)

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

Page 442 Page 444
Page 443
Image 443
IBM OS/390 manual Test Environments, Differences in Testing ²Philosophy², Terminology, 419
Page 442 Page 444

OS/390 specifications

IBM OS/390, a versatile operating system, was a cornerstone in enterprise environments and played a pivotal role in mainframe computing. Released in the mid-1990s, OS/390 combined the strengths of IBM's MVS (Multiple Virtual Storage) with new features and enhancements, targeting scalability, reliability, and performance in demanding business applications.

One of the key features of OS/390 was its robust support for multiple users and processes. The system allowed thousands of concurrent users to access applications and data, ensuring high availability and minimizing downtime—a critical requirement for many large organizations. This scalability was supported through various enhancements in memory management and processor scheduling, enabling optimal resource allocation across diverse workloads.

OS/390 was known for its superior workload management capabilities. The Workload Manager (WLM) component allowed administrators to define service policies, specifying how system resources would be allocated according to the priority of tasks. This ensured that critical business processes received the necessary resources while less critical tasks were managed more flexibly.

Another significant characteristic of OS/390 was its commitment to security. The operating system provided comprehensive security features, including user authentication, data encryption, and auditing capabilities. This focus on security was vital for organizations handling sensitive data, ensuring compliance with regulations and safeguarding against unauthorized access.

OS/390 also supported advanced technologies that facilitated integration and development. The system included features like the IBM CICS (Customer Information Control System) for transaction processing and IMS (Information Management System) for database management. These technologies allowed organizations to build robust, high-performance applications tailored to specific business needs.

The ease of network integration was another strength of OS/390. With the advent of the Internet and global connectivity, OS/390 systems could easily interface with various network protocols, enabling businesses to operate in a connected world. This inclusion paved the way for many organizations to expand their capabilities and offer new services, driving digital transformation.

In conclusion, IBM OS/390 represented a significant advancement in mainframe technology, combining scalability, security, and robust workload management. Its rich feature set and support for critical enterprise applications solidified its role as a vital component of many organizations' IT infrastructures, ensuring they could meet their operational challenges head-on while supporting future growth. As technology continues to evolve, the legacy of OS/390 remains influential in the realm of computing.
Top Page Image Contents