1. Geoff Nicholls, Consulting IT Specialist Introducing IMS 13
June 2013 2013 IBM Corporation
2. Introducing IMS 13 Important Disclaimer 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. 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 IBMS 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, Information Management, IMS, CICS, DB2, WebSphere
and z/OS are trademarks or registered trademarks of International
Business Machines Corporation in the United States, other
countries, or both. If these and other IBM trademarked terms are
marked on their first occurrence in this information with a
trademark symbol ( or ), these symbols indicate U.S. registered or
common law trademarks owned by IBM at the time this information was
published. Such trademarks may also be registered or common law
trademarks in other countries. A current list of IBM trademarks is
available on the Web at Copyright and trademark information at
ibm.com/legal/copytrade.shtml Other company, product, or service
names may be trademarks or service marks of others. 2 2013 IBM
Corporation
3. Introducing IMS 13 Agenda QPP & Status of IMS Versions
System Enhancements Database and DBRC Enhancements Transaction
Manager and Integration Enhancements Prerequisites, Migration,
Coexistence 3 2013 IBM Corporation
4. Introducing IMS 13 Introducing IMS 13 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 4 2013 IBM Corporation
5. Introducing IMS 13 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
End of service has not been announced IMS Version 13 Announced on
October 3, 2012 Currently in QPP program General availability has
not been announced 5 2013 IBM Corporation
6. Introducing IMS 13 IMS 13 System Enhancements 6 2013 IBM
Corporation
7. Introducing IMS 13 IMS 13 System Enhancements 7 IMS Connect
Enhancements Concurrent Application Threads Reduced Total Cost of
Ownership (TCO) IMS CQS Enhancement IMS DRD Enhancement IMS User
Exit Enhancements IMS Security Enhancements /DIAGNOSE Command
Enhancements 2013 IBM Corporation
8. Introducing IMS 13 IMS Connect 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 8 XML Converter
Enhancements Dynamic creation of Ports and Datastores via command
2013 IBM Corporation
9. Introducing IMS 13 IMS Connect Enhancements Reduced Time
Enhancements specifically for IMS SOAP Gateway users Ability to
increase the number of Converters that can be loaded (from 100 to
2000) 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 z/OS Windows/AIX/ zLinux/zOS Web Service
Client (.NET, SAP, java, etc.) SOAP Envelope with XML message HTTP
/ SOAP XML message IMS SOAP Gateway TCP/IP / XML IMS Connect IMS
message IMS XML Converter Benefits: Enhances the flexibility of
converter usage Directly impacts IMS Soap Gateway environments 9
2013 IBM Corporation
10. Introducing IMS 13 IMS Connect Enhancements Reduced Time
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 No need to manually refresh exit z/OS Windows/AIX/
zLinux/zOS Web Service Client (.NET, SAP, java, etc.) SOAP Envelope
with XML message HTTP / SOAP XML message IMS SOAP Gateway TCP/IP /
XML IMS Connect IMS message IMS XML Converter Benefits: Improved
efficiencies during error conditions Eliminates IMS Connect restart
and user interactions Directly impacts IMS Soap Gateway
environments 10 2013 IBM Corporation
11. Introducing IMS 13 IMS Connect Enhancements Reduced Time
Enhancements for ALL IMS Connect users 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 11 2013 IBM
Corporation
12. Introducing IMS 13 IMS Connect Enhancements Reduced Time
Enhancements for ALL IMS Connect users RACF Event Notification
Facility (ENF) Support Background IMS Connect 12 provided the
option to cache RACF UserIDs (UIDs) along with a command to refresh
them (UIDCACHE=Y) IMS Connect 13: 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 RACF CONNECT, REMOVE and ALTUSER REVOKE commands NOTE: This
function applies only when RACF UID caching has been enabled in IMS
Connect Benefits: Allows IMS Connect to listen for certain RACF
events indicating that a change has been made to a specific UserID
Avoids manual intervention 12 2013 IBM Corporation
13. Introducing IMS 13 IMS Connect Enhancements Enhancements
for ALL IMS Connect users Reporting of Overall Health to Workload
Manager (WLM) WLM Health Report New function to automatically
report the overall health of IMS Connect Allows Sysplex Distributor
to use and take this information into account for The health of the
workload balancing IMS Connect is directly related to the
percentage of available sockets. As clients connect, the health
value reported to WLM by IMS Connect will start to go down. Coding
a distribution method of SERVERWLM VIPADYNAMIC VIPADISTRIBUTE
DEFINE DISTMETHOD SERVERWLM Note: the health value is not used when
DISTMETHOD is ROUNDROBIN or BASEWLM Allows multiple IMS Connects
sharing ports on one system to use this information 8888 TCP HWS*
SHAREPORTWLM TO WLM ;SHARED PORT FOR HWS. USING HEALTH REPORTED
Benefits: Allows WLM to know when resources are constrained or
available Minimizes the possibility of assigning work that IMS
Connect is unable to handle 13 2013 IBM Corporation
14. Introducing IMS 13 IMS Connect Enhancements Enhancements
for ALL IMS Connect users 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
Connects TCPIPQ value and SOMAXCONN in TCP/IP During peak
processing times requests up to this value can be queued in TCP/IP
without their connections being rejected pending IMS Connect action
Benefits: Provides a configurable option to increase the backlog
queue size in TCP/IP 14 2013 IBM Corporation
15. Introducing IMS 13 IMS Connect Enhancements Enhancements
for ALL IMS Connect users Dynamically CREATE IMS Connect resources
through commands For PORT and DATASTORE CREATE IMSCON TYPE(PORT)
NAME(portnum1, portnum2, ...) LIKE(portnum_model) SET(attribute1,
attribute2, ...) Equivalent to defining TCPIP (regular port) or
ODACCESS (DRDA port) statement in HWSCFGxx 15 2013 IBM
Corporation
16. Introducing IMS 13 IMS Connect Enhancements Enhancements
for ALL IMS Connect users Dynamically CREATE IMS Connect resources
through commands For PORT and DATASTORE CREATE IMSCON
TYPE(DATASTORE) NAME(datastore_name) LIKE(datastore_model)
SET(attribute1, attribute2, ...) Equivalent to defining the
DATASTORE statement in HWSCFGxx DATASTORE=( APPL=, ACKTO=,
CM0ATOQ=, DRU=, GROUP=, ID=, MAXI=, MEMBER=, OAAV=, RRNAME=,
SMEMBER=, TMEMBER= ) Note: Definitions created by CREATE commands
do not persist across IMS Connect restart Benefits: IMS Connect
customers can now add new ports and IMS datastore connections
without having to restart IMS Connect Improved IMS Connect
availability Existing type-2 command architecture leveraged 16 2013
IBM Corporation
17. Introducing IMS 13 Overall Value of IMS Connect
Enhancements Enhanced usability while providing better performance
and diagnostics Increased resiliency to Abnormal Ends (ABENDs)
Improved usability and manageability 17 2013 IBM Corporation
18. Introducing IMS 13 Increase Number of Concurrent
Application Threads 4 x More Applications! Increase the limit of
concurrent application threads from 999 to 4095 Limit applies to
the total number of combined: Dependent Regions
(MPP/BMP/IFP/JMP/JBP) CICS/DBCTL threads Open DB Access (ODBA)
threads Change to MAXPST parameter on IMS control region Note:
Reducing MAXPST= requires a Coldstart 31 dependent regions - 1980
(IMS 1.1.6) 999 dependent regions - 1995 (IMS 5.1) 4095 dependent
regions - 2013 (IMS 13) Benefits: Increased capacity and
scalability for IMS systems Allows vertical growth More dependent
regions for use with synchronous callout and program switch 18
MAXPST should no longer be a limiting factor in IMS Growth 2013 IBM
Corporation
19. Introducing IMS 13 IMS 13 Highest Efficiency, Lowest Total
Cost of Ownership 19 2013 IBM Corporation
20. Introducing IMS 13 Reduced Total Cost of Ownership Reduced
Cost 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
path length 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 20 2013 IBM Corporation
21. Introducing IMS 13 Specific Reduced TCO Enhancements
Reduced Cost 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 1.13 (Dec.
2012) Provides improvements in dynamic address translation and
usage of translation lookaside buffer (TLB) IMS 13 requests the
following areas to be backed by pageable large pages, when
available: CQS interface buffers DPSB pool (DLI/SAS PSB pool) *
DLDP pool (DMB pool) * DBWP pool (DMB work pool) * * If you page
fix these pools, then they will not be backed by 1M pages. 21 2013
IBM Corporation
22. Introducing IMS 13 Specific Reduced TCO Enhancements
Reduced Cost 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 dynamic allocation of large number
of data sets To enable, add the following statement to your ALLOCxx
SYS1.PARMLIB member: SYSTEM MEMDSENQMGMT(ENABLE|DISABLE) 22 2013
IBM Corporation
23. Introducing IMS 13 Other Reduced TCO Enhancements 23
Reduced Cost 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. 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. OSAM CML Lock Reduction. General
instruction optimization (replacing STCK with STCKF, long
displacement facility exploitation). IMS cache manager spin loop
elimination. Enhancements are across many components of IMS,
showing the reduced TCO focus for the whole IMS product. 2013 IBM
Corporation
24. Introducing IMS 13 IMS 13 User Exit Enhancements Reduced
Time 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 IMSs ability to call multiple routines of
the same type from a single point within the exit 27 2013 IBM
Corporation
25. Introducing IMS 13 Refreshable User Exits Reduced Time
Refresh user exits without an IMS system outage Defines exit types
to support a list of exit names BSEX - DFSBSEX0 (Build Security
Environment Exit) LOGEDIT - DFSFLGE0 (Log Edit Exit) LOGWRT -
DFSFLGX0 (Log Write Exit) NDMX - DFSNDMX0 (Non-Discardable Message
Exit) RASE - DFSRAS00 (Resource Access Security Exit) OTMAIOED -
DFSYIOE0 (OTMA Input/Output Edit Exit) OTMARTUX - DFSYRTUX (OTMA
Resume Tpipe Security Exit) OTMAYPRX - DFSYPRX0 (OTMA Destination
Resolution Exit) Benefits: Improves availability Simplifies user
exit management 28 2013 IBM Corporation
26. Introducing IMS 13 /DIAGNOSE Command Enhancements Reduced
Time Users can now send formatted /DIAGNOSE SNAP command output to
a SYSOUT data set, enabling easy submission to IBM support SYSOUT
data set will contain documentation that is Formatted and readable
Easy to retrieve SHOW() support added for LTERM, NODE, USER BLOCK
can now specify multiple single instance blocks and more block
types can be snapped More blocks can be snapped for DB, LINE, LINK
Support added for MSNAME Benefits: Improve time and effort to
capture diagnostic information Reduce time needed to resolve
problems 32 2013 IBM Corporation
27. Introducing IMS 13 Summary of IMS 13 System Topics IMS
Connect Enhancements Concurrent Application Threads Reduced Total
Cost of Ownership (TCO) IMS CQS Enhancement IMS DRD Enhancements
IMS User Exit Enhancements IMS Security Enhancements /DIAGNOSE
Command Enhancements 33 2013 IBM Corporation
28. Introducing IMS 13 IMS 13 Database and DBRC Enhancements 34
2013 IBM Corporation
29. Introducing IMS 13 IMS 13 Database and DBRC Enhancements
HALDB Alter DEDB Alter Database Versioning DBRC Enhancements 35
2013 IBM Corporation
30. Introducing IMS 13 HALDB Alter Improved Availability
Structural Changes can be made to an IMS HALDB whilst 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 A A B C B C Benefits: Improves IMS HALDB
availability by providing structure changes without taking the
database offline Provides flexibility in rolling database changes
into the system 36 2013 IBM Corporation
31. Introducing IMS 13 HALDB Alter Overview Improved
Availability 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 37 2013 IBM
Corporation
32. Introducing IMS 13 OLR Overview - Reminder Cursor points to
root key or RBA of last committed reorganized record Input Data
Sets Cursor Database records that have been copied to the output
Locked Database Records A thru J and X Database records yet to be
copied to the output Database records are copied from the input to
the output datasets in UORs UOR : One or more HALDB records (root
and all of its dependent segments) that are reorged within one
commit boundary. Output Data Sets M thru V and Y Database records
that have been copied from the input 38 Database records can be
read, replaced, inserted or deleted 2013 IBM Corporation
33. Introducing IMS 13 HALDB Alter Online Processing Online
Reorg is used to alter the structure of a HALDB database The input
side uses the current DBD from the active ACBLIB The output side
uses the new DBD from a staging ACBLIB Delta files are built to
represent the changes between the active/input DMB and the
staged/output DMB All database partitions are included in the reorg
process Application programs accessing the existing database
continue running using the current DBD Max of 10 TCBs will be
scheduled concurrently for an ALTER process, if necessary 39 2013
IBM Corporation
34. Introducing IMS 13 HALDB Alter Online Processing (contd)
The new database structure will be available for use after the OLR
ALTER and OLC processes have completed successfully Make necessary
updates to affected application programs Take a backup of the
active ACBLIB member(s) being changed Stop access to the altered
HALDB database Use /DBR or UPDATE command Do OLC to complete the
alter process for changed ACBLIB member(s) Member Online Change is
recommended Reads directly from the staging ACBLIB Can process
specific ACBLIB members requiring activation INITIATE OLC
TYPE(ACBMBR) NAME(acbmember) Start access to the altered HALDB
database Until OLC process is complete, application programs
accessing the database receive the unaltered format of the segment
40 2013 IBM Corporation
35. Introducing IMS 13 HALDB Alter Prerequisites Improved
Availability Software requirements CSL SCI OM DBRC RECON MINVERS
(13.1) 41 2013 IBM Corporation
36. Introducing IMS 13 Fast Path Data Entry Database (DEDB)
Alter Improved Availability Allows DEDB Area changes without
unload/reload of the area Dynamic change for UOW, SIZE and ROOT
parameters of an existing Area Replace the randomizer Provides new
DEDB dynamic change utility Runs as a standard Fast Path IFP
utility Area remains online Requires the use of a two-stage
randomizer allowing Areas to be processed individually If SDEPs are
present, only the randomizer name can be changed Supports VSO Areas
if /VUNLOAD is done before DEDB Alter is executed Benefits:
Improves DEDB Area availability by providing definitional changes
without taking the Area offline Provides flexibility in rolling
Area changes into the system 42 2013 IBM Corporation
37. Introducing IMS 13 Database Versioning Overview Usability
Allows programs to use different versions of the same physical
database Multiple views of the physical data maintained in the IMS
Catalog Existing applications can remain unchanged when the
physical structure of the database changes Recompile just those
programs referencing changed fields/segment Applies to Full
Function DB, HALDB, Fast Path DEDB Supports database types: HDAM,
HIDAM, PHDAM, PHIDAM, DEDB Benefits: 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 44 2013 IBM Corporation
38. Introducing IMS 13 Database Versioning Overview (contd)
Database Versioning supports the following database types DEDB HDAM
IMS Catalog HIDAM PHDAM PHIDAM Database Versioning supports the
following database structure changes For all supported database
types Increasing the length of a segment Adding a new field to
space at the end of a segment For Full-Function and HALDB database
types Adding new field(s) that remap existing field(s) and space at
the end of a segment 45 2013 IBM Corporation
39. Introducing IMS 13 Database Versioning Overview (contd)
Database Versioning must be enabled in DFSDFxxx 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
IMS Catalog Database Versioning requires enablement of the IMS
catalog DBD definitions for versioned databases must be in the IMS
catalog Application programs can select the desired database
version 46 Specifying the version number on the PCB of the PSB
Specifying the version number on a DL/I INIT VERSION call 2013 IBM
Corporation
40. Introducing IMS 13 Database Versioning Implementation
DFSDFxxx PROCLIB: new DATABASE section keywords Specify whether
database versioning is enabled and default version DBVERSION=
DBLEVEL= IMS Catalog 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 47 Overrides the version number
that is specified on the PCB statement Must be issued before
issuing a DL/I DB call to the database 2013 IBM Corporation
41. Introducing IMS 13 Solution Overview Database Versioning
Flow #1 DBD Source DBJK21 V1 DBDGEN DBDLIB ACBLI B DBJK22 V1 ACBGEN
DBJK21 V1 DBJK22 V1 DBJK23 V1 DBJK23 V1 Version V1 of DBDs put into
ACBLIB & Catalog PSB=PSBJK Source DBJK21 V1 DBJK22 V1 DBJK23 V1
PSBGEN -------------------------PCB -------------------------DBJK21
V0 DBJK22 DBJK23 V1 PSBLIB IMS Catalog PSBJK PSBGEN DBJK21 V0,V1
DBJK22 V0,V1 DBJK23 V0,V1 IMS Retrieve DBJK21 from Catalog
Application DBJK21 DBJK22 DBJK23 DLI Active DBJK21 V0 DBJK22 V1
DBJK23 V1 DBJK21 V1 DBJK22 V1 DBJK23 V1 Database Versioning enabled
-> data returned to app at V0 & V1 levels DBJK21 DBJK22
DBJK23 48 2013 IBM Corporation
42. Introducing IMS 13 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 49 2013 IBM Corporation
43. Introducing IMS 13 Summary of IMS 13 Database Manager and
DBRC Topics 50 HALDB Alter DEDB Alter Database Versioning DBRC
Enhancements 2013 IBM Corporation
44. Introducing IMS 13 IMS 13 Transaction Manager and
Integration 51 2013 IBM Corporation
45. Introducing IMS 13 IMS TM and Integration Enhancements
Callout function enhancements ISC Over TCP/IP OTMA enhancements 52
2013 IBM Corporation
46. Introducing IMS 13 Callout Function Enhancements 53
Synchronous Program Switch Enhancements to RECEIVE function for
handling truncated messages OTMA destination descriptors support
asynchronous messages that are going to IBM Websphere MQ 2013 IBM
Corporation
47. Introducing IMS 13 Background DL/I ICAL support from
previous IMS releases Provided synchronous callout capability to
resources outside IMS z/OS IMS WebSphere MPP/JMP/IFP/BMP/JBP IMS TM
resource adapter OTMA TM/CTL Services IMS IMS SOAP GATEWAY
Application Program ICAL DB Services Connect TCP/IP user-written
Client IMS Connect API 54 OTMA Descriptor OTMA Descriptor Database
2013 IBM Corporation
48. Introducing IMS 13 Synchronous Program Switch Usability 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 programs UOW
WebSphere IMS TM services IMS TM resource adapter Application
Program IMS IMS SOAP GATEWAY Connect IMS dependent region OTMA IMS
DB services Database ICAL TCP/IP user-written Client MPP, JMP IFP,
MD BMP 55 2013 IBM Corporation
49. Introducing IMS 13 Synchronous Program Switch Benefits
Modernization of the IMS application infrastructure Provides an
internal service flow of IMS transactions to complete a business
process In the same IMS or a different IMS Implementation of a
Process Server or Broker inside IMS Reduces unnecessary network
traffic when accessing multiple applications in the same IMS or
IMSplex WAS IMS Connect IMS WAS MPP1 WAS Application MPP2 MPP3 MPP4
WAS Application IMS Connect IMS MPPx ICAL ICAL ICAL ICAL MPP1 MPP2
MPP3 MPP4 57 2013 IBM Corporation
50. Introducing IMS 13 IMS Java Dependent Region use of
External Subsystem Attach Facility Allow Java Dependent regions to
use the External Subsystem Attach Facility (ESAF) Allows
connections for DB2 to be consistent across all region types Allows
access to other subsystems such as WebSphere MQ Eliminates the need
to use z/OS Resource Recovery Services (RRS) Attach for DB2
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 63 2013 IBM
Corporation
51. Introducing IMS 13 InterSystem Communication (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 Benefits: Provides a strategic protocol alternative to
SNA/VTAM Allows an all inclusive TCP/IP solution for networks 64
2013 IBM Corporation
52. Introducing IMS 13 ISC Over TCP/IP Either IMS or CICS can
initiate the request 1 Msg Switch IMS End User TCP/IP SCI tran OR
INPUT IMS 2 INPUT REPLY 5 CICS 3 INPUT Transaction IMS Connect
REPLY 6 Process transaction 4 tran REPLY Initiating a CICS
transaction from IMS using an ISC TCP/IP connection Process
transaction TCP/IP SCI IMS INPUT Transaction 4 REPLY 3 IMS Tx.
(Start/Retrieve) 2 Connect 5 REPLY 1 CICS End User Tx. CICS 6 REPLY
Initiating an IMS transaction from CICS using an ISC TCP/IP
connection 65 2013 IBM Corporation
53. Introducing IMS 13 IMS TM and Integration Enhancements 66
Callout OTMA Enhancements JDR use of ESAF ISC over TCP/IP to CICS
2013 IBM Corporation
54. Introducing IMS 13 IMS 13 At a Glance And more to come!
Database Management Transaction Management and Integration Systems
Management 67 HALDB Alter DEDB Alter Database Versioning
Synchronous Program Switch OTMA Descriptor Support for WebSphere MQ
Bridge OTMA Early Termination Notification OTMA Enhancements JDR
Support for ESAF IMS to CICS via ISC over TCP/IP IMS Connect
Enhancements Reduce TCO Increase number of concurrent applications
Elimination of SECURITY Macro Standalone Security User Exits Log
Latch Reduction User Exit Enhancements DIAG Command Enhancements
2013 IBM Corporation
55. Introducing IMS 13 IMS 13 At a Glance And more to come!
Migration and Coexistence 68 DBRC: Allow IMS 11 and IMS 12
migration to IMS 13 Syntax Checker: Support for new and changed
parameters 2013 IBM Corporation
56. Introducing IMS 13 IMS 13 Prerequisites, Packaging and
Migration 69 2013 IBM Corporation
57. Introducing IMS 13 IMS 13 Software Prerequisites* IMS 13
Minimum Release Levels 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 (5696-234)
APAR OA39392 / PTF UA66823, OA36172/UA61786 *Subject to Change 70
2013 IBM Corporation
58. Introducing IMS 13 IMS 13 Software Prerequisites* Other
prerequisites for optional line items: Database Versioning requires
the IMS Catalog Java Dependent Regions require JDK 6.0.1 or later
IMS Universal Drivers require: IBM JDK 6.0.1 or later DB2 V9 or
later (when used with DB2) WebSphere Application Server V7 or later
(when used with WAS) CICS V4.1 or later (when used with CICS) Other
middleware requirements: IRLM 2.3 DB2 9 or later CICS 3.1 or later
ISC using TCP/IP requires CICS 5.1 WebSphere MQ V7.0.1 or later
*Subject to change 71 2013 IBM Corporation
59. Introducing IMS 13 IMS 13 Hardware Prerequisites IMS 11,12
and 13 run only on 64 bit Processors running in z/Architecture mode
that supports the Long Displacement Facility ESA mode is not
supported by IMS 11, 12, or 13 For a list of System z machines see:
ibm.com/systems/z/hardware/ z900 machines must be at GA2 level
(microcode level 3G or later) 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
64.0.175.0 (Sept 2008) or higher 72 2013 IBM Corporation
60. Introducing IMS 13 IMS 13 Migration and Coexistence
Considerations IMS 13 supports migration/coexistence for IMS 11 and
IMS 12 DBRC Migration/Coexistence SPEs IMS 11: APAR PM53134 /
UK80026 IMS 12: APAR PM53139 / UK80027 IMS 13 supports RSR
migration/coexistence from/with IMS 11 and IMS 12 IMS 12 is the
last release to support the SECURITY system generation macro
Security Migration/Coexistence SPEs Allows RCLASS and SECCNT to be
coded via PROCLIB members prior to IMS 13 IMS 11: PM48203 / UK74050
IMS 12: PM48204 / UK74051 3 security exits no longer in IMS Nucleus
- now standalone only DFSCSGN0, DFSCTRN0, DFSCTSE0 DFSCSGN0 is now
called at IMS initialization 73 2013 IBM Corporation
61. Introducing IMS 13 IMS 13 Packaging Packaging Change Only
IRLM 2.3 will be distributed with IMS 13 IMS 13 Program Number:
5635-A04 FMIDs HMK1300 JMK1301 JMK1302 JMK1303 JMK1304 JMK1305
JMK1306 HIR2230 74 IMS System Services IMS Database Manager IMS
Transaction Manager IMS ETO IMS Recovery Level Tracker IMS Database
Level Tracker IMS Java on Demand IRLM 2.3 2013 IBM Corporation
62. Introducing IMS 13 IMS 13 Release Planning Guide -
GC19-3658-00 Release Planning Guide is Available from the z/OS
Information Centre:
http://pic.dhe.ibm.com/infocenter/dzichelp/v2r2/index.jsp 75 2013
IBM Corporation
63. Introducing IMS 13 IMS Strategic Objectives Reduce Total
Cost of Ownership Reduce MIPS usage Advanced autonomics IMS is
self-managing and self-tuning Extend the lead in availability,
scalability, and performance Consistently deliver IMS capacity
limits that are well beyond customer needs Provide IMS performance
metrics that help you grow your business securely Extend the
lifecycle of IMS applications and transactions Pervasive
integration capabilities enable reuse of trusted IMS resources
Enable high-volume transaction processing for next wave of
applications Big Data, next gen Web Services, Cloud, and more 76
2013 IBM Corporation