ims v13 overview - kiesslich consulting · pdf filehaldb alter dedb alter database versioning...
TRANSCRIPT
Announcements
• IMS 13 QPP announce date: October 3, 2012
• IMS 13 QPP start date: December 14, 2012
• IMS 13, IMS 13 DB VUE & IMS Enterprise Suite 3.1
announce date October 1, 2013
• IMS 13, IMS 13 DB VUE & IMS Enterprise Suite 3.1
GA date: October 25, 2013
HALDB Alter
DEDB Alter
Database Versioning
Native SQL
.NET Access to IMS Data
Synchronous Program Switch
OTMA Descriptor Support for WebSphere MQ Bridge
OTMA Early Termination Notification
OTMA Enhancements
IMS to CICS via ISC over TCP/IP
IMS Shared Queues Local First EnhancementI
Reduce TCO
Increase number of 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
IMS 13 At a Glance
Database Management
Transaction Management and
Connectivity
Systems Management
4
IMS 13 Overview topics
• Lowering TCO
• Openness with Industry Standard Interfaces
• Faster time to market with Database Versioning
• Increased Availability, Autonomics & Dynamic Capabilities
• Integration
• Usability/Simplification
5
Highest Efficiency, Lowest Total Cost of Ownership
6
Reducing Costs
• Major focus on reducing CPU usage
• 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 zEnterprise hardware functions
Benefits:
• Improved performance, lower cost per transaction, reduced cost of ownership
Reduced Cost
7
IMS 13 and Java
• IMS 13 Universal DB Driver delivers:
– Up to 65% CPU time savings for Java applications in the Java
Batch Processing Region
– Up to 17% elapsed time savings for Java applications in the
Java Batch Processing Region
Reduced Cost
8
IMS 13 on IBM zEC12 = Superior Performance
10% CPU reduction, per Full Function transactions, from IMS 12 to IMS 13 for IMS Connect, HALDB workload with 10K clients
31% CPU reduction, per Fast Path transactions, from IMS 12 to IMS 13 for IMS Connect workload using FP 64 bit buffers
Multiple concurrent BMP jobs on IMS 13 complete in up to 50% lower elapsed time compared with IMS 12
Up to 89% reduction in log latch contention on IMS 13; can improve your overall throughput, lowering cost per transaction even more
Cost-effective zIIP solutions for some IMS workloads lower CPU consumption by up to 23 %
Reduced Cost
9
IMS 13: Highest Efficiency, Lowest TCO
• IMS V11: 29,000 trans/sec lab benchmark on IMS 11/z10
• IMS V12: 46,000 trans/sec lab benchmark on IMS 12/z196
• IMS V13: …
Performance, Reduced Cost
10
100,000 transactions per second, on a single IMS system, sustained!
11
IMS 13: Highest Efficiency, Lowest TCO
• IMS 13’s 100,000 trans per second was actually:
117, 292 trans per second
Performance, Reduced Cost
12
Openness with industry standard interfaces
13
IMS 13: Openness with industry standard interfaces
• Native SQL support for IMS COBOL programs
• First non-relational DBMS to provide SQL access from COBOL programs
• Addresses the skills concern for customers
Reduced Time
14
IMS 13: Openness with industry standard interfaces
• IMS Data Provider for Microsoft .NET
• SQL access to IMS data from a .NET environment
• IBM intends, at a future time, possibly via its support and service processes, to make
available IMS Data Provider for Microsoft .NET as part of the IMS Enterprise Suite for
Distributed Systems offering. IMS Data Provider for Microsoft .NET will be designed to provide
standard SQL access to IMS data from Microsoft .NET applications. The intention is to allow
Microsoft .NET applications to transparently and directly read and manipulate IMS data without
the need for intermediate steps and additional tooling to accomplish these tasks.
• 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.
Reduced Cost
Statement of Direction :
15
Faster time to Market with Database Versioning
16
IMS V13: Database Versioning
• Enables structural changes to a database without having to modify
existing IMS applications that access that database
– Structural changes limited to segment length increases
Benefits: Faster time to Market
• 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
Reduced Time
A
B C
A
C B
17
Increased Availability, Autonomics and dynamic capabilities
18
HALDB Alter
• Change the structure of an IMS HALDB without a DB outage
– Increase the length of an existing segment
– Add a new field to space at the end of an existing segment
A
B C
A
C B
Benefits:
• Improves IMS HALDB availability by providing structure changes without
taking the database offline
• Provides flexibility in rolling database changes into the system
Reduced Time
19
DEDB Alter
IMS 13 adds ability to dynamically change DEDB specifications
– Users can dynamically change UOW, SIZE, ROOT and Randomizer while DEDB is online
– New DEDB Alter utility is used to make changes
Benefits:
• Improves DEDB Area availability by providing definitional changes without
taking the Area offline
• Provides flexibility in rolling Area changes into the system
Reduced Time
20
IMS 13: Availability, Autonomics & Dynamic Capabilities
Greater ease-of-use with IMS Connect Enhanced OTMA Autonomics TCO reduction
Reduced Cost
21
Integration
22
InterSystem Communication (ISC) Over TCP/IP
• New option that supports TCP/IP network connectivity for
Intersystem Communication (ISC) connections
– IMS – CICS
– Supports both static and dynamic terminals
– Requires CICS Transaction Server for z/OS 5.1
• Announced October 3, 2012
Benefits:
• Provides a strategic protocol alternative to SNA/VTAM
• Allows an all inclusive TCP/IP solution for networks
Reduced Time
23
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
Benefits:
• Provides a single DL/I call to request a synchronous service regardless of
where that service resides
• Simplifies integration and improves usability
Reduced Time
24
Asynchronous Callout to WebSphere MQ via MQ Bridge
• OTMA Descriptor enhancements
– New TYPE=MQSERIES to define WebSphere MQ destination
• Provides asynchronous callout and messaging support (DL/I ISRT ALTPCB)
IMS
Application WebSphere
MQ IMS
OTMA
Benefits:
• Eliminates need to write an OTMA user exit to recognize an MQ destination
• Simplifies integration and improves usability
Reduced Time
25
IMS Java Dependent Region use of External Subsystem Attach Facility
• Allow Java Dependent regions to use the External Subsystem Attach
Facility
• 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 RRS Attach for DB2
WebSphere
MQ
IMS Java
Application DB2 z/OS
Benefits:
• Allows JMS access to MQ from Java
• Allows MQ access from COBOL and PL/I
• Simplifies external subsystem definitions
• Improved performance for DB2 due to eliminating extra signon processing
Reduced Cost
26
Increase Number of Application Threads
• Increase the limit of concurrent application threads to 4095
• Limit applies to the total number of combined:
– Dependent Regions
– CICS/DBCTL threads
– Open DB Access (ODBA) threads
Benefits:
• Increased capacity and scalability for IMS systems
• Allows vertical growth
• More dependent regions for use with synchronous callout and program switch
4 x the number of applications!
31 dependent regions -
1980 (IMS 1.1.6)
999 dependent regions -
1995 (IMS 5.1)
4095 dependent regions -
2013 (IMS 13)
Reduced Cost
27
Integration with WebSphere DataPower appliance V6.0 (5725-K52)
• IMS Synchronous Callout Support for customers who need a high
performance IMS callout solution.
• IMS Database Support enables a direct connection to an IMS database
through the IMS Universal JDBC Driver. This support allows you to
issue dynamic SQL calls such as basic CRUD operations on the IMS
database.
• IMS Connect Support allows distributed services to drive an IMS
transaction through DataPower.
Reduced Cost
28
Usability/Simplification
29
SECURITY Macro removed from SysGen
• 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
Reduced Time
30
Security User Exits removed from Nucleus
• User exits DFSCSGN0 (Signon/Signoff), DFSCTRN0 (Tran.
Authorization) and DFSCTSE0 (Security Reverification) 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 using a new
parameter that contains the storage address
Benefits:
• Simplifies process to customize IMS with user exits
• Simplifies writing of user exit DFSCSGN0
• Reduces 24-bit private virtual storage usage
Reduced Time
31
User exit enhancements
• Build Security Environment User Exit (BSEX)
• Log Record Edit User Exit (LOGEDIT)
• Logger User Exit (LOGWRT)
• Non-Discardable Messages User Exit (NDMX)
• OTMA Input/Output User Exit (OTMAIOED)
• OTMA Security User Exit (OTMARTUX)
• OTMA Destination Resolution User Exit (OTMAYPRX)
• Resource Access Security User Exit (RASE)
Reduced Time
32
User exit enhancements …
• The enhanced user exit services provide you the ability to:
– Use the REFRESH USEREXIT command to bring in a new copy of a user
exit routine without bringing IMS down
– Use the QUERY USEREXIT command to display information about the
user exit
– Define multiple user exit routines that are called for a user exit type
Benefits:
• Simplifies process for User exit Maintenance
Reduced Time
33
IMS Explorer for Development
• Catalog Navigation View
• A new Eclipse view that will allow you to navigate through the PSBs/DBDs on a given IMS catalog.
• Invoke queries like
– "What DBDs are referenced by this PSB" or
– "What PSBs reference this DBD".
• You will be able to filter the list of PSBs/DBDs using a search dialog wherein you can provide a portion of a resource name and any resource containing that substring will be listed in the search results view.
• Productivity aid for DBAs and IMS application Programmers
Reduced Time
34
IMS Explorer for Development
• Catalog Navigation View
Reduced Time
35
IMS Explorer for Development
• IMS Transaction Unit Test Support
• A Transaction editor, a Test Case editor, and runtime console will be provided.
• The tooling enables the user to define transaction attributes and provide transaction input messages in human readable format.
• The tooling will automatically handle the data conversion and send the message payload to IMS to invoke a given transaction.
• The user will be able to easily duplicate existing test cases and tweak input messages in order to exercise different code paths within their applications.
• Used in conjunction with the Debug tool it will be a powerful tool set for developing, maintaining, and debugging IMS transactions.
• Productivity aid for IMS application programmers
Reduced Time
36
IMS Explorer for Development
• IMS Transaction Unit Test Support
Reduced Time
37
IMS Explorer for Administration
• A replacement for IMS Control Center.
• A web-based console to operate and administer IMS.
• IMS Explorer for Administration can query, start, and stop IMS resources from an
easy-to-use browser interface.
• It can discover IMS resources, show the health of the resources, and show relationships between them.
– Resources can be filtered and context sensitive help is provided.
• IMS Explorer for Administration is available through APAR PM94292 as an extension of the Administration Console component of IBM Tools Base for z/OS, V1.4 (5655-V93).
Reduced Time
38
IMS Resource Relationships
39
Acknowledgements and Disclaimers
Availability. References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates.
The workshops, sessions and materials have been prepared by IBM or the session speakers and reflect their own views. They are provided for informational purposes only, and are neither intended to, nor shall have the effect of being, legal or other guidance or advice to any participant. 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. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this presentation or any other materials. 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 the applicable license agreement governing the use of IBM software.
All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results.
© Copyright IBM Corporation 2013. All rights reserved.
•U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM, the IBM logo, ibm.com, and IMS 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.
40
Thank You!