Route Code missing in WTO messages written in CA OPS/MVS

book

Article ID: 6369

calendar_today

Updated On:

Products

CA OPS/MVS Event Management & Automation

Issue/Introduction

We are finding WTOs, that previously appeared on the operator's console, are not showing up.  The message goes to the SYSLOG with route code 0.   This is causing the operator to miss the intended messages.

Cause

Missing route codes in the generated messages.

Environment

OPS/MVS

Resolution

  1. Check for setting or not setting the WTODEFAULTROUTE parameter in the OPSSPA00 member of your hlq.CCLXCNTL dataset
  2. Add the parameter if it does not exist. (see the documentation link in the Additional Information).
  3. 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.

WTODEFAULTROUTE Parameter
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.

Default value
0

If the ROUTE code keyword is not used and the parameter WTODEFAULTROUTE is set to 0, the default is taken from the SYS1.PARMLIB CONSOLxx member.
For example:

DEFAULT ROUTCODE(1) 

Additional Information

https://techdocs.broadcom.com/us/en/ca-mainframe-software/automation/ca-ops-mvs-event-management-and-automation/14-0/reference-information/parameter-reference/parameters-in-ca-ops-mvs/message-related-parameters.html#concept.dita_207050b899e54554d6f3f9553361d222847e526d_WTODEFAULTROUTEParameter