IBM OS/390 User Manual
Chapter 9. Telecommunications Subsystems
VSE and OS/390 platforms rely on the same set of communications products and
protocols. Although the product sets are the same, some differences exist in
product implementation and usage. The differences are primarily related to the
operating systems and their file structures. This chapter will discuss the
similarities and differences between VSE and OS/390 environments for the
following telecommunications products:
protocols. Although the product sets are the same, some differences exist in
product implementation and usage. The differences are primarily related to the
operating systems and their file structures. This chapter will discuss the
similarities and differences between VSE and OS/390 environments for the
following telecommunications products:
•
9.1, ACF/VTAM
•
9.2, ACF/NCP
•
9.3, BTAM
•
9.4, Migrating TCP/IP
•
9.5, MQSeries
9.1 ACF/VTAM
The most recent release of VTAM for OS/390 is VTAM Version 4 Release 4.1.
However, this product is not available separately and is packaged together with
TCP/IP as the OS/390 eNetwork Communications Server Release 5.
However, this product is not available separately and is packaged together with
TCP/IP as the OS/390 eNetwork Communications Server Release 5.
Previous
releases of VTAM up to Version 4 Release 4 were available as a stand-alone
product, 5695-117. At the time of writing, supported releases of VTAM for VSE
include Version 3 Release 4 and Version 4 Release 2.
product, 5695-117. At the time of writing, supported releases of VTAM for VSE
include Version 3 Release 4 and Version 4 Release 2.
The functions of VTAM for OS/390 are, with one major exception, a superset of
the functions of VTAM for VSE. The main differences are related to those
between the operating systems, rather than to any differences in the way that
SNA networks are defined and configured. However, OS/390 does not provide a
facility such as the VSE Interactive Interface (II) to guide you through SNA
resource definitions. You must code new network resource definitions from
scratch, although you should be able to use most of your existing VSE definitions
without change. The exception would be the definition of new resources required
for networking configuration changes associated with the migration project.
the functions of VTAM for VSE. The main differences are related to those
between the operating systems, rather than to any differences in the way that
SNA networks are defined and configured. However, OS/390 does not provide a
facility such as the VSE Interactive Interface (II) to guide you through SNA
resource definitions. You must code new network resource definitions from
scratch, although you should be able to use most of your existing VSE definitions
without change. The exception would be the definition of new resources required
for networking configuration changes associated with the migration project.
The following subsections summarize the tasks you will have to perform to
install and set up an OS/390 VTAM system. For further details we recommend
the following product manuals (those quoted are for Communications Server for
OS/390 Release 5):
install and set up an OS/390 VTAM system. For further details we recommend
the following product manuals (those quoted are for Communications Server for
OS/390 Release 5):
•
eNetwork Communications Server for OS/390 Installation and Migration
Guide, SC31-8622
Guide, SC31-8622
•
eNetwork Communications Server for OS/390 Network Implementation Guide,
SC31-8563
SC31-8563
•
eNetwork Communications Server for OS/390 Resource Definition Reference,
SC31-8565
SC31-8565
•
eNetwork Communications Server for OS/390 Resource Definition Samples,
SC31-8566
SC31-8566
•
eNetwork Communications Server for OS/390 Programming, SC31-8573
•
eNetwork Communications Server for OS/390 Customization, LY43-0110
Copyright IBM Corp. 1998
185