®

IMS Version 13

IMS 13 Overview

© 2011 IBM Corporation

IBM Advanced Technical Skills

IMS Version 13

IMS 13 System Enhancements

� IMS Connect Enhancements

� Concurrent Application Threads

� Reduced Total Cost of Ownership (TCO)

� IMS Command Enhancements

� IMS CQS Enhancement

2

� IMS CQS Enhancement

� IMS DRD Enhancement

� IMS User Exit Enhancements

� IMS Security Enhancements

� /DIAG Command Enhancements

IMS Version 13

XML Converter Enhancements

� Support for extending the current limit of 100 up to 2000 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)

3

– 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

IMS Version 13

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

4

(HWSXMLA0) after the ABEND limit ABLIM has been reached

� Benefit

– Improved efficiencies during error conditions

• Eliminates IMS Connect restart and user interactions

IMS Version 13

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

5

• 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 Version 13

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

6

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 Version 13

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

7

– 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

IMS Version 13

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

8

• 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

IMS Version 13

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!

– 31 dependent regions - 1980 (IMS 1.1.6)

9

– 31 dependent regions - 1980 (IMS 1.1.6)

– 999 dependent regions - 1995 (IMS 5.1)

– 4095 dependent regions - 2013 (IMS 13)

� Related parameters

– MAXPST=

– PST=

– MAXTHRDS= for ODBM

– MAXTHRDS=, MINTHRDS= for DBCTL

IMS Version 13

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

10

– 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.

IMS Version 13

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)

11

� 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

� Benefits

– Simpler, more efficient, and more consistent interface

IMS Version 13

IMS Command Enhancements

� Enhancements are focused on type-2 commands for the Operations Manager (OM) environment

� Benefits

– Support of new IMS 13 functions

12

– Improved manageability

IMS Version 13

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

13

� Benefits

– Improved manageability for CQS

IMS Version 13

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

14

� 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

IMS Version 13

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

15

� Move security user exits out of the IMS nucleus into 31-bit storage

– DFSCSGN0 Signon/off Security

– DFSCTRN0 Transaction Authorization

– DFSCTSE0 Security Reverification

IMS Version 13

/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

16

– Improved turn-around time in problem resolution

IMS Version 13

IMS 13 Transaction Manager and Connectivity Enhancements

� Callout function enhancements

� ISC Over TCP/IP

� OTMA enhancements

� Non-Discardable Message Exit (DFSNDMX0) enhancements

17

IMS Version 13

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.

18

IMS Version 13

Synchronous Program Switch

� New capability that enhances the DL/I ICAL support

� 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

• Reduces unnecessary network traffic when accessing multiple applications

19

• Reduces unnecessary network traffic when accessing multiple applications in the same IMS or IMSplex

WASApplication

WASIMS

Connect

IMS

MPPx

JMP4

JMP2

MPP3

ICALICALICALICAL

WASApplication

WASIMS

ConnectIMS

JMP4

JMP2

MPP3

MPP1MPP1

Before ICAL support processing Flow

ICAL support processing Flow

IMS Version 13

Support for Truncated Messages

� New subfunction capability that enhances the DL/I ICAL support

� 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

20

� 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 Version 13

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

21

• Allows an all inclusive TCP/IP solution for networks

IMS Version 13

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

22

– Addresses issues associated with transactions messages being accepted but not processed

– Function being added to IMS 12: APAR PM73869

IMS Version 13

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

23

� 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

IMS Version 13

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

24

Messages exit routine

– IMS 11 APAR PM67950 / PTF UK81040

– IMS 12 APAR PM45943 / PTF UK71989

– Included in IMS 13

IMS Version 13

IMS 13 Database and DBRC Enhancements

� Database Versioning

� HALDB Alter

� DEDB Alter

� DBRC Enhancements

25

IMS Version 13

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

26

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

� Benefit

– Minimizes impact and reduces cost associated with making and coordinating coding changes to affected application programs when a physical database structure changes

IMS Version 13

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

27

� Benefit

– Make structural changes to a database while maintaining database availability

IMS Version 13

FIELD 1

FIELD 2 Space

FIELD 2 SpaceNew

FIELD 3

Add a new field to space at the end of a segment

