Feedback
IBM United States
Software Announcement 201-296
October 16, 2001

IBM Information Management System Version 8 — Leading the Marketplace in Information Integration, Availability, and Management

 ENUS201-296.PDF (68KB)


At a Glance

IBM Information Management System 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, concurrent 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, concurrent online change for the sysplex, and easier systems generation

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 Database Manager (IMS DB) and IMS Transaction Manager (IMS TM) 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/capacity
  • Superior integrity
  • Continuously available database solutions for IMS TM and CICS® users

In addition, simplified access to new and existing IMS applications and data, and enabling Internet access, is also supported with new or recently enhanced IBM products (refer to Description section for details).

Improved systems/data management and enhanced performance/availability are also supported with IMS tools (refer to Description section for details).

IBM's robust portfolio of IMS tools and utilities helps users manage and gain the best performance from IMS. To learn more about IBM's IMS products and tools, visit the Web at:

Planned Availability Date

  • March 1, 2002, is the IMS V8 (5655-C56) Quality Partnership Program (QPP) start date. IBM plans to ship IMS V8 to customers already selected as participants in the QPP process. Refer to Marketing Announcement 392-061 , dated March 17, 1992, for information regarding the QPP process.
  • General availability of IMS V8 will be announced at a later date.

Description

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/capacity
  • Superior integrity
  • Continuously available database solutions for IMS TM and CICS® users

In addition, simplified access to new and existing IMS applications and data, and enabling Internet access, is also supported with the following new or recently enhanced IBM products:

  • z/OS™ Version 1, Release 2 (5694-A01)
  • IMS Connect Version 1, Release 2 (5655-E51)
  • VisualAge® Java™ Enterprise Edition Version 4 (5724-B14)
  • IBM Developer Kit for OS/390®, Java2 Technology Edition (5655-D35)
  • IMS DataPropagator™ Version 3, Release 1 (5655-E52)
  • CICS Transaction Server for z/OS Version 2 (5697-E93)
  • DB2® UDB for z/OS and OS/390 Version 7 (5675-DB2)

Improved systems/data management and enhanced performance/availability are also supported with the following IMS tools:

  • IMS High Performance Change Accumulation Version 1, Release 1 (5655-F59)
  • IMS Network Compression Facility for z/OS (5655-E19)
  • IMS Fast Path Basic Tools for z/OS, Version 1, Release 2 (5655-E30)
  • IMS Extended Terminal Option for z/OS, Version 2, Release 2 (5655-E12)
  • IMS Parallel Reorganization Version 2, Release 1 (5655-F74)

IBM's robust portfolio of IMS tools and utilities helps users manage and gain the best performance from IMS. To learn more about IBM's IMS products and tools, visit the Web at:

IMS V8 Database Manager Enhancements

Availability/Recovery Items

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 XRC (eXtended Remote Copy) 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, you must 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.
  • 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/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 supported 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 V3R1 product, which provides asynchronous, near real-time IMS-to-DB2 propagation by taking advantage of the asynchronous messaging function of the 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.

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 Database Recovery Control (DBRC) Facility and in a CFRM policy. It allows for the automatic switching of modes when a loss of connectivity, a structure failure, or a Coupling Facility failure occurs in one of the VSO structure instances.

Performance/Capacity Items

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 Data Entry Databases. 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 16 M line. This done by moving system Program Status Tables and code paths from local to above the 16 M line.

Manageability

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.

Single Image Operations Manager

  • The new Operations Manager 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.

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.

Application Development

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.

Java Enhancements

  • Java Standards Enhancements support 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 aggregate functions (MIN, MAX, and so on) and scalars.
  • JDBC Access to IMS DB Data provides access from WebSphere™ Application Server, CICS Transaction Server, and DB2 Stored Procedures environments as well as from IMS TM applications. This support is also being provided for IMS V7 through the service process.

IMS V8 Transaction Manager Enhancements

Availability/Recovery/Capacity Items

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/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.

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.

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 with 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 Coupling Facility failure, structure failure, or loss of connectivity. This support is also being provided for IMS V7 through the service process.

Performance/Capacity Enhancements

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 Coupling Facility. IMS customers require reliable, high bandwidth, host-to-host communications support between IMS systems. This is the role of the IMS Multiple Systems Coupling Facility.

    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 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 16 M line. This is done by moving system Program Status Tables and code paths from local to above the 16 M line.

