Browse Prior Art Database

Callable Dialog Manager

IP.com Disclosure Number: IPCOM000037061D
Original Publication Date: 1989-Nov-01
Included in the Prior Art Database: 2005-Jan-29
Document File: 4 page(s) / 55K

Publishing Venue

IBM

Related People

Buckheit, RT: AUTHOR [+2]

Abstract

Disclosed is a Callable Dialog Manager (CDM) for host operating systems.

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

Page 1 of 4

Callable Dialog Manager

Disclosed is a Callable Dialog Manager (CDM) for host operating systems.

Historically, a dialog manager has required the establishment of an environment in order to initialize the services it provides. The services depend upon structures, linkages and data areas created by the environment. The environment, however, implies that dialogs must execute within it. The environment may itself be incompatible with systems in which a dialog manager is desirable. Therefore, the environment limits the range of applicability of the dialog manager to systems in which it can be tolerated.

The CDM design provides a dialog manager concept not requiring an environment. It consists of individually callable services to initialize processing, define and manage variables, create and manage tables, display panels, and terminate processing. All services are designed to be independent of operating system features. Therefore, the CDM provides a base for dialog manager services that is portable across operating systems.

(Image Omitted)

The CDM is comprised of a set of dialog management services which will enable the creation of application dialogs that are portable between host operating systems.

The CDM has four unique aspects: callable architecture, interaction between user and service through a communication block, the creation of a virtually unlimited number of dialog manager instances, and storage management using pools.

The architecture of the CDM does not require establishment of an environment prior to execution of dialog management services.

In the CDM, processing is initiated with a service call invoked from within the user dialog. Once processing has been initiated, the user dialog communicates with the services through a small section of storage belonging to the user. This storage is called the dialog manager communication block. When the user dialog has completed its function and has no further use for the CDM services, processing is terminated with a final service call.

The callable architecture allows user applications to be executed in native environments independent of environmentally established structures.

Fig. 1 shows the general module flow for an invocation of a CDM service. A User Dialog 11 invokes a service through a call to the Program Interface Module 2 which identifies the Service Function Module 4 by scanning the Service Name Table 3. The Program Interface Module 2 then invokes the Service Function Module 4 and supplies the service parameter list. The Service Function Module calls the Service Parser Module 5 to validate the service parameter list. Once the parameter list has been validated, the Service Function Module 4 performs processing required for the service.

1

Page 2 of 4

The communication block, previously mentioned, is the communication mechanism between the dialog and the service. The communication block resides in storage belonging to the dialog, but its contents must only be altered by the CDM...