ims02 ims 13 overview - ims ug june 2013 melbourne

Introducing IMS 13June 2013

Alison Coughtrie European IMS Architecture Team

© 2013 IBM Corporation

Introducing IMS 13

© 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 IBM’S CURRENT PRODUCT PLANS AND STRATEGY, WHICH ARE SUBJECT TO CHANGE BY IBM WITHOUT NOTICE. IBM SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES ARISING OUT OF THE USE OF, OR OTHERWISE RELATED TO, THIS PRESENTATION OR ANY OTHER DOCUMENTATION. NOTHING CONTAINED IN THIS PRESENTATION IS INTENDED TO, NOR SHALL HAVE THE EFFECT OF, CREATING ANY WARRANTIES OR

Important Disclaimer

© 2013 IBM Corporation2

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

Introducing IMS 13

European IMS Architecture Team (EIAT)

A Team of “IMS Architecture” specialists in Europe

• Technical Team Executive: Hélène Lyon

• Operate across Europe and MEA

Team Mission

• Confirm and secure existing IMS workload and seek opportunities to derive new benefit and workload on existing systems.


and workload on existing systems.

Focus on Face-to-Face with customers

• Manage European IMS Accounts – the “Heat Map”

• Understand role of z & IMS in customer business

Focus on IMS Value and IMS positioning in IBM software capabilities• IMS Apps modernization – Transactional & Batch workload

• IMS Data governance

Focus on IMS Buzz• Promote IMS modernization to the main European IT Actors

Work with IBM SO and other outsourcers

Team with GSE User’s Group

• Participate in IBM sponsored events

Introducing IMS 13

Agenda

QPP & Status of IMS Versions

System Enhancements

Database and DBRC Enhancements


Transaction Manager and Integration Enhancements

Prerequisites, Migration, Coexistence

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


– 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

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


• Will be withdrawn from Marketing on September 9, 2013


• Will be withdrawn from Marketing on September 9, 2013• End of service has not been announced

IMS Version 12


• 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

Introducing IMS 13

IMS 13 System Enhancements



Introducing IMS 13


• 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


• IMS Security Enhancements

• /DIAGNOSE Command Enhancements

Introducing IMS 13

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)


• Reporting of overall health to Workload Manager (WLM)

• Configurable TCP/IP backlog (queue) size

• Dynamic creation of Ports and Datastores via command

Introducing IMS 13


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

Reduced Time


Benefits:

• Enhances the flexibility of converter usage

• Directly impacts IMS Soap Gateway environments

Web Service Client

(.NET, SAP, java, etc.)

IMS SOAP IMS SOAP GatewayGateway

IMSIMS

Connect

z/OS

HTTP / SOAP TCP/IP / XML

Windows/AIX/zLinux/zOS

SOAP Envelopewith XML message XML message

XML ConverterXML Converter

IMS message

Introducing IMS 13

IMS Connect Enhancements …

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

Reduced Time


Benefits:

• Improved efficiencies during error conditions

• Eliminates IMS Connect restart and user interactions

• Directly impacts IMS Soap Gateway environments

Web Service Client

(.NET, SAP, java, etc.)

IMS SOAP IMS SOAP GatewayGateway

IMSIMS

Connect

z/OS

HTTP / SOAP TCP/IP / XML

Windows/AIX/zLinux/zOS

SOAP Envelopewith XML message XML message

XML ConverterXML Converter

IMS message

Introducing IMS 13


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)

Reduced Time


• 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

Introducing IMS 13



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)

Reduced Time


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

Introducing IMS 13



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

workload balancing

Coding a distribution method of SERVERWLM

VIPADYNAMIC …

VIPADISTRIBUTE DEFINE DISTMETHOD SERVERWLM

The “health” of the

IMS Connect is

directly related to

the percentage of

available sockets.

As clients connect,


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 ;SHARED PORT FOR HWS. USING HEALTH REPORTED

TO WLM

Benefits:

• Allows WLM to know when resources are constrained or available

• Minimizes the possibility of assigning work that IMS Connect is unable to

handle

As clients connect,

the health value

reported to WLM

by IMS Connect

will start to go

down.

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

