Announcement Letter Number 290-487 dated September 5, 1990
US - Last Revised on September 5, 1990

Brief Description of Announcement, Charges, and Availability

       IBM MVS/ESA (TM) System Product (MVS/ESA SP) Version 4 and its
associated products are key elements in a set of IBM solutions that
extend the power of MVS/ESA across the enterprise.  Highlights are
Advanced Program-to-Program Communication for MVS (APPC/MVS), Dynamic
Reconfiguration Management, introduction of the MVS systems complex
(sysplex), and new and enhanced systems management solutions.
 (TM) Trademark of International Business Machines Corporation.

Customer Letter Section

The business environment of the 1990s will be characterized by the
integration of information systems into all aspects of the
enterprise.  Today's applications will continue to support the
management and control of the business environment; new application
solutions will provide growth opportunities and competitive
advantages to the companies who implement them.
       The Information Systems (I/S) organization will continue to
support a rapidly growing user population whose jobs and productivity
depend more and more on the ability to access and share information
across multiple locations on diverse systems and networks.
       These factors require systems that have the capability and
flexibility to:
o   Support new applications and requirements across heterogeneous
    hardware and software environments
o   Enable enterprise-wide access to data
o   Grow in range and size with minimal disruption to users and
    application availability
o   Extend over a broader area -- to other floors, buildings, and
    locations, and interconnect to local and wide area networks
o   Manage increasingly large and sophisticated systems cost
    effectively, dynamically, and automatically
       IBM answers these challenges to the MVS customer with today's
announcements:  MVS/ESA SP Version 4, the new ESA/390 (TM)
Architecture, the ES/9000 (TM) and ES/3090-9000T (TM) processors, and
other software products that support the MVS/ESA installation.  The
synergy among today's architecture, hardware, and software
announcements offers MVS customers:
o   New applications opportunities through Systems Application
    Architecture (TM) (SAA (TM)) distributed and cooperative
    processing with APPC/MVS
o   New change and growth capabilities through the Enterprise Systems
    Connection Architecture (TM) (ESCON (TM)) and Dynamic
    Reconfiguration Management
o   New options for availability, growth enablement, and
    manageability with:
    -   The ES/9000 and ES/3090-9000T processors
    -   Introduction of the MVS sysplex (systems complex)
    -   The Processor Resource/Systems Manager (TM) (PR/SM (TM))
        Automatic Reconfiguration Facility
o   Focus on enterprise systems management with:
    -   The introduction of IBM's strategy for systems management:
        the SystemView (TM) structure and products for delivery of
        integrated systems management solutions
    -   New and enhanced products and offerings for operations
        management, performance management, and business
o   Extended options for protecting the security of information
       The MVS functions and products announced today are key
elements in a set of IBM solutions that extend the power of MVS/ESA
across the enterprise, from the workstation to the mainframe, driving
new possibilities in computing.
 (TM) Trademark of International Business Machines Corporation.
The past decade has seen significant workload growth on programmable
workstations, local area networks (LANs), LAN servers, and mid-range
processors, as well as on the mainframe.  The workstation offers the
productivity advantages of flexibility, desktop compute power,
sophisticated graphics, and access to multiple sessions.  The
mainframe, on the other hand, has the advantage of access to
enterprise data, and the attendant facilities for ensuring security,
integrity, and control.
       I/S organizations have begun to leverage the strengths of each
environment by implementing distributed systems and cooperative
processing.  By optimally locating application programs, data, and
presentation services across available resources, I/S can more
effectively support the business objectives of the enterprise.
       Distributed and cooperative processing can extend the value of
current applications by making them available to more users across
the business, and open up possibilities for new business solutions
that are currently too expensive or complicated to implement.
       APPC/MVS, available in MVS/ESA SP Version 4 Release 2, is the
MVS vehicle for cooperative processing in the SAA environment.
APPC/MVS implements the SNA LU6.2/APPC protocol and the SAA Common
Programming Interface -- Communications (CPI-C) to allow programmers
to write MVS applications that can communicate with applications
programs on other platforms in a SNA network.  With APPC/MVS,
workstation application programs will be able to access and use host
services and data, and take advantage of the MVS features of address
space isolation and security in ways not possible in the past.
APPC/MVS will also allow applications to communicate across address
spaces in an MVS system and direct output to the JES2 and JES3 spool.
       Using APPC/MVS services, applications may request connections
