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



On 10/23/2014 2:50 PM, Jon Paris wrote:
Two options I can think of.

1) Convert the code to RPG IV and where needed call the C library MI functions.

This is easier than it seems at first blush.

On Oct 23, 2014, at 2:33 PM, John Yeung wrote:

Hey folks, here's one you probably don't hear every day:

What are my options for compiling an RPG program that contains embedded MI code?

In my particular case, the RPG is RPG III or RPG/400, and it contains
what appear to be preprocessor directives #BEGIN and #END (the '#' is
in column 1), which delimit the MI code.

The comments at the top of the source indicate that ZMILIB must be in
the library list, and the program object created by the CRTRPGMI
command. As you may guess from the fact that I'm asking, these don't
exist anywhere on our current system, and I'm not having any luck
Googling these things.

I have some actual, honest to goodness MI programs that I use for
various housekeeping chores. No production level stuff; that would
drive the other developers in the group mad. If you have a situation
where the #BEGIN and #END bracket an entire MI program [1] then you
might want to scrap the RPG 'wrapper' and just compile the MI program as-is.

--buck

[1] A complete MI program has some DCL statements, almost certainly DCL
DD and DCL SPCPTR. It will also have some opcodes like MATPRATR. It'll
end with PEND and every line will terminate in a semicolon.

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.