5735-RC2 IBM Advanced Communication Function for VTAM (ACF/VTAM) V1 R1 for OS/VS
5735-RC2 IBM Advanced Communication Function for VTAM (ACF/VTAM) V1 R1 for OS/VS
IBM U.S. Product Life Cycle Dates
Program Number
Abstract
Product Positioning
Highlights
Description
Technical Description
Planning Information
Publications
Security, Auditability, and Control
5735-RC2 - ACF/VTAM V1 R1 Encrypt/Decrypt Feature
Abstract
Highlights
Technical Description
Compatibility
Publications
5735-RC2 - ACF/VTAM V1 R2
Abstract
Highlights
Summary and Advantages of ACF/VTAM V1.2
Customer Responsibilities
Operating Environment
Compatibility
Migration and Planning Considerations
Conversion
Performance and Storage Considerations
Publications
5735-RC2 - ACF/VTAM V1 R3
Abstract
Highlights
Summary and Advantages
Operating Environment
Compatibility
Migration and Planning Considerations
Data Security, Auditability, and Control
Performance and Storage Considerations
Program Currency
Publications
MVS System Integrity Applies
Program Marketing Service Replaced
Number VRM Announced Available Withdrawn Discontinued By
5735-RC2 1.00.0 1976/11/09 1978/02/00 1988/05/17 1989/03/16 5665-289
5746-RC3 1.00.0 1976/11/09 1977/12/00 1988/05/17 1989/03/16 -
- 5735-RC2 ACF/VTAM (OS/VS)
- 5746-RC3 ACF/VTAM (DOS/VS)
There Is More Than One Description for This Product
(For IBM US, No Longer Available as of May 17, 1988)
(For IBM US, Program Services Discontinued as of March 16, 1989)
Advanced Communications Function for VTAM Version 1 (ACF/VTAM) is for
users of DOS/VS, OS/VS1, and OS/VS2 (SVS and MVS) that can provide new
capabilities for data communication in a network with a single S/370 or
with multiple S/370s. These capabilities described below are added to
VTAM functions as described in the pages for each SCP (DOS/VS, OS/VS1,
and OS/VS2).
Not available.
Support of communication between two user-written ACF/VTAM application
programs, through record Application Program Interface (API) extensions.
Support of message traffic pacing between application programs, or
inbound from 3770, 3276, 3650, 3601/3602/3694 terminals operating in
SNA/SDLC transmissions mode.
Support of a remote 3705-II Communications Controller with ACF/NCP/VS.
Support of 3705-I and 3705-II multiple channel attachment capabilities
through ACF/NCP/VS.
Expansion of VTAM network operator DISPLAY command to provide more
information about network resources and elements.
Dynamic buffer pool allocation capability.
Designed to run with the latest current level* of NCP/VS as well as
ACF/NCP/VS.
Capability for dynamic collection of tuning statistics.
Extended serviceability through support of the ACF/NCP/VS capability
for concurrent trace of up to eight lines attached to a 3705.
Extended availability through improved switched network backup support
for SNA-SDLC devices.
For all operating systems, execution of ACF/VTAM in a problem program
partition, region or address space, rather than as a system task.
Extended serviceability through improved tracing support under DOS/VS,
equivalent to ACF/VTAM support under OS/VS1, MVS, and SVS.
* Latest current level means that SCP level of VTAM or TCAM or SCP
version of NCP/VS shipped most recently at the time of initial
availability of ACF/VTAM.
Advantages:
Application-to-Application Communication:
Communication between two user-written ACF/VTAM Version 1 applications
offers users greater flexibility to design and implement more efficient
application processing in a network. For example, a single user-written
application may provide centralized processing for other user-written
applications as well as terminal users. This may eliminate duplicate
processing support, and optimize the use of system resources among
multiple application programs.
Inbound Pacing:
Pacing of inbound message traffic for a user application program can
help avoid buffer overrun. ACF/VTAM provides this function as a user-
selectable session establishment function.
Remote 3705-II:
Support of remote 3705-II with ACF/NCP/VS offers the advantages of the
new communications controller capabilities for 3705-II.
Multiple Channel Attachment:
Support of the multiple channel attachment capability of ACF/NCP/VS
expands the sharing capabilities of a 3705-I or a 3705-II. This may
permit more economical use of one communications controller, where a
3705-II can support a maximum of four ACF/VTAM host systems, running
under any combination of DOS/VS or OS/VS operating systems. (Some of the
four may be ACF/TCAM or the latest current level of TCAM 10; one may be
VTAM 2.0.) Also, this sharing capability allows one 3705-1 to support a
maximum of two ACF/VTAM host systems. (One may be ACF/TCAM or VTAM 2.0
or TCAM 10.)
Operator DISPLAY Command:
DISPLAY command capabilities permit a network operator (or programmed
operator application) to obtain more information about the status of
network resources; that is, nodes, lines terminals, logical units,
physical units, application programs, and buffers. Such information may
be useful for status purposes, for performance analysis or to determine
if an action is required for a failing element in the network.
Dynamic Buffer Allocation:
Can dynamically allocate main storage for buffer pools according to
message traffic loads and availability of main storage resources. This
gives the user considerable flexibility to optimize the use of main
storage for buffer pools and determine buffer pool space requirements
that are consistent with throughput and response time.
Tuning Statistics:
A new tuning statistics function permits dynamic accumulation of data
about the I/O interface to a channel-attached communications controller
or a channel-attached 3790. Such data may aid a user in determining and
selecting optimum values for start parameters and network definition.
Multiple Line Trace:
Provides the capability to trace concurrently a maximum of eight lines
with ACF/NCP/VS.
Improved Switched Network Backup:
Improved switched network backup support for SNA-SDLC devices allows
(a) control units associated with a failed or deactivated nonswitched
line to be reactivated through an alternate, switched line, or (b)
terminals associated with a failed or deactivated control unit (switched
or nonswitched) to continue to receive communication support through
reconfiguration to a backup, switched control unit.
VTAM as a User Task:
Permits the operator to unconditionally terminate ACF/VTAM, without
waiting for resources to be released. Upon termination, all system
resources acquired by ACF/VTAM are released, and the partition, region or
address space may be used for other purposes.
Improved Trace Support (DOS/VS):
Permits activity trace records produced by ACF/VTAM (line, buffer, I/O
and tuning statistics trace data) to be written to additional media.
TPRINT:
Improvements include:
- Device SYSLIST output to tape, disk or hardcopy.
- TPRINT as a job step independent of ACF/VTAM, which may be active or
inactive, as well as a subtask under ACF/VTAM.
- Trace and TPRINT failures are isolated from ACF/VTAM, which continues
to operate in the event of such failures.
Multisystem Networking Facility:
The ACF/VTAM Multisystem Networking Facility is a feature for the
ACF/VTAM program product. It extends the capabilities of ACF/VTAM to
support the implementation of intersystem communication among multiple
S/370s operating with DOS/VS, OS/VS1, and/or OS/VS2 (SVS and/or MVS).
The ACF/VTAM Version 1 Multisystem Networking Facility supports cross-
system message routing, through which data may be transmitted across
systems to its destination without host intervention after initial
session establishment.
The ACF/VTAM Multisystem Networking Facility Version 1 can support
cross-system communication for the following types of configurations:
- Multiple S/370 configurations, operating with any combination of
DOS/VS or OS/VS operating systems, where each host processor has a
network controlled by ACF/VTAM with the Multisystem Networking Facility
and ACF/NCP/VS. Optionally, some of the host processors may have
networks controlled by ACF/TCAM with the Multisystem Networking Facility
and ACF/NCP/VS.
- A network controlled by a single S/370 with two access methods,
ACF/VTAM and ACF/TCAM, each with its own Multisystem Networking Facility,
in conjunction with ACF/NCP/VS.
- Combinations of the above types of configurations.
The ACF/VTAM Multisystem Networking Facility, in conjunction with
ACF/NCP/VS, enables the user to have cross-system communications
providing resource sharing, distributed processing and increased resource
availability through the facilities described below:
- Support of communication, via ACF/NCP/VS, between an ACF/VTAM
subsystem or user-written application program on one host system and:
- An SNA-SDLC device controlled by ACF/VTAM Version 1 or ACF/VTAM
Version 2 or ACF/TCAM on a different host system.
- A 3270 BSC device controlled by ACF/VTAM or ACF/TCAM on a different
host system. (Selected 3270 features are supported between ACF/VTAM and
ACF/TCAM host systems, as discussed below under "Planning
Considerations".)
- Support of communications, via ACF/NCP/VS, between an ACF/VTAM user-
written application program on one host system and a corresponding user-
written ACF/VTAM application program, or an ACF/TCAM message handler or
user-written application program on a different host system.
- If the communication links which connect the host system
configurations described above pass through one or more intermediate
system configurations, message traffic can be routed through the local
ACF/NCP/VS of each intermediate S/370 Processor.
- Support of the capability for one ACF/VTAM host system to assume
control of a 3705 with ACF/NCP/VS that is channel-attached to a different
ACF/VTAM (or ACF/TCAM) host that fails or is deactivated. This support
applies between adjacent 3705s with ACF/NCP/VS. Appropriate system
definitions and network operator procedures are required.
- An active 3705 with ACF/NCP/VS and its associated terminals can
continue in an active state without re-IPL, unless it also fails or is
deactivated.
- If the 3705-II with ACF/NCP/VS is to be re-IPLed while its channel-
attached host is unavailable, it must be re-IPLed as a remote
communications controller; however, as a remote communications
controller, communication links to communications controllers other than
its local are not supported.
Ability of a network operator to control (using the VARY command)
which of the applications and terminals controlled by the ACF/VTAM host
are eligible to communicate with applications or terminals controlled by
a different ACF/VTAM (or ACF/TCAM) host system. Also, the operator may
determine (using a DISPLAY command) which terminals and applications are
currently eligible for such cross-system communication.
Ability for testing of links between local 3705s with ACF/NCP/VS.
Support of backup switched or leased SDLC links between local 3705s
with ACF/NCP/VS.
Advantages:
Enhances application processing and screening of information between
multiple S/370 networks. For example, a user-written VTAM application
program may provide processing and data base access on one ACF/VTAM host
on behalf of user-written application programs or terminals on different
ACF/VTAM hosts.
Permits distributed processing and expands resource sharing
capabilities between multiple S/370 networks as well as between a S/370
and a communications subsystem such as the 3790. Permits a wide range of
multiple S/370 configurations to support orderly applications growth with
Systems Network Architecture.
Can minimize redundant network applications.
Permits interconnection of S/370 networks with the complete range of
low-end to high-end processors and virtual operating systems that support
ACF/VTAM or ACF/TCAM.
A communications management configuration permits certain
communications management functions (such as terminal ownership, session
establishment or loading of ACF/NCP/VS) to be consolidated in one of the
processors that are connected by the multiple channel attachment
capability of ACF/NCP/VS and the 3705 Communications Controller.
- Other local processors are freed for applications processing.
- The communications management processor can be backed up by another
local processor.
- Excess capacity in the communication management processor can be used
to run applications.
- Functions such as user-written transaction routing and message
switching applications can be accomplished in the communications
management processor.
Single and Multisystem Considerations:
Communications Controller Support:
ACF/VTAM operates with the following communications controllers:
- 3704 Communications Controller (as supported by the latest current
level of NCP/VS that is available when ACF/VTAM becomes available).
- 3705-I Communications Controller (as supported by ACF/NCP/VS or the
latest current level of NCP/VS that is available when ACF/VTAM becomes
available).
- 3705-II Communications Controller (as supported by ACF/NCP/VS or the
latest current level of NCP/VS that is available when ACF/VTAM becomes
available).
Related IBM Programs:
The following summarizes relationships in a networking environment:
------------------
| | |OS/|OS/|
|DOS/|OS/|VS2|VS2|
|VS |VS1|SVS|MVS|
|---------------------------------------
| x | x | x | x |DB/DC |CICS/VS |ACF/|
| | x | x | x | |IMS/VS |VTAM|
|----|---|---|---|-------|--------| * |
| x | | | |RJE |POWER/VS| |
| | x | | | |JES1/RES| |
| | | | x | |JES2/RJE| |
|----|---|---|---|-------|--------| |
| | | | x |Inter- |TSO | |
| x | x | | x | active|VSPC | |
|----|---|---|---|-------|--------| |
| x | x | x | x |Device |BTP | |
| x | x | x | x |Support|SSS | |
|----|---|---|---|----------------| |
| x | x | x | x |Network | |
| | | | | Operation | |
| | | | | Support Program| |
|----|---|---|---|----------------| |
| x | x | x | x |User | |
| | | | | Application | |
| | | | | Programs | |
----------------------------------------
| * To ACF/VTAM or ACF TCAM devices -- |
| same or different host system. |
| NOTE: Refer to pages on individual |
| system for information on programming|
| for specific SNA (and non-SNA) |
| devices. |
----------------------------------------
Planning Considerations:
Machine and estimated storage requirements are provided in an update
to the "Advanced Communications Function for VTAM General Information
Manual". ACF/VTAM requires the following features in support of the
Compare and Swap instruction: Conditional Swapping (#1051) on 3135;
Advanced Control Program Support (#1001) or Conditional Swapping (#1051)
on the 3145. ACF/VTAM operates in a VM/370 virtual machine which
supports the required release of the operating system (DOS/VS, OS/VS1,
OS/VS2, SVS or MVS). ACF/VTAM operation in a VM/370 environment is
intended for use in program development and testing and other uses where
performance is not critical. Operation of ACF/VTAM under VM/370 Release
3, even with the virtual machine assist feature, may add significant
additional processor overhead. If your customer has specific throughput
or terminal response requirements, you should plan to benchmark under
VM/370 to ensure that any proposed configuration will meet the customer's
performance needs. Each DOS/VS or OS/VS virtual machine in which
ACF/VTAM resides requires a dedicated subchannel address to a 3705-I or
3705-II with ACF/NCP/VS or the latest current level of NCP/VS. Functions
supported by the latest current levels of VTAM and NCP/VS are also
supported by ACF/VTAM and NCP/VS Release 5.0 or ACF/NCP/VS. The
following functions are supported by ACF/VTAM in conjunction with NCP/VS
Release 5.0 or with ACF/NCP/VS:
- Application-to-Application Communication
- Inbound Pacing
- Operator DISPLAY Command
- Dynamic Buffer Allocation
- Tuning Statistics
- Improved Switched Network Backup
- Improved Trace Support
The following functions are supported by ACF/VTAM only in conjunction
with ACF/NCP/VS:
- Remote 3705-II
- Multiple Channel Attachment
- Multiple Line Trace
- Multisystem Networking Facility
In a mixed ACF/VTAM - ACF/TCAM multisystem environment, ACF/VTAM's
ability to access device characteristics of terminals controlled by
ACF/TCAM is limited to those indicators defined and maintained by
ACF/TCAM. In particular, the ability to determine the following 3270
SDLC device characteristics is not supported:
- Whether the device has the selector light-pen feature.
- Whether the device is a printer.
- The physical device address (used in the copy function).
Use of ACF/VTAM requires the concurrent installation of prerequisite
VTAM system control programming (SCP) which will be available concurrent
with ACF/VTAM. This prerequisite SCP should only be installed by
ACF/VTAM users. ACF/VTAM requires the level of Virtual Storage Access
Method (VSAM) that is current at the time ACF/VTAM is made available.
Not available.
Not available.
To install and use ACF/VTAM, Version 1 the customer must:
- Design the single system network.
- Order and install all required communications equipment.
- Have prerequisite VTAM SCP installed.
- Install ACF/VTAM Version 1.
- Define the network to ACF/VTAM.
- Install NCP/VS or ACF/NCP/VS (unless all terminals are local, i.e.,
channel-attached to the host).
- Define the network to NCP/VS or ACF/NCP/VS.
To install and use the Multisystem Networking Facility feature, the
customer must:
- Design the multisystem network.
- Order and install any additional communications equipment (e.g.,
intersystem links between interconnected 3705s).
- Have prerequisite VTAM SCP installed.
- Install ACF/VTAM.
- Install ACF/NCP/VS.
- Install the Multisystem Networking Facility.
- Define the multisystem network to ACF/VTAM and ACF/NCP/VS in each
system.
ACF/VTAM Version 1 retains compatibility with ACF/VTAM Version 2 or
VTAM Level 2. ACF/VTAM offers compatibility with NCP/VS Release 5.0 as
well as with ACF/NCP/VS.
Where related IBM programs (for example, CICS/VS, IMS/VS, POWER/VS,
JES1/RES, JES2/RJE, TSO, VSPC, BTP, and SSS) operate with the latest
current level of VTAM Level 2, compatibility is retained for the level(s)
of those programs that are current at the availability of ACF/VTAM on the
appropriate operating system release. Recompilation of the related IBM
programs is not required.
Most user-written VTAM application programs that use the Application
Program Interface (API) of VTAM Level 2 will continue to operate with
ACF/VTAM without change and without recompilation when operating in a
single domain environment. Possible exceptions to this and other
considerations for moving from VTAM Level 2 to ACF/VTAM are in Appendix D
of the "Advanced Communications Function for VTAM (ACF/VTAM) Conceptual
Planning Manual" (GC38-0282). To take advantage of the multisystem
networking capabilities offered by ACF/VTAM, changes to user programs may
be required.
Program products which run under the control of CICS/OS/VS and/or
CICS/DOS/VS and operate with VTAM and/or TCAM will operate with ACF/VTAM
and/or ACF/TCAM (including the Multisystem Networking Facility). Program
products which do not violate the CICS Macro Interfaces as described in
the sales pages will require no modification to provide equivalent
terminal function under ACF/VTAM and ACF/TCAM to that provided under VTAM
and TCAM. Representative products which have been verified not to
violate these interfaces are:
- Advanced Text Management System II (ATMS II/OS/VS and ATMS II/DOS/VS)
- Display Management System/VS (DMS OS/VS and DMS DOS/VS)
- Planning Control and Decision Evaluation System/Interactive
(PLANCODE/I OS/VS and PLANCODE/I DOS/VS)
- Storage and Information Retrieval System (STAIRS/VS, STAIRS/DOS/VS,
and STAIRS/VS-TLS)
- Alpha Search Inquiry System
- Life Inquiry/Data Entry
- Interactive Training System (ITS)
The design objective for ACF/VTAM record mode path lengths for a
single system environment is approximately equal to that for a VTAM 2.0
environment for the same function. Response times in a multisystem
environment will depend on the number of 3705s with ACF/NCP/VS traversed
and other network load factors. The design objective for ACF/VTAM record
mode for OS/VS and DOS/VS is to have the overall real storage requirement
approximately equal to or less than that of VTAM 2.0. Specific user
storage requirements will be dependent on the specific configuration.
The design objective is to reduce significantly the overall control
block storage requirement per logical unit for OS/VS and DOS/VS. In
addition, the objective is to reduce the fixed storage requirement for
control blocks per logical unit for OS/VS from its current level
(approximately 88 bytes), to a level approaching that currently available
on DOS/VS systems (eight bytes).
The capability provided through the Multisystem Networking Facility to
access any application from any supported terminal offers potential for
storage savings by the elimination of duplicate application programs
among multiple hosts. Final information on path lengths and fixed
storage requirements will be available when ACF/VTAM is available.
- GC30-3033 Introduction to Advanced Communications Function
- GC38-0254 ACF/VTAM General Information Manual
- GC38-0282 ACF/VTAM Concepts and Planning
- GC38-0251 Network Operation Support Program General Information
Manual
Systems Assurance: For ACF/VTAM without the Multisystem Networking
Facility feature - requires a branch Systems Assurance Review prior to
AAS order entry. Contact your regional Systems Assurance representative
to determine if regional participation is required.
When the planned usage of ACF/VTAM includes the Multisystem Networking
Facility, proposal and order entry reviews with regional participation
are required.
Telecommunications Integrity: Provides the capability for an
installation to establish and maintain the integrity of the
telecommunications system. See the appropriate VTAM SCP sales manual
section for detailed information.
IBM Aids: IBM aids can help you prepare and plan for the new Advanced
Communications Function program products.
SNAP/SHOT is capable of modeling the following:
- Up to 100 processors and 100 3705s.
- ACF/VTAM, VTAM, ACF/TCAM, or TCAM.
- The Multisystem Networking Facilities for ACF/VTAM and ACF/TCAM.
- A 3705 attached to multiple processors.
- A 3705 buffer.
- SDLC intersystem links.
The output shows response times of transactions throughout the network
and utilization of network components. This aid is available for
controlled marketing usage through the Raleigh Communications Systems
Analysis Dept. of the Palo Alto/Raleigh Systems Center.
Productivity Aid: TPNS will provide terminal simulation in the
networking environment.
Terminals Supported by ACF/VTAM and the Multisystem Networking
Facility Feature:
ACF/VTAM supports the following listed terminals. Programmable
features which change the control of transmission characteristics and
which are not shown are not supported. Attempts to use ACF/VTAM with
unsupported features can cause unpredictable results.
The user should be aware that many terminal and control unit special
features are transparent to programming and are therefore readily usable
even though not specifically identified. Appropriate line adapters and
hardware attachment features must be included in the system
configuration.
Terminals that are functionally equivalent to those specifically
supported by ACF/VTAM may also function satisfactorily with ACF/VTAM; the
customer is responsible for establishing equivalency. IBM assumes no
responsibility for the impact that any changes to the IBM-supplied
programs or products may have on such terminals.
ACF/VTAM Terminal Support Chart (1):
Single Multi-
System system
S/S Terminals Support Support(3)
1051 X -
2740-1 X -
2740-2 X(5) -
2741-1 X -
3101, as CPT-TWX X(4) -
3232-51 X
3767-1,-2 (2740-1) X -
3767-1,-2,-3 (2740-2) X(5) -
3767-1,-2 (2741) X -
5100 (2741) X -
5110 (2741) X -
6733 (CPT-TWX 33/35)
CMCST (2741) X -
System/7 (2740-1) X -
AT&T 83B3 or WU 115A
line control type X(5) -
CPT-TWX (M33/35)
line control type X(4) -
WT Telegraph X(5) -
BSC Terminals:
2772 X -
2780 X -
2972-8,-11 X -
3271-1,-2 X(5) X(5)
3274-1C,-21C,-31C,-51C
(3271-1,-2) X(5,6) X(5,6)
3275-1,-2 X(5) X(5)
3276-1,2,3,4
(3771,-1,2) X(5,6) X(5,6)
3735 X -
3741-2,-4 X -
3747-1 X -
3771-1,-2,-3 (2772) X -
3773-1,-2,-3 (2772) X -
3773-P1,-P2,-P3(2772) X -
3774-1,-2 (2772) X -
3774-P1,-P2 (2772) X -
3775-1 (2772) X -
3775-P1 (2772) X -
3776-1,-2 (2772/3780) X -
3777-1 (2772/3780) X -
3780 (2772) X -
5275 (3275-1,-2) X(5) X(5)
5285/5288 (3271-2) X(5) X(5)
5937 (3271-1,-2) X(5) X(5)
8100/DPPX (3271) X(5,6) X(5,6)
8100/DPPX/SP (3271) X(5,6) X(5,6)
S/3 X -
System/7 (System/3) X -
System/32 (System/3) X -
System/34 (System/3) X -
System/34 (3271) X(5) X(5)
System/36 (System/3) X -
System/36 (S/360) X(2) -
System/36 3271) X(5) X(5)
System/38 (S/3) X -
System/38 (3271) X(5) X(5)
S/370 (note 2) X -
SDLC Terminals
3271-11,-12 X(5) X(5)
3274-1C,-21C,-31C,-51C
(3791) X(6) X(6)
3275-11,-12 X(5) X(5)
3276-11,12,13,14,
(3791) X(6) X(6)
3601 X X
3602 X X
3614 X(5) X(5)
3624 X(5) X(5)
3631 X(5) X(5)
3632 X(5) X(5)
3661 X(4) X(4)
3694 X X
3767-1,-2,-3 X X
3771-1,-2,-3, X X
3773-1,-2,-3 X X
3773-P1,-P2,-P3 X X
3774-1,-2 X X
3774-P1,-P2 X X
3775-1 X X
3775-P1 X X
3776-1,-2,-3,-4 X(7) X(7)
3777-1,-3,-4 X(7) X(7)
3791 X X
3791/3760 X X
and 3762 X X
5285/5288 (3274-1C) X X
5285/5288 (3770) X X
5520 (3791,3730) X X
8100/DPPX X(6) X(6)
8100/DPPX/SP X(6) X(6)
8775-11,-12
(3274) X(9) X(9)
System/32 (3770) X X
System/34 (3770) X X
System/34 (3791) X X
System/34 (3274) X(5) X(5)
System/36 (3770) X X
System/36 (3791) X X
System/36 (3274) X X
System/38 (3770) X X
Local Terminals:
Channel Attachment Only
3272-1,-2 X -
3274-1A,-21A,-31A
(3791) X -
3274-1B,21B
(3272-1,2) X -
3791 X -
3791/3760 X -
and 3762 X X
4331 Loop Adapter
(3274-1A) X(8) -
Notes: Support provided:
- The terminal type in parentheses designates the programming by
ACF/VTAM, e.g., S/7 (2740-1) means the S/7 is supported as a 2740-1.
- S/370 Models 115-168MP, whether DOS/VS, OS/VS1, or OS/VS2.
- All terminals not supported here, but supported on a single system
can communicate across systems via a user-written application, using
ACF/VTAM's application-to-application communication capability.
- Switched connection only.
- Nonswitched connection only.
- Buffer sizes of 960, 2,560, and 3,440 also supported.
- The 3776-3,-4 and 3777-3,-4 may be half duplex or duplex data
communications. Duplex operation requires PTF 607 or higher for SSP for
ACF/NCP/VS and also requires a PTF for ACF/VTAM. These PTFs will be
incorporated in the following releases:
- SSP for ACF/NCP/VS Release 2
- ACF/VTAM Release 2 on OS/VS1 Release 6.7
- ACF/VTAM Release 2 on OS/VS2 Release 3.8
- ACF/VTAM Release 2 on DOS/VSE
- ACF/VTAM does not support the attachment of the 3644 or 8775 with
Downstream Loadable Functions to the 4331 Loop Adapter Feature.
- 8775 base function only. ACF/VTAM does not support the 8775 with
downstream Loadable Functions.
Not available.
The ACF/VTAM Encrypt/Decrypt Feature is a feature for the ACF/VTAM
program product. It extends the capabilities of ACF/VTAM to support
cryptographic sessions in a single or multiple-domain network operating
with OS/VS1 and/or OS/VS2 (MVS).
- Operates with ACF/VTAM during sessions between a terminal and an
application in a single or multiple system environment, and between
applications in a multiple system environment.
- The ACF/VTAM Encrypt/Decrypt Feature allows the network operator or
installation management to define a logical unit as requiring session
level cryptography.
- Permits single-domain and multiple-domain cryptography.
- Permits encryption and decryption of messages during logical unit to
logical unit sessions. All messages in a session or only selected
messages in a session may be specified as requiring encryption.
- Applications can select encryption on a session basis.
- ACF/VTAM applications generally will not require alteration to run
with the Encrypt/Decrypt Feature. Several new SNA sense codes dealing
with unrecoverable errors associated with the Encrypt/Decrypt Feature
have been introduced. Some application programs may have to be changed
to properly handle these new sense codes.
- Processor requirements are those specified for ACF/VTAM.
- Applications can use the Encryption/Decryption function on sessions
with the following terminals:
- 3276 Control Unit/Display Station Models 11, 12, 13, and 14 with the
Encrypt/Decrypt feature #3680 installed.
- 3776 Communication Terminal Models 3 and 4 and 3777 Communication
Terminal Model 3 with the Encrypt/Decrypt Feature #3680 installed.
- The ACF/VTAM Encrypt/Decrypt feature needs the Programmed
Cryptographic Facility program product (5740-XY5).
- It can be used with OS/VS2 (MVS) Release 3.7 with the following
prerequisite selectable units:
- ACF/VTAM Multisystem Networking Facility feature (SU34) -- Multiple
Domain
- ACF/VTAM program product (SU35) -- Single Domain, Multiple Domain
- ACF/VTAM SCP (SU40) -- Single Domain, Multiple Domain
- It can be used with OS/VS1 Release 6.0 with the following
prerequisite selectable units:
- ACF/VTAM Program Product (SU7) -- Single Domain, Multiple Domain
- ACF/VTAM Multisystem Networking Facility feature (SU8) -- Multiple
Domain
- ACF/VTAM SCP (SU15) -- Single Domain, Multiple Domain
The ACF/VTAM Encrypt/Decrypt feature needs the Advanced Communications
Function for VTAM (ACF/VTAM, 5735-RC2), feature #9001, for both single
and multiple-domain operation. Multiple-domain operation also needs the
ACF/VTAM Multisystem Networking Facility, feature #6009.
ACF/VTAM applications generally will not require alteration to run
with the Encrypt/Decrypt feature. Several new SNA sense codes dealing
with unrecoverable errors associated with the Encrypt/Decrypt feature
have been introduced. Some application programs may have to be changed
to properly handle these new sense codes.
- GC38-0288 ACF/VTAM Encrypt/Decrypt Feature Licensed Program Design
Objectives
- GC38-0285 ACF/VTAM Encrypt/Decrypt Feature Licensed Program
Specifications
- LY27-8024 ACF/VTAM Encrypt/Decrypt Feature Logic (for OS/VS)
Advanced Communications Function for VTAM Version 1 Release 2
(ACF/VTAM R2) is for users of DOS/VSE, OS/VS1 and OS/VS2 (MVS) that can
provide additional capabilities for problem determination, network
operation and data communications in a network with a single host system
or with multiple host systems. ACF/VTAM V1.2 is designed to operate with
ACF/NCP/VS Release 1 or with ACF/NCP/VS Release 2. Some of the
additional capabilities provided by ACF/VTAM R2 are supported only in
conjunction with ACF/NCP/VS R2. A summary of this support appears under
the section entitled "Migration and Planning Considerations".
To support multiple S/370 networks, a user must install the ACF/VTAM
R2 Multisystem Networking Facility feature.
Problem Determination and Network Operation:
Includes additional functions that can assist in optimizing management
and control of a user's data communications installation.
- Enhanced SDLC data link test.
- Terminal connectivity test.
- Intensive mode recording of SDLC data link errors.
- Dynamic display of ACF/NCP/VS storage.
- Dynamic dump of ACF/NCP/VS storage.
- Dynamic reconfiguration of nonswitched SNA-SDLC devices under
ACF/NCP/VS R2.
- Enhanced Network operator control for sessions termination.
- Support of the Network Communications Control Facility (NCCF) program
product and its related Network Problem Determination Application (NPDA)
program product.
- VARY command enhancements.
- Allow the LOGMODE, USS, and INTERPRET tables to reside outside of the
pageable link pack area (PLPA). (OS/VS2 MVS only).
- VTAM Internal Trace enhancements.
- DISPLAY command enhancements.
Additional Data Communication Capabilities:
Include improved flexibility for sessions operations and enhanced
device support.
- Negotiable session initialization parameters.
- Application-to-application parallel sessions.
- Support of selected Start/Stop devices through the Record
Applications Program Interface (API) via the Network Terminal Option
program product.
- Support of the channel-attached 3270 systems and 3790 systems in a
multiple processor network, using the Multisystem Networking Facility
feature.
- Usability enhancements associated with channel-attached device
support.
- Usability enhancements to Unformatted Systems Services (USS).
- ACF/VTAM R1 and R2 supports the 3790 Communication System inbound
message traffic pacing function. (Also supports 8100 and 3730 systems
upon availability.)
VTAM 2.0 and ACF/VTAM V1.1 Compatibility Considerations:
- ACF/VTAM V1.2 supports only record mode operations. It does not
support basic mode operations including the SDLC/BSC path function of
NCP/VS 5.0 and ACF/NCP/VS R1. Support for selected Start/Stop devices is
provided on the Record API by the Network Terminal Option program
product. Other Start/Stop and BSC devices (except BSC 3270) previously
supported by basic mode operations are not directly supported by ACF/VTAM
R2. ACF/NCP/VS R2 provides an interface through which these non-SNA
devices can be supported via user-written NCP code.
- In a multisystem networking environment, message traffic from a
terminal to a target host, or from a host to a terminal, or from one
application program to another application program, can only be routed
through intermediate ACF/NCP/VS systems, not through intermediate host
processors.
Time Sharing Option (TSO) with ACF/VTAM V1.2 (MVS only): Includes new
support for the following products:
- Supports the 2741 Communications Terminal, the Western Union
Teletypewriter Exchange Services (TWX Model 33/35), and the World Trade
Teletypewriter Terminal (WTTY) through the Network Terminal Option
program product.
Problem Determination and Network Operation Functions:
Enhanced SDLC Data Link Test:
Offers the capability to dedicate one station on an SDLC link to
testing while allowing the remaining stations on that link to remain
active. When a station comprises a cluster control unit and its attached
devices, the control unit is dedicated to the test and its attached
devices are deactivated.
Terminal Connectivity Test:
Provides the capability of initiating an echo test from the terminal
end of a session to determine that a terminal and its connection to
ACF/VTAM R2 are functioning properly. The test does not interfere with
other stations on the link or with other devices on the same control
unit.
Intensive Mode Recording of SDLC Data Link Errors:
A network operator can dynamically invoke and terminate recording of
information about temporary errors that may be occurring on an SDLC data
link. This capability supplements existing support that records
permanent error information and permits a user to collect additional
information on SDLC data link errors. This detailed information may
preclude the need for more specific testing to re-create an error.
Dynamic Display of ACF/NCP/VS Storage:
Allows a network operator to display any contiguous 256 bytes of
ACF/NCP/VS storage without disrupting normal ACF/NCP/VS operation. This
display capability, provided in hexadecimal representation on a network
operator console, can be useful in dynamically evaluating network problem
situations.
Dynamic Dump of ACF/NCP/VS Storage:
A network operator can invoke a dump of ACF/NCP/VS R1 or R2 storage
from a channel-attached or SDLC-attached 3705. Since ACF/NCP/VS
continues to operate during the dump process, the dump will represent
ACF/NCP/VS status over a period of time. The dump contents are recorded
and printed via the facilities of the appropriate System Support Program
(SSP) for the ACF/NCP/VS and can be useful in dynamically evaluating
network problem situations.
Dynamic Reconfiguration of Nonswitched SNA-SDLC Devices under
ACF/NCP/VS R2:
Allows the network operator to selectively add or delete supported
nonswitched SNA-SDLC devices, without disrupting other network functions.
The capability supplements the ACF/NCP/VS generation process, and
supports temporary configurations in a non-disruptive fashion until a
permanent network control program generation can be done.
Increased Network Operational Flexibility and Control of Network
Resources:
Via the *VARY operator command, the operator can terminate a specific
session between a network terminal and an ACF/VTAM R2 application program
which may have other terminal sessions in operation at the same time.
This permits a session to be cancelled without interfering with the
remaining sessions or without termination of the application program.
The application program sessions also may be connected to ACF/VTAM or
ACF/TCAM application programs, as well as terminals, on the same host
system or a different host system.
The VARY inactivate command has been enhanced to:
- Allow the specification of an individual application program. This
will result in the automatic scheduling of termination processing for all
network resources associated with the application program's existing
sessions and will deactivate the application program.
- Allow the specification of an application program major node
containing active application programs. This will result in the
automatic scheduling of deactivations for all the active application
programs defined in the major node.
- Allow the specification of an SDLC line which has active terminal
cluster controllers, other than 3705s, attached to it. The terminal
cluster controllers will be automatically scheduled for deactivation and
upon completion, the SDLC line will be deactivated.
The VARY activate command has been enhanced to:
- Provide the Network Operator with a means of applying more consistent
control over the scope of a resource's activation. Prior to ACF/VTAM R2
the activation of a resource's subordinate resources was based on their
initial activation status. With ACF/VTAM R2 the network operator can
specify either that the specific resource, the resource and all its
subordinate resources regardless of initial activation status or the
resource and all its subordinate resources with initial activation status
are to be activated.
- Allow the specification of an individual application program within
an application program major node. This facility enables the network
operator to activate an individual application program that has been
previously deactivated.
The LOGMODE, INTERPRET, and DSS tables may now reside outside of the
pageable link pack area (PLPA) (OS/VS2 MVS only): Moving these tables to
SYS1.VTAMLIB could reduce the user's PLPA requirements and allows the
user to modify the tables without requiring a re-IPL of the operating
system.
VTAM internal trace enhancements: The following serviceability
facilities have been added to the VTAM internal trace capability:
- The ability to terminate or initiate the VTAM Internal Trace facility
at VTAM initialization time.
- The ability to have the VTAM Internal Trace records recorded on an
external file in a DOS/VSE environment. This capability continues to be
available in OS/VS1 and OS/VS2 MVS environments.
- The data formats and contents of certain VTAM Internal Trace records
have been enhanced. For example, the user exit records now contain the
resource names of the session partners.
Display Command Enhancements:
With ACF/VTAM R2, when a network resource is displayed an indication
of its status, as known by ACF/VTAM, is included in the display output.
This information provides both detailed status to the network operator
and serves also as an aid for problem determination. When appropriate,
the resource's status will have an identifier appended to it indicating
that it is either a virtual resource (i.e., a Network Terminal Option
resource) or, has been reconfigured by the Dynamic Reconfiguration
facility or, in the case of network backup, has been acquired from
another host system's domain.
For increased network operator awareness, enhancements have also been
made to the application program and cross domain resource displays. With
ACF/VTAM R2, additional session and resource status information is
included in the display output to aid the network operator in resource
management.
Support of the Network Communications Control Facility (NCCF) Program
Product: ACF/VTAM R2 provides an interface to support the problem
determination and network operation facilities offered by this program
product.
Additional Data Communication Capabilities:
ACF/VTAM R2 can support additional functions and device options that
significantly increase a users capability to transfer and access data in
a single or multiple system environment.
Negotiable Session Initialization Parameters:
Permits increased application program control of sessions between
user-written application programs that reside within a single host system
or across different host systems. During session initialization, two
application programs (via the ACF/VTAM R2 application program macro
interface) can dynamically exchange certain session parameters to
establish and/or modify transmission control and integrity of session
data. With this capability, it may be possible for a user to simplify
the predefined installation of intercommunicating application programs.
Application-to-Application Parallel Sessions:
Adds the flexibility for multiple sessions to operate concurrently
between two user-written application programs that reside within a single
host system or across different host systems.
Network Terminal Option Program Product Support:
Provides support to users that want to move to a SNA data
communications environment while continuing to access the following
non-SNA terminal devices:
- 2740 Communications Terminal Model 1 (nonswitched and switched)
- 2741 Communications Terminal (nonswitched and switched)
- Western Union Teletypewriter Exchange Services (TWX Model 33/35)
Access to these devices is now provided via the ACF/VTAM R2 record
mode operations. ACF/VTAM R2 in conjunction with ACF/NCP/VS R2 permits
these devices to participate in a multisystem as well as a single system
environment.
TSO/VTAM supports the 2741, TWX Model 33/35, and WTTY terminals via
the Network Terminal Option program product concurrent with the
availability of ACF/VTAM R2 for OS/VS2 (MVS).
VSPC R2 supports the IBM 2741 and TWX-33/35 protocols via the Network
Terminal Option program product on OS/VS1 and OS/VS2 on the latest
release of VSPC available.
Channel-attached 3270 System and 3790 System Networking: Permits all
channel-attached 3270 and 3790 systems supported by ACF/VTAM R2 to
participate in multiple system networks.
Channel-attached device support enhancements have been made for both
single and multiple host environments: Assignment of network addresses
for channel-attached devices now comes from the host system's sub-area.
This removes the requirement that channel-attached devices be represented
by their own unique sub-area number. Channel-attached non-SNA 3270
devices may now make use of the USS facilities available to SNA devices.
This will allow for common syntax of USS commands for SNA and non-SNA
channel-attached devices.
Unformatted System Services (USS) Enhancements:
It is now possible to supply to ACF/VTAM R2 a user defined USS message
in excess of 255 characters. This facility could be useful to an
installation wishing to display a full screen (e.g., a company logo) on a
3270 display system prior to USS logon.
The syntax for some of the new ACF/VTAM R2 commands is provided within
USS tables. This provides the capability to alter certain parameters and
defaults by modifying the supplied USS tables. The new commands are:
VARY terminate, the enhanced SDLC data link test, the terminal
connectivity test, the intensive mode recording of SDLC data link errors
and the dynamic display of ACF/NCP/VS storage. This allows an
installation to customize these parameters and defaults to reflect the
installation's requirements.
3790 Inbound Pacing Support:
This facility is supported as a user-selectable session establishment
function under ACF/VTAM R1 and R2. Pacing of inbound message traffic for
a user application program can help avoid buffer overrun. (Also supports
8100 and 3730.)
To install and use ACF/VTAM R2, the customer must:
- Design the single system network.
- Order and install all required communications equipment.
- Have prerequisite VTAM SCP for ACF/VTAM R2 installed.
- Install ACF/VTAM R2, or ACF/VTAM Version 2.
- Define the network to ACF/VTAM R2, or ACF/VTAM Version 2.
* Unless all terminals defined to ACF/VTAM R2 are channel-attached to
the host processor.
To install and use the ACF/VTAM V1.2 Multisystem Networking Facility
feature, the customer must:
- Design the multisystem network.
- Order and install any additional communications equipment, for
example, intersystem links between interconnected 3705s.
- Have prerequisite VTAM SCP for ACF/VTAM V1.2 installed.
- Install ACF/VTAM R2 or ACF/VTAM Version 2.
- Install ACF/NCP/VS R1 and/or ACF/NCP/VS R2.
- Install the ACF/VTAM R2 Multisystem Networking Facility feature or
ACF/VTAM Version 2.
- Define the multisystem network to ACF/VTAM R2 or ACF/VTAM Version 2
and to ACF/NCP/VS R1 and/or ACF/NCP/VS R2 in each host system.
ACF/VTAM V1.2 runs in a virtual storage environment on one of the
following CPUs with the relocation feature:
- Under DOS/VSE: S/370 Models 115, 125, 135, 135-3, 138 145, 145-3,
148, 155II, 158, and 3031.
- Under OS/VS1: S/370 Models 135, 135-3, 138, 145, 145-3, 148, 155II,
158, 158MP, 165II, 168, 168MP, 3031, 3032, and 3033.
ACF/VTAM V1.2 needs one of the following operating systems: DOS/VSE,
OS/VS1, or OS/VS2 (MVS) and all subsequent releases and modifications
unless otherwise stated. The licensed program ACF/VTAM R2 needs the
concurrent installation of prerequisite VTAM SCP for ACF/VTAM R2 system
control programming modules. These system control programming modules
should be installed only by ACF/VTAM R2 users.
ACF/VTAM R2 requires a current level of the Virtual Storage Access
Method (VSAM) if delayed configuration restart will be used.
The ACF/VTAM R2 Multisystem Networking Facility requires the
installation of prerequisite ACF/VTAM R2 system control programming
modules and the licensed program ACF/VTAM R2. The ACF/VTAM R2
Multisystem Networking Facility also requires the use of a 3705-I or
3705-II Communications Controller with the ACF/NCP/VS program product for
cross-domain sessions.
In a mixed ACF/VTAM R2 - ACF/TCAM multisystem environment, ACF/VTAM R2
cannot get from ACF/TCAM the physical device address (used in the copy
function) of an SDLC 3270 device controlled by ACF/VTAM. ACF/VTAM R2,
therefore, cannot provide that physical device address to application
programs.
The Time Sharing Option (TSO) of ACF/VTAM R2 only operates under
OS/VS2 MVS.
ACF/VTAM R2 retains compatibility with ACF/VTAM Version 2 or ACF/VTAM
R1, except as previously stated under "Migration and Planning
Considerations". ACF/VTAM R2 offers compatibility with ACF/NCP/VS R1 and
R2.
Where related IBM programs (for example, CICS/VS, IMS/VS, POWER/VS,
JES1/RES, JES2/RJE, JES2/NJE, JES/RJP, TSO, IIS, VSPC, BTP, SSS, and
NOSP) operate with ACF/VTAM R1 Record Mode, compatibility is retained for
the level(s) of those programs that are current at the availability of
ACF/VTAM R2 on the appropriate operating system release. Recompilation
of the related IBM programs is not required.
Compatibility of the ACF/VTAM R1 or ACF/VTAM Version 2 Record Mode
Application Program Interface (Record API) is retained for existing user
programs that utilize ACF/VTAM R2, except that the SIMLOGON CONALL
function has been changed to operate compatibly with the OPNDST CONALL
function. However, such user programs may require changes to take
advantage of the single and multisystem capabilities offered by ACF/VTAM
R2. TSO/VTAM data editing installation exits may require changes due to
new exit interface parameters.
The ACF/VTAM R2 Multisystem Networking Facility in one domain of a
multiple domain network will operate with another ACF/VTAM Multisystem
Networking Facility or ACF/VTAM Version 2 or an ACF/TCAM Multisystem
Networking Facility in another domain.
The capabilities provided by ACF/VTAM R2 operating in one domain are
limited to the capabilities provided by ACF/VTAM R1, ACF/TCAM R1, and
ACF/TCAM V2.1 when operating in another domain(s). These capabilities
are also limited to the capabilities of ACF/NCP/VS R1 when used in the
same domain or a different domain.
ACF/VTAM R2 with ACF/NCP/VS Considerations: When used only for local
user applications (that is, data communication between two application
programs in the same host system or between a channel-attached terminal
and an application program on the same host system), ACF/VTAM R2 supports
the following items without the need for ACF/NCP/VS or the ACF/VTAM R2
Multisystem Networking Facility feature:
- Enhanced Network Operator control for session termination.
- The NCCF program product.
- Application-to-application parallel sessions.
- Negotiable session initialization parameters.
- 3790 inbound pacing support.
- Terminal connectivity test.
- VARY command enhancements.
- Allow the LOGMODE, USS and INTERPRET tables to reside outside of the
pageable link pack area (PLPA). (OS/VS2 MVS only.)
- VTAM Internal Trace Commands.
- DISPLAY command enhancements.
- Usability enhancements associated with channel-attached device
support.
- Usability enhancements to Unformatted Systems Services (USS).
When used for remote network user applications, ACF/VTAM R2 supports
the following items in conjunction with ACF/NCP/VS R1 or with ACF/NCP/VS
R2:
When used for remote network user applications, ACF/VTAM R2 supports
the following items only in conjunction with ACF/NCP/VS R2:
- Enhanced SDLC data link test.
- Intensive mode recording of SDLC data link errors.
- Dynamic reconfiguration of nonswitched SNA-SDLC devices.
- The Network Terminal Option program product.
Communications Controller Support:
ACF/VTAM R2 operates with the following communications controllers as
supported by ACF/NCP/VS R1 and R2:
- 3705-I Communications Controller
- 3705-II Communications Controller
Multisystem Considerations:
In a multiple host system environment, the ACF/VTAM V1.2 enhancements
are supported for each respective ACF/VTAM V1.2 or ACF/VTAM Version 2
host system just as they are within a single host system environment.
ACF/VTAM R2 supports the following items between ACF/VTAM R2 host
systems or between ACF/VTAM R2 or ACF/VTAM Version 2 or ACF/TCAM V2 host
systems:
ACF/VTAM R2 also supports the following items from an ACF/VTAM R2 host
system when communicating with an ACF/VTAM R1 or ACF/TCAM V1.1 host
system:
- Enhanced Network operator control for session termination. *
- Channel-attached 3270 system and 3790 system networking.
In the above configurations, the appropriate access method features
for multisystem networking must be installed. ACF/TCAM V1.1 host
systems.
Migrating from VTAM 2.0 or ACF/VTAM V1.1 to ACF/VTAM V1.2:
The following migration paths are available for the given levels of
VTAM and ACF/VTAM:
VTAM 2.0 will operate with the following levels of NCP/VS and
ACF/NCP/VS:
- NCP/VS 5.0
- ACF/NCP/VS R1 (with appropriate VTAM 2.0 PTFs)
- ACF/NCP/VS R2 (OS/VS1 and OS/VS2 MVS only with appropriate VTAM 2.0
PTFs)
ACF/VTAM R1 and ACF/VTAM R2 will operate with the following levels of
NCP/VS and ACF/NCP/VS:
- NCP/VS 5.0 (ACF/VTAM R1 only)
- ACF/NCP/VS R1
- ACF/NCP/VS R2 (except ACF/VTAM R1 under OS/VS2 SVS and with
appropriate ACF/VTAM R1 PTFs)
Functions supported by VTAM 2.0 or ACF/VTAM R1 with the appropriate
level of NCP/VS or ACF/NCP/VS are also supported by ACF/VTAM R2 with the
appropriate level of ACF/NCP/VS with the following exceptions:
- OS/VS2 (SVS) is not supported by ACF/VTAM R2 and consideration must
be given to migrating a user's operating system support before or at the
same time as migrating to ACF/VTAM R2.
- Alternatives (such as the Network Terminal Option program product)
must be considered for users that have applications written for the VTAM
2.0 or ACF/VTAM R1 basic mode operations. ACF/VTAM R2 supports only
record mode operations.
- In a multisystem networking environment, message traffic from a
terminal to a target host, or from a host to a terminal or from one
application program to another application program can only be routed
through intermediate ACF/NCP/VS systems, not through intermediate host
processors. Alternatives (such as a 3705-to-3705 SDLC data link) should
be considered for users who route message traffic through intermediate
host processors under ACF/VTAM R1.
Other Considerations:
ACF/VTAM V1.2 requires the following features in support of the
Compare and Swap instruction: Conditional Swapping (#1051) on the 3135;
Advanced Control Program Support (#1001) or Conditional Swapping (#1051)
on the 3145.
ACF/VTAM R2 will operate in a VM/370 virtual machine which supports
the required release of the operating system (DOS/VSE, OS/VS1, OS/VS2
MVS).
ACF/VTAM R2 operation in a VM/370 environment is intended for use in
program development and testing and other uses where performance is not
critical. Operation of ACF/VTAM R2 under VM/370 Release 5, even with the
virtual machine assist feature, may add significant additional processor
overhead. If your customer has specific throughput or terminal response
requirements, you should plan to benchmark under VM/370 to ensure that
any proposed configuration will meet the customer's performance needs.
Each DOS/VSE, OS/VS1, or OS/VS2 (MVS) virtual machine in which
ACF/VTAM R2 resides requires a dedicated sub-channel address to a 3705-I
or 3705-II with ACF/NCP/VS R1 or ACF/NCP/VS R2.
In a mixed ACF/VTAM - ACF/TCAM multisystem environment, the ability of
ACF/VTAM R2 to access device characteristics of terminals controlled by
ACF/TCAM is limited to those indicators defined and maintained by
ACF/TCAM. In particular, the ability to determine the following 3271-11,
-12 and 3275-11, -12 device characteristic is not supported: The
physical device address (used in the copy function).
Machine and storage requirements will be provided in an update to the
"Advanced Communications Function for VTAM (ACF/VTAM) General
Information: Introduction", prior to availability of ACF/VTAM R2 on each
supported operating system. IBM will accept APARs describing any
situation where the installation of ACF/VTAM R2 causes an exposure to the
system integrity of OS/VS2 MVS.
Initially, host computers that are to participate in a multiple-domain
network can be installed separately as single-domain networks, and the
networks can be interconnected later with links between local
communications controllers. This permits an existing network to continue
in operation while the multiple-domain network is being developed. VTAM
and ACF/VTAM application programs that were originally designed to
operate in a single-domain network will continue to operate within an
ACF/VTAM R2 domain of a multiple-domain network, but may need
modification if they are to have sessions with logical units in other
domains.
ACF/VTAM R2 will support ACF/NCP/VS R1 in a 3705-I or 3705-II
Communications Controller. This permits the concurrent or subsequent
installation of ACF/NCP/VS R2 in a 3705-I or 3705-II Communications
Controller.
The design objective for ACF/VTAM R2 record mode path lengths for a
single system environment is approximately equal to an ACF/VTAM R1
environment for the equivalent function. Response time in a multisystem
environment will depend on the number of 3705s with ACF/NCP/VS traversed
and other network load factors. The design objective for ACF/VTAM R2
record mode for OS/VS and DOS/VSE is to have the overall real storage
requirement approximately equal to or less than that of ACF/VTAM R1
record mode. Specific user storage requirements will be dependent on the
specific configuration.
In DOS/VSE, OS/VS1, and OS/VS2 (MVS), the design objective, compared
to ACF/VTAM R1, is to reduce the:
- Overall ACF/VTAM R2 control block storage requirement due to
elimination of the fixed storage requirement (currently 8 bytes) for
control blocks per logical unit.
- Overall ACF/VTAM R2 storage requirement due to elimination of Basic
mode support.
In OS/VS2 (MVS), the design objective, compared to ACF/VTAM R1, is to
achieve reductions in ACF/VTAM R2 usage of OS/VS2 (MVS) common storage as
follows:
- Reduce use of the Pageable Link Pack Area (PLPA) due to elimination
of Basic mode support.
- Significantly reduce use of the Common Service Area (CSA) due to
elimination of certain control blocks and/or movement of other control
blocks from CSA to ACF/VTAM R2 private storage. (The movement from CSA
to private storage may cause re-definition of the region size for
ACF/VTAM R2.) Due to Basic mode removal and/or re-design of the ACF/VTAM
R2 OPEN/CLOSE and VARY components, this design objective includes:
- Movement of the symbol and resource definition tables to ACF/VTAM R2
private storage areas.
- Elimination of the control blocks that represented active and
inactive connections between application programs and between application
programs and network devices.
- Reduced usage of the large pageable pool during network activation.
- Elimination of terminal related fixed storage control blocks that
were used to route Basic mode input data.
Related IBM Programs:
The following summarizes relationships in a networking environment:
DOS/VSE
| OS/VS1
| | OS/VS2 (MVS)
| | |
----------------------------------------
|x |x |x |DB/DC |CICS/VS |ACF/VTAM |
| |x |x | |IMS/VS |R2 * |
|--|--|--|----------|--------| |
|x | | |RJE |POWER/VS| |
| |x | | |JES1/RES| |
| | |x | |JES2/RJE| |
| | |x | |JES2/NJE| |
| | |x | |JES3 | |
|--|--|--|----------|--------| |
| | |x |Inter- |TSO | |
| |x |x | active |VSPC | |
|x |x |x | |IIS | |
| | | | | | |
|--|--|--|----------|--------| |
|x |x |x |Device |BTP | |
| | | | Support | | |
|x |x |x | |SSS | |
|x |x |x | |Network | |
| | | | |Terminal| |
| | | | |Option | |
|x |x |x | |DSX | |
|x |x |x | |PSS/HS | |
|--|--|--|----------|--------| |
|x |x |x |Communi- |NOSP | |
| | | | cation | | |
|x |x |x |Systems |NCCF- | |
| | | | Mgt. | NPDA | |
|--|--|--|-------------------| |
|x |x |x |User Application | |
| | | | Programs | |
----------------------------------------
|* To ACF/VTAM in different host system|
| or ACF/TCAM in same or different |
| host system. See Note below. |
----------------------------------------
Note: See sales manual pages for information on programming support for
specific SNA (and non-SNA devices and other related IBM program
capabilities.
- GC30-3033 Introduction to Advanced Communications Function
- GC27-0462 Advanced Communications Function for VTAM (ACF/VTAM)
General Information: Introduction
- GC27-0463 Advanced Communications Function for VTAM (ACF/VTAM)
General Information: Concepts
- GC27-0457 Advanced Communications Function for VTAM Release 2:
Program Summary
The following terminals have single and multisystem support. The
terminal type in parentheses designates the programming support provided
by ACF/VTAM R2, e.g., S/32 (3770) means the S/32 is supported as a 3770.
Start/Stop Terminals:
(Note 1)
- 2740-1
- 2741 *
- 3101 (Models 10, 12, 13, 20, 22, 23)
- 6733 as CPT-TWX (M33/35)
- CPT-TWX (M33/35) *
- 3232-51 (Model 51)
- WT Telegraph (Note 2) *
- 3271-1, -2 (Note 2) *
- 3274-1C, -21C, -31C, -51C (3271-1, -2) (Note 2, 4) *
- 3275-1, -2 (Note 2) *
- 3276-1, -2, -3, -4 (3271-1, -2) (Note 2, 4) *
- 5285/5288 (3271-2) (Note 2) *
- 5275 (3275-1, -2) (Note 2) *
- 5937 (3271-1, -2) (Note 2) *
- 8100/DPPX (3276-1, -2, -3, -4) (Note 2) *
- 8100/DPPX/SP (3276-1, -2, -3, -4) (Note 2) *
- System/34 (3271) (Note 2) *
- System/36 (3271) (Note 2)
- System/38 (3271) (Note 2) *
- 3232-1 *
- 3271-11, -12 (Note 2) *
- 3274-1C, -21C, -31C, -51C (3791) (Note 2, 4) *
- 3275-11, -12 (Note 2) *
- 3276-1, -2, -3, -4 (3791) (Note 5) *
- 3276-11, -12, -13, -14 (3791) (Note 4) *
- 3601, 3602
- 3614, 3624 (Note 2)
- 3631, 3632 (3601, 3602)
- 3661 (Note 3)
- 3684-1,-2
- 3694
- 3767-1, -2, -3 *
- 3771-1, -2, -3 *
- 3773-1, -2, -3 *
- 3773-P1, -P2, -P3
- 3774-1, -2 *
- 3774-P1, -P2
- 3775-1 *
- 3775-P1
- 3776-1, -2, -3, -4
- 3777-1, -3, -4
- 3791 (Note 6) *
- 3791/3730 (Note 6) *
- 3791/3760
- 4701-1, -2
- 5285/5288 (3274-1C) *
- 5285/5288 (3770)
- 5520 (3791/3730)
- 5937 (3271) (Note 2)
- 6670
- 8100/DPPX (3791) (Note 6) *
- 8100/DPPX/SP (3791) (Note 6) *
- 8100/DPCX (3791) (Note 6) *
- 8775-11,-12 (3274) (Note 8)
- S/32 (3770)
- S/34 (3770) (3791)
- S/34 (3274) (Note 2)
- S/36 (3770)
- S/36 (3791)
- S/36 (3274) *
- S/38 (3770)
- Series/1
Note:
- The Start/Stop Terminals shown are supported only via the Network
Terminal Option program product.
- Nonswitched connection only.
- Switched connection only.
- Buffer sizes of 960, 1920, 2,560, and 3,440 are supported.
- With the SDLC/BSC switch feature set to SDLC.
- TSO support applies only with 3270 Data Stream Compatibility.
- ACF/VTAM does not support the attachment of the 3644 or 8775 with
Downstream Loadable Functions to the 4331 Loop Adapter Feature.
- 8775 base function only. ACF/VTAM does not support the 8775 with
Downstream Loadable Functions.
Advanced Communications Function for VTAM Version 1 Release 3
(ACF/VTAM R3) is for users of DOS/VSE, OS/VS1, and OS/VS2 (MVS) that
offers expanded network configurability, network management capability
and enhanced network recoverability. Multiple system networks require
installation of the ACF/VTAM V1.3 Multisystem Networking Facility (MSNF)
feature.
ACF/VTAM R3 is designed to operate with ACF/NCP/VS Release 2, 2.1, or
3. Some of the capabilities provided by ACF/VTAM R3 are supported only
in conjunction with ACF/NCP/VS R3. A summary of this support appears
later in these pages.
Parallel Links:
Multiple active SDLC links between adjacent 3705s; Parallel Links
allow data traffic to flow simultaneously over two or more SDLC links
between adjacent 3705s. All such links can be operational and in use at
the same time, and each can be activated or deactivated independently of
the others. This capability can provide increased message flow and
improve the availability and reliability of transmissions between 3705s.
Transmission Groups:
Logical groupings of transmission links between adjacent network
nodes. A user may define up to eight Transmission Groups, each with one
or more SDLC links between adjacent 3705s. A Transmission Group permits
multiple SDLC links to be defined as a single logical link. A single
channel between a host and its channel-attached 3705 is also defined as a
Transmission Group. If a link or links in a Transmission Group fails,
session traffic will automatically be placed on remaining active links
without loss of data. This enhances the reliability and availability of
service between 3705s. Multiple Transmission Groups and appropriate
route selection permit a user to specify message traffic for different
applications to flow through a network via preassigned Transmission
Groups. For example, interactive processing may be assigned one group
and batch processing may be assigned a different group, each with its own
physical link support.
Multiple Routes:
Multiple routes for SNA and non-SNA message transmission between nodes
in a network. A user may define up to eight routes for message
transmission between two host systems or between a host system and a
3705. When a session is initiated between two application programs or
between a terminal and an application program, one of the routes is
automatically selected to transmit the session traffic. The user may
limit the selection to a particular route or to one of an ordered
sequence of routes. Thus, it is possible to distribute the traffic for
different sessions to different routes, dividing the load among several
routes. Parallel sessions between two applications can take advantage of
multiple routes so that failure of one route does not disrupt all
sessions.
The ordered sequence of routes, determined by the installation,
defines the set of alternate routes available for session traffic. In
the event a route becomes inoperative during a session, the application
program or terminal may request that the session be re-initiated. This
causes automatic selection of one of the alternate routes. The user can
then re-synchronize the session data traffic and continue data
communications and application processing via network routes that remain
in operation.
Multiple Priority Levels:
Three levels of transmission priority selectable by session. A user
can specify one of three message traffic priorities for a session between
two application programs or between a terminal and an application
program. For example, this permits message traffic for a time-dependent
session to be transmitted through a network ahead of other message
traffic. That is, interactive processing may be given top priority by a
user while other network traffic, such as batch processing, is assigned
to a lower priority by the user.
Extended NCP Interconnection:
New capabilities for interconnecting 3705s in single and multiple
system networks. In ACF/VTAM V1.2, a remote NCP could only be link-
attached via a single link to a single channel-attached 3705. In
ACF/VTAM V1.3, a 3705 may now be link-attached via Transmission Groups to
one or more channel-attached and/or link-attached 3705s.
These capabilities can significantly expand the installation's
configurability options. Also, they can improve the overall efficiency
of the network and improve the ability of a host processor to take over a
3705 whose current owner (or a link to that owner) has failed or has been
deactivated.
See Figure 1 for some examples of interconnection flexibility.
*------* | *------* *------*
| HOST | | | HOST | | HOST |
*------* | *------* *------*
| | | |
*------* | *------* *------*
| NCP | | | NCP |---------| NCP |
*------* | | |---------| |
| | | *------* *------*
| | | |
|/| |/| | |/| |/|
| | | | |
*------* | *------* *------*
| NCP | | | NCP |---------| NCP |
*------* | | |---------| |
| | | *------* *------*
|/| |/| | ---------------------------
| | | *------*
*------* | -----| HOST |-----
| NCP | | | *------* |
*------* | | |
| *------* *------*
| | NCP |---------| NCP |
| | |---------| |
| *------* *------*
| | |
| |/| |/|
| | |
| *---------------------*
| | NCP |
| *---------------------*
---------------------------------------
*------* *------*
| HOST | | HOST |
*------* *------*
| |
*------* *--------*
| NCP |---- | NCP |
*|---|-* | */---/---*
| | | / / |
|/| |/| | /|/ / |
| | |/ / |/|
| | /| /|/ |
| |/ |/ |
| /| /| |
*--|/--|/* | *-----|-*
| NCP | |--------| NCP |
*--------* *-------*
---------------------------------------
*------*
-------| NCP |------
| *------* |
*--------* *--------*
| NCP |---------| NCP |
*--------* *--------*
| |
|/| |/|
| |
*--------* *--------*
| |---------| |
| NCP | | NCP |
| |---------| |
*--------* *--------*
---------------------------------------
Extended NCP Ownership:
As many as eight host systems can share the ownership of an NCP in a
3705 that is channel-attached* and/or link-attached to another 3705(s).
This extends the capability previously provided for sharing channel-
attached 3705s. If one of the host systems fails or gives up control of
the 3705, each of the remaining host systems is notified. This
notification serves as a signal for using the enhanced take-over
capability described below. All host systems that share ownership of an
NCP in a 3705 can also share ownership of SDLC links that connect the
3705 to other 3705s. A shared SDLC link is not deactivated until all
owning host systems give up control of the link. Each of the host
systems is notified if a link that it owns fails, or if the adjacent 3705
becomes inoperative.
* The channel and SDLC link attachments cannot exceed the number of
channels and SDLC links supported by the 3705-I or the 3705-II
communications controllers.
Flow Control:
Enhanced management of network traffic demands; Via SNA protocols, the
flow of message traffic is dynamically regulated between a host system
and a 3705 and between two host systems. Continuous feedback is
exchanged between network resources in order to regulate network traffic
and reduce the possibility of network congestion. When necessary, the
feedback triggers local flow control mechanisms in ACF/VTAM R3.
Applications and local terminals may be temporarily prevented from
introducing more data into a congested network.
Reduced Cross-Domain Resource Definition Requirements:
Requires the MSNF feature. This enhancement is available for both
terminal or application definitions and is requested when the user
defines the host-to-host control session. A terminal in one domain can
request a session with an application program in a different domain
without prior definition of the terminal within the application program's
host. Also, an application in one domain can request a session with an
application program or terminal in a different domain without prior
definition of the requesting application within the cross-domain
application program's or cross-domain terminal's host.
This enhancement is designed to reduce the need for user-specified
cross-domain resource definitions in a multisystem environment and also
to reduce the storage required to support such definitions. It permits
the addition of an application program or terminal to one host system
without the need to redefine other host systems which the resource may
want to enter an SNA session.
Session Outage Notification:
Enhanced awareness of session outages -- If the route supporting a
session becomes inoperative, then, via SNA protocols, the session ends
are made aware of the outage. Session re-initiation may be requested as
described under "Multiple Routes".
Route verification and error notification facilities -- Via the
DISPLAY command, a network operator can determine if a message route
originating in his host is operative or inoperative. This permits a
network operator to verify the availability of network routes and to take
corrective action for routes that may have become inoperative. It also
permits a network operator to verify that a route has been returned to
service following a failure or deactivation. During the verification,
appropriate resource owners are notified when an inactive or failed
resource is encountered on a route. In addition, if during network
operation a route fails, an awareness message is issued at the host
system end point(s), identifying the inoperative route to the network
operator. This permits a network operator to take appropriate action to
minimize the affects of an unusable message route on network
applications.
- Prior to ACF/VTAM Release 3, the ACF/VTAM operator had to issue a
separate command for each node for which a trace was to be initiated or
terminated. With ACF/VTAM Release 3, the ACF/VTAM operator can initiate
and terminate buffer and I/O traces for a node and all its sub-nodes with
a single ACF/VTAM operator command. This capability could reduce the
ACF/VTAM operator actions required to gather problem determination
information.
- Provides VTAM Internal Trace (VIT) enhancements. The Path
Information Unit (PIU) VIT entry has been enhanced to include traces of
System Services Control Point (SSCP) SNA sessions. The sessions being
traced are those between the SSCP and application programs, the ACF/VTAM
operator services component, and the ACF/VTAM host physical unit services
component. This additional problem determination information should be
useful in diagnosing problems where the SSCP is believed to be in error.
All VIT entries containing the same problem determination data have
been reformatted to have this data at a consistent location in each of
the different entry types. These reformatted entries should improve the
usability and readability of the entries and thus reduce the time
necessary to analyze them.
The VIT SNAP entry type has been enhanced to allow for 64 bytes of
problem determination data to be contained in the entry, thus allowing
additional information to be collected. The current length of 32 bytes
continues to be supported.
A new VIT option, CIO, has been added which provides trace entries of
ACF/VTAM channel I/O operations. The entries contain information about
start I/O conditions, channel interrupts and error recovery procedure
events. These additional entries should be useful in isolating a problem
to either an ACF/VTAM error or an error with a host processor's channel
equipment.
- Provides the capability to initiate and terminate a Generalized Trace
Facility (GTF) trace for individual ACF/VTAM user sessions (OS/VS2 (MVS)
only).
- Transmission Group Trace extends the existing SDLC line trace
capabilities to Transmission Groups. Via the ACF/VTAM operator MODIFY
command, the SNA headers of message traffic over a Transmission Group
between two IBM 3705 communications controllers can be traced as if it
were a single SDLC line.
To aid in diagnosing network problems, ACF/VTAM Release 3 provides:
- The capability for the ACF/VTAM operator to specify a time interval
after which notification will be given of ACF/VTAM operations that have
been pending completion for longer than the specified time interval. The
notification will identify the particular operation by its name and by
the origin and destination network names or addresses. The internal
ACF/VTAM event identifier will also be displayed. The ACF/VTAM operator
also has the capability to modify the time interval.
- The capability to have the last five characters of the issuing
ACF/VTAM module name appear in an ACF/VTAM operator message. If this
option is specified, the module name information will be inserted between
the message identification number and the first character of text of each
ACF/VTAM operator message. Requesting this additional information may
cause the ending text of some ACF/VTAM messages to be truncated and not
displayed.
- Operator notification when, in a multisystem networking environment,
a request for a cross-domain session fails because of one of the
following:
- Notification to the system operator when an insufficient storage
condition exists. The message will contain the buffer pool experiencing
the problem or, as appropriate to the operating system, the operating
system subpool from which the storage was requested.
- TSO/VTAM is enhanced to allow installations to specify whether data
is to be treated as 'confidential text' or not. Data not to be treated
as confidential text remains unaltered in the ACF/VTAM buffers and may
aid in problem determination.
Device Support Extensions and Network Operation
Enhancements:
In OS/VS1, ACF/VTAM Release 3 extends device support for the
Downstream Load Utility program product for 3644 Automatic Data Units
(ADU) and 8775 Display Terminals.
- For OS/VS1, ACF/VTAM Release 3 provides support of the Downstream
Load Utility program product to permit the operation of 8775s with
Advanced Functions when attached via an SDLC line to a 3705
Communications Controller operating with ACF/NCP/VS.
ACF/VTAM has been enhanced to support SNA Notify:
- ACF/VTAM application programs that use the queuing facility of the
ACF/VTAM SIMLOGON macro instruction may take advantage of SNA Notify to
acquire terminals as they are powered on without operator intervention at
the application program. This improved operational efficiency is
supported by 3270 display stations and printers attached to the 3274
Model 1A and Models 1C and 51C when communicating with hosts via SDLC
links. The 3274 support is contained in Configuration Support B (#9111)
and Configuration Support C (#9112).
Device support extensions to permit dynamic exit and re-entry to the
network:
- When devices are engaged primarily in tasks unrelated to
communications, network communication is a small percentage of the
device's use. ACF/VTAM Release 3 permits this type of device (e.g., the
System/34), operating on nonswitched SDLC lines, to disconnect and
reconnect to the network without requiring ACF/VTAM operator
intervention.
Ability to display a TSO/VTAM userid (OS/VS2 (MVS) only):
- Prior to ACF/VTAM Release 3, the ACF/VTAM operator had to enter
multiple Display commands to associate a TSO user with a specific
terminal. ACF/VTAM Release 3 provides the ACF/VTAM operator with a new
Display command option which provides for the specification of a TSO user
identification. The output of the display will contain:
- An indication that this is a TSO userid display.
- The application name (for example, TSO0005).
- The terminal name (for example, SNA3270B) associated with the
specified userid.
- The status as known by ACF/VTAM of both the application and the
terminal.
- An indication as to whether the TSO/VTAM GTF trace is in effect for
this TSO userid.
Ability to specify an Unformatted System Services (USS) table
containing installation-customized ACF/VTAM commands:
- ACF/VTAM Release 2 and ACF/VTAM Release 3 contain newly implemented
ACF/VTAM operator commands which can be customized via USS. Prior to
ACF/VTAM Release 3, these customized commands had to be placed in the
ACF/VTAM-defined default USS table. To improve the usability of this
facility and allow migration of existing customized commands, ACF/VTAM
Release 3 permits specification of an installation-defined USS table via
the START command. ACF/VTAM searches this installation-defined table
prior to searching the IBM-defined default table for ACF/VTAM operator
commands. Thus, if during testing of customized commands an error is
detected, an installation need only restart ACF/VTAM and eliminate the
specification of the USS table in error.
In OS/VS systems, the amount of private area storage ACF/VTAM may
allocate from an application program can be limited:
- Prior to ACF/VTAM Release 3, if an application program had not
requested to receive data from ACF/VTAM but data arrived for the
application program, ACF/VTAM would allocate as much storage as needed
from the application's private area to queue the data. This ACF/VTAM
Release 3 facility allows an installation, when defining an application
program, to limit the amount of private area storage ACF/VTAM may request
to queue this data.
Reliability and Availability Enhancements for OS/VS2 (MVS):
Capability to have an application program span multiple address
spaces:
- ACF/VTAM has been enhanced to permit application program interface
(API) requests from a single application program to originate from
different address spaces and to reference a single application program
access method control block (ACB). This multiple address space facility
can provide application programs with enhanced capabilities for error
isolation and session protection. This capability will also allow
application program design flexibility by permitting individual sessions
to be assigned to their own address space while being allowed to
reference a single ACB. Improved operation may also be achieved by
grouping sessions with similar characteristics or functions to be
performed in one address space.
New levels of error isolation:
Extensions to the OS/VS2 (MVS) authorized path mode of operation for
additional ACF/VTAM application program interface (API) macro
instructions and exit routines:
Support of Release 2 of the Network Terminal Option (NTO) program
product: ACF/VTAM R3 will support the devices and capabilities of
Release 2 of NTO.
NLDM Program Product: The NLDM program product, which runs as an
application on NCCF, is supported in OS/VS2 MVS environments. ACF/VTAM
will accept requests from NLDM to capture session initiation/termination
data from all resources it controls and to continuously trace data
passing between selected network resources. The session data and trace
data are sent to the NLDM application, where they are correlated to
assist in performing session-level problem determination.
3274-1A and 3274-1C/SNA Inbound Pacing: Inbound pacing is supported
under ACF/VTAM R2 and R3 for the 3274-1A and 3274-1C/SNA. These products
must be at the appropriate EC level to provide this function.
Serviceability Enhancements:
The following ACF/VTAM R2 serviceability enhancements continue to be
supported by ACF/VTAM R3:
- The ability to terminate or initiate the VTAM Internal Trace facility
at VTAM initialization time.
- The ability to have the VTAM Internal Trace records recorded on an
external file in a DOS/VSE environment. This capability continues to be
available in OS/VS1 and OS/VS2 MVS environments.
- The data format and contents of certain VTAM Internal Trace records
have been enhanced. For example, the user exit records now contain the
resource name instead of the address of the resource name.
ACF/VTAM R3 supports the following CCITT X.21 switched functions when
attached to an X.21 Interface via the 3705-II:
- Address calling
- Auto Answer
- Call progress signal
- Direct call
- Closed User Groups
- Abbreviated Address Calling
Systems Assurance: Regional Systems Assurance Reviews are required
for ACF/VTAM. DP/NSD Systems Center participation is required when the
planned usage of this product includes the Multisystem Networking
Facility feature.
Communications Controller Support:
ACF/VTAM R3 operates with the following communications controllers as
supported by the level or levels of ACF/NCP/VS that are current when
ACF/VTAM R3 becomes available:
- 3705-I Communications Controller
- 3705-II Communications Controller
ACF/VTAM R3 requires the following features in support of the Compare
and Swap instruction: Conditional Swapping (#1051) on the 3135; Advanced
Control Program Support (#1001) or Conditional Swapping (#1051) on the
3145.
ACF/VTAM R3 also requires the CPU to support the Set PSW Key from
Address (SPKA) instruction. This instruction is not supported on S/370
Models 115 and 125.
System Configuration:
ACF/VTAM R3 runs in a virtual storage environment in any system
configuration that supports a DOS/VSE, OS/VS1, or OS/VS2 (MVS) operating
system as specified in the "SCP" section.
ACF/VTAM R3 needs one of the following operating systems: DOS/VSE
with the VSE/AF licensed program, OS/VS1, OS/VS2 (MVS) and all subsequent
releases and modifications unless otherwise stated. The licensed program
ACF/VTAM R3 needs the concurrent installation of prerequisite VTAM SCP
for ACF/VTAM R3 system control programming modules. These system control
programming modules should be installed only by ACF/VTAM R3 users.
Software Configuration: ACF/VTAM R3 requires one of the following
operating systems at the specified level or subsequent levels unless
otherwise specified:
- DOS/VSE with the VSE/Advanced Function (VSE/AF) licensed product
- OS/VS1 Release 7.0
- OS/VS2 (MVS) Release 3.8
If delayed configuration restart will be used, ACF/VTAM R3 requires a
current level of Virtual Storage Access Method (VSAM).
ACF/VTAM R3 will operate in a VM/370 virtual machine which supports
the required release of the operating system (DOS/VSE, OS/VS1, OS/VS2
(MVS)). VM/370 provides a means of supporting VTAM and TCAM systems in
the same processor, each running in its own virtual machine. This
facility can be helpful when changing VTAM releases and when testing the
ACF/VTAM Multisystem Networking Facility feature. Operation of ACF/VTAM
R3 under VM/370, even with the virtual machine assist feature, may add
additional processor overhead which should be considered in your review
of the customer's performance needs.
Each DOS/VSE, OS/VS1 or OS/VS2 (MVS) virtual machine in which ACF/VTAM
R3 resides requires a dedicated sub-channel address to a 3705-I or
3705-II with ACF/NCP/VS R1, ACF/NCP/VS R2 or ACF/NCP/VS R3.
Corequisite: Use of ACF/VTAM R3 requires the concurrent installation
of corequisite VTAM system control programming (SCP) modules.
Other Considerations:
In a mixed ACF/VTAM - ACF/TCAM multisystem environment, the ability of
ACF/VTAM R3 to access device characteristics of terminals controlled by
ACF/TCAM is limited to those indicators defined and maintained by
ACF/TCAM. In particular, the ability to determine the physical device
address of a 3271-11, -12 used in the copy function is not supported.
CICS/VS Intersystem Communication - Message Performance
Option:
The ISC Message Performance Option is designed for transaction
switching between CICS/VS systems and is invoked by specifying a new
parameter on the START command and by appropriately defining the terminal
control table. Increased performance is achieved by eliminating certain
CICS/VS-generated control sequences that are normally exchanged between
two CICS/VS systems. The application designer is given the option of
increased performance as a trade-off against certain aspects of data
integrity.
As is the case today, the START command is used to generate an
asynchronous transaction. Recoverable resources are still protected
within each transaction, however, there is no communication at SYNCHPOINT
time with the transaction.
ISC Message Performance option will be of particular value in those
cases where the terminal operators are interested in making an inquiry-
only (i.e., no resources are updated) and in getting an answer in the
quickest possible time. If no answer is received after a certain time,
the inquiry is considered lost and is retried. Thus, CICS/VS is not
required to provide any recovery capability in the event of a failure,
either of the line or the system; the operator provides all the recovery
necessary, namely re-issuing the original request.
CICS/VS VTAM Dynamic Close Support:
The VTAM Dynamic Close Support being provided by CICS/VS is in
response to the user requirements to have the ability to continue
execution of CICS/VS even though the VTAM network is being shut down.
This support is complementary to the CICS/VS V1.4.0 support of Dynamic
Open. Together, they allow CICS/VS and VTAM to be initialized, run and
terminated independently of each other.
Dynamic close may be invoked either by issuing a CICS/VS Master
Terminal command or a VTAM Halt command (normal, quick or cancel).
Dynamic close results in the termination of all CICS/VS sessions with
VTAM. This may be achieved in two ways:
- Through an orderly Dynamic Close.
- Through a quick Dynamic Close.
An orderly close will wait for transaction termination on all CICS/VS
sessions and then issue a CLSDST against each active session before
issuing a VTAM CLOSE ACB macro. A quick close will abnormally terminate
all transactions currently in session with VTAM before issuing a CLOSE
ACB macro.
Parallel Sessions:
CICS/VS will support the Parallel Session capability for communication
between inter-connected CICS/VS systems. This can offer system
throughput enhancements by permitting more than one transaction to
concurrently access resources on a remote CICS/VS system. The maximum
number of concurrent transactions is governed by the number of available
parallel sessions.
Where related IBM programs (for example, CICS/VS, IMS/VS, POWER/VS,
JES1/RES, JES2/RJE, JES2/NJE, JES3/RJP, TSO, IIS, VSPC, BTP, SSS, and
NCCF) operate with the ACF/VTAM R2 Record Mode Interface, compatibility
is retained for the level(s) of those programs that are current at the
availability of ACF/VTAM R3 or ACF/VTAM Version 2 on the appropriate
operating system release. Recompilation of the related IBM programs is
not required.
Compatibility with the ACF/VTAM R2 Record Mode Application Program
Interface (Record API) is retained for existing user programs that
utilize ACF/VTAM R3. However, such user programs may require changes to
take advantage of the single and multisystem capabilities offered by
ACF/VTAM R3 or ACF/VTAM Version 2.
By the enhancements made in ACF/VTAM R3 in support of Parallel Links,
Multiple Routes and Extended NCP Interconnection, minor operational
differences do, however, exist with VTAM Level 2, ACF/VTAM R1, and
ACF/VTAM R2.
ACF/VTAM V1.3 with ACF/NCP/VS Considerations:
The following ACF/VTAM V1.3 enhancements are supported only in
conjunction with ACF/NCP/VS R3:
- Parallel Links
- Transmission Groups
- Multiple Routes
- Multiple Priority Levels
- Extended NCP Interconnection
- Extended NCP Ownership
- Flow Control
- Session Outage Notification
- Enhanced Recovery Capabilities*
- Route Verification and Error Notification Facilities
- Transmission Group Trace
- Support of Release 2 of the Network Terminal Option program product
- Support of the CCITT X.21 Switched Interface
ACF/VTAM V1.3 with ACF/NCP/VS Release 2 or 2.1 continues support of
NTO Release 1.
In addition to being supported with ACF/NCP/VS Release 3, the
following ACF/VTAM Version 1 Release 3 enhancements are supported with
ACF/NCP/VS Release 2 or 2.1:
- Reduced cross-domain resource definition requirements.
- Problem determination and serviceability enhancements.
- Device support extensions and network operation enhancements.
- Reliability and availability enhancements.
NCP/VS Version 5 and ACF/NCP/VS Release 1 are not supported with
ACF/VTAM Release 3. All facilities provided by NOSP are now available
with the Network Communications Control Facility (NCCF) program product,
which operates on ACF/VTAM Release 3. The VTAM-NCP support table that
follows lists the releases of each product through which SSCP-PU,
SSCP-LU, and LU-LU sessions are supported. It can be used to plan
migration from previous releases of VTAM to ACF/VTAM V1.3.
------------------------------
|NCPs |NCP5|V1 |V1 |V1 |V1.3|
| | |R1 |R2 |R2.1|(7) |
| | | | |(7) | |
|-----|----|---|---|----|----|
|VTAMs| | | | | |
|-----|----|---|---|----|----|
|VTAM2|yes |yes|yes|yes |no |
| | |(1)|(2)|(2) | |
|V1.1 |yes |yes|yes|yes |yes |
| | | |3,4|3,4 |(6) |
|V1.2 |no |yes|yes|yes |yes |
|V1.3 |no |no |yes|yes |yes |
|(10) | | |(5)|(5) | |
------------------------------
----------------------------
|NCPs |V2 |V2 |V3 |V3 |
|-----|----|----|----|-----|
|VTAMs|3705|3725|3705|3725 |
|-----|----|----|----|-----|
|VTAM2|no |no |no |no |
|V1.1 |no |no |no |no |
|V1.2 |no |no |no |no |
|V1.3 |yes |yes |yes |yes |
|(10) | |(8) |(9) |(8,9)|
----------------------------
Note:
- With applicable VTAM Level 2 PTFs.
- OS/VS only, with applicable VTAM Level 2 PTFs:
- OS/VS1: UX14242.
- OS/VS2 (MVS): UZ28810.
- Not supported on VSE.
- With applicable ACF/VTAM V1.1 PTFs:
- DOS/VS Release 34: UD17664.
- OS/VS1: UX14243.
- OS/VS2 (MVS): UZ28811.
- With applicable ACF/NCP/VS V1.2 or V1.2.1 PTFs when connected to
ACF/NCP/VS V1.3 or later.
- OS/VS only, with applicable ACF/VTAM V1.1 PTFs:
- OS/VS1: UX14243.
- OS/VS2 (MVS): UZ28811.
- With EREP PTFs for Link Problem Determination Aid (LPDA) level
maintenance data records.
- OS/VS2 (MVS) only, with ACF/VTAM V1.3 PTFs UZ90205, UZ90206, UZ90207,
and UZ90208. (ACF/VTAM V1.3 for OS/VS1 and DOS/VS does not support
sessions with ACF/NCP for the 3725.)
- With applicable ACF/VTAM V1.3 PTFs:
- OS/VS2 (MVS): UZ62633.
- OS/VS1: UX18990.
- DOS/VS: UD26545.
- With ACF/VTAM V1.3 PTF when the network contains any ACF/VTAM V2.2 or
ACF/NCP/VS node(s):
- OS/VS2 (MVS): UZ56422.
- OS/VS1: UX17328.
- DOS/VS: UD23966.
Note: The above matrix assumes that customers will be at current access
method maintenance levels when migrating from one NCP release to another.
Refer to the "Compatibility" section which follows for the operational
characteristic differences between ACF/VTAM R3 and VTAM Level 2, ACF/VTAM
R1 and ACF/VTAM R2.
Multisystem Considerations:
In a multiple host system environment:
- The ACF/VTAM R3 enhancements are supported for each respective
ACF/VTAM Version 2 or ACF/VTAM R3 host system.
- An ACF/VTAM R3 host system can coexist with ACF/VTAM Version 2 or
ACF/VTAM R1, ACF/VTAM R2, ACF/VTAME, ACF/TCAM V1.1, ACF/TCAM V2.1,
ACF/TCAM V2.2 and/or ACF/TCAM V2.3 host systems at the level of function
supported by these host systems and the intermediate NCPs.
Security features available with previous releases, such as
Encrypt/Decrypt, continue to be supported by ACF/VTAM R3. User
management is responsible for the selection, adequacy and implementation
of these features and the appropriate application and administration
control.
Machine and storage requirements will be provided in the "Advanced
Communications Function for VTAM (ACF/VTAM) Installation" manual at the
availability of ACF/VTAM R3 on each supported operating system.
Optionally, additional storage must be allocated in OS/VS2 MVS
environments when the NLDM program product is installed. This storage
requirement is dependent on the number of size of NLDM trace buffers
selected.
The planned design of ACF/VTAM Release 3 indicates that, due to the
ACF/VTAM R3 enhancements, the ACF/VTAM R3 path lengths, real storage
requirements, control block storage requirements, overall storage
requirements and the OS/VS2 (MVS) Common Area storage requirements may
increase compared to ACF/VTAM Release 2. The actual performance impact
(if any) to a customer will vary depending upon his particular hardware
and network configuration. IBM aids such as SNAP/SHOT should be used to
assess individual customer performance capability and storage
requirements.
Related IBM Programs:
The following summarizes relationships:
OS/VSE with VSE/AF
| OS/VS1
| | OS/VS2 (MVS)
| | |
----------------------------------------
|x |x |x |DB/DC |CICS/VS | ACF |
|--|--|--| |-------------| VTAM|
| |x |x | |IMS/VS | R3 |
|--|--|--|---------|-------------| * |
|x | | |Job |POWER/VS | |
|--|--|--|Entry |-------------| |
| |x | | |JES1/RES | |
|--|--|--| |-------------| |
| | |x | |JES2/RJE | |
|--|--|--| |-------------| |
| | |x | |JES2/NJE | |
|--|--|--| |-------------| |
| | |x | |JES3/RJP | |
|--|--|--|---------|-------------| |
| | |x |Inter- |TSO | |
|--|--|--| active |-------------| |
| |x |x | |VSPC | |
|--|--|--| |-------------| |
| |x |x | |IIS | |
|--|--|--|---------|-------------| |
|x |x |x |Device |BTP | |
|--|--|--|Support |-------------| |
|x |x |x | |SSS | |
|--|--|--| |-------------| |
|x |x |x | |NTO | |
|--|--|--| |-------------| |
|x |x |x | |DSX | |
|--|--|--| |-------------| |
|x |x |x | |Host | |
| | | | |Command | |
| | | | |Facility | |
|--|--|--| |-------------| |
| | | | |Programmable | |
|x |x |x | |Store System | |
| | | | |Host Support | |
|--|--|--|---------|-------------| |
| | | |Communi- | | |
|x |x |x | cation |NCCF | |
| | | |Network | | |
|--|--|--|Mgmt. |-------------| |
|x |x |x | |NPDA | |
|--|--|--| |-------------| |
|x | |x | |Information/ | |
| | | | | System | |
|--|--|--| |-------------| |
| | |x | |NLDM (VTAM | |
| | | | | PTF Req'd) | |
|--|--|--|---------|-------------| |
| | | |User | | |
|x |x |x |Appl. | | |
| | | |Progs. | | |
----------------------------------------
|* To ACF/VTAM in different host system|
| or ACF/TCAM in same or different |
| system (see Note below). |
----------------------------------------
Note: Non-SNA device support (other than 3270) is provided only
through the Network Terminal Option program product, or through user-
written code which uses the ACF/NCP/VS attachment facility.
The levels of VTAM and ACF/VTAM currently supported on the various
levels of the operating systems are listed below:
Programming support for OS/VS1 Release 6.7 and OS/VS2 (MVS) Release
3.7 operating system releases was withdrawn effective December 31, 1980.
The programming support for DOS/VS Release 34 was withdrawn March 31,
1981.
Programming support for the current levels of VTAM and ACF/VTAM is
being withdrawn on the following schedule:
- OS/VS2 (MVS) Release 3.7 -- December 31, 1980
- DOS/VS Release 34 -- March 31, 1981
- OS/VS1 Release 6.7 -- December 31, 1980
- OS/VS1 Release 7 -- March 31, 1982
- OS/VS2 (MVS) Release 3.7 -- December 31, 1980
- OS/VS2 (MVS) Release 3.8 -- not established
- DOS/VS Release 34:
- SCP -- March 31, 1981
- BASE and MSNF Feature -- March 31, 1981
- OS/VS1 Release 6.7:
- SCP -- December 31, 1980
- BASE, MSNF and Encrypt/Decrypt Features -- September 30, 1981
- OS/VS1 Release 7:
- SCP -- September 30, 1981
- BASE, MSNF and Encrypt/Decrypt Features -- September 30, 1981
- OS/VS2 (MVS) Release 3.7:
- SCP -- December 31, 1980
- BASE, MSNF and Encrypt/Decrypt Features -- September 30, 1981
- OS/VS2 (MVS) Release 3.8
- SCP -- September 30, 1981
- BASE, MSNF and Encrypt/Decrypt Features -- September 30 1981
- The VSE System:
- SCP -- December 31, 1982
- BASE and MSNF Feature -- December 31, 1982
- OS/VS1 Release 6.7:
- SCP -- December 31, 1980
- BASE, MSNF and Encrypt/Decrypt Features -- December 31, 1982
- OS/VS1 Release 7:
- SCP -- December 31, 1982
- BASE, MSNF and Encrypt/Decrypt Features -- December 31, 1982
- OS/VS2 (MVS) Release 3.8:
- SCP -- December 31, 1982
- BASE, MSNF and Encrypt/Decrypt Features -- December 31, 1982
- GC30-3033 Introduction to Advanced Communications Function
- GC27-0462 Advanced Communications Function for VTAM (ACF/VTAM)
General Information: Introduction
- GC27-0457 ACF/VTAM Program Summary
- ACF/VTAM Licensed Program Specifications
The following terminals have single and multisystem support. The
terminal type in parentheses designates the programming support provided
by ACF/VTAM R3, e.g., S/32 (3770) means the S/32 is supported as a 3770.
Start/Stop Terminals:
(Note 1)
- 2740-1
- 2741 *
- 3101, as CPT-TWX (M33/35)
- 3232-51 as CPT-TWX (Model 33/35)
- 6733 as CPT-TWX (M33/35)
- CPT-TWX (M33/35) *
- WT Telegraph *
- 3271-1, -2 (Note 2) *
- 3274-1C,-21C,-31C,-51C,(3271-1, -2) (Notes 2, 4) *
- 3275-1, -2 (Note 2) *
- 3276-1, -2, -3, -4 (3271-1, -2) (Notes 2, 4) *
- 3780 (Notes 2, 8) *
- 4730-F01, -R01, -F02, -R02, -F11, -R11, -F12, -R12, -F51, -R51, -F52,
-R52 (Note 2)
- 5275 (3275-1, -2) (Note 2) *
- 5937 (3271-1, -2) (Note 2) *
- 8100/DPPX (3276-1, -2, -3, -4) (Note 2) *
- 8100/DPPX (3276-1, -2, -3, -4) (Note 2) *
- System/36 (3271) (Note 2) *
- 3232-1 *
- 3271-11, -12 (Note 2) *
- 3274-1C,-21C,-31C,-51C (3791) (Notes 2, 4) *
- 3275-11, -12 (Note 2) *
- 3276-1, -2, -3, -4 (3791) (Note 5) *
- 3276-11, -12, -13, -14 (3791) (Note 4) *
- 3601, 3602
- 3614, 3624 (Note 2)
- 3631, 3632 (3601, 3602)
- 3661 (Note 3)
- 3684
- 3694
- 3767-1, -2, -3 *
- 3771-1, -2, -3 *
- 3773-1, -2, -3 *
- 3773-P1, -P2 -P3
- 3774-1, -2 *
- 3774-P1, -P2
- 3775-1 *
- 3775-P1
- 3776-1, -2, -3, -4
- 3777-1, -3, -4
- 3791 (Note 6)
- 3791/3730 (Note 6) *
- 3791/3760
- 4701-1,-2
- 4730-F01, -R01, -F02, -R02, -F11, -R11, -F12, -R12, -F51, -R51, -F52,
-R52 (Note 2)
- 4736-RH2, -RS2, -R02
- 5285/5288 (3770)
- 5520 (3791/3730)
- 5937 (3271) (Note 2)
- 6670
- 8100/DPPX (3791) (Note 6) *
- 8100/DPPX/SP (3791) (Note 6) *
- 8100/DPCX (3791) (Note 6) *
- 8775-11, -12 (3274) (Note 7)
- System/32 (3770)
- System/34 (3770) (3791)
- System/36 (3770)
- System/36 (3791)
- System/36 (3274) *
- System/38 (3770)
- System/38 (3274)
- Series/1
Note:
- The Start/Stop Terminals shown are supported only via the Network
Terminal Option (NTO) program product.
- Nonswitched connection only.
- Switched connection only.
- Buffer sizes of 960, 1920, 2,560, and 3,440 are supported.
- With the SDLC/BSC switch feature set to SDLC.
- TSO support applies only with 3270 Data Stream compatibility.
- For OS/VS1, ACF/VTAM Release 3 supports the IBM 8775 with Downstream
Loadable Functions. ACF/VTAM R3 on VSE and OS/VS2 (MVS) for the 8775 is
for base function only.
- Supported only via the Network Terminal Option R2 (NTO) program
product.
Yes.
IBM will accept APARs describing any situation where the installation
of ACF/VTAM R3 causes an exposure to the system integrity of OS/VS2
(MVS).
(R), (TM), * Trademark or registered trademark of
International Business Machines Corporation.
** Company, product, or service name may be a trademark
or service mark of others.
|
