TME 10 NetView for OS/390: End-to-End Network Management

Software Announcement
March 25, 1997
Announcement Letter Number: 297-083


Table of Contents:



At a Glance

TME 10 NetView for OS/390 (NetView for OS/390) combines the power of three key management products to deliver a single, integrated, and enhanced product that provides comprehensive network computing management. NetView for OS/390 provides:

  • Network and system information to aid in quickly analyzing and resolving network computing problems
  • Policy-driven, production-ready network automation to enhance problem resolution
  • Dynamic topology and status across the enterprise for SNA and/or non-SNA resources
  • Bidirectional management capability between S/390 and distributed environments when implemented with TME 10 Global Enterprise Manager
  • Object level security for NetView Graphic Monitor Facility (NGMF) views
  • Year 2000 support to protect your vital resource from turn-of-the-century impacts
  • Full-screen automation
-----------------------------------------
For ordering, contact:
  Your IBM representative, an IBM
  Business Partner, or IBM North America
  Sales Centers at
    800-IBM-CALL  Reference: YE010



Overview

TME 10 (R) NetView (R) for OS/390 (TM) (NetView for OS/390) provides integrated management of the networks and systems across your enterprise. This improves network efficiency and increases system availability, enabling you to reduce the overall cost of systems management. NetView for OS/390 puts the information you need in front of you with the tools and power to make a difference.

NetView for OS/390 combines the powerful functions of Tivoli's S/390 (R)-based network management products, IBM NetView for MVS/ESA (TM) (NetView), IBM NetView MultiSystem Manager (MultiSystem Manager), and IBM Automated Operations Network/MVS (R) (AON/MVS), into a single integrated product with enhanced functionality and performance improvements. By merging the management tools customers need into a single product, NetView for OS/390 provides comprehensive network computing management.

With its strategic functions and Year 2000 support, NetView for OS/390 provides the management basis that businesses need in order to use network computing as a competitive advantage today and in the future. NetView for OS/390 provides integrated, comprehensive, enterprise-wide management at significant savings over individual point product solutions.

NetView for OS/390 provides:

  • Management of a heterogeneous network environment.
  • Views of the network's health at a single glance.
  • The ability to manage failed resources directly through exception views.
  • Extensive drop-in network automation capabilities.
  • Extensible support in both automation and topology discovery.
  • Dynamic topology and status information to NetView's Resource Object Data Manager (RODM) in real time for both distributed and host resources.
  • Collection of non-SNA topology data from an expanding array of platforms and the automatic population of the centralized RODM.
  • Improved usability, including enhanced NetView for OS/390 help and browse.
  • Language Environment (R) for MVS and VM (LE/370) support.
NetView for OS/390 offers three packaging options to provide cost-competitive and simplified ordering:
  • The Unattended Option
  • The Procedural Option
  • The Graphical Enterprise Option



Intended Customers

Customers needing to centrally manage their network computing resources from a single product can use NetView for OS/390 to enable management and automation of both SNA and non-SNA resources, regardless of where they reside in the enterprise.



Key Prerequisites

The minimal level of some of the major prerequisites include:

  • IBM MVS/ESA V5R1.1
  • ACF/VTAM (R) V4R3 for MVS/ESA (ACF/VTAM (R) V4R4 required for HPR support)
  • IBM OS/2 (R) Warp V3
  • IBM Language Environment for MVS & VM (LE/370) R5 or IBM C/370 (TM) Compiler and Library V2 and IBM OS PL/I V2R3
  • IBM Resource Access Control Facility (RACF (TM)) V2R1 for NGMF view security or its SAF equivalent



Planned Availability Date

  • March 28, 1997 (English and Japanese)

------------------------------

This announcement is provided for your information only. For additional information, contact your IBM representative, call 800-IBM-4YOU, or visit the IBM home page at: http://www.ibm.com



DESCRIPTION

TME 10 NetView for OS/390 (NetView for OS/390) is a key component of IBM's network and systems management solutions. Using NetView for OS/390, you can centrally manage the systems and networks in complex distributed environments easily and reliably.

The NetView for OS/390 product is an integral part of IBM's Tivoli Management Environment (R). The TME (R) environment provides a comprehensive set of tools for maintaining complex, multivendor networks and systems from a single point of control. Coupled with TME 10 Global Enterprise Manager, NetView for OS/390 is uniquely positioned to provide the cornerstone that enables bidirectional management between the host and distributed environments.

NetView for OS/390 can help improve your network efficiency, increase system availability, and reduce your overall cost of systems management. With NetView for OS/390, one operator can monitor all of your network and system resources from a single display. NetView for OS/390 lets you automate many of your network and systems operations tasks, improving the reliability and effectiveness of the systems and networks throughout your business.

TME 10 NetView for OS/390 combines the functions of IBM NetView Version 3 for MVS/ESA, IBM NetView MultiSystem Manager Version 2 for MVS/ESA, and IBM SystemView (R) Automated Operations Network/MVS into a single, integrated product. Each of these components is described in the following sections which highlight the new and expanded functions being delivered. A more detailed description can be found in the Supplemental Information section.

TME 10 NetView for OS/390 positions customers for the future by providing Year 2000 support to protect from turn-of-the-century impacts. It also provides support to run your own high-level language (HLL) command processors and installation exits using the AD/Cycle (R) compilers and libraries. Existing PL/I and C/370 applications can be relinked with the AD/Cycle library and Language Environment/370 (LE/370), and run without modification.

NetView for OS/390 offers these three packaging options to provide cost competitive and simplified ordering:

  • The Unattended Option: The automation and management capabilities needed to enable lights-out management from a centrally-located staff; no end-user interface is supported
  • The Procedural Option: Includes the Unattended Option functions with expanded management and automation capabilities including the Automated Operations Network component without the graphical interfaces and without topology management support
  • The Graphical Enterprise Option: Full-function TME 10 NetView for OS/390, providing all the management and automation functions including the NetView Graphic Monitor Facility (NGMF), the MultiSystem Manager component, and the Automated Operations Network component



Systems and Network Management: Integrated NetView Component

Highlights of the expanded function, improved performance, and enhanced usability and installation functions for the NetView component follow.

  • The Resource Utilization Management function enables you to prioritize, monitor, and control essential system resource usage by NetView tasks.

  • Enhancements to Automation Capabilities:
    • VSAM Access for REXX procedures
    • Full-screen Automation
    • PIPE Enhancements
    • REXX Enhancements
  • SNA Topology Manager (SNATM) enhancements in storage, serviceability, availability, and recoverability
    • Virtual storage required by SNATM has been significantly reduced.
    • A storage shortage causes SNATM to terminate only the responsible command, not the entire task.
    • New support for internal trace buffer and increased granularity for trace data collection is available.
    • New NetView for OS/390 samples are available to help you customize SNATM views.
  • Enhancements to NetView Sysplex Support now provide cloning support and automatic restart manager (ARM) support.

  • Enhanced End-to-end Management Support for APPN (R) Technologies: The session monitor now supports High-Performance Routing (HPR) and Multi-Node Persistent Sessions (MNPS).

  • Expanded support for LE/370

  • Usability and Functionality Enhancements to NetView GMF, including Support for Session Data

  • Ability to Dynamically Control Access to Resources: NetView for OS/390's span of control function is now dynamic and independent of VTAMLST. It supports both SNA and non-SNA resources, as well as NGMF views, and allows the use of wildcard characters in resource and view names.

  • Security Enhancements were made to NGMF Views so that NGMF views and resources within views can be restricted to operators authorized to see them.

  • Ability to Run Multiple NetView for OS/390 Graphical Enterprise Options on One MVS Image is offered.

  • The Hardware Monitor alert wrap count has been increased to 9999.

  • Performance and Serviceability Enhancements to RODM:
    • Improved locking structure, virtually eliminating deadlocks
    • Significantly improved RODM performance
    • Less storage required for objects
  • Performance and Serviceability Enhancements to GMFHS: Trace data from the GMFHS can be sent to the GTF, eliminating the need to recycle GMFHS to see logged trace entries.

  • Enhanced NetView for OS/390 Help Facility
    • Message and Command Help Information
    • Updated and restructured NetView Help Desk
    • Message and command help is now stored as members of a partitioned data set. NetView for OS/390 no longer uses VSAM files for this.
  • Improved Log Browse Response Time and Functional Enhancements

    Two new log browse facility commands:

    • LOCATE -- Allows you to position your log browse display to a given record number or date and time.
    • ALL -- Allows you to display either a subset or all of the records in the log.
    Also, when you enter the BROWSE command, all of the most recent records are automatically displayed. The BLOG command shipped as a sample in previous releases. It is now a fully-supported command.

  • Installation Enhancements: The NetView Installation and Administration Facility/2 (NIAF/2) is a workstation-based tool that allows users to install the NetView for OS/390 program and perform administrative tasks. NIAF/2 also allows users to maintain a current level of the NetView for OS/390 program.

  • Enhancements to Installation Exits
    • A new exit allows more granular processing of NetView session awareness (SAW) records.
    • The DSIEX17 installation exit now gives you additional choices for automating action messages and DOM (delete operator message) signals.
    • The new LOADEXIT statement has been added to DSIDMN to allow you to load installation exits selectively.
  • Support for Internationalized Date and Time Formats: New parameters allow you to customize the long and short formats for dates and times displayed in many host NetView for OS/390 functions.

    Note: This customization support is not uniform throughout all components of NetView for OS/390. However, most host NetView components, including the ones listed here, will support your specified customization parameters:

    • Host-based screen displays for major components, such as the session monitor, status monitor, hardware monitor, and command facility
    • All host NetView component commands
    • All host NetView component messages



Non-SNA Management: Integrated MultiSystem Manager Component

The MultiSystem Manager product has been integrated into NetView for OS/390. It provides the management support for a wide range of heterogeneous networks and can provide dynamic topology discovery and status of non-SNA resources. Its expanded function now supports all of the following types of networks:

  • IBM OS/2 LAN Network Manager (LNM) networks
  • Novell NetWare networks
  • IBM LAN NetView Management Utilities (LMU) networks
  • Internet Protocol (IP) networks using IBM NetView for AIX (R)
  • NetFinity (R) networks
  • Asynchronous Transfer Mode (ATM) networks using IBM Nways (TM) Campus Manager for AIX
The MultiSystem Manager component also includes the Open Topology Interface. When used in conjunction with an Open Topology Agent, the Open Topology Manager provides the basis to manage any resource in your network. By using the Open Topology Interface, any agent provider can populate the Resource Object Data Manager (RODM) with resources, enabling graphical display of the status and topology of those resources.

Using the Open Topology Interface, along with the topology features for managing LAN physical media, NetWare servers and requesters, IP resources, LMU resources, NetFinity resources, and ATM resources, NetView for OS/390 provides you with a unique opportunity to manage the diverse resources in your network from a single NetView Graphic Monitor Facility screen.

Customers who wish to manage additional resources from an MVS application can take advantage of MultiSystem Manager Access, a REXX interface to RODM.

Managing your network resources from the host with the MultiSystem Manager component of NetView for OS/390 provides value in the following areas.

  • Correlation of all resources that may affect the network.

  • Improved centralized control by dynamically collecting, storing, and updating resource topology and status data in RODM for use by NGMF.

  • Customized views created with the BLDVIEWS utility are easy to understand, allowing operators to focus on failing resources quickly.

  • Improved operator productivity in using the MultiSystem Manager-provided Command Tree/2 command sets. This allows the operations staff to issue object-specific commands to system resources using point-and-click technology.

  • Increased operations effectiveness through easy isolation of problem sources detected by different agents.

  • Enhanced automated operations since topology and status updates are received by NetView for OS/390 and automatically stored in RODM. This enables resource topology and status information to be automated using NetView for OS/390 and RODM automation techniques.
The MultiSystem Manager component includes the following new functions.
  • Management of ATM and NetFinity resources from NGMF has been centralized. ATM and NetFinity resources are dynamically discovered by MultiSystem Manager and stored in RODM.

  • Improved performance for the discovery and update process for resources managed by an open-topology agent.

  • Improved performance in exception view processing, RODM access, and alert processing.

  • NetView for OS/390 sample CNMSJH12 can now be used to load the MultiSystem Manager data model as well as the GMFHS/SNA Topology Manager data model. This provides a faster, simpler way to load the data models.

  • NetView for OS/390 span of control enhancements have been enabled for MultiSystem Manager views.

  • The LAN Network Manager (LNM) feature has been enhanced to discover and display remote and parallel bridges.

  • GETTOPO command processing has been enhanced so your BLDVIEWS customization is no longer affected by rediscovery of resources in your network.

  • Additional relationships are now discovered between resources managed by different agents. Existing topology correlation by LAN MAC address has been expanded to also discover when resources on the same workstation share the same TCP/IP address.

  • Correlation is now faster, can be customized, and provides additional information about correlated resources. Operators can now diagnose complex problems more easily.



Automation: Integrated AON/MVS Component

The Automated Operations Network/MVS product has been integrated into TME 10 NetView for OS/390. The Automated Operations Network (AON) component enables you to implement network automation without writing procedures, yet it can be easily extended to meet your unique networking requirements. It enhances the network management function provided by the NetView component by providing cost-effective, automated network operations facilities. These facilities improve controls, which enhance operator productivity and network availability.

The AON component provides a single, integrated, automated solution for diverse environments, including SNA, TCP/IP, VTAM Subarea, X.25, APPN, and token-ring LANs. It provides the drop-in automation policy and routines necessary to automate network recovery and increase availability of your network. The drop-in automation policy can be easily extended to suit your environment.

