IMS V13 Overview_FtLauderdale - IMS UG Fort Lauderdale 2013

© 2011 IBM Corporation

®

IMS Version 13

IMS 13 Overview

American Express Ft. Lauderdale

October 15, 2013

Diane Goff, IMS Advanced Technical [email protected]

IMS Version 13

2

IMS 13 General Availability Announced!

IMS 13 GA announced on 10/1/2013

for availability on 10/25/2013

IMS Version 13

3

IMS 13: Lowest cost per transaction in the industry

• Affordability:

– Double-digit CPU reductions

• Simplicity:

– New Web interface, mobile enabled, for easier administration

– Expanded Eclipse-based function with IMS Explorer

– Easier IMS data access using SQL from COBOL and .NET apps

• Speed:

– 100,000+ reasons to migrate to IMS 13

– Dynamically “ALTER” databases

– IMS enhanced connectivity increases throughput for some Fast Path

workloads by more than 160%

Up to 10% Up to 15% Up to 62%CPU savings for

traditional workloads

CPU savings for specialized

workloads

CPU savings for Java

workloads

“..IMS 13 migrations have been really easy to implement and have run very smoothly. I have been really impressed by the ease of installing the new version and shipping it to our systems.…..A big ‘well done’ to your team."

UK-based Bank

Register for the IMS 13 and IMS Enterprise Suite 3.1 Webcast on October 29

IMS Version 13

4

IBM IMS

100,000 reasons to move to IMS 13

Still delivering the highest levels of performance, availability

security, and scalability in the industry.

#IBM_IMS

IMS 13 Speed: Record-Setting Benchmark

Actual TPS = 117,292

IMS Version 13

5

Celebrating IMS’s 45th Anniversary Worldwide

�Download & Print! http://bit.ly/IMS45th

�Snap Photos!

�Share!

5

IMS Version 13

6

IMS 13 - Agenda

� Status of IMS Versions

� Prerequisites, Migration, Coexistence

� System Enhancements

� Transaction Manager, Connectivity, and Integration Enhancements

� Database and DBRC Enhancements

6

IMS Version 13

7

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


– End of service has not been announced

� IMS Version 12



� IMS Version 13


– Currently in QPP program


IMS Version 13

8

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

– IRLM 2.3 if the IRLM is used

IMS Version 13

9

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

• WAS V7 or later

• CICS V4.1 or later

– DB Versioning requires implementation of the IMS Catalog

IMS Version 13

10

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

IMS Version 13

11

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)

IMS Version 13

12

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 64.0.175.0 (Sept 2008) or higher

IMS Version 13

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

� 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

IMS Version 13

14

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

� EAV enhancement for GSAM

� U240 timeout in an ESS call

IMS Version 13

15

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

16

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)

• 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

17

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

18

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

19

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 beenenabled 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

20

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

IMS Version 13

21

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

IMS Version 13

22

Overall Value of IMS Connect Enhancements

� Enhanced usability while providing better performance and diagnostics

� Increased resiliency to Abnormal Ends (ABENDs)

� Improved usability and manageability

IMS Version 13

23

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)

– 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

24

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

IMS Version 13

25

Benefits of the Concurrent Thread Enhancement (Increasing MAXPST)

� 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

IMS Version 13

26

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

� Benefits

– Improved performance, lower cost per transaction, reduced cost of ownership.

IMS Version 13

27

Reduced Total Cost of Ownership

� IMS 13 includes the following reduced TCO focus areas

– Specific Reduced TCO enhancements

– Other Reduced TCO enhancements

– External Subsystem Access Facility (ESAF) for Java Dependent

Regions

IMS Version 13

28

Specific Reduced TCO Enhancements …

� Exploitation of pageable 1M pages

– IMS 13 uses pageable 1 MB pages for certain storage pools and control blocks when this function is available.

• Pageable 1 MB pages are supported in z/OS V1.13 (web

delivery and PTFs required) and higher z/OS releases when

running on a IBM zEnterprise EC12 processor with Flash

Express.

– Pageable 1 MB pages can improve performance by reducing the

number of steps in dynamic address translation, and by improving

translation lookaside buffer (TLB) coverage.

IMS Version 13

29


� Support for memory-based data set ENQ management for dynamically allocated data sets (MEMDSENQMGMT)

– The MEMDSENQMGMT function provides the following benefits:

• Enables jobs and subsystems to use memory-based data set

