You are correct, I guess it can minimally satisfy the requirement.
TSM supports 41 characters of the standard 94 allowed characters.
I am in agreement that TSM passwords can be very secure, especially
since we allow 5 wrong password attempts before the account is locked.
In reality, a 4 characte
I have not personally submitted an enhancement request. I have requested
it in a few different meetings with IBM/TSM people. It's been a while
but I think one of them was going to submit one on my behalf. I searched
the RFE page and the only related one is tying it to LDAP for passwords,
so I subm
-Kevin Kettner wrote: -
>Does anyone know if IBM is ever going to expand the character set
>accepted for TSM passwords? I was hoping that would happen in TSM
>6.3,
>but apparently it still has the same password rules as it has for as
>long as I can remember:
>
>http://pic.dhe.ibm.com/infoc
I'm in agreement. I don't think complex passwords add that much more
security, but I constantly get flack from people who don't really
understand that.
On 7/24/2012 8:37, Allen S. Rout wrote:
On 07/23/2012 06:03 PM, Kevin Kettner wrote:
http://xkcd.com/936/
I think this reference rebuts you
On 07/23/2012 06:03 PM, Kevin Kettner wrote:
http://xkcd.com/936/
I think this reference rebuts your desire, rather than supporting it.
In fact, I was already looking for the comic in order to rebut, before I
got to the end of your message. :)
- Allen S. Rout
Sven,
"Run as administrator" did it. Thanks. I knew I was missing something
2008 specific.
Ullrich,
Sorry, I should have put my commandlines in the original post.
I already use -k and -u flags.
Also, as shown in the OP, I was already in the instance directory.
Habit, and easier than messing wit
Charles,
I support Wanda's suggestions, and would like to add another
possibility.
For some time we were experiencing nightly issues where the backup of
large files was causing log-pinning and ultimately the backup processes
were being canceled, as well as larger backups taking a long time to
comp
Hello Josh,
in a Windows environment you need to start dsmserv in foreground using the
parameter "-k"
Try to run from commandline (so called DOS box):
dsmerv.exe -k server1
(server1 is usually the first TSM instance name)
You need to cd to the instance directory where dsmserv.opt resides, fir