The AON base toolkit also allows you to leverage IBM's overall automation knowledge if you choose to write your own automation routines. For example, by using AON's threshold correlation routines, you can leverage AON's base toolkit to get your own automation up and running more quickly.

Highlights of the expanded function, improved performance, and enhanced usability and installation include the following.

  • Automation performance is improved.

  • VTAM messages handling is enhanced.

  • AON will now set the RODM "Automation In Progress" status so NGMF operators can quickly determine when automation is already handling a resource outage.

  • Security authorization on the commands sent to LAN Network Manager (LNM): Any command sent can be restricted from use by any operator you specify.

  • More than two auto-tasks can now be specified for SNA automation and AON message processing to improve overall system performance.

  • A new option in the AON trace facility allows you to turn off tracing altogether, reducing overhead and improving performance. A trace can easily be enabled from the AON operator interface when needed.

  • The NCP Recovery function supports using the NCP load module name or PU name during the recovery processes.

  • You can decide whether NCPs are status-checked during AON initialization, and you can invoke recovery processing for NCPs that are down.

  • The SNA automation feature can now recover dynamic resources that VTAM may not know about after a failure occurs.

  • The LAN Automation feature can now distinguish between traditional 2-port bridges and multiport bridges.



PRODUCT POSITIONING

NetView for OS/390 is a key component in connecting the management of the S/390 environment to the distributed world. It provides the TME 10 automation services for S/390 applications. Through TME 10 Global Enterprise Manager, it can exchange events, commands, and topology data with the TME 10 Enterprise Console and other TME 10 distributed products. In addition, with its open application programming interfaces (APIs), NetView for OS/390 can be an integration point for other S/390 vendors to the TME 10 distributed environment.

TME 10 NetView for OS/390 is a program for managing networks and systems through graphical display and automation. NetView for OS/390 integrates NetView Version 3 with two of its popular applications, MultiSystem Manager and Automated Operations Network. By merging these three programs into a single offering, NetView for OS/390 provides what customers need to manage network computing resources. It reduces manual resource definition and complex automation set-up through production-ready automation and extends centralized management into multiple non-SNA network environments. NetView for OS/390 can be used in an enterprise as a centralized manager, a mid-level manager, or a S/390 management endpoint.



FUNCTION PREVIEW

Access to the NetView for OS/390 console function is provided by a new function in TME 10 NetView for OS/390, a Java (TM) client. The NetView for OS/390 console is no longer tied to a 3270 terminal or emulator session. You can now access the command facility, hardware monitor, session monitor, central site control facility (CSCF), and any NetView console function from any Java-capable workstation, regardless of platform (for example, OS/2, Windows (R) NT, or Windows 95).

Workstation code and documentation will be delivered though the TME 10 NetView for OS/390 homepage at:

    http://www.networking.ibm.com/nmv/nmvindex.htm
The Java client is planned to be made available in the second quarter of 1997.

Previews provide insight into IBM plans and direction. General availability, ordering information, and terms and conditions will be provided at product announcement.



EDUCATION SUPPORT

Training is offered through IBM Education and Training (E&T) and through Tivoli Systems.

For current information on Tivoli Systems education, call 800-tivoli8 (512-794-9070 for outside U.S.), e-mail training@tivoli.com, or visit the Tivoli Systems home page on the Internet (select "Product" for training information) at:

    http://www.tivoli.com
For current information on IBM Education and Training courses in the U.S., contact 800-426-8322. Outside the U.S., contact your local country IBM E&T contact. Worldwide information is also available on the IBM E&T home page on the internet at:
    http://www.training.ibm.com
Trademarks
      OS/390, MVS/ESA, C/370, RACF, and Nways are trademarks of
      International Business Machines Corporation in the United
      States or other countries or both.
      NetView, S/390, MVS, Language Environment, ACF/VTAM, VTAM,
      OS/2, SystemView, AD/Cycle, APPN, AIX, and NetFinity are
      registered trademarks of International Business Machines
      Corporation in the United States or other countries or both.
      Windows is a registered trademark of Microsoft Corporation.
      Java is a trademark of Sun Microsystems, Inc.
      TME 10, Tivoli Management Environment, and TME are registered
      trademarks of Tivoli Systems, Inc.  in the United States or
      other countries or both.
      Other company, product, and service names may be trademarks or
      service marks of others.



SUPPLEMENTAL INFORMATION



Packaging Options

Detailed highlights of the packaging options and the following three TME 10 (R) NetView (R) for OS/390 (TM) (NetView for OS/390) components are described below:

  • Systems and Network Management: Integrated NetView Component
  • Non-SNA Management: Integrated MultiSystem Manager Component
  • Automation: Integrated AON Component
NetView for OS/390 also provides three packaging options so that you can choose the package that bests meets your business needs.

NetView for OS/390 is available in these function-based packages.

  • Unattended Option

    Unattended Option is the option you will need if you want lights-out management from a centrally-located staff. This package can only be run in conjunction with one or more instances of a Procedural Option or Graphical Enterprise Option. It does not provide the functions needed for it to be the only NetView for OS/390 package that you use.

    The Unattended Option provides automation capabilities without the hardware monitor, session monitor, and status monitor displays or the NetView Graphical Monitor Facility.

    It provides a limited selection of other NetView for OS/390 functions, including:

    • Application programming interfaces
    • The NetView Bridge for accessing MVS (R) databases
    • Command facility
    • Event Integration Facility and adapters for TME (R)
    • Support for extended MCS consoles
    • Hardware monitor, session monitor, and status monitor single-line queries
    • NetView Installation and Administration Facility/2
    • A program-to-program interface
    • Resource Object Data Manager
    • Subsystem interface (SSI) for communication with MVS
  • Procedural Option

    The Procedural Option includes all the functions of the Unattended Option, plus the following features:

    • Browse facility
    • Help and Help Desk facilities
    • Remote operations support
    • Support for logons to the local 3270 host using a 3270 interface
    • Central site functions for users accessing NetView only through 3270 interfaces
    • Dynamic authorization definitions for commands and resources
    • Automated Operations Network component (without the graphical interface)
  • Graphical Enterprise Option

    The Graphical Enterprise Option is the choice if you want graphical capabilities.

    This package includes all the functions in both the Unattended Option and Procedural Option, plus the following features:

    • Integrated NetView Graphic Monitor Facility and Graphic Monitor Facility Host Subsystem
    • Exception views (also known as critical-objects displays)
    • Dynamic network management of your SNA resources using the SNA Topology Manager
    • Dynamic authorization definitions for NGMF views
    • Command Tree facility for issuing point-and-click commands against resources in NGMF views
    • Automated Operations Network component with graphics
    • MultiSystem Manager component



Systems and Network Management: Integrated NetView Component

Highlights of the expanded function, improved performance, and enhanced usability and installation functions for the NetView component are as follows.

  • Enhancements to Resource Utilization Management

    The resource utilization management function in NetView for OS/390 enables you to prioritize, monitor, and control essential system resource usage by NetView tasks. You can obtain information that helps you plan for and tune NetView, so that tasks can be adjusted according to the amount of resources consumed.

  • Enhancements to Automation Capabilities
    • Improved VSAM Access:

      NetView now provides access to VSAM files directly from REXX procedures, NetView command lists (CLISTs), PL/I and C/370 (TM) programs, and the NetView for OS/390 command line. Using the command processors DSIVSMX and DSIVSAM, you can access any keyed VSAM file, including those that are defined by NetView for OS/390 data services tasks.

      The DSIVSMX command processor can define, read, and write VSAM-keyed files directly from a command processor, without using data services tasks. This command also provides access to IDCAMS, the VSAM services utility.

      With this support, you can implement VSAM applications, including end-use applications developed in REXX (in conjunction with the pipeline facility).

    • Full-Screen Automation

      NetView for OS/390 now includes support for full-screen automation. With full-screen automation, a REXX, PL/I, or C program can perform any NetView for OS/390 full-screen component tasks that a NetView operator could perform using the same component and a 3270 display. Examples of NetView for OS/390 full-screen components are NLDM and full-screen TAF. Using full-screen automation, an application program is able to:

      • Read data from a NetView for OS/390 application panel.
      • Write data to a NetView for OS/390 application panel.
      • Execute the PF, PA, Enter, and Clear function keys on a NetView for OS/390 application panel.
    • PIPE Enhancements

      NetView for OS/390 pipeline support has been enhanced to include complex pipelines. Complex pipelines allow processing of stages with multiple input and output data streams. Some new stages have also been introduced, including COUNT, EDIT, DUPLICAT, COLOR, REVERSE, and LOOKUP.

    • REXX Enhancements

      NetView for OS/390 REXX programs can now determine the name by which they are invoked. REXX programs can check the security authorization of the NetView for OS/390 operator executing the program and modify processing accordingly.

  • SNA Topology Manager Enhancements in Storage, Serviceability, Availability, and Recoverability

    The virtual storage required by the SNA Topology Manager (SNATM) has been significantly decreased. Also, when a storage shortage is detected, the SNA Topology Manager tries to terminate only the responsible command instead of ending the entire SNATM task. A new command displays the internal storage pool usage of the SNA Topology Manager.

    Prior to TME 10 NetView for OS/390, the SNA Topology Manager terminated when RODM or VTAM (R) CMIP services terminated. The SNA Topology Manager now reinitializes and attempts to reconnect to the failing component, based on retry intervals and limits that you define. The TOPOSNA SETDEFS command has been enhanced to let you enter specifications for retrying the RODM connection, the VTAM CMIP services connection, and MONITOR commands.

    An improved TOPOSNA TRACE function supports an internal trace buffer and increased granularity for trace data collection.

    New NetView for OS/390 samples have also been added to help you customize SNA Topology Manager views.

    The optional suppression of NetID from DisplayResourceName of SNATM objects is provided.

  • Enhancements to NetView Sysplex Support

    NetView now supports two MVS Version 5 Release 2 features that are available for use on System/390 (R) Parallel Sysplex (TM) and related systems: cloning support and automatic restart manager (ARM) support.

    For example, in a parallel sysplex environment, a copy of NetView may be running on multiple MVS images. Data set names, partitioned data set member names, and the contents of these members may need to be unique for each MVS image. Cloning support reduces the amount of maintenance required by permitting this type of data to be shared across multiple systems while retaining the uniqueness of each MVS image. With cloning support, it may no longer be necessary to maintain separate NetView for OS/390 partitioned data sets with unique member data. To take full advantage of this function, an MVS system of Version 5 Release 2 or later is required.

    Automatic restart manager (ARM) support decreases the need for operator intervention to restart NetView for OS/390 following an abnormal termination. For example, if the NetView for OS/390 main task abends, the NetView program will be automatically restarted if ARM support is enabled.

  • Enhanced End-to-End Management Support for APPN (R) HPR and MNPS Technologies

    The NetView for OS/390 session monitor now supports High-Performance Routing (HPR) and Multi-Node Persistent Sessions (MNPS). From the session monitor, you can now see the current session route information for HPR-capable sessions, including those parts of the route that have been switched. You can also see the new session route information for sessions that have been recovered by VTAM's MNPS support.

  • Expanded Support for LE/370

    NetView for OS/390 allows a choice of the High Level Language you can run. NetView for OS/390 allows you to run either AD/Cycle (R) LE/370 or a combination of PL/1 and C/370 as your High Level Language.

  • Multiple Enhancements to NetView GMF, Including Support for Session Data

    You no longer need to use a NetView 3270 session to retrieve basic information from the session monitor. Additional function and expanded integration are provided from NGMF, reducing the need for 3270 screens. The session monitor's session list function is now provided from NGMF. You can display session list information for a resource to either all other session partners or to a specified partner. You can also display from NGMF the meaning of any sense codes that are indicated in this session list information. In addition, the session list information is available in message form to automation routines.

    Additionally, the following NGMF functions and enhancements were added:

    • Sample routines are supplied that provide an IML capability for 3174 controllers directly from NGMF.
    • Span of control for NGMF now includes span checking for the following options on the Set Operator Status and Clear Operator Status functions of the Resource pull-down menu:
      • Marker
      • Suspended Manually Clear
      • Suspended Automatically Clear
    • A new NetView for OS/390 setting allows operators to use a NetView Version 3 Release 1 Graphic Data Server to communicate with the NetView for OS/390 host programs during your migration to NetView for OS/390.
    • The Automated Operations Network component now sets the RODM "Automation in Progress" status when it attempts to recover failed resources. By letting operators know which resource outages are being handled by automation routines, this new Automated Operations Network feature allows operators to concentrate only on resources that are not being recovered by Automated Operations Network.
    • The automatic NetView Autotask Logon at NGMF operator logon.
    • The capability to logon NGMF Server with a fully qualified LU name.
  • Ability to Dynamically Control Access to Resources

    NetView for OS/390's span of control function defines which resources can be accessed by an operator. This function is enhanced to use a NetView for OS/390 span table. This table enables you to define named spans that contain not only resource names but also view names. The resource and view names in the table entries can include wild-card specifications. This table can be updated and reloaded using the REFRESH command without restarting NetView. The table is maintained independently from the VTAMLST and RODM object definitions. In addition, the SECMIGR command has been enhanced to provide migration from the existing span of control definitions to the new NetView for OS/390 span table.

  • Security Enhancements to NGMF Views

    A new NetView for OS/390 feature allows you to use NetView for OS/390 span table definitions to restrict operators from displaying specified NGMF views or resources within views. The resources and/or views are specified in the NetView for OS/390 span table. You can specify the following for each operator:

    • Whether the operator's authority is limited for displaying NGMF views, resources, or both
    • Whether objects the operator is not authorized to see will be visible as null objects or hidden from the operator's view
    • Whether the NGMF operator will receive a notification when a span-restricted view cannot be displayed or when at least one resource is excluded from the view displayed to the operator
    • Whether the NGMF operator will receive a notification when at least one view name is excluded from a span-restricted view list displayed to the operator
  • Ability to Run Multiple NetView for OS/390 Graphical Enterprise Options on One MVS Image

    With past NetView releases, you could run two sets of NetView on the same system, but you could not have full function on both NetViews. NetView for OS/390 allows you to run two graphical NetView for OS/390s on the same system, with both controlling graphical workstations. In this context, a graphical NetView for OS/390 release refers to the combination of the NetView component of NetView for OS/390, RODM, and GMFHS.

    This new function can give you the flexibility to keep a stable production environment using your current NetView release while you are installing and customizing the new NetView for OS/390 release. It could also be used to divide the work in your network. While one NetView for OS/390 performs systems automation functions, using a combination of NetView for OS/390 and either AOC or Systems Automation for OS/390, a second NetView for OS/390 could be used to perform network management and network automation functions, using the functions of the NetView, MultiSystem Manager, and Automated Operations Network components.

  • Enhancements to the Hardware Monitor

    The Hardware Monitor alert wrap count has been increased to 9999.

  • Performance and Serviceability Enhancements to RODM

    RODM now has an improved locking structure that eliminates the need to explicitly lock and unlock objects. An added benefit of this feature is significantly improved RODM performance. RODM also requires less storage for objects. Additionally, several new dump options are also provided for RODM. Some options allow you to limit the number of dumps taken within a time interval and to expand the scope of a dump. One option allows you take a dump when an abend occurs while copying user data.

  • Performance and Serviceability Enhancements to GMFHS: Trace data from the GMFHS can be sent to the GTF. This eliminates the need to recycle GMFHS to see logged trace entries.

    GMFHS is modified to use the Hardware Monitor Alerts database.

  • Enhanced NetView for OS/390 Help Facility:
    • NetView Help Desk

      The NetView help desk provides information to assist you in performing network management functions, including problem determination. Information includes the following:

      • Table of contents
      • Terminal not working
      • Transaction or application not working
      • Slow response time
      • Problems identified through network monitoring
      • Help using NetView
      • Problem with an agent or service point
      • Displaying status and statistics
      • Gathering trace data
      The help desk facility has been rewritten to use the same facilities as the new message and command help. You can use the backward and forward PF keys to move through help desk topics, and the FIND command to search within a topic. From the table of contents, you can select a topic. The help desk can be customized more easily, and you now have wide/deep screen support for the help desk.

    • NetView for OS/390 Message and Command Help Information

      NetView for OS/390 message and command help information is now stored as members of a partitioned data set. NetView for OS/390 no longer uses VSAM files to store this information. This results in more flexibility for customizing the help information. You can also locate specific information through the FIND command and through scrolling, and you now have wide/deep screen support for help.

  • Enhancements to the Log Browse Facility: Two new commands have been added to the log browse facility. Once you access the log browse facility by entering the BROWSE command, you can now quickly locate and display the records you want to see.
    • The LOCATE command allows you to position your log browse display to a given line number or date and time.
    • The ALL command allows you to display either a subset or all of the records in the log browse facility.
    Also, when you enter the BROWSE command in this NetView for OS/390 release, all of the most recent records are automatically displayed.

    The BLOG command, which was shipped as a sample in previous releases, is now part of the NetView for OS/390 product. Like BROWSE, the BLOG command gives you access to the log browse facility. You can use BLOG to display a subset of records in the log. Once you have accessed the log with the BLOG command, you can also use the new ALL command to display all the log records or to change the display filter. While a log browse request is in progress, you can now press Enter to cancel this request without having to exit the browse facility.

    Additionally, log browse requests that result in the reading of a large number of log records now have improved response times.

  • Installation Enhancements

    The NetView Installation and Administration Facility/2 (NIAF/2) is a workstation-based installation tool that allows new users and users migrating from NetView V1R3, V2R3, V2R4, or V3R1 to install the TME 10 NetView for OS/390 program, as well as perform administrative tasks. NIAF/2 also allows users to maintain a current level of the NetView for OS/390 program.

    NIAF/2 provides the following usability and functional features:

    • An OS/2 (R) workstation platform
    • Graphical end-user interface
    • Use of the OS/2 notebook control
    • Use of a flowchart for the installation process
    • Administration and installation tasks documented in the
    • Host and workstation installation and administration tasks
    • Installation options for new users and migrating users (greater flexibility for migrators)
    • Data validation for each installation parameter
    • Information on new and changed parameters for migrators
    • Context-sensitive help for each task and installation parameter
      • Recommended value information
      • Maximum and minimum value information
      • Default value information
    • Access to softcopy books
    • Selective component installation
    • A single profile for multiple installations, which reduces the time require to define each NetView system separately
    • Ability to identify and track all activities performed per installation using a log
    • Ability to customize the NIAF/2 program
    • Storage Management Subsystem (SMS) support
    • Ability to print the Process Chart
    • Enhancements to specifying information on the Scope of Commands page in the Parameter Profile component
    • Preserving of comments and %INCLUDE statements that appear in NetView PDS members (such as DSIDMN and DSICMD)
    • Enhancements to Installation Exits
    NetView for OS/390 now includes the following installation exit enhancements:
    • A new installation exit, DSIEX20, allows more granular processing of NetView session awareness (SAW) records. This exit allows a customer to accept or discard SAW records based on their content.
    • The DSIEX17 installation exit has been enhanced to give you additional choices for automating action messages and DOM (delete operator message) signals.
    • The new LOADEXIT statement has been added to DSIDMN. This statement allows you to load installation exits selectively. You no longer need to load all installation exits.
  • Support for Internationalized Date and Time Formats

    NetView for OS/390 now includes new parameters that allow you to customize the long and short formats for the dates and times displayed in many host NetView for OS/390 functions. The OVERRIDE command also supports these new parameters. This means you can specify date and time formats for NetView for OS/390 in general, and then override the defaults for specific operators.

    Note: This customization support for dates and times is not uniform throughout all components of NetView for OS/390. However, most host NetView components, including the ones listed here, will support your specified customization parameters:

    • Host-based screen displays for major NetView for OS/390 components, such as the session monitor, status monitor, hardware monitor, and command facility
    • All host NetView component commands
    • All host NetView component messages
  • Automatic Logoff of Inactive NetView User IDs



Non-SNA Management: Integrated MultiSystem Manager Component

The MultiSystem Manager product has been integrated into NetView for OS/390. NetView for OS/390 provides the management support for a wide range of heterogeneous networks. The MultiSystem Manager component can provide the dynamic topology discovery and status of non-SNA resources. Its expanded function now supports all the following types of networks:

  • IBM OS/2 LAN Network Manager (LNM) networks
  • Novell NetWare networks
  • IBM LAN NetView Management Utilities (LMU) networks
  • Internet Protocol (IP) networks using IBM NetView for AIX (R)
  • NetFinity (R) networks
  • Asynchronous Transfer Mode (ATM) networks
The MultiSystem Manager component of NetView for OS/390 also includes the Open Topology Interface. When used in conjunction with an Open Topology Agent, the Open Topology Manager provides the basis to manage any resource in your network. By using the Open Topology Interface, any agent provider can populate the Resource Object Data Manager (RODM) with resources, enabling graphical display of the status and topology of those resources.

Using the Open Topology Interface along with the MultiSystem Manager component topology features for managing LAN physical media, NetWare servers and requesters, Internet Protocol resources, LAN NetView Management Utilities resources, NetFinity resources, and ATM resources, NetView for OS/390 provides you with a unique opportunity to manage the diverse resources in your network from a single NetView Graphic Monitor Facility screen.

Managing your network resources from the mainframe with the MultiSystem Manager component of NetView for OS/390 provides value in the following areas:

  • Correlation facility, enabling correlation of all resources that may affect the network.

  • Improved centralized control by dynamically collecting, storing, and updating resource topology and status data in RODM for use by the NetView Graphic Monitor Facility (NGMF). This saves the operations staff from the overwhelming job of manual data entry and maintenance.

  • Customized views created with the BLDVIEWS utility are easy to understand, allowing operators to focus on failing resources quickly. The BLDVIEWS utility lets the system programmer create views and aggregate resources using simple control cards.

  • Improved operator productivity in using the MultiSystem Manager provided Command Tree/2 command sets. This allows the operations staff to issue object-specific commands to system resources using point-and-click technology without learning sets of commands and command syntax.

  • Increased operations effectiveness by allowing operators to easily isolate the source of problems detected by different agents.

  • Enhanced automated operations since topology and status updates are received by NetView for OS/390 and automatically stored in RODM. This enables resource topology and status information to be automated using NetView for OS/390 and RODM automation techniques.
The MultiSystem Manager component of NetView for OS/390 includes the following new enhancements that can help you better manage all the nodes in your network:
  • Management of ATM and NetFinity resources from NGMF has been centralized. ATM and NetFinity resources are dynamically discovered by MultiSystem Manager and stored in RODM.

  • Performance for the discovery and update process for resources managed by an open-topology agent has been improved. The new ATM and NetFinity features have been designed to take advantage of these performance enhancements.

  • Exception view processing, RODM access, and alert processing have been enhanced for improved performance.

  • NetView for OS/390 sample CNMSJH12 can now be used to load the MultiSystem Manager data model as well as the GMFHS/SNA Topology Manager data model. This provides a faster, simpler way to load the data models.

  • NetView for OS/390 span of control enhancements have been enabled for MultiSystem Manager views.

  • The LAN Network Manager (LNM) feature has been enhanced to discover and display remote and parallel bridges.

  • GETTOPO command processing has been enhanced so your BLDVIEWS customization is no longer affected by ReDiscovery (R) of resources in your network.

  • The MultiSystem Manager component of NetView for OS/390 now discovers additional relationships between resources managed by different agents. Existing topology correlation by LAN MAC address has been expanded to also discover when resources on the same workstation share the same TCP/IP address. For example, TME 10 software and a LAN adapter card residing on the same server will both be shown in a lower-level NGMF view of that workstation.

  • The correlation function now runs faster, can be customized, and provides additional information about correlated resources. Operators can now diagnose complex problems more easily. For example, an operator can now determine that the cause of an ATM switch failure is actually a failure in the underlying TCP/IP adapter, which is reported by a different management agent.



Automation: Integrated AON/MVS Component

The Automated Operations Network/MVS product has been integrated into NetView for OS/390. The Automated Operations Network component enables you to implement network automation without writing procedures, yet it can be easily extended to meet your unique networking requirements. It enhances the network management function provided by the NetView component by providing cost-effective, automated network operations facilities. These facilities improve controls, which enhance operator productivity and network availability.

Automated Operations Network provides a single, integrated, automated solution for diverse environments, including SNA, TCP/IP, VTAM Subarea, X.25, APPN, and token-ring LANs. It provides the drop-in automation policy and routines necessary to automate network recovery and increase availability of your network. The drop-in automation policy can be easily extended to suit your environment.

The AON base toolkit also allows you to leverage IBM's overall automation knowledge if you choose to write your own automation routines. For example, by using AON's threshold correlation routines, you can leverage AON's base toolkit to get your own automation up and running more quickly as a result.

Highlights of the expanded function, improved performance, and enhanced usability and installation functions that improve your ability to manage network automation are as follows.

  • Improved automation performance is provided through:
    • Quicker access to the AON Common Global variables.
    • Improved routing of AON commands between components.
    • Improved handling of VTAM messages.
  • AON will now set the RODM "Automation In Progress" status so your NGMF operators can quickly determine when automation is already handling a resource outage.

  • Installation exit DSIEX19 can now be used for security authorization on the commands sent to the IBM LAN Network Manager (LNM) product. Any command sent to LNM for LAN automation tasks can be restricted from use by any operator you specify.

  • More than two auto-tasks can now be specified for SNA automation and AON message processing. This improves overall system performance and prevents delays in auto-task processing. Support is also provided for the new AIPOPER class of auto-tasks. These auto-tasks are used to set the RODM "Automation in Progress" status.

  • A new option in the AON trace facility allows you to turn off tracing altogether. This reduces NetView for OS/390 overhead and improves performance. When you need to run a trace, you can enable tracing easily from the AON operator interface.

  • The NCP Recovery function supports using the NCP load module name or PU name during the recovery processes.

  • You can decide whether NCPs are status-checked during AON initialization, and you can invoke recovery processing for NCPs that are down.

  • The SNA automation feature can now recover dynamic resources that VTAM may not know about after a failure occurs.

  • The LAN Automation feature can now distinguish between traditional 2-port bridges and multiport bridges. This information helps you solve problems quicker using the LAN HelpDesk and gives you more accurate performance statistics for multiport bridges.



OPEN BLUEPRINT (R)

TME 10 NetView for OS/390 provides for the manageability of hardware and software resources. Its implementation is consistent with the Systems Management function described in IBM's Open Blueprint. It supports the Systems Network Architecture/Management Services (SNA/MS) protocol from IBM and the Common Management Information Protocol (CMIP) industry-standard protocol from the International Telecommunications Union -- Telecommunications (ITU-T) and the International Organization for Standardization and its associated technical committee (ISO/IEC) to facilitate open, distributed, multivendor interoperability.



TECHNICAL INFORMATION



Specified Operating Environment

Hardware Requirements



NetView for OS/390 Hardware Requirements

