Browse Prior Art Database

Dynamically Networked OS/2 Queues

IP.com Disclosure Number: IPCOM000104441D
Original Publication Date: 1993-Apr-01
Included in the Prior Art Database: 2005-Mar-19
Document File: 4 page(s) / 110K

Publishing Venue

IBM

Related People

Cardone, RJ: AUTHOR

Abstract

Disclosed is a design that extends native OS/2* queuing capabilities across a local area network (LAN). Applications that use the Network Queuing Service manipulate queues in the same manner as they would using native OS/2 APIs. Applications may open, close, write or query queues that exist on the same or different OS/2 platforms. These applications do not know the actual LAN without previous definition or configuration.

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

Dynamically Networked OS/2 Queues

      Disclosed is a design that extends native OS/2* queuing
capabilities across a local area network (LAN).  Applications that
use the Network Queuing Service manipulate queues in the same manner
as they would using native OS/2 APIs.  Applications may open, close,
write or query queues that exist on the same or different OS/2
platforms.  These applications do not know the actual LAN without
previous definition or configuration.

      In the diagram, application A1 could open queues owned by
applications A2 and B2 using the same API, even though the queues
exist on different nodes.  Application AI has no knowledge of the LAN
location of either queue.  These queues behave exactly like native
OS/2 queues from the perspective of each application.  Any number of
nodes may be participating in networked queuing at any time.

      The novelty of the Network Queuing Service design is that no
communication predefinition or static configuration tables are
required.  Communication routing is established when queues are
opened.  Network nodes do not share or synchronize configuration
information.  This allows the network configuration to change
dynamically with little overhead.

      The Network Queuing Service consists of a set of Network
Queuing APIs implemented in a dynamic link library (dll) and a
Network Queue Controller program implemented in an executable (exe)
module.  Required are the base OS/2 operating system, a LAN
attachment and an implementation-specified LAN communication
protocol.  This protocol must support connection-oriented (session)
and connectionless (broadcast) communication.  NETBIOS is an example
of such a protocol.

      To participate in networked queuing, applications us the
following APIs instead of the standard OS/2 queuing APIs:

1.  CloseQueue
2.  CreateQueue
3.  OpenQueue
4.  QueryQueue
5.  PeekQueue
6.  PurgeQueue
7.  ReadQueue
8.  WriteQueue

      The calling paraeters for each API exactly match, in number and
function, the parameters of the corresponding OS/2 API
(DosCloseQueue, DosCreateQueue, etc.).  With one exception, all API
parameters have the same data type and length as in the corresponding
OS/2 API.  The single exception is the queue handle parameter found
on each API which is not an OS/2 queue handle, but a Network Queuing
Services handle.

      The open API will attempt to open the target queue on the
target...