Browse Prior Art Database

Unsolicited Notification by a Server in MVS to a Requester in CICS

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

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 begin contact with a Client or Requester in CICS/MVS* or other environments accessible by a LU 6.2 conversation. The Requester may or may not be active within that environment at that point in time. In the normal Client Server model, the the Requester begins the conversation and makes a request for work from the Server. The work is completed and the Requester is notified and the conversation ends. There are times, such as asynchronous work being completed or mail arriving for the user, that the Service must begin the contact with Requester. As all components need this function at times, a generic function is needed to carry out unsolicited notification. In addition, the location of the user should be transparent to the Server.

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

Unsolicited Notification by a Server in MVS to a Requester in CICS

       This article describes the problem for OfficeVision*/MVS
(OV/MVS) Servers in APPC/MVS to be able to begin contact with a
Client or Requester in CICS/MVS* or other environments accessible by
a LU 6.2 conversation.  The Requester may or may not be active within
that environment at that point in time. In the normal Client Server
model, the the Requester begins the conversation and makes a request
for work from the Server. The work is completed and the Requester is
notified and the conversation ends. There are times, such as
asynchronous work being completed or mail arriving for the user, that
the Service must begin the contact with Requester. As all components
need this function at times, a generic function is needed to carry
out unsolicited notification. In addition, the location of the user
should be transparent to the Server.

      The solution to this problem is to develop a generic function
to deliver an unsolicited notification to the user. This function
must track and keep the location of a user. Then, when a Service
needs to contact the user, it makes the request to this function. If
the user is a CICS requester or another environment accessible
through LU 6.2, then the function allocates a LU 6.2 conversation
with the CICS region or other environment using the information it
obtained previously.  The actual notification is carried out by the
component, as the information is component...