impact2014 session #1317 you have got a friend on z - tales from cics transaction gateway final

© 2014 IBM Corporation

You've got a friend on z - tales from CICS Transaction Gateway

Session #1317

Ian ShoreIBM

CICS Transaction Gateway Manager Email: [email protected]

Elena Nanos Health Care Service Corporation

Lead Systems ArchitectEmail: [email protected]

Please Note

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.

1

CICS Transaction Gateway

Secure, scalable and highly available connectivity into the

CICS server family

Delivers access to CICS applications through standards-based

interfaces

?

2

Business value of CICS TG

Why choose CICS TG?

• No changes to CICS applications

• Lifecycle separation

• Network concentrator

• Distributed platforms integrate with any CICS server

• Bridges the skills gap

– Rich programming APIs

• Secure, scalable and highly available connectivity

• Monitoring and statistics provide insights into workload patterns*

3

What is CICS Transaction Gateway

Request Monitoring

Statistics through SMF

Dynamic Server Selection (DSS)

64-bit Gateway daemon on z/OS

NIST SP800-131a compliance

Application development with CICS TG APIs

…

There's much more ...

http://pic.dhe.ibm.com/infocenter/cicstgzo/v9r0/index.jsp

http://pic.dhe.ibm.com/infocenter/cicstgmp/v9r0/index.jsp

4

CICS TG Deployment options

CICS TG for Multiplatforms

CICS TG for z/OS

CICS TG Desktop Edition

DE+MP

support

AIX Windows

Linux (z/p/x)Oracle Solaris

HP-UX

CICS TS for z/OS

CICS TS for VSETXSeriesCICS TS for i

5

CICS TG Deployment options

CICS TG for Multiplatforms

Licensedby AU

100s

CICS TS for VSETXSeriesCICS TS for i

CICS TG for z/OS

Enterprise1000s

Licensedby PVU

Licensedby VU

CICS TS for z/OS

.NET Java C/C++

.NET

Java

C/C++

JEE

DE+MP

support

AIX Windows

Linux (z/p/x)Oracle Solaris

HP-UX

DE DE DE

.NET

Java

C/C++

JEE

CICS TG Desktop Edition

6

CICS TG for z/OS V9.1 open beta

?

7


JSON

Mobile devices

IBM Worklight server

8


Available now

Built upon the V9.0 foundation

Not for production use

Time limited

The CICS TG plug-in for CICS Explorer V5.2 is also available

Try it out and tell us what you think

9


Content

Mobile integration (JSON web services)

Access to channel data for request monitoring

Systems management for IPIC connections

IPIC heartbeat

SSL connectivity for .NET

Integration with IBM Rational Integration Tester (RIT)

10

Mobile demo

11

HCSC CICS Transaction Gateway

User Experience Implementing High Availability CICS TG

Architecture on z/OS Platform

Health Care Service Corporation (HCSC) is the fourth largest health insurance company in the nation.

Largest customer-owned health insurer in the U.S., founded in 1936, now with more than 14 million members, HCSC operates health insurance Plans in Illinois, Montana, New Mexico, Oklahoma, Texas, and Dearborn National.

We're greater than 21,000 employees strong with 60 local offices and state-of-the-art technology, including two Tier IV data centers – the industry's highest reliability level –that provide the speed and data security to meet our customers' current and future business needs.

13

Session #1317 - You've got a friend on z - tales from CICS Transaction Gateway

About Health Care Service Corporation

14


� Topology 1 was our main WASd/CICS TG configuration.

� Topology 2 was proposed configuration moving CICS TG off distributed platform into

z/OS, using CICS TG on z/OS stand-alone (Remote mode). This is our current topology.

� Topology 3 is also used with WAS on z/OS and CICS TG configuration, using CICS

TG in Local mode. Note: Local mode on z/OS can use either EXCI (which is MRO

cross memory), or IPIC (which is still sockets-based, but will be optimized in TCPIP to

Fast Local Sockets - effectively cross memory - when co-located within the same

LPAR as CICS).

