ims problem analyzer problem investigation cex update

© 2010 IBM Corporation

Information Management

2010 – Information Management Tech Conference - Brazil

Updates to IMS performance tools

Janet LeBlanc Silicon Valley Lab [email protected]




IMS Tools Product Portfolio

HALDB ToolkitSequential Randomizer Generator

IMS DB Reorganization ExpertOnline Reorganization FacilityIMS Cloning ToolIMS Database Control Suite

IMS HP Image CopyDEDB Fast RecoveryIMS Recovery Expert V2

Batch Terminal SimulatorBatch Backout ManagerProgram Restart Facility

Data Base Administration

Utility Management

Backup and Recovery

Application Management

Performance Management

Command Control FacilityETO SupportHP Sysgen ToolsQueue Control FacilityIMS Workload Router

TransactionManagement

System Administration

RegulatoryCompliance

Buffer Pool AnalyzerNetwork Compression Facility

IMS Configuration ManagerIMS Sysplex Manager

IMS Audit Management ExpertIBM Data Encryption for IMS and DB2 Databases

IMS Tools Base for z/OS

IMS Tools Generic ExitsTOSIPolicy ServicesIMS Tools Knowledge BaseIMS HD Compression Ext

IMS Fast Path Solution Pack for z/OS

IMS HP Fast Path UtilitiesIMS DB Repair FacilityIMS HP Image CopyIMS Library Integrity Utilities

IMS Database Solution Pack for z/OS

DB Reorganization Expert- Unload, Load, Index Build, Prefix Resolution/UpdateHP Image CopyHP Pointer CheckerLibrary Integrity Utilities

IMS Performance Solution Pack for z/OS

IMS Connect ExtensionsIMS Performance AnalyzerIMS Problem Investigator

IMS Recovery Solution Pack for z/OS

HP Image CopyDatabase Recovery FacilityHP Change AccumulationRecovery Expert




Updates to IMS Tools Performance Tools

2009

� August 2009– IMS Connect Ext V2.2– IMS Performance Analyzer V4.2

� October 2009– IMS Problem Investigator V2.2

2010

� February 2010– IMS Tools Solution Packs

•IMS Performance Solution Pack

•IMS Connect Ext

•IMS Performance Analyzer

•IMS Problem Investigator

– IMS Tools Base

• IMS Tools Knowledge Base




New Year – New Message!

� IMS Tools Solution Packs• Related products packaged together to provide end-to-end IMS

solutions

Database, Fast Path, Recovery, Performance• Lay the foundation for new IMS Tools in the pipeline via a no-charge

Base Pack which contains necessary common code (Generic Exits,

DAI, ITKB, etc.)

� What’s the value to customers?• The customer receives a complete solution for all of their needs

rather than having to purchase multiple tools

• Solution Packs are discounted, offering real value

Reduce CPU

Consumption

Reduce DBA Labor Costs

Eliminate Application Downtime

++ ++ ==Deliver faster return on your investment!




IMS Recovery IMS Recovery

Solution PackSolution Pack

IMS Database IMS Database


IMS Performance IMS Performance


Everything you need for…

IMS Fast Path IMS Fast Path


IMS Tools Base




IMS Performance Solution Pack for z/OS

� IMS Connect Ext

� IMS Performance Analyzer

� IMS Problem Investigator




IMS Connect Extensions

� IMS Connect Extensions is a key tool for managing access to IMS through IMS

Connect

� Key benefits: – Provides event collection and instrumentation for IMS Connect

– Streamlines operational management of IMS Connect and its clients

– Assists in the development of TCP/IP clients and the transition to an SOA

� Principal users: IMS tuning specialists, application developers, and administrators

7



© 2004 IBM Corporation8

What’s new in IMS Connect Extensions V2R2?(includes features delivered through PTFs in V2R1)

� Eclipse-based operational management GUI

� Rules-based routing

� Extended status information

� TCP/IP information (similar to NETSTAT) for active sessions

� Routing intelligence improved to use IMS flood-warn state

� IMS V11 command support

� IMS V11 event collection

� Improved management of IMS Connect transaction options

� Persistent trace: activate IMS Connect Extensions tracing on every system restart

� Verify user service exit function

� Batch Command utility refresh of Connect Extensions options

� Mixed-case password support

� Simplified configuration with setup dialog




Eclipse GUI

� New IMS Connect interface: provides all IMS Connect Extensions operational

management capabilities

� Does not provide definition management (still ISPF only)

� Shipped as part of the product libraries

� Connects via the same TCP/IP port as the IMS Connect Extensions’ ISPF dialog

� Requires no additional server-side configuration

9




Tokyo

Centralized monitoring and control

IMS

IMS Connect

IMS

IMS

IMS Connect

New York

IMS

IMS Connect

IMS

IMS

IMS Connect

File Option Help

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

_ Stop IMS 1 link

_ View TOKYO sessions

_ Stop NY sessions

F1 – Help F2 - Scroll

Eclipse or ISPF

10

Single consolidated view of sessions running on all systems

(or view activity for individual systems or user-defined groups)

Extensive details on

individual sessions

The

system view

shows the

status of

all

systems

Cancel sessions

Active Sessions

12

You can

submit IMS

Connect

commands against

systems and

receive the output

IMS Connect command support

13

View activity for

IMS Connect

components. Stop

and start, exits, ports, and

datastores. Reload

Exits

Status Monitor View




Rules-based routing

� The simplest way to gain the benefits of IMS Connect Extensions’ routing

� Create rules that, for a given DESTID, determine a primary and fallback collection

of candidate datastores

� IMS Connect Extensions will balance workload between the datastores in the

primary collection

� If none of the datastores in the primary collection are available or if all datastores in that collection are in flood, then IMS Connect Extensions spreads workload

between the fallback collection

� Compatible with transactional messages, Send Only, Resume TPIPE,Synchronous callout, and Asynchronous callout

� Benefits: improved availability and performance; simplified management of clients;

better capacity management

14




IMS Connect Transaction Options

� IMS Connect clients can specify transaction parameters that:– Balance between responsiveness, resource usage, and reliability

– Handle duplicate client sessions

� Problem:– Tweaking and optimizing these values may require modifying every client that can

potentially access IMS Connect

– Customers may want to temporarily change parameter values for various reasons (peak-

capacity, faults, etc)

For example: clients specify the amount of time they are willing to wait on a

response from IMS:– A timeout that is too short can cause unnecessary session terminations.

– A timeout that’s too long can hurt client performance.

15




IMS Connect Transaction Options

File Menu Settings Help ──────────────────────────────────────────────────────────────────────────────

EDIT Transaction Command ===>

Name . . . . : PAYROLL Description . .

Application . . . SIMPLE +

Activate Transaction Timer Message timeout . . 00 (default)ACK/NAK timeout . . 00 (default)

Activate Transaction ExpirationActivate Client ID Cancellation

/ Activate Transaction Routing

Override Application options

Route transactions to:1 1. All Datastores

2. Datastore . . . . . . +3. Datastore Group . . . +4. Affinity List . . . . +

Routing Error processing:1. Use the original datastore in the message request 2. Reject the transaction

Set the timeout value for messages, as well as ACKs and NAKs for a given transaction code (V2R1)

Sets transaction expiration and Client ID cancellation options (V2R2)

16




IMS DB

WebSphere

IMS Connect

O

DB

MOther

application

LPAR A

TCP/IP

Distributed

Distributed IMS database access

IMS DB

O

DB

M

LPAR B




TCP/IP

ODBA DB

Distributed Database Lifecycle

What

happened?What was the

response time?

Which parts of the lifecycle do we Which parts of the lifecycle do we

care about?care about?

IMS Connect

What

happened?

What

