IBM United States
Software Announcement 202-229
September 24, 2002

IBM Information Management System (IMS) V8 — Leading the Marketplace in Information Integration, Management, and Availability

 ENUS202-229.PDF (133KB)


At a Glance

IBM IMS V8 enhancements include:

IMS V8 Transaction Manager

  • Enhanced application development/execution with Java and XML
  • Improved systems availability in error handling and network reconnection
  • Increased performance/capacity in routing and workload balancing
  • Improved manageability with single point of operations control, Coordinated Online Change for the sysplex, and easier systems generation

IMS V8 Database Manager

  • Enhanced application development and connectivity with Java and XML
  • Improved availability in database restart and recovery
  • Increased performance/capacity in logging, recovery, and database size
  • Improved manageability with single point of operations control, Coordinated Online Change for the sysplex, and easier systems generation

For ordering, contact:

Your IBM representative, an IBM Business Partner, or IBM Americas Call Centers at 800-IBM-CALL (Reference: YE001).

Overview

The IBM Information Management System (IMS™) is unsurpassed in database and transaction processing availability and speed. With the demands of the evolving e-business environment, and a marketplace working in Web time, IMS delivers the integrity, capability, and performance customers have learned to expect from IBM.

IBM is enhancing IMS Transaction Manager (IMS TM) and IMS Database Manager (IMS DB) with IMS Version 8, which enables you to shape how you:

  • Transform the way you do business with integrated information
  • Build e-business applications that tolerate the rigors of doing business on the net
  • Run a scalable, available, safe, and easily managed environment
  • Leverage everything you learn in the process, and mine all your information to make better decisions

IMS TM continues with IMS V8 as IBM's premier Transaction Server for environments that:

  • Employ relational and hierarchical data stores
  • Require the utmost in integrity, capacity, availability, and performance for e-business and enterprise computing environments

IMS V8 DB is IBM's premier hierarchical database server. It continues to provide and enhance:

  • High performance and capacity
  • Superior integrity
  • Continuously available database solutions for IMS TM and CICS® users

Simplified information integration of new and existing IMS applications and data, and enablement of Internet access, are also supported with the following new or recently enhanced IBM products:

  • IMS Connect V1.2 (5655-E51)
  • IBM Developer Kit for OS/390®, Java™ 2 Technology Edition (5655-D35)
  • WebSphere® Application Server Enterprise Edition V4.1
  • WebSphere Studio Application Developer Integration Edition V4.1

Improved systems and data management and enhanced performance and availability are also supported by IBM's robust portfolio of IMS tools and utilities. These tools help users manage and gain the best performance from IMS. IBM tools have been upgraded to work with IMS V8. Although ready and available now, the IMS tools are committed to work with IMS V8 on day one of its general availability (GA).

To learn more about IBM's IMS products and tools, visit the Web at:

or

Key Prerequisites

IMS V8 can be used with all IBM processors capable of running OS/390 Version 2, Release 10, or later. Additional prerequisites exist for specific IMS V8 functional items.

Planned Availability Date

October 25, 2002

Description

IMS Version 8 DB and TM Information Integration Enhancements

Java Enhancements

  • Java Standards Enhancements provide selected support for the new Java standards as they evolve. JDBC 2.0 enhancements include support for Updatable ResultSet and limited reverse cursors. SQL enhancements to IMS DB data include support for a subset of aggregate functions (MIN, MAX, and so on) and scalars.

  • JDBC access to IMS DB data provides access from WebSphere EJBs, CICS Transaction Server Java applications, and DB2® Java Stored Procedures environments, as well as from IMS TM applications.

  • Java Dependent Regions take advantage of the new IBM Technology for Persistent Reusable Java Virtual Machines (JVM) to speed up the processing of Java applications and provide a serially reusable JVM that can be reset to a known state between transactions. This support provides new region types for message-driven and non-message-driven IMS Java applications.

  • Java Tooling introduces a new IMS utility called DLIModel, which automatically constructs the required IMS Java "metadata class" from PSB and DBD source (initially with IMS V7 the user was responsible for creating this class manually). The utility allows information on additional fields, long Java-style names, and datatypes to be supplied from user-coded control statements, and/or from XMI descriptions of COBOL copybook members. If desired, it will produce XMI descriptions of databases that conform to the Object Management Group's Common Warehouse Metamodel 1.1. This greatly eases development of Java applications and JDBC access to IMS DB.

  • Java Installation and Usability enhancements provide expanded sample applications for IMS, WebSphere, CICS, and DB2 stored procedures, expanded examples for logically related databases and secondary indexes, improvements for installation and Installation Verification Program (IVP) applications, and expanded documentation.

  • Java-COBOL Interoperation provides the ability to execute COBOL routines in an IMS Java Message Processing or a Java Batch Processing region. This support provides the ability to build an application with IMS message processing in a Java class and IMS database access in a COBOL routine. It also supports an application with IMS message processing logic in a COBOL "main" method, and that invokes other Java or COBOL routines that perform IMS database access.

  • J2EE Two-Phase Commit Support is provided in conjunction with WebSphere Java applications, using IMS Connect and the IMS Connector for Java. IMS Connect and IMS Connector for Java and WebSphere Java applications provide easy e-business access to IMS applications and data in a number of environments, such as Windows®, AIX®, Linux, Solaris, and z/OS™ platforms.

    Using the IMS Connector for Java J2EE Development support in VisualAge® for Java or WebSphere Studio Application Development Integration Edition, IBM provides easy Java application development for e-business solutions with IMS. These Java applications can use IMS Connect's IMS Connector for Java J2EE Runtime support for enhanced application connectivity to IMS. This IMS Connector for Java Development and Runtime support now provides J2EE local two-phase commit support (through IMS Connect's "Local" option) across Local OS/390 or z/OS environments. This J2EE local two-phase commit support provides enhanced data integrity for development and runtime connectivity of applications running in WebSphere and IMS.

XML Enhancements

  • Service definition creation for IMS COBOL and C applications enables these IMS applications to be used as Web services, using WebSphere Studio Application Developer Integration Edition Version 4.1.

  • Service definition deployment of IMS services as EJB services or SOAP services makes them available to distributed WebSphere Application Server (WAS). This transforms existing IMS COBOL and applications into Web services by supporting SOAP, EJB, and Java inbound bindings.

  • IMS COBOL and PL/I programs can receive and send XML directly using the XML Enabler for COBOL and PL/I to parse the incoming XML documents. IMS supports the transmission of XML documents in the data portion of the IMS message. Messages can be placed on and retrieved from the IMS message queues from applications running in any IMS region.

Dynamic LE Runtime Parameters

  • Dynamic LE Runtime Parameters provide the ability to dynamically update Language Environment® (LE) runtime parameters for an IMS Transaction or a Batch Message Program and make it easier to use the Debug tool for application testing. Parameters can be changed without requiring CEEROPT and CEEUOTP to be changed, reassembled, and relinked.

IMS Version 8 DB and TM Manageability Enhancements

Sysplex-Wide Resource Manager

  • The new Resource Manager, a component of the new IMS Common Service Layer (CSL), provides for the coordination of an online change across all the IMSs in the IMS Sysplex. In addition, it provides for global management of IMS terminal resources by maintaining resource information for clients using a resource structure. It enhances availability by enabling a user to resume work on another IMS and enforcing single active users. It also provides systems management by enforcing single user sign on in the IMS Sysplex, if requested, and enables enforcement of unique names for message destinations.

    The resource structure supports Automatic Altering and System-Managed Rebuild. It also supports Structure Copy where the IMS Common Queue Server performs the rebuild to copy the contents from one resource structure to another. Resource structures can also be duplexed to keep from losing resources on the structure, in the event of failure, since these structure resources are not checkpointed or logged.

Coordinated Online Change

  • Coordinated Online Change eases, manages, and automates change across the IMS Sysplex. You can enter commands on one IMS and request that the new IMS Resource Manager coordinate an online change across all the IMSs in the IMS Sysplex, replacing the earlier manual coordination process. The Coordinated Online Change function will be delivered through the Version 8 service process.

Single Image Operations Manager

  • The new Operations Manager, a component of the new IMS CSL, provides the framework for a single point of control (SPOC) for IMS. It supports IMS commands and responses and introduces new IMS Sysplex commands. It also provides an application programming interface (API) that allows commands to be entered from a SPOC to one or more IMS systems and consolidated command responses to be returned. This API allows you to write tools to automate IMS operations. It simplifies operations by supporting a SPOC that presents a single system image for the IMS Sysplex, allowing you to enter commands to all IMSs in the sysplex from a single console.

    A SPOC application program is also provided to help manage a group of IMSs in a sysplex from a TSO SPOC. This program lets you issue commands to all the IMS subsystems in the sysplex, display consolidated responses from these commands, and send a message to an IMS terminal that is connected to any IMS in the IMS Sysplex. This would offer less complexity in managing multiple IMSs in a sysplex environment.

  • IBM is also providing a Control Center capability as an alternative graphical user interface for the new Operations Manager through IMS Connect, greatly easing IMS operations. The Control Center capability is integrated with the DB2 UDB V8 administration tools in Fixpack 1. It would then be providing a single user interface from which you can control both IMS and DB2.

    The administration tools include a Control Center for navigating IMS Sysplex systems, wizards for creating the new IMS V8 Operations Manager commands, and a results window for sorting and filtering single-system image command results. The tools also include a Command Center for typing and executing both the new commands and the old operations commands. IMS Connect is also being enhanced through the service process to allow the Control Center to communicate with the IMS V8 Operations Manager.

    Additional IMS Connect service stream enhancements include J2EE Connector Architecture two-phase commit support, enhanced security, and support for the new Internet Protocol Version 6 (IPv6), which provides increased scalability and simplified configurations, renumbering support, and application compatibility.

Syntax Checker

  • Syntax Checker, a new addition to the IMS installation process, helps reduce system generation effort by assisting system programmers in defining and maintaining selected input parameter members residing in the IMS PROCLIB. It provides parameter syntax checking, parameter value verification, and detailed help text at the parameter level tailored to the IMS release.

    Syntax Checker provides assistance in migrating to a new release by identifying any new and/or obsolete parameters. It displays the PROCLIB member in an ISPF panel. Any parameters or values in error are highlighted, allowing you to add, change, or correct the value of the parameters. Detailed parameter help text is available at the touch of a key.

    Using Syntax Checker, the system programmer can ensure the parameters are valid prior to shutting down and restarting IMS control regions. This eliminates the risk of parameter error during a start-up of IMS and the time-consuming process of locating and correcting parameter syntax or value errors.

