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



Terry,

My understanding of CRTBNDCL and CALLPRC relationship is that it is allowed
as long as the procedure called by the CALLPRC is located in a service
program the CRTBNDCL binder can locate.  Which procedures can CRTBNDCL
binder locate?  Well, it seems only ones located in IBM's service programs,
since there is no parm on CRTBNDCL to specify a user service program.  
I suppose one could ADDBNDDIRE to some system binding directory and ensure
that it's found that way, but that's not something I'd like to do.

I assume that on your CRTPGM you specify both your CLLE and your RPGLE
modules, so obviously the CRTPGM binder can locate your RPGLE procedure
easily.

Short answer, stick with CRTPGM when binding multiple modules or user
created service programs.

Elvis

-----Original Message-----
Subject: [SPAM] CALLPRC & CRTBNDCL

Greetings List,
I am trying to call an RPGLE procedure from a CLLE program by using the
CALLPRC command. When I try to compile the CLLE with the CRTBNDCL
(option 14 in PDM) the compile abends saying that it cannot find the
definition for the procedure. If I compile the CLLE as a module (option
15 in PDM) or use the CRTPGM command it compiles normally. Is there some
compile trick to be able to use the CALLPRC with the CRTBNDCL command?


Thanks,

Terry



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.