×
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.
On 23/04/2008, at 3:42 AM, rob@xxxxxxxxx wrote:
Limiting characters was a good way to forbid words. Taking out
vowels was
a common technique. Removing this capability does not do much for
"freedom of choice" for administrators.
Yes, that's my point.
However, from a V6R1 machine:
Message ID . . . . . . : CPF22C5
Date sent . . . . . . : 04/22/08 Time sent . . . . . . :
13:41:14
Message . . . . : Password contains one of the following: A.
Cause . . . . . : The password rule for restricted characters in
passwords
(system value QPWDLMTCHR) requires that they not contain any of the
following characters: A.
Recovery . . . : Specify a new password that does not contain
any of
the
restricted characters.
The error message still exists because you may be running with
QPWDRULES set to *PWDSYSVAL which means the old rules (and system
values) are in effect.
Once you change to the new rules you lose one of the old ones. I
think it should still be available as an option (*CHRLMTCHR or
*LTRLMTCHR or something).
Normally, when a feature is removed the IBM documentation is pretty
good at pointing that out. I can't find any such indication hence my
question.
Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists
http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------
As an Amazon Associate we earn from qualifying purchases.
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.