ENQ management for dynamically allocated data sets, instead

of scheduler work area-based (SWA-based) data set ENQ management.

• Is faster than SWA-based data set ENQ management, and is

intended for jobs that allocate a large number of data sets, such

as IMS.

– If the MEMDSENQMGMT function is enabled on your z/OS system,

data set ENQs for dynamically allocated data sets are managed in

memory.

IMS Version 13

30


� zIIP Utilization Enhancement …

– In IMS Version 13 (“V13”), certain processing in the IMS Connect address space and in the IMS Open Database Manager (“ODBM”) address space as specified below may, when enclave SRB executionis enabled by a user, be executed under enclave service request blocks (“SRBs”). Enclave SRB execution may be enabled as unconditional ; or it may be enabled as conditional, based on the presence of at least one online zIIP during address space initialization. When enclave SRB execution is enabled, V13 will direct z/OS to authorize such work to be processed on an available zIIP.

Note that in an unconditional status, the user may enable such processing to be executed in enclave SRB mode when no zIIP is online or part of the user's System z environment. But, of course, no zIIP utilization could result. A user might request enclave SRB execution even in the absence of zIIPs, to allow the system to project how much work is eligible to run on zIIP and probably would if there were zIIP capacity available. See the PROJECTCPU parameter of the IEAOPTxx SYS1.PARMLIB member in z/OS MVS Initialization and Tuning Reference (SA22-7592) for further information.

IMS Version 13

31


� zIIP Utilization Enhancement …

– Except as otherwise described below, the following IMS Connect and ODBM processing can execute under an enclave SRB in V13:

• Processing of IMS Connect address space SOAP message threads forSOAP messages arriving via TCP/IP

• Processing of IMS Connect and ODBM address space Distributed Relational Database Architecture (“DRDA”) threads for DRDA requests arriving via TCP/IP

• Processing of IMS Connect address space Multiple System Coupling(“MSC”) threads for MSC messages arriving via TCP/IP

• Processing of IMS Connect address space Intersystem Communication ("ISC") threads for ISC messages arriving via TCP/IP

• Processing of ODBM address space threads for requests arriving through the CSLDMI API.

Note that any user exits called by the above processing will not execute under an enclave SRB. User exits are always given control in task control block (TCB) mode, and such exit instructions are not authorized to be processed on a zIIP. Also note that certain processing cannot, due to technical restrictions, execute under enclave SRBs. Such processing includes calling z/OS Resource Recovery Services (“RRS”), IMS DL/I call processing, and z/OS supervisor calls (“SVCs”). IMS switches from SRB mode into TCB mode to perform such processing, and thus such processing will not execute on a zIIP.|

IMS Version 13

32

Specific Reduced TCO Enhancements

� zIIP Utilization Enhancement

– Note: This information provides only general descriptions of the types and

portions of workloads that are eligible for execution on Specialty Engines (for

example, zIIPs, System z Application Assist Processors (zAAPs), and

Integrated Facility for Linux (IFL) (“SEs”)). IBM authorizes customers to use

IBM SEs only to execute the processing of Eligible Workloads of specific

Programs expressly authorized by IBM as specified in the “Authorized Use

Table for IBM Machines” provided at

www.ibm.com/systems/support/machine_warranties/machine_code/aut.html

(“AUT”). No other workload processing is authorized for execution on an SE.

IBM offers SEs at a lower price than General Processors/Central Processors

because customers are authorized to use SEs only to process certain types

and/or amounts of workloads as specified by IBM in the AUT.

IMS Version 13

33

Other Reduced TCO Enhancements …

� BPE dispatcher hot cache line prefetch

� Eliminate local lock obtain around buffer page fix for OSAM buffers

� DFSCPY00 improved SVC directory entry search algorithm and removal of IVSK instructions

� IMS logger LOG latch contention reduction

� IMS dispatcher optimization

� IMS page load service algorithm optimization

� Reduce unintentional cache sharing for common storage PSTs

� Shared queues local first optimization for program-to-program switch messages

� Type-2 processing for the IBM IMS Universal Drivers

IMS Version 13

34

Other Reduced TCO Enhancements

� Replace z/OS STORAGE calls in IMS Connect and OTMA with more efficient storage managers (CPOOL, DFSBCB).

� Hash OTMA destination blocks for faster access

� Allow Fast Path / OTMA syncpoint processing to be asynchronous, freeing the dependent region to process the next transaction earlier.

