IMS10 unleash the capabilities of new technologies

Session - IMS10
*
Nick R. Griffin - IMS Tools Product Line Manager
Unleash the
Capabilities of New
Technologies with
IMS Tools

Important disclaimer
2
© Copyright IBM Corporation 2014. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
THE INFORMATION CONTAINED IN THIS PRESENTATION IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY. WHILE
EFFORTS WERE MADE TO VERIFY THE COMPLETENESS AND ACCURACY OF THE INFORMATION CONTAINED IN THIS
PRESENTATION, IT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. IN ADDITION, THIS
INFORMATION IS BASED ON IBM’S CURRENT PRODUCT PLANS AND STRATEGY, WHICH ARE SUBJECT TO CHANGE BY
IBM WITHOUT NOTICE. THE INFORMATION ON NEW PRODUCTS IS FOR INFORMATIONAL PURPOSES ONLY AND MAY
NOT BE INCORPORATED INTO ANY CONTRACT. THE INFORMATION ON ANY NEW PRODUCTS IS NOT A COMMITMENT,
PROMISE, OR LEGAL OBLIGATION TO DELIVER ANY MATERIAL, CODE OR FUNCTIONALITY. THE DEVELOPMENT,
RELEASE, AND TIMING OF ANY FEATURES OR FUNCTIONALITY DESCRIBED FOR OUR PRODUCTS REMAINS AT THE
SOLE DISCRETION OF IBM. IBM SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES ARISING OUT OF THE USE OF, OR
OTHERWISE RELATED TO, THIS PRESENTATION OR ANY OTHER DOCUMENTATION. NOTHING CONTAINED IN THIS
PRESENTATION IS INTENDED TO, NOR SHALL HAVE THE EFFECT OF, CREATING ANY WARRANTIES OR
REPRESENTATIONS FROM IBM (OR ITS SUPPLIERS OR LICENSORS), OR ALTERING THE TERMS AND CONDITIONS OF
ANY AGREEMENT OR LICENSE GOVERNING THE USE OF IBM PRODUCTS AND/OR SOFTWARE.
IBM, the IBM logo, ibm.com, Information Management, IMS, and z/OS are trademarks or registered trademarks of International
Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked
on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law
trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law
trademarks in other countries. A current list of IBM trademarks is available on the Web at “Copyright and trademark information” at
www.ibm.com/legal/copytrade.shtml

Agenda
Enabling Analytics for IMS Data
How to manage Big Data for IMS
Leveraging New Technologies
Q&A

Data Cloud Engagement
Social. Mobile. Security.
Empowering people with
knowledge, enriching
them through networks
and changing
expectations.
The emergence of cloud
is transforming IT and
business processes into
digital services
Data is becoming
the world’s new
natural resource
There are three important shifts fundamentally
changing the way that decisions are made…

Mobile is redefining the Data Center
5
91% 75% 96% 90% 900%
Mobile users keep their
device within arm’s reach
100% of the time
Mobile shoppers take
action after receiving a
location based message
Year-to-year increase in
mobile cyber Monday sales
between 2012
and 2011
Users use multiple screens
as channels come together
to
create integrated
experiences
Increase of global machine-to-
machine connections by 2022
© 2013 IBM Corporation5
IMS Mobile
A14

The benefits of implementing mobility into your IT model
 Mobility started as a productivity
enhancement
 Mobility has evolved into a system of
engagement platform
 IDC: The number of people accessing
the Internet from smartphones, tablets
and other mobile devices will surpass
the number of users connecting from a
home or office computer by 2015.
7

Integrate mobile across the enterprise
 Mobile technology leaders
know they must integrate
mobile applications with
back-end systems such as
IMS
74% of CIOs
say mobile solutions
are part of their vision
for increasing
competitiveness

Why System z is an attractive platform for mobile connectivity
IMS 13
Delivering the highest levels of performance, availability, security, scalability and
connectivity in the industry
 Breaking through 100k TPS 800% greater than IMS 12
 CPU reductions up to 62% for Java Apps
 SQL access to IMS data from both .NET and COBOL
applications
 Greater flexibility and faster deployment for new
applications with database versioning
 Big data exploitation of Hadoop / Big Insights, MDA, Watson
Explorer…
 Simplified mobile access with JSON, IMS Connect….

The IMS Mobile Business
 Our Target Market
