iims 13 systems enhancements and migration

© 2013 IBM Corporation

®

IMS Version 13

IMS 13 System Enhancements

and Migration

Diane Goff IBM IMS Advanced Technical Skills

[email protected]

IMS Version 13

IMS 13 General Availability Announced!

IMS 13 GA announced on 10/1/2013

for availability on 10/25/2013

IMS Version 13

IMS 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

Migration

IMS Version 13


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


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


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


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

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 been enabled in IMS Connect

Benefit

– Allows IMS Connect to listen for certain RACF events indicating that a change has been made to a specific UserID

• Avoids manual intervention

IMS Version 13

Reporting of Overall Health to WLM

WLM (Workload Manager) Health Report

– New function to automatically report the overall health of IMS Connect

• Allows Sysplex Distributor to use and take into account this

information for workload balancing

Benefit

– Allows WLM to know when resources are constrained or available

– Minimizes the possibility of Sysplex Distributor assigning work that IMS

Connect is unable to handle

IMS Version 13

Configurable TCP/IP backlog (Queue) size

New parameter TCPIPQ

– Allows users to configure the length of the queue in TCP/IP for

connection requests that have not yet been assigned a socket.

• Connection requests are held on this queue until IMS Connect

can assign a socket

– Overrides the default which is equal to the maxsoc value

– 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

Summary of IMS Connect Enhancements


– Enhances the flexibility of converter usage

• Directly impacts IMS Soap Gateway environments


– Improved efficiencies during error conditions

• Eliminates IMS Connect restart and user interactions


– Improved diagnostics and problem determination

• Avoids manual intervention

IMS Version 13

Summary of IMS Connect Enhancements ...

RACF Event Notification Facility (ENF) Support for cached RACF UserIDs (UID)

– Allows IMS Connect to listen for certain RACF events indicating that a change has been made to a specific UserID

Reporting of overall health to Workload Manager (WLM)

– 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

Configurable TCP/IP backlog (queue) size

– Provides a configurable option to increase the backlog queue size in TCP/IP to be greater than 50

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

IMS Version 13

Concurrent Application Threads Enhancement

Partition Specification Table (PST) used for

– Active dependent regions (MSG/BMP/IFP/JMP/JBP)

– CICS/DBCTL threads

– Open Database Access threads

Customers continue to require more PSTs!

– 31 dependent regions - 1980 (IMS 1.1.6)

– 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

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

Command Considerations – type-2 and type-1

The following DRD commands for transactions support a

MAXRGN parameter of up to the MAXPST= value

– CREATE TRAN

– CREATE TRANDESC

– UPDATE TRAN

– UPDATE TRANDESC

Output of the /DISPLAY TRAN command supports a 4 digit

decimal number for BAL() instead of a 3 digit number

The TRANSACT IMSGEN macro only supports MAXRGN=255

IMS Version 13

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

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

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

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


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


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


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

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

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

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

ESAF support in Java Dependent Regions (JDR)

Prior to IMS 13, the only external subsystem (ESS) that JDR

applications could access is DB2 using the DB2 RRS Attach Facility

(RRSAF)

– No access to other external subsystems such as WebSphere MQ

– DB2 RRSAF usage unique to JDR vs. other region types

• More complex external subsystem definitions

Need for consistent External Subsystem Attach Facility (ESAF)

interface across all region types for DB2

Need for less complex external subsystem definitions

Need support for other external subsystems

IMS Version 13

ESAF support in Java Dependent Regions (JDR)

With IMS 13, there are two methods for accessing DB2 from JDRs

– Access via the previously existing DB2 RRSAF interface

– Access via the standard ESAF interface

With IMS 13, the ESAF interface can be used in JMP/JBP regions to

access any ESAF defined to the IMS control region

– WebSphere MQ, DB2, WOLA (WebSphere Optimized Local Adapter)

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

IMS Version 13

Benefits of ESAF Support in Java Dependent Regions

JMP/JBP regions can now use the standard ESAF (External

Subsystem Attach Facility) for accessing external subsystems

such as DB2 for z/OS, WebSphere MQ, and WOLA

– Provides consistent External Subsystem Attach Facility (ESAF)

interface for DB2 across all region types

– Uses simplified external subsystem definitions

