More likely someone changed the signon display for QCTL (or QBASE -
whatever the controlling subsystem is in system value QCTLSBSD) and put it
in a library (QGPL ?) that doesn't yet exist when you are trying to reload
the system, or a library that was deleted before you IPL'd, or in QSYS but
they didn't use a SAVSYS containing it when trying to reload.
IPL in manual mode, select option to change system at IPL, work with
system values, change controlling subsystem to one you hopefully haven't
altered the signon display for (if QCTLSBSD is QCTL try QBASE, and vice
versa), and continue IPL.  When system is up fix problem with signon
display in subsystem description of what used to be your controlling
subsystem, then change QCTLSBSD sysval back and do a normal IPL.
Tip - if you make a fancy signon display file, put it in QINTER, QPGMR,
etc. but leave the controlling subsystem (therfore system console) at
IBM's default of QDSIGNON in QSYS.  If you must change the signon display
for controlling subsystem, put it in QSYS and do a SAVSYS, so you have it
available if you have to reload OS/400.


Marc Rauzier <>
Sent by:
2002/01/16 05:40
Please respond to midrange-l

        To:     sswaim <>
        Subject:        Re: SRC  B900 3C30

Le mer. 16 janv. 2002 11:23:30, sswaim écrivait:

> I have a 9402 -200 with this src code.  I can not find a reference
> to it. Does anyone know what this means.

Sign-on file could not be opened (or found) by the controlling
Basically, the QSYS/QDSIGNON (by default) display file is corrupted or

> Scott Swaim

Cordialement/Best regards
Marc Rauzier

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.