Going back to your original question, I think a reasonable UACC for BRODCAST would be NONE. This is because all "normal access", ie writing and reading, is handled under the covers by the SEND and LISTBC commands.
Even with user logs, the likelihood is that the id sending the message is not the id that owns the log. Giving everyone even READ access to all users' logs would not make sense. The only exception should be access by personnel responsible for managing such logs at a system level. Sent from my iPhone > On Apr 19, 2017, at 13:54, gsg > <[email protected]> wrote: > > Does SYS1.BRODCAST need to have UACC of UPDATE? If so, is it actually stated > somewhere? Been trying to find information on this. > > TIA > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