Transaction Trace

  • Transaction Trace takes advantage of the OS/390 and z/OS Transaction Trace Facility to ease serviceability by providing transaction tracing information.

RACF® Abend Suppression

  • The RACF Abend Suppression enhancement prevents a RACF 483-4C abend from causing the abnormal termination of the IMS system. This event can occur during a user signon (or equivalent request) where there is an invalid index block in the RACF database. Where this invalid block exists, a signon request fails with a message and a new reason code, rather than terminating IMS. This enhancement improves the availability and serviceability of the IMS system.

IMS Version 8 Database Manager Scalability Enhancements

IMS/DB2 Coordinated Disaster Recovery Support

  • The IMS Remote Site Recovery (RSR) function is extended to support coordinated IMS/DB2 disaster recovery by working with eXtended Remote Copy (XRC) for the DB2 logs. If IMS and DB2 logs, log control information, and (optionally) database data are sent to a remote site by independent transfer mechanisms without this support, the customer has to synchronize the IMS and DB2 logs and ensure that the IMS and DB2 databases are consistent when a disaster occurs. This can be a time-consuming and error-prone process and puts data integrity at risk.

    This new support enhances IMS RSR for coordination of IMS and DB2 disaster recovery processing at a remote recovery site, offering an IBM solution for synchronizing the logs. In the supported configuration, XRC is used for the DB2 logs. The steps required by the user to synchronize the logs are greatly reduced.

Database Recovery Control (DBRC) Enhancements

  • Automatic RECON Loss Notification adds support to automatically propagate a Recovery Control Data Set (RECON) reconfiguration to other DBRC instances. When an error on a RECON data set results in a RECON reconfiguration on one IMS subsystem, other DBRC instances using the same RECONs are notified. The result is that all IMS subsystems automatically deallocate the failed RECON data set so the user can quickly recover from the loss. This function takes advantage of the Structured Call Interface (SCI) component of the new IMS CSL.

  • Elimination of abends . When authorizing databases or recording Extended Error Queue Elements (EEQEs), DBRC no longer abends and is less likely to cause IMS to abend due to RECON record size problems. DBRC no longer abends when attempting to deallocate a database that is recorded in RECON as "already deallocated."

  • RECON Command Authorization Support allows users to control RECON access and update via DBRC batch commands or via the High Availability Large Database (HALDB) Partition Definition Utility. Users have flexibility to customize security criteria and maintain an audit trail through user exit implementation. This helps you protect the integrity of database data by allowing finer control over the data you can access.

  • 16 MB RECON Record Size helps you avoid problems caused by RECON records (such as the PRILOG record which identifies the primary log for an active system) exceeding the maximum VSAM RECORDSIZE. This enhancement eliminates planned and unplanned outages due to RECON record size. DBRC implements its own RECON record spanning.

  • DBRC PRILOG Compression has been enhanced to reduce its overhead, improving performance. Since DBRC now supports RECON records of unlimited size, compression is attempted whenever an Online Log Data Set (OLDS) is archived.

Parallel Database Processing

  • This support allows IMS to do DB authorization, allocation, and open using multiple MVS™ threads, replacing the earlier serialized process. For systems with large numbers of databases, this can significantly reduce the time required to re-open databases after an outage and return the system to steady state, increasing system availability. This function is provided automatically and controlled by IMS.

Batch Resource Recovery Service (RRS) Support

  • Batch RRS support allows batch programs to use MQSeries® with coordinated commit. It also provides a full two-phase commit for batch programs accessing DB2 and/or IMS DB. Today's Batch Attach from DB2 does not support coordinated commit.

    Batch RRS support also allows for work that captures data and propagates it to another system (for example, a DB2 system) to participate in the two-phase syncpoint process along with the IMS work, thus ensuring that all work is done, or not done, as part of the same unit of recovery. Note that this Batch RRS support is also being provided on IMS V7 through the service process.

  • Batch RRS support is utilized by the new IMS DataPropagator™ V3.1 product, which provides asynchronous, near-real-time IMS-to-DB2 propagation by taking advantage of the asynchronous messaging function of the IBM MQSeries product. The operations and administration of an asynchronous propagation are simplified, easier to use, and less error prone. This near-real-time propagation would also offer improved performance and reliability, minimizing the impact on mission-critical IMS applications that are updating IMS DB data being propagated to DB2.

Database Image Copy 2 Enhancements

  • Database Image Copy 2 enhancements allow multiple database data sets to be copied in one utility execution. The utility passes the data sets to DFSMSdss™ on multiple DUMP commands to be processed in parallel. Optionally, you can specify that the data sets are to be processed by a single DFSMSdss DUMP command, which results in the image copies being written to the same output data set. Logical completion, in most cases, is achieved for all the database data sets in a very brief time. Also, the utility supports specification of a group name for the database data sets being copied. Logical completion is indicated for the group rather than for the individual database data sets. With these added capabilities, you are able to better manage and automate image copy processing. The Database Image Copy 2 enhancements will be delivered through the Version 8 service process.

Fast Path Shared Virtual Storage Option (VSO) Coupling Facility Enhancements (also being provided on IMS V7 through the service process)

  • System-Managed Rebuild allows rebuilding a VSO structure to enable migration of that structure from one Coupling Facility to another for planned reconfiguration without taking the VSO structure off line. All structures can be migrated using a single command.
  • Automatic Altering of VSO structure size and entry-to-element ratio allows dynamically expanding or contracting a VSO structure based on its actual coupling facility storage usage with exclusive control as needed. Over-configured coupling facility storage can be reclaimed when OS/390 and/or z/OS needs that storage.
  • System-Managed Duplexing of VSO structures allows dual VSO structure support without explicitly defining both primary and secondary structures in IMS DBRC Facility and in a CFRM policy. It allows for the automatic switch of modes when a loss of connectivity, a structure failure, or a Coupling Facility failure occurs in one of the VSO structure instances.

Fast Path Data Entry Database (DEDB) Enhancements

  • DEDBs greater than 240 Areas (up to 2048) extend the capacity of Fast Path Databases above the prior 240-area restriction, significantly increasing the number of areas supported by DEDBs. This provides more data storage capacity in each DEDB and could lead to greater design flexibility.
  • Nonrecoverable DEDBs are provided for use as work databases where recoverability is not a requirement. Marking the DEDB nonrecoverable reduces the amount of log record and checkpoint information, thus improving the performance of IMS.

Common Storage Area (CSA) Virtual Storage Constraint Relief (VSCR) Enhancements

  • CSA VSCR enhancements relieve storage constraints by IMS using less local and common storage below the 16M line. This is done by moving system Program Status Tables and code paths from local to above the 16M line.

High Availability Large Database (HALDB) Enhancements

  • HALDB Single Partition Processing enables utilities and applications to process or access a single partition while not affecting any other partition in the HALDB.
  • New DBRC batch command support for HALDBs.
    • CHANGE.DB
    • CHANGE.PART
    • DELETE.DB
    • DELETE.PART

IMS V8 Transaction Manager Scalability Enhancements

Sysplex Terminal Management

  • Sysplex Terminal Management recovers terminal state information after a session reconnect and allows the terminal user to log back on another IMS after a failure. The Resource Manager is used to share VTAM® terminal-related resources among IMS systems in the IMS Sysplex. IMS managed VTAM Generic Resources affinity can be eliminated while maintaining terminal and user state data.

    IMS maintains VTAM terminal and user state data, if requested. IMS enforces resource type consistency for message destinations and enforces resource name uniqueness. IMS also supports the global Callable Services for terminals or users, enabling user exits to obtain node and user information across the IMS Sysplex.

Advanced Program to Program Communication (APPC) Enhancements

  • Dynamically Add/Delete LU 6.2 Descriptors , increasing availability by avoiding the necessity of bringing down IMS for this purpose.
  • Use Another Logical Unit (LU) as an Outbound LU , increasing availability by avoiding the problems of an outbound LU being disabled.
  • Use a CPU Time Limit for CPI-C (explicit) Transactions , increasing availability by helping to prevent looping programs that tie up resources.
  • APPC Synchronous Shared Queues Support enhances distribution of workload in an IMS Sysplex environment. This new support allows you to run synchronous transactions entered from APPC on any IMS system in the Shared Queues group. Synchronous transactions can run on any back-end system from any front-end system; the output message is sent back to the client from the front-end system.

    Previously, only asynchronous transactions for these environments were supported. This new support uses the z/OS Resource Recovery Services (RRS) Multi-System Cascaded Transactions support.

    The APPC Synchronous Shared Queues Support will be delivered through the Version 8 service process.

OTMA Synchronous Shared Queues Support

  • Open Transaction Manager Access (OTMA) Synchronous Shared Queues support enhances distribution of workload in an IMS Sysplex for OTMA Send_then_commit (CM1) transactions. This new support allows you to run synchronous transactions entered from OTMA on any IMS system in the Shared Queues group. Synchronous transactions can run on any back-end system from any front-end system; the output message is sent back to the client from the front-end system.

    Previously, only asynchronous transactions for these environments were supported. This new support uses the z/OS Resource Recovery Services (RRS) Multi-System Cascaded Transactions support.

    The OTMA Synchronous Shared Queues Support will be delivered through the Version 8 service process.

Shared Message Queues and Expedited Message Handler Coupling Facility Duplexing Support

  • IMS is providing support for z/OS Coupling Facility (CF) Duplexing function for IMS Shared Message Queue structures and IMS Fast Path Expedited Message Handler (EMH) structures. When CF Duplexing is enabled, z/OS creates a duplex copy of the structure for failure recovery. If the IMS Shared Queues structure or the EMH structure fails or if a connection to the structure is lost, z/OS switches to the unaffected structure instance without the overhead of a structure rebuild.

    CF Duplexing also enables System-Managed Rebuild. MVS does the structure rebuild for a planned reconfiguration (that does the structure copy) if no IMS Common Queue Server (CQS) is up. The advantage to System Rebuild is that CQS does not have to be up, thus improving availability. IMS CQS managed rebuild is still needed to address CF failure, structure failure, or loss of connectivity. This support is also being provided for IMS V7 through the service process.

