30.6.3 Methodology

In VSE, users with security needs frequently use one or another vendor security package, as IBM provides only simple access control and logging security. In the OS/390 environment, in addition to vendor program offerings, IBM provides the OS/390 Security Server (a follow on to the highly regarded RACF product).

The Security Server provides system security services to ensure secure access from batch and online user programs to flat files, VSAM files, and databases. Printout, job submission and other system facilities such as program source and load modules, TSO/ISPF functions, CICS Transaction Server, IMS, DB2 and other OS/390 subsystems all integrate with the OS/390 Security Server protection for their resources. A System Authorization (SAF) API interface is provided so that user application programs can use the Security Server to protect

application-specific resources.

30.7 Configuration Management

30.7.1 Overview

Configuration management is concerned with the generation and maintenance of a configuration database that contains information of all physical and logical resources and their relationships. Configuration is not concerned with implementing or managing changes to the information system resources, but rather with data on the location of components (current topology), their identifying attributes, their status (for example, active, online), future planning, and the process for gathering the configuration data.

For OS/390 accurate knowledge of the hardware physical configuration (connections of systems to I/O devices, systems to other systems), logical configuration (system and subsystem names, cross system connection definitions), and software configurations (product releases, libraries, and where they execute) becomes increasingly important as the environment grows. Inaccurate or obsolete configuration data can impact system availability and waste manual time hunting down and finding the proper information. This data is used within other disciplines, so the tasks for managing and maintaining it are important to carry out.

Configuration management data requirements include the following:

∙Standard data usage - a single definition of configuration data for each type of resource.

∙Shared, common data - ability to share configuration data among people, application, and subsystems. Sharing with the asset management discipline is particularly important.

∙Reliable data - the ability to dynamically update the configuration database.

30.7.2 Tasks

The configuration management process includes the following:

∙Configuration design - designing logical or physical, hardware, software, and applications configurations.

∙Environmental planning - determination of the physical specifications required to support a configuration.

Chapter 30. Systems Management Philosophy and Methodology 469

Page 492 Page 494
Page 493
Image 493
IBM OS/390 manual Methodology, Configuration Management Overview
Page 492 Page 494

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