Book description
This IBM® Redbooks® publication describes the new channels and containers support in IBM Customer Information Control System (CICS®) Transaction Server V5.2. The book begins with an overview of the techniques used to pass data between applications running in CICS.
This book describes the constraints that these data techniques might be subject to, and how a channels and containers solution can provide solid advantages alongside these techniques. These capabilities enable CICS to fully comply with emerging technology requirements in terms of sizing and flexibility.
The book then goes on to describe application design, and looks at implementing channels and containers from an application programmer point of view. It provides examples to show how to evolve channels and containers from communication areas (COMMAREAs).
Next, the book explains the channels and containers application programming interface (API). It also describes how this API can be used in both traditional CICS applications and a Java CICS (JCICS) applications.
The business transaction services (BTS) API is considered as a similar yet recoverable alternative to channels and containers. Some authorized program analysis reports (APARs) are introduced, which enable more flexible web services features by using channels and containers.
The book also presents information from a systems management point of view, describing the systems management and configuration tasks and techniques that you must consider when implementing a channels and containers solution.
The book chooses a sample application in the CICS catalog manager example, and describes how you can port an existing CICS application to use channels and containers rather than using COMMAREAs.
Table of contents
- Front cover
- Notices
- IBM Redbooks promotions
- Preface
- Summary of changes
- Chapter 1. Introduction to channels and containers
-
Chapter 2. Application design and implementation
- 2.1 Container usage as a replacement to COMMAREAs
- 2.2 Flexible way to pass multiple pieces of data
- 2.3 Overloaded COMMAREAs
- 2.4 STARTBROWSE application programming interface
- 2.5 Channels and containers in called subroutines
- 2.6 Data conversion and code page conversion
- 2.7 Storage
- 2.8 Dynamic routing application considerations
- 2.9 Best practices
-
Chapter 3. Programming
- 3.1 EXEC CICS application programming interface
-
3.2 CICS Java
- 3.2.1 Creating channels and containers in JCICS
- 3.2.2 Placing data in a container
- 3.2.3 Passing a channel to another program or task
- 3.2.4 Receiving the current channel
- 3.2.5 Getting data from a container
- 3.2.6 Browsing the current channel
- 3.2.7 Browsing a name channel
- 3.2.8 Deleting a container
- 3.2.9 Code page considerations
- 3.3 Business transaction services
- 3.4 Web services
- 3.5 CICS-WebSphere MQ bridge
- Chapter 4. Systems management and configuration
-
Chapter 5. Sample application
-
5.1 Implementation scenario
- 5.1.1 The CICS catalog manager example application
- 5.1.2 The base application
- 5.1.3 Porting steps: CICS back end
- 5.1.4 Stage 1: Porting to channels and containers
- 5.1.5 Installing and setting up the base application
- 5.1.6 Defining the 3270 interface
- 5.1.7 Running the application
- 5.1.8 Stage2: Catalog item images support
-
5.2 Running the stage 2 code
- 5.2.1 Installing and setting up the Stage 2 application
- 5.2.2 JCICS image handler program installation
- 5.2.3 Define a JVMSERVER definition in CICS TS
- 5.2.4 Transfer the CICS Bundle to z/OS UNIX System Services
- 5.2.5 The Liberty profile servlet access to the catalog manager
- 5.2.6 Running the catalog servlet
- 5.2.7 Deploying the catalog servlet
- 5.2.8 Workspace setup for developing OSGi servlets and JSP
- 5.2.9 Create the catalog OSGi Project
- 5.2.10 Create an EBA project to the OSGi Bundle Project
- 5.2.11 Create a CICS BUNDLE to the EBA project
- 5.2.12 Add the com.ibm.cics.server package to your OSGi project
- 5.2.13 Create the dynamic web project
- 5.2.14 Define a CICS JVMSERVER with Liberty profile
- 5.2.15 Export the CICS Bundle to z/OS
- 5.2.16 Define a CICS Bundle definition for the catalog servlet
-
5.1 Implementation scenario
- Chapter 6. Frequently asked questions
- Appendix A. CICS channels and containers Liberty servlet example
- Appendix B. Additional material
- Related publications
- Back cover
-
IBM System x Reference Architecture for Hadoop: IBM InfoSphere BigInsights Reference Architecture
- Introduction
- Business problem and business value
- Reference architecture use
- Requirements
- InfoSphere BigInsights predefined configuration
- InfoSphere BigInsights HBase predefined configuration
- Deployment considerations
- Customizing the predefined configurations
- Predefined configuration bill of materials
- References
- The team who wrote this paper
- Now you can become a published author, too!
- Stay connected to IBM Redbooks
- Notices
Product information
- Title: Using IBM CICS Transaction Server Channels and Containers
- Author(s):
- Release date: March 2015
- Publisher(s): IBM Redbooks
- ISBN: 9780738440507
You might also like
book
CICS Transaction Server from Start to Finish
In this IBM® Redbooks® publication, we discuss CICS®, which stands for Customer Information Control System. It …
book
Implementing CICS Web Services
The Web services support in CICS Transaction Server Version 3.1 enables your CICS programs to be …
book
Securing Access to CICS Within an SOA
With the emergence of service-oriented architecture (SOA), the options for accessing the existing IBM Customer Information …
book
Liberty in IBM CICS: Deploying and Managing Java EE Applications
Abstract This IBM® Redbooks® publication is intended for IBM CICS® system programmers and IBM Z architects. …