Robert A. Rosenberg wrote:
At 17:35 -0400 on 04/30/2012, John Eells wrote about Re: ServerPac RACF*
jobs (rant):
So we created two jobs, with an overall z/OS section for each job, and
then subsections for other things you could order along with z/OS to be
included if you ordered them. The result *was* (at the time) tested
against new, empty RACF databases and any bugs found were fixed. That
structure virtually guaranteed some duplication in things like SETR
commands, but because of how the internals of ServerPac production
worked at the time there was no good way to prevent that.
That was (if I understand correctly) because no-one bothered to look at
the interaction between optional components. From your description it
sounds like the added subsections were of the "If Component X is ordered
then add these commands" type with no attempt to have the added commands
divided into 2 groups (Unique to this component and shared with 2 or
more components). Commands in the 2nd group should only be added if a
prior component has not been ordered.
I'd quibble with "no one bothered" (development resources are finite and
something to accomplish the desirable goal you outline would have had to
have been built), but that's exactly how it works. Further, the jobs
are generated as though there are no security definitions already, which
other than on brand new systems will probably never be the case.
Again, none of this is to say the solution is perfect (we all know it
wasn't) or that it can't stand improvement (it certainly could). But as
usual, discussion here won't solve much compared to requirements that
might influence future development.
(Also as usual, if anyone does submit a requirement, please focus on
what you need and not how you think IBM should satisfy the need. An
awful lot of requirements specify an implementation we cannot satisfy
instead of a need we might be able to satisfy and get rejected for that
reason.)
<snip>
--
John Eells
z/OS Technical Marketing
IBM Poughkeepsie
[email protected]
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
