Performing Analytics on IMS using the DB2 Analytics Accelerator- UG Philadelphia 2015
IMS Continued Modernization - IMS UG May 2013 Philadelphia
-
Upload
ibm-ims -
Category
Technology
-
view
256 -
download
2
Transcript of IMS Continued Modernization - IMS UG May 2013 Philadelphia
© 2012 IBM Corporation
IMS Continued ModernizationNancy Stein – IBM IMS ATS
Philly IMS User Group Meeting – May 2013
© 2012 IBM Corporation2
More than 75% of the world’s
Top 25 companies listed in the Fortune 100 entrust their
business to IMS every second
100
© 2012 IBM Corporation3
IMS – an IBM Icon of Progress
© 2012 IBM Corporation4
IMS – from Apollo to XRF
IMS 360
1972 - 2.2 + 2.3
1968 - 1.0Multi-region architecture
1971 - 1.2 + 2.0
Scheduling by intent on segment type
1973 - 2.4.1MFS3270s
IMS VSVSAMSecondary IndexProgram Isolation
1974 – 1.0 1975 – 1.1Parallel DLIGSAMAppl. Chk/RestartVSAM Buffer Pools
1975 – 1.1.3
MSCSMP
1977 – 1.1.4
Fast PathDBRC
1978 – 1.1.5
FP Mixed ModeAOI and CMD calls
IMS VS
1980 – 1.1.6
31 Dependent regionsISCMSC VTAM
1981– 1.2Data SharingIRLMPROCOPT GON/GOT
1984 – 1.3DASD LoggingDLI SAS
1986 – 2.1VSCR
1987 – 2.2XRF
1970 - 1.1
Scheduling by intent on database
© 2012 IBM Corporation5
IMS – from DBCTL through the present day
IMS ESA
1989 - 3.1
DBCTL
1995 - 5.1Parallel SysplexOTMA
1998 - 6.1Shared Queues999 Dependent Regions
IMSHALDB2000 – 7.1 2002 – 8.1
Common Service LayerGlobal Online Change
2004 – 9.1
HALDB OLRIntegrated IMS Connect
2007– 10
DRDMSC BandwidthGlobal Status Management
2009 – 11Open DBDB QuiesceACBLIC Dynamic AllocationTransaction ExpirationIMS Web 2.0 Solutions
1993 - 4.1
APPCETO
1998 - 4.9PRPQ for Y2K Support
2011 – 12IMS Catalog64-bit FP Buffer ManagementIMS-to-IMS TCPIP SupportFast Path Secondary IndexIMS Enterprise Suite
© 2012 IBM Corporation6
Compatibility• Application compatibility
– Programs written in 1969 still work
– IMS does not require recompiles for new IMS releases
• Database compatibility
– Databases do not require upgrades for new IMS releases
• IMS has allowed users to grow their applications in lieu of forcing major conversions
© 2012 IBM Corporation7
Adaptability • And yet IMS also keeps up with technological trends
– Provides a TCP/IP socket server – IMS Connect• Access to both IMS transactions and databases
– Allows IMS applications to be either clients or servers
– Delivers adapters that run in JEE, SOAP, etc. environments• Pluggable components that provide easy interfaces to IMS resources
– Supports type-2 and type-4 Universal Drivers for access to IMS DB
• Provides application programming interfaces
– Unique to IMS • DL/I calls to access IMS resources: message queues and data
• IMS applications can be written in: COBOL, PL/I, Assembler, C/C++, Pascal, ADA, REXX, Java
– Portable – Java classes and JDBC
© 2012 IBM Corporation8
And … • That is why IMS continues to be current
– Application programs that were written for IMS 5, 10, 15, 20, 40… years ago can continue to run today
• Even when they are now invoked from the web
– Or continue to be invoked from older 3270 devices or emulators
– The same application, without change, can be accessed from any type of connection mechanism or network that can access IMS
• The IMS architecture allows communication components and even database components to be exchanged or replaced
– Without affecting the application in IMS
© 2012 IBM Corporation9
How does a 44-year old software product continue to thrive? • Revolutionary Architecture
– Multiple regions– Separate database definitions from applications– Separate communication management from
applications• Persistent Compatibility
– An application program written in 1969 still runs on IMS 12
– No application recompile or rebind is required after migrating
– No database conversion required after migrating• Programming interface
– Database definitions maintained in DBDs– Application views and access limitations maintained
in PSBs– DLI calls used for both database access and
input/output messaging• Adaptability
“You build sophisticated
structures around IMS……when
you lift the covers on those IMS
transactions, they are incredibly
sophisticated in what they do…..”
Steve Mills, Senior VP and Group Executive Software & Systems, at IBM IMPACT 2012 Conference Keynote
© 2012 IBM Corporation10
15 million gigabytes of production data managed by IMS
$3.0 trillion ($US) per day transferred through IMS, by one customer
200+ million users served every day
375 million accounts…..for one customer
46,000 transactions per second…..on a single IMS system
© 2012 IBM Corporation11
IMS Evolution Strategy
IMS interfaces IMSNew IMS interfaces and models
Installation and
Operations
Application Development
Reporting and
Analysis
Reduce the need for special, in-depth IMS skills
JCLISPFSDSFJES
User ModsUser ExitsDBDGENPSBGENACBGEN
OLCDRDDLI
SQL / JDBC
IMS Tools
Rational
Optim
Cognos
QMF
InfoSphere
J2EE
pureQuery
IMS TM and DB
Databases
Catalog
© 2012 IBM Corporation12
IMS Evolution / Simplification
• Deliver more intuitive UIs and interfaces to talk to IMS
– Eclipse-based tooling for Application Development – IMS Explorer and IMS 12
– SQL support from Java with Open Database in IMS 11
– More operational consistency with z/OS, CICS, DB2, RDz, and Omegamon for IMS
• Reduce planned outages and manual tuning
– Dynamic Database Buffer Pools – IMS 12
– Database Quiesce – IMS 11
– Dynamic allocation of ACBLIB data sets – IMS 11
– Dynamic Resource Definition – IMS 10
– Online Reorganization – IMS 9
© 2012 IBM Corporation13
Rapid IMS Application Development• Extending IMS Application Development to Business Analysts
– Make decisions based on up-to-the-minute data
• Business Rules– ILOG BRMS support – code generation
• Mashups– IMS Web 2.0 Solutions for Mashup Center– Available in V10 for IMS TM feeds, IMS 11 for IMS Data feeds– Ability to easily integrate multiple RESTful services, widgets, data
• COGNOS– Real time query of IMS data– Business analyst with no IMS skill can make decisions based on data supplied by
IMS• QMF
– Real time query and reporting of IMS data– Extended for business intelligence and analytics
© 2012 IBM Corporation14
IMS 11: Distributed Access to IMS Data• IMS Open Database enables access to IMS databases anywhere in the
IMSplex, directly from z/OS and distributed Java clients !!!
– Using industry standard Distributed Relational Database Architecture to communicate with IMS Connect
– Universal DB Resource Adapter• JEE environments (e.g. WebSphere Appl. Server) - JCA 1.5• SQL Calls
– Universal JDBC Driver• Non-JEE and JEE environments• SQL Calls
– Universal DLI Driver• Non-JEE and JEE environments• DL/I call concepts (SSA, command codes)
– RYO (Roll Your Own) • Program sends DRDA commands directly to IMS Connect
IMS Connect becomes the gateway to IMS transactions and data ! Makes Application development and Connectivity much simpler !
© 2012 IBM Corporation15
IMS JDBC Support
• JDBC 3.0• Standard SQL implementation for the SQL subset
– Keys of parent segments are included in tables as foreign keys• Updatable results set• Local commit/rollback support• Metadata discovery API implementation
– Uses metadata stored in the IMS Catalog– Enables JDBC tooling to work with IMS DBs as with DB2 DBs
© 2012 IBM Corporation16
IMS Open Database and DRDA
ODBM
IMS Universal DB Drivers
ApplicationRequestor
TCP/IPClient
z/OS
TCP/IPDDM
IMS Connect
TCPIP
DRDA PORT
IMSSCI
DRDA DLICalls
DRA or
ODBA
DRDAIMS Application Server
IMSDB’s
IMS Connect and Open Database Manager work together as a DRDA server for IMS data
Allows distributed access to IMS databases via TCP/IP using the IMS Universal Database Drivers
Enables use of SQL database query language for access to IMS databases
IMSCAT
© 2012 IBM Corporation17
Open Database Manager - ODBM• z/OS address space
– Common Service Layer component
• Functions– Receives database connection requests from IMS Connect– Translates incoming database requests from DDM protocol to DL/I calls– Manages ODBA or DRA interface to IMS– Sends/receives byte string to/from IMS – Translates responses into DDM protocol for the client– Send results set back to client
• Provides isolation of application containers from IMS– Abend of container during DL/I call does not cause IMS U0113 abend
• Distributed Syncpoint (global transaction) requires RRS on z/OS• Use of z/OS Resource Recovery Services with ODBM is optional
– If RRS=Y (default), ODBM uses ODBA interface– If RRS=N, ODBM uses DRA interface (like the DBCTL interface)
© 2012 IBM Corporation18
IMS Open Database
IMS
WAS for z/OS
Traditional ODBAODBA S
CI
Appl.Java Appl.
DR
A
DB
ODBM
SC
I
OD
BA
or D
RA
Traditional ODBA
Java Appl.
JEE
Java Appl.
Non-JEE
IMS
IMSConnect
SC
I
DR
A
DBODBM
SC
I
TCP
/IP
LPAR
ODBA
SC
I
TCP
/IP
LPARRYO DRDA Appl. TCP/IP O
DB
A or
DR
A
CICS
CCTL
Appl.Java Appl. Traditional DRA
DR
A
CICSAppl.Java Appl.
TCP
/IP
CCTL
WAS
Appl.Java Appl.
JEE
z/OS or distributed
TCP
/IPO
DB
AO
DB
ATC
P/IP Assembler Macro Appl.
Non-JEE (DB2 SP) CAT
CAT
© 2012 IBM Corporation
IMS 12: IMS CATALOG• Metadata about IMS database and program resources, and application
information stored in an IMS PHIDAM/OSAM HALDB database • Database Metadata
– describes a physical database (ie. organization, segments, keys) • Program Metadata
– describes a programs view of the database (ie. access, authority)• Application Metadata
– describes an applications view of the data in the database• Fields not defined in DBD• Arrays and Structures • Field data types and data type conversion • Field redefines• Alternative Field maps for a segment
• New ACBGEN– Generates ACB member & populates the catalog metadata in a single
UOW
19
© 2012 IBM Corporation
IMS Catalog• The IMS catalog is a key component of the IMS growth strategy:
– Trusted IMS source for IMS database, program and application information
– All Universal drivers leverage the IMS catalog• Direct access to IMS metadata in the catalog• No need for separate Java metadata classes on client platforms• Metadata no longer file-system dependent • Catalog metadata is kept up-to-date via new ACBGEN
– Scalable Open Database solutions– Metadata discovery and exchange via IMS Open Database and the
IMS Explorer for Development– Broad IMS integration with the IBM and ISV portfolio of tools (Optim
Development Studio, Rational Asset Analyzer, InfoSphere Data Architect, etc)
20
© 2012 IBM Corporation
IMS Enterprise Suite
• IMS Enterprise Suite is a product within the IMS SOA Integration Suite – IMS Enterprise Suite DLIModel utility plug-in – IMS Enterprise Suite SOAP Gateway– IMS Connect APIs– Java Message Service (JMS) API– IMS Enterprise Suite Explorer for Development
• IMS Explorer V2.1.1.3 download available as of 06-22-2012• IMS Explorer V2.2 download available as of 11-02-2012
• Supported with SMP/E and the IBM Installation Manager• Supports IMS 10, 11 and 12
21
© 2012 IBM Corporation
IMS Enterprise Suite Explorer for Development• Visualization and editing of IMS DBD and PSB definitions
– Provides graphical editors to: • Display IMS database hierarchical structures• Display/create/edit PSBs• Change/add fields on a DBDs
– Import Cobol CopyBooks and PL/I Structures to a database segment*– Generate DBD and PSB source
• Easily access IMS data using SQL statements– Leveraging IMS Universal JDBC driver
• Access the IMS Catalog for metadata discovery• Connectivity to the z/OS system
– Browse a Data Set and submit JCLs – Import / export DBD and PSB source from a data set to IMS Explorer
• Supports cross-product integration:– IBM® Rational® Developer for System z® – IBM Optim™ Development Studio – IBM Problem Determination Tools Plug-ins for Eclipse
Simplify IMS application development tasks
*Requires IMS-ES 2.2 or RDz 822
© 2012 IBM Corporation23
IMS Explorer: Revolutionizing IMS application development
Graphical interface to easily access and manipulate IMS data using standard SQL
Graphically-driven editors to display and update IMS program and database definitions
Generate SQL to
access IMS data
See database
relationships
Change DBD and
PSB definitions
© 2012 IBM Corporation
IMS EXPLORER HANDS-ON LAB
24