×
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.
(cross-posted to midrange-l from wdsci-l, as the problem doesn't seem to
be WDSC related).
Okay, so it looks like the binding process can find the module based on
this:
Yes I have the library in my list which is ulrmods that both modules are
complied in DACOPYCL and PNCOPYM. Also I do have the EXPORT keyword at the
begining of my procedure(PNCOPYM).
ALso this the command I using to compile:
SBMJOB CMD(CRTPGM PGM(ULRMODS/DACOPYCL) MODULE(*LIBL/DACOPYCL
*LIBL/PNCOPYM) ACTGRP(*NEW)) JOB(*JOBD) JOBD(ULRICH) OUTQ(*USRPRF)
INLLIBL(*JOBD)
Given the error message from your original post
> Definition not found for symbol 'PNCOPYM'.
> Cause . . . . . : No definition was found for reference PNCOPYM in
> *MODULE
> object DACOPYCL in library ULRMODS. The definition either does not
> exist
> or
> is not of the same data or procedure type as the reference.
I suspect that Charles is on the right track. Is your procedure really
called PNCOPYM? It probably shouldn't be if 'H nomain' is specified.
What does the PI look like? What does the CALLPRC command from the CL
look like?
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.
midrange.com