happened?

Distributed Database Access

18




IMS Problem Investigator:Format and navigate log files quickly and easily

� IMS PI allows you to

interactively browse and

analyze log records

� Instantaneous view of the

logs

� Navigate by the time of

day

� Select records to drill

down right to the values

of individual flag bits

� Modern IMS transactions

affect multiple

subsystems

� Information about these

transactions is recorded

in even more sources

� IMS PI provides a unified

logical view of

transactions spanning all

these systems

IMS log

IMS transaction

IMS Problem Investigator

Data sources

Transaction activity merged into a single view

IMS-related subsystems

Transaction activity logged in multiple locations

IMS monitor

TRF Extractordata set

Extracts

CQS logDB2 log

DB2 CQSIMS DB/TMIMS ConnectWebSphere

MQ

WebSphere MQlog extract

IMS ConnectExtensions

journal

SMF

ISPF

dialogReports

OMEGAMONTRF records

IRLM long-lockrecords

User records

IMS ConnectExtensions

IMS PATransaction

Index




New in IMS PI V2.2 – GA Dec 2009

� Time slicing: Process large log files with the responsiveness and convenience of a

small extract file

� Transaction index: Extend the insights of transaction performance recorded by IMS PA to help analyze transactions in IMS PI

� Unit of work tracking: Isolate a single unit of recovery (TU) within a transaction

(TX) with a long program switch sequence

� Improved coverage with support for the DB2 and MQ logs

� Extract to CSV: Import the required fields from selected log record types into a

DB2 database or PC spreadsheet

� OMEGAMON TRF: transaction accounting, DLI and DB2 calls




Time slicing

Process Log Files Row 21 of 537 More: < >Command ===> Scroll ===> CSR

Select a Log File to browse. IMS Release 101 + Zone

/ Log File Rel + Filter + ZoneWWWWWWWW ‘IMSP.INDEX' 101 CA01

‘IMSP.SLDS' 101 01‘IMSP.OMEGAMON.ATF

WWWWWWWW ‘DB2.LOG.ARCHIVE'

Time Slicing Row 1 of 4 More: < >Command ===> Scroll ===> CSR

Specify the time of day and duration that you want to analyze. Select theslice (first row) to merge and process all the files, or select one file.

————————————————— Time Slice ———————————————————Time Date Duration

/ Type HH.MM.SS.thmiju YYYY-MM-DD HH.MM.SS.thmijuSSSS ALL 16.50.00.000000 2009-07-10 00.01.00.000000

—————————————————— Log Files ———————————————————Type Start Time Date Duration CoverageIDX 16.00.12.407506 2009-07-10 Fri 1.28.50.420549 COMPLETEIMS 16.00.02.466524 2009-07-10 Fri 1.53.37.334729 COMPLETEATF 16.00.15.965444 2009-07-10 Wed 1.47,45.176289 COMPLETEDB2 12.28.46.529264 2009-07-10 Sat 5.59.59.999999 COMPLETE

******************************* Bottom of data ********************************

Process large log files with the speed and convenience of a small extract

Specify the time period you need to investigate.PI goes directly to that point in the log(s), no waiting for a long sequential scan.

Merges all 4 files, and displays only the required 1minute interval




Transaction indexAll the accumulated information from the IMS log about each transaction is condensed into a single transaction index record – use the index as input into:1. IMSPA reporting, instead of re-processing large SLDS log files2. IMSPI, to enable more intelligent problem detection, as follows:

Conditions Row 1 to 2 of 2Command ===> Scroll ===> PAGE

Code: CA01 Transaction

/ Field Name + Oper Value +TRANCODE EQ 'MQATREQ1'PROCESS GT 1.0

******************************* Bottom of data ********************************

BROWSE JCH.INDEX Record 00427482 More: < >Command ===> FILTERFILTERFILTERFILTER Scroll ===> PAGE

