IBM United States
Software Announcement 201-354
December 4, 2001

IBM CICS Transaction Server for z/OS V2.2 Delivers Major Value to All CICS Customers

 ENUS201-354.PDF (160KB)


At a Glance

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

  • Facilities to support applications written in Java, and for reuse or incorporation of existing applications and data within these applications
  • Support for session beans conforming to the J2EE Enterprise JavaBeans (EJB) 1.1 architecture
  • Extensions to the capability and facilities for applications based on procedural programming models
  • Enhancements to the facilities for network connectivity in support of e-business enablement
  • Improvements to application availability
  • Enhancements to CICS DB2 performance and usability
  • Significant enhancements to systems management

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. Leading functions are support for Java™ SDK 1.3, and support for session beans conforming to the J2EE Enterprise JavaBeans (EJB) 1.1 programming model. CICS also provides a range of important functions that can be used by applications written in other programming styles.

CICS TS V2.2 is recommended for all CICS customers, for deployment in large-scale production. For customers not planning to exploit Java, CICS TS V2 provides important enhancements in a wide range of areas. Functions to aid efficient application development include an enhanced 3270 bridge, an integrated CICS translator for use with COBOL and PL/I, CICS COBOL and PL/I XML application capability, and enhancements to function shipping of remote file requests. Improvements to connectivity include support for external call interface (ECI) over TCP/IP, improved CICS exploitation of TCP/IP services, connection optimization, and support for VTAM® LU alias facility. Enhancements in the area of availability include sign-on retention for persistent sessions, automatic restart of CICS data-sharing servers, and system-managed rebuild of coupling facility structures. DB2® users benefit from the CICS-DB2 performance improvements, DB2 group attach, and the RMI purge option. Standard CICS systems management facilities for the new functions are provided along with significant additions to CICS monitoring and statistics. Enhancements to CICSPlex® SM include workload management for most new functions, important communications improvements, a remote MAS agent for Windows®, and usability enhancements to the Web user interface.

Key Prerequisites

CICS Transaction Server for z/OS Version 2 Release 2 requires OS/390® Version 2 Release 10, or later.

Planned Availability Date

January 25, 2002

Description

CICS Transaction Server for z/OS Version 2 (CICS TS V2) delivers major enhancements that strengthen its support for e-business applications. Leading functions are support for Java SDK 1.3, and support for session beans conforming to the J2EE Enterprise JavaBeans (EJB) 1.1 programming model. CICS also provides a range of important functions that can be used by applications written in other programming styles.

CICS TS V2.2 is recommended for all CICS customers, for deployment in large-scale production. For customers not planning to exploit Java, CICS TS V2 provides important enhancements in a wide range of areas. Functions to aid efficient application development include an enhanced 3270 bridge, an integrated CICS translator for use with COBOL and PL/I, CICS COBOL and PL/I XML application capability, and enhancements to function shipping of remote file requests. Improvements to connectivity include support for external call interface (ECI) over TCP/IP, improved CICS exploitation of TCP/IP services, connection optimization, and support for VTAM LU alias facility. Enhancements in the area of availability include sign-on retention for persistent sessions, automatic restart of CICS data-sharing servers, and system-managed rebuild of coupling facility structures. DB2 users benefit from the CICS-DB2 performance improvements, DB2 group attach, and the RMI purge option. Standard CICS systems management facilities for the new functions are provided along with significant additions to CICS monitoring and statistics. Enhancements to CICSPlex SM include workload management for most new functions, important communications improvements, a remote MAS agent for Windows, and usability enhancements to the Web user interface.

For a full description of the functions delivered in CICS TS V2, refer to Functions Delivered in CICS TS V2.2 below.

A description of EJB technology and its benefits is given in the Enterprise JavaBeans — Overview section.

CICS TS V2.2 is intended for high-volume production both for customers wishing to exploit Java and EJB technology, and for those whose main emphasis is on applications based on procedural programming models. CICS TS V2.2 is the replacement for CICS TS V2.1, CICS TS V1.3, and earlier releases of CICS; it is the recommended migration target for all CICS customers. CICS TS V2.2 provides an evolutionary path, enabling customers to enhance their installations by adopting new technology at their own pace. The limitations that applied to CICS TS V2.1 do not apply with this release: CICS TS V2.2 is delivered through customized offerings; and it does not have an early discontinuance of program services.

The capabilities for Java and EJB technology in CICS TS V2.2 include support for Java SDK 1.3 and the new persistent, reusable JVM, providing enhancements to robustness and integrity. A full implementation of the EJB 1.1 security specification is delivered. Use of a Lightweight Directory Access Protocol (LDAP) server, available with the operating system, is supported for Java Naming and Directory Interface (JNDI). Standard WebSphere™ EJB deployment tooling is exploited, in place of the product-specific tools provided with CICS TS V2.1. Extensive scenario testing has been carried out to ensure the reliability of the new function meets CICS's established standards of integrity for production use of business-critical applications. There are improvements to serviceability including, for example, generating trace information at more trace points.

Accessibility by People with Disabilities

The following features support use by people with disabilities:

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

The Information Center has been tested and is accessible for use by people with visual, physical, or hearing impairment. The test included using accessibility aids such as screen readers. The Information Center incorporates features which have been designed for users with visual impairment. Syntax diagrams may be displayed in three different formats, two of which are accessible, one of which has been specially designed for visually impaired users. Diagrams may be viewed as a textual description or in the original diagrammatic form. Some information with restricted distribution or limited application is not supplied in a format designed for accessibility. This information is available on request in an accessible format: refer to the Information Center.

The CICSPlex SM Web user interface has been updated to provide enhanced accessibility.

REXX Development System for CICS/ESA®, REXX Runtime Facility for CICS/ESA, and CICS Application Migration Aid Version 1.1 have been tested and are accessible for use by people with visual, physical, or hearing impairment. The tests included using accessibility aids such as screen readers.

Note: Some accessibility features may not be available in the bundled product WebSphere Application Server, Advanced Single Server Edition V4.0.

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.

Product Positioning

CICS is IBM's premier transaction processor for the z/OS and OS/390 environments, enabling thousands of enterprises to run business-critical workloads totalling billions of transactions per day, with a financial value of trillions of dollars. Many of these 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 TS V2 continues to provide an efficient and effective environment for applications written in COBOL, PL/I, C, C++, and other languages. This version strengthens application development capabilities, enables enhanced re-use of 3270 applications, and enables applications to manipulate XML directly.

CICS support for Java has evolved through a number of stages. With Version 2, CICS TS now provides a robust, high-performance environment for enterprise applications written in Java. Its exploitation of the innovative persistent, reusable JVM, together with an architecture providing a separate JVM for each of the transactions running in a CICS region, ensures that Java applications have a high degree of isolation from each other, while achieving execution speed which is comparable with that of procedural languages. A range of Java services enables applications to exploit the strengths of CICS via open Java Enterprise APIs. VisualAge® for Java and WebSphere Studio may be used to develop these applications and deploy them under CICS; no special tools are needed.

By supporting EJB session beans, CICS provides another dimension for application architects. Stateful session beans may be seen as a contemporary equivalent of pseudo-conversational programs and are suitable for a wide range of applications. The technology also enables transactional peer-to-peer interoperation with WebSphere Application Server using IIOP and may be used as an advanced connector. By exploiting the WebSphere EJB Container, CICS enables construction of re-usable business logic components, which are binary portable between CICS and WebSphere and may be deployed in either environment using the same tools. Where an EJB component needs to incorporate procedural logic modules to accomplish its business function, CICS enables this mixed-language component to run in a single execution environment with good isolation from other components, improving robustness and manageability.