HCSC CICS TG Topology

Current Configuration

15

Previous HCSC Distributed Configuration


5

16


HCSC CICS TG HA Architecture

(set in Runtime env CICSCLI)

SECTION IPICSERVER = SYS1CIC1description = IPIC connection to CICS region #1 hostname = your.host.net

port = 3101 tcpkeepalive = Y srvidletimeout = 60 srvretryinterval = 0 connecttimeout = 10sendsessions = 200

ENDSECTION

SECTION IPICSERVER = SYS1CIC2description = IPIC connection to CICS region #2hostname = your.host.net


ENDSECTION

SECTION IPICSERVER = SYS2CIC3description = IPIC connection to CICS region #3 hostname = your.host.net


ENDSECTION

SECTION IPICSERVER = SYS2CIC4description = IPIC connection to CICS region #4hostname = your.host.net

port = 3104 tcpkeepalive = Y srvidletimeout = 60 srvretryinterval = 0 connecttimeout = 10

sendsessions = 200

ENDSECTION

On the Gateway you can set - CONNECTTIMEOUT, which is a numeric value between 0 and 3600, specifying the maximum time in seconds that establishing a connection is allowed to take. The default value of 0 means that no limit is set. For more details see - http://publib.boulder.ibm.com/infocenter/txformp/v7r1/index.jsp?topic=/com.ibm.cics.tx.doc/tasks/t_config_ipic.html

Session #1317 - You've got a friend on z - tales from CICS Transaction Gateway17

Sample CICS TG CONFIG File

18


Technology Utilized in HCSC CICS TG HA Architecture

Two different workload balancing polices (round robin or fail over) are supplied – both of which use server rules from the HA configuration file to remap and retry failed requests.

For example, the following server rule defines the server alias SERVER1 as mapping to 4 actual CICS servers CICSA, CICSB, CICSC & CICSD:

SERVER1=CICSA,CICSB,CICSC,CICSD

� The round robin policy will distribute requests in a round robin fashion, so that

requests are evenly distributed across servers CICSA, CICSB, CICSC & CICSD.

� The fail over policy will distribute requests in a hierarchical order so that all requests

are sent to CICSA, if this is unavailable requests will be sent to CICSB, if CICSB is

unavailable requests will be sent to CICSC, and if CICSC is unavailable requests will

be sent to CICSD.

http://www-01.ibm.com/support/docview.wss?uid=swg24021484

19

SupportPack CA1T – CICS TG High Availability User Exits


Three different CICS request exit implementations are provided as follows:

1. FailOver – uses a list of CICS servers to define how server names are remapped. Requests will be retried using a static list of servers, each server being used in turn from the list until the list is exhausted or the request succeeds.

2. RoundRobin – distributes ECI requests around a list of CICS servers in round-robin fashion. Requests will be distributed evenly across the servers, and retried until the request succeeds or all servers have been used.

3. RequestValidation – validates the transaction ID, program, and user ID parameters in the ECI request against a defined list. No server name remapping is performed.

Latest enhancements

CA1T V3.0 support pac has been recently updated and gives ability to set new environment variable CTG_HAVALIDATION=EXCLUSIVE, then any request which matches one of the USERID, TRANSID and PROGRAM validation rules will be rejected with ECI_ERR_INVALID_CALL_TYPE (-14).

Note: Configuration is based on a flexible set of rules defined in a configuration file. On z/OS, the configuration file can reside either on HFS or

in an MVS dataset. Rules for workload balancing can be generic per Gateway, based on server aliases, or on the payload type (for example,

channel or commarea). Rules for request validation can be specified based on user IDs, transaction IDs, or program names, and operate as

either a white list (INCLUSIVE) or black list (EXCLUSIVE). All rules can be dynamically updated while the Gateway daemon is running. A

configurable retry interval is provided to improve the efficiency of request distribution when using workload balancing.

http://www-01.ibm.com/support/docview.wss?uid=swg24021484

20

(cont.)

SupportPack CA1T V3.0 – CICS TG HA User Exits


