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



This sounds real similar to a message I got a couple of months ago.

If I remember correctly, what the problem turned out to be was I had a NOMAIN 
module that contained a procedure that had the same name as the module.  In 
other words, the module was something like ProcA and the procedure was ProcA.  
It works fine if the module is not a NOMAIN module.  Pretty screwy - they could 
definitely have used a better message.

HTH,

Todd Kidwell (Netstar)
AS/400 System Administrator
(313) 224-0578

>>> Leslie Russell <leslier@datrek.com> 07/12/00 10:53AM >>>
I was just trying to compile an RPG module and this is the error message 
I got.
The module I am trying to compile has been ok until just a few minutes 
ago. 
I looked at the compiler listing and found that I had left the prototype 
for the newest procedure out of my prototype /copy member, but I have 
done that before and it didn't generate this message. 
Anybody know what gives?    


                     Additional Message Information                       
  
                                                                          
      
 Message ID . . . . . . :   RNS9311       Severity . . . . . . . :   50   
      
 Message type . . . . . :   Information                                   
      
 Date sent  . . . . . . :   07/12/00      Time sent  . . . . . . :   
09:49:32   
                                                                          
      
 Message . . . . :   Compilation stopped. Internal failure occurred. 
Error code 
   is  1.                                                                 
      
 Cause . . . . . :   The possible error codes are:                        
      
     1  - Failure occurred in the compiler front end.                     
      
     2  - Failure occurred while  exiting the command.                    
      
     3  - Failure occurred in the back end.                               
      
     4  - Failure occurred in the command.                                
      
     5  - Memory allocation error occurred in the command.                
      
     12 - Memory allocation error occurred in the front end.              
      
     13 - Read error occurred in the compiler front end.                  
      
     14 - Write error occurred in the compiler front end.                 
      
 Recovery  . . . :   Call your service representative, giving the error 
code    
 id.
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com 
+---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.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.