Where is compile listing?

[SteversJE]

I can't find the compile listing on the IBM box after the object is created. Where does it go? I sometimes compile something so I know where to look when I see "MCH0603 unmonitored by UXINVOICE at statement 0000292300." Is there an alternative to the compile listing?

[thomprl]

If you are compiling inside of VSCode. The compile listing usually shows on the terminal tab at the bottom of the screen. I'm pretty sure VSCode converts the spool file to text and then loads it into the terminal tab and deletes the spool file. Then you can use the problems tab to see any errors.

[SteversJE]

I understood that part of it. This just addresses the immediate use of the compile listing for the compile-edit-debug cycle, not my longer term (months) use of keeping it around for production troubleshooting.

[sebjulliand]

Since every command executed by Code for i are run into a shell, the output doesn't go into a spooled file but directly in the shell's standard output. That output is logged in the terminal used to run the action (as @thomprl said).

[thomprl]

Thanks, wasn't sure about the magic behind the scenes.

[SteversJE]

(I can't tell if I'm replying to sebjulliand or thomprl; I'll find out after I post.)

Thanks sebjulliand. I guess the implication is I can't change the behavior of the extension to keep the compile listing, but I can get my desired outcome by creating additional commands to submit the compiles to batch. (Which I already tested and does work fine.)

[chrjorgensen]

@SteversJE Instead of keeping the spoolfile from the compile, you should compile it into the program object using DBGVIEW *ALL or *LISTING.

That way you always have the compile listing at hand, it follows the program into production.

You see it when you STRDBG against the program.

[SteversJE]

Thanks. I'm looking at that *LIST approach. I just hope the line is easy to find and doesn't require scrolling and perusing.

(Okay, I'm going off on a tangent here. Thread can be done.)