Forwards / Backwards . . HH.MM.SS.THMIJU Time of Day . . HH.MM.SS.THMIJUCode Description Date 2009-07-10 Friday Time (Relative)

/ --- ------------------------------------------------------ ----------------TXTXTXTX CA01 Transaction 16.50.06.570728

TranCode=MQATREQ1 Program=MQATPGM Userid=FUNTRM07LTerm=FUNTRM07 Terminal=SC0TCP07 Region=0001OrgUOWID=IADG/C476657D88074C60 RecToken=IADG/0000002300000000CPU=0.033756 InputQ=0.000734 Process=1.204564TotalTm=1.305298 RegTyp=MPP DBCalls=5

---------------------------------------------------------------------------01 Input Message TranCode=MQATREQ1 +0.00000035 Input Message Enqueue TranCode=MQATREQ1 +0.00003208 Application Start TranCode=MQATREQ1 Region=0001 +0.0006315607 Start of UOR Program=MQATPGM Region=0001 +0.00063205 DLI (GU) TranCode=MQATREQ1 Region=0001 +0.00063831 DLI GU TranCode=MQATREQ1 Region=0001 +0.000697

Locate all MQATREQ1 transactions with processing time > 1 sec

Track against the index record to display all associated transaction log records:




OMEGAMON ATF: DLI callsOMEGAMON V4.2 ATF provides IMS transaction call trace for all DLI, DB2 and MQ calls

For each DLI call, see elapsed time, functon and status codes, SSAs:

BROWSE JCH.INDEX Record 00427482 More: < >Command ===> Scroll ===> PAGE


/ ---- ------------------------------------------------------ ----------------SSSS 01 DLI GHU Database=DI21PART ELAPSE=0.000153 +0.004704

01 DLI REPL Database=DI21PART ELAPSE=0.000516 +0.00499450 Database Update Database=DI21PART REGION=0001 +0.00507401 DLI GHU Database=DI21PART ELAPSE=0.000617 +0.00512801 DLI DLET Database=DI21PART ELAPSE=0.000415 +0.00519150 Database Update Database=DI21PART Region=0001 +0.00524650 Database Update Database=DI21PART Region=0001 +0.00538201 DLI ISRT Database=DI21PART ELAPSE=0.000298 +0.00546850 Database Update Database=DI21PART Region=0001 +0.00551550 Database Update Database=DI21PART Region=0001 +0.005561

BROWSE JCH.INDEX Record 00427491 Line 00000000********************************* Top of data *********************************+0012 Code... 01 DLI GHU+001C STCK... C476657D89349520 LSN.... 000000000000079C

Date... 2009-07-10 Friday Time... 16.50.06.575433.320

+0013 ATRSTYPE... 62 ATRPST..... 0001+0016 ATRCOR..... C9C1C4C70001C476656EDA182902+0024 ATRCRE..... C9C1C4C7404040400000002300000000+0034 ATRSTART... C476657D89349520 ATRELAPS... 0.000153 secs+0084 DATABASE... 'DI21PART'

+0094 ATRDLIS.... Function and Status Codes+0094 ATRVERB.... 'GHU ' ATRRC...... ' '

+0128 ATRDXV..... Segment Search Argument+0000 D7C1D9E3 D9D6D6E3 4DD7C1D9 E3D2C5E8 *PARTROOT(PARTKEY*+0010 40407ED4 D8C140E3 C5E2E340 D2C5E85D * =MQA TEST KEY)*

********************************* End of data *********************************




OMEGAMON ATF: DB2 calls

For each DB2 call, see:• Elapsed time• SQL call type • SQL statement number in DBRM

BROWSE JCH.INDEX Record 00427518 More: < >Command ===> Scroll ===> CSR


