IBM United States
Software Announcement 201-060
March 13, 2001

IBM CICS Transaction Server for z/OS Version 2 Brings e-business Enhancements and Support for Enterprise JavaBeans Technology

 ENUS201-060.PDF (205KB)

(Corrected on May 15, 2001)

Feature numbers were changed in the Supplementary Data Area section.

(Corrected on March 22, 2001)

Change made in the text under the heading Enhancements to CICS Exploitation of TCP/IP Services.

At a Glance

CICS Transaction Server for z/OS Version 2 brings major enhancements in support of e-business to CICS on the OS/390 and z/OS platforms — the most powerful and flexible e-business server in the industry. These include:

  • Support for the industry-standard Enterprise JavaBeans (EJB) architecture, enabling CICS to act as an EJB server
  • Facilities for the generation of new EJB applications, or for the reuse or incorporation of existing applications and data in an EJB solution
  • Enhancements to the facilities for network connectivity in support of e-business enablement, and to Java™ programming under CICS
  • Extensions to facilities for applications based on procedural programming models
  • Significant extensions to CICSPlex SM

Also announced are enhancements to CICS Transaction Server for OS/390 Version 1 Release 3.

For ordering, contact:

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

Overview

CICS® Transaction Server for z/OS Version 2 (CICS TS V2) delivers major enhancements that strengthen its support for e-business applications. It provides a major new function that supports industry-standard EJB technology: CICS TS V2 is an EJB server supporting the EJB 1.1 programming model. It also provides a major range of functions available for applications written in other programming styles.

The support for enterprise beans in CICS TS V2 includes exploitation of a new, optimized JVM, enhanced CORBA function, and enhanced CICSPlex® SM functions including workload management. Other facilities available to enterprise beans are JDBC/SQLJ access to DB2® data, JCICS access to VSAM data, extensions to JCICS, and the CICS Connector for CICS TS, enabling interoperability between enterprise beans and applications and data using other programming models.

Additional enhancements are provided in a wide range of areas. Enhancements to Web enablement include support for external call interface (ECI) over TCP/IP. Functions to aid efficient application development include an enhanced 3270 bridge, an integrated CICS translator for use with COBOL and PL/I, and enhancements to file control function shipping. Improvements to connectivity include support for VTAM® LU alias facility. Enhancements in the area of availability include sign-on retention for persistent sessions, support for system-managed rebuild of coupling facility structures, automatic restart of CICS data-sharing servers, and CICSPlex SM workload management of 3270 bridge. Significant usability enhancements are provided by changes to the CICSPlex SM Web user interface.

These new functions are staged through Release 1 and Release 2. CICS TS V2.1 is targeted specifically at early adopters of EJB technology. CICS TS V2.2 is the next release recommended for all CICS customers, for deployment in large-scale production. It delivers a range of functions of major value to all.

Also announced are functional enhancements to the current product, CICS Transaction Server for OS/390® Version 1 Release 3.

Key Prerequisites

For CICS Transaction Server for z/OS Version 2, the following is required:

  • For Release 1, OS/390 Version 2 Release 8, or later.
  • For Release 2, OS/390 Version 2 Release 10, or later.

Planned Availability Dates

  • Release 1: March 30, 2001
  • Release 2: A Beta Program will begin in or before September 2001

Description

CICS Transaction Server for z/OS Version 2 (CICS TS V2) is the latest version of IBM's CICS transaction management product on the OS/390 and z/OS platforms. CICS TS V2 brings major enhancements supporting the role of CICS and CICS applications in e-business. These enhancements include the addition to CICS, with its proven and accepted strengths of integrity and scalability, of support for the Enterprise JavaBeans (EJB) 1.1 programming model. This is provided with a full range of facilities, including CICSPlex SM workload management, stand-alone tools for development and deployment, debugging support, and complementary run-time facilities including access to DB2 data using JDBC/SQLJ, and to VSAM using JCICS. Also provided are enhancements to Java programming under CICS that exploit a new, performance-optimized Java Virtual Machine (known as the persistent, reusable JVM), and enhanced CORBA support for Java programs.

CICS TS V2 also provides a range of enhancements to network connectivity in support of e-business enablement. These include support for outbound IIOP, enhanced systems management, including connection optimization, of both IIOP and HTTP connections and, for IIOP only, support for persistent sockets and asynchronous receive.

Also delivered by CICS TS V2 are important extensions to support for procedural programming, improved application availability, ECI over TCP/IP, and extensions to JCICS. Enhancements to CICSPlex SM base functions, workload management, and its Web user interface are incorporated.

CICS applications can include components built in different programming styles. Their interoperability is simplified by the provision of the CICS Connector for CICS TS, that enables enterprise beans to invoke procedural components using code that can be generated automatically by VisualAge® for Java.

This announcement describes both Release 1 and Release 2 of CICS Transaction Server for z/OS Version 2. Together they provide a staged delivery of the new functions.

CICS Transaction Server for z/OS Version 2 Release 1: This initial delivery of CICS TS V2 is made available for those customers who want to get ahead with testing, application development, proof of concept, or piloting with Enterprise JavaBeans technology.

Key features of the CICS TS V2.1 implementation of Java 2 Platform, Enterprise Edition (J2EE) technology are the support for multiple independent JVMs within a CICS region, and support for a new EJB container. In CICS TS V2.1, each Java application runs in its own JVM, isolated from other applications, and can call procedural applications without compromising this isolation. CICS maintains a pool of JVMs and reinitializes each JVM after the execution of a transaction, assuring the integrity of subsequent transactions. It exploits the selective reset capabilities of the persistent, reusable JVM to ensure that each JVM is reinitialized as efficiently as possible. In addition, CICS TS V2.1 supports a new EJB container derived from WebSphere™ Application Server. This facilitates bytecode portability of applicable enterprise beans (including container-specific classes) developed with WebSphere for execution under CICS. The EJB container is supported by development tools which enable the deployment of enterprise beans into the CICS environment.

To assist in providing high availability and continuous operations, CICS TS V2.1 provides a logical EJB server made up of multiple listeners and application-owning regions (AORs). EJB execution is workload balanced within this logical server via CICSPlex SM's workload manager.

Enterprise beans have facilities which give them simple access to existing or new applications and data, including those which use other programming styles. They can easily access CICS VSAM files via supplied JCICS classes. JDBC/SQLJ support enables access to DB2 data. The CICS Connector for CICS TS is provided to allow easy interoperation between enterprise beans and any other applications or data.

CICS TS V2.1 also includes other important enhancements. Among these are functions to improve ease of application programming, in particular an integrated CICS translator for use with COBOL and PL/I compilers, local/remote transparency for function shipped file requests, and lifting of the requirement to use RLS when data sharing a BTS repository file. Availability is improved by automatic restart of CICS data-sharing servers. Connectivity is enhanced by support for VTAM LU alias facility. Usability is improved by modifications to the CICSPlex SM Web user interface.

It is recommended that CICS TS V2.1 should be licensed only by customers who already have experience in the use of CICS TS V1.3 and its Java capabilities.

Note that CICS TS V2.1 is announced with a limited duration of program services, which emphasizes the role for which this release is recommended.

CICS Transaction Server for z/OS Version 2 Release 2: CICS TS V2.2 is intended for high-volume production, and is the replacement for CICS TS V1.3 and earlier releases of CICS. It is the path for future growth for all CICS customers. It provides the evolutionary path for those who already use CICS applications and wish to enhance their installations without moving to EJB technology. For those wishing to exploit EJB, CICS TS V2.2 offers a unique platform for the new technology in an environment with the robustness, integrity, and scalability which are hallmarks of CICS.

The limited duration that applies to the program services of Release 1 does not apply with this release.

CICS TS V2.2 brings CICS support for EJB technology to high-volume production. A full security implementation is delivered, meeting the EJB 1.1 specification. Enhanced levels of the Enterprise Java APIs are supported.

Moreover, important enhancements are made to the robustness, scalability, and performance of the EJB function. These enhancements include changes to the support for the persistent, reusable JVM, so that it can exploit CICS storage management and recovery mechanisms. These changes will both improve performance and increase the robustness under certain stress conditions. Scalability is improved by modifying the use of storage and enabling a larger pool of JVMs, so allowing a larger number of concurrent EJB tasks in a CICS region. Sharing of classes between multiple JVMs in a region reduces storage usage and improves performance whenever a JVM has to be reinitialized. Improvements to serviceability include, for example, generating trace information at more trace points.

This release also brings many other new functions. These include support for ECI client applications communicating over native TCP/IP, and an enhanced 3270 bridge that can be easily invoked by ECI, EXCI, DPL, or LINK. Calls to the 3270 bridge can be workload managed by CICSPlex SM workload manager. An agent for management of CICS on the Windows NT™ platform is provided. Other enhancements are provided to further improve application availability. These include support for sign-on retention for persistent sessions, and support for system-managed rebuild of the coupling facility structures used by the CICS datasharing servers. Improvements are provided to performance when working with DB2, and a group attach facility is provided. Enhancements are provided to function shipping of remote file requests.

The general availability date for CICS TS V2.2 will be given in a later announcement. That announcement will also include more detailed information about CICS TS V2.2.

CICS Transaction Server for OS/390 Version 1 Release 3: Before the general availability of CICS TS V2.2, it is recommended that customers using CICS/ESA® V4.1 or earlier in a production environment migrate to CICS TS V1.3, which continues as the latest and most powerful CICS server for general purpose production.

Enhancements have been made to CICS Transaction Server for OS/390 Version 1 Release 3. More information on these enhancements is given later in this announcement.

Euro Currency

This program is EuroReady.

For more information on the implications of the euro, visit the IBM euro Web site at:

EuroReady Products: IBM considers an IBM product to be EuroReady if the product, when used in accordance with its associated documentation, is capable of correctly processing monetary data in the euro denomination and of respecting the euro currency formatting conventions (including the euro sign). This assumes that all other products (for example, hardware, software, and firmware) that are used with this product are also EuroReady. IBM hardware products that are EuroReady may or may not have an engraved euro sign key on their keyboards.

Currently, EuroReady status applies primarily to IBM products specific to the EMU countries. Products that are not specific to these countries are deemed to be "not ready" for euro unless otherwise stated in the product's country-specific specifications.

IBM Hardware Ready: IBM supplies certain IBM products which include third party software (pre-loaded or not) and/or third party attached hardware. In these instances, IBM is not in a position to assert that these third party products are, in themselves, EuroReady.

Therefore, such IBM products will be designated as Hardware ready.

EuroReady Solutions

IBM considers a solution to be EuroReady when the solution providers have:

  • Analyzed the euro requirements, including the need to comply with relevant EC rules
  • Built in appropriate function

and can clearly demonstrate this by:

  • Detailing euro related requirements
  • Describing how these will be implemented in the solution
  • Declaring when the implementation will be generally available

The euro capabilities of a EuroReady solution will be clearly identified as features of the Solution specification as described in the contracts document.

Product Positioning

Many enterprises see significant advantages in building upon their core investment in CICS skills and applications, and extending that investment to provide the basis for their new e-business solutions.

CICS support of Java has evolved through a number of stages. With CICS TS V2, the next step, as requested by CICS's customers, is support of Enterprise JavaBeans. The benefits of EJB technology complement the benefits of the CICS environment. EJBs hide the complexities of transactions, concurrency, and security from the programmer; they allow configuration at deployment time; and they support the scalability and robustness needs of real e-business. The EJB model exploits the strengths of CICS via open Java Enterprise APIs.

By supporting EJBs, CICS enables the seamless inclusion of an enterprise's investment in CICS into the IBM Application Framework for e-business. New server-side business logic can be built to take advantage of existing (and new) procedural CICS applications. Enterprises with a strong investment in CICS skills can evolve them at their own pace into Application Framework skills. CICS can act as a peer application server within solutions which are architected to the Application Framework and are implemented using WebSphere. The recommended direction to evolve business logic running in CICS into e-business solutions is using EJBs.

CICS supports those parts of the Application Framework and J2EE which fit naturally with its role as a server for core transactional business logic. It enables re-use of existing development and operational skills. CICS provides a run-time environment optimized for business logic written as EJBs which can run alongside, and interoperate with, business logic written in languages such as COBOL. Both EJB applications and COBOL applications can access existing (and new) DB2, IMS™ DB, and VSAM data concurrently, and with complete integrity. By allowing new EJBs to run simultaneously in the same managed run-time environment as, for example, traditional 3270-based applications, CICS enables the same operational personnel to support all styles of application.

CICS TS V2 does not provide support for entity beans. EJB applications running under CICS may, however, use the support for entity beans provided by other products, such as WebSphere Application Server Version 4 for z/OS and OS/390. As an EJB server, CICS TS V2 provides an appropriate set of container services, supporting the EJB 1.1 specification, which means that it can host any session bean that uses the EJB 1.1 APIs.

In summary, the role of CICS TS V2 in an EJB solution on OS/390 or z/OS is:

  • To enable the efficient and optimized re-use and extension of existing CICS applications and business logic
  • To enable enterprises with a strong investment in CICS skills and infrastructure to easily embrace EJBs and the Application Framework, by building on those CICS skills
  • To support mixed application types and workloads within a single CICS system
  • To enable use of existing DB2, IMS DB, and VSAM data from EJB applications

Statement of Direction

IBM plans to enhance CICS VSAM Recovery (CICSVR) as a part of continuing customer support, addressing a number of customer-requested enhancements and introducing new functions which include:

  • Batch Logging for VSAM data. Changes made to VSAM data sets by batch applications will now be written to a z/OS or OS/390 logstream. This additional capability expands the scope of CICSVR from just a CICS-related data recovery tool to a general VSAM data recovery tool.
  • Change accumulation processing. Forward recovery log records can now be consolidated into a change accumulation data set. CICSVR can use the change accumulation data set to improve the performance of the forward recovery.

The new release of CICSVR is intended to be packaged with CICS TS V2 for optional, convenient, customer licensing and installation; however, to use it, a separate license for CICSVR will be required. The new release of CICSVR will also be offered as a separately orderable product. OS/390 V2R6, or later, will be required for installation of this enhanced CICSVR product, but OS/390 V2R10, or later, will be required to take advantage of new CICSVR function being introduced with this new product level.

Statements of Direction provide insight into IBM plans and directions. All information being released represents IBM's current intent, is subject to change or withdrawal without notice, and represents only goals and objectives. Any reliance on this Statement of Direction is at the relying party's sole risk and will not create any liability or obligation for IBM.

Hardware and Software Support Services

SmoothStart™/Installation Services

jStart program: IBM has created the jStart program to help customers gain the critical experience they need using emerging and established technologies, including XML, Java, and Enterprise JavaBeans. The jStart program helps customers get started on an application through a unique partnership that brings the right combination of tools, skills, and resources together for the rapid deployment of production applications. Behind the jStart program is the Java Component Services (JCS) team which is a specialized services unit missioned to support IBM's e-business strategy by providing Java development services to customers. The JCS team are experts in Java technology, and can provide a wealth of technical skills to help in the most demanding projects involving Java components, Servlets, Enterprise JavaBeans, JSPs, and other emerging technologies.

For more information, visit the Java technology zone at:

or e-mail:

    jStart@us.ibm.com

