ims database futures - kyle charlet - nyc and toronto rug february 2014

© 2013 IBM Corporation

IMS Database: Futures Update

Kyle Charlet

STSM: IMS SOA and Modernization


© 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 orcommon 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

Other company, product, or service names may be trademarks or service marks of others.

Important Disclaimer

© 2013 IBM Corporation3

Strategy: IMS database and transaction manager

• Integrate organically with DB2 for z/OS

• Position as application manager of choice

• Position as industry-leading container for mixed-language workloads

• Integrate organically across the enterprise

• Increase dynamic capabilities

• Reduce planned outages

• Standardize channel access

Collectively increase workload, grow

IMS data worldwide, and strengthen

all IMS core capabilities

Enabled for services, mobile and cloud provisioning


IMS moving forward

Continued modernization of the IMS system

� IMS catalog

� Dynamic database

� State-of-the-art app server for language interoperability

� Enhanced inter-application communication

� Dependent region scalability

� Updated programming models

� Native SQL

� .NET Data Provider

� Aggressively pursue full integration with strategic portfolio offerings


Mobile

IBM Confidential


IMS Mobile

� The IMS mobile strategy gives our customers a mobile foundation they can

depend on

� Expand IMS ecosystem via delivery of mobile infrastructure

� Offer an integrated platform for full discovery, modeling, deployment and execution of both

transaction and data assets for mobile consumption

� REST interface with JSON wire protocol

IBM Confidential


IMS mobile enablement – intended direction

System zMobile

Devices

WAS Liberty Profile

REST services

JSON to/from byte[]

Discovery, modeling, deployment tooling

IMS Connect

IBM Confidential


IMS mobile enablement – potential for local optimization

Mobile

Devices

WAS Liberty Profile

REST services

JSON to/from byte[]

Discovery, modeling, deployment tooling

JDBC (type 2)

WOLA over OTMA

System z

IMS Connect

IBM Confidential


Big Data

IBM Confidential


Big Data Exploration

Find, visualize, understand all big data to improve decision making

Enhanced 360o Viewof the Customer

Extend existing customer views (MDM, CRM, etc) by incorporating additional internal and external information sources

Operations Analysis

Analyze a variety of machinedata for improved business results

Data Warehouse Augmentation

Integrate big data and data warehouse capabilities to increase operational efficiency

Security/Intelligence Extension

Lower risk, detect fraud and monitor cyber security in real-time

Big Data use cases


Enhancing IMS analytics on System z with Big Data

• Much of the world’s operational data resides on z/OS

• Unstructured data sources are growing fast

• There is a need to merge this data with trusted OLTP data from System z data sources

• IMS intends to provide the connectors and the DB capability to allow BigInsights to easily and efficiently access the IMS data source

IMS intends to support


Enhancing IMS analytics on System z with Big Data

� Observation points lead to new business opportunities

� Observation points gleaned from both archived data and live data

� Score business events, track claims evolution, and more

� Make the data available to people who can do something meaningful with it

IMS intends to support


System z data consolidation and IDAA

Leveraging your DB2 & IMS information infrastructure

• Organized to a support high speed transaction environment with historical and analytic

information

• Increase agility by rapidly responding with immediate, accurate information, eliminating

the need to search for answers with analysis that is timely

• Enables the organization to become more nimble by placing fact-based information into

the hands of decision makers

• Removes the never-ending search for the right information

DB2 Production

Data

IMSProduction

Data

Potential for IMS

Blending System z and

Netezza technologies to

deliver unparalleled, mixed

workload performance for

complex analytic business

needs.


Dependent region

scalability

IBM Confidential


Current IMS model

Control region

Dependent region

JVM (and app)

Dependent region

JVM (and app)

Dependent region

JVM (and app)

Dependent region

JVM (and app)

Dependent region

JVM (and app)

•Single control region can have up to 4095 dependent regions

•Each dependent region has its own JVM

•Dependent regions isolated from one another (failure isolation)

•Applications run serially in each dependent region

•One at a time, no parallelism

• When a new dependent region is started, IMS starts a new JVM in that region and applications are scheduled in the JVM as they come into the system

Separate address spaces

Control region

Dependent region

JVM (and app)

