correction:

the lowlevel name must include a "slash"
/myfile.txt

On 2/11/07, Helder Garcia <helder.garcia AT gmail DOT com> 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 object name. For example: myfile.txt

object type (d/f): If directory or file. In the example, it must be file
(f).

object owner name: the OS user that will be the owner on TSM. root, for
example.
wait for mount (y/n): Didn't try it. Probably if you want to wait for
media mount. No effect if you're using diskpool.

seed string: From the API Guide:
"The sample application creates its own data streams when backing up or
archiving objects. It does not read or write objects to the machine file
system. The object name does not correspond to any file on your workstation.
The "seed string" that you enter generates a pattern that can be verified
when the object is restored or retrieved."

mgmt class override: If you want the object bound to another management
class, instead of the default one. It is like the INCLUDE xxx MC statements.
Leave it blank to use the default management class.


On 2/11/07, Beth Rogers <brogers966 AT yahoo DOT com> wrote:
>
> 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 that I would like to use to see if the problem is on my end or in
> the
> application but my problem is I don't know what to feed the API tester
> during the archive prompts.   Using the api tester, dapismp.exe, I can
> log
> on successfully but don't know how to answer these questions: highlevel,
> lowlevel, object type (d/f), object owner name, wait for mount (y/n),
> seed
> string, mgmt class override.
>
> The host is an AIX-RS/6000 box with TSM Server Version 5, R2, Level 7.1.
> The client is Windows Server 2000 SP4, TSM CLient version 5, R3, Level
> 3.0.
>
> Has anyone used this before, know what kind of answers are needed or
> know
> where to find the documentation for the api tester?  I have been
> unsuccessful in my searches.
>
> Thanks in advance ....
>



--
Helder Garcia

--
Helder Garcia