TME 10 NetView for OS/390 runs in a virtual storage environment on any IBM system configuration with sufficient storage that supports MVS/ESA (TM).

NetView Graphic Monitor Facility: The NetView Graphic Monitor Facility workstation code executes on any IBM Personal Computer with a 386 or higher processor or any IBM Industrial Computer that compatibly supports the IBM Operating System/2 (R) Version 3 (WARP) defined in the Software Requirements section that follows. The Japanese translation feature requires a double-byte character set (DBCS)-capable terminal that runs IBM OS/2 Version 3.0 J or later.

The following are the minimum requirements beyond those required for OS/2 and other concurrently running programs:

  • Any hardware that runs the supported levels of IBM OS/2 Version 3 (or later)
  • 3.0MB of additional memory (combined client/server, with a 200 resource network and one view active)
  • 15MB of additional fixed disk space
  • Color display (SVGA, 1024 x 768, recommended)
  • Mouse
  • Communications Manager/2 Version 1.1 (79G0258, 79G0257) or later or Communications Server Version 4 (5765-652) and Personal Communications for OS/2 Version 4 Release 1 (PCOMM; 39H3929) with PCOMM CSD2
The selection of personal computer model size, DASD, and memory depends on performance factors.

NetView Installation and Administration Facility/2 (NIAF/2): The NetView Installation and Administration Facility/2 (NIAF/2) consists of workstation code that executes on any IBM Personal Computer with a 386 or higher processor or IBM Industrial Computer that compatibly supports the IBM Operating System/2 2.1 (OS/2) or Operating System/2 3.0 (WARP) defined in Software Requirements section that follows. It is recommended that NIAF/2 run on a 486 processor with a 33MHz or higher clock speed. The Japanese translation feature requires a double-byte character set (DBCS)-capable terminal that runs IBM OS/2 Version 3.0 J or later. The following are the minimum requirements beyond those required for OS/2 and other concurrently running programs:

  • Any hardware that runs the supported levels of IBM OS/2 3.0 (or later)
  • 2.0MB of additional memory
  • 15MB of additional fixed disk space plus 2MB of additional disk space for each NetView domain to be installed using NIAF/2
  • Optional: Online NIAF/2 supplied books require an additional 10MB of fixed disk space
  • Color display (SVGA, 1024 x 768, recommended)
  • Mouse
  • Communications Manager/2 Version 1.1 (79G0258, 79G0257) or later or Communications Server Version 4 (5765-652) and Personal Communications for OS/2 Version 4 Release 1 (PCOMM; 39H3929) with PCOMM CSD2 for host and workstation communications and the following:
    • Any communication adapter that Communications Manager/2 supports

    • 3270 emulator communications (optional -- for supporting NetView 3270 interfaces on the workstation) -- Any 3270 emulator adapter supported by Communications Manager/2
  • IBM DATABASE 2 (TM) (DB2 (R)) for OS/2 Version 2 (41H2112) or later
The selection of a Personal Computer model size, DASD, and memory depends on performance factors, such as the size of the supported network, the number of views, and the amount of network activity.

NetView for OS/390 storage estimate worksheets in the NetView for OS/390 Tuning Guide (SC31-8240) provide help in workstation storage calculations.



NetView for OS/390 MultiSystem Manager Component

MultiSystem Manager Component NetWare Support Requirements

  • Any IBM Personal Computer or compatible computer as required for NetWare Version 3 or 4 will support the topology agent for NetWare. The topology agent for NetWare is shipped with NetView for OS/390.
MultiSystem Manager Component LAN: Network Manager Support Requirements:
  • Any IBM Personal Computer or compatible computer as required for Operating System/2 and LAN Network Manager Version 2 will support the topology agent for LAN Network Manager. The topology agent for LAN Network Manager is part of the LAN Network Manager product.
MultiSystem Manager Component Internet Protocol Support Requirements
  • Any IBM RISC System/6000 (R) POWERstation (TM), POWERserver (R), or compatible computer as required for AIX Version 4.1 or later and NetView for AIX Version 4. The topology agent for Internet Protocol is shipped with NetView for OS/390 and runs as an application on NetView for AIX.
MultiSystem Manager Component LAN NetView

Management Utilities Support Requirements:

  • Any IBM Personal Computer or compatible computer as required for Operating System/2 and LAN NetView Management Utilities will support the topology agent for LAN NetView Management Utilities. The topology agent for LAN NetView Management Utilities is part of the LAN NetView Management Utilities.
MultiSystem Manager Component NetFinity Support Requirements
  • Any IBM Personal Computer or compatible computer as required for NetFinity will support the topology agent for NetFinity. The topology agent for NetFinity is part of the NetFinity product.
MultiSystem Manager Component Asynchronous Transfer

Mode (ATM) Support Requirements:

  • Any IBM RISC System/6000 POWERstation, POWERserver, or compatible computer as required for AIX Version 4.1 or later, NetView for AIX Version 4 and Nways (TM) Campus Manager ATM for AIX. The topology agent for ATM is shipped with NetView for OS/390 and runs as an application on NetView for AIX.



NetView for OS/390 Automated Operations Network Component

Automated Operations Network Component Requirements

  • Dynamic Display Facility (DDF) requires 3x79 Terminal with Extended Attribute Support for a display capable of seven colors
  • The SNA Automation feature has these additional requirements for Switched Network Backup Automation:
    • IBM 586x modems (except Model 1) with two or four wire SNBU couplers, if desired, or
    • The 786x, 7855, or LPDA (R)-2 command set capable modems

      Note: Only the 786x Models 45, 46, and 47 can automatically switch back from SNBU.

  • Automated Operations Network LAN Automation has these additional requirements:
    • An IBM Personal Computer or compatible workstation LAN Network Manager running under OS/2 with the Communications Manager communicating with VTAM over an SSCP-PU or LU 6.2 session
    • 3172, 3174, or 3745 Token-Ring Host Gateways or Communications Manager functioning as an SDLC-attached host gateway for the LAN manager
  • To use the LAN RTAP functions requires:
    • IBM Personal Computer or compatible workstation configured with:
      • A minimum of 8MB of RAM
      • .5MB hard drive storage
      • 80286 or higher processor
      • Token-ring network 16/4 trace and performance adapters AT (R) Bus (feature number 5121, product number 74F5121) or Micro-channel (feature number 5130, product number 74F5130) or DatagLANce (TM) Network Analyzer for Ethernet/Token-Ring Version 1 Release 2 (11H0233)
      • Communications adapter card to provide SNA non-DFT (SSCP-PU or LU 6.2) connection to AON LAN automation (separate from the TAP adapter card)
  • TCP/IP Automation has this additional requirement:
    • A properly configured RISC System/6000 POWERstation or POWERserver to support an SNA connection between the RISC System/6000 and the 370/390 Host on an SSCP-PU or LU 6.2 session.
Software Requirements



Required for All Packaging Options

This section defines the minimum programming requirements for NetView for OS/390 and its S/390 (R) MVS/ESA operating environments. Specific functions of NetView for OS/390 may require additional products or higher levels of the products as noted below.

NetView for OS/390 is executed as an application on the MVS/ESA operating system, with VTAM. NetView for OS/390 support is provided at the listed levels or subsequent levels that are upward-compatible, unless otherwise stated. Upward compatibility means that functions provided by the earlier releases are still supported.

Programming Requirements: NetView for OS/390 is executed as a subsystem in the following MVS/ESA environment:

  • MVS/ESA SP (TM)-JES2 Version 5 Release 1.1 (5655-068) or MVS/ESA SP-JES3 Version 5 Release 1.1 (5655-069)
    • ACF/VTAM (R) Version 3 Release 4.2 for MVS/ESA (5685-085) or later
    • ACF/NCP Version 4 (5668-854) or later
    • TSO/E Version 2 Release 5 (5685-025) or later (for REXX interpreter)
    • SMP/E Release 8 (5668-949) or later
NetView-to-NetView Communication

In a multiple-domain network or across multiple SNA networks, the NetView program can communicate with another NetView program, regardless of the operating system. NetView for OS/390 can communicate with the following, at the listed system's level of capabilities:

  • NetView Version 1 Release 3 for MVS/XA (TM) and MVS/ESA
  • NetView Version 2 Release 2 for VM and VSE
  • NetView Version 2 Release 3 for MVS/XA, VM/ESA (R), and VSE/ESA (TM)
  • NetView Version 2 Release 4 for MVS/ESA
  • NetView Version 3 Release 1 for MVS/ESA
  • TME 10 NetView for OS/390
Function Compatibility

The functions of the following versions and releases are upwardly compatible with NetView for OS/390:

  • NetView Version 1 Release 3 for MVS/XA and MVS/ESA
  • NetView Version 2 Release 2 for VM and VSE
  • NetView Version 2 Release 3 for MVS/XA, VM/ESA, and VSE/ESA
  • NetView Version 2 Release 4 for MVS/ESA
  • NetView Version 3 Release 1 for MVS/ESA
Note: Upward compatibility means that functions provided by the earlier releases are still supported.

The NetView Graphic Monitor Facility workstation code provided with NetView Version 2 is not upwardly compatible. NetView for OS/390 workstation code must be used in conjunction with the NetView for OS/390 host.

A new NetView for OS/390 setting allows operators to use a NetView Version 3 Release 1 Graphic Data Server workstation to communicate with the NetView for OS/390 programs during your migration to NetView for OS/390.

System Definition Compatibility

For equivalent, non-system dependent functions, TME 10 NetView for OS/390 will operate with the definition statements and the command lists of the following:

  • NetView Version 1 Release 3 for MVS/XA and MVS/ESA
  • NetView Version 2 Release 2 for VM and VSE
  • NetView Version 2 Release 3 for MVS/XA, VM/ESA, and VSE/ESA
  • NetView Version 2 Release 4 for MVS/ESA
  • NetView Version 3 Release 1 for MVS/ESA
For equivalent non-system dependent functions, NetView for OS/390 will operate with the REXX procedures of NetView Version 1 Release 3, Version 2, and Version 3.

The NetView constants module DSICTMOD should be updated and reassembled as part of the installation of NetView for OS/390.

User applications, written for these NetView releases in accordance with NetView customization publications and using NetView customization services, will be source compatible. A reassembly or recompile using NetView for OS/390 macro libraries is required.

If user customization code is being migrated from one operating system release to another, user code that contains system-dependent functions may not run and may require conversion.

TME 10 NetView for OS/390 Installation

  • SMP/E Release 8 (5668-949) or later
  • TSO/E Version 2 Release 5 (5685-025) or later (for REXX support)



Enhanced Function Support

The following TME 10 NetView for OS/390 functions and features require the specified program levels or subsequent upward-compatible levels unless stated otherwise.



NetView Component

NetView Installation and Administration Facility/2

  • OS/2 3.0 (WARP; 83G8100, 83G8102, 83G8103, 83G8111, 83G8108, 83G8700 , 83G8701, 83G8702, 83G8703, 83G8708, 83G8709, 83G8710, 83G8711, 83G8712), or OS/2 3.0 J
  • Communications Manager/2 Version 1 Release 1 (79G0258, 79G0257) or later or Communications Server Version 4 (5765-652) and Personal Communications AS/400 (R) and 3270 Version 4 Release 1 for OS/2 (PCOMM; 39H3929) with PCOMM CSD2 or for Japanese version, Communications Manager/2 1.1 J or later
  • IBM Database 2 for OS/2 Version 2 (41H2112) or later
Resource Object Data Manager (RODM)
  • One of the following sets of runtime libraries:
    • PL/I 370 and C/370
    • OS PL/I Version 2.3 Library (5668-911)
    • C/370 Library Version 2 (5688-188)
    • AD/Cycle LE/370 Version 1 Release 5 (5688-198)
  • RODM Methods
    • TME 10 NetView for OS/390 RODM methods written in PL/I and C are compatible with AD/Cycle LE/370 Version 1 Release 5 compiler and runtime libraries.
NetView Bridge -- Support for INFO Access
  • Information/System Version 4 Release 2.2 (NetView Bridge Adapter; 5685-059)
  • Information/Management Version 4 Release 2 (5685-060) or later
  • Application Programming Interface (API) requirements as applicable:
    • OS PL/I Version 2.3 Library (5668-911) for PL/I API and C/370 Library Version 2 (5688-188) for C API or AD/Cycle LE/370 Version 1 Release 5 (5688-198)
Graphic Monitor Facility Host Subsystem
  • RODM requirements
ASCII Console Support in Graphic Monitor Facility Host Subsystem
  • Transaction Control Protocol/Internet Protocol (TCP/IP) Version 2.0 for OS/2 (65G1220)
NetView Graphic Monitor Facility (NGMF)
  • OS/2 as applicable
    • OS/2 3.0 (WARP; 83G8100, 83G8102, 83G8103, 83G8111, 83G8108, 83G8700 , 83G8701, 83G8702, 83G8703, 83G8708, 83G8709, 83G8710, 83G8711, 83G8712), or OS/2 3.0 J
    • Communications Manager/2 Version 1.1 (79G0258, 79G0257) or later or Communications Server Version 4 (5765-652) and Personal Communications AS/400 and 3270 Version 4 Release 1 for OS/2 (PCOMM; 39H3929) with PCOMM CSD2 or for Japanese version, Communications Manager/2 1.1 J or later
NGMF Communications Manager Configuration Utility
  • NGMF requirements
RODM Administration and NGMF Problem and Inventory Functions
  • NGMF requirements plus
  • NetView Bridge requirements (PL/I API or LE/370)