Dependent region

JVM (and app)

Control region

Dependent region

JVM (and app)Dependent region

JVM (and app)

Dependent region

JVM (and app)

Control region

Dependent region

JVM (and app)Dependent region

JVM (and app)

Dependent region

JVM (and app)

Dependent region

JVM (and app)

Control region

Dependent region

JVM (and app)

Dependent region

JVM (and app)

Dependent region

JVM (and app)

Dependent region

JVM (and app)

Dependent region

JVM (and app)

Control region

Dependent region

JVM (and app)


Multi-threaded IMS model – intended direction

Control region

•Single control region can have up to 4095 dependent regions

•Each dependent region has its own JVM

•Dependent regions isolated from one another (failure isolation)

•Applications run in parallel in each dependent region

•A new thread is created and the application is loaded in that thread and the main method is called•Current thought is 255 threads max

Dependent region

JVMThread/App

Thread/AppThread/App

Dependent region

JVMThread/App


Dependent region

JVMThread/App


Dependent region

JVMThread/App


Dependent region*

JVMThread/App


* IMS JVM launcher runs in dependent region address space


Catalog

IBM Confidential


General information

� IMS users (DBAs) need a more dynamic database definition function using industry

standards

� IMS will use DDL to support changes to database definitions

– DDL will operate as DL/I calls

� DDL changes can be activated when committed

– Simplify steps to make and activate a database change

– Optional based on system wide setting (production vs test)

� Future IMS enhancements to eliminate database outages will exploit DDL

� IMS users will use DDL authoring tools such as the IMS Enterprise Suite Explorer for

Development (E4D) to model database changes and create DDL

� IMS customers will not migrate from DBD source and PSB source to DDL immediately

– Catalog populate utility used to update the catalog from DBD and PSB source


Current environment

ACBLIB

Catalog

PSB

source PSBLIB

DBD

source DBDLIB

PSBGEN

DBDGEN

ACBGEN& CatalogPopulateIMS Explorer

IMS

� Trusted IMS metadata information

� Comprehensive view of IMS database metadata (including application metadata) managed by IMS with standard access patterns (JDBC/SQL)

� Offers metadata discovery and exchange via IMS Open Database and the IMS Explorer for Application Development

� Scalable Open Database solution – large scale deployment into virtualized production and test environments

� Enables broad IMS integration into the IBM and non-IBM portfolio of tools (Optim Development Studio, Rational Asset Analyzer, InfoSphere Data Architect, etc)


IMS catalog – intended direction

PSBLIB

Catalog

• IMS DB changes start with catalog

• IMS loads resource information from catalog

• ACBLIB/PSBLIB/DBDLIB can be created/updated from the catalog

• Tools that use these libraries can continue to operate, but should migrate to

catalog

• PSB and DBD source can be optionally generated from the catalog or from the

DBDLIB / PSBLIB with tools

IMS ExplorerDDL

ACBLIB

DBDLIB

PSB

source

DBD

source

IMS

Optional – Not used by IMS


Dynamic database definition with DDL

� SQL incorporates DDL to modify the schema

of a database

� Authoring DDL is straight-forward with

sophisticated tooling support in the industry

� SQL/DDL can be used to update/add

metadata in the catalog without the need of

a GEN

– Directly update the catalog

� IMS can be notified of such an update and

load the new definitions


Dynamic database definition with DDL (cont)

� SQL incorporates DDL to modify the schema

of a database

� Authoring DDL is straight-forward with

sophisticated tooling support in the industry

� SQL/DDL can be used to update/add

metadata in the catalog without the need of

a GEN

– Directly update the catalog

� IMS can be notified of such an update and

load the new definitions


IMS and DDL – moving towards a dynamic database (intended direction)

� Simplifies the process of adding a new Database resource– Without DDL:

1. Define your database characteristics (DBD)2. Compile/link database definitions (DBDGEN)3. Define your program specifications (PSB)4. Compile/link your program specifications (PSBGEN)5. Perform ACBGEN6. Allocate database data sets7. Define DBRC definitions8. Define IMS database for dynamic allocation (MDA)9. Bring online all IMS applicatoin-related definitions (OLC)10.Start IMS Databases11.Load and initialize IMS databases12.DBRC processing (DBRC IC)

