We don't want to give the zDC user ID access to BPX.FILEATTR.PROGCTL, because this is a very powerfull and thus dangerous authorisation to give. As a consequence, when a new version of the libdtzagent.so comes in, the program control bit does not get set on that new shared lib. We do get an ICH408I message in the job log of the zDC started task, obviously. We have system automation and we could very well automate the extattr command and the re-starting of the zDC. But before re-inventing the wheel again: has someone already done this and would they be willing to share a few pieces of code?
Thanks and very best regards,
Solved! Go to Solution.
the zLocal doesn’t run in a program controlled environment so it doesn’t need the program controlled bit to be set and the error message when the bootstrapper tries to set it and fails is just an annoyance.
You can ignore the message or update to a more recent bootstrapper that doesn’t try to set the bit.
The bootstrapper with version greater than [7.2.19] = 18.104.22.1688 doesn’t try to set the bit.