IBM Services for CICS Web Enablement: IBM can provide on-site services to assist you with Web enabling your existing or new CICS Applications. These services can include an analysis of your organization's environment and infrastructure, business requirements for e-business, general Internet strategy, and candidate CICS applications for Web enablement. We can also assist you with the installation and implementation of the most appropriate CICS Web Enablement method that matches your e-business requirements.

IBM Migration Services for CICS Transaction Server

IBM Global Services has the capability to provide on-site assistance from our CICS services specialist to work with your technical staff to produce a CICS Transaction Server for z/OS Version 2 Migration Plan that can include the following:

  • Migration of CICS journals to MVS™ Logger
  • Changes in startup, shutdown, and recovery operations of CICS regions
  • Evaluation of CICS resource definitions
  • Assessing applications that use the CICS Web Support
  • Evaluating connectivity between CICS Regions
  • Consideration of CICS environment use of DB2 and DL/1 resources

Installation and implementation of CICS Transaction Server for z/OS Version 2 is provided in accordance with the CICS Transaction Server for z/OS Version 2 Migration Plan.

IBM Installation Services for CICSPlex SM

IBM Global Services has the capability to provide on-site assistance from our CICS services specialist to work with your technical staff to produce a CICSPlex SM Installation Plan that can include the following:

  • CICS Transaction Affinities
  • CICS Region configuration design and implementation of improved CICS and CMAS JCL structure
  • Implementation of Dynamic Transaction Routing and Dynamic Program Link Routing
  • Implementation of the CICSPlex SM Web user interface
  • Demonstrate use of CICSPlex SM API
  • Exploitation of CICSPlex SM Single Point of Control
  • Exploitation of CICSPlex SM Business Application Services
  • Exploitation of CICSPlex SM Real Time Analysis
  • Implementation of VSAM Record Level Sharing

Installation and implementation of CICSPlex SM is provided in accordance with the CICSPlex SM Installation Plan.

For general information on IBM Global Services, go to:

For services for CICS, go to:

Reference Information

For information on WebSphere Application Server V4.0 for z/OS and OS/390, refer to Software Announcement 201-058 , dated March 13, 2001.

For information on MQSeries® Integrator Agent for CICS Transaction Server, refer to Software Announcement 201-059 , dated March 13, 2001.

CICS Web Pages

For up-to-date information on CICS, refer to:

For the latest information on CICS TS V2, refer to:

Trademarks

 
WebSphere, IMS, SmoothStart, and MVS are trademarks of International Business Machines Corporation in the United States or other countries or both.
 
CICS, CICSPlex, DB2, VTAM, OS/390, VisualAge, CICS/ESA, and MQSeries are registered trademarks of International Business Machines Corporation in the United States or other countries or both.
 
Windows NT is a 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.

New Functions in CICS Transaction Server for z/OS Version 2

The following description applies to both CICS® Transaction Server for z/OS Version 2 Release 1 and Release 2. Where a function is only in Release 2, this is indicated.

Enterprise JavaBeans

There are many advantages to the use of EJB technology. It provides the benefit common to all Java™ products of easy portability between different platforms, and further, it allows portability between different EJB-compliant transaction management products (EJB servers). By automating the infrastructure services, EJB technology allows the programmer to concentrate solely on business logic, without any need to consider transactional or environmental factors, thus increasing programmer productivity. Another benefit of EJB architecture is that it allows customization simply by altering attributes in the deployment of an enterprise bean — customization does not require alteration to the source code of the program. EJB architecture is scalable, allowing enterprise beans, once written, to be migrated to any different small-scale or large-scale environment.

The use of EJB technology, particularly as implemented in CICS TS V2.2, will deliver EJB functionality with the power, scalability, and reliability that CICS has over many years developed to an unrivalled degree. CICS TS V2 also allows an EJB implementation to incorporate and reuse existing CICS applications, written in COBOL or any of the other CICS-supported languages.

All functions provided by CICS TS V2 for the support of EJB are in accordance with the Enterprise JavaBeans architecture, Version 1.1, as defined by Sun Microsystems, Inc. This specification may be viewed at:

The details of the implementation are unique to the particular product that is providing the EJB support, in this case CICS TS V2. Many of these details are internal, and concern the mapping of the functions defined by the EJB architecture to the existing tried and tested transactional functionality of CICS. Unique functions of the implementation of the EJB support that are externally visible are those which apply to ways in which existing CICS applications and data may be used in an EJB environment. CICS TS V2 provides extensive facilities for the integration of such existing functions with new applications developed using the EJB programming model.

CICS TS V2 supports the Enterprise JavaBeans architecture, Version 1.1. The only exceptions are that it does not support entity beans, and that CICS TS V2.1 does not have a full implementation of the EJB 1.1 security specification. Its support for the EJB specification means that CICS TS V2 can act as an EJB server (sometimes known as Enterprise Java Server (EJS), or Enterprise Server for Java (ESJ)). An EJB server supports the execution of an enterprise bean , which is a reusable software server component, written in Java to the Enterprise JavaBeans specification. (This is similar to the way in which, in a non-transactional environment, a JavaBean is a reusable software component, written in Java, which is intended for use in a desktop or client application.)

An enterprise bean is a transactional application program, or application program component, written in Java to the EJB specification. This contrasts with an application program written, for example, in COBOL or C, to the CICS programming model.

The EJB server, in this case CICS TS V2, contains a standard set of components that provide a standard set of services, defined by the EJB specification, for the support of the enterprise beans. These services include support for the Remote Method Invocation (RMI) interface that enterprise beans use for communication, in the case of CICS TS V2 using the Internet InterORB Protocol (IIOP); management services, which are provided by an EJB container; a distributed transaction management service; and security services.

The EJB container is a part of any EJB server. At run-time, the EJB container creates and manages enterprise bean instances, and provides the services required by each enterprise bean running in it. Any number of enterprise beans can be deployed into an EJB container. Services provided by the EJB container include:

  • Lifecycle. The enterprise bean does not need to itself manage process allocation, thread management, object activation, or object passivation.
  • State management. The enterprise bean does not need to save or restore conversational object state between method calls.
  • Security. The enterprise bean does not need to authenticate users or check authorization levels. These functions are performed by the container on its behalf. (But note that CICS TS V2.1 does not include a full implementation of EJB security.)
  • Transaction management. Each enterprise bean does not need to specify transaction demarcation code in order to participate in distributed transactions. The EJB container manages the start, enrollment, commitment, and rollback of transactions on its behalf.
  • Persistence. The enterprise bean does not need to store or retrieve persistent data using a database. The EJB container can automatically manage persistent data on its behalf. This applies only to entity beans (not directly supported by CICS TS V2).

The EJB container in CICS TS V2 is derived from WebSphere™ Application Server. The use of this container enables binary portability of applicable enterprise beans developed with WebSphere for execution under CICS.

Enterprise beans are deployed into an EJB server. For this to happen, their execution environment is configured by a CORBASERVER resource definition. This execution environment is known as a CorbaServer.

In the EJB context, any outside user of the services of the enterprise bean is known as a client. Interaction by a Java client with an enterprise bean is handled through two wrapper interfaces which are generated by the container: the home interface and the remote interface . These interfaces are defined as Java Remote Method Invocation (RMI) interfaces, accessed through IIOP.

  • The home interface is the mechanism by which a client identifies the enterprise bean that it wants. The client can create, remove, and (for entity beans only, refer to below) find existing instances of enterprise beans. When an enterprise bean is deployed in an EJB container, the container can register the home interface in a namespace that can be accessed remotely. Using the API of the Java Naming and Directory Interface (JNDI), any client can locate the home interface by name.
  • The remote interface allows a client to access the business methods of the enterprise bean. When a client creates or finds an instance of an enterprise bean, the container returns a remote interface for that instance of the enterprise bean. The remote interface intercepts all business method calls from the client, and inserts whatever transaction, state management, persistence (where applicable), and security services were specified when the enterprise bean was deployed.

The rules defining aspects of a particular enterprise bean are defined by what is called the deployment descriptor , a document written in eXtensible Markup Language (XML). This defines the lifecycle, security, transaction management, and persistence of the enterprise bean.

There are two principal types of enterprise bean: session beans and entity beans .

  • A session bean is created by a client, and normally persists only for the duration of a single conversation or session with the client. (Thus, it is comparable to a pseudo-conversational transaction in conventional CICS.) Its function is typically to perform operations on business data; it may or may not be transactional; and it is not recoverable. If persistence of information is required, then the writer of the session bean must implement appropriate operations in the bean class methods, such as JDBC or SQL calls. A transactional session bean can either manage its own Object Transaction Service (OTS) transactions, or it can use container-managed transactions.

    A session bean can also perform a JCICS link to an existing CICS transaction in COBOL or any other supported language. This allows a session bean to be effectively a wrapper of an existing procedural CICS application. It can also use the CICS Connector for CICS TS, newly introduced in this product, allowing it to communicate by a COMMAREA with a CICS application running in the same or another CICS system. The other CICS system can be any CICS system that supports DPL, such as CICS/ESA® V4.1.

    There are two types of session beans: stateful session beans , and stateless session beans . A stateful session bean is one which has a client-specific conversational state, which it maintains across methods and transactions. A stateless session bean has no client-specific non-transient state.

  • An entity bean is typically an object representation of business data. Typically, the data is maintained in a store such as a database. Unlike session beans, entity beans are relatively long lived: the data normally persists beyond the life of any client instance. An entity bean can be accessed by more than one client at the same time. An entity bean is recoverable: it will survive a crash of the EJB server. It may or may not be transactional, but if it is so, its transactional functions are performed by the container; the entity bean may not manage its own OTS transactions.

    There are two types of persistence management for entity beans: bean-managed persistence and container-managed persistence . In the case of bean-managed persistence, the entity bean implements its own persistence operations, such as JDBC or SQL calls, allowing it to use data stored in any other file or database manager. In the case of container-managed persistence, the writer of the entity bean does not need to have any awareness of the persistence operations.

    Support for entity beans is not provided by CICS TS V2. EJB applications running under CICS may, however, call entity beans hosted by other products, such as WebSphere Application Server Version 4 for z/OS and OS/390.

As a practical alternative to entity beans for management of data with CICS TS V2 in the EJB environment, Data Access Beans may be employed. These enable data to be managed in relational databases that support the Java DataBase Connectivity (JDBC) API, such as DB2® for OS/390®. The Data Access Beans use a common SQL syntax, so they work both on OS/390 and on workstation platforms. In particular, the beans provided as part of VisualAge® for Java professional edition may be used. There are three such beans: Select Bean, Modify Bean, and ProcedureCall Bean. VisualAge for Java includes Smart Guides that make them even easier to use. One of the Smart Guides is an SQL Assist Smart Guide , that allows the visual composition of an SQL statement.

EJB Run-time Functions

Java Naming and Directory Interface (JNDI): JNDI is an API defined in the Java programming language that provides directory and naming functionality for Java applications. In CICS TS V2, the JNDI API enables an enterprise bean or other Java program to look up a name or to locate an enterprise bean, local or remote, which, if desired, can then be invoked.

The JNDI API is mapped to an external naming directory server; a suitable JNDI server is a requirement. In the case of CICS TS V2.1, a CORBA Object Services (COS) naming directory server provided by WebSphere Application Server Advanced Edition V3.5 is shipped as a complementary component of the product, to run on a Windows NT™ or Windows™ 2000 machine.

In the case of CICS TS V2.2, support will be added for a Lightweight Directory Access Protocol (LDAP) server. An LDAP server with a CORBA object reference schema is required. The LDAP which is planned to be shipped in z/OS V1R2 meets this requirement, and can provide support across a Parallel Sysplex®.

JDBC: For information concerning JDBC support which has been added to CICS TS V1.3, refer to the section Enhancements to CICS Transaction Server for OS/390 Version 1 Release 3 . The JDBC support for CICS TS V2.1 is provided by the DB2 Server for OS/390 or DB2 Universal Database® Server for OS/390 at a JDBC 1.2 API level. The DB2 support has been upgraded to support the IBM Developer Kit for OS/390, Java 2 Technology Edition, V1.3 environment of CICS TS V2.1.

JDBC Access to IMS™: JDBC access to IMS Version 7 Database Manager (DB) data was initially provided with IMS V7, at its general availability, for Java applications running under control of the IMS Transaction Manager. This support is being extended through the IMS V7 service process to provide JDBC access to IMS V7 DB data from Java applications running under CICS Transaction Server for z/OS Version 2.

The CICS Connector for CICS TS: CICS TS V2 introduces the CICS Connector for CICS TS, providing an option for an enterprise bean to communicate with an existing (non-Java) CICS application typically running under another CICS system. The non-Java program can be written in any supported language. Communication is by means of a COMMAREA to any CICS system which supports DPL, such as CICS/ESA V4.1.

This facility may be used typically to access programs running in a separate region, but it can also be used for programs in the same region of CICS TS V2 as that in which the enterprise bean is running. The mechanism reuses some of the Java classes shipped with the CICS Transaction Gateway. Communication with the remote CICS system is by means of distributed program link (DPL) calls. The function can also be used by an application written in Java that is not an enterprise bean.

This is a powerful technique that allows the creation of enterprise beans in the EJB server which are based on existing CICS application programs. It is a method of integrating existing CICS applications into an installation running enterprise beans. There is no requirement for communication through any other server platform, and the programmer of the enterprise bean does not require an understanding of CICS programming.

The CICS Connector for CICS TS supports the Common Connector Framework (CCF) client interface, an API that provides a standard way for a Java program to interact with an application server such as CICS. The recommended method of creating an enterprise bean that uses the CICS Connector for CICS TS is by means of VisualAge for Java, using its Enterprise Access Builder (EAB). Alternatively, other products that provide similar function may be used.

The CICS Connector for CICS TS is compatible with CICS Transaction Gateway Version 3. Command beans, generated by VisualAge for Java which use the CCF interface provided by CICS Transaction Gateway, can be migrated to run under CICS TS V2.1 and use the CICS Connector for CICS TS. Other beans, which use the underlying Java ECI interface, can also be migrated to CICS TS V2.1.

As compared to the alternative of using the JCICS classes for a similar function, the CICS Connector for CICS TS has advantages: (a) of portability, in that the code can be used from a CICS or non-CICS Java environment; (b) the availability of VisualAge for Java tooling for this function.

EJB Access to Other Resources: Also available to enterprise beans are the facilities of JCICS which enable access to VSAM data and CICS resources. Access to DL/I data is available by a JCICS link or using the CICS Connector for CICS TS, via a program in, for example, COBOL. Refer also to JDBC Access to IMS , above.

CICS Support for the Persistent, Reusable JVM: Support by CICS for the Java Virtual Machine (JVM) was introduced in CICS Transaction Server for OS/390 Version 1 Release 3, enabling CICS application programs to be written in Java, and compiled into bytecode using any standard Java compiler. In CICS TS V2, this support is enhanced to support the IBM Developer Kit for OS/390, Java 2 Technology Edition, V1.3, with a special enhancement. This JVM, with the special enhancement, is known as the persistent, reusable JVM. This enables significant optimizations in terms of a reduction in the cost of initialization for a Java application program. The benefits apply to use of enterprise beans, and also to Java programs that are called from outside CICS by ECI, EXCI, or DPL, or through 3270 datastreams.

