end to end transaction management with bmc solutions-1 - end...cics1 sql plan1 dpl to prog2 cics2...

End to End Transaction Management Bringing the two world together

Eric Maanen

Software Consultant

2

Abstract

› Do you wonder why one renegade transaction can cost you thousands of Euros without breaching your SLA agreements? Nonsensical, isn't it?

› Find out how you can look into that transaction that went sour.

– Follow business services across all of the technical systems and sub-systems at a transaction level,

– Identify the components responsible for business slowdowns or outages, and

– Determine and correct the root cause of transaction problems.

3

The Problem

› SLA’s are typically expressed in term such as:

– A percentile of work to be completed in the specified amount of time

– Or an average response time

– An example: WLM in z/OS

• And WLM is not End-to-End

› From a SLA Reporting standpoint

– What if the one transaction that the “Prime Minister” does for his banking takes 30 seconds all of a sudden

4

The Problem

› Real-time Alarms are also typically expressed in term such as:

– Response time, mostly average over a short interval, for transaction as seen within a sub-system does not exceed a threshold

› From a Real-time Alarm Standpoint

– Again, what if the one transaction that the “Prime Minister” does for his banking take 30 seconds all of a sudden

5

What we need is to look beyond technology monitoring to provide the end user’s point

of view of application performance

The Need

93%

Network

Web Server

J2EE Server

MQ Server

Oracle

CICS

Siebel

Business Service

Available, Performing Unavailable or Slow

6

The Need

› Customer Reality: Transaction Management Remains a Challenge1

– Leading challenges to transaction management are “lost transactions” and “determining the cause of poor performance”

– Most companies have a need to measure end-to-end service availability from the user’s perspective (68%)

– Few companies measure end-to-end service availability (37%)

– Over 50% cite the “lack of appropriate tools” as the limiting factor to managing transactions

– Companies believe transaction management must span mainframe anddistributed environments

1 Ziff-Davis, Enterprise Transaction Management Survey, December 2005 – Survey sample: 1,190

7

The Need

› As one customer puts it

– “We need to investigate slow downs that last roughly 30 seconds to a minutes where response time is elongated to 0.5 seconds!”

– “When the VP’s ask for this we have to look in CICS, DB2, IMS and MQ logs and traces in order to follow where a given ‘business transaction’ went and how the time was spent”

– “It is not easy as we are the people who manage systems/subsystems and we have little knowledge about what makes-up a ‘business transaction”

8

The Idea!

› For the purpose of integrity processing, the z/OS system/subsystems maintain UOR/UOW information for application

› Exploit this information to automatically correlate UOR/UOW in order to derive what is a ‘business transaction’

› UOR/UOW information is already collected in our various monitors

9

CICS

DB2

IMS

MQ

WAS

3270

Web

Batch

TSO

CTG

How it worksA day in the life of a transaction

10

How it worksSample Flow for illustration

MVI

CAS

DB21

MVCICS

PASMVDB2

PAS

MVLOG

STC

MVTA

PAS

MVI

CAS

DB22

MVCICS

PASMVDB2

PAS

MVLOG

STCMVTA

PAS

CICS1

SQL PLAN1

DPL to PROG2

CICS2

SQL PLAN2TRN1 CSMI

UOR4UOR3

UOR2UOR1

SYNCPOINT

And

End

MVTA

Log

MVTA

Log

11

Sample UsageIn CICS an end-user invoke transaction MCB1

12

Sample UsagePerform some query

13

Sample UsageEventually result of the query is return

14

Sample Usage

› How would you know

– If any, which other CICS transaction makes-up this ‘business transaction’

– If any, which other IMS transaction makes-up this ‘business transaction’

– If any, which DB2 Subsystem Tables could have been involved involved

– If any, which WebSphere MQSeries queues could have been involved

› With a little bit of…..

– You don’t need to know nor worry about what makes-up a ‘business transaction’

– You are called upon to investigate and you know it happened in the morning and luckily you know it originated from a CICS transaction MCB1

