×
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.
-----Original Message-----
From: Dan [mailto:dan27649@xxxxxxxxx]
Sent: Thursday, May 17, 2018 2:02 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: CALLPRC issue "Definition not found for symbol"
This is my first go at using a CLLE program to call a procedure from a service program.
The EmployeeAuthorizationStatus procedure is in service program CA9800, using that exact case. The binder source has:
Export Symbol( EmployeeAuthorizationStatus )
This procedure is currently being used in other RPGLE programs.
Using CRTCLMOD, I created the module just fine. My CRTPGM command:
CRTPGM PGM(DANLIB/CA8560CT$2) MODULE(DANLIB/CA8560CT$2)
BNDSRVPGM((CALIB/CA9800 *DEFER)) BNDDIR(CALIB/CABNDDIR) DETAIL(*EXTENDED) ... generates the following messages:
CPD5D1D: *SRVPGM object QZDMMDTA in library QSOC not found.
CPD5D02: Definition not found for symbol 'EmployeeAuthorizationStatus'.
(Cause: No definition was found for reference EmployeeAuthorizationStatus in *MODULE object CA8560CT$2 in library DBALEBULK2. The definition either does not exist or is not of the same data or procedure type as the reference. <-- I HAVE NO IDEA WHAT THIS MEANS.)
CPF3C50: Program CA8560CT$2 not created.
I have no idea where QZDMMDTA comes from. In another thread, Buck has suggested that I should treat this as a red herring. That same thread discussed the CPD5D02: Definition not found for symbol error, but that was for an RPGLE program.
Ideas?
- Dan
As an Amazon Associate we earn from qualifying purchases.
This thread ...
Re: CALLPRC issue "Definition not found for symbol", (continued)
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.