63
© 2014 IBM Corporation 2014 IMS Trends and Directions Betty Patterson IBM Distinguished Engineer IBM Silicon Valley Laboratory San Jose, California September 11, 2014

IMS Trends and Directions for Montreal RUG 2014 09-11

  • View
    108

  • Download
    3

Embed Size (px)

DESCRIPTION

IMS Trends and Directions presentation given by Chief Architect Betty Patterson at the inaugural IMS RUG in Montreal Quebec, Sept 2014

Citation preview

Page 1: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation

2014

IMS Trends and Directions

Betty PattersonIBM Distinguished Engineer IBM Silicon Valley LaboratorySan Jose, California September 11, 2014

Page 2: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation1 2014

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

IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.

IBM, the IBM logo, ibm.com, Information Management, IMS, CICS, DB2, WebSphere 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

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

Disclaimer

Page 3: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation2 2014

Any information contained in this document regarding Specialty Engines ("SEs") and SE eligible workloads provides only general descriptions of the types and portions of workloads that are eligible for execution on Specialty Engines (e.g., zIIPs, zAAPs, and IFLs). IBM authorizes customers to use IBM SEs only to execute the processing of Eligible Workloads of specific Programs expressly authorized by IBM as specified in the “Authorized Use Table for IBM Machines” provided at: http://www.ibm.com/systems/support/machine_warranties/machine_code/aut.html (“AUT”). No other workload processing is authorized for execution on an SE.

IBM offers SEs at a lower price than General Processors/Central Processors because customers are authorized to use SEsonly to process certain types and/or amounts of workloads as specified by IBM in the AUT.

NOTE: Performance is based on measurements and projections using IMS benchmarks in a controlled environment. The results that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, the amount of zIIP capacity available during processing, and the workload processed. Therefore, results may vary significantly and no assurance can be given that an individual user will achieve results similar to those stated here. Results should be used for reference purposes only.

The test scenarios (hardware configuration and workloads) used in this document to generate performance data are not considered ‘best performance case’ scenarios. Performance may be better or worse depending on the hardware configuration, data set types and sizes, and the overall workload on the system.

The information contained in this document is distributed on an “AS IS” basis without any warranty either expressed or implied. The use of this information or the implementation of any of these techniques is a customer responsibility and depends on the customer’s ability to evaluate and integrate them into their operational environment. While each item may have been reviewed by IBM for accuracy in a specific situation, there is no guarantee that the same or similar results will be obtained elsewhere. Customers attempting to adapt these techniques to their own environments do so at their own risk.

Disclaimer

Page 4: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation3 20143

Agenda

IMS 13

IMS User Interfaces

IMS Mobile Feature Pack

Big Data and Analytics

Page 5: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation4 2014

IMS Product Investment

Core Capabilities– Reduce path length, contention,

I/O…– Reduce planned outages– zIIP enablement

Big Data & Analytics– Accelerate time to insight

Cloud/Mobile– Rapidly enable/control cloud &

mobile access to IMS resources

Optimize and extend the value of your IMS investment

Expand and empower the IMS talent population

Open interfaces & Java Modern tooling for

administrators, developers and DBAs

Strategic Intent Investment

Continue to deliver the IMS value propositionMinimize cost per txSuperior performance & RAS

Page 6: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation5 2014

IMS 13 delivers…Speed & ScalabilityMeeting your growing

demands with ease and without compromise

Simplicity

With easier integration, access and administration

Affordability

Lowering your cost per transaction

• 117,292 tx/sec on a single IMS System

•Increase workload throughput by up to 130%

•Up to 10% CPU savings for traditional workloads

• Up to 62% CPU savings for Java workloads

•Native SQL support for COBOL

•Dynamic change and version capabilities for DB

•New web interface for administration

Page 7: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation6 2014

IMS 13 Quality Partnership Program

Who participated– Representative cross section of the

IMS install base– 2 Japanese customers + HATC (Japan)– New QPP participant in production

prior to GA

Their results– Highest quality rating in IMS

history– 3 customers in production prior to

GA– 7 customers in production as today

300+ million transactions per day in production already!

Page 8: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation7 2014

£

What our QPP clients are saying about IMS 13

7

“The…IMS 13 migrations have been really easy to implement and have run very smoothly. I have been really impressed by the ease of installing the new version and shipping it to our systems.…..A big ‘well done’ to your team." – United Kingdom-based Bank

