Initially developed in the mid-1980s, Network Data Mover started as a software solution designed to transfer files between mainframe computers, particularly those running IBM’s MVS operating system. Over time, it evolved to support other platforms like midrange systems and eventually PCs, reflecting the growing need for cross-platform file sharing. It was created by a group of engineers who left the University Computing Company (later Uccel) to form The System Center, Inc. in Dallas. The product was rebranded in 1993 to “Connect: Direct” after Sterling Software acquired The System Center, and it’s been part of IBM’s portfolio since 2010, following their purchase of Sterling Commerce.
NDM was built to tackle the limitations of earlier file transfer methods, like FTP, by offering a more reliable and efficient way to move data, especially in enterprise settings. It initially leaned on IBM’s Systems Network Architecture (SNA) for transfers over private lines, but by the early 1990s, it added TCP/IP support, making it more versatile. Its focus on automation and resilience set it apart—features like checkpoint restart (so transfers could pick up where they left off after an interruption) and compression to speed things up while using less bandwidth. It’s widely used in industries like finance and government, where moving large, sensitive files across diverse systems—mainframes, Linux, Windows, you name it—is a daily necessity.
Today, as IBM Sterling Connect: Direct, it’s still about secure, high-volume file transfers, with modern perks like TLS encryption and support for a web-based console to keep tabs on everything. It’s less of a household name than FTP but a backbone for organizations needing something robust and dependable over long-haul connections.