Example 1

FIELD 1

28

FIELD 1

FIELD 3

Example 2

FIELD 1 FIELD 2

FIELD 2 Space

New

FIELD 3Space

IMS Version 13

FIELD 1

FIELD 2

New SpaceFIELD 2

Increase the length of an existing segment

Example 1

FIELD 1

29

FIELD 1

Example 2

FIELD 1 FIELD 2

FIELD 2

New Space

Space

Space

IMS Version 13

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

30

– 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

IMS Version 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

31

– 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

IMS Version 13

IMS SOA Integration Enhancements

� IMS Enterprise Suite V2.2

– SOAP Gateway

– Explorer for Development

32

IMS Version 13

End-to-end Transaction Tracking – Provider Scenario(correlation based on Tracking ID)

IMS ES 2.2SOAP

Gateway

IMS Connect

OTMA

IMS 13

IMS App

HorizontalTracking ID +(XML) request data

messageexits*

HorizontalTracking ID + message data

Tracking ID

HorizontalTracking ID +(XML) response data + CSM

HorizontalTracking ID +

Transaction Tracking API

Request withoptional tracking ID

response

Route / generate

Tracking ID

Soap Client

33

eventexit *

message data

IMSLog record

SOAPGateway

Transaction log

Transaction Tracking API

Monitoringdata*

Horizontal and VerticalTracking IDs

ITCAMIMS ConnectExtensions

IMS Connect

Extensionsjournal

Problem Investigator

Performance Analyzer

IMSPerformance Analyzer

IMSProblem Investigator

records events withTracking ID

Tracking ID

Horizontal and VerticalTracking IDs

IMS Version 13

IMSSOAP

Gateway

IMS SOAP Gateway WS-Security SAML unsigned tokens for synchronous callout applications

z/OS

IMS

TM/CTL

ServicesIMS

Connect

HWS1

Web

Service

Application

Program

ICAL

DEST1

Resume TPIPE TPS

TPS

DEST1TPSHWS1HWSXMLA0

CORTKN

USERA

XML

USERA

Initiating ClientUSERA

CORTKN

USERA Java

34

HWS1 DEST1OT

MA

HWSXMLA0XMLCNV1D

ACK

Send_ONLY

HWSXMLA0

XML ConverterXMLCNV1D

CORTKN

USERA

XML

USERA

Request

data

Response

data

XML

USERA

XML

USERA

Connection BundleTPS

USERA

CORTKN

USERA

Custom

Authentication

IMS Version 13

IMS ES 2.2 ExplorerImporting data structures

� Importing data structures

– metadata field layouts imported from data structure files (COBOL copybooks or PL/I includes)

� Procedure

� DBD file

– select Import COBOL or PL/I Data Structures.

35

– select Import COBOL or PL/I Data Structures.

– select the data structure file that contains the COBOL copybooks or PL/I includes that you want to import.

– Optional:

• using source from the IMS catalog, specify the map and case name to import the data structure

� Benefit

– RDz is not required

– no need to shell share with RDz

IMS Version 13

IMS Explorer V2.2 Joint Project with IBM Data Studio V3.2

� IBM® Data Studio support for pureQuery with IMS

– Can generate pureQuery code for IMS databases

• All generated SQL supported by IMS

36

Annotated pureQuery interface

IMS Version 13

SQL Parsing in IMS � IMS intends to invest in SQL Call Handler

� Example with IMS SQL call handler

– How much money has my insurance company paid out in claims for the year 2011?

– SELECT SUM(CLAIMAMOUNT) FROM CLAIMS WHERE YEAR=2011

z/OSClient ApplicationSQL Call

37

IMS DB

IMSJDBCDriver

Claims$2432$41

…$6255+ ________

$797439097

Claims$2432$41

…$6255

IMS SQLCall Handler

$797439097

Total Claims

$797439097

IMS Version 13

SQL Parsing in IMS

IMS intends to invest in SQL Call Handler

� Open Database End to End flow with native SQL

z/OSIMS

JDBCDriver ODBM

IMSConnect

DRDADRDA

38

RYO IMS DB

IMSCatalog

IMSJDBCDriver

IMS Java

enabled

Dep Region

Type 4

