And it's not just getting the authorization lists right.
I had to rerun this:

To me this sounds like IBM has had to make a deliberate attempt to change
the authority of that command to some IBM suggested default. It wasn't
like the other stuff where there was some sync issue between authorization
lists not being there or some such thing.
And it's also not like all commands got changed to *PUBLIC *EXCLUDE.
I think I'll open this one as a separate ticket.

Rob Berendt

Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2015 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact