yes they are shoing copied... would the output of the query help?

No...
We use the clone for application refresh from Production std devices.
We do the 1st copy (prod std -> clone)
Mount the clone to a Dev system.
We expect to make updates and changes to clones on Dev.
We would like to then clone the Dev clone devices again to another separate set of clones which will be used against other host applicaitons.

yes it does. Only difference is our logical name is N/A:

Source Device Target Device State Copy
--------------------------------- ---------------------------- ------------ ----
Protected Modified Modified
Logical Sym Tracks Tracks Logical Sym tracks CGDP SRC <=> TGT (%)
--------------------------------- ---------------------------- ------------ ----

N/A 0099 0 0 N/A 0259 0 X... Copied 100
N/A 009D 0 0 N/A 025D 0 X... Copied 100
N/A 00A1 0 0 N/A 0261 0 X... Copied 100
N/A 00A5 0 0 N/A 0265 0 X... Copied 100
N/A 00A9 0 0 N/A 0269 0 X... Copied 100
N/A 00AD 0 0 N/A 026D 0 X... Copied 100

Total --------
Track(s) 0
MB(s) 0.0

what is the current state of your clones ? "Copied" ?

that's fine, i have these devices in a device group so they got logical names assigned to them, i renamed my target devices to actually say CLNXXX ..so it's easier for me to identify source and target. I am going to try to clone from one of the CLNXXX devices to a brand new standard device..that's what you are trying to do ?

does it look something like this:

 
Device Group (DG) Name: TESTGROUP
DG's Type             : REGULAR
DG's Symmetrix ID     : 000XXXXXXXXX
 
 
         Source Device                   Target Device            State     Copy
--------------------------------- ---------------------------- ------------ ----
               Protected Modified                Modified
Logical   Sym  Tracks    Tracks   Logical   Sym  Tracks   CGDP SRC <=> TGT  (%)
--------------------------------- ---------------------------- ------------ ----
DEV001    0890         0        0 CLN201    08B1        0 XXX. Copied       100
DEV002    0891         0        0 CLN202    08B2        0 XXX. Copied       100
DEV003    0892         0        0 CLN203    08B3        0 XXX. Copied       100
DEV004    0893         0        0 CLN204    08B4        0 XXX. Copied       100
DEV005    0894         0        0 CLN205    08B5        0 XXX. Copied       100
DEV006    0895         0        0 CLN206    08B6        0 XXX. Copied       100
DEV007    0896         0        0 CLN207    08B7        0 XXX. Copied       100
DEV008    0897         0        0 CLN208    08B8        0 XXX. Copied       100
 
Total           -------- --------                --------
  Track(s)             0        0                       0
  MB(s)              0.0      0.0                     0.0
 
 
Legend:
 
(C): X = The background copy setting is active for this pair.
     . = The background copy setting is not active for this pair.
(G): X = The Target device is associated with this group.
     . = The Target device is not associated with this group.
(D): X = The Clone session is a differential copy session.
     . = The Clone session is not a differential copy session.
(P): X = The pre-copy operation has completed one cycle
     . = The pre-copy operation has not completed one cycle

ok, let me try this right now ..

definitely ..always want to learn

Thank you so much for testing this and providing an answer. I think in the situation we wish to use it, we will be fine splitting the device and having to resync fully again.
Would you like to know how we make out?

Thanks again,
Debbie

i am afraid you can't do that unless you split clone from its standard device. This is what i get when i tried this:

 symclone -g TESTGROUP create -diff -copy CLN208 sym ld TST009
 
Execute 'Create' operation for device 'CLN208'
in device group 'TESTGROUP' (y/) ? y
 
'Create' operation execution is in progress for device 'CLN208'
paired with target device 'TST009' in
device group 'TESTGROUP'. Please wait...
 
 
The Source device cannot be manipulated because it is a Copy session Target device

you could split the clone from the std and then create a new clone session , but that in turn would destroy your original std-clone relationship and you will need to recreate that again...and that's a full sync. You could use BCV and then create multiple copies from that ..altought it has it be either a Unprotected BCV or a 2-way mirror BCV ..it can't be a raid-5 bcv. Page 152 in "EMC Solutions Enabler Timefinder Family CLI version 6.4 Product Guide" has an example on how to do this.