Even though the system is set to do a normal, unattended mode IPL, it will stop at DST if the Service Tools security profile (qsecofr) still has it's password set to the shipped default value.

Unattended IPL stops at DST (ibm.com)

Hopefully none of you experienced this since you've all changed the SST password for QSECOFR.

Even though the system is set to do a normal, unattended mode IPL, it will stop at DST if the Service Tools security profile (qsecofr) still has it's password set to the shipped default value.

Unattended IPL stops at DST (ibm.com)

Hopefully none of you experienced this since you've all changed the SST password for QSECOFR.

I have a system in this exact state .  When trying to connect via client solutions LAN console, the usual box asking for credentials

pops up, once typed user and password (qsecofr/QSECOFR) the password expired message appears and you get prompted for a new passord,

once entered the new password you obtain a nice USER DISABLED message.  Are we loked out of the system ?

Even though the system is set to do a normal, unattended mode IPL, it will stop at DST if the Service Tools security profile (qsecofr) still has it's password set to the shipped default value.

Unattended IPL stops at DST (ibm.com)

Hopefully none of you experienced this since you've all changed the SST password for QSECOFR.

Pino - not sure what OS version you are at.....I know the above post was for 7.5 in particular. But...I wonder if one of these 2 docs might be of some help to you

Resetting OS QSECOFR Password Using DST - Version 5 and Higher

QSECOFR Password for Service Tools is Disabled

I have a system in this exact state .  When trying to connect via client solutions LAN console, the usual box asking for credentials

pops up, once typed user and password (qsecofr/QSECOFR) the password expired message appears and you get prompted for a new passord,

once entered the new password you obtain a nice USER DISABLED message.  Are we loked out of the system ?

Even though the system is set to do a normal, unattended mode IPL, it will stop at DST if the Service Tools security profile (qsecofr) still has it's password set to the shipped default value.

Unattended IPL stops at DST (ibm.com)

Hopefully none of you experienced this since you've all changed the SST password for QSECOFR.

Thank you Rich but there is no way to get the system to complete the ipl, so no commands can be imparted.

The system is V7R5 and stops at DST as described in the document referenced above. Nothing is sais about it in the document

but from what I see, there is a further restriction in V7R5 that prevents you even from connecting to the console in case DST user is disabled.

Someone knows about it ? It seems the only way out is restoring from scratch or , maybe, attaching a HMC console....

Pino - not sure what OS version you are at.....I know the above post was for 7.5 in particular. But...I wonder if one of these 2 docs might be of some help to you

Resetting OS QSECOFR Password Using DST - Version 5 and Higher

QSECOFR Password for Service Tools is Disabled

I have a system in this exact state .  When trying to connect via client solutions LAN console, the usual box asking for credentials

pops up, once typed user and password (qsecofr/QSECOFR) the password expired message appears and you get prompted for a new passord,

once entered the new password you obtain a nice USER DISABLED message.  Are we loked out of the system ?

Even though the system is set to do a normal, unattended mode IPL, it will stop at DST if the Service Tools security profile (qsecofr) still has it's password set to the shipped default value.

Unattended IPL stops at DST (ibm.com)

Hopefully none of you experienced this since you've all changed the SST password for QSECOFR.

Pino - Hope you've called IBM by now about the issue you are having. I provided the docs/links hoping that you could have an HMC connected to the system and attempt one of the processes outlined in one of those links etc. I did find that in the MTU for 7.5  the following instructions etc