CICS supports those parts of the IBM Framework for e-business and the Java 2 Enterprise Edition (J2EE) specification that are appropriate to its role as a server for core transactional business logic. It provides a run-time environment optimized for business logic written as enterprise beans that 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 enterprise beans to run simultaneously in the same managed run-time environment as, for example, traditional 3270-based applications, CICS enables the same operations personnel to support multiple styles of application.

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

  • Efficient and optimized extension and re-use of existing CICS applications and business logic
  • Enterprises with a strong investment in CICS skills and infrastructure to create applications using new technologies by building on those skills
  • Support of mixed application types and workloads within a single CICS system
  • Re-use of existing DB2, IMS DB, and VSAM data from Java and EJB applications

Hardware and Software Support Services

SmoothStart™/Installation Services

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 specialists 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 the MVS™ logger
  • Changes in startup, shutdown, and recovery operations of CICS regions
  • Evaluation of CICS resource definitions
  • Assessment of applications that use the CICS Web support
  • Evaluation of 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 this 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 specialists 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
  • Demonstration of the 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 this CICSPlex SM Installation Plan.

For general information on IBM Global Services, go to:

For services for CICS, go to:

Reference Information

For the original announcement of CICS Transaction Server for z/OS Version 2, refer to Software Announcement 201-060 , dated March 13, 2001.

For information on WebSphere Application Server, Advanced Single Server Edition V4.0, refer to Software Announcement 201-198 , dated June 26, 2001.

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 WebSphere Application Server V4.0.1 for z/OS and OS/390, refer to Software Announcement 201-265 , dated September 25, 2001.

For information on CICS Transaction Gateway Version 4.0, refer to Software Announcement 201-187 , dated June 26, 2001.

For information concerning withdrawal from marketing and duration of program services on CICS Universal Clients Version 3 and CICS Transaction Gateway Version 3, refer to Withdrawal Announcement 901-248 , dated October 2, 2001.

For information on CICS Interdependency Analyzer for z/OS and OS/390, refer to Software Announcement 201-339 , dated November 27, 2001.

For information on CICS Performance Analyzer for OS/390 V1.1, refer to Software Announcement 201-143 , dated May 8, 2001.

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

For information on Enterprise COBOL for z/OS and OS/390 V3R1, refer to Software Announcement 201-343 , dated November 27, 2001.

For information on Enterprise PL/I for z/OS and OS/390 V3R1, refer to Software Announcement 201-344 , dated November 27, 2001.

CICS Web Pages

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

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

Trademarks

 
z/OS, WebSphere, IMS, SmoothStart, and MVS are trademarks of International Business Machines Corporation in the United States or other countries or both.
 
CICS, VTAM, DB2, CICSPlex, OS/390, CICS/ESA, VisualAge, and MQSeries are registered trademarks of International Business Machines Corporation in the United States or other countries or both.
 
Windows is a registered trademark of Microsoft Corporation.
 
Java is a trademark of Sun Microsystems, Inc.
 
Other company, product, and service names may be trademarks or service marks of others.

Functions Delivered in CICS® TS V2.2

The following are the principal new functions provided in CICS TS V2.2. Some of these functions, although not previously delivered, were described in the previous announcement of March 2001. Others of these functions already described in that announcement were delivered in CICS TS V2.1; these functions are indicated by an asterisk.

Enhanced Java™ Support

CICS support for Java has been dramatically enhanced. Firstly, the level of Java supported has been upgraded to Java 2 at SDK V1.3.1 level. Secondly, CICS exploits a completely new Java Virtual Machine (JVM) specially designed to optimize performance for short running programs such as CICS transactions. Thirdly, support for Java Enterprise APIs such as JDBC, JNDI, and RMI has been significantly enhanced. Fourthly, CICS applications can now use the Common Connector Framework (CCF) client API to allow portability between CICS and non-CICS servers of Java application classes that invoke CICS programs.

CICS Support for the Persistent, Reusable JVM: Support for the JVM has moved forward in CICS TS V2.2 to the IBM Developer Kit for OS/390®, Java 2 Technology Edition, V1.3.1, known as the persistent, reusable JVM. Note that, unlike the position with CICS TS V2.1, there is no requirement to install a special enhancement; the enhancement has been incorporated into this level of the JVM. The use of this JVM enables significant performance optimizations for any Java program running in CICS, including enterprise beans. The performance benefits accrue from two sources. Firstly, by serially reusing a JVM the initialization cost for a Java application is dramatically reduced. Secondly, by discarding all the application objects created by the Java program in one go, when the program terminates, the performance overhead of the more usual garbage collection mechanism is effectively eliminated.

The persistent, reusable JVM supports special techniques that enable system and middleware code to re-initialize the JVM before it is reused for the next Java program. This ensures that there can be no interference between the applications, or between programs running on behalf of different end users, that serially reuse the same JVM. CICS supports a set of JVM instances ready for use within each CICS address space and provides management of the pool of JVMs to optimize throughput and to allow Java classes to be replaced without requiring that CICS be restarted.

* SQLJ/JDBC Support: CICS Java applications can access DB2® data via the Java DataBase Connectivity (JDBC) and SQLJ APIs. The JDBC API uses the dynamic SQL model; the SQLJ uses the static SQL model. Support is provided via a type2 JDBC driver provided by DB2 for OS/390 at a JDBC 1.2 API level. The DB2 support has been upgraded to support the persistent, reusable JVM. 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.

* 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 has been extended to provide JDBC access to IMS DB data from Java applications running under CICS Transaction Server for z/OS™ Version 2. It requires IMS V7, with service applied, or IMS V8.

Java Naming and Directory Interface (JNDI): JNDI is a Java API 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. CICS TS V2.2 introduces support for a Lightweight Directory Access Protocol (LDAP) server as a JNDI service provider. An LDAP server with a CORBA object reference schema is required; the LDAP server in the SecureWay® Security Server, licensed as part of the base z/OS or OS/390 operating system, meets this requirement, and can provide support across a Parallel Sysplex®. Alternatively, a CORBA Object Services (COS) naming directory server can be used. WebSphere™ Application Server, Advanced Edition for Windows NT® V3.5, or later, meets the requirements (refer to the Software Requirements section). The use of the LDAP server available with the operating system enables simpler interoperation with WebSphere Application Server V4.0 for z/OS and OS/390, for example if using entity beans running under WebSphere, since both CICS and WebSphere can then use the same LDAP server.

* The CICS Connector for CICS TS: CICS TS V2 introduces the CICS Connector for CICS TS, providing an option for a Java program or 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 within the local system or to any CICS system that supports DPL, such as CICS/ESA® V4.1.

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, and later. Command beans generated by VisualAge for Java that use the CCF interface provided by CICS Transaction Gateway are binary portable to run under CICS TS V2.2 and use the CICS Connector for CICS TS. Other beans that use the underlying Java ECI interface can also be migrated to CICS TS V2.2.

As compared to the alternative of using the JCICS classes for a similar function, the CICS Connector for CICS TS has advantages: (a) 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.

* Enhancements to CORBA Interoperability: 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 is provided 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 Support

CICS TS V2.2 supports session beans at EJB 1.1 specification level. A description of the EJB architecture, and session beans in particular, is given below: refer to Enterprise JavaBeans — Overview . Enterprise beans run in a container. CICS uses the common WebSphere container exploiting collaborator classes that map the infrastructure services that the container needs to the underlying CICS functions. This common implementation helps ensure binary compatibility for enterprise beans deployed on any of the WebSphere application servers and on CICS TS V2.

Enterprise beans running in CICS can be developed using any application development tool that supports EJB 1.1. The enterprise beans are deployed using the standard WebSphere Application Assembly Tool. The enterprise bean developer does not need to have knowledge about the platform on which the bean will be executed and hence does not need any CICS expertise.

