No, what I am saying is that is perfectly OK to add 100 scheduling environments, just not all at once (i.e. 1 activation of the Service policy).
Add them 10 at a time and measure the results, adjust. Repeat until all needed environments have been added. <snip> Do you mean that adding 100 Scheduling Environments is something I should never want to do? What could be the unintended impact? The policy can hold 999 Resources and 999 Schenvs and the Schenv Redbook even gives performance hints for this situation (add a control Resource to each Schenv). I think the only way to do it automated is with a macro of my terminal emulator. This way I also do mass updates to my SMS SCDS (e.g. change the retain-days-only-backup of all my managementclasses). This is much less sensitive to typo's than doing it manually. Kees. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Staller, Allan Sent: Monday, August 11, 2014 16:54 To: [email protected] Subject: Re: Mass updates to the WLM policy. IMO, no massive changes should *EVER* be added to a WLM Service Definition. *BEWARE* the law of unintended consequences. It is not a matter of the doing (via any method), it is a matter of the impact. Just my $0.02 USD worth. <snip> It has been asked before: is it possible to do mass updates to the WLM policy easily, e.g. add 200 Scheduling Enviroments to it, in batch or so? Apart from the replies, that the OP should not want to do what he wants to do, the general answer was NO. Is this still so? The z/OS MF interface seems to work the same way as the TSO interface: on update at a time. Has anyone found out the layout of the WLM policy PDS and a way or tool to manipulate (unload, update, reload) it in order to insert mass updates there? </snip> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