– IMS customers with plans to expand their business to leverage mobile
access
 How we can help
– Securely deliver IMS applications and data to mobile and cloud developers
in a managed, governed, and optimized way via:
 An integrated platform that supports full discovery, modeling, enablement, and
deployment of both IMS transactions and IMS data
 A singular approach for System z clients using WAS, CICS, IMS, and DB2
– Provide options to help manage TCO
– Provide solutions for clients in each quadrant of the mobile maturity model
 Benefit to our clients
– A comprehensive solution that addresses skills, TCO, continued ROI on their
IMS investment, and System z qualities of service

11
IMS Mobile Enablement
z/OS
IMS
Connect
IBM Worklight
Server
Database
Manager
Transaction
Manager
IMS
Application
Mobile
Devices
IMSSOAP
Gateway
SQL Adapter
HTTP Adapter
IMS DB
IMSUniversal
Driver
IMS Explorer for Dev
IMS Explorer for Admin
Web / Desktop
Web-enabled IMS apps
ISPF
z/Linux
IMS Enterprise Suite Components
The IBM IMS Mobile Feature Pack
(IMS Mobile) provides the solution to
easily enable your IMS transaction
assets as services for mobile and cloud
consumption.

12
First National Bank (FNB)
Achieving sub-second response for hundreds of millions of monthly transactions
on the mainframe
The need:
The ubiquity and convenience of cellphones and tablets as computing devices
represented a clear growth opportunity for FNB; in South Africa, more people have
cellphones and smart mobile devices than bank accounts. FNB wanted to launch a
reliable, secure and highly responsive mobile channel before its competitors, and
looked for a platform that would enable very short time-to-market.
The solution:
FNB integrated a new Java-based mobile front-end directly with tried-and-trusted
business logic and core banking services running on IBM® Information
Management System (IMS™) on an IBM zEnterprise® EC12 server. IBM IMS
Enterprise Suite Connect APIs for Java and C and IBM IMS Enterprise Suite SOAP
Gateway manage links between the channel applications and core functionality and
data on the mainframe.
The benefit:
 Rapid deployment enabled FNB to gain first-mover advantage in the market,
gaining the number one spot for mobile banking
 Ultra-low average end-to-end response times of 30 milliseconds ensure snappy
performance for mobile banking users
 Fast, secure and reliable mobile banking generates more business for FNB and
reduces its average cost per transaction
“We don’t start from the premise
that the mainframe
is best; rather, we look at the
requirements—big data, huge
numbers of concurrent processes,
high performance, high scalability,
high security—and then look at
what technology can deliver all of
those things. The answer is IBM
zEnterprise and IMS.”
—Jay Prag, CIO – Hogan Channels,
FNB
Solution components:
 IBM® zEnterprise® EC12
 IBM z/OS®
ZSP03833-USEN-00

Analysis with Big Data for IMS

14
IBM DB2
Analytics
Accelerator
Applications DBA Tools, z/OS Console, ...
. . .
Operation Interfaces
(e.g. DB2 Commands)
Application Interfaces
(standard SQL dialects)
DB2
Log
Manager
IRLM
Buffer
Manager
Data
Manager
System z
Superior availability
reliability, security,
workload management,
OLTP performance ...
Powered by PDA
True appliance,
Industry leading
ease of performance
Uniform DB2
service,
maintenance,
database
administration, ...
Uniform and
transparent
access for
transactional
and analytical
applications
DB2 for z/OS Approach: Hybrid Database Management System

Query Execution Process Flow
DB2 for z/OS
Optimizer
IDAADRDARequestor
DB2 Analytics Accelerator
Application
Application
Interface
Queries executed with DB2 Analytics Accelerator
Queries executed without DB2 Analytics Accelerator
Query execution run-time for queries that
cannot be or should not be off-loaded to
IDAA
SPU
CPU FPGA
Memory
SPU
CPU FPGA
Memory
SPU
CPU FPGA
Memory
SPU
CPU FPGA
Memory
SMP
Host
Queries executed with value of “ALL” may receive a SQL Error Code if the query cannot run on the accelerator
Heartbeat (DB2 Analytics Accelerator availability and performance indicators)

16
More users across the organization want access to
business critical analytics

History of IMS Analytics
 Desire to combine IMS data with other data
– Social, DB2 z/OS data, SAS data, etc
 ETL IMS data into data warehouse