SNA Topology Manager
  • RODM requirements plus
  • ACF/VTAM Version 4 Release 3 for MVS/ESA (5695-117) or later
  • Generalized Trace Facility
  • C/370 Library Version 2 (5688-188) or AD/Cycle LE/370 Version 1 Release 5 (5688-198)
APPN Accounting Manager
  • ACF/VTAM Version 4 Release 3 for MVS/ESA (5695-117) or later
  • Generalized Trace Facility
  • C/370 Library Version 2 (5688-188) or AD/Cycle LE/370 Version 1 Release 5 (5688-198)
  • System Management Facility or an equivalent external logging facility
NetView Graphic Monitor Facility Installation (if not using NIAF/2)
  • The applicable file transfer program for the communication subsystem
APPN Topology and Accounting Agent
  • OS/2 2.0 or later
  • Communications Manager/2 Version 1 Release 1 (79G0258, 79G0257) or later or Communications Server Version 4 (5765-652) and Personal Communications AS/400 and 3270 Version 4 Release 1 for OS/2 (PCOMM; 39H3929) with PCOMM CSD2
MVS Sysplex Support -- NetView Cloning and Automated Restart: Manager Support
  • MVS/ESA Version 5 Release 2 (5655-068)
Pre-initialized PL/I Environments for NetView HLL
  • OS PL/I Version 2.3 Library (5668-911) or AD/Cycle LE/370 Version 1 Release 5 (5688-198)
Pipeline Automation: Pipeline automation for MVS commands requires the use of extended multiple console support.

Support for IBM LAN Network Manager Enhanced Command Interface

  • IBM LAN Network Manager Version 2.0 (03H3519, 03H3523, or 03H3527)
Session Monitor Support of APPN* Display and Problem Determination
  • ACF/VTAM Version 4 Release 1 for MVS/ESA (5695-117)
  • ACF/NCP Version 6 Release 2 (5688-231)
Session Monitor Support of HPR and MNPS
  • ACF/VTAM Version 4 Release 4 for MVS/ESA (5695-117)
Session Monitor Support of VTAM Takeover-Giveback of an NCP
  • ACF/VTAM Version 4 Release 1 for MVS/ESA (5695-117)
Session Monitor support of DLUR/DLUS
  • ACF/VTAM Version 4 Release 2 for MVS/ESA (5695-117)
  • Communications Manager/2 1.11 for local support
  • Communications Manager/2 1.2 for cross network support
Session Monitor support of VR-TG and Bordernode
  • ACF/VTAM Version 4 Release 2 for MVS/ESA (5695-117)
Session Monitor Support of VTAM Extended MS-Transport
  • ACF/VTAM Version 4 Release 1 for MVS/ESA (5695-117)
Management of Frame Relay (DTE) and Ethernet
  • ACF/NCP Version 6 (5688-231)
NetView Parallel Transmission Group Support
  • ACF/NCP Version 5 Release 4 MVS and VM (5668-738)
NetView Network Asset Management

This provides NCP vital product data (VPD) and hardware device vital product information for those devices that support the Request Product Set ID (PSID) architecture or signal converters that support LPDA-2 commands:

  • ACF/NCP Version 4 Release 2 (5668-854) for the 3720 or 3725 communication controllers
In addition to device support, the following releases of ACF/NCP provide vital product information for the communication controller:
  • ACF/NCP Version 4 Release 3.1 (5668-854) for the 3725
  • ACF/NCP Version 5 Release 4 VSE (5668-738) and
  • ACF/NCP Version 5 Release 4 MVS and VM (5668-738) or later for the 3720 or 3745
NetView Performance Monitor (NPM) Alerts
  • NPM Version 1 Release 6 (5665-333 MVS) or later for session alerts
NetView Support for Programmable Network Access (PNA)
  • PNA Version 1.11 (72F0-708)
SAF Security Checking on RODM Connections
  • RACF (TM) 2.1 (5695-039) or later or its SAF equivalent
SAF Security Checking on NetView Operator Password Protection
  • RACF 2.1 (5695-039) or later or its SAF equivalent
SAF Security Checking RMTCMD RMTOPS Class
  • RACF 2.1 (5695-039) or later or its SAF equivalent
SAF security checking for NetView Command Authorization
  • RACF 2.1 (5695-039) or its SAF equivalent



SAF security checking for NetView Span of Control Access

  • RACF 2.1 (5695-039) or its SAF equivalent
SAF security checking for NetView Operator Logon Information
  • RACF Version 2 Release 1 (5695-039) or its SAF equivalent
View Security

One of the following programs and the required RACF service level as specified in the NetView for OS/390 Program Directory to support the function:

  • RACF Version 2 Release 1 (5695-039) or later or OS/390 Release 1 (5645-001)
High Level Language (HLL) Restriction: If you are installing NetView for OS/390, you must make a decision about the High Level Language you will run. NetView for OS/390 will allow you to run with either AD/Cycle LE/370 or a combination of PL/I and C/370 as your High Level Language, however you cannot mix them. What is different than with NetView Version 3 Release 1 is that you may now use AD/Cycle LE/370 if you intend to manage your systems and networks graphically which will include the usage of the NGMF, GMFHS, and SNA Topology components of NetView for OS/390.



MultiSystem Manager Component

  • IBM Library for SAA (R) REXX/370 Release 3.0 (5695-014) or REXX Alternate Library (Release 3.0 level)
Topology Feature for NetWare Requirements
  • NetWare for DOS 3.12 or 4.1
  • One server in the network must be running NetWare for SAA 1.3 or later (at the service level required by the Topology Feature for NetWare program directory). All other managed servers in the network must be running the COMMEXEC component of NetWare for SAA 1.3 or later. To exploit the LU6.2 capabilities, NetWare for SAA 2.0 must run on the managing servers and the COMMEXEC component of NetWare for SAA 2.0 on all managed servers. The LU 6.2 capability also requires Communication Manager/2 Version 1.01 or higher at the service level required by the Topology Feature for NetWare program directory.
  • DOS 5.0 or later -- for installation facility
The NetWare agent command utility and the NetWare TELNET utility require the Topology Feature for NetWare.

The Topology Feature for LAN Network Manager Requirements

  • IBM LAN Network Manager 2.0 (03H3519, 03H3523, or 03H3527) with NetView connectivity, at the service level required by the Topology Feature for LAN Network Manager program directory.

  • Communications Manager/2 Version 1 Release 1 (79G0258 or 79G0257) configured with:
    • Service Point Application Router (SPAR)
The Topology Feature for Internet Protocol Requirements
  • AIX Version 4 Release 1 (5765-393) or later
  • NetView for AIX Version 4 (5765-527 feature number 5608) or later
  • AIX NetView Service Point Version 1 Release 2.2 (5621-107) and IBM Communications Server for AIX, Version 4 (5765-652)
The Topology Feature for LAN NetView Management Utilities Requirements:
  • IBM LAN NetView Management Utilities Version 1.1 (76G7991) or NetView for OS/2 Version 2 (16H9589) or later with the LAN NetView Management Utilities CSD at the service level specified in the Topology Feature for LAN NetView Management Utilities program directory
  • Communications Manager/2 Version 1 Release 1 (79G0258 or 79G0257) configured with:
    • Service Point Application Router (SPAR)
    • Remote Operations Support (ROPS)
The Topology Feature for NetFinity Requirements
  • Tivoli NetFinity Manager and Services that supports the NetFinity topology agent



The Topology Feature for ATM Requirements

  • AIX Version 4 Release 1.4 (5765-393) or later
  • AIX NetView Service Point Version 1 Release 2.2 (5621-107) and SNA Server/6000 Version 3 Release 1.0.1 (5765-582) or later
  • Nways Campus Manager ATM for AIX Version 1.13 (31H7063 or 31H7064) or later
  • NetView for AIX Version 4 (5765-527;feature number 5608) or later



Automated Operations Network Component

  • PL/I Version 2 Runtime Libraries (5668-911) for the Reporting Facility
  • PL/I Version 2 Compiler & Library (5668-909 or 5668-910) to print and tailor reports
SNA Automation Requirements
  • To use the SNBU automation requirements:
    • ACF/NCP Version 4 Release 3.1 (5668-854) or later; Version 5 Release 4 (5668-738) or later is required for complete DMPX support of IBM 7861/8 model 4x modems.
LAN Automation Requirements
  • IBM LAN Network Manager Version 2.0 (03H3519, 03H3523, or 03H3527)
  • Operating System/2 (OS/2), as required by LAN Manager and LAN management utilities
  • A host-attached IBM Token-Ring Network
  • Communications Manager with SPA and ROPS for each LAN manager workstation and RTAP probe station
TCP/IP Automation Requirements
  • AIX Version 4 Release 1 (5765-393) or later
  • NetView for AIX Version 4 (5765-527 feature number 5608) or later
  • AIX NetView Service Point Version 1 Release 2.2 (5621-107) and Communications Server for AIX, Version 4 (5765-652)



The Japanese Version of the MultiSystem Manager Component

Requirements

  • IBM Library for SAA REXX/370 Release 3.0 (5695-014) or REXX Alternate Library (Release 3.0 level)
The Japanese Version of the Topology Feature for NetWare Requirements
  • The Japanese version of NetWare includes 3.12 J or 4.1 J or later.
  • The Japanese version of NetWare for SAA includes 1.3B J or later.
  • One server in the network must be running NetWare for SAA 1.3B J or later (at the service level required by the Topology Feature for NetWare program directory). All other managed servers in the network must be running the COMMEXEC component of NetWare for SAA 1.3B J or later. To exploit the LU6.2 capabilities, NetWare for SAA 2.0 must run on the managing servers and the COMMEXEC component of NetWare for SAA 2.0 on all managed servers. The LU 6.2 capability also requires Communication Manager/2 Version 1.01 or higher at the service level required by the Topology Feature for NetWare directory.
  • DOS 5.0 or later -- for installation facility
The NetWare agent command utility and the NetWare TELNET utility require the Topology Feature for NetWare.

The Japanese Version of the Topology Feature for LAN Network Manager Requirements

  • The Japanese Version of LAN Network Manager Version 2.0 (03H3519, 03H3523, or 03H3527) with NetView connectivity, at the service level required by the Topology Feature for LAN Network Manager in the program directory.
  • The Japanese version of Communications Manager/2 Version 1 Release 1 (79G0258 or 79G0257) configured with:
    • Service Point Application Router (SPAR)
The Japanese Version of Topology Feature for Internet Protocol Requirements
  • The Japanese version of AIX Version 4 Release 1 or later
  • The Japanese version of NetView for AIX Version 4 (5765-527 feature number 5608) or later
  • The Japanese version of AIX NetView Service Point Version 1 Release 2.2 (5621-107) and IBM Communications Server for AIX, Version 4 (5765-652)
The Japanese Version of the Topology Feature for LAN NetView Management Utilities Requirements
  • IBM LAN NetView Management Utilities Version 1.1 (76G7991) or NetView for OS/2 Version 2 (16H9589) or later with the LAN NetView Management Utilities CSD at the service level specified in the Topology Feature for LAN NetView Management Utilities program directory.
The Topology Feature for LAN NetView Management Utilities also requires Communications Manager/2 Version 1.1 at the service level specified in the Topology Feature for LAN NetView Management Utilities program directory and configured with:
  • Service Point Application Router (SPAR)
  • Remote Operations Support (ROPS)
The Japanese Version of the Topology Feature for NetFinity Requirements
  • The Japanese version of the Tivoli NetFinity Manager and Services that support the NetFinity topology agent
The Japanese Version of the Topology Feature for ATM Requirements
  • The Japanese version of AIX Version 4 Release 1.1 or later
  • The Japanese version of NetView for AIX Version 4 (5765-527 feature number 5608) or later
  • AIX NetView Service Point Version 1 Release 2.2 (5621-107) and SNA Server/6000 Version 3.1.0.1 (5765-582) or later
  • Nways Campus Manager ATM for AIX Version 1.13 (31H7063 or 31H7064) or later
Compatibility: In order to take advantage of the MultiSystem Manager component, the appropriate MultiSystem Manager feature and associated agent must be installed. Prior levels of an MultiSystem Manager agent will continue to run with the topology manager of the MultiSystem Manager component, so that all the agents do not need to be migrated at the same time as the host migration takes place. However, the host portions of all the features must be migrated to the same version at the same time.

Limitations for the MultiSystem Manager Component's Topology Feature for NetWare: For the MultiSystem Manager component's Topology Feature for NetWare: Although a topology agent for NetWare can reside on a server running NetWare 4.01, the NetWare 4.01 server cannot act as a collection point. This does not apply to the other supported NetWare releases.



USER-GROUP REQUIREMENTS

This announcement satisfies or partially satisfies over 79 requirements from users, or one or more of the worldwide user-group communities, which include Australasian SHARE/GUIDE (ASG), COMMON, COMMON Europe, GUIDE International, G.U.I.D.E. Europe, Japan GUIDE/SHARE (JGS), Guide Latin American (LAG), SHARE EUROPE, and SHARE Incorporated. Requirements satisfied include:

REQ00004160  Provide command to load help and message files
REQ00004513  Allow NetView Automation Table to automate on a
              full-screen msg
REQ00004514  Full-screen Automation Access
REQ00005851  Automation performance tool
REQ00005854  Pre-initialized program support for PL/1 and C
REQ00006093  Improvement needed to NetView message help file
              maintenance
REQ00006922  Provide online performance statistics
              (CPU, I/O, ETC.)
REQ00010063  NCP Auto handle PU-name vs. Loadmod
REQ00013264  Increase the "ACTIVE" alerts wrap count in NPDA
REQ00014213  Increase the total number of alerts "LIVE" in
              alerts dynamic
