Compile messages / results from custom compile CLLE program not displayed in VS Code

[YD-123456]

Description

We have implemented a custom CLLE compile program
compile.txt
we use to compile our IFS-based source files.
The compile itself runs successfully, but the result messages are not displayed in VS Code.

It seems that VS Code does not show the actual compile errors or messages produced by our CLLE program.

Question

How do we need to modify our compile program so that compile errors and messages are properly displayed in VS Code?

Additional context

We use a similar compile procedure in RDi, and there it works fine — RDi correctly displays the compile results and error messages.

We decided to store all our source code on the IFS instead of using traditional source files.
This allows us to use more descriptive filenames than the 10-character system object limit.

Our naming convention is:

PGMNAME_pgmDescription.sourceType

Where:

• PGMNAME – IBM i system program name (max 10 chars)
• pgmDescription – Descriptive text explaining the program’s purpose
• sourceType – Source type, such as sqlrpgle, rpgle, etc.

Examples

• ORDRPG_HandleCustomerOrders.sqlrpgle
• INVUPDATE_RecalculateStockLevels.rpgle

I will attach our CLLE compile program source to this issue for review.

Description

We have implemented a custom CLLE compile program e to compile our IFS-based source files.
The compile itself runs successfully, but the result messages are not displayed in VS Code.

It seems that VS Code does not show the actual compile errors or messages produced by our CLLE program.

Question

How do we need to modify our compile program so that compile errors and messages are properly displayed in VS Code?

Additional context

We use a similar compile procedure in RDi, and there it works fine — RDi correctly displays the compile results and error messages.

We decided to store all our source code on the IFS instead of using traditional source files.
This allows us to use more descriptive filenames than the 10-character system object limit.

Our naming convention is:

PGMNAME_pgmDescription.sourceType

Where:

• PGMNAME – IBM i system program name (max 10 chars)
• pgmDescription – Descriptive text explaining the program’s purpose
• sourceType – Source type, such as sqlrpgle, rpgle, etc.

Examples

• ORDRPG_HandleCustomerOrders.sqlrpgle
• INVUPDATE_RecalculateStockLevels.rpgle

I will attach our CLLE compile program source to this issue for review.

[sebjulliand]

Hi @YD-123456 ,
could you share the definition of the action you defined in Code for IBM i to run your compile command?
There must be something missing in there.
Thanks!

[YD-123456]

No, I receive only following message

[sebjulliand]

What's the error?

[YD-123456]

When the compilation completes successfully:
compilationSuccess.txt

When the compilation fails:
compilationFail.txt

[sebjulliand]

I think I know what's wrong.

Here:

Fetching errors for [MYLIB]/TESTPGM_THISISATEST.
Error: Failed fetching table: CPD0074:  Value 'TESTPGM_TH' for FROMFILE exceeds 10 characters.

Since the name of the compiled object is derived from the source file name based on a naming convention of yours, Code for i fails to retrieve the member from the EVFEVENT file, because that member is named after the compiled object.

But since this pull request has been merged, there should be a solution: #2926

Code for i can now find EVFEVENT members to retrieve based on the joblog. It will look for messages following this pattern:

EVFEVENT: <object>

or

EVFEVENT: <library>,<object>

So I assume that if your custom compile command is able to write this kind of message into the joblog, Code for i will be able to pick up the correct location and retrieve the errors.

Once you've done that, remove the /* *EVENTF SRCMBR(&NAME) */part so it doesn't look for something that doesn't exist.

Note: you'll have to use the latest pre-release (2.18.2) of Code for i for this to work.

[YD-123456]

Sorry! Thanks a lot!!! It works!

[sebjulliand]

Perfect! Thanks for the feedback 👍🏻