What infrastructure was required?

Interlink required both hardware and software components. The hardware typically involved channel attachment to the IBM mainframe, while the software ran on both the mainframe (NCP) and the DEC VAX/VMS systems. Understanding of both SNA and Decnet protocols was essential.

For mainframe products: Did this run in an LPAR?

For mainframe products like Interlink, operation within an LPAR (Logical Partition) was common. The software was z/OS dependent and likely required specific subsystems to be active for proper functioning. Knowledge of z/OS configuration was necessary.

Did this extend or enhance another product?

Interlink extended the capabilities of both IBM SNA and DEC Decnet networks. It required these networks to be already in place and functioning. It was not a standalone product but rather an add-on that enhanced existing network infrastructure.

What business problem did Interlink solve?

Interlink solved the business problem of connecting disparate network environments, allowing organizations to leverage their investments in both IBM and DEC technologies. Without it, data sharing and application access between these environments would be difficult or impossible.

What would happen if an organization did NOT use Interlink?

If an organization did not use Interlink, they would face significant challenges in integrating their IBM SNA and DEC Decnet environments. This could lead to duplicated effort, data silos, and reduced efficiency in accessing resources across the two networks.

What was the business value of Interlink?

Interlink allowed organizations to protect their investments in existing IBM and DEC systems by enabling them to work together. This avoided the need for costly replacements or migrations, while still providing enhanced functionality and interoperability.

How did Interlink address security?

Security in Interlink involved controlling access to resources and applications across the SNA and Decnet networks. This likely included authentication mechanisms to verify user identities and access control lists to restrict access to specific resources.

What audit/logging capabilities existed?

Auditing and logging capabilities likely existed within Interlink to track user activity and system events. This information could be used to monitor security, troubleshoot problems, and ensure compliance with regulatory requirements.

What ongoing operational requirements existed?

Ongoing operational requirements for Interlink included monitoring network performance, maintaining the hardware and software components, and providing support to users. This required skilled personnel with expertise in both IBM SNA and DEC Decnet technologies.

What were common implementation challenges?

Common implementation challenges included configuring the NCP on the IBM mainframe, ensuring proper channel attachment, and resolving compatibility issues between the SNA and Decnet environments. Thorough planning and testing were essential for a successful implementation.

What administrative interfaces were available?

Administrative interfaces likely included command-line interfaces (CLIs) for configuring the system and monitoring its performance. User management would have been handled through the IBM mainframe's security system or the DEC VAX/VMS system's user accounts.

Are You a Vendor? Claim Your Listing

Take control of your product listings. Add verified information, showcase updates, and unlock a Claimed Vendor badge across the directory.

Claim Your Listing Now

Interlink

Name: Interlink
Availability: InStock

Interlink Computer Sciences Not Supported z/OS

Networks and Communication

Vendor

Interlink Computer Sciences

Product Overview

Interlink's architecture centered around bridging IBM SNA and DEC Decnet networks. Key components included the NCP (Network Control Program) on the IBM mainframe, channel attachment hardware, and software components running on the DEC VAX/VMS systems. These components communicated using SNA and Decnet protocols, requiring a deep understanding of both network architectures.

The system allowed 3270 terminals to function as DEC terminals, effectively translating between the two environments. SNS/PrintQ provided print queue access from VAX/VMS to SNA printers. Given the end of support for Interlink, a modern architecture blueprint should consider alternatives like IBM z/OS Connect, Microsoft Host Integration Server, or Software AG Entire Net-Work.

These solutions typically leverage TCP/IP-based communication and offer more flexible integration options. The migration architecture should address network connectivity, application integration, security, and management. It should also consider the use of APIs and modern protocols to facilitate communication between different systems.

A phased migration approach is recommended to minimize disruption and ensure a smooth transition.

Frequently Asked Questions

What did Interlink do?

Interlink provided a bridge between IBM's SNA and DEC's Decnet networks. It allowed 3270 terminals to function as DEC terminals, enabling communication between the two environments. SNS/PrintQ, a related product, allowed VAX/VMS users to access SNA printers.

Was Interlink a system, application, or tool?

Interlink was a combination of hardware and software, acting as middleware to facilitate communication between different network architectures. It provided the necessary translation and routing functions to enable interoperability between IBM SNA and DEC Decnet environments.

What types of organizations used Interlink?

Organizations that needed to integrate IBM mainframe environments with DEC VAX/VMS systems used Interlink. These were often large enterprises in industries like finance, insurance, and government that had invested heavily in both IBM and DEC technologies.

When should a company consider Interlink?

Companies considered Interlink when they needed to connect their IBM SNA-based mainframe applications with DECnet-based systems. This allowed users on either network to access resources and applications on the other, improving overall efficiency and resource utilization.

What are the alternatives to Interlink?

Alternatives to Interlink include modern network integration solutions that support TCP/IP-based communication. These solutions often provide more flexible and scalable connectivity options compared to the older SNA and Decnet protocols.

Help Improve This Directory

Notice outdated information? Have insights about this product? Help the mainframe community stay informed with accurate, current data.

Report Issue Suggest Product Share Event

Share Your Product Experience

Help the community by sharing your experience with mainframe products. Your insights help others make informed decisions.

Share Your Experience

Are You a Vendor? Claim Your Listing

Interlink

Product Overview

Frequently Asked Questions

What did Interlink do?

Was Interlink a system, application, or tool?

What types of organizations used Interlink?

When should a company consider Interlink?

What are the alternatives to Interlink?

What infrastructure was required?

For mainframe products: Did this run in an LPAR?

Did this extend or enhance another product?

What were the main system components?

What business problem did Interlink solve?

What would happen if an organization did NOT use Interlink?

What was the business value of Interlink?

How did Interlink address security?

What audit/logging capabilities existed?

What ongoing operational requirements existed?

What were common implementation challenges?

What administrative interfaces were available?

Related Products

More from Interlink Computer Sciences

e-Control

TurboAPI

TurboFTP

TurboTelnet

Similar Products

2cIP

2cSNA

3770Link

3780Link

ACF/NCP

ACF/SSP

Help Improve This Directory

Share Your Product Experience