/ ---- ------------------------------------------------------ ----------------87 Generic ESS TranCode=MQATREQ1 Region=0001 SSID=DB3A +0.0081985600 Sign-on to ESAF Region=0001 SSID=DB3A +0.0085925600 Thread created for ESAF SSID=DB3A +0.00860987 Generic ESS TranCode=MQATREQ1 Region=0001 SSID=DB3A +0.00861282 DB2 OPEN SSID=DB3A STMT=12 PROGRAM=MQATPGM +0.00932182 DB2 FETCH SSID=DB3A STMT=13 ELAPSE=0.000910 +0.00975382 DB2 FETCH SSID=DB3A STMT=13 ELAPSE=0.000847 +0.01046882 DB2 FETCH SSID=DB3A STMT=13 ELAPSE=0.000415 +0.01080082 DB2 FETCH SSID=DB3A STMT=13 ELAPSE=0.000417 +0.01109082 DB2 FETCH SSID=DB3A STMT=13 ELAPSE=0.000314 +0.01141982 DB2 FETCH SSID=DB3A STMT=13 ELAPSE=0.000276 +0.01173582 DB2 FETCH SSID=DB3A STMT=13 ELAPSE=0.000198 +0.01205382 DB2 FETCH SSID=DB3A STMT=13 ELAPSE=0.000372 +0.01269682 DB2 FETCH SSID=DB3A STMT=13 ELAPSE=0.000516 +0.01298182 DB2 UPDATE TranCode=MQATREQ1 Region=0001 SSID=DB3A +0.0132980020 DB2 Unit of Recovery Control - Begin UR +0.0153190020 DB2 Update In-Place in a Data Page +0.01533582 DB2 CLOSE SSID=DB3A STMT=14 PROGRAM=MQATPGM +0.01567782 DB2 DELETE SSID=DB3A STMT=15 ELAPSE=0.000116 +0.0160000010 DB2 Savepoint +0.0160710020 DB2 Delete from a Data Page +0.01616782 DB2 ISRT SSID=DB3A STMT=16 ELAPSE=0.000219 +0.0164810020 DB2 Insert into a Data Page +0.016647

Also notice the DB2 log events (0020)merged in sequence with the other ATF and IMS log record events




OMEGAMON ATF: MQ calls

For each MQ call, see:• Elapsed time• MQ call type • Queue name



/ ---- ------------------------------------------------------ ----------------87 Generic ESS TranCode=MQATREQ1 Region=0001 SSID=CSQ6 +0.0390655600 Sign-on to ESAF Region=0001 SSID=CSQ6 +0.0392405600 Thread created for ESAF SSID=CSQ6 +0.03925687 Generic ESS TranCode=MQATREQ1 Region=0001 +0.03926088 MQ CONN SSID=CSQ6 +0.03947188 MQ OPEN SSID=CSQ6 QNAME=PROD_IN_QUEUE +0.03987488 MQ GET SSID=CSQ6 QNAME=PROD_IN_QUEUE +0.04032188 MQ GET SSID=CSQ6 QNAME=PROD_IN_QUEUE +0.075995 88 MQ GET SSID=CSQ6 QNAME=PROD_IN_QUEUE +0.10161888 MQ CLOS SSID=CSQ6 QNAME=PROD_IN_QUEUE +0.57202688 MQ OPEN SSID=CSQ6 QNAME=PROD_OUT_QUEUE +0.57236688 MQ PUT SSID=CSQ6 QNAME=PROD_OUT_QUEUE +0.57281788 MQ CLOS SSID=CSQ6 QNAME=PROD_OUT_QUEUE +0.57699888 MQ DISC SSID=CSQ6 QNAME=PROD_OUT_QUEUE +0.590434




Track and merge all types of logs

We have reached end of the transaction we are tracking.Observe all the syncpoint events in the IMS and DB2 logs, as well as the OMEGAMON ATF call trace, and end of transaction events:



