---> I think TIVOLI doesn't understand IBM's religious belief in upward
compatibility and so TSM 4 doesn't have a bridge from ADSM/TSM 3.
compatibility and so TSM 4 doesn't have a bridge from ADSM/TSM 3.

More than that now we have v5.1 which would support compatibility only
with v4.2.x. And v4.1 would be out of support very soon.
There were already many threads on this list about ADSM v3.1 clients. Just
to name few OSes not having current (or even supported) client - AIX 4.2,
HP-UX 10.20, OS/2, Solaris 2.6. And we are talking about long-term
archiving in *SM.
Do you prefer to be forced to do client upgrades every year just to be
supported. And later when have to retrieve few years old archive get error
"ANS1357S Session rejected: Downlevel client code version" ? And on
IBM/Tivoli broshures there are statements that TSM clients are available
for more than 30 platforms. How many of them are supported?
We've seen long discussions here about how to keep data alive. And we can
achieve it. But as Paul pointed what can we do with this data if there is
no software to understand this data. If right now you need to restore a
program from Win95 node and it does not work on WinME?
ADSM came from mainframe world and have had meeting stringent
requirements.

Sorry for being rude but on my *PERSONAL* opinion Tivoli is doing software
much more microsoft way than IBM way.

Zlatko Krastev
IT Consultant




Please respond to Joe Faracchio <joef AT socrates.Berkeley DOT EDU>
Sent by:        "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To:     ADSM-L AT VM.MARIST DOT EDU
cc:

Subject:        Re: No drives available - UPDATE

If its the same or similiar problem I had in converting from
a 3466-C00 (tsm 3) to a 3466-C01(tsm 4) but using the same 3494/3590s
then its because your system thinks the tapes are ONLY capatible in
READ/ONLY mount modes.

Even though you are mounting a tape for RESTORE if you look closely
you will find the tapes are being mounted R/W.  If the system sees
a tape R/O it will mount it R/O and this bypasses the problem.

The system thinks the tapes were originally written using heads
(B1/E1/whatever) that are write-incompatible with your 'current/new'
(even though the same) drives.

IBM offered the above workaround but I know of no APAR to adddress it
with a fix.   I think TIVOLI doesn't understand IBM's religious belief
in upward compatibility and so TSM 4 doesn't have a bridge from
ADSM/TSM 3.

If I'm right then your works cut out for you.  You have to move data or
reclamate all FILLING tapes and make all FULL tapes READ/ONLY until they
are re-cycled.  that's what I had to do.  SIGH.

                 hope this helps.

            ... joe.f.

Joseph A Faracchio,  Systems Programmer, UC Berkeley
Private mail on any topic should be directed to :
         joef AT racchio DOT net
 (510)642-7638 (w)  (209)483-JOEF (M)
                             5633
   2 weeks left!!!

On Thu, 7 Mar 2002, Jason Morgan wrote:

> Earlier I posted a question regarding a migration problem I was having
> while trying  to restore to a 3590 with a tape stacker.
>
> I was encountering a no drives availabel while trying to restore.
>
> To overcome this problem, I had to mark the volume as READ ONLY. The
> restore went throught without a hitch.
>
> Can anyone tell me what TSM does differently on a restore when a tape is
> marked as READ ONLY instead of READ WRITE ?
>
> I think it has something to do with mount points.
>
> Thanks in advance.
>
> Jason
>