2010 Jul 12 10:08 AM
Hi,
We are facing a strange problem...
First job runs to update TVARVC variable to a new value...let say 6 to 7....
Second job which runs immediatly after first job uses this variable in TVARVC to read the value picks up old value instead of new value....i.e. its using 6 instead of 7.
Also TVARVC variable is Fully Buffered table...Can anyone tell me eventhough this variable is updated with new value, why second job is picking old value..??? also i dint see any COMMIT WORK after updating TVARVC in program...i doubt if buffered and no commit work causing the issue...any thoughts???
Expecting your help.
Thanks
Hari
Hi,
We are facing a strange problem...
First job runs to update TVARVC variable to a new value...let say 6 to 7....
Second job which runs immediatly after first job uses this variable in TVARVC to read the value picks up old value instead of new value....i.e. its using 6 instead of 7.
Also TVARVC variable is Fully Buffered table...Can anyone tell me eventhough this variable is updated with new value, why second job is picking old value..??? also i dint see any COMMIT WORK after updating TVARVC in program...i doubt if buffered and no commit work causing the issue...any thoughts???
Expecting your help.
Thanks
Hari
2010 Jul 12 11:35 AM
Hi Hari,
Is your update and the program that uses the update in the same LUW? You can create a function module, and run it "in update task". Then update your TVARV table, and run the other program from the function module.
This will put all the programs in the same LUW.
If for some reason your update to TVARV doesn't happen, and it abends, your other program will not be executed.
Just a thought,
Michelle
2010 Sep 17 10:30 AM
2010 Dec 13 4:29 AM
Hi,
How did u resolve the buffering problem. I have the same issue.
Regards,
Bathula
2019 Jul 30 3:24 PM
Hi Hari Nair,
Could you explain how you solved the buffer issue? Would be very helpfull, thx a lot
regards,
Gerald