Database Resource Security Macro and DSECT Assembly

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database management systems face challenges in securely managing and updating resource security information, particularly in customizing, updating, or amending table load modules, which can lead to difficulties in maintaining integrity and security due to the complexity of source code management.

Innovation Solution

A method is introduced that involves creating a macro and corresponding data section definitions to define security for each resource, assembling these into a load module, processing the module to obtain source code, and re-assembling it to modify or add security information, allowing for easier management and customization of resource security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If resource security information is centralized in a single table load module, then security control is enhanced, but the system becomes difficult to customize, update, or amend

Engineering Contradiction:
Improvesecurity controlVSAvoidcustomization and update capability
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent segments the centralized load module into modular components: a template portion containing reusable security definitions and a data portion containing resource-specific security information. This segmentation allows individual resources to be customized and updated independently without affecting the entire security system, resolving the contradiction between centralized security control and ease of customization.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary action by pre-defining security templates with common security parameters and configurations before resources are created or modified. This allows rapid customization of resource security by simply filling in resource-specific data against the pre-established template, eliminating the need to modify the entire load module and enabling easy updates while maintaining centralized security management.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If source code is maintained separately to enable resource changes, then adaptability is improved, but security risks increase due to potential overwrite or loss

Engineering Contradiction:
Improveresource modification capabilityVSAvoidsource code security
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent uses copying by maintaining a template portion that contains the secure, standardized security definitions. When resources need to be modified or added, the system copies the appropriate template portions and populates them with resource-specific data, rather than modifying the original source code directly. This ensures the master template remains secure and unchanged while still enabling full adaptability for resource customization.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If the load module is updated frequently to reflect resource changes, then adaptability is improved, but system stability deteriorates

Engineering Contradiction:
Improveresource update capabilityVSAvoidload module stability
Core Design Contradiction:
Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The patent segments the load module into a stable template portion and a flexible data portion. The template portion containing security definitions remains unchanged and stable, while the data portion can be easily updated to reflect resource changes. This segmentation allows frequent resource updates without compromising the stability of the core security infrastructure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements copying by creating resource-specific instances from the master template. When resources are added or modified, the system copies the template structure and populates it with new data, rather than modifying the template itself. This ensures the load module's core structure remains stable while accommodating frequent resource changes through non-destructive copying operations.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS8886564B2Program for resource security in a database management system
Publication Date: 2014.11.11 CA TECH INC
  • US8886564B2 patent drawing
  • US8886564B2 patent drawing
  • US8886564B2 patent drawing

AI summary

An inventive method is presented for resource security in a database management system having a plurality of resources, the method comprising creating a macro and a corresponding data section definition (DSECT) defining security for each resource, assembling all of the DSECTs into a load module, processing the load module to obtain source code, and assembling the source code, such that changing the source code of one resource modifies the defined security of the resource and adding new source code to the source code adds a new resource having security to the plurality of resources. The processing step can comprise loading the load module, reading a DSECT having a total number of resources, and, for each resource of the total number of resources, reading a next DSECT, finding the defined security in the next DSECT, and obtaining the source code associated with the defined security.