EMC support answered my question... so this is for anyone that comes across this.  Basically the devices were locked in a DeltaMark session.  You can list devices locked in a DeltaMark session by issuing:  bash-3.2# ./symchg list -session  Symmetrix ID: 000190XXXXXXX       C H A N G E    T R A C K E R     D E L T A M A R K     S E S S I O N S          Device Name           Directors                  Device                --------------------------- ------------- -------------------------------------                                                                            Cap Physical               Sym  SA [IMAGE] DA :IT  Config        Attribute    Sts   (MB) --------------------------- ------------- -------------------------------------  Not Visible            003D ???:? 01B:C5  RAID-5        N/Grp'd      RW   35723 Not Visible            003E ???:? 16B:C4  RAID-5        N/Grp'd      RW   35723 Not Visible            003F ???:? 16A:D2  RAID-5        N/Grp'd      RW   35723 Not Visible            0040 ???:? 01A:D3  RAID-5        N/Grp'd      RW   35723 Not Visible            0041 ???:? 16A:D0  RAID-5        N/Grp'd      RW   35723 Not Visible            0042 ???:? 01A:D1  RAID-5        N/Grp'd      RW   35723 Not Visible            0043 ???:? 16A:D6  RAID-5        N/Grp'd      RW   35723 Not Visible            0044 ???:? 01A:D7  RAID-5        N/Grp'd      RW   35723 Not Visible            00D1 01C:0 01A:C0  2-Way Mir     N/Grp'd      RW       3 Not Visible            00D2 01C:0 16A:D0  2-Way Mir     N/Grp'd      RW       3  10 Change Tracker DeltaMark sessions were found.  As long as you know it's safe to do so, you can end the DeltaMark session on the device by: bash-3.2# ./symchg delete dev 003D  A Change Tracker DeltaMark session has been deleted for Symmetrix Device 03D  You may now provision (or meta) the device without complaint.  Primus ID: emc271365 covers this error/behavior and offers corrective steps (though for the life of me, I can never search for nor find EMC Primus articles anywhere in Powerlink or any of the other support resources).
Trying to provision space from our DMX-4.  Was chugging along with no problems, then suddenly:   ./symconfigure -cmd "form meta from dev 0031 config=striped, stripe_size=2cyl; add dev 0032:0033 to meta 0031;" commit     Establishing a configuration change session...............Established.      Error occurred while Defining change number 1:     A DDF session exists. Operation cannot be performed     Device 0031 generated the failure      Terminating the configuration change session..............Done.  The configuration change session has failed.  Does it on any device, not just 0031.  Stuck now.  Any assistance would be great.  Thanks.
A DDF Session Exists