Virtual Telecommunications Access Method

Last updated

Virtual Telecommunications Access Method (VTAM) is the IBM subsystem that implements Systems Network Architecture (SNA) for mainframe environments. [1] VTAM provides an application programming interface (API) for communication applications, and controls communication equipment such as adapters and controllers. In modern terminology, VTAM provides a communication stack and device drivers.

Contents

History

VTAM was introduced in 1974 after a series of delays [2] as a major component of SNA along with the 370x Network Control Program (NCP) and Synchronous Data Link Control (SDLC).

In IBM terminology, VTAM is an access method software allowing application programs to read and write data to and from external devices. It is called 'virtual' because it was introduced at the time when IBM was introducing virtual storage by upgrading the operating systems of the System/360 series to virtual storage versions. VTAM was supposed to be the successor to the older telecommunications access methods, such as Basic Telecommunications Access Method (BTAM) and Telecommunications Access Method (TCAM), which were maintained for compatibility reasons. As such, VTAM is comparable with the Virtual Storage Access Method (VSAM), which was at that time a new and supposedly converged access method for disk storage.

ACF/VTAM

Originally, VTAM was provided free of charge like most systems software of that time. However, VTAM 2 was the last version to be freely available. ACF/VTAM (Advanced Communication Function/Virtual Telecommunications Access Method) was introduced in 1976 [3] and was provided for a licence fee. The major new feature of ACF/VTAM was the Multisystem Networking Facility, which introduced "implementation of intersystem communication among multiple S/370s.". [4]

A limited version of ACF/VTAM known as ACF/VTAME (Advanced Communications Function for the Virtual Telecommunications Access Method Entry) was made available for DOS/VSE systems running on the IBM 4300. [5]

SNA Services

VTAM has been renamed to be the SNA Services feature of Communications Server for OS/390 . This software package also provides TCP/IP functions. VTAM is used in multiple enterprises as of September 2019.

Features

VTAM supports several network protocols, including SDLC, Token Ring, start-stop, Bisync, local (channel attached) 3270 devices, [6] and later TCP/IP.

In a VTAM network, communication took place through an integrated communication adapter in the mainframe itself, or by a separate programmable front-end processor, the IBM 3745/3746 Communications Processor, with its own operating system, the Network Control Program NCP. These machines are no longer actively marketed by IBM, but are still supported. IBM provides hardware maintenance and microcode updates for the estimated 20,000 installed 3745/3746 controllers. A robust third party industry of smaller 3745/3746 specialty companies provide such controllers, upgrades, features, and related support services. VTAM and SNA are still in use by many enterprises.

Initially, VTAM only allowed communication between mainframes and peripheral equipment such as terminals, distributed processors and minicomputers. Later, 'cross-domain' resources [7] were introduced (not to be confused with TCP/IP domains) allowing SNA networks with more than one mainframe. A subsequent development was SNA Network Interconnect (SNI) [8] , allowing networks of different organizational entities (firms) to be interconnected with a high degree of independence. Finally, Advanced Peer to Peer Networking functions (APPN) were added to VTAM [9] . In APPN the mainframe is no longer the heart of the network, but all nodes in the network are considered as peers. One of the reasons why APPN was introduced was to act as a DECnet-killer, but by the time APPN was actually shipped the popularity of DECnet had already declined. APPN was considered overly complex and as of 2012 has been largely superseded by TCP/IP.

Related Research Articles

<span class="mw-page-title-main">IBM 3270</span> Family of block-oriented display terminals and printers made by IBM

The IBM 3270 is a family of block oriented display and printer computer terminals introduced by IBM in 1971 and normally used to communicate with IBM mainframes. The 3270 was the successor to the IBM 2260 display terminal. Due to the text color on the original models, these terminals are informally known as green screen terminals. Unlike a character-oriented terminal, the 3270 minimizes the number of I/O interrupts required by transferring large blocks of data known as data streams, and uses a high speed proprietary communications interface, using coaxial cable.

<span class="mw-page-title-main">MVS</span> Operating system for IBM mainframes

Multiple Virtual Storage, more commonly called MVS, is the most commonly used operating system on the System/370, System/390 and IBM Z IBM mainframe computers. IBM developed MVS, along with OS/VS1 and SVS, as a successor to OS/360. It is unrelated to IBM's other mainframe operating system lines, e.g., VSE, VM, TPF.

<span class="mw-page-title-main">VSE (operating system)</span> Operating system

VSEn is an operating system for IBM mainframe computers, the latest one in the DOS/360 lineage, which originated in 1965. It is less common than z/OS and is mostly used on smaller machines.

<span class="mw-page-title-main">OS/390</span> Operating system for IBM mainframes

OS/390 is an IBM operating system for the System/390 IBM mainframe computers.

Systems Network Architecture (SNA) is IBM's proprietary networking architecture, created in 1974. It is a complete protocol stack for interconnecting computers and their resources. SNA describes formats and protocols but, in itself, is not a piece of software. The implementation of SNA takes the form of various communications packages, most notably Virtual Telecommunications Access Method (VTAM), the mainframe software package for SNA communications.

<span class="mw-page-title-main">VM (operating system)</span> Family of IBM operating systems

VM is a family of IBM virtual machine operating systems used on IBM mainframes System/370, System/390, zSeries, System z and compatible systems, including the Hercules emulator for personal computers.

Interlink Computer Sciences, Inc., of Fremont, California, was a developer of hardware and software that allowed IBM mainframe computers running the MVS operating system to be connected to non-IBM networks.

Remote job entry, or Remote Batch, is the procedure for sending requests for non-interactive data processing tasks (jobs) to mainframe computers from remote workstations, and by extension the process of receiving the output from such jobs at a remote workstation.

