Hi Len:
The problem showed up after the migration with the library where we
have our copypools. It reported no tapes to mount. After doing a few
useless things, I called TSM support. The issue was fowarded  to level 2
and they requested a trace.
They came back within a day with the cause.
It only showed up in the one library with the copypools that once had E
type cartridges. It didn't show up in our newer library that holds the
primary storage pools and was populated with K type tapes from the
getgo.
Level 2 did not specify exactly what the 'bad' format was, just that it
was left over from ADSM 3.7 and how to remove it.

>>> SNOLEN AT VM.SAS DOT COM 08/30/03 08:39PM >>>
In article <sf4f4c45.021 AT gwia.thruway.state.ny DOT us>, Lawrence Clark
<Larry_Clark AT THRUWAY.STATE.NY DOT US> says:
>
>It was fairly straightfoward and quick, but we have 3494 libraries
and
>had done am audit fix=yex the week prior.
>We had a gotcha afterwards with some data being in ADSM 3.7 format
that
>caused problems afterwards, but we made then roadonly and did move
datas
>on them.

Hello Larry

Can you tell us a little more about the trouble with ADSM 3.7 data.
We are planning to migate from TSM 4.2 to 5.2 and have data going back
to ADSM 2.1.

Thanks len boyle