REQ00020355  GMF Comm Mgr messages should have Comm Mgr error and
              sense codes
REQ00020962  Include NetView Language requirements with LE/370
REQ00021568  Support of LE/370 by NetView
REQ00022143  Auto logoff of NetView users.
REQ00022549  Generic support for span of control
REQ00022650  NetView should support AD/CYCLE C and PL/I
REQ00024522  Provide full-screen 3270 sessions in NetView
              Autotasks.
REQ00024526  NetView optional OST Timeout.
REQ00024585  SPAN CHECK AT, EVERY, AFTER, and EXCMD
REQ00025824  Provide timeout for NetView UserIDs
REQ00028363  Allow parsing full screens in NetView.
REQ00036099  Single Parameter Library for Multiple NetViews.
REQ00036392  Allow User Access to NLDM and NPDA Databases
REQ00036460  Increase NPDA ALH
REQ00041021  chargeback accounting for NV OST CPU, I/O and MEMORY
             usage.
REQ00042121  GMF needs to be upward compatible with Host NetView
REQ00042525  NetView message correlation for (CNM4061,CNM411I,
              DWO154I,DSI503I)
REQ00042620  NetView query of hardware monitor data base
REQ00043510  Provide Interface to NLDM/NPDA for Automation
REQ00043523  RODM Access Tools
REQ00043525  VSAM access from NetView REXX command lists
REQ00043528  Capability to do full-screen automation
REQ00043784  NetView Dynamic DSISPN update
REQ00044371  NetView message queueing in MVS dataspace
REQ00045167  Support "INCLUDE" function for NIAF/2 parameter
              profiles
REQ00045361  Netlog browse should allow a command to flush the
              buffer
REQ00045443  VTAM SPAN Parameter on Model Statements for DDDLU
REQ00046043  NetView GMF resource status history
REQ00048438  Dynamic FLCVCORR when new objects are added.
REQ00048713  NMSM should display parallel bridges like LNM.
REQ00049212  Scope of Control for RODM-Applications
REQ00049351  NetView GMF automatically opening command response
              window
REQ00049729  Turn off beep that accompanies NPDA message BNJ1538I
REQ00049731  Allow NetView to override RACF OPERPARM values
REQ00049928  NGMF CM/2 NDF definitions
REQ00050812  GMF Server Security -- Limiting the Views Available
REQ00051595  Determine REXX command entered when synonyms exist
REQ00051800  Pre-init environments for C
REQ00053060  DSICBS ACTR needs to be increased
REQ00053228  Allow the use of fully qualified network names for
              GMF servers
REQ00053327  Continuous Availability of SNATM
REQ00053364  Propagate up the worst status to an Aggregate Object
REQ00053366  Incorporate MultiSystem Manager Functions
              in base NetView
REQ00053690  Ship NGMF with VTAM Display as default option
REQ00053727  Change Font used in NGMF Command Response windows
REQ00054170  Amendment to NIAF/2 Guide
REQ00054325  Need TOPOSNA messages to go back to operator who
              issued the cmd
REQ00054355  Need ability to view NLDM and NPDA database
              information from  NGMF
REQ00054502  Want Command Profile Editor to remember user ID
REQ00054506  Would like to set cursor position using VIEWCURROW
              and VIEWCURCOL
REQ00055895  Enhancements on DSI124I storage request failed
REQ00055897  Improve NetView recovery on storage shortage
REQ00056365  NetView CSCF SPAN security
REQ00056473  Click in a window to stop view cycling in NGMF
REQ00056486  Provide date and time search method for netlog-browse
              function
REQ00056488  Make BLOG part of NetView
REQ00056646  MultiSystem Manager NetFinity support / connection
REQ00056674  BNJMTERM must be added to IEAVTRML but needs to use
              RESMGR macro
REQ00056854  NETCONV ACTION=STOP command needs a correlated
              message response
REQ00056931  TASKUTIL enhancement
REQ00057169  AON/MVS panel interface needs work for VTAM V4R3
REQ00057638  BNH280I contains inaccurate information
REQ00058606  NetView Support lacking for LE370
REQ00058670  Object manipulation in NGMF under RACF control
REQ00059324  See OW20380 Timeout optional/configurable
REQ00059539  NGMF Command Response Window Pop-Up Actions
REQ00059968  German vowel support
REQ00060461  NetView support for LE370
REQ00046462  IST169I Automation



Planning Information

Customer Responsibilities: To learn about NetView for OS/390 new functions, tools, samples, demos, and other product information online using the Internet World Wide Web, see the TME 10 NetView for OS/390 homepage at:

    http://www.networking.ibm.com/nmv/nmvindex.html
To learn about MultiSystem Manager development tools online using the Internet World Wide Web, see the MultiSystem Manager homepage. A link to the MultiSystem Manager homepage can be found at:
    http://www.raleigh.ibm.com/nva/nvaover

    and

    http://www.raleigh.ibm.com/netsoft.html

Packaging: The three NetView for OS/390 packaging options build upon a common base. That base is the function included in the Unattended Option. It includes many useful functions including automation functions and RODM, and is mainly intended to support centralized network management by providing those functions necessary to allow information to be collected and acted upon at remote sites.

Refer to Technical Description in the Sales Manual for a chart that lists the specific functions available in the Unattended Option as well as for the additional functions mentioned below.

The Procedural Option includes base NetView for OS/390 functions, excluding NetView Graphic Monitor Facility, GMFHS, SNA Topology Manager, APPN Accounting Manager, the APPN Topology and Accounting Agent, and MultiSystem Manager.

The NetView for OS/390 Graphical Enterprise Option includes the base NetView for OS/390, NetView Graphic Monitor Facility (including downloadable workstation client/server and client code), GMFHS, RODM, SNA Topology Manager, APPN Accounting Manager (including the downloadable APPN Topology and Accounting Agent workstation code), Automated Operations Network, and MultiSystem Manager.

All three options include the NIAF/2 workstation code on the basic license media.

Tools and documentation which are specific to the creation of a host Topology Manager are provided on the MultiSystem Manager base feature product tape. After MultiSystem Manager is installed on MVS, refer to FLCVREAD in the SFLCSAM1 dataset to locate a document.

Resources which may be used for creation of a host topology manager or an Open Topology Agent are available in the IBM MKTTOOLS repository and at an FTP site on the Internet. The MKTTOOLS repository can be accessed by your IBM representative by issuing the VM command: TOOLCAT MKTTOOLS. Request the MSMDEV package.

To obtain MultiSystem Manager application development tools on the Internet, use anonymous FTP at:

    netview.cary.ibm.com
To learn about MultiSystem Manager development tools online using the Internet World Wide Web, see the MultiSystem Manager homepage. A link to the MultiSystem Manager homepage can be found at:
    www.raleigh.ibm.com/nva/nvaover

    and

    www.raleigh.ibm.com/netsoft.html

Optional materials available as described above include:
  • MultiSystem Manager for MVS/ESA: Topology Agent Developer's Toolkit
  • MultiSystem Manager for MVS/ESA: Topology Agent Developer's Guide
  • MultiSystem Manager for MVS/ESA: Sample Topology Agent
  • MultiSystem Manager for MVS/ESA: Topology Application Developer's FlowChart
  • MultiSystem Manager for MVS/ESA: Sample MVS Topology Manager
The topology agents for the various topology features are available as follows:
  • The topology agent for Topology Feature for NetWare is available as part of the Topology Feature for NetWare. The agent code is shipped with the Topology Feature for NetWare and may be downloaded or it is available on 3.5-inch diskette. To obtain the topology agent on 3.5-inch diskette, the media feature number for the diskette must be specified when ordering.

  • The topology agent for Topology Feature for Internet Protocol is available as part of the Topology Feature for Internet Protocol. The agent code is only available on 3.5-inch diskette. To obtain the topology agent on 3.5-inch diskette, the media feature number for the diskette must be specified when ordering.

  • The topology agent for Topology Feature for LAN Network Manager is provided with the LAN Network Manager product.

  • The topology agent for Topology Feature for LAN NetView Management Utilities is provided with the LAN NetView Management Utilities product.

  • The topology agent for ATM is available as part of the Topology Feature for ATM. The agent code is only available on 3.5-inch diskette. To obtain the topology agent on 3.5-inch diskette, the media feature number for the diskette must be specified when ordering.

  • The topology agent for NetFinity resources is provided with the NetFinity product.



System Integrity

IBM will accept APARs where the installation of NetView for OS/390 introduces an exposure to the system integrity of the operating system. NetView for OS/390 is intended to run authorized in the operating system environment.



Security, Auditability, and Control

Security and auditability features of NetView for OS/390 include:

  • Operator Logon Security: NetView facilities check an operator's authorization prior to NetView use. The logon authorization information can be stored in NetView or in security software, such as RACF. An authorized NetView for OS/390 operator or automated operator establishes the session used for the transfer of graphic status data between the host and workstation.

  • NGMF View Authorization: An NGMF operator can be restricted to a subset of views or resources within views. NGMF view authorization information can be stored in NetView or in security software, such as RACF.

  • Resource Control Authorization: An operator may be restricted to a subset of network resources. Resource control authorization information can be stored in NetView for OS/390 or in security software, such as RACF.

  • Command Authorization: An operator can be restricted to a subset of the commands available through NetView for OS/390. Authorization checking support also extends to keywords and values of ACF/VTAM commands. The command authorization authority information can be stored in NetView for OS/390 or in security software, such as RACF.

  • Administrative Security: NGMF Administrative tasks are allowed on any workstation by operators that have been authorized. These can be kept in a restricted access area.

  • Auditability: Operator messages and commands are logged. Logging can provide a hard copy audit trail of network operation activities. When commands are protected using RACF or the NetView command authorization table, SMF records can be generated for all commands or for specific commands.
Security software refers to IBM's Resource Access Control Facility (RACF), a user-written application or other security product supported by the MVS/ESA System Authorization Facility Interface (RACROUTE) macro.

If sensitive data is sent over external communication facilities, user management may wish to use cryptography.

The NetView Graphic Monitor Facility on the workstation uses the protection features of OS/2 that relate to memory access and the use of system-controlled resources.

User management is responsible for evaluation, selection, and implementation of security features, administrative procedures, and appropriate controls in application systems and communication facilities.



ORDERING INFORMATION



New Licensees

Orders for new licenses will be accepted now.

Shipment will begin on the planned availability date.

New users of TME 10 NetView for OS/390 should specify:

         Type           Model

5697 B82

Basic License

Graphical Enterprise Option: To order this option for the basic license, specify the program number and feature number 9001 for asset registration. For a graduated one-time charge or graduated monthly license charge, specify the feature number below that corresponds to the group that contains the designated machine.

Also, specify the feature number of the desired distribution medium.

The MultiSystem Manager Component, Topology Agents for NetWare, Internet Protocol, and ATM are only available on 3.5-inch diskettes requiring separate distribution media. However, they are available at no additional charge. To order any of these topology agents, specify the feature numbers of the desired distribution media.

Note: The Graphical Enterprise Option includes the NGMF workstation code, the Topology and Accounting Agent code, and the NIAF/2 workstation code, as well as the MultiSystem Manager and Automated Operations Network workstation code which can be downloaded to the workstation at no additional charge.

                 Basic                         Basic
               Graduated                     Graduated
                  OTC                           MLC
Group #      Feature Number                Feature Number

18 3018 3003 20 3019 3004 25 3020 3005 28 3021 3006 29 3022 3007 30 3023 3008 31 3024 3009 32 3025 3010 35 3026 3011 38 3027 3012 40 3028 3013 50 3029 3014 60 3030 3015 70 3031 3016 80 3032 3017


OTC=One-Time Charge

MLC=Monthly License Charge

Procedural Option: To order this option for the basic license, specify the program number and feature number 9001 for asset registration. For a graduated one-time charge or graduated monthly license charge, specify the feature number below that corresponds to the group that contains the designated machine.

Also, specify the feature number of the desired distribution medium.

Note: The Procedural Option includes the NIAF/2 workstation code which can be downloaded to the workstation at no additional charge.

                 Basic                         Basic
               Graduated                     Graduated
                  OTC                           MLC
Group #      Feature Number                Feature Number

18 3048 3033 20 3049 3034 25 3050 3035 28 3051 3036 29 3052 3037 30 3053 3038 31 3054 3039 32 3055 3040 35 3056 3041 38 3057 3042 40 3058 3043 50 3059 3044 60 3060 3045 70 3061 3046 80 3062 3047

Unattended Option: To order this option for the basic license, specify the program number and feature number 9001 for asset registration. For a graduated one-time charge or graduated monthly license charge, specify the feature number below that corresponds to the group that contains the designated machine.

Also, specify the feature number of the desired distribution medium.

Note: The Unattended Option includes the NIAF/2 workstation code which can be downloaded to the workstation at no additional charge.

                 Basic                         Basic
               Graduated                     Graduated
                  OTC                           MLC
Group #      Feature Number                Feature Number

18 3078 3063 20 3079 3064 25 3080 3065 28 3081 3066 29 3082 3067 30 3083 3068 31 3084 3069 32 3085 3070 35 3086 3071 38 3087 3072 40 3088 3073 50 3089 3074 60 3090 3075 70 3091 3076 80 3092 3077



Multiple Operating System -- PR/SM (TM) (MOSP)

Graphical Enterprise Option: To order this option for a graduated one-time charge or graduated monthly license charge, specify the feature number below that corresponds to the group that contains the designated machine.

Also, specify the feature number of the desired distribution media.

