NetView for z/OS: the automation engine that bills off the SCRT clock.

NetView for z/OS is IBM's long established systems and network management product, the automation backbone in many mainframe operations centers. It handles network monitoring, automated operations, event correlation, and the unattended responses that keep large z/OS environments running. It is frequently licensed as part of a broader IBM Z automation suite alongside related System Automation function, which is why its licensing has to be read in the context of the bundle it sits in, not as a standalone line.

NetView for z/OS is an IPLA program licensed under Value Unit pricing. You acquire an entitled license capacity for a one time charge (OTC), expressed in Value Units that convert from MSUs through a Value Unit Exhibit, and you then pay an annual Subscription and Support (S&S) charge on that perpetual license. It is not a Monthly License Charge product, so it does not bill on the Rolling 4-Hour Average through SCRT the way z/OS, CICS, and Db2 do. The Value Unit Exhibit is tiered: the larger the licensed capacity, the fewer Value Units per MSU you pay at the margin, and Value Units of one product cannot be aggregated with another.

Worked illustration of the tiered exhibit: a program priced at, say, 1 Value Unit per MSU at the bottom of the table may price at a lower marginal rate per MSU as licensed capacity climbs into higher tiers. The exhibit code and rate table are program specific, so the only number that matters is the one on NetView's own exhibit, checked against the MSU capacity it actually runs on.

The dominant cost driver is entitled license capacity: the Value Units you hold, sized to an MSU capacity that may or may not reflect what NetView runs on today. Because NetView is IPLA, the recurring cost is the annual Subscription and Support stream on that perpetual license, and it does not fall when you shape the monthly peak. The second driver is the bundle: when NetView is licensed inside a broader automation suite, its cost is entangled with the other components, and the suite renewal, not a NetView line item, is where the number is actually set. A third, quieter driver is stranded entitlement, capacity licensed for an estate that has since been consolidated but still carries S&S.

IPLA Value Unit products carry a different audit profile from MLC products: the question is not your monthly peak but whether your deployed capacity sits inside your entitled license capacity. Common traps we see at pattern level:

Because NetView is IPLA, the levers are about capacity and the bundle, not the R4HA. The five that pay:

NetView is deeply embedded in the operations automation of many shops, and ripping it out is a project, not a renewal tactic. The credible alternatives are about scope and overlap, not wholesale displacement: competing and third party automation and network management tools exist and are genuinely contestable in greenfield or partial scope, and within a large IBM estate the real question is usually whether you are licensing more NetView capacity and function than the operation uses. Treat any pitch that frames a quick NetView replacement as a negotiation lever with caution, because the automation runbooks built on it represent years of embedded operational logic.