Browse Prior Art Database

Unsolicited Notification by a Server in MVS to a List of Requesters

IP.com Disclosure Number: IPCOM000108031D
Original Publication Date: 1992-Jan-01
Included in the Prior Art Database: 2005-Mar-22
Document File: 1 page(s) / 44K

Publishing Venue

IBM

Related People

Cox, DR: AUTHOR [+3]

Abstract

This article describes the problem for OfficeVision*/MVS (OV/MVS) Servers in APPC/MVS to be able to set up a list of contacts of Clients or Requesters to do event notification. This would deal with the situation when a Server has started a unit of work. When that work is complete, a list of one or more users is to be notified of the completion. The work could be an asynchronous event, outside of the Service itself. The Service needs to set up the notification in advance of the completion and then the function would complete the notification based on parameters supplied. This function is based on the ability to do unsolicited notification.

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

Unsolicited Notification by a Server in MVS to a List of Requesters

       This article describes the problem for OfficeVision*/MVS
(OV/MVS) Servers in APPC/MVS to be able to set up a list of contacts
of Clients or Requesters to do event notification. This would deal
with the situation when a Server has started a unit of work. When
that work is complete, a list of one or more users is to be notified
of the completion. The work could be an asynchronous event, outside
of the Service itself. The Service needs to set up the notification
in advance of the completion and then the function would complete the
notification based on parameters supplied. This function is based on
the ability to do unsolicited notification.

      The solution to this problem is to develop additional features
on top of a generic function to deliver an unsolicited notification
to the user. The feature would allow the function to accept a request
to do unsolicited notification in advance. An Office component can
set up a list of users to be notified at the completion of an event.
An Event Control Block (ECB) is set up to be posted at the completion
of the the event. The Component also provides information on how to
notify the user, as only the component can understand how to perform
the presentation to the user. The function only provides the
communication protocol to reach the user, if possible. The component
must provide how to handle the information for the event completion
if the user is no...