IBM CICS Transaction Server for OS/390 Release 3 Provides Single Solution Package

Software Announcement
September 8, 1998
Announcement Letter Number: 298-318


Table of Contents:

(Corrected on October 20, 1998)

Specified Operation Environment, Software Requirements section -- verbiage changed/deleted. Supplemental Information -- Program numbers 5648-B42 and 5648-B43 deleted. Trademark inserted for NetWare. In Terms and Conditions section -- Program number deleted and Paragraph changed.

At a Glance

IBM CICS Transaction Server for OS/390 Release 3 provides an easy to use S/390 (R) client/server package. It includes CICS server, CICS client, CICS Transaction Gateway, and CICS management function in a single solution package that offers:

  • Secure integration of business with new world of electronic commerce and network computing for easy integration of business systems for both intranet and Internet

  • Flexible point of entry into network computing with a scalable and reliable growth path, especially with Web technologies

  • Support for all models of client/server computing with comprehensive client support from IBM and non-IBM workstations

    The CICS Transaction Gateway Version 3.0, a robust, secure and scalable gateway, supports OS/2 (R), Windows NT (R), AIX (R) and Solaris, and brings access from a user at a Web browser or Network Computer to business-critical applications running on CICS servers.

  • Exploitation of S/390 Parallel Sysplex
-----------------------------------------
For ordering, contact:
  Your IBM representative, an IBM
  Business Partner, or IBM North America
  Sales Centers at
    800-IBM-CALL  Reference: LE010

EXTRA! EXTRA! . . .

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



Overview

CICS (R) Transaction Server for OS/390 (R) (CICS TS) is the base for the future growth of general purpose and large scale or complex transaction processing. This flexible and easy to use client/server package is the delivery vehicle for CICS products. CICS TS contains CICS-enabling functions, orderable with one program number and delivered as one product -- with one price.

New Release 3 functions include:

  • Application Enablement
    • Java (TM) Application Support

    • Object-oriented interface to CICS services for C++

    • CICS business transaction services

    • Long temporary storage queue names
  • e-Business Enablement
    • CORBA Client support

    • CICS Web Interface enhancements

    • CICS EXCI enhancement for resource recovery

    • 3270 Bridge Interface enhancements

    • New CICS Transaction Gateway and CICS Universal Clients
  • Enterprise Scalability
    • Dynamic routing and load balancing of distributed program link (DPL) and EXEC CICS START requests

    • Coupling facility data tables support

    • Sysplex Wide Enqueue (ENQ) and Dequeue (DEQ)

    • Named Counter Server
  • Enterprise Management
    • CICSPlex (R) System Manager enhancements

    • Resource definition online (RDO) for CICS temporary storage

    • Autoinstall for MVS (TM) consoles

    • Enhancements to CICS monitoring and statistics



Intended Customers

A CICS 390 solution for transaction processing for OS/390 customers with expanding CICS applications.



Key Prerequisites

  • OS/390 Version 2 Release 5 or later
  • A coupling facility for Parallel Sysplex (R), if not using DASD-only logging for a single-system sysplex



Planned Availability Date

March 26, 1999

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

This announcement is provided for your information only. For additional information, contact your IBM representative, call 800-IBM-4YOU, or visit the IBM home page at: http://www.ibm.com



DESCRIPTION



Application Enablement

Java Application Support: CICS introduces support for a new programming interface for use in CICS application programs written in Java.

CICS support for the Java programming language is similar to the CICS language support for COBOL or C++. The normal CICS program execution model is used, in place of a long-lived Java Virtual Machine (JVM). Access to a range of CICS services, traditionally available through the CICS command-level API, is via a set of Java classes. The CICS translator is not required for Java. The application program is developed and compiled, using a Java compiler (such as VisualAge (R) for Java) on a workstation or in the OS/390 UNIX (R) Systems Services (OS/390 UNIX) environment on MVS. The compiler output is then processed by the IBM VisualAge for Java, Enterprise Edition for OS/390 product in OS/390 UNIX to create program objects in MVS partitioned data set extended (PDSE) libraries.

When invoked, CICS loads the program from the PDSE and executes as a Language Environment (LE) run-unit, similar to C++.

Object-Oriented Interface to CICS Services for C++: CICS introduces a new C++ Object-Oriented (OO) Programming Interface, enabling application programmers to have access to those CICS services previously only available using the CICS command-level application programming interface (API). The CICS OO API, based on the CICS C++ foundation classes, gives a C++ programmer the choice of writing CICS application program using either the traditional CICS command-level API or the CICS OO API classes.

CICS Business Transaction Services: CICS Business Transaction Services (CICS BTS) provides an API and support services that simplify the development and management of complex business transactions. Organizations can focus on the development of business logic, without needing to implement complex support infrastructures.

A real-world business transaction, for example, the booking of a holiday, may involve multiple actions that take place over an extended period. Traditionally, the individual actions that make up a complex business transaction have been mapped onto CICS transactions. The CICS Business Transaction Services provide a better way of modelling and managing complex business transactions.

Using CICS Business Transaction Services, each action that makes up the business transaction is implemented as one or more CICS transactions. CICS BTS is used to control the overall progress of the business transaction, managing the interrelationship, ordering, parallel execution, commit scope, recovery, and restart of the actions that make up the business transaction.

Long Temporary Storage Queue Names: The CICS temporary storage (TS) facility is enhanced to allow TS queues to have names up to 16 characters long, providing much greater flexibility in user application programs. For example, 16-character names allow you to generate queue names of the form "ttttSuuuuuuuu", where tttt is the transaction identifier, S can represent a sequence character (allowing you to have more than one queue for each transaction) and uuuuuuuu is the user id.

Support for longer TS queue names removes many of the restrictions and difficulties that face application designers caused by the 8 character limit.



e-Business Enablement

CORBA Client Support: The Internet Inter-ORB protocol (IIOP) is a standard for use when providing communication between object-oriented applications programs executing on different processors. It is part of the Common Object Request Broker Architecture (CORBA) V2.0 specification. CICS TS Release 3 supports inbound requests to Java application programs, using the IIOP protocol. CICS has not implemented the full function Object Request Broker (ORB), because of the following limitations:

  • Objects may not have any implicit (system-managed) persistent state.

  • State is initialized at the start of each method call.

  • Application state must be referenced by explicit method parameters.

  • Outboard object references are not supported -- results in runtime errors.
Each method call is implemented as a CICS transaction, retaining the existing TOR/AOR structure.

CICS Web Interface Enhancements: The CICS Web Interface (CWI) is enhanced with a number of major improvements, including support for work-load management (WLM).

  • The CICS Web Interface has been restructured as a CICS domain, providing improved reliability and serviceability

  • Addition of new EXEC CICS application programming interface commands for the manipulation of Web entities

  • Improvements to the definition and management of HTML templates

  • CICS Web interface work can be sysplex-enabled

  • More than 32 K of data can be handled, inbound and outbound

  • Uses the 3270 Bridge enhancements in a Web 3270 environment
CICS EXCI Enhancement for Resource Recovery: CICS supports MVS Recoverable Resource Management Services (RRMS), using MVS context services, for applications that use the external CICS interface (EXCI). This enables applications using EXCI, such as DCE AS/CICS servers, to participate in full recovery of a distributed unit of work, enabling seamless integration with other work managers within the enterprise, and ensuring a greater return on investment for your mission critical applications. CICS inbound Transactional Remote Procedure Calls (TRPC) support will be added to DCE AS and Encina Toolkit Executive to enable AS/CICS servers to participate in Encina distributed transaction processing applications.

In earlier releases, EXCI enforces a syncpoint by the CICS server region before returning control to the EXCI client program. With use of MVS RRMS, an extended mode of EXCI operation (transactional) now provides:

  • The unit of work, within which the CICS server program changes recoverable resources, becomes part of the MVS unit of recovery associated with the EXCI client program.

  • The CICS server unit of work is not committed when the server program returns control to the client. This unit of work continues over multiple EXCI DPL calls, until the EXCI client decides to commit or backout the unit of recovery.
3270 Bridge Interface Enhancements: The 3270 Bridge is enhanced with:
  • New options of the START command are provided to initiate a user transaction and to establish the Bridge environment. A Bridge Transaction is no longer needed for this purpose.

  • Removal of some restrictions on the CICS commands used by a user transaction. Support is added for:
    • START TRANSID TERMID commands, where TERMID is the bridge facility and TRANSID is local

    • RETURN IMMEDIATE

    • INPUTMSG on RETURN, XCTL and LINK

    • SET TERMINAL ATISTATUS
Applications written for 3270 terminals can be run on CICS systems without VTAM (R). The bridge can process commands faster than existing front end methods, such as FEPI and EPI, because the terminal emulation is part of the same CICS transaction. There is only a single unit of work, simplifying recoverability.



Enterprise Scalability

CICS support for Parallel Sysplex environments is extended with the following new function:

  • Dynamic Routing and Load Balancing of Distributed Program Link (DPL) and EXEC CICS START Requests

    CICS dynamic routing facility is extended to provide mechanisms for dynamically routing transactions started by distributed program link (DPL) requests, and a subset of START commands. Dynamic balancing for DPL includes:

    • DPL requests from an external CICS interface (EXCI) client.

    • External Call Interface (ECI) requests from any of the CICS Client workstation products.
    The routing mechanisms allow workload balancing to be managed by CICSPlex SM, allowing integrated workload balancing for EXCI clients, CICS clients, and started tasks.

    The ability to dynamically route all types of program link requests improves the performance and reliability of:

    • CICS Web Interface

    • CICS Gateway for Java

    • EXCI calls

    • CICS Client ECI calls

    • DCE/RPC

    • ONC/RPC

    • Any function that issues an EXEC CICS LINK Program request

      Similarly, the performance and reliability of applications that use the subset of START commands, which can be dynamically routed, are improved.

  • Coupling Facility Data Tables Support

    CICS coupling facility data tables support allow user applications running in different CICS regions that reside in one or more MVS images within a Parallel Sysplex, to share working data with update integrity.

    Data in a coupling facility data table is accessed through the CICS file control API, enabling existing applications to use it, either without any modification, or with minimum changes, depending on the level of function required. Coupling facility data tables provide efficient sharing of data with integrity, and behave much like a sysplex-wide equivalent of user-maintained data tables. Key lengths greater than 16 bytes are not supported.

  • Sysplex Wide Enqueue (ENQ) and Dequeue (DEQ)

    The Sysplex wide (global) enqueue and dequeue function enables CICS transactions running in the same region, or in different regions within a sysplex, to serialize on a named resource using the existing CICS API. By extending the scope of the CICS enqueue mechanism, a major source of inter-transaction affinity is removed, enabling better exploitation of Parallel Sysplex environments, improving price/performance, capacity and availability.

    For example, serialization makes it possible for concurrent updates to shared Temporary Storage queues by multiple CICS transaction instances, while locking a shared Temporary Storage queue against concurrent updates. This eliminates the race problem created by relying on serial reuse of a principal facility.

  • Named Counter Server

    A utility program is provided for the efficient generation of unique sequence numbers (for example, the next order number) in a parallel sysplex environment.



Enterprise Management

CICSPlex System Manager Enhancements: The CICSPlex System Manager has been enhanced to work with the new CICS functions of this release.

The CICSPlex System Manager is now an exclusive element of CICS Transaction Server for OS/390, being fully integrated with the base CICS product. Stand-alone releases of the CICSPlex SM product (5695-081) do not support CICS TS Release 3. All the CICSPlex SM functions are available, including:

  • Business Application Services (BAS) for defining and installing CICS resources across multiple CICS occurrences on S/390 systems.

  • Generating messages and generic alerts for triggering automation actions.

  • Runtime analysis (RTA) for detecting potential CICS problems and taking automatic corrective actions.

  • As well as managing CICS systems in different MVS images and regions, CICS/VSE (R) Version 2.3 (5686-026), CICS Transaction Server for OS/2 Warp Version 4.1 (5622-808), can be managed from a CICSPlex System Manager managing address space (CMAS).

  • Extensions to CICSplex system management functions include:
    • Enable Userkey CICSPlex SM API applications
Resource Definition Online (RDO) for CICS Temporary Storage: Instead of coding macros to define a temporary storage table (TST), CICS provides TSMODEL resource definitions for temporary storage (TS) queues in the CICS system definition (CSD) file. The define command on the CEDA transaction is used for this resource definition online (RDO) facility, and in the DFHCSDUP utility program. Temporary storage model definitions can also be discarded while CICS is running.

RDO for temporary storage eliminates the need to prepare a temporary storage table (TST) for batch assembly and link-edit. There is now no need to shut down and restart CICS in order to make changes to TS queue definitions. RDO support for TS queues is part of the CICS high availability and continuous operations strategy.

Autoinstall for MVS Consoles: Autoinstall for terminals is extended to include MVS consoles, removing the need to define MVS consoles to CICS. Autoinstall for consoles can use the same autoinstall control program as for terminals. This saves a considerable amount of system programmer effort for defining and maintaining individual console resource definitions.

Enhancements to CICS Monitoring and Statistics: Additional information is provided by CICS monitoring and statistics for many of the changes and new functions introduced in CICS.



Base CICS Enhancements

  • Provide support for long-lived TCP/IP connections. The CPU costs involved in setting up a TCP/IP connection for each incoming request or data post to the CICS server are high. In a conversational or pseudo conversational business transaction, which has multiple requests and posts, a considerable saving in CPU can be made if all flows after the first are made without the need to re-establish the connection. With this support, performance of both the CICS Web interface and IIOP is improved.

  • Support for BMS maps on LU6.2 sessions, via new MAPPINGDEV option. The new API enables applications to perform BMS data mapping in the absence of a suitable principal facility terminal.

  • Enhance the CICS-DBCTL operator transaction (CDBM) to support issuing IMS (TM) commands from a file rather than just screen input, with the ability to update and maintain the file.

  • Enable run-unit work area storage to be reused for EXEC CICS LINK for programs running under Language Environment (LE).

  • Provide support for explicit TCP/IP address per IP service.

  • Euro: Provide support, including the new euro-capable code pages.
Refer to the CICS Release Guide (GC33-1570) for more information.



New CICS Gateway and Clients