Multiple Systems Coupling Facility Fiber Connection Channel-to-Channel Support

  • Multiple Systems Coupling (MSC) Facility Fiber Connection (FICON™) channel-to-channel (CTC) support increases the volume of IMS messages that can go between IMS systems when using the IMS Multiple Systems CF. IMS customers require reliable, high bandwidth, host-to-host communications support between IMS systems. This is the role of the IMS Multiple Systems CF.

    One of the physical host-to-host MSC connections supported by IMS is MSC channel-to-channel hardware support. CTC bandwidth is enhanced on the new IBM eServer zSeries processors by implementing Fiber Connection channel support for CTCs. This FICON support could be significantly faster than the Enterprise System Connection (ESCON®) support for large blocks of data transferred.

    It is estimated that one FICON CHPID can do the work of a number of ESCON CHPIDs (that is, more bandwidth). This increased bandwidth is the result of faster data transfer rates, I/O rates, and CCW and data pipelining. The distance between hosts is also increased.

    IMS MSC support is provided for this new FICON CTC support, greatly improving the bandwidth across systems. This support is also being provided for IMS V7 through the service process.

Common Storage Area (CSA) Virtual Storage Constraint Relief (VSCR) Enhancements

  • CSA VSCR enhancements relieve storage constraints by IMS using less local and common storage below the 16M line. This is done by moving system Program Status Tables and code paths from local to above the 16M line.

Accessibility by People with Disabilities

The following features support use by people with disabilities:

  • Operation by keyboard alone
  • Optional font enlargement and high-contrast display settings
  • Screen readers and screen magnifiers tested for use by people with visual impairment
  • Speech recognition products tested for use by people with mobility impairment
  • Optional display of audio alerts for people with hearing impairment

Product Positioning

IMS continues to evolve by powering e-business environments while preserving your investments in mission-critical applications and data as well as leveraging existing skills. Customers can more confidently extend their business into e-business when they have the assurance of performance, scalability, availability, security, integrity, and recovery that IMS has provided for 30 years, and they know that it continues to be enhanced for powering 21st century solutions. Building on your present assets allows you to bring e-business solutions to the marketplace more quickly and at lower total cost than rip-and-replace alternatives.

IBM demonstrates its commitments to both its customers and to IMS by continuing to enhance IMS. Current investments have:

  • Substantially improved database availability
  • Established open access to IMS transactions
  • Extended Parallel Sysplex® systems support

IMS, the recognized database manager and transaction server in the industry, is critical to your business.

Hardware and Software Support Services

SmoothStart™/Installation Services

IBM Installation Services are provided for IMS by IBM Global Services, or your IBM Business Partner, at an additional cost. For additional information, contact your IBM representative and ask for Installation Services for IMS.

Additional technical services (planning and migration assistance, performance tuning, and other services) can be obtained through the Worldwide IMS Product Affinity Services team. For more information, contact the team at:

    dmservices@us.ibm.com

Reference Information

Refer to Software Announcement 202-211 , dated September 10, 2002, regarding IBM Data Management Tools.

Refer to Software Announcement 202-195 , dated August 20, 2002, regarding IBM COBOL V3R2.

Refer to Software Announcement 202-214 , dated September 17, 2002, regarding DB2 UDB V8R1.

Refer to Software Announcement 202-190 , dated August 13, 2002, regarding z/OS V1R4.

Trademarks

 
The e-business logo, IMS, z/OS, MVS, DataPropagator, DFSMSdss, FICON, zSeries, and SmoothStart are trademarks of International Business Machines Corporation in the United States or other countries or both.
 
CICS, OS/390, WebSphere, DB2, AIX, VisualAge, Language Environment, RACF, MQSeries, VTAM, ESCON, and Parallel Sysplex 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.
 
Other company, product, and service names may be trademarks or service marks of others.

Education Support

The following Information Management System (IMS™) classes are available now:

                                                       Course
Course Title                                           Number
 
IMS Fundamentals                                       CM010
IMS System Programming:  DBCTL                         CM100
IMS Database Recovery and Sharing                      CM201
  Control (DBRC)
Implementing IMS Security                              CM431
IMS Parallel Sysplex(R) Workshop                       CM621
IMS Connectivity and Web Enablement                    CM651
  Workshop
IMS DB Application Programming                         U3717
IMS DC Application Programming                         U3718
Physical Organization of Databases                     CM220
IMS Fast Path Implementation                           CM420

Call IBM Learning Services at 800-IBM-TEACH (426-8322) for schedules and enrollments. Visit the following Web site for additional information:

Technical Information

Specified Operating Environment

Hardware Requirements

Processors: IMS V8 operates on all IBM processors capable of running OS/390® Version 2, Release 10, or later.

System Console: The console requirements of OS/390 Version 2, Release 10, or later, apply.

Tape Units: At least one IBM 3420, 3480, or 3490 tape unit is required for installation and maintenance.

Direct Access Devices: Both the Binder work data set SYSUT1 (during the bind of the IMS VTAM® control blocks load monitoring module) and the SDFSRESL must reside on a device that supports a record size of 18 KB, or greater. For all other system libraries and working storage space, any device supported by the operating system is allowed.

Multiple Systems Coupling: When the physical link is channel-to-channel and is dedicated to IMS, the System/370™ channel-to-channel adapter, or a logical channel on the IBM 3088 or ESCON® is required.

MSC FICON™ CTC support requires that at least one side of the MSC link be an IBM eServer zSeries with the FICON channel and FICON CTC microcode. The other side (IMS) can be any processor with a FICON channel.

Supported Terminals: The IMS V8 Release Planning Guide lists the supported terminals.

In general, use of the IMS V8 Resource Manager requires a Coupling Facility level 9, or later. Sysplex Data Sharing (including Data Caching and VSO Data Sharing) with IRLM V2 requires a Coupling Facility level 9, or later.

Shared Queues and Shared EMH support require a Coupling Facility level 9. System-managed duplexing requires a Coupling Facility level 11, or later, and bidirectional CF to CF links.

Fast Path Virtual Storage Option (VSO) Systems Managed Rebuild requires Coupling Facility level 9, or later. Auto altering of VSO structure requires Coupling Facility level 9, or later. System Managed Duplexing of VSO structures requires Coupling Facility level 11, CF-to-CF links.

RSR Requirements: Sysplex Timer® (if data sharing or if workload is spread across multiple CPUs), highband control unit (3172), and at least one tape unit (3420, 3480, 3490) at the tracking site are required.

IMS/DB2® Coordinated Disaster Recovery support requires that the DB2 logs reside on devices supporting eXtended Remote Copy.

IMS Database Image Copy 2 enhancements require concurrent-copy capable DASD controllers.

Software Requirements

IMS V8 operates under OS/390 Version 2, Release 10 configurations, or subsequent versions, releases, and modification levels, including z/OS™ (5694-A01), unless otherwise stated, and requires the following minimum version, release, or modification levels:

  • OS/390 Version 2, Release 10 (5647-A01) with DFSMS (a base element of OS/390 Version 2, Release 10)
  • RACF® (included in a separately orderable Security Server feature of OS/390 Version 2, Release 10), or equivalent, if security is used
  • IBM High-Level Assembler Toolkit (5696-234), a separately orderable feature of OS/390

IMS V8 also operates in a virtual machine (VM) under control of OS/390 Version 2, Release 10, and is intended for use in a customer program development, testing, and non-XRF production environment, with some restrictions.

z/OS Version 1, Release 2 or higher is required for IMS MSC FICON CTC support.

z/OS Version 1, Release 2 or higher is required for Shared Queues/EMH Coupling Facility duplexing support and for system managed duplexing of VSO structures, Resource structures, and IRLM structures.

The z/OS Version 1, Release 2 Communications Server Affinity enhancement can be used, optionally, with IMS V8 Sysplex Terminal Management for enhanced usability.

z/OS Version 1, Release 2 Coupling Facility duplexing is recommended, though not required, for IMS V8 Resource Manager.

To take full advantage of Sysplex-wide Resource Management, including Sysplex Terminal Management and Coordinated Online Change, and the Single Image Operations Manager, all systems in the IMSplex should use IMS V8.

All systems involved in using APPC/OTMA Synchronous Shared Queues support should to be on IMS V8 and z/OS Version 1, Release 2, or higher (with OW50627) for Multi-System Cascaded Transactions support. Resource Recovery Services must also be active on all of these systems.

IMS Java™ application support has the following requirements:

  • The IBM Developer Kit for OS/390.
  • Java 2 Technology Edition (5655-D35), with a special enhancement referred to as the Persistent Reusable Java Virtual Machine (JVM). This is required for IMS V8 Java Dependent Region support. Note also that the High-Performance Java (HPJ) is not supported in IMS Version 8.
  • Unix System Services at runtime.
  • JDBC access to IMS DB for DB2 Stored Procedures requires DB2 UDB for z/OS and OS/390, Version 7 (5675-DB2) with APARs PQ46673 and PQ50443. You must also have the DB2 for OS/390 and z/OS SQLJ/JDBC driver with APAR PQ48383.
  • JDBC access to IMS DB for CICS® applications requires CICS Transaction Server for z/OS Version 2 (5697-E93).
  • JDBC access to IMS DB for WebSphere® applications requires WebSphere Application Server (WAS) z/OS V4.0.1 and additional WAS z/OS Connection Management support.
  • Java-COBOL Interoperation requires the object-oriented syntax for Java interoperability that is provided in IBM Enterprise COBOL for z/OS and OS/390 Version 3 Release 2.
  • Local J2EE two-phase commit support requires IMS Connect Version 1 Release 2 service stream enhancements plus either VisualAge® for Java 4.0 with its IMS Connector for Java 1.2.2 fixpack and WAS/390 4.0.1 or WebSphere Studio Application Developer Integration Edition 4.1 and WAS/390 4.0.4.

XML Enhancements have the following requirements:

  • Service definition creation for IMS COBOL and C applications requires WebSphere Studio Application Developer Integration Edition Version 4.1.
  • Service definition deployment of IMS services as EJB services or SOAP services requires WebSphere Application Server Enterprise Edition V4.1 (for COBOL and C).
  • IMS COBOL and PL/I programs receiving and sending XML documents require the XML Enabler for COBOL and PL/I, Version 3 Release 1.

