The Computing Center of the University at Cologne runs 4 TSM-Server
(IBM 3466 NSM with three 3590E-drives) under TSM level 4.1.5.0.

On one of these machine we use the HSM-feature with a Veritas filesystem
on a fileserver under SunOS  5.6. It runs without any problems in the last
2 years. After adding and deleting some disks at the fileserver, we had to
connect the device with the HSM-Partion to another target:


The device path of an hsm file system was changed.
Afterwards dsmmonitord showed error message:
ANS9529W dsmmonitord: cannot obtain handle of file system state file

We found that the fsid hidden in file dmiFSGlobalState was different from
the
new fsid, so we edited dmiFSGlobalState inserting the new fsid.
dsmmonitord
is running now but dsmrecalld shows errors:

10/14/02   09:33:53 ANS9028E dsmrecalld: cannot determine the file system
name
for fsid (800b40, 12).
10/14/02   09:33:53 ANS9548W Cannot complete remote file access.
10/14/02   09:33:53 ANS4007E Error processing
'/export/hsm/rrzk/ade25/diplom
txt.zip': access to the object is denied

800b40 is the old fsid that has now changed to 800088.

Question: What is to be done when the device path of an hsm file system is
changed under SunOS 5.6 and vxfs?


Thanks in advance,

Joern Gehm

--
______________________________________________________________________________
Joern Gehm         Internet: gehm AT rrz.uni-koeln DOT de
                   Tel: (0221) 478-5350 ,  FAX: -5568 ,   Sekr: -5586
Regionales Rechenzentrum, Universitaet Koeln, Robert-Koch-Str. 10, 50931 Koeln
______________________________________________________________________________