Below is the response from L2 support  Referred primus :emc312873 This is due to an Enginuity issue. There is a generic problem on THIN to 73 THICK NULL group copy. If THIN is unallocated and R2 is IVTOC, the code processes up to the end of the device.A temporary workaround is to fully allocate the R1 device, including special cylinders. OPT 412611 has been opened for this issue and a permanent fix is in progress. Then you can do full establish.
I am seeing a new issue in my environment when I try to setup replication between VMAX and DMX.  All existing replication is working fine between the frames, but when I create new RDF group and new pairs , and establish them ..they are immediately going into invalid state.  Support told me to fully allocate thin device on source side and then try sync.  Does anyone faced similar issues ?? Is there any fix for this problem.         Source (R1) View                 Target (R2) View     MODES--------------------------------    ------------------------ ----- ------------             ST                  LI      STStandard      A                   N       ALogical       T  R1 Inv   R2 Inv  K       T  R1 Inv   R2 Inv       RDF PairDevice  Dev   E  Tracks   Tracks  S Dev   E  Tracks   Tracks MDAE  STATE-------------------------------- -- ------------------------ ----- ------------ DEV001  2BC2 RW       0  2015344 NR 555C WD       0        0 C.D.  InvalidDEV002  2BDA RW       0  5485591 NR 5574 WD       0        0 C.D.  Invalid DEV003  3D34 RW       0  3318588 NR 558C WD       0        0 C.D.  Invalid
VMAX to DMX SRDF/A goes invalid