“The control region CPU was reduced about 7% per transaction.

The time waiting for the IMS log latch was reduced 90% per transaction.

The number of WADS I/Os per transaction dropped 14%.”

“TI was able to get IMS 13 installed across all of our test and development environments during QPP….This is the fastest we’ve ever installed a new IMS post GA.”

Page 9: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation8 2014

IMS 13

Page 10: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation9 2014

IMS 13 Speed: Record-setting Benchmark

IMS 13 Performance Goal: 100,000 transactions per second using:– a single IMS instance– an IMS Fast Path Credit Card application with updates– TCP/IP to drive the workload through IMS Connect – the latest IBM hardware and software– sustained and repeatable results

Two white papers – www.ibm.com/ims– IMS 13 Performance Evaluation Summary– IMS 13 Fast Path High Volume Transaction Processing

Achieved117,292 tps!

Page 11: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation10 2014

Reducing Total Cost of Ownership

Page 12: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation11 2014

Improving Efficiency in IMS

Goals– Reduce CPU usage to lower the cost per transaction– Improve performance driving IMS over 100,000 transactions per second – Reduce contention to allow for greater scalability as workloads increase

Changes throughout IMS to improve performance, reduce storage usage and reduce CPU used to run IMS– Using more efficient storage services– Improved algorithms – Reducing pathlength– Optimizing frequently used processes– Latch / lock improvements– Storage reductions

– Use of System z hardware functions

Cross-platform focus on reducing mainframe software costs

Page 13: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation12 2014

General TCO Enhancements

IMS Log latch contention reduction

DL/I call path improved SVC directory entry search algorithm

CQS mainline modules changed to use branch-relative branching

Cache efficiency improvements

General instruction optimization

IMS page load service algorithm optimization

IMS dispatcher optimizations

Page 14: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation13 2014

Transaction Manager TCO Enhancements

Shared Queues local first optimization extended for program switch messages

OTMA Early Termination Notification

OTMA Transaction Instance Block (YTIB) chain changed from a single linked list to a hash table

IMS Connect and OTMA storage management enhancements

Streamline OTMA buffer initialization

Page 15: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation14 2014

Database Manager TCO Enhancements

Database Space Management Block Serialization Latch Improvements

OSAM Cross Memory Local Lock (CML) Reduction

IMS cache manager efficiency improvements

Fast Path syncpoint improvements for log contention

Page 16: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation15 2014

Hardware Exploitation

Memory Data Set ENQ Management Exploitation– More efficient memory-based data set ENQ management improves allocation of

large number of data sets– Must be enabled in z/OS ALLOCxx SYS1.PARMLIB member

• SYSTEM MEMDSENQMGMT(ENABLE|DISABLE)

Exploitation of pageable 1M pages– Requires zEC12 with Flash Express and z/OS 1.13 – Provides improvements in dynamic address translation and

usage of translation lookaside buffer (TLB)

System z Integrated Information Processor (zIIP) support– For selected workloads

Page 17: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation16 2014

IMS 13 zIIP Enablement

System z Integrated Information Processor (zIIP) specialty engine support is extended to optionally include some IBM authorized processing

– DRDA Workload - The processing of IMS Connect and Open Database Manager (ODBM) address space Distributed Relational Database Architecture (DRDA) threads for DRDA requests arriving via TCP/IP

– CSLDMI Workload - The processing of ODBM address space threads for requests arriving through the CSLDMI API

– SOAP Workload - The processing of IMS Connect address space SOAP message threads for SOAP messages arriving via TCP/IP

– MSC Workload - The processing of IMS Connect address space Multiple System Coupling (MSC) threads for MSC messages arriving via TCP/IP

– ISC Workload - The processing of IMS Connect address space InterSystemCommunication (ISC) threads for ISC messages arriving via TCP/IP

Page 18: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation17 2014

IMS 13 zIIP Eligible Workloads

Page 19: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation18 2014

IMS 13 Base Measurement Improvements

Page 20: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation19 2014

IMS 13 IMS Connect/OTMA Improvements

Page 21: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation20 2014

IMS 13 Log Latch Contention Reduction

Page 22: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation21 2014

IMS 13 Block Serialization Latch Contention Reduction

