Create individual compile actions

[ghost]

Hi,

I created a new compile action called build that triggers context sensitive compile processes.
This buil process works as designed, If i get a compile error I see the result in the problems view.
But if the compile and create falils the behavior is, that compile errors are displayd but the final message box that says compile successful or failed always display compile successful.

My question is: what triggers the message unsuccessful creation of a programm?

Any help would be appreciated.

[sebjulliand]

Hi @KPL-PGMR ,
an action will be successful if the command(s) it runs return an exit code 0. If the exit code is anything but 0, then the action will be treated as unsuccessful.

Check your build process and if it's a script (for example), make sure it returns an exit code that reflects the build outcome.

[ghost]

Hi @sebjulliand ,
thanks for the quick reply. What do you mean by exit code? Ist a return variable in the command, that ist being fed by the cpp, or a message returning a severity greater than zero?

[sebjulliand]

When you call a command in a shell, any command, it always return a exit code (or exit status) telling the shell if it was successful or not. 0 means OK, anything else means something bad happened.

You can check it for yourself by opening a PASE terminal from Code for i and running these commands:

This will make echo print 0:

system "DSPLIB QGPL"
echo $?

This will make echo print 255:

system "DSPLIB QGLOPL"
echo $?

The special variable $? is the exit code of the last command run in the shell. So when the second system "DSPLIB..." call failed, its exit status was 255.

So, depending on how your specific build command or script ends, if it always return an exit code 0, the action will always be considered a success.

You can check what's your action exit code by looking at the Code for IBM i output after it's been run.

Every command run by Code for IBM i is logged here, with its output and exit code. You should be able to locate your action call in there and check its exit code.

If it's always 0 regardless of the actual outcome, then change your command so it doesn't end successfully (make it send an escape message with severity 30 for example).

[ghost]

Hi @sebjulliand ,
thank's a lot for detailing. Now I understood.