You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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:
You can see that the line is not specified for two DATA log entries
The text was updated successfully, but these errors were encountered: