Hi,
thanks for the answer.
I may have explained the problem poorly. New try.
If we have in a sqlful.bat script:
tdpsqlc backup * full /configfile=someconfig.cfg
and the file someconfig.cfg does not exist, the command runs along with
default config and returns with rc=0.
Problem with that is
Hi,
I have a strange problem with TSM Server 6.3.4.300 on Windows Server.
When I try to delete a disk volume do I get following error.
Any idea how I can delete this disk volume from TSM?
ANR0162W Supplemental database diagnostic information: -1:58030:-1655
([IBM][CLI Driver][DB2/NT64]
Call it in to IBM; those messages clearly are not, business as usual. Even if
I thought I recognized them, I still would worry that they don't mean the same
on your system as mine.
It reminds me of a problem I saw on a 6.2 system last fall. Lots of
undocumented commands were dictated by IBM
H, last week I applied 6.3.4.0 after running for some time on 6.3.0.0.
Decided to search my actlogs for this message and 2 of 5 of my servers have
them too.
Christian, please post what the cause/solution is, I will reach out to IBM as
well.
Thanks
Rick Adamson
-Original
What kind of disk are ?
2014-06-05 8:00 GMT-05:00 Rick Adamson rickadam...@biloholdings.com:
H, last week I applied 6.3.4.0 after running for some time on 6.3.0.0.
Decided to search my actlogs for this message and 2 of 5 of my servers
have them too.
Christian, please post what the
Christian,
Agreed, you need to open a ticket.
Also, do you know about the special audit script you have to run if you do
DISCARDDATA on a dedup vol:
http://www-01.ibm.com/support/docview.wss?uid=swg21666371myns=swgtivmynp=OCSSGSG7mync=E
Wanda
-Original Message-
From: ADSM: Dist Stor
Hi Hans,
I agree with you. Please open a PMR.
Del
ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 06/05/2014
05:45:50 AM:
From: Hans Christian Riksheim bull...@gmail.com
To: ADSM-L@vm.marist.edu
Date: 06/05/2014 05:46 AM
Subject:
I am not sure if this is documented, but after I upgraded my TSM servers to 7.1
code. Somehow the passexp setting for all of my TDP nodes got change from 0
(zero, never expire) to blank, which means they now will take the server
default settings. Where is this documented?
Other issues are a