CICS Universal Clients Version 3.0: The IBM CICS Universal Clients Version 3.0 are developed from the CICS Clients Version 2. They are an all 32-bit product, delivered for the OS/2, Windows NT, Windows (TM) 98, AIX and Solaris platforms. They bring the any-to-any communication capabilities previously available only on Intel-based platforms also to AIX and Solaris.

The CICS Universal Clients also provide a range of functional enhancements, including a Security API, improvements to installation, and an application for workload management.

The CICS Universal Clients Version 3.0 may be copied freely for use with any IBM CICS server.

CICS Transaction Gateway Version 3.0: The IBM CICS Transaction Gateway provides powerful mechanisms for enabling access from the Internet to the tried and trusted transactional capabilities of IBM CICS servers (including CICS Transaction Servers and TXSeries (TM) servers). The CICS Transaction Gateway uses the latest technologies, both HTTP and Java based, to link the open, object-oriented world of Web browsers on the Internet or an intranet to the power, flexibility, integrity and robustness of CICS enterprise computing.

The CICS Transaction Gateway is provided for the OS/2, Windows NT, AIX, and Solaris platforms. It also supports Windows 98 for application development. It runs on the same system as the Web server, and is capable of supporting a large number of concurrent users. It is an integrated product which incorporates the functions provided by the CICS Universal Clients Version 3.0, enabling communication with a wide range of CICS Servers.

The CICS Transaction Gateway enables any Internet-connected desktop workstation or Network Computer to provide access for your customers, your business partners, or your distributed sales force to your business-critical core corporate applications on CICS.



Euro Ready

This product will be Euro Ready at general availability. The detailed reasons and actions are available on the Web site:



Year 2000

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



PRODUCT POSITIONING

CICS as an Application Server: The transaction-processing strengths of CICS in an enterprise computing environment are appreciated and exploited worldwide. But today, CICS is more than an exceptionally capable transaction processor -- it is an application server that allows you to distribute applications and data flexibly across your network in any way that your changing enterprise may need.

CICS is a family of modern transaction processing products that enables your business to exploit applications and data on many different hardware and software platforms. It is a truly robust and open platform on which to build your enterprise systems. With this release you should get a greater return on investment for your technology by increasing productivity and performance, especially through Web technologies.

CICS views an application and all its associated services as an entity. It manages and coordinates all the different resources needed by applications, such as databases, files and message queues, to ensure completeness and integrity of data. CICS is a true application server.

The four main themes of this release are aimed at providing a balance of solutions to meet customer needs. These are:

  • Applications Enablement
  • e-Business Enablement
  • Enterprise Scalability
  • Enterprise Management
Each theme contains specific product items that provide potential business benefits in resolving Critical Business Issues. These are:
  • Reduced costs -- Development productivity.

  • Improved time to market -- Programmer productivity, design and reuse.

  • Reduced production costs -- Efficient use of existing skills and components, efficient integration and reuse of existing data and processes.

  • Improved business efficiency -- Efficient design and reuse of business and IT processes.

  • Extended reach to market -- Extending business processes to the Web.

  • Improved user productivity, look and feel -- Intuitive look and feel of GUI.

  • Improved performance and manageability.

  • Increased scalability of business.
With CICS Transaction Server for OS/390 Release 3 and OS/390, customers can make the correct decision for developing applications for S/390, leveraging the best mix of features in which an organization can invest, bringing real business benefits.

CICS Transaction Server for OS/390 Release 3 provides improved productivity for application developers through the CICS Business Transaction Services, easier operational and systems management capabilities, increased price performance and manageability, while also attracting customers and vendors to new technologies via the Internet and Java.

Additional Enterprise Integration Facilities: Bridge system boundaries to allow your customers to connect to systems wherever they may be, and free your enterprise to grow the way you want, for example, the new API for resource definitions.

Parallel Computing Support: Make the benefits of parallelism and new technology immediately available. The first release provided additional data sharing. It made more use of VTAM generic resource function, and used IBM's coupling technology for improved handling of log streams. It also enhanced recovery for data sharing. This release extends that support with more functions, such as the dynamic routing of DPL and EXEC CICS START requests.

Greater Availability and Capacity in a Parallel Sysplex Environment: Substantial enhancements have been made to CICS and other systems components with the use of the MVS logging function, the new recovery manager (CICS TS Release 2), and CICS data tables in a coupling facility (CICS TS Release 3). This improves availability and capacity in a Parallel Sysplex.

Enhanced Systems Management Facilities: Increases your operational efficiency, and allows you to improve your service level commitments. Enhancements include: resource definition online (RDO) for DB2 (R) resources (CICS TS Release 2), temporary storage (CICS TS Release 3), transient data, and centralized log management.

CICS Transaction Server for OS/390 provides all of the function announced for prior versions, (refer to the Compatibility section for differences).

Connectivity to all other CICS family members is the same as that for CICS/ESA 4.1. CICS connectivity support extensions provide support for CICS clients (EPI, ECI), CICS Transaction Gateways and for inbound ONC RPC calls.

In addition to the new application support enhancements in this release, more command-level function, previously available only at macro level, has been added to CICS TS (including API for RDO resources (CICS TS Release 2)). This makes migration to command level easier. The migration aid, CICS Application Migration Aid (5695-061), (refer to Software Announcement 290-736 dated November 27, 1990), an element of CICS Transaction Server for OS/390, can be used to assist users converting macro-level programs to command-level programs, so that these applications can be migrated to CICS/ESA (R) Version 4 and to CICS Transaction Server for OS/390.

CICS TS is the base for future growth of general purpose, large scale or complex transaction processing.

All command-level applications should be migrated to either CICS Transaction Server for OS/390 or CICS/ESA Version 4 now, because these are the Year 2000 ready CICS products.

CICS support for data sharing, MRO use of MVS cross-system coupling facility (XCF), combined with VTAM persistent sessions and the MVS Automatic Restart Manager (ARM), provides a flexible alternative to the CICS Extended Recovery Facility (XRF).



HARDWARE AND SOFTWARE SUPPORT SERVICES



SmoothStart (TM)/Installation Services

With IBM SmoothStart Services for OS/390 Internet Enablement, IBM helps you in building an OS/390 test environment that simulates an advanced application deployment on the World Wide Web. With this service, an IBM services specialist will assist you in setting up the Lotus (R) DominoGoWeb server connection between this test environment and your data that resides on an existing OS/390 CICS (or DB2 or IMS, or MQSeries (R)) database.

IBM Global Services provides a set of services, at an additional cost, to support specific product themes of CICS Transaction Server for OS/390 V1.3. Examples of these services are:

  • Planning Services for CICS Application Migrations

    With IBM Planning Services for CICS Application Migrations, IBM Global Services helps customers plan the migration of their existing applications through to the latest release of CICS Transaction Server for OS/390 (Version 1 Release 3).

    IBM Global Services provides an executable plan to manage the migration of CICS applications from existing versions to new CICS production systems.

    An IBM Global Services migration specialist helps make sure that the application software migration plan is tailored to meet your requirements. During the planning phase, you can assign personnel to work with the migration specialist to help tailor the application software migration plan.

    There are three migration plans:

    • CICS Application Migration Planning to CICS Transaction Server for OS/390 Version 1 Release 3

      Offering: Planning process to manage the migration of customer applications to new versions of CICS:

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

      • CICS/MVS (R) Version 2 to CICS Transaction Server for OS/390 Version 1 Release 3

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

      • CICS/ESA Version 4 to CICS Transaction Server for OS/390 Version 1 Release 3

      • CICS Transaction Server for OS/390 Version 1 to CICS Transaction Server for OS/390 Version 1 Release 3
    • Macro to Command Conversion Assessment for CICS Applications

      Offering: Plan the conversion of one or more of CICS applications from macro to command level.

    • Preparing for Dynamic Workload Balancing

      Offering: Development of a migration plan and analysis of the performance of selected applications by assessing the affinities and interdependences of the applications.

      This may include one week of CICSPlex SM on-site SmoothStart assistance.

    The migration specialist has the knowledge and expertise to help plan the application software migration.

  • Parallel Sysplex Services

    The Enhanced S/390 Parallel Sysplex Offering (EPSO) provides an attractively priced package integrating hardware, maintenance and services, with competitive financing options, to assist you in migrating to S/390 Parallel Sysplex.

    The IBM migration and implementation services address the traditional lengthy migration process when many software products must be upgraded in order to have a working Parallel Sysplex data sharing environment. It is the intent of the services to migrate a selected application to Parallel Sysplex and be in a production data sharing environment within one year.

    EPSO services include two comprehensive modules: Systems Enablement and Application Enablement. The objective of Systems Enablement is to establish a Parallel Sysplex environment. IBM provides assistance and guidance in building the system, validating the hardware, and implementing some system functions in the Coupling Facility.

    IBM is responsible for project management and provides guidance in migration planning and detailed implementation tasks. The system capabilities of a Parallel Sysplex are enabled providing a validation of the Parallel Sysplex environment.

    In Application Enablement, one customer application is enabled for Parallel Sysplex exploitation. IBM assists in selecting the application, developing a plan, and migrating the selected application to a Parallel Sysplex environment. IBM is responsible for project management and provides support and guidance in implementing data sharing and dynamic transaction routing, testing the application, migrating the application to production, and establishing a Parallel Sysplex in a production environment.

    For more information, check the EPSO package on MKTTOOLS.

For additional information, contact an IBM Global Services representative. Additional information on IBM Global Services can be found by visiting: Trademarks
      MVS, IMS, TXSeries, and SmoothStart are trademarks of
      International Business Machines Corporation in the United
      States or other countries or both.
      CICS, OS/390, CICSPlex, Parallel Sysplex, S/390, AIX, OS/2,
      VisualAge, VTAM, CICS/VSE, DB2, CICS/ESA, MQSeries, and
      CICS/MVS are registered trademarks of International Business
      Machines Corporation in the United States or other countries or
      both.
      Windows is a trademark of Microsoft Corporation.
      Windows NT is a registered trademark of Microsoft Corporation.
      Java is a trademark of Sun Microsystems, Inc.
      UNIX is a registered trademark in the United States and other
      countries exclusively through X/Open Company Limited.
      Lotus is a registered trademark of Lotus Development
      Corporation.
      Other company, product, and service names may be trademarks or
      service marks of others.



SUPPLEMENTAL INFORMATION

As part of the IBM server strategy, CICS (R) Transaction Server for OS/390 (R) has both exclusive and non-exclusive elements. The base CICS element of CICS TS is CICS 5.3, the third release of the latest CICS version, first available as CICS 5.1 in the first release of CICS TS. This element, the CICS successor to CICS/ESA (R) Version 4 Release 1, is exclusive and includes features and products available with prior CICS versions and releases:

  • CICSPlex (R) SM

  • CICS Web Interface

  • Open Network Computing Remote Procedure Call (ONC RPC)

  • CICS Transaction Affinities Utility

  • CICS-DB2 (R) attachment facility
The non-exclusive elements of the product, also available as separate products, are:
  • REXX Development System for CICS/ESA
  • REXX Runtime Facility for CICS/ESA
  • CICS Distributed Data Management (DDM)
  • CICS Application Migration Aid Version 1.1
  • CICS Universal Clients Version 3.0
A non-exclusive element of the product, but not available as a separate product, is:
  • CICS Transaction Gateway Version 3.0



Key Features of CICS Business Transaction Services

  • Extends pseudo-conversational mechanisms to non-terminal initiated transactions, including browsers, RPCs and messages

  • Management and control is maintained at the business transaction and action level

  • Separation of business logic from control logic

  • Individual CICS transactions are transparent from the "before and after" actions

  • Programmer productivity in developing encapsulated business logic

  • The processes and activities of CICS Business Transaction Services can be monitored and/or statistical information gathered

  • Resources can be analyzed at the business or CICS transaction level

  • In a CICSplex, CICS Business Transaction Services processes and actions can take full advantage of CICSPlex SM facilities

  • Systems management workload separation and workload balancing is available

  • CICS Business Transaction Services processes can be used as servers in a client/server environment

  • Implementation of an efficient concurrency model

  • Separation of the contextual information from the business logic

  • Access to existing transactions from the CICS Business Transaction Services environment

  • Ease restriction on size of communications buffer to 32 K



CORBA Client Support Features

CICS support for inbound requests using the IIOP protocol provides:

  • Improved application development productivity. Use of a distributed object model gives well defined (strongly typed) interfaces for applications with inheritance and polymorphism characteristics.

  • Stronger type checking at compile time and reduction in application error compared with the use of untyped COMMAREAS used in CICS ECI calls. Run-time type checking is also enabled for use in polymorphic implementations.

  • The use of vendor-independent client platforms, giving true separation of server and client environments



New CICS Clients and CICS Transaction Gateway Details

CICS Universal Clients Version 3.0: The new IBM CICS Universal Clients Version 3.0 replace the previous CICS Clients Version 2. They are for 32 bit platforms only, and introduce CICS Universal Clients on the AIX (R) and Solaris platforms. This means that Clients on these platforms may now communicate directly with the wide range of CICS servers supported by the CICS Universal Clients.

The CICS Universal Clients Version 3.0 for AIX and Solaris provide most of the same CICS Universal Client functions as are provided on the OS/2 (R), Windows NT (R) and Windows (TM) 98 platforms. Supported functions include:

  • Support for concurrent ECI and EPI

  • Provision of ECI and EPI System Management exits

  • Support for API tracing

  • The ability to link, connect and disconnect concurrently from multiple CICS servers, including connections by a mixture of protocols.
For differences in supported functions, refer to the Migration and Compatibility section.

The CICS Universal Clients Version 3.0 introduce a security API. The External Security Interface (ESI) provides a client interface to APPC password expiration management (PEM).

The ESI is intended for use by CICS client applications that need to verify and change the password recorded by an external security manager for a specified userid. The external security manager is assumed to be accessible from a CICS server to which the CICS client is connected. The functions are:

    CICS_VerifyPassWord

    CICS_ChangePassWord

Use of the ESI eliminates the need for client application programmers to understand PEM data formats and communications server interfaces. These interfaces are described in detail in the CICS TS CICS RACF (R) Security Guide (SC33-1701).

CICS Universal Clients Version 3.0 for Windows NT and Windows 98 have moved to Industry-standard installation by InstallShield. Benefits include installation in national languages. The CICS Universal Clients for AIX and Solaris are delivered as compressed tar files.