Page 23: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation22 2014

IMS 13 Universal Database Driver Type-2 Enhancements

Page 24: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation23 2014

Building on Core Capabilities

Page 25: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation24 2014

Database Versioning

Allows application programs to use different versions of the same physical database Provides the ability to assign user-defined version identifiers to different versions of an IMS

database structure Enables structural changes to a database while providing multiple views of the physical IMS

data to various applications– Applies to Full Function DB, HALDB, Fast Path DEDB– Supports database types: HDAM, HIDAM, PHDAM, PHIDAM, DEDB

Supports the following database structure changes:– Increasing the length of a segment– Adding a new field (or fields) to space at the end of a segment

Benefits– Physical database structure can be changed without having to modify all the existing application

programs using the database – Applications referencing a new physical database structure can be brought online without affecting

applications that use previous database structures– Applications not requiring sensitivity to the new physical database structure can continue to access

the database without any modifications or recompilation

IMS Catalog

Page 26: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation25 2014

Allow structure changes without the need to unload/reload the data– Add a new field (or fields) to space at the end of an existing segment– Increase the length of an existing segment

After changes are made to segment definitions in a DBD• Online Reorganization process is used to alter the online database from the current

structure to the new structure• Database unload / reload not required• INITIATE OLREORG NAME(masterdb) OPTION(ALTER)• TERMINATE OLREORG

• Online Change process is used to activate the changed ACBLIB members in the IMS online system

• Application programs can start using the new database structure

Benefits– Improves IMS HALDB availability – Provides flexibility in rolling database changes into the system

High Availability Large Database (HALDB) Alter

CSL

Page 27: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation26 2014

Allows dynamic change to DEDB Area without unload/reload of the area – Alter physical attributes of DEDB Area - DBD: SIZE, UOW and/or ROOT

• SIZE - Change the CI size of an Area in a DEDB database • UOW and ROOT - Change the Root Addressable and Independent Overflow

parts of DEDB area• Does not support DEDBs defined with Sequential Dependents (SDEPs)

– Change the randomizer used for a DEDB Area - DBD: RMNAME

Provides new DEDB dynamic change utility that runs as IFP utility Only one active DEDB Area can change at a time for a given DEDB

– DEDB Alter runs concurrently for if different DEDBs

Requires the use of a two-stage randomizer allowing Areas to be processed individually

Benefits– Improves DEDB Area availability – Improves management of DEDBs– Eliminate system down time for DEDB definition changes

Fast Path Data Entry Database (DEDB) Alter

Page 28: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation27 2014

Native SQL support for COBOL

Enable SQL for COBOL programs to access IMS database– Support for COBOL in addition to the current Java-based IMS applications– Uses metadata from the IMS catalog

Provide support for dynamic SQL in IMS dependent regions for COBOL– SQL statement converted into 1 or more DL/I calls

Requires COBOL V5.1

EXEC SQLIMS ……SELECT LastName,FirstName,ZipCode FROM TELEPCB1.PHONEBOOK

Benefits– Simplify application programming to allow SQL programmers to access IMS Database in a

similar method to what is used for relational databases– Expand IMS database usage to a wider group of application and database developers

• Take advantage of SQL skills without requiring in-depth IMS database knowledge

IMS Catalog

Page 29: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation28 2014

Increase Number of Concurrent Application Threads

Increase the limit of concurrent application threads from 999 to 4095 Limit applies to the total number of combined:

– Dependent Regions – CICS/DBCTL threads – Open Database Access (ODBA) threads

Allows larger values for the MAXPST parameter for the IMS control region

Benefits– Allows increased capacity and scalability to add more threads to an

existing IMS system– More dependent regions for use with synchronous callout and program

switch

4 Times

More Concurrent

Applications!

Page 30: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation29 2014

User Exit Enhancements

Builds on support added to IMS 11 and 12– Allows a list of exit routines for a given exit point– Allows user exits to be refreshed without an IMS system outage

Enhanced exits for IMS 13 New Exit Type Current Name DescriptionBSEX DFSBSEX0 Build Security Environment Exit LOGEDIT DFSFLGE0 Log Edit ExitLOGWRT DFSFLGX0 Log Write ExitNDMX DFSNDMX0 Non-Discardable Message ExitRASE DFSRAS00 Resource Access Security ExitOTMAIOED DFSYIOE0 OTMA Input/Output Edit ExitOTMARTUX DFSYRTUX OTMA Resume TPIPE Security Exit OTMAYPRX DFSYPRX0 OTMA Destination Resolution Exit

