linter issues appear after pgm is complete

[NextPage66]

I had completed this code last week. I opened it up this week to make a minor change. There were no issues when i opened the source today but as soon as i entered the change on line 60 i see all these issues pop up. Now i can close and reopen the source and the issues are still there. I removed my changes and saved it but the issues are still there.
This happened last week on another source file and I ended up reformatting it to make the linter happy.
I don't understand what is going on with this?
It does not like the lines starting in certain positions. I thought *FREE was FREE!! Should not be worried with indentation issues.
And why did it change its mind from one day to another?

The only extensions i have enabled are Code for i, Code for IBM i Walkthroughs and IBMi Languages.

VS Code version: Code 1.106.3 (microsoft/vscode@bf9252a, 2025-11-25T22:28:18.024Z)
OS version: Windows_NT x64 10.0.19045

[richardm90]

@NextPage66 , are you able to replicate the problem? If so are you able to provide a copy of the source file and the steps to replicate. Then I should be able to replicate myself and debug the problem.

[NextPage66]

I have not tried to create any other **free source from scratch. I just don't understand the linter. One time it likes the indentation and the next time it doesn't. I will send screen shots of some messages that make no sense.
One main question here is: Does **free have a columnar format? I have written in many other languages that do not require columnar formatting.
As I work in this source it appears the linter is enforcing columnar formatting. It seems inconsistent and i can't figure it out.

What is the best way to provide you a copy of this source?

[NextPage66]

[richardm90]

@NextPage66, if you're happy to provide the source that is causing the problem (i.e. ARO803R.SQLRPLE) then you can either right-click on that member in the object browser and select download or simply copy and paste the entire contents of the source member (when open in VS Code) and save that to a local file. Could you also do the same for your RPGLINT.JSON.

As an example I've done this for a source member of mine called WRKCUS.rpgle. Note that I had to add the extension of .txt as .rpgle is not a supported file tile type. You can either drop the local source file into the GitHub comment box or paste it.

WRKCUS.rpgle.txt

[NextPage66]

