Partition Mobility for Extended Code Migration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing code optimization techniques, such as dynamic code optimization, struggle to migrate partitions with extended mode features to systems that do not support these features, as they require removing or modifying code to ensure compatibility, which can disrupt self-referential programs and compromise performance.
Innovation Solution
A method is introduced to manage the migration of partitions by identifying extended mode features in application code and either enabling or removing them based on the target system's capabilities, using a partition mobility facility that selectively removes or modifies code to ensure compatibility, while preserving self-referential integrity and optimizing performance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If code rewriting is performed to remove extended mode features for migration compatibility, then adaptability improves, but productivity deteriorates due to performance optimization loss
Solution Approach 1:
The code is divided into multiple segments: extended mode feature code segments and standard mode code segments. The partition is split into a first partition containing extended mode features and a second partition containing standard mode code, allowing selective migration of compatibility portions while preserving performance optimizations in the standard mode segment.
Solution Approach 2:
The extended mode features are extracted and isolated into a separate first partition that can be selectively removed or disabled during migration. This extraction allows the core functional code to be migrated to systems without extended mode support while maintaining the option to restore features on compatible systems.
2Adaptability or versatility
If extended mode features are removed to ensure compatibility, then adaptability improves, but reliability deteriorates due to self-referential program failures
Solution Approach 1:
The partition structure is made dynamic and adjustable based on the target system's capabilities. The system can adaptively configure whether to run the first partition with extended mode features or the second partition with standard mode code, ensuring both compatibility and reliability across different system environments.
Solution Approach 2:
The system changes operational parameters by detecting extended mode feature support and dynamically selecting which partition configuration to execute. This parameter-based adaptation allows the same code base to reliably operate on both systems with and without extended mode features.
3Adaptability or versatility
If dynamic code recompilation is performed to remove extended mode features, then adaptability improves, but loss of time increases due to recompilation overhead
Solution Approach 1:
The code is pre-compiled into multiple versions during the build process: one version with extended mode features and another without. This preliminary preparation eliminates the need for dynamic recompilation during migration, as the appropriate pre-compiled version can be directly deployed based on system capability detection.
Solution Approach 2:
Instead of recompiling code dynamically, the system uses pre-existing copies of the code in different optimization levels and feature sets. The migration process simply selects and deploys the appropriate pre-compiled copy that matches the target system's capabilities, avoiding time-consuming recompilation operations.
Data Source
AI summary
A partition mobility facility in which a partition that is executing one or more applications that have optimized code with one or more extended features is to be moved from a source system to a target system. If the target system does not support the extended mode features, then action is taken to remove the code having those features to facilitate migration.