Del,
I've tried all that, but it doesn't work.
Met vriendelijke groet, with kind regards,
Richard van Denzel
Consultant
IBM CATE, TSM Certified Consultant
____________________________________________________________
Solution Professional Services B.V.
____________________________________________________________
Transistorstraat 167, 1322 CN Almere
Postbus 50044, 1305 AA Almere.
T: +31 (0)36 880 02 22
F: +31 (0)36 880 02 44
M: +31 (0)652 663 978
W: www.sltngroup.com
E: [EMAIL PROTECTED]
____________________________________________________________
Solution Professional Services B.V. is onderdeel van SLTN GROUP
IBM Premier Business Partner
____________________________________________________________
Del Hoobler <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
05-01-2004 16:18
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Re: TDP for SQL problem ACO5091E or ACO5422E
Richard,
ACO5091E also is displayed when the password stored
is not correct. Try this:
1. Add "CLUSTERNODE YES" to the DSM.OPT file.
2. Reset the password on the TSM Server for the node you
are using for DP for SQL.
3. Issue a command that connects to the TSM Server
specifying the /TSMPASSWORD= option. For example:
TDPSQLC QUERY TSM /TSMPassword=password
4. Retry the command that was failing.
Thanks,
Del
----------------------------------------------------
> I have a strange problem with TDP for MS-SQL 5.2.1.0 (running on TSM
> Server 5.2.1.3 on Windows 2003 Server).
>
> When I put CLUSTERNode yes in the DSM.OPT I get error ACO5091E, which
> basically tells me that I'm using PASSWORDACCESS GENERATE but there is
no
> password (how come that the normal BA-client is working then?).
> When I put CLUSERNode no in the DSM.OPT I get error ACO5422E, telling me
> that an ODBC error occurred with MS-SQL (now PASSWORDACCESS GENERATE
> works).
>
> The above system is part of an active-passive Microsoft cluster.
