Identifying Source modified through VS-Code or green screen SEU

[santoshkatagi]

Is there a way to identify developers modified the Source through VS-Code vs green screen SEU?

[sebjulliand]

I don't think so. Same goes with RDi. You can't tell for sure which editor was used to modify a member or ifs file.

[worksofliam]

Converting to discussion.

[MarcoDeSenas]

Is there a way to identify developers modified the Source through VS-Code vs green screen SEU?

If you start journaling the source physical file, you might find some information related to your concern. I never tried to journal such an object so, I am really unsure about what would be the result and which file operation would be logged when a member (I guess you are using physical files for your sources) is updated with SEU or with Code4i. I will try to run a try.

More information about the content of journal entries here https://www.ibm.com/docs/en/i/7.5.0?topic=information-journal-code-descriptions and https://www.ibm.com/docs/en/i/7.5.0?topic=information-layouts-fixed-length-portion-journal-entries.

[MarcoDeSenas]

Is there a way to identify developers modified the Source through VS-Code vs green screen SEU?

I remembered that SEU was clearing the member when saving the updates, and it appears that Code4i does the same.
When journaling the file and filtering the journal entries on F code and CR (clear member) type, I get that:

SELECT entry_timestamp, job_name, program_name FROM TABLE ( QSYS2.DISPLAY_JOURNAL( 'DIMARCO2', 'JRN', JOURNAL_CODES => 'F', JOURNAL_ENTRY_TYPES => 'CR', OBJECT_LIBRARY => 'DIMARCO1', OBJECT_NAME => 'QRPGLESRC', OBJECT_OBJTYPE => '*FILE', OBJECT_MEMBER => 'TEST')) AS JT;

The first row is related to an update with SEU. The second row is related to an update with Code4i. Program name is not the same. We can assume that Code4i updates will always go through an ssh session (job and program QP0ZSPWT). Job and programs names are not an officially documented method however. I cannot test with RDi, but I believe that RDi connects through the host servers, so job and program names are probably other ones.
So, it looks like you can use this tip. However, depending on the volume of updates on your source files, the journal receivers might grow quickly.