I'm still learning some of this stuff myself, but what I've been having to do is create the pairs without specifying a device group to add them too... then once they are recognized as an RDF pair I can add them to the device group.

This was giving me some real trouble last week since it is a bit different ( I think) from when we originally built the environment.

That is exactly what I was using, but I left off the -g XXX at the end

Once the pairing was created I was able to add the R1 to the device group.

Just be aware that to do the createpair with the invalidate option the R2 devices have to be set to write disabled (I think not ready works too).

Can you give me a example of the syntax you are using? Here is an example of what I am issuing.

symrdf createpair -file hlanndp006.dat -sid 0110 -rdfg 3 -invalidate r2 -type rdf1 -g CWVDYN1

the file contain the following. R1 and R2
$ cat hlanndp006.dat
c14 582
c15 583
c16 584


Thanks

AFAIK this command will try to CREATE the group CWVDYN1 and put all the devices in the dg .. but since the DG already exists, it will fail

Why don't you create a different group and later (after the creation) move all the devices from the new (temporary) DG to the good old CWVDYN1 ?? You can also follow Allen directions and use the pairfile only to create the pairs and later throw the devs in the existing DG via symld

-s-

That's how I'd do it: create a temporary group to be able to control the new paired devices and after the initial sync is done, delete the group and add the devs to the already existing group.

You can:

symrdf -rdfg xxx -sid yyy -file pairifle -type Rx -invalidate R2 createpair -g TempDgName

to create the DG while also creating the pairs and

symld -g TempDgName moveall DestDgName [-force] [-rename]

to move the devices from the temporary group to the real DG ..