IMS/DB2 Coordinated Disaster Recovery Support requires the IMS V8 Remote Site Recovery (RSR) Recovery Level Tracking (RLT) feature.

The Database Image Copy 2 (IC2) Enhancement support requires the following DFSMSdss™ maintenance:

  • OW54614: UW88877 or UW88878
  • OW51608: UW89183 or UW89184
  • OW55384: UW92928 or UW92929

IMS V8 TM can be connected via subsystem routing communications to DB2 Version 6, Release 1 (5645-DB2) or DB2 Version 7, Release 1 (5675-DB2).

IMS V8 DB can be connected via the DBCTL interface to CICS Transaction Server for OS/390 Version 1 (5655-147), CICS Transaction Server for z/OS Version 2 (5697-E93), CICS/ESA® Version 4 (5655-018), or user-written software.

IMS Version 8 TM can be connected via InterSystem Communications (ISC) to IMS Version 8 (5655-C56), IMS Version 7 (5655-B01), IMS Version 6 (5655-158), CICS Transaction Server for z/OS Version 2 (5697-E93), CICS Transaction Server for OS/390 Version 1 (5655-147), CICS/ESA Version 4 (5655-018), or user-written software.

The IMS ETO feature requires the IMS TM feature.

The IMS RSR RLT feature requires either the IMS TM or the IMS DB feature.

The IMS RSR DLT feature requires the IMS RSR RLT and IMS DB features.

IMS V8 is written in High Level Assembler, PL/X, and C.

RACF Abend Suppression requires OW51755 and OW52125.

Compatibility: IMS V8 is upwardly compatible from previous versions, allowing existing applications and data to be used without change. Migration and coexistence support is provided for IMS V6 and V7 with V8. Review the Preventative Service Planning (PSP) information for further, current details.

IMS V7 introduced a new combined MSC exit (DFSMSCE0) and was the last release to support the old MSC exits: Terminal Routing (DFSCMTR0), Input Message Routing (DFSNPRT0), Link Receive Routing (DFSCMLR0/DFSCMLR1), and Program Routing (DFSCMPR0). Customers using these exits need to migrate to the new exit.

IMS V7 was the last release to support the High Performance Java Compiler. Customers using HPJ-compiled applications should migrate to the new Persistent Reusable JVM support.

IMS V8 is the last release to support the IMS V5 SDEP CI format.

IMS V8 is the last release to support the Security Maintenance Utility (SMU). Customers using SMU should migrate to the Resource Access Control Facility (RACF) or an equivalent product.

IMS V8 is the last release to support Basic Telecommunications Access Method (BTAM). Customers using BTAM should migrate to Virtual Telecommunications Access Method (VTAM) or Transmission Control Protocol/Internet Protocol (TCP/IP). User code or tools dependent on BTAM should migrate to VTAM or TCP/IP.

Limitations

Performance Considerations

IMS Connect Drives Nearly 6,000 Transactions per Second

The IMS Performance group at IBM's Silicon Valley Lab has been conducting performance tests with IMS Connect. IMS Connect performance has been continually demonstrating significant improvement over the initial results posted in the IMS Summer 99 Newsletter article. Recent performance testing was done to determine whether high throughput rates could indeed be achieved with IMS Connect, utilizing several of the new key performance improvements being provided, such as persistent sockets, UNIX® System Services latch elimination, and OTMA latch contention reduction.

With one IMS Connect and one IMS, and using transactions that access IMS DB databases, IMS reached 5,955 transactions per second steady throughput. CPU usage was 52.3%. Thus, IMS Connect, enabling IMS for Internet access, has demonstrated the utmost in connectivity performance.

IMS Version 8 in a Parallel Sysplex Runs over One Billion Transactions per Day

IBM's Performance group has revisited the Fast Path High Stress environment for IMS Version 8 with 64-bit support on z/OS 1.2 in a four-way Parallel Sysplex using a shared Expedited Message Handling queue (EMHQ). V8 adds Parallel Database Open, which exhibits improved warm start times (up to 50% faster than IMS Version 7) and CSA VSCR, which provides up to a 45% reduction (compared to IMS Version 7) in CSA used below the 16 megabyte line.

Four IMS V8 systems, each on a separate LPAR with Common Queue Server (CQS) and IMS Resource Lock Manager (IRLM), demonstrated over 11,700 transactions per second with four-way datasharing, all with database updates. Contributing to the high transaction rate were CSA VSCR, Shared Virtual Storage Option (Shared VSO), improved IBM hardware including one 2064-216 processor and one M800 ESS DASD unit using large volumes (15,000 and 30,000 cylinders), FICON channels, Parallel Access Volumes, and Multiple Allegiance. Each IMS was logging at a rate of 3.2 megabytes per second, which is well below the demonstrated OLDS logging capacity of 26.8 megabytes per second on the FICON connected M800.

At a peak transaction rate of 11,784 transactions per second, this is further proof that IMS Version 8 and z/OS are the industry-leading high-performance transaction and database servers.

User Group Requirements: This announcement satisfies, or partially satisfies, the following requirements from one or more of the worldwide user group communities. Groups 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.

  • REQ00063772 — Determining PSB causing BACKOUT status for OLDS
  • REQ00075299 — Make LE Option overrides available via JCL fr IMS without LRR
  • REQ00062760 — Need ability to pass parameters through IMS to application
  • REQ0064445 — Allow passing of run-time parameters through IMS to COBOL programs
  • REQ00061239 — The messages received from all of the external interfaces could be distributed and executed on any of the IMS systems within the sysplex
  • MR0112014738 — Database Image Copy 2 — Copy multiple data sets per execution
  • MR0603007225 — Database Image Copy 2 — Copy multiple data sets per execution
  • MR00074058 — Database Image Copy 2 — Copy multiple data sets per execution
  • MR00075166 — Database Image Copy 2 — Allow user to select OPTIMIZE option
  • MR00074017 — IMS Message DFS0618A should be highlighted and non-scrollable
  • MR0427016016 — IMS and RACF resource class specification with IMS start-up (Done by M52)
  • R00051213 — Support MFSTEST for ETO nodes
  • R00051213_1 — Support MFSTEST for ETO nodes
  • R00051213_2 — Support MFSTEST for ETO nodes
  • R00061184 — ETO parallel sysplex support
  • R00061284 — Ability to force a single signon in an IMS-plex environment
  • R00067380 — Enable new/modified LU6.2 descriptors without an IMS restart
  • R00068340 — Eliminate VTAM generic resource affinity for LUO and LU6.1 sessions
  • R00068341 — Resume IMS conversations on a different IMS in sysplex
  • R00068343 — Unique LTERM names for multiple ETO signons of same userid in sysplex
  • R00070037 — STIMER support for in-bound CPI-C transactions
  • R00040194 — Allow user data to be attached to MSC transaction being shipped to a remote site (7.1)
  • R00045977 — Remove MSC SPA length restriction for program switching (6.1)
  • R00054794 — Need full APPC support across MSC links (5.1)
  • R00070192 — Allow user exit to mark a transaction to be processed locally when created by a BMP via a program-to-program switch
  • REQ00062341 — IMS DBRC Strategy Paper
  • REQ00057808 — Need IMS PRILOG enhancement for continuous availability
  • REQ00053336 — IMS — RECON LRECL Restriction
  • REQ00051031 — Need to improve PRILOG management for higher availability
  • REQ00037880 — DBRC SSID REC GROWTH SHD NOT BE LIMT'D by MAX RECSZ ON RECON
  • REQ00062341 — IMS DBRC Strategy Paper
  • REQ00053087 — Propagate RECON Switches to all connected IMS systems
  • REQ00038561 — IMS CONTROL REGIONS SHOULD REPORT RECON SWITCH WHEN DETECTED
  • REQ00022820 — Message to the online subsystem joblog for RECON failure
  • REQ00064733 — RECON Security Levels (BDUG)
  • REQ00063614 — Security Exit in DSPURX00
  • REQ00062341 — IMS DBRC Strategy Paper
  • REQ00058683 — Provide RACF support for DBRC commands
  • REQ00038017 — IMS/DBRC/RECON Security
  • REQ00022878 — DBRC Should Have Global Security Interfaces
  • REQ00003842 — ALLOW READ ONLY ACCESS TO RECONS
  • REQ00020216 — DBRC U2480 Abend causes IMS to abend
  • REQ00061661 — DSP0307I INTERNAL DBRC ERROR shouldn't cause ctl region abend
  • REQ00065574 — DBRC requirement: Add "FORCE" for needed record delete
  • MR00076785 — Define Shared VSO DEDBs as non-recoverable
  • MR0427014714 — Non-recoverable DEDB in a Dataspace
  • REQ00041858 — Non-recoverable DEDB in a Dataspace
  • REQ00041858_1 — Non-recoverable DEDB in a Dataspace
  • REQ00041858_2 — Non-recoverable DEDB in a Dataspace
  • MR00074788 — Lift the restriction of 240 areas maximum for a single DEDB
  • REQ00022860 — Provide Display of Transaction Definition
  • REQ00022885 — Better MVS™ System Console Support in IMS
  • REQ00023983 — Browse of data from DISPLAY commands
  • REQ00023984 — Second level of command security
  • REQ00029470 — Distinct security for /CHE command
  • REQ00038659 — MTO support improvements
  • REQ00038672 — Reserved keywords suppression
  • REQ00038978 — IMS — Allow /CHE DUMPQ via AOI Program
  • REQ00039893 — IMS Master Terminal Support
  • REQ00051854 — Provide synchronous response to all IMS commands
  • REQ00051866 — IMS should not enhance the existing MTO interface
  • REQ00052335 — Exit of IMS conversations during Online-Change
  • REQ00053638 — /DIS Command Generic Resources (IMS 4.1)
  • REQ00055873 — /DIS NODE should have CLASS and PRIORITY
  • REQ00056111 — IMS Automation Requirements
  • REQ00056126 — Message Standardization — Improved MTO Support
  • REQ00056128 — Multiple MTO Terminals — Improved MTO Support
  • REQ00056135 — AOF like Support — Improved MTO Support
  • REQ00056136 — CLIST Command Support — Improved MTO Support
  • REQ00057423 — /DIS command output is not sorted by Alpha-Numeric order
  • REQ00058535 — /DIS USER command enhancement
  • REQ00058616 — Provide a "Sysplex Centric" view of shared IMS resources
  • REQ00058636 — Ability to synchronize view of shared resources by new system
  • REQ00059028 — /DIS USER DEADQ — no "None Found" message
  • REQ00060704 — /DIS MODIFY needs a keyword for programs such as PGM
  • REQ00063094 — DFS™ message when connecting to an external resource
  • REQ00064394 — Display Command Enhancement
  • REQ00065257 — Generic /START REGION Support Enhancement
  • REQ00066093 — PMOP1096-028 Need Global IMS Command Support — Single Point of Control
  • REQ00066094 — PMOP1096-029 Coordinated IMS Online Change
  • REQ00068160 — PTDB0997 Co-ordinated Resource Management
  • REQ00068341 — POTH1297-168 Conversations with Shared Queues
  • MR00058525 — Display of system parameters (IMS DFSPBxxx) at startup
  • MR1109001332 — VSCR Needed for FDBR
  • MR00073389 — USE MORE MEMORY ABOVE 16M
  • R00048263 — Open databases in parallel (avail for FF)
  • R00060540 — DB alloc/open in parallel (FF)
  • R00021947 — Start DB with /OPEN command
  • R00042061 — /STA DB with open

