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



When you do get into DST, either via IPL or via function 21,
one of the options in DST lets you configure this stuff...

----- Original Message -----
From: <rob@dekko.com>
To: <midrange-l@midrange.com>
Sent: Wednesday, November 06, 2002 8:51 AM
Subject: Re: How to start DST without an IPL


> This is a multipart message in MIME format.
> --
> [ Picked text/plain from multipart/alternative ]
> Yes.  With V5R2, you get that stupid message when you run CHGDSTPWD.  Then
> you have to start DST mode with function-21, to change the password.  The
> message alludes that you can configure your system not to have to do this
> but durned if I know how.
>
> Rob Berendt
> --
> "They that can give up essential liberty to obtain a little temporary
> safety deserve neither liberty nor safety."
> Benjamin Franklin
>
>
>
>
> Vern Hamberg <vhamberg@centerfieldtechnology.com>
> Sent by: midrange-l-admin@midrange.com
> 11/06/2002 10:05 AM
> Please respond to midrange-l
>
>         To:     midrange-l@midrange.com
>         cc:
>         Fax to:
>         Subject:        Re: How to start DST without an IPL
>
>
> Rob
>
> Not in QCPFMSG, at least. This looks new. What I wonder is, what happens
> if
> you disable QSECOFR's service tools user ID? I've been in an environment
> where many people had access to the QSECOFR service tools ID (not a
> production shop, a lab). We often ran into the problem where we did not
> remember whether the password was uppercase or lowercase, and then whoever
> got wrong would use CHGDSTPWD and have to find one that had not been used,
> then notify the rest of the team, etc.  yada yada yuk! So I've advocated
> having individual service tools IDs for anyone who needs to get to DST,
> and
> that no one be given access to QSECOFR for this, except one primary
> administrator.
>
> But does v5r2 make this even more prone to this kind of confusion?
>
> Vern
>
> At 08:59 AM 11/6/2002 -0500, you wrote:
> >This is a multipart message in MIME format.
> >--
> >[ Picked text/plain from multipart/alternative ]
> >Does V5R1 have this message?  I don't have any machines with that old of
> >an OS:
> >
> >CPF4AB7
> >Message . . . . :   Service tools user ID password cannot be changed.
> >Cause . . . . . :   Your system is configured to prevent a service tools
> user
> >   ID with a default and expired password from changing its own password.
> >
> >Recovery  . . . :   Either change the password of the service tools user
> ID
> >   through DST or use the Start Service Tools (STRSST) command, select
> the
> >   option to work with system security, and enable service tools user ID
> > with a
> >   default and expired password to change its own password. Try the
> request
> >   again.
> >
> >Rob Berendt
> >--
> >
> >Vern Hamberg <vhamberg@centerfieldtechnology.com>
> >
> >         To:     midrange-l@midrange.com
> >         cc:
> >         Fax to:
> >         Subject:        Re: How to start DST without an IPL
> >
> >
> >On V5R1, anyway, if you use CHGDSTPWD and then go into DST (or SST), you
> >need to change the password, and you cannot repeat a certain number (?)
> of
> >them.
> >
> >But once _in_ DST, you can change the password for any DST user to
> >anything, even repeated ones.
> >
> >This is similar to the situation with CHGUSRPRF vs. CHGPWD - the former
> >does not enforce the password rules, the latter does.
> >
> >But V5R2 may have changed some of this.
> >
> >Vern
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.