20

21


Support Pack CH51: CICS TG Simple Request Monitor Utility Setup

� CICS TG V8.0 or prior has two CICS Resource Adapters – XA and non-XA.

� CICS TG V8.1 has support for Java Enterprise Edition 6

� The CICS connectors included with CICS TG V8.1 exploit JEE 6 / JCA 1.6

� JEE 6 certified application servers (e.g. WAS 8.0) benefit from:

� A single ECI resource adapter (rather than two) including support for both XA (two-phase commit) and non-XA transactions

� A more flexible approach to setting the transactional capabilities of the CICS ECI resource adapter

� Lower administrative and maintenance overheads

Resource adapters compatible with JEE 5 (or earlier) application servers are available

use with CICS TG V8.1 in remote mode only from Support Pac CC03

22

CICS JCA Resource Adapters


22

23


� The CC03 Supportpac provides access to CICS TG resource adapters and the

maintenance levels of each resource adapter is documented in the download page

http://www.ibm.com/support/docview.wss?uid=swg24008817

� For compatibility reasons, connectivity from the CICS JCA resource adapters to a remote CICS TG is only supported, if the remote CICS TG is at the same or higher release level than the version of the JCA resource adapter.

� The version of the CICS TG class libraries or RARs must be at the same maintenance level, or lower than the version of the Gateway daemon.

� The version of the resource adapters is listed in the <resourceadapter-version> element

in the ra.xml file, supplied with the resource adapter package.

Example below is ra.xml file for CTG V9.0 -

CICS TG Compatibility with WebSphere

24


CICS Connection Pool Tuning in WAS

25


MVS Console Commands

Issue #1We implemented new Application using CICS TG on z/OS, which had invalid Userid set on Connection

Factory. This caused ID to get suspended and Application was redriving error routine to reestablish CICS TG connection, after each failure. This caused connections not getting released, causing all connections to be in use across all 4 CICS TGs, resulting in CICS TG -16 ECI_ERR_RESOURCE_SHORTAGE.