Enterprise beans running on CICS can use all the Java capabilities described in the previous sections as well as JCICS classes to exploit CICS functionality. Note, however, that use of the JCICS functions means that the bean will not be portable to non-CICS platforms. Use of the JCICS classes or CCF to LINK to an existing procedural program (written, for example, in COBOL) allows existing business logic to be exposed to the outside world as an enterprise bean. The client applications need not be aware that the enterprise bean's business logic is actually implemented in COBOL.

EJB Run-Time Functions

All of the above enhanced Java support capabilities may be used by those exploiting EJB technology. In addition, the following functions are specific to EJB support.

* Support for Enterprise Beans: CICS TS V2.2 supports session beans, written to the EJB 1.1 specification. It incorporates an EJB container derived from the EJB container in WebSphere Application Server. The use of this container enables binary portability of applicable enterprise beans developed with WebSphere for execution under CICS.

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.

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

Data Access Beans are a practical alternative to entity beans for access to data from enterprise beans running in CICS TS V2. These enable read and write access to data in relational databases that support the Java Data Base 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, which allows the visual composition of an SQL statement.

* 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 via a program written in, for example, COBOL, invoked by a JCICS link, or invoked using the CICS Connector for CICS TS. Refer also to JDBC Access to IMS section, above.

EJB Security: In CICS TS V2.2, the Java 2 security policy mechanism and the security specification of the EJB Version 1.1 architecture are supported. 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 is controlled by Java 2 security policies that can be customized by the user.
  • The security roles and method permissions in the deployment descriptor will be recognized and honored.

The EJB security solution in CICS TS V2.2 uses the System Authorization Facility (SAF) interface to exploit services of the SecureWay Security Server in z/OS and OS/390 (formerly the Resource Access Control Facility [RACF®]). This support requires APARs OW46859 and OW49190 to OS/390 or z/OS. 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

A new Java-based CICS utility is introduced to ease the administrative burden of defining profiles for the SecureWay Security Server.

In addition to EJB security as described above, CICS TS V2.2 provides a capability for security authentication of users accessing CICS over IIOP, providing secure interoperability between CICS and other IBM and non-IBM systems using the SSL client authentication protocol.

Note that when used with non-EJB applications, CICS TS V2.2 has the same security and auditability features as CICS TS V1.3. CICS transaction and resource security continue to apply when the CICS API is used, including the JCICS API.

Application Development and Deployment Functions in Support of EJB

EJB Support Tools: As indicated in the initial announcement, changes have been made in CICS TS V2.2 to further simplify and to provide common solutions with the WebSphere platform.

The tools provided in CICS TS V2.1 are not shipped with this release. The CICS JAR Development Tool for EJB Technology, CICS Development Deployment Tool for EJB Technology, and CICS Production Deployment Tool for EJB Technology are no longer required.

Introduced in this release is the use of the Application Assembly Tool (AAT). This is a general tool also used by members of the WebSphere Application Server V4.0 family (but note that this is not the same tool as that referred to as the AAT in WebSphere Application Server V4.0 for z/OS and OS/390). This is a workstation-based tool running on Windows NT or Windows® 2000; it is used to build JAR files ready for the run-time environment, and is required in order to prepare enterprise beans for installation into the CICS TS V2.2 system. The tool allows users to define the contents of the JAR file by indirectly editing the deployment descriptor, and will then produce the generated code required to run in an EJB environment. The AAT is shipped as a component of WebSphere Application Server, Advanced Single Server Edition V4.0, which is included for this purpose as an element of CICS TS V2.2. Note that V4.0.1 is the minimum required level; this is the level shipped with CICS TS V2.2.

A new tool is supplied as part of CICS TS V2.2. The resource manager for enterprise beans is a Web-based tool that gives an application developer the ability to work with EJB resources in CICS without having to use a CICS terminal. It provides access to the common functions associated with CorbaServers and DJARs, gives diagnostic information for DJARs that have not been correctly installed, and offers information about the naming server and beans that are published to it.

For use of 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 to a JVM of a remote debugger that conforms to JPDA, such as IBM Distributed Debugger V9.1, or later.

CICS EJB Samples: Three EJB samples are shipped with CICS TS V2.2. One is simple, and is intended for use for installation verification purposes. The second is based on the first, but includes Web components that can be installed in a J2EE Web Application Server, such as WebSphere Application Server Version 4.0.

The third 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 J2EE Web Application Server, such as the shipped WebSphere Application Server, Advanced Single Server Edition V4.0.

Systems Management Functions Supporting EJB

A number of new CICS resources have to be defined to implement support for enterprise beans. In particular a new resource, known as a CorbaServer, has to be defined to specify the properties of the container. In addition the deployed JAR files can be pre-defined or installed automatically. The enterprise beans in a deployed JAR file can be published to the JNDI namespace either explicitly or automatically by requesting the AUTOPUBLISH option on the CorbaServer definition. These resources are defined and managed using the usual CICS RDO, SPI, and CEMT functions. The method request executed by the enterprise bean runs under a CICS transaction ID and is associated with a standard CICS user ID. Hence the usual CICS security and monitoring mechanisms apply to enterprise bean invocations just as they do for procedural CICS transactions. This approach allows existing operational procedures to continue to be used when using enterprise beans and removes the need for the system programmers to have a detailed understanding of the EJB architecture.

Two new CICS-supplied transactions are introduced:

  • CREA gives system programmers a view of the beans and methods within a JAR file and offers them the ability to associate those beans and methods with CICS transaction IDs. The tool will take into account any installed definitions to supply default values for the transaction IDs, which the user is then free to modify. The result of the associations is the generation of an optimum list of REQUESTMODELs that will lead to incoming requests for beans within that JAR file using the transaction IDs specified using the tool. The REQUESTMODELs generated can be installed directly into CICS, written to the CSD, or both. This tool removes the need for a system programmer to derive REQUESTMODEL definitions and enter them using CEDA.
  • CREC is a read-only version of CREA. It offers a view of the JAR file and the associations implied by installed REQUESTMODELs. It does not offer the user the ability to change the associations or generate REQUESTMODELs.

In addition, a new Java-based CICS utility is introduced to ease the administrative burden of defining profiles for the SecureWay Security Server.

CICS Transaction Server for z/OS Version 2 incorporates a new version of CICSPlex® System Manager. This 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, and related actions 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
  • 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 to enterprise beans the distributed routing program model introduced in CICS TS V1.3. All existing facilities provided by CICSPlex SM in this context, such as workload separation and application availability, are provided for enterprise bean invocation. The customer can write a user-replaceable module to customize the routing logic.

In 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 CICSPlex SM workload management is compatible with, and complementary to, MVS™ TCP/IP connection balancing across multiple listener regions.

New Facilities for CICS Exploitation of Procedural 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 Debug Tool 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.

Refer to the Software Requirements section for details of the necessary levels of the COBOL and PL/I products required for this function. Lower levels of these compilers continue to be supported, but without the benefits of the Integrated Translator.

CICS COBOL and PL/I XML Application Capability: The CICS COBOL and PL/I XML Application Capability provides the capability to parse XML documents directly in CICS COBOL and PL/I applications. The XML Enabler for COBOL and PL/I can be used to enhance your existing high-performance CICS transactions written in COBOL and PL/I in a B2B environment by supporting XML document interchange. CICS supports the transmission of XML documents in the data portion of a CICS message.

This capability is being provided through COBOL and PL/I and supports CICS TS V1.3 as well. It requires IBM Enterprise COBOL for z/OS and OS/390 Version 3, or IBM Enterprise PL/I for z/OS and OS/390 Version 3. These compilers also support data encoded in the various Unicode formats, and supply methods for conversion either way between these formats and EBCDIC.