15

Sample Usage - Interface 3270Starting an Analysis

16

Sample Usage - Interface 3270 Specify some search criteria

17

Sample Usage - Interface 3270 That morning we see that 5 MCB1 were executed

18

Sample Usage - Interface 3270 Let’s look at that 16 seconds one

19

Sample Usage - Interface 3270 Let’s look at what else made up that transaction

20

Sample Usage - Interface 3270 Let’s get the detail

21

Sample Usage - Interface 3270 Let’s get the Response Time Component

22

Sample Usage - Interface 3270 Let’s zoom-in the Communication Data

23

Sample Usage - Interface 3270 Waiting for user input…

24

Sample Usage – Web Interface We know it is transaction TALL sometime…

25

Sample Usage – Web InterfaceExpand on 2 instances in CICS

26

Sample Usage – Web Interface Correlate the component

27

Sample Usage – Web Interface The component of the ‘business transaction’

28

Sample Usage – Web Interface The component of the ‘business transaction’

29

Sample Usage – Web Interface The topology of the ‘business transaction’

30

Next Steps at the Enterprise Wide level

› Tracking transaction flows at the enterprise level

› Additional z/OS support

– Integration with WebSphere for Application Server

– Provide for CICS Transaction Gateway, IMS Connect and DB2 Connect

› captures MQ related transaction flows when they enter z/OS

– For MQ applications following ‘best practices’ where MQ MSGIDs are unique, answer to important questions can be done:

• A CICS task executes MQPUT to a Queue for which an IMS trigger is defined

• Question: What IMS transaction ran and how well did it perform?

› does not capture MQ related flows before they enter z/OS

– From where did the initial MQ request originate in the distributed environment and how well did application processes associated with it perform

31

Java API

C API

CICS API

COM/.NET API

Introducing QNami! by MQSoftware

32

Introducing QNami! by MQSoftware

– Transaction Monitoring

– Transaction Tracking

– Business Performance Monitoring

• Quantitative

• Qualitative

– Business Process Measurements

– SLA Monitoring and Reporting

– Business Payload Monitoring and Reporting

– Business Service Monitoring

– Performance and Availability Monitoring

– Event Correlation and Management based on Payload Contents and Transaction Timeouts or Failures

– Real-time User Defined Dashboards

33

Application Flow Diagram

34

End-to-End Business Transaction

35

WASWAS WMBWMB

CICSCICS

DB2DB2

IMSIMS

WMQ WMQ

Linux AIX

z/OS

Business Application Support Virtual Team

MV

Sample Business Application:Insurance Policy Purchase

Architectural view of data flow for

Insurance Policy Purchase business

application

36


WASWAS WMBWMB

CICSCICS

DB2DB2

IMSIMS

WMQ WMQ

Linux AIX

z/OS

Txn 1 Start

Txn 1 End

Life is good!


Everything is running with no problems. Virtual team members can concentrate on other

value producing activities

37


WASWAS WMBWMB

CICSCICS

DB2DB2

IMSIMS

WMQ WMQ

Linux AIX

z/OS

Txn 1 Start


Q Nami! operations console

showing the status of individual

transactions



transactions

Q Nami! drill-down to

performance and availability

metrics for WMB

Q Nami! drill-down to

performance and availability

metrics for WMB

Analyze specific node in WMB

execution group to optimize

response times

Analyze specific node in WMB

execution group to optimize

response times

38


WASWAS WMBWMB

CICSCICS

DB2DB2

IMSIMS

WMQ WMQ

Linux AIX

z/OS

Txn 1 Start




transactions



transactions

Q Nami! drill-down to business

service views for insurance policy

purchase business application

Q Nami! drill-down to business

service views for insurance policy

purchase business application

Analyze specific interactions of

mainframe components through

MVTA

Analyze specific interactions of

mainframe components through

MVTA

Thank You!

end to end transaction management with bmc solutions-1 - end...cics1 sql plan1 dpl to prog2 cics2...

Documents