Tivoli Operations Planning and Control Enhances Business Systems Integration and Expands Function

Software Announcement
June 23, 1998
Announcement Letter Number: 298-217

Table of Contents:



At a Glance

  • Enables you to manage job scheduling from a unique business systems perspective through the instrumentation of the Tivoli OPC product

  • Expands job scheduling in your enterprise by adding new tracker agents for Digital UNIX and OS/390 UNIX

  • Enables administrators to start and track SAP R/3 jobs from Tivoli OPC with the exploitation of Extended Agent technology

  • Increases communication reliability by using the standard TCP/IP C-Socket interface

  • Increases flexibility in managing large workloads with the removal of the maximum limits in several areas

  • Reduces the need for skilled personnel at remote locations through centralized workload management 

-----------------------------------------
For ordering, contact:
  Your IBM representative, an IBM
  Business Partner, or IBM North America
  Sales Centers at
    800-IBM-CALL  Reference: YE010


EXTRA! EXTRA! . . .


Subscribe to IBM iSource, your electronic
 source for customized IBM information!
 Go to our web site at
http://www.ibm.com/isource
 or send an e-mail to
 info@isource.ibm.com
 with the word SUBSCRIBE in the body.



Overview

Tivoli Operations Planning and Control (OPC (TM)) plans, manages, and automates production workloads from a single point of control. It can span from a single-image OS/390 (TM) system to complex, distributed, multivendor networks. It uses open interfaces to enable communication with IBM and non-IBM operating environments.

OPC Tracker Agents and SAP R/3 Support

Tivoli OPC enhances business systems integration with:

  • Expanded tracker agent support for:
    • Digital UNIX (R)
    • OS/390 UNIX
  • Support for SAP/R3 jobs through the exploitation of Tivoli Workload Scheduler Extended Agent technology
This support is in addition to the previously announced support for OS/390, MVS/ESA (TM), AIX (R), OS/2 (R), Windows (TM)/NT, OS/400 (R), HP-UX, SunOS, Sun Solaris, DEC Open/MVS (TM) and Pyramid MIPS ABI workloads.

With the addition of the OPC Tracker Agents and the SAP R/3 support, you can now manage the workloads on Digital UNIX and OS/390 UNIX systems from a single point of control -- your S/390 (R) system. The OPC Tracker Agents automatically perform full function workload management from the Tivoli OPC controller system. This centralized workload management reduces the need for skilled personnel at remote locations and helps you manage your distributed systems in a cost-effective way.

Support for the Job Scheduling Business System of Tivoli GEM

Tivoli OPC has been instrumented to support the Job Scheduling Business System of the Tivoli GEM Systems Management Business System. This enables you to manage this strategic application from a unique business systems perspective, focusing your IT resources on keeping these systems healthy and productive.

Expands Function

In order to help users be more productive, OPC delivers the following:

  • TCP/IP communication improvements

  • Catalog management enhancements

  • Dataset delete function (EQQDELDS) improvements

  • Removal of maximum limits in several areas

Product Name Change

Tivoli Operations Planning and Control Version 2 Release 2 is the follow-on release to TME 10 (TM) Operations Planning and Control Version 2 Release 1. It has been renamed from TME 10 OPC to Tivoli OPC.



Intended Customers

  • Customers who want the availability of enterprise-wide scheduling. Tivoli OPC provides the ability to view and manage independent workloads across your diverse networks.



Key Prerequisites

  • Tivoli OPC runs on MVS/ESA and OS/390

  • Additional software, required for specific functions is specified under Technical Information



Planned Availability Date

June 26, 1998

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

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

Key areas of enhancements in Release 2 are described in the following sections.