Benefits– Simplifies user exit management– Improves availability

Page 31: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation30 2014 30

IMS Connect Enhancements

Enhancements for ALL users– CREATE commands for PORT and DATASTORE – Reporting of overall health to Workload Manager (WLM)– Configurable TCP/IP backlog (queue) size– Automatically refresh cached userids by listening to RACF events (ENF signals)– Expanded Recorder Trace Records for TCP/IP and SCI interactions for external trace

Enhancements specifically for IMS SOAP Gateway users– Query support for XML Converters – Ability to increase the number of Converters that can be loaded – Automatic restart of the Language Environment when an XML converter ABENDs– Automatic refresh of the BPE User Exit for the XML Adapters after the ABEND limit

(ABLIM) has been reached

Benefits– Provide better resiliency, and make IMS Connect easier to use and manage

CSL

Page 32: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation31 2014

Extending Integration

Page 33: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation32 2014

.NET Access to IMS DB

.NET Data Provider for IMS to enable standard ADO.NET SQL accessdirectly to IMS data from .NET applications– No need for intermediate steps/tools to access IMS databases – SQL access – Transparent to application

Builds on IMS 13 and Open Database support IMS Connect used for TCP/IP connectivity

Benefits– Simplifies application development for .NET environments– Lower cost and complexity– Standards Based

• Enables tools to work without any additional work for IMS

IMS Catalog

CSL

Page 34: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation33 2014

InterSystem Communication (ISC) Over TCP/IP

New option for TCP/IP connectivity for Intersystem Communication (ISC) connections between IMS TM and CICS– Supports both static and dynamic terminals

• Static terminal definitions– SYSGEN stage 1 TYPE, TERMINAL, SUBPOOL macros – DFSDCxxx PROCLIB member

• Dynamic terminal specification– Logon descriptors in the DFSDSCMx or DFSDSCTy PROCLIB member

– IMS Connect used for TCP/IP connectivity• New parameters in the HWSCFGxx configuration member

– IMS and IMS Connect communicate using the Structured Call Interface (SCI) of the Common Service Layer (CSL)

– Requires CICS Transaction Server for z/OS 5.1

Benefits– Provides a strategic protocol alternative to SNA/VTAM

• Allows an all inclusive TCP/IP solution for network

CSL

Page 35: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation34 2014

IMS Callout

Enable IMS transactional or batch applications as Service Requesters– Interoperate with business logic outside the IMS environment– Callout to Java EE apps (EJB and MDB) and Web Services using WebSphere

Application Server and IMS TM Resource Adapter– Callout to Web services providers (e.g. Microsoft .NET) using SOAP Gateway– Callout to other apps and to DataPower

Asynchronous Callout– IMS application invokes external applications without waiting for response.

• Using IMS API – ISRT ALTPCB on OTMA destination• Sent to any OTMA clients, such as IMS Connect or WMQ • Tpipe name specified via DRU exits or OTMA descriptor

– OTMA descriptor only supporting IMS Connect prior to IMS 13 when MQ support added

Synchronous Callout– IMS application invokes external application and synchronously wait for the

response.• Using IMS API - ICAL, added for synchronous callout with timeout capability and

support large messages• Not in two-phase commit scope

Page 36: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation35 2014

Synchronous Program Switch Extend IMS Synchronous Callout to allow DL/I ICAL to invoke another IMS Application

– DL/I ISRT continues to be used for asynchronous program switch OTMA Descriptor enhanced to recognize an IMS transaction destination Java programs can use the Java Message Service (JMS) API for synchronous program

switch

Benefits– Provides a single DL/I call to request a synchronous service regardless of where that service

resides– Simplifies integration and improves usability

ICAL DEST1

ICAL TRANB

TRANAIMS CTL Region

IMS Connect

WebSphereIMS TMRA

IMS SOAPGateway

TCP/IPRYO appl

OTMA

MSG-Q

Destination Descriptor

TYPE(IMSCON)

TRANBGU IOPCBISRT IOPCB

Destination Descriptor

TYPE(IMSTRAN)

12

3

4

56

7

GU, IOPCB