Enhancements to the function of the CICS Universal Client for Windows NT as a Windows NT service allow (a) the entry of start-up parameters when started from the Service Control Panel, and (b) the sending of CICS Client controls when running, where these do not require a parameter or have a default parameter.

The CICS Universal Clients for Windows NT and Windows 98 introduce an application for workload management. This uses the EPI user exits and allows the customer to write an application to enable workload to be distributed across multiple CICS regions or CICS servers.

The CICS Universal Clients Version 3.0 are supported for a single user only at an end-user workstation connected to a CICS server in a configuration of two or more tiers. For functions involving multiple users, the CICS Transaction Gateway Version 3.0 should be used. The CICS Transaction Gateway incorporates the CICS Universal Clients for the respective platforms.

CICS Clients Version 2: The CICS Clients Version 2 continue to be available as a program package, for download from the Internet, and packaged with certain Transaction Servers, CICS Transaction Servers, and TXSeries (TM) servers. In particular, they are the only source of CICS Clients for the 16-bit platforms Windows 3.1 and DOS.

They can be used for communication with CICS TS Release 3.



Table 1: CICS Universal Clients V3 and CICS Transaction Gateway V3

Communication

The following table shows the communication capabilities with CICS servers for the CICS Universal Clients Version 3.0 and the CICS Transaction Gateway Version 3.0.

                            Commns.
                            Protocol         Functions
                            T=TCP/IP
                            A=SNA               CICS
CICS                        X=TCP62             3270          Auto-
Server        Platforms(1)  N=NetBIOS ECI EPI   Emuln. TN3270 Install

CICS/ESAV4R1; OS/2 A, X Y Y(2) Y(2) Y Y CICS Windows NT A(4) X Y Y(2) Y(2) Y Y Transaction Windows 98 Server AIX A Y Y(2) Y(2) Y Y for OS/390 Solaris -- -- -- -- -- -- V1R1 and later

CICS/VSE (R) VOS/2 A Y Y(3) Y(3) Y(3) Y(5) Windows NT A(4) Y Y(3) Y(3) Y(3) Y(5) Windows 98 AIX A Y Y(3) Y(3) Y(3) Y(5) Solaris -- -- -- -- -- --

CICS/400 (R) VOS/2 A Y Y Y Y Y and later Windows NT A(4) Y Y Y Y Y Windows 98 AIX A Y Y Y Y Y Solaris -- -- -- -- -- --

Commns. Protocol Functions T=TCP/IP A=SNA CICS CICS X=TCP62 3270 Auto- Server Platforms(1) N=NetBIOS ECI EPI Emuln. TN3270 Install

Trans Server OS/2 T, A(6) Y Y Y Y Y for AIX Windows NT V4(7); Windows 98 CICS for AIX T, A(6) Y Y Y Y Y Solaris Solaris T Y Y Y Y Y V2.1.1; CICS for HP-UX V2.1.1; Trans Server for Windows NT V4(8); TXSeries V4.2 for AIX, HP-UX, Solaris, and Windows NT

Transaction OS/2 N, T, A Y Y Y Y Y Server for Windows NT OS/2 Warp Windows 98 V4(9); AIX T, A Y Y Y Y Y CICS Solaris T Y Y Y Y Y Transaction Server for OS/2 Warp V4.1(10); VisualAge (R) CICS Enterprise Application Development for OS/2 and for Windows NT(11)

Notes:

(1)   The CICS Transaction Gateway for Windows 98 has the same
      functions as the CICS Transaction Gateway for Windows NT, but
      is supported for application development only.
(2)   The CICS/ESA V4R1 host requires PTFs UN90142 and UN90143.
(3)   The CICS/VSE V2R3 host requires PTFs UN90168 and UN90169.
(4)   Including via NetWare for SAA.
(5)   Only for dependent LU6.2 sessions.
(6)   Only with Transaction Server for Windows NT V4.0, TXSeries for
      Windows NT V4.2, Transaction Server for AIX V4.0, or TXSeries
      for AIX V4.2.
(7)   Transaction Server for AIX V4.0 contains CICS for AIX V2.1.1.
(8)   Transaction Server for Windows NT V4.0 contains CICS for
      Windows NT V4.0.
(9)   Transaction Server for OS/2 Warp V4.0 contains CICS for OS/2
      V3.0.
(10)  CICS Transaction Server for OS/2 Warp V4.1 contains CICS for
      OS/2 V3.1.
(11)  In VisualAge COBOL V2.2 and VisualAge PL/I V2.1.

CICS Transaction Gateway V3.0: The IBM CICS Transaction Gateway Version 3.0 is a key e-business enabling feature of CICS Transaction Server for OS/390. It provides a robust, scalable, easy-to-use and secure complement to a Web server, enabling multiple users at Web browsers or Network Computers to access business critical applications running on IBM CICS servers, including CICS Transaction Servers and TXSeries servers, using standard Internet protocols, in a range of configurations.

The CICS Transaction Gateway Version 3.0 incorporates, in a single integrated product, the CICS Universal Clients Version 3.0, which provide its functions for communication with CICS servers. There is no requirement for the separate installation of the CICS Universal Clients. All CICS Universal Client functions are available at a machine running the CICS Transaction Gateway.

The CICS Transaction Gateway also replaces and integrates two previous gateway functions: the CICS Internet Gateway (delivered, for the OS/2 and Windows NT platforms, as part of the CICS Clients Version 2); and the CICS Gateway for Java (TM) (available for download from the Internet, for use with the respective CICS Clients Version 2 or CICS for UNIX (R) Clients). The CICS Transaction Gateway is based on many years of experience with CICS Clients and Gateways in large numbers of demanding customer applications, and represents a streamlined and efficient implementation of the gateway functions.

The CICS Transaction Gateway Version 3.0 is provided for the OS/2, Windows NT, AIX, and Solaris platforms.

  • In addition, the CICS Transaction Gateway supports the Windows 98 platform (also Windows 95), for application development only. It is not supported for production use on this platform.
The CICS Transaction Gateway Version 3.0:
  • Provides the widest possible access to CICS business applications

    CICS Transaction gateway enables any Web browser, Network Computer or Internet-enabled consumer device to access business applications running on CICS servers, using one of three possible methods:

    1. All Web browsers support HTTP. The CICS Transaction Gateway will render existing CICS 3270 applications into HTML automatically, and transmit to the browser using HTTP. Customers can also create their own Java servlets which present information from CICS applications in HTML forms, customized as required.

    2. Java-enabled Web browsers can run Java applets. The CICS Transaction Gateway enables customer applets to access CICS 3270 applications and CICS programs using supplied Java classes and Java beans.

    3. ORB-enabled Web browsers can run Java beans which interoperate with server-side Java beans (running on the CICS Transaction Gateway) via the CORBA IIOP protocol. The server-side beans can then invoke CICS 3270 applications and CICS programs using supplied Java classes.
  • Supports easy development of customer solutions

    CICS Transaction Gateway provides a straightforward installation process that enables developers to set up and administer a gateway server easily. In the Windows NT environment, installation is performed using InstallShield.

    CICS Transaction Gateway provides an implementation of the IBM Common Connector Facility as a set of Java beans which integrate well into an Integrated Development Environment (IDE), such as IBM VisualAge for Java. VisualAge provides a visual construction facility which allows beans to be connected together to rapidly create working solutions.

    It also provides implementations of IBM's well proven ECI (External Call Interface) and EPI (External Presentation Interface) programming interfaces in C, C++, and COBOL, and as COM objects.

  • Provides high performance and scalability

    The CICS Transaction Gateway is a highly optimized, multi-threaded Java application that can concurrently support large numbers of connected browsers with sub-second response times. It exploits the capabilities of the embedded CICS Universal Clients Version 3.0 for efficient communication with CICS servers, and can exploit the capabilities of (SMP) Symmetric Multi-Processor hardware for high transaction throughput. It also incorporates a sophisticated workload balancing facility which allows the transaction workload from a large population of browsers to be distributed across multiple CICS regions or CICS servers.

  • Provides comprehensive security capabilities

    The CICS Transaction Gateway provides comprehensive support for multiple aspects of security, which are critical to successful Internet operation. These are:

    1. Privacy, via implementations of (SSL) Secure Sockets Layer, and of HTTP-S (HTTP over SSL). These encrypt data flowing between the browser and the Gateway server.

    2. Authentication, via built-in support for user IDs and passwords that are authenticated by CICS application servers. In addition, it provides an External Security Interface (ESI), which enables customer applications to verify user IDs and passwords and to change expired passwords.

    3. Authorization, which is provided as a standard function of each CICS server, enabling customers to control what transactions a given end user can run and what data that user can access.
  • Provides robust, multi-platform implementation

    The CICS Transaction Gateway provides a single, consistent Java implementation across multiple server platforms, exploiting the "write once, run anywhere" capability of Java, and based upon the new CICS Universal Clients Version 3.0, with their common 32-bit implementation running on multiple operating systems and communications protocols.

The CICS Transaction Gateway includes a set of Java EPI Beans for creating Java front ends for existing CICS 3270 applications, without any programming. This enables Java applications or applets to be created, simply by the use of a tool such as VisualAge for Java, which enable existing CICS applications designed for the use of 3270 terminals to interface with the Web browser or Java enabled environment. A CICS Transaction Gateway (MVS (TM)) will be made available that provides direct access from a Web server to CICS Transaction Server for OS/390 Release 3 using the external CICS interface (EXCI).

CICS Universal Clients Version 3.0: The CICS Universal Clients, which are integrated into the CICS Transaction Gateway, are also available for separate installation. For information on the functions of the CICS Universal Clients Version 3.0, refer to the prior Supplemental Information description section.

CICS Gateway for Java: The CICS Gateway for Java Version 2.0.1 remains available for download from the Internet, but it is only supported with the CICS Clients Version 2 and the CICS for UNIX Clients for the respective platforms, which also remain available. It is not supported with the CICS Universal Clients Version 3.0.

CICS Internet Gateway: The CICS Internet Gateway remains available for the OS/2 and Windows NT platforms in the CICS Clients Version 2, and for AIX in the Transaction Server for AIX, Version 4.1, the TXSeries, Version 4.2 for AIX, and on the CICS Clients Version 2 CD-ROM. It is not supported for use with the CICS Universal Clients Version 3.0.

CICS and Lotus Notes (R): The CICS Gateway for Lotus Notes (also referred to as the CICS Link for Lotus (R)), remains available in the CICS Clients Version 2. It is not included in the CICS Transaction Gateway. For interoperation of CICS and Lotus Notes, you are recommended to use the MQSeries (R) Enterprise Integrator, which has functional enhancements above the CICS Gateway for Lotus Notes. It offers a common API that can be used to integrate Lotus Notes with IMS (TM) or MQSeries as well CICS; it supports the EPI as well as the ECI; and it can be driven directly from a Web browser connected to Domino (TM). (Note that the CICS Transaction Gateway does not require the use of MQSeries in order to access CICS.) MQSeries Enterprise Integrator 1.0 is included in MQSeries and CICS Connections for Domino, part of the Lotus Domino.Connect (TM) family. For more information and to order, access:

For the licensing of the CICS Transaction Gateway for use with different CICS servers, refer to the Terms and Conditions section.



EDUCATION SUPPORT

The CICS curriculum, that includes a migration class, is available.

Descriptions of all classroom and self-study courses are contained in the Catalogs of IBM Education and Training.

Call IBM Education and Training at 800-IBM-TEACH (426-8322) for education catalogs, schedules, and enrollments.



OPEN BLUEPRINT (R)

CICS Transaction Server for OS/390 provides the capability for distributed parts of an application to "converse" with one another. Its implementation is consistent with the Conversational function described in IBM's Open Blueprint. It provides the Common Programming Interface for Communications (CPI-C) industry-standard interface from X/Open. It supports the Advanced Program-to-Program Communication (APPC) protocol from IBM to facilitate open, distributed, multivendor interoperability.



TECHNICAL INFORMATION



Specified Operating Environment

Hardware Requirements

Processors: CICS Transaction Server for OS/390 runs on any IBM S/390 (R) processor that supports OS/390 Version 2 Release 5 (or later) and has enough processor storage to meet the combined requirements of the host operating system, CICS TS, the access methods and the application programs. These include:

  • All models of the S/390 Parallel Enterprise Servers or S/390 Parallel Transaction Servers (IBM 9672)

  • All models of the S/390 Multiprise (TM) 2000

  • All models of the IBM ES/9000 (R) Processor Unit 9021, the 9121, or the 9221

  • An IBM ES/3090 (TM)-9000T processor (Models 15T, 17T, 18T, 25T, 28T) that supports IBM Enterprise Systems Architecture/370 (TM) (ESA/370) and must have optional ESA/390 (TM) facilities

  • PC Server System/390 (R) or RS/6000 (TM) and System/390 Server-on-Board
CICS TS is dependent on the MVS logging function, requiring either the DASD logging function for a single-system or a coupling facility for a Parallel Sysplex (R) system.

Coupling Facility: A CICS Transaction Server for OS/390 on a Parallel Sysplex system must have one or more coupling facilities with their associated coupling links installed, unless using the Integrated Coupling Migration Facility (ICMF) or Internal Coupling Facility (ICF).

However, a coupling facility is not required for a single MVS image when using the "DASD-only option" of the MVS system logger. This option provides support for single or multiple sysplexes that do not include a coupling facility (non-parallel sysplex).

A coupling facility can be defined in one of three ways:

  1. A stand-alone IBM 9674

  2. A PR/SM (TM) logical partition (LPAR) running the coupling facility control code. Processors that can enable the coupling facility function in a logical partition include:
    • ES/9000 9021 711-based models
    • ES/9000 9121 511-based models
    • S/390 Parallel Enterprise Servers (9672)
    For the 9121 511-based models, it is necessary to use ICMF in this configuration to provide coupling facility functions.

  3. A PR/SM (TM) logical partition with ICMF for both the 9021 711-based and 9121 511-based processors, or the S/390 Parallel Enterprise Servers (9672). This latter configuration does not require the coupling links.
In general, a stand-alone coupling facility is recommended for a production environment to eliminate a single point of failure and two coupling facilities are recommended for high availability.