� General instruction optimization (using newer instructions, converting modules to branch relative addressing)

� Reduction of contention for the database block serialization latch

IMS Version 13

35

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

� Benefits

– Simpler, more efficient, and more consistent interface

IMS Version 13

36

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)

IMS Version 13

37

IMS Command Enhancements Overview

� 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)

� IMS repository command enhancements

� ISC over TCP/IP command enhancements

IMS Version 13

38

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

IMS Version 13

39

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

IMS Version 13

40

IMS DRD Enhancements …

� 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

IMS Version 13

41

IMS DRD Enhancements

� IMS Repository change list support

– allows DRD resource definition changes to be made when an IMS system is down and make those changes available to IMS when it

restarts

– the IMS change list is created in the IMS Repository for an IMS system

that is down when an IMPORT DEFN SOURCE(REPO) SCOPE(ALL)

command is issued and the resources and descriptors specified on the

IMPORT command are in the IMS' resource list.

• the IMS change list consists of the resource or descriptor names

and resource types. It is read during IMS warm and emergency restart. The resource definitions for the resource and descriptor

names in the IMS change list are imported from the repository at

end of warm or emergency restart after the IMS log is processed

IMS Version 13

42

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 aredefined 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

43

� 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)

Enhanced User Exit Services Added to More Control Region Exit Types

IMS Version 13

44

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

45

New IMS Startup Security Parameters

� RCLASS parameter added to DFSPBxxx PROCLIB member

– RCLASS support in DFSDCxxx PROCLIB member will remain

• DFSPBxxx RCLASS parameter value will override DFSDCxxx if specified in both

� SECCNT parameter added to DFSDCxxx PROCLIB member

� 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)

IMS Version 13

46

/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

IMS Version 13

47

/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

IMS Version 13

48

EAV Enhancement for GSAM

� IMS Version 13 extends support for extended address volumes (EAV)

to GSAM database data sets

� Available in IMS 12 via PM86782 / UK94966

� Benefits

– Can now allocate GSAM database data sets in the extended addressing

space (EAS) of an EAV

IMS Version 13

49

U240 timeout for long running External Subsystem (ESS) call in IMS dependent regions

� ABENDU240 will now be enforced in IMS dependent regions that arerunning in an External Subsystem (ESS) when time expires using IMS Timing Services

– IMS timing is established in BMP Regions using CPUTIME= and the STIMER= parameters on the BMP startup.

– MPP regions establish timing using the STIMER= parameter on the MPP startup and the PROCLIM= or PLCT/PLCTTIME parameters for the transaction being processed by the MPP.

� Prior to this change, ABENDU240 was delayed until after the External Subsystem returned to IMS

– Now when the Timeout routines detect processing in an ESS, they will schedule ABENDU240.

� Available in IMS 12 as PM81063 / UK94216

IMS Version 13

50

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

� EAV Enhancement for GSAM

� U240 timeout in an ESS call

IMS Version 13

51

IMS 13 Transaction Manager, Connectivity, and Integration Enhancements

� Callout function enhancements

� ISC Over TCP/IP

� OTMA enhancements

� Non-Discardable Message Exit (DFSNDMX0) enhancements

� Support for native SQL

� TM Resource Adapter Updates

� IBM IMS Enterprise Suite V3.1

– IMS Data Provider for Microsoft .NET

• Statement of Direction

� WebSphere DataPower Integration Appliance V6.0

� IMS Explorer for Administration

IMS Version 13

52

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.

IMS Version 13

53

Background

� DL/I ICAL support from previous IMS releases

– Provided synchronous callout capability to resources outside IMS

IMS SOAP GATEWAY

z/OS

IMS

Database

DB

Services

OT

MA

TM/CTL

Services

IMS

Connect

TCP/IP

user-written Client

WebSphere

IMS TM resource adapterApplication Program

ICAL

MPP/JMP/IFP/BMP/JBP

OTMADescriptor

OTMADescriptor

IMS Version 13

54

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

Database

IMS DB

services

IMS dependent

regionIMS TM

services

MPP, JMPIFP, MD BMP

OTMA

Application

Program

ICALIMS SOAP GATEWAY

IMS

Connect

TCP/IP

user-written Client

WebSphere

IMS TM resource adapter

IMS Version 13

55

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

ICAL

ICAL

IMS1

MPP2

IMS X

IMS2

MSC

Shared

Msg Queues

