Our data center fire suppression system was inspected earlier this
morning. The inspector somehow managed to trigger the fire suppression
system. He was able to abort the activation before Halon was discharged,
but not before the electrical power to the data center was cut off.
We have gotten the TSM server host (zSeries Linux) back up, but we have
not been able to bring up the TSM server (5.3.4.0). It fails during
initialization with the following messages:

ANR0200I Recovery log assigned capacity is 10800 megabytes.
ANR0201I Database assigned capacity is 66800 megabytes.
ANR0306I Recovery log volume mount in progress.
ANR0353I Recovery log analysis pass in progress.
ANR9999D pkthread.c(570): ThreadId<0> Run-time assertion failed: "Cmp64(
scanLsn, LOGV->headLsn ) != GREATERTHAN", Thread 0, File logread.c, Line
398.
ANR7824S Server operation terminated.
ANR7823S Internal error LOGREAD388 detected.

I already have a Severity 1 call in to IBM. We have mirrored recovery
log volumes. I tried renaming the primary volumes to force the server
to use the copies. The server failed with the same messages. I have
since renamed the primary log volumes back to their original names.
Even so, the TSM server now generates messages like the following:

ANR0215W Recovery log volume /tsmlog01/logvol is in the offline state -
VARY ON required.

I have no idea how I am supposed to vary on the volumes when the TSM
server won't start.

Is there anything else I should try while waiting to hear from IBM?