Browse Prior Art Database

Performance Improvements between Requester and Server in OV/MVS

IP.com Disclosure Number: IPCOM000108555D
Original Publication Date: 1992-Jun-01
Included in the Prior Art Database: 2005-Mar-22
Document File: 2 page(s) / 80K

Publishing Venue

IBM

Related People

Cox, D: AUTHOR [+3]

Abstract

This article addresses the need to remove a major performance inhibitor between Requester and Server in OfficeVision*/MVS. It is the requirement for a Parser and a Builder for communication. The requirement for Generalized Data Stream (GDS) communication between Requester and Server in OV/MVS means that a Parser/Builder is needed by both sides in each communication. This requirement stems from the product restrictions by DISOSS on OV/MVS. A GDS protocol is a required tool to insure communication between unlike products or products at different version levels. However it is a performance inhibitor between requester and server from the same product at the same version level. Requests and replies are kept in control block format within the requester and the server.

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

Performance Improvements between Requester and Server in OV/MVS

       This article addresses the need to remove a major
performance inhibitor between Requester and Server in
OfficeVision*/MVS.  It is the requirement for a Parser and a Builder
for communication.  The requirement for Generalized Data Stream (GDS)
communication between Requester and Server in OV/MVS means that a
Parser/Builder is needed by both sides in each communication.  This
requirement stems from the product restrictions by DISOSS on OV/MVS.
A GDS protocol is a required tool to insure communication between
unlike products or products at different version levels. However it
is a performance inhibitor between requester and server from the same
product at the same version level. Requests and replies are kept in
control block format within the requester and the server.  However
when a request is passed from the requester to the server, it must be
changed into a GDS format, where an identifier is placed in front of
each parameter value and the entire request is placed within a GDS
wrapper.  Upon receipt, the request must be extracted from the GDS
wrapper and format, and placed into control block format for
processing.  The same process is repeated to handle the reply.

      The solution is to provide a second protocol handler for
requests and replies between Requester and Server in OV/MVS.  This is
a private protocol only for local communication where the request
will not flow outside the sysplex.  This second protocol handler
deals with requests and replies in control block format.  There is a
simple header to indicate the specific control block structure for
the request.  The control block is the same format as the server uses
internally.  This means that additional memory is not needed to
construct the control block from...