Are there any problems to have several customized AOMPORC ?
Release : 5.0
Component : CA SOLVE:Operations Automation for z/OS
No problem to have several customer's secondary AOMPROCs as long as they are used as expected by customer's operation.
$RMAOMP does &AOMCONT to a AOMPROC where NCLID is stored into a global variable $RMAOM2 . The secondary AOMPROC may pass a message/event by &AOMCONT to other customized AOMPROC.