Applications can issue multiple ICALs to different destination TYPEs

Synchronous calloutSynchronous program switch

WebSphereDataPower

Page 37: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation36 2014

OTMA Descriptor Enhancements and Asynchronous Callout to WebSphere MQ via MQ Bridge

OTMA Descriptor enhancements for All destinations – New option to allow exits to be called to override descriptor

OTMA Descriptor enhancements for WebSphere MQ destinations– New TYPE=MQSERIES to define WebSphere MQ destination

• Provides asynchronous messaging support (DL/I ISRT ALTPCB)

Benefits– Eliminates need to write an OTMA user exit to recognize an MQ destination – Simplifies integration and improves usability

IMS Application

WebSphereMQ

IMSOTMA

Page 38: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation37 2014

IMS Java Dependent Region use of ESAF

Allow Java Dependent regions to use the External Subsystem Attach Facility (ESAF)

Allows connections for DB2 to be consistent across all region types Allows access to other subsystems such as WebSphere MQ Eliminates the need to use z/OS Resource Recovery Services (RRS) Attach for

DB2

Benefits– Allows JMS access to MQ from Java– Allows MQ access from COBOL and PL/I– Allows WebSphere Optimized Local Adapter (WOLA) access from COBOL and PL/I– Simplifies external subsystem definitions

WebSphereMQ

IMS JavaApplication

DB2 z/OS

Page 39: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation38 2014

Migration and Coexistence

Page 40: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation39 2014

SECURITY Macro removed from System Definition

System Definition macro SECURITY is no longer used as part of the IMS system generation process

Specify security settings through PROCLIB members RCLASS parameter added to DFSPBxxx

– RCLASS also supported in DFSDCxxx– DFSPBxxx RCLASS parameter value overrides DFSDCxxx if both specified

SECCNT parameter added to DFSDCxxx Other Security settings continue to be specified in DFSPBxxx

– SECLVL parameter is replaced by RCF, TRN and SGN in DFSPBxxx– TYPE parameter is replaced by ISIS in DFSPBxxx

Benefits– Simplified system generation process – Easier method to update security related settings

Page 41: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation40 2014

SECURITY Preconditioning for IMS 11 and 12

New parameters introduced to IMS 11 and IMS 12

Allows preconditioning by specifying new security settings prior to IMS 13– RCLASS added to DFSPBxxx– SECCNT added to DFSDCxxx– IMS 11 - PM48203 / UK74050 ; IMS 12 - PM48204 / UK74051

If specifying RCLASS in DFSPBxxx, the following APARs avoid an unnecessary error message – IMS 11 PM72199; IMS 12 PM73558

Benefits– Simplified migration process – Easier method to update security related settings

Page 42: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation41 2014

Security User Exits removed from Nucleus

User exits DFSCSGN0, DFSCTRN0 and DFSCTSE0 now linked separately, loaded from STEPLIB (if present) into 31-bit storage

New DFS1937I message indicates which user exits have been loaded– Can be used in automation to ensure that exits are being used

DFSCSGN0 now called at IMS initialization – Storage can be obtained and shared with the other exits

Benefits– Simplifies process to customize IMS with user exits– Simplifies writing of user exit DFSCSGN0 – Reduces 24-bit private virtual storage usage

Page 43: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation42 2014

IMS 13 and IMS Enterprise Suite 3.1

Database Management HALDB Alter DEDB Alter Database Versioning Native SQL for COBOL

Transaction Management and Connectivity

Synchronous Program Switch OTMA Descriptor Support for

WebSphere MQ Bridge OTMA Early Termination Notification OTMA Enhancements ISC over TCP/IP IMS Shared Queues Local First Enh IMS Connect SOAP Gateway Enh

Systems Management- Reduce TCO - Increase concurrent applications - Elimination of SECURITY Macro - Standalone Security User Exits- Log Latch Reduction- User Exit Enhancements- JDR support for ESAF- DIAG Command Enhancements- IMS Connect Enhancements- zIIP enablement

IMS Enterprise Suite - .NET Data Provider for IMS DB- IMS SOAP Gateway

Enhancements- IMS UI Enhancements

Page 44: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation43 2014

IMS User Interfaces

Page 45: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation44 2014

IMSISPF

IMS Explorer for Administration (Web Browser)

AdministratorsDevelopers

