RE: Mixed-case password support

We went to password level 2 at the beginning of December.  We only had
problems with out of date client software.  Old releases of Client Access
won't authenticate to the new passwords.  I'm talking about the connection
dialog, not the emulated 5250 sessions.  A third party client-server report
writer had the same problem with its connection dialog, but they were able
to patch it within a couple of weeks.

We have a fairly large user community, so fair warning and communication
were important.  Fortunately users notice the new password level the first
time they change their password, not immediately after the system value is
set.  We performed an after-hours test, migrating from QPWDLVL 0 to
QPWDLVL2.  We set up a few new user profiles in advance for testing so that
we could document the (minimal) effects on the users.  At the end of the
test we switched back to QPWDLVL 0 and scheduled the real migration for
overnight a few days later, with notification for the users.  The test, the
change back, and the real migration each required an IPL.  We missed Client
Access and the report writer in our testing.  You should make sure that
everyone is up to date on Client Access if you're using it, and you should
test any authentication outside the realm of 5250 signon.


-Jim

James P. Damato
Manager - Technical Administration
Dollar General Corporation
<mailto:jdamato@xxxxxxxxxxxxxxxxx>



-----Original Message-----
From: Bill Brosch [mailto:bbrosch@xxxxxxxxxxxxxx]
Sent: Tuesday, December 30, 2003 3:07 PM
To: Midrange Systems Technical Discussion
Subject: Mixed-case password support


Hello everyone!

Has anyone used the 128 character mixed-case password support for V5R1?  If
so, 
any problems and/or gotchas?

Tia,
Bill

-- 
Bill Brosch
Swift Technologies
email:  bbrosch@xxxxxxxxxxxxxx
Voice:  (847) 289-8339
Fax:    (847) 289-8939