International Business Machines Corporation

Juliet C Candee

Steven Jay Greenspan

Joshua W Knight

David B Emmes

Alan Michael Webb

John L Czukkermann

Roger E Bonsteel

Aspen L Payton

James M Caffrey

Karla Kay Arndt

William Robert Richardson

Xiao Ling Chen

Hao Wu

Ravi Shankar

Jes Kiran Chittigala

Si Yu Chen

Wen Bin Han

Norman Christopher Böwing

Michael Groetzner

Taru Varshney

Bradley J Smith

Yan Fei Qin

Ricky L Kready

Computer implemented method, systems, and computer program products include program code executing on a processor(s) obtain a first container comprising image layers, wherein the image layers include a base image layer and one or more image layers. The program code determines dependencies between the image layers. The program code obtains a request for an application where at least one image layer of the one or more image layers comprises features of the application. The program code identifies, based on the dependencies, at least one additional image layer related to the at least one image layer. The program code generates and deploys a second container, where image layers of the second container consist of the at least one image layer, the at least one additional image layer related to the at least one image layer, and the base layer.

Deployment of updated services or layers on demand through containers

A partition function is transferred from a source system to a multi-tenant target environment. The transfer is executed from a source system to a multi-tenant target environment. Physical and logical input/output (I/O) configuration settings of a partition image are separated on the source system, moving logical I/O configuration settings from the source system to a remote multi-tenant target environment. A dedicated target system of the remote multi-tenant target environment is selected. Physical information about hardware and connections of the dedicated target system are added to the logical I/O configuration settings. The logical I/O configuration settings combined with the physical information in the target system are activated. An operating system with the activated logical I/O configuration is started such that the partition function is transferred.

Transferring an operating image into a multi-tenant environment

Aspects include prefetching a plurality of high-level information, high-level metadata, low-level metadata, and low-level information including a plurality of components associated with a monitored entity for disaster recovery. A subsequent instance of the high-level information, the high-level metadata, and the low-level metadata is requested. The subsequent instance of the high-level information is fetched based on detecting a change in the high-level metadata. A subsequent instance of one or more of the components of the low-level information corresponding to one or more changes in the low-level metadata is fetched for updating a plurality of disaster recovery data of the monitored entity in a persistent database.

Disaster recovery data fetching control

A computing system resource recovery method can include identifying a resource manager associated with a computing transaction, classifying the computing transaction to determine a predetermined metric, measuring an actual metric of the computing transaction, comparing the predetermined metric to the actual metric to detect abnormal behavior in the transaction and modeling the abnormal behavior to determine how the resource manager is affected by the abnormal behavior.

User-coordinated resource recovery

A computing system includes a processor configured to identify a resource manager associated with a computing transaction, classify the computing transaction to determine a predetermined metric, measure an actual metric of the computing transaction, compare the predetermined metric to the actual metric to detect abnormal behavior in the transaction and model the abnormal behavior to determine how the resource manager is affected by the abnormal behavior.

A system for porting code from a native platform to a non-native platform is provided which utilizes a non-native, platform-specific layer of code and a platform-neutral layer of code. The platform-neutral layer substantially emulates the native platform of ported code and provides a platform-neutral interface to the ported code. Together, the platform-specific layer and the platform-neutral layer provide an execution environment in which the ported code operates as a kernel extension of the non-native platform. The platform-neutral layer of the execution environment is portable to other non-native platforms so that code can be ported to another non-native platform by replacing the platform-specific layer with a customized platform-specific layer, which is adapted to the other non-native platform.

System and program product for porting code utilizing a portable execution environment

A system and program product for facilitating computing-environment control of a resource to be accessed by existing program code is provided which includes transparently replacing an uncontrolled resource referenced by existing program code with a resource controlled by a computing environment. The protocol also includes transparently interposing at least one resource management service of the computing environment between the existing program code and the resource controlled by the computing environment, wherein the at least one resource management service provides computing-environment control of the resource to be accessed by the existing program code. The replacing of the uncontrolled resource prevents the existing program code from directly accessing the resource.

System and program product for providing computing-environment control of a resource to be accessed by program code

A method of porting code from a native platform to a non-native platform is provided which utilizes a non-native, platform-specific layer of code and a platform-neutral layer of code. The platform-neutral layer substantially emulates the native platform of ported code and provides a platform-neutral interface to the ported code. Together, the platform-specific layer and the platform-neutral layer provide an execution environment in which the ported code operates as a kernel extension of the non-native platform. The platform-neutral layer of the execution environment is portable to other non-native platforms so that code can be ported to another non-native platform by replacing the platform-specific layer with a customized platform-specific layer, which is adapted to the other non-native platform.

Method, system and program product for porting code utilizing a portable execution environment

An exemplary embodiment of the present invention is a method for affinity free restart of a resource manager in a multi-system environment. The method begins when a restart request is received from a first resource manager on a first system in the multi-system environment. The first resource manager is associated with an incomplete transaction. Next, a distributed transaction unit of recovery structure is built for the incomplete transaction. Then, the distributed transaction unit of recovery structure is sent to a transaction manager for restart processing. The restart process includes restarting the first resource manager on the first system. The restart process also includes restarting a second resource manager on a second system in the multi-system environment if the incomplete transaction is associated with the second resource manager. The second system is a different system in the multi-system environment than the first system and the second resource manager previously had a node in common with the first resource manager. Additional embodiments include a system and storage medium for affinity free restart of a resource manager in a multi-system environment.

Method and system for removal of resource manager affinity during restart in a transaction processing system

Syncpoint processing is performed for a distributed transaction. The distributed transaction includes a plurality of units of recovery, and syncpoint processing is performed for at least a portion of the units of recovery, without passing messages between the units of recovery of the at least a portion of the plurality of units of recovery. Instead, syncpoint processing (including transactional logging) is controlled by one syncpoint manager associated with one of the units of recovery, and that unit of recovery collects information representative of the other units of recovery.

Growing community of inventors

Danbury, CT, United States of America

Juliet C Candee