/ ---- ------------------------------------------------------ ----------------05 DLI ISRT TranCode=MQATREQ1 Region=0001 +0.5908315600 Commit Prepare starting Region=0001 SSID=CSQ6 +0.59177887 Generic ESS TranCode=MQATREQ1 Region=0001 SSID=CSQ6 +0.59388287 Generic ESS TranCode=MQATREQ1 Region=0001 SSID=DB3A +0.5939570020 DB2 Unit of Recovery Control - End Commit Phase 1 +0.59413503 Output Message Response LTerm=FUNTRM07 +0.59690735 Output Message Enqueue LTerm=FUNTRM07 Region=0001 +0.59693937 Syncpoint Region=0001 +0.59697637 Syncpoint message transfer Region=0001 +0.59701333 Free Message +0.59705331 Communications GU LTerm=FUNTRM07 +0.59726987 Generic ESS TranCode=MQATREQ1 Region=0001 SSID=CSQ6 +0.59907536 Output Message Dequeue LTerm=FUNTRM07 +0.60191633 Free Message +0.6019805600 Commit Continue completed Region=0001 SSID=CSQ6 +0.60262387 Generic ESS TranCode=MQATREQ1 Region=0001 SSID=DB3A +0.60262605 DLI Detail TranCode=MQATREQ1 Region=0001 Func=ASRT +0.5917480020 DB2 Unit of Recovery Control - Begin Commit Phase 2 +0.6027110020 DB2 Unit of Recovery Control - End Commit Phase 2 +0.6044075600 Commit Continue completed Region=0001 SSID=DB3A +0.6052225612 End of Phase 2 Syncpoint Program=MQATPGM Region=0001 +0.60523407 Application Terminate TranCode=MQATREQ1 Region=0001 +0.605362F1 Transaction End TranCode=MQATREQ1 Region=0001 +0.60569904 Summary Completion TranCode=MQATREQ1 Region=0001 +0.605699

******************************** Bottom of Data *******************************




Batch job:

report/extract

request

JCL

Specifiedinput files

Generates& submits

SLDS (or OLDS)

Disk or tape:

IMS Log records

IMS Connect Extensions

journal data sets

IMS Connect records

IMS PA

ISPF dialog

IMS Monitor data sets

OMEGAMON

TRF Extractor data sets

IMS Monitor records

Report/extract

request

with input file

ddnames

Extracts

TransactionIndex

Reports

IMS Performance Analyzer




OMEGAMON TRF

� Analyzes OMEGAMON monitor-level instrumentation

� Transaction response time breakdown, CPU time, and other resource

usage statistics

� Full Function and Fast Path database DL/I call count and elapsed time

� DB2 database call count and elapsed time




OMEGAMON TRF

OMEGAMON TRF DLI Call Summary_____________________________

Func Call Total Average Minimum Maximum Calls per Calls perTrancode Database Code Count Elapsed Elapsed Elapsed Elapsed second minute________ ________ ____ ________ __________ __________ __________ __________ __________ __________BANKING CUSTOMER ISRT 3 0.101742 0.033914 0.003939 0.093401 0.00 0.04

REPL 1 0.001066 0.001066 0.001066 0.001066 0.00 0.01DLET 1 0.005595 0.005595 0.005595 0.005595 0.00 0.01GU 7 0.571528 0.081646 0.000915 0.557844 0.00 0.10GHU 3 0.004219 0.001406 0.001343 0.001520 0.00 0.04Total 15 0.684150 0.045610 0.000915 0.557844 0.00 0.23

ORDER ORDERS ISRT 3 0.023952 0.007984 0.001385 0.016799 0.00 0.04REPL 1 0.000120 0.000120 0.000120 0.000120 0.00 0.01DLET 1 0.000239 0.000239 0.000239 0.000239 0.00 0.01GU 5 0.024809 0.004961 0.001622 0.015286 0.00 0.07GHU 2 0.002255 0.001127 0.000727 0.001528 0.00 0.03Total 12 0.051375 0.004281 0.000120 0.016799 0.00 0.18




Reporting improvements

