International Business Machines Corporation

Tsuneo Horiguchi

Richard Tallman

Laurence Edward England

Anthony Hassitt

Eric Lynn Porter

Alfred William Shannon

Jason Yaohua Cai

Stephen Sherman Miller

Kimberly Marie Ketell

Marilyn Zupsich Smith

William David Wallace

Lawrence C Weber

Richard Kirchhofer

Scoping operating system semantics in a computing environment, wherein a process comprising at least one enclave is executing in the computing environment, is disclosed. Such scoping is performed by determining whether an operating system semantic is explicitly directed to the process, or whether the operating system semantic is implicitly directed to the process. If the operating system semantic is explicitly directed to the process, then the operating system semantic is scoped to the process. If the operating system semantic is implicitly directed to the process, then the operating system semantic is scoped to an enclave of the process in which the operating system semantic occurs.

System, method, and computer program product for scoping operating system semantics in a computing environment supporting multi-enclave processes

A method, apparatus, and article of manufacture for handling access to multiple file-systems from a program written in a high-level language such as COBOL, programming language compilers and run-time environments. More specifically, the present invention provides a computer-implemented method for supporting multiple file-systems in file input/output (I/O) operations. As a result, an object program has access to different file-systems without recompilation. Further, the interfaces within the source language are independent of the specified file-system, so that support of any number of different file-systems can be accomplished with relative ease. In addition, the ability to dynamically select a file-system on a file-by-file basis is provided, thereby allowing the program to use a first file-system for one file and a second file-system for another file.

Method for supporting multiple file-systems in file input/output operations

A method, apparatus, and program storage device for supporting improved record processing protocols for COBOL SORT and MERGE functions using input and output procedures in an object program. The SORT and MERGE functions include protocols for obtaining all of the input records via an input procedure in the object program and storing them into a memory area before performing the sort or merge steps of the SORT or MERGE function. Similarly, the SORT and MERGE functions store their results into a memory area before invoking the output procedure in the object program. Also, the present invention provides an optional overflow file which is used if the memory capacity is inadequate to store and retrieve all of the requisite data.

Sort and merge functions with input and output procedures

A method and system for managing computer program execution is implemented in a set of callable run-time support services which allow processes written in single or multiple languages to cooperate and behave in a predictable and orderly manner. Three key program execution constructs are defined: process, enclave, and thread. The process is the highest level construct of the program execution. It consists of one or more enclaves. The enclave defines the scope of execution semantics defined by the high level languages. This includes the scope of application termination and the scope of name resolution for shared data, files and procedures. The enclave consists of one or more threads. The thread is the basic program execution unit with its own state of execution. A thread may execute concurrently with other threads. A thread may consist of a series of call invocations of procedures. These procedures may be written in different high level languages. The callable services provide means for creating and terminating these constructs. A request to terminate a process results in termination of all the enclaves (including threads) in the process. Terminating an enclave terminates all threads in the enclave. The termination request may be combined with signaling a termination condition allowing execution of registered condition handling exit routines.

Program execution in a software run-time environment

System, method, and computer program product for scoping operating

Processing an asynchronous interrupt of a processing entity which executes in a computer system is disclosed. An invocation stack is maintained in the computer system. The invocation stack includes a plurality of stack frames, wherein each of the stack frames has a fixed part of a predetermined length and a variable part of a variable length. An interrupt service routine is pre-defined to service the asynchronous interrupt. Processing of the asynchronous interrupt is performed by determining an address of a next available memory location in the invocation stack. A starting address in the invocation stack for a new stack frame is determined by adding a predetermined 'skip' value to the next available memory location address. The new stack frame is to be used by the interrupt service routine. Then, a portion of the invocation stack starting from the starting address is allocated for the new stack frame, and the new stack frame is generated in the invocation stack using the allocated portion of the invocation stack.

Asynchronous interrupt safing of prologue portions of computer programs

