RC/Compare: Display more granular details of a comparison for one object in a Compare Strategy.
Article ID: 275184
Updated On:
Products
Issue/Introduction
When performing a compare strategy, there are various methods to check or verify before the strategy is analyzed exactly what changes have been found by RC/Compare.
This is because generating a compare analysis may take a lengthy time bases on the amount of work it has to do.
One faster method is to update the strategy and use the COMPARE command from the Compare Explode Services screen. See knowledgebase article:
That gives the user a report covering the whole strategy.
If the user wants to focus on just one object like a specific table then there is another report available.
Environment
DB2 for Z/OS
Release : R20
Resolution
If the user wants to focus on just one object like a specific table among many in the strategy then there is another report available to see the detailed changes found. Sometimes the changes can be extensive.
Update the strategy.....
---------------- RC/M Compare Explode Services ---------------- yy/mm/dd hh:mm
COMMAND ===> SCROLL ===> CSR
STRATEGY ===> TBL2 DESCRIPTION ===> COMPARE TBL2
CREATOR ===> authid1 SHARE OPTION ===> U (U,Y,N,X,L)
VIEW STRATEGY INFO ===> N CREATE/DROP OBJECTS ===> N (U,Y,N)
--------------------------------------------------------------------- authid1
SOURCE SSID ===> IMPORTED DATASET | TARGET SSID ===> ssid
| TARGET LOC ===> LOCAL
|
E TY | Ob Dep
S X PE NAME CREATOR VERSION | CH CH NAME CREATOR VERSION
E A T TBL2 authid1 | TBL2 authid1
******************************* BOTTOM OF DATA ********************************
The above Compare Strategy compares a table with some DDL from a dataset....a SQL to SSID comparison just as an example.
On the "S" column above enter an "E" for edit to edit the table object on the strategy.
ROPTBALX ------------------ Table Alter ------------------ yyyy/mm/dd hh:mm:ss
COMMAND ===> COMPARE SCROLL ===> CSR
Table => TBL2 > Creator => authid1 > Comm/Lab => N
Database => DBP2 Editproc => Data Cap => CHANGES
Tablespace => TSP2 Validproc => OBID =>
Partitioning > NO (TS Parts: 9) Audit => NONE Volatile => N
Table Type => REGULAR Restrict => N CCSID => UNICODE
Row Size => 28/-4,020 Forgn Key => N Chk Const > N
Append => Y
CMD ### PS COLUMN NAME COLUMN TYPE SIZE N D FORDAT PK UK FK
___ 1 1 A CHAR 5 N Y MIXED 1
___ 2 B CHAR 4 Y N MIXED __
___ 3 C CHAR 5 Y N MIXED __
___ 4 D CHAR 5 Y N MIXED __
___ 5 E CHAR 5 Y N MIXED __
******************************* BOTTOM OF DATA ********************************
Looking at the screen where edits of the object can be entered manually if required, instead enter the command line command "COMPARE".
The report below shows the SOURCE and the TARGET values and the value that will be generated. See those in RED below as the changed table values.
ROPTBAL3 ------------------ Table Alter ------------------ yyyy/mm/dd hh:mm:ss
COMMAND ===> SCROLL ===> CSR
Table => TBL2 > Creator => authid1 > Comm/Lab => N
(Target) => TBL2 > (Target) => authid1 > (Trg) => N
(Source) => TBL2 > (Source) => authid1 > (Src) => N
Database => DBP2 Editproc => Data Cap => CHANGES
(Target) => DBP1 (Target) => (Trg) => NONE
(Source) => DBP2 (Source) => (Src) => CHANGES
Tablespace => TSP2 Validproc => OBID =>
(Target) => TSP2 (Target) => (Trg) => 3
(Source) => TSP2 (Source) => (Src) =>
Partitioning > YES (TS Parts: 9) Audit => NONE Volatile => N
(Target) => NO (Target) => NONE (Trg) N
(Source) => NO (Source) => NONE (Src) N
Table Type => REGULAR Restrict => N CCSID => UNICODE
(Target) => REGULAR (Target) => N (Trg) => EBCDIC
(Source) => REGULAR (Source) => N (Src) => UNICODE
Row Size => 28/-4,020 Forgn Key => N Chk Const > N
(Target) => 29 (Target) => N (Target) >
(Source) => 28 (Source) => N (Source) >
Append => Y
(Target) > N
(Source) > Y
CMD ### PS COLUMN NAME COLUMN TYPE SIZE N D FORDAT PK UK FK
___ 1 1 A CHAR 5 N Y MIXED 1
TRG 1 A CHAR 5 N Y MIXED 1
SRC 1 1 A CHAR 5 N Y MIXED 1
___ 2 B CHAR 4 Y N MIXED __
TRG 2 B CHAR 5 Y N MIXED
SRC 2 B CHAR 4 Y N MIXED
___ 3 C CHAR 5 Y N MIXED __
TRG 3 C CHAR 5 Y N MIXED
SRC 3 C CHAR 5 Y N MIXED
___ 4 D CHAR 5 Y N MIXED __
TRG 4 D CHAR 5 Y N MIXED
SRC 4 D CHAR 5 Y N MIXED
PF8 or 7 to scroll to next page:
CMD ### PS COLUMN NAME COLUMN TYPE SIZE N D FORDAT PK UK FK
___ 5 E CHAR 5 Y N MIXED __
TRG 5 E CHAR 5 Y N MIXED
SRC 5 E CHAR 5 Y N MIXED
See this group above:
Database => DBP2 Editproc => Data Cap => CHANGES
(Target) => DBP1 (Target) => (Trg) => NONE
(Source) => DBP2 (Source) => (Src) => CHANGES
The report is showing that tablespace TSP2 will be moving to a new database , DBP2 where the target was originally DBP1.
The report is showing that DATA CAPTURE will become "CHANGES"" where it had previously been "NONE" on the target table.
Also, on the COLUMN section of the report , column B is changing from a length of 5 to a length of 4 from the source table.
This is why the below is in the report above:
Row Size => 28/-4,020
(Target) => 29
(Source) => 28
Since column "B" is becoming shorter then the overall length of the record will be one shorter from 29 to 28.
RC/Migrator does issue this warning when the length of the record is going to be shorter due to a column length change. This allows the user to consider if this will be an issue.
-- RMA593W DATA LOSS POSSIBLE DUE TO COLUMN TYPE CHANGES IN TABLE
-- authid1.TBL2
In this section it shows that the table will now be a partitioning table with the tablespace having NUMPARTS 9. The input DDL had a index-controlled partitioning index and as that type is now deprecated RC/Migrator creates a partitioning table. The original partitioned index with partitioning keys is recreated as a partitioned index without the keys.
Partitioning > YES (TS Parts: 9) Audit => NONE Volatile => N
(Target) => NO (Target) => NONE (Trg) N
(Source) => NO (Source) => NONE (Src) N
The above tells you that the source and target were not partitioning tables but now it will be a partitioning table with 9 partitions with the same partitioning keys that the partitioned index had before.
So, this report shows you the details of the source and the target values but also the end result decided on by the compare.
Feedback
