Archives of the TeradataForum
Message Posted: Mon, 14 Aug 2000 @ 09:48:33 GMT
Hi Dave and David,
the problem is not to change the passwords in teradata. The problem is to distribute the new passwords in all the logon files on different platforms. You have to stop all production processes as long as you need to change the password and change the logon files. Some of them could be on MVS, some on UNIX and the Business Objects users are stored on a third place.
Surely, it is possible to do all this stuff but it is boring. And some of the tasks need a huge overhead of administration to be sure that all the scheduling tasks are done correctly. We are running some thousand batch jobs a day. I was a little bit upset as NCR mentioned that change request was from 1996. I can not understand why NCR agreed a change request but did not implement it without any notice to their customer. =CD To correct the last sentence: I can understand that it is not a easy problem to change the password expiration from system level to user level but I expect to be informed about the changes and the timeframe.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|