Testmachine with TSM installed getting errors

[akstrom]

Hi

I have a test machine with TSM installed that is now giving me error, and will not load new documents into CMOD:

TSM Error: ANS0266I (RC2302) The dsmEndTxn vote is ABORT, so check the reason field., Return Code=2302, Reason=29, File=arssmsms.cpp, Line=3774  Srvr->xxxxxx<-

I know we had some space issues last week, but it was solves and we added more disk.

I am not sure, but could it be that the disk that is added needs to be "added" to TSM (even though the disk system under /tsmdata looks ok now) ?
Or is this some other problem than disk error.

We were thinking of just switching the
ARS_STORAGE_MANAGER from =TSM to =CACHE_ONLY, but will this give us problems along the road ?

I do not have TSM installed in production and the one on the test machine was installed a long time ago (but have been updated)
 

[Justin Derrick]

There's a section on the wiki that describes this and links to the IBM Documentation: 

https://cmod.wiki/index.php?title=Troubleshooting_Content_Manager_OnDemand#Return_Codes

Your error return code seems to imply that you dn't have any more storage space - you may need to assign any new volumes to a specific storagepool.

From the TSM API Docs:

Code: [Select]

#define DSM_RS_ABORT_NO_STOR_SPACE_STOP      29
-JD.

[akstrom]

Thanks, Justin
I know we had shortage of space, but we added more space and should have more than enough. Do we need to "mount it" somehove .. the new space ?

Before last week the space looked like this : /dev/fslv03      205,00      6,12   98%      107     1% /tsmdata
And now it is like this : /dev/fslv03      250,00     49,96   81%      107     1% /tsmdata

But it looks like it does not accept the new disk

Sincerely,

Anne K Strøm

[akstrom]

... and is it possible to "skip" the TSM by just change the ARS_STORAGE_MANAGER from TSM to CACHE_ONLY ?

[Justin Derrick]

Depends on the configuration -- if they're sequential volumes (like tapes) then you need to manually add volumes or might need to change your 'maxscratch' parameter. 

As for disabling TSM, it's just going to result in a lot of weird errors as CMOD tries to do retrievals and maintenance tasks since the App Groups are likely configured for it.  If that's not a concern, then carry on.

-JD.