3270 Bridge Enhancements: The CICS 3270 bridge was introduced in CICS Transaction Server for OS/390 Version 1 Release 2, and enhanced in CICS TS V1.3. It was used as the basis for the CICS Web bridge, which maps the output of 3270 applications to HTML data in conjunction with the facilities of CICS Web Support. It has now been used as the basis for a LINK interface to the 3270 bridge that allows a 3270 transaction (that meets certain requirements) to be driven using client ECI, host EXCI calls, and DPL or LINK. This provides an alternative to 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 systems using the local or remote (DPL) EXEC CICS LINK interface, are now supported. It may be used in conjunction with the new support for ECI over TCP/IP.

Other new functions introduced include the ability to workload balance transactions using the bridge environment in a CICSplex, the capability of renaming the bridge facility TERMID, and a new SPI for managing bridge facilities.

Load Module Scanner: The Load Module Scanner (which was made available for CICS TS V1.3 in November 2000 via the service channel but was not included in CICS TS V2.1) makes available 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 that will determine those programs that will not work under the CICS 3270 bridge. Another filter table is provided of commands that may cause programs not to be threadsafe. This function can also employ user-defined filter tables, allowing it to be used for any other purposes required by the user.

* 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 Business Transaction Services (BTS) repository, can now be shared across multiple regions without the requirement to use RLS.

* CICS Web Bridge Enhancements: A range of enhancements to the CICS Web bridge removes a number of limitations and allows it to support a larger subset of current 3270 and BMS applications. These enhancements include:

  • Support for dynamic changing of BMS field attributes.
  • Support for multiple maps. Multiple maps in a single screen image are correctly positioned; and where maps overlap, a best effort is made to generate a satisfactory image.
  • Retention of map to support the SEND MAP DATAONLY command.
  • Changes to terminal control support to improve performance and to allow BMS and terminal control commands to be mixed in the same application.
  • Support for the RECEIVE BUFFER command and 3270 structured fields.
  • Improvements to diagnostic facilities, particularly in 3270 terminal control.
  • 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.

* 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).

* 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 user ID 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 user ID and password with the HTTP basic authentication protocol, and if these are successfully validated, the client certificate is automatically registered to that user ID. 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.

* CICS — Language Environment® Enhancements: A range of changes has improved the function of CICS with Language Environment, principally in the areas of usability, serviceability, and performance. Required levels of Language Environment apply to these items.

Usability enhancements include:

  • Language Environment and CICS diagnostics placed together in the transaction dump
  • Fewer trace entries caused by taking a dump, so the trace table is more useful
  • Formatting of some Language Environment control blocks in a CICS transaction dump
  • 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

Serviceability improvements include:

  • Integration of Language Environment and CICS IPCS verb exits
  • Extensions to some CICS trace points to trace the application's register save area

Performance enhancements include:

  • Dynamic storage tuning controlled by a new SIT option AUTODST

VSAM Control Interval Deadlock Avoidance: An enhancement to file control is included in CICS TS V2.2 that removes the risk of unanticipated deadlocks due to access to records that reside in the same VSAM control interval.

Enhancements to Network Connectivity for e-business Enablement

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

ECI over TCP/IP: This 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 directly with CICS on System/390®, clients have had to use SNA LU6.2, or use TCP62 (APPC over TCP/IP) support with the AnyNet® feature of SecureWay Communications Manager for OS/390. The use of native TCP/IP directly into CICS removes the need for the AnyNet feature of SecureWay Communications Manager for OS/390, and any SNA configuration on z/OS or OS/390, and thereby simplifies the administration of large networks of clients. No change is required to the client or to the server applications.

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

* Enhancements to CICS Exploitation of TCP/IP Services: Enhancements are included in CICS TS V2 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 (MAXSOCKETS) 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 that initiates a receive request on an IP connection to continue to execute concurrently.
    • Shared sockets, created by one task and remaining active for a number of tasks.

These enhancements 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 predefined LU aliases. VTAM LU alias facilities provide improved connectivity and interoperability 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 (not APPC synclevel 2), 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 (netnames), can interconnect without creating any problems because of the duplicate netnames. This facility can be beneficial, for example, for organizations that offer bureau services.

Improved Application Availability

Enhanced DB2 Facilities

CICS-DB2 Performance: The CICS-DB2 Attachment Facility is enhanced in the level shipped with CICS TS V2.2 to exploit CICS open transaction environment (OTE) function. When CICS TS V2.2 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, and defined to CICS as threadsafe, may benefit from reduced TCB switching. For threadsafe applications making heavy use of EXEC SQL, the reduced TCB switching should provide a significant performance improvement.

DB2 Group Attach: This new function allows a CICS customer to exploit the DB2 facility whereby the name may be specified as 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, with APARs PQ44614, PQ45691, and PQ45692.

DB2 Exploitation of the RMI Purge Option: A new Resource Manager Interface (RMI) purge option is introduced in CICS TS V2.2. This allows the writer of a task-related user exit (TRUE) to specify whether, before calling it, the RMI should defer purge and deactivate runaway. This offers an operational enhancement by making it easier to recover from system stall situations in CICS. The CICS-DB2 Attachment Facility uses the new RMI purge option when CICS is connected to DB2 V6 or higher; this allows applications waiting in DB2 to be purged from CICS. Previously only forcepurge, with its danger of loss of integrity, was supported.

Enhanced Support for CICS Data-Sharing Servers

* 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 temporary storage data sharing 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 startup, 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: 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, namely temporary storage, coupling facility data tables, and named counter servers. This facility exploits the Cross-System Extended Services® (XES) system-managed rebuild support included in the operating system. For OS/390 V2.10 and z/OS V1.1, OS/390 or z/OS APAR OW39892 must be installed. No APAR is required for z/OS V1.2, or later.

A further benefit enabled by this function is system-managed coupling facility structure duplexing (refer to following item).

System-Managed Coupling Facility Structure Duplexing: CICS shared temporary storage queues, coupling facility data tables, and named counters can now be protected by system-managed coupling facility structure duplexing. This means that, in the event of a failure of a coupling facility, CICS applications using these servers continue to operate. This facility requires z/OS V1.2, with an enabling PTF — refer to z/OS information.

Sign-on Retention for Persistent Sessions: 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 the CICS catalog at the time of sign-on and sign-off. This enables it to retain a terminal's sign-on status across a failure in either CICS or VTAM, and to sign the user on again at reconnection.

The conditions under which a user sign-on status is restored 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).

Checking Availability of MVS Logger: The overhead in checking that the connection to the MVS logger is still available has been dramatically reduced.

Systems Management Enhancements

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

Also introduced is a facility to enable unattended installation of a CICS for OS/2® remote MAS Agent.

CICSPlex SM Communications Enhancements: The communication (COMS) component of CICSPlex SM is a highly sophisticated component that provides transportation of requests and their responses across the MAS/CMAS network. It is built to cope with a dynamically changing network topology across multiple protocols. Fundamental to this is the concept of a ring between two CMASs (one session outbound; one inbound). In this release, various enhancements have been made to ring initialization and termination logic to cope with normal ring activation and various failure scenarios, which will provide increased resilience of the ring and consequently enhanced availability of the COMS component.

Improvements have also been made to storage management for ring initialization: large highly interconnected CMAS networks have been exposed to the possibility of consuming storage when the entire network is simultaneously restarted, and high usage at run time can also cause this effect. Storage allocated during this process previously was held on to for the life of the CMAS, providing the potential for other tasks to go short on storage (SOS). With this release, a new dynamic storage algorithm is incorporated that will reduce the likelihood of an SOS condition in the CMAS, and provide active management of an SOS condition in the event of an SOS being experienced in the CMAS.

The appearance of the CICSPlex SM Web user interface is improved * . Usability is enhanced by preventing 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.

* CICSPlex SM Business Application Services (BAS) Integration: 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."

Other Benefits of CICS TS V2.2

Monitoring and Statistics Changes: Extensive changes and additions have been made to CICS monitoring data and statistics in CICS TS V2.2. These include:

  • The CICS statistics utility program now provides additional resource type options that allow selection of the global types of statistics data, to reduce the size of statistics reports when an overview is required.
  • The CICS sample statistics program has been enhanced * to support the new functions of CICS TS V2. In addition, it is now shipped as pregenerated executable code (as well as in COBOL source code), allowing it to be installed as supplied. The program may be invoked from a 3270 terminal or from a browser (using the CICS Web Support).
  • New system initialization parameters allow the user to specify statistics settings during CICS startup.
  • New performance class data fields are added in support of Open Transaction Environment, JVM, TCP/IP support, and CICS Web support.
  • There are new CICS statistics for CorbaServer resources and request model resources, and new global statistics for the JVM pool, TCP/IP support, and the CICS log manager.

* Information Center: 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.

* Advanced ClusterProven™: CICS TS V2 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 TS V2 satisfies and exceeds the required technical criteria for this status. More information is available on the Web at:

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

The base CICS element of CICS TS V2.2 is CICS V6.2. The CICSPlex System Manager element of CICS TS V2.2 is CICSPlex SM V2.2. CICS TS V2.2 also includes the following elements:

  • REXX Development System for CICS/ESA
  • REXX Runtime Facility for CICS/ESA
  • CICS Application Migration Aid Version 1.1
  • WebSphere Application Server, Advanced Single Server Edition V4.0

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

Note that the WebSphere Application Server, Advanced Single Server Edition V4.0 is licensed under the IBM International Program License Agreement (IPLA), and is delivered with IPLA licensing materials. For the conditions that apply to this element, refer to the Terms and Conditions section.

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)
  • Media Pack: WebSphere Application Server, Advanced Single Server Edition for Multiplatforms V4.0 (includes IPLA licensing material)
  • Proof of Entitlement for installation in five processors of WebSphere Application Server, Advanced Single Server Edition for Multiplatforms V4.0

Note that no complementary products are packaged with this product. CICS VSAM Recovery V2.3, MQSeries® Integrator Agent for CICS Transaction Server V1.1, and CICS Transaction Gateway V4.0 are all available separately. Further information concerning CICS VSAM Recovery and CICS Transaction Gateway is given later in this announcement.

Tivoli® Agent: Note that the Tivoli agent that was shipped as part of CICS TS V2.1 is no longer shipped with CICS TS V2.2, because it is shipped as part of Tivoli Business Systems Manager (5698-BSM). (This agent exploits the CICSPlex SM API to provide CICS management data to Tivoli Business Systems Manager; the latter provides the ability to launch the CICSPlex SM Web user interface.)

Enterprise JavaBeans — Overview

There are many advantages to the use of EJB technology. It provides the benefit common to all Java development of easy portability between different platforms, and further, it allows portability between different EJB-compliant transaction management products. Such a product is called an EJB server (sometimes known as Enterprise Java Server [EJS], or Enterprise Server for Java [ESJ]). 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 from small-scale to large-scale environments.

All functions provided by CICS TS V2 for the support of EJB are in accordance with the J2EE Enterprise JavaBeans architecture, Version 1.1, as defined by Sun Microsystems, Inc. This specification, the Enterprise JavaBeans Specification, V1.1, Final Release, 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.2. Many of these details are internal, and concern the mapping of the functions defined by the EJB architecture to the existing tried and tested services of CICS. CICS TS V2.2 also provides extensive facilities for integration of existing functions with new applications developed using the EJB programming model. It supports session beans compliant with this specification.

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 nontransactional environment, a JavaBean is a reusable software component, written in Java, that 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 programming model. This contrasts with an application program written, for example, in COBOL or C, to the CICS programming model.

An EJB server 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.2 using the Internet Inter-ORB Protocol (IIOP); management services, which are provided by an EJB container; a distributed transaction management service; and security services.

An 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 rules. These functions are performed by the container on its behalf.
  • Transaction management. The 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.2).

Enterprise beans are deployed into an EJB server. For this to happen, in the case where CICS is the EJB server, their execution environment is known as a CorbaServer, and is configured by a CorbaServer resource definition.

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 specifies the enterprise bean that it will use. The client can create, remove, and (for entity beans only, see 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 requirements 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 use container-managed transactions.

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

  • An entity bean (not directly supported by CICS TS V2.2) 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 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.

The processes required for the deployment of enterprise beans into an EJB server are performed with the aid of tools for the purpose. A Java Archive (JAR) file can contain one or more Java beans, of different sorts, including enterprise beans. Where these Java beans are enterprise beans, the JAR file 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 has a standard format and includes 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 "deployed JAR file," which means they include generated code specific to the CICS EJB container 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 in which it is made known to, and hence runnable in, a particular EJB server.

Additional Information

CICS Transaction Gateway V4.0.1: The CICS Transaction Gateway V4.0.1 will be shipped on December 31, 2001. This includes support for the J2EE Connector Architecture 1.0 specification, previously made available as a beta. This specification is an industry standard interface, published on September 17, 2001, and derived from IBM's Common Connector Framework (CCF) which was introduced with VisualAge for Java. For more information on CICS Transaction Gateway Version 4.0, refer to Software Announcement 201-187 , dated June 26, 2001.

Service for CICS Universal Clients V3.1: As announced on October 2, 2001, program services for CICS Universal Clients Version 3.1 are extended, and will now be available until December 31, 2002. For more information, refer to this announcement as listed in the Reference Information section, above.

CICSPlex SM V1.3: Note that, as announced on August 7, 2001, CICSPlex System Manager for MVS/ESA™ Version 1 Release 3 will be withdrawn from marketing effective December 31, 2001, and its service will be discontinued effective December 31, 2002.

CICS VSAM Recovery: IBM plans to make a new version of CICS VSAM Recovery (CICSVR) available soon. Specific availability dates, ordering information, and terms and conditions will be provided when the product is announced.

  • CICSVR is designed to be an easy to use VSAM recovery utility which can be used to recover VSAM data sets which are lost or damaged. CICS or batch VSAM data sets can be recovered.
  • CICSVR will have VSAM batch logging for VSAM data. Changes made to VSAM data sets by batch applications can be logged to a z/OS or OS/390 log stream. CICSVR can use the log records to help recover the VSAM data.
  • Change accumulation processing will be available. Forward recovery log records can be consolidated into change accumulation data sets. CICSVR can use change accumulation data sets to help speed up forward recovery.
  • Complete forward recovery automation will be possible when the VSAM data set was backed up by DFSMShsm™ and/or DFSMSdss™.
  • VSAM Data Set selection filters on CICSVR PDF panels and Disaster/Recovery functions are two customer requirements that help enhance function and improve usability.

Education Support

Several new CICS Transaction Server for z/OS Version 2 training offerings are available now or will be available in 2002. Not all courses are available in all countries.

Available now, CICS Transaction Server for z/OS: EJB Support and More! is a no-charge Web-based course teaching the features and functions of CICS Transaction Server for z/OS Version 2. The course consists of audio, text, and graphics. The worldwide course code is CS04. You can access the course at:

Available in early 2002, CICS TS for OS/390 Transition: From V1 To V2 is a classroom course for system programmers who need information helpful for planning migrations from CICS TS V1.3 to CICS TS V2.2. Its worldwide course code is CI95, and most country course codes will be in the format CI95x, where "x" is one additional alphanumeric character.

Other CICS Transaction Server for z/OS Version 2 training available in 2002:

  • Fastpath for Migrating CICS/ESA Applications to CICS Transaction Server for z/OS V2 . This classroom course teaches students basic need-to-know information to transition a set of CICS/ESA applications to the latest release of CICS. It does not teach new functional enhancements, but concentrates on migrating existing applications. The worldwide course code is CI96.
  • Implementing Java Support in CICS . This classroom course teaches students how to enable Java support in CICS Transaction Server for z/OS, including how to configure an EJB container and how to deploy enterprise beans in the CICS environment. The worldwide course code is CI21.
  • Implementing the CICS Transaction Gateway . This classroom course teaches students to install and configure the CICS Transaction Gateway. The worldwide course code is CI71.

Application Development Training

If you are developing CICS Java applications, an important new course, CICS Application Programming with Java , is available in some countries. For general training on Java, Enterprise JavaBeans, and VisualAge for Java, customers are advised to review the IBM Learning Services Application Development curriculum.

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, call 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 are 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. This requires one or more coupling facilities with their associated coupling links installed, an IBM 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 by 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 Components: For the WebSphere Application Server, Advanced Single Server Edition V4.0 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 that are restricted to the single-byte character set (SBCS) Katakana part of code page 930.

Software Requirements

Note that the Program Directory (GI10-2543) will normally contain the latest level of information on software requirements, particularly concerning service levels of supported products.

Operating environment:

  • The minimum required level of operating system for CICS Transaction Server for z/OS Version 2 Release 2 is OS/390 (5647-A01) Version 2 Release 10. z/OS (5694-A01) at all release levels is also supported. 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.

  • For system-managed coupling facility structure duplexing, z/OS V1.2 is required, with an enabling PTF — refer to z/OS information.

  • Note that the Language Environment library SCEERUN must be available to CICS during CICS initialization, by inclusion in either the STEPLIB concatenation or the LNKLIST. Language Environment services are used by a number of CICS functions.

  • For Java application programs or for support of enterprise beans with CICS TS V2.2, the IBM Developer Kit for OS/390, Java 2 Technology Edition, V1.3.1 (5655-D35), known as the persistent, reusable JVM, is required.

  • Service updates to the operating system are required in order to run the persistent, reusable JVM. The required PTFs are listed at:

CICS TS V2.2 supports Java program objects. These are Java applications that have been compiled using the VisualAge for Java Enterprise Toolkit for OS/390 (ET/390) byte-code binder (sometimes called high-performance compiler for Java). However, for restrictions, refer to the Compatibility section.

For generating all Java programs for use with CICS TS V2.2, IBM VisualAge for Java V3.5 or V4.0, or WebSphere Studio Application Developer, is supported. For generating Data Access Beans, VisualAge for Java V3.5.3, or later, including WebSphere Studio Application Developer, is required.

The CICSPlex SM remote MAS agent for Windows may be used with TXSeries for Windows NT Version 4.3 (delivered in WebSphere Application Server Enterprise Edition for Windows NT), or later.

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)
  • IBM Enterprise COBOL for z/OS and OS/390 Version 3 (5655-G53)

