Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Subcontractor Agent Service for a File Access Processor

IP.com Disclosure Number: IPCOM000034202D
Original Publication Date: 1989-Jan-01
Included in the Prior Art Database: 2005-Jan-27
Document File: 3 page(s) / 58K

Publishing Venue

IBM

Related People

Catino, RJ: AUTHOR

Abstract

A File Access Processor (FAP) is responsible for servicing requests on behalf of application support processors (ASPs) which submit requests to and receive responses from FAP using a connection-oriented communication protocol provided by a facility termed Inter-Processor Communications Manager. Fig. 1 illustrates the interaction between an ASP and the FAP. (Image Omitted) In order to process requests on behalf of the application support processor, the FAP manages data structures which serve to process the request for the application support processor within the FAP. These data structures are called agent structures. Once a request is received the FAP dynamically assigns an agent structure to process a collection of related requests that comprise a logical unit of work (LUW).

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 48% of the total text.

Page 1 of 3

Subcontractor Agent Service for a File Access Processor

A File Access Processor (FAP) is responsible for servicing requests on behalf of application support processors (ASPs) which submit requests to and receive responses from FAP using a connection-oriented communication protocol provided by a facility termed Inter-Processor Communications Manager. Fig. 1 illustrates the interaction between an ASP and the FAP.

(Image Omitted)

In order to process requests on behalf of the application support processor, the FAP manages data structures which serve to process the request for the application support processor within the FAP. These data structures are called agent structures. Once a request is received the FAP dynamically assigns an agent structure to process a collection of related requests that comprise a logical unit of work (LUW). The agent structure is used for the duration of the LUW; once the LUW completes, the agent structure is used to process another LUW for the same or another ASP. Agent structures in FAP are composed of two parts - real agents and pseudo agents. Real agents contain data about the LUW being processed by the ASP, and pseudo agents contain communication about the current connection to the FAP, as well as application status data which persists for the duration of the ASP's connection to the FAP. Real agents allow an LUW to be processed by the FAP on behalf of the ASP. Real agents provide the data areas required to execute server requests as required by various subcomponents of FAP. Real agents are dispatchable entities that are dispatched by FAP. A pseudo agent cannot be dispatched unless it is associated with a real agent. Pseudo agents contain information about the connection between the ASP and the FAP. Because less storage is needed to contain communications information than to contain LUW information, the FAP can support many more pseudo agents than real agents, and dynamically associate a pseudo agent with a real agent when an ASP begins an LUW. This dynamic association of agents allows the FAP to support many more connections than it would if one real agent were used per connection. Fig. 2 illustrates the connection of an ASP to an agent structure in the FAP. The subcontractor agent is a real agent that is available for executing functions on behalf of ASPs or the FAP itself. Under normal circumstances, all the processing done on behalf of the ASP is done using its assigned real agent and pseudo agent. Because ASPs may execute multiple LUWs, there may be times when ASPs are between LUWs, whereby they will have pseudo agents but not real agents. If an ASP wishes to terminate its connection to the FAP while the ASP is is between LUWs, it initiates its connection termination processing by informing the Inter-Processor Communications Manager that it wishes to discontinue its conection with the FAP. In turn, the Inter-processor Communications Manager indicates to the FAP that the ASP wishes to terminate its c...