IMS Performance Pack -Philly UG Sept 2015

© 2013 IBM Corporation©2014 IBM Corporation

IBM® IMS Performance AnalyzerOverview

James MartinFUNDI Software<[email protected]>

Information Management for System z

1


Please note

2

IBM’s statements regarding its plans, directions, and intent are subject tochange or withdrawal without notice at IBM’s sole discretion. Informationregarding potential future products is intended to outline our generalproduct direction and it should not be relied on in making a purchasingdecision.

The information mentioned regarding potential future products is not acommitment, promise, or legal obligation to deliver any material, code orfunctionality. Information about potential future products may not beincorporated into any contract. The development, release, and timing ofany future features or functionality described for our products remains atour sole discretion.

Performance is based on measurements and projections using standardIBM benchmarks in a controlled environment. The actual throughput orperformance that any user will experience will vary depending upon manyfactors, including considerations such as the amount ofmultiprogramming in the user’s job stream, the I/O configuration, thestorage configuration, and the workload processed. Therefore, noassurance can be given that an individual user will achieve results similarto those stated here.

© 2013 IBM Corporation©2014 IBM Corporation©2014 IBM Corporation

Agenda

IMS Performance Analyzer overview

Version 4.2 features



3

© 2013 IBM Corporation©2014 IBM Corporation©2014 IBM Corporation4

IMS Performance Analyzer

IMS Performance Analyzer (IMS PA) is a tool that uses the IMSand related logs to create performance and throughput reports

IMS Performance Analyzer remains the premier tool for:

– Service Levels and capacity planning

– Response time analysis

– Monitoring enterprise-wide indicators that can adversely affect IMSperformance


IMS PA Highlights

Accepts input from the IMS Log, Monitor, Connect, and OMEGAMON TRF data

Delivers end-to-end transit analysis for all types of transaction workloads,including shared-queues, by merging sysplex log files

Delivers end-to-end IMS Connect and IMS Log reporting; providing a completepicture of the life-cycle of transactions as they pass through Connect and into IMS

Provides an ISPF dialog and batch commands to best manage reportingrequirements across your entire IMS enterprise

Offers DBRC Log selection for quick and easy log report requests

Report Forms allow you user defined templates for customized content

Comprehensive IMS monitor reporting including Fast Path

Measure usage and availability of databases, programs, regions, buffers andqueues (message and other internal queues)

User-defined performance thresholds allow you to set goals and report exceptions

A history of transaction performance can be maintained in Transaction HistoryFiles

Report critical performance information -- from high-level management summariesto detailed traces for in-depth analysis

Analyzes the impact of IMS Connect on transaction performance

5


IMS PA Highlights Input from IMS Log, Monitor, Connect, and OMEGAMON

– A Report Set defines a selection of reports, extracts and associatedoptions

– There are five types of Report Sets: LOG, MON, CEX, TRF, ATF

• Report Set corresponds to the type of input data it is designed toprocess

• Any number of Report Sets can be defined, but a separate batch job isrequired for each type of Report Set

• One batch job runs one Report Set or runs a selection of reports andextracts from one type of Report Set

• The reports and extracts in a Report Set, including multiple programtraces, are produced as a group from one pass of the input data sets,without sorting

– A Report Set can be run ad hoc or scheduled against different input eachtime

• Report Sets changes via ISPF affect the next run of the Report Set

– Optionally, a Log Report Set includes the specification of extract files,transaction index, and user-written record processors

• These are executed concurrently with IMS PA reports in the samepass of the log data set

7


IMS PA Highlights

Input from IMS Log, Monitor, Connect, and OMEGAMON TRF data

– IMS PA produces comprehensive sets of reports and extracts from IMS Log,Monitor, IMS Connect Extensions, and OMEGAMON TRF and ATF data sets

– The ISPF-based dialog is used to create and maintain your report and extractrequests in Report Sets of type LOG, MON, CEX, TRF, or ATF

– System and report interval options can be specified at run time