Instrumentation for Tivoli Global Enterprise Manager: Tivoli OPC has been instrumented to support the Job Scheduling Business System of the Tivoli GEM Systems Management Business System. From the Tivoli GEM console, a Tivoli OPC user has complete control of all the Tivoli OPC components, regardless of the platform on which they run, having a unique point of management for all of them. In more detail, the Tivoli OPC instrumentation for Tivoli GEM enables you to do the following:

  • Show all the Tivoli OPC components, including controllers, stand-by controllers, OS/390 trackers, AS/400 (R) tracker agents, TCP/IP connected tracker agents.

  • Show the different links between the above components. This provides, at a glance, a check on the health of the connections. For example, an OS/390 tracker might be running but may not be connected to the controller.

  • Graphically manage monitors and:
    • Ask for value of the monitor
    • Be notified when the value of the monitor changes
    • Associate a severity with each monitor value
  • Start and stop Tivoli OPC trackers without logging them on

  • Know at a glance, in a sysplex environment, which is the active controller and which is the stand-by.

  • Execute commands on Tivoli OPC components, using the same point of control, regardless of the platform and operating system used for that component.

SAP R/3 Support: Tivoli OPC has been enhanced to exploit the Extended Agent technology of Tivoli Workload Scheduler. This technology enables Tivoli OPC to interface with a number of third party applications that can perform scheduling. By using this technology, you can now start and track a SAP R/3 job from Tivoli OPC. You can also retrieve and display the job log at the Tivoli OPC controller. This function is available via one of the following Tivoli OPC components:
  • Tracker Agent for Sun Solaris
  • Tracker Agent for Windows/NT
  • Tracker Agent for HP-UX
  • Tracker Agent for AIX
  • Tracker Agent for Digital UNIX
TCP/IP Communication Improvements: The TCP/IP communication component that enables the controller to communicate with the TCP/IP connected tracker agents has been restructured to use the standard TCP/IP C-Socket interface. This change enables Tivoli OPC for the latest OS/390 releases and provides for the use of the standard TCP/IP features. One example is the KEEPALIVE option. When this TCP/IP feature is used, the communication between the controller and the tracker agents is even more reliable.

Catalog Management Enhancements: The logic that Tivoli OPC uses when determining which catalog management actions to perform has been extended to manage the following situations:

  • Some steps in a job are not executed, but are flushed. The datasets referred to in those steps are ignored by the catalog management function.

  • A dataset referred to with disposition NEW in one step is also referred to in other steps. Logic to determine the action to perform in these cases has been added to the Catalog Management function.

Dataset Delete Function (EQQDELDS) Improvements: The Dataset Delete function has been enhanced to determine the correct action when a dataset referred to with disposition NEW in one step is also referred to in other steps. Logic to determine the correct action to perform in these cases has been added to the Catalog Management function. The Dataset Delete function has also been improved to do the following:
  • Delete the datasets with an expiration date.

  • Issue diagnostic information when the IDCAMS DELETE command or the DFHSM ARCHDEL command fails to delete a dataset.

Current Plan Occurrence Limit Removal: The maximum number of occurrences in the current plan has been increased from 32767 to 9999999. This enhancement gives you more flexibility in managing the current plan when you have large workloads.

Operations in Application Description Limit Removal: You can now define up to 255 operations in each Application Description. This enhancement provides for more flexibility in the definition of the workload.

Application Description and Operator Instructions Consistency Check: The consistency between the Application Description and the Operator Instruction OPC databases is now enforced by OPC. For instance, whenever an operation is deleted the associated operator instructions are also deleted. Some usability enhancements have also been implemented in the Application Description dialogs when defining operator instructions. For example, you can now also access temporary operator instructions.

JCL Editing from Application Description Dialogs: You can now customize the Tivoli OPC dialogs so that a library management application used in the customer's environment to manage the production jobs can be invoked from the Application Description OPC dialogs, thus increasing user productivity. New row commands have been added to invoke such an application from the Operation List panel while working with an Application Description.

OPC Control Language Tool: The OPC Control Language (OPCL) tool enables you to access and manipulate Tivoli OPC data by using a REXX-like language. Several macro-functions are made available that perform, in a single action, what would require several invocations of the OPC Program Interface functions. The OCL tool acts as an extension to the REXX language processor. Therefore, normal REXX statements can be coded together with OCL statements. This tool runs in a batch TSO session.