Planning Information

Direct Customer Support: Direct customer support is provided by the IBM Operational Support Services — Support Line. This fee service can enhance your productivity by providing voice and electronic access into the IBM support organization. IBM Operational Support Services — Support Line will help answer questions pertaining to usage, how to, and suspected software defects for eligible products.

Installation and technical support is provided by IBM Global Services. For more information on services, call 800-IBM-4YOU (426-4968).

Security, Auditability, and Control

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

The following advance publications are available. To order, contact your IBM representative.

  • IMS Version 8 Fact Sheet (GC27-1517)
  • IMS Version 8 Release Planning Guide (GC27-1305)

New Licensees

CFSW configuration and order entry capability are available.

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

                                                      ESL OTC
Program                                               Feature
Number             Description                        Number
 
5655-C56           Database Level Tracking            0066
5655-C56           Database Manager                   0107
5655-C56           Extended Terminal Option           0148
5655-C56           Recovery Level Tracking            0189
5655-C56           Transaction Manager                0025

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

Parallel Sysplex License Charge (PSLC) Basic License: To order 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, Level B, Level C, and Level D features and quantity.

If there are 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.

IMS Database-Level Tracking
 
                      PSLC           PSLC Basic License
Machine               Feature        MLC Feature
MSU Capacity          Number         Description
 
1                     0043           PSLC Base, 1 MSU
2                     0044           PSLC Base, 2 MSUs
3                     0045           PSLC Base, 3 MSUs
4 -- 45               0046           PSLC Level A, 1 MSU
                      0047           PSLC Level A, 42 MSUs
 
46 -- 175             0048           PSLC Level B, 1 MSU
                      0049           PSLC Level B, 10 MSUs
                      0050           PSLC Level B, 50 MSUs
 
176 -- 315            0051           PSLC Level C, 1 MSU
                      0052           PSLC Level C, 10 MSUs
                      0053           PSLC Level C, 50 MSUs
 
IMS Database-Level Tracking (Continued)
 
                      PSLC           PSLC Basic License
Machine               Feature        MLC Feature
MSU Capacity          Number         Description
 
316 or more           0054           PSLC Level D, 1 MSU
                      0055           PSLC Level D, 50 MSUs
 
Not Applicable        0056           PSLC NC Identifier

Example 1: For a single machine with 11 MSUs, the PSLC features would be:

  • 0045 — quantity 1
  • 0046 — 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:
    • 0045 — quantity 1
    • 0047 — quantity 1
    • 0048 — quantity 5
    • 0049 — quantity 1
  • PSLC no-charge license #2:
    • 0056 — quantity 1

Database Manager
 
                      PSLC           PSLC Basic License
Machine               Feature        MLC Feature
MSU Capacity          Number         Description
 
1                     0084           PSLC Base, 1 MSU
2                     0085           PSLC Base, 2 MSUs
3                     0086           PSLC Base, 3 MSUs
4 -- 45               0087           PSLC Level A, 1 MSU
                      0088           PSLC Level A, 42 MSUs
 
46 -- 175             0089           PSLC Level B, 1 MSU
                      0090           PSLC Level B, 10 MSUs
                      0091           PSLC Level B, 50 MSUs
 
176 -- 315            0092           PSLC Level C, 1 MSU
                      0093           PSLC Level C, 10 MSUs
                      0094           PSLC Level C, 50 MSUs
 
316 or more           0095           PSLC Level D, 1 MSU
                      0096           PSLC Level D, 50 MSUs
 
Not Applicable        0097           PSLC NC Identifier

Extended Terminal Option
 
                      PSLC           PSLC Basic License
Machine               Feature        MLC Feature
MSU Capacity          Number         Description
 
1                     0125           PSLC Base, 1 MSU
2                     0126           PSLC Base, 2 MSUs
3                     0127           PSLC Base, 3 MSUs
4 -- 45               0128           PSLC Level A, 1 MSU
                      0129           PSLC Level A, 42 MSUs
 
46 -- 175             0130           PSLC Level B, 1 MSU
                      0131           PSLC Level B, 10 MSUs
                      0132           PSLC Level B, 50 MSUs
 
Extended Terminal Option (Continued)
 
                      PSLC           PSLC Basic License
Machine               Feature        MLC Feature
MSU Capacity          Number         Description
 
176 -- 315            0133           PSLC Level C, 1 MSU
                      0134           PSLC Level C, 10 MSUs
                      0135           PSLC Level C, 50 MSUs
 
316 or more           0136           PSLC Level D, 1 MSU
                      0137           PSLC Level D, 50 MSUs
 
Not Applicable        0138           PSLC NC Identifier

Recovery Level Tracking
 
                      PSLC           PSLC Basic License
Machine               Feature        MLC Feature
MSU Capacity          Number         Description
 
1                     0166           PSLC Base, 1 MSU
2                     0167           PSLC Base, 2 MSUs
3                     0168           PSLC Base, 3 MSUs
4 -- 45               0169           PSLC Level A, 1 MSU
                      0170           PSLC Level A, 42 MSUs
 
46 -- 175             0171           PSLC Level B, 1 MSU
                      0172           PSLC Level B, 10 MSUs
                      0173           PSLC Level B, 50 MSUs
 
176 -- 315            0174           PSLC Level C, 1 MSU
                      0175           PSLC Level C, 10 MSUs
                      0176           PSLC Level C, 50 MSUs
 
316 or more           0177           PSLC Level D, 1 MSU
                      0178           PSLC Level D, 50 MSUs
 
Not Applicable        0179           PSLC NC Identifier

Transaction Manager
 
 
                      PSLC           PSLC Basic License
Machine               Feature        MLC Feature
MSU Capacity          Number         Description
 
1                     0002           PSLC Base, 1 MSU
2                     0003           PSLC Base, 2 MSUs
3                     0004           PSLC Base, 3 MSUs
4 -- 45               0005           PSLC Level A, 1 MSU
                      0006           PSLC Level A, 42 MSUs
 
46 -- 175             0007           PSLC Level B, 1 MSU
                      0008           PSLC Level B, 10 MSUs
                      0009           PSLC Level B, 50 MSUs
 
176 -- 315            0010           PSLC Level C, 1 MSU
                      0011           PSLC Level C, 10 MSUs
                      0012           PSLC Level C, 50 MSUs
 
316 or more           0013           PSLC Level D, 1 MSU
                      0014           PSLC Level D, 50 MSUs
 
Not Applicable        0015           PSLC NC Identifier

Variable Workload License Charge (VWLC) Basic License: To order a basic license, specify the program number and feature number 9001 for asset registration. Specify the WLC Base feature. If applicable, specify the WLC Level 1, Level 2, Level 3, and Level 4 features with the appropriate quantity. Also, specify the feature number of the desired distribution medium.

The VWLC requires the use of the IBM License Use Management (LUM) tool.

VWLC Aggregation: When z/OS is installed on two or more IBM S/390® or IBM eServer zSeries 900 (z900) machines comprising a sysplex, Variable WLC aggregation applies to z/OS and the S/390 software programs that have Variable WLC.

Whether there is only one license or more than one license of the program in the sysplex, the charge for all licenses is associated to the "aggregation license" by specifying the applicable WLC feature numbers and quantity represented by the sum of the MSUs (millions of service units) in the sysplex. The "aggregation license" is an additional program license that is ordered and serialized, although there is no shipment associated with it.

For the actual licenses, the charge is reflected as $0.00 by specifying the applicable "registration" Variable WLC feature numbers and the quantity equal to the MSUs of that license running on the designated machine.

Database Level Tracking
 
                   WLC           WLC Basic License
                   Feature       Monthly License Charge
MSU Capacity       Number        Feature Description
 
0 -- 45            0070          VWLC Base, L1:  incl 45 MSUs
 
46 -- 175          0071          VWLC Add Qty, L1:  46-175 MSUs
                   0072          WLC Reg Base, L1:  incl 1 MSU
                   0073          WLC Reg Add Qty, L1:  46-175 MSUs
 
176 -- 315         0074          VWLC Add Qty, L2:  176-315 MSUs
                   0075          WLC Reg Add Qty, L2:  176-315 MSUs
 
316 -- 575         0076          VWLC Add Qty, L3:  316-575 MSUs
                   0077          WLC Reg Add Qty, L3:  316-575 MSUs
                   0078          L3:  per 50 MSUs, 316-575 MSUs
                   0079          L3:  Reg per 50 MSUs, 316-575 MSUs
 
Database Level Tracking (Continued)
 
                   WLC           WLC Basic License
                   Feature       Monthly License Charge
MSU Capacity       Number        Feature Description
 
576 -- 875         0080          VWLC Add Qty, L4:  576-875 MSUs
                   0081          WLC Reg Add Qty, L4:  576-875 MSUs
                   0082          L4:  per 50 MSUs, 576-875 MSUs
                   0083          L4:  Reg per 50 MSUs, 576-875 MSUs
 
