Presentation is loading. Please wait.

Presentation is loading. Please wait.

IMS 13 Quick Look GSE BENELUX IMS User Group Meeting

Similar presentations


Presentation on theme: "IMS 13 Quick Look GSE BENELUX IMS User Group Meeting"— Presentation transcript:

1 IMS 13 Quick Look GSE BENELUX IMS User Group Meeting
June Antwerp Belgium Steve Nathan -

2 Disclaimer © Copyright IBM Corporation 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. 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, 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

3 Acknowledgement This presentation was originally prepared by Diane Goff IBM Advanced Technical Solutions (ATS) Additional material is from Alison Coughtrie European IMS Architecture Team

4 Agenda Status of IMS Versions Prerequisites, Migration, Coexistence
System Enhancements Transaction Manager and Connectivity Enhancements Database and DBRC Enhancements

5 Introducing IMS13 – Smarter Than Ever!
IMS 12 Overview Introducing IMS13 – Smarter Than Ever! IMS 13 Quality Partnership Program Announced on October 3, 2012 Program began on December 14, 2012 QPP participants have installed and are testing IMS 13 General availability of IMS 13 will be announced at a later date. Announcement Letter available on ibm.com Current Status 12 customers in IMS 13 QPP in 2013 All customers through Sandbox production 5 customers have IMS 13 in AD environments 3+ targeted for full production by GA Copyright IBM Corp. 2011

6 Status of IMS Versions IMS Version 9 IMS Version 10 IMS Version 11
IMS 12 Overview Status of IMS Versions IMS Version 9 End of service was November 7, 2010 IMS Version 10 Generally available on October 26, 2007 End of service was November 5, 2012 IMS Version 11 Generally available on October 30, 2009 Will be withdrawn from Marketing on September 9, 2013 End of service has not been announced IMS Version 12 Generally available on October 28, 2011 IMS Version 13 Announced on October 3, 2012 Currently in QPP program General availability has not been announced Copyright IBM Corp. 2011

7 Software Prerequisites
IMS 12 Overview Software Prerequisites Minimum software level prerequisites z/OS V1R13 (5694-A01) RACF (included in separately orderable SecureWay Security Server), or equivalent, if security is used High Level Assembler Toolkit Release 5 ( ) APAR OA39392 / PTF UA66823 is required for z/OS 1.13 for IMS V13 IRLM 2.3 if the IRLM is used * subject to change z/OS 1.13 is the base operating system level for IMS 13. Copyright IBM Corp. 2011

8 Software Prerequisites ...
IMS 12 Overview Software Prerequisites ... Minimum software levels for optional functions Java Dependent Regions requires JDK 6.0.1 ISC TCP/IP requires CICS 5.1 Depending on the environment, the IMS Universal Drivers require: IBM JDK or later DB2 V9.1 or later WAS V7 or later CICS V4.1 or later DB Versioning requires implementation of the IMS Catalog * subject to change Copyright IBM Corp. 2011

9 Software Prerequisites ...
IMS 12 Overview Software Prerequisites ... Minimum software levels for optional functions ... IMS 13 supports interactions with DB2: Versions 9, 10 CICS: Versions 3.2, 4.1, 4.2, 5.1 CICS 5.1 (newly announced) is required for ISC TCP/IP support Requires z/OS 1.13 MQ for z/OS: Versions V7.0.1, V7.1 Note V6 EOS was September 2012 7.01 introduced MQ message expiry interfacing with IMS transaction expiration 7.1 enhanced the expiry support and support for OTMA resource monitoring protocol messages * subject to change Copyright IBM Corp. 2011

10 Hardware Prerequisites
IMS 12 Overview Hardware Prerequisites IMS 13 runs only on 64 bit processors running in z/Architecture mode Processors must also support the Long-Displacement Facility of the z/Architecture ESA mode is not supported For a list of z/Series machines see:  z900 machines must be at GA2 level (microcode level 3G or later) The hardware prerequisite for a 64 bit processor running in z/Architecture mode is not new for IMS. Copyright IBM Corp. 2011

11 Hardware Prerequisites ...
IMS 12 Overview Hardware Prerequisites ... Sysplex Data Sharing (including Data Caching and VSO Data Sharing) Coupling Facility (CF) level 9, or later Shared Queues and Shared EMH support Coupling Facility level 9 or later System-managed CF Duplexing CF level 12, or later and bidirectional CF to CF links EAV support for non-VSAM data sets EAVs are supported on DS8000 at microcode level R4.0 via bundle (Sept 2008) or higher Copyright IBM Corp. 2011

12 Supported Migrations and Coexistence
IMS 12 Overview Supported Migrations and Coexistence IMS 12 to IMS 13 Upgrade RECONs from IMS 12 to IMS 13 Databases are compatible Application programs are compatible IMS 11 to IMS 13 Upgrade RECONs from IMS 11 to IMS 13 Check Release Planning documentation at GA for additional prerequisites/coexistence/migration items Copyright IBM Corp. 2011

13 IMS 13 System Enhancements
IMS 12 Overview IMS 13 System Enhancements IMS Connect Enhancements Concurrent Application Threads Reduced Total Cost of Ownership (TCO) IMS Command Enhancements IMS CQS Enhancement IMS DRD Enhancement IMS User Exit Enhancements IMS Security Enhancements /DIAG Command Enhancements There are nine enhancements for the IMS Systems component of IMS 13.. Copyright IBM Corp. 2011

14 IMS Connect Enhancements
IMS 12 Overview IMS Connect Enhancements XML Converter Enhancements Auto-restart of the Language Environment (LE) Expanded Recorder Trace Records Use of RACF Event Notification Facility (ENF) Support for cached RACF UserIDs (UID) Reporting of overall health to Workload Manager (WLM) Configurable TCP/IP backlog (queue) size IMS Connect can now be used by both IMS TM users and IMS DBCTL users since the Open Database enhancement in IMS There are six enhancements for IMS Connect in IMS 13. Copyright IBM Corp. 2011

