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


  1.  Home
  2. MIDRANGE-L
  3. April 2010

Re: compile option*NOUNREF

David FOXWELL wrote:
<<SNIP>>

Here's what I did.
DSPOBJD of modules.

DSPFD member list of all QRPGLESRC

SELECT ODOBNM FROM dspobjdmod
join dspfdMbrLst on mlname=odobnm
WHERE MLSEU2 ='SQLRPGLE'

I realise of course that this method may give undesired results, as I'm assuming that there is a relation to a module name and a member name in a QRPGLESRC file. The two files in my sql
statement are actually independent of each other.


FWiW: To more accurately list all modules which were compiled with embedded SQL:

DSPOBJD *ALL/*ALL *MODULE *FULL
OUTPUT(*OUTFILE) OUTFILE(ODMODULE)
CREATE FUNCTION ModHasSQL (LIB varchar(10), MOD varchar(10))...
RETURNS CHAR /* '1'=True\'0'=False */...
SELECT ODLBNM, ODOBNM FROM ODMODULE
WHERE ODOBAT='RPGLE' AND ModHasSQL(ODLBNM, ODOBNM) = '1'

The function would reflect the result of the QBNRMODI Retrieve Module Information API call, for its ability to retrieve any DB2 SQL attributes from the *MODULE identified by qualified name as input.

Regards, Chuck

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.