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



Because RPG uses a protype to get the actual name from the EXTPROC keyword..


And RPG by default uppercases everything...

In order to have truly mixed case procedure name, you need

dcl-pr MyProc extproc('MyProc');

or
dcl-pr MyProc extproc(*dclcase);


Your RPG program could use
MYPROC();
MyProc();
myproc();

It doesn't matter, since all the CALLP's are upper-cased and the compiler
ensures that MYPROC points to 'MyProc'.

Charles



On Thu, May 17, 2018 at 1:34 PM, Dan <dan27649@xxxxxxxxx> wrote:

Sonuvab****

All of my procedure names show up as uppercase in DSPSRVPGM
SRVPGM(CALIB/CA9800) DETAIL(*PROCEXP). I changed my CLLE program so that I
removed the single quotes surrounding the name, which effectively turns it
to uppercase, created the module and program as noted before, and I have a
compiled program that gives the results I expected.

The RPGLE programs that call this same EmployeeAuthorizationStatus
procedure don't care about the case. Why am I able to use mixed case in
the RPGLE call but not the CLLE call?



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.