× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



We moved to level 2, no problems. Only a few "caps lock".

Jim Essinger wrote:

Charles,

Yes, we are still using a password level of 0. I am also interested in
user experiences of those who have gone from 0 to 2 or 3.

Jim


On Mon, Oct 1, 2012 at 3:39 AM, Charles Wilt <charles.wilt@xxxxxxxxx> wrote:


No replies? Does this mean everybody is still running at password level
0? :)

Charles

On Fri, Sep 28, 2012 at 9:45 AM, Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:

All,

We're considering moving from password level 0 to password level 2 or
3 on v5r4...

I've read through the "Considerations for changing QPWDLVL..."
sections of the infocenter.

But I'd appreciate any feedback from those of you who have done this

already.

One specific question I have, we have custom sign-on screens. I know
these need to change to support passwords greater than 10 chars, but
if we leave the QPWDMAXLEN at 10 initially, can we leave the signon
screens alone after changing QPWDLVL until we want to actually start
using long passwords? Our initial goal is simply to support
mixed-case passwords.

Lastly, the documentation for both level 2 and 3 say, "not use
password level 2 if your system communicates with other systems that
use password level 0 or 1 passwords or run on pre-V5R1 versions of the
operating system." All of our systems are at v5r4, so that's not an
issue. However, we've got 130+ systems :) At the very least, we'd
like to change our development system first, followed by our
QA/PRE-PROD systems, before we start on the 120+ production boxes....
Obviously, non-production boxes don't talk to production boxes very
often, but there is some communications. Such as our CMS (Aldon)
using SNADS to send deployments and many developers use TELNET or
STRPASTHR from development to a production box.
Is that going to continue to work with the boxes at different
QPWDLVLs? Or do I really need to change every box at once?

From what I can tell, having the boxes at different QPWDLVLs should be
ok as long as we don't start using long/mixed case passwords till all
boxes are changed...

Thanks!
Charles

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.





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.