© 2015 IBM Corporation

CICS Transaction Server V5.3

Introducing CICS Transaction Server V5.3 Technical Overview

Steve FoleyIBM CICS Software Architect Teamsteve_foley@uk.ibm.com

IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion.

Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision.

The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.

Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user’s job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.

Please Note

2

• CICS TS V5.1 & V5.2 Review

• CICS TS V5.3 Overview• Service Agility

• Operational Efficiency

• Cloud with DevOps

• Additional requirements satisfied

• Explorer

• Summary

Agenda

3

*

Release Availability Service

CICS TS V5.3 11th December 2015

CICS TS V5.2 13th June 2014

CICS TS V5.1 14th December 2012

CICS TS V4.2 Withdrawn from marketing 30th September 2018

CICS TS V4.1 Withdrawn from marketing 30th September 2017

CICS TS V3.2 Withdrawn from marketing 31st December 2015

CICS TS V3.1 Withdrawn from marketing 31st December 2015

CICS TS – Service Planning

CICS TS V5 Vision

Enhanced support for Java and the

WebSphere Liberty profile

Service Agility

Performance optimizations, enhanced

metrics and addition security

Operational Efficiency

New cloud and DevOps support to automate CICS

deployments

Cloud Enablement

300+ requirements

satisfied in V5!

5

• WebSphere Liberty Profile Support• A production-ready web container

• Local access to CICS applications and data

• Deploy lightweight Java servlets and JSPs • More features supported in V5.2

• Mobile Feature Pack integration• JSON support for mobile applications

Service Agility in V5.1 and V5.2

6

• Greater capacity• More threadsafe, more 64-bit exploitation, increased limits

• Managed operations• Resource threshold policies – message, abend or event

• CPU time, storage usage, data access• Deeper insight

• Audit trail of system changes, additional metrics collected

• Web Services security• Kerberos support• Security Assertion Mark-up Language support

Operational Efficiency in V5.1 and V5.2

7

• Application and platform support• Manage disparate resources as a single, versioned

application entity• Rapidly move through the application lifecycle • Automate dependency management• Managed with policies

• CICS regions grouped as platforms for rapid application deployments• Decoupling applications from the region topology

Cloud in V5.1 and V5.2

8

Service Agility

Enhanced support for Java and the WebSphere Liberty profile

Cloud with DevOps

Operational Efficiency

Performance optimizations, enhanced metrics and additional security

New cloud and DevOps support to automate CICS deployments

• Additional Liberty features• Enhanced interoperability• Simplified management• Enhanced Java SE support

• Web service optimizations• Performance improvements• Enhanced metrics• Additional security options

• Automated builds• Scripted deployments• UrbanCode Deploy support• Enhanced cloud enablement

Planned availability: December 11, 2015

IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion.

IBM CICS Transaction Server V5.3

9

• Service agility focuses on enhanced support for Java and the WebSphere Liberty profile and includes: • Additional WebSphere Liberty profile features

• Enhanced interoperability

• Simplified management

• Enhanced Java SE support

Service Agility

10

• Support JEE6 Web profile

• Java EE Connector Architecture (JCA)

• Java Message Service 1.1 - with WLP embedded messaging engine

• Database Session Persistence (JDBC Type 4 driver only)

• MongoDB

• Open Service Gateway Initiative (OSGi) Console

• Java Management Extensions (JMX)

Support additional Liberty profile features

11

• IBM makes the following statements of general direction:

• IBM intends to deliver support for Java applications that exploit Java EE 7 Full Platform features when running in the WebSphere Liberty profile that is integrated with IBM CICS Transaction Server for z/OS (CICS TS)

• IBM intends to deliver additional Java EE 7 components and technologies for the CICS TS hosted WebSphere Liberty profile through continuous delivery of new features in the coming months

• These additional components and technologies are intended to include support for Java EE 7 Web Profile features and support for JMS 2.0 with IBM MQ for z/OS

Statements of Direction

12

• Java EE Connector Architecture (JCA) connects enterprise information systems such as CICS or SAP to JEE application servers

• CICS Transaction Gateway (CTG) provides a set of JCA resource adapters to support the use of the JCA for connecting to CICS TS

• CICS now provides its own JCA local ECI feature• Liberty’s JCA feature means to connect into CICS you need to go out

of CICS using JCA, then back in via CTG• CICS provides optimized JCA adapter supporting CTG’s JCA ECI interfaces• Allows you to port existing JCA applications that use the JCA ECI interfaces

from other JEE applications servers into the a CICS Liberty JVM server• You can develop new JEE applications that can link to existing CICS

COBOL programs without being tied to the proprietary JCICS Java API

Enhanced interoperability using JCA

13

5.3

Pre-V5.3

CICS region

LibertyVSAM

COBOLProgram

DB2

JEE app server

WebApp

EJB

JCAWebClient

CICS Transaction

Gateway

14

At V5.3

CICS region

LibertyVSAM

JVM Server

Liberty

WebApp

COBOLProgram

JCICS

DB2

JDBCWebClient HTTP

EJBJCA

5.3

15

• Liberty z/OS Connect feature enables connectivity between e.g. mobile devices and CICS programs• Enables CICS programs to be called with a JavaScript Object Notation

(JSON) interface• Support the conversion between JSON and high-level language

data structures

Liberty z/OS Connect feature

16

• Also available via APAR for V5.1 and V5.2• At V5.3 choice of native or Java parser available

Easier management of zFS files from JVM server

• New options for controlling the location for JVM stdout, stderr, trace and dump output• Stderr/stdout/dfhjvmtrc can be redirected to MVS DD instead of

zFS files• Timestamps in JVM server output logs can be localized

• New TZ JVM profile option to specify your local time zone• Timestamps still in UTC (Coordinated Universal Time) if not

set• Old log files can be deleted

• New LOG_FILES_MAX JVM profile option to specify how many iterations of each log file to keep• All logs kept if not specified or set to zero

17

• Java 8 support• Will exploit new facilities of the z13 • Can run Java 8, 7.1 and 7 in different JVM servers in the same CICS

• Implemented PHASEIN support for bundles• Enables registration of a new OSGi bundle replacing any currently

registered version• New requests will use the new version• Existing requests will use the old version until complete

• IBM MQ Java Message Service (JMS) classes can be used to access MQ, as an alternative to the proprietary MQ classes for Java

• Only Java programs that run in an OSGi JVM server • No support in Liberty (yet)

Enhanced Java SE support

18

• Operational efficiency includes performance optimizations, enhanced metrics: • Web service optimizations

• Performance improvements

• Enhanced metrics

Operational efficiency

19

HTTPRequests

Long running task on its own TCB that listens for work.

Process next piece of work

CSOLSocket listener

Application processing run under the context established by CWXN

CWXNWeb attach task

Determines the contextof the user transaction

that is started.This is known as the

Web attach task.

User Transactioni.e. CWBA, CPIH

Web service optimizations

• Pre V5.3

20

21

HTTPRequests

Long running task on its own TCB. It must not be blocked by an individual request.

If CICS SSL OR Web analyser program ORStatic response ORNot enough data => CWXN

Gets tran ID and user ID from URIMAP and/or AT-TLS

Start the application transaction with the specific tranid and userid

Process next piece of work

CSOL

Sync receive the body data and pass to the next step in application

Application processing run as before

CWXN

Run whenunable toestablishcontextin SOLS

User Transactioni.e. CWBA, CPIH

13% reduction in CPUfor web-owning region

2.4GB/hr reduction inSMF 110 record volumes

Eliminate CWXN where possible

• In the V5.3 open beta

SSL enhancements

• Introduced support for Application-Transparent Transport Layer Security (AT-TLS) • Decryption/encryption is handled by the TCPIP address

space rather than in CICS

• No need for CWXN as request comes into CSOL ready-decrypted

• CICS SSL still requires CWXN• Multiple TCB switches eliminated

22