Actual value used is the smaller of IMS Connect’s TCPIPQ value and SOMAXCONN


Actual value used is the smaller of IMS Connect’s TCPIPQ value and SOMAXCONN

in TCP/IP

Benefits:

• Provides a configurable option to increase the backlog queue size 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

Introducing IMS 13



• 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

Introducing IMS 13



• 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

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


Introducing IMS 13

Increase Number of Concurrent Application Threads

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

4 x More Applications!


Note: Reducing MAXPST= requires a Coldstart

Benefits:

• Increased capacity and scalability for IMS systems

• Allows vertical growth

• More dependent regions for use with synchronous callout and program switch

31 dependent regions - 1980 (IMS 1.1.6)999 dependent regions - 1995 (IMS 5.1)4095 dependent regions - 2013 (IMS 13)

MAXPST should no longer be a limiting factor in IMS Growth

Introducing IMS 13

IMS 13 Highest Efficiency,


IMS 13 Highest Efficiency, Lowest Total Cost of Ownership

Introducing IMS 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 path length

Reduced Cost


• 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

Introducing IMS 13

Specific Reduced TCO Enhancements

IMS logger LOG latch contention reduction

• Improves usage of log latch and log buffer management for increased logging bandwidth and more efficient processing

Shared queues local first optimization now applies to program-to-program switch

messages as well as ordinary input messages

• Avoids false scheduling on another IMS when the local IMS can process the program-to-program switch message

Exploitation of pageable 1M pages

Reduced Cost


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.

Introducing IMS 13

Specific Reduced TCO Enhancements …

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)

Reduced Cost


SYSTEM MEMDSENQMGMT(ENABLE|DISABLE)

Introducing IMS 13

Other Reduced TCO Enhancements

• OTMA YTIB chain changed from a single linked list to a hash table, to improve FINDDEST performance.

• Convert OTMA and IMS Connect STORAGE calls to CPOOL.

• Remove unnecessary clearing of OTMA buffers.

• DFSCPY00 improved SVC directory entry search algorithm and removal of

IVSK instructions.

• CQS mainline modules changed to use branch-relative branching.

Reduced Cost


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

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


Benefits:

• Improved manageability for CQS

Introducing IMS 13

IMS Dynamic Resource Definition with Repository Enhancement

IMSRSC Repository Datasets Contain:

Stored resource definitions for DRD resources for one or more DRD-enabled IMS systems

• Programs / transactions / databases / FP routing codes and descriptors

Resource lists for each IMS

• Contains resource names and resource types that can be processed by an IMS system

IMS Change lists – new in IMS 13

• Contain resource and descriptor names that were imported using the IMPORT


• Contain resource and descriptor names that were imported using the IMPORT

SCOPE(ALL) command when an IMS was down

• Behind the scenes, a separate IMS change list is actually created for each

resource/descriptor type

• Applied at next warm/emergency restart after IMS log is processed – internal import is

done

• IMS change list is deleted at the end of warm/emergency restart and at end of coldstart

Introducing IMS 13

IMS DRD Repository Enhancements …

Support for the IMS repository is 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


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

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

Reduced Time


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

Introducing IMS 13

Refreshable User Exits

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)

Reduced Time


• 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

Introducing IMS 13

SECURITY Macro removed from SysGen

System Definition macro SECURITY is no longer used as part of the IMS

system generation process

• All security settings can be defined as IMS startup parameters through PROCLIB

members

• RCLASS parameter added to DFSPBxxx

RCLASS also supported in DFSDCxxx

DFSPBxxx RCLASS parameter value overrides DFSDCxxx if both specified

Reduced Time


DFSPBxxx RCLASS parameter value overrides DFSDCxxx if both specified

• SECCNT parameter added to DFSDCxxx

• Other Security settings continue to be specified in DFSPBxxx

SECLVL parameter is replaced by RCF, TRN and SGN in DFSPBxxx

TYPE parameter is replaced by ISIS in DFSPBxxx

Benefits:

• Simplified system generation process

• Easier method to update security related settings

Introducing IMS 13

Preconditioning IMS 11 and 12 for SECURITY change

New parameters introduced to IMS 11 and IMS 12