For customers intending to open data sets in RLS mode, further hardware information is provided.

An upgrade to the coupling facility to CFLEVEL=2, is necessary to run in the RLS environment. In order to upgrade to this licensed internal code, the following upgrades to the coupling facility are required:

  • 9674-C01 or 9672-R1 level machines:
      E/C D79756 (SE) MCLS 033,034,035 for DR46 E/C D79533 (SE) MCLS 058,059,060 for DR44
  • 9674-C02/C03 or 9672-R2/R3 level machines:
      E/C E45568 (SE) MCLS 058,059,060 for DR66 E/C E12981 (SE) MCLS 082,083,084 for DR64
  • ES/9000 9021 711-based machines:
      SEC 236422 CFCP0048-54
  • ES/9000 9121 511-based machines:
      SEC C35956 CFCP0041-47
Other Sysplex Hardware: Customers migrating to S/390 Parallel Sysplex, and with multiple processors sharing data across MVS images also require:
  • The IBM Sysplex Timer (R) to provide a common external time source

  • DASD controllers with enough paths to dedicate one to each processor (CPC) in the Sysplex, or a director to provide the paths
Storage: Compared with the prior release of CICS TS, central storage usage will not change significantly.

Terminals: Current and new terminals will be supported by CICS Transaction Server for OS/390 if they are accessed through VTAM (R) or TCAM(DCB).

TCP/IP attached systems or workstations will be supported, if either the CICS ONC RPC function of CICS or the CICS basic TCP/IP sockets feature of OS/390 Version 2 (5647-A01) are used. Access via TCP/IP is also provided with CICS Internet support and with the TCP62 protocol support.

The list of current terminal types, with modes of connection, is documented in the CICS Resource Definition Guide (SC33-1684).

DASD: Support for any new disk device will be completely transparent to CICS Transaction Server for OS/390. Support is provided in the standard access methods used by CICS.

Customers needing the concurrent copy of active files or databases will need to install IBM 3990 Model 3 or Model 6 DASD controllers.

Tapes: CICS Transaction Server for OS/390 will continue to support current tape devices, including IBM 3480. There is no support for tape logging. There are no restrictions on the use of tapes for extra partition transient data.

Printers: Support for any new VTAM attached printers will be completely transparent to CICS Transaction Server for OS/390, assuming these printers are compatible with currently supported models.

CICS Universal Clients and CICS Transaction Gateway: The CICS Universal Clients Version 3.0 will run on any hardware capable of running the appropriate operating system and other prerequisite software.

The support for the CICS Universal Clients Version 3.0 for OS/2, Windows NT, and Windows 98 is for any IBM compatible machine. NEC PC 98 series hardware is also supported.

Requirements for hard-file space for the CICS Universal Clients Version 3.0 are in the region of:

OS/2                     8 MB
                          +5 MB for TCP62
Windows NT               8 MB
                          +5 MB for TCP62
Windows 98               8 MB
                          +5 MB for TCP62
AIX                      4 MB
Solaris                  4 MB

The CICS Transaction Gateway Version 3.0, will run on any hardware capable of running the appropriate operating system and other prerequisite software.

Requirements for hard-file space for the CICS Transaction Gateway Version 3.0 are in the region of:

OS/2                     11 MB
                          +5 MB for TCP62
Windows NT               11 MB
 (also Windows 98)        +5 MB for TCP62
AIX                      8 MB
Solaris                  8 MB

Software Requirements

Minimum Infrastructure for CICS Transaction Server for OS/390: Requirements are the same as CICS TS Release 1, except as noted by an (*), where the later level is the minimum required. Refer to Software Announcement 296-349 dated September 10, 1996.

OS/390 Version 2 (5647-A01) Release 5 or later *

The following products, as required by the customer for related functional purposes:

CICS Transaction Server for OS/390

ACF/TCAM(DCB) (5735-RC3) Version 2.4 + PTFs or ACF/TCAM(DCB) (5665-314) Version 3.1 + PTFs IMS/ESA (R) Database Manager (5695-176) Version 5.1 (5655-158) Version 6.1* DB2 (5685-DB2) Version 3.1 (<-DB2 3.1 Service ends December 31, 1998) DB2 (5695-DB2) Version 4.1* DB2 (5655-DB2) Version 5.1* DB2 (5645-DB2) Version 6.1* OS PL/I-R/T (5668-910) Version 2.3 CICS VSAM Recovery Version 2.3 (CICSVR) (5695-010) TIVOLI Performance Reporter for OS/390 (5695-101) Version 1.3 *

CICS Clients (5639-001) Version 2.0.4, with service level 7 applied, or later *

*     NetView (R) for MVS/ESA (TM) Version 3 Release 1 (5655-007), or
      later, required to provide a Resource Object Data Manager
      (RODM) repository that CICSPlex System Manager exploits through
      the use of NetView MultiSystem Manager Version 2 Release 2
      (5655-126)

Note: OS/390 Version 2 Release 5 (5647-A01) includes many products required by CICS as exclusive elements of OS/390.

For information on compilers and assemblers, refer to CICS Release Guide (GC33-1570).

The information above shows minimum prerequisite software levels and they do not support specific new functions in any of the releases listed (refer to below).

Note: For communication from/to either CICS/ESA Version 3 Release 3 or CICS/ESA Version 4 Release 1 via advanced program-to-program communication (APPC) to CICS Transaction Server for OS/390, the following prerequisite APARs must be applied to the earlier releases:

Release                                           APAR

CICS/ESA Version 3 Release 3 (PTF is UN79397) PN71911 CICS/ESA Version 4 Release 1 (PTF is UL80372) PN73189

Requirements Beyond Minimum Function

------------------------------------------------------------
 New Function       Introduced      Prerequisite
 Description         in CICS        Software
------------------------------------------------------------
 IMS DB with SSP    Version 3.3
 IMS DB N-way           --        IMS/ESA Database Manager
  Data Sharing                      (5695-176) Version 5.1
 Database2 (DB2)        --        DB2 (5695-DB2)
  Data Sharing                      Version 4 Release 1
------------------------------------------------------------

Note: Refer to CICS Migration Guide (GC33-1571) for guidance on copying DFHIRP within a Parallel Sysplex, for use with XCF MRO when using MVS Cross System Coupling Software.

Note: The following VTAM information advises on what service is recommended for any Parallel Sysplex:

  • Information APAR II08658 relates to Advanced Peer-to-Peer Networking (R) (APPN (R)) on ACF/VTAM (R) 4.2.

  • Information APAR II01501 relates to service for multi-path channel and APPN host-to-host channel.

  • The SYSPLEX -- PSP Bucket for DATASHARING has a VTAM subset. This includes Generic Resource recommendations.
------------------------------------------------------------
 New Function Description
 (Introduced in CICS Transaction     Prerequisite
  Server for OS/390)                 Software
------------------------------------------------------------
 Long Temporary Storage              RACF (5695-039)
  Queue Names                         Version 2.2*
 CICS enhancement to EXCI for
  resource recovery using
  MVS recoverable resource           OS/390 Version 2
  management services (RRMS)          Release 5*
                                      + PTF UW46914
 Java Language Support               IBM VisualAge for
                                      Java, Enterprise
                                      Edition for OS/390
                                      (5655-JAV),
                                      Version 2.0*
 Java Client Support                 OS/390 (5647-A01)
                                      Version 2.5*
                                      for Java Developer
                                      Kit/Runtime 1.1
                                     Java for OS/390
                                      (5655-A46)
                                      CICS Gateway
                                      for Java (MVS) V2.1.0*
------------------------------------------------------------

Required PTFs (OS/390 and associated products):

  • RRMS (OS/390 V2 R5) UW46914
  • RACF certificate support PTFs UW91119, UW91120
The following APARs are required before using Java Language support:
  • OW31036 bind with long object names

  • OW31718 DFSMS (TM) 1.4 invalid loader storage check

  • OW31924 IEW2333E Invalid syntax in IMPORT control statement

  • OW32111 IEW2900T E913 Binder abnormal termination 3D052900 2010 16

  • OW32261 IEW2900T E913 Binder abnormal termination 3D052900 1077952576 16

  • OW32334 IEW2900T E913 Binder abnormal termination 35602900

  • OW33782 DFSMS 1.4 DESERV to set output buffer length for PDSE access

  • OW34052 Load optimization for C_WSA for DLLs in dynamic LPA

  • OW34052 affects the program object size recorded by the Binder in the PDSE directory, and hence the amount of storage CICS allocates for a directed load.

  • PQ08747 In order for LE to support double precision floating-point in single thread environment

  • PQ17512 0C4 when signal occurs in stack extension boundary

  • Info APAR (II11025) on RETAIN (R), lists all the CICS TS and LE 1.8 compatibility fixes
The following APARs are recommended when using CICS LINK:
  • LE APAR PQ14883 + COBOL APAR PQ16794
  • LE APAR PQ14888
  • LE APAR PQ17931
CICS VSAM Recovery Version 2 Release 3 (5695-010) (CICSVR 2.3) is required for VSAM forward recovery with the logging function in MVS.

The later level of software and its prerequisites are required only to support the indicated new functions. PTFs may be required for any of these new functions.

CICS Universal Clients and CICS Transaction Gateway: The CICS Universal Clients Version 3.0 support the following Operating Systems:

For the CICS Universal Client for OS/2:

  • OS/2 Warp Version 4
  • OS/2 Warp Server Version 4
For the CICS Universal Client for Windows NT:
  • Windows NT Workstation Version 4.0, or later

  • Windows NT Server Version 4.0, or later (including versions for DBCS languages)
For the CICS Universal Client for Windows 98:
  • Windows 95
  • Windows 98
For the CICS Universal Client for AIX:
  • AIX Version 4.2.1, or later
  • AIX Version 4.3.1, or later
For the CICS Universal Client for Solaris:
  • Solaris Version 2.5.1, or later
For SNA Communications from CICS Universal Clients Version 3.0, the following communications products are required:
Universal
Client
Platform          Supporting Products -- One Of:

OS/2 IBM Communications Server for OS/2 Warp, Version 4.0, or later (including eNetwork (TM) Communications Server for OS/2 Warp Version 5.0)

Windows NT Microsoft (TM) SNA Server Version 3.0, or later IBM Communications Server for Windows NT Version 5.0, or later (including IBM eNetwork Communications Server for Windows NT, Version 5.01) IBM Personal Communications AS/400 (R) and 3270 for Windows NT Version 4.11 with APAR IC16672, or Version 4.2

Windows 98/95 Microsoft SNA Server Version 3.0, or later IBM Personal Communications AS/400 and 3270 for Windows 95 Version 4.11 with APAR IC17000, or Version 4.2 AIX IBM Communications Server for AIX, Version 4, or later

For TCP/IP communication from CICS Universal Clients Version 3.0 on all platforms, support is included in the Operating System.

For NetBIOS communication from CICS Universal Clients Version 3.0 for OS/2, Windows NT, or Windows (98/95), support is included in the Operating System.

TCP62 support for the CICS Universal Client for OS/2 requires IBM eNetwork Communications Server for OS/2 Warp, Version 5.0; APAR JR10793 must be applied.

With the CICS Universal Clients Version 3 for Windows NT and Windows 98, if SNA communications are required as well as TCP62, IBM Personal Communications AS/400 and 3270, Version 4.2 should be used.

For use of DCE with the CICS Universal Client for Windows NT, DCE Runtime Services are required. The DCE products supported are:

  • IBM DCE for Windows NT Versions 1.1.1 or 2.0
  • Digital DCE for Windows NT Version 1.1c
  • Gradient PC-DCE Version 2.0 for Windows NT/95
Products with which LU alias names may be used are:
.--------------------------------+------+---------+--------.
| Product                        | OS/2 | WIN NT  | WIN 98 |
|--------------------------------+------+---------+--------|
| IBM Personal Communications    |      |    X    |    X   |
|--------------------------------+------+---------+--------|
| Microsoft NA Server --         |      |         |    X   |
| Client                         |      |         |        |
|--------------------------------+------+---------+--------|
| Microsoft SNA Server           |      |    X    |        |
|--------------------------------+------+---------+--------|
| IBM Communications Server for  |      |    X    |    X   |
|  Windows NT -- Client          |      |         |        |
|--------------------------------+------+---------+--------|
| IBM Communications Server for  |      |    X    |        |
|  Windows NT                    |      |         |        |
|--------------------------------+------+---------+--------|
| IBM Communications Server for  |   X  |         |        |
|  OS/2 Warp, Version 4,         |      |         |        |
|  or later                      |      |         |        |
|--------------------------------+------+---------+--------|
| NetWare for SAA Client         |      |    X    |    X   |
|  (Note that with NetWare       |      |         |        |
|  for SAA, LU names             |      |         |        |
|  can only be aliases)          |      |         |        |
'--------------------------------+------+---------+--------'

Password management using the PEM service transaction is supported using the following protocol drivers:

.-------------------------+-----------+-----------.
|    Client Platform      |   TCP62   |    SNA    |
|-------------------------+-----------+-----------|
|    OS/2                 |  CCLTCP62 |  CCLIBMSN |
|-------------------------+-----------+-----------|
|    Windows NT           |  CCLTCP62 |  CCLWNTSN |
|    Windows 98           |           |           |
'-------------------------+-----------+-----------'

The following compilers and application development tools are supported:

.-----------------------+----------------------------------.
| Client Platforms      |                                  |
|-----------------------+----------------------------------|
| OS/2                  |    VisualAge C++ Version 3.0,    |
|                       |     or later                     |
|                       |    VisualAge PL/I Version 2.0,   |
|                       |     or later                     |
|                       |    IBM REXX for OS/2             |
|-----------------------+----------------------------------|
| OS/2, Windows NT,     |    VisualAge COBOL Version 2.1,  |
|  Windows 98/95        |     or later                     |
|-----------------------+----------------------------------|
| Windows NT,           |    VisualAge C++ Version 3.5,    |
|  Windows 98/95        |     or later                     |
|                       |    Microsoft Visual C++          |
|                       |     Version 5.0, or later        |
|                       |    Micro Focus COBOL             |
|                       |     Version 4.0.26               |
|                       |    Microsoft Visual Basic        |
|                       |     Version 4.0, or later        |
|-----------------------+----------------------------------|
| AIX                   |    IBM C for AIX and C Set++     |
|                       |     for AIX Version 3.1,         |
|                       |     or later                     |
|                       |    IBM COBOL Set for AIX         |
|                       |     Version 1.1, or later        |
|-----------------------+----------------------------------|
| Solaris               |    Sun WorkShop C++              |
|                       |     Version 3.0.0                |
|                       |    Micro Focus COBOL             |
|                       |     Version 4.0.05               |
'-----------------------+----------------------------------'

