Thanks. Looks like that did the trick when both node and password were
removed from the
scheduled script.
Different from the MS-SQL API. Such are standards.
>>> [EMAIL PROTECTED] 07/18/2005 12:36:21 PM >>>
PASSWORDACCESS=generate is not allowed when using -adsmnode and
-adsmpwd.
This is a securit
PASSWORDACCESS=generate is not allowed when using -adsmnode and -adsmpwd.
This is a security restriction imposed by the TSM API. To use the new
node name with
PASSWORDACCESS generate you have to:
1. copy dsm.opt to dsmnew.opt
2. update node name in dsmnew.opt to new node name
3. run: domdsmc q ad
