Re: The dreaded DST password

[jeff_carey@xxxxxxxxxx]

The problem with that approach seems to be that if one of those users 
disables their profile (which is very easy), the only way to fix it is 
from the console (which is 30 miles away). 


Jeff Carey





"Vern Hamberg" <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
07/03/2003 12:56 PM
Please respond to "Midrange Systems Technical Discussion"

 
        To:     "Midrange Systems Technical Discussion" 
<midrange-l@xxxxxxxxxxxx>
        cc: 
        Subject:        Re: The dreaded DST password


What about going into DST and giving each person who needs access his own
DST profile? You can also change passwords there to a duplicate with no
check. You can also control what each one has access to.

Then change the password for QSECOFR, lock it up, and never use it, except
for service personnel.

Maybe?

Vern

At 08:38 AM 7/3/2003 -0500, you wrote:
>We run into continual problems with out DST profiles becoming disabled 
(as
>people forget or try to use SST without the correct password).
>
>Would it be possible to create a batch job that would reset a dst profile
>and change it's password?   I know we can rest QSECOFR to *DEFAULT using
>CHGDSTPWD, but can we then change it to a specified value using a batch
>job?   Of course that value would have to increment to avoid duplicating
>passwords, but is this even possible?
>
>
>Jeff Carey


_______________________________________________
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.