Browse Prior Art Database

Conditional Line Execution Process

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

Publishing Venue

IBM

Related People

Anderson, B: AUTHOR [+3]

Abstract

Disclosed is a process by which the execution of a function can be dynamically controlled by a user on a function and caller basis. It is referred to as the Conditional Line Execution (CLE) procedure.

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

Conditional Line Execution Process

      Disclosed is a process by which the execution of a function can
be dynamically controlled by a user on a function and caller basis.
It is referred to as the Conditional Line Execution (CLE) procedure.

      When a software developer utilizes a function such as an error
log function or message display function, the intent of this use is
to help the customer diagnose problems detected in software programs.
Providing this data is often useful, but sometimes it can be a
hindrance.  If a program is in a loop utilizing a function such as an
error log facility, the error log can fill up or the machine cycles
required to continually log the error because of the loop can cause
the machine to lock-up.  The user of a program needs to have control
to disable some or all calls by an application for a particular
service.

      In order to fulfill this requirement, the CLE process was
invented.  CLE provides this function through four components:

1.  a unique identifier placed on the call by the product developer
    to the facility of the service (e.g., error logging)

2.  CLE daemon

3.  CLE user interface

4.  Call Control Table (CCT).

Details of each component follow.

      Each call for a service (e.g., error logging) includes a unique
value which identifies the specific caller of the service.  The
format of this identifier follows:

|------------|------------|----------|
   |  product   | component  | sequence |
   | identifier | identifier |  number  |
   |------------|------------|----------|
   0            3            6          8

      The "product identifier" is a three-character value that
uniquely identifies the product making the call.  The "component
identifier" is a three-character value that uniquely identifies the
component or module within the product that is making the call.  The
"sequence number" indicates the specific instance of the call within
the module or component.

      The CLE daemon is a background task that receives calls from
service facilities and determines whether a function should occur.
When called by a service facility, it is passed the name of the
service in question and the unique identifier of the caller of the
service.  Using the CCT, the CLE daemon searches for an entry that
matches the service and the caller of the service.  If a match is
found and the "Action" field indicates 'N', then the CLE daemon
informs the service facility not...