Browse Prior Art Database

Officevision/MVS Requestors in MVS

IP.com Disclosure Number: IPCOM000101616D
Original Publication Date: 1990-Aug-01
Included in the Prior Art Database: 2005-Mar-16
Document File: 1 page(s) / 36K

Publishing Venue

IBM

Related People

Dalglish, C: AUTHOR [+3]

Abstract

This article describes the techniques to gain the ability to allow all environments to reach strategic Office Services in MVS. For existing MVS Office products using DISOSS and Document Interchange Architecture version 1, these protocols were published. Then anyone could write requests to DISOSS, which provides Office Services, by conforming to the architected protocols. In Strategic Office in MVS, there will be Requesters and Servers which will work on the Client/Server Model. The published interface to Strategic Office will be the Programming Interface to the Requester.

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

Officevision/MVS Requestors in MVS

       This article describes the techniques to gain the ability
to allow all environments to reach strategic Office Services in MVS.
For existing MVS Office products using DISOSS and Document
Interchange Architecture version 1, these protocols were published.
Then anyone could write requests to DISOSS, which provides Office
Services, by conforming to the architected protocols. In Strategic
Office in MVS, there will be Requesters and Servers which will work
on the Client/Server Model. The published interface to Strategic
Office will be the Programming Interface to the Requester.

      This would mean that an environment must have a local Strategic
Requester to reach these Services. However, these Requesters will not
be available in all environments.  The solution is to allow
environments without strategic Office Requesters to reach the Office
Requesters Interface in MVS. The Office Requesters would be made
available to anyone who can conduct a LU 6.2 conversation. We provide
the Strategic Office Requester as the Transaction Program Partner in
a LU 6.2 conversation.  This means that the other environment begins
a conversation with the Requester using the published Interface
information.  Then the Requester begins a conversation with the
Service to carry out the request. When the Service provides the
answer, it is returned to the other environment in the original
conversation. This would allow people from non-IBM environments or...