Updates to DB2 Change Accumulation Tool for z/OS V3.1 User's Guide

Content

---

Update 4
Date of change: July 2016
Topics: APAR PI55449/GGC-3182
Change description: The following PDF describes the documentation changes:
GGC-31-PI55449-PI62930-MiniSpec.pdf

---

Update 3
Date of change: March 2, 2015
Topics: Multiple
Change description: The following PDF describes the documentation changes:
ggc_310_Q2-03-02-2015.pdf

---

Update 3
Date of change: November 20, 2014
Topics: Multiple
Change description: The following PDF describes the documentation changes:
ggc_310_nov2104_updates.pdf

---

Update 2
Date of change: August 27, 2014
Topics: Chapter 9. Troubleshooting
Change description: The following restriction concerning online compression dictionary building has been added:

When performing online compression dictionary building, the dictionary pages may follow one or more pages with compressed rows. Change Accumulation Tool can still process table spaces and image copies with this condition, but the image copies it produces will have the dictionary pages in this same order it encountered them. This causes an error condition for any utility that requires the dictionary pages to appear before any pages with compressed row data. One such utility is the DB2 Unload utility which generates a message of the following format:

DSNU1232I <db2-ssid> <time> DSNUULCA - COMPRESSED ROW IS IGNORED BECAUSE THE DICTIONARY IS NOT AVAILABLE FOR TABLE <table name>

The image copy utility attempts to bypass this problem by writing the compression dictionary pages to the image copy dataset out of order (page # wise) so that they appear before the data pages with compressed rows for utilities such as Unload.

DB2 Change Accumulation Tool's sequential operating nature requires that the pages be sorted in page number order in a selected image copy, which pushes the compression dictionary pages back after one or more data pages with compressed rows. Change Accumulation tool then creates an image copy in page number order. REORGing the object reconstructs the compression dictionary at the beginning of the image copy, both page number wise and positionally. In order to get this scenario to work with GGC, the object will have to be reorged. This behavior is working as expected.

---

Update 1
Change description: The following PDF describes the documentation changes:

ggcuga31_updates.pdf