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