• Provides easier implementation than DB2 RRS Attach Facility

(RRSAF)

– More efficient interface compared to using the DB2 RRS Attach

Facility (RRSAF) for DB2 access

IMS Version 13

IMS Command Enhancements Overview …

Database versioning command enhancements

DBRC command enhancements

DEDB Alter command enhancements

/DIAGNOSE SNAP command enhancement

/DISPLAY POOL QBUF command enhancements

HALDB command enhancements

IMS Version 13

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


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

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

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

that they do not conflict with one another

– Example: a transaction updated to FP(E) will cause RM to check that the

associated program is defined as FP exclusive

• If conflict, EXPORT fails

Also provided through the IMS 12 service process

– APAR PM32805 / PTF UK75915

Benefits

– Simplifies management of the DRD resources

IMS Version 13

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

Delivered via IMS 12 SPE PM56010 (PTF UK79071)

Command:

– REFRESH USEREXIT TYPE(exittype)

– Refreshes the user exit types specified without bringing IMS down

– Eligible exit types are:

• ICQSEVNT

• ICQSSTEV

• INITTERM

• PPUE

• RESTART

USER_EXITS section in DFSDFxxx (where xxx is the value of the

DFSDF initialization parameter) read to pick up the EXITDEF

statements for the user exit type(s) specified on the command

– An optional MEMBER( ) parameter can be used to point to a different DFSDFxxx member

User Exit Dynamic Refresh Capability – IMS 12 SPE

IMS Version 13

IMS 13 User Exit Enhancements

Enhanced user exit services extended to additional IMS control region user exits

Users can now dynamically refresh more IMS user exit routines to bring in an updated version of the exit (or add/delete)

– Significantly reduces downtime since IMS control region no longer requires restart

Users can now display (QUERY) information about more user exits that are defined in the USER_EXITS section of DFSDFxxx

– Provides useful exit information to the user

Users can now code an exit to leverage IMS’s ability to call multiple routines of the same type from a single point within the exit

IMS Version 13

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

IMS Version 13

The exits listed can now leverage enhanced user exit services to:

– Use REFRESH USEREXIT to bring in new copy of an exit based on type

• Either all exits of a certain type as listed in DFSDFxxx will be refreshed or none

• Can also add/delete as long as DFSDFxxx updated first

– Use QUERY USEREXIT to display useful exit information

– Code multiple exits of the same exit type to be called from a single entry point

Benefits

– Expanded flexibility

– IMS availability is increased

– Management of user exits eased

Enhanced User Exit Services Added to More Exit Types

IMS Version 13


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

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

Security User Exits removed from Nucleus

User exits DFSCSGN0, DFSCTRN0 and DFSCTSE0 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

A workarea can be shared among the exits using the new

CTSECSEP and CTRNCSEP parameters rather than the old method

of v-type addressing which was used for sharing storage when they

were all in the nucleus

IMS Version 13

IMS Security Enhancements Benefits

Removal of SECURITY macro

– Significant reduction in system programmers’ time/effort required in

maintaining IMS systems

– Management of security definitions eased

– System definition (SYSGEN) process made more simple

Removal of selected user exits from IMS nucleus

– Exits are easier to maintain

– Linking to IMS nucleus no longer necessary when one of the exits has

been changed

– Usage of 24-bit storage reduced

IMS Version 13

/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

/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

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

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

ABENDU240 will now be enforced in IMS dependent regions that are running 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 PM861063 / UK94216

IMS Version 13

IMS 13 Migration

IMS Version 13

Packaging

IMS 13 program number: 5635-A04

FMID Feature Description

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

IMS Version 13

Minimum software level prerequisites

– z/OS Version 1 Release 13 (5694-A01) or later

• When running IMS Version 13 on z/OS Version 1 Release 13, APAR

OA39392 / PTF UA66823 must be installed.

• IBM High-Level Assembler Toolkit Release 5 (5696-234)

• z/OS V1R13.0 Security Server RACF V1R13.0 or later, or an equivalent

product, if security is used.

– IRLM Version 2.3 if IRLM is used

Software Prerequisites…

IMS Version 13

Software Prerequisites ...

Minimum software levels for optional functions…

– Java Dependent Regions requires JDK 6.0.1

– ISC TCP/IP requires CICS 5.1

