QBASE, QCTL, and QINTER Associated SGNDSPF is Damaged

The IBM System i products system was not accessible. Therefore, the system was powered off. A manual IPL was started. The Controlling Subsystem was changed to QBASE (if we got a session after selecting IPL the system from IPL or Install the system menu). The IPL continued until it finished. However, it was still not possible to get a sign-on screen. TCP/IP was still working.

This failure occurs because the sign-on session associated with QBASE, QCTL, and QINTER is damaged (by default, QDSIGNON). In this situation, it is typically suggested that the IBM OS/400 or IBM i5/OS Base Option be installed again. However, there is another way to recover that is less time-consuming.

Do the following:

Step 1: From a Microsoft Windows DOS command line, start an FTP session to the system and run the following FTP commands:

FTP <System i TCP/IP Address)
user ID (QSECOFR or any user with *ALLOBJ authority)
password
quo rcmd ENDSBS SBS(QINTER) OPTION(*IMMED)

Note: If the system has a system value of QPWDLVL = 0/1, run one of the following commands:

o	quo rcmd CRTDSPF FILE(QGPL/IBMFIX) SRCFILE(QGPL/QDDSSRC) SRCMBR(QDSIGNON) REPLACE(*YES)
o	quo rcmd CRTDSPF FILE(QGPL/IBMFIX) SRCFILE(QSYS/QAWTSSRC) SRCMBR(QDSIGNON) REPLACE(*YES)

If the system has a system value of QPWDLVL = 2/3, run the following command:

quo rcmd CRTDSPF FILE(QGPL/IBMFIX) SRCFILE(QSYS/QAWTSSRC) SRCMBR(QDSIGNON2) REPLACE(*YES)

Replace QGPL as destination library for anything else.

For all situations, run the remaining commands:

quo rcmd CHGSBSD SBSD(QINTER) SGNDSPF(QGPL/IBMFIX)
quo rcmd STRSBS SBSD(QINTER)
quit

Step 2: Start a Telnet session to the System i server, and make the necessary fixes (for example, change QCTL associated SGNDSPF file).

The system is now ready for a normal IPL.