More about zNALC pricing

System z® New Application License Charges (zNALC) pricing applies to the z/OS® base feature and z/OS priced features, with the exception of HCM and HLASM Toolkit. zNALC is available for z/OS on LPARs dedicated to qualified applications, among other requirements. See System z New Application License Charges (zNALC) for more details.

Although the planning tool does not support zNALC, the planning tool can be used to report MSU estimates for LPARs that are running workloads that would qualify for zNALC. Such estimates can be generated by providing the planning tool with separate COMBIN DD control statements for z/OS, traditional z/OS and zNALC. The control statements would list the LPARs in which all z/OS systems are running, the LPARs in which z/OS is not running a zNALC workload (referred to as a traditional z/OS LPAR) and the LPARs in which z/OS is running a zNALC workload (referred to as a zNALC LPAR). For instance the following set of COMBIN control statements would be used to indicate that LPARs LPAR2 and LPAR3 were running zNALC workloads and LPARs LPAR5 and LPAR6 were running z/OS workloads which did not qualify for zNALC pricing.

z/OS=*ALL
zNALC=LPAR2,LPAR3
z/OS-Traditional=LPAR5,LPAR6

The resulting z/OS, zNALC, z/OS-Traditional values are described after the sample sub-capacity report fragment later in this topic.

Whenever SCRT encounters SMF data from zNALC LPARs (for example, LPARs whose names have the format ZNALxxxx), SCRT reports the z/OS MSUs in one of two formats. These zNALC formats are shown in the following sections of the sub-capacity report:

Product Summary Information
Product Max Contributors
Product Grid Snapshot
Defined Capacity Value Used

When the SMF data is from a CPC where all of the z/OS LPARs are zNALC LPARs, SCRT reports all of the z/OS values as zNALC values and lists z/OS (zNALC) as the name in the MLC Product Name column of the sub-capacity report. In this case, IBM charges zNALC pricing for all of the z/OS use on the CPC. See Figure 1.

Figure 1. Sample sub-capacity report: product summary information for zNALC only

==E5==================================================================
PRODUCT SUMMARY INFORMATION

MLC Product Name                              MLC Product ID   Tool MSUs  Customer MSUs  Customer Comments (255 chars max)

z/OS V1 (zNALC)                               5694-A01                98                              
DB2 UDB for z/OS V8                           5625-DB2                71                              
CICS TS for z/OS V3                           5655-M15                98                              
MQSeries for z/OS V6                          5655-L82                71                              
IMS V8                                        5655-C56                98                              
Lotus Domino for z/OS V7                      5655-B86                39                              

IPLA Product Name                             IPLA Product ID  Tool MSUs  Customer MSUs  Customer Comments (255 chars max)

File Manager for z/OS V6                      5655-P17                60     (optional)  (conditional)
IBM WebSphere Application Server for z/OS V6  5655-N01                71
IBM WebSphere MQ Workflow for z/OS V3         5655-BPM                71

When the SMF data is from a CPC with both traditional z/OS LPARs (for example, LPARs whose names do not have the format ZNALxxxx), and zNALC LPARs, SCRT reports three values for z/OS:

z/OS – this value represents the MSU values for z/OS running in all LPARs on the CPC. This value is used when assigning capacity to the z/OS based IPLA sub-capacity products running on this CPC.
z/OS (Traditional) – this value represents the MSU value charged against traditional z/OS use.
z/OS (zNALC) – this value is used to determine what MSU value is charged against zNALC use. IBM® uses the zNALC value reported on the SCRT, whenever the zNALC value is smaller than the difference between the z/OS value and the z/OS (Traditional) value.

When the difference between the z/OS value and the z/OS (Traditional) value is smaller than the zNALC value, then the difference is used, unless the difference is less than three MSUs. See www.ibm.com/systems/z/swprice/mlc/znalc.html for the rules that govern the case for when the resulting zNALC value is less than three MSUs.