The integrated translator function requires IBM COBOL for OS/390 and VM Version 2 Release 2, with APAR PQ45462, or Enterprise COBOL for z/OS and OS/390 Version 3.

PL/I products supported are:

  • 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)
  • IBM PL/I for MVS and VM Version 1 (5688-235)
  • IBM VisualAge PL/I for OS/390 Version 2 (5655-B22)
  • IBM Enterprise PL/I for z/OS and OS/390 Version 3 (5655-H31)

The integrated translator function requires VisualAge PL/I for OS/390, Version 2 Release 2.1, with APAR PQ45562, or Enterprise PL/I for z/OS and OS/390 Version 3.

C applications may be compiled using:

  • OS/390 C/C++ (5647-A01)
  • C/C++ for MVS/ESA (5655-121)

Translator support 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), OS PL/I Version 1 (5734-PL1), OS PL/I Version 2 (5668-910, also 5668-909), and SAA® AD/Cycle® C/370™ (5688-216) is withdrawn and is not available in this release. It is planned that run-time support for OS/VS COBOL programs (regardless of run-time library used) and for any other programs running under pre-Language Environment run-time libraries will be withdrawn from the next release.

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

  • IMS/ESA® Database Manager Version 6.1 (5655-158)
  • IMS Database Manager Version 7 (5655-B01)
  • IMS Database Manager Version 8 (5655-C56)
  • DB2 Server for OS/390 Version 5.1 (5655-DB2)
  • DB2 Universal Database Server for OS/390 Version 6.1 (5645-DB2)
  • DB2 Universal Database Server for OS/390 Version 7.1 (5675-DB2)

For SQLJ/JDBC support, DB2 Server for OS/390 Version 5.1 requires APAR PQ51845 (PTF UQ59529); DB2 Universal Database Server for OS/390 Version 6.1 requires APAR PQ51846 (PTF UQ59528); and DB2 Universal Database Server for OS/390 Version 7.1 requires APAR PQ51847 (PTF UQ59527).

The DB2 Group Attach function requires DB2 Universal Database for OS/390 Version 7.1, with APARs PQ44614, PQ45691, and PQ45692.

  • 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 necessary service applied (formerly Tivoli Performance Reporter for OS/390 [5695-101])
  • Tivoli Business Systems Manager (5698-BSM) Version 1.5
  • CICS Universal Clients Version 3.1.2, or later
  • CICS Transaction Gateway Version 3.1.2, or later
  • CICS Transaction Gateway Version 4.0
  • 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 APAR PN73189 must be applied to CICS/ESA V4.1.

  • MQSeries Integrator Agent for CICS Transaction Server Version 1.1

The minimum modification level of WebSphere Application Server, Advanced Single Server Edition V4.0, which provides the AAT tool, is V4.0.1.

The resource manager for enterprise beans requires Netscape 4, or later, or Microsoft™ Internet Explorer Version 4.0, or later, or a Web browser with equivalent function.

For the shipped WebSphere Application Server, Advanced Single Server Edition V4.0 (including the AAT tool):

  • Java requirements are provided in the package.
  • The required operating environment is Windows NT Server Version 4.0 with service pack 6a, or later, or Windows 2000 Server or Advanced Server with service pack 1, 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

JNDI support for enterprise beans requires either an LDAP server, such as the LDAP server provided in SecureWay Security Server and licensed as part of the base z/OS or OS/390 operating system, or a COSNaming server. If a COSNaming server is required, WebSphere Application Server, Advanced Edition V3.5, or later, may be used. (Note that the shipped WebSphere Application Server, Advanced Single Server Edition V4.0 is not recommended for this function in production use; it does not support object persistence when recycling the server.)

Compatibility

Changed Behavior of EXEC CICS SIGNON/SIGNOFF: In levels of CICS Transaction Server prior to Version 2.1, an EXEC CICS SIGNON or SIGNOFF command modified the user ID and security characteristics of the transaction issuing the command, as well as the transaction's terminal. However (as documented in the CICS Application Programming Reference), this way of handling SIGNON in a running transaction can lead to unpredictable behavior. Therefore, from CICS TS V2.1, this behavior has been changed to apply only to the terminal and not the currently executing transaction. A temporary migration aid is provided to allow customers who depend on the old behavior to restore it. For full details, refer to the CICS Transaction Server for z/OS Migration Guide . Note that: (a) this aid will be removed in a future release ; (b) should problems be encountered due to the potential inconsistencies in the old behavior, no action would be taken by IBM to correct these problems.

