how to stop using TSM with CMOD?

[Shannan]

Is there a way to stop using TSM with CMOD?  We have a relatively small CMOD system (less than 50 GB of storage), only uses disk in TSM, CMOD 9.5.0.8, TSM is 7.1.1.2 on Windows.  It's a very simple OD system - just basic loading of reports for users to view via the Navigator client.  No report distribution, etc...

[Justin Derrick]

TSM doesn't require much care and feeding once it's configured properly.  There's no documented process for this -- you move the items out of TSM and back into cache with arsadmin retrieve and arsadmin store, then turn off migration of data in the App Group config, then turn off data migration in the nightly maintenance.  You'll still have the old TSM storage sets configured, but they won't be used.  CMOD may refuse to start up without the TSM server responding to requests, so you'll have to test that out and possibly change it to a cache only server.

Having said all this, none of what I've described is supported by IBM, and you may get the occasional weird error.  Test this thoroughly to determine if this process works for you.

-JD.

[Lars Bencze]

If you only have 50 GB of data stored in the TSM, I would suggest that you:

• create new Application Groups (copy the existing ones) which use cache instead of TSM for storage
• export all your TSM-stored documents, and
• reload them into the new Application Groups.

If you use TSM for DB backups, you need to redirect your backup scripts and reconfigure OnDemand to backup DB2 to disk instead.

Once you have eliminated your need for TSM, change your ars.cfg ARS_STORAGE_MANAGER=TSM to "CACHE_ONLY" and you should be done.

[Justin Derrick]

Lars' solution is better supported, but might be more work.  You may as well build a new CMOD server.

-JD.