Transfer documents from one folder to another

[Steve Lance]

We have documents loaded into a folder with a retention of 3 years.  We need to load these documents into a folder with 10 year retention.  I have over 200,000 documents to move.  Is there an easier way to accomplish this besides ARSDOC Get and then do an ARSLOAD?

[Justin Derrick]

Hi Steve.

The supported way to do this is through arsdoc/arsload.  There are third party utilities you can use to automate the process and generally make your life easier.  Send me a PM if you'd like to know more.

-JD.

[hakan_carlberg]

Hi
I don't know all the details, like why use two folders ?
What Plattform are you running ?

Have you thought about just changing "Life of Data and Indexes " on the application group ?

[Justin Derrick]

The usual reason is that the Application Group is tied to a storage set that only stores documents for 3 years.  Changing the Life of Data and Indexes doesn't stop the storage manager from deleting it.  Changing the Storage Manager to keep documents for 10 years means the documents that still only need to be kept for 3 years will end up being kept for 10, which is just as bad.

This is why I always recommend that users define a new Storage Set with each new Application Group they define, and a unique Node in Tivoli Storage Manager / Spectrum Archive.  With each Application Group having it's own Storage Set and Node, retention requirements can be changed quickly and relatively easily without affecting any other documents in the IBM CMOD archive.

-JD.

[hakan_carlberg]

Hi
I don't know how it's on Distributed platforms.
But we're running z/OS and changing "Life of Data and Indexes " on the application Group,and only using ARSMAINT do
maintain documents(not OAM-delete), will keep the documents in the Application Group for the time period.

At least that is how we do if we change the retention period.

[Justin Derrick]

Tivoli Storage Manager is usually configured differently -- there are Storage Sets defined, which are connected to TSM Nodes, which have policies defined to retain documents for a fixed period of time (usually 3, 7, or 10 years).  This config leads to the problem that Steve is experiencing -- a change in retention means an export / import cycle, or modifying the retention in TSM, leading to other issues.  I've been recommending that CMOD is configured with One App Group associated with one Storage Set, which is connected to one TSM node for several years now.

-JD.