and perform program-to-program communications between MVS
applications and applications running on other SAA systems, PC/DOS,
or any other network-connected system supporting the formats and
protocols of SNA LU6.2.  The SAA goals of location transparency and
portability of application programs are supported; applications that
adhere to the SAA interfaces can be re-compiled and, with appropriate
job control language changes, can execute on MVS.  Connectivity
across application environments is provided through callable services
that can be invoked from high-level languages, the Cross System
Product (CSP), or assembler language.
       APPC/MVS applications can directly access MVS/Data Facility
Product (MVS/DFP (TM)) data (for example,  VSAM, QSAM, etc.) and IBM
DATABASE 2 (TM) (DB2 (TM)).  Access to DB2 is through the DB2 call
attachment facility and the DB2 Time Sharing Option (TSO) attachment.
DB2 Version 2 Release 3 introduces a high-level language interface
for the call attachment facility which supports calls directly from
application programs written in PL/I, FORTRAN, OS/VS COBOL, VS COBOL
II, and C.  All releases of DB2 support calls from Assembler H
       APPC/MVS complements and co-exists with the transaction
processing capabilities of CICS/ESA (TM), IMS/ESA (TM) Transaction
Manager, the interactive facilities of TSO/Extensions (TSO/E), and
MVS batch processing.  An APPC/MVS application can use APPC/MVS
services to communicate with applications in the other MVS
environments, specifically CICS/ESA and IMS/ESA Transaction Manager.
This allows development of distributed applications that provide
access to data managed by these other environments.  Using this
technique, access to CICS/ESA data, IMS/ESA DB data, and IBM DB2 data
can be achieved.
       APPC/MVS is designed to handle applications that need to make
extensive use of MVS resources.  Such applications may be
characterized as either compute-intensive, data-intensive, or
communications-intensive.  Examples of this kind of work include
collector applications, in which a job on the host system is
periodically run to capture data on the workstation, distributor
applications, in which the job on the host updates workstation data,
or applications in which multiple data files managed by different
products need to be accessed and correlated.
       An existing TSO/E or batch application may be modified to
employ APPC/MVS, thus enabling new opportunities for enhancing
workstation usage, or implementing applications to assist in the
access, management, and control of information across an enterprise
network.  In addition, many TSO facilities may be used directly by an
APPC/MVS application.
       APPC/MVS will communicate with CICS/ESA and CICS/MVS (TM) (on
the same MVS system or across MVS systems), CICS OS/2 (TM), CICS/VSE
(TM), and CICS/VM (TM).  Communications between APPC/MVS applications
and CICS (TM) transactions can be initiated from either environment.
       The IMS/ESA Transaction Manager Version 3 Release 2 will take
full advantage of the functions and facilities offered by APPC/MVS to
allow IMS/TM applications  access to APPC/MVS services.  New IMS
applications and many existing IMS applications can be supported.

       APPC/MVS will carry the SAA Distributed Data Management (DDM)
architected protocols required for the implementation of distributed
file management and the remote access to data and storage management
components on MVS/ESA systems.
       CSP/Application Development (CSP/AD) and CSP/Application
Execution (CSP/AE), are IBM's application generator for SAA
environments.  CSP/AD Version 3 Release 3 will produce applications
which use APPC/MVS services.
       Connectivity between APPC/MVS applications and VSE
applications is achieved via the CICS/VSE LU6.2 communications
support facilities.
 (TM) Trademark of International Business Machines Corporation.
In today's world, management and expansion of the data center is
sometimes limited by technology.  The static connections between
processors and input/output (I/O) devices, and their attendant bulky
cabling requirements make it expensive, time consuming, and
disruptive to install and modify systems.
       With ESCON and the Dynamic Reconfiguration Management facility
in MVS/ESA Version 4, IBM is providing an integrated solution that
will allow I/S installations to change and grow with minimal
disruption to services and users.
ESCON, a new IBM ESA/390 I/O and interconnection architecture, is
IBM's foundation for system connectivity, extended interconnection
distances, configuration management, and I/O performance.
Architecture, technology, and topology, the cornerstones of ESCON,
are implemented in complementary hardware and software products and
licensed programs that can help an installation achieve new levels of
flexibility and manageability in configuring and updating I/S
resources.  ESCON includes:
o   Fiber optic technology
o   Dynamic connectivity between processors and I/O devices through
    switched point-to-point topology and the ESCON Director
o   The Sysplex (TM) Timer, ESCON Monitor, and ESCON Analyzer
o   The ESCON Manager
       ESCON increases geographic flexibility by allowing  greater