– Depending on the environment, the IMS Universal Drivers require:

• IBM JDK 6.0.1 or later

• DB2 V9.1 or later

• WAS V7 or later

• CICS V4.1 or later

– DB Versioning requires implementation of the IMS Catalog

Check Release Planning documentation at GA for additional

prerequisites/coexistence/migration items

IMS Version 13

Software Prerequisites

Minimum software levels for other middleware

– IMS 13 supports interactions with

• DB2 9 or later

• CICS 3.2 or later

– CICS 5.1 is required for ISC TCP/IP support

• MQ for z/OS: Versions V7.0.1 or later

IMS Version 13

Hardware Prerequisites…

IMS 13 runs only on 64-bit processors running in z/Architecture mode

– Processors must also support the Long-Displacement Facility of the

z/Architecture

– ESA mode is not supported

– For a list of z/Series machines see: www.ibm.com/systems/z/hardware

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

IMS Version 13

Hardware Prerequisites

Sysplex Data Sharing (including Data Caching and VSO Data Sharing)

– Coupling Facility (CF) level 9, or later

Shared Queues and Shared EMH support

– Coupling Facility level 9 or later

– System-managed CF Duplexing

• 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

Support Status of IMS Versions

IMS 10

– Generally available on October 26, 2007

– End of service was November 12, 2012

IMS 11


– End of service has not been announced

IMS 12

– Generally availability on October 28, 2011


IMS 13



IMS Version 13

IMS 13 Supported Connections

ISC is supported with

– IMS 13, IMS 12, and IMS 11

– CICS Transaction Server V 4.2, V4.1, V3.2 and V3.1

– CICS Transaction Server V 5.1 for ISC TCP/IP connectivity

– User-written software

MSC is supported with

– IMS 13

– IMS 12

– IMS 11

Shared Queues is supported with

– IMS 13

– IMS 12

– IMS 11

IMS Version 13

Books remain the same as IMS 12

Information Center contains information on IMS 13

IMS Library Updates

IMS Version 13

Withdrawn Support …

IMS 11 is the last release to support the SMU-to-RACF utilities

– IMS 9 was the last version of IMS to support SMU

– Migration from SMU to RACF or an equivalent product should have been

done on IMS 9 or earlier

IMS 12 is the last release to support the SECURITY macro in system

definition

– Use the initialization parameters in IMS 13

– RCLASS and SECCNT for V12 and V11

• PM48204/UK74051 V12 SPE, PM48203/UK74050 V11 SPE

IMS Version 13

Withdrawn Support …

IMS Enterprise Suite V2.1 is the last release to include DLIModel utility

plug-in

– Going forward, use IMS Enterprise Suite Explorer for Development, which

provides enhanced features over those provided in the DLIModel utility plug-in

JCA 1.0 resource adapter is no longer enhanced, use the IMS Universal

DB resource adapter instead

IMS 13 is the last release to support IMS Connect SSL function

– Instead, use IBM z/OS Communications Server Application Transparent

Transport Layer Security (AT-TLS) to set up Secure Socket Layer (SSL) on

TCP/IP connections to IMS Connect

IMS 13 is the last release to support IMS MFS Web Enablement.

– Customers using this function should migrate to IBM Rational Host Access

Transformation Services (HATS).

IMS Version 13

Withdrawn Support

IMS 11 is the last release to support the Knowledge Based Log Analysis

(KBLA) facility

– Customers using this function should migrate to use other IMS-provided analysis

utilities and reports, such as

• Fast Path Log Analysis utility (DBFULTA0)

• File Select and Formatting Print utility (DFSERA10)

• IMS Monitor Report Print utility (DFSUTR20)

• Log Transaction Analysis utility (DFSILTA0)

• Offline Dump Formatter utility (DFSOFMD0)

• Statistical Analysis utility (DFSISTS0),

• Other complementary products, such as IMS Problem Investigator, IMS

Performance Analyzer, or similar products

IMS Version 13

IMS System Topics


Concurrent Application Threads

Reduced Total Cost of Ownership (TCO)


IMS CQS Enhancement

IMS DRD Enhancement

IMS User Exit Enhancements


/DIAG Command Enhancements

Migration

iims 13 systems enhancements and migration

Technology