Dismiss
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

Centralized Control of the Data of Sna/Hlp

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

Publishing Venue

IBM

Related People

Elliott, LC: AUTHOR [+4]

Abstract

This article describes a method for the control of processing incoming communication that consists of System Network Architecture (SNA) and High Level Protocol (HLP). This method handles incoming reception, tracking, distribution, and error checking a clear and efficient manner. It also isolates the rest the system from the low level communication buffer

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

Centralized Control of the Data of Sna/Hlp

       This article describes a method for the control of
processing incoming communication that consists of System Network
Architecture (SNA) and High Level Protocol (HLP).  This method
handles incoming reception, tracking, distribution, and error
checking a clear and efficient manner.  It also isolates the rest the
system from the low level communication buffer

      Remote Data Services is a component of the OS/2* Edition Data
Base Manager.  Remote Data Services is for directing a database
kernel request to a which resides on a different machine.  The
request and any associated data must be transmitted to the database.
In addition, the return data and error must be transmitted to the
"requestor" after the has been processed.  To direct the request,
complex streams must be built and sent between the partner

      Remote Data Services uses a high level protocol (called in this
article) to transmit the request, replies, and  Physically, the data
transferred is directed by the Communications Manager.  The
Communication Manager and transmits data in packets called SNA
logical  The HLP data stream consists of multiple objects. single HLP
data stream may span over several SNA logical and could be several
million bytes long.  Also, one more HLP objects may be contained in a
logical record, or object may span SNA logical records.

      The interface to the OS/2 Communications Manager is a buffer.
The length of this buffer can be a via a configuration  As shown in
the figure, the buffer length and SNA logical record length be
different and are in most cases.  One SNA logical may fill several
communication buffers.  On the other one buffer may contain several
short SNA logical  Proper handling of incoming data, SNA logical and
communication buffers is critical to the of distributed applications.

      In order to handle this dynamic environment, a approach has
been adopted.  The protocol processes the objects within the HLP data
stream. SNA logical record handler is called by the HLP to remove the
SNA logical record header from the HLP data stream.  The SNA logical
handler performs SNA logical record receiving and tasks.  The
communication buffer handler is called the SNA logical record handler
in order to receive data the communication buffers and for tracking
functions.

      1.   The protocol manager starts the process by that the SNA
logical record handler the first n bytes of an HLP object into a area
owned by the protocol manager.  The to be copied is passed on the
interface.

      2.   On the first request, the SNA logical record must first
obtain the SNA logical record and then obtain the HLP object.  It
that the communication buffer manager the header into a data area
controlled...