Page 1 of 1

Source not matching compiled objects

Posted: Sun Dec 13, 2020 8:04 am
by atostaine
We have a field called SDQTY that is being updated by VL Windows (TXxxxxxxxxx job). IBM i journaling confirmed it is the OAM for the table.

I've done a cross reference on SDQTY and investigated every component. None of them do an update with that field. I've even done a source find and investigated all of those. We suspect that some source code has been changed and not deployed.

Is there a way to get more information from LANSA to find out what program is calling the OAM? Logging or trace or something? We believe it is updated using call_server_function.

Thanks, Art

Re: Source not matching compiled objects

Posted: Sun Dec 13, 2020 11:43 am
by Dino
Hi Art,

Did some test... If you use LANSA CONFIGURE in the IBM, and set the trace for IPCDATA, you will get some information there that shows the data that has been sent including the function making the call, the file and more important in your question, the fields. It will be better to delete or rename any old trace file, make the change and you may need to restart the listener.
lansaconfigure.png
lansaconfigure.png (231.13 KiB) Viewed 6108 times
the trace will be in the tmp folder in LANSA_xxxpgmlib folder in the IFS by default
lansaconfigure4.png
lansaconfigure4.png (11.74 KiB) Viewed 6108 times
lansaconfigure5.png
lansaconfigure5.png (32.83 KiB) Viewed 6108 times
good luck finding that!

Re: Source not matching compiled objects

Posted: Sun Dec 13, 2020 11:45 am
by atostaine
Thanks again Dino. You are very helpful it’s much appreciated.