The MultiSystem Manager component Topology Agents for NetWare, Internet Protocol, and ATM are only available on 3.5-inch diskettes requiring separate distribution media. However, they are available at no additional charge. To order any of these topology agents, specify the feature numbers of the desired distribution media.

Note: The Graphical Enterprise Option includes the NGMF workstation code, the Topology and Accounting Agent code, and the NIAF/2 workstation code, as well as the MultiSystem Manager and Automated Operations Network workstation code which can be downloaded to the workstation at no additional charge.

               MOSP Basic                    MOSP Basic
               Graduated                     Graduated
                  OTC                           MLC
Group #      Feature Number                Feature Number

18 3108 3093 20 3109 3094 25 3110 3095 28 3111 3096 29 3112 3097 30 3113 3098 31 3114 3099 32 3115 3100 35 3116 3101 38 3117 3102 40 3118 3103 50 3119 3104 60 3120 3105 70 3121 3106 80 3122 3107

Procedural Option: To order this option for a graduated one-time charge or graduated monthly license charge, specify the feature number below that corresponds to the group that contains the designated machine.

Also, specify the feature number of the desired distribution media.

Note: The Procedural Option includes the NIAF/2 workstation code which can be downloaded to the workstation at no additional charge.

               MOSP Basic                    MOSP Basic
               Graduated                     Graduated
                  OTC                           MLC
Group #      Feature Number                Feature Number

18 3138 3123 20 3139 3124 25 3140 3125 28 3141 3126 29 3142 3127 30 3143 3128 31 3144 3129 32 3145 3130 35 3146 3131 38 3147 3132 40 3148 3133 50 3149 3134 60 3150 3135 70 3151 3136 80 3152 3137

Unattended Option: To order this option for a graduated one-time charge or graduated monthly license charge, specify the feature number below that corresponds to the group that contains the designated machine.

Also, specify the feature number of the desired distribution media.

Note: The Unattended Option includes the NIAF/2 workstation code which can be downloaded to the workstation at no additional charge.

               MOSP Basic                    MOSP Basic
               Graduated                     Graduated
                  OTC                           MLC
Group #      Feature Number                Feature Number

18 3168 3153 20 3169 3154 25 3170 3155 28 3171 3156 29 3172 3157 30 3173 3158 31 3174 3159 32 3175 3160 35 3176 3161 38 3177 3162 40 3178 3163 50 3179 3164 60 3180 3165 70 3181 3166 80 3182 3167

Note: The group can be determined by referring to either the Exhibit for IBM System/370 (TM) and System/390 Machines (Z125-3901) or the Exhibit for Non-IBM Machines (Z125-3902) that are associated with the IBM Customer Agreement (Z125-4575).

Entry Support License (ESL): To order an ESL license, specify the program number, feature number 9001 for asset registration, and the applicable ESL OTC feature number. Also specify the feature number of the desired distribution medium.

For the Graphical Enterprise Option, the MultiSystem Manager component Topology Agents for NetWare, Internet Protocol, and ATM are only available on 3.5-inch diskettes requiring separate distribution media. However, they are available at no additional charge. To order any of these topology agents for the Graphical Enterprise Option, specify the feature numbers of the desired distribution media.

                              ESL One-Time Charge
Description                      Feature Number

Graphical Enterprise Option 3000 Procedural Option 3001 Unattended Option 3002

Note: ESL machines can be determined by referring to the IBM Entry End User/390 Attachment (Z125-4379).



Parallel Sysplex License Charge (PSLC) Basic License

Graphical Enterprise Option:: To order this option for a basic license, specify the program number and feature number 9001 for asset registration. Specify the PSLC Base feature. If applicable, specify the PSLC Level A and PSLC Level B features and quantity.

If there is more than one program copy in a Parallel Sysplex, the charge for all copies is associated to one license by specifying the applicable PSLC feature numbers and quantity represented by the sum of the Service Units in Millions (MSUs) in your Parallel Sysplex. For all other program copies, specify the PSLC No-Charge (NC) Identifier feature on the licenses.

Also, specify the feature number of the desired distribution medium. The MultiSystem Manager component Topology Agents for NetWare, Internet Protocol, and ATM are only available on 3.5-inch diskettes requiring separate distribution media. However, they are available at no additional charge. To order any of these topology agents, specify the feature numbers of the desired distribution media.

Note: The Graphical Enterprise Option includes the NGMF workstation code, the Topology and Accounting Agent code, and the NIAF/2 workstation, code as well as the MultiSystem Manager and Automated Operations Network workstation code which can be downloaded to the workstation at no additional charge.

                      PSLC                PSLC Basic License
Machine               Feature             MLC Feature
MSU Capacity          Number              Description

1 3363 PSLC Base, 1 MSU 2 3364 PSLC Base, 2 MSUs

3 3365 PSLC Base, 3 MSUs

4 -- 45 3366 PSLC Level A, 1 MSU 3367 PSLC Level A, 42 MSUs

46 or more 3368 PSLC Level B, 1 MSU 3369 PSLC Level B, 10 MSUs 3370 PSLC Level B, 50 MSUs

NA 3371 PSLC N/C ID

Example 1: For a single machine with 11 MSUs, the PSLC features would be 3365 -- quantity 1 and 3366 -- quantity 8.

Example 2: For two machines in a Parallel Sysplex which have an aggregation of 60 MSUs, the PSLC features would be:

  • PSLC chargeable license #1: 3365 -- quantity 1, 3367 -- quantity 1, 3368 -- quantity 5, and 3369 -- quantity 1

  • PSLC no-charge license #2: 3371 -- quantity 1
Procedural Option: To order this option for a basic license, specify the program number and feature number 9001 for asset registration. Specify the PSLC Base feature. If applicable, specify the PSLC Level A and PSLC Level B features and quantity.

If there is more than one program copy in a Parallel Sysplex, the charge for all copies is associated to one license by specifying the applicable PSLC feature numbers and quantity represented by the sum of the Service Units in Millions (MSUs) in your Parallel Sysplex. For all other program copies, specify the PSLC No-Charge (NC) Identifier feature on the licenses.

Also, specify the feature number of the desired distribution medium.

Note: The Procedural Option includes the NIAF/2 workstation code which can be downloaded to the workstation at no additional charge.

                      PSLC                PSLC Basic License
Machine               Feature             MLC Feature
MSU Capacity          Number              Description

1 3372 PSLC Base, 1 MSU 2 3373 PSLC Base, 2 MSUs

3 3374 PSLC Base, 3 MSUs

4 -- 45 3375 PSLC Level A, 1 MSU 3376 PSLC Level A, 42 MSUs

46 or more 3377 PSLC Level B, 1 MSU 3378 PSLC Level B, 10 MSUs 3379 PSLC Level B, 50 MSUs

NA 3600 PSLC N/C ID

Example 1: For a single machine with 11 MSUs, the PSLC features would be 3374 -- quantity 1 and 3375 -- quantity 8.

Example 2: For two machines in a Parallel Sysplex which have an aggregation of 60 MSUs, the PSLC features would be:

  • PSLC chargeable license #1: 3374 -- quantity 1, 3376 -- quantity 1, 3377 -- quantity 5, and 3378 -- quantity 1

  • PSLC no-charge license #2: 3600 -- quantity 1
Unattended Option: To order this option for a basic license, specify the program number and feature number 9001 for asset registration. Specify the PSLC Base feature. If applicable, specify the PSLC Level A and PSLC Level B features and quantity.

If there is more than one program copy in a Parallel Sysplex, the charge for all copies is associated to one license by specifying the applicable PSLC feature numbers and quantity represented by the sum of the Service Units in Millions (MSUs) in your Parallel Sysplex. For all other program copies, specify the PSLC No-Charge (NC) Identifier feature on the licenses.

Also, specify the feature number of the desired distribution medium.

Note: The Unattended Option includes the NIAF/2 workstation code which can be downloaded to the workstation at no additional charge.

                      PSLC                PSLC Basic License
Machine               Feature             MLC Feature
MSU Capacity          Number              Description

1 3601 PSLC Base, 1 MSU 2 3602 PSLC Base, 2 MSUs

3 3603 PSLC Base, 3 MSUs

4 -- 45 3604 PSLC Level A, 1 MSU 3605 PSLC Level A, 42 MSUs

46 or more 3606 PSLC Level B, 1 MSU 3607 PSLC Level B, 10 MSUs 3608 PSLC Level B, 50 MSUs

NA 3609 PSLC N/C ID

Example 1: For a single machine with 11 MSUs, the PSLC features would be 3603 -- quantity 1 and 3604 -- quantity 8.

Example 2: For two machines in a Parallel Sysplex which have an aggregation of 60 MSUs, the PSLC features would be:

  • PSLC chargeable license #1: 3603 -- quantity 1, 3605 -- quantity 1, 3606 -- quantity 5, and 3607 -- quantity 1

  • PSLC no-charge license #2: 3609 -- quantity 1



Indexed Monthly License Charge (IMLC) Basic License

Graphical Enterprise Option: For this option to order a basic license, specify the program number and feature number 9001 for asset registration. Specify the IMLC Base 80 MSU feature and the applicable additional IMLC MSU features and quantity corresponding to the MSU rating of the designated machine.

Also, specify the feature number of the desired distribution medium.

The MultiSystem Manager component Topology Agents for NetWare, Internet Protocol, and ATM are only available on 3.5-inch diskettes requiring separate distribution media. However, they are available at no additional charge. To order any of these topology agents, specify the feature numbers of the desired distribution media.

Note: The Graphical Enterprise Option includes the NGMF workstation code, the Topology and Accounting Agent code, and the NIAF/2 workstation code, as well as the MultiSystem Manager and Automated Operations Network workstation code which can be downloaded to the workstation at no additional charge.

IMLC                IMLC Basic License
Feature             MLC Feature
Number              Description

3610 IMLC Base 80 MSUs 3611 IMLC 1 MSU 3612 IMLC 10 MSUs 3613 IMLC 50 MSUs

Procedural Option: For this option to order a basic license, specify the program number and feature number 9001 for asset registration. Specify the IMLC Base 80 MSU feature and the applicable additional IMLC MSU features and quantity corresponding to the MSU rating of the designated machine.

Also, specify the feature number of the desired distribution medium.

Note: The Procedural Option includes the NIAF/2 workstation code which can be downloaded to the workstation at no additional charge.

IMLC                IMLC Basic License
Feature             MLC Feature
Number              Description

3614 IMLC Base 80 MSUs 3615 IMLC 1 MSU 3616 IMLC 10 MSUs 3617 IMLC 50 MSUs

Unattended Option: For this option to order a basic license, specify the program number and feature number 9001 for asset registration. Specify the IMLC Base 80 MSU feature and the applicable additional IMLC MSU features and quantity corresponding to the MSU rating of the designated machine.

Also, specify the feature number of the desired distribution medium.

Note: The Unattended Option includes the NIAF/2 workstation code which can be downloaded to the workstation at no additional charge.

IMLC                IMLC Basic License
Feature             MLC Feature
Number              Description

3618 IMLC Base 80 MSUs 3619 IMLC 1 MSU 3620 IMLC 10 MSUs 3621 IMLC 50 MSUs

Single Version Charging: To elect single version charging, the customer must notify and identify to IBM the prior program and replacement program and the designated machine the programs are operating on.

Version-to-Version Upgrade Credit: To upgrade from a prior program acquired for a one-time charge to a replacement program using a version-to-version upgrade credit, the customer must notify and identify to IBM the applicable prior program and replacement program participating in the upgrade credit.

Basic Machine-Readable Material: To order, select the feature number of the desired distribution medium.

TME 10 NetView for OS/390 English

                      Feature           Distribution
Environment           Number            Medium

Graphical Enterprise Option 5811 9/6250 magnetic tape for LE/370 5812 3480 tape cartridge (U.S. English) 5501 4-mm magnetic tape

Procedural Option 5831 9/6250 magnetic tape for LE/370 5832 3480 tape cartridge (U.S. English) 5503 4-mm magnetic tape

Unattended Option 5851 9/6250 magnetic tape for LE/370 5852 3480 tape cartridge (U.S. English) 5505 4-mm magnetic tape

Graphical Enterprise Option 5801 9/6250 magnetic tape for C/370 5802 3480 tape cartridge (U.S. English) 5500 4-mm magnetic tape

Procedural Option 5821 9/6250 magnetic tape for C/370 5822 3480 tape cartridge (U.S. English) 5502 4-mm magnetic tape Unattended Option 5841 9/6250 magnetic tape for C/370 5842 3480 tape cartridge (U.S. English) 5504 4-mm magnetic tape

TME 10 NetView for OS/390 MultiSystem Manager Agents English

                      Feature           Distribution
Environment           Number            Medium

Topology Agent for 5805 3.5-inch diskette NetWare

Topology Agent for 5815 3.5-inch diskette Internet Protocol

Topology Agent for 5825 3.5-inch diskette ATM

TME 10 NetView for OS/390 Japanese

                      Feature           Distribution
Environment           Number            Medium

Graphical Enterprise Option 5083 9/6250 magnetic tape for LE/370 5084 3480 tape cartridge (Japanese) 5085 4-mm magnetic tape

Procedural Option 5089 9/6250 magnetic tape for LE/370 5090 3480 tape cartridge (Japanese) 5091 4-mm magnetic tape

Unattended Option 5095 9/6250 magnetic tape for LE/370 5096 3480 tape cartridge (Japanese) 5097 4-mm magnetic tape

Graphical Enterprise Option 5080 9/6250 magnetic tape for C/370 5081 3480 tape cartridge (Japanese) 5082 4-mm magnetic tape