distance between devices and processors, and simplifying additions
and changes to the installation through the need for fewer, smaller,
and lighter cables.  ESCON also allows addition and removal of
processors and control units while the system is running, which
should increase the system availability by eliminating many planned
       Point-to-point topology is achieved with the new ESCON
Director switching units.  Options for locating your equipment are
increased because the ESCON Director reduces the number of
connections required between system resources, and allows I/O devices
to be located up to nine kilometers from the processor.  It may also
be possible to create more effective backup configurations that were
previously too expensive to consider.
       Multisystems operations and serviceability are enhanced by the
new Sysplex Timer and ESCON Analyzer.  The Sysplex Timer is a
table-top unit that synchronizes the time-of-day clocks in up to 16
supported processors or processor sides.  ESCON Analyzer uses a focal
point Personal System/2 (R) (PS/2 (R)) shared by multiple processors
to allow an enterprise to coordinate ESCON link incident reporting,
analysis, and isolation across the ESCON environment.
       New options for automated operations are provided by the ESCON
Monitor and the ESCON Manager licensed programs.  The ESCON Monitor
improves the ability to operate remote systems by providing automatic
remote power on and off and environmental sensing.  The ESCON Manager
is an IBM licensed program that provides host control and
coordination of one or more ESCON Directors.  With ESCON Manager an
enterprise can automate changes to alternate configurations for
backup or test, and coordinate these changes across systems.
       These functions allow for non-disruptive growth, new options
for managing system availability, and new flexibility for locating
the components of the I/S installation and the people who manage and
operate an MVS/JES2 or MVS/JES3 environment.
 (TM) Trademark of International Business Machines Corporation.
 (R) Registered trademark of International Business Machines
Dynamic Reconfiguration Management gives the installation the ability
to change I/O configurations without interrupting system service.
       MVS/ESA SP Version 4 support for Hardware Configuration
Definition (TM) and Dynamic Reconfiguration Management separates the
tasks of configuring and activating the I/O, making these jobs
simpler for the programmer and the operator.
       The Hardware Configuration Definition, introduced in MVS/ESA
SP Version 4 Release 1, enables an I/S organization to interactively
define hardware configurations for MVS operating systems and channel
subsystems.  The Hardware Configuration Definition provides a
panel-driven interface, defaults in the panels, validation checking
during data entry, and online help.  These features simplify the
definition task and shorten the time required to successfully define
and activate an I/O configuration.
       MVS/ESA SP Version 4 Release 2 contains the software support
for Dynamic Reconfiguration Management.  With the ability to
dynamically select a new I/O configuration definition, it may no
longer be necessary to schedule outages for these changes.  It is
possible to add to, delete from, or modify the hardware and software
configuration definition for many devices, control units, and channel
paths without requiring a hardware or software re-initialization: for
example, power-on reset of the hardware or initial program load of
the software.
       MVS/DFP Version 3 Release 3 supports dynamic reconfiguration
management and is the foundation for future Data Facility Storage
Management Subsystem (DFSMS (TM)) enhancements in the MVS/ESA
environment.  Dynamic Reconfiguration Management can be used in
conjunction with DFSMS to facilitate installation of new devices.  An
installation can define storage groups that cause new data to be
allocated and old data to be migrated to the new I/O devices.  Use of
dynamic reconfiguration eliminates the need to shut down the system
while installing the new devices or removing the old ones.
       ACF/VTAM (TM) Version 3 Release 4 works in conjunction with
Dynamic Reconfiguration Management to support the dynamic addition of
communication controllers and SNA cluster controllers to existing
 (TM) Trademark of International Business Machines Corporation.
MVS/ESA SP Version 4 introduces the MVS direction, and delivers the
initial function, for addressing customer requirements for
availability, growth paths, and manageability in multisystems
MVS/ESA SP Version 4 introduces the systems complex (sysplex), the
platform for addressing customer requirements for growth, continuous
availability, multisystems workload balancing, and enterprise-wide
access to data and applications in the MVS/JES2 and MVS/JES3
environments.  The sysplex is a combination of hardware and software
facilities that an installation uses to couple MVS systems together.
A sysplex may be implemented in either single processor or
multi-processor environments.
       In a sysplex, MVS system images and system hardware components
