Book description
DB2 provides functions to guarantee integrity at the system level and at the application level. From the system point of view, DB2's integration with zSeries and disk storage architecture is the cornerstone for data integrity. Logging functionality and COPY and RECOVER utilities are the building blocks for bringing the table space back to a current or consistent status in case of hardware or software failures or when application events need to be rerun.
From the application point of view, DB2 supports locking and commit at the transaction level, and general data integrity (at entity and semantic level), and a set of referential constraint rules for each parent/dependent table relationship. The tables linked by referential integrity are recognized during the execution of the QUIESCE utility. Other logical relations across tables, necessary to support business rules, are implemented via constraints, triggers, user defined functions, and user defined tables. Informational constraints also exist, they are not enforced by the database manager, they are used to improve query performance. In this IBM Redbooks publication, we briefly describe the integration of DB2 for z/OS with System z architecture, we then explore the data integrity options and utilize the standard recovery functions for application-related issues.
Table of contents
- Figures
- Examples
- Tables
- Notices
- Preface
-
Chapter 1: Introduction
-
Host platform
- z/OS and OS/390 system integrity
- System-level security
- Transaction-level security
- zSeries cryptography
- System z integrity features
- The zIIP
- VSAM share options
- Data sharing integrity
- Global resource serialization
- DB2 controls
- Auditing your DB2 applications
- Other security enhancements
- DB2 column level encryption
- IBM Data Encryption for IMS and DB2 Databases
- Information integrity
- DB2 and data integrity
- Example of integrity needed across applications
-
Host platform
- Chapter 2: Semantic integrity
- Chapter 3: Referential integrity
-
Chapter 4: Triggers
- Why use triggers for data integrity
- Trigger terminology
- Extending triggers with UDFs and stored procedures
- Invoking UDFs and stored procedures
- Passing parameters to UDFs and stored procedures
- Raising error conditions
- Handling errors during execution
- Auditing versus mass replication
- Impact of LOAD utility
- DB2-enforced RI versus triggers
- Execution sequence of multiple triggers
- Trigger cascading
- Interactions among triggers and other integrity checks
- Creating triggers to obtain consistent results
-
Common business scenarios
- Data validation
- Complex data validation with a UDF
- Maintaining redundant data
- Complex redundant data maintenance with a stored procedure
- Bidirectional data maintenance
- Maintaining summary data
- Maintaining existence flags
- Enforcing multiple parent RI
- Enforcing “Empty-nest-last-child-gone” rule
- Generating alerts
- Writing an MQ message
- Auditing
- Chapter 5: Other integrity features
- Chapter 6: Recovery
- Related publications
- Abbreviations and acronyms
- Index (1/3)
- Index (2/3)
- Index (3/3)
- Back cover
Product information
- Title: Data Integrity with DB2 for z/OS
- Author(s):
- Release date: July 2006
- Publisher(s): IBM Redbooks
- ISBN: 9780738495545
You might also like
book
Streamline Business with Consolidation and Conversion to DB2 for z/OS
Time to market, flexibility, and cost reduction are among the top concerns common to all IT …
book
DB2 for z/OS Application Programming Topics
This IBM Redbooks publication describes the major enhancements that affect application programming when accessing DB2 data …
book
DB2® SQL PL: Essential Guide for DB2® UDB on Linux™, UNIX®, Windows®, i5/OS™, and z/OS®, Second Edition
IBM's definitive guide to writing DB2 SQL PL stored procedures, triggers, UDFs, and dynamic compound SQL …
book
External Procedures, Triggers, and User-Defined Functions on IBM DB2 for i
Procedures, triggers, and user-defined functions (UDFs) are the key database software features for developing robust and …