Plan for a Attended IPL - Sign-on required at DST
During an attended (manual) IPL, the user will be required to sign in to DST. Any valid service tool ID with
the service tool privileges listed below is required:
• Dedicated Service Tools (DST) environment
• Operating system initial program load (IPL)
8 IBM i: Memo to Users
• Install
QSECOFR is the suggested service tool ID to be used. It is important that the current QSECOFR ID
password is known. If the QSECOFR ID password is not known, reset the password before starting the
LIC install, using the XPF command CHGDSTPWD PASSWORD(*DEFAULT). If a valid service tool ID is not
known, a scratch install may be necessary.
Important: The 11111111 (eight 1's) ID and the 22222222 (eight 2's) service tools user IDs are removed
on IBM i 7.5. If your current connection uses these Service Tool User IDs, the install upgrade requires
entering and using the QSECOFR ID (which has the default password QSECOFR).
Recovery: If the Console Information Status screen is shown with the message Service Tool User
ID does not exist or password incorrect, then press F12 which will display the DST Sign On
screen, where the ID QSECOFR and the password QSECOFR can be entered.
The Service Tool QSECOFR ID is shipped as expired but does not need to be changed during the D-mode
IPL for a new install. On the following A-mode IPL (if this is a new install), the password needs to be
changed before the partition can be IPLed or the OS installed. If this is a release upgrade, the current
partition QSECOFR ID password is required and the above recovery may be needed. On an upgrade, the
recovery can use any valid Service Tool ID and password.
Important: During an attended IPL of the system, if no console has been specified previously, two extra
screens are displayed to confirm the setting of the console type:
1. A screen that requires pressing F10 to accept your current console type
2. A screen that shows that a value did not previously exist (a zero is present for the old value) and the
new value is shown
Pressing Enter exits and sets the console type automatically.
The IPL continues to the "IPL or Install the System" screen.
Having no console specified previously is most likely to occur during the installation of a new partition, but
might happen on your first attended IPL of IBM i 7.5. For example, when a console value of zero is found
during the A-mode IPL during an upgrade or install (following the restore of Licensed Internal Code).

here's the link for the above, perhaps it can be of help to you (or others)

IBM i: Memo to Users

Thank you Rich but there is no way to get the system to complete the ipl, so no commands can be imparted.

The system is V7R5 and stops at DST as described in the document referenced above. Nothing is sais about it in the document

but from what I see, there is a further restriction in V7R5 that prevents you even from connecting to the console in case DST user is disabled.

Someone knows about it ? It seems the only way out is restoring from scratch or , maybe, attaching a HMC console....

Pino - not sure what OS version you are at.....I know the above post was for 7.5 in particular. But...I wonder if one of these 2 docs might be of some help to you

Resetting OS QSECOFR Password Using DST - Version 5 and Higher

QSECOFR Password for Service Tools is Disabled

I have a system in this exact state .  When trying to connect via client solutions LAN console, the usual box asking for credentials

pops up, once typed user and password (qsecofr/QSECOFR) the password expired message appears and you get prompted for a new passord,

once entered the new password you obtain a nice USER DISABLED message.  Are we loked out of the system ?

Even though the system is set to do a normal, unattended mode IPL, it will stop at DST if the Service Tools security profile (qsecofr) still has it's password set to the shipped default value.

Unattended IPL stops at DST (ibm.com)

Hopefully none of you experienced this since you've all changed the SST password for QSECOFR.

Thank you Rich but there is no way to get the system to complete the ipl, so no commands can be imparted.

The system is V7R5 and stops at DST as described in the document referenced above. Nothing is sais about it in the document

but from what I see, there is a further restriction in V7R5 that prevents you even from connecting to the console in case DST user is disabled.

Someone knows about it ? It seems the only way out is restoring from scratch or , maybe, attaching a HMC console....

Pino - not sure what OS version you are at.....I know the above post was for 7.5 in particular. But...I wonder if one of these 2 docs might be of some help to you

Resetting OS QSECOFR Password Using DST - Version 5 and Higher

QSECOFR Password for Service Tools is Disabled

I have a system in this exact state .  When trying to connect via client solutions LAN console, the usual box asking for credentials

pops up, once typed user and password (qsecofr/QSECOFR) the password expired message appears and you get prompted for a new passord,

once entered the new password you obtain a nice USER DISABLED message.  Are we loked out of the system ?

Even though the system is set to do a normal, unattended mode IPL, it will stop at DST if the Service Tools security profile (qsecofr) still has it's password set to the shipped default value.

Unattended IPL stops at DST (ibm.com)

Hopefully none of you experienced this since you've all changed the SST password for QSECOFR.