Also, if you have any custom routines that use a 10 character password, you need to fix those. For example, I have an FTP routine between our two i5's. The user has to key in their password at which point I build a script to do the actual porting. Some people keep those in a source member. Either way they might need to be changed. There might be similar situations.


* Jerry C. Adams
*IBM System i Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
615.995.7024
fax
615.995.1201
email
jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>



James Lampert wrote:
Rizzi, Mike wrote:

That being said - it would be ideal if we could match the password
constraints of WINDOWS, particularly in regards to length (max length
14) - to do this we would have to go to password level 2. I have done some of the pre-conversion work such as verifying current
passwords on our system are level 2 compliant.
What other gotchas are waiting to bite us?

If you have, or are planning on getting, any client-server products that assume a 10-character non-case-sensitive password, you're screwed.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.