Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

In logs specify the line relative to data manipulations #7

Open
ftomassetti opened this issue Oct 1, 2019 · 0 comments
Open

In logs specify the line relative to data manipulations #7

ftomassetti opened this issue Oct 1, 2019 · 0 comments
Labels
enhancement New feature or request log

Comments

@ftomassetti
Copy link
Contributor

Sometimes we manipulate some data but we do not show in the log the source code line which originates that data manipulation. We do not do that because obtaining that information is not trivial. We should consider doing so.

For example:

18:12:41.969  MUTE11_02.rpgle 246 STMT SUBROUTINE END CHKOPE
18:12:41.969  MUTE11_02.rpgle 246 PERF SUBROUTINE END CHKOPE 0 ms
18:12:41.969  MUTE11_02.rpgle 190 EXPR NotExpr false
18:12:41.969  MUTE11_02.rpgle 190 STMT IF NotExpr false
18:12:41.969  MUTE11_02.rpgle       DATA MSG = --ESEGUE CHKOPE --CHKOPE OK
18:12:41.969  MUTE11_02.rpgle 195 STMT EVAL MSG = "--CHKOPE OK" --CHKOPE OK
18:12:41.969  MUTE11_02.rpgle       DATA MSG = --CHKOPE OK --ESEGUE CHKFLT
18:12:41.969  MUTE11_02.rpgle 198 STMT EVAL MSG = "--ESEGUE CHKFLT" --ESEGUE CHKFLT
18:12:41.970  MUTE11_02.rpgle 250 STMT SUBROUTINE  CHKFLT
18:12:41.970  MUTE11_02.rpgle 250 RESL SUBROUTINE START CHKFLT
18:12:41.970  MUTE11_02.rpgle 254 EXPR $$FLT = BlanksRefExpr false

You can see that the line is not specified for two DATA log entries

@ftomassetti ftomassetti added enhancement New feature or request log labels Oct 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request log
Projects
None yet
Development

No branches or pull requests

1 participant