Re: CALLPRC issue "Definition not found for symbol"

[Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>]

The experts have already chimed in on RPG and auto-casing, but know that 
you're not alone in being confused.  Every time I have to create a new 
library of service programs, I go through the same stuff.  It's 
especially difficult for me because I'm a lazy, lazy man and I have a 
tendency to do this:

dcl-pr MYPGM extpgm end-pr;

That defines a prototype for a call to an external program MYPGM with no 
parameters.  It's a nice shortcut for calls to programs, but as soon as 
you start using procedures, you had better put the procedure name in 
your DCL-PR, and put it in quotes so that there's no confusion.  Well, 
less confusion, anyway.  :)


On 5/17/2018 2:34 PM, Dan 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?
>
> - Dan
>
> On Thu, May 17, 2018 at 3:17 PM, Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
> wrote:
>
> > Just for fun, Dan... when you do a DSPSRVPGM on CALIB/CA9800, and you
> > enter through the various screens, what are the procedure names on the
> > fifth screen (Procedure Exports, Display 5 of 10)?  Does
> > EmployeeAuthorizationStatus show up there as expected?
> >
> > I'm just wondering if your exported names somehow got upper-cased.  I
> > always have a bear of a time getting case right.