Tracker Agents: New Tracker Agents are provided to control the workload on:

  • Digital UNIX
  • OS/390 UNIX
SmartBatch Coexistence: Tivoli OPC has been extensively tested to make sure that all the features continue to work correctly when the production workload is under SmartBatch control.

Other Small Enhancements

  • EQQZSUBX 16 MB limit removal: because it is no longer necessary to move the JCL buffer below the 16 MB line before submitting it to JES2 or JES3, this processing has been removed from Tivoli OPC.

  • All invocations of the STIMER macro have been changed to STIMERM, to improve the robustness of Tivoli OPC.

  • Tivoli OPC Job-Submit user exit (EQQUX001) has been improved by adding two new parameters: WorkstationID and ErrorCode. When ErrorCode is set, job submission will not be performed by Tivoli OPC.

  • Tivoli OPC Operation-Status-Change user exit (EQQUX007) has been improved by adding the procstep name to the JOBAREA parameter. This enhancement provides for fully automated problem management.

  • Debugging aids for performance problems: new statistics are now produced by Tivoli OPC to trace all the activities performed during the job submission process. These statistics are especially useful when you perform tuning activities, to maximize the job throughput in Tivoli OPC. You can dynamically activate and deactivate these statistics by means of new MODIFY commands.



Year 2000

This product is Year 2000 ready. When used in accordance with its associated documentation, it is capable of correctly processing, providing, and/or receiving date data within and between the 20th and 21st centuries, provided all other products (for example, software, hardware, and firmware) used with the product properly exchange accurate date data with it.



REFERENCE INFORMATION

For information on previously available functions in OPC, refer to Software Announcement 297-075 dated March 25, 1997.

Trademarks 

      OPC, OS/390, MVS/ESA, and MVS are trademarks of International
      Business Machines Corporation in the United States or other
      countries or both.
      AIX, OS/2, OS/400, S/390, and AS/400 are registered trademarks
      of International Business Machines Corporation in the United
      States or other countries or both.
      Windows is a trademark of Microsoft Corporation.
      UNIX is a registered trademark in the United States and other
      countries exclusively through X/Open Company Limited.
      TME 10 is a trademark 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



EDUCATION SUPPORT

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