The CICS Transaction Gateway Version 3.0 supports the following Operating Systems:

For the CICS Transaction Gateway for OS/2:

  • OS/2 Warp Version 4
  • OS/2 Warp Server Version 4
For the CICS Transaction Gateway for Windows NT:
  • Windows NT Workstation Version 4.0, or later

  • Windows NT Server Version 4.0, or later (Including versions for DBCS languages)
For the CICS Transaction Gateway for Windows 98:
  • Windows 98
  • Windows 95 (Including versions for DBCS languages)
For the CICS Transaction Gateway for AIX:
  • AIX Version 4.2.1, or later
  • AIX Version 4.3.1, or later
For the CICS Transaction Gateway for Solaris:
  • Solaris Version 2.5.1, or later
The CICS Transaction Gateway Version 3.0 runs on a Java-enabled platform, and requires the following minimum levels of Java Development Toolkit (JDK) installed:
  • OS/2: JDK 1.1.6, or later

  • Windows NT: JDK 1.1.6, or later, with JIT update

  • Windows 98/95: JDK 1.1.6, or later, with JIT update

  • AIX: JDK 1.1.6, or later

  • Solaris: JDK/JIT V1.1.6 for SPARC-based machines, or later, with native threads support for Solaris Version 2.5.1, or later
The CICS Transaction Gateway requires, for servlet functions, a Web server that supports servlets. It has been tested with the following Web servers:
  • Lotus DominoGoWeb Server Release 4.6.2 (for OS/2 Warp, Windows NT, AIX, or Solaris)

  • Microsoft Internet Information Server (IIS) Version 4.0 (for Windows NT and Windows 98/95)

  • IBM Websphere Version 1.0 (for Windows NT, AIX, or Solaris)

  • Apache Version 1.3 (for AIX and Solaris)

  • Sun WebServer Version 1.0 (for Solaris)
The CICS Transaction Gateway may be used for HTML/HTTP functions with any Web browser that supports HTML Version 3. For use with Java functions, a JDK 1.1 compliant Java-enabled Web browser is required. It has been tested with the following:
  • OS/2: Netscape Navigator Version 2.0.2 with 1.1 patch

  • Windows NT, 98, 95: Internet Explorer Version 4.0.1

  • Windows NT, 98, 95: Netscape Version 4.0.3 with 1.1 patch

  • AIX: Netscape Navigator Version 4.0.4

  • Solaris: Sun HotJava (TM) Browser, Version 1.1
The data for CICS Transaction Gateway for supporting products for communications, and for supported compilers and application development tools, is the same as that for CICS Universal Clients. Refer to material on the CICS Universal Clients for this information.

Compatibility: CICS Transaction Server for OS/390 provides compatibility with prior versions of CICS as indicated.

Application Programming: CICS Transaction Server for OS/390 provides upward compatibility from CICS/ESA Version 4 Release 1, CICS/ESA Version 3 Release 3, at both source and object level for CICS application programs and maps, subject to the exceptions and comments summarized below and further described in the CICS Release Guide (GC33-1570). Any other exceptions that are identified will be documented in CICS publications.

  • Command-level programs are upward compatible at both source and object level, provided the function is still supported. However, support for the EXEC CICS ADDRESS CSA command was discontinued (CICS/ESA Version 3 Release 2.1).

  • EXEC CICS API for the CICS Web Interface

    The current interface to the Template Manager uses an EXEC CICS LINK to program DFHWBTL. A suite of new EXEC CICS commands is provided to allow user applications to retrieve information from inbound HTTP requests, and to build appropriate HTTP responses.

  • Coupling facility data tables do not support key lengths greater than 16 bytes.

  • Application programs that refer to old logs and journals should be reviewed in the light of the CICS use of the MVS logger.

  • Support is retained for CALL DL/I statements as well as EXEC DLI.

  • For access to IMS databases from CICS Transaction Server for OS/390, customers must use the IMS/ESA DB Control (DBCTL) interface.

  • IMS/ESA Version 3 Release 1 and IMS/ESA Version 4 Release 1 databases can not be accessed using local DL/I from CICS Transaction Server for OS/390. CICS/ESA Version 4 Release 1 was the last CICS release, and IMS/ESA Database Manager Version 4 Release 1 was the last IMS release, with support for CICS local DL/I and batch shared database access.

  • Macro-level program support was discontinued (not supported after CICS/MVS (R) Version 2 Release 1.2).

    The DFHMSCAN utility program, available now with all current releases, is recommended for reviewing CICS application program libraries. The DFHMSCAN utility program can be run against each application load library to find in which application programs CICS macros are used. The DFHMSCAN utility program can also be used to check on use of the EXEC CICS ADDRESS CSA command.

  • Basic mapping support (BMS) maps that are defined using CICS-supplied macro instructions, or defined online using Screen Definition Facility II (5665-366), are upward compatible.
CICS Universal Clients and CICS Transaction Gateway: ECI and EPI applications written for the CICS Clients on Intel platforms can be easily ported to the CICS Universal Clients for AIX and Solaris.

Application code written for the CICS for UNIX Clients for the AIX and Solaris platforms can be easily ported to the CICS Universal Clients for those platforms, but will usually require some minor recoding to allow for differences in names.

The CICS Universal Clients for AIX and Solaris, unlike the CICS for UNIX Clients for those platforms, do not have the Local Client interface for operating with the CICS servers on these platforms; they can only operate as local clients by using the TCP/IP interface.

Unlike the CICS for UNIX Clients for AIX and Solaris, the CICS Universal Clients for AIX and Solaris neither require nor support DCE.

The following are some of the principal differences between the CICS Universal Clients for AIX and Solaris, and those for Intel platforms:

  • The CICS 3270 emulators in the CICS Universal Clients for AIX and Solaris are 24x80 alphanumeric screens. There is no GUI support.

  • The CICS 3270 emulator in the CICS Universal Clients for AIX and Solaris does not support keyboard remapping for Alt shifted keys, Ctr/Act, Print Screen, Scroll Lock, or Pause.

  • The CICS Universal Clients for AIX and Solaris do not support NetBIOS or TCP62 communication.

  • At present, the CICS Universal Client for Solaris Version 3.0 does not support SNA communication.

  • The CICS Universal Client for AIX uses the AIX SNA Side Information Profile to provide partner LU information.

  • The CICS Universal Clients for AIX and Solaris have a command line interface only.

  • The CICS Universal Clients for AIX and Solaris do not support REXX.

  • The CICS Universal Clients for AIX and Solaris do not have field outlining on CICSTERM.
Sample HTML pages are supplied to assist you in getting started in using a Web browser as an emulator for a 3270 CICS application. These may also be used to assist in migrating from the CICS Internet Gateway to the CICS Transaction Gateway.

Applications and applets written for use with any level of the CICS Gateway for Java will work with the CICS Transaction Gateway Version 3.0.

EPI and ECI applications written for the CICS Clients Version 2 for OS/2 or Windows NT, or for the CICS for UNIX Clients for AIX or Solaris, will work with the CICS Transaction Gateway Version 3.0.

Systems Programming: If migrating from a version of CICS before Version 3, the following guides should also be obtained:

  • Migration Guide for Version 3 Releases 1 and 2 (GC33-0656)

  • CICS/ESA Version 3 Release 3 Release Guide (GC33-0792)
Both these provide guidance and details about operational and systems programming procedures. These are not covered in the new CICS Migration Guide (GC33-1571).

The SupportPac (TM) CA1C for migration to CICS Transaction Server for OS/390 is recommended, as well as the SupportPac CA1B for migration from CICS/MVS Version 2 Release 1.2 to CICS/ESA Version 4 Release 1.

HTML templates are now a CICS resource, definable using RDO or the EXEC CICS CREATE command, and can be stored in CICS Temporary Storage or CICS-managed files.

The CICS Migration Guide (GC33-1571) includes discussion on planning for migration to a VSAM record-level sharing environment from a CICS configuration that uses one or more CICS file-owning regions (FORs) in order to share VSAM files. The following are covered:

  • Data set eligibility

  • Read integrity

  • The LOCKED exception condition

  • Restricting switching between RLS mode and non-RLS mode access

  • Defining the coupling facility structures

  • Defining the sharing control data sets

  • Defining SMS storage classes

  • Changes to deadlock detection
The guide also covers the migration from a CICS region with local DL/I support to a CICS that uses IMS Database Control (DBCTL) to access DL/I databases.

The utility program, DFHLSCU, was enhanced for DASD-only log streams to help estimate staging data set sizes for CICS system and general logs (CICS TS Release 2).

For coupling facility log streams (Parallel Sysplex), the utility program DFHLSCU provides help to establish values for the following parameters used to define the structure for log blocks in a coupling facility for CICS log streams.

  • AVGBUFSIZE -- average buffer size of the log stream

  • INITSIZE -- initial amount of space allocated in CF for the structure

  • SIZE -- maximum size of log stream structure

  • STG_SIZE -- size of staging data set required by the log stream
These control the efficient use of space within the structure, and can prevent undue DASD offloading.

While DFHLSCU is supplied with CICS TS, it is also available as a SupportPac, CD14, to run on your CICS Version 3/Version 4 systems to aid in planning for coupling facility use with CICS TS and the MVS Logger.

For details on how to use DFHLSCU, refer to the CICS Operations and Utilities Guide (SC33-1685).

A sample log stream utility program, SAMLSUP, available in SupportPac CS1D, formats, copies, prints or deletes a log stream.

Other useful SupportPacs include:

  • CE19: Replicating Shared Data Tables across a sysplex

  • CA1E: CICS Transaction Server for OS/390 3270 Bridge Passthrough Transaction.

  • CA86: An enhanced CICS Web Interface analyzer

  • CA87: A CICS Web Interface to REXX for CICS/ESA
A utility program, DFHBMSUP, is provided to disassemble BMS maps in a loadlib, to aid BMS map regeneration for use with 3270 bridge.

The CICSPlex SM element of CICS TS Release 3 does not support the following levels of CICS:

  • CICS/MVS Version 2.1.2 (5665-403)
  • CICS/ESA Version 3.3 (5685-083)
  • CICS/VSE Version 2.2 (5686-026)
  • CICS for OS/2 Version 2.01 (5648-036)
The following functions previously available in CICS/ESA Version 4 are discontinued:
  • Control of CICS-DB2 interface using macro-defined, assembled and linkedited CICS Resource Control Table (RCT). (refer to the Planning Information section)

  • Support for local DL/I and batch shared database access. Database access will continue to be supported with the DBCTL interface.

  • Support for the PROTECT option for VTAM terminals. Full protection of application and business logic is supported with the use of APPC function.

  • Support for logging or journal output to tape.

  • Support for journal exits and journal user replaceable modules. Any programs that refer to old logs and journals should be reviewed in the light of the MVS logger support.

    Also formats of several of the system log record types are changed. (Details are provided in the current documentation of this product.)

  • Some of the CICS utility programs provided with prior versions are now obsolete. Refer to the CICS Migration Guide (GC33-1571) for more information.
The following functions previously available in CICS/ESA Version 3 were discontinued in Version 4:
  • Direct addressing of CICS control blocks by any means, even for exits.

  • Control of maximum tasks (CMXT/CMXTLIM) is replaced by resource definition (RDO) transaction class objects.

  • The sign-on table (SNT).
The following functions previously available in CICS/MVS Version 2 and CICS/OS/VS Version 1 were discontinued in Version 3:
  • Support for macro-level execution

  • Direct addressing of CICS control blocks (other than the EIB and user areas such as CWA) from within CICS applications

  • EXEC CICS ADDRESS CSA command

  • CICS internal security (refer to the Planning Information section)

  • DFHXSP and DFHXSE as user-replaceable modules

  • CSMT, CSST, CSOT, CSSN and CSSF transactions

  • System initialization modifications (SIMODs)

  • PCT, PPT and TCT, generated by resource definition macros
TCT definition for TCAM (DCB), remote BTAM devices and sequential terminals must be done with DFHTCT macros. There is no support for the graphical access method (GAM).

Discontinued Device Support: There is no support for devices and controllers accessed using BTAM, GAM or TCAM (ACB), in any CICS version after CICS/MVS Version 2 Release 1.2. TCAM (DCB) will continue to be supported.

Limitations: A hardware failure without a stand-alone coupling facility could cause a double failure (both in the MVS and in the coupling facility), causing a "lost locks" condition for data sets currently opened in RLS mode by CICS.

Only files that have lost locks will not be able to be accessed. Transactions without references to these files will continue to execute.

Note: "Lost locks" recovery consists of backout of in-flight transactions and resolution of any in doubt or backout-failed transactions. No CICS can execute any new transactions that try to access a data set that has suffered a lost locks condition until all of the CICSs have completed lost locks recovery for that data set. Each data set can be used by new transactions as soon as its lost locks recovery is completed.

Performance Considerations: Throughput: Comparisons with CICS Transaction Server for OS/390 Release 2, using an IBM Internal Benchmark, show that the ITR achieved with CICS TS Release 3 using coupling facility log streams is equivalent to CICS TS Release 2. Similar comparisons made for CICS TS Release 2 using DASD only log streams were between 0-5% less depending on the hardware configuration used. More detail will be available later when performance information can be obtained.

Performance information will be provided by February 26, 1999.

In order to assist in the capacity planning in an RLS environment, Quicksizer and CP90 are available.

Disclaimer: Performance benefits to be obtained in user installations are dependent on the CICS workload characteristics and on its usage within the total system environment.

User Group Requirements: This announcement satisfies or partially satisfies 7 requirements from one or more of the worldwide user group communities, which include Australasian SHARE/GUIDE (ASG), COMMON, COMMON Europe, GUIDE International, G.U.I.D.E. Europe, Japan GUIDE/SHARE (JGS), Guide Latin American (LAG), SHARE EUROPE, and SHARE Incorporated.