Allows preconditioning by specifying new security settings

prior to IMS 13

• RCLASS added to DFSPBxxx

• SECCNT added to DFSDCxxx

• IMS 11 PM48203/UK74050; IMS 12 PM48204/UK74051


• IMS 11 PM48203/UK74050; IMS 12 PM48204/UK74051

If specifying RCLASS in DFSPBxxx, the following APARs

avoid an unnecessary DFS1921I error message

• IMS 11 PM72199/UK82616; IMS 12 PM73558/UK82617

Benefits:

• Simplified migration process

• Easier method to update security related settings

Introducing IMS 13

Security User Exits removed from Nucleus

User exits DFSCSGN0 (Signon/Signoff), DFSCTRN0 (Tran. Authorization) and DFSCTSE0 (Security Reverification) now linked separately, loaded from

STEPLIB (if present) into 31-bit storage

New DFS1937I message indicates which user exits have been loaded

• Can be used in automation to ensure that exits are being used

DFSCSGN0 now called at IMS initialization

• Storage can be obtained and shared with the other exits using a new parameter that

contains the storage address

Reduced Time


contains the storage address

Benefits:

• Simplifies process to customize IMS with user exits

• Simplifies writing of user exit DFSCSGN0

• Reduces 24-bit private virtual storage usage

Introducing IMS 13

/DIAGNOSE Command Enhancements

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

Reduced Time


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

Introducing IMS 13

Summary of IMS 13 System Topics


Concurrent Application Threads

Reduced Total Cost of Ownership (TCO)

IMS CQS Enhancement

IMS DRD Enhancements

IMS User Exit Enhancements

IMS Security Enhancements


IMS Security Enhancements

/DIAGNOSE Command Enhancements

Introducing IMS 13

IMS 13 Database and DBRC


IMS 13 Database and DBRCEnhancements

Introducing IMS 13

IMS 13 Database and DBRC Enhancements

HALDB Alter

DEDB Alter

Database Versioning

DBRC Enhancements


Introducing IMS 13

HALDB Alter

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

Improved Availability


A

B C

A

CB

Benefits:

• Improves IMS HALDB availability by providing structure changes without

taking the database offline

• Provides flexibility in rolling database changes into the system

Introducing IMS 13

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

Introducing IMS 13

Database records that have

been copied to the output

Locked

Database

Records

Database records yet to beDatabase records yet to be

copied to the outputcopied to the output

CursorCursorInput

Data Sets

OLR Overview - Reminder

A thru J and X

Cursor points to root key or RBA

of last committed reorganized

record


Database records that have

been copied from the input

Output

Data Sets

Database records are copied from the input to the output datasets in UORs

UORUOR : One or more HALDB records (root and all of its dependent segments) that are reorged within one commit boundary.

M thru V and Y

Database records Database records can becan be

read, replaced, read, replaced, insertedinserted

or deletedor deleted

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


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

Introducing IMS 13

HALDB Alter Online Processing (cont’d)

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

Introducing IMS 13

HALDB Alter Prerequisites

Software requirements

• CSL

SCI

OM

• DBRC RECON MINVERS (‘13.1’)



Introducing IMS 13

Fast Path Data Entry Database (DEDB) Alter

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

Introducing IMS 13

DEDB Alter Summary

� IMS 13 adds ability to dynamically change DEDB specifications

– Users can dynamically change UOW, SIZE, ROOT and Randomizer while DEDB is online

– New DEDB Alter utility is used to make changes



Benefits:

• Improves DEDB Area availability by providing definitional changes without

taking the Area offline

• Provides flexibility in rolling Area changes into the system

Introducing IMS 13

Database Versioning Overview

Allows programs to use different versions of the same physicaldatabase

• Multiple views of the physical data maintained in the IMS Catalog

• Existing applications can remain unchanged when the physical structure of

the database changes

Usability


• 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

Introducing IMS 13

Database Versioning Overview (cont’d)

Database Versioning supports the following database types

• DEDB

• HDAM

• HIDAM

• PHDAM

• PHIDAM

IMS Catalog


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

Introducing IMS 13

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

Database Versioning requires enablement of the IMS catalog

