>Has anyone been able to query the client backup files from a custom program
>using the TSM API?
>I tried using the dsmapi.exe as a starting point to query backup objects
>(made with the GUI/CLI clients) from the TSM API but I'm constantly getting
>"format unknown" for files I can see using the GUI:
>
>*** dsmGetNextQObj failed:
>ANS1245E (RC122)  Format unknown
>
>It looks like if the API would reject passing info to the DAPISMP.exe app
>which was not sent to TSM using the API (I'm able to backup a file using
>dapismp.exe and then I get the right results)
>
>Can someone tell me how to bypass this limitation?
>
>Server and clients are all Windows based.
>My final objective is to scan the metadata in the server in order to gather
>some statistics on versions, sizes, dates, etc

Still trying, huh?  You're just the latest one to pursue this Holy Grail in
trying to compensate for the lack of an administrative API in the product.  I've
tried, too, and found that the API can at best report higher level data, about
filespaces, etc., but not files.  I summarized the situation in the "API" entry
in ADSM.QuickFacts.  The API manual's chapter 4 talks a bit about
interoperability, but not in terms of what can be achieved from the API to get
at B/A client data.

Maybe, someday, the product will provide this long-missing programming
capability; but for now it doesn't exist.

  Richard Sims, BU