Part 1 - CA Technologies

CA Datacom Education Workshop - 

Part 1: What’s Inside the CA 

Datacom Performance Monitoring 

Toolbox

Next Gen Mainframe 

MD700SN/EC150ENA 

CA Datacom Education 

Workshop - Part 1: What’s Inside 

the CA Datacom Performance 

Monitoring Toolbox 

Mike Gowen, IBM GTS Services Delivery 

Kevin Shuma, CA

abstract 

This is part one of a two-part education workshop covering advanced topics. In 

part one we look at what's in the CA Datacom performance tuning toolbox. With 

organizations highly focused on business services functionality to meet their 

rapidly changing needs, a critical requirement is making sure the application 

performs well and meets service levels for internal and external users. In this 

workshop, Kevin Shuma, CA Datacom® VP of Software Engineering, and Mike 

Gowen from the Datacom team at IBM Global Technology Services, talk about the 

performance monitoring tools you need to watch and manage CA Datacom 

performance and how they differ or work together. 

3 

Copyright © 2011 CA. All rights reserved. All trademarks, trade names, service marks and logos referenced herein belong 

to their respective companies. CA confidential and proprietary. No unauthorized copying or distribution permitted.

agenda 

• What’s in the toolbox 

• Overview of CA SYSVIEW for CA Datacom 

• The new tools in the “box” with version 12.0 

4 



what’s in the toolbox 

• The “hand” tools 

• The “power” tools 

• The new tools in the “box” with 

version 12.0 

5 



the “hand” tools 

• Well known 

• Still work and provide value 

• Usually requires manual manipulation to 

accumulate information 

• Includes: 

− Printed PXX Summary report 

− MUF EOJ Report 

− The CXX report 

6 



printed PXX Summary report 

• DBUTLTY REPORT AREA=PXX function 

• The most used “tool” 

• Pro’s 

− Most folks know it, and know how to use it 

− Provides a lot of good information 

− Can be “created” as part of the standard MUF job 

− Can be produced “on demand” 

• Con’s 

− Printed format 

− Typically reviewed with a manual effort 

− Formats can change release to release (affects automation) 

− Very hard to combine data from one report with another 

− Has been superseded by several newer tools 

• Recommendation – set MUF to print PXX at EOJ 

7 



printed PXX Summary report (cont’d) 

Option to discuss in detail in part II 

8 



MUF EOJ report 

• Produced automatically at MUF EOJ 

• Will be lost if MUF abends 

• Prints to SYSPRINT 

• Pro’s 

− Most folks know it, and know how to use it 

− Provides information not on PXX 

• Con’s 

− Can not be generated on demand 

− Printed format, typically reviewed with a manual effort 


− Hard to combine data from one report with another 


• Recommendation – save output printed at MUF EOJ 

9 



MUF EOJ report (cont’d) 

Date: 10/27/2011 ******************************************************************************** Page: 3 

* CA Datacom/DB * 

Time: 15.39.54 * Multi-User Facility * Release: 12 

* Copyright . 2009 CA. All rights reserved. * SP0 

******************************************************************************** 

M R D F SUMMARY INFORMATION 

VIRTUAL COVERED COVERED 

AREA USE SIZE BLOCKS SPACE MRDF READS MRDF WRITES 1ST/ACT READS NON-1ST READS PERCENT 

IXX00006 VIRTUAL 250M 64,000 64-BIT 2 0 USED 0 

IXX00017 VIRTUAL 40K 10 64-BIT 1 0 USED 10 

TTM00017 VIRTUAL 32M 8,190 64-BIT 2 1 USED 0 

Date: 10/27/2011 ******************************************************************************** Page: 4 




******************************************************************************** 

ACCOUNTING SUMMARY INFORMATION 

TABLE NAME: A90 DATA BASE: 5 

REQUESTS PROCESSED: 2,270,380 EXCPS: 24 

LOCATES: 55 ADDS: 55 UPDATES: 6,933 

ENTRY UNAVAILABLE: 0 EXCLUSIVE CONTROL CONFLICTS: 0 SKIPPED DUE TO EXCLUSIVE: 0 

CORE SIZE: 101,376 NUMBER OF ENTRIES: 1,079 ENTRIES RECLAIMED: 6,933 

LOCATES INITIATED: 7 SPILLS INITIATED TO AXXTHLD: 454 INTERNALLY INITIATED SPILLS: 0 


REQUESTS PROCESSED: 493,499 EXCPS: 5 

LOCATES: 28 ADDS: 28 UPDATES: 430 


CORE SIZE: 101,376 NUMBER OF ENTRIES: 1,075 ENTRIES RECLAIMED: 430 


. 

. 

. 

