30.8 Asset Management

30.8.1 Overview

Asset management provides for managing the information technology inventory of resources, including both physical and intellectual assets. The components that you will use to support your workloads in the OS/390 environment all have business attributes - just like any asset in your company - that have to be accurately known and tracked.

30.8.2 Tasks

The required activities for asset management include:

∙Administrative data - inserting into the central configuration database information such as the cost of components, their contracted maintenance expiration date, the eligible suppliers, and so on.

∙Ownership assigned - controlling who is assigned as the owner of the assets, to ensure reliable and up-to-date data.

∙Life cycle control - following a resource from identification as a requirement through purchase, installation, depreciation, and finally, disposal.

∙Integration with the change process - this data is typically not captured automatically, and must be gained through administrative applications. Any means possible to ensure consistent data by interaction with other manual or automated processes is required.

30.8.3Methodology

This process is not as critical during a migration, since the emphasis is on ensuring the components are defined and working properly together to support the migrated workload. In the long run the asset information can help identify some of the costs of running the installation, and when from a financial standpoint it makes sense to change or upgrade components. Asset management information can be kept in files, a database system, or a product like TME 10 Information Management; it should be kept where it can be easily related to the configuration data and activities mentioned earlier.

30.9 Accounting Management

30.9.1 Overview

Accounting management allows the managers of the enterprise information system to account accurately and efficiently for system and resource usage against the registered users of the systems. This is commonly known as

²chargeback². If you were doing this in the VSE environment you will likely want to continue this, so knowing where OS/390 produces accounting data and how to get to it will be important. What is accounted for and charged back varies widely by company.

Chapter 30. Systems Management Philosophy and Methodology 471

Page 494 Page 496
Page 495
Image 495
IBM OS/390 manual Asset Management Overview, Accounting Management Overview
Page 494 Page 496

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