• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.


    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

Export / Import clopset



We are in a struggle, where we need to export the clopset from TSM1 (Shared Server) to a dedicated customer TSM server.
I havent been able to find an easy way to do this, since exporting it to a text file and importing it by defining a script dosent work...
Also i cant seem to find any commands, to achieve this, which i find very odd - this should be common?

The shared TSM server can not and will not, be able to communicate with the customers TSM server - so we have to export it to a script / .txt file (or similar).

Shared TSM server is running 7.1.7
Dedicated TSM server is running 8.1.1

Thanks in advance.


ADSM.ORG Moderator
You can use the EXPORT SERVER command with FILEDATA=NONE. However, this will include:
  • policy sets
  • management classes
  • copy groups
  • schedules
  • administrators
  • optionset definitions
  • node definitions
You can't filter out just the option set. This would be good if you want to migrate all nodes and settings to a new server.

You could do it using configmanager and profiles, however that requires the two servers to talk to each other which the customer won't do.

This leaves you with one option, output the current client option set to a file and manually create them:
q cloptset > /tmp/cloptset.txt

Or, if you feel adventurous, you can create a couple of macros on the source server. Important to test this out in a non-prod environment first:

Create the two macros:
dsmadmc -id=admin -pa=admin -dataonly=yes "select 'define cloptset ',optionset_name from cloptsets" > cloptset.mac

dsmadmc -id=admin -pa=admin -dataonly=yes "select 'define clientopt ',optionset_name,option_name,option_value,'force=',force,'seqnumber=',seqnumber from clientopts" > clientopt.mac
The first macro (cloptset.mac) will not need editing.

The second macro (clientopt.mac) will.
- need to remove extra spaces, use find and replace in your text editor of choice to replace 2 spaces with 1 space, repeat until there are no more double spaces
- need to remove the space after the = with both force and seqnumber. Replace "= " with "=".

Then to run the macros:
dsmadmc -id=admin -pa=admin -itemcommit macro cloptset.mac

dsmadmc -id=admin -pa=admin -itemcommit macro clientopt.mac
Last edited:


Thanks so much for your reply.
Ive managed to copy the cloptset, by using your guide and replacing spaces in the .txt files.

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 8 21.6%
  • Keep using TSM for Spectrum Protect.

    Votes: 19 51.4%
  • Let's be formal and just say Spectrum Protect

    Votes: 6 16.2%
  • Other (please comement)

    Votes: 4 10.8%

Forum statistics

Latest member