COBOL & Mainframe · Track 07

Enterprise Test Server and non production rights

Test infrastructure is not production infrastructure, and a finding that counts it as though it were charges a buyer for capacity it never ran in production. Enterprise Test Server and non production rights describe the entitlement that covers test, development, and other non production use, and a finding that counts those environments at production rates, or ignores the non production rights entirely, overstates the position.

Enterprise Server reached the OpenText estate through the Micro Focus acquisition that closed on January 31, 2023, and it is governed by the Additional License Authorizations. Those authorizations distinguish production deployment from the test and non production use that supports it, and the Enterprise Test Server entitlement exists precisely so that test environments are not licensed as if they were production. When a discovery scan flattens an estate it counts servers, not the production status of those servers, and a finding built on that view tends to charge every running instance at the production rate. This article sets out what the non production rights cover, where the finding inflates, and how the test estate is restored to its own entitlement line by line.

What the non production rights cover

The Enterprise Test Server entitlement and the broader non production rights exist because test, development, staging, and disaster recovery standby do not consume the product the way production does. A test environment runs to validate change, not to serve the business, and the authorizations recognise that with a distinct entitlement and a distinct measurement. The boundary between production and non production is the same one examined in COBOL non production and test environment scope, and getting it right is the difference between a defensible test count and a production charge applied to non production capacity.

Where a finding counts non production as production

The overstatement begins when the scan cannot read the environment role and the finding defaults to production. Several patterns recur around Enterprise Test Server and non production rights.

Test counted as production. A validated test instance charged at the production rate because the scan saw a running server.
Non production rights ignored. An entitlement that covers test use left out of the reconstruction, so the test estate appears unlicensed.
Standby counted as live. A disaster recovery standby instance counted as an additional production deployment.
Development conflated with runtime. A development environment counted as runtime capacity, compounding the role error with a metric error.

The mechanic

The environment role governs the rate, and the rate governs the charge. A finding that counts a test server at the production rate is reading production economics into capacity the buyer never ran in production, and it is corrected by matching every environment to the production or non production entitlement that governs it.

Restoring the non production estate under the four Rs

The defense returns the test estate to its own entitlement through the firm's four Rs. Respond inside the seven day notice window, set a single controlled channel, and prevent any vendor script from measuring before the environment roles are scoped. Reconstruct the position by reading the Additional License Authorizations to establish which deployments are covered by the Enterprise Test Server entitlement and the non production rights, then label every environment with its role. Rebut the finding line by line, removing any line that counts a test, development, or standby environment at the production rate and any line that omits an applicable non production entitlement. Resolve on terms that record the role of each environment, so a future audit cannot quietly promote test to production. The reconciliation that organises this work is the one in reconciling COBOL entitlements before an audit.

How the production rate stacks the remedy

The reason a misclassified test environment matters so much is the structure of the remedy. On noncompliance the licensee is deemed to have acquired licenses at then current list price, must pay back maintenance and support, and reimburses the cost of the audit, so a single test server counted as production is not one charge but several stacked on top of each other. The core measurement that the production rate then applies to is the one set out in what is an Enterprise Server core license metric, which is why an environment role error and a core count error so often appear on the same line.

In a recent engagement

In a recent COBOL engagement, a finding counted a set of validated test and standby instances at the production rate, treating the entire Enterprise Server estate as live production capacity. The defense read the authorizations, identified the Enterprise Test Server entitlement and the applicable non production rights, and demonstrated which instances served only test and disaster recovery roles. Once each environment was matched to its role and the non production lines were re rated, the finding fell to the defensible figure. The reduction was characteristic of the firm's record across more than 200 defended audits, contributing to the 68 percent average reduction and the more than $90M in claims mitigated against vendor positions.

Why the role is decided by the entitlement, not the scan

The lesson is that the role of an environment is decided by how it is used and what the entitlement covers, not by whether a scan sees a process running. Because the noncompliance remedy is priced at then current list with back maintenance and audit cost recovery stacked on top, charging test capacity at the production rate multiplies a charge for use the buyer never made of the production estate. Reading the authorizations, scoping each environment to its role, and resolving on terms that hold the non production rights is what keeps test measured as test. To have a finding tested against the Enterprise Test Server entitlement and the non production rights that actually govern your estate, open a case.

Is your finding charging test environments at the production rate?

We read the Additional License Authorizations, identify the Enterprise Test Server entitlement and the non production rights, and re rate any line that counts test or standby as production. To get a defense team on the file, open a case or download the guide to reading the Micro Focus ALAs.

Get The Number Down →

Related field notes

These notes from the COBOL and Enterprise Server mainframe audit defense cluster cover non production scope, the core metric, and the reconciliation that scopes them. Each links back to the complete OpenText audit defense playbook for 2026.

If an OpenText or Micro Focus audit notice has arrived, the first seven days matter more than any week that follows them. OpenText Audit Defense is an independent, buyer side practice founded in 2020 by former vendor compliance leadership. We have defended more than 200 audits, reduced the average finding by 68 percent, and mitigated more than $90M in claims against vendor positions. We do not resell OpenText software and we are not affiliated with OpenText Corporation. To open a case, use the contact form on this site.