SolutionSetup automation to issue CICS TG console command –/F CICS TGname,APPL=STATS,GS every 5 minutes and send alert if field CS_CSESSCURR (total # of

IPIC sessions in use with all CICS servers) is at 80% or higher from CS_CSESSMAX (# of IPIC sessions negotiated with CICS servers). Can also have automation (OPS/MVS for example) check the values of CM_CALLOC and WT_ALLOC and alert if the threshold set has been passed.

Issue #2Application gets the following exceptions when OLD copy of CTG Client JAR is in the Classpath -

� SRVE0068E: Uncaught exception created in one of the service methods of the servlet action in application. Exception created : java.io.IOException:

� CTG6653E Unable to flow request to the Gateway daemon; this JavaGateway instance has been closed

SolutionWhen upgrading WAS version or changing CTG from Local to Remote mode, make sure that OLD CTG

Client JAR is not in the WebSphere JVM Process Definition Classpath.

CTG RAR file has both Server and Client JAR files.

Issues to Watch Out For

26


EXCI vs IPIC CPU Usage

27


CPU Cost Getting CICS Data

28


Scalability Performance Data – 31-bit vs 64-bit

29


CPU Performance Data – 31-bit vs 64-bit

30



� The 31-bit Gateway daemon is ideal for small payloads and small numbers of clients, and will typically offer a greater CPU cost per transaction compared

to a 64-bit Gateway daemon running the same workload.� Migration to 64-bit can reduce number of address spaces. The 64-bit

Gateway daemon offers good scalability for both large payloads and large

numbers of clients. For best performance with 64-bit, use compressed

reference.� Both the 31-bit and 64-bit Gateway daemons performed at a similar TPS

when running the same workloads (based on IBM study).� When using IPIC, zAAP/zIIPs can provide large benefits by offloading

eligible work, thus potentially reducing the cost of running workloads.

� Channels (rather than COMMAREAs) provide greater benefits and flexibility, and should be considered when writing new applications.

� Fully exploit IPIC and Dynamic Server Selection after migrating from the constraint of 250 EXCI pipes.

� Rule of thumb for Gateway MEMLIMT

- MEMLIMIT should be at least

128MB (core) + Heap size + (#CM+WT threads) * 3MB

Performance Tuning Suggestions

31



� Go CICS TG on z/OS V9.0 and look into running gateway daemons in 64 bit mode and consolidating workloads, where it makes sense.

� Once you go to CICS TS V5.1 you can benefit from the increase of MAXTASKS, that now can be up to 2,000, allowing more work through the Gateway and into the single CICS.

� Using IPIC protocol with CTG V9.0 and CICS TS V5.1 you can have up to a 1,000 individual transactions going on to one CICS region and it can scale up to more

connections into one CICS region.

� Exploit channels for over 32K payloads. Can go 2GB+ payloads.

� CTG V9.0 has improved dynamic server selection process, using updated CTG monitoring

exits. There is a new monitoring exit point that gets fired just before request goes to CICS.

Now you will be able to see when the request came in and where it’s going to and then track

further down the chain.

� WebSphere V8.5.x introduced a new transaction tracking tool Cross Component Trace (XCT), which gives you some eye catcher type of fields that show you who’s got control of a particular piece of a transaction and how long it’s spent at each of these places. If you are using CICS Resource Adapter with WebSphere, than using XCT you can

see transactional tracking tokens then get passed through from WebSphere through CICS

TG.

� Take advantage of CICS TG for z/OS V9.1 open beta.

What’s Next for CICS TG?

32


Tools That Can Be Utilized to Monitor CICS TG

� Support Pack CH51: CICS TG Simple Request Monitor Utility

� CA Wily Introscope

� IBM CICS Performance Analyzer for z/OS

� IBM CICS Explorer CICS TG Gateway Plug-in

� IBM Tivoli products:� OMEGAMON Performance Management Suite for z/OS V5.1.1

� Monitoring offering for CICS TG� Composite Application Manager for Transactions

� MVS Console Commands

� CICS TG SMF 111 Records Reporting

� MICS CICS TG Report

�

33


CA Wily Introscope CICS TG Metrics

34


CA Wily Introscope Response Time Metrics

CICS Transaction Gateway - Activity Summary

_____________________________________________

0STTG0001 Printed at 11:29:15 3/01/2013 Data from 08:00:00 2/21/2013 to 08:00:00 2/21/2013 Page 1

CICS TG GATEWAY 02/21/13 REPORT

Gateway ID Start time Up time Number of Number of Peak Peak TPS time Connect Worker

Intervals requests TPS Timeouts Timeouts

ZOSCGRP0.CICS TG2P003 2013-02-14 06.10 7days 17.34.09 95 1643676 13 2013-02-21-17.15.00 0 0




Gateway ID Start time Collection time Region Java heap Clients Workers EXCI pipes IPIC sessions

Size/Max Size/Max Peak/Max Peak/Max Num/Max Num/Avail

ZOSCGRP0.CICS TG2P003 2013-02-14 06.10 2013-02-21-16.00.00 875M/1000M 71M/512M 19/500 3/800 0/0 0/400




CICS Performance Analyzer V5.1 now includes two CICS TG batch reports, "Activity Summary" and "Usage and Capacity" which can be run against SMF 111 records from CICS TG for z/OS.

35

CICS Performance Analyzer for z/OS - Sample Reports


ExplorerReports

36


CICS Transaction Gateway Plug-in for the CICS

eports

37



IBM Tivoli OMEGAMON Performance Management Suite for z/OS V5.1.1

� Deep dive monitor of CICS TG instances (Gateway daemon and WebSphere clients) running on z/OS� Alert users to communication problems between CICS TG and CICS� Provides up-to-the-second details on transaction rate, I/O and CPU consumption� Helps to plan for workload growth, performance trend analysis and future capacity planning� One-click dynamic linking into monitoring tools for other System z applications

eports

38



IBM Tivoli OMEGAMON Performance Management Suite for z/OS V5.1.1

eports

39



� End-to-End analysis of transaction response time and performance� Full transaction tracking of flows through CICS TG on both z/OS and

multiplatforms� Helps identify topology connections from WebSphere through CICS TG to

CICS (and onwards)� View system and transaction interactions at four levels of depth (Server,

Component, Application and Transaction)

IBM Tivoli Monitoring Offering for CICS TG

CSSYS1CIC1_SIPADDR=yourSYS1.network.net (CICS server TCP/IP address)

CSSYS1CIC1_SIPPORT=3168 (CICS server TCP/IP port)

CSSYS1CIC1_LALLREQ=4549989 (Number of requests processed)

CSSYS1CIC1_CWAITING=-2 (Number of requests waiting on a response)

CSSYS1CIC1_SSESSMAX=200 (Number of requested IPIC sessions)

CSSYS1CIC1_CSESSMAX=200 (Number of negotiated IPIC sessions)

CSSYS1CIC1_CSESSCURR=0 (Number of IPIC sessions in use)

CSSYS1CIC1_LCOMMSFAIL=49 (Number of CICS communication failures)

CSSYS1CIC1_LCONNFAIL=4484 (Number of connection failures)

CSSYS1CIC1_LLOSTCONN=32 (Number of lost connections)

CSSYS1CIC1_LSESSFAIL=0 (Number of IPIC session failures)

CSSYS1CIC1_LIDLETIMEOUT=0 (Number of timed out connections)

CSSYS1CIC1_LREQDATA=28649890161 (Amount of CICS request data)

CSSYS1CIC1_LRESPDATA=29043330152 (Amount of CICS response data)

CSSYS1CIC1_LAVRESP=64 (Average CICS response time)

CSSYS1CIC1_CAPPLIDQ=ILA (APPLID qualifier of connected CICS)

CSSYS1CIC1_CAPPLID=YourCICSApplid (APPLID of connected CICS)

CSSYS1CIC1_ICOMMSFAIL=0 (Number of CICS communication failures)

CSSYS1CIC1_ICONNFAIL=0 (Number of connection failures)

GD_IAVRESP=42 (Average Gateway daemon response time)

GD_LAVRESPIO=109 (Average Gateway daemon response time

with I/O)

GD_IAVRESPIO=98 (Average Gateway daemon response time

with I/O)

GD_SNAME=CICS TGPRD1 (Gateway daemon name)

GD_CHEALTH=100 (Gateway daemon health)

GD_LHAEXIT=4687171 (Number of CICS request exit calls)

GD_IHAEXIT=642 (Number of CICS request exit calls)

GD_SDFLTSRV= (Default server name)

GD_LRUNTIME=1758839 (Gateway daemon running time)

GD_SSTATINT=001500 (Length of the statistics interval HHMMSS)

GD_SSTATEOD=000000 (Logical End Of Day time HHMMSS)

GD_CNEXTRESET=150000 (End of interval time HHMMSS)

GD_IRUNTIME=199 (Interval running time)

WT - Worker thread

WT_SMAX=800 (Maximum number of worker threads)

WT_SINIT=200 (Initial number of worker threads)

WT_CCURR=200 (Current number of worker threads)

WT_CALLOC=0 (Currently allocated worker threads)

WT_LTIMEOUTS=0 (Number of times worker time out reached)

WT_ITIMEOUTS=0 (Number of times worker time out reached)

With CICS TG on z/OS stand alone we can use MVS console commands to display statistical information about the CICS TG, or can obtain statistics using the Statistics API interface.

/F CICS TGname,APPL=STATS,GS

40


40

Headline Goes Here

41


eports

42



eports

43



44


� Common Architectures and Standard Used with CICS� Support Pack CC03: CICS JCA Resource Adapters for Use With

JEE Application Servers� POC Testing – High zAAP Offload Rate� zAAP Offload with EXCI and IPIC Connections� WLM Feedback� CA Wily Introscope ECI Pool Size Metrics� Support Pack CH51: CICS TG Simple Request Monitor Utility� IBM Tivoli OMEGAMON XE for CICS on z/OS V5.1.0� IBM Tivoli Monitoring offering for CICS TG� IBM Tivoli OMEGAMON XE for CICS on z/OS Statement Of

Direction

Need more information?!

Ask your Account representative to arrange a visit or call

• Can contact me directly

– [email protected]

– @ian_shore

Sign up to the CICS TG for z/OS V9.1 open beta

• Engage directly with the CICS TG development team, discuss the open beta capabilities, and leverage the very best expertise available

• http://www.ibm.com/cics/openbeta/

Performance reports now available

• http://www.ibm.com/support/docview.wss?uid=swg24036898

45

Questions?

We Value Your Feedback

Don’t forget to submit your Impact session and speaker

feedback! Your feedback is very important to us – we use it to

continually improve the conference.

Use the Conference Mobile App or the online Agenda Builder to

quickly submit your survey

• Navigate to “Surveys” to see a view of surveys for sessions you’ve attended

47

Thank You

Legal Disclaimer

• © IBM Corporation 2014. All Rights Reserved.• The information contained in this publication is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained

in this publication, it is provided AS IS without warranty of any kind, express or implied. In addition, this information is based on IBM’s current product plans and strategy, which are subject to change by IBM without notice. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this publication or any other materials. Nothing contained in this publication is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software.

• References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in this presentation may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results.

• If the text contains performance statistics or references to benchmarks, insert the following language; otherwise delete: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.

• If the text includes any customer examples, please confirm we have prior written approval from such customer and insert the following language; otherwise delete:All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer.

• Please review text for proper trademark attribution of IBM products. At first use, each product name must be the full name and include appropriate trademark symbols (e.g., IBM Lotus® Sametime® Unyte™). Subsequent references can drop “IBM” but should include the proper branding (e.g., Lotus Sametime Gateway, or WebSphere Application Server). Please refer to http://www.ibm.com/legal/copytrade.shtml for guidance on which trademarks require the ® or ™ symbol. Do not use abbreviations for IBM product names in your presentation. All product names must be used as adjectives rather than nouns. Please list all of the trademarks that you use in your presentation as follows; delete any not included in your presentation. IBM, the IBM logo, Lotus, Lotus Notes, Notes, Domino, Quickr, Sametime, WebSphere, UC2, PartnerWorld and Lotusphere are trademarks of International Business Machines Corporation in the United States, other countries, or both. Unyte is a trademark of WebDialogs, Inc., in the United States, other countries, or both.

• If you reference Adobe® in the text, please mark the first use and include the following; otherwise delete:Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.

• If you reference Java™ in the text, please mark the first use and include the following; otherwise delete:Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

• If you reference Microsoft® and/or Windows® in the text, please mark the first use and include the following, as applicable; otherwise delete:Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.

• If you reference Intel® and/or any of the following Intel products in the text, please mark the first use and include those that you use as follows; otherwise delete:Intel, Intel Centrino, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

• If you reference UNIX® in the text, please mark the first use and include the following; otherwise delete:UNIX is a registered trademark of The Open Group in the United States and other countries.

• If you reference Linux® in your presentation, please mark the first use and include the following; otherwise delete:Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others.

• If the text/graphics include screenshots, no actual IBM employee names may be used (even your own), if your screenshots include fictitious company names (e.g., Renovations, Zeta Bank, Acme) please update and insert the following; otherwise delete: All references to [insert fictitious company name] refer to a fictitious company and are used for illustration purposes only.

49

50


Common Architectures and Standard Used with CICS

51


Headline Goes Here

52


http://www-01.ibm.com/support/docview.wss?uid=swg24008817&myns=swgother&mynp=OCSSGMJ2&mync=E

Headline Goes Here

53


54


EnvironmentHardware

• IBM System z: z10 2097-763 model E64• 2GB of Central Storage (RAM)• LPAR with 3 dedicated GCPs• LPAR with 1 zAAP available (zAAP offload scenario only)• IBM System x: x3550 M3 Intel® Xeon® 5600• OSA-Express3 10GB Ethernet SR

Software

• CICS Transaction Gateway for z/OS V8.1• CICS Transaction Server for z/OS V4.2 (zAAP offload scenario only)• CICS Transaction Server for z/OS V4.1• z/OS V1R12• IBM 31-bit SDK for z/OS Java Technology Edition, Version 6.0.1• SUSE Linux Enterprise Server 11

The graph shows zAAP offload with 200 clients 32KB offload @ 1890 TPS

Data from CICS Transaction Gateway for z/OS V8.1 Performance summaryat: ftp://public.dhe.ibm.com/software/htp/cics/support/supportpacs/individual/CTGV81_Performance-V1.2.pdf

zAAP Offload with EXCI and IPIC Connections

rchitecture

55


WLM Feedback

56


CA Wily Introscope ECI Pool Size Metrics

57


Support Pack CH51: CICS TG Simple Request Monitor Utility

58

� Performance Tuning�Helps to prevent CICS becoming overloaded or underutilized

�Allows for optimization of workflow through CICS TG and onto CICS

�Alerts users to changes in behavior when abnormal workloads hit

CICS TG

�Provides users with an account of transactions per minute and CPU

consumption

� Availability�Alerts users to communication problems between CICS TG and

CICS

� Manageability�Helps to determine where to control resources in CICS TG or CICS

� Monitoring�Transaction Monitoring in Gateway daemon and WebShere

Application Server on z/OS

�Transaction Response Time Analysis, Payload and Wiresize per

transaction

� End To End Response Time Analysis

� Problem Determination�Identifies the bottlenecks within CICS TG daemon

�Identifies Abended transactions

�Correlates all application Flows within a Transaction

�Provides Transaction Flow Trace

� Capacity Planning�Helps to plan for workload growth, perform trend analysis, detect

system anomalies and to identify performance bottlenecks using the

historical data via the Tivoli Data Warehouse repository

� Total Cost of Ownership�Opens up the “black-box” of CICS TG thread management and helps

to save precious resources in both CICS TG and CICS

IBM Tivoli OMEGAMON XE for CICS on z/OS V5.1.0


eports

59



There are two products in the IBM Tivoli Monitoring portfolio that monitor CICS TG to help with problem identification, resolution, and prevention:

IBM Tivoli Monitoring Offering for CICS TG

60

� In addition to IBM Tivoli OMEGAMON XE on z/OS and IBM Tivoli

OMEGAMON XE on CICS, Tivoli intends to provide additional new V5.1

support, including IBM Tivoli Monitoring V6.2.3 on IBM Tivoli OMEGAMON XE for IMS™, IBM Tivoli OMEGAMON XE for Mainframe Networks, IBM Tivoli

OMEGAMON for Messaging, IBM Tivoli OMEGAMON XE for DB2 Performance Expert (and Monitor) on z/OS, and IBM Tivoli OMEGAMON XE for Storage.

� Tivoli plans to discontinue the Tivoli OMEGAMON II® agents and UIs

commonly called Common User Access (CUA).� IBM plans to discontinue OMEGAVIEW, which is comprised of OMEGAMON II

agents.

� Tivoli OMEGAMON plans to discontinue Installation and Configuration Assistant Tool (ICAT) and use the Parmgen methodology as the strategic way

to install and upgrade the Tivoli OMEGAMON family of products.

� IBM Tivoli OMEGAMON XE for CICS on z/OS will remove Epilog functions

from V5.1. A companion product that would provide improved reporting capability is IBM CICS Performance Analyzer for z/OS.

Source - http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/1/897/ENUS212-041/index.html&lang=en&request_locale=en#h2-sodx

IBM Tivoli OMEGAMON XE for CICS on z/OSStatement of Direction


impact2014 session #1317 you have got a friend on z - tales from cics transaction gateway final

Technology

multiplatforms cics

cics tg plugin

zos cics ts

hcsc cics tg topology

cics tg apis theres

business value of cics

zos cics tg desktop

vu cics ts