Precisely Connect: priced on the engine, not your MSU.

Precisely Connect is the data integration and ETL engine formerly sold as Syncsort DMExpress and DMX, carried over when Syncsort (Precisely) rebranded in 2020. It accesses, understands, and transforms complex mainframe data, importing from sources including DB2, VSAM, IMS, Oracle, SQL Server, and Teradata and delivering to cloud and distributed targets such as Snowflake, Databricks, Azure Synapse, and cloud storage, in both batch and real time. For mainframe owners it is the pipe that moves legacy data to modern analytics platforms, which is why its licensing belongs in any estate review even though the engine itself runs largely off the mainframe.

Connect is licensed on the engine through Precisely's license key system rather than primarily on z/OS MSU. The unit of measure is tied to the engine deployment, the servers, nodes, or cores it runs across, together with the components, connectors, and target adapters enabled. License keys are issued and managed through the Precisely customer portal. Where a Connect component runs on the mainframe to read source data, mainframe footprint can enter the entitlement, so the basis is not purely distributed and should be read from your own schedules. The point for buyers is that the metric follows the integration engine and its scale, not the rated capacity of the z/OS machines it reads from.

Directional and pattern level. Precisely packaging and units of measure evolve, so confirm the current basis in your own Connect schedules before modeling a renewal.

The first cost driver is the deployed scale of the Connect engine, the count of servers, nodes, or cores, which grows easily in elastic and cloud environments where capacity is added without a procurement event. The second is the connector and component mix, since each source and target adapter for DB2, VSAM, IMS, Snowflake, Databricks, and the rest can carry its own entitlement and they accumulate as new pipelines are built. The third is environment sprawl into development, test, and disaster recovery, plus any mainframe side component used to reach source data. Because the engine is designed to scale out, the licensed footprint is the thing that quietly outgrows the contract.

Connect exposure sits in the gap between the deployed engine and the licensed footprint. Common traps we see at pattern level:

An engine licensed product renews on footprint discipline. The five levers that pay:

Data integration is a crowded market, and Connect competes with cloud native ETL services, with other change data capture and integration vendors, and with custom pipelines, so an alternative is genuinely available. The strength of Connect is its high performance handling of complex mainframe formats such as VSAM and IMS, which general purpose tools handle less gracefully, so the credible alternative narrows where mainframe source complexity is the requirement. For pipelines that touch only simpler sources, the alternative is real and a useful lever. Price the migration of each pipeline honestly, since rebuilding integration logic carries its own cost and risk, and use the contestable pipelines as leverage rather than betting the whole estate on a switch.