> Filtering of data can be defined by a date-time range or time slot, and SelectionCriteria to restrict reporting to only the objects of interest (such as particularprograms, databases, user IDs, LTERMs, and IMS subsystem IDs)

> Graphs and export files can be produced from log extracts by time interval

> Extracts of total transaction traffic or exception transactions (MSGQ or FastPath), CPU usage and database update activity can also be created for directimport by external programs such as DB2 or PC-based reporting tools

> ISPF also generates the JCL to run the reports

8


IMS PA Highlights

A Report Form is a user-defined template for the design of a report, andspecifies:

A list of fields to be reported, for example transaction code, user ID,response time, CPU time.

Summary options for grouping purposes. For example summarize bytransaction code or by transaction code within each 5 minute timeinterval.

Statistical functions including average, minimum, maximum, standarddeviation, peak percentile, total, and count. For example, report averageresponse time, 95th percentile response time or total number ofdatabase calls.

With Form-based reports and extracts you can:

– Print report output or view using SDSF or ISPF Outlist utility

– Export extract data sets to DB2 tables or PC spreadsheets

9


IMSPA TerminologyObject List

– An Object List enables values to be specified for objects (such asTRANCODE, LTERM, CLASS, USERID). Object Lists are specified inSelection Criteria in your reports and extracts. The input data is filteredbased on the specified values so that you restrict reporting to only thedata that you are interested in.

Expectation Set

– An Expectation Set contains a set of expectations that define'exceptional' results. These threshold values are used by theManagement Exception and Fast Path Transaction Exception reports tohighlight exceptions.

Control Datasets

– These dataset store the different customization set

Report Sets . . . . 'DNET089.IMSPA.RSET'

Report Forms . . . . 'DNET089.IMSPA.FORM'

Expectation Sets . . 'DNET089.IMSPA.EXPQ'

Object Lists . . . . 'DNET089.IMSPA.OBJL'

Distributions . . . 'DNET089.IMSPA.DIST'10


IMSPA TerminologyForms Based Reporting

– Report Form is a user-defined template for the design of a report, andspecifies fields to be reported, summary options for grouping purposesand statistical functions including average, minimum, maximum, etc.

IMS Transaction Index

– The IMS Transaction Index is a specialized extract file created by IMSPerformance Analyzer batch reporting. Each record in the indexrepresents an IMS transaction and contains cumulative informationfrom the IMS log about that transaction.

IMS Connect Transaction Index

– The IMS Connect Transaction Index is a specialized extract file createdby IMS Performance Analyzer batch reporting. Each record in theindex represents an IMS transaction and contains cumulativeinformation from the IMS Connect Extensions journal about that

transaction.

11


IMSPA Terminology

Object Lists

– An Object List enables values to be specified for objects (suchas TRANCODE, LTERM, CLASS, USERID). Object Lists arespecified in Selection Criteria in your reports and extracts. Theinput data is filtered based on the specified values so that yourestrict reporting to only the data that you are interested in.

Distributions

– Distributions define the attributes of distribution graphs that areprovided in some of the IMS PA reports such as the TransactionTransit Statistics log report and the Communications monitorreports.

12


Transaction index

IMSPerformanceAnalyzer

IMSProblemInvestigator

IMS PA batch job condensesall IMS log records forone IMS transaction intoone Transaction Index record

Save processing time by usingTransaction Index as inputto IMS PA instead of IMS log

Transaction Index contains performanceinformation (such as response time) derivedfrom IMS log fields, enabling more intelligentfiltering and analysis in IMS PI

IMS log

TransactionIndex

All the accumulated information from the IMS log about each transaction iscondensed into a single transaction index record (created by IMS PA).

Use the transaction index as input into:

IMS PA reporting - Instead of re-processing large SLDS log files

IMS PI analysis - To enable more intelligent problem detection


CA01 Transaction 05.45.31.117104

UTC=14.45.31.117097 Program=DBFSAMP1 Userid=DVP Region=0001

OrgUOWID=IBDF/C384D622EB529E61 IMSID=IBDF IMSRel=111