Java Levels: CICS TS V2.2 does not support JVM mode programs at levels of Java earlier than the 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 or V4.0 can be used. Note that they support the SDK 1.2 level, but applications developed using them can be deployed into a SDK 1.3 environment. WebSphere Studio Application Developer supports development at the SDK 1.3 level. Note also that enterprise beans developed using VisualAge for Java V3.5 or V4.0, which support the EJB 1.0 specification, need to be migrated to the EJB 1.1 specification level. This may be done using the Application Assembly Tool (AAT) supplied with CICS TS V2.2. Enterprise beans developed using WebSphere Studio Application Developer support the EJB 1.1 specification.

CICS Programs Running under the JVM: A JVM program cannot link, either directly or indirectly, to another JVM program in the same CICS region. The reason for this restriction is that CICS JVM programs run in separate, isolated JVMs as separate UNIX® System Services (USS) processes, and USS does not allow multiple processes to run concurrently on the same TCB.

Support for Java Program Objects: Java program objects are programs compiled with the VisualAge for Java Enterprise Toolkit for OS/390 (ET/390) byte-code binder (they are compiled with the hpj command, and 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, rather than as Java program objects. However, to ease migration from CICS TS V1.3, CICS TS V2.2 continues to support Java program objects, which can run with or without the HOTPOOL option, except that:

  • IIOP applications must execute in JVM mode
  • Enterprise beans must execute in JVM mode
  • Java applications that use the CCF client interface must execute 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 for Java 2 and 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 appropriate application development tooling. Note that users of VisualAge for Java V3.0.2 should migrate to VisualAge for Java V3.5 or later.

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.

Java Applications Used with the CICS Connector for CICS TS: Java applications compiled on a distributed platform for use with the CICS Transaction Gateway may be used with the CICS Connector for CICS TS in CICS TS V2.2 without recompilation; unlike the position with CICS TS V2.1, references to applids do not need to be changed to sysids.

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 invoked only in the region where the file control command was originally issued, not in the file-owning region (FOR). A new global user exit, XFCFRIN, is introduced. This new exit is a domain level exit and will be invoked on entry to the file control component (for example, in the FOR). This exit may:

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

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

Compiler Support: For compiler support, refer to the Software Requirements section.

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 January 31, 2003).

RODM: As previously announced, the function of CICSPlex SM to populate CICS resource existence and minimal state data into the Resource Object Data Manager (RODM) component of NetView is removed from CICSPlex SM in CICS TS V2.2.

Remote MAS Agents: Support has been removed in CICS TS V2.2 for remote MAS agents for CICS on the z/OS or OS/390 platform.

Migration: To convert the CICSPlex SM Web User Interface server to CICS TS V2.2, it is necessary to migrate to the new level the MAS that acts as the Web User Interface server, using the normal MAS migration procedures; to upgrade the Web User Interface CSD group; and to migrate the contents of the Web User Interface server repository (EYUWREP) to a new data set, using the repository export and import functions.

Performance Considerations

Traditional Procedural Language Workloads: Comparisons with CICS TS V1.3, using an IBM internal benchmark, show that CICS TS V2.2 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. IIOP applications are supported in JVM mode only. The VisualAge for Java, Enterprise ToolKit for OS/390 bytecode binder cannot be used for IIOP applications. Although these IIOP applications in CICS TS V2.2 must run in JVM mode rather than as Java program objects, the performance is similar in terms of CPU costs and response time to that achieved for the same applications in CICS TS V1.3.

CICS Support for the Persistent, Reusable JVM: CICS TS V2.2 exploits the enhancements in the persistent, reusable JVM, at its latest level. 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 timeframe to the next release.

CICS EJB Support: CICS TS V2.2 supports EJB session beans. The performance in this environment will be dependent on many factors relating to the application design, including the transactional qualities, the implicit services used by the enterprise bean, and adherence to the EJB programming specification. Although CICS TS V2.2 is recommended as capable of use in high-volume production, care will be necessary with regard to capacity planning guidance.

Security, Auditability, and Control

Refer to the section EJB Security above.

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 2: Release Guide may be downloaded free of charge now, in PDF format, from:

Important: When placing an order for CICS TS V2.2 (5697-E93), an order must also be placed for program number 5630-A64, feature 0019 quantity 5. This is a no-charge feature which provides one year's maintenance for WebSphere Application Server, Advanced Single Server Edition V4.0, shipped as part of the product.

Current Licensees

Current licensees of CICS Transaction Server for z/OS Version 2 Release 1 will be sent a program reorder form that can be returned directly to IBM Software Delivery and Fulfillment. Reorder forms are scheduled to be mailed by February 8, 2002. Reorder forms returned to IBM Software Delivery and Fulfillment will be processed within 10 workdays of receipt. When CICS Transaction Server for z/OS Version 2 Release 2 is available, CICS Transaction Server for z/OS Version 2 Release 1 will no longer be available.

Note that CICS Transaction Server for z/OS Version 2 Release 2 can be delivered only by customized offerings, in particular CBPDO (program number 5751-CS3) or ServerPac (program number 5751-CS9). Unlike CICS TS V2.1, it is not available by a stand-alone 5697-E93 product order.

New Licensees

Shipment will begin on the planned availability date.

  • Orders that ship before the planned availability will include CICS Transaction Server for z/OS Version 2 Release 1.
  • Orders that ship after the planned availability date will include CICS Transaction Server for z/OS Version 2 Release 2.

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

    Type: 5697
    Model: E93

For ordering information on the base program, CICS Transaction Server for z/OS Version 2 Release 1, refer to Software Announcement 201-060 , dated March 13, 2001.

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 of tape 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 numbers are provided for these two languages, but this is only to cause the shipment of the appropriate translated hardcopy publications along with the common product tapes.

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

Publications

Publications Overview: In CICS TS V2, there has been a move away from the traditional printed books as the default deliverable to a new 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 various 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.

