Browse Prior Art Database

System Resource Controller Socket Model

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

Publishing Venue

IBM

Related People

Stokes, EJ: AUTHOR

Abstract

The figure depicts the socket model for the System Resource Controller (SRC) to communicate with command processes and subsystems. Requests submitted remotely are processed the same as if they were submitted locally. By using the internet socket family, requests can be processed independent of origin (local or remote). If local, then the loopback paths through the socket code are executed; otherwise, the data is placed on the network.

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

System Resource Controller Socket Model

       The figure depicts the socket model for the System
Resource Controller (SRC) to communicate with command processes and
subsystems.  Requests submitted remotely are processed the same as if
they were submitted locally.  By using the internet socket family,
requests can be processed independent of origin (local or remote).
If local, then the loopback paths through the socket code are
executed; otherwise, the data is placed on the network.

      The UDP protocol is used to communicate.  The nature of
communication between the command process, SRC, and subsystem is
generally a single packet, datagrams (UDP/light-weight protocol) can
be used.  TCP (a heavy-weight protocol) provides guaranteed delivery
and ordering.  Ordering here is really not important because
communication is generally a single packet.  Guaranteed delivery is
generally not a problem in the local case because loopback paths are
executed and packets never hit the wire.  In the remote case, this
could be a slight problem.  To overcome this problem, the command
process needs to set a timer to bound response time (not wait forever
for response).

      The items in the figure are defined below: SRC:  System
Resource Controller, proper Command Process:  Process that sends
commands to SRC Subsystem:  Daemon or other piece of code under
control of SRC commands
      The execution of a SRC command is summarized below.
  SRC is listening on a well-known port for work requests. Command
process connects to that well-known port and sends a work request to
SRC.  SRC examines that work request.  The work request may be
processed by SRC, or SRC may send it to the subsystem to be
processed.  If SRC processes the work request, SRC sends the response
to the command process.  Otherwise, SRC sends the request to the
subsystem on the port which SRC has specified that the subsystem is
to listen on for work requests.  The subsystem processes the work
request and sends the response directly to the command process that
originated the work request using the port that command process has
specified it is listening for the re   sponse.

      The detailed execution of a SRC command is documented below to
aid in unders...