Generic DB2 Database Utility Procedure for Mainframe
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The complexity and cost of managing large DB2 databases on mainframes are exacerbated by the need for skilled administrators to create and manage numerous JCL files, proc files, and control cards, leading to inefficiencies and run-time errors due to the confusing user interfaces and cluttered reports from existing utilities.
Innovation Solution
A system and method utilizing generic database utilities that eliminate the need for control cards by using a single procedure (proc) for each database utility function, where parameters identify the DB2 database name and generate utility control cards, reducing the complexity and time required for database operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional JCL files, proc files, and control cards are used to manage DB2 databases, then database operations can be performed, but the system complexity and staffing costs increase significantly
Solution Approach 1:
The patent combines multiple separate software components (JCL files, proc files, and control cards) into a single integrated utility execution file. This merging eliminates the complexity of managing three separate files for each database operation while maintaining the same functional capabilities and operational reliability.
Solution Approach 2:
The patent creates a universal utility execution file that can perform multiple database operations (backup, restore, update, etc.) on multiple databases through a single file format. This universal approach replaces the need for database-specific and operation-specific file combinations, reducing overall system complexity.
2Manufacturing precision
If skilled database administrators are hired to manage database utilities, then proper JCL files and control cards can be created, but staffing costs increase
Solution Approach 1:
The utility execution file is designed to be self-configuring and self-executing, automatically generating the necessary parameters and control information without requiring manual creation by skilled administrators. The system serves itself by incorporating all necessary operational data within the utility file structure.
Solution Approach 2:
The patent uses template-based utility execution files that can be copied and reused across multiple databases and operations. Instead of creating custom files for each scenario, standardized templates are replicated and configured with different parameters, eliminating the need for skilled administrators to create unique files for each operation.
3Reliability
If multiple software components are created for each database operation, then database utilities can be executed, but the time required to create and manage these files increases
Solution Approach 1:
The patent combines multiple software components (JCL files, proc files, and control cards) into a single integrated utility execution file. This merging eliminates the complexity of managing three separate files for each database operation while maintaining the same functional capabilities and operational reliability.
Solution Approach 2:
The utility execution files are pre-configured with all necessary parameters, control logic, and operational instructions before execution. This preliminary preparation eliminates the need for time-consuming file creation and configuration at the time of operation, as everything is already in place within the utility file.
4Ease of operation
If control cards are used to set parameters for jobs, then database operations can be controlled, but the complexity of generating proper control cards increases
Solution Approach 1:
The patent integrates the control card functionality directly into the utility execution file structure. Instead of requiring separate control cards to be generated and matched with JCL files and proc files, all parameter control capabilities are merged into the single utility file, eliminating the complexity of coordinating multiple components.
Solution Approach 2:
The utility execution file acts as an intermediary that automatically translates high-level operational requests into the specific parameter settings and control instructions previously requiring manual control card generation. This intermediary layer eliminates the need for users to directly create or understand control card syntax.
Data Source
AI summary
A system and method for performing database utilities on a DB2 database may include using a single procedure (proc) for each database utility function. At least one parameter may be provided, where the at least one parameter identifies a DB2 database name. A generic control card may be accessed, where the generic control card may be identified by a value of the parameter(s). A utility control card may be generated using the at least one parameter. A database utility may be executed on a DB2 database by using the generated utility control card.