<span class="mw-page-title-main">3270 emulator</span>

A 3270 Emulator is a terminal emulator that duplicates the functions of an IBM 3270 mainframe computer terminal on a computer, usually a PC or similar microcomputer.

In computing, Advanced Program to Program Communication or APPC is a protocol which computer programs can use to communicate over a network. APPC is at the application layer in the OSI model, it enables communications between programs on different computers, from portables and workstations to midrange and host computers. APPC is defined as VTAM LU 6.2

<span class="mw-page-title-main">IBM 3705 Communications Controller</span>

The IBM 3705 Communications Controller is a simple computer which attaches to an IBM System/360 or System/370. Its purpose is to connect communication lines to the mainframe channel. It was a first communications controller of the popular IBM 37xx series. It was announced in March 1972. Designed for semiconductor memory which was not ready at the time of announcement, the 3705-I had to use 1.2 microsecond core storage; the later 3705-II uses 1.0 microsecond SRAM. Solid Logic Technology components, similar to those in S/370, were used.

Binary Synchronous Communication is an IBM character-oriented, half-duplex link protocol, announced in 1967 after the introduction of System/360. It replaced the synchronous transmit-receive (STR) protocol used with second generation computers. The intent was that common link management rules could be used with three different character encodings for messages.

IBM Advanced Peer-to-Peer Networking (APPN) is an extension to the Systems Network Architecture (SNA) "that allows large and small computers to communicate as peers across local and wide-area networks."

<span class="mw-page-title-main">IBM TPNS</span> Test automation tool developed by IBM

Teleprocessing Network Simulator (TPNS) is an IBM licensed program, first released in 1976 as a test automation tool to simulate the end-user activity of network terminal(s) to a mainframe computer system, for functional testing, regression testing, system testing, capacity management, benchmarking and stress testing.

<span class="mw-page-title-main">IBM 37xx</span> Series of mainframe communication controllers manufactured by IBM

IBM 37xx is a family of IBM Systems Network Architecture (SNA) programmable communications controllers used mainly in mainframe environments.

The IBM Network Control Program, or NCP, was software that ran on a 37xx communications controller and managed communication with remote devices. NCP provided services comparable to the data link layer and Network Layer functions in the OSI model of a Wide area network.

The IBM 2780 and the IBM 3780 are devices developed by IBM for performing remote job entry (RJE) and other batch functions over telephone lines; they communicate with the mainframe via Binary Synchronous Communications and replaced older terminals using synchronous transmit-receive (STR). In addition, IBM has developed workstation programs for the 1130, 360/20, 2922, System/360 other than 360/20, System/370 and System/3.

<span class="mw-page-title-main">IBM 3745</span>

The IBM 3745 is the latest and last of a 37xx family of communications controllers for the IBM mainframe environment. As of mid-2009 there were an estimated 7,000+ of the larger 3745 models still in active production status, down from 20,000 or more in 2007. The 3745 and associated 3746 models were once heavily used within financial, insurance and retail industries as well as within government agencies globally. However, today most organizations have migrated away from the use of 3745s. IBM's Enterprise Extender and the Communication Controller for Linux on System z (CCL) have largely displaced the older 3745s. IBM announced in September 2002 that it would no longer manufacture new 3745s, but IBM continues to support the hardware by providing worldwide maintenance service, by providing microcode releases and by supporting the associated software including NCP and the virtual telecommunications access method (VTAM). IBM has announced end-of-service dates for Japan, Europe and the Middle East, but has not yet announced end-of-service for the Americas and parts of Asia.

An access method is a function of a mainframe operating system that enables access to data on disk, tape or other external devices. Access methods were present in several mainframe operating systems since the late 1950s, under a variety of names; the name access method was introduced in 1963 in the IBM OS/360 operating system. Access methods provide an application programming interface (API) for programmers to transfer data to or from device, and could be compared to device drivers in non-mainframe operating systems, but typically provide a greater level of functionality.

<span class="mw-page-title-main">IBM 3767</span>

IBM 3767 Communication Terminal is a serial printer terminal that employed dot matrix print-head technology and, for the first time, the Synchronous Data Link Control (SDLC) communications protocol set under IBM's Systems Network Architecture (SNA). It was introduced in 1974 and was used widely during the late 1970s to 1990s, for attachment to IBM System/360 and System/370 mainframe computers and IBM System/7 as an alternative to a 2741 typewriter terminal.

References

  1. ↑ IBM Corporation (2011). ABCs of z/OS System Programming Volume 4 (PDF).
  2. ↑ Frank, Ronald A (October 17, 1973). "IBM Delays Second Virtual TP Release; SD:C Impact Expected". Computerworld. Retrieved June 30, 2020.
  3. ↑ IBM Corporation (8 August 2001). "5735-RC2 IBM Advanced Communication Function for VTAM (ACF/VTAM) V1 R1 for OS/VS". Archived from the original on 2016-03-04. Retrieved June 30, 2020.
  4. ↑ Introduction to Advanced Communications Function (PDF). IBM. May 1979. GC30-3033-1. Archived from the original (PDF) on 2017-11-26.
  5. ↑ Network Program Products: General Information (PDF). IBM. September 1985. GC27-0657-2.
  6. ↑ Introduction to VTAM (PDF). IBM. April 1976. GC27-6987-5.
  7. ↑ "z/OS Communication Server: SNA Network Implementation Guide - Static definition of cross-domain resources". IBM.
  8. ↑ "z/OS Communication Server: SNA Resource Definition Samples - Connecting multiple networks using SNA network interconnection". IBM.
  9. ↑ "Networking on z/OS - Introduction to APPN". IBM.
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.