SQL Stored Procedure Content Past Record Length of 80

[kellycookson]

I'm trying to code an IBM i Db2 SQL stored procedure using the Code for i extenstion in VS Code.

• I continually get a linter error message that says "Content past record length of 80."
• The actual record length for the line of code is always much less than 80 characters.
• Code for i won't let me save the source member because of these errors.

I can open, modify, and save the stored procedure in SEU. I can can also create the stored procedure without errors using a 5250 session. This seems like an issue with Code for i. Do I need to suppress the linter somehow? Is this a bug with the linter?

[kellycookson]

Resolved.

[sebjulliand]

Great!
Can you share how you solved it in case others have the same issue please @kellycookson ? Thanks 😊

[kellycookson]

Unfortunately, I can't. I don't know how it got resolved.

• AI agent Claude Sonnet 4.6 suggested that I create an RPGLINT.JSON file and set record length to 112. But this didn't have any impact (which makes sense as I was coding a SQL stored procedure).
• Despite seeing the Content past record length of 80 error that prevented me from saving changes using Code for i, I was able to open the stored procedure source member in SEU just fine and save it. I was also able to create ("compile") the stored procedure using a 5250 session with no errors. The problem seemed specifically with Code for i in VS Code.
• I closed the source member file and then restarted VS Code. That cleared the message that was preventing the source member file from being saved. But I have no idea why. (It will be very frustrating if a developer writes a lot of code, but then has to restart VS Code with unsaved changes because this message is preventing them from saving.)

Just to note, I'm using VS Code Insiders, which is usually just a little ahead of VS Code.