Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - tehrenreich

Pages: [1]
1
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).

2
*** 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

3
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

Pages: [1]