Browse Prior Art Database

Support of Distributed Computing Environment Remote Procedure Call Protocol in Customer Information Control System Client for Windows NT

IP.com Disclosure Number: IPCOM000119137D
Original Publication Date: 1997-Dec-01
Included in the Prior Art Database: 2005-Apr-01
Document File: 8 page(s) / 259K

Publishing Venue

IBM

Related People

Tran, TM: AUTHOR

Abstract

Disclosed is a Design and Implementation of Distributed Computing Environment (DCE) Remote Procedure Call (RPC) Protocol in Customer Information Control System (CICS*) Client for Windows NT**. The Design, however, can also be extendible to other Client platforms, such as OS/2*, AS/400*, S/390*, and Windows 95**.

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

Support of Distributed Computing Environment Remote Procedure Call
Protocol in Customer Information Control System Client for Windows
NT

      Disclosed is a Design and Implementation of Distributed
Computing Environment (DCE) Remote Procedure Call (RPC) Protocol in
Customer Information Control System (CICS*) Client for Windows NT**.
The Design, however, can also be extendible to other Client
platforms, such  as OS/2*, AS/400*, S/390*, and Windows 95**.

The CICS Client can be summarized as a while loop message processing
structure:
   WHILE NOT Close
   DO
     Get Next Message
     Process Message
     Release Message Data
   END

      Messages are generated either by Client application and flown
between Client and Server by means of a Protocol method.  For
example, Transmission Control Protocol/Internet Protocol (TCP/IP) is
using Socket  Protocol, whereas DCE is using Binding Protocol.  This
invention only deals with one thing, which is DCE Protocol.  First,
examine the overview  structure of the high level structure of CICS
Client, which is shown in  the Figure.  The interfaces, A, B, C, D,
and E, which are shown in the  Figure, are defined as follows:
  o  A - This is interprocess Transport.  It provides the
          connection between the main CICS client process
          and the application using the client.
  o  B - This defines the boundary between the Function Shipping
          and the Transaction Routing services and the internal
          client support for the External Call Interface (ECI),
          External Presentation Interface (EPI) and Emulator
          application.
  o  C - The data passed across this interface is packed and
          unpacked.
  o  D - This is a general purpose communication interface used
          by the client.
  o  E - This is an interface that each Protocol Driver (TCP/IP,
          NetBIOS, Systems Network Architecture (SNA), DCE RPC) must
          provide.

      And, this invention provides DCE RPC Protocol for E interface
in CICS Client for Windows NT.

      To minimize the configuration and system resources needed on
the server and client and to reduce the number of RPC calls made to
a minimum, a single RPC function will be provided to handle all
client-server communications or bindings.  This function will be
implemented in both the client and server, thus, both CICS client and
CICS server operate as RPC servers.
  o  CICS_RpcConverse
       This function sends a datastream from one system to
      another.  When it returns, it may include the response data
      stream.
        Format
     typedef struct {
       UINT32 Length;
       UINT8 *Data;
     } cics_buffer_t;
     INT32 CICS_RpcConverse(rpc_binding_handle_t  Binding,
                            cics_buffer_t...