• DBD definitions for versioned databases must be in the IMS catalog

Database Versioning Overview (cont’d)

IMS Catalog


• DBD definitions for versioned databases must be in the IMS catalog

Application programs can select 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

Introducing IMS 13

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=

Database Versioning Implementation

IMS Catalog


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

Introducing IMS 13

Solution Overview – Database Versioning Flow #1

DBJK21 V1DBJK22 V1DBJK23 V1

ACBLI B

DBJK21 V0,V1DBJK22 V0,V1

IMS Catalog

DBJK21 V1DBJK22 V1DBJK23 V1

DBDLIB

PSBJK

PSBLIB

PSBGEN

--------------------------

PCB

--------------------------

PSB=PSBJK Source

DBJK21 V1

DBD Source

DBJK22 V1

DBJK23 V1

DBDGEN

PSBGEN

ACBGEN

��

Version “V1” of DBDs put into

ACBLIB & Catalog��


DBJK21

DBJK22

DBJK23

Application

IMS

DBJK22 V0,V1DBJK23 V0,V1

PSBJK--------------------------

DBJK21 V0

DBJK22

DBJK23 V1

DBJK21 V0

DBJK22 V1

DBJK23 V1

DLI

Retrieve DBJK21 from Catalog

DBJK21 V1

DBJK22 V1

DBJK23 V1

Active

��

Database Versioning enabled -> data

returned to app at V0 & V1 levels

��

��DBJK21

DBJK22

DBJK23

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


• PTF UK80027

Allow IMS 12 to understand IMS 13 RECON records

Introducing IMS 13

Summary of IMS 13 Database Manager and DBRC Topics

• HALDB Alter

• DEDB Alter

• Database Versioning

• DBRC Enhancements


Introducing IMS 13

IMS 13 Transaction Manager and


IMS 13 Transaction Manager andIntegration

Introducing IMS 13

IMS TM and Integration Enhancements

• Callout function enhancements

• ISC Over TCP/IP

• OTMA enhancements


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


Introducing IMS 13

Background

DL/I ICAL support from previous IMS releases

• Provided synchronous callout capability to resources outside IMS

z/OS

IMS

OT

MA

TM/CTL

WebSphere

IMS TM resource adapterApplication Program

MPP/JMP/IFP/BMP/JBP


IMS SOAP GATEWAY

Database

DB

Services

OT

MA

TM/CTL

Services

IMS

Connect

TCP/IP

user-written Client

IMS Connect API

Program

ICAL

OTMADescriptor

OTMADescriptor

Introducing IMS 13

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

Usability


Database

IMS DB

services

IMS dependent

regionIMS TM

services

MPP, JMP

IFP, MD BMP

OTMA

Application

Program

ICALIMS SOAP GATEWAY

IMS

Connect

TCP/IP

user-written Client

WebSphere

IMS TM resource adapter

Introducing IMS 13


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 within the calling program’s

UOW

Usability

MPP1

MPP4

MPP3

ICAL

ICAL

ICAL

IMS1

MPP2

IMS X

IMS2

MSC

Shared

Msg Queues


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

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


same IMS or IMSplex

WASApplication

WASIMS

Connect

IMS

MPPx

MPP4

MPP2

MPP3

ICALICALICALICAL

WASApplication

WASIMS

ConnectIMS

MPP4

MPP2

MPP3

MPP1

MPP1

Introducing IMS 13


Usage examples:

Applications can issue multiple ICALs to different destination TYPEsSynchronous callout

Synchronous program switch

ICAL

TRANAIMS CTL Region

IMS Connect

WebSphere

IMS TMRA

IMS SOAP

Gateway

OTMA

Destination

1

2

GU, IOPCB

Usability


ICAL DEST1

ICAL TRANB

Gateway

TCP/IP

RYO pgm

MSG-Q

Destination Descriptor

TYPE(IMSCON)

TRANB

GU IOPCB

Destination Descriptor

TYPE(IMSTRAN)

23

4

56

7

Introducing IMS 13


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

Usability


LTERM Override

ALTPCB destinations

Multiple ICALs

Recursive requests

Holding database locks across an ICAL request

• Increased importance for performance tooling

Benefits:

• Provides a DL/I call to request a synchronous service regardless of where that

service resides

• Simplifies integration and improves usability

Introducing IMS 13

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 (AIB return code= x’100’ & reason code=x’00C’)

• IMS 13 keeps a copy of the entire response message in the control region private

storage


storage

Benefits:

• 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

Introducing IMS 13

Asynchronous Callout to WebSphere MQ via MQ Bridge

OTMA Descriptor Enhancements

• New TYPE=MQSERIES to define WebSphere MQ destination

• Provides asynchronous callout and messaging support (DL/I ISRT ALTPCB)

• New option to allow exits to be called to override descriptor

Applies to all destination descriptors

Corresponding enhancement to IMS Type-2 OTMADESC commands

• [CREATE | UPDATE | DELETE |QUERY] OTMADESC

Recovered across warm and emergency restarts

Usability


Recovered across warm and emergency restarts

Benefits:

• Eliminates need to write an OTMA user exit to recognize an MQ destination

• Simplifies integration and improves usability

• Provides dynamic change capability with the Type-2 commands

IMS

ApplicationWebSphere

MQIMS

OTMA

Introducing IMS 13

OTMA Early Termination Notification

Allows OTMA to leave the XCF group earlier in termination processing

• Notifies OTMA clients (IMS Connect, WebSphere MQ, OTMA Callable Interface) of the

termination (scheduled & unscheduled) via their XCF Group Exit

Client can then route requests to other systems

• Addresses issues associated with transaction messages being accepted but not

processed

Function added to IMS 12: PM73869/UK90361

Reduced Time


Benefits:

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

informed of an IMS shutdown in order to choose more timely alternatives

• Potentially reduces unsuccessful attempts to send in new requests

• Can expedite shutdown processing

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

ApplicationDB2 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

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


• 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

Introducing IMS 13

ISC Over TCP/IP

Either IMS or CICS can initiate the request

IMS

1

2 3

456

INPUT INPUT Transaction

REPLY REPLY

IMSConnect

CICS

SCI TCP/IP

INPUT

REPLY

tranOR

tran

Msg SwitchIMS

End User Process

transaction


Initiating a CICS transaction from IMS using an ISC TCP/IP connection

REPLY

IMS

23

4 5REPLY REPLY

IMSConnect CICS

SCI TCP/IP

Initiating an IMS transaction from CICS using an ISC TCP/IP connection

CICSEnd UserProcess

transaction

Tx.

1Tx. (Start/Retrieve)INPUT

Transaction

6

REPLY

Introducing IMS 13

IMS TM and Integration Enhancements

• Callout

• OTMA Enhancements

• JDR use of ESAF

• ISC over TCP/IP to CICS


Introducing IMS 13

HALDB Alter

DEDB Alter

Database Versioning


OTMA Descriptor Support for WebSphere MQ Bridge

OTMA Early Termination Notification

OTMA Enhancements

IMS 13 QPP At a Glance – … And more to come!

Database Management

Transaction Management andIntegration


OTMA Enhancements

JDR Support for ESAF

IMS to CICS via ISC over TCP/IP


Reduce TCO

Increase number of concurrent applications

Elimination of SECURITY Macro

Standalone Security User Exits

Log Latch Reduction

User Exit Enhancements

DIAG Command Enhancements

Integration

Systems Management

Introducing IMS 13

DBRC: Allow IMS 11 and IMS 12 migration to IMS 13

Syntax Checker: Support for new and changed parameters

IMS 13 QPP At a Glance – … And more to come!

Migration andCoexistence


Introducing IMS 13

IMS 13 Prerequisites, Packaging


IMS 13 Prerequisites, Packaging and Migration

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

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

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


• 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

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

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 IMS System Services

JMK1301 IMS Database Manager

JMK1302 IMS Transaction Manager


JMK1303 IMS ETO

JMK1304 IMS Recovery Level Tracker

JMK1305 IMS Database Level Tracker

JMK1306 IMS Java on Demand

HIR2230 IRLM 2.3

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


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

Introducing IMS 13

Questions?


Contact [email protected]

ims02 ims 13 overview - ims ug june 2013 melbourne

Technology