I think Richard may have a point regarding IC32186 and technote 1194088
(which mentions APAR IC32498). IC32186 could very well have been the
problem... it was fixed in the 4.2.2 and 5.1.1 clients. You can try
renaming the empty file spaces by their fsid.
Regards,
Andy
Andy Raibeck
IBM Software G
Andy, Richard,
A summary select showing the total extent of the problem:
tsm: TSM>adsm:select node_name as "Node
Name ",filespace_id,de
lete_occurred as "Date Delete Occurred " from filespaces
where file
space_name=''
ANR1699I Resolved ADSM to 1 server(s) - issuing co
>OK, that is in agreement with what the ANR0919E message is telling you,
>though I have no idea how you could end up with file spaces with no names.
...
May be circumstances as described in APAR IC32186 and Technote 1194088.
As Andy says, we need the Format=Detailed output of Query Filespace,
whi
OK... actually the SELECT statement I was looking for:
select node_name, '"' || filespace_name || '"'
from filespaces
where node_name='CERIUM'
was intended to provide the node name in one output column and the
filespace name, in double quotes, in the second output column, so we could
clearl
Andy,
Here's the first one I tried.
Q OCC only shows FSID 1 and 2.
Unnamed[1]
--
CERIUM
CERIUM/
CERIUM/nfs/cerium-
/c1
tsm: ADSM>q fi cerium
Node NameFilespaceFSID Platform Filespace Is
Files- CapacityPct
Name Type
