On Feb 11, 2007, at 8:23 PM, Helder Garcia wrote:
correction:
the lowlevel name must include a "slash"
/myfile.txt
Actually, not, if this conforms to TSM conventions:
the HL_NAME portion from a client path includes the last slash
preceding the LL_NAME, which is simply the filename within the
correction:
the lowlevel name must include a "slash"
/myfile.txt
On 2/11/07, Helder Garcia <[EMAIL PROTECTED]> wrote:
What I could deduce they have these meanings. An example, to an object
/tmp/myfile.txt
highlevel: directory where the object is located. For example: /tmp
lowlevel: the objec
What I could deduce they have these meanings. An example, to an object
/tmp/myfile.txt
highlevel: directory where the object is located. For example: /tmp
lowlevel: the object name. For example: myfile.txt
object type (d/f): If directory or file. In the example, it must be file
(f).
object own
I have an application from Nice Systems which uses the TSM API to archive
files but it is not working. It only seems able to create filespaces but
not actually place the file on the TSM host. And no errors are being
generated anywhere. There is a TSM API Tester that comes with the TSM
client tha
