Re: *CURRENT user with PASSWORD(*NONE)

I guess setiing the PWDEXPITV property of the userprofile to *NOMAX will do
the trick.

Rune




                    "McCallion,
                    Martin"                  To:     "'java400-l@midrange.com'" 
<java400-l@midrange.com>
                    <martin.mccallion@       cc:
                    misys.com>               Subject:     *CURRENT user with 
PASSWORD(*NONE)
                    Sent by:
                    java400-l-admin@mi
                    drange.com


                    09.09.2002 13:52
                    Please respond to
                    java400-l






This morning we received an AS400SecurityException with the text:
"Password is expired".  The class in question was running fine on
Friday, and the user under which it was running has PASSWORD(*NONE).  We
are using the localhost/*current approach for system and user.  This was
when calling the connectService( AS400.DATAQUEUE ) method.  A series of
JDBC connections in the same job also failed to establish, but they
didn't provide such a clear error message.

In the following entry in the list archives:
http://archive.midrange.com/java400-l/200204/msg00024.html Dave Wall
states this:

           "As a convenience when running on the iSeries, the Toolbox can
use the
            userid and password of the job's current thread instead of
having them
            supplied by the application.  This does not, however, override
the first
            consideration.  If the thread's password is *NONE or expired,
the
            connection will not work."

Which would imply that our approach should never have worked.

We got around the problem by changing the user profile to have a
password, signing on and off (I doubt that this was necessary) and
changing it back to not having a password.  This is no great problem for
us; however, we are a software vendor, and it would be at least an
annoyance for our clients to have to do this once a month, for example
(I suggest this time period because our passwords are set to expire
monthly. though that may have nothing to do with it).

Is there any way to prevent this happening again?  We are at V5R1, and
using the toolbox with native optimisations,
/QIBM/ProdData/OS400/jt400/lib/jt400Native.jar.

Cheers,

Martin.

--
Martin McCallion
Senior Technical Consultant
Work:  martin.mccallion@misys.com
Home: martin.mccallion@ukonline.co.uk
Misys International Banking Systems
1 St George's Road, London, SW19 4DR, UK
T +44 (0)20 8486 1951
F +44 (0) 20 8947 3373
www.misys.com
This email message is intended for the named recipient only. It may be
privileged and/or confidential. If you are not the  intended named
recipient of this email then you should not  copy it or use it for any
purpose, nor disclose its contents to any other person. You should
contact Misys International Banking Systems as shown below so that we
can take appropriate action at no cost to yourself.
Misys International Banking Systems Ltd,1 St
George's Road, London, SW19 4DR, UK. Email: ibs.postmaster@misys.com.
Tel: +44 (0) 20 8879 1188 Fax: +44 (0) 20 8947 3373
Misys International Banking Systems Ltd is
registered in England and Wales under company no. 971479
_______________________________________________
This is the Java Programming on and around the iSeries / AS400 (JAVA400-L)
mailing list
To post a message email: JAVA400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l
or email: JAVA400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/java400-l.