– With DDL: 1. Define your database characteristics (DDL)2. Submit your DDL


DDL defaults and extended IMS syntax (intended direction)

� For users who do not want to rely on the IMS defaulting system, the DDL syntax has been enhanced

� All parameters that can be specified in the GEN macros are optional parameters in the IMS extended DDL syntax

� The IMS extended DDL syntax can be used in combination with existing defaults and will override those default values when specified.

� DDL syntax has also been extended to allow users to fully specify their own PSB definitions– If a PSB is defined in the same commit scope as a CREATE or

ALTER database call, no default PSB will be generated


PSB generation (intended direction)

� Standard DDL doesn’t provide a way to specify a PSB

� On a CREATE or ALTER command, a new PSB will be generated for the user in the IMS catalog

� This PSB will only be authenticated to the user that issued the CREATE or ALTER command– Additional users can be added through the normal SAF


Manual PSB generation

� DDL syntax has been enhanced for users to write their own PSBs instead of relying on system defaulted ones.

PSB

PCB


IMS Explorer for Development

� The IMS Explorer for Development is a tool to help with database visualization

and querying


IMS Explorer for Development – DDL creation (intended direction)

� The IMS Explorer for Development will be enhanced with the following DDL

editing/generation features

– A full text DDL editor, that allows users to manually create their own DDL scripts

– A graphical interface for creating/altering DDL resources

• The generated DDL will be the extended IMS DDL syntax


IMS Explorer for Development - DDL validation (intended direction)

� The IMS Explorer for Development will provide additional validation prior to submitting a DDL script

� Speeds up database change development as syntax errors are detected sooner

� Warns the user if the DDL script has changes that requires user intervention– For example: Unload/reload operations

� Warns the user if the DDL script is long running vs short running

– Long running: Creating a new database resource– Short running: Adding application metadata to an existing table

� Provides a way to view the IMS DDL audit trail to lookup database change history


Explorer for Administration

IBM Confidential

© 2013 IBM Corporation31 IBM Confidential

IMS Explorer for Administration 1.4

• Enterprise System View

• IMS Resource and IMSPlex

discovery

• Hierarchical representation starting

from the SYSPLEX to the IMS

Resources

• Enterprise Search

• Search across the entire enterprise

on any type of resource

• Visual Status

• Quickly see the status of any IMS

Resource with colored status icons

• Hover and click status icons for

reason codes and corrective actions

• Filter IMS Resources

• Manage IMS Resources

• Start/Stop and update IMS Resource

Attributes

• Multi select IMS Resources to

manage and update

• Resource Relationships

• View relationships between IMS

Resources

• At a glance understand why a

transaction is having a problem

• Customize

• Change the column attribute defaults


IMS Explorer for Administration 1.4 (discovery)

• Minimal configuration

• Define a Sysplex

• Define the discovery endpoint

• IMS Connect connections

• Discovery of IMS Resources:

• IMSPlexes

• IMSPlex Members

• IMS Connect Instances

• IMS Instances

• Transactions

• Databases

• Programs

• Routing Codes

Discovering....

IMS


Demonstration of IMS Explorer for Administration 1.4

© 2013 IBM CorporationIBM Confidential

Providing deeper insight into IMS (intended direction)

Disconnect

Communication

Displays clients

associated with

the port

QUERY IMSCON TYPE(DATASTORE)

QUERY IMSCON TYPE(PORT)

QUERY IMSCON TYPE(IMSPLEX).

QUERY IMSCON TYPE(ODBM)

QUERY IMSCON TYPE(RMTIMSCON)


Providing deeper insight into IMS (intended direction)

/DIS OTMA /DIS STRUCTURE

QUERY ODBM TYPE(DATASTORE) NAME(IMS1) SHOW(ALL) /DIS A REG /RMLIST DBRC ='RECON'


Command Entry (intended direction)

Command output is

rendered back into a

grid with rich function


Additional update support (intended direction)

Multi-select Transactions for Update

ims database futures - kyle charlet - nyc and toronto rug february 2014

Technology

ims data sourceims

ibm logo

ims database

ims analytics

ims soa

ims ecosystem

data assets

ibm trademarked terms