I was unable to recreate the problem in a test environment:
However I've found a strange (for me) behavior:
Server v4.1.4.1 on AIX 4.3.3ML6 (pumba.acit.bg)
Client v4.1.3 on AIX (pumba.acit.bg)
Client v3.7.2 on OS/2 (pc300-os2.acit.bg)

1. No any backup or archive data
tsm: PUMBA.ACIT.BG>show archive pumba.acit.bg *
Conversion status for node PUMBA.ACIT.BG (False)
tsm: PUMBA.ACIT.BG>show archive pc300-os2.acit.bg *
Conversion status for node PC300-OS2.ACIT.BG (False)

2. Backup of single file from AIX client
tsm: PUMBA.ACIT.BG>show archive pumba.acit.bg *
Conversion status for node PUMBA.ACIT.BG (False)
ANR2034E SHOW: No match found using this criteria.

3. Archive of single file from AIX client
tsm: PUMBA.ACIT.BG>show archive pumba.acit.bg *
Conversion status for node PUMBA.ACIT.BG (False)
/home : (DIR) / goldie (MC: DEFAULT)
Inserted 09/18/01 08:42:13
/home : (FILE) /goldie/ TSM4140README.DEV (MC: DEFAULT)
Inserted 09/18/01 08:42:13

4. Archive of single file from OS/2 client
tsm: PUMBA.ACIT.BG>show archive pc300-os2.acit.bg *
Conversion status for node PC300-OS2.ACIT.BG (False)
OS2 : (DIR) \  (MC: DEFAULT)
Inserted 09/18/01 08:46:11
OS2 : (FILE) \ README (MC: DEFAULT)
Inserted 09/18/01 08:46:11

BUT:
tsm: PUMBA.ACIT.BG>show archive pumba.acit.bg *
Conversion status for node PUMBA.ACIT.BG (False)
/home : (DIR) / goldie (MC: DEFAULT)
Inserted 09/18/01 08:42:13
/home : (FILE) /goldie/ TSM4140README.DEV (MC: DEFAULT)
Inserted 09/18/01 08:42:13
(fsId=5) : (DIR) \  (MC: DEFAULT)
Inserted 09/18/01 08:46:11
(fsId=5) : (FILE) \ README (MC: DEFAULT)
Inserted 09/18/01 08:46:11

So the question is - why it shows data from ANOTHER fileset which resides
on ANOTHER node?


Zlatko Krastev
IT Consultant






"Cook, Dwight E" <cookde AT BP DOT COM> on 17.09.2001 22:31:50
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To:     ADSM-L AT VM.MARIST DOT EDU
cc:

Subject:        ANR7821S Thread 30 (tid 52) terminating on signal 11
(Segmentatio n violation).

Well, in the following environment

Session established with server TSMSRV10: Solaris 2.6
  Server Version 4, Release 1, Level 4.0
  Server date/time: 09/17/01   14:27:09  Last access: 09/17/01   14:25:39

I've found that a "show archive <nodename> <filespacename>" of a node that
was renamed will kill the tsm server every time !

seems to work OK on straight nodes... only on a node that I renamed does it
kill the tsm server process.

Not worth calling into tivoli since "show archive" is an unsupported,
undocumented, debug command.

Just throught I'd pass along advance notice !

"Kids, don't try this at home!" ;-)

Dwight