> Sorry Hans if I was unclear, but for you that haven't upgraded to
version
> 4.2, this problem doesn't exist.
>
> The system object bug was first introduced with version 4.2.2.0. For
> thoose of you using a lower version, my suggestion is to not upgrade to
> version 4.2.2, as you will also get th
Hans Hedlund <[EMAIL PROTECTED]>
> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
> 2002-10-14 16:05
> Please respond to "ADSM: Dist Stor Manager"
>
>
> To: [EMAIL PROTECTED]
> cc:
> Subject:Re: clean
-10-14 16:05
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Re: cleanup... (was: upgrade from TSM 4.1.3 to TSM 5.1.5)
Just to add to the total confusion, you can (will?) experience the same
(similar?) problem in a 4.2.2.
Just to add to the total confusion, you can (will?) experience the same
(similar?) problem in a 4.2.2.x server which I don't see properly clearified
on ADSM-L. Everyone's talking about this appearing when trying to upgrade to
5.1.x, but I have the problem in a plain 4.2.2 environment too: SYSTEM
O
