Hi Neeraj,
This can be applicable at any layer - router DSA and/or data DSA.
By default this is turned on. Usually this setting is used if you would want to block the incoming traffic manually via DSA console (aka DXconsole). A good example would be:
- Applications connecting to data DSAs directly and you need to shutdown the DSA for maintenance.
- You would want to block any new binds to DSA to all the pending transactions (mainly if the setup MW and you have MW queues pending) to be finished.
- You connect to DSA console and run 'set allow-bind = false;' which will be effective immediately.
- After that shutdown the DSA and when you restart after planned activity, it will default back to 'set allow-bind = true;' so DSA can be opened to incoming binds.
Same applies to router DSA if you environment is setup in such a way that NOTHING connects to data DSAs directly. Meaning, as all binds are initial made to router DSA(s) which is supposed to chain requests to underlying data DSA(s), you would want to block binds at router DSA(s) first, let the data DSA activity get drained, perform your maintenance task, when you restart, it will set back to 'on' again.
set allow-binds Command -- Enable or Disable New Bindings on a DSA - CA Directory - 12.6 - CA Technologies Documentation
Hope this addresses your concerns.
Thanks,
Hitesh