We have migrated from CA OPS/MVS r12.2 to r12.3 in our sysplex. We are finding WTOs, that previously appeared on the operator's console, are not showing up in CA OPS/MVS r12.3. The message goes to the SYSLOG with route code 0. Previously in the CA OPS/MVS r12.2 software, it had route code 2. This is causing the operator to miss the intended messages.
To ensure that previously undeliverable messages are now received, you must update all automation code that issues WTOs to include a destination, such as Route codes or console name. Check for setting or not setting the WTODEFAULTROUTE parameter in the OPSSPA00 member of your hlq.CCLXCNTL dataset in both your CA OPS\MVS r12.2 and r12.3 software libraries.
- Check for setting or not setting the WTODEFAULTROUTE parameter in the OPSSPA00 member of your hlq.CCLXCNTL dataset in both your CA OPS/MVS r12.2 and r12.3 software libraries.
- Add the parameter if it does not exist. (see the documentation link in the Additional Information).
- Set the WTODEFAULTROUTE parameter to specify a ROUTE code that will be used for any WTOs issued with ADDRESS WTO or OPSWTO that do not include a route keyword.
This parameter specifies the single z/OS route code to add to any WTO issued by OPSWTO or ADDRESS WTO when no route codes are specified, no console is specified, and the MCSFLAG is not set to HRDCPY only. This parameter supersedes any z/OS default route code and reduces the number of undeliverable messages.