876 -- 1314        4405          VWLC Add Qty, L5:  876-1314 MSUs
                   4407          WLC Reg Add Qty, L5:  876-1314 MSUs
                   4406          L5:  per 50 MSUs, 876-1314 MSUs
                   4408          L5:  Reg per 50 MSUs, 876-1314 MSUs
 
1315 -- 1975       4429          VWLC Add Qty, L6:  1315-1975 MSUs
                   4431          WLC Reg Add Qty, L6:  1314-1975 MSUs
                   4430          L6:  per 50 MSUs, 1314-1975 MSUs
                   4432          L6:  Reg per 50 MSUs, 1314-1975 MSUs
 
1976 or more       4433          VWLC Add Qty, L7:  1976+ MSUs
                   4435          WLC Reg Add Qty, L7:  1976+ MSUs
                   4434          L7:  per 50 MSUs, 1976+ MSUs
                   4436          L7:  Reg per 50 MSUs, 1976+ MSUs

Example 1: For a single machine with the program running at 220 MSUs, the Variable WLC features would be:

  • 0070 — quantity 1
  • 0071 — quantity 130
  • 0074 — quantity 45

Example 2: If there are two machines in a sysplex, and a program is running on machine #1 at 190 MSUs and on machine #2 at 140 MSUs, the Variable WLC feature numbers and quantities to be ordered would be:

  • License on machine #1 for 190 MSUs:
    • 0072 — quantity 1
    • 0073 — quantity 174
    • 0075 — quantity 15
  • License on machine #2 for 140 MSUs:
    • 0072 — quantity 1
    • 0073 — quantity 139
  • Aggregation license for a total of 330 MSUs:
    • 0070 — quantity 1
    • 0071 — quantity 130
    • 0074 — quantity 140
    • 0076 — quantity 15

Database Manager
 
                   WLC           WLC Basic License
                   Feature       Monthly License Charge
MSU Capacity       Number        Feature Description
 
0 -- 45            0111          VWLC Base, L1:  incl 45 MSUs
 
46 -- 175          0112          VWLC Add Qty, L1:  46-175 MSUs
                   0113          WLC Reg Base, L1:  incl 1 MSU
                   0114          WLC Reg Add Qty, L1:  46-175 MSUs
 
176 -- 315         0115          VWLC Add Qty, L2:  176-315 MSUs
                   0116          WLC Reg Add Qty, L2:  176-315 MSUs
 
316 -- 575         0117          VWLC Add Qty, L3:  316-575 MSUs
                   0118          WLC Reg Add Qty, L3:  316-575 MSUs
                   0119          L3:  per 50 MSUs, 316-575 MSUs
                   0120          L3:  Reg per 50 MSUs, 316-575 MSUs
 
576 -- 875         0121          VWLC Add Qty, L4:  576-875 MSUs
                   0122          WLC Reg Add Qty, L4:  576-875 MSUs
                   0123          L4:  per 50 MSUs, 576-875 MSUs
                   0124          L4:  Reg per 50 MSUs, 576-875 MSUs
 
Database Manager (Continued)
 
                   WLC           WLC Basic License
                   Feature       Monthly License Charge
MSU Capacity       Number        Feature Description
 
876 -- 1314        4409          VWLC Add Qty, L5:  876-1314 MSUs
                   4411          WLC Reg Add Qty, L5:  876-1314 MSUs
                   4410          L5:  per 50 MSUs, 876-1314 MSUs
                   4412          L5:  Reg per 50 MSUs, 876-1314 MSUs
 
1315 -- 1975       4437          VWLC Add Qty, L6:  1315-1975 MSUs
                   4439          WLC Reg Add Qty, L6:  1314-1975 MSUs
                   4438          L6:  per 50 MSUs, 1314-1975 MSUs
                   4440          L6:  Reg per 50 MSUs, 1314-1975 MSUs
 
1976 or more       4441          VWLC Add Qty, L7:  1976+ MSUs
                   4443          WLC Reg Add Qty, L7:  1976+ MSUs
                   4442          L7:  per 50 MSUs, 1976+ MSUs
                   4444          L7:  Reg per 50 MSUs, 1976+ MSUs

Example 1: For a single machine with the program running at 220 MSUs, the Variable WLC features would be:

  • 0111 — quantity 1
  • 0112 — quantity 130
  • 0114 — quantity 45

Example 2: If there are two machines in a sysplex, and a program is running on machine #1 at 190 MSUs and on machine #2 at 140 MSUs, the Variable WLC feature numbers and quantities to be ordered would be:

  • License on machine #1 for 190 MSUs:
    • 0113 — quantity 1
    • 0114 — quantity 174
    • 0116 — quantity 15
  • License on machine #2 for 140 MSUs:
    • 0113 — quantity 1
    • 0114 — quantity 139
  • Aggregation license for a total of 330 MSUs:
    • 0111 — quantity 1
    • 0112 — quantity 130
    • 0115 — quantity 140
    • 0117 — quantity 15

Extended Terminal Option
 
                   WLC           WLC Basic License
                   Feature       Monthly License Charge
MSU Capacity       Number        Feature Description
 
0 -- 45            0152          VWLC Base, L1:  incl 45 MSUs
 
46 -- 175          0153          VWLC Add Qty, L1:  46-175 MSUs
                   0154          WLC Reg Base, L1:  incl 1 MSU
                   0155          WLC Reg Add Qty, L1:  46-175 MSUs
 
176 -- 315         0156          VWLC Add Qty, L2:  176-315 MSUs
                   0157          WLC Reg Add Qty, L2:  176-315 MSUs
 
316 -- 575         0158          VWLC Add Qty, L3:  316-575 MSUs
                   0159          WLC Reg Add Qty, L3:  316-575 MSUs
                   0160          L3:  per 50 MSUs, 316-575 MSUs
                   0161          L3:  Reg per 50 MSUs, 316-575 MSUs
 
576 -- 875         0162          VWLC Add Qty, L4:  576-875 MSUs
                   0163          WLC Reg Add Qty, L4:  576-875 MSUs
                   0164          L4:  per 50 MSUs, 576-875 MSUs
                   0165          L4:  Reg per 50 MSUs, 576-875 MSUs
 
876 -- 1314        4413          VWLC Add Qty, L5:  876-1314 MSUs
                   4415          WLC Reg Add Qty, L5:  876-1314 MSUs
                   4414          L5:  per 50 MSUs, 876-1314 MSUs
                   4416          L5:  Reg per 50 MSUs, 876-1314 MSUs
 
Extended Terminal Option (Continued)
 
                   WLC           WLC Basic License
                   Feature       Monthly License Charge
MSU Capacity       Number        Feature Description
 
1315 -- 1975       4445          VWLC Add Qty, L6:  1315-1975 MSUs
                   4447          WLC Reg Add Qty, L6:  1314-1975 MSUs
                   4446          L6:  per 50 MSUs, 1314-1975 MSUs
                   4448          L6:  Reg per 50 MSUs, 1314-1975 MSUs
 
1976 or more       4449          VWLC Add Qty, L7:  1976+ MSUs
                   4451          WLC Reg Add Qty, L7:  1976+ MSUs
                   4450          L7:  per 50 MSUs, 1976+ MSUs
                   4452          L7:  Reg per 50 MSUs, 1976+ MSUs

Example 1: For a single machine with the program running at 220 MSUs, the Variable WLC features would be:

  • 0152 — quantity 1
  • 0153 — quantity 130
  • 0156 — quantity 45

Example 2: If there are two machines in a sysplex, and a program is running on machine #1 at 190 MSUs and on machine #2 at 140 MSUs, the Variable WLC feature numbers and quantities to be ordered would be:

  • License on machine #1 for 190 MSUs:
    • 0154 — quantity 1
    • 0155 — quantity 174
    • 0157 — quantity 15
  • License on machine #2 for 140 MSUs:
    • 0154 — quantity 1
    • 0155 — quantity 139
  • Aggregation license for a total of 330 MSUs:
    • 0152 — quantity 1
    • 0153 — quantity 130
    • 0156 — quantity 140
    • 0158 — quantity 15

Recovery Level Tracking
 
                   WLC           WLC Basic License
                   Feature       Monthly License Charge
MSU Capacity       Number        Feature Description
 
0 -- 45            0193          VWLC Base, L1:  incl 45 MSUs
 
46 -- 175          0194          VWLC Add Qty, L1:  46-175 MSUs
                   0195          WLC Reg Base, L1:  incl 1 MSU
                   0196          WLC Reg Add Qty, L1:  46-175 MSUs
 
176 -- 315         0197          VWLC Add Qty, L2:  176-315 MSUs
                   0198          WLC Reg Add Qty, L2:  176-315 MSUs
 
316 -- 575         0199          VWLC Add Qty, L3:  316-575 MSUs
                   0200          WLC Reg Add Qty, L3:  316-575 MSUs
                   0201          L3:  per 50 MSUs, 316-575 MSUs
                   0202          L3:  Reg per 50 MSUs, 316-575 MSUs
 
576 -- 875         0203          VWLC Add Qty, L4:  576-875 MSUs
                   0204          WLC Reg Add Qty, L4:  576-875 MSUs
                   0205          L4:  per 50 MSUs, 576-875 MSUs
                   0206          L4:  Reg per 50 MSUs, 576-875 MSUs
 
876 -- 1314        4417          VWLC Add Qty, L5:  876-1314 MSUs
                   4419          WLC Reg Add Qty, L5:  876-1314 MSUs
                   4418          L5:  per 50 MSUs, 876-1314 MSUs
                   4420          L5:  Reg per 50 MSUs, 876-1314 MSUs
 
1315 -- 1975       4453          VWLC Add Qty, L6:  1315-1975 MSUs
                   4455          WLC Reg Add Qty, L6:  1314-1975 MSUs
                   4454          L6:  per 50 MSUs, 1314-1975 MSUs
                   4456          L6:  Reg per 50 MSUs, 1314-1975 MSUs
 
Recovery Level Tracking (Continued)
 
                   WLC           WLC Basic License
                   Feature       Monthly License Charge
MSU Capacity       Number        Feature Description
 
1976 or more       4457          VWLC Add Qty, L7:  1976+ MSUs
                   4459          WLC Reg Add Qty, L7:  1976+ MSUs
                   4458          L7:  per 50 MSUs, 1976+ MSUs
                   4460          L7:  Reg per 50 MSUs, 1976+ MSUs

