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



Hi All,

Could someone please explain to me what the correct way would be to compile
the following ?

I have two modules. The first performs screen validations & then calls the
second module with a CALL opcode. The second module performs printing. Now
the two modules are bound into a program using CRTPGM cl command. A service
program containing two modules (one of which contains mupltiple procs
[NOMAIN] ) is also bound into the pgm at the time of CRTPGM. The problem
I'm sitting with is the point at which the first pgm calls the second, an
error occurs. It seems as if a program object is being sought. I tried
changing the CALL to a CALLB but then received a compilation error
(something about procedure pointer call).

What am I doing wrong here? Do I have to prototype/create a procedure form
the second module? Is there a correct way of doing what I'm currently
trying to achieve?

Any help would be appreciated.
 Incidentally, if there is no obvious error from my explanation and someone
would like the error messages, I'd be glad to give them.

Regards
John.


+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-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.