× 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: MI - Compiler.
  • From: "Leif Svalgaard" <leif@xxxxxxxx>
  • Date: Tue, 3 Jul 2001 22:12:52 -0500

From: Hall, Philip <phall@spss.com>

> But that's what I said, the MI statements in the RPG array. You may have a
> PEND; now, but at one point there wasn't, if I remember correctly, because
I
> got the same error. In fact, take the PEND; off of one of your MI programs,
> compile and QPRCRTPG should cough and die...
>
> If you look closely at the error message Chris posted, it *is* the RPG
> program that creates your QPRCRTPG front-end that's being executed, in
> particular, it's at the point where it calls QPRCRTPG with the array of MI
> statements to actually create the front-end from those statements;
>
> Error RPG0202 caused program CRTMIPGM to stop.   <===== why CRTMIPGM ?

We need to hear from Chris. I'm sure Chris has the PEND; version.
But does the name of the program that is stopped not look a bit
odd? I would have expected CRTMICMP or some such.



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

Replies:

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.