IMS Version 13

56


� Usage examples

– Applications can issue multiple ICALs to different destination TYPEs

• Synchronous callout

• Synchronous program switch

ICAL DEST1

ICAL TRANB

TRANAIMS 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

Destination Descriptor

TYPE(IMSTRAN)

1

23

4

5

6

7

GU, IOPCB

IMS Version 13

57


� 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

IMS Version 13

58

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

59

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

60

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

IMS Version 13

61

OTMA Enhancements

� OTMA (Open Transaction Manager Access) value proposition

– Strengthens IMS as a foundation for open integration technologies

• Used by:

– IMS Connect: clients include IMS TM resource adapter and WAS, WMB, WESB;

DataPower; IMS Soap Gateway, ...

– IMS MQ Bridge: clients include WMB, RYO, ...

– OTMA CI: clients include WOLA

– IMS Connect API: clients include DataPower

– ...

– All of which support cloud technologies and enterprise mobility

IMS Version 13

62

IMS 13 OTMA Enhancements ...

� Enhancements to OTMA destination descriptors

• Simplify asynchronous messaging to WMQ

• Remove the need to code the DFSYPRX0/DFSYDRU0 exits

• Provide dynamic change capability with the Type-2 commands

– New descriptor TYPE={MQSERIES}

• Provides asynchronous callout and messaging support (ISRT ALTPCB)

– Specification of EXIT={YES | NO}

• Determines whether or not the OTMA exits are to be called

– Corresponding enhancement to IMS Type-2 OTMADESC commands

• [CREATE | UPDATE | DELETE |QUERY] OTMADESC

– Recoverable across warm and emergency restarts

IMS Version 13

63


� A new global flood control option that enforces the global flood limit

– Rejects new transaction input and protects IMS from storage exhaustion

• Versus just a warning message

– Note: Individual Member level flood control is unchanged

• Warning at 80%, Rejection at 100%, Relief at 50%

• Enabled by

– Issuing “/DIS TMEMBER ALL INPUT xxx” command

• Previous releases caused only a warning

– Specifying INPT value in a special new member client descriptor

• Reserved name of DFSOTMA

IMS Version 13

64


� OTMA early termination notification

– Autonomic enhancement for higher availability that allows OTMA clients to be

informed of an IMS shutdown earlier in the termination process

• Potentially reduces unsuccessful attempts to send in new transaction

messages that cannot be processed

– Can expedite shutdown processing

– Planned outages (e.g., /CHE FREEZE | DUMPQ | PURGE)

• Sends resource monitor protocol message during Phase 1 of IMS shutdown

– Unplanned outages (e.g. abend)

• OTMA issues XCF IXCLEAVE immediately after the log buffers are purged

• Function being added to IMS 12: APAR PM73869

IMS Version 13

65

Enhancements for the Non-Discardable Messages Exit Routine

� Customer requirement for a new function to PSTOP an abendingtransaction

– 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

IMS Version 13

66

RYO

IMS.NET

Support for native SQL

� Native SQL Processor

IMS DB

IMS 13

IMSJDBC

DriverODBM

IMS

Connect

IMS

Catalog

IMS

JDBCDriver

Client Application

Java Enabled

Regions

Type 4

Type 2

IMS DB

IMS

Catalog

DRDADRDA

SQL

SQL

IMS

Native

SQL

Processor DLI

z/OS

MPP,IFP,BMP

Regions

COBOL

Native

SQL

IMS Version 13

67

IMS TM Resource Adapter

� IBM WebSphere Application Server V8.5 support

� IBM RACF password phrases to enhance the current support for RACF passwords

– This support is provided through the IMS 13 service process

IMS Version 13

68

STATEMENT OF DIRECTION: IMS Data Provider for Microsoft .NET

DRDA

IMS 13

Application Server

ODBMDATASTORE (NAME=IMSA)

ALIAS (NAME=IMS)

z/OS

TCP/IP

DDMIMS Connect

TCPIP

DRDA

PORT

8888

SCI

DRDA

SQLcalls

DRA

CCTL

ODBA

SCIOM

IMS DB

IMS CatalogPSB1

IMS

SQL

Call Handler

Command

SQL + Parameters

DataReader

Connection

DRDA Client

ADO.NET

Applications

Connection Pool

drdaserver.ims.com

Result set data

DataAdapter

DataSet

IMS Version 13

69

