IBM OS/390 manual System management facilities SMF. See SMF

Models: OS/390

1 673
Download 673 pages 53.75 Kb
Page 604
Image 604

Storage Management Subsystem (SMS). A component of MVS/DFP that is used to automate and centralize the management of storage by providing the storage administrator with control over data class, storage class, management class, storage group, and ACS routine definitions.

structured programming. A method for constructing programs using only hierarchically nested constructs each having a single entry and a single exit point.

Three types of control flow are used in structured programming: sequential, conditional, and iterative.

sublibrary. In VSE, a subdivision of a library. See also library.

subprogram. A program invoked by another program. Contrast with main program.

subroutine. A sequenced set of instructions or statements that may be used in one or more computer programs and at one or more points in a computer program. (3) A group of instructions that can be part of another routine or can be called by another program or routine.

subsystem. A secondary or subordinate system, usually capable of operating independently of, or asynchronously with, a controlling system.

supervisor. The part of a control program that coordinates the use of resources and maintains the flow of processing unit operations. See also system supervisor.

symbolic name. In a programming language, a unique name used to represent an entity such as a field, file, data structure, or label.

syntax. (1) The relationship among characters or groups of characters, independent of their meanings or the manner of their interpretation and use. (2) The rules governing the structure of a language.

syntax error. A compile-time error caused by incorrect syntax. See also semantic error.

sysplex. A multiple-MVS system environment that allows MCS consoles or extended MCS consoles to receive messages and send commands across systems.

system console. A console, usually equipped with a keyboard and display screen, that is used by an operator to control and communicate with a system.

system date. The date established for the system when it is started.

system generation (SYSGEN). The process of selecting optional parts of an operating system and of creating a particular operating system tailored to the requirements of a data processing installation.

system maintenance. The modification of a system to correct faults, to improve performance, or to adapt the system to a changed environment or changed requirements.

system management facilities (SMF). See SMF.

system-managed storage. Storage managed by the Storage Management Subsystem. SMS attempts to deliver required services for availability, performance, space, and security to applications. See also DFSMS environment.

system-managed volume. A DASD, optical, or tape volume that belongs to a storage group. Contrast with DFSMShsm-managed volume and DFSMSrmm-managed volume.

System Modification Program (SMP). A program used to install software and software changes on MVS systems.

system operator. An operator responsible for performing system- oriented procedures.

system programmer. A programmer who plans, generates, maintains, extends, and controls the use of an operating system with the aim of improving overall productivity of an installation.

system resources. Those resources controlled by the system, such as programs, devices, and storage areas that are assigned for use in jobs.

system software. Software that is part of or made available with a computer system and that determines how application programs are run; for example, an operating system. Contrast with application software.

system support. The continued provision of services and material necessary for the use and improvement of an implemented system.

SystemPac. A software package consisting of installed products for a ready-to-IPL system. Some of the products have been customized in response to information provided to IBM. A SystemPac can be used to install an MVS system for the first time or to replace an existing MVS system.

systems management. Functions in the application layer related to the management of Open Systems Interconnection resources and their status across all layers of the OSI architecture.

580VSE to OS/390 Migration Workbook

Page 604
Image 604
IBM OS/390 manual System management facilities SMF. See SMF

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.