Why NDS (Network Delivery Services) tracking doesn't work when CA WA ESP initialization statement ISCOPT SENDNET(ORIGNODE) option is used.

Document ID : KB000026127
Last Modified Date : 14/02/2018
Show Technical Document Details


When using the NDS (Network Delivery Services) method to communicate between two CA Workload Automation ESP Edition Master subsystems, the tracking data is not posted to the original node.  ESP initialization statement ISCOPT NETWORK SENDNET(ORIGNODE) is used.



CA Workload Automation ESP Edition release 11.4



If ISCOPT initialization parameter specifies NETWORK SENDNET(ORIGNODE), and a NETDEST statement describing the ESP Master subsystem does not specify the network destination, then CA WA ESP cannot determine the originating node.



The NETDEST initialization parameter/command needs to be defined with SYSPLEX, or XCFGROUP, JESNODE, and SYSID parameters.  These are necessary when ISCOPT NETWORK SENDNET(ORIGNODE) is in use.  

Example: NETDEST ADD NETNODE(espm_newyork) SYSPLEX(newyork) JESNODE(nyc) SYSID(espm_nyc)

Note: If PTF RO88003 is applied, then the JESNODE parameter is no longer required.  ESP will set JESNODE automatically. 


Additional Information:

CA Workload Automation ESP Edition Installation and Configuration Guide - Chapter 22 Setting Up Communications between Two or More Masters.