Manageability

Sysplex Wide Resource Manager

  • The new Resource Manager 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 enforce 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.

Single Image Operations Manager

  • The new Operations Manager 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 IMS Sysplex from a single console.

    A SPOC application program is also provided to help manage a group of IMSs in an IMS 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. The result is less complexity in managing multiple IMSs in a sysplex environment.

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.

Application Development

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.

Java and XML Enhancements

  • Java Standards Enhancements support 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 aggregate functions (MIN, MAX, and so on) and scalars.
  • 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 is also being provided on IMS V7 through the service process.
  • XML Support of IMS TM Messages sends and receives IMS TM messages as XML documents.

Euro Currency

This program is not impacted by euro currency.

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.

Trademarks

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

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 G6 processor or IBM 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.

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 10.

Fast Path Virtual Storage Option (VSO) Systems Managed Rebuild requires Coupling Facility level 9. Auto altering of VSO structure requires Coupling Facility level 9. System Managed Duplexing of VSO structures requires Coupling Facility level 10, 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-AQ1) 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 is required for IMS MSC FICON CTC support.

z/OS Version 1 Release 2 is required for Shared Queues/EMH Coupling Facility duplexing support and for system-managed duplexing of VSO 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 and Coordinated Online Change.

To take full advantage of Coordinated Online Recovery, Sysplex Terminal Management, Single Image Operations Manager, and/or Sysplex Wide Resource Management, IMS V8 should be on all the sysplex systems involved.

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

IMS Java application support requires:

  • 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.

JDBC access to IMS DB for DB2 Stored Procedures requires DB2 UDB for z/OS and OS/390, Version 7 (5675-DB2).

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 z/OS V4.0.1 and additional WebSphere Application Server z/OS Connection Management support.

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

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 V8 TM can be connected via Intersystem Communications (ISC) to the following: IMS V8, IMS V7 (5655-B01), IMS V6 (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.

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

Compatibility: IMS V8 is upwardly compatible from previous versions/releases, allowing existing applications and data to be used without change. Migration/coexistence support is provided for IMS V6 and V7 with V8.

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), or Program Routing (DFSCMPR0). Customers using these exits need to migrate to the new exit.

IMS V7 is 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.

Performance Considerations

IMS Version 8 Enterprise Transaction and Database Servers: IMS V8 provides High Availability Database (HALDB) support, which removes the current DL/I database size limitations — 8 GB for OSAM and 4 GB for VSAM databases — by allowing partitions and thus much larger DL/I databases.

Online Recovery Service (ORS) has made faster recovery for shared databases a reality by concurrently reading log data sets, enabling simultaneous recovery of multiple DBDSs and area recovery.

V8 IMS Monitor extends the current performance monitoring to include Fast Path DEDBs, MSDBs, EMH Queues, BALG, and IFP regions.

CQS enhancements support multiple IMS systems sharing a CQS address space in a recovery situation, thus reducing system resource requirements.

More below-the-line 16 M Common Storage Area usage is made available by moving modules and control blocks above the 16 M line.

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 Stategy 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 16 M
  • 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

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 will be available by the dates indicated. To order, contact your IBM representative.

                                  Order               Availability
Title                             Number              Date
 
IMS Version 8 Fact Sheet          GC27-1517           October 2001
IMS Version 8 Release             GC27-1305           March 2002
 Planning Guide

Ordering instructions and order processing availability will be communicated when IBM announces general availability of this product.

Terms and Conditions

Licensing: IBM Customer Agreement

Variable Charges Apply: No

Parallel Sysplex License Charge (PSLC): The Parallel Sysplex License Charge applies.

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

Version-To-Version Upgrade Credits Apply

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)

Satisfaction Guarantee: Two months for basic licenses. Starts 10 days after IBM ships, or on the day a non-DSLO additional license is authorized.

Program Services

  • 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

Trademarks

 
IMS, System/370, FICON, MVS, and DFS are trademarks of International Business Machines Corporation in the United States or other countries or both.
 
OS/390, VTAM, ESCON, Sysplex Timer, DB2, RACF, Parallel Sysplex, 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.
 
Other company, product, and service names may be trademarks or service marks of others.