Browse Prior Art Database

User Driven Configuration Parameter Subvectoring

IP.com Disclosure Number: IPCOM000121494D
Original Publication Date: 1991-Sep-01
Included in the Prior Art Database: 2005-Apr-03
Document File: 2 page(s) / 89K

Publishing Venue

IBM

Related People

Horton, VG: AUTHOR [+5]

Abstract

In many data communications environments, several communications processes may be functionally and physically grouped together into one process with one accessible interface. However, it may be necessary to communicate distinct sets of individual configuration parameters to the communications functions which have been grouped together. In addition, some configuration parameters may be specified by a communications architecture, while others are implementation-dependent and left to the product to specify.

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

User Driven Configuration Parameter Subvectoring

      In many data communications environments, several
communications processes may be functionally and physically grouped
together into one process with one accessible interface.  However, it
may be necessary to communicate distinct sets of individual
configuration parameters to the communications functions which have
been grouped together. In addition, some configuration parameters may
be specified by a communications architecture, while others are
implementation-dependent and left to the product to specify.
User-driven configuration parameter subvectoring allows for
specification of architected as well as product-specific
configuration parameters, while also providing a solution to the
problem of providing unique sets of configuration parameters to
processes which have been bundled together and which use a single
communications interface.

      The subvector structure for the configuration parameter
Interface Data (ID) field of a communications interface primitive
permits an organized method for communicating parameters across an
interface.  The configuration data is contained in a subvector with
two subfields for each entity. This allows several subvectors
containing different sets of configuration parameters to be contained
in the ID field of a communications primitive when more than one
communications function is bundled together into one entity.

      Each configuration parameter subvector is subdivided into two
subfields:  an architected configuration parameter subfield
(containing the original architected Interface Data field) identified
as subfield A and a product specific subfield identified as subfield
P.  The format of these subfields is shown in the figure.

      As shown in the figure, each subfield contains the following:
     ...