are treated as building blocks which may be replicated.  While an MVS
sysplex could consist of a single MVS system image, a continuously
available sysplex would require the use of two or more MVS images on
two or more central processing complexes (CPCs).  Multiple MVS images
may be achieved on a single CPC or across coupled CPCs in a number of
ways: using PR/SM, using VM on a single CPC, using multiple MVS
systems natively, or combining the preceding configurations.
Additional availability benefits can be achieved when hardware
elements such as processors and channel-to-channel adapters are
       MVS/ESA SP Version 4 and other announcements made today
deliver a number of facilities that begin the evolution of the

o   Improved inter-system communication through the cross system
    coupling facility (XCF)
o   Enhanced global resource serialization and multisystems
o   Improved availability through Dynamic Reconfiguration Management
    and the PR/SM Automatic Reconfiguration Facility's use of XCF
o   A foundation for improved multisystems management with Sysplex
    Timer for time-of-day clock synchronization
o   Improved inter-system connectivity through the ESCON Director,
    ESCON channel-to-channel adapter, and ESCON Manager.
       Benefits of the sysplex are maximized when an installation
utilizes all of the hardware and software elements listed above, but
not all sysplex elements are required to be present.  The initial
implementation of a sysplex could occur on a single CPC with one or
more MVS images, and expanded over time by the addition of new
hardware and software elements.  New levels of hardware and software
can be integrated into an existing sysplex environment, allowing
non-disruptive migration to new functions and technologies.
       As sysplex function evolves, customer requirements will
continue to be addressed by design focus on closer relationships
among MVS systems elements, shared DASD and file sharing, single
system image, and resource serialization.
The introduction of sysplex in MVS/ESA SP Version 4 includes delivery
of the XCF.
       The XCF component of MVS provides a generic set of facilities
that allows programs to communicate information and monitor status
across MVS system images in a sysplex, with improvements in
performance and availability over current solutions.  These coupling
services will evolve to allow an installation to view multiple MVS
systems as a single entity, and will be used by current and future
multisystems applications.
       MVS/ESA SP Version 4 delivers the initial benefits of sysplex
through XCF's use by the PR/SM Automatic Reconfiguration Facility,
global resource serialization, Operations Planning and Control/ESA
(OPC/ESA), and TSO/E, as described in the following sections.
PR/SM, which partitions a processor into multiple logical partitions,
has been enhanced to include an Automatic Reconfiguration Facility
that provides the option of automated restart of a failed production
system based on predefined installation policy.  The installation can
define an alternate MVS system with minimal storage resources that
will use XCF to monitor the production MVS system.  If the production
system partition fails, the alternate partition will automatically
take over its storage resources.  Used in conjunction with the
automated restart mechanisms found in the OPC/ESA and Automated
Operations Control/MVS (AOC/MVS) products, the production environment
could be restarted without operator intervention, with potentially
significant improvements in availability.
OPC/ESA uses XCF to provide automatic restart of OPC/ESA on another
system within the sysplex.  If a system on a sysplex fails and
OPC/ESA is managing the production workload, then the backup OPC/ESA
will automatically recover and restart the work that was running on
the failing system.  Use of XCF provides a potential performance
benefit that will increase availability.
Global resource serialization uses XCF to communicate between the MVS
system images in the sysplex, providing potential performance
improvements.  When all of the systems in a global resource
serialization complex are also in a sysplex, operation and recovery
procedures are simplified, by eliminating operator intervention in
several cases.  For example, a ring can be rebuilt without operator
intervention if a system image fails.
TSO/E uses XCF services to enhance LOGON processing, by reducing
contention for the broadcast data set.  MVS/ESA SP Version  4 uses
XCF services to enable multiple MVS/JES2 systems to be operated from
a single console.
IBM intends to enhance a future version or release of MVS/DFP to use
the cross system coupling facility services provided by MVS/ESA SP
Version 4 to offer improved Partitioned Data Set Extended (PDSE) data
       IBM also intends to enhance CICS/ESA Version 3 by using PR/SM
along with the cross system coupling facility services to reduce
operator intervention at a critical point in the takeover in a XRF
Business in the 1990s will continue to be characterized by rapid
change and a mix of consolidation and decentralization of resources
that presents significant challenges to the I/S organization.  These
factors indicate that the need for a comprehensive approach to
systems management has become imperative.  The systems management
solutions available today have evolved over the years and served
customers well, but tomorrow's solutions require improved user
interfaces, more integration of data and function, and defined
processes to allow automation.
       In response to these requirements, IBM is announcing its
systems management strategy for the planning, coordinating, and
operating of heterogeneous, enterprise-wide information systems.
IBM's systems management strategy consists of the SystemView
structure, which helps users to build consistent systems management
applications and SystemView conforming products.
       The SystemView structure is designed to provide customers with
