Re: DST/SST woes

[Steve Richter <stephenrichter@xxxxxxxxx>]

On 5/2/05, Haase, Justin C. <justin.haase@xxxxxxxxxxxx> wrote:
> You just need to IPL to DST (manual mode IPL) _after_ doing the
> CHGDSTPWD.  The new QSECOFR password will be case-senstive QSECOFR.
> Then make sure if you want to be able to do this without a manual IPL
> next time to change the security setting in DST (not sure of exact
> option number) to allow users to change an expired password with the
> system running.

I dont think you need to IPL to complete the password change.  running
STRSST will start the process just as the manual ipl will.  Here are
my notes on the topic:

In the event of "dst profile is expired" or "profile disabled", do the
following:
- chgdstpwd *default
- strsst
- when prompted for dst user name and password, press f9 to change the password
- change the password.  the current password value is case sensitive,
so if "qsecofr" does not work, enter "QSECOFR".

-Steve

> 
> Justin C. Haase - iSeries System Administrator
> IBM Certified Systems Expert - eServer i5
> Kingland Systems Corporation
> email - justin.haase@xxxxxxxxxxxx
> 
> 
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of George Kinney
> Sent: Monday, May 02, 2005 12:35 PM
> To: 'midrange-l@xxxxxxxxxxxx'
> Subject: DST/SST woes
> 
> I've run into a problem that I'm hoping someone has a novel solution to.
> 
> The QSECOFR userid for DST/SST has been disabled (apparently too many
> failed signon attempts), and I have no idea how to re-enable it.
> 
> I reset the password via CHGDSTPWD *DEFAULT, but since its disabled, it
> doesn't matter.
> 
> I can get into DST or SST via '22222222', but that user doesn't have
> authority to re-enable the QSECOFR profile. (In fact, no other profile
> appears when you go to that option.) There are no other SECOFR users
> defined in DST.
> 
> Looking through the docs, it looks to me like we'd have to re-install
> the OS to re-enable it. Is this true? Is there another way?
> 
> ----------------------------------------------
> George Kinney
> System Coordinator / NEX IS
> NEX Transport, Inc.
> gkinney@xxxxxxxxxxxxxxxx
> ----------------------------------------------
> --
> 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.
> 
> CONFIDENTIALITY NOTICE:  This e-mail communication, including attachments, is 
> covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is 
> confidential, and may be legally privileged.  If you are not the intended 
> recipient or believe you received this communication in error, please reply 
> to the sender indicating that fact and delete the copy you received.  In 
> addition, retention, dissemination, distribution, copying, or otherwise use 
> of the information contained in this communication is strictly prohibited.  
> Thank you.
> 
> --
> 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.
> 
>