In addition, 23 requirements submitted by customers through their IBM representatives are satisfied.

Long TS Queue Names:

 EBCICD89012         (237): Queue names shall be 16
                              characters

CICS Web interface enhancements

 PASR R066279-1     (4139):  Remove 32 K byte inout
                              limitations of CWI
 PASR R066279       (4140)
 PASR R067918       (3166)

Global enqueue (ENQ) and dequeue (DEQ)

 GBCICS93002        (3031): (CEMT I UOWENQ extended)
 EBCICU92005        (3080): CICSplex-wide ENQ and
                              DEQ mechanism
 GBCICS93030        (3138): Provide extended ENQ
                              DEQ facility
 PASR R044415       (3451): SPI to support an ENQ
 SSCICS96002        (3894): Implement ENQUEUE and
                              DEQUEUE across
                              multiple regions
 PASR R062815       (4035): CICS Global ENQ/DEQ

Parallel Sysplex support extensions

 PASR R014899-2     (3455): Restore ability to
                             invoke CICS Dynamic
                             Transaction Routing
 PASR R047654       (3580): DFHDYP should support
                              ATI tasks
 PASR R062819       (4030): MPNS function only useful
 (APAR PQ01573)               in a planned outage
                              environment
 PASR R069344       (4215): Extend workload balancing
                              to other environments
                              including CWI
                              (include routing of
                              STARTS - DPL)

RDO for TST:

 SDCICS88040         (191): Provide a means to direct
 PSRR I074          (1237)    all auxiliary nonrecoverable
 PASR RJHY361       (1284)    queues to main
 AACMSX87001         (193): Provide a means to specify
                              a default sysid for the
                              TS-owning region
 PASR RJJV749        (709): Provide an ability in
                              CICS to generically
                              scan DFHTEMP within a
                              program to evaluate
                              temporary storage to
                              curtail (limit)
                              fragmentation
 PASR RKDJ717       (2385): Ability to display TS
 PASR RKIZ844       (2580)    queue names and
                              optionally purge

Autoinstall for Consoles

 PASR R053427       (3806): Autoinstall for Consoles
 PASR R053427-1     (3847)
 PASR R053427-3     (3979)
 PASR R053427-4     (4055)

System Management Changes (CICSPlex SM)

 PSRR UP1312:               Indication of vertical
                              scrolling position
 PASR R059080       (3939): ICWAIT message provided
                              so that WLM can report
                              why transactions are
                              hanging up
 PASR R062531       (4022): Need to separate BATCHREP
                              messages from
                              repository output
 PASR R065393       (4123): MAS/CMAS needs to be
                              shutdown from
                              console transaction
 PASR R068387       (4181): Remove CICSPlex SM API
                              requirement
                              for TASKDATAKEY=CICS
                     (150): WLMATAFF - Provide
                              summary view of
                              affinities vy MAS
                     (134): Hyperlink from CONNECTD
                              to SESSION
                     (135): Hyperlink from CICSRGND
                              to TASK view
                     (152): Display
                              REQUIRED/NOREQUIRED
                              status for PROGRAM view
                     (207): Add hyperlink MAS
                              to CICSRGN

Other Sources or Confirmation of Requirements

Key Customer Requirements

  • Support for complex business transactions

  • EXEC CICS API for Web document creation

  • HTML templates as a true CICS resource

  • Send and receive more than 32 K bytes of data in HTTP requests and responses

  • Web error program to allow users to override CICS default actions in the event of a failure

  • Shared data tables in the coupling facility

  • Enable CICSPlex System Manager applications from user-key

  • Scrolling CICSPLex System Manager help panels



Planning Information

Customer Responsibilities

Discontinued Device Support: There is no support for devices and controllers accessed using BTAM, GAM or TCAM (ACB). TCAM (DCB) will continue to be supported. There is no support for the IBM 7770 device. You should consider the IBM 9270 VRU, Voice Response Unit, as an alternative.

Programming and Operation Interfaces

  • CICS/ESA 4.1 removed the addressability to and changed the content of CICS control blocks. CICS exits do not have access to control blocks. Functions are available for exits to obtain information about the status of CICS facilities.
    • The API/SPI of CICS will continue to be enhanced to provide access to the required CICS control information and, where appropriate, the ability to manipulate that information.

    • Improvements are made for the continued protection of system control blocks against unauthorized access.

    • "Global User Exits" are provided, with improvements to the API/SPI available within them, so that information about CICS can be obtained without direct reference to CICS control blocks. However, these exits are product specific programming interfaces and may change in number and function from release to release. Compatibility of exits between releases is never guaranteed. Compatibility is provided for the API/SPI commands.

    • Users exit programs will abend if reference to the CSA or TCA is made.
  • Transaction CWBC is removed in CICS TS Release 3.

  • VSAM data set DFHWBCD is removed in CICS TS Release 3. It is replaced by the TCIPSERVICE resource type. Sample TCIPSERVICE definitions are supplied in the CSD group DFH$SOT.

    A new shared temporary storage queue, DFHWBxx, is provided, with definition in DFHCURDI.

  • The sign-on table (SNT) has been discontinued.

  • CICS internal security was discontinued with CICS/ESA Version 3 Release 3. CICS supports the external security manager interface, that can be used with RACF (or an equivalent security manager package) for security and for CICS operator data.

  • Trace interpretation tables, that were in the CICS Diagnosis Reference (LY33-6088) for the first release, and in the CICS User's Handbook (SX33-6104) for the prior release, are now in the CICS Trace Entries Handbook (SC34-5446).

  • CICS TS Release 2 was the last release of CICS to support running the CICS-DB2 interface using a macro-defined, assembled and linkedited CICS Resource Control Table (RCT). CICS TS only provides resource definition online (RDO) support for the RCT, with the RCT macro shipped only to allow macro-generation for migration of the RCT to the CSD.

  • In CICS TS Release 2, transactions in a bridge environment are run by starting a transaction known as a bridge transaction.

    In CICS TS Release 3 the prior method of running a transaction in a bridge environment is no longer supported and is superseded by the new START TRANSID BREXIT command. The newer design alleviates a number of security restrictions and useability problems caused by the number of bridge transaction definitions required to use the bridge.

  • Functions already discontinued include, among others:
    • The local DL/I interface to IMS/ESA, leaving DBCTL as the only supported interface. Changes made in CICS/ESA Version 4 Release 1 and available with CICS Transaction Server for OS/390 provide a number of enhancements to the CICS-DBCTL interface, notably an installation verification procedure (IVP) to ease migration to DBCTL, and a CICS-supplied transaction, CDBM, to simplify operator communication between CICS and DBCTL.

    • Support for the PROTECT option for VTAM terminals. Full protection of application and business logic is supported with the use of APPC function.

    • Support for logging or journal output to tape.

    • Support for journal exits and journal user replaceable modules. Any program that refers to old logs and journals should be reviewed because CICS uses the MVS logger support.

    • The formats of several system log record types have been changed. (Details will be provided in the early documentation of this release.)

    • Some of the CICS utility programs provided with prior versions are now obsolete. Refer to the CICS Migration Guide (GC33-1571) for more information.
  • CICS is dependent on the MVS logging function, requiring either the DASD-only logging function for a single-system MVS image, or a coupling facility. The DASD-only logging function is provided with OS/390. For a Parallel Sysplex system, CICS Transaction Server for OS/390 systems require a coupling facility, or coupling facility control code in a PR/SM LPAR.

  • If a customer has a BATCH requirement for VSAM RLS, as well as from the online CICS system, the latest level of the language environment (LE) run-time libraries will be required. Refer to the CICS Release Guide (GC33-1570) for a discussion on improved sharing of data sets between CICS and batch. For example, batch jobs can read and update, concurrently with CICS, non-recoverable VSAM data sets that are opened by CICS in RLS mode. Batch jobs can read (but not update) a recoverable data set in the RLS mode when it is concurrently accessed by CICS in RLS mode. With APAR OW25251 and OW25252, recoverable data sets defined with SHROPTIONS(2) can be concurrently accessed for input by batch programs using non-RLS mode (NSR, LSR) and by CICS for input or output in the RLS mode.

  • If using the cross-system coupling facility (XCF) of MVS/ESA SP (TM) Version 4 (and later releases) to take advantage of the improved MVS and PR/SM functions, operator intervention will be required to restart DBCTL after a CICS XRF region switch.

  • Customers implementing new Java applications, who need access to data held in DB2 databases, should use the latest level of DB2 with support for SQLJ:
    • SQLJ with DB2 Universal Database (R) Server for OS/390 (5645-DB2) Version 6.1
  • The CICS global ENQ/DEQ function uses MVS Global Resource Serialization (GRS) services. For guidance on use of and setting up of ENQ/DEQ, refer to the CICS Resource Definition Guide (SC33-1684).
Note: Normally, all communicating CMAS should be at the same level. However, during the migration of a CICS region below CICS/ESA Version 4 Release 1, such as CICS/MVS Version 2 Release 1.2, a CMAS at CICSPex SM Version 1 Release 3 level should be used for controlling this lower level CICS, because the CICSPlex SM element of CICS TS Release 3 does not support the following levels of CICS:
  • CICS/MVS Version 2.1.2 (5665-403)
  • CICS/ESA Version 3.3 (5685-083)
  • CICS/VSE Version 2.2 (5686-026)
  • CICS for OS/2 Version 2.01 (5648-036)
Vendor Products: Customers are advised to contact the suppliers of any third-party software used with CICS to ensure that critical packages run with CICS Transaction Server for OS/390.

To enable software vendors to adapt products to the changed programming interfaces in CICS, in 1996, IBM invited software vendors to participate in an Early Test Program, prior to the general availability of CICS Transaction Server for OS/390. A similar, new testing offering for this release was available from the beginning of April 1998. The Early Test Program is offered through the IBM Software Vendor System Support Center in Dallas, Texas. Call 800-627-8363 for more information.

Prior to this announcement, IBM disclosed information to many software vendors, for whom additional and early support has been provided.

Packaging: The base media for the CICS Transaction Server for OS/390 is shipped via MVS Custom Built Productivity Option (CBPDO) (5751-CS3) at planned availability, and via the OS/390 ServerPac (5751-CS9) delivery option, with the next ServerPac offering refresh within two months of product availability. The basic object material is shipped either on 9/6250 tape, 3480 tape cartridge or on 4-mm DAT cartridge.

CICS Transaction Server for OS/390 and OS/390, itself, are not available via MVS Custom Built Installation Process Offering (CBIPO) (5751-CS1). CBIPO support for two of the earlier versions of CICS, CICS/MVS Version 2 Release 1.2 and CICS/ESA Version 3 Release 3, was withdrawn concurrent with the availability of the first release of CICS Transaction Server for OS/390. CICS/ESA Version 4 Release 1 continues to be available via CBIPO.

Optional source material, excluding object code-only modules, is provided on the same media as the basic material except for 3480 compressed media. Optional source material is not available on 3480 compressed media. If an order includes both optional source material and 3480 compressed media, the optional source code will be shipped on regular 3480 media and the basic material will be shipped on the requested 3480 compressed media.