• HTTP Performance tuning• Protects CICS from unconstrained resource demand via HTTP(S) requests, allowing

it to recover when overloaded• If CICS region is becoming overloaded

• Initially CICS temporarily stops listening for new HTTP(S) connection requests

• Allows feedback to TCP/IP port sharing and Sysplex distributor• If CICS region continues to become overloaded

• Closes existing HTTP(S) persistent connections and marks all new HTTP(S) connections as non-persistent

• Reminder: option of using new CICS native JSON parser running in z/OS Connect

• Provides faster response time than Java parser but not zAAP offload eligible

• Can have define a mixture of pipelines to give different qualities of service for different apps

More web optimizations

23

• Improvements in trace• Use of faster hardware instructions

• Some level 1 trace moved to level 2

• Improvements in monitoring• Excluding fields is now less efficient than collecting all of them

• Reduced lock contention

• Improvements for MRO connections with high session counts• Algorithm efficiency improved

• General performance improvements• Cache alignment of control blocks

• Use of data pre-fetch

• Tuning of other internal algorithms

Core performance improvements

24

How have we done?

INTTR ON

MNPER ONCPU per Transaction comparison

11.6 % reduction in TOR

25

More SPI commands made threadsafeINQUIRE commands DISCARD commands SET commandsINQUIRE ENQMODEL DISCARD ENQMODEL SET ENQMODELINQUIRE JOURNALMODEL DISCARD JOURNALMODEL SET JOURNALNAMEINQUIRE JOURNALNAME DISCARD JOURNALNAME SET TCLASSINQUIRE RRMS DISCARD TCPIPSERVICE SET TCPIPINQUIRE STORAGE DISCARD TDQUEUE SET TCPIPSERVICEINQUIRE STREAMNAME DISCARD TRANCLASS SET TDQUEUEINQUIRE SUBPOOL DISCARD TSMODEL SET TRANCLASSINQUIRE TASK LIST PERFORM SECURITY REBUILD SET TSQNAMEINQUIRE TCLASS PERFORM SSL REBUILD SET TSQUEUEINQUIRE TDQUEUE WRITE OPERATOR SET UOWINQUIRE TCPIP SET WEBINQUIRE TCPIPSERVICE

INQUIRE TRANCLASS

INQUIRE TSMODEL

INQUIRE TSPOOL

INQUIRE TSQNAME

INQUIRE TSQUEUE

INQUIRE UOW

INQUIRE UOWENQ

INQUIRE WEB

26

• Transaction tracking extended to the CICS-MQ for z/OS bridge

• New metrics added to CICS global statistics• Transaction CPU time measurements are captured without the need

for CICS monitoring to be active

Enhance metrics

User transactions ended . . . . . . . : 905747System transactions ended . . . . . . : 31Time last user transaction attached . : 09/11/2015 22:18:50.5082 ...Time last user transaction ended. . . : 09/11/2015 22:18:50.5087 ...Average user transaction resp time. . : 00:00:00.001793Peak user transaction resp time . . . : 00:00:00.063212Peak user transaction resp time at. . : 09/11/2015 22:18:09.4275Total transaction CPU time. . . . . . : 00:00:25.256705Total transaction CPU time on CP. . . : 00:00:25.256705Total transaction CPU offload on CP . : 00:00:00.000000

27

• New resource threshold policies• All CICS commands

• IMS requests

• MQ requests

• Name Counter Server requests

• Shared Temporary Storage requests

• Support for TRANSACTION entry points• Allows a policy to be associated with a transaction ID

Cloud enablement improvements

28

• Recovery of the Application Status after a region start/restart• The available or unavailable state is restored

• New private resource, PACKAGESET, for DB2 collections• Enables you to specify different DB2 collections across different

environments by specifying in an application binding e.g.

• Test, QA, Production• CICS will issue the EXEC SQL SET CURRENT PACKAGESET

command on behalf of the application

• No need to change application as go through product lifecycle

More cloud enablement improvements

29

• The process…

Automated builds

30

