TCPware
Open-knowledge reference entry
TCPware is a third party layered product published by "Process Software LLC" of Framingham, Massachusetts to add TCP/IP capabilities to Digital Equipment Corporation's VMS operating system. In the early 1990s Digital Equipment Corporation had an internal policy favoring their own product, DECnet. Meanwhile, many VMS users in governments, large corporations and universities were discovering the "TCP/IP based" internet and required third party software to enable connectivity to it.
TCPware was enhanced in subsequent releases. Version 2.2, in 1991, added support for Sybase database procucts using the standard VMS functions. It introduced remote procedure calls (RPCs) to support distributed computing. It also added tn3270 for IBM 3270 terminal emulation, and support for the Simple Network Management Protocol (SNMP). The current version is 6.1.
Two features of the TCPware APIs, the "Telnet Library" and the "FTP Library", allow a relatively inexperienced programmer to use a high level language to write software which will connect across the internet. Quite a bit of legacy software now relies on these modules.
The public source identifies “TCPware” as open-knowledge reference entry. This brief keeps that definition visible, then builds a research path around TCPware, Open-knowledge and entry.
Why this record matters
A short description can identify a subject without explaining its stakes. For “TCPware”, the useful work is to connect “open-knowledge reference entry” to the records capable of establishing context and consequence.
The citation trail is more important than the brevity of the summary: it shows where individual claims can be examined in context. The source revision retrieved here is dated May 8, 2025. The linked authority identifier is Q4050576. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1991.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “TCPware”, its source revision and the description used here.
- Expand the search: follow TCPware primary sources, TCPware archive and TCPware research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “TCPware”?
- What terminology or title could unlock a more precise catalogue search?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “TCPware” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.