Enhancements to CORBA Support: Support for inbound Internet Inter-ORB Protocol (IIOP) requests from CORBA clients to CICS Java applications was introduced in CICS Transaction Server for OS/390 Version 1 Release 3. This support, and the implementation of the Object Request Broker (ORB), have been enhanced in CICS TS V2 to support CORBA 2.1 and IIOP 1.1.

The new functions that have been added are:

  • Support for outbound IIOP. This means that CORBA applications can now act as both client and server.
  • CICS TS V2 method invocations may participate in Object Transaction Service (OTS) distributed transactions. (Note that the OTS term "transaction" is analogous to a distributed unit of work.)
  • Longer values of up to 255 characters are allowed for REQUESTMODEL options MODULE, INTERFACE, and OPERATION.

These new functions provide the necessary infrastructure for enterprise beans to communicate using the Java RMI interface.

EJB Security: When used with non-EJB applications, both CICS TS V2.1 and CICS TS V2.2 have the same security and auditability features as CICS TS V1.3. These include the recently introduced Web certificate auto-registration feature (refer to the description earlier in this announcement). CICS transaction and resource security continue to apply when the CICS API is used, including the JCICS API.

For CICS TS V2.1 used with EJB applications, the Java 2 security policy mechanism is supported, but the implementation of EJB support does not include the full security of the EJB 1.1 specification. Specifically:

  • The getCallerPrincipal method is implemented. It returns a Principal object whose getName method returns the distinguished name of the EJB client. When the client is authenticated with an SSL certificate, the distinguished name is extracted directly from that certificate, otherwise it is generated from a user-replaceable module, DFHEJDNX.
  • The JVM will be controlled by Java 2 security policies that can be customized by the user.
  • However, the security roles in the deployment descriptor will be recognized, but will not be honored. The isCallerInRole method will always return TRUE, and EJB method authorization checks will always succeed.

For CICS TS V2.2 used with EJB applications, a full security solution is provided, meeting the EJB 1.1 specification for security roles. This will use the SAF (System Authorization Facility) interface to exploit services of the SecureWay® Security Server in OS/390 and z/OS (formerly the Resource Access Control Facility (RACF®)). The support provides:

  • Method authorization checks to determine whether a user is in a role that is authorized to execute a given method on an enterprise bean
  • A full implementation of the EJB 1.1 security API, isCallerInRole

In addition to EJB security as described above, CICS TS V2 provides a capability for security authentication of users over IIOP. In CICS TS V2.1, this provides secure interoperability between CICS and other IBM and non-IBM systems using the SSL client authentication protocol. In CICS TS V2.2, it will also provide secure interoperability between CICS and other members of the WebSphere family, using other authentication protocols in addition to SSL client authentication.

CICS EJB Sample: Several EJB sample programs are shipped with CICS TS V2. One of these is an online banking sample. It consists of an HTML form, a Java servlet plus JavaServer Pages, an enterprise bean, DB2 data tables, and two CICS server programs written in COBOL. The sample is started from a Web browser, and displays a form in which the user enters information. This invokes a servlet, which interacts with the enterprise bean. The enterprise bean uses the CCF interface of the CICS Connector for CICS TS to link to the CICS COBOL server programs, which retrieve data from the DB2 database. Information received by the enterprise bean is returned to the servlet, which uses JavaServer Pages to display it at the browser.

This sample requires DB2 Server for OS/390 Version 5.1, or later, and a suitable Web Server, such as the shipped WebSphere Application Server Advanced Edition for Windows NT V3.5.

EJB Support Tools

A Java Archive (JAR) file can contain one or many Java beans, of different sorts, including enterprise beans. Where these Java beans are enterprise beans, it is referred to as an ejb-jar. An ejb-jar file is used to transfer an enterprise bean between the development environment and the test or run-time environment. An ejb-jar is a standard format that provides the declarative information, including the Java classes, the Home and Remote Interfaces, and a deployment descriptor written in XML. When enterprise beans are deployed to CICS, they are in a CICS-deployed JAR file, which means they have generated code specific to CICS TS V2 added to them by an EJB support tool.

Deployment, in the EJB context, means the series of tasks that take an enterprise bean from being Java code in an ejb-jar file, the state in which it may have been created by a developer, to the state of being known to, and runnable in, a particular EJB server, in this case CICS, and is in a CICS-deployed JAR file, and so available if called.

These functions may be carried out by the three CICS tools for EJB technology, described below. The tools all run on Windows NT or Windows 2000, are supplied on a CD-ROM as part of the CICS TS V2.1 product package, and can be installed at the workstation using Installshield.

These tools, running on Windows NT or Windows 2000, require the necessary level of Java Virtual Machine (JVM) — this is the IBM Developer Kit for OS/390, Java 2 Technology Edition, V1.3. If required, this can be downloaded from the Web (refer to the Software Requirements section).

In releases following CICS TS V2.1, changes will be made to this tooling to further simplify and to provide common solutions with the WebSphere platform. These changes may remove the need for some of the tools provided in this release.

The CICS JAR Development Tool for EJB Technology: Enterprise beans for use in CICS TS V2.1, may be generated in a number of ways. They may be written manually by a programmer writing Java source code, using an editor of the programmer's choice, to the EJB 1.1 specification. Typically the resulting code would be in the form of several classes, and would be in a JAR file. Alternatively, they may be written using a tool such as VisualAge for Java, Version 3.5, which, at present, can only produce enterprise beans to the EJB 1.0 specification. These can still be used by this tool. Thirdly, they may be enterprise beans written using a development tool which is EJB 1.1 capable; this can include enterprise beans obtained "off the shelf" from vendors. Alternatively, they may be EJB 1.1 enterprise beans which have already been deployed to CICS, and which you now wish to deploy in an updated version (known as "round-trip deployment").

The CICS JAR Development Tool for EJB Technology uses a graphical user interface and can accept an ejb-jar file containing enterprise beans from any of the above sources. Where the source is code written to the EJB 1.0 specification, it takes the 1.0 level ejb-jar and converts it into a 1.1 level ejb-jar. It then performs two functions:

  1. The tool creates a deployment descriptor for the ejb-jar file; or where the ejb-jar already has a deployment descriptor, it can modify it. The deployment descriptor (written in XML) is a file in the ejb-jar which contains all the tailorable run-time attributes of the enterprise beans, for example, the bean name and the bindings for any resources and references which are used by the enterprise bean. The tool enables the addition, deletion, copying, and editing of the deployment descriptor.

    This function can also be carried out on CICS-deployed JAR files, which applies where they are being taken through the process of round-trip deployment. The tool can, if required, modify the information in the CICS-deployed JAR file to change the manner of its deployment into the CICS server.

  2. The second stage is the code generation stage. This function produces the extra Java classes that provide (a) the interface to the EJB run-time functions in the container, and (b) the RMI/IIOP stub and tie classes, which allow the enterprise bean to be invoked remotely.

    The code generation function is automatically performed by the "Generate" function of the tool. This function is, however, also available for separate use, as the CICS Code Generation Utility, with a command interface and a programming API.

For the remaining part of the deployment process, two alternative tools are available, if required, to assist the user. Which tool is applicable depends on whether deployment is required for testing or for production.

CICS Development Deployment Tool for EJB Technology: This tool allows the application developer to initiate the deployment of the ejb-jar file directly into CICS for unit testing, and with no need for a knowledge of CICS. Its use is only appropriate for the testing of new or modified enterprise beans, which may be applied to a CICS region which has been set up by the CICS system programmer specifically for test, and is distinct from the production regions. The application programmer can then deploy the enterprise beans without intervention from the system programmer, and with no need for CICS resource definitions or system set-up. The tool uses a Web browser interface. The file is transferred via the http protocol to a machine running a copy of WebSphere Application Server Advanced Edition V3.5 for Windows NT. (CD-ROMs of this are included in the package of the product. It may also be used by CICS TS V2.1 as its JNDI COSNaming server; normally the machine used for the Development Deployment Tool would be distinct from the latter.) A servlet running on WebSphere Application Server transfers the ejb-jar directly to the Hierarchical File System (HFS) of the CICS server using FTP. The appropriate resource definitions are generated, using defaults where appropriate, stored in the ejb-jar, and applied to CICS. It is now known as a CICS-deployed JAR file.

CICS Production Deployment Tool for EJB Technology: The CICS Production Deployment Tool works with JAR files that conform to the EJB 1.1 specification and allows the user (typically a systems programmer or system administrator) to edit the environment parameters and JNDI bindings and to create or modify the CICS resource definitions contained within the JAR. This tool uses a Java-based graphical user interface; or, alternatively, it can be run as an off-line utility using a UNIX® System Services command. It can work with an ejb-jar stored on the Windows NT machine in which the tool is running, or it can work with one in the HFS accessible by the CICS server. It can also store its output in either system, subject to this being the same system as that from which the input was read. Its output is a CICS-deployed JAR file. It then generates the DFHCSDUP input stream for installation of the CICS resource definitions into the CICS server, and the BATCHREP input stream for installation into the CICSPlex® SM environment.

Using a Debugger with the JVM: The JVM in CICS supports the Java Platform Debugger Architecture (JPDA), which is the standard debugging mechanism in the Java 2 platform. This architecture provides a set of APIs that allow the attachment of a remote debugger to a JVM. A number of third party debug tools are available that exploit JPDA and can be used to attach to and debug a JVM that is running an enterprise bean, CORBA object, or Java program under CICS.

CICSPlex SM Functions in Support of EJB

CICS Transaction Server for z/OS Version 2 incorporates a new version of CICSPlex System Manager. CICS TS V2.1 contains CICSPlex SM Version 2 Release 1; CICS TS V2.2 contains CICSPlex SM Version 2 Release 2. This new version of CICSPlex SM provides major new functions, many of which are in support of EJB technology.

CICSPlex SM Management of the EJB Server: A range of new and modified functions is provided in CICSPlex SM for its support of the EJB server. These functions are:

  • New operator views for CorbaServers and JAR files. The new views are EJCOSE and EJDJAR, and the new CICSPlex SM actions are PUBLISH, RETRACT, and DISCARD.
  • Modified operator views for transaction and request models.
  • Equivalent changes to the Web user interface for the operator view changes in the previous two points, and for beans.
  • New Business Application Services (BAS) resource definition views for CorbaServers and JAR files, EJCODEF, and EJDJDEF.
  • Modified BAS resource definition views for transactions and request models.
  • Changes to the CICSPlex SM API for the support of CorbaServers, JAR files, and beans.

Workload Management for Enterprise Beans: CICSPlex SM provides dynamic workload balancing of enterprise beans executing in CICS-provided CorbaServers. This extends the distributed routing program model of routing introduced in CICS Transaction Server for OS/390 Version 1 Release 3 to enterprise beans. All existing facilities provided by CICSPlex SM in this context, such as separation and abend avoidance, are provided for enterprise bean invocation. The customer can write a user-replaceable module to customize the routing logic.

In this workload balancing, the roles are:

  • The requester, in which the routing request originates, which, for example, can be external client code invoking the enterprise bean by an IIOP work request, or could be another logical EJB server.
  • The routing region, in which the decision is taken as to where the requested transaction should be run. This is normally a CICS listener region, and it must be running CICS TS V2.
  • The target region, in which the identified transaction is run. It must be running CICS TS V2.

In this context, a CICSplex consists of a number of cloned routing regions and cloned target regions. Each target region may run a number of CorbaServers. Note that this process is compatible with MVS™ TCP/IP connection balancing across multiple listener regions.

Enhancements to Network Connectivity for e-Business Enablement

Some of these enhancements may also be exploited by applications written to the EJB programming model.

Enhancements to CICS Exploitation of TCP/IP Services

Enhancements are included in CICS TS V2.1 that provide improved services to the CICS functions that use the Sockets domain, namely the HTTP and IIOP support:

  • Socket management, which enables you to specify the maximum number of sockets that the CICS sockets domain should have active at one time.
  • Functions that are used by the enhanced CORBA support:
    • Outbound socket support. This allows CICS to initiate an IP connection. (The term connection is here being used in its IP sense, not as a set of sessions between two systems.)
    • Asynchronous receive support, allowing a task which initiates a receive request on an IP connection to continue to execute concurrently.
    • Persistent sockets, created by one task but remaining active after that task has terminated, allowing them to be reused by another task. This enables the Object Request Broker (ORB) to create a pool of long-lived IP connections.
    • Task sockets, created by a task and remaining active only during the lifetime of that task.
    • Shared sockets, created by one task and remaining active for a number of tasks.

These offer a range of benefits in terms of management and improved scalability and performance.

Connection Optimization: Support for Domain Name System (DNS) registration has been extended, improving the connection optimization that was provided in CICS TS V1.3. Connection optimization uses DNS to balance IP connections and workload in a sysplex domain. This enhancement to connection optimization extends the RDO options and operator interfaces that allow CICS TCP/IP services to register with the OS/390 workload manager in order to take part in DNS connection optimization.

CICS Support for VTAM® LU Alias Facility: The ability has been introduced to coexist with the VTAM capability to dynamically generate an LU alias for a cross-network CDRSC (cross-domain resource). It has also been introduced for static LU aliases. VTAM LU alias facilities provide improved connectivity and inter-operability for terminal networks. Their use facilitates the growth of SNA networks, and allows integration of the networks of multiple enterprises. The addition of this support enables CICS to use an LU alias for terminals and workstations, ensuring unique names across a CICSplex comprising terminal-owning regions (TORs) and application-owning regions (AORs). CICS regions that are owned by different enterprises, and which may use the same VTAM network names, can interconnect without any problem of duplicate network names. This facility can also be used by organizations that offer bureau services.

The CICS LU alias support allows the use of a predefined LU alias for both terminals that are explicitly defined and those that are autoinstalled. A predefined LU alias can also be used for CICS regions that communicate using intersystem communication (ISC). It does not include synclevel 2 connections (LUTYPE 6.1 and 6.2) and it only supports the use of a dynamic LU alias for terminals and workstations that are autoinstalled.

ECI over TCP/IP (CICS TS V2.2): This new function allows client applications to use TCP/IP communication with the External Call Interface (ECI) directly to CICS without the use of any intervening products. Previously, to communicate with CICS on System/390®, clients have had to use SNA LU6.2 or TCP62 (APPC over TCP/IP) support with the AnyNet® feature of SecureWay Communications Manager for OS/390. This required the installation and use of an appropriate communications product such as Communications Server for Windows NT or AIX® at the client system. The use of native TCP/IP directly into CICS removes the complications of installation and configuration involved with TCP62, and simplifies the administration of large networks of clients. No change is required to the client or to the server applications.

Applications using CICS Transaction Gateway V4, CICS Transaction Gateway V3, or CICS Universal Clients V3 can take advantage of this capability, without change.

JCICS Extensions (CICS TS V2.2)

CICS TS V2.2 includes extensions to JCICS which enable it to support CICS Business Transaction Services (BTS), Web, and document APIs.

New Facilities for CICS Exploitation of Procedural Programming

In addition to its functions for the support of EJB and other new technology, CICS TS V2 introduces a range of other new CICS functions, including the following, which are directly applicable to procedural CICS programming.

