Hate to say it, but this looks like DB corruption IMHO.  If you have
the downtime, or another test server, I would run an audit against the
DB.

Also, since the error seems to be on the BFDESTROY, you might try
setting the trace flag for SHRED.  Maybe this will give more
information.

Gary
Itrus Technologies

On Aug 19, 2009, at 2:33 PM, Clark, Margaret wrote:

Did you try deleting by FSID?  Laborious, but it works when other
methods fail...   e.g. (for filespace 1):  DELETE FILESPACE
KL10143J  1 NAMETYPE=FSID
- Margaret Clark

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
Behalf Of Loon, EJ van - SPLXM
Sent: Wednesday, August 19, 2009 12:00 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Dealloc prohibited - transaction failed

I was hoping to be able to solve it myself, since the server is
running
an unsupported TSM level (5.3.4.0), so I cannot open a PMR.
Thanks anyway.
Kind regards,
Eric van Loon
KLM Royal Dutch Airlines

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
Behalf Of
km
Sent: dinsdag 18 augustus 2009 18:34
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Dealloc prohibited - transaction failed

On 18/08, Loon, EJ van - SPLXM wrote:

Hi TSM-ers!
I have two nodes which I cannot delete. When I issue a DELETE

FILESPACE

* for one of these node, I see the following errors in the log:

ANR0984I Process 59041 for DELETE FILESPACE started in the BACKGROUND

at

15:30:40.
ANR0800I DELETE FILESPACE * for node KL10143J started as process

59041.

ANR0802I DELETE FILESPACE * (backup/archive data) for node KL10143J
started.
ANR9999D ssalloc.c(1532): ThreadId <51> Dealloc prohibited -

transaction

failed.
ANR9999D ThreadId <51> issued message 9999 from:
ANR9999D ThreadId <51>  0x0000000100017f78 outDiagf
ANR9999D ThreadId <51>  0x000000010032d480 ssDealloc
ANR9999D ThreadId <51>  0x0000000100365534 AfDeallocSegments
ANR9999D ThreadId <51>  0x0000000100365e68 AfDeleteBitfileFromPool
ANR9999D ThreadId <51>  0x00000001003663c8 AfDestroyAll
ANR9999D ThreadId <51>  0x00000001003608a4 bfDestroy
ANR9999D ThreadId <51>  0x00000001001816fc ImDeleteBitfile
ANR9999D ThreadId <51>  0x000000010018a510 imDeleteObject
ANR9999D ThreadId <51>  0x00000001003d3800 DeleteBackups
ANR9999D ThreadId <51>  0x00000001003d4c80 imFSDeletionThread
ANR9999D ThreadId <51>  0x00000001000063c8 StartThread
ANR9999D ThreadId <51>  0x090000000053650c _pthread_body
ANR9999D imutil.c(7001): ThreadId <51> unexpected rc=87 from
bfDestroy
for objId=0.1066965103
ANR9999D ThreadId <51> issued message 9999 from:
ANR9999D ThreadId <51>  0x0000000100017f78 outDiagf
ANR9999D ThreadId <51>  0x0000000100181740 ImDeleteBitfile
ANR9999D ThreadId <51>  0x000000010018a510 imDeleteObject
ANR9999D ThreadId <51>  0x00000001003d3800 DeleteBackups
ANR9999D ThreadId <51>  0x00000001003d4c80 imFSDeletionThread
ANR9999D ThreadId <51>  0x00000001000063c8 StartThread
ANR9999D ThreadId <51>  0x090000000053650c _pthread_body
ANR9999D imfsdel.c(1847): ThreadId <51> IM not able to delete object
0.1066965103, rc: 19
ANR9999D ThreadId <51> issued message 9999 from:
ANR9999D ThreadId <51>  0x0000000100017f78 outDiagf
ANR9999D ThreadId <51>  0x00000001003d3840 DeleteBackups
ANR9999D ThreadId <51>  0x00000001003d4c80 imFSDeletionThread
ANR9999D ThreadId <51>  0x00000001000063c8 StartThread
ANR9999D ThreadId <51>  0x090000000053650c _pthread_body
ANR0987I Process 59041 for DELETE FILESPACE running in the BACKGROUND
processed 25 items with a completion state of FAILURE at 15:30:40.

I cannot find both the return codes 19 and 78 in the list of known
return codes for TSM...
It's reproducible. Anybody seen this before?
Thank you very much for any reply in advance!
Kind regards,
Eric van Loon

Looks like an IBM support case, probably a missing object or
something.

-km
**********************************************************************
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain
confidential and privileged material intended for the addressee
only. If you are not the addressee, you are notified that no part
of the e-mail or any attachment may be disclosed, copied or
distributed, and that any other action related to this e-mail or
attachment is strictly prohibited, and may be unlawful. If you have
received this e-mail by error, please notify the sender immediately
by return e-mail, and delete this message.

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries
and/or its employees shall not be liable for the incorrect or
incomplete transmission of this e-mail or any attachments, nor
responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
Dutch Airlines) is registered in Amstelveen, The Netherlands, with
registered number 33014286
**********************************************************************