× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: Reference code B90037F0
  • From: Leif Svalgaard <l.svalgaard@xxxxxxxxxxxxx>
  • Date: Mon, 22 Nov 1999 16:39:46 -0600


> Does anybody know what Reference code B90037F0 at IPL time means?
> 
> I don't know personally, but have some reference books here that give me
> the
> following details:
> 
> B9XX XXXX codes indicate OS/400 machine checks
> 37F0 is the start of OS400
> 
> Description: The start OS/400 process is not able to monitor for the never
> event.
> Service recovery action: IPL the system.  If the problem continues to
> occur,
> take a main storage dump, Install OS/400 again.
> 
        [Leif Svalgaard]  Thanks, I get the error when I (for testing
purposes) change
        QSECURITY from 40 t0 50, then IPL. After manual re-IPL, the error
goes
        away. When I later go back to 40, no error, then back up to 50, the
        B900 37F0 error comes back (once). I was wondering if I was doing
        something wrong, but I'm not very concerned because - as I said -
        the error goes away. It is just a pain to do manual IPL.

+---
| This is the MI Programmers Mailing List!
| To submit a new message, send your mail to MI400@midrange.com.
| To subscribe to this list send email to MI400-SUB@midrange.com.
| To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dr2@cssas400.com
+---


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-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.