10 



MUF EOJ report (cont’d) 

Date: 10/27/2011 ******************************************************************************** Page: 6 




******************************************************************************** 

XCF SUMMARY INFORMATION 

JOB/SYS NAME GROUP TOTAL JOBS TOTAL REQUESTS 

* QA10 0 0 

* QA11 0 0 

* QA12 14 2,192,985 

BUFFER SIZE IB-REQUESTS OB-REQUESTS 

1K 2,058,534 1,446,655 

2K 134,451 512,739 

5K 233,584 

6K 7 

Date: 10/27/2011 ******************************************************************************** Page: 7 




******************************************************************************** 

TCB/SRB USE SUMMARY INFORMATION 

ITEM PROGRAM USED COUNT CPU TIME POSTED COUNT I/O COUNT 

1 DBMUFPR 773 000:00:00.55 940 696 

2 *SRB-SMP 2,697,805 000:01:06.97 2,691,714 0 

3 *SRB-SMP 413 000:00:00.01 542 0 

4 *SRB-SMP 0 000:00:00.00 0 0 

7 DBMSBPR 4,954 000:00:00.46 1 0 

8 DBOCSPR 23 000:00:00.10 48 0 

9 DBOCSPR 1 000:00:00.00 3 0 

10 DBOC2PR 51 000:00:00.05 52 0 

. 

11 



printed CXX report 

• DBUTLTY REPORT AREA=CXX function 

• Primarily provides physical database information 

• Pros 

− Provides some tuning information 

• Con’s 

− Data printed from DASD may be “old” – do STATS first 

− Printed format 

− Typically reviewed with a manual effort 



12 



CXX report (cont’d) 

INDEX INFORMATION - IXX 

DEVICE TYPE - 3390 DYNAMIC EXTEND - YES 

BLOCK LENGTH - 4,096 DYN.EXT.TRACKS - 20 

LEVELS - 2 OLDEP - YES 

BLOCKS/TRACK - 12 CXXMAINT LINK - YES 

BLOCKS IN USE - 4,605 

BLOCKS UNUSED - 13,395 

TOTAL BLOCKS - 18,000 

TOTAL TRACKS - 1,500 

PERCENT FULL - 25 

. 

. 

TABLE NAME - AGR 

AREA NAME - DD1 

OCCURRENCE - AGGREGATE P008 

OCCURRENCE - DATA-DICT-AREA-1 P004 

TABLE ID - 17 AREA SQLNAME - DATA_DICT_AREA_1 

RECORD LENGTH - 809 / 821 BLOCK LENGTH - 4,096 SLACK - 0 

RECORDS IN TABLE - 1,150 OVERFLOWS IN AREA - 53,258 

LENGTH OF KEY/ELEMENTS - 1,040 BLOCKS IN USE - 1,754 

NUMBER OF KEYS - 8 BLOCKS UNUSED - 23,446 

NUMBER OF ELEMENTS - 3 TOTAL BLOCKS - 25,200 CXXMAINT LINK - YES 

CHANGE MASTER KEY - YES TOTAL TRACKS - 2,100 DYNAMIC EXTEND - YES 

DUPLICATE MASTER KEY - YES PERCENT FULL - 6 DYN.EXT.TRACKS - 10 

RECOVER - YES DEVICE TYPE - 3390 

LOGGING - YES BLOCKS/TRACK - 12 

PIPELINE - YES DSOP MODE - RANDOM 

DB COMPRESSION - YES TABLE LOADED - YES, DATE-10/14/2011, TIME-18.54.52 

USER COMPRESSION - NO 

INDEX LOADED - YES 

CLUSTER KEY ID - 0 DATADICTIONARY BASE - 2 

CLUSTER KEY LENGTH - 0 DATA BASE ID CHANGE - NO 

DEFINITION POSTED VIA - LOAD FROM BACKUP 

AUTHID - SYSADM SQL-INTENT - R 

TABLE SQLNAME - AGGREGATE UNIQUE ROW IDENTIFIERS (URI) - 312,330 

DOMAIN CONSTRAINT - NO TABLE BEING REFERENCED - NO 

DL1-T CONSTRAINT - NO TABLE REFERENCING - NO 

TABLE CONSTRAINED - NO 

ALL REFERENCING IN THIS BASE - YES 

CURRENT CHECK PENDING - LOAD SET - NO HISTORY CHECK PENDING - LOAD SET - NO 

RELATED TABLE - NO RELATED TABLE - NO 

FORWARD RECOVERY - NO 

FORWARD RECOVERY - NO 

TRIGGER(S) - NO FORCED OFF - NO 

CURRENT ROW(S) VIOLATE CONSTRAINT(S) - NO 

