Rookie admin seeking help: Recovery log volume issue on AIX

Environment:
Storage Management Server for AIX-RS/6000 - Version 5, Release 2, Level 4.3
AIX 5.2 ML 5
FAStT 900 Disk Array

Folks:
  Appreciate a little patience here; I'm still new to a lot of this, and
my terminology is a little weak.  And of course, this had to happen while
our senior person (Paul Zarnowski) is on vacation.  I suspect this is more
an AIX issue than TSM issue

   For our recovery log, we were using raw partitions (per the Tuning
Guide) and TSM Mirroring.  These raw partitions were on logical volumes
built on our FAStT array.

  In brief, we lost a hard drive on the FAStT and as a result, lost one of
the volumes of the recovery log.

tsm: ADSM2>q logvol f=d

Volume Name         Copy      Volume Name         Copy      Volume
Name         Copy      Available    Allocated        Free
(Copy 1)            Status    (Copy 2)            Status    (Copy
3)            Status        Space        Space       Space
                                                                                
               (MB)
(MB)        (MB)
----------------    ------    ----------------    ------
----------------    ------    ---------    ---------    --------
/dev/rD100b2L01-    Off-L-    /dev/rD200b2L01-    Sync'd
    Undef-        6,396        6,372          24
 L002                ine       L002
      ined
/dev/rD100b2L01-    Off-L-    /dev/rD200b2L01-    Sync'd
    Undef-        6,396        6,396           0
 L001                ine       L001
      ined

  I was successful in deleting those volumes from TSM prior to our storage
folks doing what they needed to do to replace the broken drive.  In
particular, they had to delete then recreate the logical volume.  The
command they used was:

$ sudo mklv -m /tmp/D100b2L01L001.map -t raw -y D100b2L01L001 D100b2L01 50
D100b2L01L001
         where /tmp/D100b2L01L001.map contained hdisk34:1-50
$ sudo mklv -m /tmp/D100b2L01L002.map -t raw -y D100b2L01L002 D100b2L01 50
D100b2L01L002
         where /tmp/D100b2L01L002.map contained hdisk34:51-100

This resulted in the following

$ lsvg -l D100b2L01
D100b2L01:
LV NAME             TYPE       LPs   PPs   PVs  LV STATE      MOUNT POINT
D100b2L01L001       raw        50    50    1    closed/syncd  N/A
D100b2L01L002       raw        50    50    1    closed/syncd  N/A
$
$
$ lsvg -l D200b2L01
D200b2L01:
LV NAME             TYPE       LPs   PPs   PVs  LV STATE      MOUNT POINT
D200b2L01L001       raw        50    50    1    open/syncd    N/A
D200b2L01L002       raw        50    50    1    open/syncd    N/A
D200b2L01L003       raw        1     1

So I went into TSM, attempted to define the log copy:
tsm: ADSM2>def logcopy /dev/rD200b2L01L001 /dev/rD100b2L01L001
ANR2404E DEFINE LOGCOPY: Volume /dev/rD100b2L01L001 is not available.
ANS8001I Return code 14.

Ugh.  I began poking around and reading.  I noticed in the /dev directory
the following:
[bs1 /dev] 273 $ ls -al rD100b2L*
crw-rw----   1 root     system       57,  1 Jun 28 12:57 rD100b2L01L001
crw-rw----   1 root     system       57,  2 Jun 28 12:58 rD100b2L01L002
[bs1 /dev] 274 $ ls -al rD200b2L*
crw-rw----   1 adsm2    adsm2       101,  1 Jun 28 13:48 rD200b2L01L001
crw-rw----   1 adsm2    adsm2       101,  2 Jun 28 13:47 rD200b2L01L002

I fixed the permissions, but no luck: same result on the def logcopy effort.

I've been down a number of other blind alleys that I won't document here.

Does anyone have a suggestion as to what I should look into next?

Thanks in advance!