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



If you have a product design that you want your functionality built into all the programs, like a license key validation tool that you do not want overridden by having one interjected between the calling program and the service program.

-Matt


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dan
Sent: Thursday, May 17, 2018 1:39 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: CALLPRC issue "Definition not found for symbol"

I think I got my answer with the mixed case naming of the procedure. But, for reference, CABNDDIR has only the CA9800 *SRVPGM object in it. I have never considered putting *MODULE objects into a binding directory.
(Actually, I didn't know you could, and I'm not sure why one would.)

- Dan

On Thu, May 17, 2018 at 3:27 PM, Mark S Waterbury < mark.s.waterbury@xxxxxxxxxxxxx> wrote:

Hi, Dan,

Issue:
DSPBNDDIR BNDDIR(CALIB/CABNDDIR)
or
DSPBNDDIR BNDDIR(CALIB/CABNDDIR) OUTPUT(*PRINT)

and study the results, and examine the list of objects in this binding
directory, to see if someone has somehow added both *MODULEs and
*SRVPGMs to that binding directory ... (HINT: bad idea)

The message is referring to a *MODULE object. In general, it is a "bad
practice" to put *MODULEs into a binding directory.

Instead, what you want to do is to bind *MODULEs into a *SRVPGM and then
add the *SRVPGM into the binding directory. And, never mix both *MODULEs
and *SRVPGMs in the same binding directory. ("There be dragons
here.") This is very likely the root cause of this error.

If you issue CRTSRVPGM with naming that *MODULE CA8560CT$2 explicitly,
it would likely dynamically bind to *SRVPGM object QZDMMDTA, and that
would resolve the issue(s).

_Summary_
You should always explicitly name *MODULEs on a CRTPGM or CRTSRVPGM or
UPDPGM or UPDSRVPGM command, never add them to any *BNDDIR. Place "shared"
modules into a single *SRVPGM, and bind to that, either by naming that
*SRVPGM explicity on the CRTPGM or UPDPGM command, or by using a
binding directory.

Also, I highly recommend the use of a "make" or "build" tool like Alan
Campin's COMPILE command, available at
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.think400.dk_do
wnloa&d=DwICAg&c=2S-2xx8Cum_thMfWs-kOOHQTwolPvSZ4PFLhr1wDDGs&r=wgq2KO1
Tl8HswJht2RKpmz7qvL2YDU_M-VhnRH6r43I&m=i9dCG9ZsTecTufmaYT8XSURFc5-whG7
w84az91-FwaI&s=0UDCPVSadGp5rz8L9Pys2Up0jNuBu6pgj7pb677it8o&e=
ds.htm -- this allows you to store the create commands, such as
CRTxxxMOD, followed by the CRTSRVPGM or CRTPGM commands, directly
within the source code, as comments. This way, you never lose those "make"
instructions, and it makes all subsequent maintenance easier, since
you just prompt the COMPILE command and point it at the source. The
COMPILE command is also designed to be easily integrated with WDSCi or RDi.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.midrange.com_mailman_listinfo_midrange-2Dl&d=DwICAg&c=2S-2xx8Cum_thMfWs-kOOHQTwolPvSZ4PFLhr1wDDGs&r=wgq2KO1Tl8HswJht2RKpmz7qvL2YDU_M-VhnRH6r43I&m=i9dCG9ZsTecTufmaYT8XSURFc5-whG7w84az91-FwaI&s=CgvNzl8VQhy6xCc1INtreJppXzDbBBiYAFDfNS7gAtA&e=
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at https://urldefense.proofpoint.com/v2/url?u=https-3A__archive.midrange.com_midrange-2Dl&d=DwICAg&c=2S-2xx8Cum_thMfWs-kOOHQTwolPvSZ4PFLhr1wDDGs&r=wgq2KO1Tl8HswJht2RKpmz7qvL2YDU_M-VhnRH6r43I&m=i9dCG9ZsTecTufmaYT8XSURFc5-whG7w84az91-FwaI&s=qVPEL9pfGLPWps9LXB2ekzxBAdc_OhdMHFtvD2zZwig&e=.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://urldefense.proofpoint.com/v2/url?u=http-3A__amzn.to_2dEadiD&d=DwICAg&c=2S-2xx8Cum_thMfWs-kOOHQTwolPvSZ4PFLhr1wDDGs&r=wgq2KO1Tl8HswJht2RKpmz7qvL2YDU_M-VhnRH6r43I&m=i9dCG9ZsTecTufmaYT8XSURFc5-whG7w84az91-FwaI&s=zUkL_sSvawJhR-rTIQs8y_7h_VyGzW1P6SEjVogXQQ4&e=

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.