15 XML Converter Enhancements
IMS 12 Overview XML Converter Enhancements Support for extending the current limit of 100 up to for the maximum number of XML converters New IMS Connect configuration parameter MAXCVRT ADAPTER(…, MAXCVRT= value) IMS 12 (PM64487 / UK79728) Capability to view converters that are currently loaded New Type-2 Command: QUERY IMSCON TYPE(CONVERTER) Requests detailed information about XML converters in IMS Connect Benefits Enhances the flexibility of converter usage Directly impacts IMS Soap Gateway environments The IMS Connect XML Adapter uses COBOL or PL/I converters to perform the transformation from XML to byte data and vice versa for the IMS SOAP Gateway functionality. The Converters are generated from RDz tooling and loaded in the IMS Connect address space. The IMS application COBOL copybook and Web Service XML Schema are used to generate the Converters. The IMS Soap Gateway was originally introduced in IMS V9 as part of the Integration Suite and is currently distributed with the IMS Enterprise Suite as the IMS ES Soap Gateway. The previous maximum of 100 XML Converters that could be loaded at any one time into an IMS Connect instance has been increased to This maximum is controlled through a new MAXCVRT configuration parameter in the ADAPTER statement of the IMS Connect HWSCFGx configuration member of PROCLIB. In IMS V12, the WTOR, z/OS Modify and the Type-2 UPDATE IMSCON TYPE(CONVERTER) commands could all be used to request a refresh of a converter file that was loaded in IMS Connect. IMS V13 has enhanced the Type-2 command interface with a new command to request detailed converter information. Additionally, the output from existing commands that display IMS Connect configuration information, e.g. (WTOR) VIEWHWS, (z/OS MODIFY), and Type-2 QUERY, have been enhance to also show the current and maximum number of XML converters. Both enhancements impact the flexibility of converter usage. Copyright IBM Corp. 2011

16 Auto-restart of the Language Environment (LE)
IMS 12 Overview Auto-restart of the Language Environment (LE) Automated mechanism to reinitialize the Language Environment when an XML converter ABENDs Without restarting IMS Connect Converters will be reloaded as they are needed Automatic refresh of the BPE User Exit for the XML Adapters (HWSXMLA0) after the ABEND limit ABLIM has been reached Benefit Improved efficiencies during error conditions Eliminates IMS Connect restart and user interactions IMS Connect makes use of the Language Environment (LE) as well as the IMS Base Primitive Environment (BPE) to run the XML Converters when requested by IMS SOAP Gateway. Prior to IMS V13, when one of the XML Converters ABnormally ENDs (ABENDs) it cannot be reused but an issue with LE causes IMS Connect to run the bad XML Converter a total of three times before the LE can be successfully terminated. In order to restart the LE environment, IMS Connect has to be restarted. This IMS V13 enhancement provides an automated mechanism for restarting the LE after one of the XML Converters ABENDs. This means that previously loaded converters will be reloaded the next time they need to be used. IMS Connect also automatically make a request to BPE to refresh the XMLADAP BPE User Exit after the ABEND limit (ABLIM), specified in BPE’s EXITDEF() statement for HWS USER EXIT DEFINITION, has been reached. This auto refresh allows IMS Connect users to keep IMS Connect running without having to manually refresh the XMLADAP BPE User Exit for IMS Connect after the ABEND limit has been reached. Keep in mind that if the ABLIM specified is a small integer, the XMLADAP user exit will be refreshed more frequently during multiple ABENDs. Also, BPE captures a dump for the very first ABEND that takes place and for the first ABEND after the XMLADAP BPE User Exit for IMS Connect is refreshed. Copyright IBM Corp. 2011

17 Expanded Recorder Trace Records
IMS 12 Overview Expanded Recorder Trace Records The Recorder trace records have been expanded to: Capture entire messages sent and received using: All TCP/IP communications Including DRDA sockets and ISC TCP/IP SCI (OM, ODBM, MSC, and ISC communications) Requires a Trace Level HIGH and use of the external trace data set UPDATE TRACETABLE NAME(RCTR) OWNER(HWS) LEVEL(HIGH) EXTERNAL(YES | NO) Benefits Improved diagnostics and problem determination IMS Connect V12 introduced new Recorder Trace Records that made use of BPE’s External Trace Tables. In IMS Connect V13, these trace records have been expanded to capture the entire messages sent and received on the DRDA sockets as well as all messages sent and received to/from OM and ODBM via SCI. Changing the BPE trace level from MEDIUM to HIGH is the trigger to write the enhanced trace records. Additionally they must be written to the external trace data set since they will not be written to the fixed size HWSRCDR trace data set. Copyright IBM Corp. 2011

18 RACF Event Notification Facility (ENF) Support
IMS 12 Overview RACF Event Notification Facility (ENF) Support Background IMS Connect V12 provided the option to cache RACF UserIDs (UIDs) along with a command to refresh them IMS Connect V13: RACF ENF Support for Cached UserIDs (UID) Automatically refreshes cached UIDs by listening to RACF events (ENF signals) indicating that a change has been made to a UID NOTE: This function applies only when RACF UID caching has been enabled in IMS Connect Benefit Allows IMS Connect to listen for certain RACF events indicating that a change has been made to a specific UserID Avoids manual intervention IMS Connect V12 enabled RACF UserID Caching by defining the parameter UIDCACHE=Y in the HWS statement in the HWSCFGx configuration or via the type-2 command UPDATE IMSCON TYPE(CONFIG) SET(UIDCACHE(ON)); the WTOR command SETUIDC OFF; or the z/OS command UPDATE MEMBER TYPE(IMSCON) SET(UIDCACHE(OFF)). Additionally, these cached userids could be refreshed based on an aging value or manually by issuing: a WTOR (xx,REFRESH RACFUID..), a z/OS Modify (F hws,UPDATE RACFUID NAME..OPTION(REFRESH)) or a Type-2 command (UPDATE IMSCON TYPE (RACFUID)). The RACF Event Notification Facility (ENF) Support for Cached UserIDs (UID) allows notification of changes to UIDs affected by the following RACF commands: CONNECT, REMOVE, and ALTUSER REVOKE. IMS Connect has been enhanced to listening for the type 71 ENF signals produced by these RACF commands, and act on that signal to refresh the affected UID. This new capability is applicable only when RACF UID caching has been enabled in IMS Connect. Copyright IBM Corp. 2011

19 Reporting of Overall Health to WLM
IMS 12 Overview Reporting of Overall Health to WLM WLM (Workload Manager) Health Report New function to automatically report the overall health of IMS Connect Allows Sysplex Distributor to use and take into account this information for workload balancing Benefit Allows WLM to know when resources are constrained or available Minimizes the possibility of Sysplex Distributor assigning work that IMS Connect is unable to handle Workload Manager (WLM) provides facilities that allow servers to indicate their health back to WLM. This health information can be used by the Sysplex Distributor and taken into account when connection requests are to be routed to a server. IMS Connect V13 takes advantage of the facilities provided by WLM to inform WLM of its overall health. As the health of IMS Connect deteriorates or improves, IMS Connect will notify WLM accordingly so that WLM has the most recent health information available for use by the Sysplex Distributor. Sysplex Distributor uses the health of each server when the distribution method has been set to SERVERWLM in the VIPADISTRIBUTE statement of the TCP/IP profile. . Copyright IBM Corp. 2011