RecToken=IBDF/0000000100000001 CPU=0.000933 Process=0.276242

TotalTm=0.276242 RegTyp=BMP DBCalls=4 FPCalls=4

IMS Transaction Index

Specify exception criteria, such as long Processing times,to record only problematic transactions.

Transaction Index has improved diagnostic informationfrom the IMS log when available.

– X’56FA – Transaction Statistics Record

Use the Transaction Index as Input for Transit reporting.

– Significant performance increase over using SLDS.

1414


Sorting the IMS Transaction Undex//IMSPA JOB ,NOTIFY=&SYSUID

//*

//SORT EXEC PGM=SORT

//SORTIN DD DSN=JCH.WORKSHOP.INDEX,DISP=SHR

//SORTOUT DD DSN=JCH.WORKSHOP.INDEX.SORTED,

// DISP=(NEW,CATLG),UNIT=SYSDA,SPACE=(TRK,(1,1),RLSE)

//SORTWK01 DD DISP=(NEW,DELETE),UNIT=SYSDA,SPACE=(CYL,(10,10))




//SYSOUT DD SYSOUT=*

//SYSIN DD *

SORT FIELDS=(265,26,CH,A)

/*

15


Transaction index – locate a problem transaction

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 ********************************

1. Locate all MQATREQ1transactions withprocessing time > 1 sec

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

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

/ --- ------------------------------------------------------ ----------------TX 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

2. Track the transaction to view its lifecycle in the IMS log:


56FA Transaction Accounting Statistics Records

Starting with IMS V10, support for the new performance metrics in thetype 56FA transaction-level accounting record became available forenhanced reporting in IMS Performance Analyzer. Type 56FAtransaction accounting record contains similar data to the X'07' recordbut at transaction, rather than schedule level, and provides:

- More accurate and reliable statistics for CPU time, DLI call, database I/O and ESAF usage, and isno longer an approximation derived from the type 07 application termination records

- Always available even in a WFI environment (where the type 07 record is not available)- New OSAM and VSAM read/write counts- New database I/O and locking elapsed times- New ESAF (DB2, MQ) call activity

x’56FA’ log record is required for increased reporting accuracy butnot required for Transaction Index creation

17


X’56FA’ Activation

Collection of the 56FA Accounting statistics records can be activated intwo ways:

– Globally: Specify in PROCLIB member DFSDFxxx:

<SECTION=DIAGNOSTICS_STATISTICS>TRANSTAT=Y

– Selectively by Transaction: Using the type 2 command:

UPDATE TRAN NAME(TRANxx) SET(TRANSTAT(Y))

18


CA20 Connect Transaction 0000000000000001

TranCode=PRT2 Userid=CEX2 IMSID=ICDH ClientID=CLNAC02 Port=3801

LogToken=C8962E0E2AF33103 SSN=0689 Response=0.041073 CM=1 SYNCLEVEL=1

TOV=38_MIN Socket=Tran

IMS Connect Transaction Index

IMS Connect Transaction Index:

– Contains a record for each IMS Connect transaction recorded in theIMS Connect Extensions for z/OS journal, and includes all thecumulative information from the journal about that transaction.

– IMS Problem Investigator for z/OS uses the IMS ConnectTransaction Index, either on its own or merged with the associatedIMS Connect Extensions journals and IMS log files, to provideimproved levels of problem detection.

1919


Sorting the IMS Connect Transaction Index

//IMSPA JOB ,NOTIFY=&SYSUID//*//SORT EXEC PGM=SORT//SORTIN DD DSN=IMS.CONNECT.INDEX,DISP=SHR//SORTOUT DD DSN=IMS.CONNECT.INDEX.SORTED,// DISP=(NEW,CATLG),UNIT=SYSDA,SPACE=(CYL,(20,50),RLSE)//SYSOUT DD SYSOUT=*//SYSIN DD *SORT FIELDS=(96,26,CH,A)

