Every Nonstop shop knows the feeling. The applications are rock-solid. They have processed payments, moved messages, and closed the books reliably for years, and nobody wants to touch them. Yet the world around those applications keeps moving. SNA infrastructure is aging out. Architects want real-time data and standard APIs. The pressure to modernize is real, but the last thing anyone wants is to put a proven, business-critical application at risk.
The good news is that modernization does not have to mean rip and replace. In most cases the applications are not the problem. The connectivity around them is. And connectivity is exactly the place where you can modernize incrementally, at minimal risk, without changing a line of application code.
That is the idea behind the uLinga suite from Infrasoft. Rather than one monolithic product, uLinga is a family that shares a common, fault-tolerant, process-pair core and addresses three distinct legs of the modernization journey. A site can start at whichever leg matters most today adding others as needs evolve.
Why connectivity is where modernization begins.
Replacing a Nonstop application is rarely justified. It works, it is trusted, and the institutional knowledge baked into it took years to accumulate. The pressure points almost always sit at the edges: a legacy protocol that is expensive to keep alive, transaction data that other teams cannot easily consume, or an integration style that predates the modern API.
Attacking those edges first is the pragmatic path. Modernize the connectivity, leave the application intact, and you get most of the benefit with a fraction of the risk. The recurring theme across everything that follows is simple: the application does not change; only the connectivity underneath it modernizes.
Leg one: retiring legacy SNA.
For many organizations, SNA is the piece that refuses to leave. It lingers in the network, adding cost and complexity, often right down to the last physical router tails that connect the data center to the outside world. Keeping that infrastructure alive means keeping specialist skills and specialist hardware around long after the rest of the network has moved on.
uLinga for EE addresses this directly. It carries SNA natively over an IP network using Enterprise Extender, so the Nonstop participates as an EE Node in the SNA APPN world while the transport underneath becomes HPR/IP running over UDP/IP. Access to key IBM mainframe subsystems such as CICS, IMS and TSO are retained, and the SNA APIs the applications depend on are preserved exactly as they were.
The payoff is threefold. Cost comes down, because the last of the physical SNA presence can be removed from the data center. Administration is simplified because there is far less to define and maintain. And where redundant links exist, uLinga for EE can be configured for fault tolerance across them, something that was not previously available to these applications. Network teams gain end-to-end visibility using standard IP monitoring tools, even though the applications themselves remain SNA applications from top to bottom.
Leg two: joining the event-driven world.
Modern architecture is built on real-time event streams. Fraud engines, decisioning platforms, analytics pipelines and cloud services all expect data to arrive as it happens, not in an overnight batch. Nonstop transaction data is some of the most valuable data in the enterprise, and historically it has been some of the hardest to surface where those modern platforms can use it.
uLinga for Kafka closes that gap. It gives Nonstop applications a direct, production-grade connection to Kafka, so they can both produce-to and consume-from Kafka topics. Transaction events can flow straight from the Nonstop into the streaming ecosystem, feeding fraud detection, real-time reporting, downstream microservices and cloud analytics without an intermediary platform sitting in the middle.
This is what lets a Nonstop application take its place in an event-driven architecture as a first-class participant rather than a walled-off system that needs special handling. The transaction logic does not change. What changes is that its data is finally available, in real time, to everything else the business is building.
Leg three: a unified, modern gateway.
Point solutions have a way of accumulating. Over time a site ends up with multiple ways in and out of the Nonstop, each with its own management and its own security posture. uLinga Nexus is the answer to that sprawl, and the strategic destination of the modernization journey.
Nexus is a high-performance, generic message and protocol handling platform built on the proven uLinga Gateway foundation and extended for modern applications. Nexus handles extremely high transaction loads and is secure by design, with TLS 1.3 across external connections. It offers flexible routing across TCP/IP, HTTP, Nonstop IPC and Pathsend, native HTTP and REST enablement directly on the platform, integrated data transformation including ISO 8583, and support for modern security standards such as OAuth 2.0 and OIDC single sign-on. It even extends to native support for MCP-enabled services, opening the door to AI-driven access to Nonstop applications and data.
Importantly, Nexus is an evolution, not a replacement. It keeps what already works and adds a modern, application-facing surface on top. For a development team, that means exposing Nonstop functions over the protocols they already understand, and consuming external services from the platform, without needing deep Nonstop specialist knowledge to do it.
The common thread
What ties these three legs together is as important as what makes them different. They share the same fault-tolerant core, the same online configuration approach, and the same management model. Adopting one does not commit you to a particular sequence, and none of them require changes to the applications they serve.
That is what makes the journey manageable. A site under pressure to retire SNA can start with uLinga for EE. A team chasing real-time data can start with uLinga for Kafka. An organization looking to consolidate and modernize its whole connectivity strategy can build around uLinga Nexus. Each step stands on its own, and each step fits alongside the others.
Where to start
Modernization is a path, not a cliff edge. The uLinga suite lets Nonstop customers move forward one deliberate step at a time, protecting the applications that run the business while steadily bringing the connectivity around them up to date.
At TIC, that is exactly the conversation we like to have: not “what do we replace,” but “where do we start.” If you are weighing how to modernize your Nonstop environment, talk to us about which leg of the journey makes the most sense for you first.
Be the first to comment