|
Jim this is rather curious as I have seen 1 and heard of another 2 V5R1 400's all with similar problems just in the last 3 days and the common denominator seems to be ops console. In one case IPL-ing using CDs has been of no help. The console ends up reporting that QSECOFR is disabled and the other profiles (if you are lucky enough to be able to continue) wind up with an SRC of B900 3005. All of these involve manual IPL's getting utterly stuck on the SST password issues. Ops console seems to choke after one profile is disabled - I'm not totally sure if you can then try another profile it almost seems to "remember" the last one was disabled (I hate ascribing human behaviour to computers :). The only profile that seems to consistently work is the 22222222 one. QSECOFR is a real problem.... I am not deeply involved in the processes so I can't be totally sure that the SST passwords haven't been fouled up, but different 3 systems all with the same apparent problem seems a little far fetched. Some of the work-around instructions involved (wait for it) advice to reboot the ops console at various points and see if that fixed anything. This is a bit of a continuing saga here as we reloaded the OS for one system and recovered some stuff we were waiting, but as this is a test/experimentation system we are persevering with trying to get hold of the problem - with IBMs assistance. I'd be interested to here how you get on with your experience. regards Evan Harris >Our AS/400 has gone done and I am home for the day. I get a call this >morning, they can't get into the console to bring up the system. > >They/We/I have managed to disable QSECOFR, QSRV, 11111111 and 22222222 and >we can't get in to bring the console up. > >This is a very irriating thing IBM did, because it seems that every time the >AS/400 goes down I'm not in and all the accounts get disabled. > >How am I supposed to bring this system up? > >Tried Manual mode and selecting 21 and enter... and am asked for user name >and password! > >Please help, our AS/400 is down and people are getting irritated (including >me). > >Thanks! > >Regards, > >Jim Langston >_______________________________________________ >This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list >To post a message email: MIDRANGE-L@midrange.com >To subscribe, unsubscribe, or change list options, >visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l >or email: MIDRANGE-L-request@midrange.com >Before posting, please take a moment to review the archives >at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com 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.