Author Topic: CMOD MP v10.1.0.4 (Use File System) - Storage PATH Changed Wildly?  (Read 2054 times)

tehrenreich

  • Newbie
  • *
  • Posts: 4
    • View Profile
We are in the middle of migrating off of TSM and now with Fix Pack 4 for v10.1 the pathing all changed for (External Storage Manger - Use File System) causing us a huge setback in developed migration scripts.

Question - Can anyone shed light on what the different parts of the new PATH storage represent?  AND Why the path changed

CMOD MP v10.1.0.(GA/FP1/FP2/FP3) Path Format
Z:\IBM\ONDEMAND\ARCHIVE\BBA\196FAA

CMOD MP v10.1.0.4 Path Format
Z:\IBM\ONDEMAND\ARCHIVE\3\BBA\BBA\00\FAA\196FAA

tehrenreich

  • Newbie
  • *
  • Posts: 4
    • View Profile
Re: CMOD MP v10.1.0.4 (Use File System) - Storage PATH Changed Wildly?
« Reply #1 on: May 02, 2019, 05:30:31 AM »
*** Follow-UP ***
CMOD MP v10.1.0.4 Path Format
Z:\IBM\ONDEMAND\ARCHIVE\3\BBA\BBA\00\FAA\196FAA
In this example path for Fix Pack 4 of v10.1!

Question: Why is Directory BBA repeated twice?
Question: What is the meaning/purpose of Directory Path FAA?
Question: The ordinal number 00, how is this derived and means what?

Regarding the ordinal # we've done some testing.
We are confused what the ordinal number is doing for storage.

It doesn't appear to be used to evenly split # of OBJECTS based on the following obervations.

LOAD_ID = 100
Ordinal # = 00

LOAD_ID = 12345
Ordinal # = 01

LOAD_ID = 92345
Ordinal # = 09

LOAD_ID = 99999
Ordinal # = 09

LOAD_ID = 100000
Ordinal # = 10

LAOD_ID = 109000
Ordinal # = 10

LOAD_ID = 111000
Ordinal # = 11

cjlewis

  • Newbie
  • *
  • Posts: 2
    • View Profile
Re: CMOD MP v10.1.0.4 (Use File System) - Storage PATH Changed Wildly?
« Reply #2 on: May 03, 2019, 09:19:25 AM »
CMOD supports multiple platforms, some of which have file system limitations such as a limit to the number of files in a directory or a limit on the number of directories. Naming is often designed to work within those limitations. What objects are named is much less of a concern than if those objects can't be stored or retrieved. Describing the various parts of the names is not done in the documentation since naming may change at any time, as you've seen. The file system storage is unmanaged unlike cloud storage or TSM so there is no database to record short names or hashes to simplify directory structures.

tehrenreich

  • Newbie
  • *
  • Posts: 4
    • View Profile
Re: CMOD MP v10.1.0.4 (Use File System) - Storage PATH Changed Wildly?
« Reply #3 on: May 03, 2019, 10:23:32 AM »
We require explanations of the PATH parts so we can complete an architecture change of 10 Million Objects from TSM Storage to File System Storage.  So complete explanation of how the File System Storage PATH is architected is a requirement.  We are attempting to sunset our TSM server and move over to a technology that better suites our requirements (NAS Storage - File System Storage).

Justin Derrick

  • IBM Content Manager OnDemand Consultant
  • Administrator
  • Hero Member
  • *****
  • Posts: 2229
  • CMOD Guru for hire...
    • View Profile
    • Tenacious Consulting
Re: CMOD MP v10.1.0.4 (Use File System) - Storage PATH Changed Wildly?
« Reply #4 on: May 03, 2019, 02:29:38 PM »
I have a utility that does this , but it's only for the UNIX systems, and wouldn't run on Windows...

You're likely going to have to use arsadmin store in order to be supported.

-JD.
IBM CMOD Professional Services: http://TenaciousConsulting.com
Call:  +1-866-533-7742  or  eMail:  jd@justinderrick.com
IBM CMOD Wiki:  https://CMOD.wiki/
FREE IBM CMOD Education & Webinars:  https://CMOD.Training/

Interests: #AIX #Linux #Multiplatforms #DB2 #TSM #SP #Performance #Security #Audits #Customizing #Availability #HA #DR