HISTORY ROW(S) VIOLATE CONSTRAINT(S) - NO 

DATA SET NAME - DCMQA.QAMUF4.DD1002 

DATA DTF/DDNAME - DD1002 

13 



the “power” tools 

• May require some set-up 

• Can be tailored for your use 

• More flexibility in use 

• Includes: 

− Accounting Facility 

− Dynamic System Tables 

− CA SYSVIEW for CA Datacom 

DBA 

14 



the accounting facility 

• Built-in CA Datacom facility 

• Activated and tailored (by the user) on each MUF 

• Provides a simple and highly efficient way to capture 

“user-tailored” statistics about processing 

• Has a pre-defined set of statistics that can be collected 

• Utilizes a CA Datacom database/table(s) to store the 

collected statistics 

• Once collected the user is responsible for reporting, 

analyzing, and purging the collected data 

15 



the accounting facility (cont’d) 

• The Accounting Facility is NOT 

− A true ACCOUNTANTS tool 

• Only collects certain MUF information 

• Does not collect every cost 

• Could be used as a “usage”/”allocation” tool 

− A replacement for CXX reports, PXX reports or DSTs 

− A place to store non-Accounting Facility data 

− A “zero” overhead tool 

16 




• The Accounting Facility is 

− Very flexible 

• Allows 100 different collection tables 

• Allows the user to select level of granularity of collection in each table 

– One row per key value 

• Allows the user to select the “data” columns to be collected 

– All data from requests matching criteria (key value) is merged into one row 

• Data collection can be stopped and started as needed 

• Accounting definitions can be added, deleted, updated with stopping MUF 

− Persistent 

• Data collected by accounting is stored in Datacom tables 

• Data is spilled (committed) periodically as determined by user 

• User must delete unwanted or unneeded data 

17 




• The Accounting Facility is 

− Sharable 

• Accounting definitions and data can be moved from MUF to MUF 

like any other CA Datacom 

− Accessible 

• Data collected by accounting is stored in Datacom tables 

• Accessible to DQ, DR, SQL, Ideal, COBOL, etc. 

− Updatable 

• Accounting columns can be updated – not recommended 

• Accounting tables can have “user columns” which can be 

updated 

18 




• 38 Key-Type Fields (Identifying columns) 

− Provide information that can be used to identify the criteria for “collection” 

• 19 Incremental Fields (Collection columns) 

− Cannot be selected for inclusion in the accounting table key 

− When selected for inclusion in the accounting table will have the 

“accumulated” data value of all requests processed for this key value 

• 3 Non-Incremental Fields (Not Key available) 

− Provide information that can be included in the data portion 

− When selected for inclusion in the accounting table will have the data value 

of the last request 


19 



Dynamic Systems Tables (DST) 

• Introduced in release 10 

• Tell you almost everything you could want to know 

about MUF 

• Continue to change with every release 

• In Version 12.0 

Directory (CXX) MUF Related SQL specific 

12 tables 36 tables 10 tables 

20 



Dynamic Systems Tables (cont’d) 

• Easy to turn on 

− MUF Parameter SYSTEMDBID 1000 

• No overhead 

− No work done unless a DST query is executed 

− Query is processed in memory (no IO) 

− Very fast response 

• Data is not persistent 

− Only retrieved when requested 

− Memory only – gone when MUF is gone 

21 



Dynamic Systems Tables (cont’d) 

• One of my “FAVORITE THINGS” 

• The basis for various other “power tools” 

− CA SYSVIEW Performance Management for CA Datacom 

− CA Explore Performance Management for CA Datacom 

− CA Wily Introscope 

− CA Datacom AutoScope 

− CA Datacom/AD using products 

• CA 11 

• CA Disk 

• Etc. 


22 



CA Sysview for CA Datacom 

• Real-time performance monitor for the CA Datacom z/OS 

environment 

• Direct access to Dynamic System Tables 

• Exclusive ability to see inside MUF 

− Even when the MUF is looping or in a “wait” state 

• Recommended tool for monitoring CA Datacom 

23 



MENU DATACOM 

24 



DCLIST or LISTDCOM 



profile 



screen formats 



add screen format 



screen format for format JMGLISTs 



activate by overtyping active profile 



DCAREA 



DCDBASES 



DCDBASES (cont’d) 



DCMUFS 



DCTASKS 



SELECT STATUS NE ‘NOT ACTIVE’ 



TRACE 



MENU DCDIR – Directory information 



MENU DCMUF – Multi-User information 



MENU DCMUF (cont’d) 



MENU CSF - CICS Service Facility 



MENU Datacom Online Reference 



Sysview Commands 

• Some Neat Sysview Shortcuts 



