COBOL and Enterprise Server mainframe audit defense.

Visual COBOL, Enterprise Server and the mainframe application development tools came to OpenText through the Micro Focus acquisition and are governed by the Micro Focus Additional License Authorizations. These products are licensed on capacity metrics such as cores, MIPS, and workload, and a COBOL finding turns on how that capacity is measured. The vendor opens by reading the largest capacity figure it can support and pricing the gap to your entitlement at list, with back maintenance and audit costs added.

The central overclaim is core counting. Modern hosts and virtualised platforms present far more cores than a COBOL workload actually consumes, and a finding that counts every physical core, or every core in a virtualisation cluster, rather than the cores the runtime is licensed and configured to use, inflates the number sharply. Alongside cores sit further traps:

• Runtime versus development confusion, where development seats and runtime deployments are counted under the same metric.
• MIPS and workload figures read at a peak rather than a representative level.
• Non production and test environments counted against production capacity entitlement.
• Decommissioned workloads and high availability standbys still carried in the count.

Enterprise Server regions, PACs, and sub capacity arrangements add further definitional questions, each of which can be overstated in an opening position. The defense rests on the deployment evidence: the cores actually allocated, the workload actually run, and the clear line between development and production that the authorization draws.

The decisive material is the deployment record. Core allocation, virtualisation configuration, and workload reporting show what the COBOL runtime actually consumed, and that is the only basis a defensible capacity finding can stand on. The full method is set out in the four Rs and in the complete OpenText audit defense playbook.

COBOL findings follow the same shape as the rest of our practice. The opening number rests on a core count that ignores allocation and the development boundary, and the defensible figure emerges once deployment evidence replaces the raw capacity reading. Across more than 200 defended OpenText and Micro Focus audits, the firm record holds steady.

For the mechanics that apply across every product line, start with how to respond to an OpenText seven day audit notice and the reading Micro Focus ALAs paper.