Example 1: For a single machine with the program running at 220 MSUs, the Variable WLC features would be:

  • 0193 — quantity 1
  • 0194 — quantity 130
  • 0197 — quantity 45

Example 2: If there are two machines in a sysplex, and a program is running on machine #1 at 190 MSUs and on machine #2 at 140 MSUs, the Variable WLC feature numbers and quantities to be ordered would be:

  • License on machine #1 for 190 MSUs:
    • 0195 — quantity 1
    • 0196 — quantity 174
    • 0198 — quantity 15
  • License on machine #2 for 140 MSUs:
    • 0195 — quantity 1
    • 0196 — quantity 139
  • Aggregation license for a total of 330 MSUs:
    • 0193 — quantity 1
    • 0194 — quantity 130
    • 0197 — quantity 140
    • 0199 — quantity 15

Transaction Manager
 
                   WLC           WLC Basic License
                   Feature       Monthly License Charge
MSU Capacity       Number        Feature Description
 
0 -- 45            0029          VWLC Base, L1:  incl 45 MSUs
 
46 -- 175          0030          VWLC Add Qty, L1:  46-175 MSUs
                   0031          WLC Reg Base, L1:  incl 1 MSU
                   0032          WLC Reg Add Qty, L1:  46-175 MSUs
 
176 -- 315         0033          VWLC Add Qty, L2:  176-315 MSUs
                   0034          WLC Reg Add Qty, L2:  176-315 MSUs
 
316 -- 575         0035          VWLC Add Qty, L3:  316-575 MSUs
                   0036          WLC Reg Add Qty, L3:  316-575 MSUs
                   0037          L3:  per 50 MSUs, 316-575 MSUs
                   0038          L3:  Reg per 50 MSUs, 316-575 MSUs
 
576 -- 875         0039          VWLC Add Qty, L4:  576-875 MSUs
                   0040          WLC Reg Add Qty, L4:  576-875 MSUs
                   0041          L4:  per 50 MSUs, 576-875 MSUs
                   0042          L4:  Reg per 50 MSUs, 576-875 MSUs
 
876 -- 1314        4401          VWLC Add Qty, L5:  876-1314 MSUs
                   4403          WLC Reg Add Qty, L5:  876-1314 MSUs
                   4402          L5:  per 50 MSUs, 876-1314 MSUs
                   4404          L5:  Reg per 50 MSUs, 876-1314 MSUs
 
1315 -- 1975       4421          VWLC Add Qty, L6:  1315-1975 MSUs
                   4423          WLC Reg Add Qty, L6:  1314-1975 MSUs
                   4422          L6:  per 50 MSUs, 1314-1975 MSUs
                   4424          L6:  Reg per 50 MSUs, 1314-1975 MSUs
 
1976 or more       4425          VWLC Add Qty, L7:  1976+ MSUs
                   4427          WLC Reg Add Qty, L7:  1976+ MSUs
                   4426          L7:  per 50 MSUs, 1976+ MSUs
                   4428          L7:  Reg per 50 MSUs, 1976+ MSUs

Example 1: For a single machine with the program running at 220 MSUs, the Variable WLC features would be:

  • 0029 — quantity 1
  • 0030 — quantity 130
  • 0033 — quantity 45

Example 2: If there are two machines in a sysplex, and a program is running on machine #1 at 190 MSUs and on machine #2 at 140 MSUs, the Variable WLC feature numbers and quantities to be ordered would be:

  • License on machine #1 for 190 MSUs:
    • 0031 — quantity 1
    • 0032 — quantity 174
    • 0034 — quantity 15
  • License on machine #2 for 140 MSUs:
    • 0031 — quantity 1
    • 0032 — quantity 139
  • Aggregation license for a total of 330 MSUs:
    • 0029 — quantity 1
    • 0030 — quantity 130
    • 0033 — quantity 140
    • 0035 — quantity 15

S/390 and zSeries Usage Pricing (Usage License Charge) Basic License: To order a basic license, specify the appropriate program and feature number, if required, for asset registration. Specify the applicable S/390 and zSeries Usage Pricing feature. Also, specify the feature number of the desired distribution medium.

Charges will be based upon the Peak MSUs. Usage reported between thresholds of features 1, 2, or 3, will be rounded up to the next MSU level. Above 1.0 MSU, usage will be rounded to the nearest whole MSU. For example, 2.4 MSUs would round to 2.0 MSUs for pricing, and 2.5 MSUs would round to 3.0 MSUs for pricing.

The customer pricing will be determined by selecting either:

  • Feature 1 (if usage is below 0.25 MSU)
  • Feature 2 (if usage is between 0.26 and 0.50)
  • Feature 3 (if usage is between 0.51 and 1.0)
  • Feature 3+ (# MSUs from 2-11 times the charge associated with feature number 4) + (# MSUs from 12-44 times the charge associated with feature number 5) + (# MSUs from 45-78 times the charge associated with feature number 6) + (# MSUs above 78 times the charge associated with feature number 7 — if applicable)

Examples for ordering:

A customer with a measured usage (from the IBM Measured Usage report) of 0.3 MSU would:

  • Order quantity 1 of the 0.26 to 0.5 MSU base feature

A customer with 6.6 MSUs (from the IBM Usage report) would:

  • Be rounded up to 7.0 MSUs
  • Order quantity 1 of the "0.51 to 1.0 MSU" base feature
  • Order quantity 6 of the Level A 1 MSU feature

A customer with 15 MSUs (from the IBM Usage report) would:

  • Order quantity 1 of the "0.51 to 1.0 MSU" base feature
  • Order quantity 10 of the Level A 1 MSU feature
  • Order quantity 4 of the Level B 1 MSU feature

A customer with 50 MSUs (from the IBM Usage report) would:

  • Order quantity 1 of the "0.51 to 1.0 MSU" base feature
  • Order quantity 10 of the Level A 1 MSU feature
  • Order quantity 33 of the Level B 1 MSU feature
  • Order quantity 6 of the Level C 1 MSU feature

A customer with 85 MSUs (from the IBM Usage report) would:

  • Order quantity 1 of the "0.51 to 1.0 MSU" base feature
  • Order quantity 10 of the Level A 1 MSU feature
  • Order quantity 33 of the Level B 1 MSU feature
  • Order quantity 34 of the Level C 1 MSU feature
  • Order quantity 7 of the Level D 1 MSU feature

Database Level Tracking
 
                                             Usage Pricing
                                             Feature
Description                                  Number
 
0 to 0.25 MSU Base                           0057
0.26 to 0.5 MSU Base                         0058
0.51 to 1.0 MSU Base                         0060
 
Level A Chg/MSU (2 to 11 MSUs)               0061
Level B Chg/MSU (12 to 44 MSUs)              0062
Level C Chg/MSU (45 to 78 MSUs)              0063
Level D Chg/MSU (Above 78 MSUs)              0064
Level D Chg/MSU (Per 50 MSUs for             0065
  Machine Capacity of 79+ MSUs)
 
NC ID Feature                                0059

Database Manager
 
                                             Usage Pricing
                                             Feature
Description                                  Number
 
0 to 0.25 MSU Base                           0098
0.26 to 0.5 MSU Base                         0099
0.51 to 1.0 MSU Base                         0101
 
Level A Chg/MSU (2 to 11 MSUs)               0102
Level B Chg/MSU (12 to 44 MSUs)              0103
Level C Chg/MSU (45 to 78 MSUs)              0104
Level D Chg/MSU (Above 78 MSUs)              0105
Level D Chg/MSU (Per 50 MSUs for             0106
  Machine Capacity of 79+ MSUs)
 
NC ID Feature                                0100

Extended Terminal Option
 
                                             Usage Pricing
                                             Feature
Description                                  Number
 
0 to 0.25 MSU Base                           0139
0.26 to 0.5 MSU Base                         0140
0.51 to 1.0 MSU Base                         0142
 
Level A Chg/MSU (2 to 11 MSUs)               0143
Level B Chg/MSU (12 to 44 MSUs)              0144
Level C Chg/MSU (45 to 78 MSUs)              0145
Level D Chg/MSU (Above 78 MSUs)              0146
Level D Chg/MSU (Per 50 MSUs for             0147
  Machine Capacity of 79+ MSUs)
 
NC ID Feature                                0141

Recovery Level Tracking
 
                                             Usage Pricing
                                             Feature
Description                                  Number
 
0 to 0.25 MSU Base                           0180
0.26 to 0.5 MSU Base                         0181
0.51 to 1.0 MSU Base                         0183
 
Level A Chg/MSU (2 to 11 MSUs)               0184
Level B Chg/MSU (12 to 44 MSUs)              0185
Level C Chg/MSU (45 to 78 MSUs)              0186
Level D Chg/MSU (Above 78 MSUs)              0187
Level D Chg/MSU (Per 50 MSUs for             0188
  Machine Capacity of 79+ MSUs)
 
NC ID Feature                                0182

Transaction Manager
 
                                             Usage Pricing
                                             Feature
Description                                  Number
 
0 to 0.25 MSU Base                           0016
0.26 to 0.5 MSU Base                         0017
0.51 to 1.0 MSU Base                         0019
 
Level A Chg/MSU (2 to 11 MSUs)               0020
Level B Chg/MSU (12 to 44 MSUs)              0021
Level C Chg/MSU (45 to 78 MSUs)              0022
Level D Chg/MSU (Above 78 MSUs)              0023
Level D Chg/MSU (Per 50 MSUs for             0024
  Machine Capacity of 79+ MSUs)
 
NC ID Feature                                0018

Growth Opportunity License Charge (GOLC): To order GOLC software, specify the program number, feature number 9001 for asset registration, and the GOLC monthly charge feature number from the table below. Also, specify the feature number for the desired distribution medium.

Database Level Tracking
 
GOLC                     GOLC
Category                 Feature Number
 
H30                      0067
H50                      0068
H70                      0069

Database Manager
 
GOLC                     GOLC
Category                 Feature Number
 
H30                      0108
H50                      0109
H70                      0110

Extended Terminal Option
 
GOLC                     GOLC
Category                 Feature Number
 
H30                      0149
H50                      0150
H70                      0151

Recovery Level Tracking
 
GOLC                     GOLC
Category                 Feature Number
 
 
H30                      0190
H50                      0191
H70                      0192

Transaction Manager
 
GOLC                     GOLC
Category                 Feature Number
 
H30                      0026
H50                      0027
H70                      0028

zSeries Entry License Charge (zELC): To order zELC software, specify the program number, feature number 9001 for asset registration, and the zELC monthly charge feature number from the table below. Also, specify the feature number for the desired distribution medium.

Database Level Tracking
 
z800 Models                        zELC Feature Number
 
0A1 -- 1 engine                    4009
0B1 -- 1 engine                    4010
0C1 -- 1 engine                    4011
001 -- 1 engine                    4012
0A2 -- 2 engines                   4013
002 -- 2 engines                   4014
003 -- 3 engines                   4015
004 -- 4 engines                   4016

Database Manager
 
z800 Models                        zELC Feature Number
 
0A1 -- 1 engine                    4017
0B1 -- 1 engine                    4018
0C1 -- 1 engine                    4019
001 -- 1 engine                    4020
0A2 -- 2 engines                   4021
002 -- 2 engines                   4022
003 -- 3 engines                   4023
004 -- 4 engines                   4024

Extended Terminal Option
 
z800 Models                        zELC Feature Number
 
0A1 -- 1 engine                    4025
0B1 -- 1 engine                    4026
0C1 -- 1 engine                    4027
001 -- 1 engine                    4028
0A2 -- 2 engines                   4029
002 -- 2 engines                   4030
003 -- 3 engines                   4031
004 -- 4 engines                   4032

Recovery Level Tracking
 
z800 Models                        zELC Feature Number
 
0A1 -- 1 engine                    4033
0B1 -- 1 engine                    4034
0C1 -- 1 engine                    4035
001 -- 1 engine                    4036
0A2 -- 2 engines                   4037
002 -- 2 engines                   4038
003 -- 3 engines                   4039
004 -- 4 engines                   4040

Transaction Manager
 
z800 Models                        zELC Feature Number
 
0A1 -- 1 engine                    4001
0B1 -- 1 engine                    4002
0C1 -- 1 engine                    4003
001 -- 1 engine                    4004
0A2 -- 2 engines                   4005
002 -- 2 engines                   4006
003 -- 3 engines                   4007
004 -- 4 engines                   4008

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

Basic Machine-Readable Material: Users of IMS V8 Database Manager must select one of the following supply features:

Environment         Feature Number         Distribution Medium
 
OS/390              5872                   3480 tape cartridge
OS/390              6745                   4-mm cartridge

Users of IMS V8 Database Manager Optional Source must select one of the following supply features:

Environment         Feature Number         Distribution Medium
 
OS/390              5976                   3480 tape cartridge
OS/390              6753                   4-mm cartridge

Users of IMS V8 Database Level Tracking must select one of the following supply features:

Environment         Feature Number         Distribution Medium
 
 
OS/390              5882                   3480 tape cartridge
OS/390              6746                   4-mm cartridge

Users of IMS V8 Extended Terminal Option must select one of the following supply features:

Environment         Feature Number         Distribution Medium
 
OS/390              5892                   3480 tape cartridge
OS/390              6747                   4-mm cartridge

Users of IMS V8 Recovery Level Tracking must select one of the following supply features:

Environment         Feature Number         Distribution Medium
 
OS/390              5950                   3480 tape cartridge
OS/390              6751                   4-mm cartridge

Users of IMS V8 Systems Services Optional Source must select one of the following features:

Environment         Feature Number         Distribution Medium
 
OS/390              5989                   3480 tape cartridge
OS/390              6754                   4-mm cartridge

Users of IMS V8 Transaction Manager must select one of the following supply features:

Environment         Feature Number         Distribution Medium
 
OS/390              5963                   3480 tape cartridge
OS/390              6752                   4-mm cartridge

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)
 