� Cold start analysis takes the IMS log and tell you what would be lost in the event

of a cold start

� Gap analysis identifies gaps in journal reporting

� Journal spill file support: report on IMS Connect transactions, for which event

records exist in multiple journals




Cold start analysis

� Analyzes what would happen after an emergency cold start of IMS at some point in time (for example, now or at end of log)

� Identifies what messages would be lost

� What in flight transactions with external subsystems be lost

� Helps for disaster recovery planning and executing a disaster recovery

� May help provide information on unprocessed input messages




Gap analysis

� Gap analysis identifies periods of time where log records are not being cut

� Can highlight an external system event that may have caused IMS to slow down

� Ability to set thresholds to reduce the number of “false positives”

� Can run across all systems in the IMSplex

� Can be used for IMS Connect Extensions journals




Forms: Distributions and Service Levels

– Ensure transactions are performing according to management-defined service levels– User-defined thresholds, for example - <0.1, 01 to 0.5, >0.5 seconds etc.– Report as either a percentage (of all transactions) or as a count

Response Time Distribution

Min Avg Max <0.01 <0.05 <0.10 <0.20 <0.50 >=0.50 >=0.50

Tran Total Total Total Total Total Total Total Total Total Total

Trancode Count IMS Time IMS Time IMS Time IMS Time IMS Time IMS Time IMS Time IMS Time IMS Time IMS Time

BALANCE 89 0.045362 0.119435 1.493757 1.12% 31.46% 85.39% 91.01% 93.26% 6.74% 6

LOGON 92 0.028291 0.158065 1.667653 1.09% 31.52% 72.83% 85.87% 93.48% 6.52% 6

ORDER 95 0.017040 0.117309 0.833115 0.00% 35.79% 80.00% 86.32% 94.74% 5.26% 5

PAY 936 0.004527 0.019000 0.358372 33.76% 94.87% 98.18% 99.47% 100.00% 0.00% 0

STOCK 98 0.025835 0.103145 0.812622 0.00% 29.59% 83.67% 89.80% 95.92% 4.08% 4

TRANSFER 78 0.015636 0.118776 0.765933 0.00% 44.87% 78.21% 80.77% 96.15% 3.85% 3

WITHDRAW 105 0.026213 0.110366 1.556585 0.00% 29.52% 75.24% 89.52% 96.19% 3.81% 4

Service Level dictates that 95% of transactions must have response time less than 0.5 seconds, then…

PAY, STOCK, TRANSFER, WITHDRAW do meet the required level of service – OK

BALANCE, LOGON, ORDER do not meet the required level of service – Fail




Forms: database updates and ESAF activity by transaction

IMS Tran CPU InputQ Process OutputQ Total

Start Trancode PST Time Time Time Time IMS Time . . .

09.49.26.679840 MQATREQ1 1 0.026658 0.000145 1.724738 0.000000 1.724883

10.37.00.753450 MQATREQ2 2 0.015126 0.000221 0.491174 0.000000 0.491395

10.37.41.829685 MQATREQ3 3 0.015126 0.000150 0.386636 0.000000 0.386786

10.38.09.060759 MQATREQ4 4 0.015126 0.000265 0.404939 0.000000 0.405204

Total IO DB IO VSAMRead VSAMWrit ESAFcall

Trancode . . . Count Time Count Count Count

MQATREQ1 7 0.000384 2 3 267

MQATREQ2 12 0.001034 4 7 57

MQATREQ3 16 0.001287 6 11 62

MQATREQ4 18 0.001564 9 16 71

Bad response time! What caused it?

Perhaps it was an external subsystem,but which one and what happened?




More information

� IBM DB2 and IMS Tools website:

http://www.ibm.com/software/data/db2imstools/

ims problem analyzer problem investigation cex update

Technology

zos ims

ims flood

new ims tools

ims tools performance

ims tuning specialists

ims problem investigator

ibm corporationibm corporation

information management