6. Database Tailoring and Retrofitting Techniques › 6.3 Retrofitting Guidelines › 6.3.2 Retrofitting Database Files › 6.3.2.1 Value Change Only

6.3.2.1 Value Change Only

Each of these types involves a change to the value of a key
data element.  The simplest case is where there is a
one-to-one mapping of old key data element values to new
values.  That is, for every old value, there is one and ONLY
one new value.

The changed key will take the same order as the original key.
For example, assume a file's key contains a character data
element whose values are

    AA01
    AA02
    BA01

    If these values are changed to

    AB01
    AB02
    BB01

then re-sorting the file observations results in no change to
the order of observations.  In this case, the retrofit job
described in the previous section would perform the change
correctly.

Perform the data element content correction according to the
previous section.  This correction must accompany the change
to CA MICS or user exit logic that corrects the data
element's value during the daily update cycle.  For example,
if the change is to sharedprefix.MICS.PARMS(ACCTRTE) to
change SMF account level data elements, make the change to
ACCTRTE and treat the database without running an
intervening daily update job.  Note that such complex-level
changes require changes to all files on which the data
elements occur, in all timespans and for all database units
that have the component.

Be sure to apply the change to the test database first.
Testing the retrofit ensures that the change is complete and
and correct before implementing it in production.  This is
particularly necessary because, on implementation,
complex-level changes affect all database units at once.