When using ESPDST (CYBESDT1), the explicit data set trigger utility, will determine that the specified explicit data set trigger is not defined to the target CA ESP Workload Automation subsystem. It will issue message
"ESP1655W Explicit data set trigger for <dsn> not defined to ESP subsystem <ssid>" and exits with return code 4.
In prior releases ESPDST would not produce errors and terminate with a return code 0. I would like to restore the old behavior.
USERMOD 71, when set on a tracking ESP subsystem, will cause ESPDST to exit with return code 0 instead of return code 4 when the specified explicit data set trigger is not defined to ESP. ESP166W, a benign and accurate informational message, will still be issued when USERMOD 71 is set.