Capacity Provisioning for z/OS V2R1: Support of IFLs, SAPs and ICFs
OzanBaran 120000M0Q0 Visits (4525)
Following is a quick Capacity Provisioning (CP) for z/OS V2R1 tip but first I should say that I have been very impressed with CP for z/OS. They have been delivering valuable new functionality every z/OS release based on customer feedback and requirements. I will be talking about a couple more in other blog entries. Specifically their support of manually activated capacity as well as defined & group capacity limits – aka Soft or WLM capping.
CP for z/OS V2R1 allows the end users to activate/deactivate IFLs, SAPs and ICFs that are within their On/Off Capacity on Demand (CoD) records without the need to logon to a Service Element (SE). In other words acti
For instance looking at one of our CPCs I see that we have 12 IFLs and 5 spare processors. Also since we are a test shop we don’t have any activation limits for our On/Off CoD records as indicated by the -1 in the Configuration Report below.
F CPOSERV,APPL=R C DEST=*
Just to give you an idea on what to expect I activated one of those 5 spare engines as an IFL.
F CPOSERV,APPL=A R CPC=P91 IFL=13
Then I deactivated that IFL via:
F CPOSERV,APPL=I R CPC=P91 IFL=
For more details on CP for z/OS please refer to: MVS Capacity Provisioning User’s Guide
Make sure to take a look at their web site as well. I find the What’s New and FAQs sections to be very handy. Also if you are new to z/OS capacity provisioning take a look at the Further Info section for some introductory presentations.