© 2011 IBM Corporation

®

IMS Version 13

IMS 13 Overview

IBM Advanced Technical Skills

IMS Version 13

2

IMS 13 - Agenda

� Status of IMS Versions

� Prerequisites, Migration, Coexistence

� System Enhancements

� Transaction Manager and Connectivity Enhancements

� Database and DBRC Enhancements

2

IMS Version 13

3

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

– 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

4

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

* subject to change

IMS Version 13

5

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

* subject to change

IMS Version 13

6

Software Prerequisites ...

� Minimum software levels for optional functions ...

– IMS 13 supports interactions with

• DB2: Versions 9, 10

• CICS: Versions 3.2, 4.1, 4.2, 5.1

– CICS 5.1 (newly announced) is required for ISC TCP/IP support

• Requires z/OS 1.13

• MQ for z/OS: Versions V7.0.1, V7.1

– Note V6 EOS was September 2012

– 7.01 introduced MQ message expiry interfacing with IMS transaction expiration

– 7.1 enhanced the expiry support and support for OTMA resource monitoring

protocol messages

* subject to change

IMS Version 13

7

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

8

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

9

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

10

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

IMS Version 13

11

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

12

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(I, 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

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

� Benefit

– Improved efficiencies during error conditions

• Eliminates IMS Connect restart and user interactions

IMS Version 13

14

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

15

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

16

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

17

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

18

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

19

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

20

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

21

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

22

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

23

Specific Reduced TCO Enhancements

� IMS logger LOG latch contention reduction

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

� Shared queues local first optimization now applies to program-to-program switch messages as well as ordinary input messages

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

� Exploitation of pageable 1M pages

– Based on usage of new zEC12 processors with Flash Express storage and z/OS 1.13 (Dec. 2012)

– Provides improvements in dynamic address translation and usage of translation lookaside buffer (TLB)

� DB Space Management Block Serialization Latch Improvements

– Split from single to multiple latches to improve heavy BMP workloads

� MEMDSENQMGMT Exploitation

– More efficient memory-based data set ENQ management improves allocation of large number of data sets

IMS Version 13

24

Other Reduced TCO Enhancements

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

� Convert OTMA and IMS Connect STORAGE calls to CPOOL

� Remove unnecessary clearing of OTMA buffers

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

� OSAM CML Lock Reduction

� General instruction optimization (replacing STCK with STCKF, long displacement facility exploitation)

� IMS cache manager spin loop elimination

� CQS mainline modules changed to use branch-relative branching

� Cache efficiency improvements (DPST blocks packed into a single IPAGE to keep cache references localized)

� IMS page load service algorithm optimization

� IMS dispatcher optimizations

IMS Version 13

25

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

26

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

27

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

28

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

29

IMS DRD Enhancement

� Support for the IMS repository (a single centralized store for resource

definitions in an IMSplex) enhanced to validate resource attributes

between associated resources when a resource definition is added

to, updated in, or deleted from the IMSRSC Repository

– Validates transaction, routing code, and program attributes

� Also provided through the IMS 12 service process

– APAR PM32805 / PTF UK75915

� Benefits

– Simplifies management of the DRD resources

IMS Version 13

30

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

31

� 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

32

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

33

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

34

/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

35

/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

36

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

IMS Version 13

37

IMS 13 Transaction Manager and Connectivity Enhancements

� Callout function enhancements

� ISC Over TCP/IP

� OTMA enhancements

� Non-Discardable Message Exit (DFSNDMX0) enhancements

IMS Version 13

38

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

39

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

OTM

A

TM/CTL

Services

IMS

Connect

TCP/IP

user-written Client

WebSphere

IMS TM resource adapterApplication

Program

ICAL

MPP/JMP/IFP/BMP/JBP

OTMA

DescriptorOTMA

Descriptor

IMS Version 13

40

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

IFP, MD BMP

OTMA

Application

Program

ICALIMS SOAP GATEWAY

IMS

Connect

TCP/IP

user-written Client

WebSphere

IMS TM resource adapter

IMS Version 13

41

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

42

Synchronous Program Switch...

� 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

43

Synchronous Program Switch...

� Considerations

– To use synchronous program switch in a shared queues environment, all of the participating IMS systems must be Version 13 or later and have a MINVERS value of 13.1

– New design implications

• Timeout values

• Transaction Expiration

• Late Responses

• LTERM Override

• ALTPCB destinations

• Multiple ICALs

• Recursive requests

• Holding database locks across an ICAL request

– Increased importance for performance tooling

IMS Version 13

44

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

45

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

46

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

47

OTMA Enhancements ;

� OTMA destination descriptor enhancements

– TYPE={MQSERIES}

• Provides asynchronous callout and messaging support (ISRT ALTPCB)

– EXIT={YES | NO}

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

� Corresponding enhancement to IMS Type-2 OTMADESC commands

– [CREATE | UPDATE | DELETE |QUERY] OTMADESC

• Recovered across warm and emergency restarts

� Benefits

– Simplifies asynchronous messaging to WMQ

– Removes the need to code the OTMA exits, DFSYPRX0 and DFSYDRU0

– Provides dynamic change capability with the Type-2 commands

IMS Version 13

48

OTMA Enhancements

� OTMA early termination notification

– Enhancement that allows OTMA to leave the XCF group earlier in

termination processing

• Allows OTMA clients (IMS Connect, WebSphere MQ, OTMA C/I) to be

notified of the termination via their XCF Group Exit

– Can route requests to other systems

– Addresses issues associated with transactions messages being accepted but

not processed

– Function retrofitted to IMS 12: APAR PM73869 / PTF UK90361

IMS Version 13

49

Enhancements for the Non-Discardable Messages Exit Routine

� Customer requirement for a new function to PSTOP an abending

transaction

– Stops scheduling but allows queueing to continue

� New functions provided by for the DFSNDMX0, the Non-Discardable

Messages exit routine

– IMS 11 APAR PM67950 / PTF UK81040

– IMS 12 APAR PM45943 / PTF UK71989

– Included in IMS 13

IMS Version 13

50

Summary of IMS 13 Transaction Manager and Connectivity Topics

� Callout function enhancements

� ISC Over TCP/IP

� OTMA enhancements

� Non-Discardable Message Exit (DFSNDMX0) enhancements

IMS Version 13

51

IMS 13 Database and DBRC Enhancements

� Database Versioning

� HALDB Alter

� DEDB Alter

� DBRC Enhancements

IMS Version 13

52

Database Versioning

� IMS 13 allows application programs to use different versions of the

same physical database

– Multiple views of the physical data are maintained in the IMS catalog

– Application programs can use different views of the same physical IMS

database

� Benefit

– Customers can support multiple versions of an IMS database

– Physical database structure can be changed without having to modify all

the exiting application programs using the database

52

IMS Version 13

53

Database Versioning Overview

� Provides the ability to assign user-defined version identifiers to

different versions of an IMS database structure

� Enables structural changes to a database while providing multiple

views of the physical IMS data to various applications

� Applications referencing a new physical database structure can be

brought online without affecting applications that use previous

database structures

� Applications not requiring sensitivity to the new physical database

structure can continue to access the database without any

modifications or recompilation

53

Can be used in conjunction with IMS 13 database ALTER functions.

IMS Version 13

54

Database Versioning Overview ;

� Database Versioning supports the following database types

– DEDB

– HDAM

– HIDAM

– PHDAM

– PHIDAM

� Database Versioning supports the following structure changes to a

database

– For all supported database types

• Increasing the length of a segment

• Adding a new field to undefined space at the end of a segment

– For Full-Function and HALDB database types only

• Adding a new field that defines an alternative mapping of bytes in a

segment

54

IMS Version 13

55

� Database Versioning requires IMS catalog enablement

– DBD version definitions must be stored in the IMS catalog

• Populate catalog with DBD version definitions

� All systems in an IMSplex must be running IMS 13

– DBRC MINVERS value of “13.1” required

Database Versioning Overview ;

55

IMS Version 13

56

� 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

� 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 requires enablement of the IMS catalog

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

Database Versioning Requirements

IMS Version 13

57

� 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

58

HALDB Alter

� IMS 13 provides ability to make structural changes to a HALDB

database without a database outage

– Structural changes can be made to DB segment definitions

– HALDB Online Reorganization is used to apply the structural changes to

the online database

– Online Change process is used to activate the new ACBLIB member(s)

in the online IMS system

� Benefit

– Eliminate a database outage when structural changes must be made to

segment definitions in a DBD

– Improved online availability of HALDB databases

58

IMS Version 13

59

HALDB Alter Overview

� Structural changes can be made to online HALDB databases

– PHDAM

– PHIDAM

� Types of structural changes

– Add a new field to space at the end of an existing segment

– Define new fields that remap existing fields and space in a segment

– Increase the length of an existing segment

59

A

B C

A

CB

IMS Version 13

6060

FIELD 1

FIELD 1

FIELD 2 Space

FIELD 2New

FIELD 3

Add a new field to space at the end of a segmentExample 1

Example 2

FIELD 1

FIELD 1 FIELD 2

FIELD 2 Space

New

FIELD 3

Sp.

Sp.

IMS Version 13

6161

FIELD 1

FIELD 1

FIELD 2

SpaceFIELD 2

Define new fields to remap existing fields in a segmentExample 1

Example 2

FIELD 1

FIELD 1 FIELD 2

FIELD 2

Space

Overlay

FIELD 2A

New

FIELD 3

Overlay

FIELD 2B

New

FIELD 3

Space

Space

Overlay

FIELD 2ASp.

Sp.

IMS Version 13

6262

FIELD 1

FIELD 1

FIELD 2

SpaceFIELD 2

Example 1

Example 2

FIELD 1

FIELD 1 FIELD 2

FIELD 2

Space

Overlay

FIELD 2A

New

FIELD 3

Overlay

FIELD 2B

New

FIELD 3

Space

Space

Overlay

FIELD 2ASp.

Sp. Space

Space

Increase the length of an existing segment

IMS Version 13

63

HALDB Alter Overview ;

� After changes are made to segment definitions in a DBD

• Online Reorganization process is used to alter the online database from

the current structure to the new structure

• Type-2 INITIATE OLREORG

• DB unload / reload not required

• Online Change process is used to activate the changed ACBLIB members

in the IMS online system

• Application programs can start using the new database structure

63

IMS Version 13

64

HALDB Alter Prerequisites

� Software requirements

– All systems in an IMSplex must be running IMS 13

• DBRC MINVERS value of “13.1” required

– Type-2 Command environment required

• Common Service Layer (CSL)

– Structured Call Interface (SCI)

– Operations Manager (OM)

• Type-1 /INITIATE OLREORG command is not supported

IMS Version 13

65

DEDB Alter

� IMS 13 adds ability to dynamically modify a DEDB Area while the Area

remains online

– Alter the physical attributes of a DEDB Area

– SIZE, UOW, or ROOT specifications

– Change the randomizer used for a DEDB Area

� Benefits

– Improved DEDB Area availability

• Make definitional modifications without taking the Area offline

• Improved management of DEDBs

• Provide flexibility in implementing Area changes into the system

• Eliminate system down time for DEDB definition changes

IMS Version 13

6666

DEDB Alter Overview

• A new DEDB Alter utility is provided to dynamically modify a DEDB

database

• Runs as a standard Fast Path IFP utility

• DEDB Areas remain online during utility execution

• A 2-stage randomizer must be used

• Enables areas to be processed individually

• DEDB alter does not support DEDB databases in VSO or SVSO mode

• Must be unloaded with /VUNLOAD before executing Alter utility

• DEDB areas to be altered must be registered to DBRC

• DBRC MINVERS value in RECON for all IMS subsystems that share

the DEDB area must be "13.1" or later

– If SDEPS present, only the randomizer name can be changed

IMS Version 13

67

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 / PTF UK80026 to IMS 11

• Allows IMS 11 to understand IMS 13 RECON records

– IMS 12 to IMS 13

• Apply DBRC coexistence SPE APAR PM53139 / PTF UK80027 to IMS 12

• Allows IMS 12 to understand IMS 13 RECON records

IMS Version 13

68

Summary of IMS 13 Database Manager and DBRC Topics

� Database versioning

� HALDB Alter

� DEDB Alter

� DBRC enhancements

IMS Version 13

69

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

– Synchronous program switch

– ISC TCP/IP Links

– OTMA destination descriptor

enhancements

– and more!

69