/*

20


Report Sets IMS Performance Analyzer provides a comprehensive suite of reports

to help users manage transaction performance and monitor resourceutilization in IMS TM and DB systems.

A Report Set can be a single report/extract, or a set of reports/extractsfor processing.

– Run Multiple reports in a single in a single pass of the input data files.

• Report Sets that process IMS Log data (OLDS or SLDS) are type LOG.

• Report Sets that process IMS Monitor or DB Monitor data are type MON.

• Report Sets that process IMS Connect data, or combined IMS and IMS Connectdata are type CEX.

– Requires IMS Connect Extensions

• Report Sets that process OMEGAMON ATF journal input are type ATF.

– The different types of Report Set (LOG, MON, CEX, and ATF) can coexist inthe same Report Sets data set, but are specified and run separately.

21


IMS Log Reports

Transaction Transit Reports

Transaction Transit Reports (Form-based)

Resource Usage & Availability Reports

Fast Path Transit Reports

Fast Path Resource Usage Reports

Trace Reports

22


IMS Monitor Reports

Region Activity Summary Reports

Region Activity Analysis Reports

System Analysis Reports

Program Analysis Reports

Resource Usage Reports

Fast Path Analysis Reports

Monitor Data Analysis Report

23


IMS Connect Reports – via IMS Connect Extensions

• Transaction Transit Reports

• Transaction Transit Reports (Form-based)

• Resource Usage Reports

• Trace Reports

24


Omegamon for IMS ATF Reports

• Transaction Transit Reports

• Trace Reports

• Extracts

25


Version 4.2 Features

26


Form-based reporting: Improved coverage

1.Integrated MPP and IFP support – all transaction types nowsupported

See your entire transaction workload in a single report

2.FP database support – for MPP and IFP transactions alike

DEDB calls, Area I/O, FP buffer usage and contention, VSO

3.End-to-end MSC

Merge the front and back end logs to get the complete responsetime breakdown

4.CICS DBCTL - IMS V11 APAR PM24076

CICS transaction id and task number in an IMS report

Tie it back to the CICS PA report


IMSPA Form-based transit reporting evolution

28

Part 1 of 2

1. Customizable reporting; complete coverage of all transaction workload types –breakdown of response time and resource usage

2. Three report output formats – Printed, CSV, DB2

3. Flexible summarization, including distributions or service levels – "what percentageof transactions had a response time greater than 1 second?”

4. Transaction Index; for use in IMS Problem Investigator

5. Combined IMS and Connect (via CEX) transaction analysis

6. CICS-DBCTL

• Improved identification of CICS transaction in the IMS log – tie the transaction back to the CICSPerformance Analyzer report

• DBCTL thread availability and scheduling delay

7. Syncpoint time breakdown

• PH1, PH2, PH1+PH2

• OTHREAD – how long did the (asynchronous) OTHREAD process take to update the FP areas?

8. Improved BMP analysis – syncpoint/checkpoint activity

9. Individual database update activity. Which transactions update which databases?

10. External subsystem activity. Which transactions use DB2, and for update or read-only?


Database and ESAF cross-reference

List of transactions with DB and XREF usage

IMS Tran CPU InputQ Process OutputQ Total DB Call DB IO DB Lock Database ESAF

Trancode Start Time Time Time Time IMS Time Count Time Time Name Name

NEWORDER 09.56.21.101795 0.006942 0.067237 0.022835 0.000000 0.090072 17 0.003110 0.000000 ORDERS DB2P

INVENTRY

CUSTOMER

WITHDRAW 09.56.23.738099 0.013405 0.000340 0.245464 0.000000 0.245804 14 0.000491 0.000000 ACCOUNT DB2P

CUSTOMER MQP1

SUPPLIER 09.56.49.995508 0.005473 0.000539 0.009268 0.000124 0.009931 10 0.000386 0.000000 SUPPLIER DB2P

INVENTRY MQP1

AUDIT

29

Form-based reporting enhancements, focusing on:

Databases updated by the transaction

External subsystems used by the transaction

List of transactions, with their database and ESAF activity

Part 2 of 2


Synchronous callout – IMSPA report

30

The sync callout response time is alarge percentage of the overallprocessing time: indicative of adelay

Transactions w/ synch-callout

SUMM0001 Data from 10.18.37 19Apr2011 to 10.21.06 19Apr2011

Avg Avg Avg Avg Avg Avg Avg

Tran CPU InputQ Process SyncCout Total SyncCout SyncCout

Trancode Count Time Time Time RespTime IMS Time ACK Cnt NAK Cnt

MYORDER 57760 0.0023 0.0052 0.5673 0.4723 0.5725 1 0

Part 1 of 2


Synchronous callout – IMSPI tracking

31

Part 2 of 2

BROWSE IPI000.QADATA.JASDEEP2.VB10.IM01001 Record 00000057 More: < >

Command ===> Scroll ===> PAGE

Forwards / Backwards . . HH.MM.SS.THMIJU Time of Day . . HH.MM.SS.THMIJU

Code Description Date 2011-04-20 Wednesday Time (Relative)

/ ---- Search limit reached (+5000) ------------------------- ----------------

01 Input Message TranCode=SMQLG 01.19.00.003853

35 Input Message Enqueue TranCode=SMQLG +0.000001

31 DLI GU TranCode=SMQLG Region=0006 +0.000057

6701 YOUT Sync callout message sent +0.000125

6701 YACK Received ACK +0.000618

6701 YRSP Sync callout response received +0.201386

03 Output Message Response LTerm=OTM00001 +0.201420

35 Output Message Enqueue LTerm=OTM00001 Region=0006 +0.201422

37 Syncpoint Region=0006 +0.201424

37 Syncpoint message transfer Region=0006 +0.201425

33 Free Message +0.201428

5612 End of Phase 2 Syncpoint Program=PSBLG Region=0006 +0.201431

31 Communications GU LTerm=OTM00001 +0.201440

36 Output Message Dequeue LTerm=OTM00001 +0.203894

33 Free Message +0.203895

07 Application Terminate TranCode=SMQLG Region=0006 +0.220357

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

Delay due tosync callout


Program Switch: Transaction list

32

Part 1 of 2

Transaction BANK0001 originated from lterm NEWYORK at 14.58.02.023922

It switched to trancode BANK0010

Trancode BANK0010 then switched to BANK0011

Four (4) further switches to Trancode BANK0015 completed the sequence

The overall transaction response time is always reported against theoriginating transaction – 4.467306 seconds – from when the originatingtransaction arrived on the message queue to when a response was sent backto the terminal

The last transaction in the sequence responded back to the terminal – you cantell because it has an output queue time

Notice the long switch times for the last 2 transactions – this contributed toalmost 0.5 seconds of the response time


Program Switch: Summary

33

Part 2 of 2


LOGINFO – IMS log information reportCode Count MCNT Recs/Sec Avg len Max Len Byte/Sec MB %

01 IN 21,342 0 1,725 3,240 96 36.8 6.3 IMS Message

INPUT 15,072 0 1,727 3,240 67 26.0 4.5 Input message

MSC FE 134 0 1,032 1,912 0 0.1 0.0 MSC front end

MSC BE 3,418 0 1,193 3,240 10 4.0 0.7 MSC back end

CONTINUE 2,718 0 2,417 3,240 17 6.5 1.1 Continuation record

03 OUT 15,256 0 2,081 3,240 82 31.7 5.4 IMS Message

OUTPUT 14,602 0 2,138 3,240 81 31.2 5.3 Output message

MSC BE 137 0 1,749 2,672 0 0.2 0.0 MSC back end

MSG SWI 517 0 551 800 0 0.2 0.0 Message switch

07 41,039 50,985 0 456 456 48 18.7 3.2 Program schedule end

MPP 32,753 34,446 0 456 456 38 14.9 2.6 MPP

QUICK 8,190 16,463 0 456 456 9 3.7 0.6 MPP quick reschedule

FALSE 12 0 0 456 456 0 0.0 0.0 MPP false schedule

BMP 15 0 0 456 456 0 0.0 0.0 BMP

ABEND 69 76 0 456 456 0 0.0 0.0 Abended transaction

08 41,040 0 148 148 15 6.0 1.0 Program schedule start

MPP 32,835 0 148 148 12 4.8 0.8 MPP

QUICK 8,190 0 148 148 3 1.2 0.2 MPP quick reschedule

BMP 15 0 148 148 0 0.0 0.0 BMP

31 76,983 0 223 832 44 17.2 2.9 GU from the Message Queue

DLI 61,447 0 115 126 18 7.0 1.2 DLI (application input)

COMMS 15,536 0 652 832 26 10.1 1.7 Communications (output)

4001 1 0 1,516 1,516 0 0.0 0.0 Checkpoint begin

50 259,638 0 340 3,964 230 88.4 15.1 Database Update

Total 1,366,218 3 427 4,140 1,524 584.6 100.0

34

Both PA and PI alwaysproduce this report; useful toprofile your IMS log


IMS PA: Useful new reports in version 4.2

Cold start analysis

Analyzes what would happen after an emergency cold start of IMS at somepoint 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


OMEGAMON for IMS ATF with IF3 support

Transaction . . . . MPX00110 Date-Time . . . . . 2011-07-09-02.51.26.382999

Jobname . . . . . . IMS9YMS1 Region ID . . . . . 002 Region Type . . . . MPP

Elapsed Time . . . . 2.200601 Total CPU Time . . . 0.007901 Dependent Region CPU 0.003299

DLI CPU Time . . . . 0.005478 DB2 CPU Time . . . . 0.000000 MQ CPU Time . . . . 0.000000

Control Region CPU . 0.000000 DLISAS Region CPU . 0.004601 Other Regions CPU . 0.000000

Elapsed time DL/I . 0.666187 Elapsed time DB2 . . 0.000000 Elapsed time MQ . . 0.000000

Time Relative Duration

hh.mm.ss.thmiju ss.thmiju ss.thmiju CPU Time Description Resources FC SC

_______________ ___________ _________ _________ ____________________ _________________ ____ __

02.51.26.382999 0 2.200601 0.000000 SUMMARY COMPLETION

02.51.27.861013 + 1.478013 0.000011 0.000008 DLI CALL (TM) I/O PCB GU

02.51.27.861041 + 1.478041 0.528531 0.004565 DLI CALL (DB) BD$HDMO0 BD#AASEG GU

02.51.28.389595 + 2.006595 0.042433 0.000423 DLI CALL (DB) BC$HDLO0 BC#AASEG GHU

02.51.28.432044 + 2.049044 0.001128 0.000122 DLI CALL (DB) BC$HDLO0 BC#BASEG GHNP

02.51.28.433182 + 2.050183 0.093938 0.000215 DLI CALL (DB) BC$HDLO0 BC#BASEG REPL





02.51.28.527371 + 2.144371 0.000015 0.000015 DLI CALL (DB) BC$HDLO0 BC#BASEG GHNP36

Elapsed and CPU times per IMS Region and ExternalSubsystem

Elapsed and CPU timesper DLI and ESAF call

Alsoavailablefor TRF


IMSPA useability enhancements1. Support for incorrect or mixed IMS versions,

useful for mixed version shared queues andcontinuity during release migration:IPI0331I System IMSP changed from version 10 to 12

2. ITKB enabled:

Write reports directly to the ITKB repository

View the reports from the IMS Tools Admin Console WUI

3. Transaction Index exceptions by processingtime and ABEND – to reduce the extract toproblem trans only

4. Improved documentation; including:

Form field explanations

More scenarios and examples

Enabled for IBM Infocenter37



38


IMS Performance AnalyzerTransaction Total Time

________________________________InputQ IMS Tran Process CPU CPU Svc IM

Trancode Userid Program Time Start Time Time UnitsCEXTCONV IPI2 CEXTPGM 0.005 12.04.23.008 0.036 0.008 175CEXTCONV IPI2 CEXTPGM 0.003 12.04.24.056 0.023 0.007 152CEXTCONV IPI2 CEXTPGM 0.003 12.04.25.086 0.024 0.008 184

CPU Reported as Service Units

APAR PM77790

New field CPUSU available for Forms based Transit reports

– Normalization of CPU time reporting

– Get direct performance comparisons between older and newerCPU’s when considering upgrades.

39


ATF - Record TraceSpecify report options.

Reports Required: Report Output DDnames:/ Trace Overview TRACE001

Trace Detail TRACE002Trace Detail (Expanded) TRACE003

Report Options:/ Include Monitor events

Selection Criteria:Object Type Inc/Exc Object + List Validation Warning

Transaction CodeUser IDIMS Subsystem IDProgram

OMEGAMON Trace Report Enhancement

Monitor report option – APAR PM83151

– Provides additional transaction characteristics

– Provides reporting detail for DB2 SQL and WebSphere MQ events

40


Alternate IMS processing ID identification

APAR (v4.2) PM73151 – (v4.3) PM74169

Available via option 3(Report Sets) - Log GlobalOptions

– PA can now source IMS processing ID in 2 ways:

• From the Log input DD - Lxxxxunn where xxxx is the IMSID

• Derived from the IMS Log Records – field TPCPOSSN via 56records

41


Start 01Jun2011 12:04:23:01 IMS Performance AnalyzerDatabase Update Activity-ICDE______________________________

5050Database Program Proc Total Updates ISRT DLET REPL________ ________ ____ _________ ________ ________ ________ ________ ____

DI21PART APPL 575 DLI 575 179 274 122I/O 421 135 0 286

B/O 65 DLI 65 26 26 13I/O 52 0 0 52

Format Option(2) – Database Update Activity report

APAR PM68240

Get a much more detailed look at your database updateactivity

42


CEXGARPT - Gap AnalysisCommand ===>

Specify report options. ————— Report Interval ——————YYYY/MM/DD HH:MM:SS:TH

Report Output DDname GAPS FromTo

Processing Options:Gap Threshold . . . 1.500000 seconds (s.thmiju)

IMS Connect Gap Analysis Report

Quickly identify potential performance issues by locatingperiods of time when log records are not being written

– Requires IMS Connect Extensions archive journals

User customizable Gap threshold lets you choose whatan “acceptable” gap really is.

43


LOGINFO operand

APAR PM68240

Use IMSPALOG LOGINFO batch command togenerate Log Info report without Running a report set.

44

Code Count MCNT Recs/Sec Avg len Max Len Byte/Sec MB %

01 IN 21,342 0 1,725 3,240 96 36.8 6.3 IMS Message





03 OUT 15,256 0 2,081 3,240 82 31.7 5.4 IMS Message





MPP 32,753 34,446 0 456 456 38 14.9 2.6 MPP



BMP 15 0 0 456 456 0 0.0 0.0 BMP



MPP 32,835 0 148 148 12 4.8 0.8 MPP



Additional Updates

APAR PM74169

– IMS Version 13 Support

– OMEGAMON IF3 support

45


Support Improvements

IMS support

– Support for IMS Versions 13 and 14

Inflight transaction support for IMS Log reports

– Transaction information that was previously incomplete due toa log switch is now complete

Region PST increased from 3 to 4 bytes

– Region PST field size increased due to an increase in themaximum partition specification table (MAXPST) limit to 4095

47


Form-based reporting enhancements

BMP treatment option

– New option to report each BMP syncpoint interval as asingle transaction

Shared queues option

– New option to only report transactions that wereprocessed on subsystems who logs were input

Program switches option

– New option to either report all transactions independently,or to group transactions associated with a program switchsequence

48

1 of 2


Form-based reporting enhancements

Additional reporting of CPU time as service units

– The service unit normalizes the reporting of CPU time toallow for performance comparisons

New value in QTYPE form field

– Form-field QTYPE has a new value, LOCALF, thatindicates the shared queue transaction was processed‘local-first’

New region occupancy form field

– Form field “REGOCCUP” reports the elapsed time thetransaction occupies in a message region

49

2 of 2


Start 01Jun2011 12:04:23:01 IMS Performance AnalyzerDatabase Update Activity-ICDE_____________________________

5050Database Program Proc Total Updates ISRT DLET REPL________ ________ ____ _________ ________ ________ ________ ________ ___

DI21PART CEXSPGM APPL 152 DLI 152 38 76 38I/O 114 38 0 76

CEXSPGM B/O 10 DLI 10 4 4 2I/O 8 0 0 8

CEXTPGM APPL 317 DLI 317 80 158 79I/O 238 80 0 158

CEXTPGM B/O 55 DLI 55 22 22 11I/O 44 0 0 44

DFSSAM04 APPL 85 DLI 85 55 30 0I/O 53 11 0 42

MQDTPGM APPL 21 DLI 21 6 10 5I/O 16 6 0 10

*Total* APPL 575 DLI 575 179 274 122I/O 421 135 0 286

*Total* B/O 65 DLI 65 26 26 13I/O 52 0 0 52

Log report enhancements

FORMAT2 option for Database Update Activity reports

– Reports can be generated with the more concise FORMAT2 option

50

1 of 6



Alternate IMS processing ID identification available viaoption 3(Report Sets) - Log Global Options

– PA can now source IMS processing ID in 2 ways:

1. From the Log input DD - Lxxxxunn where xxxx is the IMSID

2. Derived from the IMS Log Records – field TPCPOSSN via 56records

Monitor report enhancement

– Monitor report ALTSCHED global option is improved to countactual schedules only, and provide a more accurate picture of thetransactions per schedule ratio in pseudo-WFI environments

51

2 of 6


ATF - Record TraceSpecify report options.

Reports Required: Report Output DDnames:/ Trace Overview TRACE001

Trace Detail TRACE002Trace Detail (Expanded) TRACE003

Report Options:/ Include Monitor events

Selection Criteria:Object Type Inc/Exc Object + List Validation Warning

Transaction CodeUser IDIMS Subsystem IDProgram

52


OMEGAMON ATF Trace Report Enhancement

– Provides additional transaction characteristics

– Provides reporting detail for DB2 SQL and WebSphere MQ events

3 of 6


CEXGARPT - Gap AnalysisCommand ===>

Specify report options. ————— Report Interval ——————YYYY/MM/DD HH:MM:SS:TH

Report Output DDname GAPS FromTo

Processing Options:Gap Threshold . . . 1.500000 seconds (s.thmiju)

53


Quickly identify potential performance issues by locatingperiods of time when log records are not being written

– Requires IMS Connect Extensions archive journals

User customizable Gap threshold lets you choose whatan “acceptable” gap really is.

IMS Connect Gap Analysis Report

4 of 6



LOGINFO operand

– Use IMSPALOG LOGINFO batch command to generate LogInfo report without Running a report set.

Code Count MCNT Recs/Sec Avg len Max Len Byte/Sec MB %

01 IN 21,342 0 1,725 3,240 96 36.8 6.3 IMS Message





03 OUT 15,256 0 2,081 3,240 82 31.7 5.4 IMS Message





MPP 32,753 34,446 0 456 456 38 14.9 2.6 MPP



BMP 15 0 0 456 456 0 0.0 0.0 BMP



MPP 32,835 0 148 148 12 4.8 0.8 MPP


5 of 6



Gap Analysis Report

– New option to ignore type x’6D’ surveillance records that canmask periods of system inactivity

Fast Path Region Occupancy Report

– Exploits the new type x’5904’ record to provide a clearerbreakdown of occupied versus idle time

Internal Resource Usage (IRUR) Report

– Enhanced to support the new statistics provided by IMS versions12, 13 and 14

6 of 6


More Information

IMS Performance Solution Pack: Knowledge Centerhttp://www-01.ibm.com/support/knowledgecenter/SSS8SV/welcome

James MartinIBM

[email protected]

Jim MartinFundi Software

[email protected]

56

IMS Performance Pack -Philly UG Sept 2015

Technology

Transcript of IMS Performance Pack -Philly UG Sept 2015