We have a process by which application code is migrated thru various environments by a specific userid (XYZ). The corresponding DB2 packages are bound with owner (ADM), and XYZ has got BINDAGENT access on behalf of ADM.
There is one test environment where packages can be bound either by this process, or by individual users themselves. When the package is bound by XYZ with OWNER (ADM) in this envt, it is not able to grant the BIND access to other users, which is preventing individual users from binding that same package if needed.
XYZ is able to successfully bind a package as OWNER(ADM), but it is not able to GRANT bind access on the package to other users.
Is there any way of enabling XYZ to be able to grant that BIND access to other users, even PUBLIC ? The workaround I have at present is to run a daily batch job that would grant BIND access to PUBLIC for all packages that do not have PUBLIC bind access in that envt.
Thanks in advance.