RE: Running Java Application from Job Scheduler and User Has No Password

PASSWORD(*NONE) makes it so the profile can not login at all.  It
effectively makes it only eligible to own objects and be an authority
reference.  In addition to setting the password to 'Gibberish' as was
suggested in a previous post, you can set the initial menu to *SIGNOFF
in the USRPRF.  This way even if they 'guess' the gibberish password
they get signed off first thing.  We had to do this to allow access to
our files via JDBC.  

> Thanks Gary, I was rapidly coming to that conclusion myself. Sometimes
the
> documentation is a bit lax in regards to what services are being used
and
> what the overal requirements are going to be. I went round and round
with
> the auditors over this user profile so I could give it a good amount
of
> authority but disallowed it from logging in etc., by not having a
> password.
> Now when they come back next month, I'll be explaining why it has to
have
> a
> password now.
> 
> Thanks again,