SystemView takes its bow on IBM stage
IBM describes SystemView as its systems management strategy for planning, co-ordinating and operating heterogeneous information systems. The strategy consists of the SystemView structure and conforming products, and the structure of SystemView is said to be based on open standards such as the Open Systems Interconnection model, as well as proprietary architectures like Systems Application Architecture and SNA – which sounds well-meaning but still theoretical and ill-defined. The three dimensions, which define guidelines, standards and interfaces for integrating applications are the end-use dimension, the application dimension, and the data dimension. The first is meant to provide users with a consistent view of applications, the second defines guidelines for the implementation of and integration of applications, and the data dimension is said to address requirements for standardised systems management data definitions and access.
SystemView Environments
IBM says that SystemView environments can range from small stand-alone local area networks to large multi-processor systems, and it identifies two categories of systems. The first is the managing system, which provides interfaces to plan, administer and control system resources, and the second is the managed system, which meets these interfaces. SystemView applications are to be implemented across System Application Architectures like OS/2, OS/400, VM/ESA and MVS/ESA. IBM says that the AIX network management environment includes interoperability features with the SystemView structure including communication with to the SystemView network management function for problem alerting and operator commands for using TCP/IP and OSI agents; remote operator access to AIX management functions and AIX can also receive remote log-in from the host via the Host Command Facility; and a receive and forward capability for SystemView software and file distribution via NetView Distribution Manager. IBM says that these interoperability features enable operators to extend SystemView capabilities into AIX environments, although the reverse seems unlikely.
SystemView Network Management and Storage Management
Open Network Management is claimed to be a key part of SystemView, addressing the ability to manage data, voice and transmission facilities in a distributed or centralised manner. The Open Network Management structure is said to support the manager-agent capability in SystemView, and the two structures are designed to provide a consistent end-user interface, to share data and common application services, and to make use of international standards for communication and management. The NetView family will be used to manage network resources, and NetView automation facilities are to provide a base for the automation facilities in the System/370 and System/390 environments of SystemView.
SystemView and the AS/400
IBM says that OS/400 Release 3 and Systems Management Utilities support SystemView and provide the means to achieving integrated systems management. The AS/400 supports SystemView’s application dimension, and the managing facilities of OS/400 include business and change management, configuration and operations management, and performance and problem management. Business management handles system resource descriptions and locations, dynamic resource usage tracking, upgrade order processing support and the system interface to IBMLink. The second deals with Program Temporary Fix management, ordering and distribution, as well as personal computer support or Distributed Systems Node Executive. Configuration addresses product data on the hardware and software components, auto configuration, resorce management and data on the hardware and software. Operations handles remote power on and storage and data management, and problems deals with recognition, analysis and alert management. Systems Management Utilities enables multi-site AS/400 installations to support end-users with communication lines via central site management. IBM says it plans to e
xtend the AS/400’s systems management by consistency through the end-use dimension and additional application dimension functions.
Operations Planning and Control/ESA 1
IBM says that Operations Planning and Control enables data processing departments to schedule the running of production batch jobs and manual activities both locally and remotely. It consists of the base for tracking functions, plus a controlling feature. OPC/ESA supports the latest enhancements to MVS/ESA and supersedes Operations Planning and Control/Advanced. It controls the production workload within a sysplex and supports Job Control Language handling. The program also manages the tracking of local and remote events and provides an automatic restart of failing system components. When using MVS/ESA’s cross-systems coupling facility services, it enables its own restart on a standby system upon failure and will also transfer the processing of a production workload. IBM says that the use of Interactive System Productivity Facility provides for dialogs while the Resource Access Control Facility guarantees security. Console automation is established in connection with NetView and AOC/MVS. OPC/ESA operates on any processor running under MVS/SP Version 3 Release 1 and MVS MVS/ESA SP Version 4 Release 1. The Tracker facility costs between $4,065 and $53,620 for Groups 18 to 60 respectively, and distributed licence options range from $3,048 to $40,215. Monthly licences start at $85 for Group 18, rising to $1,115 for Group 60, and distributed options go from $63 to $836. For the same Groups, the Controller is $8,940 to $117,950, with distributed options costing between $6,705 and $88,462. Monthly licences are from $186 to $2,455, and distributed licence options are between $139 and $1,841. It is available in the US on June 28, 1991, and national language versions follow on September 27.
