ADSM-L

Odd retrieve behavior with Sun sol6 & TSM 3.7.2.0 client

2001-09-06 11:21:55
Subject: Odd retrieve behavior with Sun sol6 & TSM 3.7.2.0 client
From: "Cook, Dwight E" <cookde AT BP DOT COM>
Date: Thu, 6 Sep 2001 10:21:09 -0500
Just a FYI on something real strange we saw here...

Say you have CLIENTA and you have an archive /d105/oracle/blah.cntl
Now over on CLIENTB you set up a SErver entry to pretend to be CLIENTA and
issue a retrieve like...
        dsmc retrieve -serv=myserv_clienta -pass=mypass
/d105/oracle/blah.cntl  /tmp/newname.cntl
IF /d105 doesn't exist on CLIENTB you will get an error of
        ANS4005E Error processing '/tmp': file not found

now the hoot is if you create a subdir under /tmp of /tmp/temp/ and do a
retrieve (don't specify a new name)
        dsmc retrieve -serv=myserv_clienta -pass=mypass
/d105/oracle/blah.cntl  /tmp/temp/
it works (but will still fail if you just try to retrieve to /tmp/ )

biggest hoot of all is if you create a /d105 on CLIENTB and do the original
        dsmc retrieve -serv=myserv_clienta -pass=mypass
/d105/oracle/blah.cntl  /tmp/newname.cntl
it will now work

?

talk about strange <:-/

just something to file away in the back of the brain somewhere incase you
happen to see a strange error with a retrieve in the future.

Dwight
<Prev in Thread] Current Thread [Next in Thread>
  • Odd retrieve behavior with Sun sol6 & TSM 3.7.2.0 client, Cook, Dwight E <=