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
Source not matching compiled objects
Source not matching compiled objects
Art Tostaine
Re: Source not matching compiled objects
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.
the trace will be in the tmp folder in LANSA_xxxpgmlib folder in the IFS by default
good luck finding that!
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.
the trace will be in the tmp folder in LANSA_xxxpgmlib folder in the IFS by default
good luck finding that!
Re: Source not matching compiled objects
Thanks again Dino. You are very helpful it’s much appreciated.
Art Tostaine