20 Configurable TCP/IP backlog (Queue) size
IMS 12 Overview Configurable TCP/IP backlog (Queue) size New parameter TCPIPQ Allows users to configure the length of the queue in TCP/IP for connection requests that have not yet been assigned a socket. Connection requests are held on this queue until IMS Connect can assign a socket Overrides the default which is equal to the maxsoc value Actual value used is the smaller of IMS Connect’s TCPIPQ value and SOMAXCONN in TCP/IP Benefit Provides a configurable option to increase the backlog queue size in TCP/IP When IMS Connect starts up, it establishes a TCP/IP listening socket on every port that is configured for its use. When these listening sockets are established, IMS Connect also sets the corresponding TCP/IP backlog or queue value to be equal to the MAXSOC value for IMS Connect. (Note that the default for MAXSOC, if not specified, is 50). This backlog or queue is the number of connection requests that can be queued in TCP/IP while waiting for IMS Connect to assign sockets to them, e.g., during peak processing times. This means that requests up to this value can be queued in TCP/IP without their connections being rejected pending IMS Connect action. Note that if IMS Connect’s value is higher than that specified for SOMAXCONN in the TCP/IP profile, the smaller of the two values (SOMAXCONN or MAXSOC) is used by the TCP/IP stack. IMS Connect V13 adds a new parameter to the configuration member for IMS Connect. This new parameter supports a value that can be different than MAXSOC for the TCP/IP backlog. The same rules, however, with respect to SOMAXCONN in the TCP/IP profile continue to apply. If TCPIPQ is greater than SOMAXCONN, the number used is the one defined for SOMAXCONN. The new TCPIPQ parameter value should therefore be coordinated with the value in the SOMAXCONN. See the z/OS Communications Server: IP Configuration Reference for details. If TCPIPQ is not specified in the IMS Connect configuration definition, then the default used is the value specified in MAXSOC. Copyright IBM Corp. 2011

21 Overall Value of IMS Connect Enhancements
IMS 12 Overview Overall Value of IMS Connect Enhancements Enhanced usability while providing better performance and diagnostics Increased resiliency to Abnormal Ends (ABENDs) Improved usability and manageability The IMS 13 IMS Connect enhancements focus on improving many aspects of using IMS Connect. Copyright IBM Corp. 2011

22 Concurrent Application Threads Enhancement
IMS 12 Overview Concurrent Application Threads Enhancement Partition Specification Table (PST) used for Active dependent regions (MSG/BMP/IFP/JMP/JBP) CICS/DBCTL threads Open Database Access threads Customers continue to require more PSTs! 15 dependent regions ? (IMS 360) 31 dependent regions (IMS 1.1.6) 999 dependent regions (IMS 5.1) 4095 dependent regions (IMS 13) Related parameters MAXPST= PST= MAXTHRDS= for ODBM MAXTHRDS=, MINTHRDS= for DBCTL IMS systems continue to grow, needing more dependent regions to process new workloads associated with usage of open database, internet connectivity options, and applications with longer dependent region residency times. IMS 13 is quadrupling the maximum number of PSTs (Partition Specification Table) that can be running concurrently in a particular IMS image. Copyright IBM Corp. 2011

23 MAXPST= parameter Used in DBC, DCC, and IMS procedures
IMS 12 Overview MAXPST= parameter Used in DBC, DCC, and IMS procedures Specifies the maximum number of PSTs for an online IMS control region Default is 255 (no change) Maximum value is 4095 in IMS 13 (quadrupled) Controls maximum number of Active dependent regions (MSG/BMP/IFP/JMP/JBP) CICS/DBCTL threads Open Database Access threads Reducing MAXPST= requires a cold start MAXPST= is the main parameter for specifying the number of PSTs. The maximum value in IMS 13 is now 4095. Copyright IBM Corp. 2011

24 Benefits of the Concurrent Thread Enhancement
IMS 12 Overview Benefits of the Concurrent Thread Enhancement Customers can now have increased capacity/scalability for their IMS systems Larger capacity for mergers/acquisitions Without having to add more IMS images Increased workloads with latest zEnterprise hardware Room for vertical growth More regions for IMS 13 synchronous program switch function, also synchronous callout, distributed syncpoint/etc. Longer region occupancies MAXPST should no longer be a limiting factor in IMS growth The concurrent thread enhancement will allow IMS systems to be able to handle increasing workload demands. Copyright IBM Corp. 2011

25 Reduced Total Cost of Ownership
IMS 12 Overview Reduced Total Cost of Ownership Cross-platform focus on reducing mainframe software 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 Reducing mainframe software costs is a major focus for major software components on the mainframe platform. The IMS labs are focusing on improvements across the entire IMS product. There were several improvements in IMS 12; IMS 13 has many more; and reduced TCO will continue to be a focus area for future IMS versions. Copyright IBM Corp. 2011

26 Specific Reduced TCO Enhancements
IMS 12 Overview Specific Reduced TCO Enhancements IMS logger LOG latch contention reduction Improves usage of log latch and log buffer management for increased logging bandwidth and more efficient processing Shared queues local first optimization now applies to program-to-program switch messages as well as ordinary input messages Avoids false scheduling on another IMS when the local IMS can process the program-to-program switch message Exploitation of pageable 1M pages Based on usage of new zEC12 processors with Flash Express storage and z/OS (Dec. 2012) Provides improvements in dynamic address translation and usage of translation lookaside buffer (TLB) DB Space Management Block Serialization Latch Improvements Split from single to multiple latches to improve heavy BMP workloads MEMDSENQMGMT Exploitation More efficient memory-based data set ENQ management improves allocation of large number of data sets This list includes a few more major areas that focus on reduced TCO in IMS 13. Copyright IBM Corp. 2011

27 Other Reduced TCO Enhancements
IMS 12 Overview Other Reduced TCO Enhancements OTMA YTIB chain changed from a single linked list to a hash table, to improve FINDDEST performance. Convert OTMA and IMS Connect STORAGE calls to CPOOL Remove unnecessary clearing of OTMA buffers DFSCPY00 improved SVC directory entry search algorithm and removal of IVSK instructions. OSAM CML Lock Reduction General instruction optimization (replacing STCK with STCKF, long displacement facility exploitation) IMS cache manager spin loop elimination CQS mainline modules changed to use branch-relative branching Cache efficiency improvements (DPST blocks packed into a single IPAGE to keep cache references localized) IMS page load service algorithm optimization IMS dispatcher optimizations There are some other areas of IMS where improvements are being addressed. Copyright IBM Corp. 2011

