I never saw any responses to this. I'm thinking surely someone in this forum has used CRTSQLRPGI with IFS source in RDi. What am I doing wrong?

[cid:image001.png@01D8612F.E0BCDAE0]<https://nelnetinc.com/nds/>
John R Weirich
IT Software Architect - iSeries
Nelnet Diversified Services<https://nelnetinc.com/nds/>
John.Weirich@xxxxxxxxxx<mailto:John.Weirich@xxxxxxxxxx>
o: x28399 | m: 979.219.9262
[Nelnet Diversified Services | Facebook]<https://www.facebook.com/nelnetcareers>
[Nelnet Diversified Services | Twitter]<https://twitter.com/NelnetCareers>
[Nelnet Diversified Services | LinkedIn]<https://www.linkedin.com/company/nelnet-diversified-services/>


From: Weirich, John
Sent: Wednesday, March 9, 2022 4:06 PM
To: wdsci-l@xxxxxxxxxxxxxxxxxx
Subject: RDi 9.6.0.11 - IFS SQLRPGLE program compile errors not showing in error listing

Greetings, maintainers and experts of RDi,

I have an RPG source file on the IFS with SQLRPGLE extension.
I have a custom compile command set up in RDi to compile it:

CRTSQLRPGI OBJ(&O/&FNR) SRCSTMF('&FP') CLOSQLCSR(*ENDMOD) OPTION(*EVENTF) DBGVIEW(*SOURCE) TGTRLS(*CURRENT) RPGPPOPT(*LVL2) COMPILEOPT('TGTCCSID(*JOB)') REPLACE(&R)

I am set to not compile in batch.

When running the compile, errors are listed in the EVFEVENT source member, but they do not display in the error listing in RDi.
I can right click on the member and choose option 'SHOW IN ERROR LIST' and the errors will display.

Doing the same with a CLLE program does not have the same issue - errors DO display in the error listing for CLLE programs when compiled from an IFS source file.

I believe the problem has to do with this statement in the following link:

https://www.ibm.com/docs/en/rdfi/9.6.0?topic=compiling-working-compile-commands

"For IFS non-batch commands, the compiler will check for PGM() or MODULE() parameters in the command string to determine the name of the generated events file."

Unfortunately CRTSQLRPGI has an OBJ() parameter, but no PGM() or MODULE() parameter.

The link also states the following:

"The parameters can be specified within a comment at the end of the command. It is necessary to specify these parameters in the command you define in the dialog so that the Error List view is populated if the command is not successful."

I tried modifying the command with CL formatted comment at the end as follows, to no effect. The errors are still not pulled into the error listing:
OBJ(&O/&FNR) SRCSTMF('&FP') CLOSQLCSR(*ENDMOD) OPTION(*EVENTF) DBGVIEW(*SOURCE) TGTRLS(*CURRENT) RPGPPOPT(*LVL2) COMPILEOPT('TGTCCSID(*JOB)') REPLACE(&R) /*PGM(&O/&N)*/

Is there another way to get the errors to show in the error listing?

Thanks,

[cid:image001.png@01D8612F.E0BCDAE0]<https://nelnetinc.com/nds/>
John R Weirich
IT Software Architect - iSeries
Nelnet Diversified Services<https://nelnetinc.com/nds/>
John.Weirich@xxxxxxxxxx<mailto:John.Weirich@xxxxxxxxxx>
o: x28399 | m: 979.219.9262
[Nelnet Diversified Services | Facebook]<https://www.facebook.com/nelnetcareers>
[Nelnet Diversified Services | Twitter]<https://twitter.com/NelnetCareers>
[Nelnet Diversified Services | LinkedIn]<https://www.linkedin.com/company/nelnet-diversified-services/>


----------------------------------------------------------------------
The information contained in this message is confidential proprietary property of Nelnet, Inc. and its affiliated companies (Nelnet) and is intended for the recipient only. Any reproduction, forwarding, or copying without the express permission of Nelnet is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to this e-mail.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 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.