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



From the ILE RPG Reference:

The control-specification statements, identified by an H in position 6,
provide
information about generating and running programs. However, there are
three
different ways in which this information can be provided to the compiler
and the
compiler searches for this information in the following order:
1. A control specification included in your source
2. A data area named RPGLEHSPEC in *LIBL
3. A data area named DFTLEHSPEC in QRPGLE

I am guessing one of those data areas exist and specify that binding
directory.

Scott

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James Lampert
Sent: Thursday, November 29, 2012 3:46 PM
To: Midrange Systems Technical Discussion
Subject: Weird message on bind failure

This is now a moot point, since I've dealt with the bind failure in
question, but:

Earlier, I was having a bind failure, on a customer box, from not having
the appropriate binding directory listed in an H-spec or in the
CRTBNDRPG parameters.

The weird part was this joblog message:

Message . . . . : *SRVPGM object QNNINLDS in library QNOTES not
found.

There's no such service program anywhere on the box, and the program
doesn't even attempt to call anything from a service program of that
name. Neither did it (at the time, until I added a reference to the one
it actually needed) explicitly reference any binding directory
whatsoever.

Just now, I looked it up in a spooled joblog, and found the second-level
text:

Cause . . . . . : *SRVPGM object QNNINLDS in library QNOTES was
specified in
binding directory QUSAPIBD in library *LIBL, but was not found for
binding.
Recovery . . . : Contact your application provider or service

representative.


What's this QUSAPIBD binding directory, that it would (evidently) get
implicitly invoked, leading to an attempt to link to a service program
that doesn't exist?

--
JHHL
--
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: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.