Dynamic File Register for Batch Processing Versioning
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional batch processing systems face inefficiencies in file management, including unnecessary storage of empty files and the inability to effectively version files due to rigid file name allocation and limitations in dynamic file addressing.
Innovation Solution
A batch processing method that uses a file register to manage physical file names with selection attributes, allowing for dynamic file versioning and flexible allocation of file names based on abstract selection criteria, enabling efficient file housekeeping and versioning.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If all necessary files are generated in advance for batch processing runs, then the program can execute without interaction, but unnecessary empty files are created and storage space is wasted
Solution Approach 1:
The system performs preliminary registration of file requirements in the file register before batch processing runs. The file definition information specifies which files will be needed, allowing the system to prepare only those specific files rather than generating all possible files in advance, thus avoiding storage waste while ensuring execution efficiency
Solution Approach 2:
The system uses feedback from actual file access during program execution to update the file register. By tracking which files are actually read or written, the system learns from past runs to optimize future file generation, eliminating the creation of unnecessary empty files while maintaining the ability to execute batch jobs autonomously
2Stability of the object's composition
If physical file names are fixedly allocated in JCL control instructions, then file references are stable, but file versioning is not possible and storage space cannot be reused
Solution Approach 1:
The file register acts as an intermediary between the fixed program code and the physical file names. The file definition information in the register maps abstract file requirements to actual physical files, allowing the system to maintain stable program references while dynamically allocating different physical files for versioning and reuse across multiple batch processing runs
Solution Approach 2:
The system introduces dynamic file name allocation through the file register, which can be updated between batch processing runs. This allows physical file names to be dynamically assigned based on versioning requirements while the program code remains unchanged, enabling both stability and adaptability
3Adaptability or versatility
If a file register with abstract selection criteria is implemented, then file management becomes flexible and versioning is enabled, but the system complexity increases
Solution Approach 1:
The file register serves multiple functions: it stores file definition information, tracks actual file usage, enables versioning through dynamic allocation, and provides feedback for optimization. By consolidating these functions into a single data structure, the system achieves high file management flexibility without proportionally increasing complexity
Solution Approach 2:
The system manages complexity by changing parameters in the file register (such as file name associations and selection criteria) rather than restructuring the entire system. This allows flexible file management and versioning to be achieved through parameter adjustments in the register, keeping the overall system structure relatively simple
Data Source
AI summary
To detect files which are generated unnecessarily or no longer required, and for reliable file versioning, in a batch-processing-oriented environment, a dynamic batch processing system is proposed. The system includes a batch processing control component to process batch processing control instructions, which include the call of at least one program, and a database with files, each of which has a physical file name. The system also includes a component to provide program-related file definition information, which defines the files which are required for a program run by abstract selection criteria. In a file register, the physical file names of the files which are created for the program runs are registered in the form of register entries, which associate at least one selection attribute with each physical file name. A service component which communicates with the control component has access to the file register and the file definition component. The service component selects and/or creates register entries on the basis of file definition information which is associated with the program to be called.