Integrated Translator for COBOL and PL/I Applications: Previously, development of new application programs has required that the source code should first be passed through a CICS-supplied translator, that translates the EXEC CICS statements into statements in the appropriate language. Then, as a separate step, the code would be passed through the compilation process. Now, CICS TS V2 delivers an Integrated Translator for use with the new COBOL and PL/I compilers, which together perform the compilation and translation process in a single step. The major benefit of this is in the debug process, as the lines of code stepped through with the IBM debugger in the compiled code exactly match the original written source file. There is no requirement for use of an intermediate listing containing the translator-generated calls. This also means that the whole process is simpler, easier, and less liable to error.

This capability is supported by IBM COBOL for OS/390 and VM, Version 2 Release 2, and IBM VisualAge PL/I for OS/390, Version 2 Release 2.1, with PTFs for the support. For other details on these products, refer to, respectively, Software Announcement 200-331 , dated September 26, 2000, and Software Announcement 200-315 , dated September 26, 2000,

Lower levels of these compilers continue to be supported, but without the benefits of the Integrated Translator.

3270 Bridge Enhancements (CICS TS V2.2): The CICS Web 3270 Bridge was introduced in CICS Transaction Server for OS/390 V1.2, and enhanced in CICS TS V1.3. Its function was to enable BMS applications to map their output to HTML data in conjunction with the facilities of CICS Web Support. This has now been complemented by the addition of a LINKable 3270 Bridge that allows a 3270 transaction to be driven using client ECI, host EXCI calls, and DPL or LINK. This is simpler to use than the previous asynchronous START BREXIT interface. It means that client environments that have LINK interfaces to CICS, such as workstation-based client programs using ECI, OS/390 client programs using EXCI, and CICS Clients using the local or remote (DPL) EXEC CICS LINK interface, are now supported. If used in conjunction with the new support for ECI over TCP/IP, use of SNA can be eliminated.

Other new functions introduced include the capability of renaming the bridge facility Termid, participation in workload balancing, and a new INQUIRE SPI.

Enhancements to Function Shipping of Remote File Requests: The remaining differences between processing of API requests for local and remote files have been virtually eliminated. RESP and RESP2 responses (apart from SYSIDERR) are now identical to their local equivalents, so that the application programmer can be totally unaware of the location of the file.

In addition, system files, for example, the BTS repository, can now be data shared without the requirement to use RLS.

Improved Application Availability

Automatic Restart of CICS Data-sharing Servers: The three types of CICS data-sharing servers are the named counter server, the coupling facility data table server, and the shared temporary storage server. For all of them, automatic restart is now supported using the services of the automatic restart manager (ARM) of the operating system. In addition, the servers can now wait during start-up, using an event notification facility (ENF) exit, for the coupling facility to become available in the event of failure of the initial connection.

System-Managed Rebuild Support for Coupling Facility Structures (CICS TS V2.2): A facility is provided in CICS to allow the automatic rebuild, in planned reconfiguration scenarios, of coupling facility structures for the CICS coupling facility servers. These include temporary storage, coupling facility data tables, and named counter servers. This facility is an exploitation of the Cross-System Extended Services® (XES) system-managed rebuild support included in OS/390 V2.8, or later. OS/390 APAR OW39892 must be installed.

Sign-on Retention for Persistent Sessions (CICS TS V2.2): Previously, when using the CICS support for VTAM persistent sessions, in the event of a failure, CICS recovered only the terminal session and not the user's sign-on status, with the result that users had to sign on again after the recovery of the session. With this new function, CICS records the sign-on status of each user in a catalog at the point of sign-on and signoff. This enables it to retain a terminal's sign-on in the event of a failure in either CICS or VTAM, and to restore the signon at reconnection.

The conditions under which a user sign-on status is retained after a recovery of persistent sessions are controlled by a number of options that are similar to those in the CICS extended recovery facility (XRF).

DB2 Group Attach (CICS TS V2.2): This new function allows a CICS user to exploit the DB2 facility where the name may be specified of a DB2 Data Sharing Group instead of an explicit DB2 subsystem name. Each group can contain one or more DB2 subsystems. This simplifies Application Owning Region (AOR) cloning within a sysplex and provides a greater level of availability.

DB2 Group Attach requires DB2 Universal Database for OS/390 Version 7.1, or later.

CICS-DB2 Performance (CICS TS V2.2): The CICS-DB2 Attachment Facility, shipped with CICS TS V2.2, will be enhanced to exploit CICS open transaction environment (OTE) function. When CICS TS V2 is connected to DB2 V6.1, or later, the attachment facility will execute using CICS open TCBs and will utilize DB2 function to move DB2 connections and threads between TCBs. CICS-DB2 applications, coded to threadsafe standards, will benefit greatly from reduced TCB switching. For threadsafe applications making heavy use of EXEC SQL, the reduced TCB switching should provide a significant performance improvement.

Workload Balancing of 3270 Bridge via CICSPlex SM (CICS TS V2.2): CICSPlex SM's workload management component is enhanced in this release to provide dynamic routing capability for 3270 Bridge enhancements described above. This reduces the implementation cost of providing dynamic routing of this work by providing plugin support for the routing exit. All that is now required are simple administrative activities. In common with existing workload management support, it provides workload balancing, separation and abend avoidance. The 3270 Bridge enhancements expose the possibility of a new type of affinity related to the bridge facility token or system lifetime. This new affinity is catered for in both the affinities utility and CICSPlex SM's workload management component.

Systems Management Enhancements

CICSPlex SM Windows NT Agent Support (CICS TS V2.2): CICSPlex SM will provide Remote Managed Application Space (RMAS) agent support to allow management of CICS on the Windows NT platform in TXSeries™ Version 4.3 (delivered in WebSphere Application Server Enterprise Edition for Windows NT), or later. This provides operations, real-time analysis, FEPI BAS support, and the ability to target CICS for Windows NT for dynamic workload management from CICS TS V2.2.

CICSPlex SM Business Application Services (BAS) Integration: As described in the section on the enhancements made to CICS TS V1.3, two significant enhancements were made to BAS in CICS TS V1.3. A further enhancement is made in CICS TS V2.2 so that the limit on the number of connections between related resources through Association Blocks will be removed altogether by using a dynamic mechanism that is scaleable without limit.

The CICS Sample Statistics Program has been enhanced to support the new functions of CICS TS V2. In addition, it is now shipped as pre-generated executable code (as well as in COBOL source code), allowing it to be installed as supplied.

The CICSPlex SM Web User Interface is revised to have a new appearance. This includes a usability improvement to prevent the main navigation icons from being lost from view on the scrolling navigation frame. This can also be advantageous when using the Web user interface on devices with short screens, such as keyboard-based PDAs with a suitable Web browser.

Tivoli® Agent: An agent is shipped as part of CICS TS V2 which exploits the CICSPlex SM API to provide CICS management data to Tivoli Business Systems Manager (5698-BSM). Tivoli Business Systems Manager provides the ability to launch the CICSPlex SM Web user interface.

Other CICSPlex SM items will also be included in CICS TS V2.2.

Other Benefits of CICS Transaction Server for z/OS Version 2

An enhancement to file control will be included in CICS TS V2.2 which removes the risk of unanticipated deadlocks due to the placement of different records in the same VSAM control interval.

As a major enhancement to the usability of its documentation, CICS TS V2 introduces an Information Center, the objective of which is to deliver information that corresponds to the tasks that are performed by the users of CICS. For more information, refer to the Publications section.

CICS TS V2 is Advanced ClusterProven™. For more information, refer to the section on enhancements to CICS TS V1.3.

Also included in CICS TS V2.1 are most of the enhancements that have been made to CICS TS V1.3 since its general availability, many of which are listed in this announcement.

Elements Included in CICS Transaction Server for z/OS Version 2

Like CICS TS V1, CICS TS V2 contains a range of elements. The base CICS element of CICS TS V2.1 is CICS V6.1, and that of CICS TS V2.2 is CICS V6.2. The product includes CICSPlex System Manager as another major element: in CICS TS V2.1, CICSPlex SM is at V2.1, in CICS TS V2.2, it is at V2.2.

In addition to these two major elements, the product also includes the following elements:

  • REXX Development System for CICS/ESA
  • REXX Runtime Facility for CICS/ESA
  • CICS Application Migration Aid Version 1.1
  • Subset for Windows NT only of WebSphere Application Server Advanced Edition V3.5

In the case of the REXX Development System, the REXX Runtime Facility, and CICS Application Migration Aid, the levels are unchanged from those delivered in CICS TS V1.3, with the exception of the application of the latest levels of service.

In addition, CICS VSAM Recovery MVS/ESA™ Version 2 (CICSVR V2) (5695-010) will be packaged as part of CICS TS V2.2. To use it, a license for CICSVR will be required. Further information is given elsewhere in this announcement.

Note that CICS Distributed Data Management (DDM) no longer appears as an element of the product. It has now become a component of the base CICS element.

CICS Universal Clients V3 and CICS Transaction Gateway V3 may be used free of charge with CICS TS V2. They are not included as part of the CICS TS V2 package, but the latest levels (currently V3.1.2 for both) are available for download on the Internet, at:

Both the CICS Universal Clients V3 and the CICS Transaction Gateway are also delivered with other CICS products, and the CICS Universal Clients are available as a program package. For further information on these products, refer to Software Announcement 299-277 , dated September 21, 1999.

All the elements of the product are included on the product tape, with the exception of those elements or components which run on a Windows NT or Windows 2000 machine. The latter are packaged on CD-ROM. For details, refer to the section on Packaging.

Note that the subset of WebSphere Application Server Advanced Edition V3.5 is licensed under the IBM International Program License Agreement (IPLA), and is delivered with IPLA licensing materials.

Enhancements to CICS Transaction Server for OS/390 Version 1 Release 3

The following enhancements to CICS Transaction Server for OS/390 Version 1 Release 3 have recently been made available, or will be made available soon, via the service channel. All these items are also included in CICS Transaction Server for z/OS Version 2 Release 1.

CICS Web Bridge Enhancements: A range of enhancements to the CICS Web Bridge is being delivered in stages, via the service channel, resolving a number of limitations in the implementation of the CICS Web Bridge and allowing it to support a larger subset of current 3270 and BMS applications. These include:

  • Support for dynamic changing of BMS field attributes (APAR PQ42898).
  • Support for multiple maps. Multiple maps in a single screen image will be correctly positioned; and where maps overlap, a best effort made to generate a satisfactory image (APAR PQ42895).
  • Retention of map to support the SEND MAP DATAONLY command (APAR PQ42895).
  • Changes to terminal control support to improve performance, and to allow BMS and terminal control commands to be mixed in the same application will be delivered in APAR PQ42900. This will also contain support for the RECEIVE BUFFER command and 3270 structured fields.
  • Improvements to diagnostic facilities, particularly in 3270 terminal control (APAR PQ42900).
  • Removal of the restriction that prevented a different map name from being used on a RECEIVE MAP command from that in a preceding SEND MAP (APAR PQ42898).

Additional CICS Web Support API Enhancements: The CICS Web Support API is enhanced by the addition of two new CICS commands to assist Web-aware applications in retrieving HTML forms data. The commands are:

  • EXEC CICS WEB READ FORMFIELD
  • EXEC CICS WEB STARTBROWSE FORMFIELD

They work with URL-encoded forms or multipart forms; HTTP requests using the "POST" method; and HTML form INPUT elements of type TEXT, PASSWORD, CHECKBOX, RADIO, SUBMIT, HIDDEN, and FILE (but they do not provide support for "GET" or for access via the plugin).

These new enhancements have been delivered in APAR PQ28513 (PTF UQ37154), APAR PQ35708 (PTF UQ42236), and APAR PQ35709 (PTF UQ42280).

SQLJ/JDBC Support: CICS Java applications can now access DB2 data via the JDBC and SQLJ APIs. This applies to both CICS JVM applications and CICS Java program objects (that is, programs bound using VisualAge for Java, Enterprise Edition for OS/390, Version 2). In addition, JDBC and SQLJ can be used with Java program objects using the new Java Hot Pooling function (for the PTFs required for Java Hot Pooling, refer to below). The JDBC API uses the dynamic SQL model; the SQLJ uses the static SQL model. Support is provided via a new type2 JDBC driver provided by DB2 for OS/390, a complete replacement for the type 1 (ODBC based) JDBC driver. JDBC and SQLJ requests are converted by the JDBC driver into EXEC SQL requests and then routed into the existing CICS-DB2 Attachment Facility. All existing tuning and control parameters available to CICS DB2 applications can be used with CICS Java applications using JDBC and SQLJ.

The type2 JDBC driver is shipped on DB2 Version 5.1 via APAR PQ44113 and on DB2 Version 6.1 via APAR PQ44115. The necessary CICS support is provided via APAR PQ34321 (PTFs UQ41490, UQ41491, and UQ41513). It is recommended that APARs PQ36041 (PTF UQ42721), PQ37771 (PTF UQ43705), and PQ39969 (PTF UQ45634) are also applied. CICS documentation updates are provided in APAR PQ34321 and in an additional documentation APAR PQ38446.

When using JDBC and SQLJ with CICS Java program objects, APARs PQ38178 (PTF UQ43439) and PQ38179 (PTF UQ43443) are required to VisualAge for Java, and it is necessary to be running on OS/390 Version 2.6, or later.

Load Module Scanner: A Load Module Scanner function has been introduced. This provides a facility to scan a load library containing CICS application programs, and compare the EXEC CICS commands in them with those in a filter table. A filter table is provided which will determine those programs that will not work under the CICS 3270 Bridge. The function can also employ user-defined filter tables, allowing it to be used for any other purposes required by the user.

The Load Module Scanner was made available in November 2000 as APAR PQ42109 (PTF UQ49286).

CICS — Language Environment® Enhancements: A range of changes has been made or is being made available that improve the function of CICS with Language Environment in the areas principally of usability, serviceability, and performance. The required levels of Language Environment are indicated in the APARs applicable to these items.

Usability enhancements include:

  • Language Environment and CICS diagnostics are placed together in the transaction dump (APAR PQ38479).
  • Fewer trace entries are caused by taking a dump, so the trace table is more useful (APAR PQ42470, PTF UQ49841).
  • Some Language Environment control blocks will now be formatted in a CICS transaction dump (APAR PQ38479).
  • A new transaction CLER to allow CICS systems administrators to inquire upon and set values for a subset of global Language Environment run-time options. (This transaction is delivered by Language Environment APAR PQ38838.)

Serviceability improvements include:

  • Integration of Language Environment and CICS IPCS verb exits (APAR PQ39051, PTF UQ46585)
  • Extensions to some CICS trace points to trace the application's register save area (APARs PQ44198 and PQ37251, PTFs UQ49876 and UQ46904)

Performance enhancement include:

  • Dynamic storage tuning controlled by a new SIT option AUTODST (APAR PQ39052, PTF UQ47893)

Web Certificate Auto-registration Feature: The Web certificate auto-registration feature allows a Web client of CICS with an SSL client certificate to register that certificate to a userid in the external security manager's database. Previously, it was necessary for a security administrator to register the certificate manually, using RACDCERT or a similar command. With this feature, a client can be prompted to enter a userid and password with the HTTP basic authentication protocol, and if these are successfully validated, the client certificate is automatically registered to that userid. Other options allow CICS to permit only registered client certificates to be used on a connection, or for HTTP basic authentication to be used for authentication regardless of whether SSL is also used. The Web certification auto-registration feature was made available in June 2000 as APAR PQ36169 (PTF UQ44196).

