Browse Prior Art Database

Transparent System Service Interface

IP.com Disclosure Number: IPCOM000080268D
Original Publication Date: 1973-Nov-01
Included in the Prior Art Database: 2005-Feb-27
Document File: 3 page(s) / 34K

Publishing Venue

IBM

Related People

Edel, TR: AUTHOR [+2]

Abstract

Current Common Services provided by a Software System must have "Built In" intelligence concerning the state of execution of its various requestors. Thus, its activities will directly vary depending on the environment of its requestor. Some examples of User states are as follows: -The User is Terminating (normally or abnormally). -The User does not want Service Validity Checking. -The User is testing a new version of a particular Service. -The Unending User Job merits special consideration within a Service that is affected by Time Zone Differences. -The User who had requested the Service is no longer in the System.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 54% of the total text.

Page 1 of 3

Transparent System Service Interface

Current Common Services provided by a Software System must have "Built In" intelligence concerning the state of execution of its various requestors. Thus, its activities will directly vary depending on the environment of its requestor. Some examples of User states are as follows: -The User is Terminating (normally or abnormally).

-The User does not want Service Validity Checking.

-The User is testing a new version of a particular Service.

-The Unending User Job merits special consideration within

a Service that is affected by Time Zone Differences.

-The User who had requested the Service is no longer in

the System.

-Messages generated by asynchronous Services requested by

a particular User are routed to various destinations,

depending on;

--Who the user is, and

--If the User Job is Active or Terminated.

-Selective Service Monitoring/Accounting on a per user basis.

This arrangement removes the requirement for various system services to interpret the execution states of its requestors at each execution, and to invoke various logic within the service depending on the user excution state. Intelligence concerning execution states of various requestors can be concentrated within the system, with the result being that no Service need be concerned about the invoker execution state.

All System Services are invoked "Indirectly" by requesting a service through an address value, pointing to another address value that is actually the Service Address Resolution. Thus, a control point is established between the invoker of a Service and the actual Service itself. Subsequently, on a Per User Basis, any authorized intelligence within the system may manipulate the actual Service Resolution transparent to both the requestor...