Browse Prior Art Database

Service Subtasks in Environment Facility

IP.com Disclosure Number: IPCOM000119549D
Original Publication Date: 1991-Feb-01
Included in the Prior Art Database: 2005-Apr-01
Document File: 1 page(s) / 40K

Publishing Venue

IBM

Related People

Cox, D: AUTHOR [+4]

Abstract

This article addresses the problem that Services in a Client/Server Transaction Model frequently need code to execute persistently, rather than just at the invocation of a request. Services, such as Office Components, need to be able to execute code at a global level, rather than just at the arrival of a transaction request. This can be just the ability to avoid repeated tasks at the initialization of a transaction, or code which oversees the execution of transaction programs for the Service. In a normal Client/Server Transaction Model, such as CICS, this is not possible. Therefore, designers and programmers must take additional resources to accomplish tasks. This affects code size, path length, and overall performance.

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

Service Subtasks in Environment Facility

      This article addresses the problem that Services in a
Client/Server Transaction Model frequently need code to execute
persistently, rather than just at the invocation of a request.
Services, such as Office Components, need to be able to execute code
at a global level, rather than just at the arrival of a transaction
request. This can be just the ability to avoid repeated tasks at the
initialization of a transaction, or code which oversees the execution
of transaction programs for the Service. In a normal Client/Server
Transaction Model, such as CICS, this is not possible.  Therefore,
designers and programmers must take additional resources to
accomplish tasks.  This affects code size, path length, and overall
performance.

      The solution for this problem in the Office Platform in MVS is
to enable services to execute code under the Environment Facility
(EF).  It is a started task, which is active during the life of the
Office Environment. Office Services can be executed as subtasks under
the Environment Facility.  As subtasks, they can be dispatched
whenever work is needed without the overhead of a separate address
space. EF can monitor the subtask and take corrective action in case
of abnormal termination.  The Service has access to all Office
Platform Resources, including allocating LU 6.2 conversations or
starting subtasks underneath themselves. The subtask can be requested
at initialization of the Office Glo...