a consistent user interface, shared data, increased integration, and
enhanced automation among systems management products.  Products
conforming to the SystemView structure together provide management
functions that span information systems resources in SAA systems,
Advanced Interactive Executive (AIX (R)), VSE, and other IBM and
non-IBM environments.
 (R) Registered trademark of International Business Machines
       MVS/ESA is the primary MVS environment for implementing
SystemView structure interfaces and supporting SystemView products.
MVS systems management focuses on integrating and automating the
management of a single system or multiple interconnected systems.
Emphasis is placed on increasing the ability of systems to manage
themselves, to provide consistent end-user interfaces, and to share
systems management data across products and systems throughout the
       Currently there is a rich set of systems management products
for managing host, business administration, network, storage, and
data base resources in the MVS environment.  As relevant existing
products are enhanced and selected new SystemView solutions are
provided in the MVS/ESA systems management area, IBM plans to have
these products conform to the SystemView end-use dimension.
       Today's announcements include significant enhancements to some
of the systems management products that support the SystemView
disciplines of operations, performance, and business administration
in the MVS environment.
Today's announcement of NetView (R) Version 2, IBM's platform for
automation, significantly strengthens the base for future MVS
automation solutions.  NetView continues to provide a single point of
control for enterprise operations management, and now provides users
with a new Graphics Monitor Facility, which utilizes an OS/2
workstation to monitor SNA networks, allowing the operator to view
network status at a glance.  For the MVS environment, the NetView
console provides the operations interface for two recently announced
automated operations products, AOC/MVS and Target System Control
Facility (TSCF).  In conjunction with NetView and OPC/ESA, these
products work together to allow customers to more easily automate the
MVS enterprise and manage multiple systems from a single point of
       AOC/MVS provides the enterprise with drop-in applications for
some of the major components and subsystems in the MVS environment

and a structure for creating automation applications.  It can
simplify the implementation and maintenance of automation procedures
for MVS console automation.  AOC/MVS allows automatic initialization,
start, restart, and shutdown of a system, automation of MVS console
message responses, monitoring of critical resources, and invoking
predefined recovery routines.
       TSCF extends NetView systems operations and automation support
to control and monitor multiple target systems at local or remote
sites from a central controlling system.  An operator can use TSCF to
initialize (IPL), monitor, and restart multiple target systems from
the focal point (or, alternatively, the installation could choose to
automate these tasks using TSCF facilities).  IBM intends that TSCF
will support the ES/9000 processor family, and the Micro Channel (R)
370, as targets.  Once the target systems have been initialized, a
NetView-to-NetView session would be used to monitor and control the
target systems.  As described in the IBM ESCON section of this
overview, this remote operations capability can be extended by using
the ESCON Monitor to power on and off the remote processor and
monitor the environment.  Additional options for automation are
provided by the ESCON Manager, which can automate changes to
alternate system configurations and coordinate these changes across
       OPC/ESA enables you to automate, control and monitor the flow
of the production workload throughout the MVS enterprise.  It
provides comprehensive scheduling services for  automating operator
tasks such as the submission of jobs, and requests to NetView to
enable restart, recovery, or rescheduling of jobs that end in error.
In addition, OPC/ESA enhances the management of MVS systems and helps
maintain high availability through the hot standby recovery function,
which enables transfer of the production workload to another system
within the sysplex, and dynamic workload plan modification in
response to changes in the production environment.
 (R) Registered trademark of International Business Machines
Service Level Reporter (SLR), in conjunction with OPC/ESA, provides
automated reporting on such items as systems availability,
performance/tuning, operations, and network management.  For example,
reports can be produced for DFSMS data migration and end user service
levels within the enterprise.
       Resource Measurement Facility (RMF) Monitor III has been
enhanced with more usable graphics and an auto-refresh function.
The SAA Asset Manager and the SAA Delivery Manager are two of the key
SystemView business administration applications.
       SAA Asset Manager supports the business administration of an
enterprise's hardware, software, and related resources by providing
functions including inventory management, order processing, invoice
processing, and service request handling.  A process manager function
is provided for defining, integrating, automating, and managing
business functions which are called processes.  SAA Asset Manager
supplies an open data base definition to collect enterprise resource
data into a single source of data that can be used by other business
management applications.
       IBM SAA Delivery Manager provides the customer with a flexible