Method for supporting multiple file-systems in file input/output

A method, apparatus, and article of manufacture for optimizing programming language compilers and run-time environments. More specifically, the present invention provides a computer-implemented method for supporting multiple call interface conventions for computer programs using compiler directives. Compiler directives are embedded in the source program that indicate the call interface conventions applicable to procedure calls or procedure entry points in the program, starting where a first compiler directive is included in the source program and continuing until another compiler directive of the same type indicates a new call interface convention or until the end of the source program. In addition, compiler options may be specified at compiler run-time to set the interface conventions for the procedure calls and the procedure entry points. These specifications can be overridden by the corresponding compiler directives specified within the source program.

Method for supporting multiple call interface conventions for computer

A computer program product and program storage device for supporting native and non-native signals transferred between processing entities of a computer program, for processing of a first type of interprocess signals and a second type of interprocess signals in a computer system is disclosed. The first type of signals conform to a first signal handling standard and the second type of signals conform to a second signal handling standard. Signal processing operates by determining whether an interprocess signal is a synchronous signal or an asynchronous signal. The interprocess signal originates from a first processing entity and is received by a second processing entity. The interprocess signal is processed using signal handling semantics defined by the first signal handling standard if the interprocess signal is an asynchronous signal. Alternatively, the interprocess signal is processed using a combination of signal handling semantics defined by the first and second signal handling standards if the interprocess signal is a synchronous signal.

Computer program product and program storage device for supporting

A method, apparatus, and article of manufacture for pre-initializing, maintaining, and terminating a persistent language execution environment. The pre-initialization function allows the specification of a termination exit routine that is invoked on any attempted termination of an object program within the language execution environment, regardless of whether the attempted termination is initiated voluntarily or involuntarily.

Method for processing an application termination initiated from a

A method and system for managing computer program execution is implemented in a set of callable run-time support services which allow processes written in single or multiple languages to cooperate and behave in a predictable and orderly manner. Three key program execution constructs are defined: process, enclave, and thread. The process is the highest level construct of the program execution. It consists of one or more enclaves. The enclave defines the scope of execution semantics defined by the high level languages. This includes the scope of application termination and the scope of name resolution for shared data, files and procedures. The enclave consists of one or more threads. The thread is the basic program execution unit with its own state of execution. A thread may execute concurrently with other threads. A thread may consist of a series of call invocations of procedures. These procedures may be written in different high level languages. The callable services provide means For creating and terminating these constructs. A request to terminate a process results in termination of all the enclaves (including threads) in the process. Terminating an enclave terminates all threads in the enclave. The termination request may be combined with signaling a termination condition allowing execution of registered condition handling exit routines.

Program execution management using process enclaves which define the

Processing of a first type of interprocess signals and a second type of interprocess signals in a computer system is disclosed. The first type of signals conform to a first signal handling standard and the second type of signals conform to a second signal handling standard. Signal processing operates by determining whether an interprocess signal is a synchronous signal or an asynchronous signal. The interprocess signal originates from a first processing entity and is received by a second processing entity. The interprocess signal is processed using signal handling semantics defined by the first signal handling standard if the interprocess signal is an asynchronous signal. Alternatively, the interprocess signal is processed using a combination of signal handling semantics defined by the first and second signal handling standards if the interprocess signal is a synchronous signal.

System and method for processing interprocess signals

Processing of an asynchronous signal directed to a thread comprising a software routine executing in a computer system such that data consistency is maintained is discussed. Such processing proceeds by determining whether the routine is signal safe such that processing of the routine may be interrupted in order to process the signal without possibly causing inconsistency of data. The routine is asynchronously interrupted and the signal is processed immediately if the routine is signal safe. If the routine is not signal safe, then the routine is not asynchronously interrupted and processing of the signal is deferred to a time when the signal may be processed without possibly causing inconsistency of data.

Growing community of inventors

San Jose, CA, United States of America

Tsuneo Horiguchi