METHOD FOR MAINTAINING EXCEPTION TABLES FOR A CHECK UTILITY

• US 20010016844A1
• Filed: 10/27/1998
• Published: 08/23/2001
• Est. Priority Date: 10/27/1998
• Status: Active Grant

• Current Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Original Assignee: Computer Associates Think Inc. (Broadcom, Inc.)
• Inventors: ISIP, AMANDO B. Jr.
• Granted Patent: US 6,401,089 B2
• Time in Patent Office: Days
• US Class Current: 707/7
• CPC Class Codes: G06F 16/24565 Triggers; Constraints
• CPC Class Codes: Y10S 707/99932 Access augmentation or optimizing
• CPC Class Codes: Y10S 707/99937 Sorting

Abstract

A method for maintaining exception tables for a CHECK utility includes generating a control statement including key words and associated values for predetermined exception table parameters. The control statement is parsed by the CHECK utility which automatically builds and executes SQL statements required to create and drop exception tables.

Claims

1. A method for maintaining exception tables, comprising the steps of:

generating a control statement including predetermined exception table parameters;

receiving the control statement in a CHECK utility;

generating a SQL statement for each of the predetermined exception table parameters; and

executing each SQL statement, wherein one of generation and deletion of an exception table is performed as a function of executing at least one SQL statement.

2. A method for maintaining exception tables in a database system, comprising the steps of:

receiving a control statement, the control statement including at least one predetermined exception table parameter;

parsing the control statement;

generating a SQL statement as a function of the parsed control statement for the at least one exception table parameter; and

executing the SQL statement.

3. The method according to

claim 2

, wherein the at least one predetermined exception table parameter includes one of a database name, an exception tablespace name, a storage group name, a primary quantity value, a secondary quantity value, an owner name and a drop value.

4. The method according to

claim 3

, wherein the control statement includes a plurality of exception table parameters.

5. The method according to

claim 2

, wherein the step of parsing the control statement is performed by a conventional CHECK utility.

6. The method according to

claim 2

, wherein the step of generating the SQL statement includes generating a SQL statement for a plurality of exception table parameters.