Dear Swaroop
Here are my 2 cents from my experience. I may not express them outright as pros and cons as I see the deciding factors as being more context dependent.
First, User VS Admin Customized. In my experience, the vast majority of, if not all, business end users generally have no desire nor intention to customize the use of ACS by themselves. They would be content to make requests to admin for the customization needed. Ans there may also be prevailing corporate security policy that restricts end users from using certain ACS functions which prevents them from doing their own customization. Only some technically oriented users would have a need, and are allowed by policy, to do their own customization but this group can be small. You may have one or both groups of these users to cater for.
Then, Local VS Remote deployment. For users who have consistent access to fast and reliable network (local and remote networks) as well as fast and reliable file server (and perhaps also a mirroring server for availability), having one shared location of ACS codes for remote use would make an admin's life less burdensome. Users who do not have the same privilege to such HW resources would do better to have local copy of ACS codes to run from. And if the latter group is a business user type, they would more likely have no desire to do the customization by themselves. Again, you may have one or both such groups of users
Depending on these factors mentioned (and a few more I do not have experience about), you may have to roll out just one or a mixed, if not even all these three, deployment styles.
Other considerations are also described here and there in this article :
https://developer.ibm.com/articles/i-ibmi-access-client-solutions-customization-trs/------------------------------
Right action is better than knowledge; but in order to do what is right, we must know what is right.
-- Charlemagne
Satid Singkorapoom
------------------------------