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



Rod,

Which debugger are you using?

For your 2nd question, IBM assumes that you will use the default
source file naming convention for ILE COBOL with SQL. That is the
file named in the message, QCBLLESRC. If you want to avoid this
message, then keep at least your copy source in a file named
QCBLLESRC, or point your copy commands within the COBOL source to the
actual file that contains the copy books.

Jim

On Thu, Mar 25, 2010 at 4:15 PM, Rod Verity <rod_verity@xxxxxxxxxxxxxx> wrote:

We have just started using ILE for a few programs and I am obviously doing
something wrong in the compile of a SQLCBLLE program. I am using CRTSQLCBLI
to compile it.  It compiles ok but the debugger does not show any of the
contents of copybooks. I thought maybe the DBGVIEW(*SOURCE) would do that
but obviously not. Has anyone found a way of making the copy member visible
in the debugger?

A second question regarding ILE compiles is the message I keep getting:

 1544  MSGID: LNC0939  SEVERITY:  0  SEQNBR:  193149
      Message . . . . :   Copy member 'CCPARESPY' not found in default
source
        file QCBLLESRC, about to check source file QLBLSRC.

We don't have a QCBLLESRC, only QLBLSRC. Is there a way of forcing the
compiler to only look in QLBLSRC?

Thanks for your help,
Rod

Please consider the environment before printing this email.

This message, including any attached documents, is intended for the
addressees only. It may contain information that is confidential,
privileged and/or exempt from disclosure. No rights to privilege or
confidentiality have been waived. Any unauthorized use or disclosure is
prohibited. If you have received this message in error, please reply to the
sender by e-mail and delete or destroy all copies of this message.
______________________________________________________
Avant d'imprimer ce courriel, pensez à l'environnement.

Ce message, incluant tous les documents joints, est à l'intention des
destinataires visés seulement.  Il peut contenir des renseignements
confidentiels, protégés et/ou ne pouvant pas être divulgués.   Aucune
renonciation n'est faite quant à sa nature confidentielle et privilégiée.
Par conséquent, toute diffusion ou utilisation non autorisée est
strictement interdite.  Si vous avez reçu ce message par erreur, veuillez
en aviser immédiatement l'expéditeur par retour de courriel et en détruire
toutes les copies existantes.

--
This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing list
To post a message email: COBOL400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/cobol400-l.



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.