A major new focus of the documentation in CICS TS V2.2 is the implementation of EJB technology 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                           7014
 CD-ROM (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:

The navigation frames, help information, and home information of the Information Center are translated to French, German, and Korean; these translations are included on the one common CD-ROM.

Printed Publications: In addition to the softcopy information in the Information Center, the following printed documentation is delivered as hardcopy with the product. Note that order numbers have changed from those applicable with CICS TS V2.1.

                                                  Order
Title                                             Number
 
CICS Transaction Server                           GC34-5983
 for z/OS Release Guide
CICS Transaction Server                           GC34-5984
 for z/OS Migration Guide
CICS Transaction Server                           GC34-5985
 for z/OS Installation Guide
CICS Transaction Server                           GC34-5987
 for z/OS Licensed Program
 Specifications
CICS Transaction Server                           GI10-2542
 for z/OS Memo to Licensees
CICS Transaction Server                           GI10-2543
 for z/OS Program Directory
CICS Business Partner                             GC34-5527
 Directory (third 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.2 is available now at:

In addition to the books listed above, the following unlicensed publications are provided within the Information Center. Hardcopy of these publications can be purchased for a fee by contacting your IBM representative or from the online IBM Publications Ordering System (see above). Alternatively the PDF files may be printed.

                                                  Order
Title                                             Number
 
CICS Application Programming Guide                SC34-5993
CICS Application Programming                      SC34-5994
 Reference
CICS Customization Guide                          SC34-5989
CICS Intercommunication Guide                     SC34-6005
CICS Internet Guide                               SC34-6007
CICS Operations and Utilities Guide               SC34-5991
CICS Resource Definition Guide                    SC34-5990
CICS Supplied Transactions                        SC34-5992
CICS System Definition Guide                      SC34-5988
CICS System Programming Reference                 SC34-5995
CICS Problem Determination Guide                  SC34-6002
CICS Messages and Codes                           SC34-6003
CICS Trace Entries                                SC34-6004
CICS External Interfaces Guide                    SC34-6006
CICS Business Transaction Services                SC34-5999
CICS Front End Programming Interface              SC34-5996
 User's Guide
CICS Family:  Interproduct                        SC34-6030
 Communication
CICS Family:  Communicating from                  SC34-6031
 CICS on System/390

In addition, the following unlicensed publications are provided within the Information Center, but are not available in hardcopy. Hardcopy of these publications is available only by printing the PDF files.

  • CICS C++ OO Class Libraries
  • CICS DB2 Guide
  • CICS Distributed Transaction Programming Guide
  • CICS Glossary
  • CICS IMS Database Control Guide
  • Java Applications in CICS
  • CICS Performance Guide
  • CICS RACF Security Guide
  • CICS Recovery and Restart Guide
  • CICS Shared Data Tables Guide
  • CICS Transaction Affinities Utility Guide
  • CICS User's Handbook
  • 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

Collection Kit for Transaction Processing and Data Products: This Collection Kit is a CD-ROM, containing books in BookManager® form for a range of IBM transaction processing and data products, including CICS TS V2.2 and other members of the CICS family.

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.

Further copies of the Collection Kit are available by other ordering methods, such as from the online IBM Publications Ordering System.

Licensed Documentation: Licensed documentation is available only to licensees of the product. Note that none of the following items of licensed documentation is available through the publications ordering system.

The licensed book Diagnosis Reference is provided, in PDF format, on the CICS Information Center CD-ROM. It may also be ordered in hardcopy, for a price of $40, by specifying the feature number 8056.

The licensed book Data Areas is provided, in PDF format, on the CICS Information Center CD-ROM. It may also be ordered in hardcopy, for a price of $40, by specifying the feature number 8055.

The licensed book Supplementary Data Areas (LY33-6098) is available only in hardcopy, for a price of $104, by specifying feature number 8051.

The 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. A hardcopy of the Supplementary Data Areas licensed book is also included.

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 .

Licensed Product Kit: In addition, the licensed Product Kit is provided for customers who wish to use BookManager for softcopy publications. The number of this Product Kit is LK3T-6935. It provides both licensed publications and unlicensed publications for this release, in BookManager softcopy form on CD-ROM. Licensees of CICS TS V2.2 can order, at no charge, one copy of the licensed Product Kit by specifying feature number 7023. Further copies may be ordered, for a fee of $40, by specifying feature number 8057.

Note that this contains RESTRICTED MATERIALS OF IBM.

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:

Note that ordering of Optional Source (excludes Object-Code Only modules) remains unchanged from the previous announcement.

Publication Updates: Subsequent revisions 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.

Redbooks™: The following existing Redbooks are relevant to CICS TS V2.2:

  • Revealed! Architecting Web Access to CICS (SG24-5466-02)
    • Published September 20, 2001
  • Enterprise JavaBeans for z/OS and OS/390 CICS Transaction Server V2.1 (SG24-6284-00)
    • Published July 31, 2001. Note that this Redbook uses the tooling shipped with CICS TS V2.1, not that in CICS TS V2.2.
  • CICS Transaction Gateway V3.1 — The WebSphere Connector for CICS (SG24-6133-00)
    • Published April 6, 2001
  • Workload Management for Web Access to CICS (SG24-6118-00)
    • Published February 13, 2001
  • Securing Web Access to CICS (SG24-5756-00)
    • Published June 1, 2000
  • A Performance Study of Web Access to CICS (SG24-5748-00)
    • Published February 17, 2000
  • Java Application Development for CICS (SG24-5275-01)
    • Published November 30, 1999
  • Business Process Model Implementation with CICS Business Transaction Services (SG24-5464-00)
    • Published August 16, 1999

Customized Offerings

This product is shipped only via Customized Offerings (that is, CBPDO, ServerPac, Systempac®). It is not shipped as a stand-alone product.

Terms and Conditions

The terms and conditions for CICS Transaction Server for z/OS Version 2 Release 2, as previously announced in Software Announcement 201-060 , dated March 13, 2001, are unaffected by this announcement except as noted below.

Information Center: Customers with a license for CICS Transaction Server for z/OS Version 2 Release 2 are licensed, at no additional charge, to install and run the Information Center on suitable workstation or server machines, which are not the designated machine, within the same enterprise. It may be run on as many machines as are reasonably necessary for use in conjunction with CICS TS V2.2.

WebSphere Application Server, Advanced Single Server Edition V4.0: This program is accompanied by WebSphere Application Server, Advanced Single Server Edition V4.0, with five (5) Proofs of Entitlement. A license of the program entitles you to install WebSphere Application Server, Advanced Single Server Edition V4.0 in no more than five (5) processors, for use only in conjunction with your authorized use of the CICS Transaction Server for z/OS Version 2 Release 2 program. Except for the foregoing additional restrictions and rights, your use of WebSphere Application Server, Advanced Single Server Edition V4.0 is subject to the terms and conditions of the International Program License Agreement and License Information document for the WebSphere Application Server, Advanced Single Server Edition V4.0 included in the packaging for the program.

CICSPlex SM Remote MAS Agents: Customers with a license for CICS Transaction Server for z/OS Version 2 Release 2 are licensed to make and use any number of copies of the CICSPlex SM remote MAS agent for OS/2 and the CICSPlex SM remote MAS agent for Windows NT, subject to their use being in conjunction with the licensed CICS TS V2.2. If required, the agents may be copied to secondary media for convenience of installation.

Items No Longer Applicable: Terms and conditions in the previous announcement for the CICS Tools for EJB Technology and the WebSphere Application Server Advanced Edition Version 3.5 are not applicable to CICS TS V2.2, since they are not shipped with this product.

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® or zSeries machine to enable communication with the licensed CICS TS V2:

  • CICS External Communication Interface (EXCI — Load Library SDFHEXCI)

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 or zSeries 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 or zSeries 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 (formerly 5696-582, now part of the CICS element)

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.

Program Services for CICS TS V2.2

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

Delivery of service for the Information Center is by download over the Web. To locate service updates, go to:

WebSphere Application Server, Advanced Single Server Edition V4.0, delivered with this product, is provided with one year of Software Maintenance (this includes upgrade protection). Service for this element of the product should be requested as normal WebSphere service. Note that if continued maintenance support is required after this one year period, it must be purchased, for each processor license used. This maintenance support will be offered on the product via its program number — feature number ordering, but may be transferred to Passport Advantage if preferred.

IBM Operational Support Services — Support Line: Yes.

Prices

Current charges are unaffected by this announcement.

Order Now

 Use Priority/Reference Code: LE001
 
 Phone:     800-IBM-CALL
 Fax:       800-2IBM-FAX
 Internet:  ibm_direct@vnet.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

 
zSeries is a trademark of International Business Machines Corporation.
 
The e-business logo, IMS, z/OS, WebSphere, MVS, TXSeries, ClusterProven, MVS/ESA, DFSMSdss, DFSMShsm, C/370, VSE/ESA, and Redbooks are trademarks of International Business Machines Corporation in the United States or other countries or both.
 
CICS, OS/390, DB2, SecureWay, Parallel Sysplex, CICS/ESA, VisualAge, RACF, CICSPlex, Language Environment, System/390, AnyNet, VTAM, DB2 Universal Database, Extended Services, OS/2, MQSeries, Sysplex Timer, ESCON, SAA, AD/Cycle, IMS/ESA, CICS/MVS, CICS/VSE, BookManager, Systempac, and S/390 are registered trademarks of International Business Machines Corporation in the United States or other countries or both.
 
Microsoft is a trademark of Microsoft Corporation.
 
Windows NT and Windows are registered 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.