STATEMENT OF DIRECTION: IMS Data Provider for Microsoft .NET IBM intends, at a future time, possibly via its support and service processes, to

make available IMS Data Provider for Microsoft .NET as part of the IMS Enterprise Suite for Distributed Systems offering. It will be designed to provide standard SQL access to IMS data from Microsoft .NET applications.

The intention is to allow Microsoft .NET applications to transparently and directly read and manipulate IMS data without the need for intermediate steps and additional tooling to accomplish these tasks.

IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision.

The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.

IMS Version 13

70

WebSphere DataPower Integration Appliance V6.0 (5725-K52)

� IMS Connect Send/Receive Support

– enables a direct connection to an IMS transaction

� New capabilities (IMS 12 and later)

– IMS ICAL Synchronous Callout Support

• enables access from IMS transaction to external service

– IMS Database Support (requires the use of the IMS Catalog)

• enables a direct connection to an IMS database

IMS Version 13

71

IBM IMS EXPLORER FOR ADMINISTRATION

� Web Browser

– Graphically administer IMS Databases and transactions

– View IMSPlex

• visualize relationships between various IMS resources – transactions, programs and databases in one view

– Replacement for IMS Control Center

• Customers currently using the IMS Control Center should use IMS Explorer for Administration.

� Software requirements

– IMS Tools Admin Console (no-charge)

• IBM IMS Explorer for Administration is available through APAR PM94292 as an extension of the Administration Console component of IBM Tools Base for z/OS, V1.4

– IMS Version 12

• IMS Connect

• Common Service Layer OM and SCI

– Supported web browser

• Firefox, Internet Explorer, Safari

IMS Version 13

72

Summary of IMS 13 Transaction Manager, Connectivity, and Integration Topics

� Callout function enhancements

� ISC Over TCP/IP

� OTMA enhancements

� Non-Discardable Message Exit (DFSNDMX0) enhancements

� Support for native SQL

� TM Resource Adapter Updates

� IBM IMS Enterprise Suite V3.1

– IMS Data Provider for Microsoft .NET

• Statement of Direction

� WebSphere DataPower Integration Appliance V6.0

� IMS Explorer for Administration

IMS Version 13

73

IMS 13 Database and DBRC Enhancements

� Database Versioning

� HALDB Alter

� DEDB Alter

� DBRC Enhancements

IMS Version 13

74

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

� 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

75

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

IMS Version 13

76

� 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

Database Versioning Requirements

IMS Version 13

77

� 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

Database Versioning Implementation

IMS Version 13

78

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

� Benefit

– Make structural changes to a database while maintaining databaseavailability

IMS Version 13

79

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

IMS Version 13

80

FIELD 1

FIELD 1

FIELD 2 Space

FIELD 2 SpaceNew

FIELD 3

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

Example 1

Example 2

FIELD 1

FIELD 1 FIELD 2

FIELD 2 Space

New

FIELD 3Space

IMS Version 13

81

FIELD 1

FIELD 1

FIELD 2

New SpaceFIELD 2

Increase the length of an existing segment

Example 1

Example 2

FIELD 1

FIELD 1 FIELD 2

FIELD 2

New Space

Space

Space

IMS Version 13

82

HALDB Alter Prerequisites

� Software requirements

– CSL

• SCI

• OM

– DBRC RECON MINVERS (‘13.1’)

IMS Version 13

83

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

IMS Version 13

84

DEDB Alter Utility

� The new DEDB Alter utility is used to change the following itemswithout 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

IMS Version 13

85

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

IMS Version 13

86

Summary of IMS 13 Database Manager and DBRC Topics

� Database versioning

� HALDB Alter

� DEDB Alter

� DBRC enhancements

IMS Version 13

87

IMS 13 Highlights

� System

– IMS CONNECT enhancements

• XML Converter Enhancements

• Expanded Recorder Trace

Records

• Reporting of overall health to

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

� Database and DBRC

– Database Versioning

– HALDB Alter

– DEDB Alter

– DBRC support for HALDB Alter and

DEDB Alter

� TM, Connectivity, and Integration

– Synchronous program switch

– ISC TCP/IP Links

– OTMA destination descriptor

enhancements

– Support for Native SQL

– and more!

87

IMS Version 13

8888

IMS V13 Overview_FtLauderdale - IMS UG Fort Lauderdale 2013

Technology

Transcript of IMS V13 Overview_FtLauderdale - IMS UG Fort Lauderdale 2013