I have not seen that one.  We went from 4.2.2.12 to v4.2.3 last week.

The only thing we are having a problem with are backupsets are taking
extremely long.  But this was an issue before going to v4.2.3.  Support
said the problem was with 'orphaned' system objects, and v4.2.3 would
correct the problem (after we ran "cleanup backupgroups").  Well, it
didn't.  They are now looking at other possibilites.

What were you doing when the error occured?  Backup, restore, reclaim?


Michael Moore
VF Services Inc.
105 Corporate Center Blvd.
Greensboro,  NC  27408
336.424.4423 (Voice)
336.424.4544 (Fax)
336.507.5199 (Pager)



                      David Browne
                      <[email protected]        To:       ADSM-L AT VM.MARIST 
DOT EDU
                      OM>                      cc:
                      Sent by: "ADSM:          Subject:  Errors after upgrade 
from TSM 4.2.1.9 to TSM 4.2.3.0
                      Dist Stor
                      Manager"
                      <[email protected]
                      .EDU>


                      01/15/03 08:24 AM
                      Please respond to
                      "ADSM: Dist Stor
                      Manager"






I was running TSM 4.2.1.9 on OS390/2.10 and upgraded yesterday to TSM
4.2.3.0 and now I am receiving the following error messages:


ANR9999D SMNODE(2008): ThreadId<942> Duplicate object  encountered during
import or rename.

Anyone else have this same problem and what did you do to correct?