When an EOJ rule issues a WTO command, the system generates a IEF196I message and its sent to the JES2 message dataset. For example:
09.43.22 JOB05172 IEF196I *ODTERJCX ENDED. NAME-CHECKLON TOTAL CPU TIME = 0.
How do I stop this message from being generated?
The default route code is causing the message to be generated.
Add a route(2) parm to the WTO command and it will resolve the issue.
In general, a WTO's issued from CA OPS/REXX code should have a Route code assigned to them. CA OPS/MVS Event Management and Automation does have the parameter WTODEFAULTROUTE that could be used to insure all WTO's from OPS/REXX code have at least a route code assigned.