– Mostly off z/OS
– Data being sent to potentially many sources
 Security can be compromised
 Performance historically not keeping up without $$$$$
17

Accelerate IMS Access - Proposed Solution
 Leverage Analytics Accelerator
– Metadata resides in DB2
– Copy IMS Data into Accelerator Only
 DB2 manages queries and controls access
18
Advantages:
• Data never leaves z/OS
• IMS workload unaffected
• Single server for z Analytics
• Join of IMS/DB2 data
• Less reason to ETL DB2/IMS
data off platform

Basic Process
 Decide IMS data needed
 Decide extraction and mapping tools and process
 Currency required (Refresh Frequency)
 Map IMS data to relational model
 Create DB2 table that matches extracted record format
 Add table to Accelerator
 Extract IMS data
 Load extracted data to DB2 table
 Load data from DB2 into the accelerator
 Enable DB2 version of table for acceleration
19

Extraction Considerations and Methods
 Considerations
– Availability requirements
– Frequency of refresh?
– Impact to OLTP workload
– What data is needed?
 Entire database, certain
segments, multiple DBs?
– Consistency of data?
20
Deep Analytics
Transactional Analytics
Image
Copies
Unload
Files
Database Clones

Extraction Considerations and Methods
 Extraction Tools and Methods
– Custom IMS Application
 Additional online workload
 Data can still be changing
– Database Clone (IMS Cloning Tool)
 Group of databases at a point in time
– Image Copies/Unload Files
 Additional knowledge of structure needed
– Mapping and ETL Tools
 IMS Explorer
 Data Stage, Informatica
 Data Virtualization
 IMS Catalog via JDBC
 Other tools
21
Deep Analytics
Transactional Analytics
Image
Copies
Unload
Files
Database Clones

Mainframe Based Data Virtualization

Mapping and Transforming Data
 Segment -> Table
 Field -> Column
 Data type not required by IMS
 Many times FIELD only defined for sequence fields
 Data content not enforced by IMS
 Data cleansing required?
 Where are field descriptions defined?
 IMS Catalog
 Copy books
 JAVA Classes
 Non-unique or non-keyed segments
23
IMS Database
DB2 Tables
Part_No Part_Description
&schema.Part_Master
Process
Code
Invoice
Code
Cost
Center
PM_Part_no
&schema.Standard_Info
Area Dept Project Division PM_Part_no
&schema.Stock_Status
…

PARTROOT
STANINFO STOKSTAT
CYCCOUNT BACKORDER
DataBase Definition (DBD)
DBD NAME=DI21PART,ACCESS=(HISAM,VSAM)
DATASET DD1=DI21PART,DEVICE=3380,OVFLW=DI21PARO,
SIZE=(2048,2048),RECORD=(678,678)
SEGM NAME=PARTROOT, PARENT=0,BYTES=50, FREQ=250
FIELD NAME=(PARTKEY,SEQ),TYPE=C,BYTES=17,START=1
SEGM NAME=STANINFO,PARENT=PARTROOT,BYTES=85, FREQ=1
FIELD NAME=(STANKEY,SEQ),TYPE=C,BYTES=2,START=1
SEGM NAME=STOKSTAT, PARENT=PARTROOT, BYTES=160, FREQ=2
FIELD NAME=(STOCKEY,SEQ),TYPE=C,BYTES=16,START=1
SEGM NAME=CYCCOUNT, PARENT=STOKSTAT, BYTES=25, FREQ=1
FIELD NAME=(CYCLKEY,SEQ),TYPE=C,BYTES=2,START=1
SEGM NAME=BACKORDR, PARENT=STOKSTAT, BYTES=75, FREQ=0
FIELD NAME=(BACKKEY,SEQ),TYPE=C,BYTES=10,START=1
DBDGEN
FINISH
END
Program Specification Block (PSB)
DBPCB01 PCB TYPE=DB,DBDNAME=DI21PART,PROCOPT=GOT,
KEYLEN=43
SENSEG NAME=PARTROOT
SENSEG NAME=STANINFO,PARENT=PARTROOT
SENSEG NAME=STOKSTAT,PARENT=PARTROOT
SENSEG NAME=CYCCOUNT,PARENT=STOKSTAT
SENSEG NAME=BACKORDR,PARENT=STOKSTAT
PSBGEN LANG=COBOL,PSBNAME=DFSSAM07
END
IMS/DB definitions
Mapping IMS Data to Tables
Table-name
PARTROOT
Column-names
PARTKEY
…
Table-name
STANINFO
Column-names
STANKEY
…
Table-name
STOKSTAT
Column-names
STOCKKEY
…
Table-name
CYCCOUNT
Column-names
CYCLEKEY
…
Table-name
BAKCORDER
Column-names
BACKKEY
…
DBD:DI21PART
24