Full-duplex Sockets I/O for IIOP over SSL: The implementation of sockets input and output for IIOP using the secure sockets layer (delivered in APAR PQ23421 (PTF UQ32182)) does not support full-duplex operation. Socket sends are serialized until the preceding socket receive has completed. APAR PQ38050 (PTF UQ46081, which was available August 2000) is intended to remove the serialization, which should improve the throughput for certain types of IIOP application using SSL.

CICSPlex SM Business Application Services (BAS) Integration: Two significant enhancements to BAS have been added to CICS TS V1.3. The previous limit of 129,000 logical connections between related resources through Association Blocks has been raised to a much larger number. To avoid problems of long initialization time or timeout abend when the count of scoped resource definitions becomes large, the Consistent Check process has been made a configurable initialization parameter, with the default set to "off". These items are shipped respectively as APAR PQ28272 (PTF UQ34379) and APAR PQ24039 (PTF UQ38107).

CICS TS V1.3 is Advanced ClusterProven: CICS TS V1.3 is registered by IBM as Advanced ClusterProven. The IBM ClusterProven program introduces new high-availability requirements that may be applied to any combination of operating system, middleware, or end-user application. CICS Transaction Server for OS/390 V1 satisfies and exceeds the S/390® platform's technical criteria and has been registered to receive ClusterProven status. More information is available on the Web at:

Java Hot Pooling: This previously announced function was shipped earlier in 2000. It offers improved performance for Java applications compiled using the VisualAge for Java Enterprise Toolkit for OS/390 (ET/390) byte-code binder (known as high-performance compiler). Java Hot Pooling is APAR PQ31328 (PTF UQ44003). It is recommended that the following fixes also be applied: APAR PQ37302 (PTFs UQ46070 and UQ46071); APAR PQ38696 (PTF UQ45046); APAR PQ38883 (PTF UQ45711); and APAR PQ40351 (PTF UQ46069).

For Java applications written for CICS TS V1.3, running using Java Hot Pooling, results in very significant improvements in performance. The throughput of a single region has been substantially increased due to: (a) a reduction in path length; (b) the higher concurrency of transactions due to the exploitation of multiple TCBs for Java code.

The opportunities for exploitation of CICS TS V1.3 have been further enhanced by the availability of the recently announced MQSeries® Integrator Agent for CICS Transaction Server. For more information, refer to Software Announcement 201-059 , dated March 13, 2001.

Hardcopy Publications: The relevant hardcopy publications for CICS TS V1.3 were reprinted in the fourth quarter of 2000 to reflect the function and maintenance updates which have been added to the product since its general availability. These are, with form numbers including the applicable suffix levels:

                                                    Order
Title                                               Number
 
CICS TS 1.3 Migration Guide                         GC34-5353-33
CICS TS 1.3 Installation Guide                      GC33-1681-32
CICS TS 1.3 Release Guide                           GC34-5352-33
CICS Application Programming Guide                  SC33-1687-33
CICS Business Transaction Services                  SC34-5268-32
CICS DB2 Guide                                      SC33-1939-33
CICS Intercommunication Guide                       SC33-1695-32
CICS Performance Guide                              SC33-1699-33
CICS System Programming Reference                   SC33-1689-33
CICS Trace Entries                                  SC34-5446-33
CICS Application Programming Reference              SC33-1688-33
CICS Customization Guide                            SC33-1683-33
CICS Messages and Codes                             GC33-1694-33
CICS Operations and Utilities Guide                 SC33-1685-33
CICS Resource Definition Guide                      SC33-1684-33
CICS-Supplied Transactions                          SC33-1686-33
CICS System Definition Guide                        SC33-1682-33
CICS RACF Security Guide                            SC33-1701-33
CICS External Interfaces Guide                      SC33-1944-33

To order, contact your IBM representative. Alternatively, they may be purchased from the online IBM Publications Ordering System, at:

Also reprinted are the following licensed publications:

  • CICS Data Areas
  • CICS Supplementary Data Areas

To order these licensed publications, contact your IBM representative. They are ordered under program number 5655-147 by feature number 8146 for CICS Data Areas, and 8147 for CICS Supplementary Data Areas.

The level of CICS Universal Clients and CICS Transaction Gateway included in the CICS Transaction Server for OS/390 Version 1 Release 3 package has been upgraded to the latest level, Version 3.1.2. Those customers with an earlier level, who have a license entitlement, may download the latest level, without charge, from:

Preview: Packaging of Complementary Products

A number of additional products will be included in the package with CICS Transaction Server for z/OS Version 2 Release 2. These products complement CICS and add value to customer solutions. They will be packaged with CICS TS V2.2 for optional, convenient customer licensing and installation, and will also be available separately. The specific terms and conditions applying to each of these products, as packaged with CICS TS V2.2, will be announced at a later date.

Planned complementary products include the following:

MQSeries Integrator Agent for CICS Transaction Server: MQSeries Integrator Agent for CICS Transaction Server (MQSI Agent for CICS) is a new product consisting of a build-time component and a run-time component which runs on CICS TS V1.3 or V2.2. It enables the construction and execution of run-time adapters to process requests from requesting applications for scripting of target applications running locally or on remote backend systems such as CICS/ESA V4.1 and IMS. Requesting applications may pass requests via MQSeries messages or CICS ECI calls; MQSeries Integrator is enabled as a requesting application. MQSI Agent for CICS exploits Business Transaction Services to manage the scripting of target applications.

For further information, announced today, refer to Software Announcement 201-059 , dated March 13, 2001.

CICS VSAM Recovery: A new level will be available of CICS VSAM Recovery, IBM's product for forward recovery of VSAM files. For more information, refer to the Statement of Direction on this product, earlier in this announcement.

CICS Transaction Gateway Version 4: For details, refer below.

Preview: CICS Transaction Gateway Version 4 (5724-A75)

Delivered within CICS TS V2.2 will be a new version of the CICS Transaction Gateway — CICS Transaction Gateway Version 4.0. CICS Transaction Gateway Version 4 will incorporate the major functions of CICS Universal Clients V3 and CICS Transaction Gateway V3 into one priced program package.

The key new features will be:

  • Supports Version 1.3 of the IBM and Sun developer kits for Java
  • Supports HP-UX 11, and Linux on S/390 platforms
  • TCP62 protocol on all supported platforms, except on OS/390

Description

CICS Transaction Gateway V4 will be the latest version of IBM's connector product which will run on the following platforms:

  • IBM OS/390 Version 2.8, or later, including z/OS
  • IBM AIX Version 4.3.3
  • Windows 2000
  • Windows NT
  • Solaris Version 2.7
  • HP-UX 11.00
  • Linux/390 Software distribution from SuSE V7.0 GA (Kernel 2.2.16)

HP-UX and Linux on S/390 are new platforms to be supported by the CICS Transaction Gateway.

CICS Transaction Gateway Version 4 will enable JavaBeans, C++ or COM objects, or C applications to connect to CICS applications running on any CICS server easily and efficiently. The CICS applications may be written in any supported language as LINKable programs or as 3270 transactions. CICS Transaction Gateway V4 will enable communication over TCP/IP, TCP62, SNA LU6.2, and other protocols. It will support transactional interoperation where the invoking application may initiate a recoverable unit of work which is coordinated with the actions of the target CICS application and the resources it accesses.

CICS Transaction Gateway V4 will provide beta support for J2EE Connector specification (J2C), the draft industry-standard interface which enables Enterprise JavaBeans and servlets running on a Java application server to access a variety of Enterprise Information Systems (EIS) with a uniform programming model. These beans and servlets can exploit the connection pooling and transaction management facilities provided by compliant application servers, together with security services provided by the target EIS. The J2C specification is derived from IBM's Common Connector Framework (CCF) which was introduced with VisualAge for Java, and is supported by VisualAge for Java V3.5. J2C support will be provided for both the CICS External Call Interface (ECI) and External Presentation Interface (EPI).

CICS Transaction Gateway Version 4 will support JVM 1.3 on all platforms, and will require this to be present for use of J2C interfaces in both local and remote execution modes. Support for EPI will be enhanced to include support for signon capable terminals, read timeouts and install timeouts within the Java APIs. New Java sample programs will also be provided.

A single new installation package will be provided for Windows NT and Windows 2000, with Roaming User support, which exploits standard Windows installation procedures.

On Windows 2000, support will be included for the Terminal Services feature, which enables support for multiple attached terminal devices.

A new implementation of the TCP62 protocol will be supported on all platforms, except on OS/390. This will be integrated with the base product and will not require separate installation. Configurations and definition used with the previous implementation will work with the new implementation transparently.

CICS Transaction Gateway V4 will incorporate the major functions of CICS Transaction Gateway V3 and CICS Universal Clients V3. It will provide bindings for the ECI, EPI, and ESI programming interfaces in a variety of languages and may be used with both IBM and non-IBM application servers. Various reliability and serviceability enhancements will also be included in the new product.

The following functions of CICS Transaction Gateway V3 will no longer be supported:

  • Operation on the OS/2®, Windows/98 and Windows/95 platforms
  • Execution of Windows 16 bit applications
  • Support for the IBM VisualAge C++ for Windows compiler
  • Support for Cobol, PL/I and REXX applications
  • The CICSTELD function.

The following protocols will not be supported on CICS Transaction Gateway V4:

  • NetBIOS.
  • DCE on Windows.
  • Netware for SAA®.
  • SunLink (SNA) on Solaris. (Note that TCP62 provides equivalent function to SunLink and may be used as an alternative to SNA.)

Product Positioning: Many enterprises use multi-tiered configurations to implement e-business applications which serve their customers as end users. These configurations typically consist of three physical tiers made up of the end-user browser, a Web server/Web application server, and a back-end Enterprise Information System (EIS), although sometimes additional tiers are also used. The purpose of CICS Transaction Gateway is to provide efficient integration of middle tier application servers with CICS-based EISs. It achieves this by providing a multi-user gateway which supports programming interfaces on the same tier as the Web application server, for use by Web applications in Java and other languages. Customers may, therefore, use existing assets and skills in building middle tier solutions in combination with their enterprise CICS systems to achieve effective e-business solutions. CICS Transaction Gateway also provides an excellent environment for customers wishing to gain familiarity with Java programming, prior to using this in the host CICS environment.

CICS Transaction Gateway V4 will enable customers to implement robust and efficient end-to-end configurations and, by supporting major server platforms, will provide considerable flexibility in the configurations which may be adopted. It will also enable customers to change configurations without modifying applications when operational reasons require this or make it desirable, for example, to increase the scalability of a solution. The option to deploy CICS Transaction Gateway V4 on OS/390 or z/OS, supporting Web applications locally on OS/390 or z/OS, or remotely on a physical middle tier server, will provide a configuration which enables high scalability to be achieved and is expected to perform at transaction rates in excess of 1,000 transactions per second.

Publications

The following new manuals will be supplied in PDF format with the product:

                                                       Order
Title                                                  Number
 
CICS Universal Clients for                             SC34-5941
 AIX Administration
CICS Universal Clients for                             SC34-5940
 Windows Administration
CICS Universal Clients for                             SC34-5942
 Solaris Administration
CICS Universal Clients for                             SC34-5944
 Linux Administration
CICS Universal Clients for                             SC34-5943
 HP-UX Administration
CICS Transaction Gateway for                           SC34-5935
 OS/390 Administration
CICS Transaction Gateway Programming                   SC34-5938
CICS Transaction Gateway for                           SC34-5932
 Windows Administration
CICS Transaction Gateway for                           SC34-5933
 AIX Administration
CICS Transaction Gateway for                           SC34-5934
 Solaris Administration
CICS Transaction Gateway for                           SC34-5937
 Linux Administration
CICS Transaction Gateway for                           SC34-5936
 HP-UX Administration
CICS Universal Clients C++ Programming                 SC34-5945
CICS Universal Clients COM                             SC34-5946
 Automation Programming
CICS Family:  Client/Server Programming                SC34-5947

New Book: Designing and Programming CICS Applications: A new book entitled Designing and Programming CICS Applications (ISBN I-56592-676-5), IBM publications order number SR23-9692-00, was recently published by O'Reilly Associates.

This book is an introduction to the design and programming of CICS applications, and is centered around the CICS-supplied ACCT application, which, for the purposes of this book, has been restructured into business and presentation logic, renamed NACT, and provided on a CD-ROM with the book. This COBOL application creates, reads, updates, and deletes records from a VSAM file. It uses BMS maps, but rewriting the COBOL application into business and presentation logic has allowed the addition of three other presentation methods. The first is based on a Web solution and describes how to write a Java program to wrap around the COBOL program using the CICS Java classes. It also uses the CICS CORBA classes to link a Web server to a CICS server through IIOP. In addition, the Web client uses a Servlet JavaBean and JavaServer Pages (JSP) to present the data to the user. The second method develops a front end using Visual Basic and links to the COBOL application using the CICS External Call Interface (ECI) and TCP62. The final presentation method uses Java and the Swing classes to produce the front end that is then linked to CICS through the MQSeries — CICS DPL bridge.

This is a practical book describing application development tools such as VisualAge for Java and WebSphere Studio. Full details are given enabling the reader to use the book as a series of practical exercises. It is suitable for (a) people who are unfamiliar with CICS and who have moved into an environment where CICS is used extensively; (b) those who are looking for ways to develop their CICS system to integrate their current applications with the new technologies; (c) business managers who need enough understanding of CICS to be able to make business decisions about their IT systems.

Also provided on the CD-ROM delivered with the book is the CICS TS V1.3 library in PDF format.

Further information about this book can be obtained from:

Education Support

For CICS Transaction Server for z/OS Version 2 Release 1, interested customers are advised to review the Application Development curriculum, particularly with respect to Java and VisualAge for Java.

An important new course, CICS Application Programming with Java , is available in some countries.

In the second quarter of 2001, a new e-learning course, CICS Transaction Server for z/OS: EJB Support and More! , will be available. This multimedia course will be provided on CD-ROM to run on a workstation.

In due course, IBM Learning Services will update courses to support CICS Transaction Server for z/OS Version 2.

A transition course CICS TS for OS/390 Transition: from V1 to V2 , with information helpful for planning migrations from CICS TS V1.3, will be ready by general availability of CICS TS V2.2.

For additional information, visit the IBM Learning Services Web page and select your country to view available offerings:

This site has descriptions of all classroom and self-study courses available in your country. The Web page also contains information on course schedules and enrollment procedures.

If you cannot find the information you need on the Web page, contact IBM Learning Services at 800-IBM-TEACH (426-8322) for additional details or to enroll in a course.

Technical Information

Specified Operating Environment

Hardware Requirements

Processors: The basic requirement is for a processor that supports the prerequisite operating system and has sufficient processor storage to meet the requirements of the operating system, CICS TS V2, the application programs, the access methods, and all other software being run. This includes the IBM e(logo)server zSeries 900.

Virtual Storage: Requirements for virtual storage for the product with Java and enterprise beans will be included in the Performance Guide.

Parallel Sysplex Support: A Parallel Sysplex environment is required by each of the data-sharing facilities supported by CICS, and by the MVS system logger's log stream merging facility. For this, one or more coupling facilities are required with their associated coupling links installed; a Sysplex Timer® to provide a common external time source; and sufficient DASD paths to support the number of central processor complexes (CPCs) in the sysplex. The DASD paths can be provided either by DASD controllers with enough paths to dedicate one to each CPC in the sysplex, or an ESCON® director to provide the paths.