DC DBTECH;DCDSETS;SORT PCT% D 



ACTIVITY CICST 



DS – DATASETS COMMAND 



DDL – list datasets allocated to DDNAME 



WHERE DBCVTPR 



DCOPEN 499 



DCSYSTEM 



DCAREAIO;SORT P-READS D 



SYSVIEW batch 

//EXECBAT EXEC PGM=GSVXBAT,PARM='LINECNT=66,SHOWINP=YES' 

//SYSPRINT DD SYSOUT=* 

//SYSIN DD * 

COMMAND=(DATACOM DBTEST;DCTABREQ;SORT DESC) 

SCROLL 

COMMAND=RETURN 

SCROLL 

COMMAND=END 

/* 



SYSVIEW batch output 



SYSVIEW review 

• Direct interface 

− Can see everything that is running in MUF 

− Can see into a MUF that is HUNG or LOOPING 

• Powerful real-time monitor 

− One MUF or many MUFs 

• Batch interface adds flexibility 

− Regularly scheduled jobs 

− Creates screen images that can be read by batch processes 



the new tools in the “box” with version 12.0 

• Provides ease of use 

• Adds automation 

• Shortens tuning effort 

• Includes: 

− ALL_INFO_REPORT 

− History Database Spill Table 

− AutoInfo 

− AutoStatus 

− AutoCollect 

− DATANE 

− DATASP 

− New space management options DSOP 4/5 

55 



ALL_INFO_REPORT 

• New console command to trigger the printing of the MUF EOJ 

reports to the PXX 

• We recommend that before using this command you 

implement the MUF option to direct PXX output to SYSOUT 

SYSOUT 0,5M,SQL,12M,SQL,2M CLASS,ML,CBS,SQL,DD,DST 

• Simple console command that can be issued via any of the 

console routes to MUF 

ALL_INFO_REPORT PXX 

ALL_INFO_REPORT PXXaaa 

– sites using a DASD PXX 

– sites using a SYSOUT PXX 

• Similar format to EOJ report just excludes page headers 

56 



ALL_INFO_REPORT (cont’d) 

ALL_INFO_REPORT 2011/10/27 15.37.28 

M R D F SUMMARY INFORMATION 

VIRTUAL COVERED COVERED 

AREA USE SIZE BLOCKS SPACE MRDF READS MRDF WRITES 1ST/ACT READS NON-1ST READS PERCENT 

IXX00006 VIRTUAL 250M 64,000 64-BIT 2 0 USED 0 

IXX00017 VIRTUAL 40K 10 64-BIT 1 0 USED 10 

TTM00017 VIRTUAL 32M 8,190 64-BIT 2 1 USED 0 

ACCOUNTING SUMMARY INFORMATION 


REQUESTS PROCESSED: 2,270,376 EXCPS: 24 

LOCATES: 54 ADDS: 54 UPDATES: 6,931 


CORE SIZE: 101,376 NUMBER OF ENTRIES: 1,079 ENTRIES RECLAIMED: 6,933 



REQUESTS PROCESSED: 493,499 EXCPS: 5 

LOCATES: 28 ADDS: 28 UPDATES: 426 


CORE SIZE: 101,376 NUMBER OF ENTRIES: 1,075 ENTRIES RECLAIMED: 430 


XCF SUMMARY INFORMATION 

JOB/SYS NAME GROUP TOTAL JOBS TOTAL REQUESTS 

* QA10 0 0 

* QA11 0 0 

* QA12 14 2,192,985 

BUFFER SIZE IB-REQUESTS OB-REQUESTS 

. 

. 

. 

1K 2,058,534 1,446,655 

2K 134,451 512,739 

5K 233,584 

6K 7 

57 



ALL_INFO_REPORT (cont’d) 

DATA BASE SUMMARY STATISTICS 

REQUESTS 2,247,490 

SQL REQUESTS 0 

DATA MANAGER REQUESTS 2,247,630 

I/O EVENTS - READS 138,409 

I/O EVENTS - WRITES 149,884 

EXCLUSIVE CONTROL REQUESTS 197,745 

EXCLUSIVE CONTROL CONFLICTS 0 

K/E BUFFER REORGANIZATION 0 

NO IXX BUFFER AVAILABLE 0 

NO DXX BUFFER AVAILABLE 0 

NO DATA BUFFER AVAILABLE 0 

NO EXPAND BUFFER AVAILABLE 0 

LAST IXX SEQUENCE NUMBER 4,278,604 

LAST DXX SEQUENCE NUMBER 2,844,007 

LAST DATA SEQUENCE NUMBER 1,901,300 

LAST EXPAND SEQUENCE NUMBER 0 

IXX BUFFER USED - 1 72 




IXX BUFFER USED - 5+ 4,278,340 

DXX BUFFER USED - 1 2,672 




DXX BUFFER USED - 5+ 2,833,406 

DATA BUFFER USED - 1 2,023 




DATA BUFFER USED - 5+ 1,893,373 

SEQ. READ AHEAD I/O EVENTS 0 

LOG AREA MAXIMUM PERCENT FULL 100 

SECONDARY E/C CONFLICTS 0 

. 

. 

. 

58 



History database – SPILL History table 

• New table added to the History database 

• History database is activated via a MUF startup option 

HISTORY dbid (default 1007) 

• Requires that a persistent database be allocated and available for MUF to use 

• SPILL table contains one row for each DBUTLTY SPILL that is executed 

• Rows include: 

FIRST_STORE_CLOCK FIRST_DATE FIRST_TIME FIRST_DATETIME 

LAST_STORE_CLOCK LAST_DATE LAST_TIME LAST_DATETIME 

SPILL_STATUS SPILL_DATE SPILL_TIME SPILL_DATETIME 

SPILL_JOBNAME SPILL_RUNUNIT RXX_SEQUENCE RXX_DSN RXX_DSN_2 

• Provides a single place to find the RXX datasets that will be needed to do a 

database recovery operation 

59 



AutoInfo 

• New DBUTLTY function added in version 12.0 

• Very simple to execute 

• Provides a snapshop of the MUF including: 

− Description of the MUF 

− MUF Options 

− MUF Summary information (Same as PXX Summary) 

− MUF MRDF, Accounting, other information (Same as MUF EOJ reports) 

− Lots of other DST information 

• Option to output the information in compressed format 

− SAM file that can be sent to support to help document issues 

− User contributed routine that can convert SAM file to XCEL spreadsheet 

60 



AutoInfo (cont’d) 

//$$$@NX@ EXEC PGM=DBUTLTY 

//CXX DD DISP=SHR,DSN=DCMQA.QAMUF4.CXX 

//SYSPRINT DD SYSOUT=* 

//DDOUT DD DSN=SHUKE01.QAMUF4.SNAPSHOT,DISP=(NEW,CATLG), 

// SPACE=(TRK,(10,5)),UNIT=WORK 

//SYSIN DD * 

AUTOINFO DDNAME=DDOUT 

/* 

Date: 10/27/2011 ******************************************************************************** Page: 2 


Time: 18.49.38 * General Utility * Release: 12 


******************************************************************************** Directory: QAMUF4 

MUF IS AVAILABLE, INFORMATION IS PROVIDED BY THE MUF. 

MUFNAME: MUF4 RELEASE: 12 SP: SP0 JOB/STC NAME: QA12MUF4 

CXXNAME: QAMUF4 JOBID: JOB11078 SYSTEM: CA31 

ENABLED TIME: 2011/10/27 18:47:49 

CURRENT MUF TIME: 2011/10/27 18:49:38 

MUF IS SHADOW: N MUF HAS SHADOW: N 

DB SUBSYS PRESENT: Y SQL: Y 

EXTERNAL SECURITY: N ACCOUNTING ON: Y 

DBIDS: DST: 1000 HISTORY: 1007 CBS TEMP: 0006 CBS HEUR: 1006 

TASKS: TOTAL: 00010 XCF: 00010 CCI: 00010 SIZE: 46080 

. 

. 

. 

61 




TABLE BUSINESS_VALUE_METRICS: BVM 

Elapsed Seconds 73 

CPU Seconds Used 8 

Physical I/O 6032 

Database Requests 152247 

Data Area Requests 160275 

Table Requests 144229 

Table Reads 100124 

Table Adds 12131 

Table Deletes 8734 

Table Updates 23240 

Calculated Business Value Metrics 

Requests per elapsed second 2085.57 

Requests per CPU second 19030.88 

Requests per Physical IO 25.24 

TABLE BUSINESS_VALUE_METRICS: BVD 

Elapsed Seconds 173 

CPU Seconds Used 0 

Request Processing % 

Database Requests 152247 ** 

Data Manager Requests 161001 105.7 

SQL Requests 0 0.0 

Physical I/O Processing % 

Total Physical I/O 6032 ** 

Physical I/O - Read 4909 81.4 

Physical I/O - Write 1123 18.5 

Sequential Read Ahead I/Os 0 0.0 

Accounting I/O 0 0.0 

Logging I/O 68 0.1 

. 

. 

. 

Includes BVM and BVDs 

62 




MUFNAME: MUF4 RELEASE: 12 SP: SP0 JOB/STC NAME: QA12MUF4 

CXXNAME: QAMUF4 JOBID: JOB11078 SYSTEM: CA31 

ENABLED TIME: 2011/10/27 18:47:49 

CURRENT MUF TIME: 2011/10/27 18:49:38 

MUF IS SHADOW: N MUF HAS SHADOW: N 

DB SUBSYS PRESENT: Y SQL: Y 

EXTERNAL SECURITY: N ACCOUNTING ON: Y 

DBIDS: DST: 1000 HISTORY: 1007 CBS TEMP: 0006 CBS HEUR: 1006 

TASKS: TOTAL: 00010 XCF: 00010 CCI: 00010 SIZE: 46080 

TABLE MFO: 

========== 

MUF_ENABLE;MUF_DATETIME;TOT;MUF_NAME;ACCTPRM_PRM_DBID;ACCTPRM_ANN_DBID;ACCTPRM_CPU_TIME;AGENT;AGENT_LOG_LEVEL;AGENT_USE_CONFIG;BRE 

AK 

20111027 18.47.49.000000;20111027 

18.49.38.410434;N;MUF4;4;5;N;N;0;N;50;6;65536;0;0;16;1006;N;8192;8000;28672;1000;0;Y;ISO;ISO;2;15; 

TABLE MFC: 

========== 

MUF_ENABLE;MUF_DATETIME;TOT;MUF_NAME;DBID;AREA_NAME;VIRTUAL_COVERED;FIRST_ACTIVE;DATASPACE;MEMORY_SIZE;BLOCKS_MAXIMUM;BLOCKS_CURRE 

NT 

20111027 18.47.49.000000;20111027 18.49.38.410434;N;MUF4;6;IXX;V;NULL;X;262144000;64000;64000;2;2;0;NULL;NULL;2;NULL 

20111027 18.47.49.000000;20111027 18.49.38.410434;N;MUF4;17;IXX;V;NULL;X;40960;10;10;1;1;0;NULL;NULL;1;NULL 

20111027 18.47.49.000000;20111027 18.49.38.410434;N;MUF4;17;TTM;V;NULL;X;33546240;8190;8190;2;2;0;NULL;NULL;2;NULL 

20111027 18.47.49.000000;20111027 

18.49.38.410434;N;MUF4;1022;IXX;C;NULL;NULL;2147483648;NULL;NULL;NULL;NULL;NULL;NULL;NULL;NULL;NUL 

20111027 18.47.49.000000;20111027 

18.49.38.410434;N;MUF4;1022;REO;C;NULL;NULL;4294967296;NULL;NULL;NULL;NULL;NULL;NULL;NULL;NULL;NUL 

20111027 18.47.49.000000;20111027 

18.49.38.410434;N;MUF4;1023;IXX;C;NULL;NULL;2147483648;NULL;NULL;NULL;NULL;NULL;NULL;NULL;NULL;NUL 

20111027 18.47.49.000000;20111027 

18.49.38.410434;N;MUF4;1023;REO;C;NULL;NULL;4294967296;NULL;NULL;NULL;NULL;NULL;NULL;NULL;NULL;NUL 

20111027 18.47.49.000000;20111027 

TABLE MFY: 

========== 

. 

. 

. 

63 



AutoStatus 


• Requires additional set-up – DBID 1018 

• Provides a set of “STATUS” snapshot of: 

− Runs as a long running task (STC) 

− Snapshots one or more MUFs on a given LPAR (per interval selected) 

− DBUTLTY AUTOSTAT must run on LPAR where source MUF(s) are 

− Can direct output to a repository MUF on a different LPAR 

− Source MUF can be repository MUF 

• Detailed usage documentation 

− CA Datacom/DB AutoScope User Guide for z/OS 


64 



AutoCollect 

• A set of new DBUTLTY functions added in version 12.0 

• Requires additional set-up – DBID 1019 and DBID 1020 

• Provides an automated system for 

− Collection snapshot “information” from the current MUF statistics 

− Creation of “delta” which are the differences between two snapshots 

− Ability to create summary, average and baseline deltas 

− Can direct output of snapshot process to a repository MUF on a different LPAR 

− Source MUF can be repository MUF 

• Detailed usage documentation 

− CA Datacom/DB AutoScope User Guide for z/OS 


65 



DATANE 


• Provides a simple and easy way to determine the sequential 

efficiency of a table 

− WHY 

• Determine if a reorganization is needed 

• Determine if only a portion of the table needs to be reorganized 

• Determine the effectiveness of an online reorganization process 

− When 

• When History report shows that significant sequential access is occurring for a 

given table 

• On a regular scheduled basis just to monitor sequential efficiency 

• After some “extra” processing that has occurred that may have effected the 

sequential order of rows 

– EOM purge and merge 

– EOY account re-ordering 

– New business added 

66 



DATANE (cont’d) 

Date: 4/14/2011 ******************************************************************************** Page: 4 


Time: 13.41.07 * General Utility * Version: 14.0 

* COPYRIGHT (C) 1990-2011 CA. ALL RIGHTS RESERVED. * 

Base: 381 ******************************************************************************** Directory: TSTTPNS 

*--- BLOCK --* PBC 6250 MRB *---- MAX ROW/BLK EFFICIENCY RATES WITH BUFFERS -----* 

GROUP ROWS BLOCKS MAX MIN AVG BLOCK EFF 2 4 8 12 16 20 24 28 32 48 64 96 128 256 

READ W/DATA ROWS ROWS ROWS CHANGES % % % % % % % % % % % % % % % 

46 100,000 10,650 16 1 9 14,885 42 55 57 

47 100,000 11,061 16 1 9 15,882 39 53 55 

48 100,000 11,047 16 1 9 16,143 39 53 54 

49 100,000 10,799 16 1 9 15,370 41 54 56 

50 100,000 10,498 16 1 10 14,795 42 56 58 

Efficiency calculated on the number of 

blocks actually touched versus the number 

minimum number of blocks need to hold 

the rows in order 

77 100,000 8,349 16 1 12 10,080 62 72 74 

78 100,000 9,507 16 1 11 12,325 51 62 64 65 

79 100,000 6,887 16 1 15 7,329 85 89 91 

80 100,000 8,373 16 1 12 9,909 63 71 74 

81 99,013 7,347 16 1 13 8,209 75 82 84 

________________________________________________________________________________________________________________________ 

FULL TABLE 

MRB 8,099,013 506,482 16 4 16 1,170,473 43 55 57 

AMRB 8,099,013 506,482 16 4 16 1,170,473 43 55 57 


67 



DATASP 


• Provides a simple and easy way to determine the “fullness” of 

a data area 

− WHY 

• Determine if a data area needs to be extended 

• Determine the effects of compression 

• Determine the effects of using DSOP 2 (versus DSOP 1) 

− When 

• On a regular scheduled basis just to monitor data area fullness 

• After some “extra” processing that has occurred that may have effected the content of the 

data blocks 

– OLREORG 

– EOM purge and merge 

– EOY account re-ordering” of a data 

– New business added 

68 



The DATASP Report – Detail and Summary Report 

Date: 5/06/2011 ******************************************************************************** Page: 2 




Base: 1022 


AREA REO BLKSIZE 4,096 TRACKS 300 BLOCKS 3,600 URI YES DSOP 4 RANDOM FOR OLREORG 

TBL CMP USER COMPRESSION RECLN RECORDS 

REO 112 31,950 

GROUP# BLOCKS KBYTES ROWS FREESP ROWS ROWLEN ---------- FREESPACE IN BLOCKS ----------- 

IN-USE % IN-USE % IN-USE MAX MAX MAX 0 TO 1/4K 1/2K 1K 2K 

EMPTY % EMPTY % DELETED MIN MIN MIN 3K 4K 8K 12K 

*AVAIL AVG AVG AVG 16K 20K 24K 32K 

difference 

1 923 92 3,259 81 29,779 4,094 36 112 715 19 31 69 

77 8 741 19 0 62 0 112 50 116 0 0 

6,221 759 30 112 0 0 0 0 

2 933 93 239 6 2,171 4,094 36 112 51 2 2 6 

67 7 3,761 94 0 62 0 112 4 935 0 0 

33,829 3,851 2 112 0 0 0 0 

3 0 0 2 0 0 4,094 0 0 0 0 0 0 

1,000 100 3,998 100 0 4,094 0 0 0 1,000 0 0 

36,000 4,094 0 0 0 0 0 0 

4 0 0 1 0 0 4,094 0 0 0 0 0 0 

598 100 2,391 100 0 4,094 0 0 0 598 0 0 

21,528 4,094 0 0 0 0 0 0 

TOTALS 1,858 52 3,502 24 31,950 4,094 36 112 766 21 33 75 

1,742 48 10,890 76 0 62 0 112 54 2,649 0 0 

97,578 3,099 9 112 0 0 0 0 

69 

Only 48 % 

not in-use 

Yet space for 

75% more rows 

Available 



new DSOP 4/5 

• Implemented through CXXMAINT in r12 

• DSOP 4 – Random for OLREORG 

• DSOP 5 – Sequential for OLREORG 

• For non-OLREORG DSOPs 4/5 mirror DSOPs 1/2 processing 

• For OLREORG processing 

• DSOP 4/5 allows empty blocks to be used for online 

reorganization 

70 



new DSOP 4/5 (cont’d) 

• CXXMAINT OPTION=ALTER,AREA=REO,DBID=1023,DSOP=4/5 

− Permitted while table is open 

− Activates a new internal space map 

− Built in the IXX 

− Very small – just a few IXX blocks 

− Keeps track of empty blocks available for OLREORG use 

• CXXMAINT should be followed up by one of the following: 

− LOAD which rebuilds IXX (database closed) 

− RETIX which rebuilds index (database closed) 

− RETIX KEYNAME=*DATA (database open) 

• Database remains open to users 

• Rebuild space maps including empty block index 

71 



using the DEFRAG report to see the DSOP 4/5 

space index 

Date: 5/05/2011 ******************************************************************************** Page: 10 




Base: 1022 


DEFRAG REPORT 

BLOCKS BLOCKS BLOCKS BLOCKS PERCENT 

KEY ID BEFORE COMBINED DELETED AFTER DELETED NOTES 

1 139 0 0 139 0.00 

2 79 0 0 79 0.00 

3 82 0 0 82 0.00 

4 91 0 0 91 0.00 

39324 78 10 10 68 12.82 MOVED RECORD 

39327 1 0 0 1 0.00 DATA FREE SPACE 

TOTALS 470 10 10 460 2.12 




summary - what’s in the toolbox 

• Lots of tools in the tool box 

• Everyone has their favorites 

• New tools being developed every 

release 

• Some tools may overlap, but not 

a problem 

• Sharing “how to” is probably the 

best tool of all 

73 



ecommended sessions 

SESSION # TITLE Date / Time 

MD720SN 

CA Datacom Education Workshop Part 2: Advanced 

Topics 

11/16/2011 

at 9:45 am

ecommended sessions (cont.) 

SESSION # TITLE Date / Time 

MD520SN 

MD540SN 

zIIP Enabling CA-based Web Services: Tales from the 

Trenches 

Impact – How a CA Ideal Application at U.S. Treasury 

Manages the Development Life Cycle 

11/16/2011 

at 11:00 am 

11/16/2011 

at 1:15 pm 

MD560SN Transforming CA Ideal Applications To Meet 2011 

Business Needs 

11/16/2011 

at 2:45 pm 

MD600SN CA Datacom® Online Data Reorganization Update 11/16/2011 

at 4:00 pm

Exhibition Center: related technologies 

• Booth 516 – CA Datacom, CA Ideal

Session # MD700SN/EC150ENA 

Please scan this 

image to fill in 

your session 

survey on a 

mobile device or 

complete a hard 

copy session 

evaluation form

terms of this presentation 

for information purposes only 

Copyright © 2011 CA. All rights reserved. IBM, CICS, DB2, IMS, and z/OS are trademarks of International Business Machines Corporation in 

the United States, other countries, or both. All trademarks, trade names, service marks and logos referenced herein belong to their 

respective companies. 

This presentation was based on current information and resource allocations as of November 2011 and is subject to change or withdrawal 

by CA at any time without notice. Notwithstanding anything in this presentation to the contrary, this presentation shall not serve to (i) 

affect the rights and/or obligations of CA or its licensees under any existing or future written license agreement or services agreement 

relating to any CA software product; or (ii) amend any product documentation or specifications for any CA software product. The 

development, release and timing of any features or functionality described in this presentation remain at CA’s sole discretion. 

Notwithstanding anything in this presentation to the contrary, upon the general availability of any future CA product release referenced in 

this presentation, CA will make such release available (i) for sale to new licensees of such product; and (ii) to existing licensees of such 

product on a when and if-available basis as part of CA maintenance and support, and in the form of a regularly scheduled major product 

release. Such releases may be made available to current licensees of such product who are current subscribers to CA maintenance and 

support on a when and if-available basis. In the event of a conflict between the terms of this paragraph and any other information 

contained in this presentation, the terms of this paragraph shall govern. 

Certain information in this presentation may outline CA’s general product direction. All information in this presentation is for your 

informational purposes only and may not be incorporated into any contract. CA assumes no responsibility for the accuracy or completeness 

of the information. To the extent permitted by applicable law, CA provides this presentation “as is” without warranty of any kind, including 

without limitation, any implied warranties or merchantability, fitness for a particular purpose, or non-infringement. In no event will CA be 

liable for any loss or damage, direct or indirect, from the use of this document, including, without limitation, lost profits, lost investment, 

business interruption, goodwill, or lost data, even if CA is expressly advised in advance of the possibility of such damages. CA confidential 

and proprietary. No unauthorized copying or distribution permitted. 

78 



Q&A

thank you

Part 1 - CA Technologies

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?