Satellite Electronic Delivery                       3450
 
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 Delivery and Fulfillment (SDF) receives the order. SDF will then ship the order via overnight air transportation.

Optional Machine-Readable Material: To order, select the feature number for the desired distribution medium:

                                    Feature          Distribution
Environment                         Number           Medium
 
IMS V8 Database Manager             5976             3480 cartridge
  (DB OPTSRC)
IMS V8 Database Manager             6753             4-mm tape
  (DB OPTSRC)
IMS V8 System Services              5989             3480 cartridge
  (SV OPTSRC)
IMS V8 Transaction Manager          6754             4-mm tape
  (SV OPTSRC)

Unlicensed Documentation: A memo, a program directory, and one copy of the following publications are supplied automatically with the basic machine-readable material:

                                                            Order
Title                                                       Number
 
Installation Volume 1: Installation and                     GC27-1297
  Verification
Installation Volume 2: System Definition                    GC27-1298
  and Tailoring
Licensed Product Kit (CD-ROM)                               LK3T-7092
 
Licensed Programming Specifications                         GC27-1299
Release Planning Guide                                      GC27-1305

The following publications will be available at product availability and are separately orderable:

                                              Order         Feature
Title                                         Number        Number
 
Installation Volume 1:                        GC27-1297     8286
 Installation and Verification
Installation Volume 2: System                 GC27-1298     8287
 Definition and Tailoring
Licensed Product Kit (CD-ROM)                 LK3T-7092     8285
Licensed Programming                          GC27-1299     8279
 Specifications
Licensed Hardcopy and Softcopy                LBOF-7780     8277
 Library
Release Planning Guide                        GC27-1305     8288
Administration Guide:                         SC27-1283     8276
 Database Manager
Administration Guide: System                  SC27-1284     8272
Administration Guide:                         SC27-1285     8198
 Transaction Manager
Application Programming:                      SC27-1286     8235
 Database Manager
Application Programming:                      SC27-1287     8199
 Design Guide
Application Programming:                      SC27-1288     8233
 EXEC DLI Commands for CICS
 and IMS
Application Programming:                      SC27-1289     8269
 Transaction Manager
Command Reference                             SC27-1291     8232
Customization Guide                           SC27-1294     8274
Database Recovery Control                     SC27-1295     8197
 (DBRC)
Diagnosis Guide and Reference                 LY37-3742     8268
Failure Analysis Structure                    LY37-3743     8238
 Tables for Dump Analysis
 (FAST)
Master Index and Glossary                     SC27-1300     8275
Messages and Codes Vol. 1                     GC27-1301     8273
Messages and Codes Vol. 2                     GC27-1302     8271
Operations Guide                              SC27-1304     8239
Open Transaction Manager                      SC27-1303     8236
 Access Guide
Summary of Operator                           SC27-1307     8234
 Commands
Unlicensed Hardcopy Library                   SBOF-7781     8278
Utilities Reference: Database                 SC27-1308     8270
 and Transaction Manager
Utilities Reference: System                   SC27-1309     8237

To obtain the basic publications shipped with the product, specify the 5xxx feature number.

Additional copies of unlicensed publications will be available for a fee at general availability. These copies can be ordered from your IBM service representative, or by direct order, or via the Publication Notification System (PNS). Go to the IBMLink™ Web site at:

Select your geographical area and select PNS.

Alternatively, go to the Web site at:

Publications with an 8xxx feature number are available for a fee.

All of the unlicensed publications can be ordered using one bill of forms number, SBOF-7781.

Access to the licensed documentation requires an IMS Version 8 license. All of the licensed and unlicensed publications can be ordered using one bill of forms number LBOF-7780. This also includes the softcopy product kit, LK3T-7092. 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 product availability. To order, contact your IBM representative. All IMS V8 licensed publications are available for a fee. Use the 8xxx feature number to order.

                                              Order         Feature
Title                                         Number        Number
 
Diagnosis Guide and Reference                 LY37-3742     8268
Failure Analysis Structure Tables             LY37-3743     8238
 (FAST) for Dump Analysis

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.

Customized Offerings

Most product media is shipped only via Customized Offerings (that is, CBPDO, ServerPac, Systempac®). Noncustomized items (CDs, diskettes, source media, media kits) will continue to be shipped via the stand-alone product.

Terms and Conditions

Agreement: IBM Customer Agreement

Variable Charges Apply: No

Indexed Monthly License Charge (IMLC) Applies: No

Location License Applies: No

Use Limitation Applies: No

Educational Allowance Available: Yes, a 15% education allowance applies to qualified education institution customers.

Volume Orders: Not applicable

Replaced Programs           Replacement Programs
Program      Program        Program       Program
Number       Name           Number        Name
 
5695-176     IMS V5         5655-C56      IMS V8
5655-158     IMS V6         5655-C56      IMS V8
5655-B01     IMS V7         5655-C56      IMS V8
5655-C56     IMS V8         Follow-on     if any

Warranty Applies: Yes

Licensed Program Materials Availability

  • Restricted Materials of IBM: None
  • Nonrestricted Source Materials: None
  • Object Code Only (OCO): All

Testing Period: Two months (Basic license only)

Program Services/Support Line

  • Support Center Applies: Yes. Access is available through the IBM Support Center.
  • Available until Discontinued: 12 months' written notice.
  • APAR Mailing Address:

      IBM Corporation
      555 Bailey Avenue
      San Jose, CA 95141

IBM Operational Support Services — Support Line: Yes

Prices

Contact your IBM representative for charges information for this announcement.

Order Now

 Use Priority/Reference Code: YE001
 
 Phone:     800-IBM-CALL
 Fax:       800-2IBM-FAX
 Internet:  ibm_direct@vnet.ibm.com
 Mail:      IBM Atlanta Sales Center
            Dept. YE001
            P.O. Box 2690
            Atlanta, GA  30301-2690

You can also contact your local IBM Business Partner or IBM representative. To identify them, call 800-IBM-4YOU.

Note: Shipments will begin after the planned availability date.

Trademarks

 
The e-business logo, IMS, System/370, FICON, zSeries, z/OS, DFSMSdss, MVS, DFS, IBMLink, and z/Architecture are trademarks of International Business Machines Corporation in the United States or other countries or both.
 
Parallel Sysplex, OS/390, VTAM, ESCON, Sysplex Timer, DB2, RACF, CICS, WebSphere, VisualAge, CICS/ESA, S/390, Systempac, and Multiprise are registered trademarks of International Business Machines Corporation in the United States or other countries or both.
 
Java is a trademark of Sun Microsystems, Inc.
 
UNIX is a registered trademark of the Open Company in the United States and other countries.
 
Other company, product, and service names may be trademarks or service marks of others.