Procedural Option 5086 9/6250 magnetic tape for C/370 5087 3480 tape cartridge (Japanese) 5088 4-mm magnetic tape

Unattended Option 5092 9/6250 magnetic tape for C/370 5093 3480 tape cartridge (Japanese) 5094 4-mm magnetic tape

TME 10 NetView for OS/390 MultiSystem Manager Agents Japanese

                      Feature           Distribution
Environment           Number            Medium

Topology Agent for 5125 3.5-inch diskette NetWare

Topology Agent for 5126 3.5-inch diskette Internet Protocol

Topology Agent for 5127 3.5-inch diskette ATM

Customization Options: Select the appropriate feature numbers to customize your order to specify the delivery options desired. These features can be specified on the initial or MES orders.

Example: If publications are not desired for the initial order, specify feature number 3470 to ship media only. For future updates, specify feature number 3480 to ship media updates only. If, in the future, publication updates are required, order an MES to remove feature number 3480; then, the publications will ship with the next release of the program.

                                                    Feature
Description                                         Number

Initial Shipments

Serial Number Only (suppresses shipment 3444 of media and documentation)

Ship Media Only (suppresses initial 3470 shipment of documentation)

Ship Documentation Only (suppresses 3471 initial shipment of media)

Update Shipments

Ship Media Updates Only (suppresses 3480 update shipment of documentation)

Ship Documentation Only (suppresses 3481 update shipment of media)

Suppress Updates (suppresses update 3482 shipment of media and documentation)

Expedite Shipments

Local IBM Office Expedite 3445 (for IBM use only)

Customer Expedite Process Charge 3446 ($30 charge for each product)

Expedite shipments will be processed to receive 72-hour delivery from the time IBM Software Manufacturing Solutions (SMS) receives the order. SMS will then ship the order via overnight air transportation.



DSLO License

To order a DSLO license, specify the program number and feature number 9901 for asset registration. For a graduated one-time charge or for a graduated monthly license charge, specify the feature numbers below for the options desired and that corresponds to the group containing the designated machine.

Graphical Enterprise Option

                                                DSLO
                  DSLO                       Graduated
               Graduated                      Monthly
            One-Time-Charge                License Charge
Group        Feature Number                Feature Number

18 3198 3183 20 3199 3184 25 3200 3185 28 3201 3186 29 3202 3187 30 3203 3188 31 3204 3189 32 3205 3190 35 3206 3191 38 3207 3192 40 3208 3193 50 3209 3194 60 3210 3195 70 3211 3196 80 3212 3197

Procedural Option

                                                DSLO
                  DSLO                       Graduated
               Graduated                      Monthly
            One-Time-Charge                License Charge
Group        Feature Number                Feature Number

18 3228 3213 20 3229 3214 25 3230 3215 28 3231 3216 29 3232 3217 30 3233 3218 31 3234 3219 32 3235 3220 35 3236 3221 38 3237 3222 40 3238 3223 50 3239 3224 60 3240 3225 70 3241 3226 80 3242 3227

Unattended Option

                                                DSLO
                  DSLO                       Graduated
               Graduated                      Monthly
            One-Time-Charge                License Charge
Group        Feature Number                Feature Number

18 3258 3243 20 3259 3244 25 3260 3245 28 3261 3246 29 3262 3247 30 3263 3248 31 3264 3249 32 3265 3250 35 3266 3251 38 3267 3252 40 3268 3253 50 3269 3254 60 3270 3255 70 3271 3256 80 3272 3257

Multiple Operating System -- PR/SM (MOSP): For a graduated one-time charge or graduated monthly license charge, specify the following feature number below that corresponds to the group that contains the designated machine.

Graphical Enterprise Option

               MOSP DSLO                     MOSP DSLO
               Graduated                     Graduated
            One-Time-Charge            Monthly License Charge
Group        Feature Number                Feature Number

18 3288 3273 20 3289 3274 25 3290 3275 28 3291 3276 29 3292 3277 30 3293 3278 31 3294 3279 32 3295 3280 35 3296 3281 38 3297 3282 40 3298 3283 50 3299 3284 60 3300 3285 70 3301 3286 80 3302 3287

Procedural Option

               MOSP DSLO                     MOSP DSLO
               Graduated                     Graduated
            One-Time-Charge            Monthly License Charge
Group        Feature Number                Feature Number

18 3318 3303 20 3319 3304 25 3320 3305 28 3321 3306 29 3322 3307 30 3323 3308 31 3324 3309 32 3325 3310 35 3326 3311 38 3327 3312 40 3328 3313 50 3329 3314 60 3330 3315 70 3331 3316 80 3332 3317

Unattended Option

               MOSP DSLO                     MOSP DSLO
               Graduated                     Graduated
            One-Time-Charge            Monthly License Charge
Group        Feature Number                Feature Number

18 3348 3333 20 3349 3334 25 3350 3335 28 3351 3336 29 3352 3337 30 3353 3338 31 3354 3339 32 3355 3340 35 3356 3341 38 3357 3342 40 3358 3343 50 3359 3344 60 3360 3345 70 3361 3346 80 3362 3347

Ordering a DSLO feature will result in IBM maintaining a record of this customer location as a DSLO user only. All material for the DSLO license must be ordered by the basic licensee. If a user selects DSLO, no other feature numbers are valid for this order and no program materials or updates will be shipped.



Unlicensed Documentation

Three program directories and a CD-ROM containing all NetView for OS/390 publications are supplied automatically with the basic machine-readable material. Additionally, one hardcopy of the following publications is also supplied automatically with the basic machine-readable material.

                                                  Order
Title                                             Number

TME 10 NetView for OS/390 Version 1 Release 1: Administration and Security Reference SC31-8222 Diagnosis Guide LY43-0108 Installation and Administration Guide SC31-8236 Planning Guide GC31-8226 User's Guide SC31-8241 Tuning Guide SC31-8240 Tutorial SK2T-6097

TME 10 NetView for OS/390 Automated Operation Network Version 1 Release 1: Planning and Installation Guide SC31-8465 Operator's Guide SC31-8466 LAN Automation Guide SC31-8468 SNA Automation Guide SC31-8469

Note that the following publications are only provided in softcopy format on the CD-ROM.

                                                  Order
Title                                             Number

Library Reference (softcopy only) Messages Manual (softcopy only)

Customers of record may also order one copy each of the following publications at no charge.

                                                  Order
Title                                             Number

TME 10 NetView for OS/390 Version 1 Release 1: Application Programming Guide SC31-8223 APPN Topology and Accounting Agent Guide SC31-8224 Automation Guide SC31-8225 Bridge Implementation SC31-8238 Command Reference SC31-8227 Customization Guide SC31-8228 Customization: Using Assembler SC31-8229 Customization: Using PL/I and C SC31-8230 Customization: Using REXX and the NetView Command List Language SC31-8231 Customization: Using Pipes SC31-8248 Data Model Reference SC31-8232 Graphic Monitor Facility User's Guide SC31-8234 RODM & GMFHS Programming Guide SC31-8233 SNA Topology Manager and APPN Accounting Manager Implementation Guide SC31-8239 Order Title Number

TME 10 NetView for OS/390 MultiSystem Manager Version 1 Release 1: ATM Networks SC31-8281 NetFinity Networks SC31-8301 LAN NetView Management Utilities Networks SC31-8459 Novell NetWare Networks SC31-8460 OS/2 LAN Network Manager Networks SC31-8461 Internet Protocol Networks SC31-8462 Open Topology Interface SC31-8463

TME 10 NetView for OS/390 Automated Operation Network Version 1 Release 1: Programmer's Guide SC31-8464 Customization Guide SC31-8467 TCP/IP Automation Guide SC31-8470

Additional copies of unlicensed publications will be available for a fee after availability. These copies may be ordered from your IBM representative, through the System Library Subscription Service (SLSS), or by direct order.

All of the above publications can be ordered using the bill of forms number indicated below.

                                                  Order
Title                                             Number

TME 10 NetView for OS/390 Unentitled Publications SBOF-7014

The entire library of unlicensed publications for TME 10 NetView for OS/390 can be ordered using the bill of forms number indicated below.

                                                  Order
Title                                             Number

TME 10 NetView for OS/390 Complete Library SBOF-7013



Displayable Softcopy Publications

TME 10 NetView for OS/390 manuals are offered in displayable softcopy form. All manuals are included. The files are shipped on CD-ROM.

The first copy of the following softcopy material is available at no charge to licensees of basic material and supplied automatically with the basic machine-readable material.

    .                                             Order
Title                                             Number

TME 10 NetView for OS/390 Online Library LK2T-9133

These displayable manuals can be used with the BookManager (R) READ licensed programs in any of the supported environments. Also included on the CD-ROM with the displayable softcopy manuals is the Library Reader (TM), to allow READ-ONLY viewing of the manuals. Terms and conditions for use of the machine-readable files are shipped with the files.



Licensed Documentation

The following licensed material will be available from IBM by March 28, 1997. To order, contact your IBM representative.

The first copy is available at no charge to licensees of basic material and supplied automatically with the basic machine-readable material.

                                                  Order
Title                                             Number

TME 10 NetView for OS/390 Diagnosis Guide LY43-0108

Subsequent updates (technical newsletters or revisions between releases) to the publications shipped with the product will be distributed to the user of record for as long as a license for this software remains in effect. A separate publication order or subscription is not needed.



TERMS AND CONDITIONS

Licensing: IBM Customer Agreement

The NetView for OS/390 program contains components that execute on either a designated machine or execute on a workstation. The following components execute on a workstation. The workstation components may be used on any workstation concurrently for use in conjunction with the licensed host component. The workstation components of NetView for OS/390 are:

  • NetView Graphic Monitor Facility
  • Topology Agent for ATM
  • Topology Agent for Internet Protocol
  • Topology Agent for NetWare
  • APPN Topology and Accounting Agent
  • Automation Agent (RTAP)
  • NetView Installation and Administration Facility/2
Variable Charges Apply: Yes

Installation License or Location License Applies: No

Usage License Applies: No

Educational Allowance: Yes, to qualified education customers

Volume Discount: Not applicable

Version-To-Version Upgrade Credits Apply: Yes

Replaced Program(s)      Replacement Program(s)             Single
Program   Program        Program  Program                   Version
Number    Name           Number   Name                      Charging
                                                            Applies

5655-007 NetView V3 5697-B82 TME 10 NetView for OS/390 Yes

5685-111 NetView V2 5697-B82 TME 10 NetView for OS/390 Yes MVS/ESA

5685-138 NetView V2 5697-B82 TME 10 NetView for OS/390 Yes MVS/XA

5685-152 NetView V1 5697-B82 TME 10 NetView for OS/390 Yes MVS/ESA

5665-362 NetView V1 5697-B82 TME 10 NetView for OS/390 Yes MVS/XA

5655-126 NetView 5697-B82 TME 10 NetView for OS/390 Yes MultiSystem Manager MVS/ESA V2

5655-044 NetView 5697-B82 TME 10 NetView for OS/390 Yes MultiSystem Manager MVS/ESA V1

5695-178 SystemView (R) 5697-B82 TME 10 NetView for OS/390 Yes Automated Operations Network/MVS V1

5645-004 Network 5697-B82 TME 10 NetView for OS/390 Yes Management for MVS V1

5697-B82 TME 10 NetView To a follow-on, if any NA for OS/390

Warranted: Yes

Licensed Program Materials Availability

  • Restricted Materials of IBM -- None

  • Non-Restricted Source Materials -- None

  • Object Code Only (OCO) -- All
Testing Period: -- Two Months (Basic License only)

Program Services

  • Support Center applies -- Yes

  • Available until discontinued -- 12 months' written notice

  • APAR Mailing Address:
    IBM Corporation
    Dept. AEJ, Bldg. 503
    P.O. Box 12195
    Research Triangle Park, NC 27709
Services for DSLO Licenses: Provided through Basic License location

Support Line: S/390



CHARGES

Contact your IBM representative for charges information for this announcement.



CALL NOW TO ORDER

To order, contact IBM North America Sales Call Center, your local IBM representative, or your IBM Business Partner (TM).

IBM North America Sales Call Center, our national direct marketing organization, can also arrange to put your name on the mailing list for catalogs of IBM products.

 Phone:     800-IBM-CALL
 Fax:       800-2IBM-FAX
 Internet:  ibm_direct@vnet.ibm.com
 Mail:      IBM North America Call Sales Center
            Dept. YE010
            P.O. Box 16848
            Atlanta, GA  30321-0848
 Reference: YE010

To identify your local IBM Business Partner or IBM representative, call 800-IBM-4YOU.

Note: Shipments will begin after the planned availability date.

Trademarks

      OS/390, C/370, Parallel Sysplex, MVS/ESA, DATABASE 2,
      POWERstation, Nways, DatagLANce, SP, MVS/XA, VSE/ESA, RACF,
      3090, PR/SM, System/370, Library Reader, and Business Partner
      are trademarks of International Business Machines Corporation
      in the United States or other countries or both.
      NetView, MVS, VTAM, System/390, APPN, AD/Cycle, OS/2, AIX,
      NetFinity, ReDiscovery, Open Blueprint, Operating System/2,
      DB2, POWERserver, RISC System/6000, LPDA, AT, S/390, ACF/VTAM,
      VM/ESA, AS/400, SAA, BookManager, and SystemView are registered
      trademarks of International Business Machines Corporation in
      the United States or other countries or both.
      TME 10 and TME are registered trademarks of Tivoli Systems,
      Inc.  in the United States or other countries or both.
      Other company, product, and service names may be trademarks or
      service marks of others.