IMS Explorer for Development (Eclipse)

IMS User Interfaces

Mobile

Page 46: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation45 2014

IMS Explorer for Administration Provide an operational web-based GUI console for IMS system management Single point of control for all IMS address spaces Discovery of IMS systems and their resources Display and operate on resources Immediately react to and resolve issues in the system Integrated with IMS Tools Available as an extension of the Administration Console component of the IMS Tools

Base for z/OS V1.4

Page 47: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation46 2014

IMS Explorer for Development

Visualize IMS database structure as defined by DBD source Change IMS Database and Program Definitions sources Graphically access IMS data using SQL View your mainframe datasets Submit JCL and inspect output in JES IMS Catalog Navigation View IMS Transaction Unit Test Support IMS Mobile Feature Pack Support

AutomaticGeneration

New

Page 48: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation47 2014

IMS Mobile Feature Pack

Page 49: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation48 2014

IMS Mobile Feature Pack

IMS Mobile is a comprehensive solution with which clients can discover IMS assets, model asset metadata, and enable and publish those assets as RESTful services.

Once published, those services are hosted by IMS Mobile for discovery by mobile and cloud Application Developers.

Associated tooling is delivered via IMS Explorer for Development.

Supports IMS 12 and later releases

IMS Mobile Feature Pack became available June 13, 2014

Page 50: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation49 2014

IMS Mobile – Ecosystem and Beyond IMS Mobile complements IBM Worklight for mobile

access with zEnterprise.

z/OS Connect, built on WebSphere Liberty Profile, enables connectivity between IMS and the mobile environment.

z/OS Connect also allows IBM Bluemix systems to easily enable IMS as a provider of Systems of Record to front-end consumers and cloud application providers.

Page 51: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation50 2014

Cloud-based Services Enterprise

SystemsIntegration

Secure and Consistent Enterprise Connectivity for Mobile and Cloud

EnterpriseApplications

EnterpriseData

On-Premise Enterprise APIs Enterprise Transaction Processing

IBM WebSphere

Liberty z/OS Connect

NewNew

CICS,IMS

Batch,WAS

• IBM WebSphere Liberty z/OS Connect – Shipped with WAS, CICS, and IMS• Designed for z/OS – builds on z/OS qualities of service• Unifies z/OS connectors – a common solutions for mobile, cloud, and web• Simplified integration – Hide complexity of connecting to z/OS using REST• Discover z/OS assets – Enhance user experience with System of Record

Cloud APIs

Mobile-Optimized APIs

Systems of Engagement Systems of Record

Page 52: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation51 2014

IBM WebSphere Liberty z/OS Connect (z/OS Connect)Purpose

• Make available to mobile and cloud developers applications and data in a secure, managed, governed and optimized way

• Liberty-based gateway that provides a secure and simple way to discover and call in to assets on z/OS from web/cloud/mobile applications using RESTful services with JSON wire protocol

• Singular approach for System z clients using WAS, CICS, IMS, and DB2

Benefits include• Light-weight and modular providing flexibility to run multiple copies on the same or

different z/OS systems and assign higher/lower priority to specific Liberty servers• Provides ability to standardize on security access for calling in to z/OS applications in all

major environments - CICS, IMS, batch, Unix System Services, and ISV software. Supports SAF-based security integration allowing for individual zConnect services to have unique sets of authorized users.

• Provides ability to track requests from cloud, mobile, web based external requestors using standard z/OS mechanisms like SMF. Fulfills audit/chargeback needs for access to z/OS applications

• Provides ability to prioritize requests within a single Liberty server - based on URIs and z/OS Connect service names – using z/OS WLM.

Page 53: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation52 2014

IMS mobile enablement potential with WebSphere z/OS Connect

MobileDevices

JSON to/from byte[]

Discovery, modeling, deployment tooling

System z

CICSWOLA

IMS ConnectIMSTM

REST services

z/OS Connect

Page 54: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation53 2014

Big Data and Analytics

Page 55: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation54 2014

Cognos 10.2 BI

Certified against IMS 12 using IMS Open Database technology

Universal JDBC driver

Real-time analytics

Page 56: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation55 2014

Big Data ExplorationFind, visualize, understand all big data to improve decision making

Enhanced 360o Viewof the CustomerExtend existing customer views (MDM, CRM, etc) by incorporating additional internal and external information sources