Flattening IMS Database Records
 Concatenated Keys
– Concatenated key fields not stored with
segment data
– Key fields needed for each row to
maintain referential integrity
 OCCURS clauses
– Multiple instances of a field in a single
instance of a segment
– Multiple ‘rows’ should be generated
26
STANINFO (Standard data)
01 STAN-INFO.
02 SI-PROC-CODE PIC XX. <-Key
02 SI-INV-CODE PIC X.
02 SI-COST-CTRS PIC X(30).
02 SI-COST-CTRS-D REDEFINES SI-COST-CTRS.
05 SI-COST-CTR-NO OCCURS 3 TIMES
PIC X(10).

Loading Transformed Data
 End result of transformation: Data in DB2 Load file format
 DB2 Load Utility can perform more transformations
 Load syntax needed to describe IMS data in file
(DEPTNO POSITION (1:3) CHAR(3),
DEPTNAME POSITION (4:39) CHAR(36),
MGRNO POSITION (40:45) INTEGER EXTERNAL(6),
HDATE POSITION (46:55) DATE EXTERNAL(10),
Etc…
27

IMS Data in DB2 Analytics Accelerator
Table A
Table B
Table C
DB2 Analytics AcceleratorDB2 Tables
Two Step Load Process – Can be CPU Resource Intensive
Extracted IMS Data
File A
File B
File C
Load Load
#1 #2
28

How IBM Tools Can Maximize Accelerator Value
 Customers want to learn more about their investment in the Accelerator and maximize its use in
their environment
– Customer’s are looking at creative ways to exploit the Accelerator….
• IMS, VSAM, SMF Data, Non-z/OS data ….
– Data Mining, IT Analytics, Reporting
 Three different areas where tools can provide value
– Assessment
• Do I have a workload that would benefit from the Accelerator?
– Optimization
• Can I optimize the workload to take advantage of the Accelerator?
– Administration
• Can I manage the Accelerator more effectively?
29

30
IBM Tools: Maximizing your Analytics Accelerator
Investment
OMEGAMON XE for DB2 PE
Analyze
and
Report
DB2 Admin/OC
Manage
and
Administer
Query Workload Tuner for z/OS
Compare
and
Tune
Query Monitor for DB2
Monitor
and
Identify
Loader
Performance
Load with
options
Compare
and
Tune
Loader
Performance
Load with
options

 Accelerator Loader can load data from a file in one of two methods:
1. Dual External Load
 Loads data into both DB2 and the Accelerator in parallel
2. Accelerator Only
 Accelerator Loader loads directly into Accelerator (no load in DB2)
 User is responsible for building the load file
– Extracted data can come from various sources
 IMS, VSAM, Oracle…..etc
– File must be compatible for input into the DB2 LOAD utility
– Field specification must describe input data format. This must be compatible with the DB2 LOAD utility.
IBM DB2 Analytics Accelerator Loader:
What is External (Dual) Load
32

IMS Data in DB2 Analytics Accelerator
Table A
Table B
Table C
Two Step Load Process – Can be CPU Resource Intensive
Extracted IMS Data
File A
File B
File C
Load Load
#1 #2
34

DB2 Analytics Accelerator Loader:
External Load (Dual Load Option)
Table A
Table B
Table C
Parallel Load into DB2 and Accelerator – Faster Load Cycles – Reduce Costs
Extracted IMS Data
File A
File B
File C
#1 #1
35

DB2 Analytics Accelerator Loader:
External Load (DB2 Analytics Accelerator Only Option)
Table A
Table B
Table C
File A
File B
File C
#1 #1
Table A
Table B
Table C
R
E
D
U
C
E
D
S
T
O
R
A
G
E
DB2 Analytics Accelerator Only Load – Reduced Elapsed Time – Reduced Cost – Reduced DASD
36
DB2 Analytics AcceleratorDB2 Tables IMS Extracted External Data

How to manage Big Data for IMS

IMS Automated Data Base Solutions
 Checks data base status on a regular basis
– User specified thresholds for key indicators
 Performs reorganization only when necessary
 Performs auxiliary functions: IC, PC, IB, etc.
 Keeps data bases performing optimally
 Saves human resources
 Saves computer resources
 Cost efficient solution for both predictable and unpredictable data base growth and
activity

Two Approaches = Single Solution
 Conditional Reorganization
– User/scheduler initiated job submission
– Immediate Sensor Data Collection from Data Base
– Evaluation of Sensor Data versus Policy
– Decision to Reorganize or Quiesce
– IMS Data Base Solution Pack Reorganization Expert
 Autonomic Reorganization
– System initiated job submission
– Periodic Sensor Data Collection from Data Base
– Periodic Evaluation of Sensor Data versus Policy
 Passive = Recommendations only
 Active = Initiate and manage Autonomic Reorganization
– IBM Base Pack IMS Autonomics Director
 No charge

Getting the Most from Conditional
Reorganization

Smart Reorg utility in Reorg Expert
44
Smart
Reorg
Driver
IMS Tools Knowledge Base
Report Service
Parallel Reorganization
Service
Conditional Reorganization
Support Service
(including Policy Services)
IMS Tools
Knowledge
Base
Server Sensor
Data
Smart Reorg utility job step Repositories
Reports
Policy
Database
Shadow
Database
Reload
Unload
Scanning Online DB
IMS
Online Subsystems
 Conditional Reorganization Support Service (CRSS)
provides extended features
 Extended services are built on the IMS Tools Knowledge Base
(IMS Tools KB) and Policy Services infrastructures
IMS Tools Online System Interface

Smart Reorg utility in Diagnosis Only mode
45
Smart
Reorg
Driver
Report Service IMS Tools
Knowledge
Base
Server Sensor
Data
Smart Reorg utility job step Repositories
Reports
Policy
Database
Conditional Reorganization
Support Service
(including Policy Services)
IMS
Online Subsystems
 Smart Reorg Driver supports diagnosis only mode,
where database exceptions and reorganization
need are checked and notified but no
reorganization is performed
Scanning Online DB

46
Smart Reorg Driver
Renamed to
original name
Renamed to
original name
Renamed to
original name
Renamed to
original name
DISPOLDDSProcessing
Shadow DBDSShadow DBDS
IndexIndexShadow
Index
IC
Index Builder Task
Image Copy Task
(can include Pointer Check)
IC
IC
Index Builder’s SORT Address SpaceIndex Builder’s SORT Address SpaceIndex Builder’s
SORT Address Space
DB is Off-linedRead-Only Access to On-line DB
DBRead-OnlyProcessing
DBQuiescentprocessing
NOTIFY.REORG
DBDSNameSwapping
CHANGE.DBAUTHREADOFF
Reload Task
Unload Task
NOTIFY.IC/UIC
RestartingDB
/DBD DB /DBR DB /STA DB
OnlineOnline
Original IndexOriginal IndexOriginal Index
Original DBDSOriginal DBDS
Renamed to
original name
CRSSPre-
process
Parallel Reorganization Service (used only when reorg needed)
Sensor data are
collected during
Reorg Reload
CRSSPost-process

Smart Reorg utility features at a glance
 All information are stored in and managed by IMS Tools KB repositories
 Sysplex-wide access to these repositories is supported by IMS Tools KB Server
47
IMS Tools KB
Server
ISPF
Report
Search/View
ISPF
System z
Server
Smart Reorg job
Sensor data records
and reports are sent
to repository
A policy is retrieved
from repository and is
applied
Policy
Repository*1
Report
Repository*2
Sensor Data
Repository
TSO users
and/or
z/OS
operator
consoles
Notification messages are sent
Sysplex
1. Sensor Data
Collection
2. Reorg policy
Definition
3. Conditional
Reorganization
4. Exception
Notification and
Reporting
5. Tracking exceptions
and reorgs
*1: ITKB Input Repository is used as the Policy
Repository.
*2: ITKB Output Repository is used as the Report
Repository.
1
3
4
5
3
Policy
Management
2

Getting the Most from Autonomics

IMS Tools Autonomics Vision
 Sensors collect resource statistics
 Policies evaluate sensor data and
identify potential problems
 Automation orchestrates the
collection and evaluation of sensor
data
 Modernization presents an
interactive modern interface for
managing the system
Putting information to work
SensorsPolicies
Automation Modernization

List of Full Function sensor data collected
Database Record Statistics (per database or HALDB partition)
 Nbr. of DB records  Avg. DB record length
Randomizer Statistics (per HDAM or PHDAM partition)
 Nbr. of total RAPs  Nbr. of unused RAPs  % of number of unused RAPs  Nbr. of synonyms
 % of number of synonyms  Nbr. of root not on home block  % of root not on home block  % of segment data in overflow
 Nbr. of roots in overflow  % of number of roots in overflow  Bytes of segments in RAA
Volume/Extents Statistics (per data set)
 Allocation type (CYL, TRK, …)  Primary allocation amount  Secondary allocation amount  SMS-managed or not
 Max. nbr of extents for the d.s.  Max. nbr. of extents for the volume  Nbr. of extents allocated  Nbr. of volumes used
 Nbr. of unused volumes  Nbr. of unused assigned volumes Nbr. of unused candidate volumes
 Nbr. of available remaining extents determined by the max. nbr. of data set extents and the max. nbr. of extents available on volumes assigned to the data set
Data Set Space Usage Statistics (per data set)
 Block/CI size  Nbr. of blocks/CIs used  Max. size of the data set  % of data set size against the max.
 High-Allocated-RBA  High-Used-RBA
IMS Space Utilization Statistics (per data set)
 Total bytes of segment data  Total bytes of free spaces  Total bytes of slack bytes  % of free spaces
 % of segment data  % of unused bytes in the data set  Total nbr. of segments  Total nbr. of VL segments
 Total nbr. of VL-split segments  % of nbr. of VL-split segments  Total nbr. of slack bytes  Avg. nbr. of slack bytes per block
 Total nbr. of FSEs  Avg. nbr. of FSEs per block  Nbr. of FSEs valid for shortest segments  Nbr. of FSEs valid for longest segments
 Avg. nbr. of non-reusable FSEs  Total nbr. of pointers  Total nbr. of ptrs pointing external block  % of nbr. Of ptrs pointing ext. block
HISAM/SHISAM Statistics (for HISAM)
 Logical record length  Total nbr. of CI splits  % of nbr. of CI splits  Total nbr. of CA splits
 % of nbr. of CA splits  Total nbr. of HISAM delete bytes  % of nbr. of HISAM delete bytes
50
Sensors

Sensor Data Repository
 The sensor data is stored in the Sensor
Data Repository as records made up of
data elements
 The data record is stored in a well-
understood and flexible format
– This allows its use years and multiple
product releases later in time
 The data and its format is
understandable between products and
releases to ensure reliable functionality
51
IMS Tools Knowledge
Base Server
Sensor Data
Store/Read
Services
Data
Validation
Data
Dictionary
Policy
Services
Smart Reorg job
Sensor Data Repository
Data element names and
their attributes, including
the description of the
element, are defined here
Sensors

Major components of a policy
 Policy has two major components:
– Rules that detect exceptions
– Exception-to-Action mapping
 Rule Set for exception detection
– Rule has two elements:
 Condition (a threshold check formula)
 Exception (a named state of a DB)
 Action List for action mapping
– An Action List entries defines an
exception-action mapping
– The sequence of Action List entries defines
whether to reorganize the subject
database
52
Policy
Rule Set
Rule Rule
Rule Rule
Rule Rule
Action List
Action
Action
Action
Rule
Class
Severity Level
Exception
Message Text
Expression
Threshold set
Condition
Threshold set
Threshold set
Condition Exception
An Action List Entry
Exception
Class
and
Level
Action
“MESSAGE”
or
“REORG”
Policies

Exception detection condition is defined in a rule
53
DB_PCT_OF_MAX_DS_SIZE
The percentage of allocated bytes (bytes for
High Allocated RBA) compared to the maximum
size (4 GB or 8 GB).
DB_PCT_BYTES_FREE_SPACE
The percentage of bytes of total free spaces to
the total used bytes for the data set.
Sample Data Elements
A named set of threshold values for the
threshold variables that are referred to
in the condition descrition above is
called a threshold set.
A Sample Condition Description
A Sample Set of Threshold Values
&1 = 85
&2 = 20
Threshold Set
You can tweak
these threshold
values
“MED” =
Policies

Attributes of an exception
 Exception class
– Represents the specific database event
category being monitored
 Exception severity level
– Is a category representing the severity of
the detected exception
– There are fixed three levels:
 WARNING
 SEVERE
 CRITICAL
 Exception message
– Is the text that can be used by the resulting
policy action to describe the database
event that crossed a rule threshold set
– Users can modify the message text
54
Class
Level
Exception
Message Text
 CRITICAL
 SEVERE
 WARNING
Exception Class:
FRAGMENTED_FREE_SPACES
* Name of the rule that detects the this exception:
IBM.FRAGMENTATION.10
An Example of Exception Class
“The fragmentation of free space in %RESOURCE%
has increased”
* The symbol %RESOURCE% is replaced by a DBD
name or a partition name.
An Example of Exception Message
Policies

Exception-to-Action mapping
 An action is the result of a rule condition being
reached or exceeded during a policy
evaluation
 A rule threshold set has been mapped to a
severity level for the exception class
associated with the rule
 In turn, the severity level is mapped to an
action
Note: In IBM-provided REORG policies, severity-level-to-action
mappings are fixed for each exception class and are not
customizable.
55
Threshold
Set
Exception Class
+ Severity Level
Action
HIGH
MED
LOW
CRITICAL
SEVERE
WARNING
REORG
MESSAGE
An Example of threshold/exception/action mapping
Automation

Drill down on Exceptions from an Enterprise-wide View
Resource status,
errors, and
recommendations
can be aggregated
with an ability to
drill down
Modernization

Holistic View of IMS Databases
…from Sensors
…from Auto Discovery
…from Autonomics Director
…from Various HP Tools
Modernization

Integrated Help Throughout
Integrated help
educates new and
experienced DBAs
on database
concepts and how
Modernization

Consider a combined strategy
Use for appropriate situation
 Conditional Reorganization for environmental compatibility
issues
– Mainly Job scheduler mandates
 Autonomic Director
– In Passive Mode for health check between scheduled
reorganizations to detect anomalies
– For On Demand requests for DB status to address perceived
performance issues
 Phased approach is best
– Gain experience with a small subset of data bases
– Consider using passive mode first
– Migrate to active mode when comfortable
SensorsPolicies
Automation Modernization

Evolution of IMS Tools
 Reduce elapsed time of data management processes
–> More application availability
 Easier, more intuitive interfaces
–> Multi-tasked staff
 Self managing – Autonomics
–> Increased workloads
 Exploit new technologies
–> Growth in data, transactions
–> Enhance business value of data

Fast-Replication Storage Processors
 Creates an instant copy of a volume or a dataset at a specific point-in-time
– Often referred to as Point-in-Time copy, instantaneous copy or time zero (t0) copy
 Advantages
– Can copy huge volumes of data very quickly
-> Lab tests
– Minimal disruption for the running applications
– Copy process is offloaded to the storage subsystem
-> opportunity to lower host CPU and host I/O
 Reduce backup costs and time
 Reduce recovery times

zIIP Processors
 Offloads General Mainframe Processor Work
 Originally Developed for DB2 Processing Loads
– DB2 V8 was the first application to exploit zIIP processors
 Now widely used to offload many zOS workloads
 Must switch between TCB and SRB execution mode
 How IMS Tools can leverage
– ‘Sorting’
• Reorganization, Index Rebuild, Change Accumulation
– Computing
• Pointer Checker
 BSAM and VSAM I/O can now be offloaded

z13 Processors
 More Instructions in Hardware
 Larger Memory
– Up to 10tb
 Simultaneous Multi-Threading (SMT)
– Similar to IDAA processors
 Intelligent I/O system
– 830 gb/sec bandwith
– IBM zHiperWrite
• DB2 log write performance

Summary
 IBM is continuing to invest in IMS Tools
– Analytics Accelerator – means to do real analytics without moving data
off of z platform.
– Autonomics – adding intelligence into tools to help DBAs manage
growing workloads more efficiently
– Leveraging new technologies to help DBAs perform tasks more
efficiently and reducing costs
 Enablement of new technologies
-> Enhance business value of application data
-> Assist in workload demands
-> Optimize cost of data management

IMS10 unleash the capabilities of new technologies

More Related Content

What's hot (14)

Viewers also liked (20)

Similar to IMS10 unleash the capabilities of new technologies (20)

More from Robert Hain (15)

Recently uploaded (20)

IMS10 unleash the capabilities of new technologies