IMS DB Futures - IMS UG September 2012 Midwest Springfield
-
Upload
ibm-ims -
Category
Technology
-
view
587 -
download
3
description
Transcript of IMS DB Futures - IMS UG September 2012 Midwest Springfield
© 2012 IBM Corporation2
Agenda
IMS modernization overview
� IMS database solutions
� Portfolio integration
� Modeling and query generation
� DataPower and IMS connectivity
© 2012 IBM Corporation3
IMS Modernization Solutions
Java
IMS
z/OS
TCP/IP
WebSphereTM/DB access
IMS TM and DBResourceAdapters
DataPower
IMS SOAPGateway
TM access
Universal JDBCdriver
DB access
Universal DLIdriver
Java API
TM AccessRYO
C API
Web 2.0(Mashup Center)
Catalog
IMS access anywhereStandards-based data server and TMOpen systems accessWeb services
© 2012 IBM Corporation4
IMS Open Database
Solution statement
� Extend the reach of IMS data– Offer scalable, distributed, and high-speed local access to IMS database resources
Value
� Business growth– Allow more flexibility in accessing IMS data to meet growth challenges
� Market positioning
– Allow IMS databases to be processed as a standards-based data server
Key differentiators
� Standards-based approach (Java Connector Architecture, JDBC, SQL, DRDA)
� Solution packaged with IMS
Enables new application design frameworks and patterns
� JCA 1.5 (Java EE)
� JDBC
© 2012 IBM Corporation5
IMS Open Database
DRDA over TCP/IP
DRDA over TCP/IP
z/OS
IMS
IMS
z/OS
Open Systems (e.g.; LUW)
JavaEE
JDBC
DLI
Universaldrivers DRDA over TCP/IP
Universaldrivers
JavaEE
DLI
JDBC
Direct
© 2012 IBM Corporation6
Solution highlights – JEE deployment
Universal DB resource adapter
� JCA 1.5– XA transaction support
• Manage multiple datasource connections in a single UOW
– Local transaction support• Manage multiple datasource connections each in their own UOW
– Connection pooling• Pool released connections for future use
– Connection sharing
– Multiple programming models available• JDBC (Universal JDBC driver incorporated)
• CCI with SQL interactions
• CCI with DLI interactions
© 2012 IBM Corporation7
Solution highlights – JDBC
Universal JDBC driver
� Significant enhancements to classic JDBC offered in IMS 9 and IMS 10– Standardized SQL support
– XA transaction support (type 4)
– Local transaction support (type 4)
– Concurrency control• Control release of distributed locks
– Updatable result set support
– Batching support• Fetch multiple rows in a single network call
– JDBC metadata discovery support
Standard SQL and metadata discovery enables significant integration opportunities for IMS
© 2012 IBM Corporation8
Solution highlights – DLI
Universal DLI driver
– Java implementation of DL/I API
– Complete DL/I support for database access
– All IMS command codes supported
– Can mix usage of JDBC and DLI drivers in the same application• SQL cannot always express what DLI offers
© 2012 IBM Corporation9
Open Database and the Universal drivers
Deep synergy with the IMS catalog
– Direct access to IMS metadata in the catalog
– Virtual and cloud deployment capabilities
• No longer file-system dependent for metadata– Industry-leading data type support
• Complex and flexible
– Mapping support
Deep synergy with Java z/OS and z196
– Significant performance improvements
– Continued partnership with Java z/OS lab
Continued SQL standardization and support
– Including similar connection parameters as DB2 for commonality across IBM
drivers
– More to come
Continued integration across the IBM portfolio
© 2012 IBM Corporation10
Data types
Data types have multiple metadata elements– Application data type
• Universal drivers use application data type to present data to clients– Physical data type
• Universal drivers use physical data type to marshal/unmarshal data to and from the database– Example
• Application data type is DECIMAL(10,2) [decimal with precision 10 and scale 2]• Physical data type is a signed packed decimal (AD community doesn’t need to know this)
New data type support– Structs (nested n levels with no constraint on element data types)
• Accessed via SQL and DLI– Arrays (nested n levels with no constraint on element data types)
• Accessed via SQL and DLI– User-defined
• Name of UDT can be defined to the catalog and intended to be used at runtime by Universal drivers to marshal/unmarshal data
• Can be part of a Struct or Array element
© 2012 IBM Corporation11
Maps
Mapping support– A Map is metadata that describes how a field (or set of fields) are mapped for a
particular segment instance– Metadata captures the various cases and for each case defines the set of fields
to be used for that case– Maps can be defined to the catalog– Example
•Insurance segment mapped multiple ways depending on value of a ‘Policy Type’ field
-----555 Disk Drive
Way, 95141500K5Single FamilyH
Red2K1989EscortFord----M
ColorValueYearModelMakeAddressValueRoomsProperty TypePolicy Type
© 2012 IBM Corporation12
Additional enhancements
� SQL– FETCH FIRST <n> ROWS ONLY– INNER JOIN <table2> ON <table1.col1> = <table2.col2>
� Connection properties– currentSchema– maxRows– fetchSize– Tracing
• traceFile, traceFileAppend, traceDirectory, traceLevel
� Variable length segment support– VL segments contain a two byte length (LL) field that will identify the size of the
segment instance– Universal Drivers are now sensitive to the LL field of a VL segment and will manage the
IO area of the segment instance on all CRUD calls
© 2012 IBM Corporation13
IMS Open Database environment
LPAR Az/OS
IMS DBCTL
IMS
PC
Open Systems
Universal
DB
Resource
Adapter
J
C
A
1.5
T
C
P
I
P
WebSphere
S
O
A
P
LPAR B
LPAR C
XCF
DRDA
IMS Connect
T
C
P
I
P
SCI
SCI
O
D
B
A
ODBM
© 2012 IBM Corporation14
IMS Open Database environment
Universal
DB
Resource adapter
J
C
A
1.5
T
C
P
I
P
WebSphere
S
O
A
P
LPAR Az/OS
Open Systems
LPAR C
IMS DBCTL
IMS
PCSCI
O
D
B
A
DLI
JDBC
RYO DRDA Appl.
IMS DBCTL
IMS
PCSCI
O
D
B
A
IMS Universal drivers
LPAR A
IMS DBCTL
IMS
PCSCI
O
D
B
A
ODBM
IMS Connect
T
C
P
I
P
SCI
ODBM
ODBM
LPAR B
XCF
WAS z/OSUniversal
DB Resource
adapter
J
C
A
1.5
T
C
P
I
P
OD
BA
PCSCI
Traditional ODBA
DLI
JDBC
IMS Universal driversTraditional ODBA
JEE
Java SE
DRDA
© 2012 IBM Corporation15
IMS 12 catalog
� 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 (OptimDevelopment Studio, Rational Asset Analyzer, InfoSphere Data Architect, etc)
ACBLIB
Catalog
PSB
source PSBLIB
DBD
source DBDLIB
PSBGEN
DBDGEN
ACBGENIMS Explorer
IMS
© 2012 IBM Corporation16
IMS catalog – intended support
PSBLIB
Catalog
• IMS DB changes start with catalog
• IMS loads resource information from catalog
• ACBLIB/PSBLIB/DBDLIB updates will be the by-product of catalog updates
• Tools that use these libraries can continue to operate, but should
migrate to catalog
• PSB and DBD source can still be optionally generated from PSBLIB and
DBDLIB
IMS ExplorerDDL
ACBLIB
DBDLIB
PSB
source
DBD
source
IMS
© 2012 IBM Corporation17
Dynamic database - Data Definition Language
� 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
� It is our intention to offer this type of dynamic definition for IMS
© 2012 IBM Corporation18IMS
ISPF
IMS Explorer for Administration
(Web Browser)
AdministratorsDevelopers
IMS Explorer for Development
(Eclipse)
IMS Modernization
© 2012 IBM Corporation19
IMS Explorer for Development
© 2012 IBM Corporation20
IMS Explorer For Development
© 2012 IBM Corporation21
IMS Explorer
• Catalog integration
• zExplorerintegration
• Advanced data type support
• Logical & physical modeling
• Resource discovery
• Model sharing
InfoSphere DataArchitect
Database Modeling & Creation
• Data privacy
• Data management
Optim Designer
Governance
• Operational BI
• Extending value of IMS data
Cognos 10 BI
Analytics
Data Studio
• SQL authoring
• pureQuery
• Query explain
Access
IBM Portfolio Integration 2012-2013
•Physical modeling & resource discovery
•Database resource creation
© 2012 IBM Corporation22
Premier System z web service enablement through DataPower SOA appliances
IBM cross-brand initiative
� Deep synergy between DataPower, System z, Rational and Common Transformation
tooling to support DataPower as the premier System z gateway for IMS, CICS and DB2
� Intended support for IMS DB access
� Intended support for top-down service approach for inbound and outbound IMS
transactional requests
XI52
XI50z
DataPower Processing Flow
Protocol transformation
WS Monitoring
Native z transports
Transaction distribution
Network-level HA and distribution
RACF-centric security
IMS
CICSDB2
© 2012 IBM Corporation23
Java dependent region deployment
Java dependent region resource adapter
� Allows new IMS transactions (JMP, JBP) to be written in Java and managed by the IMS transaction manager
� Complete Java framework for applications operating in an IMS container– Message queue processing
– Program switching
• Deferred and immediate
– Transaction demarcation
– GSAM support
– Additional IMS call support necessary for IMS transactions
• INQY
• INIT
• LOG
• Etc
� Shipped with type 2 Universal drivers
© 2012 IBM Corporation24
.NET access to IMS DB – intended support
� Solution
– Ability to directly access IMS Databases from .NET applications using
SQL
� Value
–Simplifies application development for .NET environments
–Lower cost and complexity
• No need for intermediate steps/tools to access IMS databases
• SQL access
• Transparent to application
– Standards Based
• Enables tools to work without any additional work for IMS
© 2012 IBM Corporation25
Native SQL – intended support
� Solution
–Enable SQL as API for COBOL and PL/I programs to access IMS database
• Support for COBOL and PL/I in addition to the current Java-based IMS applications
–Provide native SQL processing in IMS
• Still perform DLI call processing underneath
� Value
–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
© 2012 IBM Corporation26
Alter for IMS HALDB – intended support
� Solution
–Allows IMS HALDB structure changes without unload/reload of the database
• Adding a field to a segment
• Increasing a field length
• What about adding a new segment type?
–Built on HALDB Online Reorganization
� Value
–Improves IMS HALDB availability by providing structure changes without taking the database offline
–Provides flexibility in rolling database changes into the system
A
B C
A
CB
© 2012 IBM Corporation27
� Solution
–Allows DEDB Area changes without unload/reload of the area
• Dynamic change for UOW and ROOT parameters of an existing Area
• Split/Add Areas
–Provides new DEDB dynamic change utility
• Performs changes while the Area is online
� Value
–Improves DEDB Area availability by providing definitional changes without taking the Area offline
–Provides flexibility in rolling Area changes into the system
Alter for IMS Data Entry Database – intended support
© 2012 IBM Corporation28
Database versioning – intended support
� Solution
–Allows programs to use different versions of the same database
• Provide the support for multiple views of the physical data
• Allows old applications to remain unchanged when the physical structure of the database changes
• Make database structure changes and only compile programs referencing changed fields/segments
• Requires the catalog
• Applies to HALDB, Full Function DB, Fast Path DEDB
� Value
–Provides greater flexibility in rolling out new versions of programs and databases
–Allows new programs to get out faster without waiting for all programs to be updated to the new database structure
© 2012 IBM Corporation29
Database versioning – intended support
CBA
BINARY(8)CHAR(8)CHAR(4)
Base version
Version 1
Add field to end of segment
Version 2
Increase size of field D
D
BINARY(4)
CBA
BINARY(8)CHAR(8)CHAR(4)
D
BINARY(8)
CBA
BINARY(8)CHAR(8)CHAR(4)
© 2012 IBM Corporation30
Enhanced query capabilities – intended support
� Allow predicate processing of every field in a segment–Catalog contains all segment information–Every segment position searchable–No longer require field to be defined to IMS in the DBD–SQL and DLI support
• Catalog contains metadata for all fields (columns) in a segment (table)
� Extend GUR support (get unique record) to all database types–Retrieve an entire IMS database record in a single request
• XML or binary output possible