CICS support for data sharing can be used to access data in IMS databases, DB2 databases, VSAM data sets, CICS temporary storage, coupling facility data tables, or named counters.

Workstation Items: For the CICS JAR Development Tool for EJB Technology, the CICS Development Deployment Tool for EJB Technology, the CICS Production Deployment Tool for EJB Technology, and the Information Center, a workstation is required capable of running Windows NT or Windows 2000.

Katakana Terminal Devices: Because CICS has to issue certain messages in mixed-case, the product is not supported with displays or terminal emulators which are restricted to the single-byte character set (SBCS) Katakana part of code page 930.

Software Requirements

Note that for software requirements, the Program Directory (GI10-2525) will normally contain the latest level of information, particularly concerning APAR/PTF levels of supported products.

Operating environment:

  • The minimum required level of operating system for CICS Transaction Server for z/OS Version 2 Release 1 is OS/390 (5647-A01) Version 2 Release 8. All succeeding levels of the operating system are supported, including z/OS (5694-A01). Note that the product will not initialize unless the minimum prerequisite level of operating system is installed.
  • OS/390 APAR PQ44884 (PTF UQ50735) is required for OS/390 V2.10; or APAR PQ45245 is required for OS/390 V2.8 or V2.9.
  • The minimum required level of operating system for CICS Transaction Server for z/OS Version 2 Release 2 is OS/390 Version 2 Release 10. z/OS is also supported.
  • Note that the Language Environment library SCEERUN must be available to CICS during CICS initialization, either by inclusion in the STEPLIB concatenation or the LNKLIST. Language Environment services are used by a number of CICS functions.
  • For CICS TS V2.1, for Java application programs or for support of enterprise beans, the IBM Developer Kit for OS/390, Java 2 Technology Edition, V1.3 (5655-D35), with a special enhancement, is required. This Java Virtual Machine (JVM), with the special enhancement, is referred to as the persistent, reusable JVM.
    • The IBM Developer Kit for OS/390, Java 2 Technology Edition, V1.3 is available, at no charge, on tape or by download from:
    • Information on how to obtain the special enhancement is given in the Program Directory for CICS Transaction Server for z/OS V2.1 (GI10-2525). It is also available from IBM Solutions Assurance.
    • Service updates to the Operating System are required in order to run the persistent, reusable JVM. The required PTFs are listed at:
    • Enterprise JavaBean support with CICS Transaction Server for z/OS Version 2 Release 2 will require function included in z/OS V1.2.
  • There may be other software prerequisites for CICS Transaction Server for z/OS Version 2 Release 2 identified in a further announcement before its general availability.

COBOL applications may be compiled using:

  • IBM COBOL for MVS and VM Version 1 (5688-197).
  • IBM COBOL for OS/390 and VM Version 2 (5648-A25).
  • The integrated translator function requires Version 2 Release 2, with APAR PQ45462.

PL/I applications may be compiled using:

  • IBM PL/I for MVS & VM Version 1 (5688-235).
  • IBM VisualAge PL/I for OS/390 Version 2 (5655-B22).
  • The integrated translator function requires VisualAge PL/I for OS/390, Version 2 Release 2.1, with APAR PQ45562.

Support remains in CICS TS V2.1 for the earlier (pre-Language Environment) compilers OS/VS COBOL (5740-CB1, 5740-LM1, and 5734-CB4), VS COBOL II (5668-958, also 5688-023 and 5688-022), OS PL/I Version 2 (5668-910), and SAA AD/Cycle® C/370™ (5688-216). Translator support for these compilers is withdrawn in CICS TS V2.2. It is planned that run-time support for load modules created using these compilers, that do not use Language Environment, will be withdrawn in the release following CICS TS V2.2.

CICS TS V2 supports Java applications which have been compiled using the VisualAge for Java Enterprise Toolkit for OS/390 (ET/390) byte-code binder (known as high-performance compiler). However, for restrictions, refer to the Compatibility section.

Enterprise beans developed by VisualAge for Java Enterprise Edition for Windows 98 and Windows NT V3.5 may be used with CICS TS V2.

To generate Data Access Beans for use with CICS TS V2, VisualAge for Java Enterprise Edition for Windows 98 and Windows NT V3.5 may be used. The V3.5.3 level is required.

To generate command beans that run with the CICS Connector for CICS TS, VisualAge for Java Enterprise Edition for Windows 98 and Windows NT V3.5 is recommended, using the Enterprise Access Builder (EAB).

The following levels of other products are supported for use with CICS TS V2:

  • IMS/ESA® Database Manager Version 5.1 (5695-176)
  • IMS/ESA Database Manager Version 6.1 (5655-158)
  • IMS Database Manager Version 7 (5655-B01), or later
  • DB2 Server for OS/390 Version 5.1 (5655-DB2), with APAR PQ44113
  • DB2 Universal Database Server for OS/390 Version 6.1 (5645-DB2) with APAR PQ44115
  • DB2 Universal Database Server for OS/390 Version 7.1 (5675-DB2)
  • The DB2 Group Attach function (CICS TS V2.2) will require DB2 Universal Database for OS/390 Version 7.1, or later
  • OS PL/I V2.3 Compiler, Library and Interactive Test (5668-909)
  • OS PL/I V2.3 Compiler and Library (5668-910)
  • OS PL/I V2.3 Library only (5668-911)
  • CICS VSAM Recovery (CICSVR) (5695-010) Version 2.3
  • MQSeries for OS/390 Version 2.1 (5655-A95), with APAR PQ35501, or later
  • Tivoli Decision Support for OS/390 (5698-TD9) Version 1.5, with a PTF (formerly Tivoli Performance Reporter for OS/390 (5695-101))
  • CICS Universal Clients Version 3.0, or later
  • CICS Transaction Gateway Version 3.0, or later
  • ACF/TCAM(DCB) Version 2.4 (5735-RC3) + PTFs
  • ACF/TCAM(DCB) Version 3.1 (5665-314) + PTFs
  • For advanced program-to-program communication (APPC) to CICS/ESA Version 4.1, PTF UL80372 for PTF PN73189 must be applied to CICS/ESA V4.1
  • With CICS TS V2.2, MQSeries Integrator Agent for CICS Transaction Server Version 1.1

For the CICS JAR Development Tool for EJB Technology, the CICS Development Deployment Tool for EJB Technology, and the CICS Production Deployment Tool for EJB Technology:

  • Windows NT Version 4.0, or later, with service pack 6, or Windows 2000, with service pack 1, is required.
  • IBM Developer Kit for Windows, Java 2 Technology Edition, V1.3, at Service Level 6, or later, is required, together with the necessary Sun extensions.
    • This Developer Kit, with the Sun extensions, is provided on the CD-ROM.
    • If the CICS Tools for EJB Technology are installed without the necessary prerequisite level of Developer Kit installed, a warning is given, though installation will not be prevented.
  • The CICS Development Deployment Tool for EJB Technology requires a Web browser with CSS support and file upload capability according to RFC 1867, such as Netscape 4, or later, or Microsoft™ Internet Explorer Version 4.0, or later.

For the Information Center, or for viewing the Information Center from another workstation, the following are required:

  • Windows NT Version 4.0, or later, or Windows 2000
  • A browser that supports HTML 4.0 and the Document Object Model (DOM) standard, such as Microsoft Internet Explorer Version 5.0

For EJB support, a COSNaming server is required.

  • The subset of WebSphere Application Server Advanced Edition for Windows NT V3.5, shipped with the product, can be used for this purpose. It is recommended that Service Pack 3 be applied.

For the shipped subset of WebSphere Application Server Advanced Edition for Windows NT V3.5, Windows NT Version 4.0, or later, or Windows 2000 is required.

Compatibility

File control user exits: Changes to function shipping of file control requests have affected the invocation of file control user exits. The EXEC-level exits XFCREQ and XFCREQC are now only invoked in the region where the file control request was originally issued. A new global user exit, XFCFRIN, will be introduced. This new exit is a domain level exit and will be invoked on entry to the file control component. This exit may:

  • Bypass file control processing
  • Specify a new SYSID to enable the request to be shipped to a remote region

This new exit will be delivered via the service channel after general availability of CICS TS V2.1.

CICSPlex SM: The CICSPlex System Manager element of CICS TS V2 does not support the following CICS products that were supported by previous levels of CICSPlex SM:

  • CICS/MVS® Version 2.1.2 (5665-403)
  • CICS/ESA Version 3.3 (5685-083)
  • CICS/VSE® Version 2 (any release) (5686-026)
  • CICS Transaction Server for VSE/ESA™ Version 1 (5648-054)
  • CICS for OS/2 Version 2.0.1 (5648-036)

For CICSPlex SM support of these CICS products, a CMAS at an appropriate lower level may be used. Normally all communicating CMAS should be at the same level, however, the following products may be controlled from the CICSPlex SM element of this product through an appropriate lower level of CMAS:

  • CICS/MVS Version 2.1.2 (5665-403)
  • CICS/ESA Version 3.3 (5685-083)
  • CICS for OS/2 Version 2.0.1 (5648-036)

CICS TS V2.2 will be the last level of CICS TS V2 which includes CICSPlex SM Agent support for CICS Transaction Server for OS/2 Version 4.1 (5622-808, due for discontinuance of service in March 2003).

Like its predecessor CICS TS V1.3, this is a Tivoli-Ready product that includes Tivoli Global Enterprise Manager (GEM) — CICSPlex SM Instrumentation.

NetView: Previous levels of the CICSPlex SM component of CICS Transaction Server for OS/390 have provided the ability to populate CICS resource existence and minimal state data into the Resource Object Data Manager (RODM) component of NetView. With the advent of Tivoli, this support for NetView is now stabilized, and new object data is no longer added to this interface. The support will be removed from CICSPlex SM in CICS TS V2.2.

Java Levels: CICS TS V2 does not support levels of Java earlier than IBM Developer Kit for OS/390, Java 2 Technology Edition, V1.3. Any Java programs written for use with CICS TS V1.3 using a Java 1.1 JVM must be migrated to Java 2. For information about Java application migration issues, refer to the Web site of Sun Microsystems, Inc., at:

To avoid problems with deprecated APIs, all new Java applications for CICS TS V2 should be developed using an application development environment that supports Java 2 at the SDK 1.3 level. VisualAge for Java V3.5 can be used, but note that it supports the SDK 1.2 level. Note also that enterprise beans developed using VisualAge for Java V3.5, which supports the EJB 1.0 specification, need to be migrated to the EJB 1.1 specification level. This may be done using the CICS JAR Development Tool supplied with CICS TS V2.1.

CICS Programs Running Under the JVM: A JVM program cannot link, either directly or indirectly, to another JVM program in the same CICS region.

Support for Java Program Objects: These are programs compiled with the hpj command. (They are sometimes referred to as compiled Java programs or as HPJ programs.) In CICS TS V2.2, it is recommended that all Java programs should be run in JVM mode. However, to ease migration from CICS TS 1.3, CICS TS V2.1 and V2.2, continue to support Java program objects, which can run with or without the HOTPOOL option, except that:

  • IIOP Java program objects are not supported
  • EJBs must execute in JVM mode
  • Java applications that use the CCF client interface must run in JVM mode

If a Java program object developed for CICS TS V1.3 that has been migrated to run in CICS TS V2 requires modification, it is strongly recommended that it be recompiled to run in JVM mode. If this is not possible for some reason, the Java program object can be rebuilt as for CICS TS V1.3 using the application development tooling appropriate to that release.

Support for both IIOP and non-IIOP Java program objects will be continued in CICS Transaction Server for OS/390 Version 1 Release 3 throughout its lifetime.

CORBA Support: GenericFactory IOR files are now created during the installation of CICS resources, removing the need for the GenFacIOR utility. Note that IIOP applications are supported in JVM mode only. The VisualAge for Java Enterprise ToolKit for OS/390 bytecode binder cannot be used with IIOP applications.

Other Items: The removal of run-time support for the destination control table (DCT) has made the DCT system initialization parameter obsolete.

Migration: Before the availability of CICS TS V2.2, users of CICS/ESA Version 4.1 or earlier versions of CICS are recommended to migrate to CICS TS V1.3.

To convert the CICSPlex SM Web User Interface server to CICS TS V2.1, it is necessary to migrate the MAS that acts as the Web User Interface server; migrate the Web User Interface CSD group; and migrate the contents of the Web User Interface server repository (EYUWREP).

For information on courses, refer to the Education Support section.

Performance Considerations

Traditional Procedural Language Workloads: Comparisons with CICS TS V1.3, using an IBM Internal Benchmark, show that CICS TS V2.1 has equivalent performance characteristics in terms of Internal Transaction Rate (ITR).

IIOP Workloads: The support for inbound IIOP with Java program objects (compiled with the hpj command) has been removed with CICS TS V2.1. IIOP applications are supported in JVM mode only. The VisualAge for Java, Enterprise ToolKit for OS/390 bytecode binder cannot be used with IIOP applications. Although these IIOP applications in CICS TS V2.1 cannot use the hpj command, we expect that the performance will be similar in terms of CPU costs and response time to that achieved for the same applications in CICS TS V1.3.

CICS Support for Persistent, Reusable JVM: CICS TS V2.1 will exploit the enhancements in the persistent, reusable JVM. The CICS support enables serial reuse of pre-initialized JVMs which, together with new garbage collection, provides significant performance improvements over the previous JVM. In the general availability level, it is expected that the performance of applications in this new environment will be similar to, if not better than, that of Java program objects (compiled with the hpj command) in CICS TS V1.3. Performance will continue to be improved throughout the CICS TS V2.1/V2.2 timeframe.

CICS EJB Support: CICS TS V2.1 enables you to configure CICS as an EJB Server and support EJB session beans. The performance in this environment will be dependent on many factors including the transactional qualities, the implicit services used by the enterprise bean, and adherence to the EJB programming specification. Although CICS TS V2.1 has not been recommended for high-volume production use, constraints such as below the 16M line storage availability may limit its scalability within a single CICS address space. Performance enhancements will continue to be added to the product for CICS TS V2.2, including the use of CICS storage management for JVMs which will improve scalability by allowing a pool of a larger number of JVMs.

User Group Requirements: The enhancements described in this announcement address a range of user requirements from the various worldwide user group communities, such as SHARE, GUIDE, WAVV, and COMMON. These include the following.

In CICS Transaction Server for OS/390 Version 1 Release 3:

Requirement
Number                  Description
 
                        CICS Web Bridge enhancements:
MR0329006734             Enhance HTML template generation
                          from BMS source
MR103100591              Browser caching
MR0410002034             Samples (and CSTs) to be made
                          Web bridge enabled
 
                        CICS Web Support API enhancements:
REQ00075123              Support of files in FORMFIELD
                          API
MR0628002216             HTML form INPUT elements of
                          type FILE
REQ00074026              CICS Web Interface Parser
                          Support of the HTMLSELECT
                          MULTIPLE option

In CICS Transaction Server for z/OS Version 2 Release 1:

Requirement
Number                  Description
 
                        Enhanced Sockets Support:
REQ00068784              No standard procedu. avail. for
                          communic. to TCPhost
 
                        Integrated Translator:
REQ00036573              Expand copy books before
                          translation
REQ00035876              Expand copy books before
                          translation
REQ00036892              Show expansion of DFHRESP and
                          DFHVALUE
REQ00068178              Fix code page changes
                          (esp. applicable to C)
UCD1097-45               Need translator integrated into
                          compilers
 
MR0502002120              Remove RLS requirement for
                           sharing BTS repository files
 
                        Automatic restart for CF-related
                         servers:
MR00070720                Automated RESTART of TSQ-Server
 
                        CICS support for VTAM LU alias
                         facility:
REQ00074293               Enhanced connection definition
                           network-id name

In CICS Transaction Server for z/OS Version 2 Release 2:

Requirement
Number                  Description
 
                        ECI over TCP/IP:
REQ00062783              CICS Windows Client to CICS TS
                          via TCP/IP
REQ00063077              Support of eci_tpn over TCP/IP
REQ00063932              Support for keepalive and
                          client failure notification
REQ00066262              Wants TCP62 for Windows 3.1
                          CICS Client to connect to ESA
REQ00070270              TCP62 support for CICS
                          universal Client for AIX to
                          connect to ESA
REQ00073847              AttachSec (Identify) for eci/ip
REQ00074476              ECI on the os390 platform
 
                        JCICS Extensions:
MR1018005212             Java support for CICS/BTS
MR00074295               Java Support for Web & DOC API
 
                        Sign-on Retention:
MR00070103               Retain CICS Signon Info until
                          TOR Restart
 
                        CF Autorebuild:
MR00066257               Rebuild/Alter support for
                          shared TS Queue structure
MR00076654               Provide Structure Rebuild for
                          Shared TS Queues
MR112700440              CICS shared temp storage
                          structure needs to support
                          rebuild (yes)
 
                        Show IP address available for
                         TN3270:
REQ00069574               Ability to pass IP address to
                           the VTAM applicn
 
                        DB2 Group Attach:
MR00065722               Multiple DB2 prefixes in a
                          single CICS region
MR00066361               Support Datasharing Group id in
                          SUBID parameter of CICS RCT
MR00073578               RCT-connect to DB2-group in
                          addn to DB2-member
 
                        3270 Bridge enhancements:
MR00073484               3270 Bridge Termid requirement
                          for naming bridge facilities
MR091100141              Transaction Routing with CICS
                          3270 Bridge

Security, Auditability, and Control

Refer to the section EJB Security in the description.

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

Customer Financing

IBM Global Financing offers attractive financing to credit-qualified commercial and government customers and Business Partners in more than 40 countries around the world. IBM Global Financing is provided by the IBM Credit Corporation in the United States. Offerings, rates, terms, and availability may vary by country. Contact your local IBM Global Financing organization. Country organizations are listed on the Web at:

Ordering Information

Advance Publications

The publication CICS Transaction Server for z/OS Version 2 Release 1: Release Guide is available now, in PDF format, for download, free of charge, from:

New Licensees

Orders for new licenses can be placed now.

Shipment will begin on the planned availability date.

New users of CICS Transaction Server for z/OS Version 2 should specify:

          Type           Model
 
          5697           E93

Orders for CICS Transaction Server for z/OS Version 2 Release 1 may only be made via a stand-alone 5697-E93 product order. This release is not available in the Customized Offerings (CBPDO, ServerPac, Systempac®, or ProductPac®).

A Solutions Assurance Review is strongly recommended before an order is placed for CICS Transaction Server for z/OS Version 2 Release 1. Contact your IBM representative.

CICS Transaction Server for z/OS Version 2 Release 2 will be available under CBPDO (5751-CS3). It will also be available as soon as possible, after general availability, under ServerPac (5751-CS9).

Basic License: To order a basic license, specify the program number and feature number 9001 for asset registration.

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

                                                        ESL
                                                        One-Time
 
 
                                                        Charge
Program                                                 Feature
Number               Description                        Number
 
5697-E93             Entry Support License              0024

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 and PSLC Level B, and PSLC Level C, PSLC Level D features and quantity.

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

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

Parallel Sysplex License Charge Features

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

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

  • 0003 — quantity 1
  • 0004 — 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:
    • 0003 — quantity 1
    • 0005 — quantity 1
    • 0006 — quantity 5
    • 0007 — quantity 1
  • PSLC no-charge license #2:
    • 0014 — quantity 1

Workload License Charge (WLC) Basic License: To order a basic license, specify the program number and feature number 9001 for asset registration. Also, specify the feature number of the desired distribution medium.

Variable Workload License Charge Features

VWLC                                                     VWLC
Feature                                                  Feature
Description                                              Number
 
Base, Level 1 includes 45 MSUs                           0028
Additional qty, Level 1 up to 175 MSUs                   0029
Registration Base, Level 1 incl 1 MSU                    0030
Registration additional quantity                         0031
 Level 1 up to 175 MSUs
Additional qty, Level 2 176 -- 315 MSUs                  0032
Registration additional quantity                         0033
 Level 2 176 -- 315 MSUs
Additional qty, Level 3 316 -- 575 MSUs                  0034
Registration additional quantity                         0035
 Level 3 316 -- 575 MSUs
Level 3, Per 50 MSUs for machine                         0036
 capacity of 316 -- 575 MSUs
Level 3, Registration per 50 MSUs for                    0037
 machine capacity of 316 -- 575 MSUs
Additional qty, Level 4 576+ MSUs                        0038
Registration additional quantity                         0039
 Level 4 576+ MSUs
Level 4, Per 50 MSUs for machine                         0040
 capacity of 576+ MSUs
Level 4, Registration per 50 MSUs for                    0041
 machine capacity of 576+ MSUs

S/390 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 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)

Usage License Charge Features

                                                         Usage
                                                         Pricing
                                                         Feature
Description                                              Number
 
0 to 0.25 MSU Base                                       0015
0.26 to 0.5 MSU Base                                     0016
0.51 to 1.0 MSU Base                                     0017
 
Level A Chg/MSU (2 to 11 MSUs)                           0018
Level B Chg/MSU (12 to 44 MSUs)                          0019
Level C Chg/MSU (45 to 78 MSUs)                          0020
Level D Chg/MSU (Above 78 MSUs)                          0021
Level D per 50 MSUs (Above 78 MSUs)                      0022
 
NC ID Feature                                            0023

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

Growth Opportunity License Charge (GOLC): To order a 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.

                                  GOLC
           GOLC                   Feature
           Category               Number
 
           H30                    0025
           H50                    0026
           H70                    0027

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

Basic Machine-Readable Material: As part of the order, select the feature number of the desired distribution medium. The product is shipped on three tapes (of whichever type is chosen).

The machine-readable material shipped on the distribution media is common to all languages shipped, and includes messages translated to Japanese and Simplified Chinese. Different distribution medium feature codes are provided by language, but this is only because they cause the appropriate translated hardcopy publications to be shipped with the product tapes.

                       Feature
Environment            Number              Distribution Medium
 
OS/390 or              5801                Magnetic Tape 9-track
 z/OS                                       6250 bpi
OS/390 or              5802                3480 1/2-inch Tape
 z/OS                                       Cartridge
OS/390 or              6201                4-mm DAT Cartridge
 z/OS

Basic Machine-Readable Material with Translated Publications: For an order with hardcopy publications in Japanese (Kanji), select the feature number of the desired distribution medium below, instead of the base feature number:

                       Feature
Environment            Number              Distribution Medium
 
OS/390 or              5811                Magnetic Tape 9-track
 z/OS                                       6250 bpi, with
                                            Japanese publications
OS/390 or              5812                3480 1/2-inch Tape
 z/OS                                       Cartridge, with
                                            Japanese publications
OS/390 or              6202                4-mm DAT Cartridge,
 z/OS                                       with Japanese
                                            publications

No translated publications in Simplified Chinese are provided for CICS TS V2.1, so there are no Simplified Chinese distribution media feature numbers.

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

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

                                                    Feature
Description                                         Number
 
Initial Shipments
 
Serial Number Only (suppresses shipment             3444
 of media and documentation)
 
Ship Media Only (suppresses initial                 3470
 shipment of documentation)
 
Ship Documentation Only (suppresses                 3471
 initial shipment of media)
 
Update Shipments
 
Ship Media Updates Only (suppresses                 3480
 update shipment of documentation)
 
Ship Documentation Only (suppresses                 3481
 update shipment of media)
 
Suppress Updates (suppresses update                 3482
 shipment of media and documentation)
 
                                                    Feature
Description                                         Number
 
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:

Optional Source (excludes Object-Code Only modules): This is shipped on two tapes (of whichever type is chosen).

          Feature
          Number             Distribution Medium
 
          5841               9/6250 Magnetic Tape*
          5842               3480 Tape Cartridge*
          6205               4-mm DAT Cartridge*

* Contains RESTRICTED MATERIAL OF IBM

Publications

Publications Overview

For CICS TS V1.3, the CICS documentation was provided primarily in 55 printed books, many of which were in the format of functional product descriptions. For CICS TS V2.1, there has been a move away from printed books as the default deliverable to a new online concept. The primary source of user information is a new CICS Information Center with a graphical user interface, delivered with the product on a CD-ROM. This HTML-based Information Center runs inside a Web browser, and provides alternative means of accessing the information within it. The objective of the Information Center is to make it easy for users to retrieve the information they need to perform specific CICS tasks.

At the heart of the Information Center is an HTML representation of the total CICS library (unlicensed books). Within the graphical user interface, the key documentation can be accessed via three main classes: tasks, concepts , and reference , each separately selectable. On selecting a class, the categories for that class are displayed in the navigation panel. Each of these can be expanded into a hierarchical navigation tree of topics that in turn point to the detailed information.

The Information Center can be run from the CD-ROM or can be installed onto a workstation or Web server. It runs on Windows NT or Windows 2000. Note the requirements for a browser suitable for use with the Information Center, in the Software Requirements section.

For CICS TS V2.1, the main focus of the documentation is the implementation of EJBs in the CICS environment. A new piece of documentation entitled Java Applications in CICS is the cornerstone of this information, and has been structured to reflect the tasks required to use this new technology.

The Information Center includes a powerful search capability based on IBM's NetQuestion technology. Search results can be saved for future reference.

In addition to the new methods of accessing the CICS documentation, the Information Center provides the more traditional alternative of a complete library listing of the books (detailed below), which can be viewed in both HTML and PDF formats. The latter also provides the capability to print either the whole book or some of the pages in hardcopy at a printer, using Adobe Acrobat.

One copy of the CICS Information Center CD-ROM is automatically shipped as part of the product. Further copies can be ordered, at no additional charge, by specifying the following feature:

                                                       Feature
Title                                                  Number
 
CICS Information Center CD-ROM                         7014
 (SK3T-6903)

The Information Center (without the licensed publications which are shipped only on the Information Center CD-ROM) may also be downloaded over the Internet, from:

PDF versions of all unlicensed books contained in the Information Center are also separately available at this site.

Printed Publications

In addition to their provision within the Information Center as softcopy, the following books that provide planning and installation information are delivered in hardcopy with the product:

                                                       Order
Title                                                  Number
 
CICS Transaction Server for z/OS                       GC34-5701
 Release Guide
CICS Transaction Server for z/OS                       GC34-5699
 Migration Guide
CICS Transaction Server for z/OS                       GC34-5697
 Installation Guide
CICS Transaction Server for z/OS                       GC34-5698
 Licensed Program Specifications

In addition, the following printed documentation is delivered with the product:

                                                       Order
Title                                                  Number
 
CICS Transaction Server for z/OS                       GI10-2524
 Memo to Licensees
CICS Transaction Server for z/OS                       GI10-2525
 Program Directory
CICS Business Partner Directory                        GC34-5527
 (second edition)

Additional printed copies of these books may be purchased for a fee. Contact your IBM representative. Alternatively, books may be purchased from the online IBM Publications Ordering System, at:

If required, any of the product publications may be printed from their PDFs delivered in the Information Center.

A PDF version of the Release Guide for CICS TS V2.1 is available now at:

The following hardcopy manuals in Japanese are provided with the product instead of the corresponding hardcopy manuals in U.S. English, if the appropriate distribution media features (for the basic machine-readable material) are specified in the product order (refer to above). The remainder of the hardcopy publications materials will be shipped in U.S. English. Additional copies of these Japanese books may be purchased for a fee.

                                                       Order
Title                                                  Number
 
CICS Transaction Server for z/OS                       GC88-8662
 Release Guide -- Japanese
CICS Transaction Server for z/OS                       GC88-8661
 Migration Guide -- Japanese
CICS Transaction Server for z/OS                       GC88-8660
 Installation Guide -- Japanese

Note that this announcement also includes some information concerning the hardcopy publications for CICS TS V1.3. Refer to the section Enhancements to CICS Transaction Server for OS/390 Version 1 Release 3 .

In addition to the books listed above, the following unlicensed publications are provided within the Information Center. Hardcopy of these publications is only available by printing the PDF files, and is not orderable.

  • CICS Application Programming Guide
  • CICS Application Programming Reference
  • CICS Business Transaction Services
  • CICS C++ OO Class Libraries
  • CICS Customization Guide
  • CICS DB2 Guide
  • CICS Distributed Transaction Programming Guide
  • CICS External Interfaces Guide
  • CICS Front End Programming Interface User's Guide
  • CICS Glossary
  • CICS IMS Database Control Guide
  • CICS Intercommunication Guide
  • CICS Internet Guide
  • Java Applications in CICS
  • CICS Messages and Codes
  • CICS Operations and Utilities Guide
  • CICS Performance Guide
  • CICS Problem Determination Guide
  • CICS RACF Security Guide
  • CICS Recovery and Restart Guide
  • CICS Resource Definition Guide
  • CICS Shared Data Tables Guide
  • CICS Supplied Transactions
  • CICS System Definition Guide
  • CICS System Programming Reference
  • CICS Trace Entries
  • CICS Transaction Affinities Utility Guide
  • CICS User's Handbook
  • CICS Family: Interproduct Communication
  • CICS Family: Communicating from CICS on System/390
  • CICSPlex SM Administration
  • CICSPlex SM Application Programming Guide
  • CICSPlex SM Application Programming Reference
  • CICSPlex SM Concepts and Planning
  • CICSPlex SM Managing Business Applications
  • CICSPlex SM Managing Resource Usage
  • CICSPlex SM Managing Workloads
  • CICSPlex SM Messages & Codes
  • CICSPlex SM Monitor Views Reference
  • CICSPlex SM Operations Views Reference
  • CICSPlex SM Problem Determination
  • CICSPlex SM Resource Tables Reference
  • CICSPlex SM User Interface Guide
  • CICSPlex SM View Commands Reference Summary
  • CICSPlex SM Web User Interface Guide

All the above softcopy books for CICS, CICSPlex SM, and CICS family (as well as those for the CICS Transaction Gateway and the CICS Universal Clients) are also available in PDF format on the Internet at:

Note that the CICS Performance Guide (SC34-5718) will be made available in two stages, as more performance data is expected to be available after general availability of the product. The initial level of the document will be made available at the same time as product availability, on the above Internet site, and within the CICS Information Center. Three months after product availability, the level of the document, as available on the Internet site, will be refreshed. Customers wishing to obtain the later level of the document should access the above Internet site.