For current information on Tivoli System education, call 800-2tivoli (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:

For current information on IBM Education and Training courses in the US, contact 800-IBM-TEACH (426-8322). Outside the U.S., contact your local IBM E&T contact. Worldwide information is also available on the IBM E&T home page on the Internet at:



TECHNICAL INFORMATION



Specified Operating Environment

Hardware Requirements: This product uses only existing attachment interfaces.

Tivoli OPC (TM) operates on any IBM hardware configuration supported by one of the following:

  • OS/390 (TM) Version 2 (5647-A01)
  • OS/390 Version 1 (5645-001)
  • MVS/ESA (TM) SP (TM) Version 5 (5655-068, 5655-069)
The GUI for Application Description requires, at minimum, a Pentium (TM) 90 processor or equivalent with 16 MB of RAM, and 10 MB of disk space for use by the GUI, capable of running Operating System/2 (R) (OS/2 (R)) Warp Version 3 or Version 4, with Communications Manager/2 Version 1.1 or later, or Communications Server Version 4. It also requires a display with at least 800x600 resolution.

Workload Monitor/2 requires a personal computer with a minimum of 8 MB of RAM, and 2 MB of disk space for use by Workload Monitor/2, capable of running OS/2 Version 2 Release 1, or OS/2 Warp Version 3 or Version 4, with Communications Manager/2/2 or Extended Services for OS/2 (R). 12 MB of RAM is recommended for performance reasons.

The Tracker Agent for OS/2 requires a computer capable of running OS/2 Version 2 Release 1, or OS/2 Warp Version 3 or Version 4. The Tracker Agent uses about 1 MB of RAM.

The Tracker Agent for Windows NT (R) requires an Intel-based computer (486 or higher) capable of running Windows NT Version 3 Release 5 or Release 5.1, or Version 4. The Tracker Agent uses about 1 MB of RAM.

The Tracker Agent for OS/400 (R) requires an AS/400 (R) computer with a minimum of 3 MB of storage capable of running OS/400 Version 3 Release 1 or later, or an AS/400 RISC computer with a minimum of 6 MB of storage capable of running OS/400 Version 3 Release 6 or later. 8 MB storage is recommended for performance reasons.

The Tracker Agent for AIX/6000 (R) requires an RS/6000 (TM) computer with a minimum of 3 MB of RAM, capable of running AIX/6000 Version 3 Release 2 or Version 4. 8 MB of RAM is recommended for performance reasons.

The Tracker Agent for HP-UX requires a 700-series computer capable of running HP-UX Version 9, Version 10, or Version 11. The Tracker Agent uses between 500 KB and 1 MB of memory.

The Tracker Agent for Sun Solaris requires a SPARC computer capable of running Solaris Version 2 Release 3. The Tracker Agent uses between 500 KB and 1 MB of memory.

The Tracker Agent for SunOS requires a SPARC computer capable of running SunOS Version 4 Release 1 Modification Level 3. The Tracker Agent uses between 500 KB and 1 MB of memory.

The Tracker Agent for DEC OpenVMS requires a DEC VAX computer with at least 16 MB of memory or a DEC Alpha computer with at least 32 MB of memory, capable of running OpenVMS Version 7.0 to Version 7.1. The Tracker Agent uses about 1 MB of memory.

The Tracker Agent for Pyramid MIPS ABI requires a Pyramid Nile 100 or Nile 150 series, capable of running DC/OSx Version 1.1. The Tracker Agent uses about 1 MB of memory.

The Tracker Agent for Digital UNIX (R) requires a DEC Alpha computer with at least 32 MB of memory, capable of running Digital UNIX 4.0B. The Tracker Agent uses about 1 MB of memory.

The Tracker Agent for OS/390 Open Edition (OS/390 UNIX) operates on any IBM hardware configuration supported by OS/390 Version 1 Release 3.

A display terminal supported by ISPF Version 4.2 or later is required to invoke and run the OPC host dialogs.

The graphic function requires a terminal supporting Graphic Data Display Manager (GDDM (R)/MVS (TM)) Version 2 Release 2 or later.

Software Requirements: Tivoli OPC requires the functions provided by an MVS control program that is run in MVS/ESA mode. The Job Entry Subsystem may be either JES2 or JES3. Tivoli OPC requires one of the following environments:

  • OS/390 Version 2 (5647-A01)
  • OS/390 Version 1 (5645-001)
  • MVS/ESA SP Version 5 (5655-068, 5655-069)
Installing and maintaining Tivoli OPC requires:
  • System Modification Program Extended (SMP/E) Release 8.1 (5668-949) or later.



Controlling System

The following IBM licensed programs are required on the Tivoli OPC controlling system:

  • Tivoli OPC (5697-OPC). Both the base product (the tracker) and the controller feature are required. The Tracker Agent enabler feature is required if any Tracker Agents are used.

  • Time Sharing Options/Extensions (TSO/E) Version 2 Release 5 (5685-025) -- or -- OS/390 Version 1 (5645-001) or OS/390 Version 2 (5647-A01)

  • Data Facility Sort (DFSORT (TM)) Release 9 (5740-SM1) or later.

  • Interactive System Productivity Facility (ISPF) for MVS, Version 4.2 (5655-042) -- or -- OS/390 Version 1 (5645-001) or OS/390 Version 2 (5647-A01)

  • ACF/VTAM (R) Version 3 Release 4.2 for MVS/ESA (5685-085) or later, ACF/VTAM Version 4 Release 3 for MVS/ESA (5695-117) or later, or Communication Server for OS/390 Release 1 (5645-001) or later is required if the Graphical User Interface for Application Description, Workload Monitor/2, the Tracker Agent for OS/400, remote dialogs, or remote PIF applications are used.

  • TCP/IP for MVS Version 3 Release 2 (5655-HAL) with C socket API support, OS/390 Version 1 (5645-001), or OS/390 Version 2 (5647-A01), is required if any Tracker Agent for systems other than OS/400 is used.



GUI for Application Description

The following IBM licensed programs are required by the Tivoli OPC GUI for Application Description:

  • Operating System/2 (OS/2) Warp Version 3 (5622-601) or Version 4 (5622-851)

  • Communications Manager/2 Version 1.1 (5622-078) or later, or Communications Server Version 4 (5622-878)



Workload Monitor/2

The following IBM licensed programs are required by Workload Monitor/2:

  • Operating System/2 (OS/2) Version 2 Release 1 (5621-077) with Communications Manager/2 (5622-078) or Extended Services for OS/2 (5621-213), or OS/2 Warp Version 3 (5622-601), or OS/2 Warp Version 4 (5622-851), with Communications Manager/2 (5622-078) or Communications Server Version 4 (5622-878)

  • To work with Kanji, OS/2 J Version 2 (5605-PNC) with Workplace Shell (R) and Extended Services for OS/2 (5605-PEE) are required.



Controlled OS/390 Systems

On each Tivoli OPC-controlled OS/390 system, one of the following IBM licensed programs is required:

  • Tivoli OPC Version 2 (5697-OPC). Only the base product (the tracker) is required.

  • OPC/ESA Version 1 Release 3 Modification Level 1 (5695-007). Only the base product (the tracker) is required.



Controlled OS/2 Systems

To manage workloads from Tivoli OPC on OS/2, the following IBM licensed programs and features are required:

  • OPC Tracker Agent for OS/2 in Tivoli OPC Version 2. One Tracker Agent feature is required on each OS/2 machine with workload managed by Tivoli OPC.

  • OS/2 2.1 (5621-077), OS/2 Warp 3 (5622-601), or OS/2 Warp 4 (5622-851).

  • TCP/IP for OS/2 Version 2 (5622-086) or later.



Controlled Windows NT Systems

To manage workloads from Tivoli OPC on Windows NT, the following programs and features are required:

  • OPC Tracker Agent for Windows NT in Tivoli OPC Version 2. One Tracker Agent feature is required on each machine with workload managed by Tivoli OPC.

  • Windows NT Version 3 Release 5 or Release 5.1, or Version 4.0.



Controlled OS/400 Systems

To manage workloads from Tivoli OPC on OS/400, the following IBM licensed programs and features are required:

  • OPC Tracker Agent for OS/400 in Tivoli OPC Version 2. One Tracker Agent feature is required on each AS/400 machine with workload managed by Tivoli OPC.

  • OS/400 Version 3 Release 1 (5763-SS1) or later, or OS/400 Version 3 Release 6 (5716-SS1) or later.



Controlled UNIX Systems

To manage workloads from Tivoli OPC on UNIX systems, the following programs and features are required on the managed UNIX system:

AIX/6000

  • Tracker Agent for AIX (R) in Tivoli OPC Version 2. One Tracker Agent feature is required for each RS/6000 machine with workload managed by Tivoli OPC.

  • AIX/6000 Version 3 Release 2 Modification Level 5 (5756-030), or Version 4 up to Version 4 Release 2 (5765-655) with the optional TCP/IP feature installed.

HP-UX
  • Tracker Agent for HP-UX in Tivoli OPC Version 2. One Tracker Agent feature is required on each machine with workload managed by Tivoli OPC.

  • HP-UX Version 9, Version 10, or Version 11.

Sun Solaris
  • Tracker Agent for Sun Solaris in Tivoli OPC Version 2. One Tracker Agent feature is required on each SPARC workstation with workload managed by Tivoli OPC.

  • Sun Solaris Version 2 Release 3 up to Version 2 Release 5.

SunOS
  • Tracker Agent for SunOS in Tivoli OPC Version 2. One Tracker Agent feature is required on each SPARC workstation with workload managed by Tivoli OPC. If your machines have LoadLeveler (R) Version 1 Release 2 for Sun SPARCstation systems (5765-227) installed, only one OPC Tracker Agent feature is required.

  • Solaris Version 1.1.1 (SunOS Version 4 Release 1 Modification Level 3).



Controlled DEC OpenVMS Systems

To manage workloads from Tivoli OPC on DEC OpenVMS, the following programs and features are required:

  • OPC Tracker Agent for DEC OpenVMS in Tivoli OPC Version 2. One Tracker Agent feature is required on each machine with workload managed by Tivoli OPC.

  • OpenVMS Version 7.0 to Version 7.1.

  • POSIX for OpenVMS 2.0 or later.



Controlled Pyramid MIPS ABI Systems

To manage workloads from Tivoli OPC on Pyramid MIPS ABI, the following programs and features are required:

  • OPC Tracker Agent for Pyramid MIPS ABI in Tivoli OPC Version 2. One Tracker Agent feature is required on each machine with workload managed by Tivoli OPC.

  • DC/OSx Version 1.1.



Controlled OS/390 UNIX

To manage workloads from Tivoli OPC on OS/390 UNIX, the following programs and features are required:

  • OPC Tracker Agent for OS/390 Open Edition (OS/390 UNIX) in Tivoli OPC Version 2. One Tracker Agent feature is required on each machine with workload managed by Tivoli OPC.

  • OS/390 Version 1 Release 3 (5645-011) or later with UNIX services.



Controlled Digital UNIX Systems

To manage workloads from Tivoli OPC on Digital UNIX, the following programs and features are required:

  • OPC Tracker Agent for Digital UNIX in Tivoli OPC Version 2. One Tracker Agent feature is required on each machine with workload managed by Tivoli OPC.

  • Digital UNIX Version 4.0B or later.



Optional Software

The following Tivoli OPC functions require specific IBM programs:

  • Tracking resource availability requires the Resource Object Data Manager (RODM) in NetView (R) Version 2 Release 4 or later (5685-111), or NetView Version 3 (5655-007), or TME 10 (TM) NetView for OS/390 (5697-B82).

  • Graphical functions require GDDM/MVS Version 2 Release 2 (5665-356), or Version 3.1.1 (5695-167) -- or -- OS/390 Version 1 (5645-001) or OS/390 Version 2 (5647-A01)

  • Application transaction programs (ATP) that use OPC's application programming interface (API) require ACF/VTAM Version 3 Release 4.2 for MVS/ESA (5685-085) or later, ACF/VTAM Version 4 Release 3 for MVS/ESA (5695-117) or later, or Communication Server for OS/390 Release 1 (5645-001) or later.

  • Connecting a controller and a tracker via VTAM (R) requires ACF/VTAM Version 3 Release 4.2 for MVS/ESA (5685-085) or later, ACF/VTAM Version 4 Release 3 for MVS/ESA (5695-117) or later, or Communication Server for OS/390 Release 1 (5645-001) or later.

  • Remote processing with RJE requires ACF/VTAM Version 3 Release 4.2 for MVS/ESA (5685-085) or later, ACF/VTAM Version 4 Release 3 for MVS/ESA (5695-117) or later, or Communication Server for OS/390 Release 1 (5645-001) or later.

  • Remote dialogs and remote PIF applications requires ACF/VTAM Version 3 Release 4.2 for MVS/ESA (5685-085) or later, ACF/VTAM Version 4 Release 3 for MVS/ESA (5695-117) or later, or Communication Server for OS/390 Release 1 (5645-001) or later.

  • NetView Version 2 Release 4 for MVS/ESA (5685-111) or later is required to enable Tivoli OPC to schedule generic alerts as defined by that NetView release.

  • NetView Version 2 Release 4 for MVS/ESA (5685-111) or later is required to specify an alert receiver ID other than the default receiver.

  • User-authority-support functions require Resource Access Control Facility (RACF (R)) Version 2 (5695-039) or later, -- or -- OS/390 Release 1 (5645-001) Security Server or later

  • Data Facility Hierarchical Storage Manager (DFHSM) Version 2 Release 5 (5665-329) is required for the catalog management function to recall migrated datasets.

  • LoadLeveler for RISC System/6000 (R) Release 2 (5765-145) is required if you want to submit AIX tasks through LoadLeveler.

  • LoadLeveler Version 1 Release 2 for Hewlett-Packard systems (5765-287) is required if you want to submit HP-UX tasks through LoadLeveler.

  • LoadLeveler Version 1 Release 2 for Sun SPARCstation systems (5765-227) is required if you want to submit Sun Solaris or SunOS tasks through LoadLeveler.

  • DB2 (R) for MVS Version 3 (5685-DB2) or DB2 for MVS Version 4 (5695-DB2) is required to use the History function (restart of old operations).

  • Scheduling SAP R/3 jobs requires:
    • Tivoli Workload Scheduler Extended Agent for SAP R/3 Version 3 (5697-WKB) feature,

    • and Tivoli OPC Tracker for one of the following platforms:
      • AIX
      • Digital UNIX
      • Sun Solaris
      • Windows NT
      • HP-UX

  • The OPC Control Language tool requires the IBM Compiler Library for REXX/370 Version 1 Release 3 (5695-014).

Compatibility
  • Tivoli OPC Version 2 Release 2 uses only existing attachment interfaces to other IBM products.

  • Tivoli OPC Version 2 Release 2 can coexist with Tivoli OPC Version 2 Release 1, or with OPC/ESA Version 1 Release 3 Modification Level 1, but the products cannot share program libraries, files or datasets.

  • Event datasets containing events created by Tivoli OPC Version 2 Release 1, or by OPC/ESA Version 1 Release 3 Modification Level 1 can be used as input to Tivoli OPC Version 2 Release 2.

  • A Tivoli OPC Version 2 Release 2 system can be used to transmit work to an Tivoli OPC Version 2 Release 1, or to OPC/ESA Version 1 Release 3 Modification Level 1 system using shared submit/release dataset, Network Job Entry (NJE), OPC Network Communications Facility (NCF), cross-system coupling facility (XCF), or by transmitting events on an established session between Tivoli OPC Version 2 Release 2 and Tivoli OPC Version 2 Release 1 or OPC/ESA Version 1 Release 3 Modification Level 1.

  • Previous definitions made in OPC/ESA or Tivoli OPC Version 2 Release 1 behave as before after upgrading to Tivoli OPC Version 2 Release 2.

  • JES and SMF exits used to create Tivoli OPC Version 2 Release 2 events can also be used to create Tivoli OPC Version 2 Release 1 events after upgrading to Tivoli OPC Version 2 Release 2.

  • Existing PIF application programs can be used unchanged on Tivoli OPC, unless Access Method information is stored in a workstation record, in which case that workstation record will include a new sub-segment.

  • The Workload Monitor/2 code shipped with OPC/ESA Version 1 Release 3.1 and Tivoli OPC Version 2 Release 1 can communicate with a Tivoli OPC Version 2 Release 2 controller.

  • The GUI for Application Description must be upgraded.



Security, Auditability, and Control

Tivoli Operations Planning and Control uses the system authorization facility (SAF) of MVS to pass verification requests to your security system, for example RACF. Tivoli OPC data objects can be protected with any security system that uses the SAF interface.

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



ORDERING INFORMATION



Current Licensees

Current licensees of Tivoli Operations Planning and Control will be sent a program reorder form that may be returned directly to IBM Software Manufacturing Solutions (SMS). These reorder forms are scheduled to be mailed by July 10, 1998. Reorder forms returned to SMS will be processed within 10 workdays of receipt. When the new release is available, the prior release will no longer be available.



New Licensees

Orders for new licenses will be accepted now.

Shipment will begin on the planned availability date.

  • Orders that ship before the planned availability will receive Tivoli Operations Planning and Control Version 2 Release 1.

  • Orders that ship after the planned availability date will receive Tivoli Operations Planning and Control Version 2 Release 2.

New users of Tivoli Operations Planning and Control should specify: 
          Type        Model


          5697         OPC

Basic License: For ordering information on the base program, Tivoli Operations Planning and Control Version 2 Release 2, refer to Software Announcement 297-075 dated March 25, 1997.

Ordering information is unaffected by this announcement with the exception of the publications as noted below.

Unlicensed Documentation: A memo to users (GI10-5589) and a language dependent (English, Spanish, Kanji, German) program directory, are supplied automatically with the basic machine-readable material. All other publications remain unchanged.

For additional information on the list of documentation supplied with Tivoli OPC Version 2 Release 2, refer to Software Announcement 297-075 dated March 25, 1997.

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.

Ordering information is unaffected by this announcement.



TERMS AND CONDITIONS

The terms for Tivoli Operations Planning and Control, as previously announced in Software Announcement 297-075 dated March 25, 1997, licensed under the IBM Customer Agreement are unaffected by this announcement.

Support Line: S/390 (R)



CHARGES

Previously announced charges for Tivoli OPC Version 2 remain unchanged.

One-Time Charge: Customers who pay a one-time charge for a licensed program receive enhancements and future releases, if any, at no additional charge. Significant new function may be offered as an optional feature and charged for separately. If a replacement program is announced and the customer elects to license the replacement program for a one-time charge, an upgrade charge or a time-based credit may apply. If the replacement program is licensed for a monthly license charge, a time-based upgrade credit may apply.

Variable Charges: The applicable graduated one-time charge, if applicable, or graduated monthly license charge will be based on the group of the designated machine on which the licensed program is licensed for use. If the program is designated to a processor in a group for which no charge is listed above, the charge of the next higher group listed applies.

For upgrades of one-time charge licenses to a machine in a higher group, the upgrade charge will be the difference in the then current charges between the two groups. For downgrades of one-time charge licenses to a machine in a lower group, there will be no adjustment or refund of one-time charges paid.

For upgrades or downgrades of monthly license charge licenses, the monthly license charge applicable to the higher or lower group will apply.

Entry Support License One-Time Charge: One-time charge authorizes use only on IBM Entry End User/390 machines.

Program Upgrade Charge: For additional product information, refer to Software Announcement 297-075 dated March 25, 1997.



CALL NOW TO ORDER

To order, contact the IBM North America Sales Centers, your local IBM representative, or your IBM Business Partner.

IBM North America Sales Centers, our national direct marketing organization, can add your name to the mailing list for catalogs of IBM products. 

 Phone:     800-IBM-CALL (TM)
 Fax:       800-2IBM-FAX
 Internet:  ibm_direct@vnet.ibm.com
 Mail:      IBM North America Sales Centers
            Dept. YE010
            P.O. Box 2690
            Atlanta, GA  30301-2690
 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 

      OPC, OS/390, MVS/ESA, SP, RS/6000, MVS, DFSORT, and
      800-IBM-CALL are trademarks of International Business Machines
      Corporation in the United States or other countries or both.
      Operating System/2, OS/2, Extended Services for OS/2, OS/400,
      AS/400, AIX/6000, GDDM, ACF/VTAM, Workplace Shell, AIX,
      LoadLeveler, NetView, VTAM, RACF, RISC System/6000, DB2, and
      S/390 are registered trademarks of International Business
      Machines Corporation in the United States or other countries or
      both.
      Pentium is a trademark of Intel Corporation.
      Windows NT is a registered trademark of Microsoft Corporation.
      UNIX is a registered trademark in the United States and other
      countries exclusively through X/Open Company Limited.
      TME 10 is a trademark 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.