• CICS Build Toolkit provides a command-line interface for automating the building of CICS projects

• CICS cloud applications and bundles, and OSGi Java components, automatically built from source code

• Variable substitution to facilitate the deployment of the same application to different environments (e.g. development, quality assurance, and production)

• Supported on z/OS, Linux and Microsoft Windows

• Can be used in continuous integration environment - a build script can automatically run when developers make updates to their applications to• Check out the latest application version from source control along with its

dependencies

• Call the CICS Build Toolkit to build the projects that form the application

• Copy the built projects to a suitable location, such as an artifact repository or a staging area on zFS

Automated builds

31

• DFHDPLOY is a batch utility to support automated provisioning of• CICS bundles • OSGi bundles within CICS bundles• CICS applications

• Can be used to • Deploy CICS bundles and CICS applications• Set the desired state

• e.g. ‘enabled’ or ‘available’ • Undeploy and remove bundles and applications

Scripted deployments

32

• Example JCL to replace a an existing bundle WEBSITE//DFHDPLOY JOB CLASS=A,MSGCLASS=A,NOTIFY=&SYSUID//* //DFHDPLOY EXEC PGM=DFHDPLOY //* //STEPLIB DD DISP=SHR,DSN=CICSTS53.CICS.SDFHLOAD// DD DISP=SHR,DSN=CICSTS53.CPSM.SEYUAUTH//SYSTSPRT DD SYSOUT=*//SYSIN DD *SET CICSPLEX(MYPLEX);*UNDEPLOY BUNDLE(WEBSITE) CSDGROUP(BANKING) SCOPE(SYS1)STATE(DISCARDED);*DEPLOY BUNDLE(WEBSITE) BUNDLEDIR(/var/cicsts/bundles/Website_1.0.0/) CSDGROUP(BANKING) SCOPE(SYS1) STATE(ENABLED) TIMEOUT(60);/*

DFHDPLOY Example

33

IBM UrbanCode

• IBM UrbanCode Deploy orchestrates and automates deployment of applications, middleware configurations, and database changes

• CICS TS plug-in supports the deployment of CICS applications as part of these orchestrations by providing functions for:• Installing and removing resources • NEWCOPY and PHASEIN for programs• Issue PEFORM PIPELINE SCAN

34

• Channels and containers

• DELETE CHANNEL command added

• Query the number of CONTAINERs in a CHANNEL

• Java

• Allow use of an existing document in a Java program

• ASSIGN command

• Return terminal input length

• Return Abend offset on ASRA, ASRB and ASRD abends

• Initialization

• Police hardware levels (z9 or higher)

• Detect CICS module or table level mismatch

• STGPROT SIT option default now set to YES

• DFHRPL & Dynamic libraries can now reside in an EAS Space of an EAV volume

• Identify CICS System Definition file maintenance level

Additional requirements satisfiedOver 80 RFE requirements

satisfied in V5.3

(so far)

35

• Enhanced storm drain avoidance

• VSAM RLS

• IMS DBCTL

• WebSphere MQ

• Performance data

• Number of GET COUNTER or GET DCOUNTER for a Name Counter Server

• Number of GET and PUT queues to a Shared TS Server

• Statistics

• Peak queue depth for Transient Data queues

• Dump

• Provide a summary of all tasks or a single task in a dump

• Trace

• Provide a summary of tasks in the trace table

More requirements satisfied

36

• Set one connection in each connection category as the default e.g.

• CMCI

• z/OS (ftp or z/OSMF)

• Automatically connect to default connection(s) at Explorer startup

CICS Explorer Default Connections

37

• Improved customization options for table views to make it easier to see the data you are interested in

• Can be saved for future use

• Extended platform support:• Available for the OS X Yosemite (10.10) operating system

• Provides the ability to connect to a CICS TS for z/VSE® 2.1 system to browse and process supported resources

CICS Explorer Enhancements

38

CICS TS V5 Vision

Do it quicker

Service Agility

Do it faster

Operational Efficiency

Do it continuously

Cloud Enablement with DevOps

39