Collection Kit for Transaction Processing and Data Products: This Collection Kit is a CD-ROM. It contains books in BookManager® form for a range of IBM transaction processing and data products, including members of the CICS family. It is made available with this product for its information concerning related products, including CICS Transaction Server for OS/390 Version 1. Note that the CICS TS V2.1 documentation is not included in this Collection Kit.

One copy of the Collection Kit for Transaction Processing and Data products CD-ROM (SK2T-0730) will be shipped, free of charge, with this product if feature number 7022 is specified in the order.

For further information about the Collection Kit, including methods of ordering additional copies if required, refer to announcements or printed information on the Collection Kit, or alternatively to the last announcement of CICS TS V1.3, Software Announcement 299-057 , dated March 9, 1999.

Licensed Documentation: Licensed documentation is only available to licensees of the product. The licensed material Diagnosis Reference (LY33-6097) and Data Areas (LY33-6096) will be provided, in PDF format only, on the CICS Information Center CD-ROM. Note that these books are not available in hardcopy.

The Supplementary Data Areas (LY33-6098) licensed book is available only in hardcopy, for a price of $104, by specifying feature number 8051. Note that this book is not orderable through the publications ordering system.

These Supplementary Data Areas in softcopy on tape may be ordered for a price of $1,040 by specifying the appropriate one of the following supply feature numbers. It is delivered on a single tape. (Note that a hardcopy of the Supplementary Data Areas licensed book is included).

                                                       Feature
Distribution Medium                                    Number
 
9/6250 Magnetic Tape                                   8054
3480 Tape Cartridge                                    8052
4-mm DAT Cartridge                                     8053

Note that this contains RESTRICTED MATERIALS OF IBM . For more information, refer to the Licensed Program Specifications.

Source Listings: No source listings are provided for CICS TS V2. If you require access to such listings, use the View Program Listings (VPL) system. For further information on the VPL system, refer to:

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.

Publications for CICS TS V1.3: The relevant hardcopy publications for CICS TS V1.3 have been reprinted in the fourth quarter of 2000 to reflect the additional function which has been added to the product since its general availability. A list is given earlier in this announcement.

Publications for CICS/390 Products No Longer Being Marketed: Publications for CICS Transaction Server for OS/390 Version 1 Releases 1 and 2, and for CICS/ESA Version 4.1, continue to be maintained for the duration of the service currency of the respective products. These updated publications are available in softcopy BookManager form on the Collection Kit for Transaction Processing and Data products, SK2T-0730 (for more information, refer to above). Hardcopy books may be no longer available, and where they are still available, they may not be at the latest level.

Packaging

The following items are shipped together with the basic machine-readable material as part of the package in which the product is delivered:

  • Hardcopy publications material as listed in the publications section
  • CD-ROM: CICS Information Center (SK3T-6903)
  • CD-ROM: CICS Tools for EJB Technology (LCD4-4355)
  • CD-ROM: WebSphere Application Server, Advanced Edition for Windows NT V3.5 (Application Server and IBM HTTP Server)
  • CD-ROM: WebSphere Application Server, Advanced Edition for Windows NT V3.5 (DB2 Universal Database and IBM SecureWay Directory — SBCS)
  • CD-ROM: WebSphere Application Server, Advanced Edition for Windows NT V3.5 (DB2 Universal Database and IBM SecureWay Directory — DBCS)
  • International Program License Agreement (IPLA, Z125-3301)
  • IPLA Pointer Sheet (Z127-1000)
  • License Information: WebSphere Application Server, Advanced Edition V3.5 (LC23-4587)

Customized Offerings

CICS TS V2.1 is not shipped via Customized Offerings; it is only available stand-alone.

CICS TS V2.2 will be shipped via Customized Offerings (such as CBPDO and ServerPac).

Terms and Conditions

Licensing: IBM Customer Agreement

Variable Charges Apply: No

Indexed Monthly License Charge (IMLC) Applies: No

Installation License or Location License Applies: No

Usage Restriction Applies: No

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

Volume Discount: Not applicable

Connectivity Code

Customers with a license for CICS Transaction Server for z/OS Version 2 may copy, free of charge, the following connectivity code to any S/390 machine to enable communication with the licensed CICS TS V2:

  • CICS External Communication Interface (EXCI — Load Library SDFHEXCI)
  • CICS Transaction Gateway for OS/390 (OS/390 component of 5648-B43)

They may also copy, free of charge, the CICS inter-region communication SVC (DFHIRP) from this version to a prior version of CICS, on a different machine in the same Parallel Sysplex, for communicating with CICS TS V2.

The service and support entitlement under the license for the CICS TS V2 extends to copies of the above items when they are running on a different S/390 machine for this purpose.

Application Development Utilities

To assist developing, testing, or analyzing their applications off-line from their production CICS systems, customers with a CICS Transaction Server for z/OS Version 2 license may copy the following utilities, free of charge, to any S/390 machine within the same enterprise:

  • The CICS Translator (modules DFHEAP1$, DFHEDP1$, DFHECP1$, and DFHEPP1$, which are to be found in SDFHLOAD)
  • The Statistics utility program (DFHSTUP)
  • The Trace utility program (DFHTUP)
  • The Dump utility program (DFHDUP)
  • The Monitoring utility program (DFHMNDUP)
  • The System Definition File utility program (DFHCSDUP)
  • The CICS Transaction Affinities utility program (5696-582)

The service and support entitlement under the license for the CICS TS V2 extends to copies of these utilities when they are running on a different S/390 machine within the same enterprise.

Workstation Components of CICS TS for z/OS V2.1: Customers with a license for CICS Transaction Server for z/OS Version 2.1 are licensed, at no additional charge, to install and run the following components of the product on suitable workstation or server machines, which are not the designated machine, within the same enterprise. They may be run on as many machines as are reasonably necessary for use in conjunction with CICS TS V2.1. The components are:

  • CICS Tools for EJB Technology
  • Information Center

CICS Universal Clients V3: Any number of copies of the CICS Universal Clients V3 may be made, free of charge, for communication with CICS Transaction Server for z/OS Version 2. For this use, customers are authorized to make copies of the CICS Universal Clients as program features.

CICS Transaction Gateway V3: A customer who has a license of CICS Transaction Server for z/OS Version 2 may make any number of copies of the CICS Transaction Gateway V3, for use with any number of users within the enterprise, without charge or further licensing requirement.

Licensing of WebSphere Application Server Advanced Edition: This product is accompanied by a subset of the Windows NT version of WebSphere Application Server Advanced Edition Version 3.5 (WebSphere Application Server). A license of the program entitles you to install up to five copies of this WebSphere Application Server subset, for use only in conjunction with your authorized use of the CICS Transaction Server for z/OS Version 2 Release 1 program. Except for the foregoing additional restrictions and rights, your use of these WebSphere Application Server components is subject to the terms and conditions of the International Program License Agreement and License Information document for the WebSphere Application Server components included in the packaging for the program.

Products Eligible for Single Version Charging

                                                            Single
Replaced Programs             Replacement Programs          Version
Program   Program             Program   Program             Charging
Number    Name                Number    Name                Applies
 
5740-XX1  CICS/OS/VS V1       5655-147  CICS Transaction    Yes
                                         Server for
                                         OS/390 V1
 
5740-XX1  CICS/OS/VS V1       5697-E93  CICS Transaction    Yes
                                         Server for z/OS
                                         V2
 
5665-403  CICS/MVS V2         5655-147  CICS Transaction    Yes
                                         Server for
                                         OS/390 V1
 
5665-403  CICS/MVS V2         5697-E93  CICS Transaction    Yes
                                         Server for z/OS
                                         V2
 
5685-083  CICS/ESA V3         5655-147  CICS Transaction    Yes
                                         Server for
                                         OS/390 V1
 
5685-083  CICS/ESA V3         5697-E93  CICS Transaction    Yes
                                         Server for z/OS
                                         V2
 
5655-018  CICS/ESA V4         5655-147  CICS Transaction    Yes
                                         Server for
                                         OS/390 V1
 
                                                            Single
Replaced Programs             Replacement Programs          Version
Program   Program             Program   Program             Charging
Number    Name                Number    Name                Applies
 
5655-018  CICS/ESA V4         5697-E93  CICS Transaction    Yes
                                         Server for z/OS
                                         V2
 
5665-463  CICS DDM            5655-147  CICS Transaction    Yes
                                         Server for
                                         OS/390 V1
 
5665-463  CICS DDM            5697-E93  CICS Transaction    Yes
                                         Server for z/OS
                                         V2
 
5695-081  CICSPlex SM V1      5655-147  CICS Transaction    Yes
                                         Server for
                                         OS/390 V1
 
5695-081  CICSPlex SM V1      5697-E93  CICS Transaction    Yes
                                         Server for z/OS
                                         V2
 
5655-086  REXX Development    5655-147  CICS Transaction    Yes
           System for                    Server for
           CICS/ESA                      OS/390 V1
 
5655-086  REXX Development    5697-E93  CICS Transaction    Yes
           System for                    Server for z/OS
           CICS/ESA                      V2
 
5655-087  REXX Runtime        5655-147  CICS Transaction    Yes
           Facility for                  Server for
           CICS/ESA                      OS/390 V1
 
5655-087  REXX Runtime        5697-E93  CICS Transaction    Yes
           Facility for                  Server for z/OS
           CICS/ESA                      V2
 
5655-B54  REXX for CICS       5655-147  CICS Transaction    Yes
                                         Server for
                                         OS/390 V1
 
5655-B54  REXX for CICS       5697-E93  CICS Transaction    Yes
                                         Server for z/OS
                                         V2
 
5696-582  CICS Transaction    5655-147  CICS Transaction    Yes
           Affinities                    Server for
           Utility                       OS/390 V1
 
5696-582  CICS Transaction    5697-E93  CICS Transaction    Yes
           Affinities                    Server for z/OS
           Utility                       V2
 
5655-147  CICS Transaction    5697-E93  CICS Transaction    Yes
           Server for                    Server for z/OS
           OS/390 V1                     V2
 
5697-E93  CICS Transaction              To a follow-on,     NA
           Server for z/OS               if any
           V2

Warranted: Yes

Licensed Program Materials Availability

  • Restricted Materials of IBM: Some
  • Non-Restricted Source Materials: Some
  • Object Code Only (OCO): Some

Publication that identifies OCO components: CICS Transaction Server for z/OS Release Guide (GC34-5701)

Availability Date: Available at announcement

Testing Period: Two months (Basic license only)

Program Services

Support Center applies:                 Yes
 
                                        Access available through
                                         the IBM Support Center
 
Available until discontinued:           12-months written notice

However, for CICS TS V2.1, the notice is given with this announcement. Refer to statement of program currency.

Delivery of service for the components of this product which run on Windows NT is by download over the Web. To locate service updates for these, go to:

Program services for the subset of WebSphere Application Server Advanced Edition V3.5, delivered with this product, may be requested via CICS service.

Program Currency: CICS Transaction Server for z/OS Version 2 Release 1. Available until June 30, 2002.

Support Line: Yes

Prices

The prices provided in this announcement are suggested retail prices for the U.S. only and are provided for your information only. Dealer prices may vary, and prices may also vary by country. Prices are subject to change without notice. For additional information and current prices, contact your local IBM representative.

Growth Opportunity License Charge

                                                          GOLC
                                                          Monthly
GOLC                       Feature                        License
Category                   Number                         Charge
 
H30                        0025                           $5,167
H50                        0026                            6,332
H70                        0027                            8,662

Parallel Sysplex License Charge

                                             Feature
Description                MSU Capacity      Number       Charge
 
PSLC Base, 1 MSU           1                 0001         $1,489
PSLC Base, 2 MSUs          2                 0002          2,841
 
PSLC Base, 3 MSUs          3                 0003          4,468
 
 
PSLC Level A, 1 MSU        4 -- 45           0004            233
PSLC Level A, 42 MSUs                        0005          9,786
 
PSLC Level B, 1 MSU        46 -- 175         0006            100
PSLC Level B, 10 MSUs                        0007          1,000
PSLC Level B, 50 MSUs                        0008          5,000
 
PSLC Level C, 1 MSU        176 -- 315        0009             75
PSLC Level C, 10 MSUs                        0010            750
PSLC Level C, 50 MSUs                        0011          3,750
 
PSLC Level D, 1 MSU        316 or more       0012             56
PSLC Level D, 50 MSUs                        0013          2,800

Entry Support License Charge

                           Feature
Description                Number            OTC
 
Entry End User/390
 Entry Support License:    0024              $11,960

Variable Workload License Charges

VWLC                                         VWLC
Feature                                      Feature      VWLC
Description                                  Number       Charge
 
Base, Level 1 includes 45 MSUs               0028         $15,773
 
Additional qty, Level 1
 up to 175 MSUs                              0029             110
 
Additional qty, Level 2
 176 -- 315 MSUs                             0032              83
 
Additional qty, Level 3
 316 -- 575 MSUs                             0034              62
 
Level 3, Per 50 MSUs for machine
 capacity of 316 -- 575 MSUs                 0036           3,100
 
Additional qty, Level 4
 576+ MSUs                                   0038              62
 
Level 4, Per 50 MSUs for machine
 capacity of 576+ MSUs                       0040           3,100

Usage License Charge

                                             Feature
Description                                  Number       Charge
 
 
0 to 0.25 MSU Base                           0015         $ 1,489
0.26 to 0.5 MSU Base                         0016           2,841
0.51 to 1.0 MSU Base                         0017           4,704
 
Level A Chg/MSU (2 to 11 MSUs)               0018             934
Level B Chg/MSU (12 to 44 MSUs)              0019             400
Level C Chg/MSU (44 to 78 MSUs)              0020             300
Level D Chg/MSU (Above 78 MSUs)              0021             225
Level D per 50 MSUs (Above 78 MSUs)          0022          11,250

Entry Support License OTC: An OTC authorizes use only on IBM Entry End User/390 machines.

Order Now

 Use Priority/Reference Code: LE001
 
 Phone:     800-IBM-CALL
 Fax:       800-2IBM-FAX
 Internet:  ibm_direct@us.ibm.com
 Mail:      IBM Atlanta Sales Center
            Dept. LE001
            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

 
WebSphere, IMS, MVS, TXSeries, ClusterProven, MVS/ESA, C/370, and VSE/ESA are trademarks of International Business Machines Corporation in the United States or other countries or both.
 
CICS, CICS/ESA, DB2, OS/390, VisualAge, Parallel Sysplex, DB2 Universal Database, SecureWay, RACF, CICSPlex, VTAM, System/390, AnyNet, AIX, Extended Services, Language Environment, S/390, MQSeries, OS/2, SAA, Sysplex Timer, ESCON, AD/Cycle, IMS/ESA, CICS/MVS, CICS/VSE, Systempac, ProductPac, and BookManager are registered trademarks of International Business Machines Corporation in the United States or other countries or both.
 
Windows, Windows NT, and Microsoft are trademarks of Microsoft Corporation.
 
Java is a trademark of Sun Microsystems, Inc.
 
UNIX is a registered trademark is a registered trademark of the Open Company in the United States and other countries.
 
Tivoli is a registered trademark of International Business Machines Corporation or Tivoli Systems Inc. in the United States or other countries or both.
 
Other company, product, and service names may be trademarks or service marks of others.