RPG Compilation Errors not showing in local file

[LuGe00]

I compiled a file from local repository which got errors, these errors are not shown in the editor. If i do the same from object browser then it shows these errors. How to get the errors also shown in local compilation ?

[LuGe00]

@sebjulliand Hey tell me if you need more context to answer this properly ?

[sebjulliand]

No, I just need to find some time to make a proper answer 😉

[LuGe00]

Alright, ill be patient, sorry :)

[sebjulliand]

No worries.
Actually, to give you a good answer, can you confirm you're using one of the custom action you created recently ? Are they QShell/Pase actions now ?

[LuGe00]

@sebjulliand

This is one of the local actions.json actions:
{
"name": "RPGLE Programm erstellen",
"command": "/QOpenSys/usr/bin/sh /home/scripts/build-ibmi.sh rpgle-pgm &FULLPATH &RELATIVEPATH &PARENT &NAME WWSTEST ",
"deployFirst": true,
"environment": "qsh",
"extensions": [
"RPGLE"
]
}

I have several but they are all built alike only the parameters calling the build-ibmi.sh are different

#!/QOpenSys/usr/bin/sh
set -eu

MODE="$1"
FULLPATH="$2"
RELATIVEPATH="$3"
PARENT="$4"
NAME="$5"
CURLIB="$6"
COMPILE_SRCFILE="${7:-}"

TOPDIR="$(basename "$(dirname "$(dirname "$FULLPATH")")")"
TOPLIB="$(printf '%s' "$TOPDIR" | tr '[:lower:]' '[:upper:]')"
SRCFILE="$(printf '%s' "$PARENT" | tr '[:lower:]' '[:upper:]')"
NAMEU="$(printf '%s' "$NAME" | tr '[:lower:]' '[:upper:]')"
COPY_SRCFILE="$(printf '%s' "$PARENT" | tr '[:lower:]' '[:upper:]')"

if [ -n "$COMPILE_SRCFILE" ]; then
SRCFILE="$(printf '%s' "$COMPILE_SRCFILE" | tr '[:lower:]' '[:upper:]')"
fi

copy_member() {
system "CPYFRMSTMF FROMSTMF('${FULLPATH}') TOMBR('/QSYS.LIB/${TOPLIB}.LIB/${COPY_SRCFILE}.FILE/${NAMEU}.MBR') MBROPT(*REPLACE) CVTDTA(*AUTO) DBFCCSID(273)"
}

case "$MODE" in
rpgle-pgm)
system "CRTBNDRPG PGM(${CURLIB}/${NAMEU}) SRCSTMF('${RELATIVEPATH}') OPTION(*EVENTF) DBGVIEW(*SOURCE) TGTCCSID(*JOB)"
copy_member
;;
*)
echo "Unknown mode: $MODE" >&2
exit 2
;;
esac

So as a example when i call to compile the program the parameters are filled like this:
Running Action: RPGLE Programm erstellen (8:23:37 AM)
Working directory: /home/user/builds/AS400
Commands:
/QOpenSys/usr/bin/sh /home/scripts/build-ibmi.sh rpgle-pgm /home/user/builds/AS400/wwssrc/QRPGLESRC/program.rpgle wwssrc/QRPGLESRC/program.rpgle QRPGLESRC Program WWSTEST

[LuGe00]

Hey @sebjulliand, i fixed it right now by creating local actions where the environment is ILE and they look like this:

{
"name": "CREATE RPGLE Programm",
"command": "CRTBNDRPG PGM(WWSTEST/&NAME) SRCSTMF('&RELATIVEPATH') OPTION(*EVENTF) DBGVIEW(*SOURCE) TGTCCSID(*JOB)\nQSH CMD('/QOpenSys/usr/bin/sh /scripts/build-ibmi.sh update-source-member &FULLPATH &PARENT &NAME')",
"deployFirst": true,
"environment": "ile",
"extensions": [
"RPGLE"
]
}

, so they get correct error and warning display in local file and the sh script is only for updating source member inside pdm.

I don't know if you want to further look into this because this solution would be enough for us

[sebjulliand]

Ok, I finally have the time to make answer 😄

The process that looks up for the EVFEVENT file corresponding to the object being built will look for the definition of the command being run:

• One of the command must include *EVENTF
• The name of te object must be a value of one of these parameters: PNLGRP, OBJ, PGM, MODULE, FILE, MENU

Hence why what you did here made it work.

But when you're calling a shell script, you won't use these parameters and this process won't pick up any EVENTF information.

So the other way is to have your build command to print the location of the EVFEVENT file that should be picked up. As long as it appears in the job log, you'll be fine.

The expected format is as follow (for the moment):

: EVFEVENT: LIBRARY_NAME,OBJECT_NAME

So in your case, that would be :

: EVFEVENT: WWSTEST,&NAME

I digged around a bit and for now, these lines need to be echoed into the error output.
So adding this line in your action or in your script (which may be a better place since the script knows the actual library and object name) will do the trick - assuming you're going to put it in your script, it should be like this:

>&2 echo ": EVFEVENT: ${CURLIB}/${NAMEU}"

And just adding this in the script should be enough to have the extension load the EVFEVENT content and report the errors.

Hope this helps!