Skip to content

Conversation

VyshnaviKB
Copy link
Collaborator

Now splf file name gets created based on the filename and object type:
image

Screenshot 2025-07-15 231724 Screenshot 2025-07-15 231703 Screenshot 2025-07-15 231752

@VyshnaviKB VyshnaviKB self-assigned this Jul 15, 2025
Copy link
Member

@edmundreinhardt edmundreinhardt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can work, but I would test if the IBM i Job Log view still works with this change in place. I.e. can the the appropriate spool file be found .
@irfanshar you know what I mean.
The other simplication that I had in mind was to simply use the object name, if that is accessible. i.e. just $@
Once again, you might need to make changes to Project Explorer to keep it in sync
@SanjulaGanepola can guide you on that

@edmundreinhardt
Copy link
Member

If we were to just use the object name we will run into issues, if we have two source building into .
For example, if the Rules.mk is

HELLO.PGM: HELLO.RPGLE
HELLO.PGM: HELLO.PGM.RPGLE

@irfanshar
The scenario above is pathological, you are overwriting the same object. It is safe to assume that only one compilation will produce an object name, the only complication is if we have the same object name being built into different libraries. Now that would be rare but possible. If you wanted to be completely safe, you could qualify by library name. But I doubt this scenario would occur.

@irfanshar
Copy link
Collaborator

If we were to just use the object name we will run into issues, if we have two source building into .
For example, if the Rules.mk is

HELLO.PGM: HELLO.RPGLE
HELLO.PGM: HELLO.PGM.RPGLE

@irfanshar The scenario above is pathological, you are overwriting the same object. It is safe to assume that only one compilation will produce an object name, the only complication is if we have the same object name being built into different libraries. Now that would be rare but possible. If you wanted to be completely safe, you could qualify by library name. But I doubt this scenario would occur.

Apologies, I realized that after which is why I deleted the comment. I suppose it didn't delete on your end

@VyshnaviKB
Copy link
Collaborator Author

Tested new logic , scenario is working please find the screenshot below .
Now SPLF file name will get changed only if the target is RPGLE or SQLRPGLE for MODULE and PGM objects
NO change for remaining file extensions.
image1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants