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.

IOW: Component Y has 6 commands shared with other Components (such as Component X). If Component X has had its commands added, then when it is time to add Component Y's commands if 2 of these 6 are shared with X, then only the other 4 should be inserted (with the other 2 suppressed since they are already there due to X). If you then order Component Z (which as some shared commands with X and/or Y) you suppress any command that is in X or Y and only insert those that are not shared with them. This process is repeated with each component so that any command that is used by more than one component is flagged to show every component it is used by and thus can be excluded if any component that shares the commend has already been processed. IOW: Not ordering Component Y but testing in the order X/Y/Z will insert the shared Y and Z commands as part of the Z processing.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to