DST & OS qsecofr password lost

[Andy Wong]

Hi, I got a machine from oversea. It has already installed V5R2. I don't
have any password at all.

I know I can reset the DST password from the OS (chgdstpwd) or I can reset
the OS password if I can go in DST. However, now I don't have both. The
worst is that on the DST qsecofr user disable. Of course, I don't have any
user authourity with qsecofr equivalent!

Is there a way to go into the system without scratch install the system?

[René H. Hartman]

How about the DST 22222222 user? If that still has the default pwd you
should be able to use that to reset QSECOFR

--

"Andy Wong" <iseri...@gmail.com> schreef in bericht
news:dehffb$qvu$1...@reader01.singnet.com.sg...

[Rickie Wong]

I managed to login as 22222222, but no rights to reset qsecofr. :-(

"René H. Hartman" <so...@no-spam.org> wrote in message
news:430c7d1b$0$754$5fc...@dreader2.news.tiscali.nl...

[René H. Hartman]

Then it definitely looks you're out of luck. No chance of getting the
QSECOFR password from the original owner? There are ways to recover DST
device passwords, but if both QSECOFR profile passwords are unknown
you're in trouble. I always thought 22222222 could do it as well (never
used it), but I just checked, and, alas...
There may still be ways to do it through the front panel, modifying data
in memory, like in the old days, but if there are, they are
undocumented.
--

"Rickie Wong" <ricki...@hotmail.com> schreef in bericht
news:430c8787$1...@news.starhub.net.sg...

[Steve Richter]

why is the scratch install out of the question?

You can do a go save option 21 save the entire system. Then if you
have install cds you can scratch install from those cds. the password
will then be the default qsecofr qsecofr.

If you have a savsys from another system you can also do a scratch
install with that save tape. then when prompted for the dst password
the password should be the password that was saved on that tape.

not 100% sure about all of this :) but I think this is how it works.
The DST password for a scratch install is the one that is on the tape -
not the one on the system being installed onto.

-Steve

[René H. Hartman]

"Steve Richter" <Stephen...@gmail.com> schreef in bericht
news:1124908329.3...@g49g2000cwa.googlegroups.com...

Andy didn't state it was out of the question; he wants to avoid it.
He has no password to the system whatsoever, so he cannot do an Option21
save.
Restoring from another system's tape (or CDs) would invalidate all
license keys. IF he's got the paperwork: no problem.

IF he has an Opt21 tape for the system, he's in businness:
- Mount the tape, install the LIC from tape using option 2 (scratch the
system) and the OS. The OS comes with empty QSECOFR password first and
prompts for a password change-from-default later on. You end up with a
restored system and a signed on QSECOFR profile.
- AT THAT TIME CHANGE THE QSECOFR PROFILE's PASSWORD using CHGUSRPRF. If
you log off without doing this you're back where you started of, since
the change-from-default you made is overridden by the restored original
password (that you do not have). Also, do a CHGDSTPWD *DEFAULT.
- You then have access to the system and can do the Opt21 restore.
- Don't forget to create an extra *SECOFR OS and DST profile as a
backup.
It's a bit of work, but it can be done. BUT:... he does need to have an
Opt21 save tape from that system.

However, I'd try and get some access credentials from the previous owner
first.

[jse...@yahoo.co.nz]

Unless you can get one of those passwords, then it isn't possible to
reset them without a SLIP install.

You'll need to perform a D mode IPL and install the licensed internal
code, then install the operating system. After that is done, just
perform a manual IPL into DST where you can change the password.

Of course, after that you will need to reapply all your PTFs.

[munenew]

how did you resolve this, I am in a similar situation; no qsecofr password & DST Qsecofr locked with 22222222 & 11111111 having security *revoked

[CENTRINO]

IBM must have a collection backdoors, but they will never tell you about.

so:

Re-install OS.

I'm afraid that this is the unique "general public available solution".



"munenew" <mun...@gmail.com> escribió en el mensaje
news:k7ydnacq2vQWoMTO...@giganews.com...