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 command SELECT against server(s). ANR1687I Output for command 'SELECT ' issued against server ADSM follows:
Node Name FILESPACE_ID Date Delete Occurred ---------------------------- ------------ ---------------------------------- BLAST 5 2003-02-07 14:56:23.000000 BUBBLES 4 2003-02-07 14:56:23.000000 CALYPSO 5 2003-02-07 14:56:23.000000 CERIUM 3 2003-02-07 14:56:23.000000 CETUS 1 2003-02-07 14:56:23.000000 FLEETWOOD 5 2003-02-07 14:56:23.000000 HONEYCOMB 6 2003-02-07 14:56:23.000000 JAEGERPBK 3 MA 3 2003-02-07 14:56:23.000000 MHD2 7 2003-02-07 14:56:23.000000 MUTANTS 5 2003-02-07 14:56:23.000000 OUTGROUP.UCHICAGO.EDU 3 2003-02-07 14:56:23.000000 PICASSO.BSD.UCHICAGO.EDU 7 2003-02-07 14:56:23.000000 STARBUCK 11 2003-02-07 14:56:23.000000 STORM 4 2003-02-07 14:56:23.000000 THERA 1 2003-02-07 14:56:23.000000
Q FI name F=D shows no filespace name or hex filespace name. Neither does a select with those columns. The problem does not show up on the other two machines. Given the time of day, expiration was probably still running. I think we were still at AIX 4.3.3 and TSM 5.1.2.6 or 5.1.2.8 at that time.
At 06:05 PM 1/31/2005 -0500, you wrote:
>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, which will report the filespace name in hex, so we can determine what's actually in there. (Beware non-printing, space-occupying characters.)
Richard Sims
Fred Johanson ITSM Administrator University of Chicago 773-702-8464
