CICS VSAM Transparency for z/OS, Version 1.2


Implementing a normalized DB2 design

Assume that you decide to implement a normalized DB2® design with each group entry becoming a separate DB2 row. To illustrate this consider the following copybook extract:
Figure 1. Repeating group field
05 RETL-PRICE-GROUP OCCURS 10 TIMES
 10 RETL-PRICE-HIGH-SIZE-NUM PIC S999 COMP-3
 10 RETL-PRICE-LOW-SIZE-NUM  PIC S999 COMP-3
 10 STK-RETL-SLS-PRICE       PIC S9(5)V99 COMP-3
 10 SKU-PRICE-CHNG-PCT       PIC S9V9999 COMP-3
 10 SKU-PRICE-CHNG-AMT       PIC S999V99 COMP-3.

A normalized design uses a secondary table containing 10 DB2 rows for each VSAM record. The key of the secondary table is the same as the key of the primary table, but with an additional column to achieve uniqueness. This can be a timestamp column, or a numeric column which indicates the relative record position within the group. The additional column value must be generated by the IRD.

The secondary table is related to the primary tables through DB2 referential integrity.

There are no sample CICS® VT high-level language exits for this solution. The following section highlights the variations in MULTIRD and MULTFBE that are required.



Concept topic


Last updated: February 8, 2013 20:43:57