× 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: ILE CL calling RPG procedure help.
  • From: Scott Klement <klemscot@xxxxxxxxxxxx>
  • Date: Thu, 24 May 2001 19:33:17 -0500 (CDT)


Hi John,

Actually, I think when you put the procedure name in single quotes, such 
as PRC('DELETEMBR') it needs to be caps.  If you don't, such as 
PROC(DeleteMbr) then CL will convert it to caps for you before trying to
use it.

Or am I confused?  (Sorry... I dont use CL very much... it's too limited)


On Thu, 24 May 2001, John Taylor wrote:

> Scott,
> 
> I haven't run across this necessity for uppercase names on CALLPRC. The
> following example (from a real pgm) compiles fine and resolves to the
> correct procedure:
> 
>     CallPrc    WrkwSlsOrd
> 
> As you've stated, the RPG compiler will export the proc name in capitalized
> form, so I suspect that the CLLE compiler is forcing everything to uppercase
> on our behalf. This works at least as far back as V4R2.
> 
> 
> John Taylor
> Canada
> 
> ----- Original Message -----
> From: "Scott Klement" <klemscot@klements.com>
> To: <RPG400-L@midrange.com>
> Sent: Thursday, May 24, 2001 16:20
> Subject: Re: ILE CL calling RPG procedure help.
> 
> 
> >
> > The RPG compiler (annoyingly, in my opinion) will capitalize all the
> > letters in all the procedure/module/variable names as its compiling
> > the program.
> >
> > Therefore, if you want to call a procedure written in RPG, you need
> > to put the name in CAPS.  Like so:
> >
> > CALLPRC PRC('DELETEMBR')
> >
> > You also need to make sure that the procedure is exported from the
> > service program. To do this, you need to:
> >     1) specify the EXPORT keyword on your P-spec in the RPG program.
> >     2) If binding with EXPORT(*SRCFILE) you need to have specified
> >           your procedure with EXPORT SYMBOL(DELETEMBR) in the binding
> >           language source.
> >     3) If binding with EXPORT(*ALL), you should be okay, as long as
> >           you fulfilled condition #1.
> >
> > If this doesn't help, you'll need to post the relevant code...
> >
> 
k

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