I agree with Al, though I'd add that you also need to have enough
governance to make sure you're staying within the terms and conditions of
your zNALC approval at all times -- to make sure all the workloads that run
on those LPARs qualify and are clearly within the scope of your approval
(s). "Governance" may often mean steps such as documentation, operator
training (initial and recurrent), periodic auditing, operator sign-offs,
maintenance procedures (e.g. z/OS PTF and release upgrade procedures),
effective technical controls (such as particular RACF definitions, network
configurations, perhaps removal of certain run-time libraries and modules,
job scheduler configurations, source library build and deploy
configurations, constraints on TSO/E sign-ons), etc. Reasonably strong
governance is not unique to zNALC. It applies to practically every form of
licensing. But it's (also) important to zNALC.
If you have chargebacks then you will need to update and improve your
chargeback schedule. I've commented in the recent past about chargebacks
and their significant perils. They can be quite horrible if constructed and
applied poorly.
You may have some Sysplex aggregation issues and impacts to work through.
There's an excellent IBM redbook on that subject.
You may wish to visit or revisit your defined capacity settings
("softcaps") for both individual LPARs and groups of LPARs. You may also
want to revisit how the LPARs compete for speciality engine (zIIP)
resources, if they do, and the related zIIP configurations/controls. In
particular, it becomes relatively more important for the non-zNALC z/OS
LPARs to be "served first" if there is competition for zIIPs, other things
being equal.
That's a pretty good list!
--------------------------------------------------------------------------------------------------------
Timothy Sipples
IT Architect Executive, zEnterprise Industry Solutions, AP/GCG/MEA
E-Mail: [email protected]
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
