Browse Prior Art Database

Dynamic Offload of I/O Configuration Data

IP.com Disclosure Number: IPCOM000122205D
Original Publication Date: 1991-Nov-01
Included in the Prior Art Database: 2005-Apr-04
Document File: 2 page(s) / 63K

Publishing Venue

IBM

Related People

Cwiakala, R: AUTHOR [+5]

Abstract

This article describes a mechanism for offloading I/O configuration data, used by a channel subsystem and resident in the system area, into a hardware I/O configuration file for use during a subsequent hardware initialization process. The system area is non-program- addressable main storage. The mechanism is software controlled and is an improvement over the existing process used on IBM mainframes.

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

Dynamic Offload of I/O Configuration Data

      This article describes a mechanism for offloading I/O
configuration data, used by a channel subsystem and resident in the
system area, into a hardware I/O configuration file for use during a
subsequent hardware initialization process. The system area is
non-program- addressable main storage. The mechanism is software
controlled and is an improvement over the existing process used on
IBM mainframes.

      The initial build of the I/O configuration data in the system
area is done as part of a hardware initialization process.  The data
used exists in a hardware file and is created using an external
process that defines the I/O configuration.

      Subsequent to hardware initialization, a change is made to the
I/O configuration which requires a corresponding change to the I/O
configuration data.  The latter change is accomplished by control
program software, using existing special-purpose interfaces to the
hardware.

      In order to ensure that these changes to I/O configuration data
are available during a subsequent hardware initialization and are
identical representations of the system area changes, they must also
be saved in a hardware configuration file used for that purpose.  The
existing mechanism that creates the hardware I/O configuration file
is disjoint from the one used to change the I/O configuration data.
Given this characteristic, the potential exists for either the loss
of the I/O configuratio...