COBOL & Mainframe · Track 07

Preparing a COBOL entitlement reconstruction

The strongest position in a COBOL audit is the one you build before the vendor builds theirs. Preparing a COBOL entitlement reconstruction means assembling an independent, evidenced license position from your own entitlements and deployment record before any vendor measurement script runs, so the finding is met by a defensible count rather than answered after the fact.

Visual COBOL, Enterprise Server, and the mainframe development tooling reached the OpenText estate through the Micro Focus acquisition that closed on January 31, 2023, and all are governed by the Additional License Authorizations. A reconstruction is the work of building your own version of the license position, line by line, against those authorizations and your real deployment, rather than waiting for a discovery scan to produce a number you then have to dispute. Because the EULA places compliance squarely on the licensee and gives the vendor only seven days notice before an audit, the reconstruction is what turns a short notice period into a controlled defense. This article sets out what goes into a COBOL entitlement reconstruction, the order to build it in, and why it sets the outcome of everything that follows.

What a reconstruction actually contains

A reconstruction is not an inventory dump. It is an evidenced mapping of every COBOL deployment to the entitlement that governs it, with the metric, edition, environment role, and capacity recorded for each. It establishes the effective license position the firm's four Rs are built around, and it is the same independent position described in reconciling COBOL entitlements before an audit, prepared deliberately rather than assembled under pressure. The reconstruction answers, for every deployment, which authorization applies, what metric governs, and what the defensible count is.

The order to build it in

The sequence matters, because each layer depends on the one before it. Preparing a COBOL entitlement reconstruction follows a deliberate order.

Entitlements first. Read the Additional License Authorizations to establish what is owned and on what metric, before counting anything.
Editions and roles next. Label each deployment by edition and by production or non production role, drawing on Enterprise Test Server and non production rights.
Capacity and constraint. Record the cores actually used, applying how sub capacity licensing applies to COBOL where a deployment is constrained.
Removals last. Strike decommissioned and standby systems so they never enter the baseline, tying to defending COBOL against an inflated core baseline.

The mechanic

A reconstruction prepared before the vendor measures sets the terms of the entire defense. The party that arrives with an evidenced, entitlement based count controls the conversation, while the party that only reacts to a scan is always answering someone else's number. The reconstruction is how the buyer stops reacting and starts setting the baseline.

Where the reconstruction fits in the four Rs

The reconstruction is the Reconstruct step of the firm's method, and the rest of the defense depends on it. Respond inside the seven day notice window, set a single controlled channel, and prevent any vendor script from measuring before the reconstruction exists. Reconstruct the position by reading the authorizations and building the evidenced count described above. Rebut the finding line by line against the reconstruction, so every vendor line is met by a documented counter position rather than a guess. Resolve on terms that record the reconstructed position as the agreed baseline, so a future audit starts from it. Without the reconstruction the later steps have nothing to push against, which is why preparing it early is the highest leverage work in a COBOL defense.

Why preparation beats reaction

The vendor measurement script is designed to produce the largest defensible number from a flattened view of the estate, and once that number is on the table it anchors the negotiation. A reconstruction prepared in advance means the buyer is never anchored to the vendor's figure, because an evidenced count already exists to set against it. The evidence that gives the reconstruction its weight is the workload record discussed in reducing a COBOL finding with workload evidence, gathered before it is needed rather than scrambled together after a finding lands. Preparation is what converts the seven day notice from a disadvantage into the start of a controlled process.

In a recent engagement

In a recent COBOL engagement, a reconstruction was prepared before any vendor script ran, mapping every Enterprise Server and Visual COBOL deployment to its entitlement, edition, role, and actual capacity, and striking decommissioned and standby systems from the count. When the vendor finding arrived built on full host capacity and a flattened inventory, the defense met it line by line with the reconstruction already in hand, and the finding could not hold against an evidenced position prepared in advance. The result came down to the defensible figure quickly, 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 reconstruction is the buyer's strongest asset

The lesson is that the license position is something the buyer builds, not something the vendor hands down. Because the noncompliance remedy is priced at then current list with back maintenance and audit cost recovery stacked on top, arriving with an evidenced reconstruction is what keeps the finding from compounding against an undefended count. Reading the authorizations, building the reconstruction in order, and resolving on terms that record it is what puts the buyer in control of a COBOL audit from the first week. This work feeds directly into the broader measurement defense in how OpenText measures COBOL usage in an audit. To have a COBOL entitlement reconstruction prepared before any vendor script runs, open a case.

Do you have an evidenced COBOL position ready before the vendor measures?

We read the Additional License Authorizations and build an independent, evidenced entitlement reconstruction mapping every deployment to its metric, edition, role, and actual capacity. 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 the reconciliation, the baseline, and the evidence a reconstruction rests on. 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.