DDR for services
We could add:
# # This will make each ATMI client/server to parse ndrxconfig.xml # NDRX_USEDDR=Y
Then we could have "<services>" tag and "<routing>". the groups could be numberic (like rmid).
for these special services, we could advertise them with "<service_name>,<group_id>".
Thus if user makes "tpadvertise"/"tpunadvertise" we could use "rmid" and make two advertise calls one for common services and another for group shared.