|
Hi Mark,
yes it's weird - especially errors in the linkage stage (debug views, missing service programs, etc) are poorly reported for SQLRPGLE. The compilation fails but you have nothing in the error list.
In this case always check the compiler listings - those errors are only reported there.
HTH
Daniel
Von meinem iPhone gesendet
Am 02.10.2024 um 21:42 schrieb mlazarus<mlazarus@xxxxxxxxxxxx>:
I figured it out. There was a conflict in the command string that RDi had stored. I had changed the command default on the system to In the RDi compile string, once I changed DBGVIEW(*SOURCE) to DBGVIEW(*NONE) it started working.
I found it odd that RDi didn't report an error, though.
-mark
On 10/2/2024 2:59 PM, Buck Calabro wrote:--
On 10/2/2024 2:45 PM, mlazarus wrote:Looks good.
Hi Buck,
I have:
CRTSQLRPGI OBJ(&O/&N) SRCFILE(&L/&F) SRCMBR(&N) REPLACE(&R) OPTION(*EVENTF) DBGVIEW(*SOURCE)
CRTBNDRPG PGM(&O/&N) SRCFILE(&L/&F) SRCMBR(&N) REPLACE(&R) OPTION(*EVENTF) DBGVIEW(*SOURCE)
CRTRPGMOD MODULE(&O/&N) SRCFILE(&L/&F) SRCMBR(&N) REPLACE(&R) OPTION(*EVENTF) DBGVIEW(*SOURCE)
It still doesn't seem to be working. Is it getting confused by the multiple possibilities for commands to run? Can I specify that a specific one will be the default?
My experience is that the last one used is the default for that source type. So... try Compile> Compile> (pick the one you want). That /should/ set the default for SQLRPGLE. After that, Ctrl-Shift-C should work as you want.
This is the Rational Developer for IBM i (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/wdsci-l.
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.