Type 2

IMS DB

IMSCatalog

SQL

SQL

IMSSQLCall

Handler DLI

IMS Version 13

IMS SQL Support for COBOL

� Requirement

– Customers need access to IMS databases using SQL from IMS managed COBOL application programs

� Solution

– IMS intends to invest in COBOL SQL Calls

– Convert SQL statements to DL/I database calls

• Handle SQL errors

39

• Handle SQL errors

� Benefits

– Reduce application development cost by leveraging existing SQL skills

– Expands IMS database access for application and database developers.

IMS Version 13

.NET Data Provider Requirement

DRDA

IMS

Application Server

ODBMDDMIMS Connect SQL

calls

SCIOM

IMS

SQL

Call Handler

Command

SQL + Parameters

DataReader

ADO.NET

Applications

Result set data

DataAdapter

DataSet

40

ODBMDATASTORE (NAME=IMSA)

ALIAS (NAME=IMS)

z/OS

TCP/IPDDM

TCPIP

DRDA

PORT

8888

SCI

DRDA

calls

DRA

CCTL

ODBA

IMS DB

IMS CatalogPSB1

Call Handler

Connection

DRDA Client

Connection Pool

drdaserver.ims.com

IMS Version 13

Requirement: DataPower to IMS DB

DataPower

IMS

JDBC

Routing/

data

SQL DRDA

sends /

ODBMIMS

Connect

DRDA

Back

41

JDBC

Driver

data

transformation

sends /

receives

sends /

receives

IMS DB

IMSCatalog

IMS DB

IMSCatalog

SQL

IMSSQLCall

HandlerDLI

End

services

IMS Version 13

SSA Enhancement - Get by Offset

� Solution

– IMS 12 APAR PM65139 / PTF UK81837 & UK81838

• New SSA command code “O”

• Enhanced database SSA processing with ability to search for data in a segment by specifying a field position and length instead of a field name

• Contains core IMS database code

APAR & PTFs

CLOSED

4242

• Contains core IMS database code

– IMS 12 APAR PM69378 / PTF UK81917

• Enhanced IMS Universal Drivers to allow SQL predicates containing ‘columns’ not defined in the DBD by internally converting ‘columns’ to position and length for SSA qualification

• Contains IMS universal driver code

APAR & PTF

CLOSED

IMS Version 13

IMS 13 Highlights

� System

– IMS CONNECT enhancements

• XML Converter Enhancements

• Expanded Recorder Trace Records

• Reporting of overall health to Workload Manager (WLM)

� Database and DBRC

– HALDB Alter

– DEDB Alter

– Database Versioning

– DBRC support for HALDB Alter and DEDB Alter

� TM and Connectivity

43

Workload Manager (WLM)

– Concurrent application threads

– Reduced Total Cost of Ownership (TCO)

– Elimination of SECURITY Macro

– User Exit enhancements

– JDR support for ESAF

– DIAG command enhancements

� TM and Connectivity

– Synchronous program switch

– ISC TCP/IP Links

– OTMA destination descriptor enhancements

– and more!

43

IMS Version 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

44

– Generally available on October 30, 2009

– 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

IMS Version 13

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 (5696-234)

• APAR OA39392 / PTF UA66823 is required for z/OS 1.13 for IMS V13

45

• 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

IMS Version 13

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 6.0.1 or later

• DB2 V9.1 or later

46

• WAS V7 or later

• CICS V4.1 or later

– DB Versioning requires implementation of the IMS Catalog

* subject to change

IMS Version 13

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

47

• 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

IMS Version 13

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: www.ibm.com/systems/z/hardware/

� z900 machines must be at GA2 level (microcode level 3G or later)

48

� z900 machines must be at GA2 level (microcode level 3G or later)

IMS Version 13

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

49

• 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

IMS Version 13

Supported Migrations and Coexistence

� IMS 12 to IMS 13

– Upgrade RECONs from IMS 12 to IMS 13

– Databases are compatible

– Application programs are compatible

50

� IMS 11 to IMS 13

– Upgrade RECONs from IMS 11 to IMS 13

– Databases are compatible

– Application programs are compatible

� Check Release Planning documentation at GA for additional prerequisites/coexistence/migration items