Mainframe Build Dependency Detection via File System Monitoring
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Mainframe computers were not designed to communicate with outside systems, making it difficult for configuration management servers to monitor and manage software development activities, leading to inefficient execution of builds and lack of control over build processes.
Innovation Solution
Monitoring file system activity during software builds to record build information, which is then analyzed by a configuration management server to determine dependencies and generate optimized build scripts that reduce computing resources and build time.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If mainframe computers are used for software development, then computing power and reliability are improved, but the ability to communicate with outside systems and allow monitoring is worsened
Solution Approach 1:
An intermediary system is introduced between the mainframe computer and outside systems to enable communication and monitoring. The system captures build information from the mainframe's file system activity and transmits it to external configuration management servers, allowing the mainframe to maintain its isolated architecture while still enabling external monitoring and control.
2Productivity
If configuration management servers monitor mainframe activities, then build control and efficiency are improved, but system complexity increases
Solution Approach 1:
The mainframe system performs self-service by automatically generating and transmitting build information about its own file system activities without requiring external monitoring agents or complex integration. The build information is captured from the mainframe's own operations and made available to configuration management servers in a format that requires minimal processing.
3Reliability
If full build processes are executed, then complete software builds are achieved, but computing resources and build time increase
Solution Approach 1:
A feedback mechanism is implemented where build information is captured and analyzed to determine which files have changed and which build tasks are actually needed. This feedback loop enables the system to identify dependencies and eliminate redundant build operations, executing only the necessary tasks while maintaining build completeness.
Solution Approach 2:
Instead of executing complete build processes for all files, the system performs partial builds by identifying and processing only the specific files that have changed or are required. This selective approach reduces computing resources and build time while still achieving the necessary build outcomes.
Data Source
AI summary
Techniques are provided for determining dependencies in a mainframe development environment. While executing a first build file to generate a first build of a software program from files in a file system, the activity in the file system is monitored to determine a plurality of files that are being accessed, and first information about the plurality of files is recorded. The first information is sent to a configuration management server. From the configuration management server, second information is received that indicates one or more dependencies which are determined among the plurality of files based on the first information. Based at least on the second information, a second build file is generated. The second build file is executed to generate a second build of the software program, where the second build is generated more efficiently by using less computing resources than the first build of the software program.