InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Central Service Point for 370/ESA Systems

IP.com Disclosure Number: IPCOM000100431D
Original Publication Date: 1990-Apr-01
Included in the Prior Art Database: 2005-Mar-15
Document File: 2 page(s) / 47K

Publishing Venue


Related People

Pfeiffer, RT: AUTHOR


Disclosed is a concept which allows for a common Central Service Point to exist across all 370/ESA systems.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 80% of the total text.

Central Service Point for 370/ESA Systems

       Disclosed is a concept which allows for a common Central
Service Point to exist across all 370/ESA systems.

      The concept addresses several current development issues which
directly impact both ease of use and price of 370/ESA systems.  The
issues are:
1.   Current Input/Output subsystems require varied service points,
many times requiring additional, specific, external hardware, to
provide for Reliability, Availability and Serviceability (RAS)
2.   The vast effort required to coordinate Input/Output subsystem
microcode RAS function with each IBM-supported operating system if
each operating system were individually required to write software
implementing a Central Service Point.
3.   Provide the user with a single look and feel service interface
over the full range of 370/ESA systems.

      The concept uses the PR/SM hypervisor as a base for the Central
Service Point.  The Central Service Point focuses the set of RAS host
functions supporting Input/Output subsystems attached to the host.
As shown in the following diagram, the Central Service Point (CSP)
exists as a separate machine within the 370/ESA system.  The PR/SM
hypervisor glues the CSP to the I/O subsystems without causing
impacts to each of the several 370 operating systems used on 370/ESA
systems.  The CSP provides a central point from which services for
the system environment, particularly Input/Output subsystems are