Robert O. Dryfoos - Hopewell Junction NY, US Susan A. Pavlakis - Bethel CT, US Stephen E. Record - Block Island RI, US
Assignee:
International Business Machines Corporation - Armonk NY
International Classification:
G06F 9/44 G06F 17/30
US Classification:
717122, 717170, 717110, 7079992, 707999203
Abstract:
Methods, systems, and computer program products for file version control management are provided. Methods include receiving a loadset of at least one data file and activating the loadset. For each data file in the loadset, the data file is written to a target system and identified by a base name and a generation number. A symbolic link with an activation number is created in a version control file index (VCFX) to the data file written to the target system. An application view to the symbolic link is provided as the base name of the data file, and the application view to the symbolic link is limited based on an activation number of the application corresponding to the activation number of the symbolic link.
Controlled Scheduling Of Program Threads In A Multitasking Operating System
Joel A. Farrell - Endicott NY Stephen E. Record - Ridgefield CT Brian K. Wade - Apalachin NY
Assignee:
International Business Machines Corporation - Armonk NY
International Classification:
G06F 1730
US Classification:
395673
Abstract:
A multitasking operating system permits application programs (and their developers) to influence a schedule of execution of program threads derived from the application programs. Each of the program threads is assigned a priority level and a dispatch class in which the thread resides. Based on these parameters, the operating system schedules the threads for execution in the following manner. The operating system queues the highest priority thread which is available for execution from each dispatch class onto a run list for execution by a processor. The highest priority thread on the run list is executed first. An application program thread can change the dispatch class in which another program thread resides. An executing program thread can also voluntarily yield to a specified program thread in the same dispatch class or permit the highest priority available thread in the same dispatch class to be queued on the run list with itself being available and in contention for the run list.
Preemptive And Non-Preemptive Scheduling And Execution Of Program Threads In A Multitasking Operating System
Joel A. Farrell - Endicott NY Stephen E. Record - Ridgefield CT Brian K. Wade - Apalachin NY
Assignee:
International Business Machines Corporation - Armonk NY
International Classification:
G06F 940
US Classification:
395650
Abstract:
A multitasking operating system permits application programs (and their developers) to influence a schedule of execution of program threads which constitute the application programs by specifying parameters for the program threads. The parameters indicate each thread's priority level and dispatch class in which the thread resides. The application programs specify the thread's parameters based on the following principles of the operating system. The operating system queues the highest priority thread available for execution from each dispatch class onto a run list for execution by a processor. The highest priority thread on the run list is executed first. While this thread is dispatchable and being executed, no other thread from the same dispatch class can preempt it unless this executing thread voluntarily relinquishes control of the processor, even if the other thread has a higher priority. (This other thread would have been created or made available after the currently executing thread was selected for the run list. ) However, the currently executing thread can be involuntarily preempted at any time by another higher priority, available thread from a different dispatch class.
Full-Screen Input/Output Application Program Interface
Christine T. Casey - Newark Valley NY Stephen E. Record - Ridgefield CT
Assignee:
International Business Machines Corp. - Armonk NY
International Classification:
G06F 314
US Classification:
364521
Abstract:
An application program interface for handling full-screen input/output (I/O) operations of a display device in an information handling system, such as a computer system running one or more application programs in conjunction with an operating system. The application program interface first determines characteristics of the display device in response to a request from an application program prior to performing a full-screen I/O operation, and provides these characteristics to the application program so that the application program can provide a buffer, and if an output is to be performed, construct a valid data stream for the display device. Then the application program interface builds a parameter list in response to a request from an application program to actually perform the full-screen I/O operation. Next, in response to the parameter list, the application program interface generates instructions to process the full-screen I/O operation and coordinate this request with other requests made by other application programs. The application program interface then passes the generated instructions to a control program of the information handling system to perform the desired full-screen I/O operation, and handles any status information resulting from the I/O operation.
Stephen Record 1995 graduate of Cedar City High School in Cedar city, UT is on Classmates.com. See pictures, plan your class reunion and get caught up with Stephen and other high ...
Stephen Record 1974 graduate of Huntington High School in Huntington, NY is on Classmates.com. See pictures, plan your class reunion and get caught up with Stephen and other high ...