28 ESAF support in Java Dependent Regions (JDR)
IMS 12 Overview ESAF support in Java Dependent Regions (JDR) With IMS 13, there are two methods for accessing DB2 from JDRs Access via the previously existing DB2 RRSAF interface Access via the standard ESAF interface With IMS 13, the ESAF interface can be used in JMP/JBP regions to access any ESAF defined to the IMS control region WebSphere MQ, DB2, WOLA (WebSphere Optimized Local Adapter) Support for the SSM= parameter on the JMP/JBP dependent region startup JCL Only one ESS connection method allowed per JMP/JBP Default ESS connection method is DB2 RRSAF No impact to existing users ESAF support for Java Dependent Regions is one of the focus items for reduced TCO. The standard ESAF interface can now be used for DB2 in JDRs, reducing complexity and improving performance versus the previous DB2 RRSAF interface. JDRs can now access other ESAF interfaces as well. Copyright IBM Corp. 2011

29 IMS Command Enhancements Overview
IMS 12 Overview IMS Command Enhancements Overview DBRC command enhancements DEDB Alter command enhancements /DIAGNOSE SNAP command enhancement HALDB command enhancements IMS Connect type-2 command enhancements Dynamically create data store definitions (CREATE IMSCON TYPE(DATASTORE)) Dynamically create port definitions (CREATE IMSCON TYPE(PORT)) Query XML converters loaded in IMS Connect (QUERY IMSCON TYPE(CONVERTER) DBRC command enhancements The following DBRC commands are enhanced for IMS Version 13 to support the DBRC enhancements: - CHANGE.RECON - INIT.ADS - INIT.RECON DEDB alter command enhancements The DBRC INIT.ADS command is enhanced to support the DEDB alter function. /DIAGNOSE SNAP command enhancements The /DIAGNOSE SNAP command is enhanced to improve the reliability of diagnostic information and to streamline the problem determination process. HALDB command enhancements The following IMS commands are enhanced to support the HALDB alter function: - INIT OLREORG - QUERY OLREORG IMS Connect command enhancements Detailed on the visual. Copyright IBM Corp. 2011

30 IMS Command Enhancements
IMS 12 Overview IMS Command Enhancements Enhancements are focused on type-2 commands for the Operations Manager (OM) environment Benefits Support of new IMS 13 functions Improved manageability Copyright IBM Corp. 2011

31 IMS 12 Overview IMS CQS Enhancement When IMS Common Queue Server (CQS) rejects a z/OS STOP cqsjobname command because CQS clients are still connected (CQS0300I), CQS issues a new message, CQS0301I, for each connected client Enables the operator to shut down or quiesce the connected CQS clients so that the CQS address space can be stopped Benefits Improved manageability for CQS Copyright IBM Corp. 2011

32 IMS 12 Overview IMS DRD Enhancement Support for the IMS repository (a single centralized store for resource definitions in an IMSplex) enhanced to validate resource attributes between associated resources when a resource definition is added to, updated in, or deleted from the IMSRSC Repository Validates transaction, routing code, and program attributes Also provided through the IMS 12 service process APAR PM32805 / PTF UX75915 Benefits Simplifies management of the DRD resources Copyright IBM Corp. 2011

33 IMS 13 User Exit Enhancements
IMS 12 Overview IMS 13 User Exit Enhancements Enhanced user exit services extended to additional IMS control region user exits Users can now dynamically refresh more IMS user exit routines to bring in an updated version of the exit (or add/delete) Significantly reduces downtime since IMS control region no longer requires restart Users can now display information about more user exits that are defined in the USER_EXITS section of DFSDFxxx Provides useful exit information to the user Users can now code an exit to leverage IMS’s ability to call multiple routines of the same type from a single point within the exit This line item adds enhanced user exit services support to a number of additional user exits. This support not only includes the ability to dynamically add, update or delete a user exit without restarting the IMS control region, but also to display useful exit information and enable IMS to call multiple user exit routines from a single point within an exit. Enabling additional exits to use the enhanced user exit services expands flexibility, improves the availability of the IMS online environment, and makes it easier to manage user exits. Copyright IBM Corp. 2011

34 Enhanced User Exit Services Added to More Control Region Exit Types
IMS 12 Overview Enhanced User Exit Services Added to More Control Region Exit Types BSEX (DFSBSEX0, Build Security Environment Exit) NDMX (DFSNDMX0, Non-Discardable Message Exit) RASE (DFSRAS00, Resource Access Security Exit) OTMAYPRX (DFSYPRX0, OTMA Destination Resolution Exit) OTMARTUX (DFSYRTUX, OTMA Resume TPIPE Security Exit) OTMAIOED (DFSYIOE0, OTMA Input/Output Edit Exit) LOGWRT (DFSFLGX0, Logger Exit) LOGEDIT (DFSFLGE0, Log Edit Exit) These are the user exits that can now use the enhanced user exit services in IMS 13. . Copyright IBM Corp. 2011

35 IMS Security Enhancements
IMS 12 Overview IMS Security Enhancements All IMS security settings can now be defined as IMS startup parameters Updates to SECURITY macro in system definition (SYSGEN) no longer required due to its removal Previously, certain settings could only be defined in SECURITY macro Move security user exits out of the IMS nucleus into 31-bit storage DFSCSGN0 DFSCTRN0 DFSCTSE0 IMS 13 no longer requires the SECURITY sysgen macro. More details are on the next chart. Benefits of the removal of selected user exits from IMS nucleus are: Exits are easier to maintain Linking to IMS nucleus is no longer necessary when one of the exits has been changed Usage of 24-bit storage is reduced Copyright IBM Corp. 2011

36 New IMS Startup Security Parameters
IMS 12 Overview New IMS Startup Security Parameters RCLASS parameter added to DFSPBxxx in PROCLIB RCLASS support in DFSDCxxx PROCLIB member will remain DFSPBxxx RCLASS parameter value will override DFSDCxxx if specified in both SECCNT parameter added to DFSDCxxx in PROCLIB Retrofit SPE APARs/PTFs available for IMS startup security parameter enhancement activation in IMS 11 and IMS 12 PM48203/UK74050 (IMS 11) PM48204/UK74051 (IMS 12) If specifying RCLASS in DFSPBxxx/DFSDCxxx, can also have the following APARs/PTFs applied to avoid an error message being issued when it shouldn’t be PM72199/UK82616 (IMS 11) PM73558/UK82617 (IMS 12) You are now able to specify the RCLASS and SECCNT settings as IMS startup parameters. RCLASS has been added to the DFSPBxxx member, which will co-exist with the ability to set this parameter within the DFSDCxxx member. Support for the DFSDCxxx remains for users who had previously specified it here instead of the SECURITY macro. However, if the RCLASS parameter is specified in both members, DFSPBxxx will take precedence. As a review, the RCLASS parameter specifies an identifier of 1 to 7 alphanumeric characters that is to be used to identity the IMS system as a resource class to RACF for transaction authorization and user ID verification. SECCNT has been added to the DFSDCxxx member, which specifies the maximum number of terminal and password security violations to be accepted per physical terminal and the number of transaction command violations per transaction prior to master terminal notification of such violations. The default is 0, which nullifies notification to the master terminal. The number specified must be 0, 1, 2, or 3. Copyright IBM Corp. 2011

37 /DIAGNOSE Command Enhancements
IMS 12 Overview /DIAGNOSE Command Enhancements Process for capturing diagnostic data used in troubleshooting IMS issues has been simplified SYSOUT option now available for /DIAGNOSE SNAP output Documentation can be gathered/stored in a readable format that is easy to retrieve and send to IBM support Time-consuming SYSLOG searches and manual data formatting prior to transmission no longer required /DIAGNOSE SNAP command extended to include more resources + more coverage of existing resources SHOW() support added for LTERM, NODE and USER BLOCK – can now specify multiple single instance blocks and more blocks can be snapped More blocks can be snapped for DB, LINE, LINK MSNAME support added New SYSOUT data set supported for output of command New OPTION(SYSOUT) parameter keyword New sub-parameters and values Enhancements to /DIAG SNAP command More resources able to have blocks captured Existing resources able to have additional blocks captured SHOW( ) parameter now applies to more resources New OPTION( ) parameter narrows output captured Various resources use these enhancements LTERM( ), NODE( ) and USER( ) RM( ) – new parameter SHOW( ) – can now be used with these resources BLOCK( ) – more parameter keywords DB( ) – more control blocks MSNAME( ) – new, support added LINE( ) – more control blocks LINK( ) – more control blocks Copyright IBM Corp. 2011

38 /DIAGNOSE Command Enhancements
IMS 12 Overview /DIAGNOSE Command Enhancements Benefits Cost effective, non-disruptive alternative to console dumps /DIAGNOSE command is now more interactive Can be used more as a tool for easing the real-time diagnosis process Decreased time and effort required in capturing diagnostic information Improved turn-around time in problem resolution Copyright IBM Corp. 2011

39 Summary of IMS 13 System Topics
IMS 12 Overview Summary of IMS 13 System Topics IMS Connect Enhancements Concurrent Application Threads Reduced Total Cost of Ownership (TCO) IMS Command Enhancements IMS CQS Enhancement IMS DRD Enhancement IMS User Exit Enhancements IMS Security Enhancements /DIAG Command Enhancements Copyright IBM Corp. 2011

40 IMS 13 Transaction Manager and Connectivity Enhancements
IMS 12 Overview IMS 13 Transaction Manager and Connectivity Enhancements Callout function enhancements ISC Over TCP/IP OTMA enhancements Non-Discardable Message Exit (DFSNDMX0) enhancements There are 4 enhancements for the Transaction Manager and Connectivity in IMS 13. Copyright IBM Corp. 2011

41 Callout Function Enhancements
IMS 12 Overview Callout Function Enhancements Synchronous program switch Enhancements to RECEIVE function for handling truncated messages OTMA destination descriptors support asynchronous messages that are going to IBM WebSphere® MQ The callout function has 3 enhancements in IMS 13. The first two will be discussed in this topic, the OTMA descriptor enhancement will be discussed under OTMA enhancements but it is listed here because it applies to callout usage. Copyright IBM Corp. 2011

42 Background DL/I ICAL support from previous IMS releases
IMS 12 Overview Background DL/I ICAL support from previous IMS releases Provided synchronous callout capability to resources outside IMS z/OS IMS WebSphere IMS TM resource adapter MPP/JMP/IFP/BMP/JBP TM/CTL Services Application Program ICAL DB Services IMS SOAP GATEWAY IMS Connect OTMA The existing DL/I ICAL in IMS allows IMS applications to synchronously call out to external resources. Specifically, IMS applications can request access to and wait for replies from: WebSphere EJBs/MDBs using the IMS TM Resource Adapter To any Web Service Provider using the IMS SOAP Gateway User-written IMS Connect clients TCP/IP user-written Client OTMA Descriptor OTMA Descriptor Database Copyright IBM Corp. 2011

43 Synchronous Program Switch
IMS 12 Overview Synchronous Program Switch New capability that enhances the DL/I ICAL support Allows an IMS application program to synchronously call and wait for a reply from another IMS application program Within the calling program’s UOW WebSphere IMS TM resource adapter IMS dependent region IMS TM services IMS DB services Database Application Program IMS SOAP GATEWAY IMS Connect OTMA ICAL With IMS V13, a new capability is added to the DL/I ICAL support so that not only is access to resources outside IMS supported, but also the ability to synchronously call another IMS transaction running in any of the dependent region types. The called or target program can be an MPP, JMP, IFP, or Message-Driven BMP in the same or different IMS. TCP/IP user-written Client MPP, JMP IFP, MD BMP Copyright IBM Corp. 2011

44 Synchronous Program Switch...
IMS 12 Overview Synchronous Program Switch... Highlights An enhancement to the DL/I ICAL to invoke another IMS application In the same IMS In a different IMS In a Shared Queues back-end Across an MSC link And synchronously receive the response back during the same UOW IMS internally schedules the transaction initiated by the ICAL call as an OTMA transaction Uses a new type of OTMA destination descriptor (TYPE=IMSTRAN) which has been introduced specifically for synchronous program switch support And the target transaction can be An IFP, MPP, MD BMP, or JMP in IMS TM or TM/DB environments MPP1 MPP4 MPP3 ICAL IMS1 MPP2 IMS X IMS2 MSC Shared Msg Queues In IMS V13, the function of this DL/I ICAL has been extended to allow customers to call another IMS application, which can be in the same IMS, in the shared-queues back-end IMS, or in the remote IMS via MSC. The ICAL synchronously receives the response back during the same unit of work. This new function is called “Synchronous Program Switch.” This new synchronous program switch function expands the usage of the OTMA destination descriptor to serve the ICAL requests so that the transaction data can be sent to another IMS application for processing. Multi-segment messages and responses are supported and the target of the call can be an IFP, MPP, BMP, JMP, or JBP running in the same or another IMS TM or IMS TM/DB system Copyright IBM Corp. 2011

45 Synchronous Program Switch...
IMS 12 Overview Synchronous Program Switch... Usage examples Applications can issue multiple ICALs to different destination TYPEs Synchronous callout Synchronous program switch ICAL DEST1 ICAL TRANB TRANA IMS CTL Region IMS Connect WebSphere IMS TMRA IMS SOAP Gateway TCP/IP RYO pgm OTMA MSG-Q Destination Descriptor TYPE(IMSCON) TRANB GU IOPCB ISRT IOPCB TYPE(IMSTRAN) 1 2 3 4 5 6 7 GU, IOPCB An IMS application can issue ICALs to remote destinations such as web services and also to other IMS applications. Copyright IBM Corp. 2011

46 Synchronous Program Switch...
IMS 12 Overview Synchronous Program Switch... Considerations To use synchronous program switch in a shared queues environment, all of the participating IMS systems must be Version 13 or later and have a MINVERS value of 13.1 New design implications Timeout values Transaction Expiration Late Responses LTERM Override ALTPCB destinations Multiple ICALs Recursive requests Holding database locks across an ICAL request Increased importance for performance tooling There are several design considerations for using synchronous program switch. Copyright IBM Corp. 2011

47 Support for Truncated Messages
IMS 12 Overview Support for Truncated Messages The RECEIVE subfunction of the DL/I ICAL is enhanced to enable applications to efficiently receive large messages that did not fit into a previously specified response area. New “RECEIVE” subfunction code can be used to get truncated message IMS 13 keeps a copy of the entire response message in the control region private storage Benefit Provides the ability to complete the retrieval of a reply message Without having to re-issue a complete ICAL “SENDRECV” and associated network transmission costs IMS 13 introduces a new subfunction of “RECEIVE” for the ICAL. This enhancement supports the retrieval of an entire response message if the original ICAL received partial data and an AIB return code of x’100’ and reason code of x’00C’. By taking advantage of the new subfunction and expanding the response area in the call, the IMS application is able to retrieve the copy of the message that is temporarily kept in the IMS control region’s private storage. This enhancement relieves the burden of having to re-issue a full ICAL “SENDRECV” along with any associated network delays. Copyright IBM Corp. 2011

48 ISC Over TCP/IP ISC Over TCP/IP value proposition
IMS 12 Overview ISC Over TCP/IP ISC Over TCP/IP value proposition New option that supports TCP/IP network connectivity for Intersystem Communication (ISC) connections IMS – CICS Provides a strategic protocol alternative to SNA/VTAM Allows an all inclusive TCP/IP solution for networks IMS 13 enhances Intersystem Communication (ISC) connectivity to included the TCP/IP protocol. This capability applies to connections between IMS and Customer Information Control System (CICS) systems. This new support provides a solution for environments that want to implement an all inclusive TCP/IP network environment. Copyright IBM Corp. 2011

49 ISC Over TCP/IP Highlights Supports both static and dynamic terminals
IMS 12 Overview ISC Over TCP/IP Highlights 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 Leverages IMS Connect Enhancements to the HWSCFGxx configuration member No IMS Connect user message exit changes Uses CSL to communicate between IMS and IMS Connect Requires Structured Call Interface (SCI) and Operation Manager (OM) Requires CICS Transaction Server for z/OS 5.1 At a high level, the ISC support using TCP/IP protocols can be defined in IMS environments both statically and dynamically (ETO). It uses the SCI (structure call interface) of the CSL (common service layer) between IMS and IMS Connect in order to leverage the existing IMS Connect TCP/IP support. Copyright IBM Corp. 2011

50 ISC Over TCP/IP Either IMS or CICS can initiate the request IMS CICS
IMS 12 Overview ISC Over TCP/IP Either IMS or CICS can initiate the request IMS 1 2 3 4 5 6 INPUT INPUT Transaction REPLY Connect CICS SCI TCP/IP Initiating a CICS transaction from IMS using an ISC TCP/IP connection tran OR Msg Switch End User Process transaction IMS 2 3 4 5 REPLY Connect CICS SCI TCP/IP Initiating an IMS transaction from CICS using an ISC TCP/IP connection End User Process transaction Tx. 1 Tx. (Start/Retrieve) INPUT Transaction 6 At a high level, the ISC support using TCP/IP protocols can be defined in IMS environments both statically and dynamically (ETO). It uses the SCI (structure call interface) of the CSL (common service layer) between IMS and IMS Connect in order to leverage the existing IMS Connect TCP/IP support. Copyright IBM Corp. 2011

51 OTMA Enhancements … OTMA destination descriptor enhancements
IMS 12 Overview OTMA Enhancements … OTMA destination descriptor enhancements TYPE={MQSERIES} Provides asynchronous callout and messaging support (ISRT ALTPCB) EXIT={YES | NO} Specifies whether or not the OTMA exits are to be called Corresponding enhancement to IMS Type-2 OTMADESC commands [CREATE | UPDATE | DELETE |QUERY] OTMADESC Recovered across warm and emergency restarts Benefits Simplifies asynchronous messaging to WMQ Removes the need to code the OTMA exits, DFSYPRX0 and DFSYDRU0 Provides dynamic change capability with the Type-2 commands The destination descriptor for IMS asynchronous callout has been expanded to introduce a new type, MQSERIES, to allow customers to define message switch destinations (from ALT IOPCB) as WebSphere MQ. This new type of descriptor for WebSphere MQ externalizes the definitions in the DFSYDTx member of IMS.PROCLIB rather than forcing customers to code OTMA routing exits (DFSYPRX0 & DFSYDRU0). Thirteen new parameters for this new descriptor are introduced to prepare the MQMD structure in the OTMA user data prefix. Dynamic addition, update, or deletion of the destination descriptors for WMQ can be performed using the type-2 commands: CREATE OTMADESC UPDATE OTMADESC DELETE OTMADESC Copyright IBM Corp. 2011

52 OTMA Enhancements OTMA early termination notification
IMS 12 Overview OTMA Enhancements OTMA early termination notification Enhancement that allows OTMA to leave the XCF group earlier in termination processing Allows OTMA clients (IMS Connect, WebSphere MQ, OTMA C/I) to be notified of the termination via their XCF Group Exit Can route requests to other systems Addresses issues associated with transactions messages being accepted but not processed Function being added to IMS 12: APAR PM73869 IMS 13 introduces an enhancement that allows OTMA clients (e.g.,. IMS Connect, WebSphere MQ, OTMA C/I) to be notified of IMS termination earlier in the termination process. This will be done for both scheduled and unscheduled terminations. The IMS OTMA clients can then route new requests to other IMS systems to be processed. This enhancement addresses environments that process high rates of transactions via IMS OTMA and experience some transactions being accepted but not processed by IMS during either scheduled or unscheduled IMS terminations. Copyright IBM Corp. 2011

53 Enhancements for the Non-Discardable Messages Exit Routine
IMS 12 Overview Enhancements for the Non-Discardable Messages Exit Routine Customer requirement for a new function to PSTOP an abending transaction Stops scheduling but allows queueing to continue New functions provided by for the DFSNDMX0, the Non-Discardable Messages exit routine IMS 11 APAR PM67950 / PTF UK81040 IMS 12 APAR PM45943 / PTF UK71989 Included in IMS 13 This enhancement provides new function for the DFSNDMX0, the non-discardable messages exit routine. These enhancements are included in IMS They are also available for IMS 12 and IMS 11 via PTF. Copyright IBM Corp. 2011

54 Summary of IMS 13 Transaction Manager and Connectivity Topics
IMS 12 Overview Summary of IMS 13 Transaction Manager and Connectivity Topics Callout function enhancements ISC Over TCP/IP OTMA enhancements Non-Discardable Message Exit (DFSNDMX0) enhancements Copyright IBM Corp. 2011

55 IMS 13 Database and DBRC Enhancements
IMS 12 Overview IMS 13 Database and DBRC Enhancements Database Versioning HALDB Alter DEDB Alter DBRC Enhancements There are four enhancements to the IMS Database component in IMS 13. Copyright IBM Corp. 2011

56 Database Versioning Overview …
IMS 12 Overview Database Versioning Overview … Database Versioning provides the ability to assign user-defined version identifiers to different versions of a database structure Enables structural changes to a database while providing multiple views of the physical IMS data to application programs Applications referencing a new physical database structure can be brought online without affecting applications that use previous database structures Applications which do not require sensitivity to the new physical structure, do not need to be modified and can continue to access the database Database versioning provides the ability to assign user-defined version identifiers to different versions of the structure of a database. These identifiers enable you to make structural changes to a database while providing multiple views of physical data to a variety applications. New applications that reference a newer structure of a database can be brought online without affecting applications that use previous database structures. Unchanged applications, which do not have to be sensitive to the new physical structure of the database, can continue to access the database. Copyright IBM Corp. 2011

57 Database Versioning Overview
IMS 12 Overview Database Versioning Overview Database Versioning supports the following database types DEDB, HDAM, HIDAM, PHDAM, PHIDAM Can be used in conjunction with the database alter functions to keep track of different versions of the structure of a database only supports the following database structure changes For all supported database types Increasing the length of a fixed-length segment Adding a new field to space at the end of a fixed-length segment For Full-Function and HALDB database types Adding new field(s) that remap existing field(s) and space at the end of a fixed-length segment Variable-length segments are not supported Database versioning can be used for the following types of databases: • DEDB • HDAM • HIDAM • PHDAM • PHIDAM IMS database versioning supports databases that have logical relationships and databases that have secondary indexes. The database versioning function: Can be used in conjunction with the database alter function to keep track of different versions of the structure of a database. Supports the following structural changes to all supported database types: Increasing the length of a segment Adding a new field at the end of a segment Supports the following structural changes to FF and HALDB database types Adding a new field to a segment that remaps / overlays existing fields and space at the end of a segment. Database Versioning only supports changes which include increasing the length of the segment and defining new fields. These changes are normally implemented by recoding the DBD source and running the DBD, PSB, and ACBGEN utilities. The customer will then unload/reload the database or utilize the IMS 13 HALDB Alter function followed by performing an Online Change Changes made to any existing fields, which include changing the starting position or length of the field are not allowed. Copyright IBM Corp. 2011

58 Database Versioning Requirements
IMS 12 Overview Database Versioning Requirements Database Versioning must be enabled in DFSDFxxx DATABASE section Versioning is at the DBD level Users define the version of a database definition on the DBD Version numbers must be maintained in incremented values Database Versioning requires enablement of the IMS catalog DBD definitions for versioned databases must be in the IMS catalog Application programs can elect the desired database version Specifying the version number on the PCB of the PSB Specifying the version number on a DL/I INIT VERSION call Requirements: To enable the database versioning support, the following tasks are required: Specify the new parameter, DBVERSION=Y, in the databases section in the DFSDFxxx member of the IMS PROCLIB data set to indicate that database versioning is to be used. If Database Versioning is enabled, the IMS Catalog is required to be available in order to retrieve the correct DBD version for the application programs. If the IMS Catalog is not available then the application is returned an ‘NA’ status code. Application programs that need to access a particular version of a database definition can specify the DBVER= on the PCB statement of the PSB source, or issue the INIT VERSION call to specify the database version for each database view that is used by the application. When a version number is assigned to the DBD, if the database is logically related to one or more databases, all logically-related databases must be included in the ACBGEN process. The affected database descriptions (DBDs) must be in the IMS catalog. The IMS catalog metadata describes the current and previous structures of a database. The metadata includes the version numbers that identify each structure of a database. When an application program makes a call to a versioned database, IMS internally references the catalog to determine which structure corresponds to the provided version number and whether the format of the requested data needs to be modified before it is returned to the application program. After a DBD has a version number, apps can use the new INIT VERSION call to access a specific version of the database or specify the database version for an application program on the DBVER parm in the PCB statement. The following requirements apply: INIT VERSION call must be issued before issuing a DL/I call to access that database Version specified on INIT VERSION call overrides version number specified on the PCB Copyright IBM Corp. 2011

59 Database Versioning Implementation
IMS 12 Overview Database Versioning Implementation DFSDFxxx PROCLIB: new DATABASE section keywords Specify whether database versioning is enabled and default version DBVERSION= DBLEVEL= Database and Program Generation Statements Specify the database version number DBD: DBVER= PCB: DBVER= Override the default versioning specified in DFSDFxxx PSBGEN: DBLEVEL= “INIT VERSION” DL/I Call Overrides the version number that is specified on the PCB statement Must be issued before issuing a DL/I DB call to the database The following IMS™ components are updated to support database versioning: DFSDFxxx PROCLIB member Two new keywords are added to the DATABASE section of the DFSDFxxx PROCLIB member that specify whether database versioning is enabled and, if so, what default versioning is to be used: DBVERSION= DBLEVEL= DBD and PSBGEN generation statements The DBD and PCB statements are enhanced with a new DBVER parameter, where you can specify the database version number: DBVER= The PSBGEN statement is enhanced with a new parameter that can be used to override the default versioning that is specified in the DFSDFxxx PROCLIB member: After a DBD has a version number, apps can use the new INIT VERSION DL/I call to access a specific version of the database or specify the database version for an application program on the DBVER parm in the PCB statement. The following requirements apply: Version specified on INIT VERSION call overrides version specified on the PCB INIT VERSION call must be issued before using a DL/I call to access that database Copyright IBM Corp. 2011

60 IMS 12 Overview HALDB Alter Overview … Structural changes can be made to HALDB databases while the database remains online Add a new field to space at the end of an existing segment Increase the length of an existing segment Define new fields that remap existing fields and space in an existing segment Fixed-length segments only Benefit Make structural changes to a database while maintaining database availability A B C The following structural changes can be applied to an online HALDB with the type-2 INIT OLREORG command: Adding new fields to space at the end of the segment Increasing the length of existing segment by adding space at the end of the segment Defining new fields that re-map existing fields and space in the segment.(not structural) After a segment change is made to a DBD, an online reorganization command can be issued to initiate the change to the database. The change is implemented via an option of the TYPE 2 HALDB Online Reorganization (OLR) function – INIT OLR. Application programs that use the old database definitions can access the database while the OLR function is altering the structure of the database and until an online change is performed. Copyright IBM Corp. 2011

61 HALDB Alter Overview HALDB Alter is only supported for database types:
IMS 12 Overview HALDB Alter Overview HALDB Alter is only supported for database types: PHDAM PHIDAM After changes are made to the DBD segment definition Type-2 INITIATE OLREORG command is used to alter a database from the current structure to the new structure Type-1 command /INITIATE OLREORG does not support altering a HALDB Online Change commands are used to bring the changed ACBLIB DBD member online Application programs can start using the new database structure When a segment change is made to a DBD, an online command can be issued to initiate the change to the database. The change is implemented via an ALTER option of the TYPE 2 HALDB Online Reorganization (OLR) function. The TYPE-1 /INIT OLR command will not support the new HALDB ALTER function. An Online Change must be completed to in-affect the DBD change in the online system. Application programs that use the old database definitions can access the database while the OLR function is altering the structure of the database. Once an OLC is completed for the DBD, application programs can use the new database definitions to access the database. Copyright IBM Corp. 2011

62 Add a new field to space at the end of a segment
IMS 12 Overview Add a new field to space at the end of a segment FIELD 1 FIELD 2 Space New FIELD 3 Example 1 Example 2 EX 1: Add new field to beginning of free space at the end of a segment EX 2: Add new field to end of free space at the end of a segment The new field definitions are added to the DBD segment definition. Copyright IBM Corp. 2011

63 Increase the length of an existing segment
IMS 12 Overview Increase the length of an existing segment Example 1 FIELD 1 FIELD 2 FIELD 1 FIELD 2 New Space Example 2 FIELD 1 FIELD 2 Space EX 1: Increase the length of an existing segment by adding space at the end EX 2: Increase the length of an existing segment by adding more free space at end The new free space is added to the segment size in the DBD definition – new length on BYTES= parm of the SEGM statement FIELD 1 FIELD 2 New Space Space Copyright IBM Corp. 2011

64 HALDB Alter Prerequisites
IMS 12 Overview HALDB Alter Prerequisites Software requirements CSL SCI OM DBRC RECON MINVERS (‘13.1’) Minimal software and hardware pre-reqs: CSL and IMS 13 Copyright IBM Corp. 2011

65 IMS 12 Overview DEDB Alter IMS 13 adds ability to dynamically change DEDB specifications Users can dynamically change UOW, SIZE, ROOT, Randomizer while DEDB is online New DEDB Alter utility is used for DEDB changes DRD is not required for DEDB Alter Supports VSO Areas if /VUNLOAD is done before DEDB Alter is executed Benefits Improved management of DEDB definitions Eliminate system down time for modifications to DEDB definitions Improve data availability since changes are done while DEDB is online In IMS 13, Fast Path has added the ability to dynamically change specific DEDB specifications. For example, the UOW, SIZE, ROOT, and Randomizer routine can be changed while the DEDB is online. There is a new DEDB Alter utility that allows these DEDB changes to occur. This is support is available for VSO areas provided the areas are unloaded first using the /VUNLOAD command. Allowing dynamic changes to the DEDBs will improve data availability and reduce system down time. Copyright IBM Corp. 2011

66 IMS 12 Overview DEDB Alter Utility The new DEDB Alter utility is used to change the following items without taking the area offline The SIZE, UOW, or ROOT specifications of a DEDB area The randomizer that is used for the DEDB area Requirements A two-stage randomizer must be used, which enables areas to be processed individually. DEDBs to be altered must be registered to DBRC The MINVERS value in the RECON data set for all IMS subsystems that share the DEDB area must be at “13.1” or later If SDEPS present, only the randomizer name can be changed The DEDB Alter utility supports these new functions. ALTERAREA is used to change the UOW, ROOT, SIZE, and RMNAME (randomizer name) values. REPLRAND is used to specifically change the Randomizer name. Copyright IBM Corp. 2011

67 DBRC Enhancements Command support for HALDB Alter
IMS 12 Overview DBRC Enhancements Command support for HALDB Alter Command support for DEDB Alter MINVERS value of ’13.1’ must be set to use HALDB Alter, DEDB Alter, or synchronous program switch in a shared queues environment Supported Migration and Coexistence IMS 11 to IMS 13 Apply DBRC coexistence SPE APAR PM53134 to IMS 11 PTF UK80026 Allow IMS 11 to understand IMS 13 RECON records IMS 12 to IMS 13 Apply DBRC coexistence SPE APAR PM53139 to IMS 12 PTF UK80027 Allow IMS 12 to understand IMS 13 RECON records The major DBRC enhancments address support for the new HALDB alter capability and the new DEDB alter capability in IMS 13. There is a new MINVERS value, ’13.1’. DBRC migration and coexistence supports migration from IMS 11 and IMS 12 to IMS 13. Copyright IBM Corp. 2011

68 Summary of IMS 13 Database Manager and DBRC Topics
IMS 12 Overview Summary of IMS 13 Database Manager and DBRC Topics HALDB Alter DEDB Alter Database versioning DBRC enhancements Copyright IBM Corp. 2011


Download ppt "IMS 13 Quick Look GSE BENELUX IMS User Group Meeting"

Similar presentations


Ads by Google