×
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.
Shouldn't GenericHandler actually be GENERICHANDLER as it appears on the
Exported defined symbols?
Thanks,
Tommy Holden
From: <Rick.Chevalier@xxxxxxxxxxxxxxx>
To: <rpg400-l@xxxxxxxxxxxx>
Date: 10/06/2010 11:31 AM
Subject: Unresolved reference - What am I missing?
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
I am trying to compile a simple RPG bound program. It has two prototypes,
one for the CEEHDLR API and the other for a handler procedure in a module
I created. It is not finding a reference for the handler procedure. This
is so basic but I don't see what is wrong. We moved to 6.1 over the
weekend but I doubt that has anything to do with it. What am I missing?
To module . . . . . . . . . : QBNBSYMR
To procedure . . . . . . . : QBNBSYMR__SignalUnresolvedReferences
Statement . . . . . . . . . : 8
Message . . . . : Definition not found for symbol 'GenericHandler'.
h Bnddir('RCHEVA1POC')
d GenericHandler pr
d Condition LikeDS(Condition_t)
d Token *
d ResultCode 10i 0
d NewCondition 12a
Rick Chevalier
IT Software Solutions - Loan Servicing
817-525-7178 (w)
________________________________
Privileged and Confidential. This e-mail, and any attachments there to, is
intended only for use by the addressee(s) named herein and may contain
privileged or confidential information. If you have received this e-mail
in error, please notify me immediately by a return e-mail and delete this
e-mail. You are hereby notified that any dissemination, distribution or
copying of this e-mail and/or any attachments thereto, is strictly
prohibited.
As an Amazon Associate we earn from qualifying purchases.
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.