The above is due to the setting of SARINIT FEATURE=1, which generates the messages.
The client disabled the FEATURE, and immediately noticed a reduction in the WTO traffic.
The client reviewed a MIPS report, to monitor the SARVTAM task in question, and found a hung user session, which was consuming some CPU MIPS constantly through out the day.
The user session was cancelled, a fresh start was done on the SARVTAM task, and CPU consumption returned to normal.