Browse Prior Art Database

Architected Method of Executing Operations during Inactivity

IP.com Disclosure Number: IPCOM000112499D
Original Publication Date: 1994-May-01
Included in the Prior Art Database: 2005-Mar-27
Document File: 2 page(s) / 78K

Publishing Venue

IBM

Related People

Fisher, JO: AUTHOR [+2]

Abstract

This disclosure allows the user to perform predefined and 'on the fly' application and system operations during periods of inactivity. This disclosure is unique in that the user can define those operations before and during the use of a specific application. For example, the user could set up a word processor to spell check a document during five minute breaks. Thus, this allows the user to perform useful operations during periods of inactivity.

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

Architected Method of Executing Operations during Inactivity

      This disclosure allows the user to perform predefined and 'on
the fly' application and system operations during periods of
inactivity.  This disclosure is unique in that the user can define
those operations before and during the use of a specific application.
For example, the user could set up a word processor to spell check a
document during five minute breaks.  Thus, this allows the user to
perform useful operations during periods of inactivity.

      This disclosure is important in that there is currently no
known architected method of providing this type of function on OS/2*.
This architected method provides the following benefits:

1.  User productivity will increase since multiple supporting
    operations (e.g., spell checking a document, formatting a
    document, etc.)  can occur during periods of low activity.

2.  Applications can call other applications to perform requested
    commands during periods of low activity, using the architected
    API.

The software architecture consists of the following major components:

o   PROGRAM API.  This is the kernel API that provides the services
    for the Control Program (CP) to communicate with OS/2
    applications.

o   CONTROL PROGRAM (CP).  This is the main program that controls and
    monitors the execution of the instructions (i.e., SL operations)
    for each application.

o   USAGE MONITORING PROGRAM.  This program is responsible for
    monitoring the current activity loads of the CPU and DASD's and
    reporting that information to the kernel program.  The kernel
    program queries this status information via its API.

o   SCRIPT LANGUAGE (SL).  This is the high-level programming
    language used to define the precise instructions to be executed
    for each application.  This simple-to-use programming language
    defines the following major items:

    -   Any sequential, repetitive, or conditional instructions
    -   Instructions that should be performed based on time or date

o   CONTROL LIST (CL).  This is a list of all applications and system
    applications that have been regis...