Hello
I'm using the tsm api to bakup and restore objects to and from a tsm server 5.1.6.
Backup operations seem to proceed well, whereas restore operations fail time to time.
I set brakpoints on my programs to check if the structures I send to the tsm api function call dsmBeginQuery and dsmGetNextQObj are correct, and they seem to be. I also checked via the command line if the file I tried to restore exist on the tsm filespace I use in my application, and they do; I can restore them via the command line dsmc .
Depite all that, in my program, the dsmGetNextQObj fail with return code
DSM_RC_ABORT_NO_MATCH.
So I would like to know if they were any known bugs about those functions call, or if someone issued the same problems wether while using the API or the command line dsmc when retrieving objects.
I'm using api version 5.2.2 and server version 5.1.6.7
Thanks in advance.
I'm using the tsm api to bakup and restore objects to and from a tsm server 5.1.6.
Backup operations seem to proceed well, whereas restore operations fail time to time.
I set brakpoints on my programs to check if the structures I send to the tsm api function call dsmBeginQuery and dsmGetNextQObj are correct, and they seem to be. I also checked via the command line if the file I tried to restore exist on the tsm filespace I use in my application, and they do; I can restore them via the command line dsmc .
Depite all that, in my program, the dsmGetNextQObj fail with return code
DSM_RC_ABORT_NO_MATCH.
So I would like to know if they were any known bugs about those functions call, or if someone issued the same problems wether while using the API or the command line dsmc when retrieving objects.
I'm using api version 5.2.2 and server version 5.1.6.7
Thanks in advance.
