Converting a symdg from BCV/symmir to Clone/symclone

I have several symdgs used for manipulating symclones - mostly for backups.

I have one last symdg that is still using symmir.  Now I'm ready to convert it to our set of backup scripts that use symclone commands, but have a couple of questions.  Running 75 code on a vmax with solutions enabler 7.4.

Do I need to recreate the symdg with different flags or with -tgt for the clones?  The reason I ask this is when looking at our current symclone environments, the symdgs all look similar to the output below, the clones show up as BCVs, not as TGTs, even though this group is using symmir.  I know we wanted to have the clone target devices 'flagged' as BCVs so we could more easily differentiate them from the standards.  Would that override the 'number of locally-associated TGTs in the symdg show output below?

Group Name:  ABCDdg

    Group Type                                   : REGULAR

    Device Group in GNS                          : No

    Valid                                        : Yes

    Symmetrix ID                                 : 000192601234

    Group Creation Time                          : Wed Sep 21 01:07:09 2011

    Vendor ID                                    : EMC Corp

    Application ID                               : SYMCLI

    Number of STD Devices in Group               :   83

    Number of Associated GK's                    :    0

    Number of Locally-associated BCV's           :   83

    Number of Locally-associated VDEV's          :    0

    Number of Locally-associated TGT's           :    0

    Number of Remotely-associated VDEV's(STD RDF):    0

    Number of Remotely-associated BCV's (STD RDF):    0

    Number of Remotely-associated TGT's(TGT RDF) :    0