DST login
Arturs Brandejs
where would it be???
L'uomo mascherato
Arturs Brandejs <jru...@home.com> wrote in message
MUyq4.237148$5r2.6...@tor-nn1.netcom.ca...
> What is this DST login? is it supplied by IBM when you first get the
as400.
> where would it be???
>
>
you will request fo login
Type QSECOFR and password 2222222222.
Arturs Brandejs
type in 2222222222??? as the password?
L'uomo mascherato wrote in message <88ej8j$9ps$1...@news.IT.net>...
L'uomo mascherato
Arturs Brandejs
profile, can i still go into DST using QSECOFR/22222222 or QSECOFR/99999999
or QSECOFR/QSECOFR????
thanx people, i really appreciate this.
Obelix wrote in message ...
>On Sun, 16 Feb 3900 12:08:48, "Arturs Brandejs" <jru...@home.com>
>wrote:
>
>> what???
>> type in 2222222222??? as the password?
>Yes or just qsecofr/qsecofr...
>
>Obelix
Obelix
Scott Lindstrom
Brandejs" <jru...@home.com> wrote:
>what if i am accessing the DST menu because i have disabled the
QSECOFR
>profile, can i still go into DST using QSECOFR/22222222 or
QSECOFR/99999999
>or QSECOFR/QSECOFR????
>
yes - these are seperate. DST is precisely how you go in to
reset the regular QSECOFR password should you have no other way
to do it. (Don't remember the DST menu option).
* Sent from RemarQ http://www.remarq.com The Internet's Discussion Network *
The fastest and easiest way to search and participate in Usenet - Free!
Kevin
Environment, then option 11 and option 4 to reset system default password.
This with reset the password for QSECOFR to QSECOFR/QSECOFR.
HTH
Kevin
"Scott Lindstrom" <scott.linds...@zenith.com.invalid> wrote in
message news:1bc9bc22...@usw-ex0103-024.remarq.com...
Ugo Gagliardelli
Arturs Brandejs wrote:
>
> what if i am accessing the DST menu because i have disabled the QSECOFR
> profile, can i still go into DST using QSECOFR/22222222 or QSECOFR/99999999
> or QSECOFR/QSECOFR????
Nay! The DST (Dedicated Service Tool) is a separate environment that
goes up just after micro-code. You have three classes of users: QSECOFR
let's the super-user, 2222222222 and 1111111111 that are respectively
less capable users. To reset the passwords for the next IPL for the
OS/400 user profiles you must access DST as QSECOFR. You will have the
option to default all the password of the user profiles supplied by IBM
within OS/400.
Obviously you will be succesfull only if nobody changed the DST QSECOFR
password!
The above procedure will only reset the passwords, the status of the
user profiles will remain unchanged, so if you have the QSECOFR user
profile in the status of *DISABLED you'll continue to not be able to
logon as QSECOFR unless you'll try to logon from the device defined as
system console. To know which device, try the command DSPSYSVAL
QCONSOLE, it will show the name of such a device.
Arturs Brandejs
since i need to reset the QSECOFR user profile:
- i need to manually IPL
- go intothe DST menu as QSECOFR (login QSECOFR, pass QSECOFR ??)
- reset all profiles i need to reset, including QSECOFR
- get to the system console and log in regularly as QSECOFR
- change password
Ugo Gagliardelli wrote in message <38AAEFB9...@teamsw.it>...
Ugo Gagliardelli
Arturs Brandejs wrote:
>
> just to clarify:
>
> since i need to reset the QSECOFR user profile:
> - i need to manually IPL
yes, if your system has a key-lock you need the key to successfully
manual IPL.
> - go intothe DST menu as QSECOFR (login QSECOFR, pass QSECOFR ??)
yes, on the very first menu chose "work with DST Environment", on the
next choose "change DST user profiles" then chose "reset system-default
password"
> - reset all profiles i need to reset, including QSECOFR
you'll have the only option to default OS profiles, I'm not sure it will
default all the profiles, but the QSECOFR.
> - get to the system console and log in regularly as QSECOFR
yes, verify with DSPUSRPRF USRPRF(QSECOFR) that the status is *ENABLED,
if not CHGUSRPRF USRPRF(QSECOFR) STATUS(*ENABLED)
> - change password
and don't forget it! :-)
The above procedure is shown on "basic security guide" (I guess), and in
"AS/400 Sercice Function" in chapter 1, sub-chapter "DST Options". You
should have this book as it is shipped in the hardware shipping group of
the AS/400 system.
ugo
Ugo Gagliardelli
Arturs Brandejs wrote:
>
> isn't that a little unsecure? the fact taht you can loginto qsecofr at the
> dst menu with the password qsecofr or 2222222222 or 1111111111
I don't think so. When IBM deliver AS/400 all password are set to a
default, is up to you change them.
Hei
enter to option 21, the console will then switch to DST menu.
(This method is found in the book "Security - Basic")
Ugo Gagliardelli <u...@teamsw.it> wrote in message
news:38AB093A...@teamsw.it...
Marc Rauzier
%FFq4.237235$5r2.6...@tor-nn1.netcom.ca...
> isn't that a little unsecure? the fact taht you can loginto qsecofr at
the
> dst menu with the password qsecofr or 2222222222 or 1111111111
Hi Arturs
You can change the DST passwords in the DST menu. If you lost them you
can reset them with QSECOFR (or another *ALLOBJ and *SECADM special
authority user profile (not sure about the special authority)) with a
command I cannot remember, something like CHGDSTPWD.
Of course, you will have some problems if you lost the QSECOFR password
*and* the DST password :-))))
In this case, you have to restore one of the two. But I do not know how
to restore the DST one, maybe by restoring the SLIC.
> Ugo Gagliardelli wrote in message <38AB093A...@teamsw.it>...
> >
> >
> >Arturs Brandejs wrote:
> >>
> >> just to clarify:
> >>
> >> since i need to reset the QSECOFR user profile:
> >> - i need to manually IPL
> >yes, if your system has a key-lock you need the key to successfully
> >manual IPL.
> >> - go intothe DST menu as QSECOFR (login QSECOFR, pass QSECOFR ??)
> >yes, on the very first menu chose "work with DST Environment", on the
> >next choose "change DST user profiles" then chose "reset
system-default
> >password"
> >> - reset all profiles i need to reset, including QSECOFR
> >you'll have the only option to default OS profiles, I'm not sure it
will
> >default all the profiles, but the QSECOFR.
> >> - get to the system console and log in regularly as QSECOFR
> >yes, verify with DSPUSRPRF USRPRF(QSECOFR) that the status is
*ENABLED,
> >if not CHGUSRPRF USRPRF(QSECOFR) STATUS(*ENABLED)
> >> - change password
> >and don't forget it! :-)
[cut]
--
Cordialement
Best regards
Marc Rauzier
Ugo Gagliardelli
Marc Rauzier wrote:
...
>
> In this case, you have to restore one of the two. But I do not know how
> to restore the DST one, maybe by restoring the SLIC.
You have the chace to defautl the DST password with the command
CHGDSTPWD PASSWORD(*DEFAULT) but... to enter this command you must be
QSECOFR!
host
you can only change dst password with user QSECOFR.
"Restriction: This command is shipped with public *USE authority, but you
must be signed on as QSECOFR to use it. You cannot authorize other users
to the command."
(from: CL Reference Version 4 Document Number SC41-5722-02)
herbert
Marc Rauzier schrieb in Nachricht
<5EWq4.259$C17.1...@nnrp2.proxad.net>...
>Arturs Brandejs <jru...@home.com> a écrit dans le message :
>%FFq4.237235$5r2.6...@tor-nn1.netcom.ca...
>> isn't that a little unsecure? the fact taht you can loginto qsecofr at
>the
>> dst menu with the password qsecofr or 2222222222 or 1111111111
>
>Hi Arturs
>
>You can change the DST passwords in the DST menu. If you lost them you
>can reset them with QSECOFR (or another *ALLOBJ and *SECADM special
>authority user profile (not sure about the special authority)) with a
>command I cannot remember, something like CHGDSTPWD.
>
>Of course, you will have some problems if you lost the QSECOFR password
>*and* the DST password :-))))
>
>In this case, you have to restore one of the two. But I do not know how
>to restore the DST one, maybe by restoring the SLIC.
>
Marc Rauzier
38ADB397...@teamsw.it...
>
>
> Marc Rauzier wrote:>
> > You can change the DST passwords in the DST menu. If you lost them
you
> > can reset them with QSECOFR (or another *ALLOBJ and *SECADM special
> > authority user profile (not sure about the special authority)) with
a
> > command I cannot remember, something like CHGDSTPWD.
> command.
> ugo
OK, OK, I am wrong. But, I was not sure ....