Can I send the text file to you directly? From: Richard Moulton ***@***.***> Sent: Wednesday, December 10, 2025 10:49 AM To: codefori/vscode-rpgle ***@***.***> Cc: Duane Sanders ***@***.***>; Mention ***@***.***> Subject: Re: [codefori/vscode-rpgle] linter issues appear after pgm is complete (Issue #474) [Image removed by sender.]richardm90 left a comment (codefori/vscode-rpgle#474)<#474 (comment)> @NextPage66<https://github.com/NextPage66>, if you're happy to provide the source that is causing the problem (i.e. ARO803R.SQLRPLE) then you can either right-click on that member in the object browser and select download or simply copy and paste the entire contents of the source member (when open in VS Code) and save that to a local file. Could you also do the same for your RPGLINT.JSON. As an example I've done this for a source member of mine called WRKCUS.rpgle. Note that I had to add the extension of .txt as .rpgle is not a supported file tile type. You can either drop the local source file into the GitHub comment box or paste it. WRKCUS.rpgle.txt<https://github.com/user-attachments/files/24084163/WRKCUS.rpgle.txt> — Reply to this email directly, view it on GitHub<#474 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BEV6P7MJPZFXAA5ETBZQS4D4BBFIPAVCNFSM6AAAAACNXDXU6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMMZYGAZTAMJXGQ>. You are receiving this because you were mentioned.Message ID: ***@***.***> Notice: This email and any files transmitted within it may contain privileged, confidential, and or proprietary information intended solely for the use of the individual or entity to whom they are addressed. To prevent the disclosure of sensitive information this message should be treated with the appropriate level of security. If you are not the intended recipient or person responsible for delivering it to the intended recipient, please notify the sender via email and delete the original message immediately. You are hereby advised that any disclosure, copying or distribution of the contents of this information is prohibited. Aromatique accepts no liability for any loss or damage resulting from the transmission of this email. Thank you.

[richardm90]

@NextPage66, absolutely, you can send the file(s) to me at richard@rmsoftwareservices.co.uk.

Basically all I'd like to do is replicate your particular scenario so I can debug and understand the problem so I only need the minimal file(s) possible to replicate. My suspicion is that the problem is the same as the one I am currently working to fix as part of PR #466.

[chrjorgensen]

@NextPage66 If you don't want the RPG linter to consider indentation, you can remove the line containing "indent: 2" from your RPGLINT configuration.

Like all other free format programming languages, it's best practice to align the source code in some way, to enhance readability. The compiler don't care, but your colleagues may care. So enforcing some kind of rule for indentation is quite common. But as said, you can turn it off if you want.

[NextPage66]

Yes I very much agree on the readability. However, my version of indentation and readability do not require specific columns. I would like to turn this version off. How do I do that? Also, I don’t remember the CL pgms having this issue. Does it have a linter? From: Christian Jorgensen ***@***.***> Sent: Friday, December 12, 2025 6:27 AM To: codefori/vscode-rpgle ***@***.***> Cc: Duane Sanders ***@***.***>; Mention ***@***.***> Subject: Re: [codefori/vscode-rpgle] linter issues appear after pgm is complete (Issue #474) [Image removed by sender.]chrjorgensen left a comment (codefori/vscode-rpgle#474)<#474 (comment)> @NextPage66<https://github.com/NextPage66> If you don't want the RPG linter to consider indentation, you can remove the line containing "indent: 2" from your RPGLINT configuration. Like all other free format programming languages, it's best practice to align the source code in some way, to enhance readability. The compiler don't care, but your colleagues may care. So enforcing some kind of rule for indentation is quite common. But as said, you can turn it off if you want. — Reply to this email directly, view it on GitHub<#474 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BEV6P7N2DSD643REBV3DOWT4BKYAXAVCNFSM6AAAAACNXDXU6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMNBWGI4DKNRYGM>. You are receiving this because you were mentioned.Message ID: ***@***.***> Notice: This email and any files transmitted within it may contain privileged, confidential, and or proprietary information intended solely for the use of the individual or entity to whom they are addressed. To prevent the disclosure of sensitive information this message should be treated with the appropriate level of security. If you are not the intended recipient or person responsible for delivering it to the intended recipient, please notify the sender via email and delete the original message immediately. You are hereby advised that any disclosure, copying or distribution of the contents of this information is prohibited. Aromatique accepts no liability for any loss or damage resulting from the transmission of this email. Thank you.

[NextPage66]

I understand. Let me know if this helps you. From: Richard Moulton ***@***.***> Sent: Friday, December 12, 2025 3:04 AM To: codefori/vscode-rpgle ***@***.***> Cc: Duane Sanders ***@***.***>; Mention ***@***.***> Subject: Re: [codefori/vscode-rpgle] linter issues appear after pgm is complete (Issue #474) [Image removed by sender.]richardm90 left a comment (codefori/vscode-rpgle#474)<#474 (comment)> @NextPage66<https://github.com/NextPage66>, absolutely, you can send the file(s) to me at ***@***.******@***.***>. Basically all I'd like to do is replicate your particular scenario so I can debug and understand the problem so I only need the minimal file(s) possible to replicate. My suspicion is that the problem is the same as the one I am currently working to fix as part of PR #466<#466>. — Reply to this email directly, view it on GitHub<#474 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BEV6P7LFJRWVUJPZWUF23HL4BKAGFAVCNFSM6AAAAACNXDXU6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMNBVGU3TANZTGU>. You are receiving this because you were mentioned.Message ID: ***@***.***> Notice: This email and any files transmitted within it may contain privileged, confidential, and or proprietary information intended solely for the use of the individual or entity to whom they are addressed. To prevent the disclosure of sensitive information this message should be treated with the appropriate level of security. If you are not the intended recipient or person responsible for delivering it to the intended recipient, please notify the sender via email and delete the original message immediately. You are hereby advised that any disclosure, copying or distribution of the contents of this information is prohibited. Aromatique accepts no liability for any loss or damage resulting from the transmission of this email. Thank you. **FREE ctl-opt dftactgrp(*no) actgrp(*caller) option(*nodebugio:*srcstmt); dcl-ds barloc qualified; bloc char(9) pos(1); blpre char(1) pos(1) inz('L'); blwhs char(2) pos(2); blloc char(6) pos(4); end-ds; dcl-ds inrr EXTNAME('INVRKLBL'); end-ds; // *ENTRY PARMS dcl-pi *n ; #prtr char(10) ; #whs char(3) ; #frloc char(6) ; #toloc char(6) ; #pError ind; end-pi ; dcl-s #loc char(6); dcl-s lblnam char(8) inz('INVLB3'); dcl-s lbldev char(10); dcl-s lblqty packed(4:0) inz(1); dcl-s demand char(1) inz('N'); dcl-s perset packed(4:0) inz(1); dcl-s across packed(2:0) inz(1); dcl-pr Z4XI1024 extpgm ; parm1 char(8); //lblnam parm2 packed(2:0); //across parm3 char(10); //lbldev parm4 packed(4:0); //lblqty parm5 char(1); //demand parm6 char(17); //inrr parm7 packed(4:0); //perset end-pr ; // set printer from screen lbldev = #prtr; // reset error flag #pError=*off; exec sql set option commit=*none, datfmt=*iso; // Build workfile exec sql delete from aro803f; exec sql insert into aro803f ( select wloc from ilml01 where wwhs=:#whs and wloc between :#frloc and :#toloc and wloc <>' ' order by REGEXP_SUBSTR(wloc, '[A-Z]+'),CAST(REGEXP_SUBSTR(wloc, '[0-9]+') AS INTEGER)); // Declare cursor exec sql declare csr1 cursor for select wloc from aro803f; // Open cursor exec sql open csr1; sqlstt='00000'; // Fetch loop exec sql fetch next from csr1 into :#loc; // Test for no results if sqlstt<>'00000' and %subst(sqlstt:1:2)<>'01'; #pError=*on; exec sql close csr1; *inlr=*on; return; endif; Dow sqlstt='00000' or %subst(sqlstt:1:2)='01'; prtlbl(); exec sql fetch next from csr1 into :#loc; Enddo; // Close cursor exec sql close csr1; // close out Location Labels spoolfile and end pgm lblqty = 0; demand = 'Y'; prtlbl(); *inlr = *on; // ************************************************************** // * PRINT LOCATION LABEL // ************************************************************** dcl-proc prtlbl; //*--------------------------------------------------------------------------------- //* Data structure . . . . . . : INRR //* External format . . . . . : INRR : LXUSRF/INVRKLBL //* Format text . . . . . . . : MERGED DATA AREA //*--------------------------------------------------------------------------------- // INRWHS 2A WHS // INRLOC 6A LOC // INRBC 9A BARCODE barloc.blwhs = #whs; barloc.blloc = #loc; //* LOAD MERGED DATA AREA (INRR) inrwhs = #whs; inrloc = #loc; inrbc = barloc; Z4XI1024(lblnam : across : lbldev : lblqty : demand : inrr : perset); End-Proc; // ************************************************************* // ** PARM NOTES: // **------------------------------------------------------------------ // ** LBLQTY PERSET // ** If your label has an INCREMENTING #: // ** -The "LBLQTY" becomes the number of "SETS" of labels. // ** -The "PERSET" field becomes the number of labels Per Set. // ** // ** If your label DOES NOT HAVE AN INCREMENTING #: // ** -Z-ADD label quantity to "LBLQTY" field. // ** -Z-ADD 1 to "PERSET" field. // ** // ** >> FOR EXAMPLE: You may want two sets of labels, each set // ** >> containing five labels(1 of 5, 2 of 5,.....) // ** >> Z-ADD 2 LBLQTY Z-ADD 5 PERSET // **------------------------------------------------------------------ // ** DEMAND // ** "D" Close the spool file but leave the program open. // ** Labels print IMMEDIATELY. // ** "Y" Close program, as a result spool file closes. // ** Labels print IMMEDIATELY. // ** "N" Leave spool file open and program open. // ** LABELS ARE ACCUMULATED IN SPOOL FILE // **------------------------------------------------------------------ // ** LBLNAM // ** This is the name of the label you wish to print. // **------------------------------------------------------------------ // ** LBLACR // ** Number of labels across the form. // **------------------------------------------------------------------ // ** MRGDTA // ** Data structure(above) containing variable data to be printed. // **------------------------------------------------------------------ // ** LBLDEV // ** Name of "OUTQ" (e.g...P1, P2, QPRINT) // ** This entry WILL NOT RE-DIRECT the output, it is used by the // ** label print program to determine how the data should be sent // ** to the printer. // **==================================================================

[richardm90]

@NextPage66 , sorry I think I misunderstood your issue. If you're happy with the indentation in your source member then the best option is to turn the indentation option off in the linter configuration. When you're working with source physical files the linter picks its configuration up from a member called RPGLINT.JSON in source file VSCODE in the library you're working in. Bear in mind that this linter configuration is specific to the library so others might be using that same configuration file.

Here's a copy of VSCODE/RPGLINT.JSON I have in one of my libraries - yours might look slightly different.

{
  "indent": 2,
  "UppercaseConstants": true,
  "IncorrectVariableCase": true,
  "NoGlobalSubroutines": true,
  "DirectiveCase": "lower",
  "CopybookDirective": "include",
  "NoUnreferenced": true,
  "SpecificCasing":[
      {"operation": "*BIF","expected": "*lower"},
      {"operation": "*DECLARE", "expected": "*lower"}
   ]
}

To turn off the indentation check simply remove the "indent": 2, line and save the member.

Note I tried the linter with the source you provided and got the same indentation warnings you were showing.

I then right-clicked in the source editor area and selected the Format Document option, which then automatically sorted out the indentation for me.

If you've got any questions on this then let me know.

There is a section in the docs on the linter, which you may find interesting.

https://codefori.github.io/docs/extensions/rpgle/linter/

[NextPage66]

Hey Richardm90, You didn’t misunderstand. Sorry if I am jumping all over the place. This environment is still new to us. We use it in a very simplified manner to get away from SEU. That’s it. My original issue is still bothering me, but I have to move on and not dwell on it. I didn’t see any way to recreate what it did. It was ok with my code…no errors or messages...I saved it and opened it after a few days and the linter displayed all these issues. If you see the print screens, you can still see some inconsistencies. One comment line is flagged but another just like it is not. That may be an issue you can look into. But as far as the Linter goes, I have removed that line for indentation and made other changes to get us past these issues. Thanks for the help. We probably need to go through a VS CODE class but there are so many out there and they all have something different to say. Not sure who knows what they are talking about. From: Richard Moulton ***@***.***> Sent: Saturday, December 13, 2025 2:50 AM To: codefori/vscode-rpgle ***@***.***> Cc: Duane Sanders ***@***.***>; Mention ***@***.***> Subject: Re: [codefori/vscode-rpgle] linter issues appear after pgm is complete (Issue #474) [Image removed by sender.]richardm90 left a comment (codefori/vscode-rpgle#474)<#474 (comment)> @NextPage66<https://github.com/NextPage66> , sorry I think I misunderstood your issue. If you're happy with the indentation in your source member then the best option is to turn the indentation option off in the linter configuration. When you're working with source physical files the linter picks its configuration up from a member called RPGLINT.JSON in source file VSCODE in the library you're working in. Bear in mind that this linter configuration is specific to the library so others might be using that same configuration file. Here's a copy of VSCODE/RPGLINT.JSON I have in one of my libraries - yours might look slightly different. { "indent": 2, "UppercaseConstants": true, "IncorrectVariableCase": true, "NoGlobalSubroutines": true, "DirectiveCase": "lower", "CopybookDirective": "include", "NoUnreferenced": true, "SpecificCasing":[ {"operation": "*BIF","expected": "*lower"}, {"operation": "*DECLARE", "expected": "*lower"} ] } To turn off the indentation check simply remove the "indent": 2, line and save the member. Note I tried the linter with the source you provided and got the same indentation warnings you were showing. image.png (view on web)<https://github.com/user-attachments/assets/c6c6ff33-75dc-4433-9786-b42d4cf06594> I then right-clicked in the source editor area and selected the Format Document option, which then automatically sorted out the indentation for me. image.png (view on web)<https://github.com/user-attachments/assets/d5a4bddc-afbb-4286-a389-1179079e9a3f> image.png (view on web)<https://github.com/user-attachments/assets/02477cbe-ca54-4e6f-a534-ea72a4972548> If you've got any questions on this then let me know. There is a section in the docs on the linter, which you may find interesting. https://codefori.github.io/docs/extensions/rpgle/linter/ — Reply to this email directly, view it on GitHub<#474 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BEV6P7ID6LPK6SY4H23VAGL4BPHKZAVCNFSM6AAAAACNXDXU6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMNBZGEZDKMRWGM>. You are receiving this because you were mentioned.Message ID: ***@***.***> Notice: This email and any files transmitted within it may contain privileged, confidential, and or proprietary information intended solely for the use of the individual or entity to whom they are addressed. To prevent the disclosure of sensitive information this message should be treated with the appropriate level of security. If you are not the intended recipient or person responsible for delivering it to the intended recipient, please notify the sender via email and delete the original message immediately. You are hereby advised that any disclosure, copying or distribution of the contents of this information is prohibited. Aromatique accepts no liability for any loss or damage resulting from the transmission of this email. Thank you.