The base media are not available via stand-alone order, only via CBPDO. However, there are three optional items that are presented under supplemental base material by the configurator, when ordering the base using CBPDO:

  • CICSPlex SM VSE agent code (# 5331/5332/5723)

  • Optional Source (# 5831/5832/5724)

  • Supplementary Data Areas softcopy files (# 5841/5842/5725)
These optional items are shipped either on 9/6250 tape or on 3480 tape cartridge or 4-mm DAT cartridge. The Supplementary Data Areas softcopy files are separately chargeable.

If a customer only orders the base with the initial order, and then later chooses to order one of the optional components, an MES order must be used to place the order on the stand-alone product 5655-147 for the additional material.

In addition, softcopy versions (displayable manuals) of the documentation for the release, licensed and unlicensed, may be ordered as a priced feature as displayable softcopy BookManager (R)-built books, in a product kit. The product kit is available on CD-ROM, 3480 Tape Cartridge, 9/6250 Magnetic Tape and 4-mm DAT cartridge. Softcopy of the licensed publications for the release are available only on this product kit (# 8173/8174/8175/8176). A description of the product kit (GC33-1982) is provided with each copy.

The unlicensed softcopy documentation as displayable manuals are part of the no-charge CD-ROM feature number 7063 for the online books -- Collection Kit for Transaction Processing and Data products.

The code for the CICS Universal Clients Version 3.0, and CICS Transaction Gateway Version 3.0, is shipped on separate media (CD-ROMs) with the base material.

The CICS Transaction Gateway is not available separately. It is delivered as part of certain CICS server products, including the CICS Transaction Server for OS/390 Version 1 Release 3.

For use for application development, it is available in IBM VisualAge for Java Version 2.0.

The CICS Universal Clients Version 3.0 support the OS/2, Windows NT, Windows 98, AIX, and Solaris platforms. The CICS Universal Clients are available for download, at the latest level, from the Web via the CICS Internet home page:

The IBM TCP62 protocol mapper support provided in the clients for OS/2, Windows 98 and Windows NT, enables them to communicate with CICS Transaction Server for OS/390 Version 1.2 or later using a TCP/IP network. It allows partner LU6.2 applications to communicate without requiring any SNA configuration definitions on the client, and without any changes to the LU6.2 application on the client or server. This capability is included in the CICS Clients, or if SNA communication is required as well as TCP62, IBM Personal Communications Version 4.2 or later can be employed.

A copy of the CICS Gateway for Java (MVS) is available with the CICS Clients Version 2.0.4.

The latest level of the CICS Clients Version 2.0.4 is available on the Web at URL:

Customers wishing to use CICS Clients on Windows 3.1 or DOS platforms to communicate with CICS Transaction Server for OS/390 need to use the CICS Clients V2.0.4, with service level 7 applied.

The MQSeries-CICS Bridge, first available as a service update to MQSeries Version 1 Release 2, shows use of the CICS 3270 Bridge with CICS TS Release 2 for running a 3270-based CICS transaction without a terminal.



System Integrity

IBM will accept APARs where the installation of this licensed program causes an exposure to the system integrity of MVS.

MVS System Integrity Applies: Yes

Some CICS modules run authorized when they receive control as a result of the execution of a supervisor call or program call instruction. All other CICS modules and all application programs are intended to run unauthorized.

The above integrity statement does not apply with the High Performance Option (HPO) or if the CICS Type 6 SVC has been installed. Customers wishing to avoid any potential MVS system integrity problem should run without HPO, and should not install the Type 6 SVC provided by CICS on their systems.



Security, Auditability, and Control

The security and auditability features of the announced program include support for:

  • An external security management program
  • User exit authorization
  • Resource-level security
  • Terminal operator identification
  • Intersystem communication security
  • Journaling
  • Monitoring
  • Trace facilities
If sensitive data is sent over external communication facilities, user management may wish to consider the application of cryptography.

CICS XRF sessions using VTAM data encryption can be switched automatically, only if the latest levels of ACF/VTAM and NCP are installed. Otherwise, XRF sessions using VTAM data encryption can only be automatically restarted.

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



ORDERING INFORMATION



Current Licensees

Current licensees of CICS Transaction Server for OS/390 will be sent a program reorder form that may be returned directly to IBM Software Manufacturing Solutions (SMS). These reorder forms are scheduled to be mailed by April 9, 1999. Reorder forms returned to SMS will be processed within 10 work days of receipt. When Release 3 is available, Release 2 will no longer be available from SMS.



New Licensees

Orders for new licenses will be accepted now.

Shipment will begin on the planned availability date.

  • Orders that ship before the planned availability will receive CICS Transaction Server for OS/390 Release 2.0.

  • Orders that ship after the planned availability date will receive CICS Transaction Server for OS/390 Release 3.0.
New users of CICS Transaction Server for OS/390 should specify:
          Type        Model

5655 147

The ordering information for IBM CICS Transaction Server for OS/390 (5655-147), as previously announced (refer to Software Announcement 296-349 dated September 10, 1996), is unaffected by this announcement except as noted.

The base CICS TS product code can only be ordered under CBPDO 5751-CS3. It is not available via a stand alone 5655-147 product order.

Basic License: To order a basic license, specify the program number and feature number 9001 for asset registration. For a graduated one-time charge (OTC) or graduated monthly license charge, specify the feature number below that corresponds to the group that contains the designated machine.

Also, specify the feature number of the desired distribution medium, either for the base or for the language feature, if required. The base media must be ordered under CBPDO 5751-CS3, or via the OS/390 ServerPac 5751-CS9 (two months after availability).

Ordering a basic license also permits the CICS inter-region communication SVC (DFHIRP) from this version to be copied to a prior version of CICS, on a different machine in the same Parallel Sysplex, for communicating with this new version of CICS.

                 Basic               Basic
               Graduated           Graduated
            One-Time Charge  Monthly License Charge
Group        Feature Number      Feature Number

18 0178 0163 20 0179 0164 25 0180 0165 28 0181 0166 29 0182 0167 30 0183 0168 31 0184 0169 32 0185 0170 35 0186 0171 38 0187 0172 40 0188 0173 50 0189 0174 60 0190 0175 70 0191 0176 80 0192 0177

Multiple Operating System -- PR/SM (MOSP): For a graduated one-time charge or graduated monthly license charge, specify the feature number below that corresponds to the group that contains the designated machine.

               MOSP Basic          MOSP Basic
               Graduated           Graduated
            One-Time Charge  Monthly License Charge
Group        Feature Number      Feature Number

18 0253 0223 20 0254 0224 25 0255 0225 28 0256 0226 29 0257 0227 30 0258 0228 31 0259 0229 32 0260 0230 35 0261 0231 38 0262 0232 40 0263 0233 50 0264 0234 60 0265 0235 70 0266 0236 80 0267 0237

Note: The group can be determined by referring to either the Exhibit for IBM System/370 (TM) and System/390 Machines (Z125-3901) or the Exhibit for Non-IBM Machines (Z125-3902), that are associated with the IBM Customer Agreement (Z125-4575).

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

                                 ESL
                               One-Time
                                Charge
Program                        Feature
Number        Description       Number

5655-147 ESL 0633

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

Parallel Sysplex License Charge (PSLC) Basic License: To order a basic license, specify the program number and feature number 9001 for asset registration. Specify the PSLC Base feature. If applicable, specify the PSLC Level A and PSLC Level B features and quantity.

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

Also, specify the feature number of the desired distribution medium, either for the base or for the language feature, as required.

Ordering a basic license also permits the CICS inter-region communication SVC (DFHIRP) from this version to be copied to a prior version of CICS, on a different machine in the same Parallel Sysplex, for communicating with this new version of CICS.

                  PSLC PSLC Basic License
Machine           Feature MLC Feature
MSU Capacity      Number Description

1 0636 PSLC Base, 1 MSU 2 0637 PSLC Base, 2 MSUs 3 0114 PSLC Base, 3 MSUs

4 -- 45 0115 PSLC Level A, 1 MSU 0116 PSLC Level A, 42 MSUs

46 or more 0117 PSLC Level B, 1 MSU 0118 PSLC Level B, 10 MSUs 0119 PSLC Level B, 50 MSUs

NA 0120 PSLC N/C ID

Example 1: For a single machine with 11 MSUs, the PSLC features would be 0114 -- quantity 1 and 0115 -- quantity 8.

Example 2: For two machines in a Parallel Sysplex which have an aggregation of 60 MSUs, the PSLC features would be:

  • PSLC chargeable license #1: 0114 -- quantity 1, 0116 -- quantity 1, 0117 -- quantity 5, and 0118 -- quantity 1

  • PSLC no-charge license #2: 0120 -- quantity 1
Indexed Monthly License Charge (IMLC) Basic License: To order a basic license, specify the program number and feature number 9001 for asset registration. Specify the IMLC Base 80 MSU feature and the applicable additional IMLC MSU features and quantity corresponding to the MSU rating of the designated machine.

Also, specify the feature number of the desired distribution medium, either for the base or for the language feature, as required.

Ordering a basic license also permits the CICS inter-region communication SVC (DFHIRP) from this version to be copied to a prior version of CICS, on a different machine in the same Parallel Sysplex, for communicating with this new version of CICS.

IMLC                     IMLC Basic License
Feature                  MLC Feature
Number                   Description

0601 IMLC Base 80 MSUs 0602 IMLC 1 MSU 0603 IMLC 10 MSUs 0604 IMLC 50 MSUs

Measured Usage License Charge (MULC) Basic License: To order a basic license, specify the program number and feature number 9001 for asset registration. Specify the applicable MSUs Usage Band feature. If usage exceeds 14 MSUs, specify Usage Band 10 feature and the appropriate additional MSUs features and quantity. When multiple versions of a program are operating on the same machine, select the highest version MULC feature number. For lower versions, specify the MULC No Charge Identifier feature.

In a Parallel Sysplex, if there is more than one program copy or version, the charge for all copies and versions should be associated to the highest version copy by specifying the applicable MULC features represented by the sum of the MSUs used by the programs in the Parallel Sysplex. For all other program copies and versions, specify the MULC No-Charge Identifier feature.

Also, specify the feature number of the desired distribution medium, either for the base or for the language feature, as required.

Ordering a basic license also permits the CICS inter-region communication SVC (DFHIRP) from this version to be copied to a prior version of CICS, on a different machine in the same Parallel Sysplex, for communicating with this new version of CICS.

Program Number 5655-147

CICS Transaction Server for OS/390

MLC Measured Usage Usage Usage Feature Band Range (MSUs) Number

1 0 -- .250 0100 2 .251 -- .500 0101 3 .501 -- 1.000 0102 4 1.001 -- 1.500 0103 5 1.501 -- 2.500 0104 6 2.501 -- 3.500 0105 7 3.501 -- 5.500 0106 8 5.501 -- 7.500 0107 9 7.501 -- 10.500 0108 10 10.501 -- 14.000 0109

Above 14.000 MSU:

Each additional 1 MSU 0110 Each additional 10 MSUs 0111 Each additional 50 MSUs 0112

MULC N/C feature 0113

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

Version-to-Version Upgrade Credit: To upgrade from a prior program acquired for a one-time charge to a replacement program using a version-to-version upgrade credit, the customer must notify and identify to IBM the applicable prior program and replacement program participating in the upgrade credit.

Basic Machine-Readable Material: To order, select the feature number of the desired distribution medium:

The base media must be ordered under CBPDO 5751-CS3.

                    Feature             Distribution
Environment         Number              Medium

MVS 5801 9/6250 Magnetic Tape MVS 5802 3480 Tape Cartridge MVS 5720 4-mm DAT Cartridge

Basic Translated Machine-Readable Material: To order the additional message table with messages in Japanese (Kanji), select the feature number of the desired distribution medium below, instead of the base:

                    Feature             Distribution
Environment         Number              Medium

MVS 5811 9/6250 Magnetic Tape (NLV JPN + ENG) (CICS 9/6250 MT NLV JPN + ENG) MVS 5812 3480 Tape Cartridge (NLV JPN + ENG) (CICS 3480 TC NLV JPN + ENG) MVS 5721 4-mm DAT Cartridge (NLV JPN + ENG) (CICS 4-mm DAT C NLV JPN + ENG)

To order the additional message table with messages in Simplified Chinese, select the feature number of the desired distribution medium below, instead of the base:

                    Feature             Distribution
Environment         Number              Medium

MVS 5821 9/6250 Magnetic Tape (NLV CHI + ENG) (CICS 9/6250 MT NLV CHI + ENG) MVS 5822 3480 Tape Cartridge (NLV CHI + ENG) (CICS 3480 TC NLV CHI + ENG) MVS 5722 4-mm DAT Cartridge (NLV CHI + ENG) (CICS 4-mm DAT C NLV CHI + ENG)

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

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

                                                    Feature
Description                                         Number

Initial Shipments

Serial Number Only (suppresses shipment 3444 of media and documentation)

Ship Media Only (suppresses initial 3470 shipment of documentation)

Ship Documentation Only (suppresses 3471 initial shipment of media)

Update Shipments

Ship Media Updates Only (suppresses 3480 update shipment of documentation)

Ship Documentation Only (suppresses 3481 update shipment of media)

Suppress Updates (suppresses update 3482 shipment of media and documentation)

Expedite Shipments

Local IBM Office Expedite 3445 (for IBM use only)

Customer Expedite Process Charge 3446 ($30 charge for each product)

Expedite shipments will be processed to receive 72-hour delivery from the time IBM Software Manufacturing Solutions (SMS) receives the order. SMS will then ship the order via overnight air transportation.

Optional Machine-Readable Material: Unless ordered with the base material, an MES order must be used to place the order on the stand-alone product 5655-147 for the optional machine-readable material (not under CBPDO).

To order, select the feature number for the desired distribution medium:

CICSPlex SM VSE Agent Code

                    Feature             Distribution
Environment         Number              Medium

MVS 5331 9/6250 Magnetic Tape* MVS 5332 3480 Tape Cartridge* MVS 5723 4-mm DAT Cartridge*

Optional Source (excludes Object-Code Only modules)

MVS 5831 9/6250 Magnetic Tape* MVS 5832 3480 Tape Cartridge* MVS 5724 4-mm DAT Cartridge*

*     Contains Restricted Material of IBM

DSLO License: To order a DSLO license, specify the program number, feature number 9901 for asset registration, and the feature number below for a graduated one-time charge or graduated monthly license charge, that corresponds to the group containing the designated machine.

                                      DSLO
                  DSLO             Graduated
               Graduated            Monthly
            One-Time Charge      License Charge
Group        Feature Number      Feature Number

18 0208 0193 20 0209 0194 25 0210 0195 28 0211 0196 29 0212 0197 30 0213 0198 31 0214 0199 32 0215 0200 35 0216 0201 38 0217 0202 40 0218 0203 50 0219 0204 60 0220 0205 70 0221 0206 80 0222 0207

Multiple Operating System -- PR/SM (MOSP): For a graduated one-time charge or graduated monthly license charge, specify the following feature number below that corresponds to the group that contains the designated machine.

                                   MOSP DSLO
               MOSP DSLO           Graduated
               Graduated            Monthly
            One-Time Charge      License Charge
Group        Feature Number      Feature Number

18 0268 0238 20 0269 0239 25 0270 0240 28 0271 0241 29 0272 0242 30 0273 0243 31 0274 0244 32 0275 0245 35 0276 0246 38 0277 0247 40 0278 0248 50 0279 0249 60 0280 0250 70 0281 0251 80 0282 0252

Ordering a DSLO feature will result in IBM maintaining a record of this customer location as a DSLO user only. All material for the DSLO license will be provided through the basic license location. If a user selects DSLO, no other feature numbers are valid for this order and no program materials or updates will be shipped.

Unlicensed Documentation: A memo (GI10-2509), Program Directory (GI10-2506) and one copy of the following publications are supplied automatically with the basic machine-readable material:

                                                Order
Title                                           Number

CICS Transaction Server for OS/390 GC33-1570 Release Guide CICS Transaction Server for OS/390 GC33-1571 Migration Guide CICS Transaction Server for OS/390 GC33-1707 Licensed Program Specifications CICS Installation Guide GC33-1681 CICS System Definition Guide SC33-1682 CICS Customization Guide SC33-1683 CICS Resource Definition Guide SC33-1684 CICS Operations and Utilities Guide SC33-1685 CICS Supplied Transactions SC33-1686 CICS Application Programming Reference SC33-1688 CICS System Programming Reference SC33-1689 CICS External Interfaces Guide SC33-1944 CICS Internet Guide SC34-5445 CICS RACF Security Guide SC33-1701 CICSPlex SM Concepts and Planning GC33-0786 CICSPlex SM Administration GC34-5401 CICS Transaction Server for OS/390 GC33-1789 Planning for Installation CICS Universal Clients V3 (CD-ROM) SK2T-1790 CICS Transaction Gateway V3 (CD-ROM) SK2T-1791 LI CICS Universal Clients V3 GC34-5465 LI CICS Transaction Gateway V3 GC34-5466

Hardcopy Unlicensed Publications: The following unlicensed publications are optional. Printed copies of these will only be shipped with the basic machine-readable material for a fee of $250 if the feature number 8149 is specified.

Note that the optional unlicensed publications are available in the Online Books: Collection Kit for Transaction Processing and Data products. One copy of this CD-ROM is free. Refer to the following section on Displayable Softcopy Publications.

                                                        Feature
Order Title                                  Number     Number

CICS Family: Interproduct Communication SC33-0824 8149 CICS Family: Communicating SC33-1697 from CICS on System/390 CICS Application Programming SC33-1687 Guide CICS Distributed Transaction SC33-1691 Programming Guide CICS Front End Programming SC33-1692 Interface User's Guide CICS Problem Determination GC33-1693 Guide CICS Messages and Codes GC33-1694 CICS Intercommunication Guide SC33-1695 CICS Recovery and Restart Guide SC33-1698 CICS Performance Guide SC33-1699 CICS Business Transaction SC34-5268 Services CICS C++ OO Class Libraries SC34-5455 CICS DB2 Guide SC33-1939 CICS IMS Database Control Guide SC33-1700 CICS Shared Data Tables Guide SC33-1702 Order Title Number

CICS Master Index SC33-1704 CICS User's Handbook SX33-6104 CICS Trace Entries Handbook SC34-5446 CICS Transaction Affinities SC33-1777 Utility Guide CICS Distributed Data SC33-0695 Management User's Guide CICS Application Migration Aid SC33-0768 Guide IBM REXX Development System SH21-0482 for CICS/ESA and REXX Runtime Facility for CICS/ESA Guide and Reference CICSPlex SM Operations SC33-0789 Views Reference CICSPlex SM View Commands SX33-6099 Reference Summary CICSPlex SM Application SC34-5457 Programming Guide CICSPlex SM Application SC34-5458 Programming Reference CICSPlex SM Resource SC33-1220 Tables Reference CICSPlex SM User Interface SC33-0788 Guide CICSPlex SM Messages GC33-0790 & Codes CICSPlex SM Problem GC33-0791 Determination CICSPlex SM Managing SC33-1807 Workloads CICSPlex SM Managing SC33-1808 Resource Usage CICSPlex SM Managing SC33-1809 Business Applications CICSPlex SM Monitor SC34-5402 Views Reference CICSPlex SM Master Index SC33-1812 CICS Clients Administration SC33-1792

Additional copies of unlicensed publications, will be available individually for a fee after availability. These copies may be ordered from your IBM representative, through the System Library Subscription Service (SLSS) or by direct order.

The new CICS Trace Entries Handbook (SC34-5446) contains information formerly in the CICS User's Handbook (SX33-6104).

The CICSPlex SM Setup (GC33-0784), is retitled CICSPlex SM Administration (GC34-5401) and the set up information is now in the CICS Installation Guide (GC33-1681).

The Internet and External Interfaces Guide (SC33-1944), new with last release, superseded the following books:

  • CICS External CICS Interface (SC33-1703)
  • CICS ONC RPC Guide (SC33-1778)
  • CICS Server Support for CICS Clients (SC33-1779)
  • CICS Web Interface Guide (SC33-1825)
and is now split into two books, CICS External Interfaces Guide (SC33-1944) and CICS Internet Guide (SC34-5445).

The following books may only be ordered, by form number, from your IBM representative, through the SLSS or by direct order.

CICS Universal Clients and CICS Transaction Gateway: The following publications apply to the CICS Universal Clients Version 3.0:

                                                          Order
Book                                                      Number

CICS Universal Clients Version 3 for OS/2: SC34-5450 Administration CICS Universal Clients Version 3 for SC34-5449 Windows: Administration CICS Universal Clients Version 3 for AIX: SC34-5348 Administration CICS Universal Clients Version 3 for Solaris: SC34-5451 Administration CICS Universal Clients Version 3: Messages (softcopy only) CICS Family: Client/Server Programming SC33-1435 CICS Family: OO Programming in C++ for SC33-1923 CICS Client CICS Family: OO Programming in BASIC for SC33-1924 CICS Clients

Hardcopy of these books (except CICS Universal Clients Version 3: Messages) will be available for purchase. To order, contact your IBM representative or your dealer.

The following publications apply to the CICS Transaction Gateway Version 3.0:

                                                          Order
Book                                                      Number

CICS Transaction Gateway Version 3: SC34-5448 Administration CICS Universal Clients Version 3 for OS/2: SC34-5450 Administration CICS Universal Clients Version 3 for SC34-5449 Windows: Administration CICS Universal Clients Version 3 for AIX: SC34-5348 Administration CICS Universal Clients Version 3 for Solaris: SC34-5451 Administration CICS Universal Clients Version 3: Messages (softcopy only) CICS Family: Client/Server Programming SC33-1435 CICS Family: OO Programming in C++ for SC33-1923 CICS Clients CICS Family: OO Programming in BASIC for SC33-1924 CICS Clients

Hardcopy of these books (except CICS Universal Clients Version 3: Messages) are available for purchase. To order, contact your IBM representative or your dealer.

Displayable Softcopy Publications: Publications for this product are offered in displayable softcopy form in the IBM Online Book Library Offering (5636-PUB), on the Collection Kit for Transaction Processing and Data products (SK2T-0730). All unlicensed manuals are included except for:

  • CICS Master Index (SC33-1704)

  • CICS Transaction Server for OS/390 Licensed Program Specifications (GC33-1707)

  • CICSPlex SM View Commands Reference Summary (SX33-6099)

  • CICSPlex SM Master Index (SC33-1812)
The CICS Glossary (GC33-1705) is provided in displayable softcopy only.

CICS Clients Messages (SC33-1793) is provided in displayable softcopy only.

The unlicensed displayable manuals are part of the no-charge CD-ROM feature number 7063 for the Online Books: Collection Kit for Transaction Processing and Data products.

Licensees of CICS TS can order, for a fee, a copy of the product kit which contains softcopy versions (displayable manuals) of both licensed publications and unlicensed publications, for the release. The product kit is available on CD-ROM, 3480 Tape Cartridge, 9/6250 Magnetic Tape and 4-mm DAT cartridge. A description of the Product Kit (GC33-1982) is provided with each copy. Softcopy of the licensed publications for the release are available only on this product kit.

                                    Kit
                                    Copies
                        Order       Feature
Title                   Number      Number   Price

Product Kit for CICS TS CD-ROM LK2T-1789 8173* $40 9/6250 Magnetic Tape 8174* 40 3480 Tape Cartridge 8175* 40 4-mm DAT Cartridge 8176* 40

*     Contains Restricted Material of IBM

These displayable manuals can be used with the BookManager READ licensed programs in any of the supported environments. Terms and conditions for use of the machine-readable files are shipped with the files.

Copies of the Collection Kit for Transaction Processing and Data products can be ordered in the following ways:

  • By specifying feature number 7063 on your order to get your first copy, free of charge, shipped with your basic machine-readable material. Subsequent updates will be shipped free of charge.

  • By specifying feature number 8148 on your order to get additional copies for a fee, shipped with your basic machine-readable material.

  • By ordering feature numbers 2023 with 5023 of product number 5636-PUB, and paying an annual subscription fee. This fee will cover any updates during the year.

  • Through SLSS, by paying an annual subscription charge and ordering SK2T-0730. This will ensure that you automatically receive any updates throughout the year.

  • Through PUBORDER, by paying a one-time fee and ordering SK2T-0730. You will have to order any subsequent editions of the kit explicitly, paying a further fee.
Online books supplied as part of the collection kit can be used with both IBM Library Reader (TM), which is included on the CD-ROM, and with the BookManager READ licensed programs in any of the supported environments. Terms and conditions for the use of the machine-readable files are shipped with the files.

For more information about the collection kit for Transaction Processing and Data products, refer to Software Announcements 292-717 dated December 15, 1992, and 294-431, dated July 12, 1994.

                              Single    Additional
                              Copy      Copies
                  Order       Feature   Feature
Title             Number      Number    Number     Price

Collection Kit SK2T-0730 7063 8148 $100 Kit for Transaction Processing and Data Products CD-ROM

CICS Universal Clients and CICS Transaction Gateway: All the books applicable to CICS Universal Clients and to CICS Transaction Gateway will be shipped as part of the product in HTML format (filetype .HTM) for viewing using a Web browser; and in Acrobat format (filetype .PDF), for viewing and printing using an Adobe Acrobat reader. The Adobe Acrobat reader is shipped with the product.

In addition, programming reference information is supplied with the product in HTML format.

Softcopy publications in IPF format (filetype .INF) will not be provided.

Licensed Documentation: The following licensed material will be available from IBM at product availability. To order, contact your IBM representative.

The first copy is available at no charge to licensees of basic material by specifying the 7XXX feature number. Use the 8XXX feature number to order additional copies for a fee.

                              Single    Additional
                              Copy      Copies
                  Order       Feature   Feature
Title             Number      Number    Number     Price

Diagnosis LY33-6088 7061 8145 $37 Reference Data Areas LY33-6089 7062 8146 25

In addition, the following features are only available for the fee indicated:

                                   Single
                                   Copy
                    Order          Feature
Title               Number         Number         Price

Supplementary LY33-6090 8147 $104 Data Areas

To order the Supplementary Data Areas (LY33-6090) (printed copy) with softcopy of these data areas, specify the feature number of the desired distribution medium. This is separately chargeable.

                              Additional
                              Copies
                              Feature
Title                         Number         Price

9/6250 Magnetic Tape 5841* $1,040 3480 Tape Cartridge 5842* 1,040 4-mm DAT Cartridge 5725* 1,040

*     Contains Restricted Material of IBM

Source Listings: There are no source listings provided for CICS Transaction Server for OS/390. If you require access to such listings, use the View Program Listings (VPL) system. For further information on how to use the VPL system, refer to the VPL Users Guide dated January 1993.

Subsequent updates (technical newsletters or revisions between releases) to the publications shipped with the product will be distributed to the user of record for as long as a license for this software remains in effect. A separate publication order or subscription is not needed.



TERMS AND CONDITIONS

The terms for IBM CICS Transaction Server for OS/390 (5655-147), as previously announced (refer to Software Announcement 296-349 dated September 10, 1996), licensed under the IBM Customer Agreement are unaffected by this announcement except as noted below:

For CICS Universal Clients Version 3.0, the following conditions apply:

The CICS Universal Clients Version 3.0 may be copied free of charge to enable communications with any supported IBM CICS server, Transaction Server, CICS Transaction Server, or TXSeries server, with the exception of the servers listed below. Provided the CICS Universal Clients are used only with servers which are not on the exceptions list, customers are authorized to make copies of the CICS Universal Clients as program features.

The exceptions are:

  • CICS/ESA Version 4.1

  • CICS/VSE Version 2.3
If they are used to enable communication with either of these servers, a license is required for every copy made of the CICS Universal Clients. (Note: these licenses are not available at the present time.)

When the CICS Universal Clients Version 3.0 are not directly connected to IBM CICS Transaction Server for OS/390 the appropriate number of registered users for the server, to which the CICS Universal Clients are connected, are required.

The CICS Clients V2.0.4, with service level 7 applied, for OS/2, Windows 3.1, Windows 95, Windows NT and DOS may be copied without charge for use with the CICS Transaction Server for OS/390, but there are restrictions on copying for use with other CICS servers.

For CICS Transaction Gateway Version 3.0 (5648-B43), the following conditions apply:

The CICS Transaction Gateway Version 3.0 may be copied to any number of workstations, without additional charge, for use with the CICS Transaction Server for OS/390. It is not licensed for use with any other CICS server.

Customers wishing to develop applications using the CICS Transaction Gateway should license IBM VisualAge for Java Version 2.0.

For further information on IBM VisualAge for Java Version 2.0, refer to Software Announcement 298-277 dated August 11, 1998.

For further information on IBM VisualAge for Java, Enterprise Edition for OS/390 Version 2.0, refer to Software Announcement 298-319 dated September 8, 1998.

Program Currency: CICS Universal Clients and CICS Transaction Gateway are available until January 31, 2001.

These program services apply to service on both the CICS Transaction Gateway Version 3.0 and the CICS Universal Clients Version 3.0, as delivered by any means.

To obtain the latest service level, contact the Service Support Center for your country. Alternatively, information on service support status and service levels can be obtained and the latest service levels can be downloaded from the Internet at:

Support Line: S/390



CHARGES

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

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

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

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

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

The charges for IBM CICS Transaction Server for OS/390 (5655-147) are unaffected by this announcement.

For additional product information, refer to Software Announcements 296-349 dated September 10, 1996, 296-427 dated November 5, 1996 and 297-353 dated September 9, 1997.



CALL NOW TO ORDER

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

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

 Phone:     800-IBM-CALL
 Fax:       800-2IBM-FAX
 Internet:  ibm_direct@vnet.ibm.com
 Mail:      IBM North America Sales Centers
            Dept. LE010
            P.O. Box 2690
            Atlanta, GA  30301-2690
 Reference: LE010

To identify your local IBM Business Partner or IBM representative, call 800-IBM-4YOU.

Note: Shipments will begin after the planned availability date.

Trademarks

      TXSeries, MVS, IMS, Multiprise, ES/3090, Enterprise Systems
      Architecture/370, ESA/390, RS/6000, PR/SM, PR/SM, MVS/ESA,
      DFSMS, eNetwork, SupportPac, SP, System/370, and Library Reader
      are trademarks of International Business Machines Corporation
      in the United States or other countries or both.
      OS/390, CICS, CICS/ESA, CICSPlex, DB2, AIX, OS/2, RACF,
      CICS/VSE, CICS/400, VisualAge, MQSeries, Open Blueprint, S/390,
      ES/9000, System/390, Parallel Sysplex, Sysplex Timer, VTAM,
      IMS/ESA, NetView, Advanced Peer-to-Peer Networking, APPN,
      ACF/VTAM, RETAIN, AS/400, CICS/MVS, DB2 Universal Database, and
      BookManager are registered trademarks of International Business
      Machines Corporation in the United States or other countries or
      both.
      Windows and Microsoft are trademarks of Microsoft Corporation.
      Windows NT is a registered trademark of Microsoft Corporation.
      Java and HotJava are trademarks of Sun Microsystems, Inc.
      UNIX is a registered trademark in the United States and other
      countries exclusively through X/Open Company Limited.
      Domino and Domino.Connect are trademarks of Lotus Development
      Corporation.
      Lotus Notes and Lotus are registered trademarks of Lotus
      Development Corporation.
      NetWare is a trademark of Novell, Incorporated.

Other company, product, and service names may be trademarks or service marks of others.