means of customizing, controlling, and delivering programs and files
from a host (System/370 (TM) and System/390 (TM)) to programmable
workstations (IBM OS/2s).  Using IBM SAA Delivery Manager, end users
may select packages to be delivered, installed, and/or updated on
their workstations, or these same activities can be initiated by an
administrator at the host.  IBM SAA Delivery Manager may be used to
manage customer programs and data, IBM licensed programs and other
vendor's programs, information, and other files.
 (TM) Trademark of International Business Machines Corporation.
MVS/ESA, together with Integrated Cryptographic Service Facility/MVS,
RACF, and the Integrated Cryptographic Feature, provide enhanced
cryptographic capabilities for data secrecy, data integrity, and
personal identification.  These facilities will enable the MVS/ESA
customer to further develop a set of business solutions for security.
       Integrated Cryptographic Service Facility/MVS and the
Integrated Cryptographic Feature provide the ability to encipher and
decipher text, translate cipher text, generate and verify message
authentication codes, and support personal identification numbers
(PINs).  These services provide a consistent callable interface with
recently available IBM encryption products in a secure, high-speed
manner for customers requiring cryptography.
o   ACF/VTAM Version 3 Release 4 for MVS/ESA, VM/ESA, and VM/SP
    (Programming Announcement 290-556, dated September 5, 1990)
o   Automated Operations Control/MVS (Programming Announcement
    290-391, dated July 3, 1990)
o   IBM CICS/ESA Version 3 Release 2 (Programming Announcement
    290-520, dated September 5, 1990)
o   IBM CICS/VSE Version 2 Release 1 (Programming Announcement
    290-521, dated September 5, 1990)
o   IMS/ESA Database Manager Version 3 Release 2 (Programming
    Announcement 290-525, dated September 5, 1990)
o   IBM Integrated Cryptographic Feature (Product Announcement
    190-128, dated September 5, 1990)
o   IBM Cross System Product Version 3 Release 3 (Programming
    Announcement 290-213, dated April 24, 1990)
o   ES Connection Monitor System (Product Announcement 190-126, dated
    September 5, 1990)
o   Enterprise Systems Connection Director Model 2 (Product
    Announcement 190-136, dated September 5, 1990)
o   ES Connection Manager Version 1 (Programming Announcement
    290-498, dated September 5, 1990)
o   IBM Enterprise Systems Connection Architecture Overview (Product
    Announcement 190-134, dated September 5, 1990)
o   IBM DATABASE 2 (DB2) Version 2 Release 3 (Programming
    Announcement 290-523, dated September 5, 1990)
o   New IBM Enterprise System/9000 and ES/3090-9000T Water Cooled
    Processor Models and Associated Upgrades (Product Announcement
    190-125, dated September 5, 1990)
o   IBM ES/9000 Model 190, 210, 260, 320, 440 and 480 Processors
    (Product Announcement 190-130, dated September 5, 1990)
o   New IBM ES/9000 Family Model 120, 130, 150, and 170 Processors
    (Product Announcement 190-131, dated September 5, 1990)
o   MVS/Data Facility Product Version 3 Release 3.0 (Programming
    Announcement 290-491, dated September 5, 1990)
o   IBM Operations Planning and Control/ESA Version 1 (Programming
    Announcement 290-543, dated September 5, 1990)
o   IBM SAA Asset Manager/MVS Version 1 (Programming Announcement
    290-542, dated September 5, 1990)
o   IBM SAA Delivery Manager/MVS (Programming Announcement 290-541,
    dated September 5, 1990)
o   IBM SystemView (Programming Announcement 290-539, dated
    September 5, 1990)
o   IBM IMS/ESA Transaction Manager Version 3 Release 2 (Programming
    Announcement 290-519, dated September 5, 1990)
o   Integrated Cryptographic Service Facility/MVS (Programming
    Announcement 290-496, dated September 5, 1990)
o   MVS/ESA SP Version 4 Release 1 (Programming Announcement 290-488,
    dated September 5, 1990)
o   MVS/ESA SP Version 4 Release 2 (Programming Announcement 290-489,
    dated September 5, 1990)
o   NetView Version 2 Release 1 and 2 (Programming Announcement
    290-570, dated September 5, 1990)
o   IBM Sysplex Timer (Product Announcement 190-127, dated
    September 5, 1990)
o   Target System Control Facility (Programming Announcement 290-396,
    dated July 3, 1990)
o   Service Level Reporter Version 3 Release 3 (Programming
    Announcement 290-544, dated September 5, 1990)