Operations AnalysisAnalyze a variety of machinedata for improved business results

Data Warehouse AugmentationIntegrate big data and data warehouse capabilities to increase operational efficiency

Security/Intelligence ExtensionLower risk, detect fraud and monitor cyber security in real-time

Big Data use cases

Page 57: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation56 2014

Enhancing IMS analytics on System z with Big Data

Much of the world’s operational data resides in IMS

Unstructured data sources are growing fast

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

IMS provides the connectors and the DB capability to allow BigInsights v2.1.2.0 to easily and efficiently access the IMS data source

Allowing you to score business events, track claims evolution, and more

Page 58: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation57 2014

Machine Data Analytics Accelerator

IBM Big Data PlatformSystems

ManagementApplication

DevelopmentVisualization & Discovery

Accelerators

Information Integration & Governance

HadoopSystem

Stream Computing

Data Warehouse

Custom Applications Shrink Wrap Solutions

Health Care Networking Insurance Telco “x2020” “Unity”

IBM Big Data Platform

HadoopSystem

Stream Computing

Data Warehouse

Information Integration & Governance

MDA Accelerator

Telco HealthcareRetailFinancial services

Parsers and Extractors(applications, services, servers and devices )

Federated Discovery, Pattern Discovery, Search, Visualization Tools

for root cause analysis

Generic

Dom

ain

Specific

Tools Client Specific Customizations, Visualization tools (“zInsights”)

IT use cases:• Server, performance, troubleshooting

Business use cases:• Click stream and transaction analysis• Optimize production, advance planning

System z

Page 59: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation58 2014

Watson Explorer : visualization & discovery across all your data sources : “Integration at the glass”

Create unified view of ALL information for real-time monitoring

Identify areas of information risk & ensure data

compliance

Analyze customer information & data to unlock true

customer value

Increase productivity & leverage past work

increasing speed to market

Improve customer service & reduce

call times

WatsonExplorer

Providing unified, real-time access and fusion of big

data unlocks greater insight and ROI

Securely connect to and leverage data stored in DB2 for

z/OS & IMS

Help prioritize your System z big data integration and analytics projects

Page 60: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation59 2014

Seamless IMS integration in Watson Explorer V9 (10/2013)Big Data

ApplicationBig Data

ApplicationBig Data

Application

Web Results

Feeds

Subscriptions

Query RoutingUser Profiles

Authentication/AuthorizationBusiness RulesPersonalization

Display

Application Framework

Indexing and Search Engine

MetadataExtraction

IMS DBs

JDBC connector for IMS

IMS catalog

JDBC connector for IMS

JDBC API used to flow SQL to target IMS database(s) to retrieve all of the information of interest

JDBC metadata discovery APIs used to define the IMS database resource(s) of interest for indexing

Page 61: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation60 2014

System z data consolidation and IDAALeveraging your DB2 & IMS information infrastructure

• Value• Bring the analytics to the z enterprise

• Reduction in data movement solutions• Offer a holistic view of analytics across System z

DB2 DB2 Production Production

DataData

IMSIMSProduction Production

DataData

Potential for IMS

Blending System z and Netezza technologies to deliver unparalleled, mixed workload performance for complex analytic business needs.

1. Extract and transform IMS data2. Define IMS database metadata to a

DB2 for z/OS server and the DB2 Analytics Accelerator

3. Load IMS data into the DB2 Analytics Accelerator

Steps for loading IMS data into IDAA

New White Paper -> Accelerate business insights with IMS transactional data

Page 62: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation61 2014

Looking Ahead - IMS Focus Areas

Agility - Address changing business needs by allowing dynamic change of IMS configuration and IMS resources

Application Deployment/Management – Adapt to changing application requirements by enhancing IMS application capabilities while also simplifying and reducing the business impact of application deployment and management

IMS TM & DB2 – Enhancing or extending the capabilities of IMS transaction manager for robust integration and scalable OLTP with DB2.

Business Growth – Support and adapt to growing business transaction and data volumes that can come as a result of mobilegrowth, mergers, increased usage or new data channels

Infrastructure – Continuing to improve the overall capability, usability and resiliency of IMS

Page 63: IMS Trends and Directions for Montreal RUG 2014 09-11

© 2014 IBM Corporation62 2014

Thank You